[Q] Help moding infocus m512 snapdragon msm8926 - Android Q&A, Help & Troubleshooting

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.

Related

Can someone get....

I'm in need of the stock kernal image and the clockwork recovery.zip file thingy.
NOT the zip verson of the kernal installer.
My situation, I was stupid and installed the voodoo thing, then for someone reason I tried to flash Froyo over Bionix with the voodoo kernal thing. It didnt work so I decided to deleted everything in clockwork. Then I was like omg I cant use clock work or boot my device (stuck on vibrant screen but I can get to odin and the stock recovery).
Later I read that voodoo stopped odin on the cm forum so I couldnt use it. Thats what some dude named viralblack said and theyre a mod so I'm guessing its true.
So my last 4 ideas are:
1)Try and flash a new Kernal Image in adb and hope it gets odin to work
2)Push the cw recovery to the phone
3)Run to the library and hope my computer is the problem
4)Pretend vb is wrong and keep trying the download screen thing
Sorry if this is in the wrong section but I guessed it could go here because I need some files....
flash Eugene's froyo that does not brick via Odin. he has instructions in his thread.
...and it's kernel NOT kernal people
Sent from my SGH-T959 using XDA App
kernel, sorry I guess?
Anyhow what if my pc doesnt notice the phone when its in download mode
RPGbig said:
kernel, sorry I guess?
Anyhow what if my pc doesnt notice the phone when its in download mode
Click to expand...
Click to collapse
Download the Samsung drivers, download ODIN, and then just follow the directions in the ODIN thread
Wow
You guys have nothing better to do than flame a newb?
If you spent half the time helping instead of flaming there MIGHT just be some people with a bit more knowledge than they had yesterday.
If you cant say something constructive/helpful --Why bother!
fcbarca17 said:
Download the Samsung drivers, download ODIN, and then just follow the directions in the ODIN thread
Click to expand...
Click to collapse
Push doesnt seem to work. Permission denied or something rather.
As I said in my first odin wont work, yes I did those things like 10 or so times.
You cant expect a newborn to know how to wipe themselves.
RPGbig said:
Push doesnt seem to work. Permission denied or something rather.
As I said in my first odin wont work, yes I did those things like 10 or so times.
You cant expect a newborn to know how to wipe themselves.
Click to expand...
Click to collapse
What do you mean "push doesn't work". Are you trying to push a file via adb? If you are getting permission denied errors, that is because you either do not have root access/permissions to write to the location you are trying to push to, or because the location you are trying to push to is mounted as read-only.
If you indeed have the necessary permissions (i.e., root), then `adb remount` will re-mount the device's partitions as read-write. If adb does not allow you remount the partitions in this manner, it is because you do not have the permissions to perform the duty.
If anyone is going to give any further help, though, you need to give us a bit more information. Can you access the device via adb? Can you boot into either download or recovery? (If you have adb access, you can usually boot into either of those with `adb shell reboot download` or `adb shell reboot recovery`.) Have you attempted to flash anything via Odin? What is the exact wording of the error messages you are receiving?
If you don't provide information, you won't receive any help. Vague responses such as "Permission denied or something rather" are useless because something rather can be any number of things. Also, attempting things without reading all of the information available beforehand is another way to ensure that people will be hesitant to give you help; this forum already has threads about where to locate the stock kernel image.
Also, instead of positing what-ifs such as "Anyhow what if my pc doesnt notice the phone when its in download mode", why don't you try putting your device into download mode and attaching it to a Windows computer with the proper drivers installed and Odin running, and then ask what the next step might be after you have attempted to do something?
People get angry about members flaming newbies for posting mistakes and asking for help, but if newbies looked for answers and read all of the information available before doing something they didn't understand (or only partially understood), then this wouldn't be a problem in the first place.
rpcameron said:
What do you mean "push doesn't work". Are you trying to push a file via adb? If you are getting permission denied errors, that is because you either do not have root access/permissions to write to the location you are trying to push to, or because the location you are trying to push to is mounted as read-only.
If you indeed have the necessary permissions (i.e., root), then `adb remount` will re-mount the device's partitions as read-write. If adb does not allow you remount the partitions in this manner, it is because you do not have the permissions to perform the duty.
Click to expand...
Click to collapse
Goalush Clockwork Recovery so I can flash Bionix.
What Happens:
1. Go into recovery
2. Connect to the phone with adb
3. I type 'adb push c:\update.zip /sdcard'
4. It says 'failed to copy `c:\update.zip` to `/sdcard/update.zip` : Permission denied
I type 'adb remount' its says ' remount failed: No such file or directory
rpcameron said:
If anyone is going to give any further help, though, you need to give us a bit more information. Can you access the device via adb? Can you boot into either download or recovery? (If you have adb access, you can usually boot into either of those with `adb shell reboot download` or `adb shell reboot recovery`.) Have you attempted to flash anything via Odin? What is the exact wording of the error messages you are receiving?
Click to expand...
Click to collapse
Yes, I can get into both.
I've download Froyo that doesnt brick. Unziped and got had the drivers from sansumg set up.
I usually type 'adb reboot download' to get into download mode for odin. Then when the phone shows the android guy with the shovel. Then my computer says that an unrecognized usb device has been connect.
This time I type 'adb shell reboot recovery' and its said
'-exce `/system/bin/sh` failed: No such file or directory (2) -'
rpcameron said:
If you don't provide information, you won't receive any help. Vague responses such as "Permission denied or something rather" are useless because something rather can be any number of things. Also, attempting things without reading all of the information available beforehand is another way to ensure that people will be hesitant to give you help; this forum already has threads about where to locate the stock kernel image.
Also, instead of positing what-ifs such as "Anyhow what if my pc doesnt notice the phone when its in download mode", why don't you try putting your device into download mode and attaching it to a Windows computer with the proper drivers installed and Odin running, and then ask what the next step might be after you have attempted to do something?
People get angry about members flaming newbies for posting mistakes and asking for help, but if newbies looked for answers and read all of the information available before doing something they didn't understand (or only partially understood), then this wouldn't be a problem in the first place.
Click to expand...
Click to collapse
RPGbig said:
Goalush Clockwork Recovery so I can flash Bionix.
What Happens:
1. Go into recovery
2. Connect to the phone with adb
3. I type 'adb push c:\update.zip /sdcard'
4. It says 'failed to copy `c:\update.zip` to `/sdcard/update.zip` : Permission denied
Click to expand...
Click to collapse
You have to be rooted.. But why would you even take the hard way to use clockwork? Just download it from the market..?
I have odin with all the files that will get u to stock of ur phone. Also the froyo files does not brick. So now i exactly dont know what u need. go cows
I messed up my phone and its stuck in a bootloop. I want to put that recovery on my phone so I can flash a new rom.
RPGbig said:
I messed up my phone and its stuck in a bootloop. I want to put that recovery on my phone so I can flash a new rom.
Click to expand...
Click to collapse
If your phone is stuck in a bootloop you need to flash your phone with odin
RPGbig said:
Goalush Clockwork Recovery so I can flash Bionix.
What Happens:
1. Go into recovery
2. Connect to the phone with adb
3. I type 'adb push c:\update.zip /sdcard'
4. It says 'failed to copy `c:\update.zip` to `/sdcard/update.zip` : Permission denied
I type 'adb remount' its says ' remount failed: No such file or directory
Click to expand...
Click to collapse
OK, if `adb remount` isn't working properly, then you have to manually instruct the system to remount the system partition as read-write. This is a little different from other Android devices, because Samsung insists on using their screwy RFS. On my device, the system partition resides at /dev/block/st19. If you can get an adb shell session, opened, you can verify it by running `mount`, and seeing which /dev node is assigned to /system. Then, manually remount the system partition with `mount -o remount,rw -t rfs /dev/block/st19 /system`; this must be done as root.
It does seem a bit odd that you are getting a permission denied error on /sdcard. Are you sure that /sdcard is mounted? You can verify the same way you check what /dev node holds you system partition. On my Vibrant, /sdcard is the mount point for /dev/block//vold/179:1 (yes, that is two slashes after block). So, the command to mount the internal SD card is `mount -o remount,rw -t vfat /dev/block//vold/179:1 /sdcard`.
Now those commands should ensure that you have both your system partition and SD card mounted as read-write. Now you can copy over the update.zip that contains ClockworkMod recovery to the root of your SD card (/sdcard) with `adb push drive:\path\to\recovery.zip /sdcard/update.zip`. I recommend specifying a destination filename for update.zip. Also, sometimes an adb push command requires the trailing / of a directory.
RPGbig said:
Yes, I can get into both.
I've download Froyo that doesnt brick. Unziped and got had the drivers from sansumg set up.
I usually type 'adb reboot download' to get into download mode for odin. Then when the phone shows the android guy with the shovel. Then my computer says that an unrecognized usb device has been connect.
This time I type 'adb shell reboot recovery' and its said
'-exce `/system/bin/sh` failed: No such file or directory (2) -'
Click to expand...
Click to collapse
This last statement looks like either your system partition is not mounted, or that it does not have a shell installed. From an adb shell session, check the /system/bin directory and see if there is indeed a shell binary there (either sh itself, or sh linked to another shell such as bash). If there is no /system, then it means that your system partition is not mounted, and you can follow the steps I previously mentioned to mount the system partition.
RPGbig said:
I messed up my phone and its stuck in a bootloop. I want to put that recovery on my phone so I can flash a new rom.
Click to expand...
Click to collapse
Can you boot into recovery using the VOL_DN and POWER method, or does the adb daemon ever come online during the bootloop? If so, then either boot into recovery from a powered-off state, or use the adb shell to boot it into recovery.
http://forum.xda-developers.com/showthread.php?t=810130
rpcameron said:
OK, if `adb remount` isn't working properly, then you have to manually instruct the system to remount the system partition as read-write. This is a little different from other Android devices, because Samsung insists on using their screwy RFS. On my device, the system partition resides at /dev/block/st19. If you can get an adb shell session, opened, you can verify it by running `mount`, and seeing which /dev node is assigned to /system. Then, manually remount the system partition with `mount -o remount,rw -t rfs /dev/block/st19 /system`; this must be done as root.
It does seem a bit odd that you are getting a permission denied error on /sdcard. Are you sure that /sdcard is mounted? You can verify the same way you check what /dev node holds you system partition. On my Vibrant, /sdcard is the mount point for /dev/block//vold/179:1 (yes, that is two slashes after block). So, the command to mount the internal SD card is `mount -o remount,rw -t vfat /dev/block//vold/179:1 /sdcard`.
Now those commands should ensure that you have both your system partition and SD card mounted as read-write. Now you can copy over the update.zip that contains ClockworkMod recovery to the root of your SD card (/sdcard) with `adb push drive:\path\to\recovery.zip /sdcard/update.zip`. I recommend specifying a destination filename for update.zip. Also, sometimes an adb push command requires the trailing / of a directory.
This last statement looks like either your system partition is not mounted, or that it does not have a shell installed. From an adb shell session, check the /system/bin directory and see if there is indeed a shell binary there (either sh itself, or sh linked to another shell such as bash). If there is no /system, then it means that your system partition is not mounted, and you can follow the steps I previously mentioned to mount the system partition.
Click to expand...
Click to collapse
I tried 'adb root' and then it said 'adbd cannot run as root in production builds'
By shell session do you mean 'adb shell'? No, I dont believe that works because I get 'adbd cannot run as root in production builds'
When you mean 'shell installed' you do I have it installed on the phone? If it isnt is there anyway I could do it now?
`adb push drive:\path\to\recovery.zip /sdcard/update.zip` didnt work and gave me 'c:\update.zip' to '/sdcard/update.zip': Permission denied
Can I flash /system via my pc onto my phone? or Use the external sdcard instead of the internal?
Dude, if your phone is stuck in a bootloop, you HAVE TO FLASH IT VIA ODIN. There's no other work-around.
RPGbig said:
I tried 'adb root' and then it said 'adbd cannot run as root in production builds'
By shell session do you mean 'adb shell'? No, I dont believe that works because I get 'adbd cannot run as root in production builds'
When you mean 'shell installed' you do I have it installed on the phone? If it isnt is there anyway I could do it now?
`adb push drive:\path\to\recovery.zip /sdcard/update.zip` didnt work and gave me 'c:\update.zip' to '/sdcard/update.zip': Permission denied
Can I flash /system via my pc onto my phone? or Use the external sdcard instead of the internal?
Click to expand...
Click to collapse
Why did you try `adb root`? I don't quite understand that.
A shell session would be `adb shell`, yes. On your computer's command line, invoke `adb shell`. You are now in a shell session. What does the prompt look like? Is it "#" or "$". If it is a hash, then you have root access via adb. If it is a dollar sign, then you do not have root access; try running `su` from within the shell session. If the prompt does not change to a hash, then you are stuck for the moment, because you do not have root access via adb, and therefore nearly all of the adb commands will not work.
By "shell installed" I was referring to a shell interpreter installed on your handset. bash is the most commonly installed Linux shell, and sh is usually just a pointer to bash. If your handset does not have either /system/bin/sh or /system/bin/bash (or anything similar), then you have an incomplete system, and it got messed up along the way with something you did.
But, since it seems that you cannot gain root access through adb, and therefore cannot (re)mount your partitions, you are basically limited in your options. All you can really do is put your phone in download mode, and use Odin to reflash a complete system (including a kernel image). I would also recommend that you use the repartition option in Odin to make sure that your partitions are reformatted and you are essentially left with a wiped and clean handest to start with.
(Lack of root access via adb has severely limited your options. You are basically left with Odin as your only avenue of recourse, unless you are willing to disassemble your device to get to the internal SD card.)
Have you opened yours? Is it an actual (micro) sdcard that can be taken out like the external one?
I typed 'adb root because typing 'adb' showed this
adb root - restarts the adbd daemon with root permissions
so I guess that was what you ment by root.
When I type 'adb shell' all it gave was - exec '/system/bin/sh' failed: No such file or directory (2) -
You need to stop trying to do it the hard way and just use Odin. If your phone is not being recognized then you need the correct drivers. Once installed, you should be back up and running within 5 minutes. Stop lollygagging and fix your phone already.

