Hi
I'm using my phone (Lenovo A660) since more than two years.
Usually, I do not boot the phone to often (approximately once a month).
However, I recently realized when I turned of the phone, that the battery image is not shown when I charge my phone. Instead the screen is completely white.
When I booted the phone again, the screen remained white all the time until I pressed 3 times the power button.
Then my standard launcher (Hola) gets started normally.
However, the screen remains white when I start into bootloader mode or into recovery mode.
Hence, I cannot select anything in a menu (e.g., to perform factory reset or to wipe cache etc...), as I have only a white screen.
May someone has already seen the same behavior and knows where I can search for a solution.
Many thanks in advance for all tips that get posted
Compact problem description:
White screen under the following circumstances:
Charging while phone is off
normal boot until I press 3 times the power button (has to be done after the phone vibrates shortly)
booting into recovery mode (either with the keys or with adb command)
booting into bootloader mode (either with the keys or with adb command)
Information about the phone:
Brand: Lenovo
List item
Model: A660
Android: 4.0.4 Rom: Stock ROM with build number A660_S025_121122
Recovery image: Stock image or CMW
Kernel version: 3.0.13 #1 Rooted: Yes with SuperSU v2.01 Fastboot: not supported
Approaches tried so far:
flashed recovery rom with CMW and with stock ROM. No improvement
Change /system/media/bootanimation.zip and /system/media/images/boot_logo. No improvement
added and removed again "debug.sf.nobootanimation=1" in the file /system/build.prop. Changes at least that at shutdown an animation is shown or not.
resetted the /system/fonts folder with a copy of the stock rom
physically cleaned display contacts according to "Android Tablet White Screen fix" on youtube from My Tablet Guru
performed a complete dd image of /dev/block/mmcblk0 in order to be able to restore all partitons if something goes wrong
so far I spent approximately 2 days googling for related problems. However, may someone can provide a key word that I was missing in my search
I attached the output of logcat. May it helps at least to debug the white screen during the boot process.
Once again many thanks for any comment and suggestion.
Hi, thank you for using XDA Assist. You've tried a number of things and i don't have any further suggestions. It's most likely a hardware failure and I'm afraid you're not going to be able to fix it. You could take it to a cell repair shop and see if they have any ideas.
Related
The unit has been used for about 2 months and remains quite new. It was quite stable before. Yesterday night, about half an hour after plugged in for charging and with WiFi Hotspot turned on for sharing 3G data to another netbook, the unit suddenly rebooted itself. It then stopped at the start-up screen and remained there for several minutes. I kept holding the power button for a few seconds to turn it off but it then automatically reboot itself afterwards, and stopped at the start-up screen again. It means that even complete turning off is not possible.
Trying to enter into recovery mode showed the following few lines:
# MANUAL MODE #
-- Updating application...
Copying Common Apks.
Click to expand...
Click to collapse
and then it automatically rebooted again. It means that it can't enter into recovery mode normally.
It was possible to enter into download mode. And it was the first time this machine went into download mode. I run Odin Downloader and flashed the official stock ROM. After showing "Pass", the device rebooted itself. Unfortunately, it still stopped at the start-up screen, just showing "Samsung Galaxy Tab 7.0 plus". It is really troubesome. I have experience playing several Android devices before and it is the first time I face such troublesome problem.
The device is an official product. The biggest problem is that the original purchase invoice was lost and most likely that I couldn't get official support, repair service or replacement.
May I ask if anyone would kindly provide me some help or advice. Thanks!
Instead of going into download mode go into recovery mode and see if there are any errors. Your scenario is sounding very similar to the one I had in the past.
I just ran into a nasty snag at boot logo as well. nandroid, stock kernel and factory reset were no help. Try Odin back to Stock, it still may not get past boot logo, hold vol up and power to get into recovery and factory reset. Hope it works for you.
Unfortunately I was unable to get into recovery mode even after odin flashing stock ROM.
It rebooted itself a few seconds after displaying some lines of text. I can't see the normal recovery menu.
I had the Photon Q with the SIM mod and CM 9 working for 2 mouth. But yesterday, I were using the cellphone when it reboot itself and get freeze on the unlocked bootloader warning. I try to power it of but y could not, the I let it there until batery drain (about 4 hours)
Now when I boot the cellphone it has an strange behavior. Some times it freeze on the unlocked bootloader warning, other time make a loop boot (show the warning and restart). Also some times it display strange colors on the screen when try to boot and many times it display a randomly sorted grey vertical lines and very few times (one of every 50 times) it boot the ROM but when i touch the screen it goes black.
i can not conect to phone by adb and can not enter recovery, but i can access to the fastboot (in fact the fast boot is working but do not display anything on the screen, i suppouse that the same happend with the recovery. but i can not use it if the screen is black)
I used the fastboot and RSD to flash the stock firmware, the phone return fail on every 4.0.4 ROM but it work with the 4.1.2. After the flash some times thes phone display the morotola and sprint logo and then start the handfree configuration, but when I touch the screen it goes to black again.
I do not know if it is bricked, I think that if i have access to the fastboot i can resurrect the phone. but is very strange the random behavior.
Do you have any idea what should I do?
Thanks.
PS: sorry for my bad english
Re-Strange behaviour
Hi there, one of my Q's (also sim modded) was doing a similar bootloop warning etc. I was screwing around with it a bit. It's all good now though.
The way to force power down/reboot is to hold "volume -" and the power button for 10-15 seconds. If you drain the battery, you will be stuck with more boot-loops due to a flat battery. If you plug the charger in & the LED is green, this means it is charging a dead battery, & will need to charge for a while.
By the way, I had issues on my other Q handset running CM, failing to read the mSD card, and causing freezes, boot loops etc, so I went back to stock. Pretty sure most of the trouble is due to the mSD card read/mount error.
Edit:
Come to think about it - my Q failed after I tried to restore my CM10.1 backup from the previous phone. I suggest this may be contributing to the issue, as you are also running CM.
With the black screen/boot loop, force reboot by holding "vol -" & power button for 15 seconds, release power, then immediately hold "vol +" so it forces boot to recovery (TWRP if you have it).
I restored a previous backup eventually, but TWRP was not working too well after the screwy boot-looping etc. I ran a factory reset from the phone menu once it was running again, then rebooted into TWRP.
Super User wouldn't install from TWRP after, so I pushed it across & installed from TWRP, now I'm about to update TWRP to 2.6.
Still want to have a go at another ROM on this handset, so I can compare it to my stock one. I'm pretty sure CM10.1 was part of the problem on the other Q with my mSD card failing, as it has been fine ever since on stock.
Try this:
Try using adb to fastboot into recovery, then push TWRP (again) onto your Q using this method by arrrghhh http://forum.xda-developers.com/showthread.php?t=1887070
Push Super User across onto your mSD & install that from TWRP as instructed also.
Restore a stock/custom backup from an earlier time if you have one, or flash a fresh download.
Let me know how you go.
P.S. make sure you have "USB Debugging" enabled in developer options in order to ADB fastboot recovery.
schmandroid said:
Hi there, one of my Q's (also sim modded) was doing a similar bootloop warning etc. I was screwing around with it a bit. It's all good now though.
The way to force power down/reboot is to hold "volume -" and the power button for 10-15 seconds. If you drain the battery, you will be stuck with more boot-loops due to a flat battery. If you plug the charger in & the LED is green, this means it is charging a dead battery, & will need to charge for a while.
By the way, I had issues on my other Q handset running CM, failing to read the mSD card, and causing freezes, boot loops etc, so I went back to stock. Pretty sure most of the trouble is due to the mSD card read/mount error.
Edit:
Come to think about it - my Q failed after I tried to restore my CM10.1 backup from the previous phone. I suggest this may be contributing to the issue, as you are also running CM.
With the black screen/boot loop, force reboot by holding "vol -" & power button for 15 seconds, release power, then immediately hold "vol +" so it forces boot to recovery (TWRP if you have it).
I restored a previous backup eventually, but TWRP was not working too well after the screwy boot-looping etc. I ran a factory reset from the phone menu once it was running again, then rebooted into TWRP.
Super User wouldn't install from TWRP after, so I pushed it across & installed from TWRP, now I'm about to update TWRP to 2.6.
Still want to have a go at another ROM on this handset, so I can compare it to my stock one. I'm pretty sure CM10.1 was part of the problem on the other Q with my mSD card failing, as it has been fine ever since on stock.
Try this:
Try using adb to fastboot into recovery, then push TWRP (again) onto your Q using this method by arrrghhh http://forum.xda-developers.com/showthread.php?t=1887070
Push Super User across onto your mSD & install that from TWRP as instructed also.
Restore a stock/custom backup from an earlier time if you have one, or flash a fresh download.
Let me know how you go.
P.S. make sure you have "USB Debugging" enabled in developer options in order to ADB fastboot recovery.
Click to expand...
Click to collapse
I tried it, but do not work.
I flash the stock ROM from fastboot and also flash several recoverys, but never boot any ROM and I think that i access to the recoverys but the screen is black then is very dificult to use it. Is strange beacouse some times screen displays perfect the unlocked bootloader warning, but never display anything on the fastboot or the recovery.
Witch part of the software have the video drivers that are used on the recovery and fastboot? I think that maybe is corrupted. how can i flash it again?
Thanks.
Hey guys,
Few days ago, I woke up and saw my Nexus 5 was out of battery, charged it and when I turned it on it started to update and it was going through with optimising apps ## of ### and when I checked it again, it was stuck on the four circles animation. It got stuck on this screen for quite a while so I powered off, powered on again and now it just stays stuck on the Google logo, what should I do?
I've tried entering Fastboot Mode and selecting Recovery Mode but then nothing happens; screen stays on but stays black. I tried connecting it to my computer so I could backup my files but I can't get it to appear as a Nexus 5 drive and access the folders. Also LOCK STATE - locked [preetty sure I unlocked it back when I first got the phone in 2013 but then I haven't really done anything custom with it]
So I've tried following the steps here: androidforums.com/threads/nexus-5-stuck-in-the-start-up-screen.887612/page-3#post-6817816, but I can't get my device to appear as an adb device, even though i ran the 'fastboot oem unlock' command and it unlocked the Nexus? i.imgur.com/VHHjaVe.png (Android device is showing but 'adb list devices' command doesn't detect anything?)
Ideally I would like to access the Nexus 5 internal storage and just copy paste the folder to my computer to serve as a backup and save files, then flash a new image/factory reset it. I went over to my cousin's place last night to see if he could help as he is more technical than I am but he couldn't flash a new image onto it. I've also unlocked the phone a few times with the 'fastboot oem unlock' command, which changes to LOCK STATE - unlocked, but then if I power off the phone and enter Fastboot Mode again it will show as LOCK STATE - locked.
Also, I'm not sure at this point if the unlocking has wiped whatever data might have been on the phone anyway? [does the internal sdcard get wiped if you run oem unlock? e.g. I had about 6/32GB left on my phone but now it'll just be 31/32 GB because it wiped?]
Thanks, I hope my description of the problem is clear. I have tried googling extensively to see if anyone has experienced similar problems but they're not quite the same (eg. stuck on Google screen bootloop is a power button issue but my phone doesn't constantly reboot and the power button seems fine) [clearing cache or running Recovery mode, but my phone can't run Recovery mode] {Flashing new image but that didn't seem to work either}
Sorry my links don't work, I'm a new user so don't have enough posts here!
Hi,
I bought my OnePlus One (64 GB Sandstone Black) in September 2014. Since I got the phone, everything was running very quickly & smoothly. I did not have any problems with it, so I was very pleased with my brand new phone.
I did not tamper at all with my OnePlus One phone and every time there was a new OTA update, I updated it with the latest version. Currently my OPO has the latest Cyanogen OS 12 OTA updates (CM12S).
Last Friday I used my phone and everything was running very good, as usual. I shut down my phone and went to bed. The next day, on Saturday morning when I turned on the phone, it started showing the OnePlus One logo (with the text "powered by android"). Then CYANOGEN logo appeared on the screen and nothing happened. I waited near my phone for half an hour and nothing happened, it kept showing the CYANOGEN logo. It's like a cycle that never ends. So now I am facing a huge problem with my OPO: every time I press the power button, my OnePlus One gets stuck while booting, showing only the CYANOGEN logo. :crying:
Please see picture "OPO stuck on booting - shows only CYANOGEN logo.JPG".
As I said before, I did not tampered with my OPO, I did not flash it, I did not installed any ROM, I did not installed a custom recovery. Also, I did not drop my phone, so it is in good hardware condition. Every time there were new updates, I updated it with the latest OTA updates. I did not have any issues after the updates, so I don't understand why now it gets stuck on booting (especially since before this problem appeared, everything was working great, as usual).
I read through the forums, the internet and tried to find several solutions, without wiping my data. Any solution that I found did not work and I could not fix this problem (OPO stuck on booting, while showing the CYANOGEN logo). After two days in which I could not use my phone, I removed my SIM from the OPO and now I am using a normal phone (only for calls and SMS).
After my OPO gets stuck while booting, showing only the CYANOGEN logo, I connect it to my laptop using the USB cable (the same one used for charging), but I cannot access my files. Before this huge problem appeared, I could easily connect my OPO to my laptop. Please see pictures: "Connecting my OPO via USB - Installing device driver software - Step 1.JPG" and "Connecting my OPO via USB - Installing device driver software - Step 2 - Failed.JPG". I updated the drivers, but it did not work.
Ever since I got my phone, I have never unlocked the bootloader or rooted or anything of that sort.
I have never even touched any fastboot/adb commands since I got the OPO, until now, when I have this major problem with it.
After reading the forums, I started my OPO in Fastboot Mode and used 2 commands with fastboot.exe (Please see picture named "OPO Fastboot Mode.JPG")
Results below:
******************************
F:\OnePlus One tools>fastboot.exe devices
b01c5f88 fastboot
F:\OnePlus One tools>fastboot oem device-info
...
(bootloader) Device tampered: true
(bootloader) Device unlocked: false
(bootloader) Charger screen enabled: false
(bootloader) Display panel:
OKAY [ 0.006s]
finished. total time: 0.006s
******************************
I do not understand why "Device tampered: true", since I have never unlocked the bootloader or rooted or flashed or anything of that sort ever since I got my OPO. I did not tamper my OPO, so "Device tampered" should have been false.
I also tried to use ADB, but it does not work. Please see below:
******************************
F:\OnePlus One tools>adb devices
List of devices attached <--- THIS LIST IS EMPTY, IT DOES NOT SHOW MY DEVICE, SO ADB DOES NOT WORK AT ALL
******************************
I want to save my media files (pictures, recordings, clips, audio files), my documents and messages.
For other suggestions found on the forums, I did not use at all, because I do not want to erase all data of the phone.
My OPO can boot into recovery mode (Please see picture named "OPO Cyanogen Recovery.JPG"), so I can see the Cyanogen Recovery menu, but I do not want to wipe all my data and do a factory reset. I want to first save my data and afterwards I can erase all data and reset my OPO.
Problem: my OPO gets stuck while booting, showing only the CYANOGEN logo. I wait and wait and nothing happens (today I waited for two hours, the logo is still there and the phone does not start).
I want to:
1) Save to my computer my files (media files, documents) and messages (SMS and chat messages, like viber and so on)
2) Solve this boot logo issue (OPO stuck on booting, while showing only the CYANOGEN logo)
Any help regarding this problem is enormously appreciated.
Thanks in advance,
Bogdan
Well that sucks. You could try to install TWRP through fastboot and use it to mount the phone as a USB storage device, I think that could work.
---------- Post added at 02:56 PM ---------- Previous post was at 02:55 PM ----------
Wait no, since your bootlocker is locked it's pointless.
bogdan_p said:
Hi,
I bought my OnePlus One (64 GB Sandstone Black) in September 2014. Since I got the phone, everything was running very quickly & smoothly. I did not have any problems with it, so I was very pleased with my brand new phone.
I did not tamper at all with my OnePlus One phone and every time there was a new OTA update, I updated it with the latest version. Currently my OPO has the latest Cyanogen OS 12 OTA updates (CM12S).
Last Friday I used my phone and everything was running very good, as usual. I shut down my phone and went to bed. The next day, on Saturday morning when I turned on the phone, it started showing the OnePlus One logo (with the text "powered by android"). Then CYANOGEN logo appeared on the screen and nothing happened. I waited near my phone for half an hour and nothing happened, it kept showing the CYANOGEN logo. It's like a cycle that never ends. So now I am facing a huge problem with my OPO: every time I press the power button, my OnePlus One gets stuck while booting, showing only the CYANOGEN logo. :crying:
Please see picture "OPO stuck on booting - shows only CYANOGEN logo.JPG".
As I said before, I did not tampered with my OPO, I did not flash it, I did not installed any ROM, I did not installed a custom recovery. Also, I did not drop my phone, so it is in good hardware condition. Every time there were new updates, I updated it with the latest OTA updates. I did not have any issues after the updates, so I don't understand why now it gets stuck on booting (especially since before this problem appeared, everything was working great, as usual).
I read through the forums, the internet and tried to find several solutions, without wiping my data. Any solution that I found did not work and I could not fix this problem (OPO stuck on booting, while showing the CYANOGEN logo). After two days in which I could not use my phone, I removed my SIM from the OPO and now I am using a normal phone (only for calls and SMS).
After my OPO gets stuck while booting, showing only the CYANOGEN logo, I connect it to my laptop using the USB cable (the same one used for charging), but I cannot access my files. Before this huge problem appeared, I could easily connect my OPO to my laptop. Please see pictures: "Connecting my OPO via USB - Installing device driver software - Step 1.JPG" and "Connecting my OPO via USB - Installing device driver software - Step 2 - Failed.JPG". I updated the drivers, but it did not work.
Ever since I got my phone, I have never unlocked the bootloader or rooted or anything of that sort.
I have never even touched any fastboot/adb commands since I got the OPO, until now, when I have this major problem with it.
After reading the forums, I started my OPO in Fastboot Mode and used 2 commands with fastboot.exe (Please see picture named "OPO Fastboot Mode.JPG")
Results below:
******************************
F:\OnePlus One tools>fastboot.exe devices
b01c5f88 fastboot
F:\OnePlus One tools>fastboot oem device-info
...
(bootloader) Device tampered: true
(bootloader) Device unlocked: false
(bootloader) Charger screen enabled: false
(bootloader) Display panel:
OKAY [ 0.006s]
finished. total time: 0.006s
******************************
I do not understand why "Device tampered: true", since I have never unlocked the bootloader or rooted or flashed or anything of that sort ever since I got my OPO. I did not tamper my OPO, so "Device tampered" should have been false.
I also tried to use ADB, but it does not work. Please see below:
******************************
F:\OnePlus One tools>adb devices
List of devices attached <--- THIS LIST IS EMPTY, IT DOES NOT SHOW MY DEVICE, SO ADB DOES NOT WORK AT ALL
******************************
I want to save my media files (pictures, recordings, clips, audio files), my documents and messages.
For other suggestions found on the forums, I did not use at all, because I do not want to erase all data of the phone.
My OPO can boot into recovery mode (Please see picture named "OPO Cyanogen Recovery.JPG"), so I can see the Cyanogen Recovery menu, but I do not want to wipe all my data and do a factory reset. I want to first save my data and afterwards I can erase all data and reset my OPO.
Problem: my OPO gets stuck while booting, showing only the CYANOGEN logo. I wait and wait and nothing happens (today I waited for two hours, the logo is still there and the phone does not start).
I want to:
1) Save to my computer my files (media files, documents) and messages (SMS and chat messages, like viber and so on)
2) Solve this boot logo issue (OPO stuck on booting, while showing only the CYANOGEN logo)
Any help regarding this problem is enormously appreciated.
Thanks in advance,
Bogdan
Click to expand...
Click to collapse
So your ota s update is in storage
Go to recovery
Install update
Navigate to 0/android /data/com.cyngn.fota/cache folder
There live your update and reflash the last update
Pm becarefull do not install wrong file and downgrade
Check the name or post it here for help
geowolf1000 said:
So your ota s update is in storage
Go to recovery
Install update
Navigate to 0/android /data/com.cyngn.fota/cache folder
There live your update and reflash the last update
Pm becarefull do not install wrong file and downgrade
Check the name or post it here for help
Click to expand...
Click to collapse
In the Cyanogen Recovery Menu I clicked on Apply Update, the Choose from internal storage
In the 0/android /data/com.cyngn.fota/cache folder I found this file: cm-12.0-YNG1TAS17L-bacon-signed.zip
What should I do next? Doing this will help me fix the booting cycle issue? Or it will help to save my data?
In adition to this, I posted the same problem on a OnePlus forum.
https://forums.oneplus.net/threads/cm12s-is-stuck-on-booting-shows-only-cyanogen-logo.316950/
On this thread, the proposed solution made by a user (biltoad Level: Gingerbread) will somehow help to save my data? Then I can do a factory reset.
Please find below his suggestion. What do you think?
*****
alright i've got a working solution
download color os from here:
https://forums.oneplus.net/threads/rom-official-4-3-coloros-v-2-0-0_beta.79203/
and extract
and then follow the instruction here to set it up (dont flash yet):
http://forum.xda-developers.com/oneplus-one/general/guide-unbrick-oneplus-one-t3013732
the download cyanogen fastboot zip here
https://cyngn.com/support
extract the cyanogen fastboot zip to your extracted color os folder(replace everything)
download twrp from here : https://twrp.me/devices/oneplusone.html
copy twrp to the color folder and replace recovery.img
delete these :
8974_msimage.mbn
userdata.img
userdata_64G.img
after that you should start flashing
the download tool will stop and show red text(ignore that)
after that hold the power button for about 10 secs
hold vol down+power to boot to twrp, and start saving your data
edit : Tested
oh yeah, after you install twrp, flash this to unlock your bl http://forum.xda-developers.com/showpost.php?p=54251992&postcount=1
bogdan_p said:
In the Cyanogen Recovery Menu I clicked on Apply Update, the Choose from internal storage
In the 0/android /data/com.cyngn.fota/cache folder I found this file: cm-12.0-YNG1TAS17L-bacon-signed.zip
What should I do next? Doing this will help me fix the booting cycle issue? Or it will help to save my data?
In adition to this, I posted the same problem on a OnePlus forum.
https://forums.oneplus.net/threads/cm12s-is-stuck-on-booting-shows-only-cyanogen-logo.316950/
On this thread, the proposed solution made by a user (biltoad Level: Gingerbread) will somehow help to save my data? Then I can do a factory reset.
Please find below his suggestion. What do you think?
*****
alright i've got a working solution
download color os from here:
https://forums.oneplus.net/threads/rom-official-4-3-coloros-v-2-0-0_beta.79203/
and extract
and then follow the instruction here to set it up (dont flash yet):
http://forum.xda-developers.com/oneplus-one/general/guide-unbrick-oneplus-one-t3013732
the download cyanogen fastboot zip here
https://cyngn.com/support
extract the cyanogen fastboot zip to your extracted color os folder(replace everything)
download twrp from here : https://twrp.me/devices/oneplusone.html
copy twrp to the color folder and replace recovery.img
delete these :
8974_msimage.mbn
userdata.img
userdata_64G.img
after that you should start flashing
the download tool will stop and show red text(ignore that)
after that hold the power button for about 10 secs
hold vol down+power to boot to twrp, and start saving your data
edit : Tested
oh yeah, after you install twrp, flash this to unlock your bl http://forum.xda-developers.com/showpost.php?p=54251992&postcount=1
Click to expand...
Click to collapse
Will help you with bootloop if is rom issue
Flash ota first is cyanogen 5.0.2
Your data is safe
The other suggestion from oneplus is little risky
You should after take backup to connect with pc and tranfer your backup to pc if you factory reset or unlock bootloader
You will need proper drivers for that
Check how enable twrp mtp storage for pc
Follow the steps one by one before try it .
Good luck
Hi There,
Firstly I do apologize if this has already been posted, but I have searched through the forums and have not been able to find any specific information about this particular problem.
I have a Galaxy S3 (purchased in 2012) and a few weeks ago, the phone started to automatically switch off (when I locked it) and I would have to hold the power button for about 15-30 seconds for it to switch back on.
I checked the power button(to see if it was broken and pressing down all the time) but it seemed to be fine as whenever I pulled the battery (and put it back in after 1 minute) the phone would NOT come on unless I held the power button.
Also tried replacing the battery, but that did not seem to work.
About 1 week ago when i tried to turn my phone on, with the power button, but it would get stuck on the samsung logo screen (it was frozen, not looping).
I was still able to enter both recovery and download mode. So I tried wiping the cache but it did nothing.
Then I tired flashing the ROM with ODIN and it passed but it also did nothing (tried flashing multiple times all with "PASS" as well as wiping the data cache in conjuction with the flashing but to no avail).
Tried flashing it again with BL and it also passed, but now whenever I try to enter Recovery Mode or Turn the phone ON it would display a White Scrambled Screen which probably means eMMC failure.
Now for the problem:
How do I retrieve the information on the phone ?
N.B;
- I do not care about fixing the phone, only want the information
-I cannot enter Recovery Mode, BUT I can enter download mode.
-When I connect S3 to PC it is detected (In Device Manager it states "Samsung Mobile USB CDC Composite Device")
-I did have my phone password protected before this happened using the Pattern Password (you have a 3x3 Dot grid in which you can use to draw a line(s) which will function as a password)
-My phone is an S3 GT-I9300
-Never interfered with the ROM or software on the phone before this (was running the official android software from Samsung which I believe was Android Version 4.3).
-Have Tried EaseUs, but it does not detect the phone.
bossman111 said:
Hi There,
Firstly I do apologize if this has already been posted, but I have searched through the forums and have not been able to find any specific information about this particular problem.
I have a Galaxy S3 (purchased in 2012) and a few weeks ago, the phone started to automatically switch off (when I locked it) and I would have to hold the power button for about 15-30 seconds for it to switch back on.
I checked the power button(to see if it was broken and pressing down all the time) but it seemed to be fine as whenever I pulled the battery (and put it back in after 1 minute) the phone would NOT come on unless I held the power button.
Also tried replacing the battery, but that did not seem to work.
About 1 week ago when i tried to turn my phone on, with the power button, but it would get stuck on the samsung logo screen (it was frozen, not looping).
I was still able to enter both recovery and download mode. So I tried wiping the cache but it did nothing.
Then I tired flashing the ROM with ODIN and it passed but it also did nothing (tried flashing multiple times all with "PASS" as well as wiping the data cache in conjuction with the flashing but to no avail).
Tried flashing it again with BL and it also passed, but now whenever I try to enter Recovery Mode or Turn the phone ON it would display a White Scrambled Screen which probably means eMMC failure.
Now for the problem:
How do I retrieve the information on the phone ?
N.B;
- I do not care about fixing the phone, only want the information
-I cannot enter Recovery Mode, BUT I can enter download mode.
-When I connect S3 to PC it is detected (In Device Manager it states "Samsung Mobile USB CDC Composite Device")
-I did have my phone password protected before this happened using the Pattern Password (you have a 3x3 Dot grid in which you can use to draw a line(s) which will function as a password)
-My phone is an S3 GT-I9300
-Never interfered with the ROM or software on the phone before this (was running the official android software from Samsung which I believe was Android Version 4.3).
-Have Tried EaseUs, but it does not detect the phone.
Click to expand...
Click to collapse
Hello, the best solution will be to ask here Galaxy S III Q&A, Help & Troubleshooting since that guys know more about mentioned device.
Thank you
Paget96 said:
Hello, the best solution will be to ask here Galaxy S III Q&A, Help & Troubleshooting since that guys know more about mentioned device.
Thank you
Click to expand...
Click to collapse
Hi There Krusevac,
Thanks for the reply.
I will check it out.
Kind Regards,
B
bossman111 said:
Hi There Krusevac,
Thanks for the reply.
I will check it out.
Kind Regards,
B
Click to expand...
Click to collapse
No problem
Sent from my Nexus 5 using Tapatalk