yashsingh1/xdaforums huggingface dataset:
[General Questions and Answers] cozzie37:
[MENTION=5312578]mrmazak[/MENTION], I tried your unlock tool and I seem to have ended up with a brick after step 1. I had already done "fastboot flashing unlock" manually, but decided to use the unlock option in your tool, since it formats userdata/cache as well. Now the tablet still has the orange bootloader, but it's hanging at the "Voyager" bootsplash. So far it's been hanging for over 20 minutes, adb and fastboot don't see it, the Intel flash tool does, but I don't have anything flashable. I've also tried the reset button on the back, it was no help, and no pressing and holding of keys has helped either. I think my next step is to tag wires onto those uart pads and see if there's a serial console running.

I have found that the Yocto BSP includes patches for a 3.14.55 kernel, maybe (fingers crossed) this is the source Alco built from. I'm working on applying those patches and setting up a cross-compile toolchain now. Any chance that /proc/config.gz is available?
[General Questions and Answers] mrmazak:
I will have to flag to tool for now till I can find the reason

It runs same codes I used when I unlocked. I don't know why it did that.

- maybe unlocking a second time when already unlocked -

- maybe
[General Questions and Answers] cozzie37:
W00t! I'm in recovery!!!

What I did:

Hold volume up while plugging in USB cable

Release volume up while orange 30s bootloader warning goes by (it says volume down to reset, but it's really up)

As soon as it's gone, hold volume up again

I wiped cache and userdata in recovery, and we're up and running again! I'm wondering if your tool ran the 'fastboot reboot' before it was done wiping userdata/cache.
[General Questions and Answers] mrmazak:
maybe

but I was thinking that the format comands are the problem

either way I am releived it is not bricked

:cool:

maybe fastboot reboot recovery may be better closing command (only some devices accept that command though)

sh*t

looking at the batch i see some typos. ex "fastboot rebot" instead of "reboot" well this error was not from the tool but the original batch file
[General Questions and Answers] cozzie37:
I was thinking when I did 'fastboot flashing unlock' it automatically wiped at least the user data partition and rebooted.

Anyways, I've flashed your noforceencrypt boot.img/recovery.img, and booted your twrp long enough to find out that there's no /proc/config.gz or handy kernel .configs laying around. After reboot adb is whining that I'm not authorized, I've got no option in the dev options to clear/revoke authorizations, and I'm not getting prompted to accept. I may need your adbkeys to get debug access back.

EDIT: yeah, I'm going to need your keys, the public key alone doesn't seem to be enough. I'm getting the same error on another computer that I just installed adb/fastboot on.
[General Questions and Answers] mrmazak:
the keys I only added to stock recovery.img

and the cwm recovery dosent use keys. It has eng flag on the build.

Does the android system complain about abd? or stock recovery?

the keys are already in the github.

well here is the link

https://github.com/mrmazakblu/RCA_R...r/rca-recovery/ramdisk/data/misc/adb/adb_keys
[General Questions and Answers] cozzie37:
It's on the PC side. My laptop running Ubuntu gives

ozzie@Oberon:~$ adb shell
error: device unauthorized. Please check the confirmation dialog on your device.

And my windows desktop is something similar. There is no confirm dialog on the device. I can't get in through the OS or the modified stock recovery, and I can't boot cwm without adb access.

That looks like it's only the public key, am I missing something?

I'm currently working at this kinda from the other direction. I don't know much about Android, but I'm pretty good with hardware and Linux ;) I've soldered wires onto the serial port pads and am trying to get a logic level converter working now. My initial probing says that *something* is being transmitted over those pins. My home server is building one of the default Yocto images, I'm going to work on getting a linux kernel and/or OS booting, and the serial port should help with debugging. After that's working hopefully we can make it work in Android with root permissions, or failing that keep working on a complete linux image.
[General Questions and Answers] mrmazak:
so turning usb debugging on / off in dev options did not trigger a prompt?

not normal.

that key is same one that is loaded in the device's recovery.img at "/data/misc/adb"

on your pc in your home folder should be a " .android " folder copy that "adb_keys" there and rename it "adbkey"

that should get you adb from recovery.

you might have to trick into working by trying to start an adb sideload first.
[General Questions and Answers] cozzie37:
nope. I think hard coding your key into the recovery locked out the possibility of other keys working. I've tried all the tricks google had to offer - unplugging it and plugging back in, deleting both keys, killing and restarting the adb server, restarting usb debugging, restarting developer options, 2 different PCs running different OSs...no prompt.

Didn't work. You should have 2 keys in your .android folder, one called adbkey and the other called adbkey.pub, they're a public-private key pair. The one you've posted is the public key, adbkey.pub, which is the correct key for clients (phones/tablets), but the (adb) server needs the private key to authenticate it. The private key is much longer and starts with a "BEGIN PRIVATE KEY" header. If you want to read up more on how it works, https://en.wikipedia.org/wiki/Public-key_cryptography explains it a lot better than I ever could. And if you're concerned about security, feel free to pm it to me.

I now have a working serial connection to the tablet :) Unfortunately there's no console running on it at the moment, root or otherwise, but it does spew out the kernel log as it's running, which is as good as I ever expected to get. If anyone else ever wants to do this, the line level is 1.8V, and you need to generate it externally if you're using a cheapo logic shifter, there's nowhere easy on the board to get that 1.8V from. I haven't found a datasheet on the SoFIA-3GR, so I have no idea how high of logic level it can deal with, so I stuck with 1.8V. Probably a 1.5V battery would be enough for the purpose. Also, the RX/TX pins are labelled how they would hook up to a PC, so RX goes to RX, TX to TX.
[General Questions and Answers] mrmazak:
well if that is the case, that means nobody else has tried to use the images or recovery. Well at least not the recovery.

