Hi.
EDIT: Update Info added at the end of the page.
I hope someone will be able to help me.
First I apologize if this question already exist, but I'm too tired, and I hope there won't be a lot of grammar errors.
My brother had some error with LG Optimus L7 saying "Modem crash has been occured".
But first more details.
As I said:
LG Optimus L7 is what he is using.
He have few apps installed: sofascore, avg, viber, WhatsApp - I will be able to write full list of apps later this day.
Yesterday he update it to newest version of android - "Android 4.2, Jelly Bean"
There wasn't any problem for the whole day;
And then in the morning something happened with the phone.
And this message was on the phone - And since the picture I had taken with another phone is little doubled I hope I will write what does the error says correctly :
-----------------------------------------------------------------------------------------------------
Modem crash has been occured
Please do following action
Capture this screen
Get ramdump file from "OPBT" (I think) - Memory Debug App Tool
Send email to (I think it says) [email protected]
-----------------------------------------------------------------------------------------------------
ERR crash log report, Version 2. - Does this mean that there was also another crash......if yes, did phone restart itself then.....and is it possible to restart itself.
Error in file NV (I think), line 0
Time of crash.... some time - 3 a.m.
Now it says something I can't read.....
Build ID: PF00-M722FA-V20a-MAR-08-2013-XX - something like this.
REX-TOB ptr: 0x2?4f6300 ?-means something
tCD: task_name: DOO
Register values from nex (I think) core:
And now there is ~15 more or less "errors" which I can't read, but they say this I think:
ARM_SWC_R0 : 0x0A0A0A0A
ARM_SWC_R0 : 0x000000000
.........
ARM_SWC_R10 or RT0 : can't read.
ARM_SWC_R10 or RT0 : can't read.
ARM_SWC_R12 or RT2 : can't read.
More likely it is R12 and R10.
........
What else I can read:
ARM_JVH_SPSR : 0x00000000
....... - means that Error repeat itself or I can't read it so I can't write it
And it is possible that SWC is actually SVC
Above is on the left column, and this is on the right one:
ARM_SVC_R1 : 0x00000000
ARM_SVC_R3 : 0x00000000
ARM_SVC_R5 : 0x00000000
ARM_SVC_R7 : 0x00000000
ARM_SVC_R9 : 0x00000000
ARM_SVC_R11 : 0x00000000
ARM_SVC_CP (I think) : 0x00000000
.........
ARM_CPSR : 0x00000000
Click to expand...
Click to collapse
Also - the battery drained a lot, from 70% (12:30 am - 8 a.m.) to 10%, even more.
Also, it is a new Phone, 1 week old, so it is still under warranty if this is some bigger problem.
Thank You for your help, hope someone knows what could be the problem, any advice appreciated.
Should we worry about this.
EDIT: Update Info:
It seems that "we" needed to "restart" the phone after we update it. (Since the phone restarted itself after the update we didn't think about that then)
And that Notice we didn't saw anywhere till yesterday on some forum.
After that day, after phone crash error has appeared - ALL works perfectly since then.
All improvements by Update you can really notice, especially about battery, battery drain is a lot slower with this new update.
So, I could say that the problem is solved. If one day repeat itself, I will be back.
Thank YOU!
Best Regards
Related
seeing as how im new to the forums and i dont have 10 posts yet so i cant post in the developers forum, i'd like to extend my thanks here. i HAD a locked ATT x10 with 1.6. i was concerned about backing up my phone since ATT locked the ericsson backup & restore application. so i found the APK and downloaded it on my laptop, i then sideloaded it with android sdk via adb install and was able to back everything up before hand. i then continued with the flashtool 0.2.5 version and bundled the decrypted 2.1 ROM. i continued with the flash as instructed (including wipe userdata) and i got a flashtool log of:
24/036/2011 10:36:51 - INFO - <- This level is successfully initialized
24/036/2011 10:36:51 - INFO - Starting adb service
24/037/2011 10:37:21 - INFO - Preparing files for flashing
24/037/2011 10:37:56 - INFO - Searching for Xperia....
24/037/2011 10:37:57 - INFO - Found at USB\VID_0FCE&PID_ADDE\5&CDE1754&0&1
24/037/2011 10:37:57 - INFO - Start Flashing
24/037/2011 10:37:57 - INFO - Sending loader
24/037/2011 10:37:57 - INFO - ### read failed : checksum err! FFFFFFFF!=CBEF977B
24/037/2011 10:37:59 - INFO - Loader sent
24/037/2011 10:37:59 - INFO - Flashing kernel.sin
24/038/2011 10:38:03 - INFO - Flashing amss_fs.sin
24/038/2011 10:38:03 - INFO - Flashing system.sin
24/041/2011 10:41:15 - INFO - Flashing dsp1.sin
24/041/2011 10:41:20 - INFO - Flashing fota1.sin
24/041/2011 10:41:24 - INFO - Flashing fota0.sin
24/041/2011 10:41:25 - INFO - Flashing amss.sin
24/041/2011 10:41:33 - INFO - Flashing userdata.sin
24/041/2011 10:41:37 - INFO - Flashing cache.sin
24/041/2011 10:41:40 - INFO - Flashing finished.
24/041/2011 10:41:40 - INFO - Now unplug the device and power it on
24/041/2011 10:41:40 - INFO - Then go to application settings
24/041/2011 10:41:40 - INFO - turn on Unknown Sources and Debugging
i tried flashing the first time and noticed the 24/037/2011 10:37:57 - INFO - ### read failed : checksum err!
i turned the phone back on and it restarted with the old 1.6 still intact with no changes. i then proceeded to try the process and second time and I got the same error except this time the flash process took much longer. i thought i bricked my phone as it tried to boot and showed me a picture of a camera and then the SE logo for a long time... i proceeded to wait and VOILA! even with the checksum error 2.1 is loaded and i was able to restore my settings with 2.1 installed. i havent found any errors yet and wifi seems to turn on just fine.. havent found a single problem yet. does anyone know what this checksum error equates to?
but like i said everything seems to work as of now, i have to extend many thanks! i look forward to hopefully a stable 2.3 gingerbread in the future, thank you!
i have however noticed that instead of a "3G" connection i now see an "H", i went into "about phone" and "status" it says its using HSPA... is this bad? i know it stands for high spee packet access but im unsure of the transfers rate between it and 3g...but more importantly...why has it changed after upgrading to 2.1?
i believe "H" is faster then 3g and was just an added feature in 2.1
sure hope so...i wonder if theres a way to switch back if i want to...save battery life.
You can switch to gsm in wireless conections, mobile nets, net mode, and select only gsm (2g), so you can save battery but it is also slower. Sorry if the menu names doesn't match exactly, are translated form spanish version.
"H"
I gotta thank the devs for this tool also. Flashing, rooting, cleaning, optimising everything went fine on mine. What else can you wish for?
The H is totally normal and it is really faster than 3G...there's nothing to worry about
sagacious1 said:
i have however noticed that instead of a "3G" connection i now see an "H", i went into "about phone" and "status" it says its using HSPA... is this bad? i know it stands for high spee packet access but im unsure of the transfers rate between it and 3g...but more importantly...why has it changed after upgrading to 2.1?
Click to expand...
Click to collapse
H is for HSPA, as you've figured out. It is what AT&T was installing in 2010 while the other carriers were installing fake 4G. H is for 3.5G.
HSPA+ will be AT&T's first go with 4g, ultimately moving on to LTE. HSPA+ will be a high-speed fallback network for when AT&T fails to provide adequate data coverage. Neither of those will likely run on the X10, so the H is our last upgrade of that nature.
Sent from my X10a using XDA App
i know theres gotta be some high level gee wiz bang developer from either Sony or AT&T that can tell us whether or not the X10's transceiver will be able to run HSPA+ or LTE; whether it requires a software upgrade or not.
Hi there,
When I'm installing the rom ([ROM][31.01.2011][WWE-ITA-FRA-ELL-GER-RUS-SPA-NLD-DAN] ver 2.30 nsourm -build 23152), I get the following error:
ERROR [224] : Device not responding
This happens on WinXPx86 and Win7x64. No topic delivers an usefull answer.
I have used several roms from nsourm build 23152, but non were effective.
Is this a known issue, and does anyone have a solution for this?
With kind regards,
Raizy
Solved
I solved the issue due unpacking the DSL_SSP_MINI.zip with winrar.
Started the installation on a WinXP machine.
First time i got in the 3 colored screen and got again an error:246
Unchecked the following settings: start-->settings-->others-->USB-PC , both marks.
2nd time the installation did go complete!
I need help guys!!! Here is the thing i was using many roms starting from DFT LEO NAND to latest ICS, and with ICS instalation started with problems. hd2 started to crush while he was working and when i wanted to boot bootloader was loading and keep loading forever (using (Android 4.0.3) (AOSP ICS ROM for HD2) NexusHD2-IceCreamSandwich Beta10).
I used again ROM who was before ICS - NexusHD2-Gingerbread V3.2a (GWK74)(Android 2.3.7)[tytung_r13] and more roms using MALDGR >> all roms i install normaly and boot up and when i reboot they are going on Splash loader and keep it there forever. I tried all methods using task29, radio, magldr (installing again) still nothing and when i wanted to install DFT LEO NAND again i have error on the end of installation :
Error Description: send partition data failed
Info: .\RSPL\RSPL.cpp (802)
Error Description: flash write failed.
Info: .\RSPL\RSPL.cpp (586).
I tried to remove sd card and also did active sync detach still nothing
Any ideas.
Why will you type a whole message in bold?!
Looks like you're volumes keys may be stuck or acting up... I had this happen sometime back, ended up changing the main flex circuit strip.
Sent from my HTC HD2 using XDA
ph03n!x said:
Why will you type a whole message in bold?!
Looks like you're volumes keys may be stuck or acting up... I had this happen sometime back, ended up changing the main flex circuit strip.
Sent from my HTC HD2 using XDA
Click to expand...
Click to collapse
Sorry for my bold writing
i checked mu volume keys and everything is ok. Today i changed my radio and booted ROM everything was fine several time i rebooted and when i go in clockwork mode mode on botom of screen it is written somthing like E:/error/ recovery log etc etc. is it possible that i did something wrong with mu internal partition
here is the thing with DFT LEO NAND on my screen
USB Flasher mode
Wait USB...USB
Lauout...PC=4, ASI=3 OASI=5
Erase...
k = 25-> 23D 25 219, 1000
0: part = 37, part2 = 37
1: total = 1999, extra = 99
2: total = 320, extra = 16
[ASIZE] START: BB0 END: f40 SIZE: 390
PARTITION LAYOUT NEW
0: 0219 023E 50 89
1: 023E 0A70 50 01
2: 0A70 0BB0 50 01
3: 0BB0 0F40 20 01
Erase...
D S: 0 E: 219
D S: 1 E: 23E
D S: 2 E: A70
D S: 3 E: BB0
Save EMBR...
Default OS is AD NAND...
Flashing 0 partition...0 [219-23E] M1 OK 8B21 22C
Flashing 1 partition...1 [23E-A70] M1
and stuck loading on almost 90 %
There i get erroron DFT FLASHER:
Error Description: send partition data failed
Info:.\RSPL\RSPL.cpp (802)
Error Description: flash write failed.
Info: .\RSPL\RSPL.cpp (586)
Hi there,
I am actually trying to find a way to decrypt my phone (which was encrypted by a password, not a PIN code, which I set up, and I remember the password, no worries for that).
I actually have a root shell using adb, so I can dump everything on the phone.
My problems is that I don't really know how can I do it ?
I was thinking about a kind of brute-force in offline mode, to guess the secret password, but, the only tools I already found :
Edit: Sorry, i can't post the links, but :
Are both based on a PIN code, and I don't really know where I can find the required file (the footer, and the header), so it seems not working
Is someone already done that before, on a Galaxy S4 ?
Thanks in advance,
Regards,
4m0ni4c.
Ok, so i'm progressing !
Now I successfully found where is the major information I need to execute my script, i got :
Magic : 0xD0B5B1C5
Major Version : 1
Minor Version : 0
Footer Size : 216 bytes
Flags : 0x00000008
Key Size : 256 bits
Failed Decrypts: 0
Crypto Type : aes-cbc-essiv:sha256
Encrypted Key : 0x0000000000000000000000000000000000000000000000000000000000000000
Salt : 0x00000000000000000000000000000000
----------------
But because the Encrypted Key and the Salt seems not really good (Oh really ?) the next step is also not working well !
If someone have any idea why, I am not refusing any help ^^
Regards.
Hi Guys,
Has anyone tried the encryption feature found in Security settings? I'm using a recent nightly CM11 from Quarx/Blechd0se (Thanks, brilliant work!) quite stably for days now, but fail to make the encrypt phone function work...
When fully charged and USB powered, which are requirements, the successive encrypt phone buttons end up on a green android picture. This screen misses text and a progress bar which should normally appear on top of the screen, as seen on some screenshots. Even left for several hours, nothing progresses and a simple press on back button cancels action immediately which proves nothing has been encrypted in the meanwhile.
Took a Catlog and the only interesting message is the following:
Code:
01-02 01:34:23.732 E/Cryptfs ( 1197): Cannot get size of block device
In case it helps, find attached the output of mount command : View attachment mnt.txt
Could you have a look / help me out? (add to bug list if it applies)
In fact, for me, this function needs to be activated for connecting to my professional mails ...
Thanks in advance! :good:
Cheers
Further tested...
Hello all,
Just some more info... I flashed back to Quarx' CM9 and quickly tested once more the encryption and face the same problem but I didn't catlog, neither checked the mounts... Then I flashed Epsylon3's CM9 and quickly checked with the same result too...
But then I checked at catlog and now I get another type of error... Which is interesting and maybe promising as I already read some posts about this message...
Code:
04-14 21:11:13.101 E/Cryptfs ( 2219): Orig filesystem overlaps crypto footer region. Cannot encrypt in place.
Problem seems to be more general than only Quarx/Blechd0se's CM11 but a friend uses a CM9 flavor on a Samsung Galaxy S and has encrypted the phone successfully...
All in all it's linked with the filesystem (block device or not), how it is formated (yaffs/ext3/ext4) and mounted (mount/mount_all)...
Some interesting reading on jira.cyanogenmod.org/browse/CYAN-87 (not linked, I don't have 10 posts yet)...
Hope to find, test and come back with some more info soon...:fingers-crossed:
Cheers!