mtcd rk3188 7' hesdunit sruck in boot loop - Android Auto General

This unit has all soft touch buttons , I've tried going the reset and power button. I changed my kernel to performance governed and can't get out.
The unit is a a-media auto tmaxlife"
Anyone have tips?

No one?

Any luck? Do you know the mcu version? Is it mctd or am I out of luck? Screenshot of 'about'?
All i've gotten over the last 4 hours is LMC-AD7002, tmax4life, B01MRVJIWS, Tongxingbang.co (assuming that's the actual manufacturer)
I've been to sites in french, german,russian yada yada and nothing... You're the one and only hit.
I'm pretty sure your answer is spoken often. it's all in the timing of the reset button to get into recovery. And don't mess with kernels. I don't think it pans out all that often and boom you got a panic.
Liveboot apk would be supercool to run at startup. You could see what was killing your kernel. Obviously too late now. Fastboot flash boot ;somehow? Im fresh to head units so I can't say. Do you have busybox? Rooted? Rom?

Related

(g1) custom radio load failed. Need help!

hey guys i have a g1. its rooted.
i tried to get the latest custom radio. but idk why after wiped and then i used update frm sd. its did something then asked to reboot to finish installation . then the "Unboxing and an arrow to phone" came up. and its not going away .. its always there... i removed the battery fone ... tried to go to the recovery mode. nothing works .......
Need HELP!!!!!!!!!!!!!!!!
You said you cannot get into recover home + power
Can you get into the bootloader?? (camera + power)
If you can't boot into either of theese modes, then you probably bricked your phone during your radio update
nope.. i tried. the same screen comes up...
so there is no way to fix it now?
If you search around the forums abit there's a couple things you can try that will work in the chance that somehow it's just a softbrick....
However, not being able to boot with camera + power or home + power , is usually a sign of a brick
i think i got a softbrick.... cause its not the G1 sign.. the installation sign thats on the screen.. "Unboxing and an arrow to phone"
anyhow tnx dude
o7hafiz said:
i think i got a softbrick.... cause its not the G1 sign.. the installation sign thats on the screen.. "Unboxing and an arrow to phone"
anyhow tnx dude
Click to expand...
Click to collapse
Doesn't matter what you can see on-screen, if you can't get in to the SPL (home+camera) and can't boot the phone itself, then the thing's dead. Simple as.
Only way to fix that is to take it back to HTC/Tmo and say that's what happened after an OTA update, or replace the motherboard.
What radio were you trying to flash? One from the Hero?
not looking good :/
That part where you said unboxing.. by forever did you mean atleast 10 minutes? sometimes this part can take forever.. If you yanked the battery while it was still updating the radio odds are you're sol :/
Also did you have the correct spl installed? sadly jacking up the radio install is the easiest way to perma brick your phone...
i tried to flash this rom http://forum.xda-developers.com/showthread.php?t=552591
then i tough it'll be better if used the latest radio as that ask... so i used "update-hero-radio-63.18.55.06IU_6.35.08.22-signed" i pasted it on my sd. then used update frm sd zip...
the installed and asked to reboot.. i did then i installed but that the end that screen came up =/
So in short you tried to update a G1 with a Hero radio image. I think that's the first time I seen this one. Not sure where to point you too at this point.....
jackslim said:
So in short you tried to update a G1 with a Hero radio image. I think that's the first time I seen this one. Not sure where to point you too at this point.....
Click to expand...
Click to collapse
The "ROM Flashing for dummies" book? ;P
Moral of this story, don't flash radio images intended for other devices!!...Or ROMs for that matter. They won't brick but without the required drivers they aren't going to work.
so thats it.................. i just leave it like that......... trash that fone? lol
that radio was a mistake.. i didnt read that name.. i thought it was for g1's htc rom.. but w.e
tell what should i do... just leave it till i get a solution?
o7hafiz said:
so thats it.................. i just leave it like that......... trash that fone? lol
that radio was a mistake.. i didnt read that name.. i thought it was for g1's htc rom.. but w.e
tell what should i do... just leave it till i get a solution?
Click to expand...
Click to collapse
Depending on how long you've had the phone, if it's been less than a year, you could call T-Mobile and say something to the affect of, your phone said it needed to reboot to apply an update and now it's stuck on this screen etc.. etc.. , and they would probably issue you a replacement, however if you get caught doing this, they could charge you an additional fee, and this is probably considered an insurance scam, you can decide what you'd like to do on your own, I just wanted to throw that little disclaimer in
nice to you find such matter funny.
anyhow ... i press and held the track ball and hit power button.. the blue like came out and the screen is black... O-o is that a good sign?
please help guys
Trackball does nothing but put it into "blue light mode", the ones you need working are home+power & camera+power. there are several pseudo solutions that claim to work even if these key combinations don't and perhaps they do for a few that are only softbricked. But, there are several hundred people with G1's in paperweight mode who'd beg to differ.
Alas, you've got alot of reading ahead of you, which could have been avoided had you done more reading in the first place :/
My suggestion, being that it seems you're fairly new, with a fairly new phone is follow jackslim's advice above and do alot more research next time...
thank you all of you...
ill go talk to T-mobile tomorrow see if they are able to help...=/
but i just wanned to show how the screen looks like
http://i27.tinypic.com/10rskyx.jpg
once again thanks for the advice
kinda odd tho. have you tried putting rc29's DREAIMG.NBH on the sd and holding camera+power...
Edit: then again, a hero radio on a "not hero" could definitely cause "odd"
oh and don't forget to atleast wipe your sd before going to t-mobile....

