Develop Bugs

[Q] Issues Compiling Droid Incredible Kernel

Evening All,
I am attempting to compile a kernel for my droid incredible and am running into a problem. I successfully compiled one a few weeks ago, but am trying to refresh so i can learn more. I am using instructions found at:
http://wiki.cyanogenmod.com/index.php?title=Building_from_source,
only changing commands when necessary. I have pulled a working .config from Skyraider 2.2, created the backup and was able to edit it to my liking. For this I decided to leave everything as stock, as my intention was to just compile the stock kernel to help myself learn. When I enter
Code:
make ARCH=arm CROSS_COMPILE=$CCOMPILER
,
I receive the following error:
Code:
[email protected]:~/androkern/incredible$ make ARCH=arm CROSS_COMPILE=$CCOMPILER
scripts/kconfig/conf -s arch/arm/Kconfig
CHK include/linux/version.h
UPD include/linux/version.h
Generating include/asm-arm/mach-types.h
CHK include/linux/utsrelease.h
UPD include/linux/utsrelease.h
SYMLINK include/asm -> include/asm-arm
CC kernel/bounds.s
cc1: error: unrecognized command line option "-mlittle-endian"
cc1: error: unrecognized command line option "-mapcs"
cc1: error: unrecognized command line option "-mno-sched-prolog"
cc1: error: unrecognized command line option "-mno-thumb-interwork"
kernel/bounds.c:1: error: unknown ABI (aapcs-linux) for -mabi= switch
kernel/bounds.c:1: error: bad value (armv5t) for -march= switch
kernel/bounds.c:1: error: bad value (armv5t) for -mtune= switch
make[1]: *** [kernel/bounds.s] Error 1
make: *** [prepare0] Error 2
Being new to compiling would anyone be able to help me understand what this error means. I have not found anything so far that could help me. I was not expecting any issues since I was essential just compiling the Stock Kernel for my own use.
Would someone be able to help me learn what is causing this? Thank you.

tcberg2010 said:
Evening All,
I am attempting to compile a kernel for my droid incredible and am running into a problem. I successfully compiled one a few weeks ago, but am trying to refresh so i can learn more. I am using instructions found at:
http://wiki.cyanogenmod.com/index.php?title=Building_from_source,
only changing commands when necessary. I have pulled a working .config from Skyraider 2.2, created the backup and was able to edit it to my liking. For this I decided to leave everything as stock, as my intention was to just compile the stock kernel to help myself learn. When I enter
Code:
make ARCH=arm CROSS_COMPILE=$CCOMPILER
,
I receive the following error:
Code:
[email protected]:~/androkern/incredible$ make ARCH=arm CROSS_COMPILE=$CCOMPILER
scripts/kconfig/conf -s arch/arm/Kconfig
CHK include/linux/version.h
UPD include/linux/version.h
Generating include/asm-arm/mach-types.h
CHK include/linux/utsrelease.h
UPD include/linux/utsrelease.h
SYMLINK include/asm -> include/asm-arm
CC kernel/bounds.s
cc1: error: unrecognized command line option "-mlittle-endian"
cc1: error: unrecognized command line option "-mapcs"
cc1: error: unrecognized command line option "-mno-sched-prolog"
cc1: error: unrecognized command line option "-mno-thumb-interwork"
kernel/bounds.c:1: error: unknown ABI (aapcs-linux) for -mabi= switch
kernel/bounds.c:1: error: bad value (armv5t) for -march= switch
kernel/bounds.c:1: error: bad value (armv5t) for -mtune= switch
make[1]: *** [kernel/bounds.s] Error 1
make: *** [prepare0] Error 2
Being new to compiling would anyone be able to help me understand what this error means. I have not found anything so far that could help me. I was not expecting any issues since I was essential just compiling the Stock Kernel for my own use.
Would someone be able to help me learn what is causing this? Thank you.
Click to expand...
Click to collapse
you need to do:
export CCOMPILER=${HOME}/mydroid/prebuilt/linux-x86/toolchain/arm-eabi-4.4.0/bin/arm-eabi-
(assuming you pulled everything down in ~/mydroid , otherwise change it to where it is)
then you should be able to compile it

That command did work for me. I was able to compile it. What I would still like to know is what exactly I did when i ran that command? I don't really enjoy mashing in commands when i don't know what they mean.

Basically you created an environmental variable called CCOMPILER that is equal to the location of the cross compiler binaries.
This command would do the same thing:
make ARCH=arm CROSS_COMPILE=${HOME}/mydroid/prebuilt/linux-x86/toolchain/arm-eabi-4.4.0/bin/arm-eabi-
You are just pointing the make file to the location of the cross compiler so that it doesn't use the host compiler by default

mattwood2000 said:
Basically you created an environmental variable called CCOMPILER that is equal to the location of the cross compiler binaries.
This command would do the same thing:
make ARCH=arm CROSS_COMPILE=${HOME}/mydroid/prebuilt/linux-x86/toolchain/arm-eabi-4.4.0/bin/arm-eabi-
You are just pointing the make file to the location of the cross compiler so that it doesn't use the host compiler by default
Click to expand...
Click to collapse
+1 Whenever you "export" you're setting an environment variable to something. Then you can verify it by typing: "echo $CCOMPILER" (without quotes) and it should spit that path back at you.

fwiw, you can add that line to your .bashrc and it will always be set for you

Thank you guys, to be honest that answer is a little over my head, but its a nice basis to help me learn more. Really appreciate the quick responses.
Sent from my ADR6300 using XDA App

New Desire after ROOT + S OFF --> unmount SDCARD

Hello all
I just bought a second Desire.
After S OFF it and change recovery and Radio.
And after I just put new ROM CM10.1 but error with symlinks....
I restart the Desire and ...
I note that it can't mount sdcard.
I check all i read on this forum and other but nothing work.
Testing 4Ext USB Brick
Testing instruction in fastboot
Test: fastboot oem enableqxdm 0
fastboot oem eraseconfig
For information the Desire write this on main screen :
BRAVO PVT4 SHIP S-OFF
HBOOT-6.93 1002
MICROP-051d
TOUCH PANEL-SYM0101
RADIO-5.17.05.08
I always flash with my PC with Fastboot but after no way to mount.
I can change recovery , hboot but the sdcard did not mount.
I test sdcard in my other Desire and It is works
I take all ideas to found an solution.
Code:
D:\Android\Roms\Hboot>fastboot.exe oem boot
... INFOsetup_tag addr=0xA0000100 cmdline add=0x8E07F9F0
INFOTAG:Ramdisk OK
INFOTAG:smi ok, size = 0
INFOTAG:hwid 0x0
INFOTAG:skuid 0x26A12
INFOTAG:hero panel = 0x3
INFOTAG:engineerid = 0x0
INFOMCP dual-die
INFOMCP dual-die
INFOTAG:mono-die = 0x0
INFODevice CID is super CID
INFOCID is super CID
INFOBackup CID is HTC__E11
INFOsetting->cid::HTC__E11
INFOserial number: MB137PL07227
INFOcommandline from head: no_console_suspend=1
INFOcommand line length =423
INFOactive commandline: board_bravo.disable_uart3=0 board_bravo.
INFOusb_h2w_sw=0 board_bravo.disable_sdcard=0 diag.enabled=0 boa
INFOrd_bravo.debug_uart=0 smisize=0 userdata_sel=0 androidboot.e
INFOmmc=false androidboot.baseband=5.17.05.08 androidboot.cid=H
INFOTC__E11 androidboot.carrier=HTC-Dutch androidboot.mid=PB9920
INFO000 androidboot.keycaps=qwerty androidboot.mode=normal andro
INFOidboot.serialno=MB137PL07227 androidboot.bootloader=6.93.100
INFO2 no_console_suspend=1
INFOaARM_Partion[0].name=misc
INFOaARM_Partion[1].name=recovery
INFOaARM_Partion[2].name=boot
INFOaARM_Partion[3].name=system
INFOaARM_Partion[4].name=cache
INFOaARM_Partion[5].name=userdata
INFOpartition number=6
INFOValid partition num=6
INFOjump_to_kernel: machine_id(2457), tags_addr(0x20000100), ker
INFOnel_addr(0x20008000)
INFO-------------------hboot boot time:104796 msec

Hello people,
anybody have an idea what can i flash to solve my problem.
I have always full access to Bootloader and Fastboot , and recovery.
But when I boot stuck on HTC screen.
And in all recovery I test the message when I choose "choose zip fro msdcard " = "E:can't mount /sdcard/ "

jodiskett said:
Hello people,
anybody have an idea what can i flash to solve my problem.
I have always full access to Bootloader and Fastboot , and recovery.
But when I boot stuck on HTC screen.
And in all recovery I test the message when I choose "choose zip fro msdcard " = "E:can't mount /sdcard/ "
Click to expand...
Click to collapse
I recommend you to download Fastboot Commander and then do this:
wipe all partitions
flash the latest radio and stock hboot
flash CronMod or any other rom
If it still doesn't work I think it has to be an hardware issue...
I'm not an expert, but this way you maybe you can try to get it working...

