There's no G-Slate forum yet, so this goes here.
How to root your T-Mobile G-Slate
This process works under Linux. The hard part under Windows would be mounting a file as an ext4 filesystem, but if you can do that you win.
You need:
The four files in the gslate_root.zip archive attached to this post.
To root:
Put those four files in a directory and open a terminal to there.
Shut down your G-Slate and plug it into your computer via USB.
Hold down both volume buttons and press the power button. The G-Slate will not appear to turn on, but it'll go into APX mode.
Running "lsusb" should show an entry "0955:7820 NVidia Corp."
Run the command "sudo su" to get a root shell. Running "ls" should still show the four files.
./nvflash --bl bootloader.bin --getpartitiontable ptable.txt
./nvflash -r --read 8 system-orig.img
Wait while 400 meg of data copies.
cp system-orig.img system.img
mkdir system
mount -o loop system.img system
cp su system/bin
chmod 4755 system/bin/su
cp Superuser.apk system/app
umount system
./nvflash -r --download 8 system.img
Wait while it copies back.
./nvflash -r --sync
Press the reset button under the sim cover to reboot.
There's your rooted G-Slate. Making that process "one click" is going to suck.
Troubleshooting:
You may need to install the package libstdc++6 or lib32stdc++6 to get nvflash to run.
You may need to use "sudo" on the nvflash commands.
If you want to try to make this work on Windows, the nvflash.exe binary and the APX USB drivers are are available from nvidia.com
This is unbelievable! Can't wait to give it a shot.
EDIT: For future reference, DO NOT use Virtual Box to try and root your device. There are issues getting the drivers to work properly. Lsusb will not work. The following methods have been tested and work:
1. Wubi install of Ubuntu Linux
2. VMware install of Ubuntu Linux
3. Dual-boot install of ""
4. Dedicated Linux box (duh)
And remember: If at first you don't succeed, try try again. Then visit our IRC channel.
Trying this on Windows 7 is gonna be a trip. Never workt with ext4 before.
Install Ubuntu and you can dual boot into Windows or Ubuntu. That's what I do.
Sent from my LG-V909 using XDA Premium App
This method is confirmed working. Thank you so much for the hard work Chandon. It wasn't very hard to complete on Linux. I can't believe my G-Slate is rooted!!!! Hell yes! Oh and the device is not wiped during the process either just to let everyone know!
Some More Help
Would it be possible to pull the recovery partition off now?
Why I ask. I am in a bit of a pickle. My slate will get to the first LG boot screen and then freeze. It does not even go to the boot animation. I can still get into fastboot and APX mode and it is seen by my computer.
How did i get here. While poking around in fastboot I am pretty sure i wiped they recovery partition D'OH.
I was able to complete the steps listed (for root) with out issue but still cannot get past the boot screen since this is only modifying the system partition.
I am thinking that if that could be pulled from the device i could flash it to mine and bring my slate back to life?
Am I way off on this one?
SmellyTunic -
Attached are all the reasonably small partitions that I could pull off my device with nvflash. This should be everything except /system, /cache, and /data.
I suggest backing everything up before flashing any of these, on the off chance that there's some difference between devices.
Thanks so much for this! Is there a good linux live cd(or bootable usb flash drive) someone could suggest where this could be accomplished easily? Not ready to take the plunge actually installing linux on my system yet >.>
Here you go
shinkinrui
Info and steps can be found here http://www.ubuntu.com/download
Pretty easy to set up a dual boot machine.
Chandon,
Any chance you know off hand which one of those partitions is the recovery?
I suggest doing a Wubi install [1], where Ubuntu pretends to be a Windows app (which you can then uninstall like any other app later). Alternatively you could try using VirtualBox [2], but that's less guaranteed to work.
The only reason I wouldn't do this with a Live CD is that you'd risk losing your backup of the stock /system partition when you reboot. It would also make losing power in the middle of the flash really annoying.
[1] https://wiki.ubuntu.com/WubiGuide
[2] (edit: virtual box doesn't easily see the USB device)
Thanks guys, reading about that Wubi solution looks like the simplest way to have a dual-boot system. I like it! I'll be getting my root on later tonight
i prefer Ubuntu just cause you can install it in windows then simply restart and boot into Linux or Windows. This way you don't need to worry about not having Linux again.
SmellyTunic said:
Any chance you know off hand which one of those partitions is the recovery?
Click to expand...
Click to collapse
I'm sure that /system is 8 and the kernel is 13, but don't know about anything else. You might be able to figure it out by reading the ptable.txt file generated by the --getpartitiontable command - it's pretty clear except for the part where it uses 3 letter partition names.
Thanks. I will take a look when i get home from work.
Sent from my GT-I9000 using XDA App
While we are on the topic of development, we really need a forum over here at XDA for the G-Slate!
deez1234 said:
While we are on the topic of development, we really need a forum over here at XDA for the G-Slate!
Click to expand...
Click to collapse
I definitely concur.
thengkiu so much
works like a charm
I have no idea why I'd ever need/want to root my G Slate, I'm fairly simple in my desires for my device - but I have to say I'm delighted to see it is possible and am ever so grateful for folks who figure this stuff out because it keeps moving G Slate towards legitimacy.
Thank you!!
The hard part under Windows would be mounting a file as an ext4 filesystem, but if you can do that you win.
Click to expand...
Click to collapse
No kidding. Since the linux method failed miserably for me, I've decided to press forward with trying to do it on Windows. Problem is, I have yet to find any way to mount an ext4 filesystem on Windows. There are several options out there that will allow you to read ext4 filesystems on Windows, but not write. Any suggestions?
my friend will be happy to see that this is possible.
Does anybody know of a way to fsck the system or data partitions? I've run into a few times where I had data errors on /data, and the only way I could think of to fix them was to do a backup and restore. I was worried about losing data during the backup process, as the filesystem was already questionable.
I have e2fsck in my rom, but I can't run it from a normal shell as the filesystems are already mounted. Is there a way to make a rom automatically check and repair the filesystems on boot, and if so, how can I control the options it passes to fsck? Are there other ways to get to an unmounted system or data partition? Does clockworkmod have any kind of shell or fsck utilities built in? Are there other recovery programs that may have something like that?
You should be able to boot into CWM, unmount the partitions, connect with adb and run it from there. At least if your version of CWM has fsck in it.
Sent from my SPH-D700 using xda premium
You should be able to do it while booted into recovery through ADB.
Boot to recovery
connect usb cable to PC
run `adb shell`
Code:
unmount /data
unmount /system
fsck /dev/block/stl9
fsck /dev/block/stl10
syntax for above commands needs to be checked.
toadlife said:
You should be able to do it while booted into recovery through ADB.
Boot to recovery
connect usb cable to PC
run `adb shell`
Code:
unmount /data
unmount /system
fsck /dev/block/stl9
fsck /dev/block/stl10
syntax for above commands needs to be checked.
Click to expand...
Click to collapse
Just tried this out myself. Here's the correct syntax for the fsck command:
Code:
e2fsck -fv /dev/block/stl10
EDIT: Forgot to mention also that unmount should actually be umount. Or you could just use the CWR menus to unmount partitions.
zman0900 said:
Just tried this out myself. Here's the correct syntax for the fsck command:
Code:
e2fsck -fv /dev/block/stl10
Click to expand...
Click to collapse
How bout mtd?
sent from my always aosp epic
Please consider posting questions in Q&A next time. Thank you.
Sorry for the "newbie spam"! But that worked perfectly - I didn't realize that adb shell worked when booted from cwm. That's exactly what I was looking for.
zman0900 said:
Just tried this out myself. Here's the correct syntax for the fsck command:
Code:
e2fsck -fv /dev/block/stl10
EDIT: Forgot to mention also that unmount should actually be umount. Or you could just use the CWR menus to unmount partitions.
Click to expand...
Click to collapse
Thanks for this, this is why i love xda!
I have e2fsck in my /bin
On a samsung galaxy s2 i9100
How do i identify my /system & /data blocks
I cant remember how to find out!
So mine would be
e2fsck -fv /dev/block/????
Thanks
Colliebudz said:
Thanks for this, this is why i love xda!
I have e2fsck in my /bin
On a samsung galaxy s2 i9100
How do i identify my /system & /data blocks
I cant remember how to find out!
So mine would be
e2fsck -fv /dev/block/????
Thanks
Click to expand...
Click to collapse
If you run mount with no arguments, it will show a list of mounted partitions like "xxx on /system".
Colliebudz said:
Thanks for this, this is why i love xda!
I have e2fsck in my /bin
On a samsung galaxy s2 i9100
How do i identify my /system & /data blocks
I cant remember how to find out!
So mine would be
e2fsck -fv /dev/block/????
Thanks
Click to expand...
Click to collapse
Better to do /dev/block/platform/(your processor)/by-name/xxxx. Less chance of error
Colliebudz said:
Thanks for this, this is why i love xda!
I have e2fsck in my /bin
On a samsung galaxy s2 i9100
How do i identify my /system & /data blocks
I cant remember how to find out!
So mine would be
e2fsck -fv /dev/block/????
Thanks
Click to expand...
Click to collapse
the easiest was to find what /system and /data mount points actually are
cat /etc/fstab
to see a list of mount points.
toadlife said:
You should be able to do it while booted into recovery through ADB.
Boot to recovery
connect usb cable to PC
run `adb shell`
Code:
unmount /data
unmount /system
fsck /dev/block/stl9
fsck /dev/block/stl10
syntax for above commands needs to be checked.
Click to expand...
Click to collapse
How do I get the Moto X in Recovery mode to accept the adb command?
Because when I put in Recovery (Android Robot lying down) mode, the command adb and fastboot are not recognized.
rod.gui said:
How do I get the Moto X in Recovery mode to accept the adb command?
Because when I put in Recovery (Android Robot lying down) mode, the command adb and fastboot are not recognized.
Click to expand...
Click to collapse
Flash a custom recovery first. (CWM/TWRP)
Sent from Motorola Photon Q 4G LTE @ CM11
My phone is Huawei G525. It doesn't have CWM or any custom stuff, just rooted.
My problem is that it reports an imagic flagged inode and it recommends to fsck the partition (/system). The logs are saved in sdcard folder.
I can use adb and fastboot, but fastboot shell doesn't work and /system is mounted when i can use adb.
Is there any solution for me to run e2fsck on /system partition?
Or is there the case to worry about that error? The phone works fine...no random reboots, no crashes, no force closes.
Another thing...I've tried to make a romdump and system archive is damaged. Cannot be opened even with 7-zip.
mandgeo said:
My phone is Huawei G525. It doesn't have CWM or any custom stuff, just rooted.
My problem is that it reports an imagic flagged inode and it recommends to fsck the partition (/system). The logs are saved in sdcard folder.
I can use adb and fastboot, but fastboot shell doesn't work and /system is mounted when i can use adb.
Is there any solution for me to run e2fsck on /system partition?
Or is there the case to worry about that error? The phone works fine...no random reboots, no crashes, no force closes.
Another thing...I've tried to make a romdump and system archive is damaged. Cannot be opened even with 7-zip.
Click to expand...
Click to collapse
G525 DOES have CWM recovery available, find and install one so that you can fsck from recovery using adb.
Sent from Google Nexus 4 @ CM11
AndyYan said:
G525 DOES have CWM recovery available, find and install one so that you can fsck from recovery using adb.
Sent from Google Nexus 4 @ CM11
Click to expand...
Click to collapse
As far as I understand from here... http://bbs.dospy.com/thread-16432606-1-823-1.html , the bootloader needs to be unlocked. I've submitted for an update code and i'll wait. The chinese guy talks about U8950, but there are five different types. I've selected the first one, U8950-1. Maybe i'm lucky.
I've also tried to boot directly into the recovery found here... http://www.needrom.com/mobile/huawei-g525-u00/ , but that command is not allowed, maybe because the bootloader is locked. That was the only recovery i found that seems to be in english.
I'll try the same procedure to boot into recovery (fastboot boot recovery.img) because i don't want to mess things more that they are. I didn't found any tutorial in english and google translate is confusing.
Thanks!
LE. Does anybody know if Huawei rewrites the custom recovery if it's not the stock one.
mandgeo said:
As far as I understand from here... http://bbs.dospy.com/thread-16432606-1-823-1.html , the bootloader needs to be unlocked. I've submitted for an update code and i'll wait. The chinese guy talks about U8950, but there are five different types. I've selected the first one, U8950-1. Maybe i'm lucky.
I've also tried to boot directly into the recovery found here... http://www.needrom.com/mobile/huawei-g525-u00/ , but that command is not allowed, maybe because the bootloader is locked. That was the only recovery i found that seems to be in english.
I'll try the same procedure to boot into recovery (fastboot boot recovery.img) because i don't want to mess things more that they are. I didn't found any tutorial in english and google translate is confusing.
Thanks!
LE. Does anybody know if Huawei rewrites the custom recovery if it's not the stock one.
Click to expand...
Click to collapse
Well, you know this forum is dedicated for discussion about Samsung Epic 4G, not Huawei G525... But to help you out I might be able to dig in a bit more later this week when I have time. I'm a Chinese myself and can (hopefully) understand these procedures.
Sent from Google Nexus 4 @ CM11
AndyYan said:
Well, you know this forum is dedicated for discussion about Samsung Epic 4G, not Huawei G525... But to help you out I might be able to dig in a bit more later this week when I have time. I'm a Chinese myself and can (hopefully) understand these procedures.
Sent from Google Nexus 4 @ CM11
Click to expand...
Click to collapse
My phone is a Note 2 LTE N7105 - I realise not the same as this thread, but this is the only thread I have found that is discussing this. My /data partition needs an fsck, however, while I can adb to the phone when it is booted, I can't when it is in recovery.
I have TWRP 2.7.1.0 installed, and everything else works fine. When the phone is booted, I get the GT-N7105 driver appearing in portable devices in device manager, but when recovery is booted, I just get t0lte in "other devices".
Seems like the Samsung USB driver only works when the phone is properly booted, and doesn't match when booted to recovery.
Any ideas how to work around this?
paulkoan said:
My phone is a Note 2 LTE N7105 - I realise not the same as this thread, but this is the only thread I have found that is discussing this. My /data partition needs an fsck, however, while I can adb to the phone when it is booted, I can't when it is in recovery.
I have TWRP 2.7.1.0 installed, and everything else works fine. When the phone is booted, I get the GT-N7105 driver appearing in portable devices in device manager, but when recovery is booted, I just get t0lte in "other devices".
Seems like the Samsung USB driver only works when the phone is properly booted, and doesn't match when booted to recovery.
Any ideas how to work around this?
Click to expand...
Click to collapse
Yes, the workaround is to not use stupid Windows.
Works fine on linux.
run terminal app:
su
touch /forcefsck
Then reboot. It might depend on your ROM, but give it a go.
First, let me define "bricked". When I say bricked, I mean it doesn't boot past the acer logo, only stops there, recovery can be attempted, but seems to always fail loading update.zip in stock recovery, or can not mount anything in custom recovery (CWM so far, haven't seen TWRP do this yet).
Updates will be listed here.
Updated 6-27:
-Added fstab, ideas and theories that I have so far, and a list of things I have noticed so far in various threads.
Updated 8-14-13:
-Added a link to a massively helpful thread concerning the Samsung Brick Bug, which is apparently what we also have. Well, the firmware of our EMMC has.
-Updated the "things to try" section in post 3 with updated information and tactics.
Ok, calling in all owners with Bricked A100s, the information for this is scattered all around multiple threads, and I would like to compile a list into 1 central thread for past and present bricked A100 owners.
Please post in with the following information if available:
Date of purchase (it can be a rough guess if you don't know)
ROM it was running, was it stock acer OTA update ICS, modded stock, CM9 etc
Did you flash and unlock the bootloader, if so, where did you get it?
Did you flash and use a custom recovery, if so, where did you get it? CWM, or TWRP?
Did you have any freezes, random reboots, odd behaviour before the brick?
Did you hard reboot (use the reset button, or hold the power button)?
Did you run a custom kernel (ezterry or any others) or stock kernel?
Did you overclock, if so what was max, and did you undervolt, if so, how low?
What have you done since the brick, any wipes, roms you've attempted to use as update.zip, any flashes attempted.
The above is no longer needed, we know now that it occurs on any and all kernels/roms and any combination of either.
I'll compile the results in the second post, and hopefully someone can maybe make more sense then I can of what is occuring.
Things I have noticed compiling data from all the threads and posts about bricking I have seen:
The brick will eventually occur regardless of the Android version or kernel installed, HC, ICS, JB, no version is any safer then another, though HC seems to take much longer to happen.
It appears to be corruption or otherwise loss of access to the GPT, which stores the partition information, as this is damaged the tablet no longer knows where to find a partition, so it fails to mount (partition here).
All reports are usually prefaced by some sort of freeze and a hard reboot to brick.
Partitions always fail to mount.
Partitions that failed to mount one try will rarely mount another (cache/recovery have done this)
Flashing different recoveries seems to make no difference in mounting.
Fastboot does seem to still work provided the bootloader is intact. It allows flashing of recovery.
CPUID> SBK doesn't work. I had figured it was our flashed bootloaders, but it seems to fail on stock bootloaders as well. Likely A100 uses a different key then A500.
Happens even on completely stock, unrooted, untouched Acer HC or ICS.
adb shell cat /sys/devices/platform/sdhci-tegra.3/mmc_host/mmc0/mmc0:0001/name shows that our EMMC is M8G2FA, and mine in particular was revision 0xB, which bricked. This can also be checked with the Got Brick Bug? app for Samsung devices, while it won't tell you accurately if you are going to brick, it will give you this information as well.
After some discussion with WDS from the CM9 team, there was a rash of these bricks on other devices as well, and seemed to be the result of a bad batch of EMMC chips, or controllers for it, that caused corruption and failure to be read from or written to. The solution was difficult, but obtainable, with NVFlash to partition around the bad area, leaving itself a separate partition for itself, an island away from the rest. Difficult and time consuming, this is not an option for us as we can NOT use NVFlash at all, we can't pass the bootloader verification for NVFlash access. Either the A100 key needs leaked or released, or Acer needs to allow us to fully unlock the bootloader (no encryption anymore) for NVFlash to be an option.
This leaves us with simple tools, ADB and Fastboot, which as long as you can get to the Acer screen, you can use.
ADB doesn't give us an out right way to create, move, delete, and modify partitions, just what is on an existing partition. So, we can use tools like DD to read from and write to any given partition, as long as the device know it exists, and is functioning within that range. If the data corruption is in say, /system, and it exists within the range of the OS, then it will not work. If it exists just outside of the OS, but then gets accessed later during usage, then it will fail. Same for any partition it may have corruption or bad sectors in, it could be any partition anywhere at anytime.
Here is a massively useful thread concerning the Samsung bug, but seems to be pretty much what we have going on ourselves.
http://forum.xda-developers.com/showthread.php?t=1644364
Filesystem Table (taken from recovery)
-------------------------------------------------------------------------------
Mount Point Filesystem Device Partition
-------------------------------------------------------------------------------
/system | ext4 | /dev/block/mmcblk0p3
/data | ext4 | /dev/block/mmcblk0p8
/cache | ext4 | /dev/block/mmcblk0p4
/misc | emmc | /dev/block/mmcblk0p5
/flexrom | ext4 | /dev/block/mmcblk0p6
/sdc | vfat | /dev/block/mmcblk1p1
/boot | emmc | /dev/block/mmcblk0p2
/recovery | emmc | /dev/block/mmcblk0p1
/sd-ext | ext4 | /dev/block/mmcblk1p2
cat /proc/partitions gives this:
------------------------------------------------------------------------------
major minor #blocks name
179 0 7815168 mmcblk0
179 1 6144 mmcblk0p1
179 2 8192 mmcblk0p2
179 3 614400 mmcblk0p3
179 4 1253376 mmcblk0p4
179 5 4096 mmcblk0p5
179 6 102400 mmcblk0p6
179 7 10240 mmcblk0p7
179 8 5801984 mmcblk0p8
179 32 31166976 mmcblk1
179 33 31162880 mmcblk1p1
*Note*
While is says /data is EXT4, I think it's actually EXT3, but since it shares with internal SD as /data/media, that may be why it shows EXT4 in some places and EXT3 in others.
EMMC filesystem partitions can't be read by normal means, they don't have a true filesystem.
VFAT is any FAT/FAT32 formatted device, so external SD shows up as VFAT.
I'm pretty certain this is not complete, there are partitions that don't show up under normal usage, so there may be hidden partitions on the device.
Ideas or theories I have and things to try
I'm pretty well convinced we suffer from bad EMMC, that corruption I mentioned in post 2. However, it could also be something as simple as the partitions get scrambled, and while they are there, they can't mount due to being damaged, so I have a few things I wanted to try (hence my request for a loaned or donated bricked A100 for testing in another post I made).
1. DD system and cache partitions, the entire thing, from a working device. (done, I did this on my own tab)
2. DD the image back to a bricked A100, since cache almost always fails to mount, DD cache.img to it (haven't tried yet, don't have a bricked unit)
3. If DD fails, check where it is failing at, it will report records in/out, however DD doesn't handle bad sectors well, and may just hang.
4. If DD fails, and doesn't return a records in/out summary (hangs) attempt fastboot flash cache cache.img (requires a mounting SD card)
5. If DD fails, and external SD is NOT mountable, then ADB Shell is out, and requires launching from adb dd, which I haven't found a way to do yet. (DD would use the image from PC, not SD)
6. If DD is completely out, and fastboot can't flash either, we'll need to work on the partitions directly, using parted or some other tools that can modify the partitions, which is beyond my abilities.
All unsuccessful.
JTAG may or may not work, as it has been mentioned that even JTAG will fail to write to the EMMC with its damaged section. At this point there is only 2 possible methods that may work:
1. Motherboard replacement. Either Acer under warranty (or out of warranty if you can get your case elevated, some users report this being possible) or you replace it yourself. It's not terribly difficult, and I can probably even make a video of it if needed.
2. Someone with a reflow station may be able to remove the EMMC from the board and replace it with a non damaged unit. This place would require a method to read/dump a good chip and be able to write this back to the new one, we can not just NVFlash a system back onto the system. I don't suggest anyone with a hair dryer or heatgun attempt this. The cost for this may be high, but maybe a deal can be worked out of a shop or person is willing to take on this job, as there are TONS of dead A100s around (and A210 appears to be prone to it also, way to go Acer!)
Prevention:
There is currently no way to prevent this, however I have begun modifying Samsung's firmware patch to maybe work with our boards. This isn't something I'm good at, or even know what I'm doing, so it may work, or may not. Information can be found in the newly included link about the brick bug in post 1, however the rundown is this: Every power up (not reboot, power on) the kernel will run a check against the model and revision of the EMMC, if it falls into a given range, then it will attempt to bypass the erase functions of the EMMC firmware so it will, idealy, not write that 32 byte section of 0s causing the EMMC to crash. If it doesn't match, then it does nothing. It's originally written for Samsung devices, of course, so requires reworking for the A100, but it may work, it may not.
I purchased it in December.
It was running the first ZeroNull MOD.
Yes, I unlocked the bootloader with a method found here.
I flashed CWM with a method found here and I used it only for backing up and for flashing the mod.
Only hardly ever it random rebooted.
I was running stock kernel, and I never overclocked/undervolted.
I tried to Wipe cache and to mount all the mountable from recovery. Nothing happened.
Oh, last thing: my tab passes the Acer green logo, but it doesn't pass this:
{
"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"
}
Please, help me!
ok i have an a100 that is bricked wont boot past acer logo screen. Recovery says mmcblk0p5 is screwed and before i flashed to stock recovery cwm said mmcblk0p4 was screwed. I have a fully functional a100 with me too made backups mmcblk0p1-mmcblk0p7 and tried restoring them one by one. Some work and restore ok but others give errors. I have used this partiton table to try and attempt and restore thanks to smokku. Last night I somehow flashed the wrong img to the wrong partiton and went to recovery through update.zip in stock recovery and it actually made progress about 1/3 of the way through. It has never done that before and I wished I had given it more time to complete but it was late so I gave up. I dont have the cpuid so Im stumped. Any insight would be great as this tablet is my nephews. I guess I could make a claim with acer but then I'd be out my tablet while his is being fixed. Somehow his less than 3 month old 32gb sdcard died when the tablet died too. Thanks
Coming from cm-9-26-21-b11-a100-pm with unlocked bootloader and cwm 5.5.0.4 with ezterry
Tablet had problem with play store 921 error 3 days ago I then fixed the play store and the tablet worked fine. 3 days later the battery ran out and he recharged it to never boot again.
I have v.03.06-ics unlocked bootloader and can access fastboot and adb too but partitons are borked beyond my recovery skills
/dev/block/mmcblk0p1 SS recovery (/etc/install-recovery.sh)
/dev/block/mmcblk0p2 LX boot (boot.img)
/dev/block/mmcblk0p3 AP /system ext4
/dev/block/mmcblk0p4 CC /cache ext4
/dev/block/mmcblk0p5 MC misc
/dev/block/mmcblk0p6 FX /system/vendor ext4 (flexrom.img)
/dev/block/mmcblk0p7 AB APK (p1 and p2 signatures)
/dev/block/mmcblk0p8 UA /data ext4
Ok I'm going to ask one thing, please include all of the information I requested in the first post, it will help alot in figuring out all possible causes.
Well, ok two things, second is if you have CWM or TWRP custom recoveries, please do not flash stock recovery. If you do, we only have APX mode, which we can't use, and fastboot, which is basic flashing, no real tools to use for figuring this out. CWM and TWRP will have ADB abilities, which we need the tools for.
I'll be including the full filesystem table in the third post, which will show the device partitions and where they mount do. It will help with flashing images to the proper partitions. I'll try to have that included pretty soon.
EDIT: brendan802 Says ADB does still work in stock recovery, so my above message may not be true.
Ok I flashed back to cwm 5.5.0.4 through fastboot.
Funny thing is even on the acer loading screen I can still access adb with stock recovery. I have been trying to get fastboot update update.zip to work with no success. I have rewritten all partitons I can through fastboot with no luck. I think the partiton tables need to be rewritten through adb somehow or through apx mode but the cpuid is no longer attainable
brendan802 said:
Funny thing is even on the acer loading screen I can still access adb with stock recovery. I have been trying to get fastboot update update.zip to work with no success. I have rewritten all partitons I can through fastboot with no luck. I think the partiton tables need to be rewritten through adb somehow or through apx mode but the cpuid is no longer attainable
Click to expand...
Click to collapse
CPUID doesn't matter for our devices, the SBK isn't valid for A100s.
Fastboot doesn't rewrite partitions, just dumps the information to the partition, if the partition fails to mount, it can't do anything with it anyways.
Thanks for letting me know stock recovery allows ADB, I wasn't aware of that. I'm going to try talking to morfic and faux about using parted to manually partition the device, hopefully it means we can rebuild the partitions completely, and get the system to mount then correctly, then we can start on what caused it.
pio_masaki said:
After some discussion with WDS from the CM9 team, there was a rash of these bricks on the A500 as well, and seemed to be the result of a bad batch of EMMC chips, or controllers for it, that caused corruption and failure to be read from or written to. The solution was difficult, but obtainable, with NVFlash to partition around the bad area, leaving itself a separate partition for itself, an island away from the rest.
Click to expand...
Click to collapse
Misinformation,
I was talking about the G2 (Desire Z/Vision) & it was a problem also affecting the MT4G/DHD & others.
There was no solution
waydownsouth said:
Misinformation,
I was talking about the G2 (Desire Z/Vision) & it was a problem also affecting the MT4G/DHD & others.
There was no solution
Click to expand...
Click to collapse
Ah I apologise I thought you were talking about the A500, my bad. I'll edit that to be little more accurate. However I have read about partitioning around the corruption on the A500 with NVFlash, so I know thats possible. Well, given almost ideal circumstances it is.
brendan802 said:
Funny thing is even on the acer loading screen I can still access adb with stock recovery. I have been trying to get fastboot update update.zip to work with no success. I have rewritten all partitons I can through fastboot with no luck. I think the partiton tables need to be rewritten through adb somehow or through apx mode but the cpuid is no longer attainable
Click to expand...
Click to collapse
As you seem to have a working ADB, would it be possible for you to boot to recovery, and using adb do this:
adb shell cat /proc/partitions
then copy it out and paste it in a post, then
adb shell cat /proc/cmdline
also copied into a post here
It can then be compared to a working device (mine) and see if anything is different.
For anyone on the stock bootloader, please do the same commands and report them back. It seems we used the A200 bootloader, which may be leading to this, or at least why the SBK fails. Also for any reponses, please include the recovery and if your bootloader was unlocked.
pio_masaki said:
Thanks for letting me know stock recovery allows ADB, I wasn't aware of that. I'm going to try talking to morfic and faux about using parted to manually partition the device, hopefully it means we can rebuild the partitions completely, and get the system to mount then correctly, then we can start on what caused it.
Click to expand...
Click to collapse
No thanks for all of your knowledge and support. I am giving this tab 1 more day and if I cant restore its going back to acer. I still dont understand how the recovery started actually showing the blue progress bar on the bottom instead of an immediate red triangle. I sent the wrong command with the wrong image I think something similar to this "fastboot flash ext4 mmcblk0p4.img" or mmcblk0p5.img and of course it errored due to size mismatch but then I was able to start to flash update.zip through recovery. Still baffles me
---------- Post added at 09:55 PM ---------- Previous post was at 09:50 PM ----------
Here is my output:
C:\android-sdk\platform-tools>adb shell cat /proc/partitions
- exec '/system/bin/sh' failed: No such file or directory (2) -
C:\android-sdk\platform-tools>adb devices
adb server is out of date. killing...
* daemon started successfully *
List of devices attached
0123456789ABCDEF device
C:\android-sdk\platform-tools>adb shell cat /proc/partitions
adb server is out of date. killing...
* daemon started successfully *
- exec '/system/bin/sh' failed: No such file or directory (2) -
C:\android-sdk\platform-tools>
C:\android-sdk\platform-tools>adb shell cat /proc/cmdline
- exec '/system/bin/sh' failed: No such file or directory (2) -
C:\android-sdk\platform-tools>adb devices
adb server is out of date. killing...
* daemon started successfully *
List of devices attached
0123456789ABCDEF device
C:\android-sdk\platform-tools>
brendan802 said:
No thanks for all of your knowledge and support. I am giving this tab 1 more day and if I cant restore its going back to acer. I still dont understand how the recovery started actually showing the blue progress bar on the bottom instead of an immediate red triangle. I sent the wrong command with the wrong image I think something similar to this "fastboot flash ext4 mmcblk0p4.img" or mmcblk0p5.img and of course it errored due to size mismatch but then I was able to start to flash update.zip through recovery. Still baffles me
---------- Post added at 09:55 PM ---------- Previous post was at 09:50 PM ----------
Here is my output:
C:\android-sdk\platform-tools>adb shell cat /proc/partitions
- exec '/system/bin/sh' failed: No such file or directory (2) -
C:\android-sdk\platform-tools>adb devices
adb server is out of date. killing...
* daemon started successfully *
List of devices attached
0123456789ABCDEF device
C:\android-sdk\platform-tools>adb shell cat /proc/partitions
adb server is out of date. killing...
* daemon started successfully *
- exec '/system/bin/sh' failed: No such file or directory (2) -
C:\android-sdk\platform-tools>
C:\android-sdk\platform-tools>adb shell cat /proc/cmdline
- exec '/system/bin/sh' failed: No such file or directory (2) -
C:\android-sdk\platform-tools>adb devices
adb server is out of date. killing...
* daemon started successfully *
List of devices attached
0123456789ABCDEF device
C:\android-sdk\platform-tools>
Click to expand...
Click to collapse
Odd, this is the exact same issue I just ran into. I actually kinda bricked my device earlier today, but besides that, I was testing a Jellybean build, and it was giving these exact same errors. Basically, you have no /system, or rather, nothing there. That would certainly explain why there is no booting.
This was done in bootloader, or in recovery? If this wasn't in recovery, please try there. The other option we can try is I'll upload my system.img, which IIRC has CM9, but its a full partition image, 1.2GB. Since you seem to have access to fastboot, you can do a fastboot flash system system.img and see what it does. If it still can't work, I guess you can see if DD will work in recovery, but it would need external sd to be mountable.
Also, that CPUID is interesting. As in, that isn't close to right lol
Ive already flashed a full system backup from a working a100 with no luck in fastboot. Recovery gives nothing but mount errors. I guess I need to find a way to replace the unlocked bootloader with the original locked one and send it to acer. I do appreciate your help though.
brendan802 said:
Ive already flashed a full system backup from a working a100 with no luck in fastboot. Recovery gives nothing but mount errors. I guess I need to find a way to replace the unlocked bootloader with the original locked one and send it to acer. I do appreciate your help though.
Click to expand...
Click to collapse
I think dd a full partition in adb would give better results then a data only flash but its just a theory. Thanks for taking the time to test some stuff out for us
Tapatalked from my Galaxy S II.
Bootloader v.0.03.06-ICS
TWRP Recovery
This is my output:
C:\android-tools>adb shell
~ # cat proc/partitions
cat proc/partitions
major minor #blocks name
~ # cat proc/cmdline
cat proc/cmdline
tegraid=20.1.4.0.0 [email protected] vmalloc=256M video=tegrafb [email protected]
x3db3d000 console=none usbcore.old_scheme_first=1 [email protected] brand=
acer tegraboot=sdmmc gpt
~ #
I have access to fastboot too. But I tried everything I found on the forum without good results :crying:
LeRx79 said:
Bootloader v.0.03.06-ICS
TWRP Recovery
This is my output:
C:\android-tools>adb shell
~ # cat proc/partitions
cat proc/partitions
major minor #blocks name
~ # cat proc/cmdline
cat proc/cmdline
tegraid=20.1.4.0.0 [email protected] vmalloc=256M video=tegrafb [email protected]
x3db3d000 console=none usbcore.old_scheme_first=1 [email protected] brand=
acer tegraboot=sdmmc gpt
~ #
I have access to fastboot too. But I tried everything I found on the forum without good results :crying:
Click to expand...
Click to collapse
This is a little scary, yet exactly what I was expecting. There is no partition table, at all. Unless you happened to not paste the output of cat /proc/partitions.
The other thing I noticed, in cat /proc/cmdline, there is no bootloader listed. Also, no CPUID, which is alot bootloader related. So, this explains why SBK fails, partially I think due to us using A200 bootloaders, and partially because if the bootloader is fubar, it won't pass anyways.
So we're left with either the EMMC corrupted or failed, and took the partitions with it, or its a bootloader issue, as it doesn't show up. Of course, its entirely possible the bootloader partition is also lost, which means it can't boot past the initial boot stage, the acer screen. Also explains why nothing can be mounted, but it strikes me as a little odd that recovery DOES work, but also doesn't show up in the partition list, even while IN recovery. I mean recovery runs from RAM, but it loaded from somewhere, right?
Only other option I can suggest, at least for you, LeRx79, is to flash the bootloader blob again. Fastboot will dump whatever to where ever you point it to, but doesn't mean it can actually flash it, if the partition is missing, or invalid, then it can't write to that partition, it doesn't exist.
If you still have the tools from when you unlocked the bootloader, try this:
adb reboot bootloader
fastboot flash bootloader whateverblobfileyouused
And report back if it fails, or does it, and actually attempts to boot again, and please do
adb reboot recovery
adb shell
adb cat /proc/partitions
adb cat /proc/cmdline
and see if they change.
I've got an error when I try to flash the bootloader:
FAILED <remote: <00030003>>
LeRx79 said:
I've got an error when I try to flash the bootloader:
FAILED <remote: <00030003>>
Click to expand...
Click to collapse
OK then I suppose its gone too.
Try uhm...
Adb shell
Mount /data
See what it says probably not found but report it back here.
Then try
Parted /dev/block/mmcblk0p8 print
This should return partition info for /data including internal SD. Try for device mmcblk0p1 - mmcblk0p8 and paste what it says.
Its really looking like emmc failure which means new motherboard time. Only other thing is trying to create partitions.
Tapatalked from my Galaxy S II.
I tried to copy the system image file (system.rooted.H81510c-EU.img = 4 GB) to a different location as the /data/media/0/ of
Code:
dd if=/data/media/0/system.rooted.H81510c-EU.img bs=8192 seek=55296 count=529920 of=/dev/block/mmcblk0
is obviously NOT available to me because I use device encryption. (/data unavailable) So I tried to find a way to replace /data/media/0/ with anything that maps to my external_SD Card (/mnt/media_rw/external_SD) as this is not encrypted (can be encrypted easily). The Send_Command.exe \.\\COM5 shell is NOT very helpful in even understanding if the SD_Card is mounted. Anyone knows anything about it?
Second I tried to, as I am rooted, to copy the system image file to any location the Send_Command.exe \.\\COM5 shell would be able to read from although the device is encrypted. This would have been a 2 step process of rooting, unrooting and encryption and re rooting but I wanted to try. Somehow despite having root rights I could NOT copy anything directly to /. Or any other folder available in the Send_Command.exe \.\\COM5 shell. Any files or folders I created where successfully created when NOT created in / but I could not copy the large image file. It always told me not enough space, which is not the case. Folders I created seemed to be vanished after a reboot.
Anyone can shine a light on this? Can’t I copy because the device is already encrypted, or can’t I copy because of SLELinux Security?
Third I tried to copy the image file via Push_File.exe \\.\COM5 system.rooted.H81510c-EU.img /tmp/system.rooted.H81510c-EU.img which seemed to work. Just to find out it started fine and then quickly failed. Maybe not enough space in /tmp or wrong Push_File.exe parameter?
Anyone can help me out here?
Best regards
since you are going to need to re-encrypt it after you root it anyway why don't you just decrypt it first and save yourself the hassle?
run id in the command shell. it'll show you have recovery selinux context, which is very limited. you cant do much which is why we are having to copy the whole system partition off the device and edit it remotely. I dont think you'll have much luck mounting the sdcard, but thats not to say you shouldnt try and post back if you succeed.
@diedemus
Because LG encryption is buggy and will not encrypt when rooted. (10a + 10b tested)
I run the id command successfully. So I do have the limited shell = recovery selinux and I am root. Any idea how to mount the sdcard when in recovery selinux context?
Is there a technical documentation of that shell? I couldn't find any. Help is greatly appreciated.
Sent from outer space using telepathy
With samsung there is a way to encrypt a rooted device.
Download terminal and launch
$su
Click to expand...
Click to collapse
the $ will become a #
Now type
pkill -KILL daemonsu
Click to expand...
Click to collapse
the# will become a $
Just after that (don't wait) go to encryption and encrypt the phone (it can take long time).
remixtech said:
With samsung there is a way to encrypt a rooted device.
Download terminal and launch
the $ will become a #
Now type
the# will become a $
Just after that (don't wait) go to encryption and encrypt the phone (it can take long time).
Click to expand...
Click to collapse
Interesting. I should try that one day. Only have one device left though, no more playing around [emoji2]
This development device was encrypted. LG devices can be unencrypted. Did NOT work. Device rebooted and never started decryption. Same as with encryption.
I did remove root, supersu, busybox everything AND tricked the LG RCT into thinking that the device was never rooted.
Decryption worked fine after that. I guess encryption will too. Why LG links device encryption and rooting is beyond me.
I should write a full guide one of this days on how to archive that.
This post was written on my rooted LG G4 with Xposed AND device encryption. So it is possible [emoji3]
Gesendet von meinem LG-H815 mit Tapatalk
fpsq said:
Interesting. I should try that one day. Only have one device left though, no more playing around [emoji2]
This development device was encrypted. LG devices can be unencrypted. Did NOT work. Device rebooted and never started decryption. Same as with encryption.
I did remove root, supersu, busybox everything AND tricked the LG RCT into thinking that the device was never rooted.
Decryption worked fine after that. I guess encryption will too. Why LG links device encryption and rooting is beyond me.
I should write a full guide one of this days on how to archive that.
This post was written on my rooted LG G4 with Xposed AND device encryption. So it is possible [emoji3]
Gesendet von meinem LG-H815 mit Tapatalk
Click to expand...
Click to collapse
Please do that. I come from Samsung and i would like to encrypt my device with XPosed !