New Nexus Not Working

Hello,
I bought a Nexus one and as I don't live in a country that sells it my cousin brought it to me.
The device doesn't work and self Reboots giving me 20 seconds of use.
Tryed working with/without a sim,
Did a Factory Reset,
Formated the Sd-Card on my Pc,
and still in the same spot.
any ideas on what else to try before giving up?
anyone had this problem and fixed it?
My phone is not ROOTed and is on Version 1 of 2.1
didn't have enough time to get other info like Baseband and stuff.
I'm not willing to root the phone.
** If i send it back it will make the phone very expensive as i will have to pay costums fee when they mail it back to me
Thanks in advance!
Sounds like a DOA. Really bad luck.
If you send it back you should not pay duty to get it back usually, unless you live in a very tax hungry country! Between US and CAN you would not get duty.
Beside try speaking with cust support, DOA are usually well handled by company and so far HTC seem to be handling repair quite well as per the few post about broken screen I have seen.
Did you try running the phone WITHOUT an SD card ? good luck!
Krypton1984 said:
Hello,
I bought a Nexus one and as I don't live in a country that sells it my cousin brought it to me.
The device doesn't work and self Reboots giving me 20 seconds of use.
Tryed working with/without a sim,
Did a Factory Reset,
Formated the Sd-Card on my Pc,
and still in the same spot.
any ideas on what else to try before giving up?
anyone had this problem and fixed it?
My phone is not ROOTed and is on Version 1 of 2.1
didn't have enough time to get other info like Baseband and stuff.
I'm not willing to root the phone.
** If i send it back it will make the phone very expensive as i will have to pay costums fee when they mail it back to me
Thanks in advance!
Click to expand...
Click to collapse
If the boots, has never been rooted (boot unlock), no immediate physical damage, and has no signs of liquid damage or tampering (check void sticker).... it's likely just a software issue. Reload original firmware, or load a new firmware... Don't give up, sounds like the phone is still okay.
Was it bnib?
mrbkkt1 said:
Was it bnib?
Click to expand...
Click to collapse
So it seems.
Where are you from, Krypton1984 ?
Looks like some rogue app is loading at boot, causing reset. Possibly corrupt ROM image - but not sure. Might be software, might be hardware. But here's one thing to try:
If you're on a T-Mobile-compatible phone (900/1700/2100), do yourself a favor and flash stock Froyo. No need to root for that. The guide is in the sticky thread. In case of corrupted ROM image it'll do the trick.
I think you should factory reset it. Maybe even download the official 2.1 rom and install it. See if it fixes it.
Try a battery trade in first. Believe it or not, my first N1 seemed dead, and support gave me a swap for a new unit. When the new unit came in, it was still "dead" with the battery that originally shipped with the device. A new battery is what caused my N1 to finally come to life. The batteries that ship with N1's have QC issues, because I was one of many to report a DOA battery in the Google support forums.
its brand new,
I didn't pay customs on the way in because my cousin brought it to me, so if i send it back i will and it makes the phone very expensive.
what if when i try to change firmware the phone reboots again without finishing?
i dont want to brick the phone.
Krypton1984 said:
its brand new,
I didn't pay customs on the way in because my cousin brought it to me, so if i send it back i will and it makes the phone very expensive.
what if when i try to change firmware the phone reboots again without finishing?
i dont want to brick the phone.
Click to expand...
Click to collapse
Well booting to the bootloader will answer the hardware software question.
1. Turn off the phone.
2. Now press (and hold) the Trackball and turn on the phone.
Once you're in the loader let it sit for a while. If it stays up it's a software problem and a new ROM should sort it out. If it reboots while in the bootloader it sounds like a DOA phone.
Good luck.
You can also try a full factory reset through the bootloader. Search for the instructions as i do not know them off the top of my head
P00r said:
Between US and CAN you would not get duty.
Click to expand...
Click to collapse
Yeah, North America is all one big happy family. We've got NAFTA and everything now.
OP, I am assuming you've allowed the battery to charge full?
badomen said:
Well booting to the bootloader will answer the hardware software question.
1. Turn off the phone.
2. Now press (and hold) the Trackball and turn on the phone.
Once you're in the loader let it sit for a while. If it stays up it's a software problem and a new ROM should sort it out. If it reboots while in the bootloader it sounds like a DOA phone.
Good luck.
Click to expand...
Click to collapse
i am having a similar issue. The phone reboots randomly and gets stuck at the static X logo screen. i have to remove the battery and let it be aside for at least 10 minutes before i am able to get the phone up and running again.
i tried updating to froyo. it installed but then froze up again on reboot. i did the battery thing and then started it up, went on fine..froyo had been successfully installed, but my random reboot problem STILL DID NOT GO AWAY..
can this be sorted by installing the original rom image?? or do i have to go in for a swap?!?
i don't want to swap coz they send out refurbished devices,,but its the last option...
padhi87 said:
i am having a similar issue. The phone reboots randomly and gets stuck at the static X logo screen. i have to remove the battery and let it be aside for at least 10 minutes before i am able to get the phone up and running again.
i tried updating to froyo. it installed but then froze up again on reboot. i did the battery thing and then started it up, went on fine..froyo had been successfully installed, but my random reboot problem STILL DID NOT GO AWAY..
can this be sorted by installing the original rom image?? or do i have to go in for a swap?!?
i don't want to swap coz they send out refurbished devices,,but its the last option...
Click to expand...
Click to collapse
You'll probably need to swap based on what you're saying. I, though, actually think Refurbished devices are just as good or even better than new. Think about it, if you keep getting dust under the screen maybe a refurbished phone will already have the fix? For that scenario it works out.
padhi87 said:
i am having a similar issue. The phone reboots randomly and gets stuck at the static X logo screen. i have to remove the battery and let it be aside for at least 10 minutes before i am able to get the phone up and running again.
i tried updating to froyo. it installed but then froze up again on reboot. i did the battery thing and then started it up, went on fine..froyo had been successfully installed, but my random reboot problem STILL DID NOT GO AWAY..
can this be sorted by installing the original rom image?? or do i have to go in for a swap?!?
i don't want to swap coz they send out refurbished devices,,but its the last option...
Click to expand...
Click to collapse
I really think this is a bad RAM issue.
I had this happen to my Nexus (ATT). It was prior to flashing froyo. I tried everything, flashing back to stock (including radio), cyan's latest, Paul's (stock) Froyo (with and without radio). Same result. Seemingly random reboots.
I thought initially that it was a software issue - It would not reboot while in fastboot/Amon's Recovery. But having tried every software combination, I've concluded that it MUST be hardware, unless I'm missing something big.
The phone, for the most part, would be fine as long as I DON'T TOUCH IT. It would stay idle for a long period of time (24hrs+), then I would use it Everything from web browsing to downloading apps to making calls, and it would reboot. It's frustrating because it seems that it's rebooting for no reason except that I'm touching it.
Sent in for a replacement, it arrives today. Hopefully it will not suffer this problem.
After talking with HTC they told me i need to swap the phone.
Because i'm out of america i need to send it to someone in the US amd then they send him the new divice after he sends my old one,
I am not satisfide with google's (first guy I talked with) and HTC because none of whome understand the severity and the hard feeling of getting a BRAND NEW IN BOX paper-weight. nothing about we'll compensate you or nada.
For me it tells me the brand is not strong enough to manage an outer state service and i wouldn't recomend them for countries that they don't cell it for.
If you where born in a HTC GOOGLE compatible country enjoy!
As i'm am probably less lucky and still in 2010 nationality counts

