I had a, basically dead other than it will show up in USBdeview under some drivers including as of currenbt, the offical Motor adb/fastboot driver, surnia (moto e lte) for a while and loved it, rooted and such. The screen got broken at the top but still totally fine until I did something in a drunken state and it wouldnt power up. I put this to its finiky usb port and the charger at the time.
Fast forward to today I got a new S9 (dumb buy, gonna sell and get a oneplus instead but anyway) but wanna get any data I had (was big into crypto before it got big when usingf this device and titaniumbackup backup files I have found show some apps were used for wallets and the doable mobile mining back in the day).
A couple months ago I could get the backlight to light up and thats it, sometimes the power LED would flash intermittely and i bleive it stayed on for ~5 seconds a few times.
I got frustrated and carefully fried the screen off under heat and the internals are well built but you can see rust and thus likely water damage.
Now my computer and especailly android/rooting skills these days are very weak compared to 2018 when it finally died due to a stroke but 3 years later to the day I finally got my rig formatted and running again and drivers installed and it will show up in that developer device manager tool as fastboot surnia S - Mot Composite ADB interface. I think for a while with only my Samsung drivers installed and trying random generic ADB drivers I had it showing up as active on some general adb driver.
adb commands do nothing. They pick up my emulators and s9 fine but not it. With fastboot however I get print outs such as TA3970065Y as a device and one of the "first steps" to doing a bricked surnia reviival with some oem i forget now command that Ives een in guides too lead to this which I take as nothing there.
Code:
"(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
...
(bootloader) 3A85790366719783#54413339373030
(bootloader) 363559004D6F746F4532280000#DF28
(bootloader) 85FE6C9F6E17DF0E3C9DB6A1E28AC55
(bootloader) 96786#65060B0400000000000000000
(bootloader) 0000000
OKAY [ 0.241s]
finished. total time: 0.242s
"
/
Any tips or next steps or hail maries? Its not a HUGE loss but as I regain more of my brains memory and go through my google history during when my brain was swelling im finding more and more forgotten wallets, communities, old software, accounsts all sorts of things and I know this phone was what I used exclusively other than my PC which im still scouring for clues to my near zero memory of the 2016 year but based on the titanium backup data from it I have as well as some old posts and google history data and urls I'd love to see whats on it at the moment to save if possible.
Everything else will just be a process with google history archives and my slow brain recovery but this old thing is really getting to me now what mysteries it might hold and with the power LED working, it going into recovery mode (I assume, no working screen and its pulled off now anyway but based on watching the device show up and such)
Blah blah blah, where could I start if anywhere, or am I better off going entry by entry in my 100gb of google server data i pulled from that time frame of raw data and links with little index.
Thanks (I'm excited to get rid of my fake chinese phone (not even gonna bother doing a mediatek all in one root) I got for free and my S9 and grab a new OnePlus, I wish i had the brain to buy one when I bought the s9 thinking you could still root samsung devices butr my last one was a S4, things have changed)
Just a bump (its that allowed on XDA?)
Have this phone with the screen off sitting by my rig and cleaning up my office. Doing recovery and conslidation of 8 years of crypto too though.
Havnt had any success with changing to offical/third party ADB drivers (all enviroment vars are set, my S9 and android emus work fine)
Any last ideas? I found out my titaniumbackup backup isnt whole at all, just apks it seems.
Related
Hello ladies and gents,
I am trying to help my fiancee revive her completely dead Amaze. This phone, unlike my own, is completely stock. No recovery or ROM flashing or S-off etc. It's straight from Wind Mobile (though around 22 months old at this point).
What happened: Phone was low on battery, so it was left plugged in to charge. Seemed fine. Going back to it a couple hours later, and it was died, which was odd since it was plugged in. Now it does not turn on at all (no HTC or carrier splash, recovery boot [vol down + pwr] does nothing), and the LED behind the speaker does not illuminate to indicate charging (no flashing, either).
Plugged into my computer, I get the "QHSUSB_DLOAD" device identifier, but using the brickdetect.sh script from the Unbricker thread doesn't detect anything. Likely because this has nothing to do with S-off bricking, but since I found that thread via the QHS string, I figured trying to detect it was worth a shot.
I would really love to be able to revive this device. The fiancee is back in school right now, so my income is the only one. Spending several hundred dollars on a new phone is just a kick in the pants while trying to manage already frightening wedding-related expenses. :/
What I have tried:
- Tried cleaning the battery terminals (battery and phone side) on my device
- Tried charging both on USB and wall charger for several hours (no change, no LED, no boot, no recovery boot)
- At my carriers store, I tested a known-good battery in our device, same behaviour
- Tested our battery in a known-good Amaze, after after a longer initial charge (battery was completely flat), that device booted with our battery.
- Tried booting into recovery, no luck
- Tried following steps in several other XDA Amaze and Sensation threads, and didn't get anywhere.
- I've ordered a new battery and external charger, but I'm not hopeful due to the above testing
What I haven't tried:
- Because I am still trying to get my Credit Card Extended Warranty to cover repair replacement, I have not opened the insides of the device. This thread proposes removing and replacing a battery on the mobo to get it to reset itself. I have not tried this yet.
- Anything to do with JTAG. While I've flashed ROMs and such myself many times on my own devices, I've never ventured into JTAG territory before.
What I want to know:
- Primary: What else can I try to diagnose what is wrong with this Amaze, and if it is recoverable?
- Secondary: Unfortunately we have photos on the internal memory (not SD-card) that are not backed up. If the phone cannot be revived, is there any way for me to get into the internal storage to try to recover those photos? This would be more of a challenge project. We can live without the photos, though she'll be disappointed. I'll be the hero if I can get them back, even if it means destroying the device permanently.
Thanks in advance for anyone who may have suggestions. I'm heading to bed for the night, but I'll check this tomorrow and test out any theories.
Does anybody have any theories I can test out aside from some sort of hardware failure on the mainboard?
What OS are you running on your computer. Try looking for the device in Ubuntu, maybe it'll find it there.
Windows 8 and 8.1 have issues with the drivers and software.
Darin_Ram said:
What OS are you running on your computer. Try looking for the device in Ubuntu, maybe it'll find it there.
Windows 8 and 8.1 have issues with the drivers and software.
Click to expand...
Click to collapse
I'm using Windows 7 (64-bit), but I also tried using the Ubuntu 10.04 based Live CD (PHToolz?) from the Unbricking thread, and it didn't detect anything at all (tried with and without automount enabled).
Reading what you said again, I'd say that it's a manufacture defect. It could be a wide list of things actually, hard to pinpoint.
In regards to recovering your photos and other files on the phone's storage itself, I don't think you can recover it at all.
The best bet right now is to get it exchanged if it's still under warranty (I'm assuming you didn't void the warranty by unlocking bootloader, attaining S-Off or flashing any custom roms/kernels/incompatible zip files e.g. A rom meant for another phone)
If it has warranty, don't give up hope.
I have been at this on and off for months now and have exhausted just about every option I come across. Ive tried just about all the options on the XDA forums, and dozens of options found throughout Google, I'm at a loss but there has to be a way to root my phone.
I have an AT&T Prepaid GoPhone (Alcatel 4015T) (Fastboot shows device mt6572v1_phone). The phone is cheap, pretty uncommon, and Ive only discovered maybe 3 people on Google that have had the same question for the same phone but it all went unanswered.
The only progress I have ever made in rooting is booting it into fastboot mode, in this mode fastboot will show the device id (Which I noted above but again its mt6572v1_phone), from there I can do nothing else, all commands sent to it, however they are sent to it through dozens of vendor ids such as (0x1bbb) or no vendor ids, no matter what it will just hang and sit there indefinitely with three dots (...) waiting for the command to be sent or accepted.
Furthermore , in fastboot mode, the only sole way to reboot it is to remove the battery as the entire physical device is unresponsive as soon as FastBoot starts up. Im really desperate to root it but am beginning to lose hope in the idea that its even possible.
wiseguy12851 said:
I have been at this on and off for months now and have exhausted just about every option I come across. Ive tried just about all the options on the XDA forums, and dozens of options found throughout Google, I'm at a loss but there has to be a way to root my phone.
I have an AT&T Prepaid GoPhone (Alcatel 4015T) (Fastboot shows device mt6572v1_phone). The phone is cheap, pretty uncommon, and Ive only discovered maybe 3 people on Google that have had the same question for the same phone but it all went unanswered.
The only progress I have ever made in rooting is booting it into fastboot mode, in this mode fastboot will show the device id (Which I noted above but again its mt6572v1_phone), from there I can do nothing else, all commands sent to it, however they are sent to it through dozens of vendor ids such as (0x1bbb) or no vendor ids, no matter what it will just hang and sit there indefinitely with three dots (...) waiting for the command to be sent or accepted.
Furthermore , in fastboot mode, the only sole way to reboot it is to remove the battery as the entire physical device is unresponsive as soon as FastBoot starts up. Im really desperate to root it but am beginning to lose hope in the idea that its even possible.
Click to expand...
Click to collapse
http://forum.xda-developers.com/search.php?do=process&query=4015T&titleonly=1
I feel super awkward and a bit embarrassed to ask this question, but I'm asking for help from this community (see last 2 or paragraphs for ask if you want to skip the boring details) and I think I need to explain briefly why to define my ultimate goal and why I even have to ask rather than sift through searches and assemble the steps/versions I need, etc.
My 22 year old daughter died recently (unexpectedly). I obviously want to preserve everything I can of hers, but I'm not firing on all cylinders mentally. I was able take her ThinkPad and virtualize it to my ESX system and also yank and clone the physical drive for safe keeping. But even doing that took me a while (which it shouldn't, that's kind of what I do for a living - I should be able to do that in my sleep, but it took 3 days and a lot of screaming). I was able to access her google accounts, facebook accounts, etc. and preserve a ton of stuff from there.
Ultimately while I would want to do with her phone the same thing I did to her notebook - preserve it virtually so I could examine it without fear of changing/modifying anything, but I don't think the product exists that allows me to virtualize an existing Android phone with apps and everything intact into a PC environment. I think I could install a whole new Android emulator in Windows, but that's not probably what I want.
I had just given her a Samsung S5 SM-G900T running on Ting for her birthday about 2 weeks before she died. It was unlocked but unrooted, it's rare that I would do nothing to the phone prior to giving it to her - but I pretty much just turned it on and handed it over with no custom ROM or anything - mostly because I was pressed for time the day of her party and it was shipped late.
When I got it back from the police a few say ago (they held it for 2 months) and charged it and turned it on 2 days ago, it upgraded from Lollipop to Marshmallow 6.0.1 (baseband is PE1), which was apparently pending. I don't know if that complicates things. It pissed me off, though. I have copied off local photos off and videos and already took control of her Google and Facebook accounts as I mentioned.
My slightly confused brain tells me normally I might install TWRP or CWM and make a NAND backup and copy it off someplace and at least have a restorable copy of her phone. I haven't done much of this sort of thing with phones for a year or two, I don't know what's changed in the latest OS versions and beides, plus I sort of "lose it" a bit, especially going through her personal things.
I'm not an idiot, I'm just not all here, yet. I'm asking if someone can please give me steps to safely preserve an image of her phone (IE, install TWRP or CWM using specific version xxx, etc., using Odin version xxx, etc.) - If I can virtualize it, too, I'd love to know what product does that, but again, I don't think I can.
I don't know why I feel the need to do these things, I just do.
Any help would be greatly appreciated.
Bump. Somebody please help this fellow. This is too important for me to try advising him, I don't know enough.
So even though half my brain is addled, I did some more research and found out a few interesting things, should anyone care to try this. I found there are a couple of open source tools built for android forensics:
Open Source Android Forensics Toolkit
https://sourceforge.net/projects/osaftoolkit/
Santoku
https://santoku-linux.com/about-santoku/
And there are commercial products, , like NowSecureForensics, some (if not most) built on the toolkits I just mentioned. Another is the painfully ironically named (for me, anyway) Autopsy.
This interesting website verified (to me anyway) that rooting the phone and changing access is still fundamentally sound forensically:
http://freeandroidforensics.blogspot.com
And it confirmed there is no way (yet) to truly "virtualize" the phone entirely (unless you are the manufacturer and you have some proprietary software).
For a "live" example virtually, the best you can do is install an Android emulator and restore an ADB backup of an app. This obviously may or may not work if the app is very hardware dependent. But for a simple program it might work fine.
So in addition to rooting my daughter's S5, installing TWRP, and backing it up, I also got my daughter's HTC One M7 to finally power up, and I rooted it and installed TWRP for backup purposes as well. Many of the forensic tools I mentioned will then report from the standard TWRP backups, with no risk to changing the phone. Some want to look at the phone themselves, even offering to root them, which I find more risky.
I haven't found any one tool to fully provide what I need, you need a Windows PC, a Linux PC (or VM), one or more toolsets (each comprised of other toolsets) and then a lot of time/will to really piece together things. I haven't completed the examinations - even typing is harder now for some reason, but should anyone else need this sort of thing (hopefully for different reasons than mine), the above info is a good start.
Hi there, I just got the 6P as my nexus 5x went into bootloop (not semi-bootloop from a bad flash, the one that is caused from one of the processors dying) and none of the fixes were working. I just wanted some general info, the do's, the do nots, etc. Does this phone also suffer from the same issue? I was rooted on 8.1 with Magisk. Does flashing / rooting put you more at risk to an unfixable bootloop? I would be planning on just flashing TWRP, and Magisk on a stock rom. Any tips, recommendations, etc would be highly appreciated!
notstevek said:
Hi there, I just got the 6P as my nexus 5x went into bootloop (not semi-bootloop from a bad flash, the one that is caused from one of the processors dying) and none of the fixes were working. I just wanted some general info, the do's, the do nots, etc. Does this phone also suffer from the same issue? I was rooted on 8.1 with Magisk. Does flashing / rooting put you more at risk to an unfixable bootloop? I would be planning on just flashing TWRP, and Magisk on a stock rom. Any tips, recommendations, etc would be highly appreciated!
Click to expand...
Click to collapse
Yes this phone will do it to in fact the message that I am writing is being sent from one that went into bootloop previously. Routing and such does not cause the boot loop. It is a processor malfunction. You can flash a kernel that will disregard the faulty processors in this situation should it become necessary. All you need to do is to make sure your bootloader is unlocked so you will have the ability to flash this kernel and go ahead and search for the fix so you will have it handy.
Sent from my Nexus 6P using Tapatalk
funnel71 said:
Yes this phone will do it to in fact the message that I am writing is being sent from one that went into bootloop previously. Routing and such does not cause the boot loop. It is a processor malfunction. You can flash a kernel that will disregard the faulty processors in this situation should it become necessary. All you need to do is to make sure your bootloader is unlocked so you will have the ability to flash this kernel and go ahead and search for the fix so you will have it handy.
Sent from my Nexus 6P using Tapatalk
Click to expand...
Click to collapse
Well that's a shame to hear, my Nexus 5x went into bootloop and I could not fix it, even with the patched files. I hope it doesn't happen to this. But I'm glad to hear it rooting/flashing will not induce a permanent bootloop and that it is indeed a processor malfunction. I just unlocked the device as we speak, I'm going to be flashing Magisk and TWRP soon. What kernel are you referencing, just so I can have it *just incase*.
Thanks for the info!
notstevek said:
Well that's a shame to hear, my Nexus 5x went into bootloop and I could not fix it, even with the patched files. I hope it doesn't happen to this. But I'm glad to hear it rooting/flashing will not induce a permanent bootloop and that it is indeed a processor malfunction. I just unlocked the device as we speak, I'm going to be flashing Magisk and TWRP soon. What kernel are you referencing, just so I can have it *just incase*.
Thanks for the info!
Click to expand...
Click to collapse
Sorry I don't have the URL handy but it's in here just search in the 6p forums and you should easily find it as there has been a lot of chatter about it
Sent from my Nexus 6P using Tapatalk
Unlock the bootloader on the 6p right off the bat. Activate the developer options, Turn on OEM unlocking, Adroid debugging and Debugging notify. Shut off "verify apps over USB". You'll have to connect the device to
the computer and do the fastboot command to achieve the final bootloader unlocking but once done, you're safe. Every time you boot, you'll see the stupidhead screen imploring you to lock the bootloader but ignore it.
Phone will boot evey time. I ultimately downloaded the 8.1.0 (OPM3.171019.013, Jan 2018) image used my Ubuntu laptop to get the rom in the phone, rooted it with Magisk, TWRP'd it and got the latest Lineage 15.1 kernel and
flashed that. Only problem I have is I can't get a USB stick to be read from the OTG socket. It's identified but it won't read the stick. Now that's O.K. with me because the phone will interface with a computer fine AND
if I boot into TWRP recovery, the file manager there does backups to an attached USB stick and can read and write to it perfectly fine. It's a quirk I can live with. I believe only 4 cores are used but it runs pretty nicely.
Battery swaps are a bear and I have a "good" 64Gb model and bought a "bootloop" 128gb special that looks immaculate. I've tried most of the tricks and it's gorked. I'm going to use it for a battery swap practice unit for when
I want to swap the battery on my good 64gb model. I also bought a new housing in case I dork some of the hardware getting the case open. Crappy design on the battery and they expect a $600.00 to $700.00 when new
phone is supposed to be "throwaway" after two years? Oh, don't buy a bootloop special unless it's dirt cheap. I'll not get the $100.00 I paid for the 128gb unit back or out of it. I don't think I'll be able to fix the one I got. When I open the case, I'll heat the CPU's directly and see if that will get it to start.
What is supposed to happen is one is to let the phone drain down to near nothing, plug it into the charger, let it bootloop for 5 minutes and they apply heat to the area between the camera and the fingerprint sensor.
When it gets to 50 degrees C, the phone supposedly shuts down the "bad" cpu's and will boot as a new phone on the "good" cpu's. One then is supposed to run into the menu, become the developer and do the steps I outlined above to allow OEM unlock. THEN it's safe to try and start loading a new ROM as the phone will communicate with a computer. I took the 128Gb unit and got it connected to an Ubuntu Linux laptop and "fastboot devices" shows the phone but since the bootloader is locked it won't do anything with it. I say the 6p is "ok" when compared to a $1000.00 Pixel 2 which of course is going to be a bear if one wishes to swap out the battery in the future. Lithiums only last so long (or any battery chemistry for that matter) then they need to be replace. Spend a grand on phone and it oughta last
more than two years. Kurt
ksaves2 said:
Unlock the bootloader on the 6p right off the bat. Activate the developer options, Turn on OEM unlocking, Adroid debugging and Debugging notify. Shut off "verify apps over USB". You'll have to connect the device to
the computer and do the fastboot command to achieve the final bootloader unlocking but once done, you're safe. Every time you boot, you'll see the stupidhead screen imploring you to lock the bootloader but ignore it.
Phone will boot evey time. I ultimately downloaded the 8.1.0 (OPM3.171019.013, Jan 2018) image used my Ubuntu laptop to get the rom in the phone, rooted it with Magisk, TWRP'd it and got the latest Lineage 15.1 kernel and
flashed that. Only problem I have is I can't get a USB stick to be read from the OTG socket. It's identified but it won't read the stick. Now that's O.K. with me because the phone will interface with a computer fine AND
if I boot into TWRP recovery, the file manager there does backups to an attached USB stick and can read and write to it perfectly fine. It's a quirk I can live with. I believe only 4 cores are used but it runs pretty nicely.
Battery swaps are a bear and I have a "good" 64Gb model and bought a "bootloop" 128gb special that looks immaculate. I've tried most of the tricks and it's gorked. I'm going to use it for a battery swap practice unit for when
I want to swap the battery on my good 64gb model. I also bought a new housing in case I dork some of the hardware getting the case open. Crappy design on the battery and they expect a $600.00 to $700.00 when new
phone is supposed to be "throwaway" after two years? Oh, don't buy a bootloop special unless it's dirt cheap. I'll not get the $100.00 I paid for the 128gb unit back or out of it. I don't think I'll be able to fix the one I got. When I open the case, I'll heat the CPU's directly and see if that will get it to start.
What is supposed to happen is one is to let the phone drain down to near nothing, plug it into the charger, let it bootloop for 5 minutes and they apply heat to the area between the camera and the fingerprint sensor.
When it gets to 50 degrees C, the phone supposedly shuts down the "bad" cpu's and will boot as a new phone on the "good" cpu's. One then is supposed to run into the menu, become the developer and do the steps I outlined above to allow OEM unlock. THEN it's safe to try and start loading a new ROM as the phone will communicate with a computer. I took the 128Gb unit and got it connected to an Ubuntu Linux laptop and "fastboot devices" shows the phone but since the bootloader is locked it won't do anything with it. I say the 6p is "ok" when compared to a $1000.00 Pixel 2 which of course is going to be a bear if one wishes to swap out the battery in the future. Lithiums only last so long (or any battery chemistry for that matter) then they need to be replace. Spend a grand on phone and it oughta last
more than two years. Kurt
Click to expand...
Click to collapse
Hi Kurt,
Wow, first off thanks for the indepth response. My Nexus 5x was unlocked, rooted with Magisk, allowed unlocking, usb debugging etc. Still can't fix it. I put it in the freezer and got it to boot into TWRP for 30 seconds before it boot looped. Bootloader always works, and can flash, but cannot boot into the rom or recovery. Anyway, I bought this 6P (128gb for $170, perfect condition with a Spigen case and glass screen protector.) because the Nexus 5x is dead, but wasn't aware this also has the same issue which sucks. I run Debian 32bit on my laptop, and it's a breeze compared to windows. Just had to grab the binaries for adb and fastboot, unlike windows where you gotta install crazy large sdk packs, make sure you got the correct drivers, etc. I unlocked the 6P, oem unlocking & usb debugging is checked on developer options. I flashed TWRP, and I'm on 8.1 OPM3.171019.014 (Feb 5th) because the newest one (8.1.0 OPM5.171019.015) won't pick up my Verizon simcard. I flashed Elemental X so I can underclock it, I'm running 4 cores at 1,200mhz and it still runs flawlessly. Any reason I should be using the LineageOS 15.1 kernel? I don't ever plan on using LineageOS or a custom rom. Just stock rooted for me. The battery life is kind of poor compared to the Nexus 5x. I'm a little confused, what do you mean by "Battery swaps are a bear"? If it's worth it, maybe I will put in a new battery. Lithiums life are extended if you don't charge 100% and don't let it die. If you keep it above 20% and charge to 90% max, you'll extend the lifespan by a lot. Some phone companies like Samsung already do this. Your 100% charge is actually only 95% or so in reality. Other things like Telsa cars also do this. I wouldn't have upgraded for a few years if my Nexus 5x didn't die, and honestly if I wasn't afraid of another bootloop, I would have gotten another, I loved that phone. The pixel 2 is great, my brother has one, but I'm not spending more than 250 on a phone ever again in my life, and 250 being the absolute max. I also don't want to sign a contract and do a device payment, I want to own it in full. I will upgrade to the pixel 1 XL when this phone requires me to do so, and hopefully that's at least 2 years from now. Thanks in advance!
Cheers.
Tore open the 128gb "bootloop" special using the variety of videos out there. Heated the CPU's directly although the battery
was I believe fully charged. No dice of breaking the bootloop to have it boot to a "clean" system and unlock the bootloader.
There were no anti tamper seals on this thing so I thing someone threw it out there for $94.00 and I stupidly bit. I caution
folks that unless one can buy a "bootloop" special for less than $20.00 and they have a "good" 6P they want to replace a battery on, don't buy a bootloop special unless it is dirt cheap. Use it to practice on for battery replacement before using
it on a "good" 6p.
I heated the CPU, case off while in a bootloop and no magic restoration was seen. The battery was from October 2015.
I dinged the edges of the glass but got the back half off pretty decently. If the thing booted up and I were able to restore it, I would have been happy with it as the dings aren't really noticeable.. I need to get some guitar opening picks without a lip on them as they are better to work with.
Last ditch attempt will be to drain it down to el "zippo" percent left, put it on a charger and see if I can make the $94.00 evaporate under the auspices of a 1000 watt heat gun with the back case off. Again, don't buy a "bootloop" special of a 6p unless it's dirt cheap. Kurt
Hi all,
I'm wondering if you guys can help me get this head unit back up and running (properly).
The story so far...
I bought a cheap head unit for a project car (first Android head unit I've had). When I received it, it actually ran REALLY well, everything was super smooth, very responsive. There was a problem though, all of the internal storage was read only, nothing was left for app space. They had also removed the options to format an SD Card as internal storage so I couldn't install anything. I got to looking for a replacement firmware. After a tonne of reading I was finding it was pretty much a clone of a Joying head unit, at least from a spec and software point.
This is the unit...
*ebay.co.uk/itm/7-Quad-Core-Android-6-0-WiFi-1DIN-Car-Radio-Stereo-BT-GPS-Navi-MP5-RDS-Player/253882611489?ssPageName=STRK%3AMEBIDX%3AIT&_trksid=p2057872.m2749.l2649
I had used the Joying Tools to root it, it actually failed but strangely after a restart the FS was R/W. Only a few hundred meg was used I should've stopped there but yeah, I didn't. The more I read, the more I thought it was just a Joying unit, in a physically different package and for the most part it is. It seems like the minor differences are what is causing me problems. My touch screen now doesn't work ) I took me ages to notice too, I'm not actually sure at what point of my messing around it happened, I had a keyboard and mouse plugged in.
The screen itself is fine (undamaged), from what I can see the driver is having problems. After a bit of digging I was starting to think the driver wasn't installed for it. I could see the devices listed in programs like Hardware Info but I couldn't see any modules loaded for it. I was thinking that the new firmware didn't have the same modules so my plan was to recompile the drivers from source. I got that done and when going to install them, I saw a load of errors with dmesg. The I2C controller seem to be running but is having problems, and drivers for the controller and touchscreen do seem to be there. dmesg is showing...
start check gt9xx_i2c
<<-GTP-INFO->> Guitar reset
i2c i2c-3: xgold_i2c_error_reg_status, device: 0x41 ERR_INT 0x30 recvd msg len: 1, state: 1
<<-GTP-ERROR->> I2C Read: 0x8040, 2 bytes failed, errcode: -121!
There is a lot in there, it repeats a lot but that's what stands out, I'll need to find something to make reading the dmesg output a bit clearer but overall, you can see the communication with the touchpanel trying to happen but isn't. White reading the porting documentation for the GT9xx driver I found out that you have to tell it what GPIO's are going to be used for reset and irq, maybe some others. I'm assuming that is GPIO's from the MCU but I'm not sure, I'm still a bit hazy on how the parts of these units talk to each other. I'm thinking the drivers in the Joying firmware are configured for addresses and GPIO's different from this unit so communication with the Touchpanel isn't working (being hardcoded into the driver).
Info about the system...
Manufacturer: ReakoSound (maybe, its not printed on the box or unit but raking around it seems to be them that makes it)
Model: RK-A712
CPU: Rockchip Sofia
RAM: 1GB
ROM: 16GB
Touch: Goodix GT9157
OS: Android 6.0.1
Does anyone have any ideas about how I can get the screen up and running or does anyone have one of these units? Everything else does seem to be running perfectly, the unit is running the GTX rom for Joying Sofia head units right now.
Thanks in advance
Progress-ish
I got a hold of the original firmware. I emailed ReakoSound and asked them for it I could see right away it was the one it came with. The boot logo is of an orange and black car, I remember seeing it when I first powered it on.
I didnt quite solve things though. The RGB Colors of the buttons are correct now. After messing with it I noticed the colors were off slightly, like you would choose say green from the configuration app menu and the buttons would go red. Just like the software was configured for different gpio's. So that's back to normal now. It didn't fix the touchscreen issue though. I did notice that every time it started after reflashing the firmware, it would state that I had previously switched off a google setting and asked if I wanted to switch it back on. It was holding settings somewhere.
My plan was to try to blank it as completely as I could. I used the custom.apk to to run TWRP and used that to wipe everything. I restarted and using that ALT+PRINTSCR+E method to get into the recovery started the flash procedure, hopefully on a 100% blank system. Now, another problem...
E:failed to verify whole-file signature
E:signature verification failed
Installation aborted
No matter what firmware I use, I get the same message. The original and Joying firmwares all have the same result. I'm currently looking for a way around this. So far I'm seeing that the verification can be switched off but that looks like using other recovery software (TWRP?), I dont get the option on the stock one, it boots right into the reflashing procedure.
Any ideas?