And to use it I need to make the pair available.

file name needs to be "adbkey"

-----BEGIN PRIVATE KEY-----
<<<<<<<<<<<<<REMOVED >>>>>>
-----END PRIVATE KEY-----
[General Questions and Answers] vampirefo:
Sounds to me, like your Linux isn't setup correctly, reboot Linux then, sudo adb shell

---------- Post added at 12:04 AM ---------- Previous post was at 12:00 AM ----------

Your key shouldn't work on any computer but your own, I have never heard of or seen a key from one computer work on another computer.
[General Questions and Answers] mrmazak:
Hello

I want to ask, who has tried either the batch file or "tool" to flash new boot and recovery images.

[MENTION=4874794]cozzie37[/MENTION] is the only one who has commented on trying it, and the directions were ot quite as written, and now there is some trouble for him, with adb.

has enyone else used and had problem , or used and had no problem, please some feed back. I need to know if i need to pull the tool or not.
[General Questions and Answers] cozzie37:
Yeah something weird's going on, I don't think its either PC though. With either the Linux or the windows PC I can access adb in recovery now, but still not in the OS. I just noticed a small cut in the USB cable I've been using, so maybe that's causing issues. I'll mess with it more tomorrow.

Unless you're using a hardware (like TPM) dependent algorithm, which most aren't, keys can usually be exchanged between machines, and I'm sure it happens all the time when servers are replaced. That's part of why its so important to keep your important private keys, like openvpn and ssh keys, well protected.
[General Questions and Answers] rpk3:
Ive donated some hashes to get the source from RCA.. Hopefully.

I can get the flashtool to work without bricking.

[MENTION=4874794]cozzie37[/MENTION] ...your expertise is welcome :o) [MENTION=5312578]mrmazak[/MENTION] ..Well work on this [MENTION=2472806]vampirefo[/MENTION] .. Thanks for ALL you do for the scene!
[General Questions and Answers] cozzie37:
It's not the USB cable, and I'm an idiot. I deleted the adbkey from recovery.img hoping that would make it accept any adb session. It does not, it makes it so it won't accept any adb session. The thing I keep coming back to is that in the Developer options, the "Revoke USB debugging authoriations" button disappeared after I flashed the recovery and boot.img.

Also, I was hoping Yocto would produce images that I could test through adb/fastboot, it does not, they would need to be flashed using the Intel flash tool. So that's no longer an easy "test until something works" option, now I need to make something work, or at least not brick, first try. It's a lot of work, it would mean I don't have to worry about my adb issues.

I have attached a bootlog from the serial port. I'm not sure what the garbage is at the very beginning, it's not valid data at any of the usual baud rates, so it may just be garbage.
[General Questions and Answers] rpk3:
Bootlog....

Im a huge fan of boot logs. It's what helps me keep my ps3 spoofed at 3.55 fw... (different topic).

Do you have a pic you can post of your serial setup? This info is priceless.