Nexus One boot problem (freezing)

I received a Nexus One yesterday. First it worked for around 5 min, then rebooted by itself. From then on I never got into the system. If i turn it on normally, it freezes (or loops) at X logo. I have no problem reaching FASTBOOT and BOOTLOADER. But when I try to go to recovery, sometimes I can get to it, sometimes not (freezes at X also, or the screen is completely black so I need to pull out the battery).
What is causing the problem? I also tried to flash recovery image, same result. As long I'm a newbie, I know nothing about radio, spl, kernel ... flashing and dependencies between each.
Is it possible that it is a hardware issue? If not, what can I do, wipe, flash, etc...?
In desperate need of help... Tnx
I had exactly the same situation with my first N1. I called HTC and returned it as a defective device. My replacement device has been rock solid.
That being said, can you get into recovery Mode? (hold trackball down while powering on), if you can, try a factory reset and see if you can boot then.
Yea sometimes i can get to recovery mode. Usually when the battery is out for a while. I tried also with the factory reset, no success.
I write this problem here thinking there may be a solution (like flashing everithing...), but the problem is I know very little about all the stuff such as kernel, rom, radio, etc.
Any advice besides returning to HTC? Because I have no warranty.
You describe my problem exactly. It was a hardware problem and I returned my device to HTC.
It sounds like the same problem i have.
Looks something like this ?
http://www.youtube.com/watch?v=_bIfvl6Cuts
DvTonder said:
You describe my problem exactly. It was a hardware problem and I returned my device to HTC.
Click to expand...
Click to collapse
This is happening to my N1 quite often, it seems stable now and doesn't happen often. I am guessing it has defective RAM or something.
The important part of this is how long did you take to get your device back as I see you are also in Canada, this is why I am not sending it in also, I know they are pretty good about honouring the warranty after root if it is hardware but I don't want to send it in for nothing if it is not that bad.
I have started using a 950mV kernel, this seems to have helped. Try one out OP.

