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
Okay so I managed to compile and flash the pacman rom (ATT X+) and then I flashed the pizza kernel. I was greeted with that spinning cyanogenmod screen and eagerly awaited for my freshly cooked rom to boot. Sadly it didn't. After a minute or two, the device just rebooted. I assume something must have been crashing and caused it to not boot.
So I set off on a quest to logcat and diagnose my issue. I followed this guide:
http://forum.xda-developers.com/showthread.php?t=1726238
But when I try to do adb logcat.... the command prompt just sits at _waiting for device_
I believe my drivers are all installed. I even installed the ADB universal drivers.
http://adbdriver.com/downloads/
I even tried a logcat for dummies!
http://forum.xda-developers.com/showpost.php?p=28187592&postcount=17
Any ideas guys?
starfox5194 said:
Okay so I managed to compile and flash the pacman rom (ATT X+) and then I flashed the pizza kernel. I was greeted with that spinning cyanogenmod screen and eagerly awaited for my freshly cooked rom to boot. Sadly it didn't. After a minute or two, the device just rebooted. I assume something must have been crashing and caused it to not boot.
So I set off on a quest to logcat and diagnose my issue. I followed this guide:
http://forum.xda-developers.com/showthread.php?t=1726238
But when I try to do adb logcat.... the command prompt just sits at _waiting for device_
I believe my drivers are all installed. I even installed the ADB universal drivers.
http://adbdriver.com/downloads/
I even tried a logcat for dummies!
http://forum.xda-developers.com/showpost.php?p=28187592&postcount=17
Any ideas guys?
Click to expand...
Click to collapse
Seems debugging is not active in the freshly flashed ROM, if you know how to bake in debugging "on by default" that would be my best guess as next step to allow adb connection. Good luck!
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 XDA'rs,
Ive been messing around with building roms and I finally got one to finish(Kindle Fire V1 btw). So I flashed it to the device and tried to boot.
What I get is the backlight to come on and never see the bootlogo. So its hanging. (Not why Im posting)
My question lies in ADB. I want to get a logcat of the device as it boots to see what the problem is.
The rom is 4.2.2 so I know theres the new security prompt to enable access for adb on the device, but does this prevent me from using adb until the device will complete its boot or is there a way to make it work?
All I can get now is for it to show "0123456789ABCDEF offline".
Ill appreciate any help!
Bump
Sn0w17 said:
Hey XDA'rs,
Ive been messing around with building roms and I finally got one to finish(Kindle Fire V1 btw). So I flashed it to the device and tried to boot.
What I get is the backlight to come on and never see the bootlogo. So its hanging. (Not why Im posting)
My question lies in ADB. I want to get a logcat of the device as it boots to see what the problem is.
The rom is 4.2.2 so I know theres the new security prompt to enable access for adb on the device, but does this prevent me from using adb until the device will complete its boot or is there a way to make it work?
All I can get now is for it to show "0123456789ABCDEF offline".
Ill appreciate any help!
Click to expand...
Click to collapse
just went through this this morning too.
short version... make sure you have the newer version of adb installed and running from that directory... replace you older versions.
4.2.2 needs adb.exe 1.0.31 and can be downloaded here for windows pc.
if you have/need Linux or mac versions they are in the index of the folder too here
.
.
Basically, I'm trying to port a ROM and it's failing to boot. So what I want to do is look for errors in a file somewhere and see what is occurring that causes this to happen. I was assuming logcat but I cannot access it via recovery or even shell so I got a little sad there. I was hoping there'd be a file I could pull from the devices but I'm not sure.
Anyone got an idea?