yashsingh1/xdaforums huggingface dataset:
[G Pad 10.1 General] nicospanas:
question about adb shell in twrp

Hi, again. I just started the procedure, flashed kdz, rooted, installed flashify, flashed twrp, but I am not sure of how to get adb shell in twrp. I am not at all familiar with adb, so an as much detail as possible help would be hugely appreciated. I attached a photo to tell me if I am on the right track and how to proceed from here, cause I don't understand the weird symbols.

To remind you, I am downgrading from lollipop in order to install cyanogenmod, so if any steps could may be avoided, please let me know.
[G Pad 10.1 General] BeeWall:
I dont know how to do adb shell. I used the terminal in twrp, and typed VERY carefully.
[G Pad 10.1 General] nicospanas:
I really would like to do it as the OP suggests. I am just not sure if I should ignore the weird [6n symbols and continue entering the commands. Some people on this thread say I should first type su, but this gives a "su: not found" message. I only need some confirmation as to where to start.
[G Pad 10.1 General] abubakar1997:
Thanks i had twrp now i am on stock with ur help

can u give me stock recovery so i could go back totally on stock
[G Pad 10.1 General] nicospanas:
Cannot flash candy5

So, I found out I could start typing the commands after [6n and did so and everything seems to have gone well. But when I flashed candy5 and rebooted I do not see anything related to candy5. Storage says 8GB and available 10.89GB, but I haven't obviously completed the process. What did I miss?

Installed candy5 from twrp. Install, went to sd and selected the candy5 zip. Then wipe, factory reset and rebooted to system. How do I know when it successfully installs?

This is what I get after attempting to flash candy (sorry for the large image, I don't know how to make it smaller):
[G Pad 10.1 General] nicospanas:
I flashed candy again and it's on, but google services are not working, keyboard is not working and my pc does not recognize the tablet anymore. So I cannot adb shell or type anything on the tablet or even connect to the internet as I cannot type the password. Help please?
[G Pad 10.1 General] fatbas202:
I'll see what I can find.
[G Pad 10.1 General] fatbas202:
Can you get back to TWRP?
[G Pad 10.1 General] fatbas202:
I'm not seeing anything in my links. I'll try to track these down. In the next day or so, I'll try to get full system dumps off of my tablet and post them here.
[G Pad 10.1 General] BeeWall:
Theres one on this thread, posted by jason2678. I would suggest flashing with fastboot. If you have already done the white lines fix, you will have to 'dd' your backup aboot to the aboot partition ( mmcblk0p6 on my device), and then on a computer type "adb reboot bootloader". After a few moments, the tablet will reboot into fastboot mode. Type "fastboot devices" to be sure. If you see your device, good. If not, reconnect the usb. Now, make sure that the stock_recovery.img is in your adb/fastboot folder(Or, if you use minimal adb/fastboot like me, just "cd" to the folder the image is in). Once you are sure of everything, type "fastboot flash recovery stock_recovery.img". After this, hit the power button to select any of the restart options. It doesn't matter which because they all lead to a black screen. Long press power to reboot. Once your device is on, use adb to dd the white lines fix, this laf, also from jason2678, and abootb here from jason2678. The stock rooted by timmytim includes a boot image, so you don't have to dd that. MAKE SURE YOU DD CORRECTLY! Also, only flash the recovery from fastboot. I'm not sure which caused it, but I managed to rebrick my tablet using fastboot for all of them. I know for a fact it has trouble with aboot. Also keep in mind that after you flash the aboot from the white lines fix, you can no longer go to fastboot. The "adb reboot bootloader" will reboot normally. You need to flash all of these because otherwise the white lines fix will mess with the partitions from the kdz (example: a page or so back I believe i had trouble with download mode and recovery black screen. The laf and recovery fixed that. I'm guessing it has the same cause as the white lines.)

Thanks to jason2678 for the laf, abootb, and recovery

marcsoup for discovering the white lines fix, giving us images, and giving me the idea to try this,

fatbas202 for this thread and narrowing the white lines to aboot,

and timmytim for the boot image in the stock rom (and the stock rom itself, of course)

---------- Post added at 11:07 AM ---------- Previous post was at 11:04 AM ----------

Nevermind, I found them in other threads. If anybody needs them, they are linked in my post above.
[G Pad 10.1 General] nicospanas:
Unfortunately not. Nothing works cause I keep getting the message google.process.gapps has stopped, so I cannot get to flashify and I don't know how to start candy in recovery.

I just managed to get to TWRP.
[G Pad 10.1 General] BeeWall:
First, reboot back to twrp (power off, volume down and power, when the screen shows release power for a moment, and then press all 3 buttons), and factory wipe and wipe system. After that, go to the Mount option and make sure all the options are checked. Check and uncheck data to be sure it mounted. Then reflash Candy5 and Gapps if you have them on the internal storage still. If that fails, try downloading Gapps and Candy5 on a computer, and transfer the zips to an sd card with an sd card reader. Insert the sd card, and flash them from there. If that fails, download parted to the sd, and redo the partition stuff over adb (in order for adb to work properly in twrp, you generally have to disable mtp.) If adb doesn't work, reflash twrp and try again. If adb doesn't work you probably will have to use the terminal. If none of this works, you may have to start over and reflash the kdz. However, hopefully reflashing Candy5 and Gapps will fix everything. Good luck!
[G Pad 10.1 General] nicospanas:
It won't let me check data in mount option of twrp.
[G Pad 10.1 General] BeeWall:
You can reboot to recovery by powering off the device, holding volume down and power, releasing power for a moment, holding all three hardware buttons, selecting "Yes" on the first screen and confirming "Yes" on the second.

Note: If you have a stock recovery installed, this will trigger factory wipe, not reboot recovery.

---------- Post added at 11:35 AM ---------- Previous post was at 11:33 AM ----------

The next step would be seeing if you can mount an sd card. If you did everything as the OP said, you should have parted and Candy5 there (unless you deleted them when you were done, which I could understand)
[G Pad 10.1 General] nicospanas:
I run parted and print shows the correct partitions. I still have candy 5 and parted on external SD.
[G Pad 10.1 General] BeeWall:
If adb works, "adb shell ls -al /dev/block/platform/msm_sdcc.1/by-name" and see if userdata shows up.

EDIT: Nevermind. Just saw you post with parted.

---------- Post added at 11:43 AM ---------- Previous post was at 11:41 AM ----------

You have userdata as an ext2 partition. Run "adb shell make_ext4fs /dev/block/mmcblk0p33" and reflash. Candy5 is supposed to automatically do this, but apparently it didn't .
[G Pad 10.1 General] nicospanas:
Do I run the command make_ext4fs /dev/block/mmcblk0p33 in parted or in platform-tools?

And after I run it what should be mount between system, data, cache, sd card?
[G Pad 10.1 General] BeeWall:
Exit parted before typing this. I use minimal adb/fastboot so I don't know how platform-tools works. Is that the adb folder?
[G Pad 10.1 General] nicospanas:
OK, I ran the command and now it shows ext4. Just to make sure, before flashing candy which partitions should be mounted and which wipes should I do?
[G Pad 10.1 General] BeeWall:
Mount all, and factory wipe.
[G Pad 10.1 General] nicospanas:
I flashed and I have a running candy! It shows 11.29GB storage. For steps 35 and on do I have to be in twrp? Cause if I try to adb shell when tablet is on I get this message:

error: device unauthorized.

This adb server's $ADB_VENDOR_KEYS is not set

Try 'adb kill-server' if that seems wrong.

Otherwise check for a confirmation dialog on your device

---------- Post added at 06:22 PM ---------- Previous post was at 06:11 PM ----------

Pleas ignore previous, I had to grand su. Ran the command on a running tablet and got these results that look alright. (few numerical differences from OP)

---------- Post added at 06:40 PM ---------- Previous post was at 06:22 PM ----------

I just completed the process successfully! :):):) I can't thank you enough for your help. I was lost for some time. Thanks a lot.
[G Pad 10.1 General] BeeWall:
:good: At least your problem was easy to fix. I believe a few other people in this thread had this problem as well. I wonder why it doesn't work... Is there some sort of boot log? If so, next time this happens we could look at it to find out why it failed.
[G Pad 10.1 General] joeclark:
I wish my mine was easy. I am pretty sure mine is bricked. I am stuck in Cyanogen mod recovery, without debugging enabled and I can't boot into fastboot or download mode.