thx
[General Questions and Answers] cozzie37:
I'm using a standard USB->serial adapter, this one happens to be cp2102-based, and a generic logic level converter. As I said earlier, it's not feasible to get 1.8V off the board, so I've got an adjustable voltage regulator setup (not pictured) that can provide that, it connects to the dark green (+) and blue (-) wires. You only need the 1.8V for communication from the USB adapter to the tablet, you can listen to the tablet fine without it - and with android, there's no console running, so all you can do is listen. There are metal covers over both the SoC/memory and the wifi chip. The one on the wifi chip is epoxied, and doesn't really need to come off, unless you're super curious like me. The big one is not epoxied, and can easily be removed with a plastic putty knife, guitar pick, etc. There is a thermal pad between the SoC and the cover, mine came off cleanly with the cover, YMMV. So far I the SoC hasn't gotten that warm without the "heatsink", but I haven't been doing anything that intensive with it. Finally, there's no real point in removing the board, all that's on the back side are the connections to the external ports/buttons and ground pads.
[General Questions and Answers] mrmazak:
did you try to do another factory reset? maybe that will help reset the developer options
[General Questions and Answers] cozzie37:
I did, no dice. Do you have that option in your developer options?
[General Questions and Answers] mrmazak:
yes
[General Questions and Answers] vampirefo:
Add adb to boot.img, you should see mtp listed add a comma and then adb.

This forces adb, add in default.prop

Example

persist.sys.usb.config=mtp,adb
[General Questions and Answers] cozzie37:
How do I flash it? I can't adb to fastboot any more, can I zip it and flash thru recovery?
[General Questions and Answers] vampirefo:
TWRP can flash boot.img or yes you can zip file and flash through cwm

For zip, you have to write update script.

TWRP can flash, recovery.img, boot.img, system.img directly.
[General Questions and Answers] cozzie37:
I have the modified stock recovery flashed, I didn't think mrmazak's cwm recovery was safe to flash yet. Does update.zip need to be signed with stock recovery? Do you know of a guide for building/signing it with 6.0?

In default.prop, it was

persist.sys.usb.config=adb,mtp

Is that OK? And should there be a /adb_keys folder in boot.img? I see one of the first init.rc commands is "restorecon /adb_keys"
[General Questions and Answers] vampirefo:
You can't flash through stock recovery, I thought you were using custom recovery.

Stock recovery doesn't have adb, it doesn't have anything that you can use, if you had adb in recovery you could dd boot.img.

Your boot.img doesn't appear to be stock, adb shouldn't have been there, can you upload your default.prop

I want to see if anything else has been changed.
[General Questions and Answers] mrmazak:
not normally needed to have the keys in boot.img as they should be created when the pop up asks for permission. but have not figured why yours are not coming to pop up.

yes the stock recovery fails to flash unsigned zips. and i have been trying to fake a signed zip, but without rca's private key the signature fails
[General Questions and Answers] vampirefo:
Please tell me you didn't change below.

ro.adb.secure=1

To

ro.adb.secure=0

The removes the ability to generate an adb key.
[General Questions and Answers] cozzie37:
Right, but should the (empty) folder exist in boot.img? I wonder if adbd isn't able to create the folder to put the key in, which is causing all my issues.

Yocto builds images in a .fls format to be flashed with the Intel Flash tool. Is that a possible route?

---------- Post added at 07:45 PM ---------- Previous post was at 07:42 PM ----------

I didn't change it, I'm running mrmazak's no-force-encrypt-boot.img.

#
# ADDITIONAL_DEFAULT_PROPERTIES
#
persist.tel.hot_swap.support=false
persist.ril-daemon.disable=1
persist.radio.multisim.config=false
persist.modem.disable=true
ro.radio.noril=true
ro.adb.secure=0
libc.cpumask=0x3
ro.power_alarm.feature=false
persist.sys.power_on=false
ro.schedule.onoff=false
ro.secure=0
ro.allow.mock.location=0
ro.debuggable=1
ro.enable_boot_charger_mode=0
ro.dalvik.vm.native.bridge=libhoudini.so
ro.zygote=zygote32
dalvik.vm.image-dex2oat-Xms=64m
dalvik.vm.image-dex2oat-Xmx=64m
dalvik.vm.dex2oat-Xms=64m
dalvik.vm.dex2oat-Xmx=512m
debug.atrace.tags.enableflags=0
#
# BOOTIMAGE_BUILD_PROPERTIES
#
ro.bootimage.build.date=2016年 08月 31日 星期三 00:37:31 CST
ro.bootimage.build.date.utc=1472575051
ro.bootimage.build.fingerprint=RCA/RCT6873W42/RCT6873W42:6.0.1/MMB29M/hong07261054:user/release-keys
persist.sys.usb.config=adb,mtp
[General Questions and Answers] vampirefo:
All these devices are .fls but each are signed by manufacturer, unless RCA and Yocto uses same key you are out of luck, worth trying though.

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