Androidmarketuser said:
I recommend you to download Fastboot Commander and then do this:
wipe all partitions
flash the latest radio and stock hboot
flash CronMod or any other rom
If it still doesn't work I think it has to be an hardware issue...
I'm not an expert, but this way you maybe you can try to get it working...
Click to expand...
Click to collapse
Thanks for your help, but same result.
I check this method
Code:
ROM update without SDcard
If you don't have an sd card, or your slot is broken you can try this trick, but you will need a custom recovery like Clockwork.
Boot up your phone to recovery. And move your rom file to the adb directory, and start a command line ( cmd )
adb shell
mount data
adb push D:\custom_rom.zip /data/
Wait until the push finised, and restart your device to recovery again with "adb reboot-bootloader"
mount data
mount /data /sdcard ( mount the data folder into your sdcard folder, so your recovery will think that you have an sdcard installed )
Locate the ROM .Zip file you wish to flash.
Confirm the flash by following the on-screen instructions (ie: pressing the trackball, pressing the call button, etc.)
If no errors arise during the flashing process then the ROM flash was successful, Reboot the device.
With some root file explorer, remove the rom file if you don't need it anymore, to free up space.
Or use adb to remove the custom recovery
But i have little problem with command : adb push d:\file.rom /data/
I have error can someone give exact sentence ?
Thnaks

jodiskett said:
But i have little problem with command : adb push d:\file.rom /data/
I have error can someone give exact sentence ?
Thnaks
Click to expand...
Click to collapse
Can you write what the error message is?
If it is too long to write make a screenshot with Print key and paste it in paint.
Check if you have entered the correct path

I have this:
D:\Android\adb>adb shell
~ # mount data
mount data
~ # adb push d:\roms.zip data
adb push d:\roms.zip data
/sbin/sh: adb: not found
~ # adb push roms.zip data
adb push roms.zip data
/sbin/sh: adb: not found
~ # adb push roms.zip data
i think it is the name of roms.zip what is wrong.
I put roms.zip in root of D: , same folder of adb but nothing is ok

jodiskett said:
I have this:
D:\Android\adb>adb shell
~ # mount data
mount data
~ # adb push d:\roms.zip data
adb push d:\roms.zip data
/sbin/sh: adb: not found
~ # adb push roms.zip data
adb push roms.zip data
/sbin/sh: adb: not found
~ # adb push roms.zip data
i think it is the name of roms.zip what is wrong.
I put roms.zip in root of D: , same folder of adb but nothing is ok
Click to expand...
Click to collapse
No, you can't execute the "adb push roms.zip /data/" if you are still in the adb shell.
after you mounted the data partition, press Ctrl+C to close the shell mode and then enter "adb push roms.zip" and make sure you're in the right directory, otherwise enter the full filepath, foor example
Code:
abd push "D:\Program Files\roms.zip"

Yes , i did it
Thanks for the ctrl^c
I can flash the rom, I flashed Cron Mod and the phone started.
It is ok but no sdcard read.
Seems to be hardware problems
But i have time to check
Thanks guy

[Q] Please help me with 2nd-Bootloader/Recovery unlock process for KFire 2

