There was a Samsung Galaxy GIO, became "Nedo - Samsung Galaxy ACE"
Hello!
In short, I want to tell you about my experiment and please do not condemn. I do not recommend you to repeat it)
After failures in communicating with the Euroset about the return of the “hanging” Samsung Galaxy GIO GT-S5660 (hung 5 to 10 times a day), I decided to leave it in order to reflash to some custom firmware, since KIES firmware did not solve the problem. Well, actually, I did not find custom firmware for GIO and took it from Valiant with Android 2.3 for ACE. With ODIN, I implemented this nasty transformation of GIO into ACE. In general, this is what happened:
1. The device is sure that it is ACE
2. The accelerometer thinks that the correct position of the phone is turned on its side. (solved by turning off the auto-rotate screen)
3. The upper part of the rocker is no longer volume up, but the Home button.
4. Camera lost
5. A small artifact on the main screen (firewood bug for video)
But everything else works very fast, surprisingly the battery didn’t crawl up to one half in a day (perhaps a bug with capacity calculation, it’s possible)
')
Well and most importantly, can someone tell me how to get back to the GIO now? ) For this, I already have a .zip with the original firmware, but it is not possible to deploy it due to the lack of memory in rom.
There is a GIO kit for ODIN, but when you switch the phone to Emergancy Dwnd mode, it is determined by ODIN, but when I start the recording process, the timer goes on indefinitely, but does not write anything to rom. Here in such a deadlock came)
Or maybe there are experts and craftsmen who will help me “finish” GIO to ACE by installing the right firewood for the camera, display and accelerometer?
ps: I got access to the device via ssh, commands from under root can be executed. As I understand it, the recovery section serves as a kind of pre-bootloader. Maybe at this level, you can register something to force recovery to deploy the firmware image in memory cards? This is just a guess, I can be wrong.
In advance, I apologize if the post is not worthy of the selected blog, but I would like to hear tips and opinions. Can advise any resources and forums.
In short, I want to tell you about my experiment and please do not condemn. I do not recommend you to repeat it)
After failures in communicating with the Euroset about the return of the “hanging” Samsung Galaxy GIO GT-S5660 (hung 5 to 10 times a day), I decided to leave it in order to reflash to some custom firmware, since KIES firmware did not solve the problem. Well, actually, I did not find custom firmware for GIO and took it from Valiant with Android 2.3 for ACE. With ODIN, I implemented this nasty transformation of GIO into ACE. In general, this is what happened:
1. The device is sure that it is ACE
2. The accelerometer thinks that the correct position of the phone is turned on its side. (solved by turning off the auto-rotate screen)
3. The upper part of the rocker is no longer volume up, but the Home button.
4. Camera lost
5. A small artifact on the main screen (firewood bug for video)
But everything else works very fast, surprisingly the battery didn’t crawl up to one half in a day (perhaps a bug with capacity calculation, it’s possible)
')
Well and most importantly, can someone tell me how to get back to the GIO now? ) For this, I already have a .zip with the original firmware, but it is not possible to deploy it due to the lack of memory in rom.
There is a GIO kit for ODIN, but when you switch the phone to Emergancy Dwnd mode, it is determined by ODIN, but when I start the recording process, the timer goes on indefinitely, but does not write anything to rom. Here in such a deadlock came)
Or maybe there are experts and craftsmen who will help me “finish” GIO to ACE by installing the right firewood for the camera, display and accelerometer?
ps: I got access to the device via ssh, commands from under root can be executed. As I understand it, the recovery section serves as a kind of pre-bootloader. Maybe at this level, you can register something to force recovery to deploy the firmware image in memory cards? This is just a guess, I can be wrong.
In advance, I apologize if the post is not worthy of the selected blog, but I would like to hear tips and opinions. Can advise any resources and forums.
Source: https://habr.com/ru/post/120725/
All Articles