[Q] Could it be hacked to install another "recovery" partition and custom rom ?
I have bought a relatively cheap (not big brand) 1GHz due-core smartphone which runs Android 4.0.3. Recently, the SMS program crashes everytime I open it and I want to reflash the original Android 4.0.3 rom again. However, the manufacturer only flashes an Android 4.0 rom for my phone and serves me in a not-so-friendly way. They do not provide any information for the customers to reflash their Android roms themselves, and they also do not provide any information on rooting their phone. I have used the phone for just more than half a year and the phone's Android has crashed for 3 times.
I wonder is that any way that I could find out the hardware config of my smartphone and do some hacking to install some custom recovery and Android rom (e.g. Cyanogenmod) in the market. I do not want to depend on the manufacturer any more to accept their business manner.
Is there any suggestion or solution. Thanks a lot.
Lawrence
Hi, is it possible to extract fully working installation of Android from one device and then install it to another? The devices are similar, but the another one is apparently having some issues because it cannot finish factory reset. No need to preserve data files (downloaded software, pictures etc.) but just restore the device to working condition.
Device has ATM7021 CPU, 512MB, 8GB, 10.1" display and Android 4.2.2. Model number is P706.
A device branded GD IPPO looks similar but these tablets I have are not branded.
Hi, I know that it's a post long time ago.
It's possible to do it by making a full nandroid backup of your device firmware if your device has a custom recovery installed.
Unfortunately, I haven't found any custom recovery for ATM7021a yet.
Anyone have any idea how to install CWM or TWRP on ATM7021A? Thanks In Advance.
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.
Hi all,
Last weekend I rooted my phone. I treble-ized it and tampered with a few GSIs. I finally chose to use PHHs Treble 9 GSI.
When I connected my phone to my car's Bluetooth I could call, but there was no sound. Is this a driver issue on my Vendor partition (ie did I use the wrong Vendor), or is this a general problem with GSI?
roytje88 said:
Hi all,
Last weekend I rooted my phone. I treble-ized it and tampered with a few GSIs. I finally chose to use PHHs Treble 9 GSI.
When I connected my phone to my car's Bluetooth I could call, but there was no sound. Is this a driver issue on my Vendor partition (ie did I use the wrong Vendor), or is this a general problem with GSI?
Click to expand...
Click to collapse
it wouldnt be a dirver since android doesnt use drivers, it would be in the bluetooth stack. likely caused by a failed flash of your ROM especially if other users arent having the same issue. What kind of car is it (assuming the deck is stock to the car)
Youdoofus said:
it wouldnt be a dirver since android doesnt use drivers, it would be in the bluetooth stack. likely caused by a failed flash of your ROM especially if other users arent having the same issue. What kind of car is it (assuming the deck is stock to the car)
Click to expand...
Click to collapse
Good to know it's only a problem what's occurring on my phone. That would mean flashing a different rom could solve the issue.
The car is a Punto EVO. I haven't tried any other Bluetooth devices, but I expect the same result.
I'll flash a new rom and report back. Thanks for replying.
roytje88 said:
Good to know it's only a problem what's occurring on my phone. That would mean flashing a different rom could solve the issue.
The car is a Punto EVO. I haven't tried any other Bluetooth devices, but I expect the same result.
I'll flash a new rom and report back. Thanks for replying.
Click to expand...
Click to collapse
yeah, reflash the same ROM or try a different one. Back in the day, there were tons of issues with stuff that was designed to work on the phone based on specific kernel programming that spoke to the hardware to allow these features to physically operate, but only in touchwiz based ROMs, AOSP based ROMs were left out in the cold. With the emergence of the necessity of a clean knox in order for certain things to work, i have given up on root for the time being so that i can enjoy the awesomeness that is paying for stuff with my watch (which requires an unrooted phone to work. Technically your phone can be rooted but it makes it a pain in the anus)
anyways, i think your audio issue might be a GSI specific thing, just a hunch tho. Might want to go look in the GSI threads and see if there is a list of what works/whats broke in the ROMs. They usually just come out and tell you if ti doesnt work because if its the other way around, the devs reputation will be tarnished
I flashed Lineage OS 16 (Android 9) GSI. Same problem. Also with other Bluetooth devices. I'm thinking it's the vendor I flashed. I did find an Oreo vendor for this device mentioning Bluetooth calls don't work.
Searched for a rom without Treble but couldn't find one that has December security (or November). For now I'll use my earbuds when calling from the car.
I could flash a number of images, but don't really want to the time of finding the perfect rom for my devices has passed. I'll just keep this rom and when I feel like it, I'll flash the stock rom.
Thanks anyways for the advice!