Related
Hi,
I urgently need help for my nexus 7 that has stopped charging or recognising even the original ASUS usb cable (have tried many others as well, same result). I'm currently charging it via the method of powering it of and plugging it in without the android os running. I have even tried to connect it to my PC in bootloader mode. I have the custom trinity kernel install and want to return my device to stock kernel and os state. However I do have TWRP and need help from there to install the stock image. I have previously tried many thing such as completely wiping the system and clearing any caches in TWRP. Also I have seen that in TWRP it recognises my usb (connected via OTG cable).
So could anyone please help me with returning my nexus 7 back to stck state using TWRP.
And is there also a way of unrooting my device without using PC (using TWRP instead)?
-- Update -- I have no OS installed (tried to delete custom kernel) --
Thanks in advance.
Nexus 7 state:
- custom trinity kernel
- TWRP
- USB connection to PC not working
There should be help for you here in this sticky in this Q&A forum:
http://forum.xda-developers.com/showthread.php?t=1907796
Note 2 - Nexus 7 - Charge - Player 5.0 - Fascinate
<><><><><><><><><><>
Read twice, flash once
USB doesn't work > can't use adb
ezas said:
There should be help for you here in this sticky in this Q&A forum:
http://forum.xda-developers.com/showthread.php?t=1907796
Note 2 - Nexus 7 - Charge - Player 5.0 - Fascinate
<><><><><><><><><><>
Read twice, flash once
Click to expand...
Click to collapse
Thanks for replying, but the problem is that I can't use adb (can't connect with PC), the only thing I can do is access TWRP and usb storage (via OTG in TWRP). So I need the stock rom in a "rom" like format so I can flash it using TWRP. Could anyone please tell me another way or give the stock rom in a format that TWRP can flash (ASAP plz). Thanks in advance
The easiest thing (of course) would be if somebody put together a flashable return-to-stock ROM. I've done it before for other devices, but haven't gotten around to doing it for the N7.
You didn't really say whether you were talking about (a) "exactly stock", or whether you wanted (b) a stock recovery put back in place, or whether you were (c) also trying to get the bootloader re-locked.
Case (c) can not be done using anything except fastboot (unless you previously recorded your bootloader while it was in a locked state), so I'll just assume that you are talking about (a) and (b), and that you are going to leave the bootloader unlocked - or you had already locked your bootloader after rooting and installing a custom recovery.
I see that you are trying (in another thread) to get somebody to make you a Nandroid backup of /system from a pure stock ROM. That would be one way of doing things (making sure that you get a grouper image if you have a grouper (WiFi) or a tilapia image if you have a tilapia N7 (3G) device). And while we are on the subject, I'll throw out another way you can do just that:
- The Google "factory" system.img files are in a sparse ext4 format that can not be directly mounted (e.g. using a loopback mount) in Linux. But, the Android toolkit includes a utility (for Linux) called "simg2img" (aka Sparse IMaGe to IMaGe) which can convert the sparse ext4 "system.img" image file to a regular ext4 format image file. This could be created, mounted via a loopback (using Linux, of course), and then a "tar" backup of the whole shebang is made. The TWRP and CWM nandroid backup images are just TAR archives. So If you grok what I am telling you, you have the power to create your own "Nandroid" /system backup file directly from the factory images. (Windoze-only doods need not apply.)
If you take this route, then you only need the recovery image plus the hacked "Nandroid" backup to "restore" directly to a pure stock device using only a custom recovery. (The recovery partition can be overwritten while the recovery is running because the partition is not "in use" after the boot completes - the recovery kernel and ramdisk live entirely in memory while they are running.)
But as I noted above, this will not re-lock the bootloader. It will put stock software back on the device, though.
If you intend to save anything off the device, do it before you begin this. The stock recovery "factory reset" procedure clears the ENTIRE /data partition including the pseudo-SD card area.
good luck
how would you do the procedure
bftb0 said:
The easiest thing (of course) would be if somebody put together a flashable return-to-stock ROM. I've done it before for other devices, but haven't gotten around to doing it for the N7.
You didn't really say whether you were talking about (a) "exactly stock", or whether you wanted (b) a stock recovery put back in place, or whether you were (c) also trying to get the bootloader re-locked.
Case (c) can not be done using anything except fastboot (unless you previously recorded your bootloader while it was in a locked state), so I'll just assume that you are talking about (a) and (b), and that you are going to leave the bootloader unlocked - or you had already locked your bootloader after rooting and installing a custom recovery.
I see that you are trying (in another thread) to get somebody to make you a Nandroid backup of /system from a pure stock ROM. That would be one way of doing things (making sure that you get a grouper image if you have a grouper (WiFi) or a tilapia image if you have a tilapia N7 (3G) device). And while we are on the subject, I'll throw out another way you can do just that:
- The Google "factory" system.img files are in a sparse ext4 format that can not be directly mounted (e.g. using a loopback mount) in Linux. But, the Android toolkit includes a utility (for Linux) called "simg2img" (aka Sparse IMaGe to IMaGe) which can convert the sparse ext4 "system.img" image file to a regular ext4 format image file. This could be created, mounted via a loopback (using Linux, of course), and then a "tar" backup of the whole shebang is made. The TWRP and CWM nandroid backup images are just TAR archives. So If you grok what I am telling you, you have the power to create your own "Nandroid" /system backup file directly from the factory images. (Windoze-only doods need not apply.)
If you take this route, then you only need the recovery image plus the hacked "Nandroid" backup to "restore" directly to a pure stock device using only a custom recovery. (The recovery partition can be overwritten while the recovery is running because the partition is not "in use" after the boot completes - the recovery kernel and ramdisk live entirely in memory while they are running.)
But as I noted above, this will not re-lock the bootloader. It will put stock software back on the device, though.
If you intend to save anything off the device, do it before you begin this. The stock recovery "factory reset" procedure clears the ENTIRE /data partition including the pseudo-SD card area.
good luck
Click to expand...
Click to collapse
Thanks for the information. I do want my device (grouper WiFi) to go back to factory state (c - get rid of superSU and busybox). However I do have some questions regarding the creating nandroid backup by your method. As I have Ubuntu 12.10 installed, how would I do the procedure? And what do you mean by "mounted via a loopback"? Also is it only "system.img", what about "boot.img", "recovery.img" and "userdata.img"?
Is it possible that you could maybe give me the nandroid backup.tar as I am not much experienced, I would really appreciate it.
Thanks in advance.
Well if a (stock) factory reset erases the /data partition, userdata.img sorta doesn't matter, right?
boot.img and recovery.img are just binary blobs, so they could be taken from the factory image and used "as is" as part of your hand-assembled "Nandroid Backup"
That only leaves system.img - previously discussed.
$ sim2img google-factory-sparse-system.img ext4.system.img
$ sudo /bin/bash
# losetup /dev/loop0 ./ext4.system.img
# mkdir /mnt/Foo
# mount -t ext4 -o ro /dev/loop0 /mnt/Foo
# cd /mnt/Foo
# tar cf /home/newb/fakenandroidsystem.tar .
# cd /home/newb
# chown newb.newb fakenandroidsystem.tar
# umount /mnt/Foo
# rmdir /mnt/Foo
# losetup -d /dev/loop0
# exit
$
You will need to either find the sim2img utility as a prebuilt or download it and build it. You might need to fool with tar command-line options during the archive creation - I notice that the TWRP nandroid tar archives (system.emmc.ext4.win) seem to have absolute pathnames rooted at "/" rather than "/system". Don't know if this is significant or not.
good luck
PS it goes without saying that you need to be extremely careful about giving up root when doing this: imagine that you restore a bad /system image along with a stock recovery - you will have an unbootable device that can not be rooted without hardware repair of the USB. You might want to initially do a test restore or two without overwriting the custom recovery
with the stock version. And keep a flashable ROM on the SDcard, too. Once you have everything working correctly, only then should you restore the recovery back to stock.
Do I load the nandroid direct to my USB device (connect via OTG and then flash in TWRP) after converting the .img and from what path in ubuntu shell am I writing those commands?
Sounds like you don't have adb set up there is a ppa to set it up for you Google for it. Then try to run adb devices and it should show up
Sent from my PG86100 using Tapatalk 2
There is no problem with adb as it did work before (when USB port did work), it doesn't even show up in device manager(windows) anymore. I cannot connect with my device to my PC via USB as the port is faulty nor does it charge with the oem wall charger when system is one. I can only charge it when the system is completely turned off and then when I plug it in PC/wall charger via USB. However I can access my USB drive via OTG only in TWRP and this is only way I can flash/restore to stock system. I want to return it to stock to send it back to google (exchange).
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.
I Replaced the build.prop on my rooted Google nexus 6p running Android 7.0 with the build.prop file from the pixel to run Google Assistant.The phone is now stuck on the Google logo during boot,PLEASE HELP.
Did you make a backup copy of the file before replacing it, are you rooted, and have TWRP installed?
If so, reboot to recovery, use TWRP Terminal function to copy the backup of the build.prop to the modified one.
dratsablive said:
Did you make a backup copy of the file before replacing it, are you rooted, and have TWRP installed?
If so, reboot to recovery, use TWRP Terminal function to copy the backup of the build.prop to the modified one.
Click to expand...
Click to collapse
I did not make a back up but I am rooted and have Twrp installed.What can i do from here?
If you can boot to bootloader you should be able to replace the file with a standard one.
Alden1227 said:
I Replaced the build.prop on my rooted Google nexus 6p running Android 7.0 with the build.prop file from the pixel to run Google Assistant.The phone is now stuck on the Google logo during boot,PLEASE HELP.
Click to expand...
Click to collapse
same here please help.....freaking out
1. The build.prop contains the settings for a specific build for a specific phone. You can't just replace it from another build, not to mention another phone. Well, I guess, you already know this.
2. You should know exactly which build you were on. Exactly. Then:
* What I would do, is download the factory image from https://developers.google.com/android/nexus/images#angler
o Extract it, extract the image-angler-...zip, and mount the system.img, find the build.prop and adb push it to the phone.
o Reboot
* But you can also ask somebody who has the exact build as you do, and ask for the build.prop. Then push it to the phone.
Either restore from backup or edit the buildprop (if possible) I guess.
You only needed to edit 2 lines in the buildprop though, why replace the whole thing?
Alden1227 said:
I did not make a back up but I am rooted and have Twrp installed.What can i do from here?
Click to expand...
Click to collapse
First thing's first. Since you didn't just edit your build.prop, but replaced it with another, try setting permissions.
Step 1: Boot to TWRP > Mount > Select "System"
Step 2: Advanced > File Manager
Step 3: Navigate to /system/build.prop
Step 4: Select "chmod" and type "644" (don't include quotation marks)
Reboot and see if it works. If the permissions weren't right and you didn't change them, you'd most likely be in a boot loop. If this doesn't work you can just flash your system.img again. It won't wipe your internal storage, data (installed apps, etc.) If you have custom host files for ad blocking, you may need to apply them again.
If that does not work;
I'm going to assume you were on stock Nougat. Download the factory image (same build you were on before) and unzip the file. You'll end up with a folder with another zip archive in it. Unzip that as well. Inside you'll find a file named "system.img"
Move that system.img file to your ADB/fastboot folder. Shift+Right Click that folder and select "Open command window here"
Hold volume down + power to boot into the bootloader. Connect the phone to the PC and in the command prompt, type "fastboot devices" (no quotes again. ) It should show your devices serial number. If it does, perfect. If not, check your ADB/fastboot installation.
Once you get fastboot to show your serial number all you need to do is type;
Code:
fastboot flash system system.img
That should do it. If you need any more help, just reply back.
Edit: @istperson, AFAIK, you cannot pick out files from a .img file like that. When I right click it on my system and choose mount it tells me the image file is corrupted. Tried downloading again and hashes match. Windows 10. I use 7zip as well, and that can't open it either. Is there another program to use or is something whacky on my end? Wouldn't doubt it. Just took a Win10 update yesterday and it's been acting up on me all day. :/
RoyJ said:
Edit: @istperson, AFAIK, you cannot pick out files from a .img file like that. When I right click it on my system and choose mount it tells me the image file is corrupted. Tried downloading again and hashes match. Windows 10. I use 7zip as well, and that can't open it either. Is there another program to use or is something whacky on my end? Wouldn't doubt it. Just took a Win10 update yesterday and it's been acting up on me all day. :/
Click to expand...
Click to collapse
It's a sparse image, you have to convert it to normal mage with simg2img. Then you can mount it normally.
istperson said:
It's a sparse image, you have to convert it to normal mage with simg2img. Then you can mount it normally.
Click to expand...
Click to collapse
Awesome, thanks!
Fixed the issue
frreak said:
same here please help.....freaking out
Click to expand...
Click to collapse
I got mine to work by flashing Android 7.0
same thing happened to me.... stuck on google even after flashing stock....
dadoc04 said:
same thing happened to me.... stuck on google even after flashing stock....
Click to expand...
Click to collapse
Flash stock boot, system and vendor img files.
Sent from my Pixel XL using XDA-Developers mobile app
Same thing happened to me at first (though I did not use the build prop from a Pixel). I just dirty flashed my ROM (Octo N) and it then got passed the Google screen and loaded with no problem. I updated my build prop manually in order to get Google Assistant to work, and it's been working great ever since.
RoyJ said:
First thing's first. Since you didn't just edit your build.prop, but replaced it with another, try setting permissions.
Step 1: Boot to TWRP > Mount > Select "System"
Step 2: Advanced > File Manager
Step 3: Navigate to /system/build.prop
Step 4: Select "chmod" and type "644" (don't include quotation marks)
Reboot and see if it works. If the permissions weren't right and you didn't change them, you'd most likely be in a boot loop. If this doesn't work you can just flash your system.img again. It won't wipe your internal storage, data (installed apps, etc.) If you have custom host files for ad blocking, you may need to apply them again.
If that does not work;
I'm going to assume you were on stock Nougat. Download the factory image (same build you were on before) and unzip the file. You'll end up with a folder with another zip archive in it. Unzip that as well. Inside you'll find a file named "system.img"
Move that system.img file to your ADB/fastboot folder. Shift+Right Click that folder and select "Open command window here"
Hold volume down + power to boot into the bootloader. Connect the phone to the PC and in the command prompt, type "fastboot devices" (no quotes again. ) It should show your devices serial number. If it does, perfect. If not, check your ADB/fastboot installation.
Once you get fastboot to show your serial number all you need to do is type;
That should do it. If you need any more help, just reply back.
Edit: @istperson, AFAIK, you cannot pick out files from a .img file like that. When I right click it on my system and choose mount it tells me the image file is corrupted. Tried downloading again and hashes match. Windows 10. I use 7zip as well, and that can't open it either. Is there another program to use or is something whacky on my end? Wouldn't doubt it. Just took a Win10 update yesterday and it's been acting up on me all day. :/
Click to expand...
Click to collapse
Chmod 755 worked too
Hello,
Please and thanks in advance for any assistance!
I've successfully rooted my HD8 7th gen fire tablet, thanks to the many helpful posts here. However during some of my failed attempts while using Magisk, TWRP App, etc, I've somehow managed to wipe out my stock Recovery partition/files. I can do normal booting fine and I'm sure that I have root, as confirmed by the # at ADB shell and the Root Checker apps available.
I've tried the following:
-Entered Fastboot mode and tried several commands there: always resulting in a 'the command you input is restricted on locked hw' (So, obviously, my bootloader is locked (but I've overwritten it somehow, so it makes me think that at some point I was able to unlock it and overwrite it?)
-Flashfire, TWRP, Magisk and Flashify apps - successful messages every time I try, but no joy when trying to enter recovery mode (it's possible I'm trying to flash the wrong recovery.img file? - does anyone have it and what is it's size? i searched my tablet for the file and found two: one 17mb and the other 8mb - both "flashed" successfully, but no joy when trying to boot into them)
-adb su commands
-Giving up and doing a full Factory Restore via the GUI - it just tries to reboot to the recovery mode, which doesn't exist, so i can't do anything.
-Giving up and doing a full Factory Restore via Fastboot mode - 'the command you input is restricted on locked hw'
I was so happy I was able to obtain root, but if something gets wonky or I decide to try the much raved about resurrection image, i need to have the recovery boot available if/when everything goes wrong.
Please and thanks again for any advice.
Daveychan said:
Please and thanks again for any advice.
Click to expand...
Click to collapse
It's fairly simple but cumbersome to recreate recovery with root. You need to locate the original install-recovery script for your Rom. You may search in /etc or /system/etc . Most likely though your SuperSu deleted it.
So you download your particular Rom version from amazon, unpack it into a system image via mtk-extractor, mount that system image, and find the files.
You can mount this extracted system.bin either on Linux, or directly on your tablet. Just push it to /sdcard, and do this: https://stackoverflow.com/questions/36448234/how-to-mount-a-loop-device-in-android
Then you run the full install-recovery script which will patch your boot.img into recovery partition.
Alternatively, you can beg someone here to dump their HD8 2017 recovery, and upload the image here. So you can dd it in using root into the appropriate partition.
See, I told you - it's all very simple !
Edit: @dondraper23 - can you help a fellow XDA-er? Just dd your HD8 2017 recovery, and post it here.
Code:
dd if=/dev/block/platform/soc/by-name/recovery of=/sdcard/recovery.img
Then zip it, and post it here.
Thank you very much for the fast reply. Much appreciated!
I’ll give this a try ASAP and post back.
If anyone has the recovery.img for the HD8 Gen7, please do post it.
Thank you again!
Okay, i've spent several hours on this and I need to ask for more help.
I managed to get the system.img file from the Amazon .bin as you described. (I used the MTK Extractor for that. It's 1.57 GB by the way.) Next, I moved the system.img file to my Fire's SD card, then I connected the Fire to my Linux, and mounted the system.img file in Linux so I can see the file directory.
I can now see the install-recovery.sh file, located in the /bin folder of the mounted image, but it's read-only. Even by opening to that path via terminal with SU and trying to chmod 777 the file, it's still locked as read-only.
So, I don't know what to do next. I can't copy the file, and I don't see how to run the file via Fire anyway. (Was I supposed to somehow mount the system.img file via ADB commands and then run it that way? If so, I don't know how to do that.)
Sorry if I've asked something obvious or silly. As before, I appreciate the assistance!
Please and Thanks!
Daveychan said:
Okay, i've spent several hours on this and I need to ask for more help.
I managed to get the system.img file from the Amazon .bin as you described. (I used the MTK Extractor for that. It's 1.57 GB by the way.) Next, I moved the system.img file to my Fire's SD card, then I connected the Fire to my Linux, and mounted the system.img file in Linux so I can see the file directory.
I can now see the install-recovery.sh file, located in the /bin folder of the mounted image, but it's read-only. Even by opening to that path via terminal with SU and trying to chmod 777 the file, it's still locked as read-only.
So, I don't know what to do next. I can't copy the file, and I don't see how to run the file via Fire anyway. (Was I supposed to somehow mount the system.img file via ADB commands and then run it that way? If so, I don't know how to do that.)
Sorry if I've asked something obvious or silly. As before, I appreciate the assistance!
Please and Thanks!
Click to expand...
Click to collapse
Sure, just copy that install-recovery.sh file to your tablet, into /data/local/tmp. There is also another file you will need, it's /system/recovery-from-boot.p . Copy this one to /data/local/tmp as well. Then edit your install recovery script, to point to this /data/local/tmp/recovery-from-boot.p . Then just su, chmod 777 your install recovery script, and run it. It should take your boot, and patch it into recovery using recovery-from-boot.p patch file.
Thank you for the fast reply. But because that sh file its read-only, I can't open it or copy it.
Error when running the script
Hello again,
I managed to get around the read-only problem (opening everything as Superuser in Linux was the trick to making that work, for other noobs who may be following along with my pain here.)
I grabbed those two files as you indicated and followed the instructions. Unfortunately I was met with a ton of error messages. Here they are:
=====================
[email protected]:/data/local/tmp # /data/local/tmp/install-recovery.sh
contents of partition "/dev/block/platform/mtk-msdc.0/by-name/recovery" didn't match EMMC:/dev/block/platform/mtk-msdc.0/by-name/recovery:7022592:38eeb844c578f6bbfb6edf8ddf7ba1112200a25c
file "EMMC:/dev/block/platform/mtk-msdc.0/by-name/recovery:7022592:38eeb844c578f6bbfb6edf8ddf7ba1112200a25c" doesn't have any of expected sha1 sums; checking cache
failed to stat "/cache/saved.file": No such file or directory
failed to load cache file
patch EMMC:/dev/block/platform/mtk-msdc.0/by-name/boot:4720640:9dc6d0ebab0b237a7b2f31ae0fabe026da83cda5: LoadPartitionContents called with bad filename (EMMC:/dev/block/platform/mtk-msdc.0/by-name/recovery)
contents of partition "/dev/block/platform/mtk-msdc.0/by-name/recovery" didn't match EMMC:/dev/block/platform/mtk-msdc.0/by-name/recovery
contents of partition "/dev/block/platform/mtk-msdc.0/by-name/boot" didn't match EMMC:/dev/block/platform/mtk-msdc.0/by-name/boot:4720640:9dc6d0ebab0b237a7b2f31ae0fabe026da83cda5
source file is bad; trying copy
failed to stat "/cache/saved.file": No such file or directory
failed to read copy file
=====================
I'm attaching the two files i pulled from the system.img file - as converted from the .bin file downloaded from Amazon (as above), in case you are still willing to help out and can take a look. (I edited the install-recovery.sh file to the correct path already, so it's not the original anymore.)
MUCH APPRECIATED!
Thank you!
Daveychan said:
Hello,
Please and thanks in advance for any assistance!
I've successfully rooted my HD8 7th gen fire tablet, thanks to the many helpful posts here. However during some of my failed attempts while using Magisk, TWRP App, etc, I've somehow managed to wipe out my stock Recovery partition/files. I can do normal booting fine and I'm sure that I have root, as confirmed by the # at ADB shell and the Root Checker apps available.
I've tried the following:
-Entered Fastboot mode and tried several commands there: always resulting in a 'the command you input is restricted on locked hw' (So, obviously, my bootloader is locked (but I've overwritten it somehow, so it makes me think that at some point I was able to unlock it and overwrite it?)
-Flashfire, TWRP, Magisk and Flashify apps - successful messages every time I try, but no joy when trying to enter recovery mode (it's possible I'm trying to flash the wrong recovery.img file? - does anyone have it and what is it's size? i searched my tablet for the file and found two: one 17mb and the other 8mb - both "flashed" successfully, but no joy when trying to boot into them)
-adb su commands
-Giving up and doing a full Factory Restore via the GUI - it just tries to reboot to the recovery mode, which doesn't exist, so i can't do anything.
-Giving up and doing a full Factory Restore via Fastboot mode - 'the command you input is restricted on locked hw'
I was so happy I was able to obtain root, but if something gets wonky or I decide to try the much raved about resurrection image, i need to have the recovery boot available if/when everything goes wrong.
Please and thanks again for any advice.
Click to expand...
Click to collapse
You shuld try:
-Extract an ota update in a folder
-Run from the folder with the extracted files
Code:
fastboot flash boot boot.img
the recovery is in boot.img, doing this helped me on a similar situation
Thanks to @bibikalka for pointing me to this thread
On the 7th gen fire hd8 TWRP doesn't work yet
t0x1cSH said:
You shuld try:
-Extract an ota update in a folder
-Run from the folder with the extracted files
Code:
fastboot flash boot boot.img
the recovery is in boot.img, doing this helped me on a similar situation
Thanks to @bibikalka for pointing me to this thread
On the 7th gen fire hd8 TWRP doesn't work yet
Click to expand...
Click to collapse
It's not enough to reflash boot.img ! Recovery is created on boot by patching boot.img, but the OP's fire has messed up recovery creation scripts due to SuperSu. So he needs to either re-run the recovery creation script manually - which seems to produce errors, or simply flash a full recovery image - hence my request to extract it from a fire with working recovery.
Hey, I'll pull the recovery off mine tomorrow
NFSP G35 said:
Hey, I'll pull the recovery off mine tomorrow
Click to expand...
Click to collapse
That would be fantastic! Thank you much!
Here you go
Daveychan said:
That would be fantastic! Thank you much!
Click to expand...
Click to collapse
Just FYI, to flash this image file into recovery (assuming you have the recovery image sitting in /sdcard/recovery.img):
Code:
dd if=/sdcard/recovery.img of=/dev/block/platform/mtk-msdc.0/by-name/recovery
bibikalka said:
It's not enough to reflash boot.img ! Recovery is created on boot by patching boot.img, but the OP's fire has messed up recovery creation scripts due to SuperSu. So he needs to either re-run the recovery creation script manually - which seems to produce errors, or simply flash a full recovery image - hence my request to extract it from a fire with working recovery.
Click to expand...
Click to collapse
this is the recovery partition straight from my hd8 2017
but i am very curious about a thing, if you look at booth the boot.img and the recovery partition they contains exactly the same data, in the same structure so why cant he simply flash boot.img?
t0x1cSH said:
this is the recovery partition straight from my hd8 2017
but i am very curious about a thing, if you look at booth the boot.img and the recovery partition they contains exactly the same data, in the same structure so why cant he simply flash boot.img?
Click to expand...
Click to collapse
They do have a lot of similarities, that's why recovery is created by patching boot via a relatively small patch file. But, they are still different! That recovery menu is contained entirely within the recovery image, while the boot image does not do that.
Just to add to this, you don't need to flash the boot.img to use install-recovery.sh.
You can also modify the script to read boot from an img file.
k4y0z said:
Just to add to this, you don't need to flash the boot.img to use install-recovery.sh.
You can also modify the script to read boot from an img file.
Click to expand...
Click to collapse
Do you care to post a script that does that, and writes into a recovery image file? The syntax of that patch command is a bit messy, so I would not mind having a debugged working script
Hello again,
My apologies for the delay, work was busy this week, and I couldn't find the time to check the solution until now.
I'm so VERY HAPPY to report that all worked well, and the recovery.img and the command line you provided worked perfectly. (WOW! Thank you!)
For those who want the details, the message after the command in the terminal was:
==
#dd if=/sdcard/recovery.img of=/dev/block/platform/mtk-msdc.0/by-name/recovery
----
34816+0 records in
34816+0 records out
17825792 bytes transferred in 1.159 secs (15380320 bytes/sec)
==
I then did a full power down, and then a started it up again while holding the top-left Volume key and the Power key, and look at that! I'm sitting at the Amazon system recovery screen again! <insert YAY! here>
I'm not sure if it matters, but I thought I'd mention it. At the bottom of the screen in orange letters, it says:
===
E:Error in /cache/recovery/last_kmsg
(No space left on device)
===
So, after a little bit of searching, I selected "wipe cache partition", rebooted again into recovery, and the error is gone now.
Another normal reboot started the "Optimizing apps..." thingy, but it finished quickly and I can confirm that all my stuff is still there. Just to be sure, I did another reboot to recovery, no error messages this time, and then another regular reboot, with no optimizing.
It appears that everything in my world is good again!
My sincerest gratitude and appreciation to all who helped contribute and support this solution.
THANK YOU VERY MUCH!
Daveychan said:
the much raved about resurrection image .
Click to expand...
Click to collapse
Out of curiosity, what is this? There is an image, other than stock, for the 7th Gen HD8?
Resurrection-remix
xnatex21 said:
Out of curiosity, what is this? There is an image, other than stock, for the 7th Gen HD8?
Click to expand...
Click to collapse
It's a WIP for the HD8 I've read. My friend has this on his HD7 and swears it's twice as fast as the regular.
Here's some info:
https://forum.xda-developers.com/kindle-fire-hd/7-development/rom-resurrection-remix-5-1-x-t3234535
and here:
https://forum.xda-developers.com/le-pro3/development/9-0-resurrection-remix-v7-0-t3894663
I have two N4s with broken screens, one of which has USB debugging enabled etc.
I created a TWRP backup of boot, system & data on the one with USB enabled and transferred it over to the other one.
I now can't restore that backup. I have to use TWRP's open recovery script in an ADB shell because the screens are broken. I am using:
Code:
adb shell twrp restore /data/media/0/TWRP/BACKUPS/"serial no"/
but which initially works, then says "no partitions selected for restore".
If I put "SDBM" after the path, it says "setting restore options: SDBM" then the same thing - "no partitions selected for restore".
If I put "SDBM" after "restore" i.e. before the path name it says "Restoring SDBM... Unable to locate backup 'SDBM'"
I can't find any help via google and I'm stuck now - how can I restore a backup with adb shell twrp?
mrmrchoice said:
I have two N4s with broken screens, one of which has USB debugging enabled etc.
I created a TWRP backup of boot, system & data on the one with USB enabled and transferred it over to the other one.
I now can't restore that backup. I have to use TWRP's open recovery script in an ADB shell because the screens are broken. I am using:
Code:
adb shell twrp restore /data/media/0/TWRP/BACKUPS/"serial no"/
but which initially works, then says "no partitions selected for restore".
If I put "SDBM" after the path, it says "setting restore options: SDBM" then the same thing - "no partitions selected for restore".
If I put "SDBM" after "restore" i.e. before the path name it says "Restoring SDBM... Unable to locate backup 'SDBM'"
I can't find any help via google and I'm stuck now - how can I restore a backup with adb shell twrp?
Click to expand...
Click to collapse
From what you wrote, I see that you provided the path to the backup directory instead of to the specific backup directory.
Your path is too short because it does not contain the name of the directory that was created during the backup.
If possible, always try to paste a significant piece of text from the terminal where you performed the action, it really makes it easier to find a solution.
ze7zez said:
From what you wrote, I see that you provided the path to the backup directory instead of to the specific backup directory.
Your path is too short because it does not contain the name of the directory that was created during the backup.
If possible, always try to paste a significant piece of text from the terminal where you performed the action, it really makes it easier to find a solution.
Click to expand...
Click to collapse
Hi, thanks, I got there not long after I posted this HOWEVER adding the specific backup directory now gives me an error about digest verification (I didn't generate an MD5 hash when I made the backup). This is when trying to restore using the same flag that I used to skip MD5 generation when I made the backup.
It asks me to deselect digest verification but I can't do that on the touch screen (as it's broken) and don't know if it's possible to do this via abd?
Thanks!