Database Info

my lg o1 stuck at lg logo, need help

Hi
I tried to install cm11
on The device
And the middle of the installation I registered it was canceled
So I had to install cm7
from the Memory card
I installed it
When I run the device
He got stuck LG logo
What to do?
And I used this guide: http://forum.xda-developers.com/showthread.php?t=2589303
And I followed - Upgrading from another CM10.2 or Older ROM
Sorry for the english, I'm from Israel
And I used google translate

eran32 said:
Hi
I tried to install cm11
on The device
And the middle of the installation I registered it was canceled
So I had to install cm7
from the Memory card
I installed it
When I run the device
He got stuck LG logo
What to do?
And I used this guide: http://forum.xda-developers.com/showthread.php?t=2589303
And I followed - Upgrading from another CM10.2 or Older ROM
Sorry for the english, I'm from Israel
And I used google translate
Click to expand...
Click to collapse
Boot back in to your recovery and wipe cache and dalvik cache. Format system and then install your ROM. There are major differences between CM11 and CM7. When making big jumps like that it's always best to format system before installing a ROM.

shinobisoft said:
Boot back in to your recovery and wipe cache and dalvik cache. Format system and then install your ROM. There are major differences between CM11 and CM7. When making big jumps like that it's always best to format system before installing a ROM.
Click to expand...
Click to collapse
I just did factory reset via cwm
And still have a problem
So do just what you say and do
system format?
You mean that you are going to have a system folder in the mount and stroage given formatting?

eran32 said:
I just did factory reset via cwm
And still have a problem
So do just what you say and do
system format?
You mean that you are going to have a system folder in the mount and stroage given formatting?
Click to expand...
Click to collapse
In CWM select Wipe data/factory reset. This will wipe the cache, dalvik cache and a couple other partitions. Then go to Mounts and Storage and select Format System. That will format the system partition.
Now go back to CWM home screen and install your ROM.

shinobisoft said:
In CWM select Wipe data/factory reset. This will wipe the cache, dalvik cache and a couple other partitions. Then go to Mounts and Storage and select Format System. That will format the system partition.
Now go back to CWM home screen and install your ROM.
Click to expand...
Click to collapse
thanks man, now my lg o1 works

Glad to help
Sent from my LG-P769 using Tapatalk