Also I can't push or pull files to it. I have to pull the SD card and put it in my PC and transfer that way.

sent from a device using an app
[G Pad 10.1 General] fatbas202:
If you are in recovery, you should be able to flash partitions. I'd definitely recommend setting up ADB to do it, but you should be able to format your partitions and flash zips to them.
[G Pad 10.1 General] joeclark:
When I try to flash Roms it won't boot. I have tried just about every ROM in the Android section.

It will just boot back to Cyanogen recovery

sent from a device using an app

ADB shows that it is not authorized (I think that is the right word) I don't have it with me right now it is home and I am at work.
[G Pad 10.1 General] BeeWall:
Does Cyanogen recovery support image flashing? If so, use a computer and SD reader to put twrp on an SD card, and flash twrp. From there, download the laf partition from here, and use the twrp terminal to dd it to wherever laf is on your device(/dev/block/mmcblk0p12 for me), and you should be able to boot to download mode. (If not, dd the abootb, aboot, and boot to their partitions. Abootb is here, and the others are quoted in that post) From there, reflash the kdz. If Cyanogen does not support image flashing, it is possible, but will take a while. I'll post how if I need to.

EDIT: If Cyanogen recovery has a terminal, skip flashing twrp and go straight to laf.

EDIT2: It turns out it might not be time consuming to do this without img flashing. Here is a tutorial on flashing boot.img from a zip. I

