{
"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"
}
Team Win Recovery Project 2.3, or twrp2 for short, is a custom recovery built with ease of use and customization in mind. We started from the ground up by taking AOSP recovery and loading it with the standard recovery options, then added a lot of our own features. It’s a fully touch driven user interface – no more volume rocker or power buttons to mash. The GUI is also fully XML driven and completely theme-able. You can change just about every aspect of the look and feel.
SOURCE: https://github.com/TeamWin/Team-Win-Recovery-Project
Submit Code Change: http://teamw.in/twrp2-gerrit
Live Support: http://webchat.freenode.net/?channels=twrp
Flash attached zip in recovery...
FIXED: mount internal and external in recovery... Huge Thanks to sidneyk
Thanks ! just flashed and rebooted just fine, I looked it over real good but didnt do any wipes or flash a rom with it yet but it seems very smooth clean and fast. I may do a backup and try flashing a rom with it soon and let you know how it goes.. I like the layout much better
thanks
---------- Post added at 06:54 PM ---------- Previous post was at 06:01 PM ----------
did a backup and was able to name it and choose to put it on external, did a full wipe and just flashed [ROM][UNOFFICIAL]Slim-3.1.0-t769 STRUCK (Updated 1/21/13) successfully useing TWRP even used the mount storage and coppied the files over while in recovery. did notice that recovery rebooted itself a couple times back into recovery. I could not get unmount to go so just unpluged usb and recovery rebooted. maybe that is normal?? overall so far is working great!
Thanks again
I just flashed this recovery over your previous TWRP recovery and looks pretty good. I haven't tried flashing anything yet or doing any backups, I'll get to that later on. One thing I did notice though is that I'm still not able to see the internal sdcard in this recovery no matter what I've tried, it always just shows external sdcard. I don't know if it will help or not, but VividBoarder has a working TWRP recovery, which he calls version 2.3.2.3, for the Asus TF101 tablet that is 4.2.1 JB compatible and sees both internal and external storage and can flash from or backup to either. Here is the link to his thread, in case you want to look for possible ideas. Thanks and keep up the good work.
http://forum.xda-developers.com/showthread.php?t=1818452
sidneyk said:
I just flashed this recovery over your previous TWRP recovery and looks pretty good. I haven't tried flashing anything yet or doing any backups, I'll get to that later on. One thing I did notice though is that I'm still not able to see the internal sdcard in this recovery no matter what I've tried, it always just shows external sdcard. I don't know if it will help or not, but VividBoarder has a working TWRP recovery, which he calls version 2.3.2.3, for the Asus TF101 tablet that is 4.2.1 JB compatible and sees both internal and external storage and can flash from or backup to either. Here is the link to his thread, in case you want to look for possible ideas. Thanks and keep up the good work.
http://forum.xda-developers.com/showthread.php?t=1818452
Click to expand...
Click to collapse
Im not sure what the difference is between our phones but I am able to choose to back up between the internal or external and can mount either of them and can choose which one to install from. I can see both and access both sdcard and was running AOKP when I flashed the TWRP over CWM.
it is running great on my blaze! Im not a dev so i have no clue as to why. I did not wipe anything when I flashing TWRP. just flashed and rebooted and into AOKP just fine then rebooted into recovery to backup and flashed Slim rom.
---------- Post added at 11:40 PM ---------- Previous post was at 11:08 PM ----------
woodyjlw said:
Im not sure what the difference is between our phones but I am able to choose to back up between the internal or external and can mount either of them and can choose which one to install from. I can see both and access both sdcard and was running AOKP when I flashed the TWRP over CWM.
it is running great on my blaze! Im not a dev so i have no clue as to why. I did not wipe anything when I flashing TWRP. just flashed and rebooted and into AOKP just fine then rebooted into recovery to backup and flashed Slim rom.
Click to expand...
Click to collapse
I guess I was wrong. I just went back in and double checked myself it shows the option for internal sd but when I choose to mount it with TWRP I get my external 16 gig instead. so I guess that is what your getting too??
woodyjlw said:
Im not sure what the difference is between our phones but I am able to choose to back up between the internal or external and can mount either of them and can choose which one to install from. I can see both and access both sdcard and was running AOKP when I flashed the TWRP over CWM.
it is running great on my blaze! Im not a dev so i have no clue as to why. I did not wipe anything when I flashing TWRP. just flashed and rebooted and into AOKP just fine then rebooted into recovery to backup and flashed Slim rom.
---------- Post added at 11:40 PM ---------- Previous post was at 11:08 PM ----------
I guess I was wrong. I just went back in and double checked myself it shows the option for internal sd but when I choose to mount it with TWRP I get my external 16 gig instead. so I guess that is what your getting too??
Click to expand...
Click to collapse
Yep, tried changing it in the mounts and there is a checkbox I think in advanced with unmount sdcard checked and it wouldn't let me uncheck it. I just have to remember to move anything I want to flash to external first and especially before wiping anything. I made that mistake with a CWM recovery on the tf101 and wiped everything, expecting the new ROM to be on external, and that one could only see internal so I had to find another way to flash an OS to get back online.
[EDIT] Just for clarity, I checked again and what I see is in the install option, when I click on 'Use external', it switches to /sdcard and shows everything on the external microSD card. When I click on 'Use internal', it switches to /emmc, but shows me an empty directory. I can go up a level and see things in the / directory of the internal memory, but changing to /sdcard directory still shows the external microSD and there isn't any directory pointing to what would normally be 'sdcard' where the Download folder normally is.
What I would need to figure it out - is from the tf101 I need their BoardConfig.mk file to see if I can figure out the TWRP mount points.
Racing19969 said:
What I would need to figure it out - is from the tf101 I need their BoardConfig.mk file to see if I can figure out the TWRP mount points.
Click to expand...
Click to collapse
I'll try to grab it from his github and post a link or something here. Wish I knew more on the development side, but I know about enough to be dangerous.
[EDIT] Here you go:
https://github.com/ViViDboarder/android_device_asus_tf101/blob/ics/BoardConfig.mk
sidneyk said:
I'll try to grab it from his github and post a link or something here. Wish I knew more on the development side, but I know about enough to be dangerous.
[EDIT] Here you go:
https://github.com/ViViDboarder/android_device_asus_tf101/blob/ics/BoardConfig.mk
Click to expand...
Click to collapse
Thanks, running a build right now and will let you know how it turns out...
updated OP with the following:
There doesn't seem to be an easy-to-use interface to mount the internal sdcard (emmc) - but you can still do it. Go into Advanced, then Terminal Command, select / as your starting folder (working directory - just hit select it'll likely be there as default), then type in the following:
/sbin/mount /dev/block/mmcblk0p28 /emmc
Then when you back out of there and get to the Install area, you can switch between the internal and external. Hope that helps!
Re: TeamWin Recovery Project TWRP Recovery V2.4 Blaze4G
Racing19969 said:
...There doesn't seem to be an easy-to-use interface to mount the internal sdcard (emmc) - but you can still do it. Go into Advanced, then Terminal Command, select / as your starting folder (working directory - just hit select it'll likely be there as default), then type in the following:
/sbin/mount /dev/block/mmcblk0p28 /emmc
Then when you back out of there and get to the Install area, you can switch between the internal and external. Hope that helps!
Click to expand...
Click to collapse
Glad to see I'm still helpful
dwitherell said:
Glad to see I'm still helpful
Click to expand...
Click to collapse
Yes you are.... I remembered you posting this back when I built the first TWRP recovery.. THANKS
Racing19969 said:
Yes you are.... I remembered you posting this back when I built the first TWRP recovery.. THANKS
Click to expand...
Click to collapse
No prob - I'm just happy I could come up with something useful from time to time
And fwiw - your build was my first experience with TWRP and I have yet to look back, so thanks for getting this together!
@Racing19969 - I unpacked your zip file and unpacked the recovery image with Android Kitchen and made just 1 change to the /sbin/postrecoveryboot.sh in the ramdisk to make it look like this:
Code:
#!/sbin/sh
# 0: charge
# 1: direct
# 2: recovery_enter
# 3: recovery_end
# 4: download_end
sleep 3
echo 3 > /dev/block/mmcblk0p12
#mount internal sdcard
/sbin/mount /dev/block/mmcblk0p28 /emmc
# Enable USB mass storage
echo 0 > /sys/class/android_usb/android0/enable
echo adb,mass_storage > /sys/class/android_usb/android0/functions
echo 1 > /sys/class/android_usb/android0/enable
Then I repacked, rezipped, pushed, flashed, rebooted to Android, rebooted to recovery and from 'Install' I can see both external sdcard from external button and 'emmc' from internal button and don't have to try to remember the command, and even worse, to type it in each time. I was looking for the least intrusive and easiest way to do it without resorting to trying to rebuild the whole thing. Now I can get to the 'Download' folder if I forget to move something to the external card before rebooting recovery. I am posting this for your consideration as I don't know for sure if it messes anything else up. Thanks again for your efforts.
[EDIT] I have changed the info above to match what actually worked. I accidentally left the change in the postrecoveryboot.sh when I thought I had reverted it to test the recovery.fstab change I spoke of earlier, which actually does nothing by itself. The command added in this script does work. Sorry everyone for the confusion.
sidneyk said:
@Racing19969 - I unpacked your zip file and unpacked the recovery image with Android Kitchen and made just 1 change to the /sbin/postrecoveryboot.sh in the ramdisk to make it look like this:
Code:
#!/sbin/sh
# 0: charge
# 1: direct
# 2: recovery_enter
# 3: recovery_end
# 4: download_end
sleep 3
echo 3 > /dev/block/mmcblk0p12
#mount internal sdcard
/sbin/mount /dev/block/mmcblk0p28 /emmc
# Enable USB mass storage
echo 0 > /sys/class/android_usb/android0/enable
echo adb,mass_storage > /sys/class/android_usb/android0/functions
echo 1 > /sys/class/android_usb/android0/enable
Then I repacked, rezipped, pushed, flashed, rebooted to Android, rebooted to recovery and from 'Install' I can see both external sdcard from external button and 'emmc' from internal button and don't have to try to remember the command, and even worse, to type it in each time. I was looking for the least intrusive and easiest way to do it without resorting to trying to rebuild the whole thing. Now I can get to the 'Download' folder if I forget to move something to the external card before rebooting recovery. I am posting this for your consideration as I don't know for sure if it messes anything else up. Thanks again for your efforts.
[EDIT] I have changed the info above to match what actually worked. I accidentally left the change in the postrecoveryboot.sh when I thought I had reverted it to test the recovery.fstab change I spoke of earlier, which actually does nothing by itself. The command added in this script does work. Sorry everyone for the confusion.
Click to expand...
Click to collapse
Definately works, Thanks for the fix.... Now I just need to figure out how to add it to the recovery build process..
UPDATED OP.. NEW BUILD UP WITH INTERNAL/EXTERNAL MOUNTS FIXED... HUGE THANKS TO SIDNEYK
You must be a busy busy Dev! Many thanks for the updates!
AWESOME!
Racing19969 said:
Definately works, Thanks for the fix.... Now I just need to figure out how to add it to the recovery build process..
UPDATED OP.. NEW BUILD UP WITH INTERNAL/EXTERNAL MOUNTS FIXED... HUGE THANKS TO SIDNEYK
Click to expand...
Click to collapse
Assuming you're building with cm sources, as per the instructions, it seems to be pulling the 'postrecoveryboot.sh' from 'android_devices_samsung_msm8660-common'. You could try to make the change there (at least for your local build repo) or maybe there is some other device specific file somewhere in the process to echo that 1 line to the file just before the build? Just ideas, I haven't done much coding since the days of BASIC and that's been a while back.
Possible wipe issues?
I've been playing around with a few different ROMs since rooting and noticed yesterday that I had hardly any space left because there was a bunch of stuff from previous installs still there that I thought I wiped out in TWRP. I was getting ready to flash PACman JB again and went into TWRP to try and wipe as much clean as possible and noticed some errors and looking around in the file manager it didn't seem to be really wiping much. Factory reset probably cleaned some data out, but otherwise stuff was still there. Can someone else test and see if this is the case, especially if someone is well versed with Samsung's file and partition schemes. For now, I'm back with CWM which does seem to get rid of stuff, even the external sdcard, if you aren't careful. Thanks.
I am going to flash the lates AOKP back on and I updated twrp the other day and I have cm10 on here now. I want to back up my cm10 to my external 16 gig before I flash the new AOKP. What can I do to help?
just give me the instructions/how to of what you need and I will do my best to help.
Thanks
@sidneyk, another sure fire way to clean out unwanted junk and caches is go into settings/storage and erase SD card. This clears out all files leaving the bare minimal and most of your Google apps. I only had to reinstall about 8 apps, but my problem was saying I had no USB storage due to gallery,pics etc. . Nothing was there to delete, erased SD, problem solved plus got rid of all those extra folders I didn't know if I needed or not.
Using the newest build 1/26 did my first backup and the recovery rebooted prior to the backup finishing. The second backup went ok. Just wanted someone to know. I don't know if this is an issue with the 2.4 alpha or not, perhaps it is. I believe the backup stopped when generating the md5 for the data partition. If it happens again I will post what exactly went wrong (I was getting ready to leave when it happened).
Yes I can confirm that there are random reboots, and also the internal file sys is not mounting, it keeps showing the external SD regardless which one is mounted. Just wanna add that the internal file manager does show both correctly only when I mount it and try to browse it on the computer is when there's an issue. Im running plain stock ics.
Related
Need help - no rom, system is formatted, sdcard is formatted & won't mount, CWR works
Hello, I've been trying to fix this for quite some time now and I think I'm finally stumped so here's to hoping someone far more knowledgeable can point me in the right direction.
Here's my current situation:
- The phone is rooted, has hboot, and a working ClockworkMod Recovery v5.8.3.1
- sdcard is formatted
- sdcard will not mount
- system is formatted
Don't ask how it got to this state (because I honestly couldn't tell you in detail), I'm trying to help a friend. Apparently he tried to install AOKP Milestone 6.1, didn't like it, and tried to revert to CleanROM, but it resulted in a boot loop. From there he tried to fix it and we have the current state of the phone above. :crying:
My end goal to this is to be able to get a rom.zip onto the phone, internal or sdcard, whatever will work, and then install said rom via Clockwork Recovery.
When I try to mount the sdcard via CWR, it says "E:Can't mount /sdcard/" so I was going to use adb shell to try and mount the sdcard and then push a ROM.zip onto the sdcard, until I realized /system was formatted and as such I couldn't do anything with adb:
{
"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"
}
C:\Recovery>adb shell
- exec '/system/bin/sh' failed: No such file or directory (2) -
Click to expand...
Click to collapse
Does anyone have any ideas as to what I can do in general for any of these issues? I need to figure out a way to mount the sdcard and get a rom on there to install, or get the necessary files into /system in order to use adb to try and fix the sdcard issue.
Someone who knows their stuff, please point me in the right direction to get this resolved. I really hope the phone isn't busted for good - the fact that I still have hboot, fastboot, CWR, etc gives me plenty of hope but after endless dead-ends it's not looking so great.
Thanks in advance for your time & any assistance you can provide!
Well it seems your problem is that cwm cannot mount in recovery. Id say your best hope is to install TWRP ( http://forum.xda-developers.com/showthread.php?t=1677447) flash the .img in fastboot then mount it with twrp to your computer. Flash the zip and voila!
Sent from my HTC One XL using xda premium
Hit the thanks button if i helped!
TheNightHawk223 said:
Well it seems your problem is that cwm cannot mount in recovery. Id say your best hope is to install TWRP ( http://forum.xda-developers.com/showthread.php?t=1677447) flash the .img in fastboot then mount it with twrp to your computer. Flash the zip and voila!
Sent from my HTC One XL using xda premium
Hit the thanks button if i helped!
Click to expand...
Click to collapse
You're a life saver man thank you so much! Friend sends his gratitude as well. I was able to easily throw TWRP on there via fastboot, mount usb storage, throw the rom on there, flash it and install. So glad it was an easy fix. :good:
Thanks again!
lasertits said:
You're a life saver man thank you so much! Friend sends his gratitude as well. I was able to easily throw TWRP on there via fastboot, mount usb storage, throw the rom on there, flash it and install. So glad it was an easy fix. :good:
Thanks again!
Click to expand...
Click to collapse
Happy to help
Sent from my HTC One X using xda premium
Tell your friend that avoiding CWM is a good idea, avoiding CWM meant for the International ONe X is an even better one. He's lucky it didn't brick.
Sorry wrong thread.
Find the right forum and stop posting in the wrong forums.
Sent from my HTC One XL
lasertits said:
You're a life saver man thank you so much! Friend sends his gratitude as well. I was able to easily throw TWRP on there via fastboot, mount usb storage, throw the rom on there, flash it and install. So glad it was an easy fix. :good:
Thanks again!
Click to expand...
Click to collapse
Hi all,
I have the same how OP described. I have formatted /system, /sdcard, /data etc by using Rom Manager Recovery (Please do not ask why ). After i reboot my devices (Samsung Galaxy Nexus), only i see is "Google" logo. I can only reboot with recovery but it didn't work.
As TheNightHawk223 described, I have tried to connect to my phone usint fastboot and adb but the commands didn't work. For example, when i write "adb devices", i can see my device but status is offline. I made a search about setting device to online but people advice to enable USB debugging. But I can't open my device and i can't enable USB debugging. So i can't copy my rom and gaps into my phone.
What can i do now? Please help. My Nexus' heartbeats are getting slower, i guess it will die :crying:
ilkay
asilazmaz said:
Hi all,
I have the same how OP described. I have formatted /system, /sdcard, /data etc by using Rom Manager Recovery (Please do not ask why ). After i reboot my devices (Samsung Galaxy Nexus), only i see is "Google" logo. I can only reboot with recovery but it didn't work.
As TheNightHawk223 described, I have tried to connect to my phone usint fastboot and adb but the commands didn't work. For example, when i write "adb devices", i can see my device but status is offline. I made a search about setting device to online but people advice to enable USB debugging. But I can't open my device and i can't enable USB debugging. So i can't copy my rom and gaps into my phone.
What can i do now? Please help. My Nexus' heartbeats are getting slower, i guess it will die :crying:
ilkay
Click to expand...
Click to collapse
you are in the wrong forum this is for the htc one x go here they will be able to help
http://forum.xda-developers.com/forumdisplay.php?f=1336
i have this problem too i try lot of recovery but no sd card show
??????????????????
maxzimos said:
i have this problem too i try lot of recovery but no sd card show
??????????????????
Click to expand...
Click to collapse
See Question 15: http://forum.xda-developers.com/showthread.php?t=2136172
hehehe !!
i had the same problem with my htc dream ! i tried to install a new os " infinite dream - android 2.3.7 " . but in she-y way , i decided to format everything on my phone !!! before my brother use to do this things and suddenly i decided to do it by my own ! and the result was my phone couldn't even mount sd card ! its a very long story ... i opened it mor than 10 times and ... at last i found 2 way for unbreak it . and friends told the 3th way !
1 . you should always have a full nandroid backup alway on your pc ! you can always use that !
2 . i formatted sd with low level format , wipe it good ! then create one partition on my sd card , fat32 .
then i copy files on sd , " mtdpartmap.txt + FR-boot-v1.5.8-CustomMTD_S.zip + FR-recovery-v1.5.8-CustomMTD_S.zip + gapps-gb-20110828-signed.zip + htc -ezgb_ZeamReplacement2_S.zip + Infinite dreams Final - 7.1.2014-update_signed_final.zip " and put sd on my phone . it usually wont mount it for a long long time ! phone off - sd on - phone on - cwm - mount sd - if it did you know what to do . but if it didn't , on partition menu - press mount - again again again - wait 5 seconds each time - not yet ? get sd out - wait - put it back - mount ... no ? just reset recovery - then do the mounting again again put sd out - put sd in - mount . after 20 minutes or so , it will mount and volla !!!!! its really challenging way !!
good luck ! you gone need it !
Why are you digging up such an old thread? It's been 18 months since the original discussion ended, plus you don't end have this device.
Sent from my Evita
NABI LAB GUI
{
"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"
}
Currently you cannot install Gapps on 2.1.27 see here http://forum.xda-developers.com/showpost.php?p=45866724&postcount=1647
I abandon this project a long time ago, as the NabiLab command line program was working with very few issues besides getting the drivers working. That program was entirely for the Nabi 2 product. As I worked on rooting the Nabi XD and compiling TWRP for it, I took a condensed version of NabiLab and made it into NabiRootXD program. I never owned the Nabi JR 4GB model(Tegra2) and never bothered creating an auto installer for it, or for TWRP for that matter. Recently I came on to the new Nabi JR 16GB(Tegra3) after rooting and creating TWRP for it I wondered if I should re-use the tried and true NabiLab. That's when I remembered my initial attempts at a VB .NET app for the Nabi2. It seemed like with 4 different Nabi projects out there it might be in at least my best interest to maintain them all in one program.
Overview
The goal was to provide a program for the current crop of Fuhu Nabi devices. It should have similar function to the stable working NabiLab commandline program but expand support to the other Nabi products. I also want the user to be able to see and or edit the commands being sent to the device without having to compile the windows app, so this program sets out to simply start the similar batch files that original NabiLab used. At this point all functionality of NabiLab isn't restored to this newer program, so in some respects NabiLab original is still a superior program. In the NabiLabGUI's corner it has the latest TWRP (2.6.0.0 as of this writing), and some common adb/fastboot commands at your finger tips. At this point we can call this ALPHA testing. Despite the NabiLab commandline roots here it is bound to have some bugs. I will put it here, and down below: using the unlock bootloader feature in NabiJR 16GB will wipe your data
You Tube video description :http://www.youtube.com/watch?v=_h7ZiWp2B7Q
-Devices
Nabi 2 (NV-7A)
Nabi JR 4GB (NV-5A)
Nabi XD (NV-10A)
Nabi JR 16GB (NV-5B)
-Functions
Install TWRP 2.6.0.0
Install stock recovery
Install root
Install Gapps(Google Play, Play Store, etc)
Perform initial backup of device
For NabiJR 16GB: unlock/lock the bootloader
Send simple/common ADB and fastboot commands
Auto updating via Microsoft ClickOnce
Installation in the start menu as NabiLab
Removal via control panel
-What it doesn't do that NabiLab original did...yet
Auto restore a device back to stock
Edit lockscreen image
Display devices stats
Prerequisites
.NET framework 3.5 (Sorry)
The program has to be initially installed in Internet Explorer(double sorry)
ADB/Fastboot drivers installed. PDAnet drivers have had the most sucess. Use the tools menu on the right side to check and see if you can control Nabi with ADB and Fastboot before starting the scripts.
Device updated to it's latest firmware. While older firmware may work it is best to be on the latest.
Download
NabiLabGUI installer You have to launch this link in Internet Explorer, there is an extension for google chrome called ClickOnce but I have had little luck getting it to work. Here is the copy and paste link if you are currently in a different browser.
Code:
http://home.comcast.net/~aicjofs/NabiLabGUI/publish.htm
Since I am just hosting this on Comcast, they don't serve the proper MIME types, you may have to toggle the "compatibility mode" button in IE. If the bar is blue on the web page it likely wont work, if it's orange it will. If you are seeing xml after clicking install you need to toggle compatibility. See the video for an example.
Usage
Main Menu
Have device on, and powered up to TWRP or Android. Launch program from start menu.
The program has tool tip enabled which you can hover the mouse over to get general information. In this screen you can issue the ADB/Fastboot commands by selecting the radio button and pressing button. The CMD prompt button will open a command window where you can issue commands within the $PATH, fastboot, and adb. On the left side you select the device you have plugged in to issue device specific auto scripts.
Deivce Menu
Root, Recovery, Gapps, Backup - This option is best used if you have a brand new Nabi. A new window will open. Follow directions, start by pressing the etner key, and don't hit enter button rapidly, be patient. Most sticking points are pressing the volume keys on the device, in the correct order and quickly enough. After its complete you should have TWRP recovery installed, a rooted Nabi, with Gapps and a backup of your unmodified Nabi in the folder TWRP/BACKUPS/YOURSERIAL/stockunrooted on your device. Not a bad idea to copy this off the Nabi to your computer if you need to free space or have it in a second location.
Gapps only - Installs Gapps only. You must first have TWRP installed.
Root only - Installs root/superuser. You must have TWRP installed.
Install TWRP x.x.x.x - Install TWRP and nothing else
Install stock recovery - Install stock for OTA, or selling, etc
Bootloader unlock(only on NabiJR 16GB) - UNLOCKING WILL DESTROY YOUR DATA. IT WILL WIPE IT CLEAN. WARNING!! WARNING Now that is out of the way....Before you do anything on the NabiJR 16GB you will have to unlock the bootloader. During the script you will need to OK the unlock on the Nabi itself. You have to be quick, the timeout is 3 to 5 seconds maybe. You will get a prompt when its unlocked. Did I mention...IT WIPES YOUR DATA!
Example of Script Window
You need to have the blinking cursor in the small white bar at bottom. The window opens this way but if you leave focus and comeback you can have the cursor in the upper grey area, and press any key won't work
Other & Links
Install location XP C:\Documents and Settings\username\Local Settings\Apps\2.0\xxx\xxx or Vista/7/8 C:\Users\username\appdata\local\apps\2.0\xxx\xxx\
Nabi JR 4GB TWRP
Nabi XD TWRP
Nabi 2 TWRP
NabiLab commandline version
Main Nabi2 thread
aicjofs said:
NABI LAB GUI
I abandon this project a long time ago, as the NabiLab command line program was working with very few issues besides getting the drivers working. That program was entirely for the Nabi 2 product. As I worked on rooting the Nabi XD and compiling TWRP for it, I took a condensed version of NabiLab and made it into NabiRootXD program. I never owned the Nabi JR 4GB model(Tegra2) and never bothered creating an auto installer for it, or for TWRP for that matter. Recently I came on to the new Nabi JR 16GB(Tegra3) after rooting and creating TWRP for it I wondered if I should re-use the tried and true NabiLab. That's when I remembered my initial attempts at a VB .NET app for the Nabi2. It seemed like with 4 different Nabi projects out there it might be in at least my best interest to maintain them all in one program.
Overview
The goal was to provide a program for the current crop of Fuhu Nabi devices. It should have similar function to the stable working NabiLab commandline program but expand support to the other Nabi products. I also want the user to be able to see and or edit the commands being sent to the device without having to compile the windows app, so this program sets out to simply start the similar batch files that original NabiLab used. At this point all functionality of NabiLab isn't restored to this newer program, so in some respects NabiLab original is still a superior program. In the NabiLabGUI's corner it has the latest TWRP (2.6.0.0 as of this writing), and some common adb/fastboot commands at your finger tips. At this point we can call this ALPHA testing. Despite the NabiLab commandline roots here it is bound to have some bugs. I will put it here, and down below: using the unlock bootloader feature in NabiJR 16GB will wipe your data
-Devices
Nabi 2 (NV-7A)
Nabi JR 4GB (NV-5A)
Nabi XD (NV-10A)
Nabi JR 16GB (NV-5B)
-Functions
Install TWRP 2.6.0.0
Install stock recovery
Install root
Install Gapps(Google Play, Play Store, etc)
Perform initial backup of device
For NabiJR 16GB: unlock/lock the bootloader
Send simple/common ADB and fastboot commands
Auto updating via Microsoft ClickOnce
Installation in the start menu as NabiLab
Removal via control panel
-What it doesn't do that NabiLab original did...yet
Auto restore a device back to stock
Edit lockscreen image
Display devices stats
Prerequisites
.NET framework 3.5 (Sorry)
The program has to be initially installed in Internet Explorer(double sorry)
ADB/Fastboot drivers installed
Device updated to it's latest firmware. While older firmware may work it is best to be on the latest.
Download
NabiLabGUI installer You have to launch this link in Internet Explorer, there is an extension for google chrome called ClickOnce but I have had little luck getting it to work.
Usage
Main Menu
Have device on, and powered up to TWRP or Android. Launch program from start menu.
The program has tool tip enabled which you can hover the mouse over to get general information. In this screen you can issue the ADB/Fastboot commands by selecting the radio button and pressing button. The CMD prompt button will open a command window where you can issue commands within the $PATH, fastboot, and adb. On the left side you select the device you have plugged in to issue device specific auto scripts.
Deivce Menu
Root, Recovery, Gapps, Backup - This option is best used if you have a brand new Nabi. A new window will open. Follow directions, start by pressing the etner key, and don't hit enter button rapidly, be patient. Most sticking points are pressing the volume keys on the device, in the correct order and quickly enough. After its complete you should have TWRP recovery installed, a rooted Nabi, with Gapps and a backup of your unmodified Nabi in the folder TWRP/BACKUPS/YOURSERIAL/stockunrooted on your device. Not a bad idea to copy this off the Nabi to your computer if you need to free space or have it in a second location.
Gapps only - Installs Gapps only. You must first have TWRP installed.
Root only - Installs root/superuser. You must have TWRP installed.
Install TWRP x.x.x.x - Install TWRP and nothing else
Install stock recovery - Install stock for OTA, or selling, etc
Bootloader unlock(only on NabiJR 16GB) - UNLOCKING WILL DESTROY YOUR DATA. IT WILL WIPE IT CLEAN. WARNING!! WARNING Now that is out of the way....Before you do anything on the NabiJR 16GB you will have to unlock the bootloader. During the script you will need to OK the unlock on the Nabi itself. You have to be quick, the timeout is 3 to 5 seconds maybe. You will get a prompt when its unlocked. Did I mention...IT WIPES YOUR DATA!
Example of Script Window
You need to have the blinking cursor in the small white bar at bottom. The window opens this way but if you leave focus and comeback you can have the cursor in the upper grey area, and press any key won't work
Other & Links
Install location XP C:\Documents and Settings\username\Local Settings\Apps\2.0\xxx\xxx or Vista/7/8 C:\Users\username\appdata\local\apps\2.0\xxx\xxx\
Nabi JR 4GB TWRP
Nabi XD TWRP
Nabi 2 TWRP
NabiLab commandline version
Main Nabi2 thread
Click to expand...
Click to collapse
going to give this a whirl on my daughters now
:good:
So no way to root and install gapps on the 16gb nabiJR without unlocking the bootloader and installing the custom recovery?
Sent from my Xperia Tablet Z
Spectre51 said:
So no way to root and install gapps on the 16gb nabiJR without unlocking the bootloader and installing the custom recovery?
Sent from my Xperia Tablet Z
Click to expand...
Click to collapse
I have not tried it, but in theory you could use motochooper root method. Then manually transfer su, superuser.apk, set permissions, then install gapps manually. No need to unlock bootloader, of course without doing it you have no recovery to fall back upon.
Just used this on both my Nabi Jr 4GB and Nabi2, worked wonderfully! A couple bugs that cause software crash, but nothing that restarting it back up didn't hurt. I think the scripting for the all-at-once Recovery/Backup/Root/GApps needs some work, as they both got hung up for me on each one...so I just did each step individually.
Also, I downloaded it using Chrome and installed it from that way as well, and it worked just fine...and I didn't have to use any extension
Thank you very much!!!
I'm looking to do my nephews nabo but I don't know what nabi it is. The model number on the back is Nabi-A. If anyone could enlighten me that would be great. I just don't want the kid mode on there. He doesn't use it anymore so my mom is going to use the Nabi so I would like to get as close to a normal android tablet as possible (custom Rom, Google play store, etc) Thanks ahead of time for any help.
Sent from my HTC6435LVW using xda app-developers app
djeleet said:
I'm looking to do my nephews nabo but I don't know what nabi it is. The model number on the back is Nabi-A. If anyone could enlighten me that would be great. I just don't want the kid mode on there. He doesn't use it anymore so my mom is going to use the Nabi so I would like to get as close to a normal android tablet as possible (custom Rom, Google play store, etc) Thanks ahead of time for any help.
Sent from my HTC6435LVW using xda app-developers app
Click to expand...
Click to collapse
Nabi-A is the original Nabi, this program doesn't support it. I haven't followed much about that tablet. It is rootable, you could at least remove some of the kids programs. I doubt there is a custom ROM.
I have nabi Jr 16 gb, to install twrp then need to unlock boatloader. If I do that then I Will lose that, does that all apps as well provided by Fuhu?
Sent from my Amazon Kindle Fire using Tapatalk
---------- Post added at 05:44 PM ---------- Previous post was at 05:43 PM ----------
ipskang said:
I have nabi Jr 16 gb, to install twrp then I need to unlock boatloader. If I do that then I Will lose data, does that all apps as well provided by Fuhu?
Sent from my Amazon Kindle Fire using Tapatalk
Click to expand...
Click to collapse
Sent from my Amazon Kindle Fire using Tapatalk
ipskang said:
I have nabi Jr 16 gb, to install twrp then need to unlock boatloader. If I do that then I Will lose that, does that all apps as well provided by Fuhu?
Sent from my Amazon Kindle Fire using Tapatalk
---------- Post added at 05:44 PM ---------- Previous post was at 05:43 PM ----------
Sent from my Amazon Kindle Fire using Tapatalk
Click to expand...
Click to collapse
You just loose everything on internal SD(data/media), and all saved settings, games, etc. Everything you put on the device. After a reboot the device will put all your apps back from the backup on the addon partition. Basically it is a factory reset.
In your first post, its mentioned that gapps cannot be installed on 2.1.27 but I have product version 1 of Nabi Jr 16gb nick edition . Can I install gapps ? How do i check system memory?
Sent from my Amazon Kindle Fire using Tapatalk
I used the nabilab tool and did the all in one step. Everything went through.but the touch feature in TWRP is not working. I found another version that says it fixes this problem but don't know how to flash it with TWRP not working. Can anyone help?
marcran75 said:
I used the nabilab tool and did the all in one step. Everything went through.but the touch feature in TWRP is not working. I found another version that says it fixes this problem but don't know how to flash it with TWRP not working. Can anyone help?
Click to expand...
Click to collapse
not sure what nabi you have here--
http://forum.xda-developers.com/showthread.php?t=2074501&highlight=nabi
I use for all my nabis- POST 1
Test method 2 for temp install
I put the Recovery I want to install in the same folder the adb files are in.
once you figured out that its the recovery you want use method 3 to make it stick.
HTH
Stock ROm 1.03
Can anyone send me a stock rom 1.03 please, I desperately need it.
DeathMetalSquad8790 said:
Can anyone send me a stock rom 1.03 please, I desperately need it.
Click to expand...
Click to collapse
what problems are you having updating?
mjw2k11 said:
what problems are you having updating?
Click to expand...
Click to collapse
Well i got TWRP flashed however accidentally wiped rom without backup. So i have a flashed recovery with no Android OS to boot into. I just need the stock rom so i can flash it back and boot into Android, then im gonna finish rooting.
DeathMetalSquad8790 said:
Well i got TWRP flashed however accidentally wiped rom without backup. So i have a flashed recovery with no Android OS to boot into. I just need the stock rom so i can flash it back and boot into Android, then im gonna finish rooting.
Click to expand...
Click to collapse
best thing to do is follow the tutorials on here, use the nabi lab full, it contains stock rom, should be easy enough,and then just use OTA until you get to JB, most files are available here - http://forum.xda-developers.com/wiki/Fuhu_nabi_2let us know where you get stuck!
mjw2k11 said:
best thing to do is follow the tutorials on here, use the nabi lab full, it contains stock rom, should be easy enough,and then just use OTA until you get to JB, most files are available here - http://forum.xda-developers.com/wiki/Fuhu_nabi_2let us know where you get stuck!
Click to expand...
Click to collapse
Just a note that at this time of post the wiki link only has NAbi 2 content
DeathMetalSquad8790 said:
Can anyone send me a stock rom 1.03 please, I desperately need it.
Click to expand...
Click to collapse
I can't remember all the numbers which is that for the Nabi JR 4GB? JR 16GB? Something else?
I'm having the following issue when using NabiLab to back up
# Pushing gapps and root to your device
# Ignore external SD card error if you have none installed
# This will take a few minutes. Wait.
mount: mounting /system on ext4 failed: No such file or directory
mount: mounting /cache on ext4 failed: No such file or directory
mount: mounting /data on ext4 failed: No such file or directory
mount: mounting /addon on ext4 failed: No such file or directory
any help?
have you got the nabi installed and connected correctly? what are using to push gapps and root? if your on JB now (Nabi 2.3) then the filing structure is different and nabi lab wont work
Irish Cream said:
I'm having the following issue when using NabiLab to back up
# Pushing gapps and root to your device
# Ignore external SD card error if you have none installed
# This will take a few minutes. Wait.
mount: mounting /system on ext4 failed: No such file or directory
mount: mounting /cache on ext4 failed: No such file or directory
mount: mounting /data on ext4 failed: No such file or directory
mount: mounting /addon on ext4 failed: No such file or directory
any help?
Click to expand...
Click to collapse
I'm still new to this and need to know on how to install and access the debloater which is coming from this thread http://forum.xda-developers.com/showthread.php?t=2229079
also I got lagging issues with my phone. cheers.
NOTE: I already rooted and install CWM in my phone.
sambagdos said:
I'm still new to this and need to know on how to install and access the debloater which is coming from this thread http://forum.xda-developers.com/showthread.php?t=2229079
also I got lagging issues with my phone. cheers.
NOTE: I already rooted and install CWM in my phone.
Click to expand...
Click to collapse
Procedure:
1. Place the Unofficial Stock rom on your sd card.
2. Enter CWM recovery by holding vol.down+power button during power off, release only when the "BURST" image appear.
(NOTE: If you don't have CWM yet go HERE.)
3. Wipe Data. (Important!)
4. Install the ROM from SD card.
5. Install RootStock for Root Access. (Optional)
6. Reboot and Enjoy Stock Rom.
Click to expand...
Click to collapse
First, you should be asking this question in same thread. it's easy and author is answering questions there.
Instructions are not difficult to follow. as you already have rooted and installed CWM. now you need to follow instructions how to install Custom ROM.
in simple, this procedure is to install Custom ROM.
1. Place the Unofficial Stock rom on your sd card.
-- download ROM and copy it to SD card.
2. Enter CWM recovery by holding vol.down+power button during power off, release only when the "BURST" image appear. (NOTE: If you don't have CWM yet go HERE.)
-- According to you, it's already done. so, just follow instructions to enter CWM.
3. Wipe Data. (Important!)
-- In CWM, there is option to wipe Data. do it.
4. Install the ROM from SD card.
-- Now, here you'll choose "Custom ROM" file you downloaded and copied to sd card. There is options “install zip from SD card” and then “choose zip from SD card”.
5. Install RootStock for Root Access. (Optional)
-- This is Optional and i'm not sure about it's purpose. so, skip this too for now.
6. Reboot and Enjoy Stock Rom.
-- i believe, when ROM installation will be done. it will show some message or so, that's all. "6. Reboot and Enjoy Stock Rom."
Originally Posted by xylu View Post
---------- Post added at 11:00 PM ---------- Previous post was at 10:53 PM ----------
[/COLOR]sir what does debloater do?
annson08 replied: debloater simply removes bloatwares, apps that isn't really needed to get your phone to function well.
Click to expand...
Click to collapse
About debloater and RootStock for Root Access, i think they can be installed/flashed after ROM installation. That's all.
better ask same questions or copy this material to that thread to confirm what i understood and answered. make sure before you do anything. i have done such steps for other device than yours. but according to those instructions, i answered what i understood.
hope, it helped in understanding..
ajnabicancer said:
3. Wipe Data. (Important!)
-- In CWM, there is option to wipe Data. do it.
.
Click to expand...
Click to collapse
Should I back up first my current phone settings before selecting the Wipe Data? I can see in the CWM the option to back up and restore. Just want to make sure that none of my settings including my apps will get lost. Thank you.
sambagdos said:
Should I back up first my current phone settings before selecting the Wipe Data? I can see in the CWM the option to back up and restore. Just want to make sure that none of my settings including my apps will get lost. Thank you.
Click to expand...
Click to collapse
Yes, that is most important step. Make full backup and also save it on computer.
ajnabicancer said:
Yes, that is most important step. Make full backup and also save it on computer.
Click to expand...
Click to collapse
Honestly I really don't know what's the easiest way to back up my phone. Is the back up option in CWM is enough? Please enlighten me and sorry for asking another question. Thanks in advance.
sambagdos said:
Honestly I really don't know what's the easiest way to back up my phone. Is the back up option in CWM is enough? Please enlighten me and sorry for asking another question. Thanks in advance.
Click to expand...
Click to collapse
It's ok, no problem. well, i really can't say much about your device type. there are tools to make backup of ROM other than CWM. For myself, i took backup with CWM and after flashing ROM i can restore back to last ROM with CWM backup. i also made backup with one other tool "SPflash tool" and it take full ROM/firmware backup. I'm not an expert, so not sure about difference between CWM backup or SPflash tools backup. but i made both.
according to my information, "SPflash tool" is for MTK chipset phone type. i don't know about your phone. i'll try to search on it. will try to update in case i'll find something.
Yes, for your other question about backing up other than CWM. it's always good to make better backup.
---------- Post added at 08:33 AM ---------- Previous post was at 08:02 AM ----------
i tried to search little about your device and i didn't find much but on other hand, i can tell what i can do with CWM and it's Backup in short. i can restore back to stock ROM with CWM backup after installing Custom ROM. i didn't find about tools for your device. I think CWM is fine.
just do little search on CWM, don't be confused with my replies. for me, i'm satisfied with CWM backup coz i can restore back to stock anytime i change ROM. hope it helped.
successfully installed the ROM however found an error when trying to restore the back up that I've made using CWM. Perhaps it's my fault since I back up twice using CWM and deleted the 1st back up. Maybe the 1st one is part of the 2nd one and when I choose to restore then it prompts the MD5 error.
Now all my installed apps were gone
sambagdos said:
successfully installed the ROM however found an error when trying to restore the back up that I've made using CWM. Perhaps it's my fault since I back up twice using CWM and deleted the 1st back up. Maybe the 1st one is part of the 2nd one and when I choose to restore then it prompts the MD5 error.
Now all my installed apps were gone
Click to expand...
Click to collapse
Problem of md5 mismatch, don’t worry this problem can be fixed, so don’t delete that backup.
As you mentioned that you have created backup twice, it means that those were two different backups. I hope you didn't deleted other backup. keep it safe. Reminder: keep backup in your computer too.
are you getting error like this? MD5 Mismatch !!!!
{
"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"
}
Again, don't worry and don't delete backup which is giving error. there are easy solutions for this. hope it works for you. read carefully instructions/guide from the link. check this link. in case you don't understand something, you are welcome. : )
Method 1 LINK: [Trick][Noob Friendly]How to fix md5 sum mismatch error in CWM easy n quick!!
Here, i'll try to make is short and easy for you. (but read, instructions from link too for more and better understanding.)
-- Remember, always save backup on your computer or other media.
1. Open File Explorer & navigate to clockworkmod backup folder you created on SDcard. There is file "nandroid.md5". Backup/save this file & then Delete it. Create New File & name is same as "nandroid.md5"(without quotes & no capital letter).
-- Do not edit new created file or any other file/folder.
Now try to restore the backup again. hopefully it will work fine.
(In case above method don't work, proceed to second method.)
Method 2:
Method from below link is Via "ADB". (Hope, you know it. Read carefully and then follow instructions, even they are not much complicated but always make sure you understand well before doing anything.)
LINK: FIX – How to recover from MD5 mismatch – CWM Backup / Nandroid Backup
In simple and short:
Remember, always save backup on your computer or other media.
-- Make sure you have Phone drivers installed.
-- you will need ADB Tools to run those commands.
-- Enable Developer option. (in case needed, i think it's necessary)
Now to commands:
Boot the device (Connect the device – via adb , not in media storage mode) and do the following in CMD / Terminal
Note: (Make sure when you open command prompt, path should be the folder of ADB tool files)
Ex:- our path is "C:\adb>".
Now here we'll enter commands (Do not use "#" in commands.):-
Code:
adb shell
# cd /sdcard/clockworkmod/backup/2012-10-10.20.22.53
(Here 2012-10-10.20.22.53 is timestamp at which backup was generated, yours might be different! )
# rm nandroid.md5
# md5sum *img > nandroid.md5
info about commands:-
This command is to change directory/path to SDcard containing backup files.
# cd /sdcard/clockworkmod/backup/2012-10-10.20.22.53
This command will remove old nandroid.md5 file.
# rm nandroid.md5
this command will generate new md5sum file with same name as the old one.
# md5sum *img > nandroid.md5
Hope it work for you & never panic or give up.
I can see my SDcard in Recovery and I can copy stuff off via MTP from recovery...
But after I ran Fix Permissions I rebooted. The system hung on the boot animation so I force power off.
I figured the permissions got screwed up for some reason so I decided to just reflash the system.img from fastboot.
So, I did that and rebooted.
On boot it didn't hang but it acted like I was setting up a brand new phone. I finally got to the desktop and while all my apps are installed still, everything is missing. I can't see anything on the sdcard and stuff seems generally screwed up. If I go in to the settings and look at storage it still showes I have 20-something gb's used up.
Ugh... I don't know what to do... sort of panic'ing right now.
Anyone got any ideas?
edit: something is royally hosed up. Even if I boot up in and go to es file explorer and try and create a new folder on my new "blank" sdcard space it gives a failed to create folder error. I think the fix permissions option royally screwed things up. Not sure if there is any coming back from this one
Read the /sdcard sticky in general
Thanks rootSU.
Yeah, something is definitely funky between current recoveries and Lollipop.
What I found out last night:
-I cut my losses and decided to hard wipe everything. I was able to DOWNLOAD files off my phone from TWRP 2.8.1.0
-I wiped, reflashed, got the half storage issue, flashed stock recovery, factory reset, all better
-Booted Lollipop, signed in, it autoinstalled my ~130 apps (this took a long time)
-I still had all my "sdcard" files I'd downloaded. My phone wasn't recognizing in windows mtp while booted in Lollipop so I decided to copy files BACK over in TWRP
-Copied over my 16gb worth of files in TWRP (this took a very long time). Once copied over it looked good in recovery and windows mtp
-Rebooted back in to Lollipop
-All of the files I had copied over in Recovery to my phone were unreadable. Folders were showing up as "?" icons in ES File Explorer. So, all that time I'd spent copying files over from recovery was ****.
-Went back to recovery, could see files again in TWRP. Since Lollipop couldn't read them, I decided I had to just delete them from recovery and just copy them over WIFI
-Deleted in recovery, booted back to Lollipop, copied over via wifi (took >2 hours to copy over wifi)
So... in summary, TWRP + Lollipop are definitely NOT playing nice together.
It was DEFINITELY the "Fix Permission" function that totally screwed me.
And the kicker...
I was running it because on every boot I'd see the "Android is Upgrading" message flash up for a couple seconds. I googled it and someone had recommended the fix permission function.
And it's still doing it now. I now believe it is caused by the current root method from chainfire and will have to live with it until it is fixed I guess.
Sigh.... what an incredibly long night.
And just discovered that the current TWRP folder on my phone is in this messed up state.
TWRP created this folder and it can only be viewed in recovery.
Even a root shell can't get in to it from ADB in Lollipop:
Code:
[email protected]:/sdcard # cd TWRP
cd TWRP
tmp-mksh: cd: /sdcard/TWRP: Permission denied
{
"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"
}
Yeah, I also have problems. Due to habit, I used "Fix Permissions" in TWRP - caused bootloop. Luckily i had just made a TWRP Backup, so I wiped the phone and restore it - worked fine again.
Guess I have to stay away from the feature until a fix.
I rooted my n5 lollipop.... But some rooted apps fail to get root access...like es file manager (root exp)...xmodgames...etc
In es it says failed test...and xmod shows device is not rooted
Sent from my Nexus 5 using XDA Free mobile app
Redux90 said:
Yeah, I also have problems. Due to habit, I used "Fix Permissions" in TWRP - caused bootloop. Luckily i had just made a TWRP Backup, so I wiped the phone and restore it - worked fine again.
Guess I have to stay away from the feature until a fix.
Click to expand...
Click to collapse
Yup, something is broken. I found out the hard way
myliferockkss said:
I rooted my n5 lollipop.... But some rooted apps fail to get root access...like es file manager (root exp)...xmodgames...etc
In es it says failed test...and xmod shows device is not rooted
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
This is completely unrelated to the topic of this thread. It's a known issue. Apps need to update how they're calling su.
GldRush98 said:
Yup, something is broken. I found out the hard way
This is completely unrelated to the topic of this thread. It's a known issue. Apps need to update how they're calling su.
Click to expand...
Click to collapse
Okay sorry boss *noob here*
Sent from my Nexus 5 using XDA Free mobile app
I too am in the same boat, I was able to restore to a previous backup but there are issues with some apps and my storage is messed up.
GldRush98 - I was a bit confused by your post, may you please clarify
I am thinking of copying my files over to me desktop via MTP in windows. Wiping and re-flashing. Then, I plan on copying over the files - Is this what gave you issues? or was it just the TWRP folder.
or would this idea work: Wipe, re-flash then restore a backup (before i fixed permissions)?
Thank you for your input
manny.m said:
I too am in the same boat, I was able to restore to a previous backup but there are issues with some apps and my storage is messed up.
GldRush98 - I was a bit confused by your post, may you please clarify
I am thinking of copying my files over to me desktop via MTP in windows. Wiping and re-flashing. Then, I plan on copying over the files - Is this what gave you issues? or was it just the TWRP folder.
or would this idea work: Wipe, re-flash then restore a backup (before i fixed permissions)?
Thank you for your input
Click to expand...
Click to collapse
If you copy files back in android it should be fine. Don't use adb or TWRP MTP. See my first post
Thank you for the quick response! I have been away from these forums for a while now and I'm not able to located the said sticky under General. One more question, besides abd or TWRP MTP what other options would I have?
Thanks again!!
rootSU said:
If you copy files back in android it should be fine. Don't use adb or TWRP MTP. See my first post
Click to expand...
Click to collapse
Yup, this is correct.
In my haste I totally misread rootSU's post. I got all my stuff out with Windows MTP, flashed the factory images and now I'm good!
Thanks again!
Same issue on nexus4.
I wasn't able to create a file/folder on the phone.
Tried fix permission and bootloop happened.
I don't want to re-wipe everything, maybe a only rom flash from twrp will help me?
mcgyver83 said:
Same issue on nexus4.
I wasn't able to create a file/folder on the phone.
Tried fix permission and bootloop happened.
I don't want to re-wipe everything, maybe a only rom flash from twrp will help me?
Click to expand...
Click to collapse
You can try the restorecon command from a terminal if you can get back in to Android.
Code:
su
restorecon -FR /data/media/0
reboot
I've seen others post that it is a potential fix.
Thank you man,I flashaed again the stock rom with data wipe.
I lost all my files but now all is working.
Many thanks
Hi guys, I have the same problem. Is there a solution to fix it, with full wipe? I can use just Odin because I can't get anywhere in the phone. I'm now trying stock room so hopefully it will work. If someone know the correct way to get working phone again let me know.
Thanks
Hello Everyone,
I fell victim to this issue and am a total noob when it comes to this. I was actually trying to remove the root and flash back to the stock software and accidentally ran the fix permissions expecting it to fix an issue that was arising. I have a ROM to restore but TWRP wont pick it up and I cannot seem to locate the proper directory folder. I already backed up all my data previously to starting and am ok with wiping everything but pretty much at this point I am at a loss.
If someone could help me out my email is [email protected]
I know it too late for you, but that is one feature I stay well away from. Never use it if you are reading this. Took me days to sort my phone out.
This is a thread for the rooting and install of TWRP for the Uefone Power 3
Code:
/*
* 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 included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/
TWRP 3.2.1-0: https://drive.google.com/file/d/1cLqcDrun5f6h1BHjUFfXDdlhwEWwM-49/view?usp=sharing
SuperSU: https://drive.google.com/file/d/1sZwahrodGJmYWzaIohxEETeIAabCOPfb/view?usp=sharing
Steps to install TWRP and SuperSU
Copy the above SuperSU to your SDCard.
First of all, you will be required to unlock your bootloader.
There is an option for this under Developer Options in the settings menu. Activate this.
Also activate USB Debugging. This makes this a whole lot easier.
Now, open a terminal, if on Linux, or command prompt if on windows, and enter the following:
Code:
adb reboot bootloader
Code:
fasboot oem unlock
Follow the onscreen instructions to unloack your bootloader. THIS WILL WIPE YOUR DEVICE!!!
Once this is complete, it will go back to the fastboot screen.
Now, from within your terminal/command prompt, navigate to the folder where you have downloaded the above recovery.img to.
Enter the following command once there:
Code:
fastboot flash recovery recovery.img
This will flash TWRP to your device, overwriting the stock recovery.
Once this is complete, there will be a screen telling you how long it took etc. Now you need to hold down your volume up button, and power button. Keep holding these untill you reach the menu for recovery, fastboot or normal mode.
Select Recovery.
This will boot into TWRP for the first time. when you get there, you will be prompted with a screen asking for a password. Cancel this.
WHAT EVER YOU DO, DO NOT FORMAT DATA LIKE IT ASKS YOU!"" YOU WILL LOSE TWRP!!!
Your then presented with the main TWRP screen, go ahead and tap on Install. Next, hit Select Storage, and select Storage 1. This is your SDCard.
Now flash SuperSU.
When this is installed, reboot to your main system, and update the SuperSu binary.
Now proceed to reboot back to recovery, how ever you wish.
Once in recovery, go into Wipe, and hit Format Data, this will wipe your phone again, but youve just done this anyway so it doesnt matter
Now flash SuperSU again, just to be safe, the same way as above.
Reboot to your system, and your done!
You will have to go through the setup of the whole android system again, but its worth it your now rooted and have TWRP to install the Custom ROMs that will be coming shortly
Have Fun!
Reserved
wow, that was quick thank you
will try it now and update as soon as it's done!
alright, so i tried to flash super su, but i never get to access the storage partitions (i think they are not mounted).
so i tried to factory reset / wipe the phone to get rid of the encryption, but i still cant select storage 1 from the menu.
here some more detail:
- i have already had the bootloader unlocked
{
"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"
}
- then i come to this screen when twrp starts, and select "swipe to allow modifications"
- then i press install and want to select "storage 1", this however doesnt work. (due to encryption?)
- i tried to mount it, but cant even mark it active. just gets gray for half a second and then nothing
- tried to do a wipe via twrp as well, with no success
any ideas?
tbst1337 said:
alright, so i tried to flash super su, but i never get to access the storage partitions (i think they are not mounted).
so i tried to factory reset / wipe the phone to get rid of the encryption, but i still cant select storage 1 from the menu.
here some more detail:
- i have already had the bootloader unlocked
- then i come to this screen when twrp starts, and select "swipe to allow modifications"
- then i press install and want to select "storage 1", this however doesnt work. (due to encryption?)
- i tried to mount it, but cant even mark it active. just gets gray for half a second and then nothing
- tried to do a wipe via twrp as well, with no success
any ideas?
Click to expand...
Click to collapse
Your third screenshot - what's the last option, under Microsd?
Also, when going through install, can u see "external SD"?
ukhellfire666 said:
Your third screenshot - what's the last option, under Microsd?
Also, when going through install, can u see "external SD"?
Click to expand...
Click to collapse
the last one is USB OTG, also showing 0MB - i actually tried flashing supersu through the usb as well, with no luck
i can see external_sd but there dont seem do be ANY contents
do you think it is the encryption? because everything shows 0MB in brackets
EDIT:
i just thought what the hell i try again to flash it via usb. havent changed anything but suddenly SUCCESS
appreciate your time thanks
tbst1337 said:
the last one is USB OTG, also showing 0MB - i actually tried flashing supersu through the usb as well, with no luck
i can see external_sd but there dont seem do be ANY contents
do you think it is the encryption? because everything shows 0MB in brackets
EDIT:
i just thought what the hell i try again to flash it via usb. havent changed anything but suddenly SUCCESS
appreciate your time thanks
Click to expand...
Click to collapse
So what did you do differently? If you can explain a bit more, I'll change/add it to the guide. Maybe as a second option or something...?
ukhellfire666 said:
So what did you do differently? If you can explain a bit more, I'll change/add it to the guide. Maybe as a second option or something...?
Click to expand...
Click to collapse
i just booted again into twrp and suddenly my 4gb usb was showing up as the only thing not 0mb, so the usb otg partition was mounted. from there on i just pressed install and located the zip file on the usb drive. had some errors. below some pics i took with my old phone:
tbst1337 said:
i just booted again into twrp and suddenly my 4gb usb was showing up as the only thing not 0mb, so the usb otg partition was mounted. from there on i just pressed install and located the zip file on the usb drive. had some errors. below some pics i took with my old phone:
Click to expand...
Click to collapse
Ahhh brilliant! I don't suppose u found that he sdcard was mounted too did you?
Have the errors gone now your rooted? The rest of the guide should still count...?
ukhellfire666 said:
Ahhh brilliant! I don't suppose u found that he sdcard was mounted too did you?
Have the errors gone now your rooted? The rest of the guide should still count...?
Click to expand...
Click to collapse
yes i am indeed rooted!
everything else, including internal storage was 0mb as well. usb otg was literally the only one.
i have not gone back into recovery since, but rebooted several times and also used root apps (adaway). everything seems to work great and the rest of the guide still counts!
in total, everything seems stable until now :good: my goal is to not touch twrp anymore until android 8.1 will be released
tbst1337 said:
yes i am indeed rooted!
everything else, including internal storage was 0mb as well. usb otg was literally the only one.
i have not gone back into recovery since, but rebooted several times and also used root apps (adaway). everything seems to work great and the rest of the guide still counts!
in total, everything seems stable until now :good: my goal is to not touch twrp anymore until android 8.1 will be released
Click to expand...
Click to collapse
The official 8.1 update with overwrite TWRP.
I am now working on a cm14.1 build. As im having to use a prebuikt kernel, this is as far as I can go.
As soon as I have a beta ROM I'll upload.
Don't suppose you could boot to recovery and just double check that everything is as it should be? Put my mind at ease, make sure it works for you, as it does for me...
ukhellfire666 said:
The official 8.1 update with overwrite TWRP.
I am now working on a cm14.1 build. As im having to use a prebuikt kernel, this is as far as I can go.
As soon as I have a beta ROM I'll upload.
Don't suppose you could boot to recovery and just double check that everything is as it should be? Put my mind at ease, make sure it works for you, as it does for me...
Click to expand...
Click to collapse
sure man, maybe joining me on discord would make this process faster https://discord.gg/jPZqn4
Hi.
Thank you for twrp.
I am trying to use SuperSu with SuHide, i wipe data with this twrp to be able to install supersu in BINDSBIN mode to /data but data partition stay unencrypted to be mountable with thw twrp.
How to encrypt it back with own known password keeping supersu and suhide working?
TWRP has no option to reformat with password, no way to get origin password for stock recovery formated partition.
Any idea?
MioCZ said:
Hi.
Thank you for twrp.
I am trying to use SuperSu with SuHide, if i wipe data with this twrp to be able to install in BINDSBIN mode to /data but data partition stay unencrypted.
How to encrypt it back with keep supersu and suhide working?
TWRP has no option to reformat with password, no way to get origin password for stock recovery formated partition.
Any idea?
Click to expand...
Click to collapse
No idea I'm afraid. Sorry.
I used encryption in system Setup, i works, but with unknown password stored somewhere in nvdata partition. I am worry about loose root after OTA update and without pasword for twrp no way to get again to data partition.
I'm thinking of buying this phone. It's great to see that root already seems to work and that there might be a CM/LineageOS Rom soon. Root and custom recovery is crucial so one reason less to not buy it.
Are you guys happy with it in general? Does the dual camera work with bokeh and shoot good photos with low lag required to capture playing kids? Good value?
I can not install Snap Chat
Thank you ukhellfire666
The recovery was successfully installed
My question:
is there any idea to fully remove superSu to install snapchat
A full system backup has been taken.
DaF1974 said:
I'm thinking of buying this phone. It's great to see that root already seems to work and that there might be a CM/LineageOS Rom soon. Root and custom recovery is crucial so one reason less to not buy it.
Are you guys happy with it in general? Does the dual camera work with bokeh and shoot good photos with low lag required to capture playing kids? Good value?
Click to expand...
Click to collapse
good day to you.
in general i am happy with it, but the camera really blows. it is - without a doubt - the worst camera i had since my LG VX-5200. iphone 6s and galaxy s6 have way better cameras.
i am really frustrated, because they advertised the 4 cameras ..." " heavily, but they really suck. maybe it's just with the stock app and another app would make it better (but somehow i doubt that)
tomorrow i will go on holiday and was stoked that the phone arrived before, so i could take it with me to take pictures etc. seems like i will need to get the old digital camera out....
alshyib said:
Thank you ukhellfire666
The recovery was successfully installed
My question:
is there any idea to fully remove superSu to install snapchat
A full system backup has been taken.
Click to expand...
Click to collapse
Is possible to flash un-supersu package. Is somewhere in SuperSu topic. Or you can flash clean ROM / your backups (boot.img, recoovery.img, system.img).
Because this i have used supersu in BINDSBIN mode and suhide. So i have hiden su, locked bootloader, working OTA and all root sensitive apps.
bootloop
Hello, I followed the instructions but my phone bootloop on twrp, it does not start the system can you help me please?
---------- Post added at 02:23 AM ---------- Previous post was at 02:21 AM ----------
Hello, I followed the instructions but my phone bootloop on twrp, it does not start the system can you help me please?