Hello
I'm having problems following the post [BOOTLOADER] 2nd-Bootloader/Recovery unlock process for KFire 2 [TWRP 2.6.3.0]
I tried several ways during several days but I'm totally stuck, I don't know what i should do more. My KF is 10.5.0, from 2012, not HD, without camera, so I'm sure that is KF2, second generation. And I'm working with Mac OSx.
Here what i did;
STEP 1. Backup your stock partitions to your own HD for later if you need disaster recovery >>> i cannot make it
myname-MacBook-Pro:~ myname$ adb pull /dev/block/mmcblk0boot0 failed to copy '/dev/block/mmcblk0boot0' to './mmcblk0boot0': Permission denied
So i didn't make backup and go direct to STEP 2 and 3.
I placed all the files on my device in the sdcard area.
STEP 3. Install the stack override in /system: It looked it worked, i used factory cable;
myname-MacBook-Pro:~ myname$ adb push stack/download
Android Debug Bridge version 1.0.29
-d - directs command to the only connected USB device
returns an error if more than one USB device is present.
-e - directs command to the only running emulator.
returns an error if more than one emulator is running.
-s <serial number> - directs command to the USB device or emulator with
the given serial number. Overrides ANDROID_SERIAL
environment variable.
-p <product name or path> - simple product name like 'sooner', or
a relative/absolute path to a product
out directory like 'out/target/product/sooner'.
If -p is not specified, the ANDROID_PRODUCT_OUT
environment variable is used, which must
be an absolute path.
devices - list all connected devices
connect <host>[:<port>] - connect to a device via TCP/IP
Port 5555 is used by default if no port number is specified.
disconnect [<host>[:<port>]] - disconnect from a TCP/IP device.
Port 5555 is used by default if no port number is specified.
Using this command with no additional arguments
will disconnect from all connected TCP/IP devices.
device commands:
adb push <local> <remote> - copy file/dir to device
adb pull <remote> [<local>] - copy file/dir from device
adb sync [ <directory> ] - copy host->device only if changed
(-l means list but don't copy)
(see 'adb help all')
adb shell - run remote shell interactively
adb shell <command> - run remote shell command
adb emu <command> - run emulator console command
adb logcat [ <filter-spec> ] - View device log
adb forward <local> <remote> - forward socket connections
forward specs are one of:
tcp:<port>
localabstract:<unix domain socket name>
localreserved:<unix domain socket name>
localfilesystem:<unix domain socket name>
dev:<character device name>
jdwp:<process pid> (remote only)
adb jdwp - list PIDs of processes hosting a JDWP transport
adb install [-l] [-r] [-s] <file> - push this package file to the device and install it
('-l' means forward-lock the app)
('-r' means reinstall the app, keeping its data)
('-s' means install on SD card instead of internal storage)
adb uninstall [-k] <package> - remove this app package from the device
('-k' means keep the data and cache directories)
adb bugreport - return all information from the device
that should be included in a bug report.
adb backup [-f <file>] [-apk|-noapk] [-shared|-noshared] [-all] [-system|-nosystem] [<packages...>]
- write an archive of the device's data to <file>.
If no -f option is supplied then the data is written
to "backup.ab" in the current directory.
(-apk|-noapk enable/disable backup of the .apks themselves
in the archive; the default is noapk.)
(-shared|-noshared enable/disable backup of the device's
shared storage / SD card contents; the default is noshared.)
(-all means to back up all installed applications)
(-system|-nosystem toggles whether -all automatically includes
system applications; the default is to include system apps)
(<packages...> is the list of applications to be backed up. If
the -all or -shared flags are passed, then the package
list is optional. Applications explicitly given on the
command line will be included even if -nosystem would
ordinarily cause them to be omitted.)
adb restore <file> - restore device contents from the <file> backup archive
adb help - show this help message
adb version - show version num
scripting:
adb wait-for-device - block until device is online
adb start-server - ensure that there is a server running
adb kill-server - kill the server if it is running
adb get-state - prints: offline | bootloader | device
adb get-serialno - prints: <serial-number>
adb status-window - continuously print device status for a specified device
adb remount - remounts the /system partition on the device read-write
adb reboot [bootloader|recovery] - reboots the device, optionally into the bootloader or recovery program
adb reboot-bootloader - reboots the device into the bootloader
adb root - restarts the adbd daemon with root permissions
adb usb - restarts the adbd daemon listening on USB
adb tcpip <port> - restarts the adbd daemon listening on TCP on the specified port
networking:
adb ppp <tty> [parameters] - Run PPP over USB.
Note: you should not automatically start a PPP connection.
<tty> refers to the tty for PPP stream. Eg. dev:/dev/omap_csmi_tty1
[parameters] - Eg. defaultroute debug dump local notty usepeerdns
adb sync notes: adb sync [ <directory> ]
<localdir> can be interpreted in several ways:
- If <directory> is not specified, both /system and /data partitions will be updated.
- If it is "system" or "data", only the corresponding partition
is updated.
environmental variables:
ADB_TRACE - Print debug information. A comma separated list of the following values
1 or all, adb, sockets, packets, rwx, usb, sync, sysdeps, transport, jdwp
ANDROID_SERIAL - The serial number to connect to. -s takes priority over this if given.
ANDROID_LOG_TAGS - When used with the logcat option, only these debug tags are printed.
Silvia-Kozakura-no-MacBook-Pro:~ silviakozakura$ adb shell su -c "dd if=/sdcard/stack of=/dev/block/platform/omap/omap_hsmmc.1/by-name/system bs=6519488 seek=1"
And then the STEP 4, where I'm stuck "Flash the OLD bootloader, new otter2-freedom-boot.img and TWRP recovery" I used factory cable to enter in Fastboot mode but always i get this error;
myname-MacBook-Pro:~ myname$ fastboot -i 0x1949 flash bootloader otter2-u-boot-prod-10.2.4.bin
error: cannot load 'otter2-u-boot-prod-10.2.4.bin'
- Cannot load any file, I put all the files at sdcard/download, I don't know what i did wrong.
I'm willing to pay money to who will help me.

KindleRooteado said:
Hello
I'm having problems following the post [BOOTLOADER] 2nd-Bootloader/Recovery unlock process for KFire 2 [TWRP 2.6.3.0]
I tried several ways during several days but I'm totally stuck, I don't know what i should do more. My KF is 10.5.0, from 2012, not HD, without camera, so I'm sure that is KF2, second generation. And I'm working with Mac OSx.
Here what i did;
STEP 1. Backup your stock partitions to your own HD for later if you need disaster recovery >>> i cannot make it
myname-MacBook-Pro:~ myname$ adb pull /dev/block/mmcblk0boot0 failed to copy '/dev/block/mmcblk0boot0' to './mmcblk0boot0': Permission denied
So i didn't make backup and go direct to STEP 2 and 3.
I placed all the files on my device in the sdcard area.
STEP 3. Install the stack override in /system: It looked it worked, i used factory cable;
myname-MacBook-Pro:~ myname$ adb push stack/download
Android Debug Bridge version 1.0.29
-d - directs command to the only connected USB device
returns an error if more than one USB device is present.
-e - directs command to the only running emulator.
returns an error if more than one emulator is running.
-s <serial number> - directs command to the USB device or emulator with
the given serial number. Overrides ANDROID_SERIAL
environment variable.
-p <product name or path> - simple product name like 'sooner', or
a relative/absolute path to a product
out directory like 'out/target/product/sooner'.
If -p is not specified, the ANDROID_PRODUCT_OUT
environment variable is used, which must
be an absolute path.
devices - list all connected devices
connect <host>[:<port>] - connect to a device via TCP/IP
Port 5555 is used by default if no port number is specified.
disconnect [<host>[:<port>]] - disconnect from a TCP/IP device.
Port 5555 is used by default if no port number is specified.
Using this command with no additional arguments
will disconnect from all connected TCP/IP devices.
device commands:
adb push <local> <remote> - copy file/dir to device
adb pull <remote> [<local>] - copy file/dir from device
adb sync [ <directory> ] - copy host->device only if changed
(-l means list but don't copy)
(see 'adb help all')
adb shell - run remote shell interactively
adb shell <command> - run remote shell command
adb emu <command> - run emulator console command
adb logcat [ <filter-spec> ] - View device log
adb forward <local> <remote> - forward socket connections
forward specs are one of:
tcp:<port>
localabstract:<unix domain socket name>
localreserved:<unix domain socket name>
localfilesystem:<unix domain socket name>
dev:<character device name>
jdwp:<process pid> (remote only)
adb jdwp - list PIDs of processes hosting a JDWP transport
adb install [-l] [-r] [-s] <file> - push this package file to the device and install it
('-l' means forward-lock the app)
('-r' means reinstall the app, keeping its data)
('-s' means install on SD card instead of internal storage)
adb uninstall [-k] <package> - remove this app package from the device
('-k' means keep the data and cache directories)
adb bugreport - return all information from the device
that should be included in a bug report.
adb backup [-f <file>] [-apk|-noapk] [-shared|-noshared] [-all] [-system|-nosystem] [<packages...>]
- write an archive of the device's data to <file>.
If no -f option is supplied then the data is written
to "backup.ab" in the current directory.
(-apk|-noapk enable/disable backup of the .apks themselves
in the archive; the default is noapk.)
(-shared|-noshared enable/disable backup of the device's
shared storage / SD card contents; the default is noshared.)
(-all means to back up all installed applications)
(-system|-nosystem toggles whether -all automatically includes
system applications; the default is to include system apps)
(<packages...> is the list of applications to be backed up. If
the -all or -shared flags are passed, then the package
list is optional. Applications explicitly given on the
command line will be included even if -nosystem would
ordinarily cause them to be omitted.)
adb restore <file> - restore device contents from the <file> backup archive
adb help - show this help message
adb version - show version num
scripting:
adb wait-for-device - block until device is online
adb start-server - ensure that there is a server running
adb kill-server - kill the server if it is running
adb get-state - prints: offline | bootloader | device
adb get-serialno - prints: <serial-number>
adb status-window - continuously print device status for a specified device
adb remount - remounts the /system partition on the device read-write
adb reboot [bootloader|recovery] - reboots the device, optionally into the bootloader or recovery program
adb reboot-bootloader - reboots the device into the bootloader
adb root - restarts the adbd daemon with root permissions
adb usb - restarts the adbd daemon listening on USB
adb tcpip <port> - restarts the adbd daemon listening on TCP on the specified port
networking:
adb ppp <tty> [parameters] - Run PPP over USB.
Note: you should not automatically start a PPP connection.
<tty> refers to the tty for PPP stream. Eg. dev:/dev/omap_csmi_tty1
[parameters] - Eg. defaultroute debug dump local notty usepeerdns
adb sync notes: adb sync [ <directory> ]
<localdir> can be interpreted in several ways:
- If <directory> is not specified, both /system and /data partitions will be updated.
- If it is "system" or "data", only the corresponding partition
is updated.
environmental variables:
ADB_TRACE - Print debug information. A comma separated list of the following values
1 or all, adb, sockets, packets, rwx, usb, sync, sysdeps, transport, jdwp
ANDROID_SERIAL - The serial number to connect to. -s takes priority over this if given.
ANDROID_LOG_TAGS - When used with the logcat option, only these debug tags are printed.
Silvia-Kozakura-no-MacBook-Pro:~ silviakozakura$ adb shell su -c "dd if=/sdcard/stack of=/dev/block/platform/omap/omap_hsmmc.1/by-name/system bs=6519488 seek=1"
And then the STEP 4, where I'm stuck "Flash the OLD bootloader, new otter2-freedom-boot.img and TWRP recovery" I used factory cable to enter in Fastboot mode but always i get this error;
myname-MacBook-Pro:~ myname$ fastboot -i 0x1949 flash bootloader otter2-u-boot-prod-10.2.4.bin
error: cannot load 'otter2-u-boot-prod-10.2.4.bin'
- Cannot load any file, I put all the files at sdcard/download, I don't know what i did wrong.
I'm willing to pay money to who will help me.
Click to expand...
Click to collapse
You have to keep the files on your PC, not the Kindle. Execute the commands from where you kept the files. I'll write you a full tutorial when I have time.
Sent from my device running CyanogenMod 11

SafinWasi said:
You have to keep the files on your PC, not the Kindle. Execute the commands from where you kept the files. I'll write you a full tutorial when I have time.
Sent from my device running CyanogenMod 11
Click to expand...
Click to collapse
That makes sense, thank you! I will try

Well, now I don't understand anything, I'm making the same i did yestarday but without the same results, with different errors.
I've relocated the factory settings in KF and I checked if the root is ok.
So now says;
STEP 1. Backup
myname-no-MacBook-Pro:~ myname$ adb pull /dev/block/mmcblk0boot0
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
error: device not found
STEP 3. Install the stack override in /system
myname-no-MacBook-Pro:~ myname$ adb push stack/download
Android Debug Bridge version 1.0.29
-d - directs command to the only connected USB device
returns an error if more than one USB device is present.
-e - directs command to the only running emulator.
returns an error if more than one emulator is running.
-s <serial number> - directs command to the USB device or emulator with
the given serial number. Overrides ANDROID_SERIAL
environment variable.
-p <product name or path> - simple product name like 'sooner', or
a relative/absolute path to a product
out directory like 'out/target/product/sooner'.
If -p is not specified, the ANDROID_PRODUCT_OUT
environment variable is used, which must
be an absolute path.
devices - list all connected devices
connect <host>[:<port>] - connect to a device via TCP/IP
Port 5555 is used by default if no port number is specified.
disconnect [<host>[:<port>]] - disconnect from a TCP/IP device.
Port 5555 is used by default if no port number is specified.
Using this command with no additional arguments
will disconnect from all connected TCP/IP devices.
device commands:
adb push <local> <remote> - copy file/dir to device
adb pull <remote> [<local>] - copy file/dir from device
adb sync [ <directory> ] - copy host->device only if changed
(-l means list but don't copy)
(see 'adb help all')
adb shell - run remote shell interactively
adb shell <command> - run remote shell command
adb emu <command> - run emulator console command
adb logcat [ <filter-spec> ] - View device log
adb forward <local> <remote> - forward socket connections
forward specs are one of:
tcp:<port>
localabstract:<unix domain socket name>
localreserved:<unix domain socket name>
localfilesystem:<unix domain socket name>
dev:<character device name>
jdwp:<process pid> (remote only)
adb jdwp - list PIDs of processes hosting a JDWP transport
adb install [-l] [-r] [-s] <file> - push this package file to the device and install it
('-l' means forward-lock the app)
('-r' means reinstall the app, keeping its data)
('-s' means install on SD card instead of internal storage)
adb uninstall [-k] <package> - remove this app package from the device
('-k' means keep the data and cache directories)
adb bugreport - return all information from the device
that should be included in a bug report.
adb backup [-f <file>] [-apk|-noapk] [-shared|-noshared] [-all] [-system|-nosystem] [<packages...>]
- write an archive of the device's data to <file>.
If no -f option is supplied then the data is written
to "backup.ab" in the current directory.
(-apk|-noapk enable/disable backup of the .apks themselves
in the archive; the default is noapk.)
(-shared|-noshared enable/disable backup of the device's
shared storage / SD card contents; the default is noshared.)
(-all means to back up all installed applications)
(-system|-nosystem toggles whether -all automatically includes
system applications; the default is to include system apps)
(<packages...> is the list of applications to be backed up. If
the -all or -shared flags are passed, then the package
list is optional. Applications explicitly given on the
command line will be included even if -nosystem would
ordinarily cause them to be omitted.)
adb restore <file> - restore device contents from the <file> backup archive
adb help - show this help message
adb version - show version num
scripting:
adb wait-for-device - block until device is online
adb start-server - ensure that there is a server running
adb kill-server - kill the server if it is running
adb get-state - prints: offline | bootloader | device
adb get-serialno - prints: <serial-number>
adb status-window - continuously print device status for a specified device
adb remount - remounts the /system partition on the device read-write
adb reboot [bootloader|recovery] - reboots the device, optionally into the bootloader or recovery program
adb reboot-bootloader - reboots the device into the bootloader
adb root - restarts the adbd daemon with root permissions
adb usb - restarts the adbd daemon listening on USB
adb tcpip <port> - restarts the adbd daemon listening on TCP on the specified port
networking:
adb ppp <tty> [parameters] - Run PPP over USB.
Note: you should not automatically start a PPP connection.
<tty> refers to the tty for PPP stream. Eg. dev:/dev/omap_csmi_tty1
[parameters] - Eg. defaultroute debug dump local notty usepeerdns
adb sync notes: adb sync [ <directory> ]
<localdir> can be interpreted in several ways:
- If <directory> is not specified, both /system and /data partitions will be updated.
- If it is "system" or "data", only the corresponding partition
is updated.
environmental variables:
ADB_TRACE - Print debug information. A comma separated list of the following values
1 or all, adb, sockets, packets, rwx, usb, sync, sysdeps, transport, jdwp
ANDROID_SERIAL - The serial number to connect to. -s takes priority over this if given.
ANDROID_LOG_TAGS - When used with the logcat option, only these debug tags are printed.
myname-no-MacBook-Pro:~ myname$ adb shell su -c "dd if=/sdcard/stack of=/dev/block/platform/omap/omap_hsmmc.1/by-name/system bs=6519488 seek=1"error: device not found
myname-no-MacBook-Pro:~ myname$ adb shell su -c "dd if=/download/stack of=/dev/block/platform/omap/omap_hsmmc.1/by-name/system bs=6519488 seek=1"
error: device not found
myname-no-MacBook-Pro:~ myname$ adb shell su -c "dd if=/download/stack of=/dev/block/platform/omap/omap_hsmmc.1/by-name/system bs=6519488 seek=1"
error: device not found
I tryed to run "stack" placed on sdcard of the device and placed on my computer, nothing worked.
I think is better don't do anything else, i will wait for help...

KindleRooteado said:
Well, now I don't understand anything, I'm making the same i did yestarday but without the same results, with different errors.
I've relocated the factory settings in KF and I checked if the root is ok.
So now says;
(post edited due to large size_
I tryed to run "stack" placed on sdcard of the device and placed on my computer, nothing worked.
I think is better don't do anything else, i will wait for help...
Click to expand...
Click to collapse
Okay,first off,download the files to your PC,not the Kindle. Connect the Kindle to your PC with USB debugging enabled. Then,open a command window and cd to the directory where you kept the files.
Now issue the following commands to backup partitions:
Code:
adb pull /dev/block/mmcblk0boot0
adb pull /dev/block/platform/omap/omap_hsmmc.1/by-name/boot
adb pull /dev/block/platform/omap/omap_hsmmc.1/by-name/recovery
adb pull /dev/block/platform/omap/omap_hsmmc.1/by-name/system
Note:If you get "permission denied" error,use the following command:
Code:
adb remount
If you still get the error,ensure that you have root.
Next,install the stack override:
Code:
adb push stack /sdcard/
adb shell su -c "dd if=/sdcard/stack of=/dev/block/platform/omap/omap_hsmmc.1/by-name/system bs=6519488 seek=1"
And flash the old bootloader with 2nd bootloader and Team Win Recovery: (use factory cable to boot into fastboot)
Code:
fastboot -i 0x1949 flash bootloader otter2-u-boot-prod-10.2.4.bin
fastboot -i 0x1949 flash boot otter2-freedom-boot-10.4.6.img
fastboot -i 0x1949 flash recovery otter2-twrp-2.6.3.0-recovery.img
fastboot -i 0x1949 reboot

SafinWasi said:
Okay,first off,download the files to your PC,not the Kindle. Connect the Kindle to your PC with USB debugging enabled. Then,open a command window and cd to the directory where you kept the files.
Now issue the following commands to backup partitions:
Code:
adb pull /dev/block/mmcblk0boot0
adb pull /dev/block/platform/omap/omap_hsmmc.1/by-name/boot
adb pull /dev/block/platform/omap/omap_hsmmc.1/by-name/recovery
adb pull /dev/block/platform/omap/omap_hsmmc.1/by-name/system
Note:If you get "permission denied" error,use the following command:
Code:
adb remount
If you still get the error,ensure that you have root.
Next,install the stack override:
Code:
adb push stack /sdcard/
adb shell su -c "dd if=/sdcard/stack of=/dev/block/platform/omap/omap_hsmmc.1/by-name/system bs=6519488 seek=1"
And flash the old bootloader with 2nd bootloader and Team Win Recovery: (use factory cable to boot into fastboot)
Code:
fastboot -i 0x1949 flash bootloader otter2-u-boot-prod-10.2.4.bin
fastboot -i 0x1949 flash boot otter2-freedom-boot-10.4.6.img
fastboot -i 0x1949 flash recovery otter2-twrp-2.6.3.0-recovery.img
fastboot -i 0x1949 reboot
Click to expand...
Click to collapse
Hello, I really appreciate your help. I followed your instructions but I'm still stuck... I got:
Permission denied
remount failed: Operation not permitted
And Superuser is enabled for sure.
{
"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"
}

Can you try mounting system from ES file explorer?
Sent from my device running CyanogenMod 11

SafinWasi said:
Can you try mounting system from ES file explorer?
Sent from my device running CyanogenMod 11
Click to expand...
Click to collapse
thanks, i will do tomorrow

Still doesn't work... I mounted system with ES file explorer and after I tried again to do the backup:
Code:
Last login: Sat Sep 6 09:24:20 on console
myname-no-MacBook-Pro:~ myname$ cd desktop
myname-no-MacBook-Pro:desktop myname$ adb pull /dev/block/mmcblk0boot0
failed to copy '/dev/block/mmcblk0boot0' to './mmcblk0boot0': Permission denied
myname-no-MacBook-Pro:desktop myname$ ./adb pull /dev/block/mmcblk0boot0
-bash: ./adb: No such file or directory
myname-no-MacBook-Pro:desktop myname$ adb remount
remount failed: Operation not permitted
myname-no-MacBook-Pro:desktop myname$ ./adb remount
-bash: ./adb: No such file or directory
myname-no-MacBook-Pro:desktop myname$

KindleRooteado said:
Still doesn't work... I mounted system with ES file explorer and after I tried again to do the backup:
Code:
Last login: Sat Sep 6 09:24:20 on console
myname-no-MacBook-Pro:~ myname$ cd desktop
myname-no-MacBook-Pro:desktop myname$ adb pull /dev/block/mmcblk0boot0
failed to copy '/dev/block/mmcblk0boot0' to './mmcblk0boot0': Permission denied
myname-no-MacBook-Pro:desktop myname$ ./adb pull /dev/block/mmcblk0boot0
-bash: ./adb: No such file or directory
myname-no-MacBook-Pro:desktop myname$ adb remount
remount failed: Operation not permitted
myname-no-MacBook-Pro:desktop myname$ ./adb remount
-bash: ./adb: No such file or directory
myname-no-MacBook-Pro:desktop myname$
Click to expand...
Click to collapse
Ok,try running "adb root" and then issue the commands

I think where can be my mistake. When I installed the android sdk adb I never got the list of my devices, my KF2 didn't appear, but i didn't think that was so important...
Then i thought that i didn't need to do anything else to connect the Kindle to my computer with USB debugging enabled, sorry. Now I'm trying to do USB debugging enabled following this guide: https://developer.amazon.com/appsan...etting-up-your-kindle-fire-tablet-for-testing
And again I'm stuck. I don't understand the meaning of this errors, any idea? I'm working with mac OSX, no Windows PC available in 10.424 Km...
Code:
myname-no-MacBook-Pro:SDK tools myname$
myname-no-MacBook-Pro:SDK tools myname$ ./android update adb
Unable to access jarfile /Users/myname/desktop/SDK tools/archquery.jar
Unable to access jarfile /Users/myname/desktop/SDK tools/archquery.jar
Exception in thread "Thread-1" java.lang.NoClassDefFoundError: com/android/utils/ILogger
Caused by: java.lang.ClassNotFoundException: com.android.utils.ILogger
at java.net.URLClassLoader$1.run(URLClassLoader.java:202)
at java.security.AccessController.doPrivileged(Native Method)
at java.net.URLClassLoader.findClass(URLClassLoader.java:190)
at java.lang.ClassLoader.loadClass(ClassLoader.java:306)
at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:301)
at java.lang.ClassLoader.loadClass(ClassLoader.java:247)

SafinWasi said:
Ok,try running "adb root" and then issue the commands
Click to expand...
Click to collapse
I'm a really pain, sorry.
I guest i cannot run any adb command until l fix the USB debugging enabled.
Code:
myname-no-MacBook-Pro:desktop myname$ adb root
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
adbd cannot run as root in production builds

I think i finally enabled USB debugging, but I'm not sure. I have made ​​my device appears in the list, but the other .adb commands are not working still. The fact that my device appears in the list is a good sign or not?
Code:
myname-no-MacBook-Pro:desktop myname$ adb devices
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
D026A0A02494022P device
myname-no-MacBook-Pro:desktop myname$ adb pull /dev/block/mmcblk0boot0
failed to copy '/dev/block/mmcblk0boot0' to './mmcblk0boot0': Permission denied
myname-no-MacBook-Pro:desktop myname$ adb remount
remount failed: Operation not permitted
myname-no-MacBook-Pro:desktop myname$ adb root
adbd cannot run as root in production builds
myname-no-MacBook-Pro:desktop myname$

KindleRooteado said:
I think i finally enabled USB debugging, but I'm not sure. I have made ​​my device appears in the list, but the other .adb commands are not working still. The fact that my device appears in the list is a good sign or not?
Code:
myname-no-MacBook-Pro:desktop myname$ adb devices
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
D026A0A02494022Pdevice
myname-no-MacBook-Pro:desktop myname$ adb pull /dev/block/mmcblk0boot0
failed to copy '/dev/block/mmcblk0boot0' to './mmcblk0boot0': Permission denied
myname-no-MacBook-Pro:desktop myname$ adb remount
remount failed: Operation not permitted
myname-no-MacBook-Pro:desktop myname$ adb root
adbd cannot run as root in production builds
myname-no-MacBook-Pro:desktop myname$
Click to expand...
Click to collapse
Its definitely a good sign. I'll keep digging.
Sent from my device running CyanogenMod 11
---------- Post added at 08:43 PM ---------- Previous post was at 08:39 PM ----------
OK,found something. Try this:
Code:
adb shell su -c "dd if=/dev/block/mmcblk0boot0 of=/sdcard/boot0block.IMG"
adb pull /Edvard/boot0block.IMG
Try this with other commands as well. And if it prompts SuperSU,say grant.
Sent from my device running CyanogenMod 11

SafinWasi said:
Its definitely a good sign. I'll keep digging.
Sent from my device running CyanogenMod 11
---------- Post added at 08:43 PM ---------- Previous post was at 08:39 PM ----------
OK,found something. Try this:
Code:
adb shell su -c "dd if=/dev/block/mmcblk0boot0 of=/sdcard/boot0block.IMG"
adb pull /Edvard/boot0block.IMG
Try this with other commands as well. And if it prompts SuperSU,say grant.
Sent from my device running CyanogenMod 11
Click to expand...
Click to collapse
Thank you very much again. The first command works, it asked me to grant SuperSu and i did, but nothing else.
Is Edvard/boot0block.IMG a file i have to download?
Code:
myname-no-MacBook-Pro:~ myname$ cd desktop
myname-no-MacBook-Pro:desktop myname$ adb shell su -c "dd if=/dev/block/mmcblk0boot0 of=/sdcard/boot0block.IMG"
4096+0 records in
4096+0 records out
2097152 bytes transferred in 0.459 secs (4568958 bytes/sec)
myname-no-MacBook-Pro:desktop myname$ adb pull /Edvard/boot0block.IMG
[B]remote object '/Edvard/boot0block.IMG' does not exist
[/B]myname-no-MacBook-Pro:desktop myname$ adb pull /dev/block/mmcblk0boot0
failed to copy '/dev/block/mmcblk0boot0' to './mmcblk0boot0': Permission denied
myname-no-MacBook-Pro:desktop myname$
Why it's so complicated?

KindleRooteado said:
Thank you very much again. The first command works, it asked me to grant SuperSu and i did, but nothing else.
Is Edvard/boot0block.IMG a file i have to download?
Code:
myname-no-MacBook-Pro:~ myname$ cd desktop
myname-no-MacBook-Pro:desktop myname$ adb shell su -c "dd if=/dev/block/mmcblk0boot0 of=/sdcard/boot0block.IMG"
4096+0 records in
4096+0 records out
2097152 bytes transferred in 0.459 secs (4568958 bytes/sec)
myname-no-MacBook-Pro:desktop myname$ adb pull /Edvard/boot0block.IMG
[B]remote object '/Edvard/boot0block.IMG' does not exist
[/B]myname-no-MacBook-Pro:desktop myname$ adb pull /dev/block/mmcblk0boot0
failed to copy '/dev/block/mmcblk0boot0' to './mmcblk0boot0': Permission denied
myname-no-MacBook-Pro:desktop myname$
Why it's so complicated?
Click to expand...
Click to collapse
Lol,it should be:
adb pull /sdcard/boot0block.img

SafinWasi said:
Lol,it should be:
adb pull /sdcard/boot0block.img
Click to expand...
Click to collapse
Lol, I am about to give up.
The last command that you give me worked but again I couldn't make backup, cause i got the same error.
Silvia-Kozakura-no-MacBook-Pro:~ silviakozakura$ adb pull /sdcard/boot0block.img6366 KB/s (2097152 bytes in 0.321s)
So, i had the brilliant idea to skip that step and go ahead to install the stack and then to flash bootloader.
And now I'm stuck at the second command, my computer is sending 'boot' for 40 minutes, not sure if this is normal, but i suppose it is not...
I'm going to sleep, tomorrow i will see what to do or not. Thanks for your time.
Silvia-Kozakura-no-MacBook-Pro:desktop silviakozakura$ adb pull /sdcard/boot0block.img
6245 KB/s (2097152 bytes in 0.327s)
Silvia-Kozakura-no-MacBook-Pro:desktop silviakozakura$ adb pull /dev/block/mmcblk0boot0
failed to copy '/dev/block/mmcblk0boot0' to './mmcblk0boot0': Permission denied
Silvia-Kozakura-no-MacBook-Pro:desktop silviakozakura$ adb push stack /sdcard/
204 KB/s (4096 bytes in 0.019s)
Silvia-Kozakura-no-MacBook-Pro:desktop silviakozakura$ adb shell su -c "dd if=/sdcard/stack of=/dev/block/platform/omap/omap_hsmmc.1/by-name/system bs=6519488 seek=1"
0+1 records in
0+1 records out
4096 bytes transferred in 0.002 secs (2048000 bytes/sec)
Silvia-Kozakura-no-MacBook-Pro:desktop silviakozakura$ fastboot -i 0x1949 flash bootloader otter2-u-boot-prod-10.2.4.bin
sending 'bootloader' (227 KB)...
OKAY [ 0.129s]
writing 'bootloader'...
OKAY [ 0.057s]
finished. total time: 0.186s
Silvia-Kozakura-no-MacBook-Pro:desktop silviakozakura$ fastboot -i 0x1949 flash boot otter2-freedom-boot-10.4.6.img
sending 'boot' (8153 KB)...

KindleRooteado said:
Lol, I am about to give up.
The last command that you give me worked but again I couldn't make backup, cause i got the same error.
Silvia-Kozakura-no-MacBook-Pro:~ silviakozakura$ adb pull /sdcard/boot0block.img6366 KB/s (2097152 bytes in 0.321s)
So, i had the brilliant idea to skip that step and go ahead to install the stack and then to flash bootloader.
And now I'm stuck at the second command, my computer is sending 'boot' for 40 minutes, not sure if this is normal, but i suppose it is not...
I'm going to sleep, tomorrow i will see what to do or not. Thanks for your time.
Silvia-Kozakura-no-MacBook-Pro:desktop silviakozakura$ adb pull /sdcard/boot0block.img
6245 KB/s (2097152 bytes in 0.327s)
Silvia-Kozakura-no-MacBook-Pro:desktop silviakozakura$ adb pull /dev/block/mmcblk0boot0
failed to copy '/dev/block/mmcblk0boot0' to './mmcblk0boot0': Permission denied
Silvia-Kozakura-no-MacBook-Pro:desktop silviakozakura$ adb push stack /sdcard/
204 KB/s (4096 bytes in 0.019s)
Silvia-Kozakura-no-MacBook-Pro:desktop silviakozakura$ adb shell su -c "dd if=/sdcard/stack of=/dev/block/platform/omap/omap_hsmmc.1/by-name/system bs=6519488 seek=1"
0+1 records in
0+1 records out
4096 bytes transferred in 0.002 secs (2048000 bytes/sec)
Silvia-Kozakura-no-MacBook-Pro:desktop silviakozakura$ fastboot -i 0x1949 flash bootloader otter2-u-boot-prod-10.2.4.bin
sending 'bootloader' (227 KB)...
OKAY [ 0.129s]
writing 'bootloader'...
OKAY [ 0.057s]
finished. total time: 0.186s
Silvia-Kozakura-no-MacBook-Pro:desktop silviakozakura$ fastboot -i 0x1949 flash boot otter2-freedom-boot-10.4.6.img
sending 'boot' (8153 KB)...
Click to expand...
Click to collapse
What the… it should not ta take more than 10 seconds
Sent from my device running CyanogenMod 11

Hi, i was trying to to restore my kindle to 10.2.3 firmware cause i was told that it was the only way to flash a new rom and something didn't work.
Now shows this red triangle all the time. I cannot reboot, restore and my computer doesn't recognizes it.
Please help me, what i can do.
(It can enter to fastboot)

Having trouble flashing TWRP to HTC M8

Hello i hope im posting this in the right place.
First let me explain that i am very much NOOB when it comes to Android rooting, I have always been an IOS user untill recently
when i seen the light and decided to move to Android.
So as for the problem, I have unlocked the Bootloader ( was simple enough), but now when i try flashing TWRP the phone will try to boot, then all that happens is a battery symbol starts falshing on screen and the phone is completely unresponsive. i assume this is "soft bricked", i am able to recover by unplugging the usb and holding the power buttons. I have tried many different TWRP versions
all with the same outcome.
Im not sure what info you will need in order to help but i will start with * Running Android 5.0.2
* Phone was originally O2uk, and now unlocked on 3 ireland
* Sense Version 6.0
any help would be much appreciated, thanks in advanced
Mick

The question is more how you flashed it ?
What exact command did you use ?

Ok so what i did was entered the command- "adb devices" the device is connected
next was "adb reboot bootloader" and my phone entered fastboot menu
finally was " fastboot flash recovery (filename)"
then on the phone selected "HBOOT" then "RECOVERY"
Mick

Oke that seems good, just making sure you didn't flash it to the boot partition !
Can you post another command output ?
Fastboot getvar all
Then post the full list except the serial and imei

bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: [email protected]
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.11.206.10
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: xxxxxxxxxxxxxxxxx
(bootloader) imei: xxxxxxxxxxxxxxxxx
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8ql_ul
(bootloader) platform: hTCBmsm8939
(bootloader) modelid: 0PKV10000
(bootloader) cidnum: O2___001
(bootloader) battery-status: good
(bootloader) battery-voltage: 0mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: 4107a7cf
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
(bootloader) mfg-name: 0001
all: Done!

Any ideas how i can fix this problem or is it something im doing wrong?

Mikey899 said:
Any ideas how i can fix this problem or is it something im doing wrong?
Click to expand...
Click to collapse
Yup definitely going the wrong route as you have the M8s and NOT the M8 !!!
http://forum.xda-developers.com/showthread.php?t=3114245
Have a read there mate
Roms for the M8 also don't work on the M8s, actually it's pretty unsupported. Also make sure to create a full stock backup once you flashed the correct TWRP for the M8s so you can go back to stock easily !!!

Now that was very NOOB of me, thanks man, will have a read and let you know how i get on

ok so i have had a good read and im still unclear on what method i need to use to flash the TWRP for the m8s

Mikey899 said:
ok so i have had a good read and im still unclear on what method i need to use to flash the TWRP for the m8s
Click to expand...
Click to collapse
Just fastboot flash it, you only need the correct TWRP (the one from that thread, it's modified to work with the M8s)
If that doesn't work you have to use the htc_fastboot files from that thread and fastboot flash it again

yes i was thinking that and i tried it, but rather than load it onto the device as it usually would, this is what i got
"adb flash recovery twrp-recovery-2.8.6.0-m8s-qlul.img"
Android Debug Bridge version 1.0.31
-a - directs adb to listen on all interfaces for a connection
-d - directs command to the only connected USB device
returns an error if more than one USB device is present.
-e - directs command to the only running emulator.
returns an error if more than one emulator is running.
-s <specific device> - directs command to the device or emulator with the given
serial number or qualifier. Overrides ANDROID_SERIAL
environment variable.
-p <product name or path> - simple product name like 'sooner', or
a relative/absolute path to a product
out directory like 'out/target/product/sooner'.
If -p is not specified, the ANDROID_PRODUCT_OUT
environment variable is used, which must
be an absolute path.
-H - Name of adb server host (default: localhost)
-P - Port of adb server (default: 5037)
devices [-l] - list all connected devices
('-l' will also list device qualifiers)
connect <host>[:<port>] - connect to a device via TCP/IP
Port 5555 is used by default if no port number is specified.
disconnect [<host>[:<port>]] - disconnect from a TCP/IP device.
Port 5555 is used by default if no port number is specified.
Using this command with no additional arguments
will disconnect from all connected TCP/IP devices.
device commands:
adb push [-p] <local> <remote>
- copy file/dir to device
('-p' to display the transfer progress)
adb pull [-p] [-a] <remote> [<local>]
- copy file/dir from device
('-p' to display the transfer progress)
('-a' means copy timestamp and mode)
adb sync [ <directory> ] - copy host->device only if changed
(-l means list but don't copy)
(see 'adb help all')
adb shell - run remote shell interactively
adb shell <command> - run remote shell command
adb emu <command> - run emulator console command
adb logcat [ <filter-spec> ] - View device log
adb forward --list - list all forward socket connections.
the format is a list of lines with the following format:
<serial> " " <local> " " <remote> "\n"
adb forward <local> <remote> - forward socket connections
forward specs are one of:
tcp:<port>
localabstract:<unix domain socket name>
localreserved:<unix domain socket name>
localfilesystem:<unix domain socket name>
dev:<character device name>
jdwp:<process pid> (remote only)
adb forward --no-rebind <local> <remote>
- same as 'adb forward <local> <remote>' but fails
if <local> is already forwarded
adb forward --remove <local> - remove a specific forward socket connection
adb forward --remove-all - remove all forward socket connections
adb jdwp - list PIDs of processes hosting a JDWP transport
adb install [-l] [-r] [-d] [-s] [--algo <algorithm name> --key <hex-encoded key> --iv <hex-encoded iv>] <file>
- push this package file to the device and install it
('-l' means forward-lock the app)
('-r' means reinstall the app, keeping its data)
('-d' means allow version code downgrade)
('-s' means install on SD card instead of internal storage)
('--algo', '--key', and '--iv' mean the file is encrypted already)
adb uninstall [-k] <package> - remove this app package from the device
('-k' means keep the data and cache directories)
adb bugreport - return all information from the device
that should be included in a bug report.
adb backup [-f <file>] [-apk|-noapk] [-obb|-noobb] [-shared|-noshared] [-all] [-system|-nosystem] [<packages...>]
- write an archive of the device's data to <file>.
If no -f option is supplied then the data is written
to "backup.ab" in the current directory.
(-apk|-noapk enable/disable backup of the .apks themselves
in the archive; the default is noapk.)
(-obb|-noobb enable/disable backup of any installed apk expansion
(aka .obb) files associated with each application; the default
is noobb.)
(-shared|-noshared enable/disable backup of the device's
shared storage / SD card contents; the default is noshared.)
(-all means to back up all installed applications)
(-system|-nosystem toggles whether -all automatically includes
system applications; the default is to include system apps)
(<packages...> is the list of applications to be backed up. If
the -all or -shared flags are passed, then the package
list is optional. Applications explicitly given on the
command line will be included even if -nosystem would
ordinarily cause them to be omitted.)
adb restore <file> - restore device contents from the <file> backup archive
adb help - show this help message
adb version - show version num
scripting:
adb wait-for-device - block until device is online
adb start-server - ensure that there is a server running
adb kill-server - kill the server if it is running
adb get-state - prints: offline | bootloader | device
adb get-serialno - prints: <serial-number>
adb get-devpath - prints: <device-path>
adb status-window - continuously print device status for a specified device
adb remount - remounts the /system partition on the device read-write
adb reboot [bootloader|recovery] - reboots the device, optionally into the bootloader or recovery program
adb reboot-bootloader - reboots the device into the bootloader
adb root - restarts the adbd daemon with root permissions
adb usb - restarts the adbd daemon listening on USB
adb tcpip <port> - restarts the adbd daemon listening on TCP on the specified port
networking:
adb ppp <tty> [parameters] - Run PPP over USB.
Note: you should not automatically start a PPP connection.
<tty> refers to the tty for PPP stream. Eg. dev:/dev/omap_csmi_tty1
[parameters] - Eg. defaultroute debug dump local notty usepeerdns
adb sync notes: adb sync [ <directory> ]
<localdir> can be interpreted in several ways:
- If <directory> is not specified, both /system and /data partitions will be updated.
- If it is "system" or "data", only the corresponding partition
is updated.
environmental variables:
ADB_TRACE - Print debug information. A comma separated list of the following values
1 or all, adb, sockets, packets, rwx, usb, sync, sysdeps, transport, jdwp
ANDROID_SERIAL - The serial number to connect to. -s takes priority over this if given.
ANDROID_LOG_TAGS - When used with the logcat option, only these debug tags are printed.

i also tried the htc_fastboot.exe and when i run it i get "AdbWinApi.dll missing"

You don't "run" the fastboot file. And "adb flash recovery" can't work either
The command =
Fastboot flash recovery recovery filename
And the phone is in the bootloader -fastboot usb mode
You put the TWRP in the fastboot folder and then open a command prompt there. Then type the command

Thanks for all your help man, i have managed to root thanks to you. sorry for the inconvenience
Mick

Mikey899 said:
Thanks for all your help man, i have managed to root thanks to you. sorry for the inconvenience
Mick
Click to expand...
Click to collapse
Cool, no worries.

{ROOT} {100% Working} Vzw Desire 526 Perm Root {Unlocked Boot-Loader Required}

How To Get Permanent Root
This is a workaround until I can compile a Bootable Kernel
First of all say thanks to @Captain_Throwback !!
He was the original creator of the TWRP Recovery for the Desire 626s.
I have taken his TWRP recovery for the 626s, unpacked it and ported in some of the Desire 526 recovery image.
Kinda a cracked up way of doing this but hey ( It Works)
Step #1
Unlock Your Boot-Loader !!! (currently accomplished with a Java Card / HTC Service Tool)
Even with the card you could run into trouble with unlocking the boot-loader.
There is no switch to Enable OEM Unlock available in the Developer Options.
Here is a work-around for that.
Step #1-A
Open up terminal shell on a computer and pull the frp image from the device. (Temp Root Required)
Code:
dd if=/dev/block/bootdevice/by-name/frp of=/sdcard/frp.img
Terminal Output
[email protected]_a13wlpp:/ #dd if=/dev/block/bootdevice/by-name/frp of=/sdcard/frp.img <
1024+0 records in
1024+0 records out
524288 bytes transferred in 0.364 secs (1440351 bytes/sec)
[email protected]_a13wlpp:/ #
Pull the frp.img to the computer.
If you are still in adb shell.
Code:
exit
exit
Then from the normal command line
Code:
adb pull /sdcard/frp.img
Terminal Output
f=/dev/block/bootdevice/by-name/frp of=/sdcard/frp.img <
1024+0 records in
1024+0 records out
524288 bytes transferred in 0.364 secs (1440351 bytes/sec)
[email protected]_a13wlpp:/ # exit
[email protected]_a13wlpp:/ $ exit
[email protected]:~$ adb pull /sdcard/frp.img
2758 KB/s (524288 bytes in 0.185s)
[email protected]:~$
Now open the frp.img file in a hex editor. Like HXD in windows.
Go to the last line of the file.
Change the very last 00 to 01 and save the file.
Reference the screen shots below.
Factory FRP
{
"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"
}
Patched FRP
Flash the patched frp.img to the device.
Back to the terminal.
Code:
adb push frp.img /sdcard/frp.img
Code:
adb shell
su
dd if=/sdcard/frp.img of=/dev/block/bootdevice/by-name/frp
If you have completed this now your clip can unlock the boot-loader
In case your wondering this will also work on a boot loader locked device. It will get you as far as being able to get a unlock token from fastboot using Fastboot oem get_identifier_token WITH THE DEVICE IN DOWNLOAD MODE
Unfortunatly HTC-DEV still will not give you the UNLOCK TOKEN yet. The pg2fs partition needs an edit then htc dev will generate a good code. Problem is without clip you cannot modify the pg2fs image. Allthough I am working on it.
STEP #2 ( Get Perm Root !! )
Download the Patched TWRP and SuperSu
The 2 files are attached to the thread. Unzip the TWRP-No-Touch.img.zip Do not unzip the Super.zip.
Copy the super.zip to the device sdcard. Use file explorer or terminal.
Code:
adb push super.zip /sdcard/super.zip
Flash the TWRP Recovery to the device.
reboot to download mode
Code:
adb reboot download
Flash the recovery
Code:
fastboot flash recovery Twrp-526-NO-TOUCH.img
Boot into TWRP Recovery
Code:
fastboot boot recovery
DON'T PANIC !! Yes your right......The touch screen is not working!!!
I need to compile a custom kernel to get TWRP working Right.
I have compiled the kernel but it isn't booting right yet. That's why I figured out this work around for now.
So Now What ???
No worries....Even though we can't access the TWRP commands from the touch screen LETS NOT FORGET.........
We can use the command line :highfive:
Open up terminal on your computer.
If it's not already open.
Go into the shell.
Code:
adb shell
No need to type su cause in case you didn't notice we are already ROOT. "#"
So to install SuperSu (or any other zip package) we do this.
#1 Mount the system partition.
Code:
mount -o rw -t ext4 /dev/block/mmcblk0p62 /system
#2 Tell TWRP what we want it to do one stap at a time
Set device to boot into recovery upon reboot.
Code:
echo 'boot-recovery ' > /cache/recovery/command
Tell TWRP to install SuperSu when it boots.
Code:
echo '--update_package=/sdcard/super.zip' >> /cache/recovery/command
Reboot the recovery to install the SuperSu.
Code:
reboot recovery
Now you will see TWRP boot back up and when it boots up it will install the zip package.
Congratulations you are now one of the first peoples to have a fully rooted Verizon Desire 526. :laugh::silly:
Lets get busy boys !!!! We need to get this boot loader unlocked for the rest of the community.
It's all about the pg2fs partition. If we can find a way to write to it with s-on and boot loader locked then we can unlock all boot-loaders

Glad to see sum positive progress in the right direction....

BigCountry907 ,
Since the MarshaMallow update gives us the developer options OEM unlock switch, shouldn't we just update to it first, to get the bootloader unlock?

OEM Update
You won't find the option to turn on OEM in the device.
You can enable it! Here's how:
Go to the Google Play Store.
Search secret codes revealer.
Search codes
Look for 759
Click launch code
Confirm launch
Under oem click on.
Congrats. You've just enabled oem on your desire 526!
Happy hunting.
BigCountry907 said:
How To Get Permanent Root
This is a workaround until I can compile a Bootable Kernel
First of all say thanks to @Captain_Throwback !!
He was the original creator of the TWRP Recovery for the Desire 626s.
I have taken his TWRP recovery for the 626s, unpacked it and ported in some of the Desire 526 recovery image.
Kinda a cracked up way of doing this but hey ( It Works)
Step #1
Unlock Your Boot-Loader !!! (currently accomplished with a Java Card / HTC Service Tool)
Even with the card you could run into trouble with unlocking the boot-loader.
There is no switch to Enable OEM Unlock available in the Developer Options.
Here is a work-around for that.
Step #1-A
Open up terminal shell on a computer and pull the frp image from the device. (Temp Root Required)
Code:
dd if=/dev/block/bootdevice/by-name/frp of=/sdcard/frp.img
Terminal Output
[email protected]_a13wlpp:/ #dd if=/dev/block/bootdevice/by-name/frp of=/sdcard/frp.img <
1024+0 records in
1024+0 records out
524288 bytes transferred in 0.364 secs (1440351 bytes/sec)
[email protected]_a13wlpp:/ #
Pull the frp.img to the computer.
If you are still in adb shell.
Code:
exit
exit
Then from the normal command line
Code:
adb pull /sdcard/frp.img
Terminal Output
f=/dev/block/bootdevice/by-name/frp of=/sdcard/frp.img <
1024+0 records in
1024+0 records out
524288 bytes transferred in 0.364 secs (1440351 bytes/sec)
[email protected]_a13wlpp:/ # exit
[email protected]_a13wlpp:/ $ exit
[email protected]:~$ adb pull /sdcard/frp.img
2758 KB/s (524288 bytes in 0.185s)
[email protected]:~$
Now open the frp.img file in a hex editor. Like HXD in windows.
Go to the last line of the file.
Change the very last 00 to 01 and save the file.
Reference the screen shots below.
Factory FRP
Patched FRP
Flash the patched frp.img to the device.
Back to the terminal.
Code:
adb push frp.img /sdcard/frp.img
Code:
adb shell
su
dd if=/sdcard/frp.img of=/dev/block/bootdevice/by-name/frp
If you have completed this now your clip can unlock the boot-loader
In case your wondering this will also work on a boot loader locked device. It will get you as far as being able to get a unlock token from fastboot using Fastboot oem get_identifier_token WITH THE DEVICE IN DOWNLOAD MODE
Unfortunatly HTC-DEV still will not give you the UNLOCK TOKEN yet. The pg2fs partition needs an edit then htc dev will generate a good code. Problem is without clip you cannot modify the pg2fs image. Allthough I am working on it.
STEP #2 ( Get Perm Root !! )
Download the Patched TWRP and SuperSu
The 2 files are attached to the thread. Unzip the TWRP-No-Touch.img.zip Do not unzip the Super.zip.
Copy the super.zip to the device sdcard. Use file explorer or terminal.
Code:
adb push super.zip /sdcard/super.zip
Flash the TWRP Recovery to the device.
reboot to download mode
Code:
adb reboot download
Flash the recovery
Code:
fastboot flash recovery Twrp-526-NO-TOUCH.img
Boot into TWRP Recovery
Code:
fastboot boot recovery
DON'T PANIC !! Yes your right......The touch screen is not working!!!
I need to compile a custom kernel to get TWRP working Right.
I have compiled the kernel but it isn't booting right yet. That's why I figured out this work around for now.
So Now What ???
No worries....Even though we can't access the TWRP commands from the touch screen LETS NOT FORGET.........
We can use the command line :highfive:
Open up terminal on your computer.
If it's not already open.
Go into the shell.
Code:
adb shell
No need to type su cause in case you didn't notice we are already ROOT. "#"
So to install SuperSu (or any other zip package) we do this.
#1 Mount the system partition.
Code:
mount -o rw -t ext4 /dev/block/mmcblk0p62 /system
#2 Tell TWRP what we want it to do one stap at a time
Set device to boot into recovery upon reboot.
Code:
echo 'boot-recovery ' > /cache/recovery/command
Tell TWRP to install SuperSu when it boots.
Code:
echo '--update_package=/sdcard/super.zip' >> /cache/recovery/command
Reboot the recovery to install the SuperSu.
Code:
reboot recovery
Now you will see TWRP boot back up and when it boots up it will install the zip package.
Congratulations you are now one of the first peoples to have a fully rooted Verizon Desire 526. :laugh::silly:
Lets get busy boys !!!! We need to get this boot loader unlocked for the rest of the community.
It's all about the pg2fs partition. If we can find a way to write to it with s-on and boot loader locked then we can unlock all boot-loaders
Click to expand...
Click to collapse

Good to know about the 759 code webag.youtag.
But without buying the clip device we are still stuck.
So hopefully BigCountry907 can find a way to unlock the bootloader and root without the clip.
Sidenote: I tried changing my PRL but couldn't get the changes to stick. I tried DFS and QPST. Am I missing something?

@webag.youtag
I installed the mentioned app and used the code.
It shows in the app that the oem is turned on.
But It isn't setting the last byte of the FRP to 01 so ultimatly it will not work.
I tested and still get.
[email protected]:~$ fastboot oem get_identifier_token
...
(bootloader) [KillSwitch] : /dev/block/bootdevice/by-name/frp
(bootloader) [KillSwitch] Last Byte is 0X00, disable unlock
(bootloader) [KillSwitch] oem unlock Turn Off!
OKAY [ 0.082s]
finished. total time: 0.082s
[email protected]:~$
The app lacks permissions to write to the frp partition.
Anyone working on unlocking the boot-loader needs to use the method I posted previously.
And also note: If you reboot the phone then you need to flash the frp partition again.
During re-boot the bit gets set back to 00.
So in a nutshell.
Edit your frp. Make 00 = 01.
Then dd flash the frp.
Then adb reboot download.
Then fastboot oem get_identifier_token.
Problem is there still is a change required in the pg2fs partition / TO Avoid the CID Not Allowed Error
@supermaxkato
Not sure about the prl.
But I have noticed that the security system is tricky.
It will show you in adb shell that you have written the changes to the partition successfully.
But due to the read only protection the partition never really gets written.
Basically instead of giving an error it is writing to a NULL device successfully.

I was looking around and saw a post! (Rare I know)
Have you tried hboot instead of fastboot?also, I have no computer (sad). I am able to get temp root with "kingroot-4.8.2" I am able to use hex edit to change frp from 00 to 01. Is there a way to get identifier token without a PC? Maybe in configuration files or prop files?
BigCountry907 said:
@webag.youtag
I installed the mentioned app and used the code.
It shows in the app that the oem is turned on.
But It isn't setting the last byte of the FRP to 01 so ultimatly it will not work.
I tested and still get.
[email protected]:~$ fastboot oem get_identifier_token
...
(bootloader) [KillSwitch] : /dev/block/bootdevice/by-name/frp
(bootloader) [KillSwitch] Last Byte is 0X00, disable unlock
(bootloader) [KillSwitch] oem unlock Turn Off!
OKAY [ 0.082s]
finished. total time: 0.082s
[email protected]:~$
The app lacks permissions to write to the frp partition.
Anyone working on unlocking the boot-loader needs to use the method I posted previously.
And also note: If you reboot the phone then you need to flash the frp partition again.
During re-boot the bit gets set back to 00.
So in a nutshell.
Edit your frp. Make 00 = 01.
Then dd flash the frp.
Then adb reboot download.
Then fastboot oem get_identifier_token.
Problem is there still is a change required in the pg2fs partition / TO Avoid the CID Not Allowed Error
@supermaxkato
Not sure about the prl.
But I have noticed that the security system is tricky.
It will show you in adb shell that you have written the changes to the partition successfully.
But due to the read only protection the partition never really gets written.
Basically instead of giving an error it is writing to a NULL device successfully.
Click to expand...
Click to collapse

Can you please upload your unlocked boot loader bigcountry907?

Any more progress on this, gentlemen?

When I follow the OP and get to the step:
"fastboot flash recovery Twrp-526-NO-TOUCH.img"
I receive the following error:
FAILED (remote: 9: SD_SECURITY_FAIL recovery and bootloader isn't BL_UNLOCK)
finished. total time: 2.762s
Steps taken:
-frp.img (Pulled from the device, edited & reflashed back with dd command, adb shell reports successful)
-pushed super.zip to device
-rebooted using fastboot to download mode
-attempted to flash TWRP & get the fail with the same error multiple times
Any suggestions or clues? I've attempted this several times, following the OP step by step.
Thanks for the help

@rfunderburk39
You have to unlock the BOOTLOADER first.
Currently I can only unlock it with the xtc-2 clip.
But I'm working on it.
Surprisingly my desire 530 was able to be s-off using TWRP recovery.
If i can somehow capture the commands passed from the xtc-2 clip to the twrp recovery we can replicate it.
Other than that were looking at cooking a qfil / qpst flashable rom.
Not easy.
does anyone know how to log all commands sent to TWRP?

BigCountry907, is the desire 530 you were able to root with twrp the verizon version? If so, did you have to unlock the bootloader first? Because I don't see it on htcdev.

@BigCountry907 I misunderstood the OP, I thought the frp.img edit was a work around of the Java Card.
I will look into the logging of the the TWRP commands. Let me know if I can help out in other ways.

@rfunderburk39
It gets you one step closer but still at the end it fails.
Verizon implements some major security.
I could really use some help.
I got alot together. The entire qcom msm8909 source + manuals you name it.
I was amazed today when i unlocked a desire 530 with the xtc-2 clip and it used @Captain_Throwback twrp to s-off the device.
The beauty of this is it proves S-Off is possible through twrp recovery.
It was my belief that the recovery did not have high enough permissions to write to the radio and get s-off.
Apparently if you know the right commands in the TWRP #shell it's possible.
So how deep into linux / android do you go?
My next best attempt is to generate a service rom using QPST to flash in EDL mode.
Ever make a partition.xml file???
Thats aboot where im at.
oh yea and JTAG TOO.

BigCountry907 said:
@rfunderburk39
It gets you one step closer but still at the end it fails.
Verizon implements some major security.
I could really use some help.
I got alot together. The entire qcom msm8909 source + manuals you name it.
I was amazed today when i unlocked a desire 530 with the xtc-2 clip and it used @Captain_Throwback twrp to s-off the device.
The beauty of this is it proves S-Off is possible through twrp recovery.
It was my belief that the recovery did not have high enough permissions to write to the radio and get s-off.
Apparently if you know the right commands in the TWRP #shell it's possible.
So how deep into linux / android do you go?
My next best attempt is to generate a service rom using QPST to flash in EDL mode.
Ever make a partition.xml file???
Thats aboot where im at.
oh yea and JTAG TOO.
Click to expand...
Click to collapse
Tommorrow my time will be limited during the day, but I can look into "qcom msm8909 source + manuals" & the ability to log TWRP commands and see what I can find.
Interesting about the 530, I was not aware that was possible.
I've used linux for about 20 years, and would consider my knowledge to be good, with the ability to usually get to source of a problem and/or find a solution slash work around.
I've never created a partition.xml, but would be happy to look into it.
I do have quite a bit of past JTAG experience but that was using a serial port not USB, which I assume you are referencing.

@supermaxkato
No my Desire 530 is Metro-Pcs.
I took one of the verizon 526 and activated it then used the phone number to port to Metro Pcs.
With the port it cost $70 for the Desire 530 + 1 month of unlimited service. Essentially the Desire 530 was free.
Any Verizon HTC most likely will have the same security scheme.
@rfunderburk39
This is good news. I would be grateful to have help on this.
It is difficult to know what kind of experience people have some don't even know how to use adb.
I will start another thread with all the information I know so far.
And I have the MSM8909 source code. Not just the kernel but the "Qualcomm Chipcode" Board Support Package.
And many qcom manuals.
This should be very helpful to us.
I will name the new thread "{WIP} {ROM} MSM8909 Service Rom From Source / QPST Root + Unlock + Unbrick"
I will post all current information there.

Something potentially worth trying:
-Grab the Settings.apk (and .odex) from the 526+ or 626, just make sure its the same version of android.
-Push those to device
-adb shell
-su
-mount -o rw,remount,rw /system
-exit
-exit
-adb push Settings.apk /system/priv-app/Settings/
-adb push Settings.odex /system/priv-app/Settings/arm/
-Open >settings>developer options on the device
-check and see if the option “OEM Unlock” appears
-reboot into "download mode" and see if the settings stick.
-run fastboot oem get_identifier_token
Granted this holds the possibility of bricking the phone, but more than likely will not stick on a reboot & the Settings.apk will be replaced with the device original.

I will test on mine.
Give me an hour

Well I replaced the settings files with the settings files from the unlocked ruu for the 526.
It's a no-go the settings app crashes on boot.
This would only add the oem_unlocking option.
We can get the same result by changing the last byte 00 of the FRP.img to 01 and then in a root shell
to pull
dd if=dev/block/bootdevice/by-name/frp of=/sdcard/frp.img
to push
dd if=/sdcard/frp.img of=dev/block/bootdevice/by-name/frp
This will work to get a Unlock Token but the HTC-DEV site will reject it.
ERROR = CID Not Allowed.
If you can find a way to write the pg2fs partition I can make this work.

BigCountry907 said:
@rfunderburk39
It gets you one step closer but still at the end it fails.
Verizon implements some major security.
I could really use some help.
I got alot together. The entire qcom msm8909 source + manuals you name it.
I was amazed today when i unlocked a desire 530 with the xtc-2 clip and it used @Captain_Throwback twrp to s-off the device.
The beauty of this is it proves S-Off is possible through twrp recovery.
It was my belief that the recovery did not have high enough permissions to write to the radio and get s-off.
Apparently if you know the right commands in the TWRP #shell it's possible.
So how deep into linux / android do you go?
My next best attempt is to generate a service rom using QPST to flash in EDL mode.
Ever make a partition.xml file???
Thats aboot where im at.
oh yea and JTAG TOO.
Click to expand...
Click to collapse
BigCountry907 said:
Well I replaced the settings files with the settings files from the unlocked ruu for the 526.
It's a no-go the settings app crashes on boot.
This would only add the oem_unlocking option.
We can get the same result by changing the last byte 00 of the FRP.img to 01 and then in a root shell
to pull
dd if=dev/block/bootdevice/by-name/frp of=/sdcard/frp.img
to push
dd if=/sdcard/frp.img of=dev/block/bootdevice/by-name/frp
This will work to get a Unlock Token but the HTC-DEV site will reject it.
ERROR = CID Not Allowed.
If you can find a way to write the pg2fs partition I can make this work.
Click to expand...
Click to collapse
I didn't think it would work, just an outside chance. Hoped it may give a different token, that in turn would pass over at HTC-DEV.
Back when I had other HTC devices, I used a tool here on XDA [TOOL] HTC Easy Unlock Bootloader Tool. It doesn't appear to be maintained any longer, its based around Windows *.bat files (easy enough to edit)
https://forum.xda-developers.com/showthread.php?t=2133336
and SimpleGoldCard
https://forum.xda-developers.com/showthread.php?t=970157
SimpleGoldCard would access a site, after downloading that, you select it in the SimpleGoldCard application & it would create the image.
https://huygens.hoxnet.com/goldcard.html
I haven't had time to read through these post just yet, the method may no longer be valid. But worth a look, and I will be reading through these today to see.
Also I will see what I can find about a work-a-round of the the writing to pg2fs partition