Related
09/01/2012:
this tutorial may work for those who are having encryption issues on ics or jb roms (the error is related to mmcblk0p2(data))
well, after some months of work, here´s an tutorial about how to fix the mostly common sdcard issues.
1º Of all :***Be sure of what you´re doing,or else you can corrupt the partition table of you sdcard/brick your phone,and I´ll not be responsible of it***
2º-Do Not send me PMs, post here so everyone that have the same problem can now how to fix it.
3º-If you are an starter, you can post here your questions,but be sure that you haven´t found answers on Google or other threads.
and 4º-Read ALL topic before start and try one solution than the other,they´re in order of difficulty and risk of get an "permanent" brick.
0 - Always backup your EFS folder, maybe its not related to this thread but it´s also very important to remember.
I -If you have a folder called "voodoo" in your sdcard, you may have voodoo enabled on your ROM, so be sure of disabling it before trying a new rom or a stock rom.
if you´re on another rom already and having problems in mounting partitions, try to flash you last rom or a kernel that supports voodoo and it´s compatible with your new rom.
II-If you´re getting problems in mounting DBDATA,Download a full rom that contains DBDATA to flash with odin(or only flash dbdata,but you´ll have to do a full wipe later). To see if it haves dbdata.rfs by opening your .tar file in 7zip or others.
III-If you´re getting Can´t mount data (dev/block/mmcblkl0p2) File exists, try to flash an kernel with voodoo suport,if it still the same, format data in the menu of your recovery.
IV-If you´re getting can´t mount sdcard (/dev/block/mmcblk0p1)File exists, try to access it via ADB and send pull file command to recover your files(must have root),if you could do that, so try to format it via recovery.If not work,Download gparted, burn it on cd (it´s an CD with a tool of linux) and go to ADB shell to run this command:
su
echo /dev/block/mmcblk0 > /sys/devices/platform/s3c-usbgadget/gadget/lun1/file
now
reboot your PC in gparted and format mmcblk0p1(it´s the first partition) in FAT32.
Done
V-If you´re getting cant mount sdcard (/dev/block/mmcblk0p1) with (invalid argument) You can try the fix IV and see if it works,if not, proceed to VI.
VI-If you´re getting cant mount data(dev/block/mmcblk0p2) or can´t mount sdcard (/dev/block/mmcblk0p1) with (invalid argument) or (no such file or directory) you may have to do this:
***search on google for 'fdisk' commands first***
You MUST*¹ remake your partition table manually,so the phone have the /data partition back to boot.
*¹
In some cases you can use gparted to do this, without doing it manually,
you shoud only mount mmcblk0 before.
you can run this command line on adb shell to mount it:
echo /dev/block/mmcblk0 > /sys/devices/platform/s3c-usbgadget/gadget/lun1/file
You Will have to format it and it MUST have the partitions as said below.
YOU SDCARD MUST HAVE THE FOLLOWING PARTITION TO BOOT ON AND RECOGNIZE INTERNAL SDCARD:
/dev/block/mmcblk0p1
AND
/dev/block/mmcblk0p2
Start:
Open ADB,comnect your phone and proceed.
run adb shell
su
fdisk /dev/block/mmcblk0
p (you should see your partition table,POST HERE BEFORE CONTINUING)
YOU ARE NOW ABOUT TO REMAKE YOUR PARTITIONS:
partition 1 will correspond to mmcblk0p1(SDcard) and partition 2 will correspond to mmcblk0p2 (DATA)
**DO ONLY AS I SAY HERE, UNLESS YOU MAY GOT I/O ERROR ON YOUR SDCARD AND ITS ALL OVER. I say because it happened to me and i had to dissolder the internal sdcard an use only the external.**
**********IF YOU DONT HAVE ANY IDEA OF LINUX COMANDS: DO NOT PROCEED !!!!!!!!!*************
tap on adb:
n (will create a new partition)
1 (partition number)
press enter on keyboard so it selects the first block
get a calculator and estimate the size of the partition 1.IT MUST HAVE around 2GB left.
write the block number you got in calculator(BE SURE OF WHAT YOU TAPE HERE)
t
b (partition 1 is done and formatted as fat 32)
Now again:
n
2
enter on keyboard
enter again so it select the last block
(DO NOT TYPE COMMAND "T" FOR PARTITION 2, IT BY DEFAULT SET TO LINUX EXT FORMAT)
p (you will see you new partition table)
****IT MUST HAVE 2 partitions, partition 1 is in fat 32 format and partition 2 is in linux format(AND MUST HAVE AROUND 2GB)****
w (IT WILL WRITE YOU NEW PARTITION TABLE ON YOU SDCARD,SO BE SURE IT's ALL CORRECT)
Done,
now tap:
q
fdisk /dev/block/mmcblk0
p (you should see your new partition table, if ok reboot your phone, flash an stock rom for vibrant (I sugest an T959UVJFD ROM only to correctly format your partitions),root it,backup it,and enjoy,You can put a custom rom if you want so.)
If You have an error That does not appear here and you think it may me related to you sdcard just ask. In one or two days I or others developers may post here a possible solution.
Thanks For Google and some XDA users who indirectly helped me doing this.
You can try Paragon Hard Disk Manager in place of gparted
but remember: mmcblk0p1 is FAT32 and mmcblk0p2 in EXT2 (in truth it´s not EXT2, its in rfs, but the stock rom T959UVJFD is the only that I have absolute sure that will do the conversion).
Sorry for my bad english, it´s not my native language.
Great post doiiido!
Hay doiiido, you have been thanked and this post has been added to the [REF][KERNEL] ✰ The Official Vibrant Kernel ßible Thread ✰ → 07/05/12.
Great post!
News
Original pos by: ferhanmm
link to it:
http://forum.xda-developers.com/showthread.php?t=1665123
[FIX] Data wipe error or Can't mount /dev/block/mmcblk0p1
Data wipe error, Can't mount /dev/block/mmcblk0p1, or Vibrant screen boot loop even after flashing stock odin JFD phone will not boot. Phone will only boot Eugenes JK2 but internal and external storage will still list as corrupted and Lists 0.00 MB in storage.
Internal storage has been destroyed, I’ve been able to fix a phone using this technique to be mostly working. The external SD card will always have to be in the phone for this to work.
1. Partitioning the MicroSD Card
Get an 8gb(or larger) micro sd card. Class 10 would be better here. Put it into a Card Reader, then run Gparted.
Gparted (usb method is easiest) - http://gparted.sourceforge.net/liveusb.php
Using Gparted, delete everything else and create 2 partitions and :
6000mb FAT32 as PRIMARY
1607mb(remainder) Reiser as PRIMARY
2. Flash to Stock
Open up Odin flash stock JFD with pit file and repartition checked.
After phone boots completely, power off.
3. Flashing CM9
Take MicroSD out of phone an put it in pc, then copy update.zip, GAPPS, Cyanogenmod Rom all to the FAT32 partition that we created earlier. In Windows it should show up where all of your drives are listed in.
update.zip (https://www.dropbox.com/s/ju5eg5ernxcaqpt/update.zip),
GAPPS (http://www.goo-inside.me/gapps/gapps...317-signed.zip)
CyanogenMod Rom Zip(http://download.cyanogenmod.com/get/...mtd-signed.zip)
Enter recovery mode with volume buttons and power.
Reinstall packages twice.
Install zip from sd card select update-cm-9-20120520-nightly-vibrantmtd-signed.zip phone will boot loop on vibrant screen so take out the battery then enter recovery a second time installing the cm9 update again.
Then flash Gapps zip the same way.
When phone boots up camera, and gallery will not work until the next step.
4. Edit Vold.Stab file
Downlad ES File Explorer from play store.
Hit Menu button, settings, Check box for Root Explorer, Check box for mount file system, check box for Up to Root
Press Up once, you should now be at "/"
Open system directory, open etc directory, scroll to bottom and select Vol.fstab, select Text, Select ES Note Editor, update text to the following:
#internal sdcard dev_mount emmc /mnt/sdcard 1 /devices/platform/s3c-sdhci.0/mmc_host/mmc0
#external sdcard dev_mount sdcard /mnt/emmc auto /devices/platform/s3c-sdhci.2/mmc_host/mmc2
After edits, click back and click yes to save changes. Exit out of es file explorer and restart phone. Post results:
Should work with any version of CM9, newer nightlies would obviously be preferred. Will make more detailed guide soon.
Credit to these guys for providing the solution -
http://www.youtube.com/watch?v=zdMhYYdMB08
http://forum.xda-developers.com/show....php?t=1447303
Samsung Vibrant
News
Original post by:
draikz
Link to original post:
http://forum.xda-developers.com/showthread.php?t=848737
** [GUIDE] FIX AND RESCUE YOUR VIBRICK + ODIN SUPPORT! N00b Friendly **
Fixing so-called "Bricks"/Odin Errors
This guide is open to contribution/editing/correcting
I DO REALIZE THAT MOST OF THESE LINKS ARE BROKEN, PLEASE SCAN THE THREAD TO FIND UPDATED LINK. I'M NOT VERY ACTIVE ANYMORE, SORRY!
-----------------------------------------------------------------------------------------------------
BOOT CYCLE
This is where you get the annoying Samsung Screen/Galaxy S screen.
DOWNLOAD REQUIRED (CREDITS TO JUSTANOTHERCROWD):
Quote:
Originally Posted by justanothercrowd
JFD ODIN Images from Samsung (PDA)
www.justanotherdev.slackdev.com/T959UVJFD.tar
MD5:632730f6b637f53e5b10e5cbc8b966a7
512 PIT File (PIT Extract first!)
www.justanotherdev.slackdev.com/s1_odin_20100512.rar
MD5:b5628c8e183fdd8f4c703321ca40e33a
ODIN
www.justanotherdev.slackdev.com/Odin3.rar
ALL 3 Files plues the root update.zip
http://tinyurl.com/2bc5b6r
thx to KopyKatKiller
1. Get into Download Mode (WITH THE PHONE PLUGGED IN) by following the steps below
*Turn off the phone until you get to the charging battery screen (keep in mind, your phone is currently PLUGGED IN)
*Press volume up and down, and power all at once.
*As soon as the screen turns black, release your power button.
2. Unplug phone from USB
3. Open Odin (in Administrator if you're running W7 or Vista), try one of the ones I attached to this post, at least one of them is bound to work, some don't work for me, but works for others, some doesn't work for others, but works for me, whatever floats your boat
4. Load in the files into Odin that you have downloaded from above Just load in the files corresponding to the text field.
DO NOT CHECK REPARTITION.
5. Plug in your phone with the DL mode
6. Click start and wait for the magic
-----------------------------------------------------------------------------------------------------
NO-BOOT PHONES
This is where your phone does NOT turn on, no combo of buttons works and power button does nothing.
DO THIS ONLY WHEN YOU PLUG IN YOUR PHONE AND NOTHING SHOWS UP ON THE SCREEN!!! If else, follow the steps from above.
This method is basically same as above, EXCEPT the way you get into Download Mode as your phone is HARD BROKEN.
1. Download all the files required in the "BOOT CYCLE" section of this post.
2. Remove everything from your phone (SD card, sim, battery).
3. Plug your phone into your computer WITHOUT the battery, as you have already taken it out in the last step.
4. Press and HOLD vol. up and vol. down.
5. As you are HOLDING these buttons, reattach your battery.
6. You should be in Download Mode.
7. Unplug phone from USB
8. Follow steps 4-8 from the "BOOT CYCLE" section.
Troubleshooting:
-Odin stuck at some random process?
*Switch to another odin
*Make sure you did NOT check repartition, if you did, just repeat all the steps over again, except for the downloading parts, obviously.
-Phone not responsive?
*Try "NO-BOOT PHONES"section of this guide
-Phone stuck at Galaxy S logo screen?
*Put it in to DL mode, and run Odin again, it's just a bad install.
-All three ODIN is nonfunctional, stuck or giving "FAILED" errors?
*DO NOT CLOSE ODIN ONCE IT HAS FAILED!
*Unplug your phone
*Replug in your phone, get it into DL mode
* Unplug once it is in DL mode
*Replug and ODIN should recognize your phone
*Leave all the settings the same, then click "Start" again.
-Cannot get into download mode using the method I listed? Use the method(s) below:
Soldering Method
More methods coming soon
-----------------------------------------------------------------------------------------------------
I know how much of a pain posting in the Q/A section can be and the wait time is pretty bad, so if you need help regarding UNBRICKING and ONLY UNBRICKING feel free to post in here.
Hope you enjoy, this is my first guide, please don't flame. Any comments or suggestion is suggest, or if you have your own method I'll also post it
POST YOUR RESULTS!
-Steven
The only forums this guide should be posted on is XDA, DZ, and PHANDROID under the username DRAIKZ and EXPLOSIVE. If it helped you, feel free to donate a coke or two!
After having rooted (with nexus 10 toolkit v1.3.0) my nexus 10 and flashed AOPK Nexus 10 (WIP) Task650 & Ktoonsez (1-4) rom, I'm unable to upload to, change or move any files or folders on my internal SD card. I installed Root Explorer and changed from Mount R/O to Mounted as r/w. Access is granted by Super SU. I also tried to change permission settings, unfortunatedly without any success. There appeared the following message:
"Warning
Permissions change was not successful. Please note that some file systems (e.g. SD card) do not allow permission changes."
Is there a possibility to change these permissions in order to be able to create and move files and folders on my SD card?
Thanks for taking your time to help me with my issue!
Anzirothu
1. Clear cache
2. Clear dalvik
3. Fix Permissions
forgot something ?
Thank you for your reply, Patrik!
1. done.
2. done.
3. Fix Permissions - How? With cwm? I did fix permissions with cwm recovery, but the problem persists...
Just so we are clear, when you say "upload to, change, or move" are you meaning you cannot copy a file from your computer to your Nexus 10? Or just that you cant arrange stuff through root explorer from within the tablet itself?
Neither copying from PC to Nexus nor arranging stuff through root exlorer from within the tablet itself. I can't even download an email attachment and put it to the SD card. The card seems to be locked.
I had that problem once but I dont remember what caused it or what exactly I did to fix. I think I just did a complete wipe by locking and unlocking the bootloader and then installing a new ROM again.
I think I did this too (unroot, lock bootloader, then root and unlock bootloader) and then installed the same rom again. I will try it this time with another rom.
Isn't there really no other solution to get access to my SD card again??
Thx for your help!
Are you using a toolkit to unlock and root? If so them maybe it is not doing something right and it messing up a permissions somewhere. It could also be a driver problem on your PC with being unable to copy a file to the tablet.
Thank you for your help!
I am using the nexus 10 toolkit V1.3.0. Right now I'm trying to intall twrp recovery with a fully wiped sd card. No easy task fot me being a noob...
In ClockWorkMod, make sure that /data is mounted
Then download the Android SDK: http://developer.android.com/sdk/index.html
I usually put all the files just in C:/android-sdk-windows
Once you have it all there open up the SDK Manager and download all the additional files needed. You probably only need to download "Android SDK Tools" and "Android SDK Platform-tools", but I always download the other files for whatever version of Android I am running, in our case Android 4.2. That way I have them if I need to do something else.
Once downloaded, open the Android-sdk-windows/platform-tools directory. copy:
adb.exe
adbWinApi.dll
adbWinUsbApi.dll
fastboot.exe
to your base C:/Android-SDK-Windows directory.
Now open command prompt from Start -> run
type: cd C:/Android-SDK-Windows
type: "adb devices" and it should list your tablet. It will actually say something with your devices serial number and then "Recovery" after it, showing your tablet is in recovery. If you dont see this then you either dont have your tablet mounted right from in the Recovery, ClockWorkMod is stupid, or you dont have working adb drivers.
Now copy the ROM you want to flash to C:/Android-SDK-Windows
Then type: "adb push blahblahblah.zip /data/media/0"
That should push the ROM to the root of your SD card. Give it time, it takes a while to push a ROM file. Once it is done, flash the ROM.
That *should* put it in the right spot where it looks like it is on your "internal storage" (what you see when navigating files within the ROM). If you dont see the ROM in clockworkMod then keep navigating back to the root of your internal storage and then open up "data", then "media", then "0" and you should see it. If you still cant find the ROM, push it again but just use "/data/media" as the location.
I just did all these steps myself to verify I remembered it all correct and I was able to successfully copy a ROM and find it on my tablet to flash by doing everything I just listed above. SO you should be good to go if you follow all those steps properly. I know it looks like a lot of work, but it really isnt and will go quite fast. Most of it is just the setup for getting ADB and Fastboot ready to use.
For a ROM to install, I would recommend to someone new like you either of these:
http://forum.xda-developers.com/showthread.php?t=2071082
^^^^^ That one is pretty close to the stock ROM with a few fixes and a couple extra features
or: http://forum.xda-developers.com/showthread.php?t=2071082
^^^^^ This one is pretty much CyanogenMod 10.1, but built by a different guy and not pulling every new thing from CM, just the "cherry picks" of features. It tends to be a bit more stable and less buggy than the real CM10.1 nightly's
And for a kernel you can flash and forget you will want to try this one:
http://forum.xda-developers.com/showthread.php?t=2098157
^^^^^ To flash that you will want to do a similar thing as how you pushed the ROM to your device. Only this time you will copy the kernels' "boot-r4.img" file into your android-adk-windows directory and use the command: "fastboot flash boot boot-r4.img"
While I enjoy the KTManta kernel more, it does require a bit of tweaking to get running perfect. Which is one of the things I like about it because of all the options to tweak. But for someone just learning this stuff that would be a bad thing, so Franco's kernel is much better than stock and doesnt require you to adjust anything once it is flashed to your tablet.
EDIT: If you are coming here for the first time, this guide should still work, but @PorygonZRocks has created a flashable zip that should deal with a lot of these issues automatically. You can check out his post here:
https://forum.xda-developers.com/showpost.php?p=75787067&postcount=699
This method will indirectly allow you to root the LG Gpad v410 after it has been upgraded to Lollipop 5.1.1. Yes. Rooting LG v410 Lollipop. It's through a downgrade, but it works.
It took a while to get working, but here's how I did it. The process is straightforward, but the details matter greatly. You will brick your device if you mess up. Please read everything *first* before you do anything. Be sure you understand the process. I'll try to explain what's going on along the way.
An external SD card is extremely helpful for this process. You *could* adb push everything, but that will tedious.
First, you need some files.
The 4.4.2 KDZ which is a TEST OS, but it can be rooted and it downgrades to a Bump'able bootlaoder:
http://forum.xda-developers.com/g-pad-10/general/kdz-lg-g-pad-7-0-v410-t3224867
The LG 2014 Flash Tool:
http://www.mediafire.com/download/fwrcd3pdj0svjtb/LG_Flash_Tool_2014.zip
Android LG Drivers:
https://www.androidfilehost.com/?fid=24052804347802528
Parted for Android. You can probably find it other places, but I found this file:https://dl.dropboxusercontent.com/u/84115590/LG%20G2%2016GB%20Solution/sdparted-recovery-all-files.zip
EDIT: There seems to be a lot of confusion here. My bad. All you need is the file named "parted" from this zip file - nothing else. Just put that one file in the root of your external SD card.
https://dl.dropboxusercontent.com/u/84115590/LG G2 16GB Solution/sdparted-recovery-all-files.zip linked from here: http://www.**********.com/your-32gb-lg-g2-shows-only-16gb-storage-space-heres-the-fix/
EDIT2: The dropbox link is down. I've attached the file directly.
The Candy5 ROM (This will potentially save you some manual steps. Somewhat optional, but highly recommended):
http://forum.xda-developers.com/g-pad-10/development/rom-candy5-g-pad-v410-lollipop-5-1-1-v2-t3111987
Flashify APK:
http://www.apkmirror.com/apk/christian-gollner/flashify/flashify-1-9-1-android-apk-download/
TWRP for the v410:
http://forum.xda-developers.com/g-pad-10/development/recovery-twrp2-8-5-0lgv400-410-t3049568
LG One Click Root:
http://forum.xda-developers.com/lg-g3/general/guide-root-lg-firmwares-kitkat-lollipop-t3056951
(You may use Purple Drake or whatever else you want. They all use the same root script as this does and the GUI is helpful for novices.)
Android SDK (specifically adb.exe. After installing go to SDK Manager and ensure that Android SDK Platform Tools is checked):
http://developer.android.com/sdk/index.html
For clarification below, when I have commands in "quotes" they are Windows commands. When they are in `backticks` they are commands that you run inside of ADB which actually run on your device....as root. Root can screw things up. Please be extra cautious. If you blame me for messing up your device I will laugh at you. But that's not gonna happen, right? Good. Let's go.
Now that you have everything, put it all into a folder where you can access it easily.
Install the LG Drivers.
Install Android SDK (or otherwise get adb.exe).
Extract all of the archives.
Move the KDZ to the LG Flash Tool 2014 folder.
Put the tablet into Download Mode by powering it off, holding VolUp, and plugging in the USB cable. Press VolUP when instructed. You must be in Download mode before continuing.
Run LGFlashTool2014.exe. Select the KDZ file. Click "CSE Flash". Click "Start". Select "English" and click OK. Do not change anything else.
WAIT for the flash to continue. If you really want to brick your device, here's a good opportunity.
The device will reboot into Android 4.4.2. You will only have 4GB of internal storage at this point. DON'T PANIC! We are fixing it.
Enable USB debugging.
Connect the device.
Install and run LG One Click Root. Wait for the device to be rooted before proceeding.
Copy the Flashify apk, TWRP image, and Candy5 ROM to your external SD card.
Install Flashify and flash TWRP to the recovery partition.
Use the Flashify menu to reboot in to recovery.
DON'T PANIC! You will get white vertical lines on the boot screen from now on. They only show up during boot animations. A small price to pay. This may be fixed at a later date. for the time being! Thanks to marcsoup's first post ever, we have a fix! Details below. PLEASE click this link and thank him!
Things get tricky here. Copy parted to your external SD card and then run "adb shell" from Windows to get a shell in TWRP.
In TWRP, unmount /data by tapping Mount > uncheck Data.
`cp /sdcard/parted /sbin/` This copies the parted binary to /sbin so it can be executed in the path. I had trouble running `/sdcard/parted`, but YMMV.
`chmod +x /sbin/parted` Make it executable.
`parted /dev/block/mmcblk0` Run parted against the internal mmc
`p` Prints the partition table.
`rm 34` Deletes partition 34 labeled "grow". This is the root of our problem. The KDZ apparently only creates a 4GB partition, I assume so the test build has maximum compatibility with all sized devices.
`rm 33` Deletes partition 33 "userdata"
`p` Print to verify
`mkpartfs` Create a partition and put a filesystem on it. If we only expand the partition it won't help us because the filesystem is still only 4 GB.
a) name: userdata
b) type: ext2 (the tool only supports ext2. This is ok for now.)
c) start: 3439MB (the end of part 32. IT MAY BE DIFFERENT FOR YOU!) Be sure you do not omit the MB part otherwise the offset will overwrite another critical partition.
d) end: 15.8GB (where "grow" ended above. IT MAY BE DIFFERENT FOR YOU!) Be sure you do not omit the GB part otherwise the offset will overwrite another critical partition.
`p` Verify. For me it did not name the partition properly. Gotta fix that.
(if necessary) `name 33 userdata` This is critical for mount to find it in /dev/block/platform/msm.sdcc.1/by-name/ on some/all ROMS.
`p`. Verify one last time. Compare it to my partition table in the attachments. If you want to brick, delete some random partitions here.
Flash Candy5 with TWRP. It's only 239 MB, so it will flash quickly. I do this because Candy5 will reformat mmcblk0p33 from ext2 to ext4 for you. It does this as part of it's system boot, apparently. If you install a different ROM that does not do this, you can reformat it by running `make_ext4fs /dev/block/mmcblk0p33`. If your ROM does not have make_ext4, it likely has some differnt method to make an EXT4 filesystem. `/system/bin/mke2fs -t ext4 /dev/block/mmcblk0p33` may work better. Just flash Candy5 and be done with it.
Tap Wipe > Swipe to Factory Reset.
Tap Reboot > System.
WAIT!!! It will take a minute for the ROM to start the first time. You will have white lines and and possibly a white screen. WAIT. It's moving the DEX files to cache, formatting a partition, creating default folders on the internal storage, and several other things. WAIT! When the screen goes dim or turns off then it's ready.
Cycle the display or turn it on. You should be at the Candy5 lock screen.
USB debugging is on by default. Run "adb shell".
`mount | grep userdata` Make sure mmcblk0p33 is mounted.
`df` Make sure /data is 11.3 GB (or whatever size it is on non-16GB devices).
HELL YEAH, you downgraded, rooted, and fixed the partition problem. Enjoy your tablet!
Thanks to dopekid313 for finding the KDZ.
Thanks to timmytim for Candy5.
Thanks to the creators of the root script, flashify, TWRP, and XDA for being so awesome.
Thanks to marcsoup for fixing a fix to the white lines.
Thanks to navin56 for the partition dumps. PLEASE thank his post!
White lines fix.
What we are going to do is flash the aboot partition with the stock image provided by navin56. I've removed the extra files from the dump, so simply download aboot.img.7z below. Unzip it using 7zip.
These commands are to be run in TWRP. Reboot to TWRP recovery and connect with "adb shell". All of the following commands will be run in ADB under TWRP. If you cannot figure out how to get here, please post in the thread and someone will help you. Onward:
If you do everything correctly then you don't have to reflash your ROM and you won't lose data. This process can be done any time after flashing the KDZ, even before you follow the steps above to resize the userdata partition. It's a completely separate process.
Unzip aboot.img.7z so you have the file named aboot.img. You should also make sure that aboot.img's MD5 sum is e97431a14d1cee3e9edba513be8e2b52. Do not flash the 7z file. Please.
Copy aboot.img to your external SD card. It should live at /sdcard/aboot.img
Boot to TWRP and run "adb shell"
`ls -al /dev/block/platform/msm_sdcc.1/by-name/` Let's make sure we are flashing the right partition. On my device "aboot" is /dev/block/mmcblk0p6. You should verify this on your device or you WILL brick your tablet.
`dd if=/dev/block/mmcblk0p6 of=/sdcard/aboot-fukt.img` Let's back up our current aboot partition before we go flashing things just in case there are unintended consequences later. Be sure you have the same partition that "aboot" referred to in the 4th step or you have just backed up the wrong partition.
`dd if=/sdcard/aboot.img of=/dev/block/mmcblk0p6` Be sure the file exists, is the correct aboot.img, and you are flashing the right partition. You have been warned!!
Reboot TWRP and enjoy your boot animations again.
If I missed anything, please let me know. As far as I know this is the very first tutorial that details what is necessary to accomplish this. Please hit the Thanks button on every thread that you visit to download files!
FAQ:
Q: Why do I only have 11.3 GB of space when my device is 16GB?
A: The entire internal SD card (eMMC) is 16 GB. Gotta have someplace to install the bootloader, recovery, android, the modem OS, the secondary bootloader, the cache, the resource and power manager, and all of the other partitions necessary for the table to operate. Please look at the second screenshot in the OP. All of those 33 partitions take up room on the internal card. Fortunately ALL of those partitions ONLY take up about 4.4 GB. Hence the 'userdata' partition is ~11.3 GB.
If anyone wants to use my work to create a flashable zip to make it easier for novices, please do so. My problem is solved and I don't have the time to create the zip. Please post any questions and I'll gladly answer them! I'm so stoked that we have a usable downgrade method now!
Thank You, Worked Great
Thanks for making this I was gonna do it but was to lazy lol and thanks for linking my thread and giving cred instead of just linking straight to the kdz thank you
grandamle91 said:
Thank You, Worked Great
Click to expand...
Click to collapse
Glad to be of help!
dopekid313 said:
Thanks for making this I was gonna do it but was to lazy lol and thanks for linking my thread and giving cred instead of just linking straight to the kdz thank you
Click to expand...
Click to collapse
Of course! If you hadn't obtained the firmware then we'd all still be looking for a solution. It pisses me off to no end when people try to take credit for other people's work. We all just need to realize and acknowledge that we are simply standing on the shoulders of those who did the work necessary for each of us to do our work.
I just noticed since we formatted the userdata it screws up TWRP. It won't mount Data and it says the settings are corrupted
grandamle91 said:
I just noticed since we formatted the userdata it screws up TWRP. It won't mount Data and it says the settings are corrupted
Click to expand...
Click to collapse
Is this after you've rebooted into Candy5 and the partition is reformatted as ext4 (or you've done so manually)? TWRP may not be able to mount an ext2 partition.
EDIT: I just tested this. Following my instructions and flashing to Candy5, TWRP sees mmcblk0p33 (userdata) as the full size and mounts it at /emmc.
For clarification, after you run the parted commands, it will mess with the partition table and TWRP will most likely not be able to see it to remount it - at least not until after a reboot. This is why you need an external SD card from which to install ROMs.
/data not mounted
Edit: nevermind. The partition 33 was still ext2. I had to run make_ext4fs /dev/block/mmcblk0p33 and now I am able to mount /data. Thanks.
Thanks for taking the time to help us.
I followed the steps and till 33 I am good. But once I am in Candy5, I am not able to adb shell (adb not recognizing device eventhough usb debugging is on). I rebooted to recovery and adb works there. But my /data partition is not enabled in TWRP. I am not able to check it either under Mount in TWRP.
Code:
mount | grep userdata
is empty
Code:
df
does not show data
I tried this and my tablet bootlooped. I was able to get into fastboot and restore. I would GREATLY appreciate it if someone who has the time, would kindly donate their valuable time to into making an exe zip or something.
gridironbear said:
I tried this and my tablet bootlooped. I was able to get into fastboot and restore. I would GREATLY appreciate it if someone who has the time, would kindly donate their valuable time to into making an exe zip or something.
Click to expand...
Click to collapse
At what point did it bootloop? What was the last step that you took before rebooting?
Zip
I would really appreciate a zip file as I have never been savvy with adb and for whatever reason it doesn't want to work on Windows 10.
drumm3rb0y said:
I would really appreciate a zip file as I have never been savvy with adb and for whatever reason it doesn't want to work on Windows 10.
Click to expand...
Click to collapse
A zip file for what part? The only part that requires ADB directly is to fix the internal storage. You absolutely have to flash the KDZ and then root before you can do anything. If you are on 5.x then you have no possible way to root, much less flash a zip file.
If you tell me what exactly you are having issues with I will try to help.
fatbas202 said:
A zip file for what part? The only part that requires ADB directly is to fix the internal storage. You absolutely have to flash the KDZ and then root before you can do anything. If you are on 5.x then you have no possible way to root, much less flash a zip file.
If you tell me what exactly you are having issues with I will try to help.
Click to expand...
Click to collapse
The adb part is the part im having issue with. Everything else is flashed already. I was wondering if you could make a zip for the adb part so I can just flash it through twrp.
thanks for the great help. it did work perfectly to regain the lost space.
what about white lines ? is there any solution for that problem ?
I have tried flashing back stock recovery extracted from kdz, dd' but didn't help.
Now i am thinking of flashing back the aboot.bin extracted from original kdz or i can dump ".img" from another working device. (i have 4 similar devices)
what is your opinion i m not a developer and i need your advise. should i go ahead and which partition should i dd ? aboot or abootb or boot ?
regards
shahidmianoor said:
thanks for the great help. it did work perfectly to regain the lost space.
what about white lines ? is there any solution for that problem ?
I have tried flashing back stock recovery extracted from kdz, dd' but didn't help.
Now i am thinking of flashing back the aboot.bin extracted from original kdz or i can dump ".img" from another working device. (i have 4 similar devices)
what is your opinion i m not a developer and i need your advise. should i go ahead and which partition should i dd ? aboot or abootb or boot ?
regards
Click to expand...
Click to collapse
I have no solid evidence of this, but I suspect that the white lines are caused by a display driver issue where when the bootloader hands over control of the display to the kernel it doesn't get reinitialized properly. I have no ideas as to how to get rid of that at the moment but if I stumble across something I'll be sure to post here.
While I'm not an Android developer, I've been a Linux admin for 10+ years and have a lot of experience with Android devices. I'd be really hesitant to go flashing things ad hoc. While Download Mode may save you if you flash the wrong thing, I'm not entirely sure what the limitations that you may run in to with a locked bootloader are.
After having this device for months on 5.x and FINALLY being able to downgrade and run custom ROMs with root, not seeing a boot animation is a pittance to pay. But I'll keep looking.
i have same problem entered in TWRP but when ADB sheel thorough DP tools it didn't connect to my device. i m also using windows 10
Do I need to Re-mount Data ? I press format data button at TWRP and mount data. It looks work great.
After all process, it shows 16Gb total at storage, 11.04GB available. it works perfectly.
I need the stock V41010d, so I reflash the stock rom rooted at [ROM][STOCK](V410 ONLY)KOT49I.V4101d | 4.4.2 | Rooted + Busybox
Now, my Gpad is at stock V41010d, but I have a question about the boot screen, is it still with white lines and white screen? Any method to fix it?
Hello,
Thanks for the great work. unfortunately I am facing some difficulty, starting from step# 16 "Things get tricky here", how to run"adb shell in TWRP?
also can I use minimal_adb_fastboot_v1.1.3_setup.exe as mentioned in the link in the OP http://www.droidviews.com/your-32gb-lg-g2-shows-only-16gb-storage-space-heres-the-fix/ ?
also I noticed the path have been used includes 'parted' folder, but the folder I have after unzipping the parted zip called 'sdparted-recovery-all-files', do I rename the folder to 'parted' instead?
please help and excuse my broken English.
I'm also having trouble with the adb shell step. When my device is powered on normally, adb commands work. However, in TWRP mode my computer can't recognize the tablet, mount properly, and copy over parted. All the steps have been identical to this point. Any ideas?
iphone5sf said:
Do I need to Re-mount Data ? I press format data button at TWRP and mount data. It looks work great.
After all process, it shows 16Gb total at storage, 11.04GB available. it works perfectly.
I need the stock V41010d, so I reflash the stock rom rooted at [ROM][STOCK](V410 ONLY)KOT49I.V4101d | 4.4.2 | Rooted + Busybox
Now, my Gpad is at stock V41010d, but I have a question about the boot screen, is it still with white lines and white screen? Any method to fix it?
Click to expand...
Click to collapse
You shouldn't need to remount or format data. The parted command nukes the filesystem and creates a new one formatted as ext2. At this point the running kernel has the old partition table loaded and won't know that the partition has been extended. Simply flash Candy5 and reboot at this point and it will reformat the userdata partition.
See above for the white lines during the boot animation. Known issue, no fix in sight, doesn't really matter.
nmnm4alll said:
Hello,
Thanks for the great work. unfortunately I am facing some difficulty, starting from step# 16 "Things get tricky here", how to run"adb shell in TWRP?
also can I use minimal_adb_fastboot_v1.1.3_setup.exe as mentioned in the link in the OP http://www.droidviews.com/your-32gb-lg-g2-shows-only-16gb-storage-space-heres-the-fix/ ?
also I noticed the path have been used includes 'parted' folder, but the folder I have after unzipping the parted zip called 'sdparted-recovery-all-files', do I rename the folder to 'parted' instead?
please help and excuse my broken English.
Click to expand...
Click to collapse
You only need the sdparted-recover-all-files.zip from that site. "parted" is not a folder, but the binary (without a file extension) inside of that zip file. Copy that file to /sbin and you are in business.
zmali1 said:
i have same problem entered in TWRP but when ADB sheel thorough DP tools it didn't connect to my device. i m also using windows 10
Click to expand...
Click to collapse
summonholmes said:
I'm also having trouble with the adb shell step. When my device is powered on normally, adb commands work. However, in TWRP mode my computer can't recognize the tablet, mount properly, and copy over parted. All the steps have been identical to this point. Any ideas?
Click to expand...
Click to collapse
I'd recommend installing the SDK and pulling the drivers from that. Alternatively, you can try the drivers here: https://github.com/koush/UniversalAdbDriver.
Technically, when I ran the "parted" commands I was actually booted in to rooted 4.4.2 from the KDZ; I wasn't actually in TWRP. It's just not a very recommended way of going about it. I explained how to run all of this from TWRP, but there's no technical reason that you *can't* run this from Android. You just *shouldn't* because you can't cleanly unmount the filesystem and it theoretically could cause filesystem corruption. I just figured that I don't care about that partition getting corrupted since it's getting wiped out.
Hello everyone,
Please Help me to fix this issue
TWRP shows E: Unable to mount '/cache'
E: Unable to mount '/data'
E: Unable to mount '/system'
E: Unable to mount '/cache'
E: Unable to mount internal storage
I have twrp v2.5
Actually, I am trying many solutions but nothing change
Hi, pal. I have the exactly same problem these days. On my opinion, when you have made wipe and wipe dalvik cache, you just deleted the system folder and data. I did same thing, now I'm stuck! :Д When you are trying to change the firmware, is the logo pictures changing for you every time you flash any other .zip file? We' are now complete lost man. Is your USB working like mine where PCs not detecting it? I think they've launched this kind of firmware only to destroy our device, so we can buy a new one. That's the idea. Go to the service and repair center of Lenovo and ask them for help! I wrote them down before a while, now I'm waiting for the response. We have left only two or three possibilities to flash the Rom with the Terminal in the Recovery. But if your PC recognizing the drivers, you will manage to flash the Stock 4.2.2 Rom with Flash tool , otherwise you are stuck too! I have no idea how to flash it. I can give you the terminal commands for you, which are hard to find, but you and me, we need the proper .img files for the flashing procedure. Go to the 4pda forum and ask for help, if you find any solution, come back here telling it and for me. There's a possibility, but it is difficult to create a proper .zip archive, because I only know that we need those folders and files: meta folder- updater-script, logo. bin, lk.bin, boot.img and system.img.
But when I insert the commands there, I don't know how the whole process must be working, something is happening there. The problem is that one of those lines did not work for me. Those are the commands for flashing any Rom with the terminal in the recovery. But first you must see if the PC is installing your drivers properly, open device manager and look for the drivers on the internet and try to install them. May be you have a working USB port, so there's no problem, just flash the stock rom with the Flash tool. But if it is not working as it is here, no other possibilities left, my boy! The only one left or two of them : Flashing the device either through fast boot mode or adb sideload, but you must install those drivers so PC can find the device. Well, you can always do this at your own risk from the terminal.
Oh, I forgot, those problem came when we deleted fstab file for our device.
Flashing firmware through the TWRP terminal commands:
dd if=/external_sd/system.img of=/dev/block/mmcblk0p6 (for the memory ROW+ ) or
dd if=/external_sd/system.img of=/dev/block/mmcblk0p5 (for CN+ memory)
dd if=/external_sd/boot.img of=/dev/bootimg
dd if=/external_sd/lk.bin of=/dev/uboot
dd if=/external_sd/logo.bin of=/dev/logo
First, system.img must be converted to systemEXT4.img, then flashing it and you need to have a systemEXT4 in the .zip archive. But I think my system folder is deleted. :Д
simg2img /external_sd/system.img /external_sd/systemEXT4.img
Good luck to you! According to me there is a space after the dot and it must be like this: system. img, boot. img. But not sure!
Hi again. Tooday It occurred to me where our problem may be came with the tablets. When we flashed a custom Rom, we put it for the wrong MTK processor. Ours is MT8389, not 6589. The stock roms are too for the MT8389 according to me. We flashed a wrong Rom. Now the tab must be formatted somehow either through some commands from the terminal, or USB port and path to the USB must be repaired. Then, flashing with the Flash tools is our only option left! Sorry! );
They killed our device on purpose with the Custom rom. Do not flash them any more with such Roms.
Greetings,
i did go through dual-booting linux on our device kind of process and spend a bit of time, trying to figure out the correct steps.
Was not easy, for a newbie like me, i dont know much about linux itself, most of the inscrutions are written in "foreing language" for me, so here is more of a detailed guide.
This guide is only for installation on the SDCARD, i did not try out internal storage
!!! Im not responsible for anything that happens during/using these steps, you and only you are responsible to what happens, use with caution !!!
Requirements:
Unlocked bootloader: https://forum.xda-developers.com/t/...6c-boot-for-asus-memo-pad-7-me176c-x.3780225/
Installed TWRP: https://forum.xda-developers.com/t/...p-3-3-1-for-asus-memo-pad-7-me176c-x.3745190/
Both of these guides are made step by step, so there should be no questions about this
First of all, go to https://images.postmarketos.org/bpo/v22.12/asus-me176c/ , there are 3 different types of UI, the kernel itself should be the same, but i dont know for sure myself
Phosh - very well working on our device, missing a bit of RAM to launch firefox stable for example
Plasma-mobile - i found this one was very hardware heavy, it takes quite alot of more storage aswell, i do not recommend this for our device
Sxmo - this one did boot up just fine, but i wasnt able to get more testing as my hardware inputs were not recognized by the software, i do not recommend this one
There are multiple software version, i did try only the latest one
Possible to try out the lower (outdated) versions yourself
After downloading these files, you should have 2 of the .xz archives, unpack them somewhere, i did put them into the same folder, but thats just my own preference
After unpacking them, you should have
XXX-asus-me176c-bootpart.img
XXX-asus-me176c.img
XXX are reference to date of the build
To have ourself things easier, we will rename both of these build and leave only the "asus-me176c.img/asus-me176c-bootpart.img", you can leave them named as theyre, but it will take you a bit more time in the terminal
After that, we will move one of our images (the non-bootpart one) to the internal storage of the device.
Make sure, to have enough space available. I have the 8GB version and it was kind of struggle for me to install the plasma-mobile version.
I did also try moving that file to USB-OTG and SDCARD, but i had some problems with USB-OTG in TWRP and SDCARD gets wiped when you install the OS.
So, please, use internal storage for the file, the OS IS NOT GOING TO GET INSTALLED ON YOUR INTERNAL STORAGE IN THIS WAY, WE ARE GOING TO INSTALL IT ON A SDCARD.
After moving our file to the internal memory, we will go and reboot our tablet to fastboot mode
when powered off, press volume down + power on, release power when screen lights up
in the custom bootloader menu, using volume keys (power one does not work), we select Fastboot (power down to move and power up to select)
Our phone should boot into fastboot mode, we go and connect our phone to the computer
after connecting the phone, we go to the folder where our xxx asus-bootpart.img is located, go ahead and SHIFT+RIGHTCLICK on empy space in the folder, select Open a terminal/powershell window here
in the terminal/powershell we type in command " fastboot flash APD asus-me176c.img "
let the command process, after its done, go and type in " fastboot reboot-bootloader "
our phone gets rebooted into the bootloader, with volume keys once again, select RECOVERY
when our device gets booted to TWRP, go to Mount -> Tick ESP
anywhere on your PC, open up the default text editor, paste in:
title postmarketOS
volume 80868086-8086-8086-8086-000000000007
linux /vmlinuz-edge
initrd /intel-ucode.img
initrd /initramfs
# Comment this out to get more output on screen while booting
options console=null
this text is only used for the latest version of the OS, for lower versions, please follow https://wiki.postmarketos.org/wiki/ASUS_MeMO_Pad_7_(asus-me176c)
select the file type as "every files" instead of text document
name it pmos.conf and save it anywhere you like
at your computer, download MiniDiskPartition tool, or other partition tool
partition your sdcard using the selected tool
i have 32GB sdcard, i did partition my sdcard roughly 8GB with FAT32 for file sharing between android/linux/windows and the rest with EXT4 for the Linux itself
i believe the partition size for Linux doesnt matter aslong as its over 4GB, the installation itself should resize the partition on sdcard itself, depending on how it needs, BUT im still not 100% how this works
connect your phone to the computer
in TWRP go to MOUNT and tick ESP
in the folder where you saved the pmos.conf, open up a terminal (once again SHIFT+RIGHTLICK and open terminal/powershell here)
type in " adb push pmos.conf /esp/loader/entries/ " , press enter
in TWRP go to Advanced and go to Terminal
type in " df "
then you should see your partitions, we are looking for one that belongs to /external_sd/ , usually dev/block/mmcblkX0Y (X and Y are not specified), it should have it written at the end
mine was " /dev/block/mmcblk0p1 " YOURS CAN BE DIFFERENT! in the original guide, they specify, it can be also SDXY (XY belongs to any number)
after we find our partition that belongs to /external_sd/ , we go into the terminal in TWRP and type in:
dd if=/PATHTOYOURIMGFILE/ of=/PATHTOYOUREXTERNALSDCARDPARTITION/ bs=4m
i did have the IMG file in my internal storage, therefore my command was:
dd if=/sdcard/asus-me176c.img of=/dev/block/mmcblk0p1 bs=4m
make sure to use the bs=4m instead of bs=4M (as specified in the original guide), otherwise you will get "illegal number" error
after this, you should wait! The file is 1,6 - 2,4 GB, it takes time
your result should appear in the terminal
if your installation was succesfull, you can go in TWRP to REBOOT and select BOOTLOADER
you should have postmarketOS option available in the bootloader boot options, select it
you should boot your postmarketOS now
if you didnt, you probably didnt follow the guide correctly, read the steps once again
if you couldnt install the postmarketOS and youre sure you did follow the steps correctly, contact me on XDA (preferably make a comment under this thread)
Original thread:
ASUS MeMO Pad 7 (asus-me176c) - postmarketOS
wiki.postmarketos.org