[Q] Hard-Bricked G1

Hi there,
I fear I hard bricked my G1 (after long years of good service as gps device thanks to a 2600mAh battery).
Since it was quite slow on CM7, I downgraded it to CM6.1. But this would'nt boot. (boot loop)
So I did a bit of reading and decided to downgrade the radio too. I downloaded a flashable zip and flashed it the usual way in the CWM recovery - which didn't finish (after a few minutes), so I removed the battery.
Since then my G1 wont start any more. On top of that, it want event charge. If I try to charge it the status led wont event light up. (I already tried it with two different batteries, both yield the same results.)
Funny thing though: If I don't charge it and let it sit for a few hours, the status LED very shortly lights up when pressing the power button. (But other than this nothing happens and if I press the power button again shortly after the LED stays dead.)
So ... I fear the problem is hardware and not software related.
Does anybody have an idea what could be broken (software or hardware) and if it's software based if there's a way to revive my phone?
(Before anybody asks ... yes, I have newer android phones, but I really live my G1 for nostalgic value so if there a way to get it running again I definitely would try.)
thx a lot,
Bapf
Sounds like you need JTAG, and don't take this the wrong way, but flashing firmware isn't the usual way, its the way you brick your phone. If possible always use fast boot to flash firmware or you are asking for a brick.
You can buy the JTAG equipment yourself and the software is free. Or you can see if you can find someone locally to do it. Unless you have a particular sentimental value to this phone it maybe cheaper to buy a new one.... Sorry for bad news
Sent from my Nexus 7 using xda premium
Bricked G1 - Try Again w/ SIM Card IN!
I had the exact symptoms mentioned in this post - tried nearly everything until I finally put back in the SIM card (even through I don't have T-Mobile anymore) - it booted again and registers the AC adapter and/or USB cable. Hope this helps some who are struggling at this level as I did!!
Bapf said:
Hi there,
I fear I hard bricked my G1 (after long years of good service as gps device thanks to a 2600mAh battery).
Since it was quite slow on CM7, I downgraded it to CM6.1. But this would'nt boot. (boot loop)
So I did a bit of reading and decided to downgrade the radio too. I downloaded a flashable zip and flashed it the usual way in the CWM recovery - which didn't finish (after a few minutes), so I removed the battery.
Since then my G1 wont start any more. On top of that, it want event charge. If I try to charge it the status led wont event light up. (I already tried it with two different batteries, both yield the same results.)
Funny thing though: If I don't charge it and let it sit for a few hours, the status LED very shortly lights up when pressing the power button. (But other than this nothing happens and if I press the power button again shortly after the LED stays dead.)
So ... I fear the problem is hardware and not software related.
Does anybody have an idea what could be broken (software or hardware) and if it's software based if there's a way to revive my phone?
(Before anybody asks ... yes, I have newer android phones, but I really live my G1 for nostalgic value so if there a way to get it running again I definitely would try.)
thx a lot,
Bapf
Click to expand...
Click to collapse
I don't know if this will work,as I've never encountered a situation such as this, but have you tried bootloader(power button+camera button)?
If you can get it into bootloader, then I have the original rc29 DREAIMG.NBH file(plus, rc29 is the best place to start if you want to root it or install a custom rom).If you get it working and just want stock 1.6, i have those updates as well.
(all said out of hope, I have a g1 and I love it,I'm really glad that someone else shares my enthusiasm!!)
If bootloader works, give me your email and i'll send you the files, good luck!:fingers-crossed:
Nope. It won't even start the bootloader.
Sent from my Nexus 4 using xda app-developers app
Well thats unfortunite, I guess it's just for a soft brick.

Question Tab S8+ (SM-X806B) acting weird

So 2 days ago i made a deal for a S8 plus tablet. Second hand but as good as new. Not even a scratch. First impressions were great, model and serial numbers matching (SM-X806B). Came home happy.
Then, at 40% batery, i turned on economic mode. SOme time later i noticed a vertical stripe always on the right corner, everytime the screen moved, like a vsync problem. It seens to appear only when refresh rate goes down to 60Hz, instead of 120Hz default.
So i soft reseted and found out that, when shutting down, the tablet show some command line like a Linux distro. When booting up, it shows a debug panel beside the android/samsumg logo, with some of the hardware info. Now i'm also noticing random red flashing on all the edges of the screen, like when it's loading something.
did a factory reset, and some of the samsung aplications would not install, saying it mismatched signature... Can't update android either through the settings menu. Google apps works fine.
Finally, even after the factory reset, the dev's options were already unlocked, with some apps like IOThidenmenu on the app screen.
So, do you guys know why is this happening? Is this hardware /android version a test model? If so, is there a way to rewrite it to a customer mode?
I don't want to keep a expensive time bomb in my hands.
Thank you all
You can flash the latest full firmware and see what happens. Click the yellow How To Guide quick filter at the top of the list of threads in this section, then you'll see one of the first threads is for rooting. You don't have to root, or even unlock the bootloader, so skip anything about that. You just want to use SamFirm or Frija to download the latest firmware, and then use Odin to flash it to your tablet.
So, in the meantime, the tablet was completely off for almost 20 days due to myself sleeping while watching youtube crap and not having a proper charger. Found out that usb (common) can't jump-start it once it shuts down. Was waiting for Amazon deliver a original charger, as in here knockoffs are rampant...
About the red flashing edges: ive noticed it only happens when the tablet is upside-down from the vvertical perspective (usb up). Still dont know why, but at least i know what not to do.
About the screen tearing: gone. Dont want to know why. Leave it there.
Still cant update 99% of galaxy store related apps and cant do ota update. Funny thing is hardware diagnostic apps like antutu, geekbench, cpu-z won't precisely tell me about the hardware in it. Some would say its another soc (snap dragon 440!) While identifying the adreno 730. Others wont show the android version correctly... Some will it's rooted while others not. Crazy stuff. It's clearly is, at least, a tab s7+, even if it had a customized rom to fool people. But its not. 8gb of ram, samsung's test app and the serial number all but confirm it is a sm-806b.
So, looking more deeper into it, i found this:
from this info, it (sort) can be established that:
It from november 2021, Austria, binary category 0.
A test model. And it arrived in south america somehow.
What would you do? Sell it for 3x times the price on ebay or try to overwrite the firmware so you could update and make use of AR camera bull****?
Jokes aside, can i overwrite the firmware with a american version without bricking it? My sim cards works fine as it is now, but i suspect that even with a recent EUX, i wont be able to update galaxy store apps due to geolocalization.

Categories

Resources