Related
Phone Details
Motorola Atrix 4G AT&T (bought around June 2011 Time frame)
System Version
4.5.91.MB860.ATT.en.US
Model Number
MB860
Android Version
2.34
Baseband Version
N_01.77.30P
Webtop Version
WT-1.2.0-110
Kernel Version
[email protected] #2
Build Number
4.5.91
I am absolutely new to this Android ROM installs on the phones. Though I decided to install this ROM I absolutely didn’t’ have any idea how to proceed. As a beginner I started doing the following in order.
Download and Keep the CM7 ROM
1. Downloaded Ba2F.zip to my laptop
2. Downloaded and Installed the Motorola USB drivers MotoHelper_2.0.53_Driver_5.2.0.EXE
3. Connect the Atrix and set the USB option on the phone to “USB Mass Storage”
4. Copy both BaTF.zip as well as the Extracted one to Phone internal storage as well as the Ext-SDcard on the phone
Download ROM Manager and Titanium Backup
1. Downloaded both from Android Market (ROM Manager Pro and Titanium Backup Free Version)
2. Both Apps won’t open because I had not ROOTED the phone
Root the Phone
1. I used “Pete's Motorola Root Tools.EXE” file to ROOT the phone
2. Followed step by step as mentioned here http://www.androidauthority.com/how-to-root-motorola-atrix-4g-35233/
Flash ClockworkMod Recovery
1. I used ROM Manager to do this as when you try to do anything in ROM manager it prompts to do this. The version of this is 5.0.2.0 ( I am not sure what is this for why we have to do this)
Unlocking the Bootloader
1. What I learned is, to unlock the bootloader, we have to first flash the phone with the SBF file
a. Installed RSDLite5.3.1.msi
b. Loaded the file 4547-fix-try2.sbf (Downloaded from http://forum.xda-developers.com/showthread.php?t=1136261)
c. Boot the phone with Power+volume UPPER key pressed till "Starting RSD protocol support" comes up
d. Connect to the Laptop and Hit Start button in RSD Lite Program
e. It Did Throw an error saying “FAIL” after showing the following message
i. Failed to boot: error 0x1000'( not word for word). There will also be a list of boot options like Fastboot, RSD, Recovery, etc. And it says Starting Fastboot Protocol
2. Then comes unlocking the phone
a. Though I had the previous error message, it still had the Fastboot Protocol loaded
b. I went to the FASTBOOT folder in command prompt of my laptop executed the following to unlock the phone which worked perfectly as I see the “Unlock” on the left hand corner when phone boots
c. fastboot oem unlock (it gave me the code) then I used the code to unlock
d. fastboot oem unlock #######
e. fastboot reboot
3. Installing the recovery IMG
a. I had downloaded the Recovery IMG file (recovery-atrix5.img) from http://forum.xda-developers.com/showthread.php?t=1204500
b. Booted the phone into Fastboot mode (turn off phone, hold power and volume down key until 'fastboot' appears then use volume up to select so it says 'starting fastboot protocol support').
c. From the CMD promnt and FASTBOOT directory I used fastboot erase recovery
d. Then I executed fastboot flash recovery recovery-atrix5.img (Note: I didn’t rename the file to recovery as suggested by some people)
e. Then gave fastboot reboot to restart.
4. Booting into Recovery mode (This is where I have the problem)
a. The phone is not booting into recovery it’s not going past the Android and yellow Triangle screen
b. I re-flashed the phone same SBF file (this time it was a success showed in the RSD Lite Program), re-installed the same IMG file after renaming to recovery.img
c. Also tried with a different IMG from the same link (recovery-blue-atrix5.img) but no luck
d. Also deleted the file install-recovery.sh from ./etc/ folder (bought the app root manager to delete the file) and then push the recovery.img, no luck
e. Some people said to TAP the bottom right corner while on that screen, did that but nothing is happening
f. Then I saw a note to press both the Volume Keys at the same time, this works but in this mode the cursor (I mean the selection) on the phone doesn’t go to the First TWO (i and iii) shown below, it allows me to select any of the last FOUR (v, vi, vii, viii).
i. Android System Recovery <3e>
ii. <EMPTY LINE >
iii. Android System Recovery utility
iv. <EMPTY LINE >
v. Reboot System now
vi. Apply update from sdcard
vii. Wipe data/factory reset
viii. Wipe cache partition
g. Using the above option I did factory reset but sill no results.
5. Current condition of the phone
a. It boots in unlock mode and I can do all the daily tasks. But I want to install the CM7 ROM that’s my requirement
PLEASE HELP HELP HELP
First of all, I applaud your effort in giving the a very comprehensive description of your issue.
Second, it seems you are having issues with installing a custom recovery because the recovery you're describing is still the stock recovery. I'll look around and see if I can find something that might help.
jhakash said:
4. Booting into Recovery mode (This is where I have the problem)
a. It boots in unlock mode and I can do all the daily tasks. But I want to install the CM7 ROM that’s my requirement
PLEASE HELP HELP HELP
Click to expand...
Click to collapse
---------- Post added at 11:31 AM ---------- Previous post was at 11:28 AM ----------
Have you tried re-installing the CWM from RomManager through RomManager? And then boot into recovery from within the app?
---------- Post added at 11:40 AM ---------- Previous post was at 11:31 AM ----------
EDIT: This might seem trivial, but is "USB Debugging" turned on?
You are the Man, I just flashed the same CWM 5.0.2.0 and i am in the recovery mode. This gave me an error when i did last time hence i didn't try again.
Thanks a bunch
Glad I can help, also, I think it's recommended to use the RomManager recovery for CM7 so good thing it worked.
jhakash said:
You are the Man, I just flashed the same CWM 5.0.2.0 and i am in the recovery mode. This gave me an error when i did last time hence i didn't try again.
Thanks a bunch
Click to expand...
Click to collapse
Oops.. started again, Can i use the recovery-atrix5.img and ROM manager flash it? if yes, then how?
I copy this file (after renaming to recovery.img) to both internal storage and SD card then what option should i choose in ROM Manager?
If you downloaded the CWM zip file for the romracer recovery and as long as RomManager's recovery is working then, yes, you can.
jhakash said:
Oops.. started again, Can i use the recovery-atrix5.img and ROM manager flash it? if yes, then how?
I copy this file (after renaming to recovery.img) to both internal storage and SD card then what option should i choose in ROM Manager?
Click to expand...
Click to collapse
jhakash said:
Oops.. started again, Can i use the recovery-atrix5.img and ROM manager flash it? if yes, then how?
I copy this file (after renaming to recovery.img) to both internal storage and SD card then what option should i choose in ROM Manager?
Click to expand...
Click to collapse
See post#2 from romracer's thread. Read the Miscellaneous part. Probably need to get rid of, or backup, install-recovery.sh.
He has mentioned he already did that. In his OP, under the steps he took look at "Booting into Recovery Mode" - 4.d, he says he removed it.
Maybe he's not doing it in the right order? Do you happen to know which should be done first as far as installing recovery and removing said file?
ghost_og said:
See post#2 from romracer's thread. Read the Miscellaneous part. Probably need to get rid of, or backup, install-recovery.sh.
Click to expand...
Click to collapse
live4nyy said:
He has mentioned he already did that. In his OP, under the steps he took look at "Booting into Recovery Mode" - 4.d, he says he removed it.
Maybe he's not doing it in the right order? Do you happen to know which should be done first as far as installing recovery and removing said file?
Click to expand...
Click to collapse
Woops, I should have read more carefully. It's best to remove the file first and then flash the recovery.img, or else the script will install the stock recovery on boot. That would make stock recovery the current one on the phone at the time of the script getting deleted.
I would double check and make sure /system/etc does not have install-recovery.sh. If it is not there, then proceed to the fastboot steps and reflash the recovery.img again. It should stick this time.
@Ghost, yes i deleted the file multiple times however i didn't find the /system/etc folder on the Internal Storage. however I found the install-recovery.sh file under /etc folder. The thing i observed that whether i flash it with a new CWM or not if i reboot the phone then it was created by itself.
@Live4nyy, Thanks for your suggestion, I could able to install CM7 now and it looks awesome good so far, but looks like i need to install Google Apps separately to access the APP market, am I right?
The only thing that happens to me is, it allowed me to go to Recovery only ONCE after i Flashed it thru ROM Manager, if i exit out of recovery without doing anything then next time tried to go to Recovery, it will struck at the same old Android screen and i had to flash it again. But Many thanks for suggesting to flash it thru ROM Manager.
Now with CM7, under ROM Manager (I guess this comes default with CM7) I see there is no version listed under "Flash Clockworkmod Recovery" and it says i must have to install it in-order to Flash and restore ROMs, do i need to do that? I can go to Recovery mode after reboot without any issues. Please Advise.
------
Jhakash
jhakash said:
@Ghost, yes i deleted the file multiple times however i didn't find the /system/etc folder on the Internal Storage. however I found the install-recovery.sh file under /etc folder. The thing i observed that whether i flash it with a new CWM or not if i reboot the phone then it was created by itself.
Click to expand...
Click to collapse
I just checked out my girlfriend's stock, locked, unrooted Atrix and she actually has install-recovery.sh in both /etc and /system/etc. Her file manager does not alphabetize anything in either folder, so I almost overlooked the second one.
If you're already on CM7, then you probably won't need to worry anymore. They have an entirely different set of start up scripts in that folder. Welcome to the community!
At this point I do not know enough to help you any further with this issue. All I knew about is the file that needs to be removed that @ghost_og has mentioned. But if you can flash it from RomManager and access CWM from there as well then I guess that's a good enough workaround for now.
Does anyone else have any idea why the stock recovery cannot be removed?
jhakash said:
@Live4nyy, Thanks for your suggestion, I could able to install CM7 now and it looks awesome good so far, but looks like i need to install Google Apps separately to access the APP market, am I right?
The only thing that happens to me is, it allowed me to go to Recovery only ONCE after i Flashed it thru ROM Manager, if i exit out of recovery without doing anything then next time tried to go to Recovery, it will struck at the same old Android screen and i had to flash it again. But Many thanks for suggesting to flash it thru ROM Manager.
Now with CM7, under ROM Manager (I guess this comes default with CM7) I see there is no version listed under "Flash Clockworkmod Recovery" and it says i must have to install it in-order to Flash and restore ROMs, do i need to do that? I can go to Recovery mode after reboot without any issues. Please Advise.
------
Jhakash
Click to expand...
Click to collapse
I am good to go now, everything seems to be functioning well after flashing CM7 ROM, no more recovery issues, and the Stock recovery is gone now.
Appreciate for all the info you guys provided, it helped a lot. Have a great day and Merry Christmas.
Regards
Jhakash
Hi.
While trying to upgrade my tablet to a later version of Android, something borked the bootloader. The tablet boots fine to a bare ICS (no gapps, but ROM MANAGER installed, though it does nothing but hang), but trying to boot into recovery mode hangs it (black screen with android robot, OEM info).
I can install apks to the tablet. I have installed ADB on my PC and it sees my tablet.
Where do I go from here ?
I have no clue
- what exact file(s) I need (my tablet is an Ainol novo8 advanced)
- where I need to put them
- what the commands are to do that
- it should be rooted (the superuser app aloows me to grant su privileges to apps)
Any help that can bring my tablet back to life would be very welcome.
Olivier
obarthelemy said:
Hi.
While trying to upgrade my tablet to a later version of Android, something borked the bootloader. The tablet boots fine to a bare ICS (no gapps, but ROM MANAGER installed, though it does nothing but hang), but trying to boot into recovery mode hangs it (black screen with android robot, OEM info).
I can install apks to the tablet. I have installed ADB on my PC and it sees my tablet.
Where do I go from here ?
I have no clue
- what exact file(s) I need (my tablet is an Ainol novo8 advanced)
- where I need to put them
- what the commands are to do that
- it should be rooted (the superuser app aloows me to grant su privileges to apps)
Any help that can bring my tablet back to life would be very welcome.
Olivier
Click to expand...
Click to collapse
If you can still use ADB your tablets bootloader is likely not messed up, it sounds like you booted the tablet into fastboot mode not recovery. To get into recovery you can enter it by holding a key combination the most common combination is holding volume up plus the power button at the same time. If that doesn't work from ADB you should be able to get into recovery by running the command:
Code:
adb reboot recovery
Also ROM manger doesn't always work right with every device so I would recommend just uninstalling ROM Manager for now. If it is booting fine into bare ICS then your tablet should be ok, if your looking for Google Apps for ICS they can be found here http://cmw.22aaf3.com/gapps/gapps-ics-20120317-signed.zip. Let me know if you still have questions .
Sent from my SCH-I535 using xda premium
Thanks a lot for your answer.
I'm sorry I didn't describe the issue well: I can no longer access the recovery mode.
I used to get to it by cold-booting the tablet holding Vol+ and Power. I used that to install ICS, gaps, powertools and 3D tools as described in http://forum.xda-developers.com/showthread.php?p=36059461#post36059461. The first package (recovery CWM) failed to installed because it was unsigned), the others installed, but in the end it seems I only got ICS: I have no gapps.
Now doing Vol+ and Power only gets me to the boot screen (a green android with OEM info, on a black background). Your "adb reboot recovery" does the same. I can only exit that screen by a hard reset.
During a normal boot, that screen flashes by for a couple of thesconds, then another, then the ICS colorful boot animation.
I have no clue how the recovery boot process works. I'm guessing it's reading a file of the internal Flash, and that file or dependencies got corrupted or partly overwritten by one of the packages I installed ? I'm not even sure if CWM recovery replaces the default recovery mode, or if it chains right after it ? I do have a supposedly-working CWM recovery .zip from the authors of the CM10 hack, as well as the "original" files listed here: http://forum.xda-developers.com/showpost.php?p=31089682&postcount=286 (official images from an out-of-the-box, unhacked tablet).
PS: the recovery mode I used to have was very rustic, only taking "update.zip" as an input, so when I did the update I had to go back and forth renaming the first package to "update.zip", applying it, renaming it "update1.zip, then on the the second package, etc, etc... It said Android System Recovery (3e), so maybe 3e was the version.
last but not least, if I could at least get the gapps onto the tablet, even w/o fixing the recovery mode, it would be very useful. I can install apks, or follow instructions to do it via adb ?
obarthelemy said:
Thanks a lot for your answer.
I'm sorry I didn't describe the issue well: I can no longer access the recovery mode.
I used to get to it by cold-booting the tablet holding Vol+ and Power. I used that to install ICS, gaps, powertools and 3D tools as described in http://forum.xda-developers.com/showthread.php?p=36059461#post36059461. The first package (recovery CWM) failed to installed because it was unsigned), the others installed, but in the end it seems I only got ICS: I have no gapps.
Now doing Vol+ and Power only gets me to the boot screen (a green android with OEM info, on a black background). Your "adb reboot recovery" does the same. I can only exit that screen by a hard reset.
During a normal boot, that screen flashes by for a couple of thesconds, then another, then the ICS colorful boot animation.
I have no clue how the recovery boot process works. I'm guessing it's reading a file of the internal Flash, and that file or dependencies got corrupted or partly overwritten by one of the packages I installed ? I'm not even sure if CWM recovery replaces the default recovery mode, or if it chains right after it ? I do have a supposedly-working CWM recovery .zip from the authors of the CM10 hack, as well as the "original" files listed here: http://forum.xda-developers.com/showpost.php?p=31089682&postcount=286 (official images from an out-of-the-box, unhacked tablet).
Click to expand...
Click to collapse
obarthelemy said:
PS: the recovery mode I used to have was very rustic, only taking "update.zip" as an input, so when I did the update I had to go back and forth renaming the first package to "update.zip", applying it, renaming it "update1.zip, then on the the second package, etc, etc... It said Android System Recovery (3e), so maybe 3e was the version.
Click to expand...
Click to collapse
obarthelemy said:
last but not least, if I could at least get the gapps onto the tablet, even w/o fixing the recovery mode, it would be very useful. I can install apks, or follow instructions to do it via adb ?
Click to expand...
Click to collapse
The recovery you are referring to is to the standard Android 3e recovery it is included in every version of Android, and will always be like that unless you install a custom recovery such as CWMR and or TWRP. As a general rule you should never install a custom ROM without having a custom recovery image installed first, essentially all the stock 3e recovery is good for is installing OTA updates and preforming a basic factory reset of your phone. You should try and fix your recovery before going any-further, you can sign the un-signed zip by using this tool. Overall, I would focus on trying to fix the recovery to prevent any further damage to your tablet and so that way you have a simple way to recover from anything that might go wrong when flashing ROMs, mods, and other zip files.
issue with the uImage linked
The uImage linked on the download pages for the CM10 and CM9 version ends in ".*"
I have no clue what the normal extension should be; replacing that *.zip doesn't work. Is the file bad, or am I just too clueless about what to do with it ?
Ok so the question is:
1- which "recovery mode" file should I install on my tablet, especially since the mod author's ones seem flaky
2- how do I do that via ADB since my tablet no longer seems to have a working "recovery mode".
I'm sorry to hassle you with those questions... I've looked around, I can't find info nor files I'm confident about ?
Hey guys,
I have a bit of a head scratcher. I am currently trying to flash my new Sanei n10 tablet with CM10 and it is proving much more difficult than I first imagined.
My main problem seems to be that the device just does not want to boot in CWM. I have installed the latest version of CWM (found here) via the Terminal Emulator but it doesn't boot into CWM Recovery, but rather just boots normally. I have also tried using the hard keys to boot into it but all that does is boot me into the default android system recovery (3e) which is useless as it will only update from verified roms.
The device is rooted and I have ROM Manager installed. I have given Terminal Emulator superuser permissions... It just doesn't seem to want to boot into CWM Recovery. I have tried using both ROM Manager as well as NOVO7 Tools to boot into it but I get the same results (device just reboots normally)
I think that it might be something to do with the stock ICS 4.0.4 that came with the device.that is causing me so much hastle, but I was hoping someone out there might have experienced a similar issue or can offer some insight to where I am going wrong.
Thanks in advance!
M
msm1003 said:
Hey guys,
I have a bit of a head scratcher. I am currently trying to flash my new Sanei n10 tablet with CM10 and it is proving much more difficult than I first imagined.
My main problem seems to be that the device just does not want to boot in CWM. I have installed the latest version of CWM (found here) via the Terminal Emulator but it doesn't boot into CWM Recovery, but rather just boots normally. I have also tried using the hard keys to boot into it but all that does is boot me into the default android system recovery (3e) which is useless as it will only update from verified roms.
The device is rooted and I have ROM Manager installed. I have given Terminal Emulator superuser permissions... It just doesn't seem to want to boot into CWM Recovery. I have tried using both ROM Manager as well as NOVO7 Tools to boot into it but I get the same results (device just reboots normally)
I think that it might be something to do with the stock ICS 4.0.4 that came with the device.that is causing me so much hastle, but I was hoping someone out there might have experienced a similar issue or can offer some insight to where I am going wrong.
Thanks in advance!
M
Click to expand...
Click to collapse
here
1. Download the latest ClockWorkMod for Allwinner A10 tablets from here:
http://forum.xda-developers.com/show....php?t=1802268
2. Put all three files in the ZIP inside the root of a MicroSD card and insert it in the tablet
3. Check from the Terminal app inside the tablet to see if the MicroSD card is mounted in /sdcard (just type "ls /sdcard").
4. If the "ls" command doesn't show anything (that's what happened in my case), then you must modify the "install-recovery.sh" file and replace all instances of "/sdcard" with "/mnt/extsd".
5. With the proper "install-recovery.sh" file, run the commands specified in the above xda link (in my case the card is in "/mnt/extsd" instead of "/mnt/sdcard" as the original example shows):
su
cd /mnt/extsd
sh install-recovery.sh
sh reboot-recovery.sh
6. The tablet will then reboot to CWM recovery. Then follow the regular steps to install Cyanogenmod (wipe plus install ROM + GApps + Compatibility). This time the Recovery menu won't care about the files being unsigned and will install them right away!
I rooted my Nook using the method here. I then downloaded Goo Manager though the app store and installed TWRP recovery. If I choose "reboot recovery" in Goo Manager, it will grant SU access and reboot, however it will not boot in to TWRP. it will just reboot the Nook normally. Then I powered down normally and now my Nook won't boot at all! It just shows the splash screen and shuts off or bootloops if i plug it in. What's up?
Edit: I tried doing the root method over again to unbrick it. I could boot in to recovery but the tablet still won't boot after I flash.
Unfortunately I can't help you. Just give my view that whenever I have tried TWRP there has been issues. EIther "not just doing the job" which is annoying but not much more. But also getting stuck in bootloop. When that happened to me I stumbled on the repart.im recover image that put my Tablet back to "out of the box" condition. I ran it and after that I have used CWM without issues.
Hopefully someone will come along with a better answer to you.
asawi said:
Unfortunately I can't help you. Just give my view that whenever I have tried TWRP there has been issues. EIther "not just doing the job" which is annoying but not much more. But also getting stuck in bootloop. When that happened to me I stumbled on the repart.im recover image that put my Tablet back to "out of the box" condition. I ran it and after that I have used CWM without issues.
Hopefully someone will come along with a better answer to you.
Click to expand...
Click to collapse
How did you flash CWM? I can't find any flashable files anywhere. Did you do it through Rom Manager or something like that or did you download a file and flash it through a bootable SD recovery?
Back when I origianlly did it I did it like I outline in this post (under C): http://forum.xda-developers.com/showthread.php?t=2081981
Nowadays I do it differently though, but that process should still work.
GooManager does not flash the right recovery image for some root methods. The Nook Tablet one has acclaim in the name, and when I rooted mine, I realized it tried to flash a build for blaze. I just booted from a CWM SD to install my ROMs, and then flashed TWRP to internal using fastboot.
alevineman said:
GooManager does not flash the right recovery image for some root methods. The Nook Tablet one has acclaim in the name, and when I rooted mine, I realized it tried to flash a build for blaze. I just booted from a CWM SD to install my ROMs, and then flashed TWRP to internal using fastboot.
Click to expand...
Click to collapse
Where did you get the TWRP to flash and what is fastboot?
Snakebear said:
Where did you get the TWRP to flash and what is fastboot?
Click to expand...
Click to collapse
Fastboot is a tool in the Android SDK that can do a lot, including flashing a recovery.
Steps to use
Make a Ubuntu 13.04 virtual machine
Open Terminal
Put in : "sudo apt-get install android-tools-fastboot"
Install CyanoBoot if not already
When booting Press n in cyanoboot
Choose start fastboot using buttons
Plug into computer and hook up to VM
Download TWRP internal 2.4.3.0 from iamafanof.wordpress.com
Open terminal
Type cd Downloads
Type ls
Look for a file that starts with twrp
Type fastboot flash recovery then type the file name of the twrp file
Done
Snakebear said:
How did you flash CWM? I can't find any flashable files anywhere. Did you do it through Rom Manager or something like that or did you download a file and flash it through a bootable SD recovery?
Click to expand...
Click to collapse
See http://forum.xda-developers.com/showpost.php?p=40998406&postcount=3.
my nook tablet stopped in read forever.
my nook tablet stopped in read forever.
volume buttons not working
needs twrp recovery
any help?
My brother has a Nabi 2 which was rooted, and we recently received an update from Jelly Bean to Kit Kat. We (more like I) tried to do this without unrooting, and it ended up boot looping for around 4 hours before I intervened. I downloaded the latest stock ROM I could find, and I went into TWRP to flash it. Every single time, it says "Unable to flash zip '/external_sdcard/246stock.zip', then tells me that there is no operating system installed. I tried upgrading TWRP, and got 2.8. Touch was very close to unresponsive. I also tried 2.7.1.0, and 2.7.0.0, and also every other version I could find. Every single version either couldn't flash it, couldn't mount anything, or touch was unresponsive. I downloaded all the recoveries from xda's Nabi 2 page. None of them work. Is there anything I can try to fix this?
wither719 said:
My brother has a Nabi 2 which was rooted, and we recently received an update from Jelly Bean to Kit Kat. We (more like I) tried to do this without unrooting, and it ended up boot looping for around 4 hours before I intervened. I downloaded the latest stock ROM I could find, and I went into TWRP to flash it. Every single time, it says "Unable to flash zip '/external_sdcard/246stock.zip', then tells me that there is no operating system installed. I tried upgrading TWRP, and got 2.8. Touch was very close to unresponsive. I also tried 2.7.1.0, and 2.7.0.0, and also every other version I could find. Every single version either couldn't flash it, couldn't mount anything, or touch was unresponsive. I downloaded all the recoveries from xda's Nabi 2 page. None of them work. Is there anything I can try to fix this?
Click to expand...
Click to collapse
You don't "install" that zip, you "restore" it.
Use TWRP 2.7.0
Download this 3.0.13 stock ZIP
Use an external SDcard and make a backup of just "boot"(this is a setup for next step)
Put SD card in computer. Navigate to the folder TWRP/BACKUPS/XXXX. XXX is a serial number unique to your Nabi.
- Make a new folder and call in whatever you want. So it should now look like TWRP/BACKUPS/XXX/yourfolder
- Unzip the 3.0.13 stock you downloaded in to the "yourfolder" you created above. The files should look like ext4.system.win, emmc.boot.win, ext.addon.win, etc. This should set you up for the 3.0.13 ROM.
- Download this 3.0.13 bootloader
- Copy the zip to the SDcard. This will be for the bootloader update.
- Put sdcard in Nabi
- Go to "restore tab", and find the backup under the "yourfolder" you made and unzipped the files to.
- You should be able to select boot, system, and addon and skip the others.
- If everything restores then go to TWRP "install tab", find the bootloader zip you downloaded and install it.
- Reboot
aicjofs said:
You don't "install" that zip, you "restore" it.
Use TWRP 2.7.0
Download this 3.0.13 stock ZIP
Use an external SDcard and make a backup of just "boot"(this is a setup for next step)
Put SD card in computer. Navigate to the folder TWRP/BACKUPS/XXXX. XXX is a serial number unique to your Nabi.
- Make a new folder and call in whatever you want. So it should now look like TWRP/BACKUPS/XXX/yourfolder
- Unzip the 3.0.13 stock you downloaded in to the "yourfolder" you created above. The files should look like ext4.system.win, emmc.boot.win, ext.addon.win, etc. This should set you up for the 3.0.13 ROM.
- Download this 3.0.13 bootloader
- Copy the zip to the SDcard. This will be for the bootloader update.
- Put sdcard in Nabi
- Go to "restore tab", and find the backup under the "yourfolder" you made and unzipped the files to.
- You should be able to select boot, system, and addon and skip the others.
- If everything restores then go to TWRP "install tab", find the bootloader zip you downloaded and install it.
- Reboot
Click to expand...
Click to collapse
ok, im in BIG trouble with my daughter... Yep, I managed to brick her Nabi 2 following this tutorial and I dont know really know where I went wrong. But now when the Nabi 2 is powered on, all I see is the nabi logo, but no OS...or TWRP!... eeek!
I had been trying for days to get a stable TWRP on and Gapps, I did get TWRP v2.3.3.0 up and running at one point, but no Gapps installed and no SuperSU to be found, it was as if it wasnt rooted at all. (even after reinstalling both within TWRP). Then of course i found a thread that said Gapps didnt work on nabi 2 version 2.1...!
I do have a TWRP backup folder saved but i dont seem to have any way to get it back onto the Nabi 2... as its no longer detected in windows like it was before..? (despite the ding sound windows makes when plugged in ?).
I can only get to the 1st bootmenu (holding Vol+ and Power ok. Selecting any options results in little (or nothing) happening... i.e. when selected;
Boot Normally - nothing happens, nabi logo only. And if i leave it too long, it freezes here and i have to reboot.
Fastboot Protocol - with usb connected to pc, i do get to the Bootloader menu with, Bootloader, Continue, Reboot-bootloader, Reboot and Poweroff , options. The Pc 'dings' to indicate detection, but is not detected by adb ?
Recovery Kernel - nothing happens, nabi logo only.
Forced Recovery - screen goes black, then nothing follows.
on Fastboot Protocol menu, if i select the options;
Bootloader - without touching anything, pc dings to indicate some connection...?
Continue - if selected, i hear windows drop whatever connection it had previous..?
Reboot-bootloader - nothing happens, nabi logo only.
Reboot - reboots, then nabi logo only.
Poweroff - nabi 2 shuts down.
As it stands , all i can access are these options above, but i dont seem to have a way of getting windows to communicate over the usb cable...? that said, with pdanet running, it does detect the nabi 2, but of course it cant talk to it as I cant get to pdanet on the nabi 2... just gives some weird error that im using wrong adb , or it just cant connect to the nabi.
Tried using Nabilab v2, but device is not detected...?
...so i would be most grateful if some nabi 2 guru could assist with any possible resurrection, otherwise I will remain "the worst daddy ever"...ugh!
cheers in advance
the_xlr8r said:
ok, im in BIG trouble with my daughter... Yep, I managed to brick her Nabi 2 following this tutorial and I dont know really know where I went wrong. But now when the Nabi 2 is powered on, all I see is the nabi logo, but no OS...or TWRP!... eeek!
I had been trying for days to get a stable TWRP on and Gapps, I did get TWRP v2.3.3.0 up and running at one point, but no Gapps installed and no SuperSU to be found, it was as if it wasnt rooted at all. (even after reinstalling both within TWRP). Then of course i found a thread that said Gapps didnt work on nabi 2 version 2.1...!
I do have a TWRP backup folder saved but i dont seem to have any way to get it back onto the Nabi 2... as its no longer detected in windows like it was before..? (despite the ding sound windows makes when plugged in ?).
I can only get to the 1st bootmenu (holding Vol+ and Power ok. Selecting any options results in little (or nothing) happening... i.e. when selected;
Boot Normally - nothing happens, nabi logo only. And if i leave it too long, it freezes here and i have to reboot.
Fastboot Protocol - with usb connected to pc, i do get to the Bootloader menu with, Bootloader, Continue, Reboot-bootloader, Reboot and Poweroff , options. The Pc 'dings' to indicate detection, but is not detected by adb ?
Recovery Kernel - nothing happens, nabi logo only.
Forced Recovery - screen goes black, then nothing follows.
on Fastboot Protocol menu, if i select the options;
Bootloader - without touching anything, pc dings to indicate some connection...?
Continue - if selected, i hear windows drop whatever connection it had previous..?
Reboot-bootloader - nothing happens, nabi logo only.
Reboot - reboots, then nabi logo only.
Poweroff - nabi 2 shuts down.
As it stands , all i can access are these options above, but i dont seem to have a way of getting windows to communicate over the usb cable...? that said, with pdanet running, it does detect the nabi 2, but of course it cant talk to it as I cant get to pdanet on the nabi 2... just gives some weird error that im using wrong adb , or it just cant connect to the nabi.
Tried using Nabilab v2, but device is not detected...?
...so i would be most grateful if some nabi 2 guru could assist with any possible resurrection, otherwise I will remain "the worst daddy ever"...ugh!
cheers in advance
Click to expand...
Click to collapse
Wow I havent been on here in ages, got an email about your quote though.
I have forgotten so much about these Nabis over the last decade?! So how did you get to the non-booting part? You were able to complete the steps above all successfully? or did it fail at some part?
If you successfully flashed 3.0.13 bootloader with install in TWRP then I don't think you will be able to boot the TWRP you had on the device. That would be my guess at this point why you can't get to recovery.
[NABI] General Information
Fuhu Nabi General information 1. Introduction It was only recently that the Nabi2 got it's own forum. This device has been out a couple of years so the information you may be looking for is spread all over XDA. The largest single chunk of...
forum.xda-developers.com
Read the above. You are pretty much stuck in having to use fastboot.(The driver must be installed if you keep hearing the ding). You will need a fastboot.exe if you don't have one. Search minimal ADB and fastboot. I'd download TWRP 2.8.7 and try to use section 7 to get it on device i.e "fastboot flash recovery recovery.img"
If you unsuccessfully flashed bootloader then you need to use TWRP 2.8.5 Files should be in that thread also or my AHF https://androidfilehost.com/?w=files&flid=41987.
Ill check back later
aicjofs said:
Wow I havent been on here in ages, got an email about your quote though.
I have forgotten so much about these Nabis over the last decade?! So how did you get to the non-booting part? You were able to complete the steps above all successfully? or did it fail at some part?
If you successfully flashed 3.0.13 bootloader with install in TWRP then I don't think you will be able to boot the TWRP you had on the device. That would be my guess at this point why you can't get to recovery.
[NABI] General Information
Fuhu Nabi General information 1. Introduction It was only recently that the Nabi2 got it's own forum. This device has been out a couple of years so the information you may be looking for is spread all over XDA. The largest single chunk of...
forum.xda-developers.com
Read the above. You are pretty much stuck in having to use fastboot.(The driver must be installed if you keep hearing the ding). You will need a fastboot.exe if you don't have one. Search minimal ADB and fastboot. I'd download TWRP 2.8.7 and try to use section 7 to get it on device i.e "fastboot flash recovery recovery.img"
If you unsuccessfully flashed bootloader then you need to use TWRP 2.8.5 Files should be in that thread also or my AHF https://androidfilehost.com/?w=files&flid=41987.
Ill check back later
Click to expand...
Click to collapse
Hi, thanks for getting back ...
Q. So how did you get to the non-booting part? You were able to complete the steps above all successfully? or did it fail at some part?
A. yes i followed the tut but once i rebooted that was the end and where my big problems began.
Q. If you successfully flashed 3.0.13 bootloader with install in TWRP then I don't think you will be able to boot the TWRP you had on the device. That would be my guess at this point why you can't get to recovery.
A. Yes, using TWRP i installed 3.013 bootloader.
Q. You are pretty much stuck in having to use fastboot. (The driver must be installed if you keep hearing the ding). You will need a fastboot.exe if you don't have one. Search minimal ADB and fastboot.
A. This may be the issue, i may be using older version of adb and fastboot. I already had minimal adb stored away, so i experimented by copying the adb files over to my NabiLabFull folder, this time it was green (detected) ... sort of...
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
ill have a read at the links you provided and will report back soon, thanks.
ok... getting somwehere but not where i expected....
i tried to install the 2 x TWRP versions you mentioned but it wouldnt load into either. So i reverted back to trying 2.3.3.0 and bingo , im in... but shouldnt 2.8.5 or 2.8.7 have worked since Im now showing Navi version as 3.0.13.. (was previously on 2.1.9) ?
im sitting at the TWRP 2.3.3.0 menu now , and still have Nabilab running but am afraid to do anything next lol.... where should i proceed to, from here ? Should I be installing any particular version of Root and Gapps now that im into TWRP 2.3.3.0 (or even try to update TWRP beforehand ?
PS. I am using a UK nabi 2 , in case that makes any difference to files im downloading to it ?
cheers
Im not at a location where I can look at the Nabilab script but as I recall the script is pulling it from build.prop on the system partition. This would indicate to me that the system partition flashed, and so likely the addon and boot. Also the fact that you can't boot another TWRP besides 2.3.3, and the normal boot hanging at the logo leads me to believe that the bootloader was not updated.
Again I'm trying to remember here....but as I recall the bootloader for the Nabi is passing a commandline to the kernel. You have a kernel in the 3.0.x ROM and an identical kernel in TWRP 2.8.7. The fact that neither boot would mean to me the bootloader is original and passing the old commandline to a newer kernel.
You have to get things in sync. The bootloader and the boot.img(kernel+ramdisk) have to match each other. The way that makes the most sense is to install the bootloader3013 zip through TWRP. You already tried that obviously and that's how you got here.
1) You could try the bootloader install inside TWRP again, seems like you can recover if it fails now. Of course if it works then 2.3.3 TWRP should no longer work(which is what I thought happened and why you couldn't boot TWRP initially) so you'd have to try the 2.8.7 at that point.
2) Since the bootloader is original(or Jellybean-ish) you could restore your backup and regroup.
When I get to a place I can look at the install script for the bootloader maybe I can jog my memory. I thought it just dd to mmcblock0
ok. thanks.
so i make no more mistakes, ill check I have all the correct files i need with you first...
I have saved to external sdcard, KK3013bootloader.zip containing;
META-INF
android-info.txt
blob
I have also saved to external sdcard, 3013stock.zip (unzipped)
I have also saved to external sdcard, some old Gapps.zip version (no idea if recent or not) ?
I have also saved to external sdcard, some old root.zip version, again, not sure if correct ?
I think I'm breaking it when i get to here...
1) You could try the bootloader install inside TWRP again, seems like you can recover if it fails now. Of course if it works then 2.3.3 TWRP should no longer work(which is what I thought happened and why you couldn't boot TWRP initially) so you'd have to try the 2.8.7 at that point.
....So, if im in TWRP 2330 now, and I install KK3013Bootloader.zip, it will then no longer boot to TRWP ... is that correct? If so, how then do i get TWRP 285 or 287 working ?
....think i'm getting a smidge lost at this bit lol
[update] - cannot install anything in TRWP 2330 as its not recognizing my 64gb sdcard (formatted to fat32) ... does it have to be a certain formatted type FAT/FAT32/EXT12/3/4 or other ?
Also, i couldnt find a working download link for anyone's scripts... many thanks
the_xlr8r said:
I think I'm breaking it when i get to here...
1) You could try the bootloader install inside TWRP again, seems like you can recover if it fails now. Of course if it works then 2.3.3 TWRP should no longer work(which is what I thought happened and why you couldn't boot TWRP initially) so you'd have to try the 2.8.7 at that point.
So, if im in TWRP 2330 now, and I install KK3013Bootloader.zip, it will then no longer boot to TRWP ? is that correct. If so, how then do i get TWRP 285 or 287 working ?
[update] - cannot install anything in TRWP 2330 as its not recognizing my 64gb sdcard (formatted to fat32) ... does it have to be a certain formatted type FAT/FAT32/EXT12/3/4 or other ?
Click to expand...
Click to collapse
For #1 You install the bootloader zip. Swipe install then reboot. It won't do anything at first because it installs the "blob" (which is the bootloader) to the staging partition. Reboots for 15 seconds and installs the blob. The only way at that point to get a newer TWRP is by booting bootloader to fastboot, and then fastboot flash the newer TWRP on to it.
No it should recognize fat32. There was something about storage being realigned between versions too. You could always use adb too I guess.
adb push bootloaderXXXX.zip /data/media ?
The end of this thread may be usefully too
[RECOVERY][NABI2] TWRP 2.3.3.0, 2.8.5.0 testing
This is an update to the TWRP recovery for the Nabi 2. At this point this recovery is still considered in testing. The normal disclaimers apply. Have a good backup moved to your computer from the previous recovery. Before starting this...
forum.xda-developers.com
The original TWRP posts
Nabi 2 Root and Gapps Install
#include /* * Your warranty is now void. * * I am not responsible for bricked devices, dead SD cards, * thermonuclear war, or you getting fired because the alarm app failed. Please * do some research if you have any concerns about features...
forum.xda-developers.com
Nabi 2 Root and Gapps Install
#include /* * Your warranty is now void. * * I am not responsible for bricked devices, dead SD cards, * thermonuclear war, or you getting fired because the alarm app failed. Please * do some research if you have any concerns about features...
forum.xda-developers.com
thanks, am i downloading the correct TWRP zip ?
TWRP 2.8.5.0 Released
TWRP 2.8.5.0 is out now for all currently supported devices.
twrp.me
Which version Gapps should i be using ?
The Open GApps Project
OpenGApps.org offers information and pre-built packages of The Open GApps Project. The Open GApps Project is an open-source effort to script the automatic generation of up-to-date Google Apps packages. All Android versions and platforms supported.
opengapps.org
the_xlr8r said:
thanks, am i downloading the correct TWRP zip ?
TWRP 2.8.5.0 Released
TWRP 2.8.5.0 is out now for all currently supported devices.
twrp.me
Which version Gapps should i be using ?
The Open GApps Project
OpenGApps.org offers information and pre-built packages of The Open GApps Project. The Open GApps Project is an open-source effort to script the automatic generation of up-to-date Google Apps packages. All Android versions and platforms supported.
opengapps.org
Click to expand...
Click to collapse
No download the TWRP in one of the last 2 links I sent. First is 2.8.5, and other is 2.8.7
I thought on KitKat Fuhu actually has Gapps? You will let Playstore update it to whatever version they stopped with for KitKat support.
There is always NabiLabGUI2015 https://drive.google.com/file/d/1x_4btZE2VzYWJ_aag9U20ubIGY9NXjcN/view?usp=sharing
I never really finished the project but it might be easier as it has all the recoveries already in it. Stay away from NVflash/APX stuff for now.
ok , sorry i already went ahead and installed bootloader3103
then ADB'd on twrp-recovery-KKNV7AUS-287.zip
I can now get TWRP 2.9.7.0 loaded up, but still no OS booting once i have rebooted the nabi2...
maybe the OS is missing ..? how do i reinstall it ? (i tried doing a restore by using the old TWRP backup i had from the start , by pasting in the 3013stock files) but that didnt work.
....still stuck, but getting closer
the_xlr8r said:
maybe the OS is missing ..? how do i reinstall it ? (i tried doing a restore by using the old TWRP backup i had from the start , by pasting in the 3013stock files) but that didnt work.
....still stuck, but getting closer
Click to expand...
Click to collapse
No I think we are good, the plan was for you to flash bootloader to proper, and that seems to be the case.
It might not be missing the OS, it might need data/media wiped(factory reset). Of course the tablet is completely wiped during that, don't know if the daughter had stuff on there.
Either way it doesn't hurt to try and restore it again. When you say pasting the 3013 restore files, you mean in the folder with your backup? Over top the files or just a folder in the same folder as the backup?
The fact that Nabilab says 3.0.13 makes me think the system files were restored and not missing. You did all this through NabiLab or TWRP?
hi , tried every way i could
yes, i copied and pasted the 3013stock files over the top of the old backup and tried to restore, still didnt boot to OS.
tried your NabiLab2015 , UK menu didnt open so i just used the US menu.
tried to follow step.2 "Flash Full" , seemed to start ok , but then..... this happened...
Note: using NabiLab2015, I skipped using step 1. to download stock 3013, as it wouldnt do it, so i copied the 3013.zip i had downloaded earlier into this folder. which seemed to allow step 2 to work...
whats best option to use now that it failed at 30% install ? thanks
the_xlr8r said:
hi , tried every way i could
yes, i copied and pasted the 3013stock files over the top of the old backup and tried to restore, still didnt boot to OS.
tried your NabiLab2015 , UK menu didnt open so i just used the US menu.
tried to follow step.2 "Flash Full" , seemed to start ok , but then..... this happened...
Note: using NabiLab2015, I skipped using step 1. to download stock 3013, as it wouldnt do it, so i copied the 3013.zip i had downloaded earlier into this folder. which seemed to allow step 2 to work...
whats best option to use now that it failed at 30% install ? thanks
View attachment 5718161
Click to expand...
Click to collapse
Looks like the ADB connection reset. This step is copying the files to the tablet to data/media. It failed at addon. Either cable to computer had a glitch or maybe data/media(internal storage) is full. You can retry again, it didn't flash anything to device at all.
Maybe in TWRP, go to advanced, terminal and type bdf? See if filesystem looks ok. Seems like a cable issue right now though
[UPDATE]
thankyou sir for all your help.
after another try on a Flash Full , everything was installed and it rebooted and updated.
i'm so glad your email still worked after 10 years of not looking at this nabi stuff , otherwise this nabi of mine would be in the bin before now.. lol.... @)
..couple of things, now that its on android 4.4 etc , is it safe to perform any further updates ?
Its running as a US version now, will that affect anything with me being in the UK ?
still not able to get external sdcard detected in TWRP... any ideas ?
many thanks
the_xlr8r said:
[UPDATE]
thankyou sir for all your help.
after another try on a Flash Full , everything was installed and it rebooted and updated.
i'm so glad your email still worked after 10 years of not looking at this nabi stuff , otherwise this nabi of mine would be in the bin before now.. lol.... @)
one last thing, now that its on android 4.4 etc , is it safe to perform any further updates ?
Click to expand...
Click to collapse
No problem, havent thought about Nabi's in probably 2 years. Some of my favorite memories were helping people on Christmas Day, or this Dad from Brazil on his son's birthday, Mom from Italy etc, etc and imagining the kids didn't even know all the panic haha.
You are pretty much done at 4.4. Really no OS level updates to do. Fuhu never did anything else, the source code they gave us was worthless for kernel building, and honestly this Tegra chipset was at it end anyway. Like I said earlier Google play services will update to the latest for the kitkat version, and that will be it. Apps that still support Android this old will have updates of course.
EDIT: Its funny about NabiLabGUI2015. I get emails about my google drive link because link is so old and I have to manually share it the zip for it. I forgot that it would have been really useful if I ever finished it.
most of the trouble I was facing was working links on the forum, hardly any worked and I spent days searching.
even searching for NabiLab2015 proved impossible. Only for you providing a new link, i would never have found it... maybe you could update some old posts with fresh links, and that will make some old-timers like myself, feel young again trying this stuff lol.
but andyways, thank you again so much for your help. theres not many out there in this day and age, that would have bothered... so i salute you sir!
kind regards
stay safe
ps. my daughter says Im the best dad in the world again ... I told her the wizard on the tinterweb fixed it using some of Gandalf's magic....