Can someone help me?
I need the config.gz from the 4.2.2 kernel
Can someone connect the device to pc with usb debugging on and do ''adb pull /proc/config.gz'' in cmd?
And can you give me the config.gz file?
Have fun.
Related
After some days work, I had edited most of the special device drivers and build rule files for cliq2 now.
I had succeed to build all the source for cliq2, and got target files, then I try to flash the update.zip to my cliq2, but my phone didn't boot, I was sad T_T.
My phone stack at the boot screen, I can access into the bootmenu screen, but can't access the normal UI.
Now, I want to know, is there any methods to help me debug in booting? Or, dose anyone konw , what is wrong about my phone( or my cm porting)? I want to use the adb to help me cat the log files, but the cliq2 doesn't have the adb services in booting, anyone can help me to run the adb services in booting?
Maybe I can use the 2nd-init in bootmenu to start adb, but I don't know how to edit the init.rc file to start the adb services properly.
My English is poor*_*, I post this thread, I want to get some suggestion or help in porting, not ask how to fix my phone
Any suggestion?
Can someone please zip and upload these from the newest SDK with secure USB debugging (4.2) so I don't have to download a full new SDK. [Got these already]
I could also use a new adb binary for use on-device from terminal or script (or is it the same one?).
Thks
[Edit]
That would be 1.0.30 or above for the on-device adb. Can someone on a 4.2 ROM shoot me this file?
Thks
[Edit]
Guess there were too many bricks this week _that demanded attention. No biggy, I just downloaded the new SDK but I still need adb 1.0.30 or newer for on-device use. If someone gets a chance I would appreciate it. I will zip and post the API 17 (4.2.2) versions of adb and fastboot for anyone else that may need them.
Thks
hello, i'm new and sorry for my english, i have a chinaphone with android 4.2.2 e don't have the name of this model, so i can't find any roms or firmware for this phone.
The problem is that i installed chianfire3d and after install driver and reboot my phone is blocked in bootloop.
I FIND some tread for uninstal chinefire driver fro adb usind adb shell command.
When i write adb devices i can see my phone number, but when i use ab shell or usb or reboot or other return a message with "error closed"
I can only access to cwm 3.0 and i can't run usb debug mode.
Can someone help me with adb shell? why this happened?
help me please:good:
Hello.
I need an adb insecure kernel/a kernel with usb debugging enabled at boot for this device for development purposes but I'm a total noob in terms of kernel development. Is there anyone willing to make this?
If it matters my exact model is SM-A516B/DS.
Thank you a ton!
I think you can do it another way without an adb insecure kernel. It's been so long since I did this but this may help.
When booted normally, enable USB debugging, start adb (adb devices) and give the PC the permission permanently. Then, you can locate the following file and save it in your PC:
data/misc/adb/adb_keys
Then every time you want usb debugging to be enabled, you can create a folder called misc/adb in your data partition and then copy the adb_keys file inside.
It should work just as long as you're using the same PC to catch logs at boot when the adb_keys file was created.
And finally, you need to edit your vendor/default.prop. By default, you should have:
persist.sys.usb.config=mtp
Just change to
persist.sys.usb.config=mtp,adb
Maybe one of these is extra and not needed but I remember this used to work for me, so hopefully it still works
Good luck.
For some reason ADB Shell is not working, is there a work around for it? If so what is the command prompts? I'm trying to root and push to a device...
Is Bash a option if so where do I start??
Help a beginner hacker please
USB Debugging isn't properly set up on mentioned Android device, especially the RSA-keys what are necessary to pair PC and Android device didn't get created and stored.