[Q] How to root Huawei Mediapad?

Hi,
I've recently purchased a Huawei Mediapad Tablet running honeycomb 3.2.
I would like to root this tablet but am unable to find any guides on the web.
Any pointers and guides would be much appreciated.
Thanks
bump for you interested to know as well
Yeah, I also bought mediapad last 2 weeks, this honeycomb really unstable, hang/reboot very often. And when I switched to full resolution 1280x800, you can feel lagging. Disappointed with stock ROM.
i want to root huawei mediapad su302,please,thanks
Same here...
Just picked on up tonight, not bad hardware but the os needs a kick in the a$$.
Lets get this going people, time is a wasting!
I have beginner modding skills if anyone wants to help me start this?
Recently, I read some reference from some Chinese Forum..
There are Rooted ROMs... and tutorials about how to root by youself..
If you decide to create a rooted rom by yourself..
You need a Linux environment to do that...
Here's how I did mine...
1. First of All, download the latest ROM from Huawei official site..
http://www.huaweidevice.com/worldwide/technicaIndex.do?method=gotoProductSupport&productId=3779&tb=0
2. Unzip it, you'll have a folder "dload"
3. Extract the file" system.img.ext4" from the Update.zip
4. Copy the "system.img.ext4" into your Linux Environment..
5. mount the image file like these...
#mkdir /mnt/tmp
#mount -o loop system.img.ext4 /mnt/tmp
6. put the "superuser" binary into the path /mnt/tmp/xbin
#cp su /mnt/tmp/xbin
7. Assgin the correct permission to the su binary
#chmod 6755 /mnt/tmp/xbin/su
8. Unmount the path and copy the system.img.ext4 into the original Update.zip
#umount /mnt/tmp
9. Put the "dload" folder into the root directory of a Micro-SD
10. Power Up your mediapad, when it vibrates, press and hold Volume Down until you see the Android icon, and it will try to flash the new ROM.
11. After everything is done, Look for Super User from Market, you'll see.
--
For su binary.. you can find it here http://androidsu.com/superuser/
Here's the product of all the above steps...
http://www.multiupload.com/0WPLQILCGH (114.73MB)
(I was using the official ROM dated 26 November..
and Put the su binary Together the superuser app into the system directory.
nothing else I have done to the ROM..)
You can also flash the system.img.ext4 into your mediapad directly via fastboot
to activate the fastboot mode of mediapad..
1. Connect your mediapad to your Computer with USB cable
2. Power up the mediapad with Volume Up button press and hold until your computer sense it and install the correct driver for it.
3. Direct flash your mediapad like this..
fastboot flash system system.img.ext4
then, reboot your mediapad..
you'll have your apps un-touched, while you have the latest system. enjoy~!
--
Fastboot, extracted from the Android SDK..
Many thanks squide, especially for the system image. I was too lazy to break out ubuntu...
I now have a rooted mediapad.
However the command below did not work for me.
squide said:
3. Direct flash your mediapad like this..
fastboot flash system.img.ext4
.
Click to expand...
Click to collapse
I had to use fastboot flash system system.img.ext4
last rom with root + busybox + some app
http://uploading.com/files/53f162e9/dload.rar/
I can now run my favourite titanium backup.
squide said:
Here's the product of all the above steps...
http://www.multiupload.com/0WPLQILCGH (114.73MB)
(I was using the official ROM dated 26 November..
and Put the su binary Together the superuser app into the system directory.
nothing else I have done to the ROM..)
You can also flash the system.img.ext4 into your mediapad directly via fastboot
to activate the fastboot mode of mediapad..
1. Connect your mediapad to your Computer with USB cable
2. Power up the mediapad with Volume Up button press and hold until your computer sense it and install the correct driver for it.
3. Direct flash your mediapad like this..
fastboot flash system.img.ext4
then, reboot your mediapad..
you'll have your apps un-touched, while you have the latest system. enjoy~!
--
Fastboot, extracted from the Android SDK..
Click to expand...
Click to collapse
Thanks. Manage to root my mediapad without losing the installed apps.
Btw use this link to get the fastboot
http://dl.google.com/android/android-sdk_r13-windows.zip
squide said:
5. mount the image file like these...
#mkdir /mnt/tmp
#mount -o loop system.img.ext4 /mnt/tmp
Click to expand...
Click to collapse
Which distro are you using?
I'm having some problems writing to the image after mounting it as a loop back for Ubuntu 10.4
just a question about this device as GSMarena shows GSM support does it mean the you can use it as a phone.
freeko2 said:
just a question about this device as GSMarena shows GSM support does it mean the you can use it as a phone.
Click to expand...
Click to collapse
It's been discussed quite a bit in the Hardwarezone forum. I cannot post a link yet, so just google for 'mediapad hardwarezone forum'.
You need to install the HuaweiMediaPadPhone.apk which you can request from those in the forum. You can also find the link for Mediafire on the forum.
Once you install the apk, you will get the standard Phone and Messaging apps which you can use to make phone calls over GSM and also SMS. Working well for me.
venomrat said:
Many thanks squide, especially for the system image. I was too lazy to break out ubuntu...
I now have a rooted mediapad.
However the command below did not work for me.
I had to use fastboot flash system system.img.ext4
Click to expand...
Click to collapse
Thanks. I had a lab full of Linux systems, so I tried to put the 'su' in myself. Thanks to this fastboot procedure, I have a rooted system with no apps lost.
venomrat said:
Many thanks squide, especially for the system image. I was too lazy to break out ubuntu...
I now have a rooted mediapad.
However the command below did not work for me.
I had to use fastboot flash system system.img.ext4
Click to expand...
Click to collapse
So did you Root it with a PC?
Could you give me some info on how you did this?
I have sdk r13 & fastboot (is 1.img the file I need to flash?)
It's quite easy. just ensure.
1. Your Android SDK is installed correctly
2. Mediapad Fastboot USB driver is detected
3. get the correct system.img.ext4
4. Ensure fastboot works before issuing the flash command
by doing this you would not lose the current installed apps as this would only flash the
updated system plus root binary. After doing so please download superuser from android market
the flash process take less than 10 minutes.
btw i use this command
fastboot flash system system.img.ext4
yup i use a pc to this.
disclaimer:
there's risk of bricking your mediapad. do it at your own risk.
Thanks,
I might try this.
Where can I find system.img.ext4?
DUH!!!! I unzipped the Hauwei firmware folder update.zip and found it - that's the right one right?
---------- Post added at 02:37 PM ---------- Previous post was at 01:55 PM ----------
Also, I don't know if you saw or not, but I lost 4G connection since I originally had a T-Mobile SpringBoard and flashed the Hauwei firmware to it. Do you think rooting it will allow the 4G again? If so, would it be easy for a 'tard like me to do ?
yup that's the right file. I'm using mediapad.
Probably this rom resources file does not have the 4g icon.
Do you still have the same broadband speed?
Can you please verify this using speedtest?
Here's my recent speeds (3G). I wish I would've saved my 4G tests, but didn't realize I was going to loose all of that.
https://skydrive.live.com/redir.asp...372FEF79249B184B!172&authkey=!AHnxi6Q8Yj6srLQ
Also, what do you know about typing ()()2846579()()+ in the calculator. Can anything really be modified here? I've played around with the preferred frequencies and radio bands, but not sure what's really going on. And I think some of it goes back to a default anyway.
I was hoping that something like no 4G icon was the issue, but looking at the speeds (these are test from an area that I know get 4G speeds). I go to:
Settings >Mobile networks>Network operators>Search networks I only see T-Mo and AT&T 2G & 3G

