Develop Bugs

JTAG access?

All this talk of accidental bricking reminds me of my i910 days where if you bricked your phone, all you had to do was hook it up using JTAG and you could reflash whatever you wanted (you do need to know where to get the parts/tools though).
I'm fairly sure that the snapdragon platform on this phone, like almost every other embedded system ever made, has JTAG ports for debugging and the like. Has anyone made any progress towards finding them and using them? Or is it as heavily protected as the rest of the phone's security model? Any info would be great!

I know that in the G1 dev forum there is a JTag thread. You can ask the op seems he found them there. Maybe he's updated to the nexus or dinc and has some snapdragon test points.

Honestly77 said:
I know that in the G1 dev forum there is a JTag thread. You can ask the op seems he found them there. Maybe he's updated to the nexus or dinc and has some snapdragon test points.
Click to expand...
Click to collapse
The thread in question: http://forum.xda-developers.com/showthread.php?t=591048
I didn't see anything about snapdragon in there...

I bought a "bricked" DINC for a steal and was hoping to revive it.
Recovery and system both appeared to be toast, but at least I could get into Hboot (S-ON). Well, after trying to apply a couple "Official" Froyo RUUs, I've now also pooched Hboot. The screen no longer comes on and I've verified it's not just the screen, since it's not recognized at all on USB and therefore no fastboot.
I found this JTAG diagram, and info on dedicated repair boxes such as ORT and RIFF, however I'd like to find a cheaper solution. Shouldn't it be possible to use OpenOCD and a Wiggler JTAG? Anyone here with actual experience working with JTAG on the QSD8650.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

Generic Allwinner A13 tablet ADB problems

Right so I got this cheap Tablet for a friends birthday, He's not one for tinkering and his girlfriend who I picked it up for asked me to get it set-up ready for him to just use as a net surfer/occasional game device/Media slate.
Before I start, I have USB Debugging on, Unknown Sources etc all turned on.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Note; Image stolen from Google, Not my image :good:
I wanted to root the device, remove some of the pre-installed bloatware and just all-in-all tidy it up a little. After doing some research I discovered a thread containing "Generic A13 Tablet rooting" or something of that nature.. The first indication that there could be a problem with it was when installing all but "Android Device" driver was installed. I unplugged, uninstalled and basically tried everything including the PDAnet program.. I then discovered a link which had a driver to install. This appeared to have worked.
The PDANet program finished installing and never asked what Device I had..??
I brushed this to one side and checked ADB Devices; This just showed me the following.
Code:
ADB Devices
List of Devices;
There are no devices showing, I then thought Oh maybe its ADB.. I checked my Nexus, HTC Wildfire and my XPERIA Play, They all show up.
I then followed the guide to root the device using Doomlords Xperia Rooter, it starts.. and hangs at "Waiting for Devices".
I have been trying to do this for about an hour or two and I'm getting no-where fast.. Help!
Its an Allwinner A13 Tablet (with HDMI) also known as the Q88 A13 with HDMI

Can any body find driver or help us to find ?
Hi to all.
I have this problem with "Pierre Cardin PC704" too.
this tablet have A13 SOC too.
Can any body find driver or help us to find ?
TNX alot ^_^

[Q] CM7 To Stock ROM Error

I was running CM7 on my KF and I wanted to get back to stock. I placed the Amazon factory software update.zip on the root of sd and followed all normal flashing steps. I did not flash. No I am trying to get it back on through adb and fastboot, but every step of the process comes back with:
exec '/system/bin/sh' failed:no such file or directory
I cannot do anything, except access TWRP. If I boot normal, it stays at Kindle Fire (blue) boot screen.
What are my options?

factory cable or usbboot
The former would be your best option IMO

Here is an update
I tinkered for a few hours and have the original Kindle Fire logo back, but that is as far as it goes. Using KFU, I get this, view attachment
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