Hi,
May I ask for help here (instead of creating a new thread) ? I have the same problem: The device is booting loop at the LG screen. Bricked it when I wanted to save the ROM with ROM Manager.
I have no access to recovery mode, but Emergency mode does work (With and without battery).
I've followed multiple guides, including this one:
Most of you are stuck on a yellow screen with”Emergency mode!!” or the phone is not responding at all. You guys wanted a custom rom like Optimus Prime-v2 and let me tell you, this time it will work. Optimus One P500 comes with stock android 2.2 – V10a, V10b … and android 2.2.1 – V10n. They might be done for different regions depending upon the phone release and its popularity and definitely bug fixes and enhancements. To have Prime-v2 on your handset you will require V10a or V10b on your handset. Reason, V10n stock cannot be rooted easily. Rooting the handset is must if Prime-v2 is required on the device. Steps to install V10a, V10b series. I am using Windows 7 32-bit, 3 GB RAM laptop:
1. Clean your system first; get rid of LG PC suite and other stuff shown in Uninstall Program with vendor name as LG. Remove MSXML builts from the handset. Remove Nokia and other drivers if they are on system like Ovi suite etc. I also removed a lot of Microsoft runtime environments. Not sure about the reason but it worked for me.
2. LG usb device drivers, download the application B2CAppSetup.exe http://csmg.lgmobile.com:9002/client/app/B2CAppSetup.exe .
3. In the Menu Bar, click "Options & Help", and click "Country & Language". Select the appropriate Country & Language. I used India and select P500 from the list that popup after you change the country and region. It will download, install and save the drivers somewhere in C:\LGP500\USB_Driver, it will prompt to open the rar files, just click and install the exes seen in them.
4. Reboot the system.
5. Right click on Computer -> Properties -> Device Manager and see for three drivers – LG android usb modem, LGE serial usb port and LG composite USB device. Disable the modem driver and reboot once again.
6. Switch off the phone and press volume up + BACK button + POWER button. Phone should turn yellow with text “Emergency Mode!!” To switch it off you have to remove the battery (I know it hurts, but that’s the only way out here). Switch off and let’s continue with the setup.
7. To do the KDZ of system you will require the KDZ software updater, links keep going off and on internet. Try searching for “KDZ_FW_UPD_EN” or “KDZ_FW_UPD_EN.7z” in Google and download the software. It should be somewhere around 2.3 MB. To use it you will required some good version of WinZip or winrar again Google it and install the 7z archive utility.
8. Install msxml.msi as the manual or readme.txt says to do so.
9. To get the V10x Official ROM, you need to first determine the ROM of your choice. List of all firmware available for LG Optimus One P500 (list of codes) http://csmg.lgmobile.com:9002/csmg/b2c/client/ezlooks_model_list.jsp?model=LGP500 , search for your country (use IE it looks sexy in it), I looked out for IND/INDIA. Download link to the ROM is http://csmg.lgmobile.com:9002/swdata/WEBSW/LGP500/XXXXX/V10a_00/V10A_00.kdz where XXXX is code from list of codes. In my case it was: AINDBK. Save the file.
10. Prepare the handset by removing the SD card and boot it to emergency mode (some are already stuck on it so reading this post…: D) using the key combination stated above.
11. Connect to the PC and it should say, installing drivers’ blah… blah … your device is ready to use now.
12. Run the KDZ updater downloaded in step 7. Select 3GQCT in Type, DIAG in PhoneMode, and browse for ROM V10a in KDZ file and hit Launch Software update. Wait for somewhere around 5-10 minutes. It should say ===FINISHED=== in the log window of updater.
13. Handset will reboot, if not wait for another 5 minutes. Unplug from USB and try to switch it on.
Click to expand...
Click to collapse
My problem is that KDZ still doesn't find my phone after all these attempts - I uninstalled the device driver, then reinstalled it succesfully (B2CAppSetup.exe). I reboot, install msxml.msi, and start KDZ.
Next, I power my phone in Emergency phone, plug it, and it is detected for the first time by the computer. I do have LGE Android Platform Composite USB Device, listed in the Device Manager, as well as LGE Android Platform USB Modem.
Using KDZ, I select the "3GQCT" type, phone mode "DIAG", with the correct KDZ file I've downloaded earlier. Once I launch the software update, phone is not found.
I've tried several times, including desactivating the LG Modem from the Device Manager; unfortunately, when I disable it I need to reboot - I do reboot, but then the LGE Android Platform Composite USB Device is absent from the device manager, and isn't detected by Windows at all, until I fully reinstall the driver (...).
I really don't know what I'm doing wrong - note that I use a laptop with Windows 7 x64; I know laptops handle USB port in a different way than desktops.
Can you help please?
I must be SO close... =(
Thanks, I really appreciate it!

GameX2 said:
Hi,
May I ask for help here (instead of creating a new thread) ? I have the same problem: The device is booting loop at the LG screen. Bricked it when I wanted to save the ROM with ROM Manager.
I have no access to recovery mode, but Emergency mode does work (With and without battery).
I've followed multiple guides, including this one:
My problem is that KDZ still doesn't find my phone after all these attempts - I uninstalled the device driver, then reinstalled it succesfully (B2CAppSetup.exe). I reboot, install msxml.msi, and start KDZ.
Next, I power my phone in Emergency phone, plug it, and it is detected for the first time by the computer. I do have LGE Android Platform Composite USB Device, listed in the Device Manager, as well as LGE Android Platform USB Modem.
Using KDZ, I select the "3GQCT" type, phone mode "DIAG", with the correct KDZ file I've downloaded earlier. Once I launch the software update, phone is not found.
I've tried several times, including desactivating the LG Modem from the Device Manager; unfortunately, when I disable it I need to reboot - I do reboot, but then the LGE Android Platform Composite USB Device is absent from the device manager, and isn't detected by Windows at all, until I fully reinstall the driver (...).
I really don't know what I'm doing wrong - note that I use a laptop with Windows 7 x64; I know laptops handle USB port in a different way than desktops.
Can you help please?
I must be SO close... =(
Thanks, I really appreciate it!
Click to expand...
Click to collapse
First, serious word of advice. Stay away from ROM Manager. It does not handle this device correctly.
It sounds to me like you are not entering Emergency Mode correctly. Yes, the LG USB Modem must be disabled. Power off the device. Press the "Back + Volume Up + Power" buttons together until the device boots to Emergency Mode. Now connect device to you PC/laptop. This can also be done with the battery removed and the device off. Same method except no power button involved. Press the "Volume Up + Back" buttons while attaching your device to your data cable, assuming it's already attached to your PC/laptop.
The attachment I've posted is a stripped down version of the KDZ Updater. All you need to supply is the correct KDZ file for your phone. This one does not require any of LG's other crap software either.
Download to your PC. Extract to a folder of your choosing. Read the ReadMe.txt carefully and follow it's directions to the letter. I just used this to revive two ( 2 ) bricked P506's.
If you can boot to fastboot mode, there is a tool in my signature, Android Flash Recovery, that is designed to flash a recovery to a device with fastboot. So you have two options to restore, revive your device.

shinobisoft said:
First, serious word of advice. Stay away from ROM Manager. It does not handle this device correctly.
It sounds to me like you are not entering Emergency Mode correctly. Yes, the LG USB Modem must be disabled. Power off the device. Press the "Back + Volume Up + Power" buttons together until the device boots to Emergency Mode. Now connect device to you PC/laptop. This can also be done with the battery removed and the device off. Same method except no power button involved. Press the "Volume Up + Back" buttons while attaching your device to your data cable, assuming it's already attached to your PC/laptop.
The attachment I've posted is a stripped down version of the KDZ Updater. All you need to supply is the correct KDZ file for your phone. This one does not require any of LG's other crap software either.
Download to your PC. Extract to a folder of your choosing. Read the ReadMe.txt carefully and follow it's directions to the letter. I just used this to revive two ( 2 ) bricked P506's.
If you can boot to fastboot mode, there is a tool in my signature, Android Flash Recovery, that is designed to flash a recovery to a device with fastboot. So you have two options to restore, revive your device.
Click to expand...
Click to collapse
Hey, cheers !!
That was all I needed to do with this simple version, the update got applied properly, and I saw the FINISHED message.
My phone "rebooted". Well, what I see now if the Android logo with a big " ! ", which is normal according to what I've read.
I will do more ressearch to make sure what I do if correct now: is this safe to power off/reboot at this screen? I believe it's the last step.

GameX2 said:
Hey, cheers !!
That was all I needed to do with this simple version, the update got applied properly, and I saw the FINISHED message.
My phone "rebooted". Well, what I see now if the Android logo with a big " ! ", which is normal according to what I've read.
I will do more ressearch to make sure what I do if correct now: is this safe to power off/reboot at this screen? I believe it's the last step.
Click to expand...
Click to collapse
Yep. Sounds like you're good to go

shinobisoft said:
Yep. Sounds like you're good to go
Click to expand...
Click to collapse
Thanks
Holding the power button does not shut it down - pull the battery, right (It won't screw the thing right before the end ? XD ) ?
Look.. correct:
12 - Start the phone again. If you get stuck in a screen with an Android and an exclamation mark ("!") in a triangle, just unplug the USB cable and the battery. Plug the battery again and start the phone. It will take 2 to 5 minutes to reboot for the first time and the boot animation will be the stock LG (your carrier's stock animation is lost for good), but chances are your phone is intact, with all it's apps and configurations working the same as before the incident. When the boot finishes, turn off the phone again and put back the SD Card you took off on the first step.
Click to expand...
Click to collapse
I really don't want to mess anything at this point.

GameX2 said:
Thanks
Holding the power button does not shut it down - pull the battery, right (It won't screw the thing right before the end ? XD ) ?
Look.. correct:
I really don't want to mess anything at this point.
Click to expand...
Click to collapse
If KDZ Updater says it's done and your device has rebooted to recovery, then yes you can pull the battery to shut it down. You may still need to do the key presses for a factory reset, but the key combo has slipped my mind for the moment. Old age...

shinobisoft said:
If KDZ Updater says it's done and your device has rebooted to recovery, then yes you can pull the battery to shut it down. You may still need to do the key presses for a factory reset, but the key combo has slipped my mind for the moment. Old age...
Click to expand...
Click to collapse
Really nice, I have the Android logo !!
I will wait - people says it can take up to 5-15 minutes or even more - I won't shutdown on the logo.
Letting you know as soon as it's done.
***
After a while, the device booted, and I had a few messages saying it was restoring all the settings!
No data loss! Nothing (I had backed up my contacts and apps on my SD Card already - I was unsure if I would have loose my SMSs, I didn't) is lost !
Dude, seriously, thanks A BUNCH - this is ridiculous, I screwed the phone up at like 10PM yesterday, and did not went to sleep until 2AM because I couldn't fix the thing (I had access to FastBoot at first. I did a process to restore it from Fastboot, it should have worked properly, but then I only had access to the LG logo. Man, I thought I was toasted, and had to spend 50$ for a new phone, just because of a stupid mistake. Never would I thought that SAVING the ROM of my SD card would have screwed up the ROM!)...
I spent like 6 hours today trying to fix it, reinstalling the drivers over and over again... Installing a fresh new Windows XP on a machine, just so I could install everything on a new operating system to figure out the problem...
That was just plain crazy, seriously.
****BONUS****
The first thing I've noticed when I booted my phone was the BLACK notification bar
I really love black, and I once did ressearch a while ago to see if I could turn my white bar into black (I have Android 2.2.1), but no success.
I just realised I got it updated "accidentally" to Android 2.3, and so I was on Android 2.2. since 2011 (when I bought it) !
Well, nice addition, it is sexier with black
I belive it's because of the KDZ file I've used... I had a really hard time to find one, all the links were broken, from 2010, it's a old phone. I found the KDZ from Koodo, Canadian French, exactly my own.
Guess I "accidentally" upgraded to Android 2.3 then Nice addition !
I have no experience at all with fixing Android devices / ROM stuff - I'm used with Windows/Linux and others, but Android (although Android is a version of Linux) is another thing for me.
THANKS - seriously, I wouldn't have made it without your help.
YAY

GameX2 said:
Really nice, I have the Android logo !!
I will wait - people says it can take up to 5-15 minutes or even more - I won't shutdown on the logo.
Letting you know as soon as it's done.
***
After a while, the device booted, and I had a few messages saying it was restoring all the settings!
No data loss! Nothing (I had backed up my contacts and apps on my SD Card already - I was unsure if I would have loose my SMSs, I didn't) is lost !
Dude, seriously, thanks A BUNCH - this is ridiculous, I screwed the phone up at like 10PM yesterday, and did not went to sleep until 2AM because I couldn't fix the thing (I had access to FastBoot at first. I did a process to restore it from Fastboot, it should have worked properly, but then I only had access to the LG logo. Man, I thought I was toasted, and had to spend 50$ for a new phone, just because of a stupid mistake. Never would I thought that SAVING the ROM of my SD card would have screwed up the ROM!)...
I spent like 6 hours today trying to fix it, reinstalling the drivers over and over again... Installing a fresh new Windows XP on a machine, just so I could install everything on a new operating system to figure out the problem...
That was just plain crazy, seriously.
****BONUS****
The first thing I've noticed when I booted my phone was the BLACK notification bar
I really love black, and I once did ressearch a while ago to see if I could turn my white bar into black (I have Android 2.2.1), but no success.
I just realised I got it updated "accidentally" to Android 2.3, and so I was on Android 2.2. since 2011 (when I bought it) !
Well, nice addition, it is sexier with black
I belive it's because of the KDZ file I've used... I had a really hard time to find one, all the links were broken, from 2010, it's a old phone. I found the KDZ from Koodo, Canadian French, exactly my own.
Guess I "accidentally" upgraded to Android 2.3 then Nice addition !
I have no experience at all with fixing Android devices / ROM stuff - I'm used with Windows/Linux and others, but Android (although Android is a version of Linux) is another thing for me.
THANKS - seriously, I wouldn't have made it without your help.
YAY
Click to expand...
Click to collapse
Glad things worked out for ya And helping is what I'm here for

shinobisoft
shinobisoft said:
Yep. Sounds like you're good to go
Click to expand...
Click to collapse
Thanks for helping NOOBS, i appreciate that!

[Q] HKC P776A Android tablet stuck in twrp/cwm bootloop

Ok I finally got this tablet rooted using some chinese oneclick root tool worked great do to it was the only kit that was able to root it and i installed supersu apk to replace to chinese version worked and i went to update supersu and hit the twrp (not knowing what it was at the tim stupid right i know lol) and now it is stuck in the twrp/cwm bootloop and i cant get into recovery mode when i try it says updating img blah blah and restarts back into the bootloop. It is running 4.1.1 JB and has a micro sd card slot.There is a pic in the atachment because i dont know how to upload it to this post but it is just a pic no "extras" are included no viruses maleware ect just a pic

parkourgamer said:
Ok I finally got this tablet rooted using some chinese oneclick root tool worked great do to it was the only kit that was able to root it and i installed supersu apk to replace to chinese version worked and i went to update supersu and hit the twrp (not knowing what it was at the tim stupid right i know lol) and now it is stuck in the twrp/cwm bootloop and i cant get into recovery mode when i try it says updating img blah blah and restarts back into the bootloop. It is running 4.1.1 JB and has a micro sd card slot.There is a pic in the atachment because i dont know how to upload it to this post but it is just a pic no "extras" are included no viruses maleware ect just a pic
Click to expand...
Click to collapse
Super old I know but my kids tablet is doing this now. Did you ever find a fix?

KilluminatiStyle said:
Super old I know but my kids tablet is doing this now. Did you ever find a fix?
Click to expand...
Click to collapse
Pro tip: Don't bumb old threads like this. You might not even have similar problems. Instead create a new thread regdaring your issue.
Now, post your tablet info HERE:
Root staus?
Can you boot in recovery? If yes what recovery do you have?
Tablet model
Android version
What happened
What have tried to fix it

janekmuric said:
Pro tip: Don't bumb old threads like this. You might not even have similar problems. Instead create a new thread regdaring your issue.
Now, post your tablet info HERE:
Root staus?
Can you boot in recovery? If yes what recovery do you have?
Tablet model
Android version
What happened
What have tried to fix it
Click to expand...
Click to collapse
Root Status = ROOTED
I cannot boot into recovery mode (but when i try i get this, look in pic 2&3)
Tablet Type = HKC (NOT HTC) p776a
ANDROID Version I think (98% shure) is 4.1.1 beta JB
What happened = A few years ago 2013 i think a got this tablet then i learned about rooting, roms, and such so i spent the next year or two trying to root the tablet. I finally got it rooted with a chinese root program and all was well (i don't remember the name of the program) then there was a update for su and i pressed the twrp/cwm mode on accident (I think I was talking to someone at the time) and now it does what is shown in the image 1 it is on some boot loop. When I try to access the hboot menu it does what is shown in these images 2&3. Also my tablet has a MicroSD card slot and the battery can not be taken out. the regular bootloop picture is image file 1 that is what it looks like when it does its continuous bootloop and P.S. the tablet turns off and on automatically during the bootloop. To try and fix it i have let it do its bootloop for hours on end turn it on and off tried looking for a compatible rom (to no avail) and let the battery completely die that is about it.

parkourgamer said:
Root Status = ROOTED
I cannot boot into recovery mode (but when i try i get this, look in pic 2&3)
Tablet Type = HKC (NOT HTC) p776a
ANDROID Version I think (98% shure) is 4.1.1 beta JB
What happened = A few years ago 2013 i think a got this tablet then i learned about rooting, roms, and such so i spent the next year or two trying to root the tablet. I finally got it rooted with a chinese root program and all was well (i don't remember the name of the program) then there was a update for su and i pressed the twrp/cwm mode on accident (I think I was talking to someone at the time) and now it does what is shown in the image 1 it is on some boot loop. When I try to access the hboot menu it does what is shown in these images 2&3. Also my tablet has a MicroSD card slot and the battery can not be taken out. the regular bootloop picture is image file 1 that is what it looks like when it does its continuous bootloop and P.S. the tablet turns off and on automatically during the bootloop. To try and fix it i have let it do its bootloop for hours on end turn it on and off tried looking for a compatible rom (to no avail) and let the battery completely die that is about it.
Click to expand...
Click to collapse
Okay. Just a few more questions.
Does your tablet boot into recovery (picture 1) even if you try to boot normally? (fastboot maybe)
Can you boot into anything else other than recovery? (try different button combinations)
Does ADB recognise your tablet when it's in recovery mode? (if you don't know about this, just post your computer OS and if you have ADB/Fastboot drivers installed on your PC)
If the anwser the the first question is no:
Does ADB recognise the device while it's in the bootloop.

janekmuric said:
Okay. Just a few more questions.
Does your tablet boot into recovery (picture 1) even if you try to boot normally? (fastboot maybe)
Can you boot into anything else other than recovery? (try different button combinations)
Does ADB recognise your tablet when it's in recovery mode? (if you don't know about this, just post your computer OS and if you have ADB/Fastboot drivers installed on your PC)
If the anwser the the first question is no:
Does ADB recognise the device while it's in the bootloop.
Click to expand...
Click to collapse
sorry, i forgot to clarify the hboot. it pops up the "words" or whatever then automatically reboots there is no way to select options or keep the device on so i cant use fastboot unless there is a way i dont know of. P.S. the tablet restarts automatically so it is on for like 25 maybe 30 seconds then shuts off then turns back on and repeats till the battery is dead. My thought originally to fix it was to get a rom put it on the sdcard and see if that works but the manufacture does not supply the rom for my model only the p771a. and the only physical buttons are the home, power, the pinhole reset button, the volume and such buttons are virtual on the screen when it is fully on. And picture 1 i dont fully know what that screen symbol is the hboot one is similar but not that but yes it does but to picture 1 nomadder what i do even if i try to get to hboot menu. Sorry if this is a "little" scattered having explaining it. If it would help i can make a video and rar it and upload it here.

parkourgamer said:
sorry, i forgot to clarify the hboot. it pops up the "words" or whatever then automatically reboots there is no way to select options or keep the device on so i cant use fastboot unless there is a way i dont know of. P.S. the tablet restarts automatically so it is on for like 25 maybe 30 seconds then shuts off then turns back on and repeats till the battery is dead. My thought originally to fix it was to get a rom put it on the sdcard and see if that works but the manufacture does not supply the rom for my model only the p771a. and the only physical buttons are the home, power, the pinhole reset button, the volume and such buttons are virtual on the screen when it is fully on. And picture 1 i dont fully know what that screen symbol is the hboot one is similar but not that but yes it does but to picture 1 nomadder what i do even if i try to get to hboot menu. Sorry if this is a "little" scattered having explaining it. If it would help i can make a video and rar it and upload it here.
Click to expand...
Click to collapse
here is the video

parkourgamer said:
sorry, i forgot to clarify the hboot. it pops up the "words" or whatever then automatically reboots there is no way to select options or keep the device on so i cant use fastboot unless there is a way i dont know of. P.S. the tablet restarts automatically so it is on for like 25 maybe 30 seconds then shuts off then turns back on and repeats till the battery is dead. My thought originally to fix it was to get a rom put it on the sdcard and see if that works but the manufacture does not supply the rom for my model only the p771a. and the only physical buttons are the home, power, the pinhole reset button, the volume and such buttons are virtual on the screen when it is fully on. And picture 1 i dont fully know what that screen symbol is the hboot one is similar but not that but yes it does but to picture 1 nomadder what i do even if i try to get to hboot menu. Sorry if this is a "little" scattered having explaining it. If it would help i can make a video and rar it and upload it here.
Click to expand...
Click to collapse
1. Download fixcache.bat.zip on your computer. Extract cachefix.bat from the file.
2. Run it. It should say just "Waiting for device..."
3. Now reset your tablet with the reset button and QUICKLY plug it into the computer and wait a few minutes.
Now try to get to that text in picture 1 and tell me what happends.
Also post the text you see on the computer from the file I sent you.
Tell me if

janekmuric said:
1. Download fixcache.bat.zip on your computer. Extract cachefix.bat from the file.
2. Run it. It should say just "Waiting for device..."
3. Now reset your tablet with the reset button and QUICKLY plug it into the computer and wait a few minutes.
Now try to get to that text in picture 1 and tell me what happends.
Also post the text you see on the computer from the file I sent you.
Tell me if
Click to expand...
Click to collapse
this is what happens to the .bat fikle when i open it

parkourgamer said:
this is what happens to the .bat fikle when i open it
Click to expand...
Click to collapse
also would there be any way to pop the hood and flip a switch to reset it like on a pc tower?

parkourgamer said:
also would there be any way to pop the hood and flip a switch to reset it like on a pc tower?
Click to expand...
Click to collapse
Umm, you said there is a reset button on the tablet so pressing that would probably reset it.
The error you are getting is because adb is not installed on your PC. Use this simple adb installer to instal adb. When installing just press yes to everything. MAKE SURE THE PHONE IS PLUGGED IN THE COMPUTER WHILE INSTALLING AND THAT IT'S ON!
Now run the file again.
If you want you can add me on Skype: janekmuric
---------- Post added at 13:51 ---------- Previous post was at 13:26 ----------
If you want to know what is happening:
You are in what's called a recovery bootloop. It's when you can't get out of the recovery. What is happening in this case is that Superuser app tried to install it's binaries via recovery. Because some people don't know how to install binaries manually, the app puts a file on the cache partition so the recovery automaticly installs the zip upon booting. Now, this would be good so you don't mess up your device, but the zip file it's trying to install is faulty so it just breaks the device.
My attept at fixing this is to delete the /cache/recovery folder so it doesn't just install the file, and instead boots into a working recovery.

janekmuric said:
Umm, you said there is a reset button on the tablet so pressing that would probably reset it.
The error you are getting is because adb is not installed on your PC. Use this simple adb installer to instal adb. When installing just press yes to everything. MAKE SURE THE PHONE IS PLUGGED IN THE COMPUTER WHILE INSTALLING AND THAT IT'S ON!
Now run the file again.
If you want you can add me on Skype: janekmuric
---------- Post added at 13:51 ---------- Previous post was at 13:26 ----------
If you want to know what is happening:
You are in what's called a recovery bootloop. It's when you can't get out of the recovery. What is happening in this case is that Superuser app tried to install it's binaries via recovery. Because some people don't know how to install binaries manually, the app puts a file on the cache partition so the recovery automaticly installs the zip upon booting. Now, this would be good so you don't mess up your device, but the zip file it's trying to install is faulty so it just breaks the device.
My attept at fixing this is to delete the /cache/recovery folder so it doesn't just install the file, and instead boots into a working recovery.
Click to expand...
Click to collapse
That would be great but i cant keep my tablet on for more than like 30 seconds before it auto shuts off and it automatically tries to go into recovery when i add power to the device it wont just boot to the OS

parkourgamer said:
That would be great but i cant keep my tablet on for more than like 30 seconds before it auto shuts off and it automatically tries to go into recovery when i add power to the device it wont just boot to the OS
Click to expand...
Click to collapse
30 seconds is more than enough. Especally with an automated script like the one I sent you.
The first thing we have to do to fix your tablet is to establish a working ADB connection. Use the ADB installer i sent you. And look up on how to install Google USB driver for ADB.

janekmuric said:
30 seconds is more than enough. Especally with an automated script like the one I sent you.
The first thing we have to do to fix your tablet is to establish a working ADB connection. Use the ADB installer i sent you. And look up on how to install Google USB driver for ADB.
Click to expand...
Click to collapse
ok will try

Bricked MTCD KGL unit with Malaysk soft

Hello,
I downloaded the latest Malaysk software from the repository, tried installing it with the second method (from "System update") along with wiping flash.
Now this KGL MTCD unit is bricked, there is no response from it, aside from the buttons lighting up.
How to unbrick it?

can you get in to the Recovery?
Never change a running system if you are not knowing what you do

NiTr0Us said:
can you get in to the Recovery?
Never change a running system if you are not knowing what you do
Click to expand...
Click to collapse
Yes, if you can get into recovery you can just flash. In the thread it clearly says that you have to get into recovery BEFORE flashing (because you have to flash twice due to partitioning).
Ask your vendor how you can get into recovery if the usual way (pressing power + reset at the same time, then releasing reset and pressing power a single time again) wont work.

Just get in recovery and use the Wipe data / reset cache option, then flash it again from recovery.
Reboot and enjoy

If I could get into recovery I wouldn't be posting this topic.
Recovery doesn't work.
What now?

TO get into recovery,
when it should boot up, press and hold power.
THen it will force shutdown. Next boot brings up recovery for me!

same here bro
the unit is totaly dead, cant go to recovery...

hashtowent said:
TO get into recovery,
when it should boot up, press and hold power.
THen it will force shutdown. Next boot brings up recovery for me!
Click to expand...
Click to collapse
Like I said, I cannot get into recovery. The unit doesn't boot up at all.
Oh well, I'll just replace the motherboard.

for all of you with bricks. lets do some experiments
Can you guys hook it up to a computer and see if the computer can read it. If you can you should be able to adb the rom back.
http://www.rockchip.nl/downloads/
Make sure you have the drivers. If you can successfully read it then you can use RKTools or adb.

transitoyspace said:
for all of you with bricks. lets do some experiments
Can you guys hook it up to a computer and see if the computer can read it. If you can you should be able to adb the rom back.
Make sure you have the drivers. If you can successfully read it then you can use RKTools or adb.
Click to expand...
Click to collapse
hahahah
i do this work without read you, i came here to post the solution
with the rk3188 drivers + " RK Batchtool" i firm the unit in 3 mins. its works ok

Can you share the steps? I have a bricked unit also.

transitoyspace said:
for all of you with bricks. lets do some experiments
Can you guys hook it up to a computer and see if the computer can read it. If you can you should be able to adb the rom back.
http://www.rockchip.nl/downloads/
Make sure you have the drivers. If you can successfully read it then you can use RKTools or adb.
Click to expand...
Click to collapse
Even if MCU has changed we can recover to factory settings??
Because in my HU i can go to reboot display but appeared the message
Cant mount...../device/block/.../.../(device block required).

I had similar issues
Trimis de pe al meu SM-G930F folosind Tapatalk
---------- Post added at 03:09 PM ---------- Previous post was at 03:05 PM ----------
Fixed by removing the power connector and keeping power button pressed and restored power supply without ACC in order to establish usb connection with my laptop.
By using RK batchtool, I managed to restore my unit.
Trimis de pe al meu SM-G930F folosind Tapatalk

adibxx said:
I had similar issues
Trimis de pe al meu SM-G930F folosind Tapatalk
---------- Post added at 03:09 PM ---------- Previous post was at 03:05 PM ----------
Fixed by removing the power connector and keeping power button pressed and restored power supply without ACC in order to establish usb connection with my laptop.
By using RK batchtool, I managed to restore my unit.
Trimis de pe al meu SM-G930F folosind Tapatalk
Click to expand...
Click to collapse
But I suppose that you loaded on RK batch tool the factory Mcu and firmware right?
Because in my case I can't find factory mcu and seller doesn't know to provide me the factory software.
So with batchtool what can I do?

Qwerty11111 said:
But I suppose that you loaded on RK batch tool the factory Mcu and firmware right?
Because in my case I can't find factory mcu and seller doesn't know to provide me the factory software.
So with batchtool what can I do?
Click to expand...
Click to collapse
Factory firmware failed checksum. So, I used Malaysk ROM. The latest version failed to erase screen, but, the previous one booted successfully. Initially I tries to use recovery and ended up in brick device. Only rear camera was working. The devices stacked to Malaysk ROM screen and no stand by if ACC OFF.
Trimis de pe al meu SM-G930F folosind Tapatalk

Hi there,
Trying to install Malaysk ROM on an MTCD-KGL unit, I managed to get it bricked. As in... no screen, no sound, no Recovery, nothing! Couldn't link it to PC, nothing. The reset + volume button combination did not work for me to enter Recovery. My screen was all dead.
So... After some research, I used "Rockchip Upgrade Disk Tool" v1.4 and the unit booted from the sd card inserted in the GPS slot (Guide here: http://wiki.radxa.com/Rock/SD_upgrading ).
In theory, the unit should have started automatically upgrade from the SD but in my case it presented an error requesting me to remove the sd card. After removal, the unit went to Recovery boot menu. Still a success.
When the Recovery menu appeared, I inserted an sd card with dupdate.img on it in the GPS slot and selected install from menu. Unfortunately, the unit kept saying that it does not find the sd card. Tried the other sd slot but same error.
Success came from USB port. One of the two from the back of the unit, not the one in front. I put the dupdate.img and dmcu.img on an usb stick and inserted in one of the usb ports from the back. The unit recognized the stick and started the update process.
Now the unit is working.
If someone is interested, I can provide MCU and ROM (version from October 2016).
Hope this helps someone.

kufu said:
Hi there,
Trying to install Malaysk ROM on an MTCD-KGL unit, I managed to get it bricked. As in... no screen, no sound, no Recovery, nothing! Couldn't link it to PC, nothing. The reset + volume button combination did not work for me to enter Recovery. My screen was all dead.
So... After some research, I used "Rockchip Upgrade Disk Tool" v1.4 and the unit booted from the sd card inserted in the GPS slot (Guide here: http://wiki.radxa.com/Rock/SD_upgrading ).
In theory, the unit should have started automatically upgrade from the SD but in my case it presented an error requesting me to remove the sd card. After removal, the unit went to Recovery boot menu. Still a success.
When the Recovery menu appeared, I inserted an sd card with dupdate.img on it in the GPS slot and selected install from menu. Unfortunately, the unit kept saying that it does not find the sd card. Tried the other sd slot but same error.
Success came from USB port. One of the two from the back of the unit, not the one in front. I put the dupdate.img and dmcu.img on an usb stick and inserted in one of the usb ports from the back. The unit recognized the stick and started the update process.
Now the unit is working.
If someone is interested, I can provide MCU and ROM (version from October 2016).
Hope this helps someone.
Click to expand...
Click to collapse
Hi,
Before you saved your unit, did button light light up or not? I have same issues like you had, but unfortunatelly I can't debrick my unit. Could you provide me all files (links), which helped you to brought it alive, please? Thanks.

Hello! At my unit, yes the buttons light was on. There is a link in my post and also you can read here: http://forum.xda-developers.com/showpost.php?p=68717214&postcount=877
Hope you solve your problem.

Qwerty11111 said:
But I suppose that you loaded on RK batch tool the factory Mcu and firmware right?
Because in my case I can't find factory mcu and seller doesn't know to provide me the factory software.
So with batchtool what can I do?
Click to expand...
Click to collapse
I had factory firmware but didn't work.
I used the latest one.
Trimis de pe al meu SM-G930F folosind Tapatalk

I did a walkthrough with pics on how i recovered my unit.
https://forum.xda-developers.com/an...nt/eonon-ga6164f-mtcd-rk3188-mtcdkld-t3594368

PX5 MCU How to flash MCU or MCUconfig blind

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.

Chinese screen after botched update. HELP!!!

I tried updating my PX5 (3188/32rom/2gbram) FUSE rom to a later version and now when the headunit reboots I get a black screen. If I insert the SD card I get a chinese screen with GPS. Backup camera still works. Also, can't boot into recovery. Is my unit bricked? Pic attached.

Is it an MTCD/E. What recovery options have you considered from the forums if MTCD/E

marchnz said:
Is it an MTCD/E. What recovery options have you considered from the forums if MTCD/E
Click to expand...
Click to collapse
I had a recovery option (v8.0.5) but when the update botched I can't boot into recovery. MTCD unit. Haven't messed around with roms, recovery, etc since 2016 so forgive me for being rusty.

You have to pull out the sd card.

Yeah I figured that much out and when I do and th e unit boots up to a black screen and I get a message flash in the bottom left hand corner of head unit but can't read it as it isn't up for long. I left it be the other night, got in my truck the next morning and recovery was up but couldn't get it to recognize update.img from sd card. Now I can't get it back into recovery. Can anybody hep?

Stonington said:
Yeah I figured that much out and when I do and th e unit boots up to a black screen and I get a message flash in the bottom left hand corner of head unit but can't read it as it isn't up for long. I left it be the other night, got in my truck the next morning and recovery was up but couldn't get it to recognize update.img from sd card. Now I can't get it back into recovery. Can anybody hep?
Click to expand...
Click to collapse
Take a look at my OTG thread. I've had 100% success via this method.
For users that aren't comfortable with this OTG method, I have received SOMs from around the world - all I ask for is return freight.
Some options.