Quote:
Originally Posted by rupor
If AMR installation was successful - you should see 3 pages not two.
If AMR is not successful - it is more than likely that when you were trying to apply Apps2SD your system partition did not have enough free space to install kernel modules or new vold. So now you have unfinished installation...
Try to connect via serial gadget - and take a look at logs (logcat or dmesg - regular Linux way).
This may give some idea of what is wrong and how to correct it.
|
Thanks for your answer.
I reboot using the sd from "rupor_rescue".
In attachment the output for dmesg
This is the output from version_check.sh
[root (ttyGS0)]# version_check.sh
NAND :1.0.04.12210
MBR :N/A
uBoot :1.0.00.09010
Boot Env :1.0.00.09010
Reserved1 :N/A
Normal Kernel :1.0.04.12210
Normal Rootfs :1.0.00.09010
Recovery Kernel :1.0.00.09010
Reserved2 :N/A
Normal Boot Env :1.0.00.09010
Recovery Boot Env :1.0.00.09010
Raw Data Table :1.0.00.09010
Info :1.0.00.09010
Id :1.0.00.09010
Reserved3 :N/A
Boot Image :1.0.00.09010
Waveform :1.0.00.09010
LOG :N/A
Recovery Rootfs :1.0.00.09010
Diag :1.0.00.09010
READER :1.0.00.09010
fonts :1.0.00.09010
dictionaries :1.0.00.09010
SETTING :1.0.00.09010
preload :1.0.00.09010
data :1.0.00.09010
system :1.0.04.12210
EPD :0706A400030B01233C31
Sub CPU (firmware) :2011/08/09 :32
Sub CPU (updater) :2011/05/31 :1
OK
Using the same rescue firmware with Diskinternals Linux Reader I can see the disk. So in this way under linux I can mount them and modify them as needed.
I see which command I have in this console and the script "factory_reset.sh" seems to be very interesting!
Should I run it?