Related
My wife's SG3 SGH-I747 will show the white "Samsung" logo, then the white Samsung Galaxy S3 logo, then it goes black. Pulled the battery several times, no luck. I'm assuming this was caused by a failed update.
I can get it into download mode, I have cleared the Cache and rebooted with no luck.
I'm not a complete rookie at this, but I haven't done it for years and I'm afraid of losing the data on the phone.
How would you suggest I proceed to save the data? (Pictures and movies)
install a previous stock rom via the download mode? Or odin? I don't have a custom recovery installed.
Will the unbrick method work in my situation? If so will it wipe the phone?
I've searched the forum and can't find anyone saying if the data is salvageable.
I know it's my fault for not backing up her data, but she's in tears over losing pictures of the kids. Please help if you can.
Thanks,
Installing a ROM via Odin may require you to do a factory reset before it boots.
Boot into download mode and look at the screen. Do you see anything about a warranty bit?
I just get the download screen. (See attached picture) Nothing about a warranty
Options are:
Reboot system now
apply update from external storage
wipe data/factory reset
wipe cache partition
apply update from cache
Then it shows:
#MANUAL MODE#
--APPLLYING MULTI-CSC...
APPLIED THE CSC-CODE : ATT
SUCCESSFULLY APPLIED MULTI-csc.
.
That is the recovery mode, not download mode. To get into download, press the home button, volume down, and power button. Once the phone starts to boot, release the power button and hold the other two until you see the download message and press volume up to continue.
You were right. In download mode it says:
ODIN MODE
product name: sgh-i747
CURRENT BINARY: CUSTOM
SYSTEM STATUS: CUSTOM
QUALCOMM SECUREBOOT: ENABLE
WARRANTY BIT: 1
BOOTLOADER AP SWREV: 3
DOWNLOADING....
DO NOT TURN OFF TARGET!!
Since the warranty bit is 1, this tells me you have at least a 4.3 bootloader on your phone.
The only thing I can think of to get the files would be to flash twrp onto your phone in download mode. Then mount the drive, connect the phone to your computer, and use Windows Explorer (assuming you're on a Win machine) to copy the files off the phone.
audit13 said:
Since the warranty bit is 1, this tells me you have at least a 4.3 bootloader on your phone.
The only thing I can think of to get the files would be to flash twrp onto your phone in download mode. Then mount the drive, connect the phone to your computer, and use Windows Explorer (assuming you're on a Win machine) to copy the files off the phone.
Click to expand...
Click to collapse
Flashing a new rom would wipe the phone?
The last full firmware AT&T released was 4.1.1. The AT&T 4.3 and 4.4.2 ROMs were only released as OTA updates for an existing stock ROM and stock recovery on a phone.
If you want to flash a 4.3 or 4.4.2 ROM, you need to use a version found on XDA to to this. Trying to flash a 4.3 ROM onto a 4.4.2 bootloader and modem could brick your phone. In fact, any flashing procedure can result in a brick or a loss of user data.
Even if you successfully flash a ROM, the ROM may not boot without wiping the cache and all user data first.
Good to know, Thanks a BUNCH for the help.
You are awesome!
Now...let's pray this works!
If you install a custom recovery, you can create a backup of the existing ROM even if the ROM doesn't boot.
Cool,
Odin 3.07 sees the phone, i downloaded openrecovery-twrp-2.6.3.0-d2att.tar. Is it is loaded through the pda option?
Thanks again for your help.
Yes, flash it via the PDA section. Do not check anything except F.Reset time.
Flash TWRP, when you see the word Reset in the status windows, remove the USB cable, remove the battery, replace the battery, boot into recovery, create a backup of the rom, preferably to an external SD card. When the backup is complete, attach phone to computer, mount the partitions, locate files on the phone you want to save.
Done with install, backing up to SD now.
Ok, TWRP worked, I was able to safe the files (THANK YOU!!!). I used the file manager to find and copy the files to the sd card, then did a full backup. It never did mount to the computer, even after the drivers were installed.
It saved the backup with the file name: 1970-01-01--00-18-57 KOT49H.I747UCUFNJ1 so I'm guessing that is the build number it was trying to update to (KOT49H.I747UCUFNJ1). I can get to recovery mode and download mode, how should I go about making this phone work again?
I'm not sure how to check what version of bootloader I have. You scared me about the "bricking it" warning about flashing the wrong rom with the wrong bootloader.
If your are sure you saved the necessary files in two different places, boot into recovery and wipe cache , dalvik, and reboot. If it still won't boot, wipe cache, dalvik, and data in recovery, reboot.
Another option may be to use adb to pull files from the phone, you can even pull entire directories. I will work from recovery mode. There are tutorials on installing the toolkit for adb w/o installing all of the platform development tools. I use Linux so I can not verify how to do this on Windows, but it looks as simple as it was for me. Once adb is present on the PC, boot the phone into recovery, and in a command prompt window enter the command
Code:
adb shell pull /path/to/picture/directory C:\path\to where\you\want\it
and example may be
Code:
adb shell pull /sdcard/DCIM/camera C:\recoveredphotos
Check that I did my Windows path correctly
Good Day,
Thanks for taking the time to read my posting.
I am running a Galaxy Note 2 with TWRP v2.8.7.0. Previously, had been running CyanogenMod 12 Latest Release from 2015-11-17.
Had an issue with the phone rebooting, went into TWRP to clear Cache/Davlik Cache, seen an error after this with /Data partition not being mounted(phone was encrypted). Proceeded to go into TWRP and Format Data then reinstall the ZIP listed above from an external SD card, successfully completed installation of ZIP file for CyanogenMod 12. When I reboot the device from TWRP, through Reboot->System, keeps rebooting back into TWRP and not into CyanogenMod.
I have connected the device to a Windows computer, confirmed that I can see it connected through USB. When I issue abd devices, I see the ##### recovery listed for the device, but if I issue fastboot devices, no device is listed.
Any recommendations for what could be done to reinstall the CyanogenMod build on my device so that it can boot properly would be greatly appreciated.
Thanks to everyone on the community for the support, education and feedback over the years and for all the hard work that you do, cheers to you.
Maybe flash back to a completely stock rom, confirm that everything works, flash twrp, and cm again?
I was thinking about recovery to stock recovery when I read your post .
Tried the stock recovery using Odin3-v3.07 pointing to CF-Auto-Root-t0ltetmo-t0ltetmo-sght889.tar.md5(1/20/2015), this appeared to complete from Odin, but the phone still went into a reboot loop into CyanogenMod, but never fully started up, thereafter.
Went to the autoroot.chainfire.eu site, downloaded the latest stock recovery for device.
Pulled the battery, back into TWRP, select Wipe/Factory reset from TWRP. Installed Samsung Kies onto desktop, ran Odin3-v3.10.6 pointing AP to CF-Auto-Root-t0ltetmo-t0ltetmo-sght889.tar.md5 dated from 3/31/2016. Then went to phone and go to download mode (turn off first, press and hold following buttons: vol down + home + power). Then Press Up Volume key to get into Download mode, then connect it to PC via USB. Device shown in Odin under ID:COM. On Option uncheck “Repartition”. After reboot, phone boot into IMG for CyanogenMod. Confirmed access to phone thereafter.
Thanks for the feedback, hope this helps someone down the line, if they run into the same issue.
NO ONE?????
ODIN --> Flash Stock Recovery (AP) with NAND Erase All Option Checked (because it seemed to make sense) + Auto Reboot + F. Time Reset --> Reboots to Stock Recovery (did not work before) --> Reboot into Recovery --> Wipe Data/Cache and Dalvik just to be safe (this crashed it before) --> Reboot. THE END
TL/DR: I am currently stuck on recovery/update mode. Any attempt to wipe data or clear dalvik crashes it. any attempt to access data through TWRP crashes it. Flashing stock rom or custom rom does not help. Somethings wrong with /data? It thinks it has root from the CF Auto Root, but does not really? Something wrong with partitions? Should I wipe the nand with ODIN 3.10? Repartition? ugh ... Please help ...
I have searched the forums and found nothing that describes this issue precisely. I have also tried to apply various suggestions to repair, which, for the most part seems to have made it worse. I am hoping that people still look at this forum.
PC - Windows 7
Initially @4.2.2 ---> Touchwiz debloated stock ROM which I rooted. It worked for a couple years, but the device crashed frequently. I do not recall much about the installation, but believe that I used CWM/TWRP at the time. After installing the ROM, I ran triangle away (out of the box, it had 4.1.2, i recall)
I decided to upgrade to the most recent stock ROM (4.4.2). In order to do so, I used an easy installer I found else where on XDA. (http://forum.xda-developers.com/showthread.php?t=2773712 ---ODIN One Click exe). The device was not initially recognized, so I reinstalled the official driver package (said that they already existed, but I installed again anyway). Ran 1-click and it appeared to work.
Initially, the device booted (long startup) and seemed to function. It also preserved all data and programs (presumably did not touch the internal memory - 16 GB) and possibly root /data.
I then tried to root through most recent ODIN with CF auto root. This appeared to work and rebooted (again, showing the updating android apps screen before fully booting).
The only thing that i could find that had changed was the wallpaper (showed on lock screen but not on home screen). I could no longer find the image, so tried to go to /data/data to find it with root explorer equivalent. This is where it started to act weird.
NOTE: I did not clear anything (system cache, etc. at any point)<--a lie (see below)
It showed the root folder fine, but when I clicked on /data it took a while and could not access it. It either rebooted itself or I rebooted, but this time it was stuck in a boot logo loop. I entered download mode and flashed TWRP through ODIN. I set it to not reboot automatically so that the bootloader was not overwritten automatically (thus losing recovery). TWRP came up. The computer recognized it as a Media Device after I mounted USB storage. Just in case, I copied all of the important files from the internal SD Card to my computer. I then tried to go to the file explorer to copy the wall paper and it forced a reboot. At this point it was stuck on a logo screen boot loop again. I was able to enter Download mode and reflash TWRP. This allowed me to enter recovery again, however, now it would only boot directly into recovery (or Download mode if I did the button combo). The interesting thing was that it would reboot two or three times before successfully entering TWRP.
I believe I tried to reflash the stock ROM at this point, which might have worked but made no difference.
I was also having a lot of problems getting Windows to properly recognize the device. I had to reinstall the drivers a couple times. I tried Kies after the problems started and it tried to connect by failed. The diagnose connection did not work either. I was not able to get Kies to connect though I tried several times throughout the attempted repair
I downloaded a stock-rooted 4.4.2 ROM from here and tried to flash it. It failed.
I also tried to flash via Heimdall, but initially could not find any stock ROMs for Heimdall for the Galaxy 8. (The driver utility that is included helped to get the phone recognized by Windows sporadically).
I decided to switch over to CWM touch recovery, which I flashed via ODIN (I was having issues with TWRP again and also could not get windows to recognize the device as a media device when I mounted USB storage). This worked after a couple tries and I was able to enter CWM. I attempted to flash the stock ROM but it failed. Either at that point or when I tried to mount data it returned an error that device did not have root. Again, it would only boot into CWM (on its own) or Download mode (with key combo). At some point around here I cleared the cache and dalvik (error) after it returned an error saying insufficient space when trying to flash ROM.
I dissected the .exe from the autoflash used in the beginning (stock unrooted 4.4.2) and used the contents (system.img, cache.img, hidden.img, tz.img, recovery.img and one other I do not remember) in Heimdall to create a Heimdall package. At this point I figured out I did not need to create the package, but just specify the individual files. I flashed. It appeared to complete System.img successfully and then failed. Tried again with the same result.
Now when I rebooted, it would enter download mode with the Key combo, but otherwise it booted instantly to an error screen to the effect that a firmware installation had failed and to use the repair function in Kies to fix. Kies still did not recognize it.
At this point, I figured I should stop. Currently I can get to the download screen or the error screen. The computer recognizes it but intermittently fails to install driver. Zadig.exe sees it as Gadget Serial. Sometimes Windows just sees it as SAMSUNG_Android, in which case drivers fail. Once or twice I got it to recognize it as Samsung USB Composite Device, but Kies would still not work.
That's all i have for now. If more information is needed, let me know and I will update the post when I get home from work tonight (this is from memory).
Thank you
UPDATE: last night I went home and was able to get it back to the point where I could flash TWRP or CWM recovery. If I try to flash Stock Recovery, it fails. A minor problem is that I cannot turn it off - it just turns it self on again, so the battery keeps running down.
Hi there,
I think I (soft? hard?) bricked my whyred today after trying to install Pixel Experience (Android 10). At this time, I'm left with a flashed PE Plus that is stuck at the Google logo animation (e.g. unable to access USB debug settings); stock MIUI recovery; and fastboot, which is not recognized by ADB as I haven't had a successful boot since I flashed PE, so I can't turn USB debug on. I think I've exhausted my options, but maybe someone has a smart solution.
For those who think they can help, let me describe in detail what I did:
0) I became a dev, turned USB debug on, installed Minimal ADB and Fastboot, latest Xiaomi drivers, moved flashable zips into internal storage etc.
1) I unlocked my bootloader through Mi Unlock.
2) I successfully flashed TWRP-3.3.1.0-whyred via ADB/Fastboot and rebooted. After getting back into MIUI, I booted into recovery, which was back to stock (MIUI seems to have overwritten my recovery). At that point (probably a big mistake) I gave up on flashing TWRP and went ahead to boot right into it via ADB instead, without flashing.
3) After a successful boot into TWRP 3.3.1.0, it asked me for a decryption password. Nothing worked, so I kept googling and found out that my version of android needs TWRP 3.3.1.1, which was not on the official TWRP website yet, to decrypt automatically. I booted into TWRP 3.3.1.1 via ADB (but didn't flash), made a backup of my stock ROM, did a wipe (art/dalvik cache, cache, data, system, vendor), flashed Pixel Experience and rebooted.
4) Bootloop, I was stuck on the Google loading animation for over 20 minutes, nothing happened.
5) I panicked.
6) I tried to flash TWRP 3.3.1.1 via ABD but my PC didn't recognize my phone - probably because, for lack of successful boots, I have not managed to turn on USB debug.
7) I tried to connect to Mi Assistant through stock recovery. It didn't recognize my phone, probably for the above reason.
8) I did a data wipe through stock recovery and rebooted, hoping for whatever issue kept PE from booting normally to get resolved.
9) I'm stuck on the same Google loading animation for over 40 minutes now, no progress.
Does any of you guys see a way out, or is this story over? To recap, I have: 1) PE Plus in bootloop, no access to dev settings, 2) stock MIUI recovery with options to reboot, wipe data or connect to Mi Assistant, 3) stock fastboot, 4) a backup of my previous system on internal storage, 5) ADB on my computer that doesn't recognize my phone - no USB debugging. I don't know where to turn. I don't care much about data, I have everything in the cloud, but I'd like to save the phone if possible.
Thanks a lot.
Edit: Problem resolved - even though the connected device didn't show up in ADB on PC (adb devices came back empty), the phone was still responsive to fastboot reboot and fastboot flash recovery via PC, so I could flash TWRP 3.3.1.1 & clean flash PE. For anyone struggling with PE bootloops: make sure to 1) use TWRP 3.3.1.1 to flash, 2) do a dalvik/cache wipe after flashing the ROM and 3) not to install the TWRP app before the first successful boot - it was neglecting either 2) or 3) that caused my bootloop. The ROM itself is amazing!
mkohan said:
Hi there,
I think I (soft? hard?) bricked my whyred today after trying to install Pixel Experience (Android 10). At this time, I'm left with a flashed PE Plus that is stuck at the Google logo animation (e.g. unable to access USB debug settings); stock MIUI recovery; and fastboot, which is not recognized by ADB as I haven't had a successful boot since I flashed PE, so I can't turn USB debug on. I think I've exhausted my options, but maybe someone has a smart solution.
For those who think they can help, let me describe in detail what I did:
0) I became a dev, turned USB debug on, installed Minimal ADB and Fastboot, latest Xiaomi drivers, moved flashable zips into internal storage etc.
1) I unlocked my bootloader through Mi Unlock.
2) I successfully flashed TWRP-3.3.1.0-whyred via ADB/Fastboot and rebooted. After getting back into MIUI, I booted into recovery, which was back to stock (MIUI seems to have overwritten my recovery). At that point (probably a big mistake) I gave up on flashing TWRP and went ahead to boot right into it via ADB instead, without flashing.
3) After a successful boot into TWRP 3.3.1.0, it asked me for a decryption password. Nothing worked, so I kept googling and found out that my version of android needs TWRP 3.3.1.1, which was not on the official TWRP website yet, to decrypt automatically. I booted into TWRP 3.3.1.1 via ADB (but didn't flash), made a backup of my stock ROM, did a wipe (art/dalvik cache, cache, data, system, vendor), flashed Pixel Experience and rebooted.
4) Bootloop, I was stuck on the Google loading animation for over 20 minutes, nothing happened.
5) I panicked.
6) I tried to flash TWRP 3.3.1.1 via ABD but my PC didn't recognize my phone - probably because, for lack of successful boots, I have not managed to turn on USB debug.
7) I tried to connect to Mi Assistant through stock recovery. It didn't recognize my phone, probably for the above reason.
8) I did a data wipe through stock recovery and rebooted, hoping for whatever issue kept PE from booting normally to get resolved.
9) I'm stuck on the same Google loading animation for over 40 minutes now, no progress.
Does any of you guys see a way out, or is this story over? To recap, I have: 1) PE Plus in bootloop, no access to dev settings, 2) stock MIUI recovery with options to reboot, wipe data or connect to Mi Assistant, 3) stock fastboot, 4) a backup of my previous system on internal storage, 5) ADB on my computer that doesn't recognize my phone - no USB debugging. I don't know where to turn. I don't care much about data, I have everything in the cloud, but I'd like to save the phone if possible.
Thanks a lot.
Click to expand...
Click to collapse
I'm new to this phone as well (but not to Android). Try the following:
Download TWRP from here -> https://androidfilehost.com/?fid=6006931924117884758
Download Disable_Dm-Verity_ForceEncrypt_03.04.2020.zip from here -> https://zackptg5.com/downloads/Disable_Dm-Verity_ForceEncrypt_03.04.2020.zip
Power off phone. Hold down volume down and power button to boot into fastboot
Give the command fastboot flash recovery twrp-3.3.1-1-whyred.img to flash the recovery you downloaded earlier.
Boot into recovery
Flash Disable_Dm-Verity_ForceEncrypt_03.04.2020.zip that you downloaded earlier
The above steps will at least ensure that you retain TWRP and it doesn't get overwritten by stock MIUI recovery
After that, check whether or not your phone/ROM has anti-rollback enabled and take appropriate steps accordingly.
Ok so i flashed PE 10 plus today and was met with the same problem.
Heres how i solved it
Goto fastboot option by pressing volume down and power button
Connect to pc (If it doesnt recognize, reinstall Adb drivers and phone drivers)
If it asks for decryption password just press cancel
Wipe data/internal/vendor (wont be able to wipe dalvik as it wont mount)
Flash PE 10 Plus and nothing else.
It should boot just fine.
However i run into bootloop if i flash latest magisk so i cant root my phone :/
Hope this helps
mkohan said:
Edit: Problem resolved - even though the connected device didn't show up in ADB on PC (adb devices came back empty), the phone was still responsive to fastboot reboot and fastboot flash recovery via PC, so I could flash TWRP 3.3.1.1 & clean flash PE. For anyone struggling with PE bootloops: make sure to 1) use TWRP 3.3.1.1 to flash, 2) do a dalvik/cache wipe after flashing the ROM and 3) not to install the TWRP app before the first successful boot - it was neglecting either 2) or 3) that caused my bootloop. The ROM itself is amazing!
Click to expand...
Click to collapse
hey read your post
actually adb and fastboot are two different things.
and recovery is flashed using fastboot commands not adb.
sometimes if a rom is not booting it may have issues with encryption.
Hello
I cannot install new android system to my phone Samsung Galaxy S3 gt I305. Can someone advise what to do?
What I have done is following.
1. Installed TWRP version 3.7.0_9-0, After entering the TWRP I follow the procedure of istallation.
2. Wipe and Swipe to Factory Reset.
3. Advance Wipe: Dalvik/Cache/System/Vendor and swiped to wipe.
4. Went to Install: Selected storage: Internal Storage.
5. Choosing the file e-0.19-n-20211023142427-dev-i9305 and Swipe to confirm Flash.
Now the phone seems to installaing the zip-file e-0.19-n-20211023142427-dev-i9305.
6, Reboot System.
7. After the system reboots it looks like the android is installing on the Samsung phone. However a letter e with a jumping dot below it is displayed and this goes for hours without any success of installation. I have waited 8 hours and nothing happens.
Is there something that I have missed to do?
Attached picture of the last step that I have reached in the installation process.
Please help.
Best regards
User: samsung1979
Hi!
Standard troubleshooting answers are:
1. You did not unlocked your phone's bootloader, enabled USB debuggind, USB debugging(security) and enabled OEM(bootloader) unlock in the phone's settings.
2. You did not flash vbmeta from your current ROM, to disable verity.
3. You did not flash a good bootloader before flashing.
4. Your SD card is corrupted.
5. You did not fix the File System from the recovery
6. You didn't allow modifications and left the recovery in read only mode.
7. The ROM is unsuitable for your phone. Sometimes this happens even if you were told it is for your ROM and it was written on some forum.
Hi
Following question, is it possible to troubleshoot these steps if there is not any android anymore installed and no backup file created?
Meaning that the phone only has access to the TWRP settings and all other phone data is deleted.
If all other data is deleted, please re-install an original ROM, This can normally be done from the manufacturers software, like a PC suite.
Before reinstalling the original ROM, please try flashing the bootloader with ADB and fastboot.
Downloaded it reinstalled and installed android 13 and it is working!
Thank You!