HELP!! Signature verification failed w/ non-official Cyanogenmod 10 ROM for Sanei N10

Hello everyone. Let's see if anybody can help me, because I'm pretty stuck with this.
Note: I've already searched high and low for solutions to the "Signature verification failed", but they either don't work or don't apply here.
I've tried to install the following ROM from xda-developers in a Sanei N10:
Unofficial CyanogenMod 10 for many AllWinner A10 tablets
I've installed it following the usual procedure:
- Press Vol+ and Power to get the Recovery menu
- Select Wipe data/factory reset
- Select Wipe cache
- Install the three ZIP files: "cm10_a10_20120913.zip", "gapps-jb-20120726-signed.zip" & "n10_compatibility_1.2.1.zip"
The problem is, even though the first ZIP with the ROM installs successfully, the second one (the one with Google's apps) refuses to install, showing instead the message "signature verification failed". The same happens with the third ZIP (N10 compatibility).
So the installation doesn't actually finish. If I reboot the tablet, it runs Cyanogenmod 10, but the touchscreen doesn't work (I have to plug a USB mouse to interact with the operating system).
So what do I do to avoid the dreaded "signature verification failed" message? Just in case if it's of any help to identify the problem, I'll mention that I can see the Android bot laying down with a red triangle with an exclamation when entering the Recovery menu.
I've tried to use the ROM Manager which is preinstalled with Cyanogenmod 10, but when choosing "Flash ClockworkMod Recovery" it says that "The SD Card needs to be mounted to use ROM Manager". Of course my MicroSD is properly mounted (I can see its files in the card from console, from the "Terminal Emulator"). I think this happens because the MicroSD is mounted in /storage/sdcard1 instead of in /storage/sdcard0, but I can't change that. I can't download APKs from the browser, either, because it also says something similar about not being able to access the SD (even though it's correctly mounted and can see it mounted from Settings > Storage).
I've also tried the CyanogenMod A10 ROM available in this page, which is more recent (October instead of September):
http://www.slatedroid.com/topic/3870...mod-10-tweaks/
But the same happens.
I've even tried installing the CWM Recovery ROM, but it doesn't let me installing that from the Recovery either (same message about the "signature"), and with Odin3 it doesn't work either because I don't know how to reach the "download mode", which is needed for Odin3. Pressing Vol+ and Power I get the Recovery, but not the Download mode. Does anyone know how do I get to the download mode in the Sanei N10?
Any idea about how to solve this? Right now I have a tablet with no touchscreen and not even Google applications (so I don't even have the Play Store), so it's practically worthless (at least the WiFi works). How can I get this tablet back to being usable?
Did you fix this? I want to get this tablet and most likely want to root and rom it but if this is the case...
benny6812 said:
Did you fix this? I want to get this tablet and most likely want to root and rom it but if this is the case...
Click to expand...
Click to collapse
No, unfortunately I still couldn't fix it
There's nobody here in xda-developers who can help me? Surely somebody must know enough to help me find a solution.
I've tried creating a symbolic link from /storage/sdcard1 to /storage/sdcard (it doesn't exist right now), but it just says "link failed Read-only file system" (I was root, by typing "su" and clicking "Allow" in the Superuser window). So, I can't create symbolic links even while being root user? I need this link so ROM Manager can detect my SD Card (it says it's not mounted but it really is, but in "/storage/sdcard1").
Also, the gapps package linked in the ROM page above seems not to be properly signed, even though it has that "-signed" suffix in its name. I always get that "signature verification failed" error message. But now I've tried downloading a more recent gapps package (gapps-jb-20121011-signed.zip) and that package finally worked! BUT, even though it apparently installed successfully, I still can't see any Play Store icon, nor any other Google app (Gmail, etc.). Why? Those icons should appear after installing gapps, shouldn't they? Maybe this newer "gapps" package is somehow incompatible with this tablet? (is this even possible?).
Also, even though I can now install the newer "gapps" package, I still can't install the "n10_compatibility_1.2.1.zip" file (I still get "signature verification failed" for that ZIP), which, I guess, contains the drivers needed for the N10 so the touchscreen works (currently it doesn't, and I have to use a USB mouse to use Android in this tablet). Any ideas? I'm getting tired of trying 9485738489754935627 things with no good result . I guess Android is showing here its Linux roots...
I think the key here is managing to install a new Recovery ROM that doesn't care about signing, but how do I do that? I can't install through ROM Manager because I get that error about the SDCard needing to be mounted to use it (and it's really mounted), and then I can't create the /storage/sdcard symbolic link because I get that "link failed Read-only file system" error. Also, I can't use Odin3 because I can't manage to put this tablet in Download Mode. Aaaargh! There's no good solution
Any ideas?
Bump!
I have same problem, i think that we need a different compatibility file, or perhaps if we could open install any app like Novo7 we could fix it... hope that anyone have the solution.
Yojimbojpr said:
I have same problem, i think that we need a different compatibility file, or perhaps if we could open install any app like Novo7 we could fix it... hope that anyone have the solution.
Click to expand...
Click to collapse
Thanks for replying. If we could find some way to install a new Recovery, then we'd probably by able to get the N10 Compatibility file working. This can't be that hard to do, but I've tried lots of things, and none of them worked...
Anyone?
Please, someone help!
Bump!
No ideas?
Please, I'm getting desperate
sanei
OMA2k said:
No ideas?
Click to expand...
Click to collapse
same problem here....
jamjamjan said:
same problem here....
Click to expand...
Click to collapse
Please let me know if you find a solution to this. Thanks!
I'm having the same issue with [ROM][CM10/10.1][21 Dec] Codename Lungo
Well, at last I could finally solve the problem thanks to chris5s from this forum.
These are the steps that worked for me:
1. Download the latest ClockWorkMod for Allwinner A10 tablets from here:
http://forum.xda-developers.com/showthread.php?t=1802268
2. Put all three files in the ZIP inside the root of a MicroSD card and insert it in the tablet
3. Check from the Terminal app inside the tablet to see if the MicroSD card is mounted in /sdcard (just type "ls /sdcard").
4. If the "ls" command doesn't show anything (that's what happened in my case), then you must modify the "install-recovery.sh" file and replace all instances of "/sdcard" with "/mnt/extsd".
5. With the proper "install-recovery.sh" file, run the commands specified in the above xda link (in my case the card is in "/mnt/extsd" instead of "/mnt/sdcard" as the original example shows):
su
cd /mnt/extsd
sh install-recovery.sh
sh reboot-recovery.sh
6. The tablet will then reboot to CWM recovery. Then follow the regular steps to install Cyanogenmod (wipe plus install ROM + GApps + Compatibility). This time the Recovery menu won't care about the files being unsigned and will install them right away!
I hope this helps somebody else!
hey i just registered because i have been having the same exact problem i read that you fixed it but how can i get in to the tablet if im not able to do any movements after it boots ???
please any help would be appreciated
Download the file again, and try again
Sent from my GT-N7000 using xda app-developers app
Thatgrass said:
Download the file again, and try again
Sent from my GT-N7000 using xda app-developers app
Click to expand...
Click to collapse
i did i just dont know how to get in to the terminal app
ok so im in the terminal app but what do you mean by modify the install sh file ???
Hello "lesanei"
I just noticed your posts. Let's see if I can help you...
The touchscreen doesn't work because the appropriate drivers were not installed (because of the "signature verification failed" issue). So you need to connect a USB mouse (and preferably a keyboard too) to the tablet. The Sanei N10 should come with a USB to micro-USB adapter. If you don't have it, you can buy it for cheap here.
Since there is only the one USB input in the tablet, you can't connect two USB devices at the same time. What I did use is a wireless mouse+keyboard combo which only needed one USB dongle for reception. If you don't have that, you can just connect a USB mouse and type with the on-screen-keyboard using the mouse. It's annoying, but it works
When I say "modify the install-recovery.sh file", I mean the file inside "cwm_recovery_6.0.1.2_a10.zip". You can modify it from your PC if you prefer. You don't have to do it in the tablet if you don't know how to use the "vi" editor (command line editor). Just open the "install-recovery.sh" file in Wordpad (do not use the Notepad, because it doesn't support Unix line endings so it shows the file incorrectly) and replace all instances of "/sdcard" with "/mnt/extsd". So the file contents should look like this:
#!/system/bin/sh
if busybox test ! -f /mnt/extsd/recovery.img; then
echo no /mnt/extsd/recovery.img
exit 1
fi
cat /mnt/extsd/recovery.img > /dev/block/nandg
sync; sync; sync
echo done
Click to expand...
Click to collapse
Then place all three files ("recovery.img", "install-recovery.sh" and "reboot-recovery.sh") into your MicroSD card. Then safely extract it from your PC, insert it in the tablet and type this from the Terminal:
su
cd /mnt/extsd
sh install-recovery.sh
sh reboot-recovery.sh
Click to expand...
Click to collapse
Then follow the regular steps to install Cyanogenmod and this time all files should install sucessfully, so when rebooting, touchscreen and everything else will work.
Let me know if it works for you.

[Q&A] [TOOL][NABI2] NabiLab - Root, Play, Recovery

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

[GUIDE] Modify your System partition WITHOUT Root

Intro
This is a guide for people who want to make some modifications to config files, or other files, on System partition but do not want to root their phone or install custom recovery in order to keep OTAs and some apps, which don't play nicely with rooted phones, working. Examples of those config mods could be changing DPI or changing volume levels etc, which you would only do once and forget about it.
While root allows you to do those kinds of changes from within android, this methods would require a PC.
If you are familiar with temporary booting into a custom recovery, skip to step 5.
The usual i am not responsible for any of your actions / bricked phones disclaimer applies.
Prerequisites
- A working adb / fastboot environment. Please use Android SDK, if you installed your adb and fastboot using other tools, things might not work, so please just install SDK, install Google USB Driver from SDK manager, install Platform-Tools from SDK manager (should be installed by default) and then add your sdk platform-tools path to your PATH environment variable to have it available in cmd in every path.
- Unlocked bootloader
- TWRP image for you phone (.img) https://twrp.me/devices/huaweinexus6p.html
Follow the [GUIDE] Unlock/Root/Flash for Nexus 6P for that.
Instructions
Here is an example of modifying DPI. I prefer build.prop method of modifying DPI because using the adb wm density command usually caused some issues for me, but modifying via build.prop didn't.
1 - With you phone ON, connect it to the PC and make sure adb is working by running
Code:
adb devices
and making sure that device is listed
2 - Reboot into bootloader. and make sure fastboot is good to go too. Run commands one at a time:
Code:
adb reboot bootloader
fastboot devices
3 - Place your TWRP image file in some easily accessible folder, for the sake of this example i will use C:\Mods.
4 - Temporary boot into TWRP (we are not flashing it here at all).
Code:
fastboot boot c:\Mods\twrp-2.8.7.0-angler.img
Here is where things may not work. If you don't see your phone boot into TWRP then either your adb / fastboot environment not setup correctly (installed via a tool instead of SDK) or your img file is corrupt.
One thing that works for me when TWRP refuses to boot is to restart cmd and issue the command again this closes and reopens adb/fastboot daemon.
5 - Once TWRP is up on your phone it may display a warning saying "TWRP has detected an unmounted system partition". Swipe to allow modifications at the bottom. This screen may not come up at all.
6 - Go to Mount >>> Tick System >>> Make sure "Only Mount System Read Only" is unticked >>> Press Back button
7 - Back on your PC check if your device is listed
Code:
adb devices
8 - Pull the file you need to modify from system partition to your PC. Please note the direction of the slashes:
Code:
adb pull /system/build.prop c:/Mods
9 - Now you should see build.prop in your c:\Mods folder. Use Notepad++ or something like that to edit the file. Find the line with lcd_density= and change it's value to whatever you need and save the file.
10 - Push the file back to your phone:
Code:
adb push c:/Mods/build.prop /system
11 - Reboot
Code:
adb reboot
12 - Profit.
Hope this will help anyone who is looking to do some mods without installing custom recovery and rooting your phone.
Cheers.
Would this work for adding the tethering bypass line in the build prop?
Yes it will. What's the line again I was looking for it the other day and couldn't find it...
Works are per OP's original post, tested and boosted the headphone volume without a problem.
Headphone path is /system/etc/mixer_paths.xml
So as per OP's example to pull: adb pull /system/etc/mixer_paths.xml c:/Mods
push: adb push c:/Mods/mixer_paths.xml /system/etc
I'm using the OP's "Mods" folder to demonstrate the file path but this may vary on your PC.
Can I use this to push SuperSU / etc to my device without having to permanently flash TWRP?
skrowl said:
Can I use this to push SuperSU / etc to my device without having to permanently flash TWRP?
Click to expand...
Click to collapse
You can certainly push the files to system partition and they will retain there after reboot. So if you know which files have to be pushed for SuperSU then give that a go. It shouldn't break anything.
I haven't tried pushing SuperSU files to system partition before so I can't guarantee that OTAs will work after this. The only way to find out is to try it i guess...
Can you run nandroids?
not sure if it's allowed or not.. but with this can i push hosts file onto the phone as well for ad-blocking...?????
I will say thanks now and try it later. These are the type of tweaks I would like to make to my phone. Do you know if changing the DPI cause any stock applications to show up broken like they do on the Samsung phones?
NCguy said:
Can you run nandroids?
Click to expand...
Click to collapse
Im not sure what you mean?
rohit25 said:
not sure if it's allowed or not.. but with this can i push hosts file onto the phone as well for ad-blocking...?????
Click to expand...
Click to collapse
If it's on the system partition then I yes you can.
locolbd said:
I will say thanks now and try it later. These are the type of tweaks I would like to make to my phone. Do you know if changing the DPI cause any stock applications to show up broken like they do on the Samsung phones?
Click to expand...
Click to collapse
I've never had a problem with changing DPI using this method on a nexus phone if that helps.
denk said:
Im not sure what you mean?
Click to expand...
Click to collapse
Can you run nandroids backups from TWRP by just booting into it?
okay so after i did this i get the following during boot up
"Your device is corrupt. It can't be trusted and may not work properly". Does this mean i will not get Securty Updates any more? I saw i had an update before i performed this however, now i do not see that update notifications any more.
locolbd said:
okay so after i did this i get the following during boot up
"Your device is corrupt. It can't be trusted and may not work properly". Does this mean i will not get Securty Updates any more? I saw i had an update before i performed this however, now i do not see that update notifications any more.
Click to expand...
Click to collapse
I got this too when I flashed MOAB via adb sideload. I'm just wondering if the same warning appears with the adb push method. Also, the file's permissions don't need to be set after adb push?
My main concern is if Android Pay still works with the red triangle warning. Anyone?
FYI Flashing back to stock is no issue for me.
NCguy said:
Can you run nandroids backups from TWRP by just booting into it?
Click to expand...
Click to collapse
I think if you get the latest TWRP which supports decryption of data partition (where all your stuff is) you should be able to back it up.
Edit: backup works on nexus 5 with temporary TWRP boot. Sorry I'm still waiting for my 6p to arrive.
locolbd said:
okay so after i did this i get the following during boot up
"Your device is corrupt. It can't be trusted and may not work properly". Does this mean i will not get Securty Updates any more? I saw i had an update before i performed this however, now i do not see that update notifications any more.
Click to expand...
Click to collapse
Thanks for trying it out! Sometimes OTA notifications take a little while to come up after reboot. But based on the warning Im afraid that they might be disabled now. It looks like it runs some sort of a check on the system partition to verify its legitimacy. So modifying files would be fine on it using this method but looks like adding them won't work.
TWRP just released their recovery with decryption support so you can just follow the standard procedure or just temporary booting into TWRP and rooting from there which works as well.
denk said:
I think if you get the latest TWRP which supports decryption of data partition (where all your stuff is) you should be able to back it up.
Edit: backup works on nexus 5 with temporary TWRP boot. Sorry I'm still waiting for my 6p to arrive.
Click to expand...
Click to collapse
On your Nexus5 I assume you are also unrooted? And have you tried a Nandroid restore, booted TWRP, no root?
NCguy said:
On your Nexus5 I assume you are also unrooted? And have you tried a Nandroid restore, booted TWRP, no root?
Click to expand...
Click to collapse
Just ran a restore to test it for you. Works fine as well.
My N5 is unrooted.
.
denk said:
Just ran a restore to test it for you. Works fine as well.
My N5 is unrooted.
.
Click to expand...
Click to collapse
Thanks a lot for that. I didn't unlock the bootloader. Ugh. Time to start over. To me nandroids alone make it worth the effort.

Categories

Resources