THINK

- and I repeat

THINK

- you should be able to replace boot.img with recovery.img and place the twrp img named recovery.img in the zip. I have not tried this, so be careful!

Good luck, whichever method you use!

---------- Post added at 07:49 PM ---------- Previous post was at 07:24 PM ----------

Also, by every, you mean for this device, right? If not, that would cause problems.
[G Pad 10.1 General] joeclark:
The best I can tell, no it does NOT support image flashing.

Yes I only tried the ROMs for the 410

sent from a device using an app

It does not have a terminal emulator

I tried something similar to that to try and reflash TWRP, but it failed.

I will try the link and see what I been do tonight. It looks like it MIGHT work.
[G Pad 10.1 General] BeeWall:
Shame. Someone should talk to the CM devs.

Just wanted to be sure... Anybody can make a mistake.

Once again, someone should talk to CM

How did you do it? Similar as in similar to the zip method?

If this fails, there is a last resort method here for fixing QD 9008, which would work, but you will have to corrput you GPT to get it to work. Obviously a bad idea. This is a last resort only. I'll try to look up more ways if zip does not work.
[G Pad 10.1 General] BeeWall:
If anybody here has NOT flashed the kdz, could they dump ALL (34 I think) partitions on their tablet? I flashed this, but have decided I want the ota. I keep downloading it, but it gives error 0x1111002 after reaching 4% in the install. Download mode shows I am unrooted. I have flashed the v41010d recovery, boot, aboot, abootb, and laf, so I think another partition is giving the error.

Or, if anybody knows what causes this error, that would be just as useful. I tried searching, but found no solution that will work for this tablet

EDIT: It appears I may need a stock, unrooted v41010d system.img If that is the case, never mind.
[G Pad 10.1 General] LeighR:
I tried this but couldn't get it to work. Thanks anyway :)

For anyone else who can't get it working but wants to fix the white lines, I used the terminal built into TWRP and did everything on my device. It was pretty quick.

