Hello XDA,
I recently switched to Linux, so I had to set up ADB from scratch again. I am trying to unbrick my prime (CM-9 stuck in boot animation; CM-10 flashing problem with GooManager). I was following this guide up until the part where she says to enter the Vendor ID. I can't seem to get my device recognized and it keeps saying "??????????? No Permissions" I tried finding the ID online and putting it into the adb_usb.ini file, but the same message comes up when I try ./adb devices. Am I supposed to put 0x0b05 and another line underneath? What should I do? I have no idea. Please help. It's been bricked for weeks.
I apologize ahead of time if this problem has been posted already or if this belongs in a different section. I honestly tried looking around. Please help.
Related
I've got an Iconia tablet with a broken recovery (I've been using CWM and Thor's ICS ROM). I'm going to follow the steps outlined here
http://forum.xda-developers.com/showthread.php?t=1129873
but.... when I look up the UID from every method, all I get is 0123456789ABCDEF.
Given all the dire warnings about not being able to recover if/when things go wrong without the real UID... this 123 UID isn't the real UID.... is it safe to proceed with the repair here? Or are things really messed up?
I have not messed with ICS myself, but my understanding from reading the ICS threads in the Iconia forums is that the device is no longer using the uid for usb serial number. So it seems you can't get it that way if you have installed any of the ICS updates.
The suggestion I have seen is to look for androidboot.serialno in dmesg directly after booting, but that does not seem to help everyone.
Another option might be to get the device into APX mode and do a usb bulk read, the first read should return 8 bytes that is the UID. I would assume this to still work even after you have installed ICS but I have not tried. I pasted some code for opening the device, reading and printing the uid (using libusb, tested on Linux) on the Iconia forum earlier this week.
Hmm OK that's helpful info. Thanks.
I tried the androidboot.serialno in dmesg, but I wasn't able to find the string.... I will try that again after a clean boot.
I've been doing all the debugging from my one Windows machine... I haven't tried plugging it into my Linux PC yet... that's next... I haven't discovered APX mode yet. Time to do some more reading, thanks for the pointers.
Edit 1: OK checked lsusb -v and I serial also shows 0123456789ABCDEF
Edit 2: Clean boot and did a new dmesg dump.. parsed the output and no sign of androidboot.serialno or anything that even resembles it.
OK, things are not getting better here. I've been tinkering a lot, and in some respect I've just made things worse.
I still cannot find the UID with any of the documented methods here on XDA. I've tried
using adb devices
using Linux lsusb -v
checking the output of dmesg for androidboot.serialno
plugging in to Windows and looking at the USB mount info using USBDeview
looking at the device manager in Windows and checking the "Parent" field
I have also booted into APX mode and to discover the UID that way too... and nothing.
All I get is 0123456789ABCDEF
At this point the frustration level was getting high enough for me to be a bit reckless... I copied "itsmagic" into /data made it executable and ran it. No errors.
I rebooted into Recovery mode, and there I get scrambled graphics on the screen (it's the Acer logo duplicated several times with loads of tearing and distortion) and the tablet vibrates constantly.. non stop until I reboot it.
I can boot normally into the current ROM (Thor2002ro v96) so I haven't busted it completely. If I try to use my existing CWM manager to install any other ROM or use the manager to reboot into recovery mode, it goes back to the scrambled screen and vibrating constantly.
Does anyone have any ideas or suggestions here? I'd be happy to even roll back to stock and start fresh. There is nothing on the tablet that needs to be saved... except the functionality of the tablet itself.
When you write nothing about APX mode, does that mean literary nothing or nothing different?
If you have root you can see if you have anything interesting in /proc/cmdline.
If not I'm out of ideas on how the get the UID for now.
While i very much doubt 0x0123456789ABCDEF is the UID used to generate the SBK of the device you could try reading and decrypting the beginning of mmcblk0 using the SBK that would give (0xA9EA7E00 0xF12BEB06 0x3AD20804 0x364A5F03) to verify this.
You could probably overwrite the restore partition from your running system, I have never done that myself though.
OK, it's SOLVED.
After much swearing and crying and a little help from the forum here and in other posts the solution to fixing the broken tablet was actually quite easy.
Based on the information here:
http://forum.xda-developers.com/showthread.php?t=1459821
- I downloaded recovery-ra-iconia-3.16-gnm.img using teh links provided on the thread above
- I ran itsmagic
- Then I did these steps:
Code:
adb push recovery-ra-iconia-3.16-gnm.img /mnt/sdcard
adb shell
su
dd if=/mnt/sdcard/recovery-ra-iconia-3.16-gnm.img of=/dev/block/mmcblk0p1
sync
reboot recovery
This booted a working recovery mode (FINALLY), and I was able to successfully flash the latest Thor2002ro ICS ROM.
Thanks for your help and suggestions eppeP, they got me thinking in the right direction.
Hello guys I am trying to bypass screen lock via adb but when I write adb devices it shows "0123456789ABCDEF Device" and then when I type adb shell then it shows"$" after that whatever I type it shows permission denied(even if I write adb).Please Help
please clear up Google
account lock
Hey guys, I've been trying to get an initial root on my HOX+, it's my first time rooting anything and I've come across a bump in the road. I've been following this rooting guide from the HOX+ forum, but so far no one's responded to my request for help, so I decided I'd broaden my quest for answers here.
This is the initial post I made:
Help! I've followed the steps to the T, but I'm struggling with installing the recovery. I've unlocked my bootloader, downloaded the TWRPrecovery.img, put it in the right folder. As soon as I boot into the bootloader, my phone seems to disconnect from the computer. I still have fastboot usb selected, but my device no longer shows up under adb devices. When I try to >fastboot flash recovery TWRPrecovery.img, I get an error "error: cannot load 'TWRPrecovery.img' : Unknown error"
I've got the international HOX+ and a computer running Win7. Any assistance in the matter would be super appreciated.
Hey all,
So I successfully rooted my phone, and then I was going to go into recovery reboot mode to install a downloaded rom. I'm not sure what did it, but on that restart I got LG Security error. I first attempted on three different computers to do LG Mobile Support Tool. It stopped everytime when it was going to begin downloading the files. I'm pretty sure if I still had the Security Error image, I would be fine, because I now know of ways to bypass the LG Support Tool, and edit the host file, and then get it downloading.
Either way, in my research after no success with LG Mobile Support Tool, I came across Fastboot. So I got fastboot, I got the drivers installed, but I'm pretty sure my problem was, on the command prompt screen when Fastboot asks' you questions I said yes on them. I believe this is what caused my phone to have the black screen. It will not go into S/W upgrade mode now. It will not do anything, just black screen. I found a tutorial over on Android Forums, and with using Fastboot, I was able to sucessfully flash "p4_769.img" According to that tutorial, after doing that I should have a dead android guy logo, and then just be able to hard reset... but that didn't change anything. Still have the black screen. Still won't go into S/W Upgrade mode.
Now according to what I've read, the next step would be to flash KDZ Afresh...I've looked for this, whatever it is, specific to my model phone, but I can't find anything. If anyone else has any ideas, I would love to hear. I'm so frustrated at this point. Very much appreciate any help. Thank you.
It sounds like now what I have to do is, using how I flashed that recovery img, I first should flash the x and uboot.bin files to my phone. Then I will be able to get into S/W mode, and then restore from there. I just have to find these bin files. I don't have a friend or anyone nearby with the same phone as mine that can:
adb shell su -c busybox dd if=/dev/block/mmcblk0p2 of=/sdcard/external_sd/p2.bin
with theres.
Hi dlipford370, you could try this http://forum.xda-developers.com/showthread.php?p=51206080
Cheers. Good luck.
Sent from my LG P76020L-EUR-XX unlocked and rooted
Hello,
I was asked to forward my problem here so here it goes:
Not a long time ago I bought Asus ME302C FHD 10 and tried to root it. I followed a guide but I can't paste link just now.
Anyhow, the guide told me to flash rooted system image. I did every step correctly except that after i rebooted it, my device got stuck on logo screen, sometimes saying "no command".
I would like to undo that by getting unrooted system image for my device or rather get a working rooted system image. I am not sure about other possibilities as I am not experienced in android rooting or anything related. I do have fastboot up and working.
Thank you a lot in advance.
Edit: I figured out that Asus website has factory system images, however I don't really know which one to use because they all are for different countries and I am not sure what device is mine. Is there a way to check parameters of your device without booting it?
Edit2: I messed with the device more and found out that adb doesn't recognize device, as in, running 'adb devices' nothing gets listed. However, 'fastboot devices' does output my device, not sure where the problem is. Also, firmwares listed on asus website are zipped files and I don't know how to flash them. I tried 'fastboot flash system zippedfile.zip' but it would give me an error.
Solved
After few sleepless nights and loads of browser tabs opened I finally managed to fix my device.
All I needed was to use a different SKU firmware from Asus website. Now I can finally boot it thanks to XDA developers team and their useful information on the forums.
I'd like to start off by apologizing for having to waste somebody's time for something I can't find the answer to. I should preface this post by saying that I know nothing about ADB, but in the last couple of days I've done plenty of reading and to be quite honest the more research sometimes adds to the confusion with contrary and outdated information.
I'm basically trying to get TWRP onto my Mi Pad 4 LTE using ADB on my Windows 10 PC coming from the MIUI EU ROM Bootloader unlocked from the supplier. USB debugging enabled drivers installed etc
I had a lot of trouble until I came across this thread http://www.testedtechnology.co.uk/debloating-the-huawei-p30-pro/ because of an error I was getting in the Powershell window.
https://forum.xda-developers.com/attachment.php?attachmentid=4781060&stc=1&d=1561218064
So basically in short, thanks to the above thread I was able to get into fastboot mode having recognized the device using the precursor .\ as shown above, but one of my problems is I'm not sure if I should be use the .\ with all commands? My problem from here now that my device was in fastboot mode I didn't know how to direct it to the file. I just have no idea what commands to you use to find a particular directory to get to recovery-TWRP-3.3.0-0429-XIAOMI_PAD4(PLUS)-CN-wzsx150.
I'm really concerned about putting the device into bootloop as some of the problems I've seen seem almost insurmountable!
Anyway sorry again and TIA for anybody taking the time to help.
All sorted now thanks for all the help.