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
ive had help in rom section but unable to get the rom installed trying to install the ultimate note 5 rom ok i follow op instructions tried muti twrp and the lastest philz ever time i flash the rom i get a error 7 code tried muti formatted sd cards tried putting on phone storage then flashing still same error.. ive read on the error 7 a little bit about it look in the updater script dont see the line it says to erase,ive flash other rom no problem but this 1 keeps failing with that error the picture says twrp 2.8.6 did it just to try out but im on twrp 3.0 now when i got the phone it was already on 5.1.1 ok1
I will be as specific and give as much detail as i can here...
You need to start over with a clean slate. Use standard class 10 micro-sd card and don't mess with multi format whatever. Use TWRP 2.8.7 or 3.0.0. Start by rebooting into recovery and wiping everything clean several times. backup any files that you need to keep. But you must wipe internal sd, system, cache, data and dalvic-cache. wipe thenm in advanced wipe options of twrp. Next reboot to download mode. Launch odin 3.10.6 or newer on your pc. connect your phone to your pc via the usb cable. In the options tab of odin make sure auto-reboot and reset time is CHECKED!!! Open the official stock OK1 rom tar using the AP button in odin. Once the md5 check completes just press start to flash the stock rom. when it finishe LET THE PHONE REBOOT!!! Once the phone boots, setup as usual then go into Settings and open "Activate this device". Let it do it's thing and it will automatically reboot. Once the phone reboots, go to settings/System update and do the prl AND profile updates. Reboot your phone again. Then make sure your data and calls work as they should.
Once you are on stock and have done all of these steps above you are ready to odin TWRP. Download the tar version of TWRP to use in odin. It is the best way to flash recoveries. Launch odin on your pc and use the AP button to add the TWRP tar. In the options tab you can uncheck auto reboot if you want. (I've never had to do that but you can). Once it flashes you can let the phone reboot or you can just pull the battery then force reboot into recovery by holding the volume-up, home and power buttons until you feel the phone vibrate. Release all buttons and wait for TWRP to boot. Once in TWRP, do all of the wipes same as before multiple times. Then for good measure go to TWRP homescreen and press "Reboot" then "Recovery" and this will reboot recovery and ensure that the rom zip will flash with no trouble. Reboot recovery then flash the UN5 rom and remember to wait for data to conect before proceeding with setup wizard. Success. If this doesn't work then give up and leave your phone stock until you figure out what's causing your problems. Good luck.
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.
I made a very noob mistake today. I was going to factory reset my Oneplus 3 in TWRP (recovery) and flash back to the stock rom but I accidentally checked off everything to be erased... which erased my current operating system, along with the stock rom I was going to install :crying:
Now im stuck with no OS, phone won't boot, can only get into recovery etc etc
I tried connecting it to the computer and clicking MOUNT in recovery, my PC detects it, but when I try to drag and drop the stock rom it just hangs there and the file transfer progress bar doesnt move.
What are my options ?
The phone is rooted
You can use sideload from twrp. Or you can put the zip you want to flash in a usb and flash it via otg.
613BulletProof said:
I made a very noob mistake today. I was going to factory reset my Oneplus 3 in TWRP (recovery) and flash back to the stock rom but I accidentally checked off everything to be erased... which erased my current operating system, along with the stock rom I was going to install :crying:
Now im stuck with no OS, phone won't boot, can only get into recovery etc etc
I tried connecting it to the computer and clicking MOUNT in recovery, my PC detects it, but when I try to drag and drop the stock rom it just hangs there and the file transfer progress bar doesnt move.
What are my options ?
The phone is rooted
Click to expand...
Click to collapse
Put the OOS you want to install on a flash memory and use it as OTG from TWRP
As mentioned above, sideload is the easiest way.
Simply follow the steps here:
https://twrp.me/faq/ADBSideload.html
You can transfer data from a pc in twrp so you have loads of options
Push it with ADB
Ex- "adb push (input_file_name) /sdcard/(output_file_name)"
I will try adb sideloading, i had tried that method a while back for installing a rom and had issues, i have windows 10.
Skinpipe said:
You can transfer data from a pc in twrp so you have loads of options
Click to expand...
Click to collapse
already tried that it wont let me. it detects the phone on my pc, but when dragging and dropping it wont transfer and throws an error saying device could not be found.
613BulletProof said:
already tried that it wont let me. it detects the phone on my pc, but when dragging and dropping it wont transfer and throws an error saying device could not be found.
Click to expand...
Click to collapse
Try reflashing twrp from fastboot
I had the same problem when I was trying to upgrade to OOS 4.0. The phone was stuck at bootscreen. I powered it off by holding power button for 10 seconds. I turned it on again and booted in recovery mode. Then I connected my OP3 to PC and I was able to copy the .zip file into the TWRP folder. In recovery mode I installed the latest firmware from the .zip file.
Maybe I should mention that the OS I'm using is Arch Linux. My PC instantly recognized my phone.
Hi,
I was trying to repartition my Note 2 with Phill's recovery to gain more space. Achieved successfully but as I tried to flash twrp back via Odin, I probably flashed TWRP to BL section and now there is no recovery or Download Mode opening. Tried to access the device via ADB commands but no device is found.
I am stuck on Samsung Logo. Is there a way to recover from this situation?
note: I have a TWRP backup taken onto the External SD card. A Smart Switch backup on the PC. Did I mess up? Is the phone unrecoveralbly bricked?
Byteman3D said:
Hi,
I was trying to repartition my Note 2 with Phill's recovery to gain more space. Achieved successfully but as I tried to flash twrp back via Odin, I probably flashed TWRP to BL section and now there is no recovery or Download Mode opening. Tried to access the device via ADB commands but no device is found.
I am stuck on Samsung Logo. Is there a way to recover from this situation?
note: I have a TWRP backup taken onto the External SD card. A Smart Switch backup on the PC. Did I mess up? Is the phone unrecoveralbly bricked?
Click to expand...
Click to collapse
Maybe better to flash stock firmware with stock pit to re-partition to the original sizes. But you need to boot into download mode.
Else it is hard-bricked