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
Hello. I have a i317 Note 2, running on T-mobile. It is rooted and was running Blisspop 5.x rom. I had set my phone down and noticed it was on the Samsung screen. Figured it was just a random reboot; but it never booted up. I reboot into recovery (TWRP) to find that there is no OS installed. It says my internal storage is 0mb, my external storage is 0mb (I have a 32gb sd card). I cannot mount nor access external storage, or anything internal. I cannot format data. I am able to see my phone while it is in recovery on my computer. But once I put it in download mode, it can no longer be seen. ADB cannot see it in download mode, I cannot fastboot (unless I'm doing it wrong). I used Odin, which can see it in download mode, but it did not fix anything. Also, now the phone says it is unable to format to remove encryption.
Prior to this it had a problem where it would be unable to stat things. Is there any way to fix this? Or am I SOL?
SchusterIX said:
Hello. I have a i317 Note 2, running on T-mobile. It is rooted and was running Blisspop 5.x rom. I had set my phone down and noticed it was on the Samsung screen. Figured it was just a random reboot; but it never booted up. I reboot into recovery (TWRP) to find that there is no OS installed. It says my internal storage is 0mb, my external storage is 0mb (I have a 32gb sd card). I cannot mount nor access external storage, or anything internal. I cannot format data. I am able to see my phone while it is in recovery on my computer. But once I put it in download mode, it can no longer be seen. ADB cannot see it in download mode, I cannot fastboot (unless I'm doing it wrong). I used Odin, which can see it in download mode, but it did not fix anything. Also, now the phone says it is unable to format to remove encryption.
Prior to this it had a problem where it would be unable to stat things. Is there any way to fix this? Or am I SOL?
Click to expand...
Click to collapse
You used Odin for what? Did you try flashing stock rom? Try using the rescue option in KIES. It has saved me in the past when I had messed up my device.
NickVXD said:
You used Odin for what? Did you try flashing stock rom? Try using the rescue option in KIES. It has saved me in the past when I had messed up my device.
Click to expand...
Click to collapse
Sorry about that, forgot that bit! I used odin to flash the stock rom, and even tried a .pit repartition. Kies does not see the phone. At most, it sees it but will not connect. So there are no rescue options to be had.
I thought I made progress. I was able to do the firmware reset with Keis. The phone got to the blisspop launch screen but just stayed there. I rebooted into TWRP and it still said I had 0mb of internal storage, and still had no OS installed. ADB still didn't see the phone, either. Now the phone will no longer boot to samsung, or to recovery, or TWRP. If I hold the power button the proximity sensor shines for a moment but that's it.
Same problem here, same phone but t0lte that ran many ROMs over 4 trouble-free years . Still at the pre-Kies stage, thus still can access twrp. Tried overwriting twrp with philz or CWM - Odin says PASSED but reality say no dice - twrp is still the recovery. Tried flashing stock - Odin again said PASSED, but still have twrp reporting 0MB.
Spent 1day surfing xda to ensure I have correct files and procedures.
Wonder if there has been any solution found...
When flashing a new recovery, do not check auto reboot. Flash the recovery in Odin. When you see the word reset in the status window, remove the USB cable from the phone, remove the battery, replace the battery, boot into recovery. Hopefully, this method will work.
Hello friends
I had a problem with the mini z11, I have a hard brick.
I wonder if there is any recovery rom, or if the official serves me.
I can flash by nubia Toolstudio?
the terminal does not turn black screen on or enters recovery, flash a rom confusion mini z9.
I need help please, if you recognize the terminal QHUSB_BULK is hope.
Thank you for your interest, Greetings
Still a little bit early for Z11 Mini...
Did you unlock bootloader, rooted and installed some recovery?
Bricked device nubia z11 mini
Hi Guys,
I was looking to update the Nubia to v 2.04 from 1.40 so I used flashify to flash the stock recovery (worked earlier) but the system went dead.
I used tool studio to get the recovery back but now it is not reading my internal storage where the files are kept, it suggest mount error with system, data etc .... so what could be a way forward?
pratikbr9 said:
Hi Guys,
I was looking to update the Nubia to v 2.04 from 1.40 so I used flashify to flash the stock recovery (worked earlier) but the system went dead.
I used tool studio to get the recovery back but now it is not reading my internal storage where the files are kept, it suggest mount error with system, data etc .... so what could be a way forward?
Click to expand...
Click to collapse
Just flash twrp from pc and go to recovery
Then mount usb storage and copy the rom.zip and flash it
moha07 said:
Just flash twrp from pc and go to recovery
Then mount usb storage and copy the rom.zip and flash it
Click to expand...
Click to collapse
Now I have flashed rom v 1.32 , it is showing splash screen but it hangs at "Be Yourself screen", adb is also not detecting the device to install twrp through pc. Please share some detailed guideline.
pratikbr9 said:
Now I have flashed rom v 1.32 , it is showing splash screen but it hangs at "Be Yourself screen", adb is also not detecting the device to install twrp through pc. Please share some detailed guideline.
Click to expand...
Click to collapse
Follow this guide to flash twrp, use the vendor id from below guide
https://forum.xda-developers.com/android/development/recovery-unofficial-twrp-3-0-2-zte-t3550995
Then u flash the rom.
Before flashing the rom, wipe everything expect internal storage and sd card
Need persist.img
Hi,
Have got to know persist.img is corrupt. Hence, flashing is happening but no booting even twrp is not helping. Persist.img is usually found in fastboot img of the rom which helps to install rom in fastboot mode. Kindly do let me know if I can find fastboot.img of Nubia z11 mini.
Thank you
Hello guys,
i have the same brick mode as the op.
The system doesn't recognize the mobile, it only shows it as QHUSB_BULK and it keeps disconnecting.
What are the steps to follow from the pc?
I found somewhere one software called one click unbrick but when i try to install the drivers with it it says that "the system policy has been modified to reject unsigned drivers".
If i can take it to the place where the phone is recognized as a storage from the pc then i can take it from there.
Thanks
Unbrick and downgrade
I once brick my nubia the same way. BUT NOW ITS ALIVE AND WORKS FINE (sulking why didn't I bought the ZUK 2 even though at the time i bought z11mini they were similarly priced)
UNBRICKING:-
ALL you have to do is download the same firmware which was installed prior to the rom to which you downgraded to [ simply put if you had v2.40 running before and tried to install v1.40 then download the v2.40 rom for flashing), once downloaded {USE A PC OR MAC TO DOWNLOAD THE ROM OR ELSE IT MIGHT GET CORRUPT} copy it to the root of an sd card(2gb upto 32gb; sdxc cards may not work), insert the sd card into the phone , then press and hold the power button until the phone reboots, as soon as you see the bootlogo press and hold vol- and power keys simultaneously, you wold boot into nubia recovery now select update from sd card confirm and let it install as soon as update finishes your phone will boot back up normally. [UP TILL THIS POINT NO FILES WOULD BE LOST].
NOW YOUR PHONE WILL BE WORKING AGAIN.
DOWNGRADING:-
YOU DON'T NEED ANY EXTERNAL SOFTWARE FOR THIS
JUST DOWNLOAD THE ROM U WANT TO INSTALL AND PLACE INTO SD CARD AS ABOVE.
TAKE A BACKUP AND SAVE ON A PC, ANOTHER PHONE OR ANOTHER SD CARD{not the same one} OR ANYWHERE ELSE SAFE cause after this everything inside your phone will be DELETED.
BOOT INTO RECOVERY as STATED ABOVE.
-ATTENTION- DON'T install the rom as yet.
FIRST WIPE cache and data.
SECOND- INSTALL THE ROM SIMILARLY AS PRESCRIBED ABOVE.
THE SYSTEM WILL INSTALL AND REBOOT.
ENJOY{but why are you so eager to downgrade your system, i was once as well but after downgrade to lollipop.....nothing......performance was same as on Marshmallow.
ADVICE- for some reason the ota updater never shows any new updates, you will have to download updated roms from nubia website to install using recovery{the app has option to apply local update but it does nothing and gets stuck on nubia logo, u will have to restart your phone after that}, as long as you are installing updates u don't need to wipe data and cache and also your files will remain intact. BUT TO THIS ONLY EXCEPTION IS V2.06, on this you do not need to wipe data and cache but the rom itself will wipe all data on your phone so be careful. :good:
NUBIA Z11 mini is Dead
pratikbr9 said:
Hi Guys,
I was looking to update the Nubia to v 2.04 from 1.40 so I used flashify to flash the stock recovery (worked earlier) but the system went dead.
I used tool studio to get the recovery back but now it is not reading my internal storage where the files are kept, it suggest mount error with system, data etc .... so what could be a way forward?
Click to expand...
Click to collapse
I Have the same problem in my Nubia z11 mini , its already dead only it recognize when it connected to PC as QHSUSB_BULK ,
i have tried to flash through QFIL but no use ,
View attachment 4753025
pratikbr9 said:
Now I have flashed rom v 1.32 , it is showing splash screen but it hangs at "Be Yourself screen", adb is also not detecting the device to install twrp through pc. Please share some detailed guideline.
Click to expand...
Click to collapse
Please tell me how to flash TWRP with this condition my device recognize only QHSUSB_BULK in the device manager ,
NO boot loader and recovery mode
I mistakenly did a Factory Reset from Android Settings instead of going into TWRP and wiping everything. I downloaded TWRP Mondrianue 3.0.2 and used Heimdall command line from a Mac to load it. Now, the device constantly reboots and goes directly to the download mode. I can't seem to get it out.
Any thoughts?
Use Odin (get a PC somewhere) and flash your stock ROM onto it while in download mode. That should restore everything.
After attempting to flash a stock MD5 via odin on a rooted P600, I am no longer able to boot. I am also unable to get to the "downloading" screen. I am only taken to a black screen. I am able to access recovery only. Thoughts, suggestions, new Frisbee?
Looking back, I believe the error was flashing only bootloader (thus why its not working) with the update file. Attempting to flash anything via adb sideload or from an internal SD yield errors. I have read about some other devices being able to load a bootloader via SD but I am unsure if that is possible here. If I can get into download mode, I am sure the device could be recovered.