Related
Hi,
Hope someone can help, about this problem. But I think all it's comes down to now is getting ADB access via Amon_RA recovery rom, as I've tried everything I can do... link to previous post here: http://forum.xda-developers.com/showthread.php?t=642468
I'm running Window 7 Pro x64, previously the ADB was working, but after setting up some ext partition option accidentaly, (I think that it's linked to that), i've tried all options I know of by trying to manually install the drivers and removing them completely etc...
Main points, I can still access recovery image, and also the bootloader. I've succesfully flashed custom roms etc... before. And phone does not boot to rom(that's because I think it didn't install correctly, not sure)
So, i'm sort of lost now, just wondering if any developers here would kindly help or put me out my misery!
re partition your ext(2/3 for Eris base rom) ext4 might not work on Eris.
if you still facing problem remove the swap & only remain the ext partition for A2SD.
edit: and please update to v1.6.2 for the recovery***
Thanks for you response but I can't do anything within the recovery image, some options keep saying please use adb to carry out the process, but I can't get adb to detect on the phone anymore. Also I can't update the latest recovery image, as i'd need adb access....
I can't see why this is happening... perhaps its the SD card that's messed up? I could repartiotion using linux using gparted or something, but I don't know how the Hero set's up the partion.
When I try to recover using nandroid I get messages like unable to mount E:SDCARD etc...
Any clues?
did you do a dalvik wipe? y not try remove the ext partition & try restore previous nandroid?
I apologize if this has been covered in another thread but I have been doing multiple searches on XDA and in google trying to find a solution but so far no luck. Long time reader of XDA but first time poster.
Details -
I successfully used NVFLASH, loaded Clockworkmod 0.8 and loaded Vega-Ntab gingerbread edition (stable RC1 I believe its called). I have been running this for a month or so with no major issues but I want to test out Vega-Ntab 5.1 and Brilliant Corners. Thinking of going with 5.1 for the hardware acceleration for gaming etc. Oh I also received my new Gtab with bootloader 1.2 and I downgraded that to 1.1 successfully before loading Vega-Ntab gingerbread. I think I can handle loading the new roms etc (may have to switch to 1.2 for Brilliant Corners I believe) but I want to do a full backup before doing so with clockworkmod so I can go back to gingerbread if I decide I liked it the best. But clockworkmod will not do a backup for me. I have tried multiple times and it always freezes/hangs at the same point. On the screen I see
ClockworkMod Recovery v2.5.1.1-bekit-0.8
SD card space free: 9697MB
Backing up boot...
Backing up recovery...
Backing up system... and here it will go no further
I have let it set at that point for hours but nothing changes. I checked the clockworkmod backup folder and it has a folder dated the current date of the backup but the contents is only boot.img and recovery.img and nothing else so I think that confirms it really isnt completing the backup.
I am unsure what the cause or solution to this is. I thought about reloading clockworkmod 0.8 but I don't think I can do this since it's already loaded. I thought about loading a newer version but from what I have read gingerbread and the other 1.1 roms will not work with anything but 0.8. I could just do a melt and repour and just go back to stock level and load 5.1 or Brilliant Corners but then I lose any apps I have loaded. I am not concerned about the majority of them but I have loaded a couple good ones as of late from Amazon that were the free app of the day and I am unsure whether I can "reload" these at a later date without being forced to pay. I have also paid for a couple games but I am assuming I can reload those without issue. I did back up all of the apps I paid for and amazon games that I loaded that I got for free (normally have to pay) with titanium backup. So assuming I can restore these with titanium backup after loading brilliant corners or vegan 5.1 then I guess the only thing that I lose by not being able to do a full backup/restore with clockwork is that if I want to go back to gingerbread then I have to start from scratch for reloading the rom.
So is the problem I am having running the back up successfully a known issue that I just can't seem to find a discussion thread about?
Thanks in advance for any help or advice.
Boot into ClockworkMod Recovery and get me a dmesg output (kernel messages) using adb. See this post for how.
Attach the dmesg.txt to your next post.
thanks for the reply. Unfortunately I am not having any luck getting the dmesg.txt file for you. I downloaded the iso image for Knoppix 6 but when I boot off the disc it starts processing everything but then it gives an error "the file /mnt-system/knoppix/knoppix is broken. then after about 30 secs it gives the following
/sbin/init: line 76: syntax error near unexpected token '/usr/share/fonts/type1/gsfonts/a010013l.pfb'
/sbin/init: line 76: '/URWGothicL-Book (usr/share/fonts/type1/gsfonts/a010013l.pfb);
I will try and download the iso from a different site and burn another disc.
I also tried a different route and loaded SDK manager to get to ADB by that route. I am running windows 7 if that makes a difference. I am not 100% sure when I am supposed to run the adb command line you listed. Do I have my gtab running clockworkmod and then mount USB so it will show up on my pc? Do I have to try and perform a backup and then run the adb command when it freezes? I don't think I can do that because if I navigate away from the mount USB it automatically unmounts it. Anyway adb doesn't appear to be seeing the gtab anyway. When I run the SDK manager it does not find any android devices. If I run the "adb devices" command it comes back with no devices. So I am not sure what basic thing I am missing to get adb or SDK to recognize the gtab.
I apologize for my lack of knowledge on adb. Your first link says if I have adb already set up to run adb shell dmesg > dmesg.txt while in clockworkmod so I am assuming I do this after mounting USB to get the pc to recognize the gtab.
I will try download and burn another iso image from a different location and see if I can boot off a disc. Assuming this time it is successful do I run the ADB command you listed in the second link while the GTab is mounted to USB and recognized by the pc? Hopefully ADB will see it if I can get this to work.
*update* I downloaded the ISO image from a different location. When I went to the folder it was downloaded to I noticed that the first ISO image I downloaded was only approx 100MB in size instead of 700+ mb. So I am re-burning another disc. Hopefully this will allow me to boot properly.
*update #2* I was able to successfully boot off of the new disc. Now I just need to figure out how and where to enter the adb command line in your link ($ sudo ./adb shell dmesg > dmesg.txt) i tried this using the Shell option but it says command not found. If I choose the File Manager option and navigate to where the adb file is that was in your linked zip file it just prompts me to edit/copy/move/rename or delete the file. I am out of time tonight so I will work on it more tomorrow. The good news though is that when I use File Manager the Gtab is listed so it is at least recognized. Now I just need to figure out how to get the dmesg.txt file you request but making some progress... I think
ashton555 said:
*update #2* I was able to successfully boot off of the new disc. Now I just need to figure out how and where to enter the adb command line in your link ($ sudo ./adb shell dmesg > dmesg.txt)
Click to expand...
Click to collapse
Step by step instructions in this post.
thanks a bunch. Those instructions were easy to follow and made sense. I have never used linux before but alot of it reminded me back of my old unix days (terminal commands that is).
Anyway I think I did everything correct and I am now attaching the txt file.
Thanks again for your help and patience with this Linux newbie let me know if I need to provide any additional information.
ashton555 said:
Anyway I think I did everything correct and I am now attaching the txt file.
Click to expand...
Click to collapse
You did indeed. And I can't see any obvious problems with the NAND-flash device, judging from the kernel messages.
Since you've already tried to take backups using CWM before, that action should've created a log file. This file might be useful. Retrieve it. Inside an xterm window on Linux, run:
Code:
hostpc$ [B]sudo ./adb pull /cache/recovery/log recovery.log[/B]
Attach this "recovery.log" file.
Next, try to read, one by one, the NAND flash partitions that CWM usually backs up. Here's an example run on my gTablet:
Code:
hostpc$ [B]sudo ./adb shell[/B] [I]Get into the shell in CWM[/I]
~ # [B]dump_image boot /dev/null[/B]
~ # [B]dump_image recovery /dev/null[/B]
~ # [B]dump_image system /dev/null[/B]
mtd: read error at 0x029a0000 (I/O error)
mtd: read error at 0x02da0000 (I/O error)
~ # [B]dump_image cache /dev/null[/B]
~ #
Type in only the commands in bold.
As you can see, my "system" partition on the NAND flash has errors (and the kernel also report this when it boots), but, the command will not hang. According to the kernel message that you just supplied, you don't have any errors on your onboard NAND flash, so, theoretically, you shouldn't get any errors at all. But, we'll see if the dump_image command hangs when reading system just like CWM does.
And if the dump_image command does hang somewhere, we can see if formatting just that system partition will get it working again. There is a utility on this board which we could use for doing that, though I've never tried it.
I successfully completed the next two tasks. I am attaching the recovery.log file. Note I had an issue copying the .log file to where I could access it in win7 (for some reason I cant attach a file while in linux). I opened it with a word processor and then saved it to my c drive which messed up the formatting. So I opened it in Word to get the formatting correct and saved it as a txt file so thats why the attached file is recovery.txt. Let me know if it messed it up to where its not useable.
On the second task
~ # dump_image boot /dev/null
this worked fine and quick
~ # dump_image recovery /dev/null
this worked fine and quick
~ # dump_image system /dev/null
this worked but took maybe 10-15 seconds
~ # dump_image cache /dev/null
this one gave an I/O error but completed the dump
mtd: read error at 0x00080000 (I/O error)
ashton555 said:
Let me know if it messed it up to where its not useable.
Click to expand...
Click to collapse
The file is just fine... and I can't see any error messages in it.
~ # dump_image system /dev/null
this worked but took maybe 10-15 seconds
Click to expand...
Click to collapse
This is normal -- "system" partition is ~200MB.
~ # dump_image cache /dev/null
this one gave an I/O error but completed the dump
mtd: read error at 0x00080000 (I/O error)
Click to expand...
Click to collapse
This also looks like normal behaviour, but, I'm puzzled that the kernel did not report any bad blocks on this partition. Check if this is a transient error:
1. Repeat the "dump_image cache ..." command a few times and see if the I/O error location is the same.
2. Try to "fix" the error on the cache partition by using the "wipe cache partition" menu item in CWM. Do this a couple of times.
3. Run the "dump_image cache ..." command again.
4. Attempt another full system backup using CWM.
If step 4 fails, we'll see if the writing of the backup to the sdcard is the problem, because the reading seems to be completing without any hangs as of now.
BTW, the most important partitions are all being read fine. The "cache" partition is not that important -- it can be empty (but not corrupt) each time the system boots and only the initial bootup might go a little slower.
And, if, in the end of all this, you can't use CWM at all, you can still make a full system backup using nvflash and a few Unix commands.
1. Repeat the "dump_image cache ..." command a few times and see if the I/O error location is the same
....i did the dump 4 times and it always gave the same I/O location
2. Try to "fix" the error on the cache partition by using the "wipe cache partition" menu item in CWM. Do this a couple of times
.... I wiped the cache 4 times successsfully
3. Run the "dump_image cache ..." command again.
.... same I/O error location
4. Attempt another full system backup using CWM
.... still freezing at backing up system
So I guess I need to try and do the backup with NVFlash and unix/linux commands? If you have a link on how to do that I will give it a try or I can search for it and see if there is a discussion thread on it.
Thanks again for your help and trying to resolve this
Question - if I started over from scratch and went back to stock and then loaded vegan gingerbread would this issue possibly correct itself? Also more importantly if I back up some apps using titanium backup before I go back to stock can I then restore them with Titanium once I have vegan ginger back loaded? Also if I loaded vegan 5.1.1 could I restore the same apps I backed up in vegan ginger? Hopefully that made sense. I don't mind starting from scratch if I need to I just wasnt sure if I would permanently lose certain apps I have loaded. It's only about 10 apps I care about
*update* - well I think I am going to be forced to start over anyway. After wiping the cache a couple times and attempting another backup (froze again at backing up system) I now can't get the gtab to boot completely. It is stuck at the flashing vegan ginger edition screen. It flashes for awhile then the screen goes black then it goes back to the flashing screen again. I know you said it would take longer to boot up the first time after wiping the cache but was doing the flash cycling for over an hour which I assume is too long? I tried wiping the cache again and I also wiped the davlik cache as someone suggested in another thread but it is back to being stuck in the flashing screen loop. Assuming I do have to start over can I at least boot to CWM, mount ext USB and copy off the titanium backup files I made so I can restore some of the paid for apps?
ashton555 said:
3. Run the "dump_image cache ..." command again.
.... same I/O error location
Click to expand...
Click to collapse
Looks like a permanent I/O error in the cache partition, then. But, I don't understand why it is "system" which is hanging on backup.
4. Attempt another full system backup using CWM
.... still freezing at backing up system
Click to expand...
Click to collapse
Get me the recovery.log.
So I guess I need to try and do the backup with NVFlash and unix/linux commands?
Click to expand...
Click to collapse
I'll think this over during the weekend. In the mean-time, read through this thread. You can safely take a complete backup of your tablet while I do a bit of experimentation on a clockworkmod-like solution. But, I suspect that you may not be able to backup "cache" using nvflash going by the I/O errors. I have errors on my "system" partition and a nvflash backup fails on it, but CWM doesn't have any problems backing up and restoring.
Question - if I started over from scratch and went back to stock and then loaded vegan gingerbread would this issue possibly correct itself?
Click to expand...
Click to collapse
Probably not. But, see this thread. It shows you how to wipe all the partitions on the NAND flash device. We don't need to format the entire NAND flash. We can see if doing a few repeated formats of the "system" and "cache" partitions gets CWM working again, if you're willing to wipe "system"--you will have to load Vegan-Ginger right after this.
Also more importantly if I back up some apps using titanium backup before I go back to stock can I then restore them with Titanium once I have vegan ginger back loaded? Also if I loaded vegan 5.1.1 could I restore the same apps I backed up in vegan ginger? Hopefully that made sense. I don't mind starting from scratch if I need to I just wasnt sure if I would permanently lose certain apps I have loaded. It's only about 10 apps I care about
Click to expand...
Click to collapse
I haven't used Titanium backup so I can't say how well it works, but, judging from the reports that other users have made, what you're suggesting should work without any problems. User downloaded applications are stored either on /data or on /mnt/sdcard (for apps moved to SD card). Since your SD cards don't seem to be affected, you can go ahead with Titanium backup.
ashton555 said:
Assuming I do have to start over can I at least boot to CWM, mount ext USB and copy off the titanium backup files I made so I can restore some of the paid for apps?
Click to expand...
Click to collapse
Yeah, copy the files in CWM, then just do a "wipe data/factory reset" and see if it boot loop goes away.
But, before you do that, gimme a half-hour and I'll send you commands which you can use to save the files in /data and /sdcard. I just have to compile and test a new version of busybox. The tar command already present in CWM doesn't seem to work properly for me.
Attaching the recovery file
I am running the nvflash back up right now.
It successfully did part-1.img through part-11.img with no errors. The last thing it said though is
"rem CACHE PARTITION BACKUP NOT NEEDED
"nvflash.exe" -r --read 12 part-12.img
press enter to continue
Is this maybe because I wiped the cache and it's empty?
I looked on my ext SD card and the titanium backup files are there (except for a couple I had forgotten do ....) so I think I am okay for going back to square one if need be.
I will go ahead (tomorrow probably) try doing what is described thread about wiping partitions on the NAND device and just formating the system and cache partitions. I am assuming that at this point I guess its okay to go ahead and try to load vegan tab 5.1.1 instead of ginger again since I wanted to try out 5.1.1 anyway or if you have any experience with it would you recommend Brilliant Corners instead since its a newer rom. I think I will have to reload the 1.2 bootloader which is okay.
ashton555 said:
Attaching the recovery file
Click to expand...
Click to collapse
No errors in there.
The last thing it said though is
"rem CACHE PARTITION BACKUP NOT NEEDED
"nvflash.exe" -r --read 12 part-12.img
press enter to continue
Is this maybe because I wiped the cache and it's empty?
Click to expand...
Click to collapse
I think so. The cache partition isn't that important anyway, so it can be skipped.
I will go ahead (tomorrow probably) try doing what is described thread about wiping partitions on the NAND device and just formating the system and cache partitions.
Click to expand...
Click to collapse
I would suggest that you copy the Titanium backed-up apps safely away immediately, then format just the system and cache partitions as per that thread. You will need to be in APX mode to use nvflash.
Immediately after the nvflash, (since the system partition is now gone), boot into CWM, then do a factory reset, repartition the internal sdcard, copy the Vegan-5.1.1 update file onto the now clean sdcard through the PC and then flash it. This should give you a clean slate.
Then check if you can do a backup using CWM. If you still can't, then I'll see if a solution can be devised to do partial backups.
And, I have tried neither Vegan* nor Brilliant Corners, so the choice is up to you.
Sorry, my test commands aren't working so I can't send you those commands I promised to back up your /data and /system--I suspect a bad USB cable.
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
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
OFFICAL TWRP RELEASED, this thread is no longer active. 3-30-2018
https://twrp.me/motorola/motorolamotox4.html
---
UNOFFICIAL BUILDS -- USE AT YOUR OWN RISK AND KNOW HOW TO GET YOURSELF OUT OF TROUBLE IF IT ARISES. I ASSUME NO RESPONSIBILITY FOR YOUR BROKEN THINGS.
UPDATED 01-11-2018
There are now 7.1 based and 8.0 based builds. Obviously, be careful to select the proper download. While I don't think flashing/booting the wrong one would permanently brick the device, let's not find out
For now I will not be attempting to make data decryption work. It is REQUIRED that you unencrypt your device by formatting userdata, so back up your stuff first.
IMPORTANT NOTES: TWRP for OREO is a bit of a pain as it currently requires manually editing your fstab. I have tried to automate this process, but it breaks stuff. So just be aware before you begin that it is a rather time consuming process.
If you make any change to your boot partition after flashing SuperSU, you will need to reflash it or you will get a bootloop.
8.0 OREO TWRP INSTALLATION:
OREO SEEMS VERY FINICKY AND DOES NOT LIKE CHANGES TO ITS FILESYSTEM -- BE PREPARED TO REFLASH STOCK.
0. FLASH OREO FACTORY IMAGE (may work otherwise, but we should be starting from fresh stock here)
1. Download FASTBOOT BOOTABLE TWRP for 8.0/OREO below
2. Download SuperSU 2.82 SR5 below
3. Move SuperSU to external SD or USB OTG
4. From bootloader, fasboot BOOT TWRP
5. Flash SuperSU (note: do not format /data now... not necessary and will cause errors on boot)
6. Reboot system
7. With any root file editor/text editor (Amaze, Total Commander, etc) open /system/vendor/etc/fstab.qcom as a text file for editing.
8. At the end of the /data partition entry, delete "fileencryption=ice" and replace it with "encryptable=footer".
9. Save fstab.qcom (and make sure it is actually saved properly!)
10. Reboot to bootloader and fasboot BOOT TWRP
11. Go to Wipe, hit the FORMAT DATA button, and type "yes" to format /data. This will erase your data, obviously:silly:
12. Reboot system (should now be unencrypted, verify in Settings>Security or by booting TWRP and checking /data with File Manager.
If you later choose to flash TWRP (not the bootable we used here!), you may need to flash SuperSU again to avoid bootloops.
7.1.1 NOUGAT TWRP INSTALLATION:
1. Download current TWRP for 7.1.1 build below
2. Download SuperSU 2.85 SR5 (https://forum.xda-developers.com/apps/supersu/2014-09-02-supersu-v2-05-t2868133
3. Move SuperSU to your external Micro SD card.
4. Fastboot flash the TWRP image.
5. Reboot to TWRP.
6. FORMAT data (not wipe...use the "FORMAT DATA" button and type "yes". OBVIOUSLY THIS WILL ERASE YOUR DATA)
7. Install SuperSU 2.85 SR5
8. Reboot to system (it WILL bootloop a couple times...don't panic!) and confirm that device is unencrypted by checking that SETTINGS>SECURITY>ENCRYPTION now prompts "encrypt" (don't do it).
DOWNLOADS:
TWRP FOR 7.1.1 (Nougat) DOWNLOAD: https://drive.google.com/open?id=1Et-AQgCNx7WDAwzihlI51euUa2ixKHEP
TWRP FOR 8.0 (Oreo) DOWNLOAD: https://drive.google.com/open?id=1WcVS_3rloF7jxPulj_jKxfsp3zy5pB5N
FASTBOOT BOOTABLE TWRP IMAGE (OREO BASED): https://drive.google.com/open?id=12ClviqtEjtflB63UQ1CZQNKEqkprBO0u **For temporary TWRP boot using "fastboot boot". Do not flash or you will be stuck in recovery!**
DEVICE TREE: https://github.com/mightysween/android_device_motorola_payton (NEEDS TO BE UPDATED WITH OREO BRANCH)
changelog:
BETA4
-reverted to 3.2.0 for current build (release candidate rebased to 3.2.1).
-fixed "format data" button
-finalized fstab for OTG/SD/INTERNAL mounting
-target is now UNENCRYPTED devices only (/data decrypt will not be fixed)
BETA3
-Rebased to TWRP 3.2.1
-USB OTG working
-all partitions mounting correctly
-considered working except for decrypt and MTP/ADB
BETA2
-fixed internal storage mount
BETA1
- updated source to TWRP 3.2.0
ALPHA3
- Fixed USB mounting (adb/mtp still nonfunctional) BROKEN IN BETA1
ALPHA2
- SD Card fixed
ALPHA1
- /system is now properly mounted.
- now plays nice with our working root method.
- ramdisk is patched to prevent first boot encryption once /data is decrypted (now requires flashable ZIP)
NOT WORKING:
adb/mtp/sideload
/data decryption (abandoned -- /data access requires unencryption)
CREDITS: @kraatus90 for kernel fix, @Chainfire for SuperSU, @jcadduono for no-verity-opt-encrypt scripts.
---
Thanks so much for all your work!
hi,
you said this is really unstable and could brick the device easily. however, you seem to be testing and experimenting with your device a lot, so i'd like to ask if you have any particual unbrick method that you use when something goes wrong.. like, a via fastboot flashable image or something simmilar...?
thanks for your work!
Thanks for you work. If you have any unbrick methods pls tell.appreciated your work ?
I am not going to provide step by step "unbrick" methods, because until the partitioning is properly set up, TWRP has potential access to things that can not be fixed.
Again, this is still highly experimental.
All that said, my entire process to protect any device remains the same: Have a backup for every partition you will be testing, make as few changes as possible at a time, test boot images before flashing (fastboot boot), and test restore methods frequently (flashing back to stock or backups), and don't do anything unless you are highly certain of the outcome.
By those standards, there is nothing to gain by installing TWRP right now, as its basic function (install/backup/restore) is not set up yet.
Found the BoardConfig flag to enable FBE (TW_INCLUDE_CRYPTO_FBE := true) but do not have the lib it is dependent on (libe4crypt) and I don't see it anywhere yet...
For reference (not sure this is most current, but it demonstrates the process)
https://github.com/nijel8/TWRP/commit/bd7492de28963b7e74e8e5d3f17ec9a5a287d9c3
I have confirmed that FBE support is present in the source, dependent on this missing module... so need to figure out where/how to enable it.
It is possible that this entire process is specific to only certain devices (i.e. Pixel, Nexus). If this is the case, we may be stuck at this point for awhile.
Obvious workaround is to not be encrypted to begin with -- but that isn't a "solution".
mightysween said:
It is possible that this entire process is specific to only certain devices (i.e. Pixel, Nexus). If this is the case, we may be stuck at this point for awhile.
Click to expand...
Click to collapse
This appears to be the case, unfortunately. Seems that the TWRP FBE support was built specifically for the Google implementation of FBE which was merged into kernel sources for Nexus and Pixel. Not even using the qseecomd I assumed it was... will remove on next build.
Info on FBE:
https://source.android.com/security/encryption/file-based
Will be testing options to disable forced encryption, and if necessary dm-verity...
Anyone who wants to dig through kernel for related flags and props, it would be greatly appreciated!
Hey, where did the big "format data" button go in TWRP? Is that optional on compile... can't find a flag for it...
Making good progress this morning.
Seem to have a build with properly decrypted /system, and working SD Card. I also have patched the boot.img to disable forced encryption on the first boot. But now, I can not find a safe way to fully format (not "wipe") the /data partition. As mentioned in the previous post, the "FORMAT DATA" button is missing. The fastboot command "fastboot format userdata" returns an error that it does not support RAW format.
Need to figure out why this is happening... and once I do, I believe I can reformat /data without encryption and then will have an almost fully working TWRP build. Obviously, the ideal solution would be to have TWRP work out of the gate with an encrypted /data, but until then this is going to be our best option.
Will post an updated test build in the OP soon.... needs further testing before I would recommend non-expert users to try it.
Getting very close now!
UPDATE: ADDED NEW BUILD TO OP
---
Also, just occurred to me that the ramdisk will need to be patched every time, so now that I have SD card support will be testing some of the existing flashable ZIPs out there that are designed specificially to prevent first-boot encryption and/or disable dm-verity.
---
mightysween said:
Hey, where did the big "format data" button go in TWRP? Is that optional on compile... can't find a flag for it...
Click to expand...
Click to collapse
This is really the only hold up... I changed the partition from 'Advanced Wipe", but as expected, it was still encrypted on boot as it doesn't actually format the footer where encryption is stored. I can't figure out where that darn "FORMAT DATA" button ran off to, and that is exactly what we need here.
mightysween said:
This is really the only hold up... I changed the partition from 'Advanced Wipe", but as expected, it was still encrypted on boot as it doesn't actually format the footer where encryption is stored. I can't figure out where that darn "FORMAT DATA" button ran off to, and that is exactly what we need here.
Click to expand...
Click to collapse
I don't know how to help except to say that using TWRP 3.1.0-MOD_1 with my XT1254 (DROID Turbo), when you go to wipe it has two buttons --- one on the left for Advanced Wipe and Format Data on the right.
johnjingle said:
I don't know how to help except to say that using TWRP 3.1.0-MOD_1 with my XT1254 (DROID Turbo), when you go to wipe it has two buttons --- one on the left for Advanced Wipe and Format Data on the right.
Click to expand...
Click to collapse
I have 3.1.1-0 (same version I am building here) on several other devices, and the button is there. It has to be triggered by something during compile, but I can't figure it out. Driving me nuts
Looking through TWRP source, and can find actions for every other button (wipe, backup, restore, install, etc) but not for format. Hmm.
I posted over on an old but semi-active TWRP flags thread, maybe someone will have some insight.
Wondering if I make a stock boot image without the encryption tag in fstab, and then wipe data and reboot... then flash my image. That may make it so the data partition is never encrypted in the first place and allow TWRP to work.
But that is an ugly, non-user friendly fix. Why can't we just format /data?
---
Final update for today... this seems to be a compile issue, which is a good thing. I tried to manually decrypt /data from the TWRP command line, and got this:
No crypto support was compiled into this build.
Click to expand...
Click to collapse
So, I must be missing something in boardconfig still... and maybe need to set up a small proprietary vendor folder with the necessary libs
mightysween said:
Final update for today... this seems to be a compile issue, which is a good thing. I tried to manually decrypt /data from the TWRP command line, and got this:
So, I must be missing something in boardconfig still... and maybe need to set up a small proprietary vendor folder with the necessary libs
Click to expand...
Click to collapse
Thanks for doing all of this! I wish I had the time and knowledge to help.
Had a few PM's checking on TWRP status, so an update.
The good news is that the X4 is using Qualcomm based decryption for /data... the bad news is that most if it seems to be closed source. This will take some time for me to figure out, but I have already made some progress by sifting through logs.
Right now, I am trying to find a device with similar decrypt scheme to have some more guidance on the process.
mightysween said:
Had a few PM's checking on TWRP status, so an update.
The good news is that the X4 is using Qualcomm based decryption for /data... the bad news is that most if it seems to be closed source. This will take some time for me to figure out, but I have already made some progress by sifting through logs.
Right now, I am trying to find a device with similar decrypt scheme to have some more guidance on the process.
Click to expand...
Click to collapse
dont know all about these things but maybe xiaomi mi a1 twrp can help as it is also using same a/b partition. and twrp is already there for it
vivek638 said:
dont know all about these things but maybe xiaomi mi a1 twrp can help as it is also using same a/b partition. and twrp is already there for it
Click to expand...
Click to collapse
Thanks, the Mi A1 is one of the devices I have been comparing to, and has been quite helpful.
mightysween said:
Thanks, the Mi A1 is one of the devices I have been comparing to, and has been quite helpful.
Click to expand...
Click to collapse
Keep searching. wish i could have helped but dont know anything about compiling n all..
I'm not much of a programmer, but I can look through the files. Is there anything in particular we're searching for?