Related
Never been rooted. My phone froze so I took out the battery and when I turned it back on, the phone was stuck on the boot logo. I've entered into the hboot menu by holding down the down volume key + power. I selected "Factory Reset " but it does nothing. I also tried selecting "Recovery Mode", which makes some green arrows appear, then the phone vibrates about 6 times in a row and goes blank.
Can I load a ROM or something to save the phone?
I also tried removing the SD card when booting, plugging the phone into the PC, etc. Nothing.
Running Gingerbread 2.3.4
I've never rooted or anything but I can follow directions if there's a way. Thanks a lot for reading.
Oh, and when I plug the phone into the computer, it appears to create a drive letter in My Computer, but when I click the drive, it doesn't open.
Should I just warranty out this phone or is there any hope? thanks.
confirm your sd card is good first.
flash your phone with the rom you like.
I think it will be ok after you flash it.
RussianSpring said:
Never been rooted. My phone froze so I took out the battery and when I turned it back on, the phone was stuck on the boot logo. I've entered into the hboot menu by holding down the down volume key + power. I selected "Factory Reset " but it does nothing. I also tried selecting "Recovery Mode", which makes some green arrows appear, then the phone vibrates about 6 times in a row and goes blank.
Can I load a ROM or something to save the phone?
I also tried removing the SD card when booting, plugging the phone into the PC, etc. Nothing.
Running Gingerbread 2.3.4
I've never rooted or anything but I can follow directions if there's a way. Thanks a lot for reading.
Click to expand...
Click to collapse
Goto the glacier forum. Download the factory img file found in the rooting topics. Boot into recovery and let it flash completely. Should be good.
Or... U have a bad emmc and it is toastito's...
How do I flash the phone once I boot into recovery? do I drag and drop the IMG file somewhere on the SD card?
Sorry for the noobness.
When I plug the phone into the PC, a drive letter appears in My Computer - but nothing happens when I click it. Once I put it in recovery, the drive letter disappears.
How would I go about flashing if I don't have access to the files on the SD card?
Okay I got access to my SD card by plugging my SD card into a different phone then the computer.
There is no root folder available when doing it this way - so where would I install the flash file to?
**** never mind, I get what they mean by root...sorry, I'm retarded *****
I think I got it, I'll give this a try.
Okay. All it does is in Hboot, it checks and loads PDIMG15.ZIP, but then it just takes me back to the Hboot menu and the phone is still stuck on the boot screen.
it says...
"SD Checking PD15IMM.ZIP
No image or wrong image!"
Then reverts back to Hboot menu. Tryed formatting the SD card. Will try a different SD card next.
Different 8gb SD card = same results. No image or wrong image.
Appreciate it if anyone has a fix on this.
If anyone else is having this issue, I found a solution:
Go to T-Mobile and buy a SG2.
Problem solved.
This is supposed to a big Android site? thanks for nothing, guys!
I ended up just getting a new phone. Appreciate no one helping. Awesome awesome.
RussianSpring said:
This is supposed to a big Android site? thanks for nothing, guys!
I ended up just getting a new phone. Appreciate no one helping. Awesome awesome.
Click to expand...
Click to collapse
Actually you are in the general section question and answers. There is an Android Section Questions and Answers, and better than that...wait for it...A MYTOUCH 4G QUESTIONS AND ANSWERS!!! Imagine that!! Im quite sure you would have gotten the answers you needed had you done a little searching and posted in the correct spot. Good luck with your new phone!
Maybe someone could of directed me there sooner? This site is confusing if it's your first time.
I know this is free...just saying. My post got a lot of views but almost no response.
Whatever. It's all good...thanks for replying.
Etrick said:
Goto the glacier forum. Download the factory img file found in the rooting topics. Boot into recovery and let it flash completely. Should be good.
Or... U have a bad emmc and it is toastito's...
Click to expand...
Click to collapse
This is a great site. This is/was your Answer!
Sent from my MB855 using xda premium
RussianSpring said:
Maybe someone could of directed me there sooner? This site is confusing if it's your first time.
I know this is free...just saying. My post got a lot of views but almost no response.
Whatever. It's all good...thanks for replying.
Click to expand...
Click to collapse
There is a search bar ...there is forums..... each forum sorted out bu the phone you have each of those forums having subforums to "general Q&a development" and so on.... my question is if you didnt have it rooted why not just take it to the store directly??? Problems like that will asure new a new phone regardless....
Just my 2 cents
oh and this is an amazing site....
rooted 100's of phones with out ever joining and ive finally joined
....crazy how the search bar takes you long ways
Ok here it is in short bullet points to make a short story
tf300t rooted
rom hydro 4.1
Screen got broke
wife bought the wrong one .69.104 something like that about 40 bucks
wife bought the right one 59 or something like that about 90 bucks
I installed it
now 99% of the time the screen is not working at most i can get the task bar(I guess its called) at the bottom to work. So 1% of the time i can get the back, home, i will call it recent active, and the stuff over on the right by the clock but say i do get in to setting i then have to use my keyboard after that. I was thinking about factory resetting but i can not even seem do to that it just sits at the asus screen with the text in the top left saying my device is unlocked.
I am so lost in whats going on. any help would be great. at this point if someone could help me I will donate to them, a project of their choice and of course the site XDA.
Since you are running a custom ROM I expect you to have an unlocked bootloader? OK you can try reflashing the stock firmware follow this guide:
http://forum.xda-developers.com/showthread.php?p=39272826
I know it is for downgrading but you can reflash with this method as well also make sure you flash the right things and this WILL WIPE EVERYTHING
Sent from my TF300T using xda app-developers app
OK thank you I will try that right now thank you very much.
So I got all the files and stuff i remembered doing this to root my table back a few years ago. But I am getting hung up on while trying to select the USB icon. When I volume down and power it boots the the pre-loader screen i guess its called. But I can not select anything or try and move the selector it freezes. It i get to the pre-loader screen and wait the 10 seconds the tablet will then just boot up normally. Have any Ideas ?
says "booting recovery kernel image"
Update
I am able to move it over to the USB icon but it freezes. Says "starting fastboot download protocol".
(My screen says "press vol down to select and press vol up to select move") that wrong atless the way I read it.
I also the touch screen worked for a bid 30 seconds but then a error popped up that I seen before but forgot to post its like dmc failed. but any ways its not 6am and I still have not slept sorry if I lost you I might not be fully awake,
joker66599 said:
So I got all the files and stuff i remembered doing this to root my table back a few years ago. But I am getting hung up on while trying to select the USB icon. When I volume down and power it boots the the pre-loader screen i guess its called. But I can not select anything or try and move the selector it freezes. It i get to the pre-loader screen and wait the 10 seconds the tablet will then just boot up normally. Have any Ideas ?
says "booting recovery kernel image"
Update
I am able to move it over to the USB icon but it freezes. Says "starting fastboot download protocol".
(My screen says "press vol down to select and press vol up to select move") that wrong atless the way I read it.
I also the touch screen worked for a bid 30 seconds but then a error popped up that I seen before but forgot to post its like dmc failed. but any ways its not 6am and I still have not slept sorry if I lost you I might not be fully awake,
Click to expand...
Click to collapse
this means you are on 4.1? it's normal the bootloader freezes when selecting usb icon then you need to flash the firmware
Your issue might be as simple as reflashing the touch pcb with the proper firmware as it also calibrates it. Since you are running a custom rom, all you need to do is download a terminal emulator. You dont need to use a computer at all. I'll walk you through it if you need. I originally had the 5158n. Flashed the touch board with g01 firmware, installed the new digitizer (g01)and it had the same symptoms as you described. I then reflashed with the digitizer connected and viola..... new g01 screen was working perfectly! 5158n was like 100 usd. G01 was only 44 shipped. Big difference!
If you need help, just pm me here and ill give you my gtalk.
Sent from my SGH-T889 using xda app-developers app
ok now that I have had a little nap I usb icon does freeze but i watched videos and mines the same as theirs but fastboot devices does not come up with any devices.. I will look in to this firmware update not sure how to do it. Sorry like i said I have not kept up on this stuff. After this problem I will be visiting the site a lot more.
joker66599 said:
ok now that I have had a little nap I usb icon does freeze but i watched videos and mines the same as theirs but fastboot devices does not come up with any devices.. I will look in to this firmware update not sure how to do it. Sorry like i said I have not kept up on this stuff. After this problem I will be visiting the site a lot more.
Click to expand...
Click to collapse
Is it still booting into the rom though? What bootloader / recovery are you using ( or which ones were you trying to flash ). Do you have a dock with keyboard / touchpad?
Also, what do you see when you enter the bootloader. Which icons? Depending on the bootloader, you may already be in fastboot mode as soon as it opens the bootloader menu.
Also fyi, you use the volume buttons for navigating through the options. Not keyboard / touch screen.
Volume down toggles the options, volume up selects and enters the mode you chose.
BEFORE flashing a rom though ( provided you are still booting to a rooted OS ), try forcing the new firmware to the touch pcb board.
Sent from my SGH-T889 using xda app-developers app
This is going to sound dumb Not sure of the name of the bootloader I have 4 icons RCK, android, usb, wipe data.
I do have a dock and table works fine besides that error i get in the settings some times dcm something or dmc something it pops up and gos away pretty quick.
I can also get into TWRP 2.6.6.6
So yeah the system it fine right now its just the touch screen that I am missing.
joker66599 said:
This is going to sound dumb Not sure of the name of the bootloader I have 4 icons RCK, android, usb, wipe data.
I do have a dock and table works fine besides that error i get in the settings some times dcm something or dmc something it pops up and gos away pretty quick.
I can also get into TWRP 2.6.6.6
So yeah the system it fine right now its just the touch screen that I am missing.
Click to expand...
Click to collapse
What version is your touch screen? Also, did you make sure to flip off the little service switch and pull the battery connector before disconnecting the bad digitizer? If not, you probably fried the coil ( small fuse ) on the motherboard.
Sent from my SGH-T889 using xda app-developers app
fuse damn no did not see or read anything about it when researching how to replace the screen. hmm I am stumped this is getting to be a nightmare. Weird thing happened again last night the touch screen started working again almost the full screen only thing I was not able to click on was the app draw thing in the top right corner but then it stopped about about 30 seconds. In worst case is there a place I can mail/take my tablet to?
joker66599 said:
fuse damn no did not see or read anything about it when researching how to replace the screen. hmm I am stumped this is getting to be a nightmare. Weird thing happened again last night the touch screen started working again almost the full screen only thing I was not able to click on was the app draw thing in the top right corner but then it stopped about about 30 seconds. In worst case is there a place I can mail/take my tablet to?
Click to expand...
Click to collapse
Did you reflash firmware yet ?
Sent from my SGH-T889 using xda app-developers app
like the rom?
Looking firmware flash up right now.
nm guessing you are talking about the asus firmware updates from the asus site I am doing that now.
Updating as i type this 114 updates not sure if thats real updates or its just reflashing/installing the ones i had before
update installed fresh firmware still no touch screen I am now unrooted too i belive.
joker66599 said:
like the rom?
Looking firmware flash up right now.
nm guessing you are talking about the asus firmware updates from the asus site I am doing that now.
Updating as i type this 114 updates not sure if thats real updates or its just reflashing/installing the ones i had before
update installed fresh firmware still no touch screen I am now unrooted too i belive.
Click to expand...
Click to collapse
No..... its specifically the touchpanel firmware. Flashing new firmware not only writes the drivers for the touch panel, but it also calibrates things in the process. What ROM / Recovery / Bootloader do you have right now? Are you rooted? Also, I asked you before.... what model screen did you order? ( G01 , G03 , 5158N, Etc ) I need to know this so I can help you get the right firmware for your panel.
Sent from my ASUS Transformer Pad TF300T using xda app-developers app
pyraxiate said:
No..... its specifically the touchpanel firmware. Flashing new firmware not only writes the drivers for the touch panel, but it also calibrates things in the process. What ROM / Recovery / Bootloader do you have right now? Are you rooted? Also, I asked you before.... what model screen did you order? ( G01 , G03 , 5158N, Etc ) I need to know this so I can help you get the right firmware for your panel.
Sent from my ASUS Transformer Pad TF300T using xda app-developers app
Click to expand...
Click to collapse
I have the 5158n I not no longer rooted so If needed I can reroot. with what ever you say will make it easiest. When i flashed the firmware it unrooted didn't know it was just touch panel firmware i should have done.
joker66599 said:
I have the 5158n I not no longer rooted so If needed I can reroot. with what ever you say will make it easiest. When i flashed the firmware it unrooted didn't know it was just touch panel firmware i should have done.
Click to expand...
Click to collapse
I uploaded the factory firmware to my dropbox for you.
This is the G01 firmware - https://dl.dropboxusercontent.com/u/37729675/02-3011-4820.ekt
This is the 5158N Firmware https://dl.dropboxusercontent.com/u/37729675/04-3021-7053.ekt
Go to settings, about , and tap the touch panel version about 10 times very fast. It should open up a special firmware window and ask you what file you want to flash. Navigate to where ever you saved the file to and select it. If it works, do not touch anything until its finished. Its trying to calibrate things and touching the screen will mess it up.
You can change from the broken 5158N to a G01 this way as well. Its MUCH cheaper ( And what I did with success ). 5158N = $100 USD. I only paid $43 USD for the G01 and had zero problems with it.
If you cant get to the update firmware screen, you can also try tapping the camera version about 10 times very fast as well.
Lastly, the easiest way is to root the tablet. Then download a terminal app. gain root ( type su in the box, hit enter, and press allow root permissions when it pops up ). After your terminal window has root, type this command without quote "touch_fw_update -u /location/of/your/file/here.ekt" . I flashed the firmware right from my etc/firmware directory, and I flashed the G01 firmware. My command looked like this "touch_fw_update -u /system/etc/firmware/touch/02-3011-4820.ekt"
DO NOT touch anything until its done doing its thing. It calibrates things and pressing the screen will mess it up. It takes about 3 minutes to complete.
If everything flashes correctly, and you still have no touch input, you might have fried the coil on the mainboard. If that's the case, you will need to break out a soldering iron and bridge it.
PS
If Ive helped, don't forget to hit thanks
Edit:
I saw that there is another firmware for the 5158n than I have posted. The other reference is to a 4822, but Im not seeing that anywhere. Hopefully the 7038 works for you though.
pyraxiate said:
I uploaded the factory firmware to my dropbox for you.
This is the G01 firmware - https://dl.dropboxusercontent.com/u/37729675/02-3011-4820.ekt
This is the 5158N Firmware https://dl.dropboxusercontent.com/u/37729675/04-3021-7053.ekt
Go to settings, about , and tap the touch panel version about 10 times very fast. It should open up a special firmware window and ask you what file you want to flash. Navigate to where ever you saved the file to and select it. If it works, do not touch anything until its finished. Its trying to calibrate things and touching the screen will mess it up.
You can change from the broken 5158N to a G01 this way as well. Its MUCH cheaper ( And what I did with success ). 5158N = $100 USD. I only paid $43 USD for the G01 and had zero problems with it.
If you cant get to the update firmware screen, you can also try tapping the camera version about 10 times very fast as well.
Lastly, the easiest way is to root the tablet. Then download a terminal app. gain root ( type su in the box, hit enter, and press allow root permissions when it pops up ). After your terminal window has root, type this command without quote "touch_fw_update -u /location/of/your/file/here.ekt" . I flashed the firmware right from my etc/firmware directory, and I flashed the G01 firmware. My command looked like this "touch_fw_update -u /system/etc/firmware/touch/02-3011-4820.ekt"
DO NOT touch anything until its done doing its thing. It calibrates things and pressing the screen will mess it up. It takes about 3 minutes to complete.
If everything flashes correctly, and you still have no touch input, you might have fried the coil on the mainboard. If that's the case, you will need to break out a soldering iron and bridge it.
PS
If Ive helped, don't forget to hit thanks
Edit:
I saw that there is another firmware for the 5158n than I have posted. The other reference is to a 4822, but Im not seeing that anywhere. Hopefully the 7038 works for you though.
Click to expand...
Click to collapse
ok cool i hope this works i am in the about and under touch panel it says elan-3011-4822 crossing figures.
joker66599 said:
ok cool i hope this works i am in the about and under touch panel it says elan-3011-4822 crossing figures.
Click to expand...
Click to collapse
That it says 4822 doesn't mean it'd work out of the box. Even if you have the correct firmware, you'd need to reflash it every time you replace the digitizer. Once in a while it would update the firmware on its own, but most of the time you'd need to do it. Good luck.
graphdarnell said:
That it says 4822 doesn't mean it'd work out of the box. Even if you have the correct firmware, you'd need to reflash it every time you replace the digitizer. Once in a while it would update the firmware on its own, but most of the time you'd need to do it. Good luck.
Click to expand...
Click to collapse
Absolutely. I know Joker66599's screen shows it having 4022 firmware, but from what I read, the 5158N also uses the 7038 firmware. Not sure which is newer though. I checked in the factory firmware folder and didnt see 4022 in there.
Weird I can not find the file .ekt when in the camera firmware screen. I can not go in using the touch panel selection. Even it I select the directory the file is in I get an error. I have the file you provided in several places just to try for ****s and giggle (root, sdcard/thechive, and sdcard/boat browser/downloads). I will post that error message in a bit.
I never rooted or unlocked the bootloader, not sure what's up. I had a 32gb SD card in it if that matters.
Anyone know what I could try and do?
Try to flash stock from fastboot, maybe something on your system has been corrupted... Are you rooted or bootloader unlocked?
thegunrun said:
I never rooted or unlocked the bootloader, not sure what's up. I had a 32gb SD card in it if that matters.
Anyone know what I could try and do?
Click to expand...
Click to collapse
You can try to recover to the recovery image.
https://developer.nvidia.com/sites/default/files/akamai/mobile/shield/HowTo-Flash-Recovery-Image.txt
You can find the boot, system and recovery .img's here
http://forum.xda-developers.com/showthread.php?t=2388870
The blob and tegra114-roth here
https://drive.google.com/?authuser=0#folders/0B7j6Imwr_sirRnl5MFRRR2sxRWM
I would upload the userdata.img, but it's too big for me to upload, and I don't think it is needed...
Guys, the OP mentioned that he has not unlocked/rooted his device, so he cannot flash the recovery image.
That should definitely not happen on an unlocked device. Can you at least see the splash animation? Things to try (in that order):
1) On the boot splash animation, connect SHIELD to your PC and try to run "adb logcat" to see if you can see what is crashing. Attach the log here if you can get it.
2) If you cannot use adb, reboot your SHIELD while holding the back and home buttons. This will bring you to the bootloader menu. Then connect to your PC and try to "fastboot erase userdata" and "fastboot erase cache" before doing "fastboot reboot". This will remove all your user data, so your SHIELD should boot again correctly provided the OTA went without any issue. You might not like the idea of losing your user data though.
3) Contact NVIDIA. You have not unlocked your SHIELD, just did a regular OTA. This is covered by the warranty so they should be able to help you.
Gnurou said:
....That should definitely not happen on an unlocked device. Can you at least see the splash animation? Things to try (in that order):....
Click to expand...
Click to collapse
Fixed that line for you.
If the device is locked getting Nvidia to fix the software should not be a problem.
I had the same problem. NVidia swapped out my Shield with a retail refurbished unit.
Happened to me but I shut it down using the nvidia button and let it sit for a few minutes and it booted.
Hit thanks if I helped you out. Doing a little bit of reading goes a long way. Sent via tapatalk.
i have got the same problem
its impossible to boot in 4.3. the only few times i got it, it tooks 10 ton 15 minutes
i go back to 4.2 and i had the same problem. the only way to get the shield back to normal is to format all (system, data, etc..) through cwmr
when i trie to update to 4.3 trought ota, i got the same problem and i have to repeat the proccess again to come back to 4.2
in 4.2 boots ok, and everything works, but i cant update
any ideas?
My boot-up problem seemed to have been caused by my 64GB SanDisk MicroSD card. When I pulled it out to transfer it to my replacement Shield, the original came up. Try pulling out your SD card before powering on if you are still having trouble.
jdsemler said:
My boot-up problem seemed to have been caused by my 64GB SanDisk MicroSD card. When I pulled it out to transfer it to my replacement Shield, the original came up. Try pulling out your SD card before powering on if you are still having trouble.
Click to expand...
Click to collapse
hi, i tried to boot without the sd and i get the same result
stock in boot logo
i thing the problem its something related with the ota update an my boot.img
someone has access to boot, system and recovery img from update 63?
maybe if i install from bootloader i get something
thanks in advance
If you power on holding back and home, you will boot into a menu. If you go into Recovery, do you get any options? On mine, it would say "No Command" and be stuck there. If yours also says "No Command", you can't really load anything using recovery.
You should consider going here. You'll have to either login or create a login, but after that, you can submit your problem to NVidia. That's what I did, and they shipped me a new unit overnight with a prepaid label to send my unit back.
Hi, Thanks for your answer. Im able to update the shield throught fastboot. This is hoy i can downgrade from 4.3 to 4.2.
Moreover ,i cant get a new unit, cause i live in spain, (and i already unlock my bootloader)
cg_gm said:
Hi, Thanks for your answer. Im able to update the shield throught fastboot. This is hoy i can downgrade from 4.3 to 4.2.
Moreover ,i cant get a new unit, cause i live in spain, (and i already unlock my bootloader)
Click to expand...
Click to collapse
good news!!! last update (64) solve the problem. now im in 4.3 and all is working ok
thanks for your help, hope thath nvidia dont mess up with the updates again
After receiving my UL28N2 Joying head unit i managed to get root on the device according to this tutorial: http://forum.xda-developers.com/showpost.php?p=69648860&postcount=84
I bought this unit to be able to use Tom Tom on it. After first trying to install it failed and it says it was not able to get any connection to the Tom Tom service.
After that i found this tutorial to change the serial number and run Tom Tom: http://forum.xda-developers.com/and...lmight-tomtom-problem-solved-fw-mtcd-t3471075
It failed to install xposed framework. As last i wanted to installt he newest version of xposed found here: http://forum.xda-developers.com/showthread.php?t=3034811
I installed the xposed version and gave it root access to install the latest framework. From there it went wrong.
The device restarted and i saw the android logo (the green doll) after that the device rebooted again and now i am stuck at the android logo (white one).
I am able to get into recovery, used this tutorial for it: http://forum.xda-developers.com/showpost.php?p=69936773&postcount=4
Am i able to recovery it and how can i do this? I tried to copy the latest update from Joying to an usb stick and put the stick in when i am into recovery but nothing happens.
Hopefully one of you guys can help me with this.
Afaik there was no xposed available for the Intel units.
Try on the sdcard1 or the usb1. System should detect a new update
Enviado desde mi D6603 mediante Tapatalk
ikerg said:
Afaik there was no xposed available for the Intel units.
Try on the sdcard1 or the usb1. System should detect a new update
Enviado desde mi D6603 mediante Tapatalk
Click to expand...
Click to collapse
What exactly do you mean?
I tried to put the latest update on a usb stick and stick it in the device, boot into recovery but it does nothing.
Trying to start android with the usb stick attached does neither work.
I meant that ROm updates usually work only over sdcard1 or usb1...but if you tried....
Once booted into recovery can you select the option to restore/update from file?
Which options do you have?
Are you expecting that update file to be detected and installed automatically or did you try to navigate through the recovery options to update?
Enviado desde mi D6603 mediante Tapatalk
I do not see any options to select
Tried to follow this tutorial: http://forum.xda-developers.com/showpost.php?p=69936773&postcount=4
I made some pictures of what i see when i follow the tutorial.
First i see the android doll with some Chinese text without! and after a second i get another message with ! at the end.
I can press the home button and i get some red text with Error, wait here... or something like that.
I want to remove the xposed framework, after that android will run again.
I got a solution. Download the latest update from the joying website: https://www.carjoying.com/Joying-blog/59.html
Copy it to a usb stick that has been formatted as FAT32 and put it in the usb outlet that comes at the same side as the wifi antenna goes out.
Apply power and press the reset button. The device will so the same routine as updating. Wait for 20 minutes and it works again.
Perhaps this can help us further, if you don't damage the boot image you can always flash a new ROM with that usb port.
I had tried this same thing on Intel unit, let xposed framework pick which version, it got stuck on white android logo forever. I found putting my sdcard with the update files would work also without a keyboard. If I cut power to it and it failed to boot 3 times , on the fourth try it would show my car logo and in red letters underneath something like "failed to boot systemui after many attempts!" At that point it automatically searches sdcard or usb for the factory image to flash.
I too tried everything for tomtom go, but no success
Skater4599 said:
I had tried this same thing on Intel unit, let xposed framework pick which version, it got stuck on white android logo forever. I found putting my sdcard with the update files would work also without a keyboard. If I cut power to it and it failed to boot 3 times , on the fourth try it would show my car logo and in red letters underneath something like "failed to boot systemui after many attempts!" At that point it automatically searches sdcard or usb for the factory image to flash.
I too tried everything for tomtom go, but no success
Click to expand...
Click to collapse
If it does not work, I have a solution, send me a message
Cr4zyMan said:
If it does not work, I have a solution, send me a message
Click to expand...
Click to collapse
Can you help me? My android head unit being stuck at boot
hackergacon9x said:
Can you help me? My android head unit being stuck at boot
Click to expand...
Click to collapse
yes i can (joying head unit).
download the latest joying version from hare: https://www.carjoying.com/blog/joying-head-unit-after-sale-support/59.html
Extract all files to SD card (or USB Card).
Remove the power from the head unit
Connect the SD card to the head unit
Press the power button, connect the power (Do not leave the power button until you see any icon).
Cr4zyMan said:
yes i can (joying head unit).
download the latest joying version from hare: https://www.carjoying.com/blog/joying-head-unit-after-sale-support/59.html
Extract all files to SD card (or USB Card).
Remove the power from the head unit
Connect the SD card to the head unit
Press the power button, connect the power (Do not leave the power button until you see any icon).
Click to expand...
Click to collapse
My head unit that I buy is made in China. The hardware is like joying. I updated the android version 6.0 of joying, now my head has a "UI does not match" error, overlay screen and wrong resolution. Functions like radio, music ... working normally Can you downgrade to stock android 5.1.1? Can you please fix this bug or downgrade?
i have an erisin device, but when i was stuck on android logo, i had to reboot device and pull out both SD CARDs!
Afterwards it could boot into the system
hackergacon9x said:
My head unit that I buy is made in China. The hardware is like joying. I updated the android version 6.0 of joying, now my head has a "UI does not match" error, overlay screen and wrong resolution. Functions like radio, music ... working normally Can you downgrade to stock android 5.1.1? Can you please fix this bug or downgrade?
Click to expand...
Click to collapse
Did you fix this?
Hello,
is there any possible way to flash the MCU config blind?
I did the mistake and changed the customer version in the advanced settings and now my screen stays completly black.
After applying the settings the Unit shut down and never came back.
I searched the forum for 2 hours now but couldn't find anything helpful.
i think i can enter the recovery but as the screen never turns on i cant see what i'm doing.
Device Infos:
Eunavi PX5 device with MTCE_LM_3V.06bd MCU
Android 9
Thank you very much
hopefully you did an export of your pre-existing settings. these export to a dmcu.cfg file.
if you put this on an sd card and re-update mcu via recovery. it will restore the working configuration.
I have my settings get buggered from time to time (especially when I change roms) and a backup of my MCU config saves me regularly.
Another option that has worked for me in the past is to swap MCU to another maker and back. This often resets the MCU config back to stock. As you are running LM MCU, flash HA or GS, and then Re-Flash your LM MCU.
Hopefully one of those will get you operating again.
Flashing with another MCU from another manufacturer don't brick the HU?
pir8man said:
hopefully you did an export of your pre-existing settings. these export to a dmcu.cfg file.
if you put this on an sd card and re-update mcu via recovery. it will restore the working configuration.
I have my settings get buggered from time to time (especially when I change roms) and a backup of my MCU config saves me regularly.
Another option that has worked for me in the past is to swap MCU to another maker and back. This often resets the MCU config back to stock. As you are running LM MCU, flash HA or GS, and then Re-Flash your LM MCU.
Hopefully one of those will get you operating again.
Click to expand...
Click to collapse
Knausepeter said:
Hello,
is there any possible way to flash the MCU config blind?
I did the mistake and changed the customer version in the advanced settings and now my screen stays completly black.
After applying the settings the Unit shut down and never came back.
I searched the forum for 2 hours now but couldn't find anything helpful.
i think i can enter the recovery but as the screen never turns on i cant see what i'm doing.
Device Infos:
Eunavi PX5 device with MTCE_LM_3V.06bd MCU
Android 9
Thank you very much
Click to expand...
Click to collapse
I hope you have your device restored right now. But if not: i has the exactly same problem. And restoring was much more simple then i thought.
1. keep de the device for a long time disconnected fully from the power. Think about 30 minutes or something.
2. place a SD card.
3. restore the power on the device.
4. press after 10 a 15 seconds one time on the on/off softbutton. You should see your startup screen and booting the device.
5. restore the custommer version to 1.
If it's not succesfully: disconnect the device from the power and let it rest for about 30 minutes and try eventually again.
If you want to in the bootloader. But it's very hard to do blind:
1. connect the power and let the device start up
2. press and hold the on/off soft button. When you see the lights on the device flashes 3 times release.
3. Press directly 2 or 3 (don't know what i did) and you are in the bootloader.
haajee86 said:
...
2. place a SD card.
...
Click to expand...
Click to collapse
I will probably have a recovery, my PX5 has a black screen (after TWRP flash to boot sector) and does not light up even at the reverse gear engaged. Btw what is the connection of the SD card mentioned in the manual?
Is it worth buying s-video (rca) - vga reduction with the fact that the video output can go to another output or is the black screen error something else?
Thanks.
hegolos941 said:
I will probably have a recovery, my PX5 has a black screen (after TWRP flash to boot sector) and does not light up even at the reverse gear engaged. Btw what is the connection of the SD card mentioned in the manual?
Is it worth buying s-video (rca) - vga reduction with the fact that the video output can go to another output or is the black screen error something else?
Thanks.
Click to expand...
Click to collapse
Revived a 2 year old thread, perhaps outline the issue and question. Is your device an MTCD/E?
My PX5 (has a reset hole and SD card slot) with hal9k Android 9 with Magisk root was fully functional. Yes is MTCD/E. It lost root, Magisk could not be reinstalled. I tried to flash TWRP recovery for PX5. In the TWRP interface I marked flash to boot. After the restart, there is only a black screen. The module that activated the display from the rear camera when reversing to the reverse gear also does not work (does not display the image from rear camera). When resetting with a button or hole, the lights flash as usual but do not start or the recovery menu is not visible. If I leave the PX5 without a reset after turning on the key, it will restart itself after about 1 minute.
I continue in the thread as it is one of the few where it is written about a practically identical situation. I found it reasonable to get info in a similar situation, more than starting a new topic. Especially if this thread does not have 100 pages.
hegolos941 said:
My PX5 (has a reset hole and SD card slot) with hal9k Android 9 with Magisk root was fully functional. Yes is MTCD/E. It lost root, Magisk could not be reinstalled. I tried to flash TWRP recovery for PX5. In the TWRP interface I marked flash to boot. After the restart, there is only a black screen. The module that activated the display from the rear camera when reversing to the reverse gear also does not work (does not display the image from rear camera). When resetting with a button or hole, the lights flash as usual but do not start or the recovery menu is not visible. If I leave the PX5 without a reset after turning on the key, it will restart itself after about 1 minute.
I continue in the thread as it is one of the few where it is written about a practically identical situation. I found it reasonable to get info in a similar situation, more than starting a new topic. Especially if this thread does not have 100 pages.
Click to expand...
Click to collapse
Rear camera module for reversing, interesting, perhaps MCU is meant.
Suggest SOM storage is now corrupt due to flashing recovery ( twrp is utterly useless on these devices, but hey,
beats reading 100s of pages. Good on you for an authentic outline of the issue)
Just a suggestion to resolve; OTG, apply MASKROM or buy replacement SOM.
Cordially, M
The module in post #7 is meant a small box that decodes the signal from the original rear camera to PX5 display. I mentioned it because it always worked. Even though the radio froze, for example, the rear view camera worked. Now the reversing speed doesn't even activate the image from the rear camera - that's why I thought the video output might be changed. Wrong construction
Anyway I understand = SDboot using SD card or USB drive made with RockChip Tools won't help me and I have to look for pins and adjust the USB cable. I wanted to avoid it Thank you for your reassurance.
I finally solved it without a USB cable. It was enough to make SDboot using an older version of SDDiskTool_v1.46 (the version of SDDiskTool_v1.69 on Windows 10 + Mac did not see the SD slot, on the second PC it made 15 partitions for me on the SD card).
1. I made an SDboot with Android 6 recovery. After inserting the SD card and pressing the reset, the boot logo appeared, ie the problem with the black screen disappeared. Immediately, the image from the rear camera "started" to work.
2. After writing Android 6 recovery, I made an Android 8 recovery SD card (also using an older version of SDDiskTool_v1.46) and I successfully repeated the procedure. With the functional recovery mode, I uploaded the update.zip from USB (the Hal9k PX5 mod 3.x) without any problems.