That's why you don't have adb, I didn't know you was running a modified boot.img.

The below needs to be changed asap before others loose their adb.

ro.adb.secure=0

To

ro.adb.secure=1
[General Questions and Answers] mrmazak:
yes I did that. should still be fix able because the stock recovery has adb access though.

problem is compounded by his image was modified again to remove my keys.

I am fixing that mistake and putting up new images tonight.

I see my file downloaded almost 20 times but no body else has posted when I asked, If this problem is wide spread.

Hopefully they are following and update to the new , new images.

please let me know about ro.secure too
[General Questions and Answers] cozzie37:
Crap.

Either that, or they knew to change it.
[General Questions and Answers] vampirefo:
OK if you have adb in stock recovery, dd the modified boot.img.

ro.secure=0 is fine, and recommended step towards adb root.
[General Questions and Answers] mrmazak:
removed the original file from host and replaced with one that has adb.secure=1 as it supposed to

unlock tool with fixed img file

https://www.androidfilehost.com/?fid=673368273298934276

IF ANYBODY HAS FLASHED THE BOOT IMAGE FROM THE TOOL LIKE I HAVE PREVIOUSLY SUGGESTED PLEASE REDOWNLOAD THE V2 TOOL AND FLASH BOOT.IMG AGAIN

This boot image has only the change from force encrypt to encryptable.

I did test boot all the previous images before posting them, BUT BECAUSE I DID NOT DO factory reset with them flashed i did not notice the lack of adb key. So if you did flash the other one you may need to use adb in recovery in order to get into fastboot to fix it.
[General Questions and Answers] cozzie37:
[MENTION=2472806]vampirefo[/MENTION] have you ever tried a USB jig with these SoFIA tablets?
[General Questions and Answers] mrmazak:
what about

ro.adb.secure=

for the recovery.img?
[General Questions and Answers] vampirefo:
Recovery doesn't matter, I usually leave as 1.
[General Questions and Answers] mrmazak:
it is zero now but if do not matter will leave it i suppose. Especially that the .img has adb key already hard coded into it. Maybe with it as =1 it would not need to have the key in it. Well "if it aint broke I will leave it"
[General Questions and Answers] vampirefo:
No, I haven't.
[General Questions and Answers] mrmazak:
Well I got curious. And changed ro.adb.secure=1 and removed the adb_keys from the modified stock recovery to see if it allow adb connection. And well it did not. It just kept giving "unauthorized", so because there is no running system to make the pop-up there is no way to accept authorization.

so like vampirefo told me, in recovery it does not matter the setting of this string.

And only way I know of to get access will be to make an insecure move and share both halves of key pair.( Replacing the adbd in the stock recovery with an insecure one, like the one in the cwm recovery, makes the stock recovery fail to have adb access)
[Xiaomi Redmi Note 3 Questions & Answers] Shardul-Canvas A74:
Today , I was on CM13 official , really liked the rom

But , today , after I bought Jio sim , I realised that I couldnt use Volte on CM13 , so I decided to jump back to MIUI using fastboot method , In the middle of flashing the usb cable connected to my phone got disconnected due to some reason , and the phone became dead , I restored the device again as it still had bootloader working , but , if now the device has developed some unknown problem , whenever I try to install twrp in it , it again gets dead , Please help , I really dont want to remain in MIUI forever :crying:
[Xiaomi Redmi Note 3 Questions & Answers] Camlin3:
Why dont you try to flash in edl mode and stock global rom shipped with your phone

---------- Post added at 06:37 PM ---------- Previous post was at 06:34 PM ----------

Also try to flash twrp through other methods like booting twrp from fastboot then flash it from twrp itself or flashify or flashing china rom(usually china roms have magic to cure weird things )i have seen it in various cases
[Xiaomi Redmi Note 3 Questions & Answers] Shardul-Canvas A74:
Thanks for suggesting , but I already tried reinstalling stock miui , yet the problem continues , and are you sure about using flashify , cause if it again bootloops , it takes 30mins to reinstall stock rom , also I noticed a new problem , that the stock rom has started behaving buggy once I insert the second sim
[Xiaomi Redmi Note 3 Questions & Answers] Camlin3:
Its looking like firmware problem+
[Sony Xperia E3] sage of six paths:
I installed the Flashtool and the drivers, but did not install any specific driver since there is non for xperia e3. Will it still work or do i need to add drivers for some other xperia. So i only installed fastboot and flashmode drivers.

