Related
Hello guys.
I know there's no way to make CWM work with encrypted memory and SD and also there's no way to decrypt.
So, any other encryption solution that allows backups?
Using android's encryption feature, what to do in case of problems?
Any way to recover?
What happens if the system bricks and a recovery is needed?
What happens flashing a non disruptive update? Is a wipe needed?
Thank you so much!
Flashing to an encrypted ICS gs2/i9100
ultradj83 said:
Hello guys.
I know there's no way to make CWM work with encrypted memory and SD and also there's no way to decrypt.
So, any other encryption solution that allows backups?
Using android's encryption feature, what to do in case of problems?
Any way to recover?
What happens if the system bricks and a recovery is needed?
What happens flashing a non disruptive update? Is a wipe needed?
Thank you so much!
Click to expand...
Click to collapse
There are two options I've found that will work for flashing encrypted ICS, one is TWRP, which you would use instead of CWM, which would allow you to enter your password & flash what ever ROM you wanted like you were working with an unencrypted phone. But it's not (yet?) available for gs2/i9100.
The other option (original post here ) outlines how to do this from the command line of a computer with the Android SDK installed. I've spelled it out to include Android SDK installation since I didn't have that installed already when I had to do this.
Download, Install & configure Android SDK
Run SDK Manager
install "Android SDK Platform-tools"
Add <whatever>/android-sdk/platform-tools/ to path
in a command prompt / terminal window type "abd" to Check that your path includes the correct folders in the SDK (I had to do this manually on Win7)
On Phone
Reboot phone into Recovery mode
in CWM format cache partition
from your PC use adb to mount /sdcard as tmpfs:
Code:
adb shell mount -t tmpfs none /sdcard
put your ROM on the (fake) sdcard
Code:
adb push <your rom> /sdcard
Use the recovery to flesh the ROM as usual
Once you reboot the device will ask for you password as normal then finish the app installation/configuration after reboot. I was able to do this upgrading from CM9.0.0 RC1 to CM9.1. All data was preserved. Phone seems to be behaving itself but I only did this an hour ago so still too soon to tell.
Props to orcruin for sharing this. :highfive:
Ed
Hi all,
Well, this is my point*: I have got a rooted and unlocked TF201 running Asus FW build US_epad-9.4.2.28. I'd like to switch to CyanogenMod and I therefore installed ClocworkMod 5.8.3.4 using ADB.
I have got an issue trying to wipe data and perform the factory reset 'cause CWM can not mount /data. I tried mounting by hand, using both advanced CWM tools and ADB command lines but without any success so far.
I guess it is because my personal data are encrypted (I did it using the Asus inbuilt tool). And /data folder is not available (=decrypted and mounted by the system) before I input my secret pass. Am I right ?
I also tried to install Cyano using Rom Manager, ROM toolbox or others GUI without any success (same thing happens : personal data are not wiped out) and install failed.
I looked for solutions on XDA forums and googled for quite a long time now without finding a solution (but I may have miss looking). Any help would be welcome.
Try using newest TWRP, maybe it could help - there are many problems with CWM on Prime. Don't forget to install version for ICS bootloader(as you are runnign ICS rom)
Sent from my Transformer Prime TF201 using Tapatalk HD
qery said:
Try using newest TWRP, maybe it could help - there are many problems with CWM on Prime. Don't forget to install version for ICS bootloader(as you are runnign ICS rom)
Sent from my Transformer Prime TF201 using Tapatalk HD
Click to expand...
Click to collapse
That is correct. I just did this last night. TWRP will let you wipe encrypted data.
Thanks for the tip. I'll have a try and let you know results
Well, it's a bit more complicated than expected...
Running CWM v 5.8.3.4, I'm able to start on recovery mode (hopefuly...) but there is absolutely no way to get a correct fastboot connection!!!
I end up with a "connection refused" message (My ADB settings are corrects as I am abble to "play" with my TF201, once up and runing). I am therefore unable to install NVFlash, TWRP or any other tool :-/
I guess my only chance left is to follow the below instructions from TWRP website:
Download - ADB / Terminal method (not recommended):
Download the corresponding .blob file above. Save it to the root of your /sdcard directly (internal memory only) and rename it to twrp.blob.Launch terminal emulator or connect to your computer and open an adb shell, then type the following:
Code:
su dd if=/sdcard/twrp.blob of=/dev/block/mmcblk0p4
Then reboot normally (NOT to recovery) to complete installation.
Click to expand...
Click to collapse
But I'll have to change the code above (as my /sdcard is crypted...) for something like :
Code:
su dd if=/twrp/twrp.blob of=/dev/block/mmcblk0p4
with /twrp a brand new (and readable by all users) folder containing the Blob file.
This is my only clue so far... Any other idea? I may just brick my Prime running a wrong command or tool
This start to be a pain in the ...
I can't even create a folder or copy files on the root folder (using ADBr Rom ToolBo Pro). They are automaticaly removed once I shutdown/restart the device or permission is recused ("read-only filesystem")
Wondering if I'll find a way :crying:
singinglarvae said:
Well, it's a bit more complicated than expected...
Running CWM v 5.8.3.4, I'm able to start on recovery mode (hopefuly...) but there is absolutely no way to get a correct fastboot connection!!!
I end up with a "connection refused" message (My ADB settings are corrects as I am abble to "play" with my TF201, once up and runing). I am therefore unable to install NVFlash, TWRP or any other tool :-/
I guess my only chance left is to follow the below instructions from TWRP website:
But I'll have to change the code above (as my /sdcard is crypted...) for something like :
Code:
su dd if=/twrp/twrp.blob of=/dev/block/mmcblk0p4
with /twrp a brand new (and readable by all users) folder containing the Blob file.
This is my only clue so far... Any other idea? I may just brick my Prime running a wrong command or tool
Click to expand...
Click to collapse
You are not able to access /sdcard from Terminal Emulator (not adb) while you are normally booted?
Sent from my Transformer Prime TF201 using Tapatalk 2
qery said:
You are not able to access /sdcard from Terminal Emulator (not adb) while you are normally booted?
Click to expand...
Click to collapse
I am abble to. But I won't be abble to read this folder once on recovery mod (as Clockwork Mod can't open this crypted folder)
singinglarvae said:
I am abble to. But I won't be abble to read this folder once on recovery mod (as Clockwork Mod can't open this crypted folder)
Click to expand...
Click to collapse
That's fine. I think you should run the dd command while normally booted, it copies the twrp.img into recoveryand it should work. Hopefully.
Sent from my Transformer Prime TF201 using Tapatalk 2
Thanks, the above code did the job after copying TWRP on my SDCard!
Code:
su dd if=/twrp/twrp.blob of=/dev/block/mmcblk0p4
So far, my TF201 is now running CM 9 and everything is now rolling!
@qery, thanks a lot for the help!
Now it's time to do NVFlash
Sent from my Transformer Prime TF201 using Tapatalk 2
I wanted to try the encrypt feature of android in my phone but now when I try to flash a new version on my rom can't mount my sdcard as it is encrypted. When I did it I imagined that it may was possible to decrypt within recovery and then flash a new rom but that's not possible.
What's the best way to decrypt my phone/flash a new rom on top, by losing as few as possible??
I googled and found a thread in the galaxy nexus forums that mentioned that the only way is via fastboot, is this possible with s2? any pointers to the s2 method?
I managed to flash another rom (miui specifically) by using adb and the commands below
./adb shell mount -t tmpfs none /sdcard
./adb push update.zip /sdcard
Click to expand...
Click to collapse
but now its not possible to decrypt the sdcard despite the fact i know the password, it doesn't even prompt me at boot
edit:
By doing factory reset I might have deleted the encryption keys rendering my sdcard inaccessible that's why I don't get prompted for password at boot. Is there anyway to fix this or create the certificates again as I know the password???
This has bin spoke about before with no results mate. Sorry. Seems its lost now. People I spoke to tried every thing with no success.
I9100/I9300
Hey flash gb firmware. A user did this and it has no encryption on it then flashed jb firmware and it was sorted :thumbup::thumbup: pls try it and see.
I9100/I9300
I'm trying to understand how to be able to mod a recently bought chinese phone "infocus m512", it's based on qualcomm snapdragon msm8926 and has android 4.4.2 installed which comes with "su" already installed, so basically the phone is already rooted.
I've found out the following:
/system is read only and cannot be remounted with r/w using the "su" available.
powering with both volume buttons pressed boots into some mode where the system is r/w but any changes made are not kept. I think it is FTM mode, the device is then recognized by ADB but not by FASTBOOT.
powering with vol down button pressed boots into download mode and the device is not recognized by ADB or FASTBOOT.
Any help understanding how to:
1. modify the /system partition
2. what can be done in FTM mode, and why changes to system do not stick
3. how to possibly use download mode to flash modified imgs?
4. find out if any write protection is enabled on the device
Thanks
sirpy said:
I'm trying to understand how to be able to mod a recently bought chinese phone "infocus m512", it's based on qualcomm snapdragon msm8926 and has android 4.4.2 installed which comes with "su" already installed, so basically the phone is already rooted.
I've found out the following:
/system is read only and cannot be remounted with r/w using the "su" available.
powering with both volume buttons pressed boots into some mode where the system is r/w but any changes made are not kept. I think it is FTM mode, the device is then recognized by ADB but not by FASTBOOT.
powering with vol down button pressed boots into download mode and the device is not recognized by ADB or FASTBOOT.
Any help understanding how to:
1. modify the /system partition
2. what can be done in FTM mode, and why changes to system do not stick
3. how to possibly use download mode to flash modified imgs?
4. find out if any write protection is enabled on the device
Thanks
Click to expand...
Click to collapse
Had any luck?
moding infocus m512 progress report
I was able to get fastboot to recognize the device using the -i option.
I was able to extract the recovery img and unpack it, also compiled a modified mkbootimg.
I did re-flash the splash img using fastboot so it seems there's no some kind of protection against flashing.
I will try to flash a modified boot and recovery that will mount the /system as rw and see if it works.
I still think maybe there's some kind of selinux settings involved preventing mounting system as rw, i will have to dig deeper for that.
GalaxyWhy said:
Had any luck?
Click to expand...
Click to collapse
sirpy said:
I was able to get fastboot to recognize the device using the -i option.
I was able to extract the recovery img and unpack it, also compiled a modified mkbootimg.
I did re-flash the splash img using fastboot so it seems there's no some kind of protection against flashing.
I will try to flash a modified boot and recovery that will mount the /system as rw and see if it works.
I still think maybe there's some kind of selinux settings involved preventing mounting system as rw, i will have to dig deeper for that.
Click to expand...
Click to collapse
Sounds good Keep me posted!
EDIT:
Are you running the most updated software? - http://www.infocusphone.com/m512updates.html
Yours came rooted you say? Where did you buy it from? - I got mine in pandawill.com and I'm waiting for it to arrive, hooeukly its rooted ?
Sent from my LG-D802
rooting infocus m512
GalaxyWhy said:
Yours came rooted you say? Where did you buy it from? - I got mine in pandawill.com and I'm waiting for it to arrive, hooeukly its rooted ?
Sent from my LG-D802
Click to expand...
Click to collapse
I bought it on lightinthebox.com anyways it shouldn't be much a problem to root it, since it's possible to flash a boot img to the device using fastboot.
I finally was able to trace the issue of not being able to mount /system as read/write to an error in the ext4 file system
it seems like the stock system.img has errors in its file system, so when the device initially mounts the /system partition it immediately remounts it as read-only because of the errors.
I was unable to flash a repaired system.img using fastboot (it dies in the middle, maybe because its such a large file), but I was able to modify the boot.img fstab.qcom to add the option errors=continue to the mount options of the /system partition. and now it is possible to mount /system as read write and you can do whatever you want as root.
{
"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"
}
In this picture it shows the phone having a recents button but on the website I bought it off it has a menu button. Which one does yours have?
You seem to know more about this stuff than me, I've usually bought well supported devices and rooting was a one click process. I just wanna get root access to be able to use Xposed Modules
Sent from my LG-D802
How'd you go?
I just received mine and I want to root it
rooting infocus m512
GalaxyWhy said:
How'd you go?
I just received mine and I want to root it
Click to expand...
Click to collapse
are you sure your device isn't already rooted? try to install supersu.
if you are sure it is not rooted you can root it the following way:
1. install adb
2.download su binary from somewhere
3. boot into Field Test Mode by (with phone turned off and connected to usb) holding both volume keys and power key together, when phone turns on release the power button and wait until the blue led turns off, then release volume keys. after a sec or two you should see some text on the screen.
4. connect to device via abd, run "adb shell"
5. mount the system as read/write by
(i'm not sure about /dev/block/mmcblk01/platform/by-name/system, it is something similar but you can find out yourself by search the subdirectories)
Code:
mkdir systmp
mount -t ext4 -o rw /dev/block/mmcblk01/platform/by-name/system /systemp
chmod 4755 /systmp/xbin/su
6. exit shell and run "adb push <path to su binary> /systmp/xbin
7. run "adb reboot"
8. install supersu or some other su manager.
let me know how it went.
sirpy said:
are you sure your device isn't already rooted? try to install supersu.
if you are sure it is not rooted you can root it the following way:
1. install adb
2.download su binary from somewhere
3. boot into Field Test Mode by (with phone turned off and connected to usb) holding both volume keys and power key together, when phone turns on release the power button and wait until the blue led turns off, then release volume keys. after a sec or two you should see some text on the screen.
4. connect to device via abd, run "adb shell"
5. mount the system as read/write by
(i'm not sure about /dev/block/mmcblk01/platform/by-name/system, it is something similar but you can find out yourself by search the subdirectories)
Code:
mkdir systmp
mount -t ext4 -o rw /dev/block/mmcblk01/platform/by-name/system /systemp
chmod 4755 /systmp/xbin/su
6. exit shell and run "adb push <path to su binary> /systmp/xbin
7. run "adb reboot"
8. install supersu or some other su manager.
let me know how it went.
Click to expand...
Click to collapse
Yeah 100% mine didn't have root but I figured it out after lots of searching around. I posted my method here http://forum.xda-developers.com/gen...discussion-t2893455/post55787107#post55787107 so others could do it if they wanted to
Similar problem here
sirpy said:
I finally was able to trace the issue of not being able to mount /system as read/write to an error in the ext4 file system
it seems like the stock system.img has errors in its file system, so when the device initially mounts the /system partition it immediately remounts it as read-only because of the errors.
I was unable to flash a repaired system.img using fastboot (it dies in the middle, maybe because its such a large file), but I was able to modify the boot.img fstab.qcom to add the option errors=continue to the mount options of the /system partition. and now it is possible to mount /system as read write and you can do whatever you want as root.
Click to expand...
Click to collapse
My phone is (seemingly) rooted, however I cannot modify platoform.xml (tried root explorer, total commander and what not). Also cannot remount the system partition using adb remount.
Can you provide details on how exactly did you modify fastab.qcom (and by the way, is it the file residing in the file system root directory)?
I tried modifying it and it seemed to succeed, however on reboot I had the original fstab.qcom.
Also, it seems that the su binary that I am using is not up to date. Each time I enter SuperSU it says that su binary needs to be updated, however the update fails (I tried both the normal way and the TWRP/CWM way). You wrote in a later post that the phone should be easily rooted using su that I can "download from somewhere". Can you point me to where I can find a suitable su binary?
modifying fstab
Beni.Falk said:
My phone is (seemingly) rooted, however I cannot modify platoform.xml (tried root explorer, total commander and what not). Also cannot remount the system partition using adb remount.
Can you provide details on how exactly did you modify fastab.qcom (and by the way, is it the file residing in the file system root directory)?
I tried modifying it and it seemed to succeed, however on reboot I had the original fstab.qcom.
Also, it seems that the su binary that I am using is not up to date. Each time I enter SuperSU it says that su binary needs to be updated, however the update fails (I tried both the normal way and the TWRP/CWM way). You wrote in a later post that the phone should be easily rooted using su that I can "download from somewhere". Can you point me to where I can find a suitable su binary?
Click to expand...
Click to collapse
Once you solve the readonly issue. you should be able to download and update supersu.
I've modified the fstab by extracing the boot.img opening it, modifying the fstab file and flash the modified boot.img back to the device.
you should be able to find numerous guides by googling on how to extract android boot.img.
for a quick fix, you can download the rom from needrom.com, and flash it. this rom is rooted and doesnt have any readonly issue on the system partition. (but you will loose everything on the phone)
sirpy said:
Once you solve the readonly issue. you should be able to download and update supersu.
I've modified the fstab by extracing the boot.img opening it, modifying the fstab file and flash the modified boot.img back to the device.
you should be able to find numerous guides by googling on how to extract android boot.img.
for a quick fix, you can download the rom from needrom.com, and flash it. this rom is rooted and doesnt have any readonly issue on the system partition. (but you will loose everything on the phone)
Click to expand...
Click to collapse
Sirpy,
Thanks for the info.
Given your diagnosis that the problem stems from errors on the file system, would it, in your opinion, be possible to repair the file system? I googled around and found a couple of threads that mention various flavors of fsck to be run in recovery mode using adb.
Does it makes sense, in your opinion? Have you tried it? If yes, which fsck did you use (plain fsck, fsck.exfat, e2fsck, or what else)? Or do you think it might be dangerous and the risk is not worth it?
About the rom from needrom - people have been complaining about GPS problems (the workaround seems to be to flash the latest InFocus firmware before flashing the needrom rom) and also about lack of phone memory after installing this firmware (did not see a stable workaround for this). If I go in this direction, I will probably try using the MIUI ROM (from Looserom and 4PDA.ru) instead.
I am currently using the original stock version (15CN_1_03A) and everything seems to be working reasonably well. My only problem is the complaint from SuperSU about the need to install a new su binary, however the current su seems to be working (more or less), so I will probably wait.
Beni.Falk said:
Sirpy,
Thanks for the info.
Given your diagnosis that the problem stems from errors on the file system, would it, in your opinion, be possible to repair the file system? I googled around and found a couple of threads that mention various flavors of fsck to be run in recovery mode using adb.
Does it makes sense, in your opinion? Have you tried it? If yes, which fsck did you use (plain fsck, fsck.exfat, e2fsck, or what else)? Or do you think it might be dangerous and the risk is not worth it?
About the rom from needrom - people have been complaining about GPS problems (the workaround seems to be to flash the latest InFocus firmware before flashing the needrom rom) and also about lack of phone memory after installing this firmware (did not see a stable workaround for this). If I go in this direction, I will probably try using the MIUI ROM (from Looserom and 4PDA.ru) instead.
I am currently using the original stock version (15CN_1_03A) and everything seems to be working reasonably well. My only problem is the complaint from SuperSU about the need to install a new su binary, however the current su seems to be working (more or less), so I will probably wait.
Click to expand...
Click to collapse
Well, yes you can try to run fsck. you should follow the method i've outlined in previous post on how to boot the device into ftm mode. then you should be able to run fsck on the system partition (/dev/block.../by-name/system). you will need to run fsck with ext4 option, though i'm not sure if fsck is included, so you might need to download the android version of it and copy it to your device in ftm mode to the root directory change its permissions to 755. (remount / partition as rw)
Firmware download link not working
Hi there..... this is my first message here , my first problem is that i am not able to download new firmware by Infocus page, it starts to download but cames to nothing. By the way I tried to update on wifi to a new 15CN_1_080 available by updating menu software on phone but after restarting i see Android System recovery <3e> 00cn_0_23A and i can choose : Reboot system now or Apply update from internal storage or Apply update from sdcard or Wipe data/factory reset or Wipe cache partition. At the end of the phone display in yellow text i read : finding update package…Opening update package…verifying update package…Installing update… Mounting partition Verifying current system…." /hidden / data / CDA /100CN / CDA / setting.xml " has unexpected contents. E: Error in / data / media / 0 / update.zip (status 7 ) installation aborted .
Until now the phone is multilanguage by default with version 15CN_1_03A . How to procede to go on ?
Therefore i am not sure phone is not already rooted, how can i verify it status and if it is already good to be flashed with a new custom rom ?
thanks a lot
Tinox said:
Hi there..... this is my first message here , my first problem is that i am not able to download new firmware by Infocus page, it starts to download but cames to nothing. By the way I tried to update on wifi to a new 15CN_1_080 available by updating menu software on phone but after restarting i see Android System recovery <3e> 00cn_0_23A and i can choose : Reboot system now or Apply update from internal storage or Apply update from sdcard or Wipe data/factory reset or Wipe cache partition. At the end of the phone display in yellow text i read : finding update package…Opening update package…verifying update package…Installing update… Mounting partition Verifying current system…." /hidden / data / CDA /100CN / CDA / setting.xml " has unexpected contents. E: Error in / data / media / 0 / update.zip (status 7 ) installation aborted .
Until now the phone is multilanguage by default with version 15CN_1_03A . How to procede to go on ?
Therefore i am not sure phone is not already rooted, how can i verify it status and if it is already good to be flashed with a new custom rom ?
thanks a lot
Click to expand...
Click to collapse
i think that your version 03A is the latest so no need for firmware upgrade.
you probably have some update.zip on your internal storage/sdcard which doesn't work and the system tries to install it on each reboot.
you need to delete it. if you can't access your phone storage via usb, you should follow the methods i've detailed in previous posts on how to boot into FTM mode and mount the different partitions, so you can access them in FTM mode.
already upgraded by seller ?
sirpy said:
i think that your version 03A is the latest so no need for firmware upgrade.
you probably have some update.zip on your internal storage/sdcard which doesn't work and the system tries to install it on each reboot.
you need to delete it. if you can't access your phone storage via usb, you should follow the methods i've detailed in previous posts on how to boot into FTM mode and mount the different partitions, so you can access them in FTM mode.
Click to expand...
Click to collapse
It is possibile seller already did root and installed ROM by needrom ? How could i check if it is already rooted ?
Tinox said:
It is possibile seller already did root and installed ROM by needrom ? How could i check if it is already rooted ?
Click to expand...
Click to collapse
download any terminal app, and type "su" in the terminal.
Looking for firmware link
Thanks Sirpy,
I check that in terminal and SU is not found so i am at the starting point for rooting phone but i am not able to download upgrade firmware 15CN_1_080 by Infocus page. Anyone able to give a working link or torrent link ? thanks
sirpy said:
download any terminal app, and type "su" in the terminal.
Click to expand...
Click to collapse
Tinox said:
Thanks Sirpy,
I check that in terminal and SU is not found so i am at the starting point for rooting phone but i am not able to download upgrade firmware 15CN_1_080 by Infocus page. Anyone able to give a working link or torrent link ? thanks
Click to expand...
Click to collapse
well as I said, from what you previously described you don't need the upgrade, you already have the latest.
Q&A for [TOOL][NABI2] NabiLab - Root, Play, Recovery
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for [TOOL][NABI2] NabiLab - Root, Play, Recovery. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!
State of Nabi 2 Root as of 12/14?
So I have admittedly been out of the loop on the state of rooting my two Nabi 2s since after I restored them to stock and all back last year when they released the update that included the Gapps. So I've been running stock since then and am on the latest firmware (2.4.6 I believe). All is mostly fine, but I would really like to get the external SD cards to be writable again, and from what I can tell, I need root again to do that.
So...as of today...what is the state (and best procedure) of rooting the Nabi 2 on the latest OTA update? Is Nabi Lab still the best tool? From what I've pieced together from scattered threads, it's looking like possibly use Nabi Lab to install TWRP, and then use that to install the SuperSU (http://forum.xda-developers.com/showthread.php?t=1538053). However, I could likely be wrong...hence why I'm asking.
Eyebolt said:
So I have admittedly been out of the loop on the state of rooting my two Nabi 2s since after I restored them to stock and all back last year when they released the update that included the Gapps. So I've been running stock since then and am on the latest firmware (2.4.6 I believe). All is mostly fine, but I would really like to get the external SD cards to be writable again, and from what I can tell, I need root again to do that.
So...as of today...what is the state (and best procedure) of rooting the Nabi 2 on the latest OTA update? Is Nabi Lab still the best tool? From what I've pieced together from scattered threads, it's looking like possibly use Nabi Lab to install TWRP, and then use that to install the SuperSU (http://forum.xda-developers.com/showthread.php?t=1538053). However, I could likely be wrong...hence why I'm asking.
Click to expand...
Click to collapse
Nabilab will still work as long as you use a version with a Jellybean TWRP(since you are on 2.4.6).
katinatez repackaged it for jellybean here:
http://forum.xda-developers.com/showpost.php?p=48987089&postcount=2088
I've searched high and low and can't find anything. I have nabi2S running KitKat. Every rooting guide I've found is for JB. Is there any way to root the 2S?
Sent from my Nexus 5 using XDA Free mobile app
jaxbierley said:
I've searched high and low and can't find anything. I have nabi2S running KitKat. Every rooting guide I've found is for JB. Is there any way to root the 2S?
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
For the sake of anyone else looking for this information we are discussing it at the main Nabi thread starting at post #2477
http://forum.xda-developers.com/showthread.php?t=1905674&page=248
Stock Restore
Hi
I have downloaded NabiLab, as I am having wifi issues on my updated Nabi2. I unzipped, ran the .bat and chose option 3 (with my nab connected via USB). Nothing happened, no errors etc, the screen flashed up and shut down. Do I need to do something with the Nabi (recovery mode etc), do I need to install anything from NabiLab before trying this? Any help would be appreciated
Firepants said:
Hi
I have downloaded NabiLab, as I am having wifi issues on my updated Nabi2. I unzipped, ran the .bat and chose option 3 (with my nab connected via USB). Nothing happened, no errors etc, the screen flashed up and shut down. Do I need to do something with the Nabi (recovery mode etc), do I need to install anything from NabiLab before trying this? Any help would be appreciated
Click to expand...
Click to collapse
What version of software? Use Nabilab2015 http://forum.xda-developers.com/showpost.php?p=59073456&postcount=2544
It has more diagnostic info. Just be in Android or TWRP with ADb enabled. It also can see if drivers are loaded.
Hacking Nabi2 to Allow Data2SD
I managed today to hack my kids Nabi2 to enable Data2SD. I was to frustrated by the limited space in the tab. My kids were complaining about not being able to add more games. Thus, I decided to take the risk of modifying the mount points of the tab to allow the data partition to point to a partition in a large sdcard, instead of the limited 4.5 GB space in the internal storage.
Warning: I am not responsible of any damage as a result of following the next steps. Always make backups
Note: I have the last update (KitKat) installed in the Nabi2
1- Dump the boot image from an adb shell:
Code:
su
cat /dev/block/platform/sdhci-tegra.3/by-name/LNX > /sdcard/boot.img
2- Open this url http://android-dls.com/wiki/index.php?title=HOWTO:_Unpack,_Edit,_and_Re-Pack_Boot_Images
to see the instructions of how to unpack and repack the boot image. Note that, the splitimage script mentioned in the page can be found at https://gist.github.com/jberkel/1087743
Warning: do not do anything in the tutorial, just wait
3- Format an sdcard as one partition of ext4 type
4- Insert the sdcard in the nabi2
5- Use the tutorial in step 2 to extract the ramdisk contents from the boot image and then Modify the file "fstab.mt799" in the ramdisk folder by replacing the line
Code:
/dev/block/platform/sdhci-tegra.3/by-name/UDA /data ext4 noatime,nosuid,nodev,journal_async_commit,data=writeback,nodelalloc,errors=panic wait,check,encryptable=/dev/block/platform/sdhci-tegra.3/by-name/MDA
with
Code:
/dev/block/platform/sdhci-tegra.0/by-num/p1 /data ext4 noatime,nosuid,nodev,journal_async_commit,data=writeback,nodelalloc,errors=panic wait,check,encryptable=/dev/block/platform/sdhci-tegra.3/by-name/MDA
which switches the data partition mount point to be on the sdcard
and the line
Code:
/devices/platform/sdhci-tegra.0/mmc_host/mmc2 auto vfat defaults voldmanaged=sdcard1:auto
with
Code:
/devices/platform/sdhci-tegra.3/mmc_host/mmc0 auto vfat defaults voldmanaged=sdcard1:12
which mount your old data partition into the directory of the external sdcard
6- Repack the boot image as mentioned in the url in step 2
7- Copy the new boot image to the nabi2 sdcard
8- Once you copied the new boot image (e.g. new_boot.img), replace the current boot image with the new one using adb shell:
Code:
su
cat /sdcard/new_boot.img > /dev/block/platform/sdhci-tegra.3/by-name/LNX
9- Now the kernel is replaced and once you rebooted your external sdcard would be in use, but note that your device is now having an empty data partition on the external sdcard, so you have to setup everything from the beginning. Note also that your previous data partition is now mounted as an sdcard, however, you have to format it from ext4 to fat32 to work as an sdcard (you can do the format from setings->storage->sdcard format)
ashahin1 said:
I managed today to hack my kids Nabi2 to enable Data2SD. I was to frustrated by the limited space in the tab. My kids were complaining about not being able to add more games. Thus, I decided to take the risk of modifying the mount points of the tab to allow the data partition to point to a partition in a large sdcard, instead of the limited 4.5 GB space in the internal storage.
Warning: I am not responsible of any damage as a result of following the next steps. Always make backups
Note: I have the last update (KitKat) installed in the Nabi2
1- Dump the boot image from an adb shell:
Code:
su
cat /dev/block/platform/sdhci-tegra.3/by-name/LNX > /sdcard/boot.img
2- Open this url http://android-dls.com/wiki/index.php?title=HOWTO:_Unpack,_Edit,_and_Re-Pack_Boot_Images
to see the instructions of how to unpack and repack the boot image. Note that, the splitimage script mentioned in the page can be found at https://gist.github.com/jberkel/1087743
Warning: do not do anything in the tutorial, just wait
3- Format an sdcard as one partition of ext4 type
4- Insert the sdcard in the nabi2
5- Use the tutorial in step 2 to extract the ramdisk contents from the boot image and then Modify the file "fstab.mt799" in the ramdisk folder by replacing the line
Code:
/dev/block/platform/sdhci-tegra.3/by-name/UDA /data ext4 noatime,nosuid,nodev,journal_async_commit,data=writeback,nodelalloc,errors=panic wait,check,encryptable=/dev/block/platform/sdhci-tegra.3/by-name/MDA
with
Code:
/dev/block/platform/sdhci-tegra.0/by-num/p1 /data ext4 noatime,nosuid,nodev,journal_async_commit,data=writeback,nodelalloc,errors=panic wait,check,encryptable=/dev/block/platform/sdhci-tegra.3/by-name/MDA
which switches the data partition mount point to be on the sdcard
and the line
Code:
/devices/platform/sdhci-tegra.0/mmc_host/mmc2 auto vfat defaults voldmanaged=sdcard1:auto
with
Code:
/devices/platform/sdhci-tegra.3/mmc_host/mmc0 auto vfat defaults voldmanaged=sdcard1:12
which mount your old data partition into the directory of the external sdcard
6- Repack the boot image as mentioned in the url in step 2
7- Copy the new boot image to the nabi2 sdcard
8- Once you copied the new boot image (e.g. new_boot.img), replace the current boot image with the new one using adb shell:
Code:
su
cat /sdcard/new_boot.img > /dev/block/platform/sdhci-tegra.3/by-name/LNX
9- Now the kernel is replaced and once you rebooted your external sdcard would be in use, but note that your device is now having an empty data partition on the external sdcard, so you have to setup everything from the beginning. Note also that your previous data partition is now mounted as an sdcard, however, you have to format it from ext4 to fat32 to work as an sdcard (you can do the format from setings->storage->sdcard format)
Click to expand...
Click to collapse
If you are not sure which line to change, I have the fstab.mt799 file attached with this post. You can simply replace your file with this one.
ashahin1 said:
I managed today to hack my kids Nabi2 to enable Data2SD. I was to frustrated by the limited space in the tab. My kids were complaining about not being able to add more games. Thus, I decided to take the risk of modifying the mount points of the tab to allow the data partition to point to a partition in a large sdcard, instead of the limited 4.5 GB space in the internal storage.
Warning: I am not responsible of any damage as a result of following the next steps. Always make backups
Note: I have the last update (KitKat) installed in the Nabi2
1- Dump the boot image from an adb shell:
Code:
su
cat /dev/block/platform/sdhci-tegra.3/by-name/LNX > /sdcard/boot.img
2- Open this url http://android-dls.com/wiki/index.php?title=HOWTO:_Unpack,_Edit,_and_Re-Pack_Boot_Images
to see the instructions of how to unpack and repack the boot image. Note that, the splitimage script mentioned in the page can be found at https://gist.github.com/jberkel/1087743
Warning: do not do anything in the tutorial, just wait
3- Format an sdcard as one partition of ext4 type
4- Insert the sdcard in the nabi2
5- Use the tutorial in step 2 to extract the ramdisk contents from the boot image and then Modify the file "fstab.mt799" in the ramdisk folder by replacing the line
Code:
/dev/block/platform/sdhci-tegra.3/by-name/UDA /data ext4 noatime,nosuid,nodev,journal_async_commit,data=writeback,nodelalloc,errors=panic wait,check,encryptable=/dev/block/platform/sdhci-tegra.3/by-name/MDA
with
Code:
/dev/block/platform/sdhci-tegra.0/by-num/p1 /data ext4 noatime,nosuid,nodev,journal_async_commit,data=writeback,nodelalloc,errors=panic wait,check,encryptable=/dev/block/platform/sdhci-tegra.3/by-name/MDA
which switches the data partition mount point to be on the sdcard
and the line
Code:
/devices/platform/sdhci-tegra.0/mmc_host/mmc2 auto vfat defaults voldmanaged=sdcard1:auto
with
Code:
/devices/platform/sdhci-tegra.3/mmc_host/mmc0 auto vfat defaults voldmanaged=sdcard1:12
which mount your old data partition into the directory of the external sdcard
6- Repack the boot image as mentioned in the url in step 2
7- Copy the new boot image to the nabi2 sdcard
8- Once you copied the new boot image (e.g. new_boot.img), replace the current boot image with the new one using adb shell:
Code:
su
cat /sdcard/new_boot.img > /dev/block/platform/sdhci-tegra.3/by-name/LNX
9- Now the kernel is replaced and once you rebooted your external sdcard would be in use, but note that your device is now having an empty data partition on the external sdcard, so you have to setup everything from the beginning. Note also that your previous data partition is now mounted as an sdcard, however, you have to format it from ext4 to fat32 to work as an sdcard (you can do the format from setings->storage->sdcard format)
Click to expand...
Click to collapse
If you don't have the time to do all these steps, I have the modified boot file attached here.
Yo can either follow steps 7 and 8 above to write it, or use the fastboot command as follows:
Code:
fastboot flash boot new_boot.img
Nabi2 not found
Hi, I purchased a reconditioned Nabi, which was reset back to stock. The wifi worked fine, until I updated it through the tablet. I am now on version 2.0 with no wifi. I have tried various options through NabiLab , however my Nabi is not recognised as being connected (although windows picks it up). Please help!
Swipe to restore
I am trying to return my nabi to stock, i can get to the screen that asks you to 'swipe to restore' but the screen is not responding. I dont have issues with the touchscreen normally
Aytul said:
I am trying to return my nabi to stock, i can get to the screen that asks you to 'swipe to restore' but the screen is not responding. I dont have issues with the touchscreen normally
Click to expand...
Click to collapse
That's weird...if you keep messing with it you may find a spot a little left, right, higher, or lower where you can grab the button to swipe....or you try to re-flash TWRP or maybe there's a new version of TWRP for your particular nabi software version.
did you ever get nabilab to see it? did you check the device manager to see if it was totally recognized? Are developer options enabled?
n3wt said:
That's weird...if you keep messing with it you may find a spot a little left, right, higher, or lower where you can grab the button to swipe....or you try to re-flash TWRP or maybe there's a new version of TWRP for your particular nabi software version.
did you ever get nabilab to see it? did you check the device manager to see if it was totally recognized? Are developer options enabled?
Click to expand...
Click to collapse
The Nabi is showing as a device, it's responds as it should up to the point of TWRP. I had to repeatedly press buttons to get to the restore swipe and have tried many times, unsuccessfully. Where do I enable developer options?
I am on version 2 (Nabi) and using the most up-to-date version of NabiLab. I am trying to restore to stock so that the software version goes back, as the update has stopped my wifi working. Even a factory reset doesn't take the Nabi software back further than v2.0
Aytul said:
The Nabi is showing as a device, it's responds as it should up to the point of TWRP. I had to repeatedly press buttons to get to the restore swipe and have tried many times, unsuccessfully. Where do I enable developer options?
I am on version 2 (Nabi) and using the most up-to-date version of NabiLab. I am trying to restore to stock so that the software version goes back, as the update has stopped my wifi working. Even a factory reset doesn't take the Nabi software back further than v2.0
Click to expand...
Click to collapse
For developer options you go to settings, scroll all the way down, if you don't see "Developer options" there, press About tablet, then repeatedly tap build number until it pops up and says "You are now a developer!", then go back and now you should see the Developer options menu item, press it and then make sure it's on at the top and that the USB Debugging option is checked.....then try nabilab again.
n3wt said:
For developer options you go to settings, scroll all the way down, if you don't see "Developer options" there, press About tablet, then repeatedly tap build number until it pops up and says "You are now a developer!", then go back and now you should see the Developer options menu item, press it and then make sure it's on at the top and that the USB Debugging option is checked.....then try nabilab again.
Click to expand...
Click to collapse
Yes this is enabled, as without it I am unable to run nabilab etc. The problem is TWRP & the version of software I am running on the tablet?
Aytul said:
Yes this is enabled, as without it I am unable to run nabilab etc. The problem is TWRP & the version of software I am running on the tablet?
Click to expand...
Click to collapse
Well, the touch issues are probably due to a bad build of TWRP but not necessarily the wrong one. The problem with nabilab not being able to see the tablet I think has to be drivers. Have you checked device manager to make sure there are no unrecognized things? 'cause the tablet show up as two separate things in there and it sounds like the USB storage part is working but not the adb and/or fastboot part(s).
n3wt said:
Well, the touch issues are probably due to a bad build of TWRP but not necessarily the wrong one. The problem with nabilab not being able to see the tablet I think has to be drivers. Have you checked device manager to make sure there are no unrecognized things? 'cause the tablet show up as two separate things in there and it sounds like the USB storage part is working but not the adb and/or fastboot part(s).
Click to expand...
Click to collapse
I've managed to sort the drivers by installing PDANet, then managed to sort TWRP by installing an older version. I've now updated to 2.1 on the Nabi but no luck with the wifi issue..i'm guessing it's really broken and it happening whilst updating may have been a coincidence?!
Aytul said:
I've managed to sort the drivers by installing PDANet, then managed to sort TWRP by installing an older version. I've now updated to 2.1 on the Nabi but no luck with the wifi issue..i'm guessing it's really broken and it happening whilst updating may have been a coincidence?!
Click to expand...
Click to collapse
It might just be broken but that's a heck of a coincidence... Do you have a backup from before the wifi issue started? If so, I'd try to thoroughly wipe everything but your external sd card and then restoring your backup and see if that helps.
n3wt said:
It might just be broken but that's a heck of a coincidence... Do you have a backup from before the wifi issue started? If so, I'd try to thoroughly wipe everything but your external sd card and then restoring your backup and see if that helps.
Click to expand...
Click to collapse
Hi, I bought it as a reconditioned did unit. Turned it on, updates it (wifi worked) and then had this problem, so no backup to go back to unfortunately