whiterhino1978 Here ...
I recently purchase a nabi 2, followed post instructions " Nabi 2 Root and Gapps Install ".
I used option 1) worked until Team Win Recovery loaded, error can't find gapps. I went install
found gapps.zip in /sdcard ran it, worked. Than I used option 2), it did a backup couldn't find
root.zip error, so use install option in recovery found root.zip on device ran it..
My backup is stock with gapps...
I have a rooted nabi tablet 2 with google apps on to stock rom ..
I notice stockimages files are available here, how i use the to return to stock ?
Would like to install all updates first, then root with gapps.
Thanks For Your Time...
ps i'm a noob "I can follow instructions..." I've rooted 2 htc hero, nook color, 2 nook tablets...
I also would like the commands for returning to stock, just in case. Anyone have these commands for ADB?
Here ya go, easily adapted if you are using windows
http://forum.xda-developers.com/showpost.php?p=35287470
i went completely to stock as far as the rom goes but when i flash the stock recovery and boot it, it has an android with an exclamation mark on it and nothing else. can anybody tell me how to fix that? thanks!
Related
i have spent the last 2 days searching these xda forums. btw u guys rock. i would not have gotten throgh rooting and putting a custom rom my first phone if it wasn't for you. anyway, i found out the hard way that trying to mod an atrix with 2.3.6 on build 4.5.141 is not easy. after many wrong turns, i was finally able to unlock my bl and get my phone rooted. then i was able to play with cwm. i was able to backup my current rom, but cannot reboot into recovery. this made me curious so i tried to enter android recovery which failed as well. both ways gives me the droid guy and a triangle. i went thru all this work so i could flash a cool rom ( thinking cm7 since it seems to be stable, but i wanna check around). since i cant reboot into recovery, im kind of at a stand still. i did my best to search through the forums before i asked any stupid questions, but im stuck. please help me.
What have you tried to get into recovery? How did you install a recovery?
Delete install-recovery.sh @ /system/etc.
Then, install Rom Racers recovery via fastboot.
Sent from my CM7 Atrix.
I tried to reboot into recovery from rom manager. When that failed i powered phone up holding volume down, then scrolled to android recovery option. i used automatic unlock v4.2 to unlock bl's (option 1). I did not use option 2 to root since i was not familiar with tenfar cwm. So i rooted using method #1 from rootzwiki's atrix page. I then chose option 6 for cwm recovery and rom manager. I went to market, downloaded rom manager. When i opened rom manager, i clicked flash cwm recovery. then tried to reboot into recovery and....dead end.
thanks swiftks. i was actually looking into following your advice. just didnt want to post until i tried. anyway, i already have rom racers zip downloaded onto my internal memory. the plan was to use rom manager to install rom from sd card just like its says on the noob page. just was never able to get that far. so im sorry for my ignorance, but how do i go about deleting that file. and how do i use fastboot to install rom racers recovery? im trying my best to learn. i broke my captivate a few days ago and this phone is new to me. plus, im not exactly a tech expert. i just follow directions well and have learned just enough to get myself into trouble
Ill let swift answer from here cuz im stumped. I do know to delete the file, you need root explorer (can find on play store) and root access. Open root explorer and navigate to system/etc then find the file and delete it.
update. so before i went hunting down root explorer i tried to flash cwm recovery through rom manager one last time (3rd time, every time said it was successful. lo and behold, i got into recovery. i am now going to attempt to upgrade to rom racers cwm. i did at one point download a fastboot file, just cant remember if i installed correctly cuz i was pretty drunk last night. how can i verify. i do definately have sdk tools tho. checked for adb devices. is fastboot under sdk tools? or was that a dumb question?. nevermind. i do have fastboot. found my fastboot device. Then entered "fastboot erase recovery" failed 000300003. im pretty sure this needs to be deleted as u suggested. when i got recovery to open, i went back and tried to finish installing romracers cwm via rom managers install from sd option. got the triangle again. reflashed cwm thru rom manager and was able to boot into recovery. from there i tried to install zip from sd, installation successful, reboot propmpt. rebooted. wnet directly to rom manager, tried to reboot into recovery... triangle. reflash thru rm, recovery boots. reboot system. tried to reboot into recovery, but triangle is back. the only way for me to get to recovery is reflash it everytime before i use it. this has got to be because i never deleted the path you suggested, right? im really tryin here, but i feel like im stuck inside a real life boot loop
twinlakesnake said:
update. so before i went hunting down root explorer i tried to flash cwm recovery through rom manager one last time (3rd time, every time said it was successful. lo and behold, i got into recovery. i am now going to attempt to upgrade to rom racers cwm. i did at one point download a fastboot file, just cant remember if i installed correctly cuz i was pretty drunk last night. how can i verify. i do definately have sdk tools tho. checked for adb devices. is fastboot under sdk tools? or was that a dumb question
Click to expand...
Click to collapse
On my computer the path for fastboot is android-sdk-tools/platform-tools/fastboot
i downloaded root explorer. deleted install-recovery.sh @ /system/etc. once i did this i was able to use fstboot commands from rom racers page. fastboot erase recovery was successful. then tried 'fastboot flash recovery recovery-atrix5.img'
error: cannot load.
im chipping away at it but wow. thoght i would be flashing cm7 by now. I do appreciate your patience, lord knows mine is running low
twinlakesnake said:
i downloaded root explorer. deleted install-recovery.sh @ /system/etc. once i did this i was able to use fstboot commands from rom racers page. fastboot erase recovery was successful. then tried 'fastboot flash recovery recovery-atrix5.img'
error: cannot load.
im chipping away at it but wow. thoght i would be flashing cm7 by now. I do appreciate your patience, lord knows mine is running low
Click to expand...
Click to collapse
At this point are you still not able to get in recovery?
finally, success! just figured out what the hell im doing with fastboot. unzipped romracers cwm to same folder containing fastboot, finished last part of cmd (fastboot flash recovery recovery.img then fastboot reboot and voila! i now have rom racers cwm. i will now enter rom manager, backup rom (which i understand is a nandroid process). then start researcing cm7 and eventually some more roms to play with. thanks for all of your help
once recovery was fixed, everything was a breeze. put cm7zip on internal sd, installed from recovery, data wipe then cache wipe, then reboot. iput google apps zip on internal sd, installed from recovery. fancy new phone! only took me 3 days to do it. i hope someone else can learn from my mistakes
twinlakesnake said:
once recovery was fixed, everything was a breeze. put cm7zip on internal sd, installed from recovery, data wipe then cache wipe, then reboot. iput google apps zip on internal sd, installed from recovery. fancy new phone! only took me 3 days to do it. i hope someone else can learn from my mistakes
Click to expand...
Click to collapse
Congrats
I have a Nabi 2 UK for my son and had GAPPS installed but stayed on the 1.9.37 version as the OAT would not work.
I now see that I can get the tablet up to 4.1 and get GAPPS as well but I seem to be defeated at the last step every turn but the 'dead' android on it's back.
I don't have the original back up to start from.
I've gone to the 1937 stock image and via TWRP, the OAT'ed to 2.1, but the second 2.3 update fails with the dead android
I've tried 2311 which also fails in the same way.
I've seen some conversations on these boards but the file outlined are often out of bandwith and I can't comment on the threads to ask for help.
So now I'm back to 1.9.37 but I also can't seem to reinstate GAPP using Nabi Labs tools I as it braks the nabi mode and the tablet won't work.
All in all this is turing out to be a massive waste of time. Any suggestions how I can salavge this?
Cheers
Fulhair
Fulhair said:
I have a Nabi 2 UK for my son and had GAPPS installed but stayed on the 1.9.37 version as the OAT would not work.
I now see that I can get the tablet up to 4.1 and get GAPPS as well but I seem to be defeated at the last step every turn but the 'dead' android on it's back.
I don't have the original back up to start from.
I've gone to the 1937 stock image and via TWRP, the OAT'ed to 2.1, but the second 2.3 update fails with the dead android
I've tried 2311 which also fails in the same way.
I've seen some conversations on these boards but the file outlined are often out of bandwith and I can't comment on the threads to ask for help.
So now I'm back to 1.9.37 but I also can't seem to reinstate GAPP using Nabi Labs tools I as it braks the nabi mode and the tablet won't work.
All in all this is turing out to be a massive waste of time. Any suggestions how I can salavge this?
Cheers
Fulhair
Click to expand...
Click to collapse
Hi.
I had a similar issue (US ROM though). I had dead Android guys, messages in TWRP that I didn't have an operating system installed and all kinds of other issues. I really thought that I had bricked the Nabi as I was up against a wall and nothing I was finding online was working.
I have posted this before elsewhere -- this is what I did to get out of it:
I think when I was installing the JB version of TWRP I also tried to change the screenlock image not realizing that the process had changed for JB. I had a complete mess with very similar if not identical issues as you.
What I did:
1. Make sure TWRP 2.6.3.0 for Jellybean is on the Nabi.
2. Download the stock 2.3.11 ROM from the Nabi wiki site and unzip it into a folder on your PC.
3. Next you need to copy the 4 recovery files from your PC to your SD card. I put the SD card into my PC and copied the files over putting them into a TWRP back up folder on the SD card. Now, in order for Jellybean TWRP to recognize the backup, I had to fool it into thinking I had a "good" existing Jellybean TWRP backup and rename the TWRP backup folders to something like this:
TWRP\BACKUPS\0f41000001000000\2014-01-24--09-54-07 JRO03C\
4. Put the SD card back into the Nabi and then boot into TWRP mode.
5. Do a restore from there.
It *should* install a clean fresh copy of Jellybean on the Nabi. It does take what seems like an eternity for it to get past the spinning circle with the NABI logo when it's loading for the first time so be patient.
You may need to alter some of this since you are in the UK though.. but the main suggestion is to put whatever copy of the ROM onto an SD card (remember to follow the correct directory format for either ICS or JB) and then restore via TWRP to get you running.
2girlzdad said:
Hi.
I had a similar issue (US ROM though). I had dead Android guys, messages in TWRP that I didn't have an operating system installed and all kinds of other issues. I really thought that I had bricked the Nabi as I was up against a well and nothing I was finding online was working.
I have posted this before elsewhere -- this is what I did to get out of it:
I think when I was installing the JB version of TWRP I also tried to change the screenlock image not realizing that the process had changed for JB. I had a complete mess with very similar if not identical issues as you.
What I did:
1. Make sure TWRP 2.6.3.0 for Jellybean is on the Nabi.
2. Download the stock 2.3.11 ROM from the Nabi wiki site and unzip it into a folder on your PC.
3. Next you need to copy the 4 recovery files from your PC to your SD card. I put the SD card into my PC and copied the files over putting them into a TWRP back up folder on the SD card. Now, in order for Jellybean TWRP to recognize the backup, I had to fool it into thinking I had a "good" existing Jellybean TWRP backup and rename the TWRP backup folders to something like this:
TWRP\BACKUPS\0f41000001000000\2014-01-24--09-54-07 JRO03C\
4. Put the SD card back into the Nabi and then boot into TWRP mode.
5. Do a restore from there.
It *should* install a clean fresh copy of Jellybean on the Nabi. It does take what seems like an eternity for it to get past the spinning circle with the NABI logo when it's loading for the first time so be patient.
You may need to alter some of this since you are in the UK though.. but the main suggestion is to put whatever copy of the ROM onto an SD card (remember to follow the correct directory format for either ICS or JB) and then restore via TWRP to get you running.
Click to expand...
Click to collapse
Thanks for the outline. Sorry if I'm being a bit dim but how do I get the 2.6.3.0 TWRP onto it?
I've got the NaviLabs GUI and TWRP'd up to v 2.6.1.0 but need to get the Jelly Bean version.
I've tried the zip install with twrp-recovery-JBNV7AUS-263 but it just breaks TWRP and won't boot.
Thanks again.
Fulhair said:
Thanks for the outline. Sorry if I'm being a bit dim but how do I get the 2.6.3.0 TWRP onto it?
I've got the NaviLabs GUI and TWRP'd up to v 2.6.1.0 but need to get the Jelly Bean version.
I've tried the zip install with twrp-recovery-JBNV7AUS-263 but it just breaks TWRP and won't boot.
Thanks again.
Click to expand...
Click to collapse
Get whatever TWRP you want
http://forum.xda-developers.com/showpost.php?p=48891386&postcount=76
Follow this http://forum.xda-developers.com/showpost.php?p=49956448&postcount=49 to put that recovery in Nabilabgui except use
For XP
C:\Documents and Settings\username\Local Settings\Apps\2.0\xxx\xxx\nabixxxx\2\recovery\new
or Vista/7/8
C:\Users\username\appdata\local\apps\2.0\xxx\xxx\n abixxx\2\recovery\new
The post is for the JR I think the above will be right for the Nabi2, I'm mobile so I can't check.
aicjofs said:
Get whatever TWRP you want
http://forum.xda-developers.com/showpost.php?p=48891386&postcount=76
Follow this http://forum.xda-developers.com/showpost.php?p=49956448&postcount=49 to put that recovery in Nabilabgui except use
For XP
C:\Documents and Settings\username\Local Settings\Apps\2.0\xxx\xxx\nabixxxx\2\recovery\new
or Vista/7/8
C:\Users\username\appdata\local\apps\2.0\xxx\xxx\n abixxx\2\recovery\new
The post is for the JR I think the above will be right for the Nabi2, I'm mobile so I can't check.
Click to expand...
Click to collapse
Good advice. Thanks for the TWRP instructions,
I can now get the TWRP v2.6.3.0 on, but only the ICS version will boot, The Jelly bean install won't bring up the TWRP screens. I've even tried updating to 2311 from the ICS version and then trying to update to the TWRP JB version with no joy.
Now I can't even get the nabi to connect to the usb in Nabi Lab GUI This is doing my head in!!!
Fulhair said:
Good advice. Thanks for the TWRP instructions,
I can now get the TWRP v2.6.3.0 on, but only the ICS version will boot, The Jelly bean install won't bring up the TWRP screens. I've even tried updating to 2311 from the ICS version and then trying to update to the TWRP JB version with no joy.
Now I can't even get the nabi to connect to the usb in Nabi Lab GUI This is doing my head in!!!
Click to expand...
Click to collapse
If going to 2311 you need to update bootloader. That is in the addonfix zip. Then JB twrp should work.
aicjofs said:
If going to 2311 you need to update bootloader. That is in the addonfix zip. Then JB twrp should work.
Click to expand...
Click to collapse
Okay, so I managed to get back to TWRP 2.6.3.0 under ICS. I then install the 2311 rom, which succeeds. As per instructions, before I reboot I go back and try to install the addon zip in TWRP.
But I get an error
'E:Error executing updater binary in zip '/external_sdcard/addonzip'
Error flashing zip '/external_sdcard/addonzip'.
I'm not sure if the error is something with TWRP or the addon.zip.
One of the microsd I have won't show the addonzip and none of the other TWRP recovery roms..and yes I have checked the directory structure.
Any ideas?
Thanks
Fulhair said:
Okay, so I managed to get back to TWRP 2.6.3.0 under ICS. I then install the 2311 rom, which succeeds. As per instructions, before I reboot I go back and try to install the addon zip in TWRP.
But I get an error
'E:Error executing updater binary in zip '/external_sdcard/addonzip'
Error flashing zip '/external_sdcard/addonzip'.
I'm not sure if the error is something with TWRP or the addon.zip.
One of the microsd I have won't show the addonzip and none of the other TWRP recovery roms..and yes I have checked the directory structure.
Any ideas?
Thanks
Click to expand...
Click to collapse
Okay, I abandoned the addon.zip and went back to 2.1.27 rom and OAT over to get to the last update which failed.
Then installed the OAT2.zip via TWRP and bingo! Now working on Jelly Bean with Google Play - okay it's now the US version but it works
I would caution that the zip install had to be installed on the internal SD not the external one.
But otherwise a BIG thank you to all for building the tools to let me do the update and for your support.
Cheers:highfive:
Hi All, I rooted my Verizon GS4 with this method "[GUIDE] Root for Verizon Galaxy S4 ***VRUAMDK Build Only!***" back before the first update so I have Root with Baseband I545VRUAMDK, Build JDQ39.I545VRUAMDKand Kernal 3.4.0-562219. I haven't tried to install any ROMs since then but started to get the itch so I started refreshing myself on the process and found that when I try to reboot into CWM Recovery it boots to Android System Recovery 3e. I'm looking for guidance on how to get CWM working properly. ROM Manager says I am using CWM 6.0.4.7. Any help will be appreciated.
Thanks
jpp2109 said:
Hi All, I rooted my Verizon GS4 with this method "[GUIDE] Root for Verizon Galaxy S4 ***VRUAMDK Build Only!***" back before the first update so I have Root with Baseband I545VRUAMDK, Build JDQ39.I545VRUAMDKand Kernal 3.4.0-562219. I haven't tried to install any ROMs since then but started to get the itch so I started refreshing myself on the process and found that when I try to reboot into CWM Recovery it boots to Android System Recovery 3e. I'm looking for guidance on how to get CWM working properly. ROM Manager says I am using CWM 6.0.4.7. Any help will be appreciated.
Thanks
Click to expand...
Click to collapse
From what I've read about that issue is people have had to Odin back to stock then start over. Now maybe you could try installing another recovery like Philz maybe using Odin or try Goo for TWRP before you Odin back to mdk and go through all that.
Sent from my SCH-I545 using Tapatalk
I had a similar thing a few years ago, with what I know now I think the recovery is temporarily flashed with CWM to gain root and stock recovery is replaced after, I'd look for an actual CWM recovery to flash in.
Same applied to me using a ROM Manager, said it was v.xxx made a backup, flashed a ROM, turns out was left without a backup..... noob-old days
Bashing away at my HTC Desire C
Thank you for the solid replies, I'm interested in getting experience with the other recovery methods anyway so I'll try those and worse case I start from scratch.
I have pretty much this same issue. I was happily running 6.0.44 CWM, installed via CWM.
Then I happened to check and see there's an update to 6.0.47. I installed via ROM manager which reported success. Except that it isnt. I basically have 2 recoveries as far as ROM manager is concerned. It thinks I'm on 6.0.47, but 6.0.44 is what boots. I'm betting it's the same issue you have.
I re-flashed Twrp trying to fix it. Now twrp is what recovery always boots; but Rom manager still thinks 6.0.47 is installed. Rom manager shows BOTH recoveries in the "Recovery already installed" menu.
Seems the issue here is the 6.0.47 when flashed via Rom manager. It bugs the crap out of me that it seems like I have 2 recoveries installed somehow. Not sure how that's possible, but everything seems like it's functioning for me.
Compare the sizes of the recoveries, one thing I've come across is when you flash a new .img in because of the NAND chip process for writing/erasing I have had 'remnants' from previous files.
In one respect it is unlikely but I wouldn't rule it out until you check yourself. It could just be left on the list as a marker that it has previously been installed.
Personally I don't use ROM Managers now, it's into TWRP Recovery and backup from there
Bashing away at my HTC Desire C
Look Like I'll Have to Start From Scratch
I'm just getting back to this because work was crazy. No Matter what recovery I try always comes up with Android System Recovery 3e. Stock MDK and re-root it is.
Maybe try using GooManager to install TWRP after you've gone back to stock.
Hello dear community
This is my very first thread I am making on this website, so please pardon me if I am on the wrong page of this website.
Anyways, I'm more or less desperate. I saw a youtube tutorial on how to install Android 4.4 Kit Kat on a Samsung Galaxy Note N7000 and I heard I'd need root AND a custom recovery.
Because I'm a total newbie to this kind of stuff, I tried the very first thing I saw that had something to do with custom recovery, because I already had my phone rooted. So, I looked up a tutorial on youtube on how to install CWM custom recovery and ended up with installing it successfully, but now my phone is stuck in a bootloop. As I already mentioned, I am a newbie and therefore I am very desperate at the moment, you know.
The only thing I can do is go to Recovery Mode, but if I try to turn the phone on it gets stuck in a bootloop (It actually doesn't loop at all, it just freezes at the moment when the Samsung Galaxy Note logo appears and doesnt do anything after that.).
I think my problem is that I actually threw a new Kernel on my phone, because the video title says "How to install Kernel with CWM [...]"
I would be very very very very very grateful if anyone was kind enough to help me get out of this!
I really need help!
Thanks!
PS.
If this helps you help me:
This happened when I had Android 4.1.2 installed.
There's going to be 2 ways to get out of this:
1) Reinstall the stock firmware via Odin.
2) Install a custom rom via recovery.
Personally, I'd go with number 2 because a) you wanted to update anyway and b) if you have the right recovery and rom, it'll be easier as you can just put the files you need on an external SD card and install via the custom recovery. Now, not all recoveries are able to flash any file. Many times you need specific ones to install the newer android versions. So, if you are wanting to install something 4.4 based, then using a recovery that was made, say, last year, probably will not work well if at all.
Another thing to try first, is to wipe the cache and dalvik cache in recovery since you said you tried to install a kernel. It is always recommended to wipe these when installing (assuming you did pick a compatible kernel with what you were trying to install).
Hello :angel: I'm kind of new to modding android and ran into a few issues. Basically I want to get Paranoid Android on my Galaxy S4 sgh-i337 running 4.4.2.
I rooted my device using towelroot but have failed to install a custom recovery. Both CWM and TWRP said they installed successfully but ended up with the same problem; when I selected reboot in recovery mode it would reboot saying Samsung Custom and then go into odin mode saying "Could not do normal boot".
I'm not sure if I installed CWM/TWRP correctly, as all the guides I found online were outdated. I installed the recoveries from the corresponding apps (CWM - ROM manager, TWRP - TWRP manager)--but like I said, both apps said recoveries were successfully installed. I also tried getting CWM using Loki on my phone + terminal emulator, but the terminal said something about loki not being the correct version for my device.
In CWM I tried the option to flash a custom ROM from sd card, but it didn't seem to recognize any files on the card while the normal samsung storage did.
So now I'm really confused and frustrated and can't seem to find answers anywhere. I would be really grateful if someone could guide me in the right direction in an easy to understand way.
Thanks for any help!