fixed
[Sony Xperia E3] engloa:
Thread closed at OPs request
[Xperia Tablet Z Q&A, Help & Troubleshooting] Alok Bajaj:
Has anyone flashed CM14 on Tablet Z LTE? Let me know here :)

https://androidfilehost.com/?w=files&flid=120798

Thanks to [MENTION=6073162]Komapatient[/MENTION] for the link
[Xperia Tablet Z Q&A, Help & Troubleshooting] Rootk1t:
It boots. Pretty usable. Has integrated Gapps (pico), latest TWRP, Snap Camera HDR app (as stock is not working).

Though, definitely not a daily driver at a current state, as CM14 in general is just not stable now.

But for testing purposes worth a try, however it doesn't change a lot from CM13 in appearance.
[Xperia Tablet Z Q&A, Help & Troubleshooting] Alok Bajaj:
Oh okay. Seems like we'll have to wait some time and hopefully those developers continue working on cm14 :)
[Xperia Tablet Z Q&A, Help & Troubleshooting] nicky-xda:
Thanks a lot for the link and [MENTION=4041916]CAHbKA[/MENTION] for the effort of this developement! :)

Could someone please give some more details about other important drivers? What about WiFi, GPS / COMPASS, IR Blaster?
[Xperia Tablet Z Q&A, Help & Troubleshooting] Rootk1t:
It depends on a build. In general all is working except IR and BT. And fast reboots happen quite often. ROM is definitely not a daily driver at this stage, but is working. Also author is trying hard in bugfixing, so hope next builds will be more and more usable.
[SuperSU] vin_:
I have a Samsung Galaxy J1, runnning Android 4.4.4 and TWRP 2.7.1. My phone has only 2.1GB of usable storage space.

As I installed using a zip file, SuperSU was a system app and cannot be moved to my SD card. This app was taking up 300ish MB on my system, and it came to the point where I couldn't even send a voice note on WhatsApp any more because of the little free space I had. When I saw that SuperSU was taking this much space, I tapped the [Uninstall Updates] button, finished uninstalling and my phone froze. It stayed frozen for about 3 minutes, when it started getting really hot. Then I removed the battery.

Upon restarting, the phone was very slow and unresponsive. I figured it could be a memory leak caused by some app, so I ignored it. However, my phone started locking up completely. I restarted again, opened SuperSU and disabled root since I thought that could be the cause of the slowness. It became more responsive, however apps like FolderMount and Kernel Aduitor stopped working. So I tried to fix it.

I went and flashed the latest SuperSU zip, but that did not fix the problem. I updated the binary from within the app, but that didn't work either. I selected [Cleanup for permanent unroot] inside the app, restarted, reflashed the zip and tried again. Nada. Finally, I went and dirty flashed my phone's stock firmware through Odin, reflashed TWRP, then SuperSU and that still didn't work.

I then hit up adb shell on my computer and entered the terminal, doing some /system exploration. I went to /system/xbin and noticed the lack of a su file. I then grabbed the file from my properly rooted Galaxy Tab 3 running CM 13 and SuperSU, then I pushed the file to /system/xbin using my recovery and set the persmissions to 777. I then enabled Superuser from within SuperSU, ran the su command in adb shell and got a "not executable: magic 7F45" error. I tried disabling and reenabling root in SuperSU, and then the system just hanged at the su command.

So can someone guide me into fixing my root? Lots of functions such as a custom LMK curve (for browsing Reddit using Sync and listening to music using Poweramp at the same time [having low RAM is a struggle]) and using FolderMount (to mount my massive WhatsApp folder onto my memory card to save on storage space) depend on it.
[Wing, P4350 Herald Upgrading] coolmen777:
Hello everyone

I have installed one of the Touch Roms and currenty trying to fix the registry entries so that all Icons in Settings/Buttons will show up properly. The functions are working fine (Messanging, VoiceCmd, etc), but some buttons don't have icons and are not named properly. I found the area in the registry where the corrections are done, but I can't seem to figure out what the proper values are. Can anyone with stock ROM lock in the path below and tell me what the values are? I will create a small guide for everyone's benefit!

What I am looking for is all Reg values for all 7 or whatever number of buttons you have programed (40C1, 40C2, etc and values inside like Default, Icon, Name, etc). Feel free to ask questions and I will tell you exactly what I need. Thanks.

Registry path: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Shell\Keys