Related
I flashed pudding on my 1.83 ATT atrix. This worked fine, and I am trying to get CWM for unlocked bootloaders now. I am following the instructions directly from the thread: http://forum.xda-developers.com/showthread.php?t=1138541
Problem is, after extracting the zip to C: and running "fastboot flash recovery C:\(image name).img", I get "fastboot is not recognized as an internal or external command..."
This leads me to believe that I don't have adb set up properly. I have standard adb set up for pushing apk's, but am I missing something specific for fastboot?
All i have under android-sdk-windows>platform-tools is adb.exe adbwinapi.dll and adbwinusbapi.dll. I DO have USB debugging on lol.
I seem to remember having more stuff under platform tools at an earlier date. All the threads for setting up adb are LONG buried, and after exhaustive searching, I finally gave up and decided to post (at least not in dev ). Even turning to google for adb help, I only get a bunch of the ad-farming tip websites that are outdated.
Please help me out guys. I can usually help myself after enough research, but I admit defeat on this one :/
Thanks much,
-omni
omni_angel7 said:
I flashed pudding on my 1.83 ATT atrix. This worked fine, and I am trying to get CWM for unlocked bootloaders now. I am following the instructions directly from the thread: http://forum.xda-developers.com/showthread.php?t=1138541
Problem is, after extracting the zip to C: and running "fastboot flash recovery C:\(image name).img", I get "fastboot is not recognized as an internal or external command..."
This leads me to believe that I don't have adb set up properly. I have standard adb set up for pushing apk's, but am I missing something specific for fastboot?
All i have under android-sdk-windows>platform-tools is adb.exe adbwinapi.dll and adbwinusbapi.dll. I DO have USB debugging on lol.
I seem to remember having more stuff under platform tools at an earlier date. All the threads for setting up adb are LONG buried, and after exhaustive searching, I finally gave up and decided to post (at least not in dev ). Even turning to google for adb help, I only get a bunch of the ad-farming tip websites that are outdated.
Please help me out guys. I can usually help myself after enough research, but I admit defeat on this one :/
Thanks much,
-omni
Click to expand...
Click to collapse
If your on linux it's "./moto-fastboot" not just fastboot.
Windows 7 64 bit. sorry, should have specified.
Nobody with win 7 knowledge/advice?
Alrighty, let us see here...
Try this.
1: Create a folder named fastboot (or whatever you prefer, just something simple like that) on the root of your C drive.
2: Download this file, http://www.mediafire.com/?yl17mz8l7w9h687
3: Unzip contents of said file into the folder you created in step 1
4: Click on Start, type cmd into the bar at the bottom and hit enter
5: Type cd C:\fastboot (or whatever you named the folder in step one)
6: Type moto-fastboot flash recovery recovery-en-goapk-0630-1029.img
That should work. The recovery included in the flash is current AS OF THIS POST. Obviously, the instructions will change if you download a newer copy of CWM as they are released, since the filename of the recovery file will change.
If you are wondering why it is moto-fastboot, the fastboot I included is the modified one that allows for larger img flashing. Not particularly useful anymore, with CWM working well now and all... but hey.
Diviance said:
Alrighty, let us see here...
Try this.
1: Create a folder named fastboot (or whatever you prefer, just something simple like that) on the root of your C drive.
2: Download this file, http://www.mediafire.com/?yl17mz8l7w9h687
3: Unzip contents of said file into the folder you created in step 1
4: Click on Start, type cmd into the bar at the bottom and hit enter
5: Type cd C:\fastboot (or whatever you named the folder in step one)
6: Type moto-fastboot flash recovery recovery-en-goapk-0630-1029.img
That should work. The recovery included in the flash is current AS OF THIS POST. Obviously, the instructions will change if you download a newer copy of CWM as they are released, since the filename of the recovery file will change.
If you are wondering why it is moto-fastboot, the fastboot I included is the modified one that allows for larger img flashing. Not particularly useful anymore, with CWM working well now and all... but hey.
Click to expand...
Click to collapse
Thanks SO much for the quick response and all the effort I'd actually updating OTA from 1.26 because I flashed back, thinking no one was gonna help! Well, when I feel up to it another night. I'll give this another shot. Thanks for the custom fastboot, too!
i get < waiting for device >
did i do something wrong?
Me too. ^^^^^^^
I figured it out, i forgot to put it into fastboot mode!
did not work for me
when I do what you told the other guy it says system cant find the path specified couls you please help I have spent a couple of days trying different things and also when I try to erase the recovery installer file it want let me
So what I am trying to do is get my feet wet with doing some dev work and basically I'm trying to figure out how to (without flashing anything, i want to remove the stuff myself):
De-bloat the stock sense rom and/or just remove all of the HTC garbage and use a different launcher all together without if affecting the system (Im not too sure what is acceptable to remove and what needs to stay in the /system/app/ dir)
Remove the annoying WiFi in the status bar
any and all help is much appreciated and even just pointing me in the right direction
Well you are going to have to flash something.
Sent from my HTC6435LVW using xda app-developers app
Bigandrewgold said:
Well you are going to have to flash something.
Sent from my HTC6435LVW using xda app-developers app
Click to expand...
Click to collapse
I guess what I was trying to say was I wanted to be able to do the work myself rather than flashing a zip someone else made to get rid of like lets say the wifi in status bar
.torrented said:
I guess what I was trying to say was I wanted to be able to do the work myself rather than flashing a zip someone else made to get rid of like lets say the wifi in status bar
Click to expand...
Click to collapse
Here's state of the art for today:
1. Hack DNA to make it look like non-Verizon to the htcdev.com site. Here's a new painless method: http://forum.xda-developers.com/showthread.php?t=2109862
2. Go to htcdev.com and follow link to unlock bootloader. Note that this will WIPE YOUR "SD CARD". It's the only thing that does that. No problem with ROMs, etc. Not even a "factory reset" wipes the "SD", but the bootloader unlock does. You can do a backup before rooting if you install ADB on your PC. See 3a.
3. Install ADB on your PC http://www.howtogeek.com/125769/how-to-install-and-use-abd-the-android-debug-bridge-utility/ and test the connection with "adb devices" command.
a. Consider backup of DNA before unlocking http://forum.xda-developers.com/showthread.php?t=1420351
4. Install a recovery.
a. Dowload a recovery to your PC, either Clockworkmod http://forum.xda-developers.com/showthread.php?t=2051547 or TWRP http://forum.xda-developers.com/showthread.php?t=1994662. Extract the recovery.img file to a folder on your desktop,
b. Connect your DNA to your PC. Open a command prompt in the folder with the recovery by shift-right clicking in that folder and selecting "open command prompt here".
c. Type "adb reboot bootloader" without quotes and enter. DNA will reboot into bootloader. enter "fastboot flash recovery recovery.img" and you're there. You're done with the PC.
5. Install superuser and busybox.
a. Download superuser http://downloads.noshufou.netdna-cdn.com/superuser/Superuser-3.1.3-arm-signed.zip to your "SD card".
b. Reboot to recovery. You can start recovery during a boot by holding down the volume down button during power up of phone.
c. Use the install zip function to install the above zip. Find links to wipe cach partition and Dalvik cache. Reboot and you're rooted.
d. Install busybox from market.
6. Change to a kernel that can write to system. Most reliable is LK 0.9.5. This will also save you considerable battery life. http://forum.xda-developers.com/showthread.php?t=2106178
a. Download the zip to your DNA and unzip it. There is a boot.img file and another zip file with "kernel modules".
b. Download flash image GUI from market. Use it to find the boot.img file and flash, ignoring the warning about modules. (hard way is use ADB and fastboot flash boot boot.img)
c. Use recovery to install the modules zip package with the install zip function. Wipe cache and Dalvik cache
and reboot.
7. Install Titanium Backup. With this, you can simply freeze or uninstall any app, system/bloat or otherwise, but it requires the system write kernel to change system files.
6. Stronly consider switching ROMs to Viper. All the good of stock but better in so many ways.
yearn2burn said:
Here's state of the art for today:
1. Hack DNA to make it look like non-Verizon to the htcdev.com site. Here's a new painless method: http://forum.xda-developers.com/showthread.php?t=2109862
2. Go to htcdev.com and follow link to unlock bootloader. Note that this will WIPE YOUR "SD CARD". It's the only thing that does that. No problem with ROMs, etc. Not even a "factory reset" wipes the "SD", but the bootloader unlock does. You can do a backup before rooting if you install ADB on your PC. See 3a.
3. Install ADB on your PC http://www.howtogeek.com/125769/how-to-install-and-use-abd-the-android-debug-bridge-utility/ and test the connection with "adb devices" command.
a. Consider backup of DNA before unlocking http://forum.xda-developers.com/showthread.php?t=1420351
4. Install a recovery.
a. Dowload a recovery to your PC, either Clockworkmod http://forum.xda-developers.com/showthread.php?t=2051547 or TWRP http://forum.xda-developers.com/showthread.php?t=1994662. Extract the recovery.img file to a folder on your desktop,
b. Connect your DNA to your PC. Open a command prompt in the folder with the recovery by shift-right clicking in that folder and selecting "open command prompt here".
c. Type "adb reboot bootloader" without quotes and enter. DNA will reboot into bootloader. enter "fastboot flash recovery recovery.img" and you're there. You're done with the PC.
5. Install superuser and busybox.
a. Download superuser http://downloads.noshufou.netdna-cdn.com/superuser/Superuser-3.1.3-arm-signed.zip to your "SD card".
b. Reboot to recovery. You can start recovery during a boot by holding down the volume down button during power up of phone.
c. Use the install zip function to install the above zip. Find links to wipe cach partition and Dalvik cache. Reboot and you're rooted.
d. Install busybox from market.
6. Change to a kernel that can write to system. Most reliable is LK 0.9.5. This will also save you considerable battery life. http://forum.xda-developers.com/showthread.php?t=2106178
a. Download the zip to your DNA and unzip it. There is a boot.img file and another zip file with "kernel modules".
b. Download flash image GUI from market. Use it to find the boot.img file and flash, ignoring the warning about modules. (hard way is use ADB and fastboot flash boot boot.img)
c. Use recovery to install the modules zip package with the install zip function. Wipe cache and Dalvik cache
and reboot.
7. Install Titanium Backup. With this, you can simply freeze or uninstall any app, system/bloat or otherwise, but it requires the system write kernel to change system files.
6. Stronly consider switching ROMs to Viper. All the good of stock but better in so many ways.
Click to expand...
Click to collapse
While all of this is very very helpful, I failed to mention that this isn't my first rodeo, While I have firm understanding of ADB and rooting and flashing, my approach was more of the "behind the scenes" kind of stuff like what goes on inside of the ROM (tweaking files and what not) I'm at the stage where im trying to learn how to cook a rom(i guess some would say). I've already done so with CM10.1 for my Nexus 7(compiled from sauce), im farily comfortable with linux and my way around the OS. I've got the kitchen setup as well as apktool and what Im trying to learn is how to use these tools to their full extent.
like to make the boot.img unsecure, create a "flashable signed zip", remove non essential apps, the starter stuff
A little bit of background about me: I love computers, im going to school for a Computer Science degree, this kind of work has always interested me and I cant seem to get enough of it, ever since ive discovered this site i cant keep away and i love this communty, I've always wanted to just do more than flash someone else's work, i want to give back and start being able to do things.
Like i said before thanks to everyone for any information its all much appreciated!
I am very new to the android world, seeing as I am a recent iOS convert. However, I am still struggling with all the terminology and technicalities of android and require assistance (perhaps a lot! :cyclops.
I have managed to root my G2 (VERIZON MODEL) but am stuck there. I do not know how to install CWM or TWRP, nor install any custom ROMs like CM or Gummy.
So will anyone be kind enough to guide me through the process? Thank you.
P.S.
I have searched through the threads in this forum regarding installing custom ROMs and am still confused.
from this thread here
http://forum.xda-developers.com/showthread.php?t=2449670
first download twrp for your device, http://techerrata.com/file/twrp2/g2vzw/openrecovery-twrp-2.6.3.3-g2vzw.zip
plug the phone to the computer, make sure u have usb debugging on in developer settings of phone
since you are already rooted, place that file recovery img to the IOROOT folder.
once done, rename the recovery file to recovery.img
one done, CONTROL + SHIFT + RIGHT CLICK, OPEN COMMAND PROMPT HERE
then type this
adb push recovery.img /data/local/tmp/recovery.img
adb shell
(IF YOU DONT SEE A # prompt on your phone, type su in the command prompt to get it then allow it on phone. once thats done then contine onto next step blow.)
cd /data/local/tmp
dd if=/data/local/tmp/recovery.img of=/dev/block/platform/msm_sdcc.1/by-name/recovery
exit
adb reboot recovery
once its complet just reboot the phone and you should have twrp installed!
once twrp is installed, you can dl the verizon version of paranoid android here
http://downloads.codefi.re/houstonn/kitkat/G2/PA/vs980/pa_g2-4.0-ALPHA-20131205-vs980.zip
and
http://www.androidfilehost.com/?fid=23252070760973599
dl the file, drag the files to the phone, dont place into any folder though.
to install, go to the ioroot folder again, control shift right click open prompt again, type adb reboot recovery
phone should reboot to recovery, go to settings, then select USE RM-F instead of formatting, then go to wipe, advance, select dalvik cache, system, data, and cache. IMPORTANT DO NOT SELECT INTERNAL STORAGE!!!
then swipe to wipe
then go to install then install the paranoid android download first, once its installed, hit the back button on the botom right, then install the GAPPS, then reboot the device your done.
Or you could just download the recovery.img that u choose, and flash it using the app called "Flashify". Easiest way by far and works perfectly for me everytime, using both TWRP and CWM whenever I need.
Once you have that done, installing a ROM such as GUMMY is fairly simple since it usually has the instructions right there in the OP of the thread. Pretty straightforward.
expertzero1 said:
from this thread here
http://forum.xda-developers.com/showthread.php?t=2449670
first download twrp for your device, http://techerrata.com/file/twrp2/g2vzw/openrecovery-twrp-2.6.3.3-g2vzw.zip
plug the phone to the computer, make sure u have usb debugging on in developer settings of phone
since you are already rooted, place that file recovery img to the IOROOT folder.
once done, rename the recovery file to recovery.img
one done, CONTROL + SHIFT + RIGHT CLICK, OPEN COMMAND PROMPT HERE
then type this
adb push recovery.img /data/local/tmp/recovery.img
adb shell
(IF YOU DONT SEE A # prompt on your phone, type su in the command prompt to get it then allow it on phone. once thats done then contine onto next step blow.)
cd /data/local/tmp
dd if=/data/local/tmp/recovery.img of=/dev/block/platform/msm_sdcc.1/by-name/recovery
exit
adb reboot recovery
once its complet just reboot the phone and you should have twrp installed!
once twrp is installed, you can dl the verizon version of paranoid android here
http://downloads.codefi.re/houstonn/kitkat/G2/PA/vs980/pa_g2-4.0-ALPHA-20131205-vs980.zip
and
http://www.androidfilehost.com/?fid=23252070760973599
dl the file, drag the files to the phone, dont place into any folder though.
to install, go to the ioroot folder again, control shift right click open prompt again, type adb reboot recovery
phone should reboot to recovery, go to settings, then select USE RM-F instead of formatting, then go to wipe, advance, select dalvik cache, system, data, and cache. IMPORTANT DO NOT SELECT INTERNAL STORAGE!!!
then swipe to wipe
then go to install then install the paranoid android download first, once its installed, hit the back button on the botom right, then install the GAPPS, then reboot the device your done.
Click to expand...
Click to collapse
So I take it that I put the "ioroot10" file into my phone over the USB, then extract the files of the TWRP file, then place the extracted TWRP file inside of the ioroot10 file? Also, I did the control+shift+right click, but there is not OPEN COMMAND PROMPT option. Sorry for all the questions..
dlee96 said:
So I take it that I put the "ioroot10" file into my phone over the USB, then extract the files of the TWRP file, then place the extracted TWRP file inside of the ioroot10 file? Also, I did the control+shift+right click, but there is not OPEN COMMAND PROMPT option. Sorry for all the questions..
Click to expand...
Click to collapse
no, you place the recovery.img to the ioroot10 folder, ioroot10 stays on your computer.
control + shift + right click = open command window here
Just use flashify its free n so much easier
the definition of open: “mkdir android ; cd android ; repo init -u git:// android.git.kernel.org/platform/manifest.git ; repo sync ; make" gansta mic drop
Hi Guys,
I'm hoping someone can help me here with unbricking my daughters Nabi 2 tablet.
The long story short is that I've tried to update to the latest OTA with TWRP 2.3.3.0 (Nabi 1.9.37) and gapps installed in the past (in order to have google play services).
After downloading the OTA and successfull file verification it booted into TWRP mode and this is when things went wrong...
As I wasn't sure about how to even leave the TWRP mode I have hit few things by accident (I think one of them asked me if I want to wipe my ROM and I said YES + when I was after that trying to reboot the tablet it gave me a warning saying something like "you have no OS installed - are you sure to reboot?).
Now, of course due to my stupid actions it doesn't work - stuck on Nabi boot logo and when I try to pres Volume+ and Power together it gives me the screen with 4 options to choose from (Boot Normally, Fastboot Protocol, Recovery Kernel, Forced Recovery) but I still can't select/move the highlighted item. All what I'm able to do now is to power it off by holding the power button pressed for couple seconds.
Based on your experience here - is there anything that can be done or is it a "real brick" and we need to buy something new for her?
Thank you for any suggestions.
Hi,
I managed to boot into TWRP somehow...
Could someone please direct me how I can re-flash it with a Nabi 2 UK OS (and where I can source the file from if possible at all)?
Cheers,
T1000
termostat1000 said:
Hi,
I managed to boot into TWRP somehow...
Could someone please direct me how I can re-flash it with a Nabi 2 UK OS (and where I can source the file from if possible at all)?
Cheers,
T1000
Click to expand...
Click to collapse
Try sections 9 and 10. http://forum.xda-developers.com/nabi-2/general/nabi-information-t3229119
Hi,
Using NabiLab I managed to load stock 1.9.37 through TWRP.
At the moment tablet will start, let me through the initial setup wizard and go into normal mode from when it was new (no Google services available).
When I try to install gapps (TWRP mode) using NabiLab it goes into endless boot loop showing just a splash screen of the screen lock and reloads again.
I tried also bringing it more to factory condition but it is not recognised in NabiLab when android is fully booted (even though PC can see it). I tried different drivers but without too much luck. When in TWRP mode it comes up as Alcatel ADB Device and when adroid is booted it comes up as a storage device rather than ADB.
I feel I'm pretty close but I need just a hint how to solve it finally without bricking it for real...
Cheers
T
termostat1000 said:
Hi,
Using NabiLab I managed to load stock 1.9.37 through TWRP.
At the moment tablet will start, let me through the initial setup wizard and go into normal mode from when it was new (no Google services available).
When I try to install gapps (TWRP mode) using NabiLab it goes into endless boot loop showing just a splash screen of the screen lock and reloads again.
I tried also bringing it more to factory condition but it is not recognised in NabiLab when android is fully booted (even though PC can see it). I tried different drivers but without too much luck. When in TWRP mode it comes up as Alcatel ADB Device and when adroid is booted it comes up as a storage device rather than ADB.
I feel I'm pretty close but I need just a hint how to solve it finally without bricking it for real...
Cheers
T
Click to expand...
Click to collapse
Pretty hard to brick a Nabi2.
Why did you choose 1.9.37? Isn't the latest 2.3.2 and already has Gapps?
When in Android do you have ADB turned on in Developer options?
Is this the procedure you used?
a) Download the ROM for your device in section 10
b) Boot to TWRP (see above for instructions)
c) Do a backup of just the boot partition in TWRP.
- Click Restore tab
- Just check "boot" and nothing else.
- Swipe to Backup
d) Eject the external SD from the tablet and place in the computer
- Note: You should unmount the card from the mount tab in TWRP before ejecting it. (Uncheck the box next to external SD)
e) Connect the SD card to you computer
f) On the SD card navigate to the folder TWRP/BACKUPS/XXXX. XXX is a serial number unique to your Nabi.
g) Make a new folder and call in whatever you want. So it should now look like TWRP/BACKUPS/XXX/yourfolder
h) Unzip the ROM file you downloaded in to the "yourfolder" you created above. The files should look like ext4.system.win, emmc.boot.win, ext.addon.win, etc. Inside the the "yourfolder" directory.
i) Download the bootloader zip for your device from section 10
j) Copy it to the external SD in a location you will remember. This will be for the bootloader update.
k) Eject the SD card from your computer (safely eject it)
l) Install SD card in Nabi
- After inserted in tablet go to TWRP mount tab and check the box to mount the SD card
m) Go to restore tab, and find the backup under the "yourfolder" you made and unzipped the files to.
n) You should be able to select boot, system, and addon and skip the others.
o) If everything restores then go to TWRP install tab, find the bootloader.zip you downloaded and install it.
p) Reboot
Code:
[U][B]Nabi2 Original United Kingdom (NABI-NV7A-UK)[/B][/U]
Version 2.3.2[URL="https://www.androidfilehost.com/?fid=24269982087011751"] Download[/URL]
ROM Mirror[URL="http://www.nabtabhacks.com/downloads/232UKstock.zip"] Download[/URL]
Bootloader [URL="https://www.androidfilehost.com/?fid=24269982087013995"] Download[/URL]
aicjofs said:
Pretty hard to brick a Nabi2.
Why did you choose 1.9.37? Isn't the latest 2.3.2 and already has Gapps?
When in Android do you have ADB turned on in Developer options?
Is this the procedure you used?
a) Download the ROM for your device in section 10
b) Boot to TWRP (see above for instructions)
c) Do a backup of just the boot partition in TWRP.
- Click Restore tab
- Just check "boot" and nothing else.
- Swipe to Backup
d) Eject the external SD from the tablet and place in the computer
- Note: You should unmount the card from the mount tab in TWRP before ejecting it. (Uncheck the box next to external SD)
e) Connect the SD card to you computer
f) On the SD card navigate to the folder TWRP/BACKUPS/XXXX. XXX is a serial number unique to your Nabi.
g) Make a new folder and call in whatever you want. So it should now look like TWRP/BACKUPS/XXX/yourfolder
h) Unzip the ROM file you downloaded in to the "yourfolder" you created above. The files should look like ext4.system.win, emmc.boot.win, ext.addon.win, etc. Inside the the "yourfolder" directory.
i) Download the bootloader zip for your device from section 10
j) Copy it to the external SD in a location you will remember. This will be for the bootloader update.
k) Eject the SD card from your computer (safely eject it)
l) Install SD card in Nabi
- After inserted in tablet go to TWRP mount tab and check the box to mount the SD card
m) Go to restore tab, and find the backup under the "yourfolder" you made and unzipped the files to.
n) You should be able to select boot, system, and addon and skip the others.
o) If everything restores then go to TWRP install tab, find the bootloader.zip you downloaded and install it.
p) Reboot
Code:
[U][B]Nabi2 Original United Kingdom (NABI-NV7A-UK)[/B][/U]
Version 2.3.2[URL="https://www.androidfilehost.com/?fid=24269982087011751"] Download[/URL]
ROM Mirror[URL="http://www.nabtabhacks.com/downloads/232UKstock.zip"] Download[/URL]
Bootloader [URL="https://www.androidfilehost.com/?fid=24269982087013995"] Download[/URL]
Click to expand...
Click to collapse
Hi aicjofs,
I followed the steps above except step c which I haven't done.
So it looked good with the NabiLab built in 1.9.37 and it seemed to load fine with my TWRP 2.3.3.0 but it was hgoing into this endless boot loop after trying to install gapps. BTW I went for 1.9.37 as it came with NabiLab and turned right.
After your reply I've donwloaded the 232UK stock rom and bootloader. Copied both onto SD card - at that stage it would let me do a restore directly from the SD card so I've copied the 232UK rom into internal memory. Restore process went OK and at the end I've installed its dedicated bootloader...
Right now the situation is that I can only boot into TWRP but restore doesn't show any available roms (both internal or external memory) even though there is backup folder on the SD card.
What worries me the most is when I go to advanced / file manager / sdcard (internal memory) in TWRP mode it doesn't show any files or folders there. When I try to dipslpay tablet information in NabiLab it shows the external SD card properties properly (capacity/free space) but on the internal memory it says "Size df:KB Free can'tKB used find".
Does it mean it has wiped all the internal memory down to zero? Would this be the reason for recovery no being able to identify the roms on external SD card too?
Looking at the log in TWRP mode it is filled with entries like
E:Unable to mount '/data'
E:Unable to mount '/cache'
E:Can't open /cache/recovery/last_install
E:Can't open (No such file or directory)
What a pain is this thing, honestly...
termostat1000 said:
Hi aicjofs,
I followed the steps above except step c which I haven't done.
So it looked good with the NabiLab built in 1.9.37 and it seemed to load fine with my TWRP 2.3.3.0 but it was hgoing into this endless boot loop after trying to install gapps. BTW I went for 1.9.37 as it came with NabiLab and turned right.
After your reply I've donwloaded the 232UK stock rom and bootloader. Copied both onto SD card - at that stage it would let me do a restore directly from the SD card so I've copied the 232UK rom into internal memory. Restore process went OK and at the end I've installed its dedicated bootloader...
Right now the situation is that I can only boot into TWRP but restore doesn't show any available roms (both internal or external memory) even though there is backup folder on the SD card.
What worries me the most is when I go to advanced / file manager / sdcard (internal memory) in TWRP mode it doesn't show any files or folders there. When I try to dipslpay tablet information in NabiLab it shows the external SD card properties properly (capacity/free space) but on the internal memory it says "Size df:KB Free can'tKB used find".
Does it mean it has wiped all the internal memory down to zero? Would this be the reason for recovery no being able to identify the roms on external SD card too?
Looking at the log in TWRP mode it is filled with entries like
E:Unable to mount '/data'
E:Unable to mount '/cache'
E:Can't open /cache/recovery/last_install
E:Can't open (No such file or directory)
What a pain is this thing, honestly...
Click to expand...
Click to collapse
My fault. I forgot to tell you once you update the bootloader you need to use TWRP for Jellybean, you are still using TWRP for Ice Cream Sandwich .
Code:
[B][U]Nabi2 Original (NABI-NV7A)[/U][/B]
Ice Cream Sandwich TWRP 2.6.3[URL="http://forum.xda-developers.com/attachment.php?attachmentid=2586828&d=1392743412"] Download[/URL]
Jellybean TWRP 2.8.5[URL="http://forum.xda-developers.com/attachment.php?attachmentid=3211498&d=1426404068"] Download[/URL]
KitKat TWRP 2.8.7[URL="http://forum.xda-developers.com/attachment.php?attachmentid=3473994&d=1442276115"] Download[/URL]
Discussion Thread [URL="http://forum.xda-developers.com/showthread.php?t=2074501"]Link[/URL]
At that point you can try to restore the 2.3.2 ROM again. Or try the 2.2 ROM http://forum.xda-developers.com/showpost.php?p=50341726&postcount=85
aicjofs said:
My fault. I forgot to tell you once you update the bootloader you need to use TWRP for Jellybean, you are still using TWRP for Ice Cream Sandwich .
Code:
[B][U]Nabi2 Original (NABI-NV7A)[/U][/B]
Ice Cream Sandwich TWRP 2.6.3[URL="http://forum.xda-developers.com/attachment.php?attachmentid=2586828&d=1392743412"] Download[/URL]
Jellybean TWRP 2.8.5[URL="http://forum.xda-developers.com/attachment.php?attachmentid=3211498&d=1426404068"] Download[/URL]
KitKat TWRP 2.8.7[URL="http://forum.xda-developers.com/attachment.php?attachmentid=3473994&d=1442276115"] Download[/URL]
Discussion Thread [URL="http://forum.xda-developers.com/showthread.php?t=2074501"]Link[/URL]
At that point you can try to restore the 2.3.2 ROM again. Or try the 2.2 ROM http://forum.xda-developers.com/showpost.php?p=50341726&postcount=85
Click to expand...
Click to collapse
Forgive me please but I'm not entirely sure how to load this TWRP 2.8.5 for JellyBean on it with TWRP 2.3.3.0 in place..
Cheers
termostat1000 said:
Forgive me please but I'm not entirely sure how to load this TWRP 2.8.5 for JellyBean on it with TWRP 2.3.3.0 in place..
Cheers
Click to expand...
Click to collapse
You will need to use fastboot to load it. If you have a nabilab folder it already has fastboot available. So using the procedure below you couldn't download the ZIP file I linked in post above. Extract the from the zip the recovery.img or twrp-recovery.img and put it in the nabilab folder. (Im puling the procedure from http://forum.xda-developers.com/nabi-2/general/nabi-information-t3229119 )
1) To load TWRP we will be in the fastboot operational mode(see section 3)
Device powered off:
-Depending on device press and hold the power and vol - keys OR power and vol + key. Some will boot straight to recovery, and others will come to the "bootloader" screen. We want the bootloader.
-To enter fastboot use vol+ and vol- to highlight and select fastboot protocol. (Device will need to be plugged in to computer and fastboot driver installed before the screen will change)
Device powered on:
-Use ADB and execute from the command line:
Code:
adb reboot-bootloader
2) USB plugged in and Fastboot/Bootoader Driver loaded(see section 4) verify with windows device manager if needed.
3) Download the TWRP zip file for your device from TWRP list below(see section 8)
4) Extract the file to the location your are running your command prompt(see section 6)
-The file will be called twrp-recovery.img or recovery.img
5) Depending on the name of the file in step 4, load TWRP by typing at the command prompt:
Code:
fastboot flash recovery recovery.img
or
Code:
fastboot flash recovery twrp-recovery.img
aicjofs said:
You will need to use fastboot to load it. If you have a nabilab folder it already has fastboot available. So using the procedure below you couldn't download the ZIP file I linked in post above. Extract the from the zip the recovery.img or twrp-recovery.img and put it in the nabilab folder. (Im puling the procedure from http://forum.xda-developers.com/nabi-2/general/nabi-information-t3229119 )
1) To load TWRP we will be in the fastboot operational mode(see section 3)
Device powered off:
-Depending on device press and hold the power and vol - keys OR power and vol + key. Some will boot straight to recovery, and others will come to the "bootloader" screen. We want the bootloader.
-To enter fastboot use vol+ and vol- to highlight and select fastboot protocol. (Device will need to be plugged in to computer and fastboot driver installed before the screen will change)
Device powered on:
-Use ADB and execute from the command line:
Code:
adb reboot-bootloader
2) USB plugged in and Fastboot/Bootoader Driver loaded(see section 4) verify with windows device manager if needed.
3) Download the TWRP zip file for your device from TWRP list below(see section 8)
4) Extract the file to the location your are running your command prompt(see section 6)
-The file will be called twrp-recovery.img or recovery.img
5) Depending on the name of the file in step 4, load TWRP by typing at the command prompt:
Code:
fastboot flash recovery recovery.img
or
Code:
fastboot flash recovery twrp-recovery.img
Click to expand...
Click to collapse
Hi,
Thank you very much for your help but it clearly looks that this is way beyond my knowledge on how to use all of these fastboot, command, adb and so on...
I regret I ever touched the thing at all.
So there is absolutely no easy way - command line is a must from where I am right now?
termostat1000 said:
Hi,
Thank you very much for your help but it clearly looks that this is way beyond my knowledge on how to use all of these fastboot, command, adb and so on...
I regret I ever touched the thing at all.
So there is absolutely no easy way - command line is a must from where I am right now?
Click to expand...
Click to collapse
Its not a must but easiest to try and walk you through. Which version of Nabilab are you using? You could move some files around and still use Nabilab. Up to you which way to go forward. I'll try and help.
aicjofs said:
Its not a must but easiest to try and walk you through. Which version of Nabilab are you using? You could move some files around and still use Nabilab. Up to you which way to go forward. I'll try and help.
Click to expand...
Click to collapse
Hi,
I'm not so much afraid of copy/paste for cmd... the biggest fear is that I don't know anything about ADB, fasboot etc. So when your instruction in previous post says use ADB and I purely don't know what it means.
I think if the option is there I'd like to ask if you could help with restoring it with Nabilab.
Thanks a million for your help!
T
termostat1000 said:
Hi,
I'm not so much afraid of copy/paste for cmd... the biggest fear is that I don't know anything about ADB, fasboot etc. So when your instruction in previous post says use ADB and I purely don't know what it means.
I think if the option is there I'd like to ask if you could help with restoring it with Nabilab.
Thanks a million for your help!
T
Click to expand...
Click to collapse
Which version of Nabilab are you using? Is it the commandline version. Black window, where you have to use keyboard to make selections?
aicjofs said:
Which version of Nabilab are you using? Is it the commandline version. Black window, where you have to use keyboard to make selections?
Click to expand...
Click to collapse
Hi,
I'm using Nabilab ver 2 - black windows with keyboard made selections.
termostat1000 said:
Hi,
I'm using Nabilab ver 2 - black windows with keyboard made selections.
Click to expand...
Click to collapse
Find the Nabilab folder on your computer. Open the "recovery" folder. Then open the "stock" folder. Inside it there is recovery.img file. Rename it to recoverystock.img.
You downloaded the twrp-recovery-JBNV7AUS.zip from a few posts back. Extract the twrp-recovery.img file and put it in the stock folder. Now rename the twrp-recovery.img file to recovery.img.
Now boot the tablet to TWRP recovery(the one that isn't working) and run Nabilab. Select 4 Install recoveries. Then 4 instal stock recovery. Then reboot in to recovery and see if you have the 2.8.5 recovery
aicjofs said:
Find the Nabilab folder on your computer. Open the "recovery" folder. Then open the "stock" folder. Inside it there is recovery.img file. Rename it to recoverystock.img.
You downloaded the twrp-recovery-JBNV7AUS.zip from a few posts back. Extract the twrp-recovery.img file and put it in the stock folder. Now rename the twrp-recovery.img file to recovery.img.
Now boot the tablet to TWRP recovery(the one that isn't working) and run Nabilab. Select 4 Install recoveries. Then 4 instal stock recovery. Then reboot in to recovery and see if you have the 2.8.5 recovery
Click to expand...
Click to collapse
Great!
Your trick worked fine and now I can see TWRP 2.8.5.0 and I have problems with drivers - keeps failing to recognize the tablet.
I'll work on the driver issue or is there something I should know about it with TWRP 2.8.5.0 lodaed?
What is my next step from here as Android is still stuck on Nabi logo (no motion) and I'm afraid to do anything in case I create even bigger mess than I already have
I also noticed when I try to shut it down from inside TWRP it asks me a question if I want to root the tablet (Install super SU) - is it something I should do and at what stage?
Thanks!
T
termostat1000 said:
Great!
Your trick worked fine and now I can see TWRP 2.8.5.0 and I have problems with drivers - keeps failing to recognize the tablet.
I'll work on the driver issue or is there something I should know about it with TWRP 2.8.5.0 lodaed?
What is my next step from here as Android is still stuck on Nabi logo (no motion) and I'm afraid to do anything in case I create even bigger mess than I already have
I also noticed when I try to shut it down from inside TWRP it asks me a question if I want to root the tablet (Install super SU) - is it something I should do and at what stage?
Thanks!
T
Click to expand...
Click to collapse
If you can see the files again now with the correct TWRP. You can try to restore the 2.3.2 ROM again. Or maybe try the procedure from post #5 with the 2.2 ROM I linked to in post #7. You don't have to do the bootloader install anymore so skip that step. Installing root doesn't matter, you can choose to install or not.
aicjofs said:
If you can see the files again now with the correct TWRP. You can try to restore the 2.3.2 ROM again. Or maybe try the procedure from post #5 with the 2.2 ROM I linked to in post #7. You don't have to do the bootloader install anymore so skip that step. Installing root doesn't matter, you can choose to install or not.
Click to expand...
Click to collapse
You're a STAR!
All happy working as new with 232UK ROM and bootloader loaded with your instructions.
I'd never get this sorted without your specialized help.
If I only could I'd send you something just to say Thank You...
T - Happy Dad of Amelia
termostat1000 said:
You're a STAR!
All happy working as new with 232UK ROM and bootloader loaded with your instructions.
I'd never get this sorted without your specialized help.
If I only could I'd send you something just to say Thank You...
T - Happy Dad of Amelia
Click to expand...
Click to collapse
Your thanks is enough Glad we got it sorted and a happy kid!
Alright, so I screwed up my watch a few days ago and it ended up not getting past the splash screen and going straight to recovery. Thanks to @z0mghii, I was able to get a TWRP backup of the system, boot, and data. I replaced this backup with my own so none of his data (if possible) could be taken advantage of. However, after flashing it, I was still unable to boot up. Here are the steps I took in order to get everything back to working order. Keep in mind this is for WREN, the small version. Some steps may be unnecessary.
1. Boot to TWRP
2. Go to advanced wipe
3. Wipe everything
4. Go to the link below and download the TWRP Backup
5. Create a backup of a small partition (like boot) on your watch to create the folder.
6. Plug watch into PC while in TWRP
7. Go to the watch's internal storage
8. Go to the TWRP folder
9. Go to the subfolder
10. Paste the downloaded backup folder into this folder, this should be with the one you created earlier
11. Restore this backup on your watch, be sure to check all the boxes
12. Reboot to the bootloader
13. Install ADB if you haven't already, I recommend the 15 second one
14. While the watch is in the bootloader and it is plugged in, type the following commands
fastboot erase cache
fastboot erase misc
fastboot reboot
https://drive.google.com/drive/folders/0B_HUnwYIrFskUW10UDZ0dXdHQzg (You might have to download each item and put them in a folder instead, unless I'm oblivious to something, sorry )
After this, your watch should boot up, then power back down, then boot back up again. This will be followed up by the boot animation and go to the welcome screen.
If any of you guys could provide me with the latest stock rom version TWRP backup or a stock recovery.img, it would be greatly appreciated. (Unless June patch is the latest). The recovery would be great no matter what. Getting the stock recovery can be done by typing the following commands into the command prompt on a PC. Hopefully they work. It should be copied onto the /sdcard.
Via adb shell (make sure ADB debugging is on in developer options, then type adb shell in CMD on PC) type: cat/proc/mtd and press enter
You will see which is recovery partition and then type: dd if=/dev/mtd/mtd1 of=/sdcard/recovery.img (note that mtd1 you must replace with number which is recovery partition)
I hope I helped somebody with this. Again, huge thanks to @z0mghii for making this possible. I'm sorry for bad formatting.
I'm really new to this. I'm also by no means a developer/hardcore android person. These commands were all taken from google. I take 0 responsibility for your device being ruined. This is just what worked for me.
Reserved
HOLY CRAP IT WORKED!! You just don't know how much this means to me, words can't express!
cland216 said:
HOLY CRAP IT WORKED!! You just don't know how much this means to me, words can't express!
Click to expand...
Click to collapse
Hell yeah. Glad I could help somebody! I've been wanting to give back to the wonderful XDA community for a while as a long time lurker. Also, I'm hoping to get a newer version of the stock rom and a stock recovery.img so you can go back to 100% factory stock for an OTA. I'm pretty proud of myself (being noobish) figuring this out.
Thanks a lot!! My watch was kept in a drawer because it was useless and it has now returned to life, I just have a problem restoring the recovery, the command to locate the recovery folder do not work me, have any idea how located the recovery folder?
klaudio_tv said:
Thanks a lot!! My watch was kept in a drawer because it was useless and it has now returned to life, I just have a problem restoring the recovery, the command to locate the recovery folder do not work me, have any idea how located the recovery folder?
Click to expand...
Click to collapse
Are you referring to "extracting" the recovery img? You only need to do it if you're running the stock recovery.
If so, I think I have screwed the command. Make sure you're in adb shell (in recovery on the watch) and then type "cat /proc/mtd" (with the space in front of cat) without the quotes in order to locate the recovery partition.
You will see which is recovery partition and then type: dd if=/dev/mtd/mtd1 of=/sdcard/recovery.img (note that mtd1 you must replace with number which is recovery partition)
Hopefully this works
Hi, my watch now works well, but I was not able to install updates, when I try to install updates from the watch, watch reboots and go to TWRP recovery. Anyone knows how install the updates?
klaudio_tv said:
Hi, my watch now works well, but I was not able to install updates, when I try to install updates from the watch, watch reboots and go to TWRP recovery. Anyone knows how install the updates?
Click to expand...
Click to collapse
Since the OP helped me, here's my chance to give back..
By no means do I know what hell I'm doing, but I know enough to be dangerous. If you're ready to live dangerously, follow these steps (which worked for me):
1. Go into TWRP on the watch and connect it usb to your computer. Using TWRP file manager, copy the update.zip from CACHE to sdcard\Download.
2. On the computer, browse to Zenwatch internal memory Downloads folder and copy the update.zip file to your computer.
3. Unzip the file on your computer using 7zip.
4. Navigate to \META-INF\com\google\android\ and look for updater-script.
5. Edit updater-script in Notepad++.
6. Delete the lines starting with getprop. This turned out to be lines 2 thru 5.
7. Delete the lines starting with apply_patch_check. This turned out to be lines 10 thru 176
8. Save changes to updater-script then in Windows Explorer highlight all of the files and folders that you unzipped, right-click them and click on 7zip --> Add to update.zip
9. Copy the new update.zip to the Zenwatch internal memory, Downloads folder, overwriting the original update.zip
10. Flash the update.zip file with TWRP.
11. Reboot TWRP to Bootloader.
12. On your computer, goto adb folder where you have fastboot files, and using command prompt type:
fastboot erase cache
fastboot erase misc
fastboot reboot
These steps worked as I was stuck on the June 1, 2016 Android security patch on my Wren Zenwatch. These steps helped me get to the September 1, 2016 security patch.
I managed to update my watch to the September 1 security patch using Cland216's method. But I am unable to update further using the method above. Does anyone have any info on how to update further? Or has any zip files to flash?
If we could get someone to upload the watches stock recovery that would solve all issues.....Why has noone done this for this model yet?
Sent from my OnePlus X using XDA Labs
I'm unable to create a backup file
5. Create a backup of a small partition (like boot) on your watch to create the folder.
6. Plug watch into PC while in TWRP
TWRP :
Could not mount /data
When I try to mount /data , I unable to /data
HOLY ****
Dude.. Let me just say...
YOU ARE THE ****ING ABSOLUTE BEST.
I am now going to make a backup, and save it to my computer, google drive, dropbox, icloud, and every other ****in place I can to make sure this never happens again. Thank you!!!!
Nicholas6706 said:
Alright, so I screwed up my watch a few days ago and it ended up not getting past the splash screen and going straight to recovery. Thanks to @z0mghii, I was able to get a TWRP backup of the system, boot, and data. I replaced this backup with my own so none of his data (if possible) could be taken advantage of. However, after flashing it, I was still unable to boot up. Here are the steps I took in order to get everything back to working order. Keep in mind this is for WREN, the small version. Some steps may be unnecessary.
1. Boot to TWRP
2. Go to advanced wipe
3. Wipe everything
4. Go to the link below and download the TWRP Backup
5. Create a backup of a small partition (like boot) on your watch to create the folder.
6. Plug watch into PC while in TWRP
7. Go to the watch's internal storage
8. Go to the TWRP folder
9. Go to the subfolder
10. Paste the downloaded backup folder into this folder, this should be with the one you created earlier
11. Restore this backup on your watch, be sure to check all the boxes
12. Reboot to the bootloader
13. Install ADB if you haven't already, I recommend the 15 second one
14. While the watch is in the bootloader and it is plugged in, type the following commands
fastboot erase cache
fastboot erase misc
fastboot reboot
https://drive.google.com/drive/folders/0B_HUnwYIrFskUW10UDZ0dXdHQzg (You might have to download each item and put them in a folder instead, unless I'm oblivious to something, sorry )
After this, your watch should boot up, then power back down, then boot back up again. This will be followed up by the boot animation and go to the welcome screen.
If any of you guys could provide me with the latest stock rom version TWRP backup or a stock recovery.img, it would be greatly appreciated. (Unless June patch is the latest). The recovery would be great no matter what. Getting the stock recovery can be done by typing the following commands into the command prompt on a PC. Hopefully they work. It should be copied onto the /sdcard.
Via adb shell (make sure ADB debugging is on in developer options, then type adb shell in CMD on PC) type: cat/proc/mtd and press enter
You will see which is recovery partition and then type: dd if=/dev/mtd/mtd1 of=/sdcard/recovery.img (note that mtd1 you must replace with number which is recovery partition)
I hope I helped somebody with this. Again, huge thanks to @z0mghii for making this possible. I'm sorry for bad formatting.
I'm really new to this. I'm also by no means a developer/hardcore android person. These commands were all taken from google. I take 0 responsibility for your device being ruined. This is just what worked for me.
Click to expand...
Click to collapse
I spoke just a bit too soon, now it is hanging on that animation with the 4 dots. Any suggestions?
NEVERMIND, I AM UP AND RUNNING!! WOOHOOOO