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've gotten pretty far in the tutorial for using nvflash until I get to the wheelie --blob blob.bin command.
I've reinstalled the naked drivers after first entering APX mode, but now I'm getting a different error that reads:
Waiting for device in APX mode...
[=] Chip UID: 0x15c7d7a4b20060c
[=] RCM Version: 0x30001
[-] Error 3 receiving response from command
I feel like this is the last big step for me to get to Androwook, but I'm too scared of flashing until I've done the necessary procedures for NVFlash. Anyone have more info on this particular error and how to fix?
jynlude said:
I've gotten pretty far in the tutorial for using nvflash until I get to the wheelie --blob blob.bin command.
I've reinstalled the naked drivers after first entering APX mode, but now I'm getting a different error that reads:
Waiting for device in APX mode...
[=] Chip UID: 0x15c7d7a4b20060c
[=] RCM Version: 0x30001
[-] Error 3 receiving response from command
I feel like this is the last big step for me to get to Androwook, but I'm too scared of flashing until I've done the necessary procedures for NVFlash. Anyone have more info on this particular error and how to fix?
Click to expand...
Click to collapse
just checking 1 more time if anyone can help out or has any insight/thoughts as to what to do?
jynlude said:
just checking 1 more time if anyone can help out or has any insight/thoughts as to what to do?
Click to expand...
Click to collapse
I have exactly the same error and cannot find any answer.
Can someone please help ?
yankeefr78 said:
I have exactly the same error and cannot find any answer.
Can someone please help ?
Click to expand...
Click to collapse
happen to have found a solution? i might just restart and try again from scratch
Same issue here. Recreated blobs, uninstalled and reinstalled drivers, rebooted everything, tried a different computer, no change.
Making an addition to this thread. Also having ongoing "Error 3 receiving response from command" when entering "./wheelie --blob blob.bin"
When run as root, I get:
"RCM_Receive communication failure"
The device is showing up when I run lsusb
Anyone been able to find a work around?
wanted to see if anyone can help with an update to see if anyone was successful with this yet? still scared to flash to hairybean without successfully going through this process
This worked for me
Hi all,
I got this same error too when using nvflash I had already on my computer (possibly from previous attempts some time ago).
I was following Matt Hills guide ("Asus Transformer Prime TF201 Unlock, Backup Blobs and Enable nvFlash") so I downloaded NVFlash from the link provided on the guide and it works now.
I'm a new user so unable to post direct link, sorry!
1. Download NVFlash from link above (in edit reason)
2. Re-copy blob files (I found trying to use the files after initially receiving the error, provided a different error)
3. Run "wheelie –blob blob.bin"
Basically just starting fresh with a different version of NVFlash!
Hope this works for you guys.
Cheers
Jim
jim.g87 said:
Hi all,
I got this same error too when using nvflash I had already on my computer (possibly from previous attempts some time ago).
I was following Matt Hills guide ("Asus Transformer Prime TF201 Unlock, Backup Blobs and Enable nvFlash") so I downloaded NVFlash from the link provided on the guide and it works now.
I'm a new user so unable to post direct link, sorry!
1. Download NVFlash from link above (in edit reason)
2. Re-copy blob files (I found trying to use the files after initially receiving the error, provided a different error)
3. Run "wheelie –blob blob.bin"
Basically just starting fresh with a different version of NVFlash!
Hope this works for you guys.
Cheers
Jim
Click to expand...
Click to collapse
Totally worked! Thanks so much...was able to get my recovery files...next step is hairybean!
I'm glad this worked for you too! Gives promise that it will help others.
After bricking my TF201 once, I learnt my lesson and was not going to proceed without taking all the right precautions.
jynlude said:
Totally worked! Thanks so much...was able to get my recovery files...next step is hairybean!
Click to expand...
Click to collapse
jim.g87 said:
Hi all,
I got this same error too when using nvflash I had already on my computer (possibly from previous attempts some time ago).
I was following Matt Hills guide ("Asus Transformer Prime TF201 Unlock, Backup Blobs and Enable nvFlash") so I downloaded NVFlash from the link provided on the guide and it works now.
I'm a new user so unable to post direct link, sorry!
1. Download NVFlash from link above (in edit reason)
2. Re-copy blob files (I found trying to use the files after initially receiving the error, provided a different error)
3. Run "wheelie –blob blob.bin"
Basically just starting fresh with a different version of NVFlash!
Hope this works for you guys.
Cheers
Jim
Click to expand...
Click to collapse
unfortunately I dont have luck whit that, i can run 2 times wheelie.
1. time it says error 3
2. time it says nverror 0x2
and then device disconnects, i press and hold power and it boots directly into APX and i can start over with the same result
any solutions? :crying:
jim.g87 said:
Hi all,
I got this same error too when using nvflash I had already on my computer (possibly from previous attempts some time ago).
I was following Matt Hills guide ("Asus Transformer Prime TF201 Unlock, Backup Blobs and Enable nvFlash") so I downloaded NVFlash from the link provided on the guide and it works now.
I'm a new user so unable to post direct link, sorry!
1. Download NVFlash from link above (in edit reason)
2. Re-copy blob files (I found trying to use the files after initially receiving the error, provided a different error)
3. Run "wheelie –blob blob.bin"
Basically just starting fresh with a different version of NVFlash!
Hope this works for you guys.
Cheers
Jim
Click to expand...
Click to collapse
Is it even possible to brick APX mode?
dj_chapz said:
Is it even possible to brick APX mode?
Click to expand...
Click to collapse
Hi mate,
The steps I listed are for creating the backup blobs. Are you trying to create them or have you bricked your device and are trying to recover?
jim.g87 said:
Hi mate,
The steps I listed are for creating the backup blobs. Are you trying to create them or have you bricked your device and are trying to recover?
Click to expand...
Click to collapse
Im trying to recover. I got the backup files. Long story short, flashed wrong recovery, wiped eMMC (all partitions gone i think) so i need to repartition. I am in constant APX mode, cant get out, if i hold power it reboots directly into APX...
I had the same problem, try use this version.
redvirus said:
I had the same problem, try use this version.
Click to expand...
Click to collapse
It's a long time ago but thanks, this version helped me overcome error 3.
:good:
Reposted from the bottom of another sad-hearted thread. BTW Screenshot is just some graphic relief from happier daze with a Kindle that would do its half of the work to make the relationship function without so much damn grief.
----
Although I had Safe Strap, SU and etc. installed on my rooted HDX 7", I panicked when my firewall failed to block the 13.3.2.1 update and cut the power off in mid update. Unfortunate reflex that led to a soft brick. Although I now can get into Fastboot no problem (I can't access the ADB commands though), I have tried to flash recoveries, boot images and so on. I can erase data (I'd call myself an expert at this part of the rooting process) and arrange file system layouts but then can't get past this error:
FAIL: flashing not allowed for locked hw.
Anyone know how to, maybe change permissions on the hardware or whatnot to get the device to let me write to the system partition? I'm flashing from a iMac btw.
I mean the Christmas colors of the text as far as what worked and what didn't are fun to look at, but the actual loading of the Kindle OS might provide more long term visual excitement. Thanks and love all y'all's insights into navigating the treacherous waters of root access and tweaking the twerkinator in these here twandroids.
----
EDIT: I can use the ./adb commands but I was having trouble before with the period-less version. Was still getting no device to show up when I query adb but got this through fastboot:
fastboot -i 0x1949 devices -l
(serial number) fast boot usb:FA130000
Redaction is mine ...
noobkidsontheblock said:
Reposted from the bottom of another sad-hearted thread. BTW Screenshot is just some graphic relief from happier daze with a Kindle that would do its half of the work to make the relationship function without so much damn grief.
----
Although I had Safe Strap, SU and etc. installed on my rooted HDX 7", I panicked when my firewall failed to block the 13.3.2.1 update and cut the power off in mid update. Unfortunate reflex that led to a soft brick. Although I now can get into Fastboot no problem (I can't access the ADB commands though), I have tried to flash recoveries, boot images and so on. I can erase data (I'd call myself an expert at this part of the rooting process) and arrange file system layouts but then can't get past this error:
FAIL: flashing not allowed for locked hw.
Anyone know how to, maybe change permissions on the hardware or whatnot to get the device to let me write to the system partition? I'm flashing from a iMac btw.
I mean the Christmas colors of the text as far as what worked and what didn't are fun to look at, but the actual loading of the Kindle OS might provide more long term visual excitement. Thanks and love all y'all's insights into navigating the treacherous waters of root access and tweaking the twerkinator in these here twandroids.
----
EDIT: I can use the ./adb commands but I was having trouble before with the period-less version. Was still getting no device to show up when I query adb but got this through fastboot:
fastboot -i 0x1949 devices -l
(serial number) fast boot usb:FA130000
Redaction is mine ...
Click to expand...
Click to collapse
can you get to safe strap at all???
Last time I checked it was a chore to unlock the bootloader is that still the case these days? Its why I haven't yet done it on my HDX 8.9" running 14.3.2.4_user_324002120
Montisaquadeis said:
Last time I checked it was a chore to unlock the bootloader is that still the case these days? Its why I haven't yet done it on my HDX 8.9" running 14.3.2.4_user_324002120
Click to expand...
Click to collapse
Wow - that's an old build! If you have used adb, have a host PC or laptop, can install device drivers and are comfortable following directions unlocking is relatively easy. At present the task remains a largely manual affair. However, the rewards are rich with a nice suite of custom ROMs including several Nougat based options. It will be like having a new device!
I have both a laptop and desktop both are running Windows 10
Montisaquadeis said:
I have both a laptop and desktop both are running Windows 10
Click to expand...
Click to collapse
Assume the device is rooted given OTA updates appear blocked. If accurate read and execute step #2 only (skip #1) from this post. The links in that post are dead; you can download the files from here. Be sure to grab the Apollo variants of both files. Life gets ugly fast if you run with the Thor variants.
The above procedure will NOT unlock the bootloader but will put into place the necessary prerequisites for doing so.
Davey126 said:
Assume the device is rooted given OTA updates appear blocked. If accurate read and execute step #2 only (skip #1) from this post. The links in that post are dead; you can download the files from here. Be sure to grab the Apollo variants of both files. Life gets ugly fast if you run with the Thor variants.
The above procedure will NOT unlock the bootloader but will put into place the necessary prerequisites for doing so.
Click to expand...
Click to collapse
The thread on TWRP says it requires an unlocked bootloader. So wouldn't that cause issues since I am NOT unlocked yet?
Montisaquadeis said:
The thread on TWRP says it requires an unlocked bootloader. So wouldn't that cause issues since I am NOT unlocked yet?
Click to expand...
Click to collapse
Nope - TWRP can be flashed on a locked device with a vulnerable bootloader. Having access to a custom recovery can be a huge benefit should something go wrong during subsequent steps.
I understand why the OP included that caveat. Makes sense if you don't have someone guiding you through the unlock procedure.
Davey126 said:
Nope - TWRP can be flashed on a locked device with a vulnerable bootloader. Having access to a custom recovery can be a huge benefit should something go wrong during subsequent steps.
I understand why the OP included that caveat. Makes sense if you don't have someone guiding you through the unlock procedure.
Click to expand...
Click to collapse
Hows the 1-click bootloader unlock working these days?
AKA
https://forum.xda-developers.com/kindle-fire-hdx/general/multi-platform-1-click-bootloader-t3241014
It was linked to in the post you linked to.
Ok so far I have done both TWRP which is indeed working and aboot and that is it.
Montisaquadeis said:
Hows the 1-click bootloader unlock working these days?
AKA
https://forum.xda-developers.com/kindle-fire-hdx/general/multi-platform-1-click-bootloader-t3241014
It was linked to in the post you linked to.
Ok so far I have done both TWRP which is indeed working and aboot and that is it.
Click to expand...
Click to collapse
Congrats! You have gotten through the riskiest part of unlocking the bootloader. From this point forward there is little you can do to hurt your HDX aside from sustained contact with a blow torch or direct engagement with an A1 Abrams battle tank (bit of an overreach but you get the point).
Unfortunately, 1-Click is still not ready for prime time. The author has the best of intentions but a severe lack of bandwidth to complete.
That said, manual unlocking is relatively easy:
1) Download/install this package on one of your Windows machines which scores drivers that have proven reliable with every HDX device I (and others) have encountered. Yep, seems illogical but it works better than all of the other alternatives (drivers) that have been bounced around for the past 4 years. You can remove the package after unlocking your device.
2) Install Minimal ADB and Fastboot (here) on the same machine
3) Verify you can launch the ADB/Fastboot command window via the icon that should have been added to your Windows desktop.
4) Boot into TWRP and tether your device using a reliable USB cable. You should receive some audible/visual feedback from Windows that it recognizes the device.
5) Launch the minimal ADB/Fastboot window, type "adb devices" and press <return>. Response should be the device identifier followed by the word 'device'. If successful type "adb reboot bootloader" followed by <return>. After a few moments the device will boot into fastboot. Type "fastboot devices" and press <return>. If successful response should be similar that noted above. Finally, type "fastboot reboot" to boot into FireOS. If any of the previous commands fail simply untether and long press power button (8-20 sec) to turn off your device. It can then be restarted in the usual fashion.
If you have difficulty with any of the items in step #5 please detail your observations and I will help you through remedial steps. Otherwise, bounce back and we will go through the remaining few steps to complete the unlock process.
Sorry for parceling this out in small chunks. Experience has taught this is the best approach rather than penning a long novel in a single post.
error: device unauthorized.
This adb server's $ADB_VENDOR_KEYS is not set
Try 'adb kill-server' if that seems wrong.
Otherwise check for a confirmation dialog on your device.
Is what came up when I went to do adb reboot bootloader.
Montisaquadeis said:
error: device unauthorized.
This adb server's $ADB_VENDOR_KEYS is not set
Try 'adb kill-server' if that seems wrong.
Otherwise check for a confirmation dialog on your device.
Is what came up when I went to do adb reboot bootloader.
Click to expand...
Click to collapse
Hum - something seems wrong. That command should not have failed if the previous "adb devices" returned the expected response. Let's take a different approach to the fastboot connectivity test:
- untether device
- boot into TWRP
- tap 'reboot' followed by 'bootloader'
- you may be prompted for a confirmation swipe; go ahead and do that
You should now see a gray "Kindle fire" logo followed by the word "fastboot" in brackets. Retether device; hopefully a ready prompt will appear. If so continue with fastboot connectivity test as documented in previous post.
If a ready prompt does not appear or the test fails you'll need to use Windows device manager to identify your device and update the device driver to "Mot Composite ADB Interface". This can be a tedious process if you haven't gone through it before. Bounce back if you need assistance.
Ok fastboot devices is not bringing anything up so it doesn't seem to have worked.
Oh in Device Manager its coming up as Kindle Fire HDX under both Universal Serial Bus devices and Portable Devices.
basically
adb devices brings up the device id but it says unautherized to the right of the id.
Montisaquadeis said:
Ok fastboot devices is not bringing anything up so it doesn't seem to have worked.
Oh in Device Manager its coming up as Kindle Fire HDX under both Universal Serial Bus devices and Portable Devices.
basically
adb devices brings up the device id but it says unautherized to the right of the id.
Click to expand...
Click to collapse
Boot into FireOS, tether and respond to any prompts. Hopefully one asks you to approve the connection to your Windows box (be sure to check the 'always' box if presented). Then repeat adb connectivity test.
Note: You may have to enable adb under developer options in settings. Might find this article helpful (found it on a quick Google search; haven't verified contents but seems to be ok; I haven't used FireOS v4 in a couple years).
Note #2: I'm happy to keep going but don't want to you to feel obligated/stressed by the barriers being thrown up. Feel free to bail at any time.
Davey126 said:
Boot into FireOS, tether and respond to any prompts. Hopefully one asks you to approve the connection to your Windows box (be sure to check the 'always' box if presented). Then repeat adb connectivity test.
Note: You may have to enable adb under developer options in settings. Might find this article helpful (found it on a quick Google search; haven't verified contents but seems to be ok; I haven't used FireOS v4 in a couple years).
Note #2: I'm happy to keep going but don't want to you to feel obligated/stressed by the barriers being thrown up. Feel free to bail at any time.
Click to expand...
Click to collapse
Ok FireOS comes up with device next to the id while TWRP says unautherized so I have no idea what is going on here personally.
Montisaquadeis said:
Ok FireOS comes up with device next to the id while TWRP says unautherized so I have no idea what is going on here personally.
Click to expand...
Click to collapse
Not going to worry about it now as it doesn't reflect an immediate barrier. You have established/verified ADB communications (good!) but still need to verify fastboot communication.
Path forward:
- Boot back into TWRP and then reboot to the bootloader/fastboot (there are more direct methods but the TWRP->Fastboot two step is the easiest for now). As before there should be a 'fastboot' in brackets but no 'ready' prompt.
- Tether device; if ready appears you're good! More likely nothing will happen. At that point you need to launch Windows device manager and change the device driver used to communicate with the HDX as detailed in a previous post. In short, locate the device (most likely shown with a yellow explanation mark); right click -> update driver; select 'Browse my computer...'; select 'Let me pick...'; locate and select 'Mot Composite ADB Interface'. If you still do not get a ready prompt after performing the above repeat the first two steps until device is retethered. Hopefully that will do it.
- Once you have a ready prompt issue the command 'Fastboot devices' to verify fastboot communications are possible. Then reboot your device.
I realize the above seems kludgy and obviously frustrating. It is without a doubt the most difficult part of unlocking the device. Once fastboot communications have been verified it's all down hill.
Davey126 said:
Not going to worry about it now as it doesn't reflect an immediate barrier. You have established/verified ADB communications (good!) but still need to verify fastboot communication.
Path forward:
- Boot back into TWRP and then reboot to the bootloader/fastboot (there are more direct methods but the TWRP->Fastboot two step is the easiest for now). As before there should be a 'fastboot' in brackets but no 'ready' prompt.
- Tether device; if ready appears you're good! More likely nothing will happen. At that point you need to launch Windows device manager and change the device driver used to communicate with the HDX as detailed in a previous post. In short, locate the device (most likely shown with a yellow explanation mark); right click -> update driver; select 'Browse my computer...'; select 'Let me pick...'; locate and select 'Mot Composite ADB Interface'. If you still do not get a ready prompt after performing the above repeat the first two steps until device is retethered. Hopefully that will do it.
- Once you have a ready prompt issue the command 'Fastboot devices' to verify fastboot communications are possible. Then reboot your device.
I realize the above seems kludgy and obviously frustrating. It is without a doubt the most difficult part of unlocking the device. Once fastboot communications have been verified it's all down hill.
Click to expand...
Click to collapse
As I said Kindle Fire HDX is listed TWICE in Device Manager when tryinng to do the fastboot. Its listed under both Portable Devices and Universal Serial Bus devices and neither have a yellow exclamation mark so I havw no clue which one to change over to the other driver. Ontop of that its 11pm here so I will check back tomorrow.
Montisaquadeis said:
As I said Kindle Fire HDX is listed TWICE in Device Manager when tryinng to do the fastboot. Its listed under both Portable Devices and Universal Serial Bus devices and neither have a yellow exclamation mark so I havw no clue which one to change over to the other driver. Ontop of that its 11pm here so I will check back tomorrow.
Click to expand...
Click to collapse
You want to work the entry listed under Portable Devices. I'm in the same timezone; also winding down for the evening.
Hi Davey, I'm responding in this thread as you requested yesterday.
Before I start trying to install TWRP, does it matter that I have Safestrap currently installed? Or should it be removed first? @Yousucks2 said the following in my other thread:
"But check first first which recovery are you install, replace Safetrap with TWRP without unlocked bootloader , will brick your device"
Also, I am running a custom Rom of kindle fire for thor. I was on kit Kat 4.4 but felt like trying out Amazon again. Not sure if that matters at all in this process.
leeismyname said:
Hi Davey, I'm responding in this thread as you requested yesterday.
Before I start trying to install TWRP, does it matter that I have Safestrap currently installed? Or should it be removed first? @Yousucks2 said the following in my other thread:
"But check first first which recovery are you install, replace Safetrap with TWRP without unlocked bootloader , will brick your device"
Also, I am running a custom Rom of kindle fire for thor. I was on kit Kat 4.4 but felt like trying out Amazon again. Not sure if that matters at all in this process.
Click to expand...
Click to collapse
Reasonable questions; responses:
- SafeStrap v4 and TWRP can coexist on the same device; no need to uninstall the former which is not a true recovery (it lives in the system partition and will be wiped out when you install a custom ROM)
- No issue running FireOS while navigating the bootloader unlock procedure
As previously noted be sure to use the Thor builds on your HDX 7. Recovering from an inadvertent Apollo flash make passing a kidney stone look appealing.
Ok I have changed the driver over to MOT composite ADB device V2 since I had 2 listed aka Version 2 and version 1.3. I now have the ready prompt and when I do fastboot devices I get the device id and fastboot to the right. So I tlooks like I am good to go with fastboot now
Montisaquadeis said:
Ok I have changed the driver over to MOT composite ADB device V2 since I had 2 listed aka Version 2 and version 1.3. I now have the ready prompt and when I do fastboot devices I get the device id and fastboot to the right. So I tlooks like I am good to go with fastboot now
Click to expand...
Click to collapse
Excellent! Next steps:
- Complete the 3rd bullet in the prerequisite section of this post. Pay careful attention to where the extracted batch file resides; move as needed. Most likely the directory will be "C:\Program Files (x86)\Minimal ADB and Fastboot" but you will need to confirm. Obviously referring to the Win 10 box.
- Perform steps #1 and #3 in the "Code generation and unlock" section. When complete it is quite possible the bootloader will be fully unlocked. However, if the procedure stalls we will have to take one more (easy) step to complete the procedure.
IMPORTANT: Step 2 in the "Code generation and unlock" section has already been performed (as directed earlier in this thread)! No need to repeat as this is the riskiest part of the unlock procedure.
Bounce back when complete. There are a couple clean-up steps that should be done before flashing a custom ROM. I can also provide guidance on which ROM to install if you don't already have one in mind.
My TF201 is working. Recovery ok. Android is working and booting.
But every time when i want to reflash by fastboot i endup with
`< waiting for device >` Fastboot is responding on `devices` command with device id but on flash still waiting.
Now when i was trying again to flash i noticed something.
`lsusb` is returning my TF201 as
```
Bus 003 Device 049: ID 0b05:4daf ASUSTek Computer, Inc. Transformer Pad Infinity TF700 (Fastboot)
```
I think thats my problem. Does anybody know how to repair it ?
Next step
Ok i figured out It's not a problem. This state is ok but still problem in flash -
After i reconfigured udev and serval things finaly able to call flash command but it only says "sending"
I'm sending there a recovery - flatline so 7MB waiting 5 minutes. No success.
Any ideas?
What bootloader version does it say your 201 is running?
NP
I was on some stock bootloader. Then i downgraded to 10.4.2.15. Finally i figured out fastboot on my PC was not communicating with tablet.
So i flashed recovery from my Macbook without any problem... Backuped tablet with wheelie and nvflash.
So my problem is gone. Now i flashed again kernel_chooser every thing is fine.
Just now im trying to find some old images of some linux and kernel to boot up some linux.
If you know about tell me. Otherwise we can close this thread.