I don't think I could've make the title any blander really could I?
So, to the issue.
I've had a hefty prowl around the forum and i've found threads that hint at the information I need (i.e. Letting me know the information exists), but not one thread that actually answers my question.
So without further ado, here it is:
How exactly did the 'nand' block association for CWM recovery change between 4.0.3 and 4.0.4?
I ask because my tablet ran 'Christian Troy's A10 CWM 6.0.1.2' perfectly on 4.0.3, but when i upgraded to my manufacturer's new 4.0.4 rom, it suddenly didn't work. That's not to say that the install-recovery.sh stopped working, but that after applying it, a reboot automatically brought me into recovery, even if I wasn't holding down Vol+. Then, after exiting, the unit stopped loading, and wouldn't even go back into CWM. Effectively, the unit seemed 'bricked'.
I resurrected the unit using Livesuit, and tried multiple other applications, and CWM versions to no joy, and then I found a thread detailing that the dev/block/nandg was no longer valid on 4.0.4, and this is why flashing CWM was causing the unit not to boot.
However, nowhere have I found which block to change it to, or what other developers have had to do to get CWM to work stably on 4.0.4.
Any ideas?
My device's specs are as follows:
Sumvision Astroplus (Astro+) 7 inch tablet.
Stock ROM Android 4.0.4
Arm A8 1.2Ghx Processor
Mali 400 GPU
The unit is known by the following names, but I'm sure there are many more:
Ployer Momo 9
Funbook
IVIEW 760TPC
Does anyone have an idea at all?
I've conected this your post here,
[rom] Unofficial CyanogenMod 9 for many AllWinner A10 tablets, post # 398-400
http://forum.xda-developers.com/showthread.php?t=1760929&page=40
investigating this problem..
I have an A13 7 inch tablet pc ET Q8 V1.3 (A13Q8 131216) which it had a problem with play store.When I was trying to load it, it was keep crashing. I decided to flash it with a different rom to see if ti works.I tried several rom's but none of them worked. After a lot o search and reading post's , threads in every forum I could find I found the original ROM with the same name and when I flashed it it got stack in the boot logo.
Has anyone any ideas why isn't working? I have a second same working tablet
Hey guys,
The patient is an Android RK3188 5.1 unit from Xtrons for a BMW. The manufacturer is "GS".
After installing basic apps the unit started to really lag, not to mention that the touchscreen stopped working. So I flashed it with a factory MTCD 5.1 KGL rom and the installation went without any problems. After that I had to flash it back to a GS ROM, so I used something I found here on XDA a while ago, namely "GS_NEW4_rk3188_5.1(20160305)".
The installation went without any problems, but the unit then stopped on the "Lollipop" logo. It doesn't go to the car logo after that, just stops dead at the Lollipop screen and that's it.
When I try entering recovery, it works like it should, but the unit blurts out a crapload of info and errors, like the ones you can see in the attached pictures.
Updates don't work anymore.
Please note: I did NOT try to update the MCU on this unit. Only the Android software.
What's the problem with this unit? How to get it back to its normal state?
Picture descriptions:
1 - how recover looks like upon entering it.
2, 3 - sorry for the blurry pictures, but it's hard to snap a good picture of the moving text. You get the idea - a thousand errors or so.
4 - when I try flashing a regular KGL rom that worked on the unit before.
Did you tried this from sd card in GPS slot?
Never had success with that, only from usb drive.
Maybe you try this and it helps...
makes2068 said:
Did you tried this from sd card in GPS slot?
Never had success with that, only from usb drive.
Maybe you try this and it helps...
Click to expand...
Click to collapse
Yes. USB doesn't work.
Test it with another usb stick.
I have the same problems with some of the USB3 32GB Sticks from Sandisk.
SanDisk SDCZ43-032G-G46 Ultra Fit 32GB USB-Flash-Laufwerk USB 3.0 ✓
SanDisk Ultra Dual USB-Flash-USB Stick 32GB USB 3.0 X
Test all USB Ports and formate the sticks fat32
Use stick as small as possible.
Same to gps card. Use 16GM max, and all works as expected. Got some problems with 32gb cards. Took too long to show covers...
So, essentially, the problem here is the SD cards or USB sticks?
I don't think that's the problem.
I know how to update headunits, and it never mattered whether I used this card, that card or that USB stick... in fact, I only use microSD cards for updates, nothing else.
What the problem is is that the update breaks the unit, rendering it impossible to use.
I need to know what is the cause of that, and how to REVERT the damage.
Please read my first post again.
looks like the internal flash memory is broken. From your pics there is a line where the recovery is trying to make a partition and fails. It might be a pain in the ass but try to get xtrons to send you another SOM board.
vinhZ said:
looks like the internal flash memory is broken. From your pics there is a line where the recovery is trying to make a partition and fails. It might be a pain in the ass but try to get xtrons to send you another SOM board.
Click to expand...
Click to collapse
Thanks for your reply.
Can you, or somebody else explain how is it that the unit got screwed when installing a new ROM?
I did not touch the MCU or anything else. The unit is a RK3188 MTCD Android 5.1 one, and I used a different MTCD ROM.
It could be anything, like any flash drive/thumb drive, sometimes they just go bad. It accounts for the slowness when you originally flashed the new rom, then just gave out when you tried to flash again.
Me so nothing I can do
I have had your same issue: follow this guide: https://forum.xda-developers.com/showpost.php?p=67184851&postcount=50
Sure that it's a MTCD rom and not MTCB?
When i installed malaysk rom for the first time, i have had the same issue. My hu is a kd one too.
Inviato dal mio Redmi Note 3 utilizzando Tapatalk
dude-nl said:
Sure that it's a MTCD rom and not MTCB?
Click to expand...
Click to collapse
Yes.
@colostro - the recovery card doesn't work.
NaviPR said:
Yes.
@colostro - the recovery card doesn't work.
Click to expand...
Click to collapse
Why does not it work ? You can make a video? We did everything as written here? - https://forum.xda-developers.com/showpost.php?p=68717214&postcount=877
GS_NEW4_rk3188_5.1(20160305) - This firmware from MTCB !!! You have loaded the firmware from another device !!
NaviPR said:
Hey guys,
The patient is an Android RK3188 5.1 unit from Xtrons for a BMW. The manufacturer is "GS".
After installing basic apps the unit started to really lag, not to mention that the touchscreen stopped working. So I flashed it with a factory MTCD 5.1 KGL rom and the installation went without any problems. After that I had to flash it back to a GS ROM, so I used something I found here on XDA a while ago, namely "GS_NEW4_rk3188_5.1(20160305)".
The installation went without any problems, but the unit then stopped on the "Lollipop" logo. It doesn't go to the car logo after that, just stops dead at the Lollipop screen and that's it.
When I try entering recovery, it works like it should, but the unit blurts out a crapload of info and errors, like the ones you can see in the attached pictures.
Updates don't work anymore.
Please note: I did NOT try to update the MCU on this unit. Only the Android software.
What's the problem with this unit? How to get it back to its normal state?
Picture descriptions:
1 - how recover looks like upon entering it.
2, 3 - sorry for the blurry pictures, but it's hard to snap a good picture of the moving text. You get the idea - a thousand errors or so.
4 - when I try flashing a regular KGL rom that worked on the unit before.
Click to expand...
Click to collapse
Unfortunately I have the same issue "block device required " and I haven't found any solution over a month now.
Hope someone help you to find a solution as from my side I disappointed and my device is now decorate my room.
With the described method, you can't enter in recovery mode?!? Did you put sd card into gps slot? Sure?
Inviato dal mio Redmi Note 3 utilizzando Tapatalk
Hey guys,
I have a similar error but after install the ROM. I have installed malasyk rom MTCD 5.1.1 without problems, but when update the device with my stock ROM i don´t have internal_sd or flash and don´t can install GPS apk.... The device work fine but without internal_sd. If install other time the malasyk ROM the internal_sd appears.
Can you help me how i can mount internal_sd or flash?
Malaysk said:
Why does not it work ? You can make a video? We did everything as written here? - https://forum.xda-developers.com/showpost.php?p=68717214&postcount=877
Click to expand...
Click to collapse
@Malaysk - everything has been done to the letter, as always. I have had successes beforehand with the recovery card.
It just simply doesn't work in this case. The unit doesn't react to the card.
GS_NEW4_rk3188_5.1(20160305) - This firmware from MTCB !!! You have loaded the firmware from another device !!
Click to expand...
Click to collapse
How do you know that it is a MTCB rom?
Same problem to me.
The HU is booting on Lollipop logo, and this is it.
I can flash MCU, but cannot flash ROM.
The device is going in Recovery Mode, but cannot flash ROM.
Also, it cannot be connected to PC, to flash it with RkBatchTool.
When i am trying this: https://forum.xda-developers.com/showpost.php?p=67184851&postcount=50
the HU doesnt power on with SD card inserted.
My device was MTCD KGL. IS written on the pCB as well, and i took pictures before first flashing.
Any help is apreciated!
I have 3 Eonon HU's, a GA2114, GA2154 and a GA2162. I have flashed the Malaysk ROM on both the GA2114 and the Ga2154 and I think Malay has done an excellent job! His ROM really makes the units run well, my question is, is it possible to flash the Malaysk ROM onto the GA2162? I have searched all the posts relating to Marshmallow 6.0 head units but I can't find any way of of getting into the recovery menu to flash the file. I can access system update and I have tried loading various other Marshmallow options such as Joying and a couple of other brand names but they don't really change anything. I have very little experience with android devices it being limited just to these head units. Any help or suggestions would be greatly appreciated. Thanks in advance.
Hey guys,
I have a question for you, cause I am not familiar with the woring of the headunits. I bought an Isudar headunit, but the coreboard gave up (PX30) quite soon. Now I have a Witson coreboard in it and it's working. My problem is, although the headunit is working, the wifi and the usb doesn't. What should I do to syncronize the hardware and software of the headunit. Should I stay with the Isudar MCU and install an Isudar rom to the headunit somehow? If you have any idea, please share with me!
Thanks in advance!
UP
clorid said:
UP
Click to expand...
Click to collapse
Perhaps read through the forums - suggest the MCU cross compatibility thread - and also figure out if it matters which Android MTCD/E ROM could be applied.
I did a firmware update back to the original stock. Unfortunately the wifi and usb still not working. Do you have any idea?
Ok, so I have some news. I did a firmware update back to the original stock rom. Wifi and usb not worked. I randomly find a rom for PX30 and I flashed it to the headunit. The usb started to work, but after a few power on it's not working again. I tried to flash another mcu but it didn't work, so now back to the original. The seller said if I can't power up the head unit's wifi with the stock firmware that's a hardware issue. What do you think?
Can someone help me how can I root the head uni? It's PX30, with GS mcu, running android 9. Unfortunately I don't have wifi and the usb recognises just pendrive. Besides I can use my sd card to copy and use files. Please let me know how to root the device with this conditions! Thanks!