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???
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
Hi guys,
Wondering if anyone here has the know how to help.
Im fiddling with some new Kobo arcs, the 7HD and the 10HD and im having some bother with installing a custom recovery img.
For simplicity sake im going to refer to them as the same device as they are both behaving the same way
The device is rooted, and I am able to flash a custom recovery made by Jenkins builder but its not functional, when you boot to the recovery OS it just goes black and the back light flashes on an off (screen remains black it just lightens up)
At this point I can reboot as normal and adb to it and flash the original recovery img and all is well.
As far as I can tell its bootloader is unlocked but there might be a second bootloader im not able to interact with yet, possible called uboot?
From adb I am able to reboot the device in to bootloader and fastboot and both function as id expect, but the problem im having is booting directly to fastboot in case I bugger something up which would allow me to fix it.
I can boot the device in to a "mode" that tries to install an APX device, ive tried using various adb, fastboot, and composite drivers and nothing seems to work, ive downloaded some old NVidia APX tegra 2 drivers ive found but these fail to work with the NVFlash utility that comes with it, it says unknown device found, which would make sense given the utility is at least 3 years old
So firstly,
Does anyone know what might course the customer recovery rom to fail and yet flash like it is doing, if so any suggestions where to start to look for a solution?
Secondly,
Does anyone know much about this APX mode and how to actually put it to good use the driver appears to work and communicate but im needing something desktop wise to talk to it...?
hope you guys can help
edit
ive answered some of question 2 myself, it appears its a pain in the arse by all accounts and not as user friendly as I was hoping, I can send commands to it but it appears that commands may need to be "signed" of sorts as I don't get any response other than acknowledgment of the command sent, ill monitor the USB traffic and see if that sheds some light, it also appears that NVflash (not to be confused with its cousin in the GPU arena) is also hopelessly out of date and once again Linux is needed to get something more updated, if there is ANY help at all id appreciate some input
D
dazza9075 said:
Hi guys,
Wondering if anyone here has the know how to help.
Im fiddling with some new Kobo arcs, the 7HD and the 10HD and im having some bother with installing a custom recovery img.
For simplicity sake im going to refer to them as the same device as they are both behaving the same way
The device is rooted, and I am able to flash a custom recovery made by Jenkins builder but its not functional, when you boot to the recovery OS it just goes black and the back light flashes on an off (screen remains black it just lightens up)
At this point I can reboot as normal and adb to it and flash the original recovery img and all is well.
As far as I can tell its bootloader is unlocked but there might be a second bootloader im not able to interact with yet, possible called uboot?
From adb I am able to reboot the device in to bootloader and fastboot and both function as id expect, but the problem im having is booting directly to fastboot in case I bugger something up which would allow me to fix it.
I can boot the device in to a "mode" that tries to install an APX device, ive tried using various adb, fastboot, and composite drivers and nothing seems to work, ive downloaded some old NVidia APX tegra 2 drivers ive found but these fail to work with the NVFlash utility that comes with it, it says unknown device found, which would make sense given the utility is at least 3 years old
So firstly,
Does anyone know what might course the customer recovery rom to fail and yet flash like it is doing, if so any suggestions where to start to look for a solution?
Secondly,
Does anyone know much about this APX mode and how to actually put it to good use the driver appears to work and communicate but im needing something desktop wise to talk to it...?
hope you guys can help
edit
ive answered some of question 2 myself, it appears its a pain in the arse by all accounts and not as user friendly as I was hoping, I can send commands to it but it appears that commands may need to be "signed" of sorts as I don't get any response other than acknowledgment of the command sent, ill monitor the USB traffic and see if that sheds some light, it also appears that NVflash (not to be confused with its cousin in the GPU arena) is also hopelessly out of date and once again Linux is needed to get something more updated, if there is ANY help at all id appreciate some input
D
Click to expand...
Click to collapse
I know this is old, but how did you flash the original recovery? I think I need to do this so that I can install the update ZIP for the Kobo 10. CWM is failing to install the file.
Just a quick question in case anyone knows:
At my place of work we have an old nexus 9 that's in pretty much perfect condition, but it was originally used in demo mode to for the display and as such, has been stuck in demo mode since coming off display.
One of the technicians claims he had a go at removing the demo mode a couple of months ago but with no success, I presume he tried at least a factory reset on it.
I'm not sure exactly what methods he tried but I was wondering if anyone here happened to know if this was possible?
It's basically sitting in a corner unused so worth a crack.
M1kesky said:
Just a quick question in case anyone knows:
At my place of work we have an old nexus 9 that's in pretty much perfect condition, but it was originally used in demo mode to for the display and as such, has been stuck in demo mode since coming off display.
One of the technicians claims he had a go at removing the demo mode a couple of months ago but with no success, I presume he tried at least a factory reset on it.
I'm not sure exactly what methods he tried but I was wondering if anyone here happened to know if this was possible?
It's basically sitting in a corner unused so worth a crack.
Click to expand...
Click to collapse
Is demo mode enabled in the system UI tuner under settings?
I would suggest flashing the latest factory images in fastboot.
cam30era said:
I would suggest flashing the latest factory images in fastboot.
Click to expand...
Click to collapse
Would be a great idea, except I'm not sure you can get into Developer Options to enable Allow OEM Unlock while in Demo Mode, which would make unlocking the bootloader (which has to be done before fastboot can function properly) quite difficult.
borxnx said:
Would be a great idea, except I'm not sure you can get into Developer Options to enable Allow OEM Unlock while in Demo Mode, which would make unlocking the bootloader (which has to be done before fastboot can function properly) quite difficult.
Click to expand...
Click to collapse
You're right, in that I'm not sure either (about enabling Developer Options). But it's worth a try.
M1kesky said:
Just a quick question in case anyone knows:
At my place of work we have an old nexus 9 that's in pretty much perfect condition, but it was originally used in demo mode to for the display and as such, has been stuck in demo mode since coming off display.
One of the technicians claims he had a go at removing the demo mode a couple of months ago but with no success, I presume he tried at least a factory reset on it.
I'm not sure exactly what methods he tried but I was wondering if anyone here happened to know if this was possible?
It's basically sitting in a corner unused so worth a crack.
Click to expand...
Click to collapse
This ADB command should do the trick:
Code:
adb shell am broadcast -a com.android.systemui.demo -e command exit
Edit:
In case that sounded overwhelming and/or to help others with this issue, here's more more info about how to do that.
You must first install the ADB drivers to your PC. I suggest using Minimal ADB rather than installing the entire Android SDK, then use Command Prompt to navigate to your ADB directory (the folder where your ADB application is installed. Use the cd command to change directories [get it, cd?] to the complete filepath to the folder containing your ADB program in Windows. I put my Minimal ADB folder that I extracted from the zip directly onto the C:\ drive so the filepath is "C:\adb". I open my command prompt and type "cd C:\adb" and it's ready to roll. Super easy), once it says C:\adb> or whatever your filepath is, copy the command code above exactly into the prompt and press Enter.
To ensure your device is properly connected, after using "cd C:\adb" to get to your ADB application, run the command "adb devices". The daemon will start and it will either list your device number if it's successfully connected or will remain blank and go back to the "C:\adb>" prompt if it's not connected properly.
There may be a notification on the device when you try to connect ADB, but i may be getting this confused with ADB Debugging. If you see a notification pop up with warnings or aging your precision to connect to your PC just click the "chill out bro it's cool, I got this" button.
I hope you get it up and running properly and can enjoy your Nexus 9!
Sent from my XT1575 using Tapatalk
Thanks guys, I'm in work tomorrow so i'll take my laptop in and give it a try, thanks for all these suggestions!
I'll tell you the results afterwards.
Hello! I am new and don't have much experience here, but I will try to post any/all needed info. I don't really know what I am doing, so a customized step-by-step guide would be awesome.
I recently got two tablets from a garage sale. One is an azpenpc model A745 (Build number KVT49L test-keys), and the other is a "Digital2 Plus" (Build number polaris_chiphd-eng 4.4.2 KVT49L 20140515 test-keys) tablet. Both run Android 4.4.2 with kernel 3.4.39.
The Asenpc one has a QuadCore-A33 processor, and the Digital2 one has a DualCore-A23. They are almost identical and have identical physical layout (buttons, camera, speaker...) Developer tools were enabled, but not root, as far as I know. I used factory reset first thing. I will also add that the UX is very unusual, especially on the Digital2 one. (The layout of the black bar that appears on swiping up from the bottom of the screen is unusual and awkward on the D2, and the other one has a hotbar 90* from the horizontal!)
I don't really trust these not to have weird bugs on them. Both have weird apps installed with vague purposes and lots of permissions, the Digital2 tablet has a massive number of un-unistallable factory apps that are total crap, and the AsenPC one has been displaying suspicious surveys in the web browser if I leave it alone too long. For this reason, and to try to get more space (hopefully), I would like to nuke from orbit.
I don't have any money and not much interest invested in these, though I would like them to work when I get done.
How do I install a custom ROM and Google Apps on these? Do ROMs for these exist (especially now that CyanogenMod went OOB), and what would I need to do to be able to install them?
Do I need Root or just an unlocked bootloader, and how do I get those on such unusual devices?
Currently, I think that I need to install the Android SDK, get a custom recovery and unlocked bootloader, and then somehow(?) use the recovery to install the image (never mind how I even get it there for the recovery to install!). There is also some way to do this directly with the SDK. I do not know the real details of how either work.
Thanks! I would really appreciate any help you can offer on how to do this, and extra kudos to anyone who can tell me how to re-arrange the hotbar, hotbar position, and swipe up/down menus too!
I was unable to locate any sections on these two tablets on this forum, or at LineageOS or PacROM. Can you please advise? How do I install a less-bloated and probably safer ROM on these tablets, and where do I actually get it from?
Lets get you started with recovery, unlocking bootloader and root.
Please search if there are roms for you device, and i ll guide on how to install it.
For now, lets get a fresh installation of your device. Sometimes a lot of stupid apps install themselves into the system partition. They are malware. They have un-suspicious names like system process, system monitor, etc. They make the device ectremely laggy and factory reset doesn't help.
Download sdk and platform tools. Just minimal fastboot package will also do.
extract them in say C:\
enable usb debugging
open cmd and do the following. Assuming the folder name is platform-tools.
Code:
cd C:\platform-tools
Code:
adb devices
if you see a device listed here with an id and an online status, everything is fine so far.
Code:
adb reboot bootloader
fastboot devices
again, if you see a device listed here with an id, everything is fine.
Code:
fastboot oem unlock
if it says success, bootloader is now unlocked
you can check using
Code:
fastboot oem device-info
Code:
fastboot reboot
Reboots phone normally
Now obtain a recovery.img for your device. Place it in platform-tools folder.
Code:
adb reboot bootloader
fastboot boot recovery.img
this will temporarily boot recovery, you can install rom from here (provided you find one online), wipe device, etc.
Thats everything you need.
Hit thanks if i helped.
Okay, thanks!
There's just one problem:
I still can't find a ROM for the AzpenPC tablet, and the Digital2 Plus also does not seem to have a ROM -- The serial number is L741GMB1405, and while there was a post on ROMs for a D2, this is a different series than the one listed.
How might I find or make a ROM for these?
Hello everyone,
I've been tinkering with my kindle attempting to flash TWRP so I could flash other ROMs on my Kindle Fire HDX 7 (3rd generation) but I have seemed to soft brick the device after using unlock.bat from https://forum.xda-developers.com/kindle-fire-hdx/general/thor-unlocking-bootloader-firmware-t3463982/post70881555#post70881555
The unlock.bat was supposed to unlock my bootloader, but now the device won't power on. If I plug it into the windows a bunch of partitions appear and windows prompts me if I want to format the various drives. If I plug my kindle into Linux, the 7 (i think) partitions show folders various different system functions.
Someone wrote in a separate forum that it's possible to restore kindle if I using something called eMMC Raw tool, but didn't really give any clear instructions.
If anyone could help me recover my device, that would be greatly appreciated. Thank you.
For some reason I can't upload a picture of the various files in the partition.
Side note: could I theoretically put CM 12 or anything else on one of the partitions instead of the stock ROM?
Praxxer1 said:
Hello everyone,
I've been tinkering with my kindle attempting to flash TWRP so I could flash other ROMs on my Kindle Fire HDX 7 (3rd generation) but I have seemed to soft brick the device after using unlock.bat from https://forum.xda-developers.com/ki...r-firmware-t3463982/post70881555#post70881555
The unlock.bat was supposed to unlock my bootloader, but now the device won't power on. If I plug it into the windows a bunch of partitions appear and windows prompts me if I want to format the various drives. If I plug my kindle into Linux, the 7 (i think) partitions show folders various different system functions.
Someone wrote in a separate forum that it's possible to restore kindle if I using something called eMMC Raw tool, but didn't really give any clear instructions.
If anyone could help me recover my device, that would be greatly appreciated. Thank you.
Click to expand...
Click to collapse
Unlock.bat did not "soft brick" your device as the actions it performs are totally benign. More likely you got sloppy and flashed an incompatible aboot (via dd) or erased aboot and don't know how to recover. Me thinks it is the latter. Keep reading; you'll eventually stumble on posts that describe corrective actions. I will edit this post with a link as time permits.
You do not need "eMMC Raw Tool" whatever that is.
edit: https://forum.xda-developers.com/ki...ing-bootloader-firmware-t3463982/post75284993
Davey126 said:
Unlock.bat did not "soft brick" your device as the actions it performs are totally benign. More likely you got sloppy and flashed an incompatible aboot (via dd) or erased aboot and don't know how to recover. Me thinks it is the latter. Keep reading; you'll eventually stumble on posts that describe corrective actions. I will edit this post with a link as time permits.
You do not need "eMMC Raw Tool" whatever that is.
edit: https://forum.xda-developers.com/ki...ing-bootloader-firmware-t3463982/post75284993
Click to expand...
Click to collapse
Ah. I wish I had seen that thread before I started the process! You may be right about the compatible boot. I couldn't find the original aboot_vuln.mbn file mentioned in the thread I was following, but managed to find aboot.img file and flashed that hoping it was the same. I could have sworn though, that the device stopped working the second after I clicked the unlock.bat file (executed outside the fastboot screen), but could be wrong.
Only problem about the thread you linked, device isn't responding to any ADB or fastboot commands, but still shows that my PC recognizes the device as a fire device.
Thank you for your time, I'll keep reading through the thread you linked.
Praxxer1 said:
Only problem about the thread you linked, device isn't responding to any ADB or fastboot commands, but still shows that my PC recognizes the device as a fire device.
Click to expand...
Click to collapse
Likely a Windows driver issue. Suggest installing Motorola Device Manager here which includes composite USB drivers that work reliably with HDX devices. Need need to run MDM; just install it. After connecting the device you will need update the driver via Windows Device Manager. Bit of hit and miss with a non-functioning device. Cables and USB ports also play a huge role, especially with fussy bootloader/fastboot communications. Avoid external hubs, USB3 ports and add-on expansion cards. Change cables, ports, etc. Good luck.
Davey126 said:
Likely a Windows driver issue. Suggest installing Motorola Device Manager here which includes composite USB drivers that work reliably with HDX devices. Need need to run MDM; just install it. After connecting the device you will need update the driver via Windows Device Manager. Bit of hit and miss with a non-functioning device. Cables and USB ports also play a huge role, especially with fussy bootloader/fastboot communications. Avoid external hubs, USB3 ports and add-on expansion cards. Change cables, ports, etc. Good luck.
Click to expand...
Click to collapse
Thanks Davey, I'll definitely give it a try. Just as a bit more information on my situation, the device manager on windows does read Fire Device "ADB composite driver". I also have it connected to the PC using a Fastboot Cable. I will give all of this a try when I get home from work today.
If I am able to communicate with the device after installing the MDM drivers, should I attempt to restore the device? Or try to unlock and flash the stock ROM?
Praxxer1 said:
Thanks Davey, I'll definitely give it a try. Just as a bit more information on my situation, the device manager on windows does read Fire Device "ADB composite driver". I also have it connected to the PC using a Fastboot Cable. I will give all of this a try when I get home from work today.
If I am able to communicate with the device after installing the MDM drivers, should I attempt to restore the device? Or try to unlock and flash the stock ROM?
Click to expand...
Click to collapse
- dump the fastboot cable (all but useless on a HDX); this isn't a generic Android device
- ADB composite drivers come in many flavors; HDX bootloader only likes a few of them
- if/when you reestablish communication first step is to restore aboot and install TWRP; unlocking and ROM installation come later
- do not attempt to reinstall stock; frustration and heartache consume those who do
- again, this is not a run-of-the-mill Android gizmo; many of the tricks you learned in kindergarden do not apply to Amazon tablets
Davey126 said:
- dump the fastboot cable (all but useless on a HDX); this isn't a generic Android device
- ADB composite drivers come in many flavors; HDX bootloader only likes a few of them
- if/when you reestablish communication first step is to restore aboot and install TWRP; unlocking and ROM installation come later
- do not attempt to reinstall stock; frustration and heartache consume those who do
- again, this is not a run-of-the-mill Android gizmo; many of the tricks you learned in kindergarden do not apply to Amazon tablets
Click to expand...
Click to collapse
Lol I feel like I'm in kindergarten tinkering with this HDX. How do I restore aboot? clearly the image I flashed with was not the correct bootloader. Should I attempt to extract aboot from the stock ROM? Or would you be able to share you tool set/point me to a working link for aboot, TWRP, and ROMs (I've looked at 4 threads so far without working links)?
UPDATE: I managed to install the ADB MOT Composite driver, but still no response to simple ADB and Fastboot commands
Thanks again
Praxxer1 said:
Lol I feel like I'm in kindergarten tinkering with this HDX. How do I restore aboot? clearly the image I flashed with was not the correct bootloader. Should I attempt to extract aboot from the stock ROM? Or would you be able to share you tool set/point me to a working link for aboot, TWRP, and ROMs (I've looked at 4 threads so far without working links)?
UPDATE: I managed to install the ADB MOT Composite driver, but still no response to simple ADB and Fastboot commands
Thanks again
Click to expand...
Click to collapse
Not uncommon. Unfortunately, there is no 'fix script' moving forward as each situation is unique. If aboot is too damaged to support basic communication it's pretty much game over for the average laymen. You will need to comb the threads for information nuggets that may apply to your situation. Or cut your losses and move on. I am not big on trying to unbrick these pups unless one well versed in low level trouble shooting. Lousy ROI; has to be a labor of love including copious time researching, trying and (likely) failing. Good luck.
@draxie - for awareness; read back a few posts for context.
1-Click is your friend
Davey126 said:
Not uncommon. Unfortunately, there is no 'fix script' moving forward as each situation is unique. If aboot is too damaged to support basic communication it's pretty much game over for the average laymen. You will need to comb the threads for information nuggets that may apply to your situation. Or cut your losses and move on. I am not big on trying to unbrick these pups unless one well versed in low level trouble shooting. Lousy ROI; has to be a labor of love including copious time researching, trying and (likely) failing. Good luck.
@draxie - for awareness; read back a few posts for context.
Click to expand...
Click to collapse
Right... the symptoms described are the normal state of affairs
after 'fastboot erase aboot' and 'unlock.bat' does no such thing.
The post linked above and/or my original "Bulk mode" post both
have the necessary instructions to recover. Alternatively, 1-Click
can handle this, assuming access to either MacOS or Linux (for
the time being).