xMatter said:
I tinkered for a few hours and have the original Kindle Fire logo back, but that is as far as it goes. Using KFU, I get this, view attachment
View attachment 2216020
Click to expand...
Click to collapse
Once again...
factory cable or usbboot
The former would be your best option IMO
https://www.youtube.com/watch?v=o8GtVXMrzrU

Would this work???
On the black hat there is an adapter, what this work just like the factory cable?
http://shop.teamblackhat.info/Factory-Adapters-motadapt.htm

Yes

site
Thank you! Could you please link to a tut on what I must do after I receive the adapter?

xMatter said:
Thank you! Could you please link to a tut on what I must do after I receive the adapter?
Click to expand...
Click to collapse
You turn the device off, then plug it in...voila, fastboot mode.

Help!
I received my factory cable today in the mail, but i am unsure of where to start. What utility should a use to get anything (preferably, kindle stock software) to happen. I only get two screens: either kindle logo OR black screen.

Firmware Download Mode (not bootloader )

Has anyone seen this on the Pixel?
I get this, when I turn off the phone and press volume up (only) then plug in the cable and get to this Download Mode that I has never seen on a Pixel. I always use bootloader to flash.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
What is it for?
What firmware use ?
Is this new? ( I've seen this on a LG phone before )
P.S. I'm on Android Q beta Qpp2 (not rooted)

valderdark said:
Has anyone seen this on the Pixel?
I get this, when I turn off the phone and press volume up (only) then plug in the cable and get to this Download Mode that I has never seen on a Pixel. I always use bootloader to flash.
What is it for?
What firmware use ?
Is this new? ( I've seen this on a LG phone before )
P.S. I'm on Android Q beta Qpp2 (not rooted)
Click to expand...
Click to collapse
Yeah, it's been noted a while back. Unfortunately it is of no use to us unless you could get factory signed firmware from google, and then have the proper interface with which to install it. Some folks were messing with it in late 2017 to see if a root exploit could be found for the Verizon variant by installing it, however, it never came to fruition.

Badger50 said:
Yeah, it's been noted a while back. Unfortunately it is of no use to us unless you could get factory signed firmware from google, and then have the proper interface with which to install it. Some folks were messing with it in late 2017 to see if a root exploit could be found for the Verizon variant by installing it, however, it never came to fruition.
Click to expand...
Click to collapse
Thought that I would mess around with it.
It would be nice to have a different way to flash a firmware just in case the other method doesn't work.
Thanks

Bricked TCL Alcatel 1x 5059x

So, I really wanted to get the phone rooted, and I couldn't do it without a recovery, because I can't find the firmware for it no matter what, there is only firmware for 5059d, so when I flashed TWRP for 5059d, it was asking for a password, but I didn't have one. I made one, but TWRP didn't let me mount internal storage. I tried factory reset and it made it even worse, it showed me this image
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I tried factory reset but didn't help, then I tried to flash 5059d stock recovery, it worked, but now it does not even want to boot into system, I have tried Wipe data/Factory reset, didn't help. I am stuck now. I did try to flash stock firmware for 5059d, but I can't do it for some reason, SP flashtool throws me some ERROR : STATUS_BROM_CMD_FAIL /0xC0060005) error. I really don't know what to do now, if someone knows to help me, it would be preety cool . This is not my main phone, but I really want to get it fixed. Screw rooting now.

Where did you get the ROM?

DerivativeOfLog7 said:
Where did you get the ROM?
Click to expand...
Click to collapse
First Google search, phone is completely gone though so not worth investigating

BokeeXD said:
First Google search, phone is completely gone though so not worth investigating
Click to expand...
Click to collapse
Look at this: https://forum.xda-developers.com/t/...rom-a-5059d-to-unbrick.4598953/#post-88676529
May be worth a shot. If I were you I'd first try normally just plugging the usb cable in while the phone is off, and if it doesn't work, take it apart, unplug the battery, and then plug it in