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
I am trying to use 'adb' from the android dev kit but I cannot see the devices, i.e. 'adb devices' doesn't report any devices. It appeared to be working earlier this evening but not any more. I was going to push a rom file to my rooted phone but obviously since I no longer see the device I am stuck. I rooted yesterday and installed the maximus rom but my phone went into a loop of restarting. Unfortunately I didn't backup before I rooted and installed Maximus rom.
Can anybody offer any help? I am using Mac OSX.
Desperate since phone is now effectively redundant
adiemask said:
I am trying to use 'adb' from the android dev kit but I cannot see the devices, i.e. 'adb devices' doesn't report any devices. It appeared to be working earlier this evening but not any more. I was going to push a rom file to my rooted phone but obviously since I no longer see the device I am stuck. I rooted yesterday and installed the maximus rom but my phone went into a loop of restarting. Unfortunately I didn't backup before I rooted and installed Maximus rom.
Can anybody offer any help? I am using Mac OSX.
Desperate since phone is now effectively redundant
Click to expand...
Click to collapse
try this: http://forum.xda-developers.com/showthread.php?t=1706918
if it didnt help u just reply and we´re gonna look whats next to unbrick ur phone
Hi
Thanks for your reply, I have hit the 'Thanks' button
I read the posting you referenced but it doesn't really offer a solution to my problem.
As described earlier I rooted my phone and flashed a Rom (Maximus) succesfully but on turning the phone on after installing the new Rom I got into a cycle of the phone rebooting without actually getting past the lock screen. My thoughts at that stage were to re flash using stock rom but on running fastboot and plugging into my Mac OSX machine via USB, the phone doesn't show up in 'devices' on the Mac. I have also tried 'adb devices' form within Android Dev Tools and although 'adb' runs fine no device is reported. Of course without devices being avaialble to 'adb' then I cannot reflash!
I have also tried from within a bootcamp installation of 'Windows XP' installed on the mac with the same results, this with 'HTC Sync' installed and therefore providing the USB Drivers required within Windows.
I have tried logging into fastboot using 'power' and 'Down Volume' at various stages of the boot process on the phone but have never seen the phone within devices.
Clearly prior to installation of the Rom (Maximus) I could see devices at both the Finder window on the Mac and from adb devices.
Any help or insight you could provide would be very gratefully received
Ok ok ok dont worry
I had to read a bit and found quit much german threads where they flash back the stock rom
as is suggested u cant flash it with odin...
the only solution i woul suggest is that u have to find a computer running windows
there its very easy to restore the stock with the methods u described earlier in the thread...
hope u get done let me know what happend
=)
The question remains; how can I flash anything be it a hacked rom or an official rom when I cant see the 'device' in both windows and mac osx?
I think what I am looking for is a reason why the phone isn't seen when plugging in via USB. Once it is seen as a 'device' I will be able to flash anything via 'adb'.
Thank you for your continued interest and assistance
ok so u know how the get it back but ur phone is not really recognized by ur computer
but i found a method using the bootloader
the problem is that the instructions are in german
but i think if u google a bit u may find it
Don't know if I misunderstood what you said..but to get into recovery, you hold volume down and the power button when the phone is turned off. Not during the boot process.
Yes you can do it with bootloader (power+volume down)
Sent from my HTC Salsa C510e using xda premium
moksha098 said:
Yes you can do it with bootloader (power+volume down)
Sent from my HTC Salsa C510e using xda premium
Click to expand...
Click to collapse
Yes, I know that. He said he attempted to do that DURING the boot process. I was stating that he had to do it while the phone was powered down.
Guys, I can get into recovery no problem. The issue is that my phone doesn't show up in devices on the mac finder window and hence when I run 'ADB Devices' from the mac when the phone is plugged into the mac with USB no device is found and so no serial number is reported in my terminal window on the mac. If I can get to see the device with 'ADB' I can push the rom and recover the phone. At the moment the phone is bricked.
Thanks guys for your continued assistance.
adiemask said:
Guys, I can get into recovery no problem. The issue is that my phone doesn't show up in devices on the mac finder window and hence when I run 'ADB Devices' from the mac when the phone is plugged into the mac with USB no device is found and so no serial number is reported in my terminal window on the mac. If I can get to see the device with 'ADB' I can push the rom and recover the phone. At the moment the phone is bricked.
Thanks guys for your continued assistance.
Click to expand...
Click to collapse
But if this doenst work why dont u try the method with the recovery mode or the bootloader i suggested
Im faily new to the android world. please forgive me of any stupid questions that i may ask.
I was trying to reinstall a new version of maximus 7 on my htc one .
i had the CM 10 installed and was having wifi issues. read that i should clear data and what not and instead of doing a factory reset....i did a format...
now i have no rom on the phone and cant figure out how to do this.
ill upload a video on what i currently have going on...
when i plug it in to the computer...i head the noise from the computer saying that it connected..but nothing popped up.
please help.
heres the youtube video of whats going on with the phone. take a look and suggest any fixes . thanks.
youtube.com/watch?v=NCSJPpLuQiE
adb sideload. you should search this thread there are many that will help you
i searched what i could. didnt find much because im not familiar with terms much.
andrey64 said:
i searched what i could. didnt find much because im not familiar with terms much.
Click to expand...
Click to collapse
you should download all in one toolkit and use the sideload feature. read the on screen directions as you go through the process and you should have no problems
I also ran into a similar predicament a few days ago. I found adb push to be much easier than sideload. Make sure that your drivers and adb is installed on your PC (I assume Windows). In recovery mode, plug phone into USB and your PC should detect the phone but you won't be able to see phone contents; mine made a connection sound.
Then open a command prompt and type: adb push ROM.zip /data/media/ROM.zip
Rom.zip is the rom file that you want to flash, which should be in the same folder as adb. For the path, I used "/data/media" because the custom recovery defaults to that but you may be able to use "/sdcard" as well.
Then flash the rom using recovery
Hello All,
I've been rooting etc for a few years now, but last night I ran into my first snag I can't seem to get out of. I was attempting to install Viper 3.0, I had flashed in twrp2.6.3.0 beta like they said to do. Went through the wipe, etc installed and it failed. Message was along the lines of "Failed: Installer status 7." So i went through the process of trying to again, but now I'm stuck in Recovery or hboot/fastboot. I had to reinstall Windows 7 on a old hard drive because the whole Windows 8.1 thing doesn't work right. So I can see my phone in adb in WIndows 7. I've successfully pushed twrp2.5 to my phone, but I can do nothing else. I've tried sideload, but that won't work. At this point the main thing I'm trying to do is push an older ROM over to my phone to see if it installs correctly, but I can't seem to even push files in adb. Any help would be greatly appreciated on the matter, as I'm sure I'm overlooking something.
C
combsco said:
Hello All,
I've been rooting etc for a few years now, but last night I ran into my first snag I can't seem to get out of. I was attempting to install Viper 3.0, I had flashed in twrp2.6.3.0 beta like they said to do. Went through the wipe, etc installed and it failed. Message was along the lines of "Failed: Installer status 7." So i went through the process of trying to again, but now I'm stuck in Recovery or hboot/fastboot. I had to reinstall Windows 7 on a old hard drive because the whole Windows 8.1 thing doesn't work right. So I can see my phone in adb in WIndows 7. I've successfully pushed twrp2.5 to my phone, but I can do nothing else. I've tried sideload, but that won't work. At this point the main thing I'm trying to do is push an older ROM over to my phone to see if it installs correctly, but I can't seem to even push files in adb. Any help would be greatly appreciated on the matter, as I'm sure I'm overlooking something.
C
Click to expand...
Click to collapse
Put the phone in recovery mode and plug it into your PC, and make sure adb devices shows your serial number. Then you should be able to just run
adb push C:\path\to\your\rom.zip /sdcard/rom.zip
Then just find it in recovery and flash it
.torrented said:
Put the phone in recovery mode and plug it into your PC, and make sure adb devices shows your serial number. Then you should be able to just run
adb push C:\path\to\your\rom.zip /sdcard/rom.zip
Then just find it in recovery and flash it
Click to expand...
Click to collapse
It made the file location, I'm waiting to see if it finishes copying it, as it's just sitting still at the moment.
Got it to work. Mods, you can delete this thread.
Hello XDA community, this is my first thread, i had never needed to post anything cause i always find everything im searching for in this awesome community... until now :crying:
Last week I got a new android device which is made by Polaroid, model: PSPR355, its a pretty low class device but I thought it would be enough for me.... then i realize I needed root permissions, for obvious reasons... easy I thought... i had rooted many devices...how hard can it be...right?... WRONG! :crying: . The first problem I encountered were the drivers..couldnt find em anywhere... fortunatelly i found a tutorial were i could install the drivers in a different way...although I took 2 days to do this...Ive been about 5 days trying to root my phone.... Ive tryied about 10 different programs with their different versions... and any of those rooted my phone, nor Oneclikroot, nor Unlockroot, etc, etc..... I really gave up trying to find something on the web cause i didnt even find the phone on its official site, so I came her defeated asking for any solution, idea, or if you want to help me with commands, a programm or anything else to root my phone, Im not even afraid of trying programming (Im trying to learn how to make roms, kernels, etc for this phone cause theres nothing on the web abou it but this is a theme for another time) if you wanted to help me i would really appreciate it, im a little desperate so anything would come useful thanks everyone and I hoppe you can help me!!! :fingers-crossed:
MecaMarck said:
If you wanted to help me i would really appreciate it, im a little desperate so anything would come useful thanks everyone and I hoppe you can help me!!! :fingers-crossed:
Click to expand...
Click to collapse
I would recommend trying the towelroot application. It can be downloaded from here, just click on the orange lambda to download the tr.apk file. Then open towelroot follow the instructions in the application. After the device reboots I would recommend downloading, Root Checker Basic form the Play Store and running that to make sure your device is rooted. Finally install SuperSU, and you should be good to go.
First thanks for answering so fast shimp208! And I guess I forgot to tell that I was in Mexico and Im using Telcel's network, I downloaded and installed the apk file but it doesnt starts I click the button pops up a black screen and then closes to the last app I used...any idea about this error...or if its beacuse of the carrier, by the way the device has Android 2.3.7 I dont know if it has something to do with this error
MecaMarck said:
First thanks for answering so fast shimp208! And I guess I forgot to tell that I was in Mexico and Im using Telcel's network, I downloaded and installed the apk file but it doesnt starts I click the button pops up a black screen and then closes to the last app I used...any idea about this error...or if its beacuse of the carrier, by the way the device has Android 2.3.7 I dont know if it has something to do with this error
Click to expand...
Click to collapse
Does it present an error message of any kind before it force closes? Try uninstalling and then re-installing the application, and if that doesn't work go to application manger under settings, find the towelroot application and select the options to clear it's cache and data. The carrier won't have any effect in this case, and with it being Android 2.3.7 your device most definitely has a kernel build date before June 3rd, 2014.
shimp208 said:
Does it present an error message of any kind before it force closes? Try uninstalling and then re-installing the application, and if that doesn't work go to application manger under settings, find the towelroot application and select the options to clear it's cache and data. The carrier won't have any effect in this case, and with it being Android 2.3.7 your device most definitely has a kernel build date before June 3rd, 2014.
Click to expand...
Click to collapse
No it simply closes without showing anything, and without even giving the "Force Close" message, i thought it was because i first installed it on the sd card, or because of not enough space but no, I moved it to the phone and uninstalled some apps I had, I uninstalled and installed towelroot twice and it didnt work, I installed the v1 of it and i got to the [make it ra1n] screen but when I click the button it closes immediately again without any error message
MecaMarck said:
No it simply closes without showing anything, and without even giving the "Force Close" message, i thought it was because i first installed it on the sd card, or because of not enough space but no, I moved it to the phone and uninstalled some apps I had, I uninstalled and installed towelroot twice and it didnt work, I installed the v1 of it and i got to the [make it ra1n] screen but when I click the button it closes immediately again without any error message
Click to expand...
Click to collapse
Very interesting, while in theory the app should work for any kernel build date earlier then June 3rd, 2014 the app many not be compatible with devices running an Android version less then 4.x.
shimp208 said:
Very interesting, while in theory the app should work for any kernel build date earlier then June 3rd, 2014 the app many not be compatible with devices running an Android version less then 4.x.
Click to expand...
Click to collapse
Yes that´s what i thought, do you think that theres no rooting method for this phone? if so, do yo think there´s a way of doing one?
MecaMarck said:
Yes that´s what i thought, do you think that theres no rooting method for this phone? if so, do yo think there´s a way of doing one?
Click to expand...
Click to collapse
Since you have the usb drivers working on your computer, try booting into the bootloader and using fastboot to see if the command fastboot devices returns anything. If the computer see's the device in fastboot that's a good sign. If your device doesn't have a locked bootloader which it likely doesn't, then I can try and create a rooted system image for you to flash in fastboot. Provided fastboot see's your device if it does, if you can provide me an adb dump of your /system folder then I will see what can be done.
Interesting for me.,.
Sent from my LT26w using xda premium
Same Boat
shimp208 said:
Since you have the usb drivers working on your computer, try booting into the bootloader and using fastboot to see if the command fastboot devices returns anything. If the computer see's the device in fastboot that's a good sign. If your device doesn't have a locked bootloader which it likely doesn't, then I can try and create a rooted system image for you to flash in fastboot. Provided fastboot see's your device if it does, if you can provide me an adb dump of your /system folder then I will see what can be done.
Click to expand...
Click to collapse
I'm in the same boat
I use moto-fastboot (any way it's fastboot)
#:\moto-fastboot devices
? fastboot
don't show any info...
I do a system dump in this way
#:\adb pull / c:\PSPR355
mega,co,nz/#!ThIUQYiS!LLbJ9e1-yVJI4juNlWQuPfa9GFH6HP9lr4X8Gwu1MBY
Change "," please, sorry mod if you want i can delete it! =$
klonic0 said:
I'm in the same boat
I use moto-fastboot (any way it's fastboot)
#:\moto-fastboot devices
? fastboot
don't show any info...
I do a system dump in this way
#:\adb pull / c:\PSPR355
mega,co,nz/#!ThIUQYiS!LLbJ9e1-yVJI4juNlWQuPfa9GFH6HP9lr4X8Gwu1MBY
Change "," please, sorry mod if you want i can delete it! =$
Click to expand...
Click to collapse
Unfortunately if fastboot doesn't show your device without any other flashing utility, even with the system dump there is no way to flash a rooted system image if it was created.
Got to see if this guys do the trick!
http://forum.xda-developers.com/showthread.php?t=2066041
shimp208 said:
Since you have the usb drivers working on your computer, try booting into the bootloader and using fastboot to see if the command fastboot devices returns anything. If the computer see's the device in fastboot that's a good sign. If your device doesn't have a locked bootloader which it likely doesn't, then I can try and create a rooted system image for you to flash in fastboot. Provided fastboot see's your device if it does, if you can provide me an adb dump of your /system folder then I will see what can be done.
Click to expand...
Click to collapse
Hello shimp well I connected my device on FastBoot Mode and my computer recognized it and it installed a driver named: ADB Testing Interface I dont know if thats a good sign or what should I do, I tried entering into recovery mode but it shows only an android little guy and exclamation quote... so I think it doesnt have a recovery boot I dont know if thats relevant, Could you help with the adb dump i dont know how to get it. And.... I dont know if besides you help me with the rooted system image you could teach me how I do this.... anyways thanks a lot for helping me! I'll keep doing everything you need so we can root this device!
MecaMarck said:
Hello shimp well I connected my device on FastBoot Mode and my computer recognized it and it installed a driver named: ADB Testing Interface I dont know if thats a good sign or what should I do, I tried entering into recovery mode but it shows only an android little guy and exclamation quote... so I think it doesnt have a recovery boot I dont know if thats relevant, Could you help with the adb dump i dont know how to get it. And.... I dont know if besides you help me with the rooted system image you could teach me how I do this.... anyways thanks a lot for helping me! I'll keep doing everything you need so we can root this device!
Click to expand...
Click to collapse
Since your computer recognizes the device and installed the driver and shows the device when in fastboot mode that's a good sign. The Android with the exclamation point is part of normal stock Android system recovery, it just means that the recovery menu has been hidden (You should be able to get the menu to appear by pressing the power and both the volume buttons in recovery mode). To dump /system run the following command:
Code:
adb pull /system
Then please send me a link to the /system dump, from there I will make a rooted system image.
Factory Rooted??
Hey guys I'm new to this so I may be wrong but has anybody thought to check if the Polaroid PSPR355 comes Factory Rooted??? I had a Polaroid Tablet, PID something(I forget the name), which I tried for hours to root resulting in: bootloop, hard reset, root, bootloop, hard reset, root, bootloop, hard reset, about to give up. So I Googled how to root Polaroid PID something (again, I forget the name), and I come to a post somewhere(forgot that too) that tells me my Tablet and similar Polaroid electronic devices(as well as most electronic devices coming from China) are factory rooted due to some Chinese law. So after the last hard reset, I downloaded HowToRoot App to check if my Polaroid Tablet is, in fact, rooted. I press the little lock button(root checker) and I find that, to my surprise, my Polaroid Table is in fact rooted. So all I had to do was download SuperSU from Google Play Store and Update Binary when prompted and I was Super User. Don't know if this helps but it worked for me.