Related
Hi folks,
So I decided to let my old&trusty TYTN2 retire peacefully and be a backup phone - bought an almost unused HD2. Cool, love the phone. Looks good and is reaaally snappy&fast.
But I'm kind of stirred by its frequent crashing and then getting stuck on white boot screen. It appears on random occasions when the phone has to do some thinking - end call, connect to PC, after inserting PIN, app start. Nothing really intensive going on.
The phone has a custom rom: Elegancia v1.0 Final WWE dating 28.07.2010
Radio version 2.08.50.05, Protocol 15.34.50.07U and the third number displayed on boot screen is "D 2.13.90963 8G"
The problem could be connected to overheating mentioned in a couple of threads, but nevertheless I have some questions.
1. Is there a possibility of the issue resulting from a faulty ROM so a reflash would do the trick?
2. Apart from getting a new motherboard or improving the cooling system described in the thread http://forum.xda-developers.com/showthread.php?t=982454 - are there any other solutions to the issue?
3. If I need to take the phone to the warranty there is a high chance that they won't like the custom ROM job so I'll have to flash a stock ROM to make it look good. Where do I get one?
4. Is there anything else specific I'd have to keep in mind?
zandhorn said:
Hi folks,
So I decided to let my old&trusty TYTN2 retire peacefully and be a backup phone - bought an almost unused HD2. Cool, love the phone. Looks good and is reaaally snappy&fast.
But I'm kind of stirred by its frequent crashing and then getting stuck on white boot screen. It appears on random occasions when the phone has to do some thinking - end call, connect to PC, after inserting PIN, app start. Nothing really intensive going on.
The phone has a custom rom: Elegancia v1.0 Final WWE dating 28.07.2010
Radio version 2.08.50.05, Protocol 15.34.50.07U and the third number displayed on boot screen is "D 2.13.90963 8G"
First thing I would do is update this as it is a older rom, Here is a link to the Elegancia thread if you want to just update to the latest version of that ROM. Also update your Radio to a the 2.14.50.04 or the 2.15.50.14 radio linked in the OP of the thread.
The problem could be connected to overheating mentioned in a couple of threads, but nevertheless I have some questions.
1. Is there a possibility of the issue resulting from a faulty ROM so a reflash would do the trick?
Answered above.
2. Apart from getting a new motherboard or improving the cooling system described in the thread http://forum.xda-developers.com/showthread.php?t=982454 - are there any other solutions to the issue?
Nope, not for the over heating problem.
3. If I need to take the phone to the warranty there is a high chance that they won't like the custom ROM job so I'll have to flash a stock ROM to make it look good. Where do I get one?
Go to htc.com and enter your serial number (under the battery) to get a list of ROMs for your HD2 and download it from there. Also make sure you or on the HTC site for your country or the country the HD2 originally cam from, there is links to the other countries sites on any of the HTC sites. Also make sure you flash it via SD card as this will revert everything at one time.
4. Is there anything else specific I'd have to keep in mind?
Yes If you have a T-Mobile HD2 you can not flash a 2.04.50.xx, 2.05.50.xx, or any x.xx.51.xx radio to it as it will brick a T-Mobile HD2.
Click to expand...
Click to collapse
Hope this helps.
Thanks a lot for a quick answer!
And another question: The phone looks like an ordinary HD2 - non-coloured buttons and no T-mobile signs anywhere. And it was bought in Estonia, albeit imported from Czech Republic - had to DL new soft from czech site. But I'm somewhat puzzled by the Model No in phone identity app: It says "T-Mobile_LEO.."
Now is that conclusive evidence or could it come just from the Elegancia ROM?
How do I make sure if the phone is actually a T-Mo or the ordinary one?
zandhorn said:
Thanks a lot for a quick answer!
And another question: The phone looks like an ordinary HD2 - non-coloured buttons and no T-mobile signs anywhere. And it was bought in Estonia, albeit imported from Czech Republic - had to DL new soft from czech site. But I'm somewhat puzzled by the Model No in phone identity app: It says "T-Mobile_LEO.."
Now is that conclusive evidence or could it come just from the Elegancia ROM?
How do I make sure if the phone is actually a T-Mo or the ordinary one?
Click to expand...
Click to collapse
Sorry for the lag in response her just managed to get back this part of the HD2 forums. If you look in your settings>about phone>hardware information and the flash size says 1024 it is a T-Mobile Leo, if it says 527 it is not. Also I am doing this from memory as I am running Android from NAND so it might be under software information, but i am fairly confident it is in hardware information. And yes it probably says T-Mobile Leo because the Elegancia ROM started as a standard 3.14 T-Mobile stock ROM and then the ROM chief modified the ROM.
OK, the hardware information says that theres 576Mb of RAM and 512Mb of flash. So I guess it's a non-T-mo phone. Thanks!
I'll probably be back with more questions, though
Well-well-well.
Long time no see.
The situation seems to be getting solved soon.
Took the phone to the repairs where they first reflashed it with the original firmware - they had to keep the phone in the *fridge* to do it successfully and avoid overheating.
So it didn't really solve anything and to the mobo change it was - luckily I could cut a good deal and the seller of the phone will pay for the repairs so the thread can be closed as a success story.
Will be back though - boys&toys. Will have to upgrade stuff, y'know.
Hi all,
My Galaxy S II keeps crashing. The phone will just power off and the battery will drain right out and the only way to turn it back on is take the battery out then charge it again. Sometimes if I am quick and realised it has crashed I can take the battery out and turn it back on and the battery will have drained 30% in an hour.
Does anybody know why the phone might do this or is there a way I can track whether something in particular is crashing the phone via a log or something like that?
Thanks
Yes there are apps that can do that.
So whats the score.......are you on latest o2 or latest unbranded.
Post the about phone details lol.
Hi,
It is on the latest H3G UK firmware and is unlocked via the Galaxy S Unlock app by Helroz (so via nv_data.bin)
4.0.4
I91000NELP4
Build: IMM76D.XWLPY
Any ideas and what is the app called?
Thanks
Hello,
Just thought I would take this opportunity to join this thread since I have been suffering from a very similar (if not identical) problem on my S2 too. It's quite lengthy, apologise for that - hope to give as clear a picture as possible:
- S2 originally from vodafone contract, am now with giffgaff
- 1 year and 6 months old
- not rooted, have always used Samsung official firmware
- updated to ICS 4.0.4 about a month ago(?)
- Kernel version 3.0.15-1056084, build number: IMM76D.BULPG
I must say I can't be certain if the random crashes started (it would sometimes heat up really hot, or sometimes not warmed up at all), phone will just turn off. Can't turn back on without taking battery out and re-inserting.
Similarly, the battery level will drop by 30+% once the battery is re-inserted.
Have experienced once where it started up in "safe mode" and although everything was still there, the apps I have put in folders were all listed cos the folders were gone. Restarted and it wasn't in safe mode anymore, but had to create new folders and sort my apps again.
The random turn offs can happen every few days, or twice a day. Don't know why it happens.
I haven't installed many new apps (some are by japanese developers but worked fine before and after I updated firmware), asked at a Vodafone store and they suggested it could be a battery problem. (offered to send it off for repair, but will take 7-10days and factory reset, which I want to avoid...)
So bought and changed a new battery (from Samsung website) which looked good (no random shut downs for a week) but it all started again last night. So it's not the battery.
Suspected it's most probably software problems.
After upgrading to 4.0.4 firmware, the phone cannot display phone serial number/network etc etc under the "legal information" in settings.
The battery log seems funny too, I would re-insert battery and restart, the battery log will still show it's been on battery for 20+hours.
I've also spotted that there're 2 OS running when looking at the battery log - when I upgraded from gingerbread to ICS, I did not do a factory reset (is that absolutely necessary?) but phone has been working perfectly for a few months after the upgrade so I thought nothing of it....
I wanted to post a screenshot but not allowed cos I'm new to forum... =(
Is it because there're 2 OS so it's clashing...?
Since I haven't rooted, I'm not sure what I can do - last resort is to wait until JellyBean rolls out from Samsung and factory reset when I upgrade?!
Hope I've given enough info to get help easier.
PS: Kies is testing my temper. Tried to solve the "this device is not supported by KIES" problem by reinstalling whilst not connected to internet, kind of worked, allowed me to backup small files (such as call logs) but when it comes to big bits e.g. photos, it will show the "unexpected error" message again.....
also got "wssyncmlnps has stopped" on my phone...
ARGH!!! just wana backup my stuff before it completely turns into a brick!
zetsuboumeow said:
Hello,
Just thought I would take this opportunity to join this thread since I have been suffering from a very similar (if not identical) problem on my S2 too. It's quite lengthy, apologise for that - hope to give as clear a picture as possible:
- S2 originally from vodafone contract, am now with giffgaff
- 1 year and 6 months old
- not rooted, have always used Samsung official firmware
- updated to ICS 4.0.4 about a month ago(?)
- Kernel version 3.0.15-1056084, build number: IMM76D.BULPG
I must say I can't be certain if the random crashes started (it would sometimes heat up really hot, or sometimes not warmed up at all), phone will just turn off. Can't turn back on without taking battery out and re-inserting.
Similarly, the battery level will drop by 30+% once the battery is re-inserted.
Glad to know it is not just me. I'm hoping I can get an app that will log what is going on right up until crash time!
Have experienced once where it started up in "safe mode" and although everything was still there, the apps I have put in folders were all listed cos the folders were gone. Restarted and it wasn't in safe mode anymore, but had to create new folders and sort my apps again.
The random turn offs can happen every few days, or twice a day. Don't know why it happens.
I haven't installed many new apps (some are by japanese developers but worked fine before and after I updated firmware), asked at a Vodafone store and they suggested it could be a battery problem. (offered to send it off for repair, but will take 7-10days and factory reset, which I want to avoid...)
So bought and changed a new battery (from Samsung website) which looked good (no random shut downs for a week) but it all started again last night. So it's not the battery.
Suspected it's most probably software problems.
After upgrading to 4.0.4 firmware, the phone cannot display phone serial number/network etc etc under the "legal information" in settings.
The battery log seems funny too, I would re-insert battery and restart, the battery log will still show it's been on battery for 20+hours.
I've also spotted that there're 2 OS running when looking at the battery log - when I upgraded from gingerbread to ICS, I did not do a factory reset (is that absolutely necessary?) but phone has been working perfectly for a few months after the upgrade so I thought nothing of it....
I wanted to post a screenshot but not allowed cos I'm new to forum... =(
Is it because there're 2 OS so it's clashing...?
Since I haven't rooted, I'm not sure what I can do - last resort is to wait until JellyBean rolls out from Samsung and factory reset when I upgrade?!
Hope I've given enough info to get help easier.
PS: Kies is testing my temper. Tried to solve the "this device is not supported by KIES" problem by reinstalling whilst not connected to internet, kind of worked, allowed me to backup small files (such as call logs) but when it comes to big bits e.g. photos, it will show the "unexpected error" message again.....
also got "wssyncmlnps has stopped" on my phone...
ARGH!!! just wana backup my stuff before it completely turns into a brick!
Click to expand...
Click to collapse
So glad it is not just me. I'm hoping I can use an app to log what is going on when crash time happens. Can someone tell me what the app is called please?
Rackers said:
So glad it is not just me. I'm hoping I can use an app to log what is going on when crash time happens. Can someone tell me what the app is called please?
Click to expand...
Click to collapse
Me too facing above all,unfortunately riding in same boat.
I have been having this problem pretty much since day 1, I've also searched the Nokia Support Discussions and it seems quite a lot of people are experiencing this. I was actually surprised that my Go-To forum here at XDA doesn't have a thread on it.
My Black Lumia 920 (EE, Phones4U, Unlocked) reboots on average about 5 times a day. Yesterday was probably the worst yet with roughly 8 reboots. That may have been more noticeable to me because I used a SIM which requires a pin though.
What I've noticed:
-The device is roughly 10 days old.
-It has been rebooting an average of 5-8 times a day
-It mostly reboots when idle (so when I'm not using it)
-I've had it reboot only twice while in use when making a call
-I've had it reboot only once when playing music.
-I've only ever noticed it rebooting when it is face up
-Rebooting happens regardless of the SIM (although I have not used it without a SIM at all) (Used both a micro SIM and a SIM cut down to size, used the original carrier SIM and other SIM, no difference to rebooting behaviour)
-I only turn on the radios I need when I need them, so 2G active 100%, 3G/4G, WiFi, Bluetooth, GPS, NFC off for 70% of the time.
-It is not due to battery drain as I usually have about 40% battery at the end of the day.
This has been my experience with the rebooting problem. The figures and estimates I'm giving are not over stating and I've tried giving as much detail so as to try and provide useful information for a solution.
Has anyone else been having this problem?
Has anyone found a working solution?
Has anyone heard or read anything concerning a fix for this?
nope - blue one on AT&T
I'd look at your installed apps, apps enabled to run in the background, etc. It should not be rebooting at all.
I have seen some posts like yours on the internets, but its not a "common" as in most 920s do it problem. Which leads me to think its some issue with an app or apps installed on some phones.
Possible solution
Hi kyrirhcp
I had a similar problem. I reset the phone which bricked it and then used this tutorial to un-brick it:
http://forums.wpcentral.com/nokia-l...after-reset-flash-process-defined-inside.html
The only difference is that I downloaded the "Nokia Data Package Manager" (not sure where from but I'm sure you can find it). This software allows you to download the firmware files directly into the correct folder. You could also look at this tutorial:
http://aydon.wordpress.com/2012/11/29/how-to-flash-your-lumia-920english/
The ROM you want is the EE specific one. It even specifies the colour of the phone. The version number is: 1232.2110.1244.3011
If you reset the device and it does not brick (i.e. freeze up on reformat) then the problem is solved and you don't need to worry. If it bricks (which it probably will) then you need to flash to recover the phone.
God bless
andrew-in-woking
Hi Andrew, thanks for your suggestions but I'm avoiding it like the plague if I'm honest. Resetting my phone and risking a brick, even with your added fix tutorial really doesn't seem worth it. Also I'm assuming that the problem you PM'd me with regarding the loss of some functionality is a result of the fix you suggest. I'm not yet willing or ready to f with my device the same way as I did with my SGNote, even more so since developers haven't yet gotten the experience they have with android. Anyway, i seem to have perhaps solved the problem at least for my device. I changed the regional settings for a completely unrelated matter and I have not since had a single reset or the accompanying massive battery drain. It's now been 3 days. The only other change was that I removed tunein radio an reinstalled it. So it seems that my problem has been solved (fingers crossed, knock on wood, ftou ftou ftou, wearing an evil eye). I hope this helps others with their problems and makes this amazing device useable to those that had this problem.
Sent from my RM-821_eu_euro1_342 using XDA Windows Phone 7 App
Try removing Whatsapp if you've got that installed.
I have had a lot of the same problems. My phone locks up a few times per day. This is the 2nd Lumia 920 I've had. After getting the second with the same problem, I decided to wait for the Portico update that was supposed to address random restarts.
Since then, I've been communicating with Nokia and Windows Phone support on twitter. All they suggest is uninstalling apps, disabling radios, contacting individual developers, and resetting your phone.
I have a hard time wrapping my mind around that. How is it possible for a user level application to take down the whole operating system/firmware?? There are plenty of crappy apps on the Windows Phone Store, I don't think it should be up to me to figure out which is destroying my experience.
I used to root/hack all my old Windows Mobile phones/android phones. When it locked up, it really was up to me to fix it and figure it out!! I chose Windows Phone since it had the locked ecosystem similar to Apple. While that may not appeal to everyone, I have a very busy life and I don't want to spend more time screwing with my phone. It just needs to work! This is my 3rd Windows phone and it's been the worst so far.
Hello:
So, the bottom line up front is I need help solving a problem with my now third, new Verizon Samsung Galaxy S4--it keeps restarting on its own, at random times, but most often after I lock the screen.
To go in more depth, if you think you may know the solution: I purchased the S4 when it first came out, some time in 2013 (not sure specifically, but it was new) and it worked just fine for 13 months (1 month past the warranty of course); this was back in August, when I got the latest Android update pushed to my phone from Verizon (4.4.2). A couple of weeks later, I would occasionally get overheating warnings that would very quickly disappear (like within a few seconds), and then the device started restarting itself... I cannot predict when it will restart, it's random, but like I said above, it usually happens most right after I lock the screen by pressing the right side button once. I started looking around on the internet for a solution then, but only found a couple of videos from earlier in 2013 where people were having battery problems (Google search has been letting me down more and more as the years pass). One day while at work, I was listening to Pandora as I always have with the phone in my front pocket, as I always have. A few hours later when I got home, not having taken the phone out of my front pocket since those last few hours at work, I went to answer a text message I had received; when I unlocked the phone, the screen was black, except for a small bit of white showing through some cracks UNDER the LCD, UNDER the screen protector, INSIDE my Otterbox Defender... the phone appeared to be working still, but the screen and touch screen did not. At that point I was pretty damn irritated and tried to find answers for a week with no luck... I called Verizon, they sent me on a goose chase to Samsung, who sent me back to Verizon, who got me in a conference call with Samsung and then left the call, and then Samsung ultimately said I would need to pay for repairs to the phone... SO... I went back to Verizon who again said I would have to talk to Samsung, but instead I just settled to giving Asurion (my phone insurance through Verizon, whom I pay an extra $9 monthly) $99 as a deductible to get a replacement S4...
Two days later I receive a brand new S4... spend hours setting it up the way I had my prior one... wasting tons of my valueable time to do so and bandwidth from my Concast ISP and the data cap they've decided to give us... one week later, the phone starts restarting itself... and this one did it more often than my prior one... EVERYTHING is up to date, minus a good amount of useless bloatware apps I never use from Samsung, like "Watch On," which I ignore... but everything necessary, I update. So, I go back to Asurion, who quickly ships me a 3rd S4...
Two days later I receive that third, brand new S4... spend hours setting it up the way I had my prior one... and now, this one is also restarting itself randomly. Interestingly, when I visited family for Thanksgiving, it restarted itself over and over and over much more frequently than when I'm at my place... at my family's place, they have very poor reception, and my phone usually has to work more to try to get the signal... IDK what the deal is, but maybe that information can be helpful to y'all.
Other things to note:
1) When I check the "RAM manager" by holding down the home button and then choosing "Task Manager", the phone is always using at least 800MB of 1.77GB of RAM... even when I choose "Clear memory" and it tells me 30 something apps have been closed... it jumps right back up to 800-900MB of usage.
2) I've tried factory resets on all three phones; with the first one where the screen cracked inside, I hooked the phone up via HDMI... within a couple of days, the restarting begins.
3) With the first replacement I received, I could not sent text messages with the default messenger app... and shortly after trying, it would restart.
4) I have used the same SIM card with all three phones since the issue began, when I first got the 4.2.2 update... I do not suspect the SIM card is the problem, but I'm also not savy with the phone... I know my way around it, but I'm not in the know.
5) I thought maybe it started because of some apps I had been trying, so I had deleted them, and the problem still persists.
6) I constantly have a Pebble Bluetooth smart watch connected to the phone... I have since I got it last Spring (2014).
7) I have never rooted the S4, overclocked it, underclocked it, or modded it in anyway because I do not know how, and I was afraid of what could happen in the future with whatever ROM I did flash onto the device if Verizon tried to push an update to it... I just don't know anything about the whole process, and I'm assuming it requires a lot of know how and babysitting of the device... I just want it to work.
8) I've replaced the battery twice; it doesn't seem to be the problem.
9) I've cleared the cache through the boot manager thing gotten to by holding a combo of buttons on the device while it's rebooting... it did not help.
Edit: 10) Today while I was listening to Pandora in the car, the audio began to skip and scratch, and then it paused for a moment, and then the phone restarted itself.
11) I forgot to mention that the reboot process itself is very fast compared to a manual restart performed by me... the phone will go black, the Samsung color rings will show a second after that, the logo appears then, the screen flashes the red Verizon logo, and then the devices is ready to be used... it's less than 10 seconds.
I've been searching around on the internet for about two months now while dealing with the problem and I can't find anything useful. Does anyone here know what my issue is and how I can fix it? Is there a way to pull error logs / information from the S4 somehow to give to someone to diagnose, like DxDiags on PC? I don't know how to read that stuff myself, but I know it can be very useful... I just don't know how to find that info inside of these very locked down ****boxes we call smartphones...
I truly appreciate any help I can get--sorry I can't offer anything in return; if I can't find a solution, I'm just going to go to my backup phone from 2011 (Droid X), and I will definitely never purchase another Samsung device, especially after they blamed me as the cause of the problem without even seeing the phone...
Thanks.
The problem is with the NG6 software build, and "probably" not with your phone. Go to Settings>About Phone> and see what Baseband Version is on your phone. If the last 3 letters are NG6, that's probably the problem. There is a new OTA update (as of 12/1).....Baseband Version ending in NK1, which corrects the rebooting problem. Either install the new update, or go back to the NC5 baseband version and that should solve your problem. Both NK1 and NC5 can be rooted if you desire.
This is specific to India for those who purchased the LG G8X ThinQ from "FlipKart" specifically the 'Made in Vietnam' Main & the dual display case both. I did not switch on the device out of the box and first directly put it on charge and typically any other phone would start charging in the powered off mode just showing a battery graphic icon with the percentage charge and any accompanying charging symbol or text but in case of this phone what happened was, I got a Circle with a "ERASING' text message for a brief less than 5 seconds and rather the phone switched on instead of charging (though it started charging after powering on) and I was forced to continue setting up the phone.
But upon seeing a lot on YouTube and also reading comments, practically everyone faced this issue even if they directly booted the phone without putting it on charge. This is weird, not acceptable, concerning and worrisome. If anyone can advise why this issue happened and if it can cause any future problems, please share your knowledge and also would request all Indian Buyers to tweet to LG India, send them a DM on Twitter and also on LG India Mobile on Facebook and also send a email to them. When they will get pressure of their Rs.320 crores buyers all together, they will have to reply. Please reply if you get any response from LG. Thanks!
i ll get my phone tomorrow. let me see if i too get the same message. but i hope its fine and there is no issue due to that 'ERASING' message
RAD7 said:
This is specific to India for those who purchased the LG G8X ThinQ from "FlipKart" specifically the 'Made in Vietnam' Main & the dual display case both. I did not switch on the device out of the box and first directly put it on charge and typically any other phone would start charging in the powered off mode just showing a battery graphic icon with the percentage charge and any accompanying charging symbol or text but in case of this phone what happened was, I got a Circle with a "ERASING' text message for a brief less than 5 seconds and rather the phone switched on instead of charging (though it started charging after powering on) and I was forced to continue setting up the phone.
But upon seeing a lot on YouTube and also reading comments, practically everyone faced this issue even if they directly booted the phone without putting it on charge. This is weird, not acceptable, concerning and worrisome. If anyone can advise why this issue happened and if it can cause any future problems, please share your knowledge and also would request all Indian Buyers to tweet to LG India, send them a DM on Twitter and also on LG India Mobile on Facebook and also send a email to them. When they will get pressure of their Rs.320 crores buyers all together, they will have to reply. Please reply if you get any response from LG. Thanks!
Click to expand...
Click to collapse
Yes, even I noticed it on the first boot, I can see only two possibilities, 1. LG updating the software (android 10) on Refurbished / unsold products from other countries and factory reset the device and update to Android 10. Since there is no charger inside the box ( Different countries have different socket and Power Standards) and LG India has confirmed on Twitter that It's not a Refurbished product, I believe that it is the latter (unsold products).
Yashaskm11 said:
Yes, even I noticed it on the first boot, I can see only two possibilities, 1. LG updating the software (android 10) on Refurbished / unsold products from other countries and factory reset the device and update to Android 10. Since there is no charger inside the box ( Different countries have different socket and Power Standards) and LG India has confirmed on Twitter that It's not a Refurbished product, I believe that it is the latter (unsold products).
Click to expand...
Click to collapse
Is rooting available for vietnam model:crying:??
Yashaskm11 said:
Yes, even I noticed it on the first boot, I can see only two possibilities, 1. LG updating the software (android 10) on Refurbished / unsold products from other countries and factory reset the device and update to Android 10. Since there is no charger inside the box ( Different countries have different socket and Power Standards) and LG India has confirmed on Twitter that It's not a Refurbished product, I believe that it is the latter (unsold products).
Click to expand...
Click to collapse
Been hearing a lot about this refurbished thing, can clearly state the product is not at all refurbished. Now whether they are selling unsold stock from other countries here in India does not matter as it's a brand new phone and I am telling you, it's great that it is an imported device. Sad but true, locally made electronics have faced a lot of issues, even MI products of late made locally. They have factory installed Android 10 out of the box and then mostly every device gets some sort of an Android update, note update and not upgrade. Android 11 will be an upgrade later but that Erasing message with brief circle is strange as because in my case I had not even switched on the phone but simply attached charger but it started by way of booting up. Any other phone will simply start charging in off state and boot only when you explicitly press on the power button. I have tweeted to LG last night for a response, request everyone to do so.
AbuAzlan said:
i ll get my phone tomorrow. let me see if i too get the same message. but i hope its fine and there is no issue due to that 'ERASING' message
Click to expand...
Click to collapse
Please also do not insert main device in to case until fully booted. Fulfill the android update and then put it in case, while doing so please observe keenly the process of firmware upgrade which is shown for the dual case. In my experience, I got the message and I did not touch the phone while firmware was being upgraded but there was no message or indication stating that firmware was successfully done. Do check and share your experience.
RAD7 said:
Please also do not insert main device in to case until fully booted. Fulfill the android update and then put it in case, while doing so please observe keenly the process of firmware upgrade which is shown for the dual case. In my experience, I got the message and I did not touch the phone while firmware was being upgraded but there was no message or indication stating that firmware was successfully done. Do check and share your experience.
Click to expand...
Click to collapse
Yeah i too didn't get any finished or successful notification i just leave it for a few min