If there is any trouble, leave it in the comments, i'll respond
I am not responsible if this crashes, bricks, causes nuclear warfare, or anything else that may happen, I'll try to fix it if you put your problem in the comments
Extract boot.img using a few simple adb commands
Hi XDA, I want to educate you on how to extract your boot.img using adb. Since systemless root and kernels all utilize the boot.img, undoing these changes consist of just flashing the boot.img in TWRP!
I pulled this from a RootJunky video and it worked on my pixel xl on any rom
Prerequisites:
You have to use TWRP (img or install, depending on the method)
Locating the boot.img
There are many tools used for this, I just like using the logs of an installer
Flash the TWRP installer and read the logs
It says "found boot image in *path*" (Usually /dev/block/sda19 or sda20)
If you want confirmation, flash magisk and it should say where your boot.img is
Extraction of the boot.img (2 ways)
Without TWRP installed
fastboot boot twrp.img
Open a terminal (on a computer) and type adb shell
your window should have only a ~#
Type this command in
HTML:
dd if=**boot.img path** of=/sdcard/boot.img
Replace the **boot.img path** with whatever path you found your boot.img in when locating it
This should pull the boot.img to your /sdcard (storage) directory
To transfer to computer, just use your favorite file transfer method!
With TWRP installed
Install TWRP
Reboot to TWRP
Follow the steps listed in the without TWRP installed category
I would like to thank RootJunky for this method, it works flawlessly
There is a method to extract boot.img without TWRP? The tablet that I own doesn't have a any developed custom recovery, is an unsupported low-end device. Thank you for your help.
kingbri said:
If there is any trouble, leave it in the comments, i'll respond
I am not responsible if this crashes, bricks, causes nuclear warfare, or anything else that may happen, I'll try to fix it if you put your problem in the comments
Extract boot.img using a few simple adb commands
Hi XDA, I want to educate you on how to extract your boot.img using adb. Since systemless root and kernels all utilize the boot.img, undoing these changes consist of just flashing the boot.img in TWRP!
I pulled this from a RootJunky video and it worked on my pixel xl on any rom
Prerequisites:
You have to use TWRP (img or install, depending on the method)
Locating the boot.img
There are many tools used for this, I just like using the logs of an installer
Flash the TWRP installer and read the logs
It says "found boot image in *path*" (Usually /dev/block/sda19 or sda20)
If you want confirmation, flash magisk and it should say where your boot.img is
Extraction of the boot.img (2 ways)
Without TWRP installed
fastboot boot twrp.img
Open a terminal (on a computer) and type adb shell
your window should have only a ~#
Type this command in
HTML:
dd if=**boot.img path** of=/sdcard/boot.img
Replace the **boot.img path** with whatever path you found your boot.img in when locating it
This should pull the boot.img to your /sdcard (storage) directory
To transfer to computer, just use your favorite file transfer method!
With TWRP installed
Install TWRP
Reboot to TWRP
Follow the steps listed in the without TWRP installed category
I would like to thank RootJunky for this method, it works flawlessly
Click to expand...
Click to collapse
Very useful guide. No, it's absolutely useless and of no help. THERE IS ZERO NEED TO EXTRACT THE BOOT.IMG IF YOU HAVE ROOT. You NEED THE BOOT.IMG TO ROOT (VIA MAGISK).. If someone has TWRP, just fkn flash magisk right then and there. Rootjunky is useless.
JhinCuatro said:
Very useful guide. No, it's absolutely useless and of no help. THERE IS ZERO NEED TO EXTRACT THE BOOT.IMG IF YOU HAVE ROOT. You NEED THE BOOT.IMG TO ROOT (VIA MAGISK).. If someone has TWRP, just fkn flash magisk right then and there. Rootjunky is useless.
Click to expand...
Click to collapse
Agreed, this is useless. I need the boot.img so that I can patch it with Magisk and then flash onto device. If I have TWRP, I don't need the boot.img.
JhinCuatro said:
Very useful guide. No, it's absolutely useless and of no help. THERE IS ZERO NEED TO EXTRACT THE BOOT.IMG IF YOU HAVE ROOT. You NEED THE BOOT.IMG TO ROOT (VIA MAGISK).. If someone has TWRP, just fkn flash magisk right then and there. Rootjunky is useless.
Click to expand...
Click to collapse
i disagree, having the boot image is usefull if you want to modify it
Likewise, I have to agree...this primer IS useful as being able to extract a boot.img file from a stock rom is imperative for a lot of users with off-brand or rebranded MTK devices. For instance, I have a Blu G80 and there is virtually no dev support for this device and I would personally like to be able to root from the latest (or any) stock ROM or heck, repartition into the new A/B format to absolve myself of OTA updates forever.
Doogee N30: I do not have root, there is no recovery or rom for my phone, Can I extract the boot.img from my phone storage, to patch it with Magisk? Maybe with adb? Idk, please help me, I'm dying here....
This should also help:
Just boot into TWRP and run the following:
Code:
find /dev/block/platform -type d -name by-name
then use
Code:
ls -la /the/path/displayed/from/find
Then make note of your boot partition, so everything after the arrow ( -> ). If you are using a slotted device, it shouldn't matter which boot slot you pull, but it might help to pull the the boot slot you are actually using.
Then, as stated in the OP
Code:
dd if=/boot/img/path of=/sdcard/boot.img
Src:
adb find phone partitions
I need the command to find the partition of all Android devices For example, on some Samsung phones, you can use the following command to partition the device adb shell ls -al /dev/block/platform/
stackoverflow.com
I just installed Magisk on my OG Pixel. Using the method above, it took me a matter of minutes. I booted into TWRP to do this in adb with root.
EDIT:
I found a more workable solution, as long as you have the "find" command in TWRP or some other ADB session.
This definitely doesn't work if you don't have root in adb. TWRP or equivalent environment is required. If you don't have TWRP for you device, then at a minimum you need some way to root the device. Once you get root, then you can startup ADB, type "su" or other SuperUser command, and then run the "dd" command above (the 3rd code block). Without root, the "dd" command will fail - permission denied.
I've tried this on a Nexus 6P and an OG Pixel so far.
Hello everyone i need help somebody can't u helpme i can't find the bot.img in My device storage i have the SKY elitte p55 i try i'n the websites any guide but no found nothing thanks for helps
adb shell
cd /dev/block/bootdevice
ls
if u found your boot_a/boot_b , proceed reboot to twrp
pull those boot_a/boot_b file to your computer using command adb pull /dev/block/bootdevice/boot_a
push the into the phone , open magisk and patch the file boot_a/boot_b
after magisk done patching , reboot to bootloader
fastboot flash boot magisk-patched.img
now u have magisk on your phone
just sharing what is done on my phone . now pixel experience plus latest on my mojito/sunny device has root
I have Chinese Android TV Boxes like below links, please which TWRP image should I use?
The TWRP site seems to be all oriented about phone recovery images.
The TV boxes appear to be AMLogic ?CPU?
Is there a tutorial that shows ideally with a phone storage diagram the concept for flash vs. backup vs recovery?
Some say you can boot from an external recovery image with fastboot without writing it on the device?
(video is a bit old from 2015)
My current understanding is the "stock recovery partition" does not offer enough functionality to read/write the various partitions (boot,recovery,system,vendor,???) So is that what TWRP recovcery images provide? It does NOT appear they offer a "generic" recovery image.
If I manage to read these partitions can I edit their filesystem content on the PC? if so with which tool? are they standard .zip/rar/tar/iso files?
Currently I am running adb command over WiFi, these boxes come with 2 USB ports and sdcard slot. Can I use USB-A to USB-A cable to connect this boxes to PC, like the phone junkies do?
I don't have the equivalent of pressing volume/power buttons like on phones to boot into recovery or standard, what's the best way of doing that, fastboot/adb/an app on the tvbox?
These boxes already have su when I enter adb shell, su, whoami >displays> root, so that means they are unlocked.
I am bit lost in all of this, otherwise I won't be here. Thank you so much!!!
Amazon.com
Amazon.com
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I tried to follow the info and steps in a video by rootjunky and apply to a chinese tv box however I am not finding the boot/recovery/system/vendor partitions I ?think? I need to back up in order to flash onto another identical box (ie. replicate the various manual setups I did of app launcher, de-installed stock apps, my apk installs, etc...)
According to the below commands and output could you please let me know what pull commands I need to issue to copy the necessary sections onto my PC, thank you so much.
Here is my current wild guess to achieve my backup and replicate goals.
Here are the peek around commands and outputs...
adb -s 192.168.1.120:5555 shell "ls -R /dev/block/platform | grep by-name"
Some output is empty ??? in particular msm_partitions.txt ?
adb -s 192.168.1.120:5555 shell "ls -la /dev/block/platform/soc/fe08c000.mmc/by-name/"
if you need any particular output (eg. adb, or AIDA64, ...) just let me know and I will post.
Video reference...
false. any rom does not have twrp capabilities, like, for example the phone Alcatel 3 2019. You should change the post's title.
In those cases that no twrp is available it is impossible to extract the boot.img afaik.
I know I'm a little late to the party here, but maybe I can provide some insight into this. For starters, until you can mount /system rw properly, ADB just aint gonna work like you want. I have one of these 905w2 boxes (oppen x88plus..) and have been dealing with this for a minute now. If you at least have wireless adb access, you can:
A) get fastboot access
B) get adb sideload access from stock recovery
..and thats about it. You use the right hand USB port. Interestingly, my win11 chimes when I plug in my box when its booted normally, however nothing appears in device manager or usbdevview.
In closing, why dont you just DD the partitions to sd\usb storage? IE:
dd if=/dev/block/by-name/boot_a of=/sdcard/boot_a.img
Related
I've noticed with a lot of CM10-based ROM's (possibly even others), I am unable to get root ADB access.
On the ROM's that have it, I set the Root access to Apps and ADB
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I can reboot, fix permissions, clear caches, but no matter what, Android Commander is never able to get Root access
This isn't the case on some ROM's I've tried though. Android Commander is able to get Root access just fine without me needing to do anything.
To name some ROM's that I can't get Root access with:
CyanogenMod 10 Nightly (9/4)
AndroidME CM10 N7 1.0.0
As for what ROM's had working Root access, I can't exactly recall correctly :/ But I think these had it working:
Codename Android 3.4.1
Team EOS 3 *JELLYBEAN* Nightlies (confirmed working ADB root)
Is there something else I should possibly be doing to get Root access on CM10-based ROM's?
Boot a unsigned kernel then ./adb remount
PS: it is effective until you reboot
Sent from my Nexus 7 using Tapatalk 2
"The Root access : No" because you'r using the rom which have a "secured adb" (even when you'r rooted)
Download the "adbd insecure" in this thread and "Enable insecure adbd", you can get "Root access: OK" in any rom
http://forum.xda-developers.com/show....php?t=1687590
adb root
The real reason behind adb root or insecure adb is the adb daemon in the device running at root permissions. In pre-Android 4.1 versions, this is usually decided by some initialisation script(like init.rc) at boot time. The script checks for value in default.prop,local.propand other environment variables.
If it finds build.prop,default.prop or local.prop property file with ro.secure=0 adbd is allowed to run as root. You'll get adb root and hence will be able to do commands like adb remount,adb root and adb shell's prompt'll be # by default. The user may be displayed as [email protected] or [email protected] adb GUIs like Android Commander and QtADB will get to work in Root mode.
But,if it's ro.secure=1, adb daemon is made to work in secure mode, and adb won't change to root mode on issuing adb root command. However, if su binary is present in $PATH, u can still call su command from adb shell. But, it's not enough for Android Commander to get Root Access. It is possible to attain adb root through any one of the following methods:
1.For CyanoGenMod based ROMs there is an option in Settings->Developer Settings->Root access to control root access. Choose ADB only or Apps and ADB in options to get adb root.
2.Else use adbd Insecure app by chainfire if you have a rooted device. This is useful, especially for Android 4.1+ devices.
3.Or, you may manually edit default.prop to set it's value to 0, but original default.prop will be restored from boot partition everytime you reboot(this is the reason why adb Insecure cannot permanently do adb root, though there is an option to repeat the rooting procedure everytime the device boots). This method is called temporary adb root. On pre-Android 4.0 ROMs default.prop file was located in / directory. I read that from Android 4.x this file is in ramdisk and so more difficult to edit. But Android 4.0 has local.prop which is easier to modify than default.prop( See method 5)
4.For permanent adb root, you'll have to extract boot.img, change default.prop, repack and then flash it back to device.
5. In Android 4.0 there's local.prop file in /data partition. Setting ro.secure=0 in this file will do adb root permanently. Else you can set another property ro.kernel.qemu=1 in the same file. But, this value makes the system think that it is running in an android emulator. Many exploits and root methods set this property temporarily to gain root. But, it may cause side effects if used permanently. Setting ro.secure=0 is recommended. Do this command in terminal app or adb shell:
echo ro.secure=0 >/data/local.prop
or you can manually copy a local.prop file with ro.secure=0 as it's content to /data.
6.Note that method 3,4 and 5 won't work in Android 4.0 Jelly Bean onwards. According to Dan Rosenburg(drjbliss in XDA),the researcher who discovered adb root emulator exploit and many other exploits, Jelly Bean doesn't parse any property files to set the ownership of adb daemon. The stock adbd will have to be replaced with an insecure one to gain adb root. But still,as adbd is located in /sbin whose contents are reloaded everytime on reboot from boot.img, it won't be permanent.
7. For permanent adb root, you may flash an insecure boot.img(one that contains and insecure adbd)
8. If you're really desperate and can't get adb root to work with any of the above methods use an exploit. Most of the adb based rooting methods utilise some exploit to make the adb daemon run as root. By studying the exploit and implementing it you could gain adb root atleast temporarily.I'm not recommending this method but as a last resort you could try them.
Acknowledgements: Thanks to Dan Rosenberg for explaining the reasons behind adb root, especially the one in Jelly Bean.
get root access with root commander
Question to that fantastic answer above.http://forum.xda-developers.com/images/smilies/good.gif
How do I push back my modified build.prop?
I have HDC S3 Ex v2 hung in bootloop, after changing vm heapsize to 60 from 64.(Tried 128 but it didn´t stick, so tried this and it unfortunately worked)
I have managed to start in recovery mode even though it´s chinese there, don´t understand, I can communicate through Android commander to pull the files but cannot push them back due to no "root access".
I installed the "insecure ADB" via Commander but it does no good when I can´t load android.
I have no backup. It is rooted Android 4.1.2 by Fastcardtech. has busybox installed
Use su in adb shell
Use adb shell and elevate to root access by using su
Code:
su
.
Now, if you get # prompt instead of $ sign you have root on adb shell. But, still you don't have adb root. So, don't try to push the files or use Android Commander. Instead we use shell commands to do the same.
First Remount /system partition as writeable.
i.To do this first type
Code:
mount
and find out system's device name and file system from the list. In case of my device (and many Stock ICS devices) this device name would be /dev/block/mtdblock?. ? varies for each device. I had /system as mtdblock8 with ext3 file system.
ii. Now type the following command
Code:
mount -o remount,rw -t <filesys> /dev/block/mtdblock? /system
use the number you have for '?' and the filesystem for <filesys>.
Now Copy the modified file to some readable location on the device, say /sdcard or /data/local/tmp. Then copy the build.prop to /system using cat command
Code:
cat /sdcard/build.prop > /system/build.prop
Hope it works!
Closer...
HEXcube said:
Use adb shell and elevate to root access by using su
Code:
su
.
Now, if you get # prompt instead of $ sign you have root on adb shell. But, still you don't have adb root. So, don't try to push the files or use Android Commander.
Copy the modified file to some readable location on the device, say /sdcard or /data/local/tmp. Then copy the build.prop to /system using cat command
Code:
cat /sdcard/build.prop > /system/build.prop
Hope it works!
Click to expand...
Click to collapse
Thank you! But...
After more than one hour installing android-sdk, I got the # ( I thought the shell through android-commander was the same first)
but it says Read only file system
Another thread suggested "remount rw" before pushing but thats not something adb shell recognices "not found".
Am I only missing the adress of my device when trying remount?
Any suggestions?
Renount /system as rw
Oh, i forgot! You've to remount /system as Read Write. I've edited the above post to include that.
You need not have installed the whole Android SDK(unless you develop for Android). It's the same adb that Android Commander or QtADB uses. You can even use adb as a standalone tool along with the required libraries(dlls on windows). Now that you have installed the Android SDK, it doesn't matter.
Yes! Yes! Yes!
HEXcube said:
Oh, i forgot! You've to remount /system as Read Write. I've edited the above post to include that.
Click to expand...
Click to collapse
:good::good::good::victory::victory::victory:
It worked! Thank you so much! A new phone useless was really disappointing, but happy again
Set heap size back to 64. Maybe I´ll dare set it to 128 another day... The phone has horrible ram performance, hoping that would cure it.
Uninstallation of an app of 6-7 mb takes at least 45 sec. My old Blade with cyanogen does that in less than 10.
Hard part was understanding my system name /dev/block/mmcblk1p1 cause it wrote /storage/sdcard vfat after it.
I saw ext4 in other part and asssumed it was that system cause it had "ro" after it.
Thank you again. You now introduced me into some new territory. Not just flashing modded roms in recovery mode.
But I will search out one modded rom so I can overclock some.
A user of my rom had this 0 folder issue.
This issue was new to me so it took a couple hours to find a solution.
Didn't find any related "How To" guides here so i thought i would share it here.
The issue is that your pc file explorer for example (Win Explorer) only sees a 0 folder while still running the latest HTC USB drivers.
Well, there is a solution to recover from this.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
To recover from this you can try the following but you must be running the latest htc drivers.
Step 1
Connect your phone to your pc by USB (note: not usb3)
Backup all your sdcard content to your pc
Download this zip file and extract this to the root of your hardisk (adb.zip)
Step 2
Now open a command shell and go to your adb folder
You can open a shell by ticking "Windows start button" and type "cmd" in the search bar and hit enter.
then type the following commands in the just opened shell and hit enter after every command
cd..
cd..
cd adb
adb shell
You should now see something like "[email protected]/#"
Step 3
Now type the following commands one by one in this shell and after every command hit enter
adb shell
rm -r /data/media/0
busybox find /data/media -maxdepth 1 ! -path "/data/media" ! -path "/data/media/0" | while read filename; do mv "${filename}" /data/media/0/ ; done
Now reboot your device.
If all went fine then you just reset the 0 folder symlink and flashed a compatible recovery
If you now go to Windows Explorer then you should see your sdcard content
If the above how to didn't help the try the steps below:
Step 1
Connect your phone to your pc by USB (note: not usb3)
Backup all your sdcard content to your pc
Download this zip file and extract this to the root of your hardisk (adb.zip)
Download TWRP 2.5.0.0 recovery (recovery.img) (md5: C18DA6C73B2C7CCC9539E58C678C8DD6) and copy it to the adb folder in the root of your hardisk you just created
Step 2
Now open a command shell and go to your adb folder
You can open a shell by ticking "Windows start button" and type "cmd" in the search bar and hit enter.
then type the following commands in the just opened shell and hit enter after every command
cd..
cd..
cd adb
adb shell
You should now see something like "[email protected]/#"
Step 3
Now type the following commands one by one in this shell and after every command hit enter
adb shell
rm -r /data/media/0
busybox find /data/media -maxdepth 1 ! -path "/data/media" ! -path "/data/media/0" | while read filename; do mv "${filename}" /data/media/0/ ; done
Step 4
Now reboot into your bootloader while your phone still connected to usb.
When your bootloader recognizes your phone you should see in red "Fastboot USB"
If not then your USB drivers aren't up to date or your using USB 3
If so then type the following commands and after every command you must hit ENTER
fastboot flash recovery recovery.img
fastboot erase cache
fastboot reboot
Goodluck :fingers-crossed:
V6-Maniac said:
A user of my rom had this 0 folder issue.
This issue was new to me so it took a couple hours to find a solution.
Didn't find any related "How To" guides here so i thought i would share it here.
The issue is that your pc file explorer for example (Win Explorer) only sees a 0 folder while still running the latest HTC USB drivers.
Well, there is a solution to recover from this.
Most likely your on Clockwork Mod Recovery when this is happening.
Not gonna tell ya the whole story but there is a issue with CWM and 0 folders.
To recover from this you can try the following but you must be running the latest htc drivers.
Step 1
Connect your phone to your pc by USB (note: not usb3)
Backup all your sdcard content to your pc
Download this zip file and extract this to the root of your hardisk (adb.zip)
Download TWRP 2.5.0.0 recovery (recovery.img) (md5: C18DA6C73B2C7CCC9539E58C678C8DD6) and copy it to the adb folder in the root of your hardisk you just created
Step 2
Now open a command shell and go to your adb folder
You can open a shell by ticking "Windows start button" and type "cmd" in the search bar and hit enter.
then type the following commands in the just opened shell and hit enter after every command
cd..
cd..
cd adb
adb shell
You should now see something like "[email protected]/#"
Step 3
Now type the following commands one by one in this shell and after every command hit enter
adb shell
rm -r /data/media/0
busybox find /data/media -maxdepth 1 ! -path "/data/media" ! -path "/data/media/0" | while read filename; do mv "${filename}" /data/media/0/ ; done
Step 4
Now reboot into your bootloader while your phone still connected to usb.
When your bootloader recognizes your phone you should see in red "Fastboot USB"
If not then your USB drivers aren't up to date or your using USB 3
If so then type the following commands and after every command you must hit ENTER
fastboot flash recovery recovery.img
fastboot erase cache
fastboot reboot
If all went fine then you just reset the 0 folder symlink and flashed a compatible recovery
If you now go to Windows Explorer then you should see your sdcard content
Goodluck :fingers-crossed:
Click to expand...
Click to collapse
It's an issue when upgrading from 4.1.2 to 4.2.2.
User can copy files to pc prior to upgrading, then copy back after and the files can be copied to the folder visible to Windows.
Also, creating a symlink to /data/media/clockworkmod in /data/media/0/ will allow a user to get CWM to see backups and allow the user to have access to it in the folder visible to Windows.
Your solution ignores the fact the someone might prefer CWM over TWRP.
Sent from my HTC One using xda app-developers app
ilal2ielli said:
It's an issue when upgrading from 4.1.2 to 4.2.2.
User can copy files to pc prior to upgrading, then copy back after and the files can be copied to the folder visible to Windows.
Also, creating a symlink to /data/media/clockworkmod in /data/media/0/ will allow a user to get CWM to see backups and allow the user to have access to it in the folder visible to Windows.
Your solution ignores the fact the someone might prefer CWM over TWRP.
Sent from my HTC One using xda app-developers app
Click to expand...
Click to collapse
Thx for the info, didn't know that.
Strange thing is that the guy i help out didn't went from 4.1.2 to 4.2.2
He went straight from 4.2.2 custom rom to 4.2.2 custom rom.
Also i don't ignore a possible desired user recovery choice.
Issue with the 0 folder came when cwm was flashed.
Butt will amend the line .
More info is also welcome...
V6-Maniac said:
Thx for the info, didn't know that.
Strange thing is that the guy i help out didn't went from 4.1.2 to 4.2.2
He went straight from 4.2.2 custom rom to 4.2.2 custom rom.
Also i don't ignore a possible desired user recovery choice.
Issue with the 0 folder came when cwm was flashed.
Butt will amend the line .
More info is also welcome...
Click to expand...
Click to collapse
Possible that he didn't format SD card prior to flashing the first 4.2.2 ROM and didn't notice the problem until he got to yours?
Sent from my HTC One using xda app-developers app
ilal2ielli said:
Possible that he didn't format SD card prior to flashing the first 4.2.2 ROM and didn't notice the problem until he got to yours?
Sent from my HTC One using xda app-developers app
Click to expand...
Click to collapse
If you have formated your SD card (firmware update that took care of that for you) DO NOT DO THIS. apon reboot your system is no longer fucntioning and if oyu boot into recovery it does not see your SD card anymore. I had to adb sideload to get a rom back ot the phone. Not the OP fault but mine. Luckly i know how to recover just wanted to give warning to others
Bump!! I think this thread should be in the stickies @Red5 what do you think?
Sent from my HTC One using xda premium
This has only became evident to me today.
I was on stock 4.1.2 and flashed Viper Rom 4.2.2 and noticed I was missing 16GB storage.
In the thread I was told to look in data/media and all my files which I saved on SD Card from 4.1.2 were there. Also this 0 folder which had pretty much the same folders but with no user files
I was told to delete duplicate files/folders in the modia (not 0) folder but I dont know if i should just leave empty folders in Media with everything in 0, or delete all folders in Media and leaving only the 0 folder there with everything inside that intact.. If that makes sense..
I am unsure what will happen to CWM if I delete that from the Data/media folder
Cheers
twerg said:
This has only became evident to me today.
I was on stock 4.1.2 and flashed Viper Rom 4.2.2 and noticed I was missing 16GB storage.
In the thread I was told to look in data/media and all my files which I saved on SD Card from 4.1.2 were there. Also this 0 folder which had pretty much the same folders but with no user files
I was told to delete duplicate files/folders in the modia (not 0) folder but I dont know if i should just leave empty folders in Media with everything in 0, or delete all folders in Media and leaving only the 0 folder there with everything inside that intact.. If that makes sense..
I am unsure what will happen to CWM if I delete that from the Data/media folder
Cheers
Click to expand...
Click to collapse
Anything that's already in /data/media/0 can be deleted from /data/media
/data/media/legacy/, /data/media/obb/, and /data/media/clockworkmod can be left alone.
If you want to be able to see your clockworkmod folder and backups when connected to a PC/MAC you'll need to create a symlink in /data/media/0 pointing to the data/media/clockworkmod folder.
Sent from my HTC One using xda app-developers app
Super frustrating problem. I had this happen a couple weeks ago and it pissed me off. Wound up just formatting and it fixed it never to return
Sent from my HTC One using Tapatalk 2
InflatedTitan said:
Super frustrating problem. I had this happen a couple weeks ago and it pissed me off. Wound up just formatting and it fixed it never to return
Sent from my HTC One using Tapatalk 2
Click to expand...
Click to collapse
Yes very annoying.
Well i formatted and reset rom and now have no SD Card, directory or files om the phone.
A guy here on xda tried for almost 2 hours last night to fix it, can sideload a rom bit still no SD and rom will not boot.
Should never have rooted this phone, i was npt going to but of course i did amyway.
Tried this method on my nexus 10 (with the proper recovery but didn't work) sucks because i don't have links to my sd card and cant download anything as a result. flashing the google stock image didnt help either wondering if there was anything else i can do?
Temp CWM-recovery
1. Download and put the UPDATE-SuperSU-vX.Xx.zip on internal/external SdCard
2. Download, extract the folder IntelAndroid-FBRL and put on the C drive
3. Follow this guide (Use the option T3)
This is new version fixed by social-design-concepts (Please support its work with donations)
Now backup kernel with recovery too:
View attachment IntelAndroid-FBRL-01-17-2015.7z
Root, backup & restore on the external card works well:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
bodivas said:
Temp CWM-recovery
1. Download and put the UPDATE-SuperSU-vX.Xx.zip on internal/external SdCard
2. Download, extract the folder IntelAndroid-FBRL and put on the C drive (do not use other versions)
3. Follow this guide (Use the option T3)
View attachment 3107550
Backup & restore on the external card works well
Click to expand...
Click to collapse
Maybe I could get you to send dumps of this device it be nice to get to the bottom of why the the updated version doesn't work on this device.
Sent from my XT907 using XDA Free mobile app
social-design-concepts said:
why the the updated version doesn't work on this device.
Click to expand...
Click to collapse
Perhaps because the new version lacks the table mount points in recovery.zip/etc:
View attachment fstab.rar
Thanks for the great work!! 2P810+++++79361W
bodivas said:
Perhaps because the new version lacks the table mount points in recovery.zip/etc:
View attachment 3107582
Thanks for the great work!!
Click to expand...
Click to collapse
Give me moment I like to get the dump of fastboot.img recovery.fstab should be generated from the fstab droidboot / fastboot uses to handle partitions I'm making changes to the recovery.fstab generation so like to include fixes for this if their using other name or something.
If you could this should dump boot recovery fastboot and system
https://www.androidfilehost.com/?fid=95887005526788692
Sent from my XT907 using XDA Free mobile app
social-design-concepts said:
If you could this should dump boot recovery fastboot and system
https://www.androidfilehost.com/?fid=95887005526788692
Click to expand...
Click to collapse
I saw that when starting new version generates mount point right (mmcblk1p1) but fails to mount internal sd card the same. I added recovery.fstab in recovery.zip/etc and your new version 12-29-2014 works without problems!
All versions of yoga 2 (8,10,13) there year numbers and partitions sizes equal ..
For the kernel, recovery and fastboot, I had to use:
Code:
dd if=/dev/block/mmcblk0p3 of=/sdcard/boot.img
dd if=/dev/block/mmcblk0p4 of=/sdcard/recovery.img
dd if=/dev/block/mmcblk0p5 of=/sdcard/droidboot.img
Download dump_yoga2_830L
This is full stock firmware
Can we use this to dual boot with Yoga 2 tablet with Windows?
bodivas said:
I saw that when starting new version generates mount point right (mmcblk1p1) but fails to mount internal sd card the same. I added recovery.fstab in recovery.zip/etc and your new version 12-29-2014 works without problems!
All versions of yoga 2 (8,10,13) there year numbers and partitions sizes equal ..
For the kernel, recovery and fastboot, I had to use:
Code:
dd if=/dev/block/mmcblk0p3 of=/sdcard/boot.img
dd if=/dev/block/mmcblk0p4 of=/sdcard/recovery.img
dd if=/dev/block/mmcblk0p5 of=/sdcard/droidboot.img
View attachment 3107675
Download dump_yoga2_830L
This is full stock firmware
Click to expand...
Click to collapse
Thanks I'll download and see if i can resolve the issue
Sent from my XT907 using XDA Free mobile app
redhern said:
Can we use this to dual boot with Yoga 2 tablet with Windows?
Click to expand...
Click to collapse
First you have to have the dump of bios..
Is the bios available? I havent seen it mentioned in any of the posts.
redhern said:
Is the bios available? I havent seen it mentioned in any of the posts.
Click to expand...
Click to collapse
BIOS is present here but you have to know where to put. And then the windows do not care so much - I want CMmod
Here the guide for ONDA V975i
I do not want to risk (I've already lost imei on my 830L) with these experiments
successfully rooted but... no adb root nor adb remount
Hello,
I successfully rooted my 1050F device following this guide
Now I'd like to run adb as root and to be able to remount rw /system to put and remove staff there but the usual method don't work.
I tried adb root and adb remount but lenovo adb cannot run as root in production build.
I tried installing adb-insecure 2.0 which usually do the trick but when I patch the kernel from the app and use adb insecure demon the device is not seen by the PC with adb .
I also tried to remount with "sudo mount -o remount rw /system" but I cannot write in the /system partition
any suggestion?
thanks,
Dario
blackdir said:
Hello,
I successfully rooted my 1050F device following this guide
Now I'd like to run adb as root and to be able to remount rw /system to put and remove staff there but the usual method don't work.
I tried adb root and adb remount but lenovo adb cannot run as root in production build.
I tried installing adb-insecure 2.0 which usually do the trick but when I patch the kernel from the app and use adb insecure demon the device is not seen by the PC with adb .
I also tried to remount with "sudo mount -o remount rw /system" but I cannot write in the /system partition
any suggestion?
thanks,
Dario
Click to expand...
Click to collapse
adb shell
su
mount -o rw,remount /system
vampirefo said:
adb shell
su
mount -o rw,remount /system
Click to expand...
Click to collapse
sure, that will work, but if you need to push several files it is very tim consuming as you need to copy to a temporary location on the device and then move them to /system
if you are able to get adb insecure you can create a batch file that you can run from the PC
Any idea about the reason why dab insecure is not working on this device?
Is it because the device is intel based and not Arm?
(if this is a stupid question, please forgive me as it is my first experience on Android Intel development)
blackdir said:
sure, that will work, but if you need to push several files it is very tim consuming as you need to copy to a temporary location on the device and then move them to /system
if you are able to get adb insecure you can create a batch file that you can run from the PC
Any idea about the reason why dab insecure is not working on this device?
Is it because the device is intel based and not Arm?
(if this is a stupid question, please forgive me as it is my first experience on Android Intel development)
Click to expand...
Click to collapse
Correct you need a adbd binary for intel fully rooted meaning its always root, or you need to have an unlocked bootloader, that allows flashing of modified boot.img.
I updated the system via OTA and root again but it said Failed: too many links or something like that but it continued and cwm is installed. Is this ok?
redhern said:
Is the bios available? I havent seen it mentioned in any of the posts.
Click to expand...
Click to collapse
Have you tried flashing the bios yet or did you find any other ways to run windows on this tablet?
bodivas said:
BIOS is present here but you have to know where to put. And then the windows do not care so much - I want CMmod
Here the guide for ONDA V975i
I do not want to risk (I've already lost imei on my 830L) with these experiments
Click to expand...
Click to collapse
bodivas, could you post a guide on how to install windows on external sd card? The guide you posted when translated to english it is very hard to understand, and the onda is built on a different chipset, slower ones, so we would need to find intel baytrail drivers for it to work right. Also would the bios for the 1050 work on the 1350?
Rooted my Yoga 2 10" with the Jan. 10 OTA update installed, worked like a charm and the next best thing to a one-click root for noobs like me!
Thanks!
Here the same. 1380F with last OTA and root is rock solid [emoji106]
I have a problem
After I root my YT2-1050f, I can't enter recovery mode.
Please note, I can only speak with any degree of certainty about devices bought from Play / Moto. I cannot attest to the accuracy of this information for US carrier versions etc. Anything you do is at your own risk
Contents / Thread overview
Introduction
What is Fastboot?
What is adb?
How to install adb and fastboot
How to test adb and fastboot work
OK Gimme some useful fastboot commands please!
OK Gimme some useful adb commands please!
A little more about using Windows command prompt
Myth Busters
Introduction
adb and fastboot are very useful command line tools. They can be used from Windows, Linux or Mac to carry out tasks on your android device, such as moving and backing up files, rooting and restoring your phone to it's factory state. Understanding how to use these tools could save your phone when you get yourself in trouble. This is especially true of rooted users. Particularly those of you who are "new to the scene". You definitely should read and understand this thread before you do ANYTHING root related.
This thread is not intended to be a non-exhausted reference. It is merely here to give an overview of the most basic of basics
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
What is fastboot?
Fastboot comprises of 2 components.
1) Fastboot mode on the phone (The Bootloader)
2) Fastboot tool on your computer
Fastboot is a small command line tool that you can use from your computer whilst the phone is connected via USB and you are booted into the bootloader. The most common uses for fastboot are:
Unlocking the bootloader - needed as part of the rooting process
Flashing a custom recovery to the device - needed as part of the rooting process
Flashing factory images - used for saving / trestoring your device back to stock
Being able to do these 3 things are essential before rooting. Many new users skip learning these and use a toolkit to root. As a result, when they mess up and we try to explain what they need to do to fix their issues, it becomes very difficult for us to help as fastboot is not understood. It is YOUR responsibility to understand these things BEFORE you mess up.
What is adb?
adb is another small command line tool that stands for "Android Debugging Bridge". Again, it can be used from a computer connected via USB to your android device. It can be used whilst the device is booted into Android or (if you have a custom recovery), it can be used in recovery too, unlike fastboot (yes, adb and fastboot are NOT the same thing) which can only be used in the bootloader.
adb can be used to push files to (or pull files from) your phone. It can also be used to execute many of the commands available in Linux terminals (Or Android terminal emulators) on the device itself. We're not here to cover all these commands however. We just want to cover the basics.
How to install adb and fastboot
adb and fastboot are very easy to install and can be installed on Windows, Linux and MAC computers. The Windows install can be a little bit more complicated than the other 2 and may need additional drivers installing too.
Windows.
There is a very handy tool that can install adb and fastboot in 15 seconds. It is recommended that you use this to install adb and fastboot. Please see the link immediately below for that tool:
ADB, Fastboot and Drivers - 15 seconds ADB Installer - Really quick and easy way to install adb and fastboot (by @Snoop05). Download links are at the bottom of post 1.
This tool asks if you want to install adb and fastboot (to which you should answer Y) and then creates c:\adb\adb.exe and c:\adb\fastboot.exe
It then asks if you want to install it system wide .. This is asking to install for all windows users. < 15 second installer needs updating to SDK 23, which is required for latest Android versions.
Download the latest SDK (adb and fastboot) versions here: https://developer.android.com/sdk/index.html (Scroll down to SDK tools only) then download the Windows *Installer*.
Open the installer and select "Platform-tools" and install the packages. This should create "C:\Program Files (x86)\Android\android-sdk\platform-tools"
Now we want to set this path as a Windows Environment variable PATH to make the executables work system wide:
right-click computer > properties > advanced > environment variables.
under system variables click "path" and click "edit"
at the end of the line, add the below:
Code:
;C:\Program Files (x86)\Android\android-sdk\platform-tools
Please note, the semi-colon ; is VERY important.
You may also need to install drivers.
Here is a link to the Google USB Driver: DOWNLOAD THIS
Code:
To install on Windows 7:
- Ensure existing drivers are uninstalled first*
- Extract the zip to c:\adb (created earlier by the installer)
- Right-click "Computer" > Manage in windows and choose "Device Manager"
- Boot the Nexus 6 to the bootloader (Volume down + Power) and connect the USB Cable
- Watch for any new devices with exclamation marks appearing
- Right-Click the new device > Update driver software
- Choose the "browse" method and browse to c:\adb, find teh folder you extracted then follow the wizard to the end - using amd6 64 if you're on a 64 bit system and i386 if you're on a 32 bit system.
*To uninstall existing drivers, boot into Android and connect the USB cable. Monitor device manager for the device showing up. To uninstall the device, right-click it to uninstall it. At the prompt, ensure you also choose to delete the driver. Repeat this for bootloader and recovery.
Code:
To Install on Windows 8, you may need to additionally disable driver enforcement
- From the Metro Start Screen, open Settings (move your mouse to the bottom-right-corner of the screen and wait for the - -- pop-out bar to appear, then click the Gear icon).
- Click ‘More PC Settings’.
- Click ‘General’.
- Scroll down, and click ‘Restart now’ under ‘Advanced startup’.
- Wait a bit.
- Click ‘Troubleshoot’.
- Click ‘Advanced Options’
- Click ‘Windows Startup Settings’
- Click Restart.
Once that is done, your Windows computer is configured for adb and fastboot.
In device manager, the device should show up as below, depending whether you are booted into recovery or bootloader...
Recovery - Android Device > Google Nexus 4 ADB Interface
Bootloader - Android Device > Google Nexus 4 Bootloader Interface
If it shows as something different, either you have existing drivers in the way or something went wrong.
Linux and Mac
Here is a really simple tool to install adb and fastboot on the above OS. The only expectation is you know how to open and run a terminal command. Please see the link immediately below:
Nexus Tools 2.2 (Featured by XDA) - adb and fastboot installer for Linux and Mac (by @corbin052198)
Once you have installed adb and fastboot from the above link, you're ready to go.
How to test adb and fastboot work
As previously mentioned, adb and fastboot are both command line tools. That means you must run these tools from command prompt (cmd in Windows) or Terminal (Linux and Mac).
Remember earlier, I mentioned that fastboot can only be used in bootloader? and adb can only be used in Android (or custom recovery - lets cover that later)? We can use the command "fastboot devices" and "adb devices to see if we have adb and fastboot working correctly.
Lets try it.
Boot your phone into android
Connect it to your computer via USB
Open cmd (start > type "cmd" on Windows) or Terminal (Mac/ Linux
Type in the windows "adb devices" and press enter
Here is what we don't want to see:
Notice how there is nothing underneath where it says "List of attached devices" That means it cannot see any device
Here is what we DO want to see:
We can see that there is now a device listed.
OK lets test fastboot. Unplug the USB and turn off the phone. When it is off, hold down Volume down + power until you feel the vibrate. You will now be in the bootloader. Reconnect the USB cable.
In the same window (cmd or terminal) we're going to now type "fastboot devices".
Again, here is an example of what we don't and do want to see:
If in both modes, you can see your devices "Serial Number", then you know they are both working.
Please note that if you cannot get adb and fastboot to work "system wide", you can open the command prompt to the location of the adb and fastboot executables exist and try from there.
OK Gimme some useful fastboot commands please!
Here are some of the most useful fastboot commands you will come across. Fastboot is used mostly for flashing images to the devices partitions on the internal memory.
Code:
fastboot oem unlock
This unlocks your bootloader and allows you to flash a recovery to root. WARNING, this will wipe your device. Rooting the N6 is essentially unlocking the bootloader, flashing a recovery and then putting the SuperSU zip on your sdcard and flashing it via the recovery. This thread covers rooting: [HOW-TO] The Nexus 6 All-In-One Beginner's Guide by @xBeerdroiDx
Code:
fastboot flash recovery recovery.img
This will flash a recovery.img to the recovery partition. The command is broken down into "fastboot flash" (what to do) "recovery" (where to flash to) "recovery.img" what to flash there. In the terminal or command prompt, you cannot just type "recovery.img" though. It has to be the path to where the recovery image is. For example, if my recovery image is on my desktop, I would have to type:
Code:
fastboot flash recovery c:\users\rootsu\desktop\recovery.img
It is worth noting, that it IS case sensitive, meaning if your file is called Recovery.img, you must type the capital R...
Other things you would flash:
Code:
fastboot flash system system.img
fastboot flash boot boot.img
These will flash the system image (ROM) and boot image (kernel) as you would if you were returning to stock.
A full guide to returning to stock can be found here: [TUTORIAL][GUIDE][HOW TO] Flash Factory Images || Unroot || Relock bootloader by @Mr hOaX
You can also boot into a recovery.img without flashing it...
Code:
fastboot boot c:\users\rootsu\desktop\recovery.img
which is "fastboot boot" (what to do) "c:\users\rootsu\desktop\recovery.img" what to do it with. As you may have noticed, we did not define the recovery partition in this command, that's because we're not flashing it....
OK Gimme some useful adb commands please!
At the moment, we are going to assume you have a custom recovery and you have booted into recovery. The reason for this is using adb in recovery can be much simpler.
Here are some useful scenarios for using adb.
Backup your sdcard to your PC
Code:
adb shell
mount data
exit
adb pull data/media/0 c:\MyBackup
**Please note, some recoveries may "mount data" automatically on boot, so don't be disheartened if you get an error stating device or resource busy. This probably just means you can't mount what is already mounted**
/data/media/0 is the real location of /sdcard for your information. Also referred to as "The mount point". What we have done here is "adb pull" (what to do) "data/media/0" (what to move) "c:\MyBackup" (where to move it to)
Push a zip file from your PC to your sdcard (useful if you wiped your sdcard and rom)
Code:
adb shell
mount data
exit
adb push c:\rom.zip data/media/0
What we have done here is "adb push" (what to do) "c:\rom.zip" (what to move) "data/media/0" (where to move it to)
You can of course also use adb to push and pull files to and from /system too. You just need to:
Code:
adb shell
mount system
exit
I mentioned earlier that using custom recovery is much easier for adb than whilst booted into Android. You need to ensure you have a kernel that allows insecure adb before you do anything with system and data partitions. You also need to ensure that USB debugging has been enabled in developer options.
For example, to mount system to pull files whilst android is running you have to:
Code:
adb root
adb shell
mount -o rw,remount /dev/block/platform/msm_sdcc.1/by-name/system /system
...which is clearly a little bit more involved, so I recommend you use recovery for adb push and pull. You can find more detailed information on adb here: http://developer.android.com/tools/help/adb.html
A little more about using Windows command prompt
One thing to understand is that like Windows, command prompt (cmd.exe) works with directories (or folders if you like). The Linux and Mac terminals are the same, but most linux users, we expect you would already know this.
Here you will see I have downloaded a recovery image that I want to flash using fastboot.
As you can see, the recovery.img is located in C:\users\rootSU\Desktop
Usually when you open the command prompt from the start menu, or run command, the command prompt will default to your user location as seen below:
So lets try and fastboot flash recovery recovery.img...
It fails with a not-too-accurate error message. It has failed because you have not told it where the recovery image is. It assumes it is in the directory as listed in the prompt
So, how do we deal with this? Well, there are 3 ways.
1) We tell the command prompt where the recovery.img actully is in the command itself
Success! As you can see, we have told the command that the location for the file is Desktop\recovery.img
2) We can change the directory in command prompt to the directory where the file is. In this example, we change directory to "Desktop". The change directory command is "cd " or in this case "cd Desktop"
3) ...and possibly the simplest method. We hold shift whilst we right-click on the folder we want to change directory to, and directly open a command prompt there:
Another point to make with command prompt or terminals, is if you do a particular command, it is "pre-programmed" to "expect" a particular format of that command.
For example, we know that adb push as a command expects after it . This means the command is actually
Code:
adb push
BUT if you put something AFTER , for example -
Code:
adb push somethingelse
, it will assume that the "somethingelse" is a bad parameter, and the command will fail. It will probably display (or "print" which is the technical term in a terminal) a helpful guide of how the command should be used instead of trying to run the command which it does not understand.
You're probably wondering why I am telling you this. Well quite simply, it is a warning about folder names. Imagine you have c:\users\rootSU\My Documents as a folder. You assume the command is then
Code:
adb pull /data/media/0 c:\users\rootSU\My Documents
but it is not... There is a space in between My and Documents. What you have actually done is
Code:
adb pull Documents
because it uses a space to signify the end of a command or parameter. It is best to avoid using folders with spaces in them. Avoid as much as you can. In the event it is unavoidable (Although when is it ever>) then please surround the path with quotation marks,
Code:
adb pull /data/media/0 "c:\users\rootSU\My Documents"
so that way, it sees everything between the " " as a single parameter.
Myth Busters
Myth 1: You need USB debugging on to use adb and fastboot
If you cannot boot into Android, it doesn't matter. You DO NOT need USB Debugging turned on to use adb outside of android. USB Debugging is an Android ONLY setting. Fastboot obviously also does not need debugging either as this too is outside of Android
Myth 2: to adb push or fastboot flash files, they must be in the same folder as adb or fastboot executables. Sorry but this is rubbish. You can pass the full path of the image you're flashing or file you're pushing in the command and fastboot / adb can be called system wide if you've set them as an environment variable or used the 15 second installer
thanks(im out of thanks). but ill be back to leave one here!!!!!
simms22 said:
thanks(im out of thanks). but ill be back to leave one here!!!!!
Click to expand...
Click to collapse
No worries. Just putting it here for info. It's not a new work, just a slightly amended version of my N5 thread. No need for thanks
rootSU said:
No worries. Just putting it here for info. It's not a new work, just a slightly amended version of my N5 thread. No need for thanks
Click to expand...
Click to collapse
it was up in the n5 threads before, and was needed here. but its here now as well, so thank you
Good guide. Needs to be a sticky. In fact, I think every device general forum should have a sticky like this. Would have saved me a lot of grief back when....
Excellent update.
Very good to see. I'm sure lots of people will be sending noobs here for the basics.
Up to your usual helpful, good work I see.
rootSU said:
This tool asks if you want to install adb and fastboot (to which you should answer Y) and then creates c:\adb\adb.exe and c:\adb\fastboot.exe
It then asks if you want to install it system wide (to which again, you should answer Y)... This then allows you to type adb commands in the command prompt without having to open a particular directory first. You may or may not understand what I mean when I say that, but take it from me, its much more convenient and easier to use this way.
Click to expand...
Click to collapse
Y option = System-wide = install to "C:\adb" and add path for system variable - This mean you can use it by any account on your pc.
N option = Current user only = install to "C:\Users\[YOUR USERNAME]\adb" and add path for user only - Only user account used for installation can actually use it.
So if you say Y or N you will be still able to use it from any directory with cmd.
rootSU said:
It will also ask if you want to install device drivers. Actually, say N to this as we're going to cover that next, using the google USB drivers
Here is a link to the Google USB Driver: DOWNLOAD THIS
Click to expand...
Click to collapse
Drivers in my installer are the one from the link you posted here. I'm not using any modified drivers, just the one that come with SDK. And they are also digitally signed.
I hope you will fix these But still nice work, beginners should understand it :good:
Snoop05 said:
Y option = System-wide = install to "C:\adb" and add path for system variable - This mean you can use it by any account on your pc.
N option = Current user only = install to "C:\Users\[YOUR USERNAME]\adb" and add path for user only - Only user account used for installation can actually use it.
So if you say Y or N you will be still able to use it from any directory with cmd.
Drivers in my installer are the one from the link you posted here. I'm not using any modified drivers, just the one that come with SDK. And they are also digitally signed.
I hope you will fix these But still nice work, beginners should understand it :good:
Click to expand...
Click to collapse
Thanks for the info. I thought system wide meant it was putting it as a path environment variable. Reason I didmt use the drivers from your tool originally is (well I wrote this thread for N5 originally) they didnt work so had to install the universal naked driver. But if yours are the same as the ones linked, I can update that.
rootSU said:
Thanks for the info. I thought system wide meant it was putting it as a path environment variable. Reason I didmt use the drivers from your tool originally is (well I wrote this thread for N5 originally) they didnt work so had to install the universal naked driver. But if yours are the same as the ones linked, I can update that.
Click to expand...
Click to collapse
Path is added in both cases.
Sooo I need a little help here. I followed the directions to unlock the bootloader and everything went good. I did the CF auto-root, and the phone booted back up as normal. Now, I was trying to flash the M preview, and all of a suddon now my phone isn't recognized in adb. You posted a pic of what we don't want to see when testing for adb, but you don't say how to fix it if we run into the problem. Any way to get it to recognize my phone again so I can get this build on?
papeshfoo said:
Sooo I need a little help here. I followed the directions to unlock the bootloader and everything went good. I did the CF auto-root, and the phone booted back up as normal. Now, I was trying to flash the M preview, and all of a suddon now my phone isn't recognized in adb. You posted a pic of what we don't want to see when testing for adb, but you don't say how to fix it if we run into the problem. Any way to get it to recognize my phone again so I can get this build on?
Click to expand...
Click to collapse
Can you be very specific with your issue please?
papeshfoo said:
Sooo I need a little help here. I followed the directions to unlock the bootloader and everything went good. I did the CF auto-root, and the phone booted back up as normal. Now, I was trying to flash the M preview, and all of a suddon now my phone isn't recognized in adb. You posted a pic of what we don't want to see when testing for adb, but you don't say how to fix it if we run into the problem. Any way to get it to recognize my phone again so I can get this build on?
Click to expand...
Click to collapse
Android M no like root, you'll either have to live with stock or wait for chainfire to do his thing.
This all worked well until I had to find my device in the cmd prompt. It listed no devices when I typed in "ADB Devices". The issue I found was with the ADB Interface Driver. I uninstalled it and reinstalled it thinking it might've been a driver issue, but it still wouldn't work. I tried the "Uninstall driver" then "scan for hardware changes" but that didn't work. Finally I found the universal ADB driver and tried using that. STILL nothing. I figured that, because I don't have my device's driver installed, it might've been that, so I tried to DL it and yet again, nothing. I have a Kyocera Hydro Life, if that helps. Also, I tried looking through the "update driver manually" in order to update the driver software by looking through the different ADB interfaces that it had but my Kyocera driver wasn't there. Is it supposed to be there or do I just use one of the ones provided?
I checked my programs and apps and it says that the Kyocera usb driver was installed. Did I do something wrong?
ScottyChaos said:
This all worked well until I had to find my device in the cmd prompt. It listed no devices when I typed in "ADB Devices". The issue I found was with the ADB Interface Driver. I uninstalled it and reinstalled it thinking it might've been a driver issue, but it still wouldn't work. I tried the "Uninstall driver" then "scan for hardware changes" but that didn't work. Finally I found the universal ADB driver and tried using that. STILL nothing. I figured that, because I don't have my device's driver installed, it might've been that, so I tried to DL it and yet again, nothing. I have a Kyocera Hydro Life, if that helps. Also, I tried looking through the "update driver manually" in order to update the driver software by looking through the different ADB interfaces that it had but my Kyocera driver wasn't there. Is it supposed to be there or do I just use one of the ones provided?
I checked my programs and apps and it says that the Kyocera usb driver was installed. Did I do something wrong?
Click to expand...
Click to collapse
Try a different USB port. If that doesn't work try a different USB cable. If that also doesn't work, you could try disabling driver signature checking for Windows.
If those don't work, try this thread > http://forum.xda-developers.com/showthread.php?t=1583801
cam30era said:
Try a different USB port. If that doesn't work try a different USB cable. If that also doesn't work, you could try disabling driver signature checking for Windows.
If those don't work, try this thread > http://forum.xda-developers.com/showthread.php?t=1583801
Click to expand...
Click to collapse
EDIT: I also forgot to mention that the error code that came up while I was in the dev manager was compatibility error code (28) when I clicked on "Device ADB interface".
ScottyChaos said:
EDIT: I also forgot to mention that the error code that came up while I was in the dev manager was compatibility error code (28) when I clicked on "Device ADB interface".
Click to expand...
Click to collapse
Error 28 means drivers not installed. Try the driver help thread that I linked above.
---------- Post added at 12:33 PM ---------- Previous post was at 12:04 PM ----------
cam30era said:
Error 28 means drivers not installed. Try the driver help thread that I linked above.
Click to expand...
Click to collapse
@ScottyChaos,
Just a fundamental question: I assume you have enabled "Developer Options" in Settings, and then checked "enable USB debugging"?
---------- Post added at 12:39 PM ---------- Previous post was at 12:33 PM ----------
[/COLOR @ScottyChaos,
Here is a thread that you might find interesting > http://forum.xda-developers.com/android/help/metro-pcs-kyocera-hydro-life-rooted-t2870678
Windows 10 device driver management is even more locked down then windows 8. I got two of the three drivers loaded but when going into adb mode on the phone through recovery it just disappeared out of the device manager. I had to unplug and plug in while in that mode to trigger a unloaded driver in the device manager. Once there I had to force the adb driver manually with the nasty windows driver warning and all. Once I did that I could see the device in adb mode and sideload my marshmallow OTA. woot!
I decided to drop a thanks bomb...
ADB is good.
But that fastboot.
Seriously, its ONE command. OK, a few different arguments to use.... But it is so easy, and so powerful. People are afraid to mess up on command line, but its actually way harder to type the wrong thing out then to click the wrong thing.
LEARN IT. Forget your toolkit.
You can fix almost anything, Its not too hard for you. It may be new... YOU CAN DO IT.
Also, I have to say it... Its not going to help anyone, but it will keep me from punching something. ADB and Fastboot... Not the same. You don't ADB a new system image....
UPDATE Thanks to @thjubeck for testing this, it seems that this userdebug kernel actually works on all devices running antirollback v0 and running Marshmallow! I only have the Sprint variant, so be careful!!! Enjoy root guys
A bit of a disclaimer is that this is root through adb. dm-verity is off and system is rw, so you can install apps as root, get a hotspot hack to work, and anything through a shell but I am having trouble installing SuperSU. Please try yourself though as I am probably doing something wrong! If there are any bugs you have found please post them, as this phone is my backup and not my daily driver.
So okay, here is the guide:
PLEASE MAKE SURE YOU HAVE A WAY TO GO BACK INCASE THINGS GO WRONG. DO NOT ATTEMPT TO ROOT THIS WITHOUT HAVING A KDZ/TOT FOR YOUR DEVICE THAT YOU KNOW YOU CAN FLASH BACK TO. I AM NOT RESPONSIBLE FOR THINGS GOING WRONG.
Here is the fix for LGUP
1. Download this zip
2. Install Terminal Emulator from the Play Store
(This is modified from the V20 bootloader unlock, HUGE thanks to all of those devs for sharing their dirtysanta code with me and allowing me to modify it!)
3. Copy all the files from inside the "dirtysanta-boot" and paste it into your active ADB directory
4. Plug your device into the computer and verify ADB is working. Then;
On Windows, double-click "RUNMEFIRST.bat, DO NOT CLOSE THE LOG WINDOW THAT OPENS, then double-click "Step1.bat"
On Linux/MacOS ("#" Signifies a comment below)
Code:
./RUNMEFIRST.sh
# OR
bash ./RUNMEFIRST.sh
Open a Separate Terminal next to the RUNMEFIRST terminal, then type:
Code:
./Step1.sh
# OR
bash ./Step1.sh
(When you run The sh or Bat files there may be a Permission denied error on 2 files: Flatland and Flatland64. This is normal and nothing to worry about.)
5. Wait for a shell prompt, then type (or copy):
Code:
run-as con
chmod 0777 /storage/emulated/0/*
6. Open Up Terminal Emulator on your phone
Type:
Code:
id
Check if context is "Untrusted_app". If it is then we're good to go!
7. Type into Terminal Emulator:
Code:
applypatch /system/bin/atd /storage/emulated/0/dirtysanta
8. Watch the RUNMEFIRST dialog for when it tells you to run Step2 (we don't have a step 2)
9. Reboot the phone into recovery mode and wipe data again
BOOM! Now the you have a userdebug kernel running on a userdebug system Time to turn off dm-verity, otherwise you will have a red triangle on reboot (Your device is corrupt. It cannot be trusted and may not boot) and cannot edit /system.
1. Finish setting up the phone and enable USB Debugging in developer options (you should know how to do this)
2. Plug the phone into your computer, and run these commands
Code:
adb root
adb disable-verity
3. Reboot the phone
4. Run
Code:
adb root
adb shell
mount -o rw,remount,rw /system
Bam. Enjoy your FULL UNLIMITED root shell with system set to rw and dm-verity off!!! Just make sure to type "adb root" before "adb shell"
If you ever want to go back, just flash your stock TOT/KDZ with UPPERCUT and you'll be all good!
BUY ME A PIZZA FOR THE HARD WORK: BTC 197ct1uti4zutJu76bYAW51H8NZ6zXeoEV PayPal: [email protected]
THANKS:
@tungkick for the userdebug boot and helping me with the ZV4 TOTs
@autoprime for UPPERCUT
@me2151 @glitschi667 @EMSpilot @elliwigy for their AMAZING work on the V20 and sharing their code!
I'm using a H850, but still - thanks for your work!
Thanks for the amazing work while almost every one lose the hope .
Allow me to ask about the other versions H860 in my case .
Any chance to modified your files to make it work ?
If you need a testing phone to try figure it out Pm me .
Again thanks for this great job
I'm a Canadian H831 owner. Just wanted to post to say great work so far and if you get SuperSU or another SU app installed, enjoy the $850 bounty.
I think I also found an unlimited hotspot hack, so there's that too!
You're doing God's work, sir. :good:
I wish I had that variant... you'be renewed my hope though.
I have a Canadian H831 [Telus], how much of an undertaking is it to rejigger your method for it?
Delete
Honestly Annoying said:
I think I also found an unlimited hotspot hack, so there's that too!
Click to expand...
Click to collapse
Care to share this info?
Sent from my LGE LG-H830 using XDA Labs
Honestly Annoying said:
Hello everyone, finally the moment you've all been waiting for! I know that a certain user who will not be named has been spreading false information about our root progress, so I am taking it upon myself to release what I personally have gotten to work
A bit of a disclaimer is that this is root through adb. dm-verity is off and system is rw, so you can install apps as root, get a hotspot hack to work, and anything through a shell but I am having trouble installing SuperSU. Please try yourself though as I am probably doing something wrong!
So okay, here is the guide:
ONLY FOR SPRINT USERS ON ZV4. YOU WILL HAVE TO WIPE YOUR DEVICE AND THIS IS YOUR WARNING HERE. DEVICE MAY BE UNSTABLE AS IT IS A USERDEBUG BUILD. THIS IS YOUR WARNING
1. Download these files here and unzip them to desktop https://drive.google.com/open?id=0B2OlLU7vg4YzLWdQYW8tWkxTbFU
2. Set up LGUP from Autoprime's guide here http://forum.xda-developers.com/lg-g5/development/uppercut-lgup-loader-g5-variants-t3511295
3. Make sure you have working ADB set up on your computer
3. Put device in download mode and plug in to computer
4. Flash LS992ZV4_04.userdebug.tot as UPGRADE
5. Boot phone into recovery mode and wipe data
6. After phone is finished setting up, install Terminal Emulator from the Play Store
(This is copied from the V20 bootloader unlock, HUGE thanks to all of those devs for sharing their dirtysanta code with me and allowing me to modify it!)
7. Copy all the files from inside the "dirtysanta-boot" and paste it into your active ADB directory
8. Plug your device into the computer and verify ADB is working. Then;
On Windows, double-click "RUNMEFIRST.bat, DO NOT CLOSE THE LOG WINDOW THAT OPENS, then double-click "Step1.bat"
On Linux/MacOS ("#" Signifies a comment below)
Code:
./RUNMEFIRST.sh
# OR
bash ./RUNMEFIRST.sh
Open a Separate Terminal next to the RUNMEFIRST terminal, then type:
Code:
./Step1.sh
# OR
bash ./Step1.sh
(When you run The sh or Bat files there may be a Permission denied error on 2 files: Flatland and Flatland64. This is normal and nothing to worry about.)
9. Wait for a shell prompt, then type (or copy):
Code:
run-as con
chmod 0777 /storage/emulated/0/*
10. Open Up Terminal Emulator on your phone
Type:
Code:
id
Check if context is "Untrusted_app". If it is then we're good to go!
11. Type into Terminal Emulator:
Code:
applypatch /system/bin/atd /storage/emulated/0/dirtysanta
12. Watch the RUNMEFIRST dialog for when it tells you to run Step2 (we don't have a step 2)
13. Reboot the phone into recovery mode and wipe data again
BOOM! Now the you have a userdebug kernel running on a userdebug system Time to turn off dm-verity
1. Finish setting up the phone and enable USB Debugging in developer options (you should know how to do this)
2. Plug the phone into your computer, and run these commands
Code:
adb root
adb disable-verity
3. Reboot the phone
4. Run
Code:
adb root
adb shell
mount -o rw,remount,rw /system
Bam. Enjoy your FULL UNLIMITED root shell with system set to rw and dm-verity off!!! Just make sure to type "adb root" before "adb shell"
If you ever want to go back, just flash the LS992ZV4_04.tot with UPPERCUT and you'll be all good!
BUY ME A PIZZA FOR THE HARD WORK: BTC 197ct1uti4zutJu76bYAW51H8NZ6zXeoEV (sorry, no PayPal :/)
THANKS:
@tungkick for the userdebug boot and helping me with the ZV4 TOTs
@autoprime for UPPERCUT
@me2151 @glitschi667 @EMSpilot @elliwigy for their AMAZING work on the V20 and sharing their code!
@schiziodd for showing how to hex edit TOT
Click to expand...
Click to collapse
Hello, I am working on the root for the Verizon V10 and I came across this today. I was wondering how you made the userdebug.tot because I know this will work on it, Dirty Santa works up to the same point as you, so i'm wondering if I could do this and maybe even get supersu to work. Thank you
@Honestly Annoying could it be possible for you to "spoof" the firmware info and change the variant (LS992ZV4) to other locked g5 (such as the h831 h860..) so we can try to flash it via uppercut and see how much it's broken ?
Update: Now works on all devices running antirollback v0!!!!
Honestly Annoying said:
Update: Now works on all devices running antirollback v0!!!!
Click to expand...
Click to collapse
Will this work on Canadian variant? How do we know what version of antirollback we have?
mapleleafs89 said:
Will this work on Canadian variant? What is antirollback v0?
Click to expand...
Click to collapse
I am not sure how to check the antirollback version on on actual phone, you would need @autoprime for that.
Antirollback is basically exactly what it sounds like: It is part of each update that disallows users to rollback to previous versions of their software. This is built off of the first version of antirollback (v0) for the G5, so it will only work on phones with that version. You can test it out yourself, as it won't do any permanent damage, but just make sure you have a working TOT/KDZ to go back on.
*#546368#*850# (hiden menu)
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
BrunoSlivar said:
*#546368#*850# (hiden menu)
Click to expand...
Click to collapse
I enter this in the dialer and call, it says USSD code running but then throws an error "Connection problem or invalid MMI code."
BrunoSlivar said:
*#546368#*850# (hiden menu)
Click to expand...
Click to collapse
Thanks for that!
mapleleafs89 said:
I enter this in the dialer and call, it says USSD code running but then throws an error "Connection problem or invalid MMI code."
Click to expand...
Click to collapse
Change the "850" to your model number. Such as "830" for T-Mobile or "992" for Sprint
Aha! 831 Canadian variant running Marshmallow. Almost upgraded to nougat but then saw this thread thankfully, I guess I will hold off if this means it increases my chances of getting root
For those interested, I can confirm that every h831 firmware up to nougat has a rollback count of 0, and from @autoprime :
H850 and H860 are fuse 00 and Sprint ZV3/4 are fuse 00.
Click to expand...
Click to collapse
Anything higher than ZV4 is 01 or higher.
Click to expand...
Click to collapse
I don't know what I missed, but now I get Your device is corrupt. It cannot be trusted and will not boot . I'mma try to flash back my system and try it again.
H860 with Nougat and anti-rollback version 0
P.S : I can't enter recovery or download mode ... how much I'm I screwed ? It just keeps rebooting