Go to TWRP then select Advanced and then File Manager. Make sure you can see aboot.img on your SD card (I'm assuming you got as far as downloading, extracting and placing it on your SD CARD) . If you have it on an external SD card, you may need to mount the card first. MAKE SURE YOU CAN SEE THE FILE BEFORE YOU TRY TO FLASH IT.

Go back and open Terminal Command. Then follow the steps in the OP from 4 onwards:
[G Pad 10.1 General] BeeWall:
I can confirm this works.
[G Pad 10.1 General] lggpadser:
Lg gpad 7.0

I need help to uprgrade my lg gpad 7.0 to 5.01 can u put a video totorial or something please ? internal memory fix i need help with that two please help :(:(:(:( :mad: :(
[G Pad 10.1 General] dopekid313:
Possible to fix storage without sd card? :D
[G Pad 10.1 General] BeeWall:
Download the parted binary straight from the tablet, and move it to /system/xbin. Then, reboot to twrp and run the commands from steps 20-28 in the terminal (I believe it is under Advanced). You don't need to flash a rom in step 29, just run "make_ext4fs /dev/block/mmcblk0p33". This worked for me.

---------- Post added at 01:33 PM ---------- Previous post was at 01:30 PM ----------

I have gotten the update to show and download. However, when the install reaches 4%, it fails saying "Err: 0x1111002". From what I've read, it's because the system.img is modified because the v41010d rom is rooted.
[G Pad 10.1 General] dopekid313:
Doesn't seem to work for me, step 20 worked but then the rest didn't it just saids "can't remove 33: no such file or directory" (i assume this is an important step?)

Tried the other steps with no luck either then did what you said after step 28 and came back to a reset phone with no storage fix :p lol its cool though this is pretty hard
[G Pad 10.1 General] BeeWall:
When using the terminal, you have to type everything as one line. So run "parted /dev/block/mmcblk0 rm 34 rm 33 mkpartfs userdata ext2 3439MB 15.8GB name 33 userdata p" (This will remove grow and userdata, create a new partition and name it userdata. It will then print the partition table.) If parted shows the right partitions, run "make_ext4fs /dev/block/mmcblk0p33" to format userdata as ext4. Then, run "parted /dev/block/mmcblk0 p" to ensure userdata shows up as ext4. If it does, you are done! If not, make sure you did not mistype anything.
[G Pad 10.1 General] fatbas202:
I always had issues when the parted binary was anywhere but the external SD card. It would run but wouldn't do everything that I expected it to. Things may be different now, but I almost screwed up my tablet by trying to run it from /system/xbin. There's nothing logical that would make some things not work; it's just loading a binary to memory, but it had issues partitioning the mmc that it was running from. Best of luck if it works for you.
[G Pad 10.1 General] summonholmes:
I'm also on Windows 10. But yes, doing this while booted into 4.4.2 works somewhat better. I've downloaded both SDK and the koush drivers, used them both to no full success, but managed to get parted onto the sd card (sort of). I tried the cp command and it couldn't find parted. I then used 'adb push' to get parted to /sdcard/. Then doing the cp command gives a permission denied error. Suggestions?
[G Pad 10.1 General] fatbas202:
Did you run it as root? After you run `adb shell` you have to run `su` and grant it permission through SuperSU on the tablet. Then you can copy it to wherever you need it and make it executable via `chmod +x /path/to/parted`.
[G Pad 10.1 General] summonholmes:
Thanks, wasn't sure how to get root permission since I'm somewhat new to this. I got parted to /sbin/ but was still unable to run adb shell through Windows to make parted executable. Luckily, the terminal in TWRP allowed me to complete the partition steps without a computer. Thanks for your help!
[G Pad 10.1 General] nmnm4alll:
Worked

That made sense now, it worked like charm, thanks again :)
[G Pad 10.1 General] fatbas202:
Excellent! I'm glad I was able to help you two get it working. Thanks for posting your success so others can have that feedback.
[G Pad 10.1 General] ezrhel26:
after 'parted /dev/block/mmcblk0' when i typed 'help' its states "sh: help: not found" can anyone help me? thanks.
[G Pad 10.1 General] fatbas202:
Are you running this under Android or TWRP? Are you running it as root? I need more information as to where you are at to help you.
[G Pad 10.1 General] ezrhel26:
thanks for replying on my novice question.. hehehhehe. im running under TWRP and running as root. im having a hard time viewing the partition after 'parted /dev/block/mmcblk0' as if parted is not working. please note that my os is windows10.

i also tried running the other way.. using "minimal adb and fastboot.exe" i already came to the point that im the same as your "guide # 28 attachment" using '/system/bin/mke2fs -t ext4 /dev/block/mmcblk0p33' on windows (33 3439MB 15.8GB 12.3GB ext4 userdata). but after 'mount | grep userdata' my /data is just 3.6GB. what did i miss something? sorry for my english :D
[G Pad 10.1 General] fatbas202:
Absolutely.

You'll have to reboot after you format to ext4. The kernel will have your old partition table loaded and the most straightforward way to correct this is to just reboot TWRP. Essentially the system thinks that /data is still mounted even though you've pulled the rug out from under it. If the mke2fs command did not error then you should be good to go.
[G Pad 10.1 General] gquint90:
Can I do this after I flash the Candy rom?
[G Pad 10.1 General] fatbas202:
Yes. Post if you run in to problems and I'll try to help you out. All of the steps should be the same except you shouldn't have to reflash the ROM. Keep in mind that you will lose all of the data on your device though.
[G Pad 10.1 General] ezrhel26:
hi my V410 is fixed!!! yehey!!! thanks a lot,, i use "minimal adb and fastboot.exe' method and i use `make_ext4fs /dev/block/mmcblk0p33` command to format userdata from ext2 to ext4. my v410 turns black but i just booted to TWRP. (guide # 30 & 31) tap Wipe> Swipe to Factory Reset........Tap Reboot> System and VOILA!!!!!!!its just weird that my Storage is 8GB but the available space is 11+GB.. anyway Thanks alot!!!!!!!!
[G Pad 10.1 General] gquint90:
Cool thank you for replying :good:. I will try this today.
[G Pad 10.1 General] fatbas202:
Is your tablet an 8GB or a 16GB model? I'm confused as to why it says that your storage is 8GB...
[G Pad 10.1 General] ezrhel26:
my tablet is 16GB at&t version. after factory reset, what i see in my "Total Space" in "Settings" is 8GB but my "Available" space is 11GB. but after flashing to skinny ROM (I flashed it to stock so i can use the Quick Remote), the "Total Space" is now 16GB. i think its just a minor glitch.. then again thanks to your tutorial, because without this i cannot recover my bricked tablet.
[G Pad 10.1 General] fatbas202:
Ah, I know what's going on. The Android image in the KDZ is for an 8GB device so it only "sees" 8GB. When you first flash it and it repartitions the userdata partition to 4GB it says it's 8GB, but with 4GB of it mysteriously used by something.

So yeah, it's just that test image's hard coded limit.
[G Pad 10.1 General] gquint90:
HA. idk what I did wrong but I messed it up. After I restarted the phone I followed the last steps and it didn't show the the 16gb fix. So I restarted the tablet and now it's just flashing the teamwin logo like if its trying to enter TWRP but it does't :crying:

EDIT: I was able to turn it off, and get back on TWRP. I think I'm going to just start over.

---------- Post added at 02:05 PM ---------- Previous post was at 01:24 PM ----------

I started over. after I finished I rebooted and now it only shows the screen to decrypt the tablet.
[G Pad 10.1 General] fatbas202:
That's not something that I would have expected. Sorry to hear that you're having trouble. :( I'd recommend flashing the KDZ and starting over just to make sure things don't get messed up any further.

I'll be back on here Monday to do what I can to help.
[G Pad 10.1 General] gquint90:
OK. Thanks. I'll wait for your return. I did start over but I keep on getting to that decrypt page. Not sure what I'm doing wrong. But I'm going thru the replies to get some ideas of what I'm doing wrong.
[G Pad 10.1 General] breakone9:
I now have lines in all screens, not just boot animations

At first everything was fine for several days. I then rebooted and now I have the white lines over the entire screen... I tried posting a link, but xda doesn't like me yet.
[G Pad 10.1 General] BeeWall:
It worked for me. Maybe there is some difference between executing on the tablet via TWRP (like I did) and using adb shell (like I think you did. Correct me if I'm wrong.) Just wondering, , in your instructions, step 18 is

. Isn't this also executing from the internal mmc?
[G Pad 10.1 General] fatbas202:
Whoops. I got my stuff backward. My bad. Yes, I was running it from the internal MMC, and yes over ADB. Thanks for correcting me on that - wouldn't want to screw up someone else's work.
[G Pad 10.1 General] BeeWall:
Is there any way I could find an unrooted system.img, or would i need a non test kdz, which we obviously don't have? I really want that update...
[G Pad 10.1 General] newbreedsoftware:
I found an easier way to get rid of the vertical lines rather than flashing the aboot.img file as that messed up my video.

Flash TWRP

Boot into TWRP

Flash KDZ or other

Device: LG G Pad 7.0 (v410)
[G Pad 10.1 General] BeeWall:
TWRP can't flash KDZ files. Do you mean zip?
[G Pad 10.1 General] newbreedsoftware:
Yes, my apologies
[G Pad 10.1 General] BeeWall:
So flashing a zip fixes the white lines... I feel like this didn't happen for me. What zip did you flash?
[G Pad 10.1 General] newbreedsoftware:
I have a stock 4.4.2 zip that I flashed
[G Pad 10.1 General] fatbas202:
The aboot image in the OP is from a stock 4.4.x ROM. You should have the same outcome if you apply a zip that flashes that partition or if you flash that partition directly.
[G Pad 10.1 General] newbreedsoftware:
Anyone have an un-altered partition list file for the v410? I think I messed up my internal storage as it only shows 4gb of total space instead of 16 and I would like to use aparted to fix it.
[G Pad 10.1 General] BeeWall:
I don't think the stock ROM includes the aboot, at least the one by timmytim. If it was that rom, then maybe there is something else in the rom that fixes the lines.

The OP has an image attached. Here it is:

Did you run the parted commands in the op? If not, that would cause the problem, as the data partition is quite small before those steps.

Did you use the timmytim stock rom, a personal backup, or one from somewhere else? If it isn't timmytim's, could I see it? I'm wondering if your rom included an aboot, or if there is something else fixing the lines.
[G Pad 10.1 General] newbreedsoftware:
well I think running that parted command is what messed up my tablet in the first place! the instructions werent very clear on what to do after running the commands, do I mount data then reboot or just reboot?

The zip I flashed was downloaded from a post somewhere on here haha, I think it was labeled 'Stockv410_rooted.zip'
[G Pad 10.1 General] fatbas202:
What commands are you referring to? If you tell me exactly what your question is about I'll update the OP to make it more clear.