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
hi,
my oneplus 3 has been rote since i got it (i bought it on launch day) but since i updated it to the beta 19, my phone is no longer rooted : when i put the phone in fastboot it says that my bootloader it unlocked but all the apps who requier root are saying that the phne is not rooted and i cant get twrp to work. i tryied with the official app on my phone and with a program called "tool all in one" (https://forum.xda-developers.com/on...ol-tool-one-driversunlocktwrpfactory-t3398993) and when i flash twrp from the program, i can boot into twrp but then i can't access my files and after i boot the phone, i can no longer boot to twrp
does anyone have a solution that doesn't involve me wiping the phone?
You loose root after updating. Try installing twrp again and then rooting it. Use the toolkit for oneplus 3. Simplifies the process
what do you mean by "then rooting it" ?
the program i use does the same thing as the toolkit and when i install twrp, as i said, it can boot on twrp one time and in twrp i can't access my files and after i boot the phone i can't get back to twrp ,i get the stock recovery
Unless your ROM has built-in root, after flashing TWRP, you have to flash SuperSU or Magisk to obtain root. Mere flashing of TWRP will not give you root.
I know but i can't get to the folder when the magisk file is : when in boot into twrp i cant see my files
Few details... it's quite difficult to help you.
What's the root method? Magisk, SuperSU or Kingroot? Which version?
Ps TWRP recovery is not depending by root, you just need to unlock bootloader (surely it's already unlocked) and flash the same recovery, from PC, via the command "fastboot flash recovery filename.img".
Now enter in TWRP:
1) Wipe /system and /cache;
2) Flash another time Open Beta 19;
3) Flash Magisk or SuperSU (be sure to have latest release);
4) Move TWRP img file from computer to device, then flash it another time (because firmware provides the OOS stock recovery);
5) Reboot and wait 5-10 minutes, because of cache rebuilding.
Tell me if you solve
I am using magisk
Yes my bootloader is unlocked
My problem is that when i flash twrp i cant access my files so i don't want to wipe system if i cant reflash something after
I think that I'll wait for the next update, maybe then it will work
But thank you for your help
Which version of TWRP do you have? Try eng.stk's latest version.
I tryied 3.1.1-2
The eng.stk is not available anymore
Your phone is encrypted, so you have to format data ( but your internal storage wiped by formating data, so back it up ,then only twrp read files in your storage)and flash custom kernel then boot restore backup .
how do you know that my phone is encrypted? i never encrypted it
i use titanium backup so i can't back my phone up until i get rot back
Whenever you flash stock ROM it encrypt if you boot into system directly . So twrp could not read internal storage. Whenever you flash stock ROM you must flash custom kernel or any other method to avoid encryption. This is happened to me and what I'd done is flash custom kernel before boot into rom
To save your data try this
https://forum.xda-developers.com/oneplus-3/how-to/unencrypt-oxygenos-loosing-data-t3412228
Who said that? Check this: https://forum.xda-developers.com/devdb/project/?id=15934#downloads
Edit: If you want to save items in internal storage, you can use ADB commands instead of TWRP. You can also simply copy and paste if your PC recognises the internal storage of your phone.
I succeeded but i had to clean everything and use the last backup i made a week ago
Thank you all for your help
Hi,
I wanted to update my Pixel C to the most current factory image with flashfire as i did it before a few times without problems.
So I DL'd current factory image from https://developers.google.com/android/images#ryu, opened it in flashfire and said it should flash the normal partitions except recovery as i don't want that it overwrites my TWRP.
Flashfire analyzed the zip file and after i said "flash" it restarted my Pixel into a black screen. At this point i was wondering that nothing more happened.
I waited for 10 minutes so that maybe something in the background could happen, but there was no further action. The screen kept black.
After these 10 minutes i restarted the device but now it always runs into TWRP directly instead of starting the system
I also tried to install the zip manually in TWRP but it tells me
"Could not find 'META-INF/com/google/android/update-binary' in the zip file.
Error installing the zip file '/usb-otg/ryu-n2g48c-factory-0bc0ee15.zip'"
As you can see from the error message i also tried to dl the file again and install it via OTG but the same thing.
If I go into the file manager in TWRP i can still access the folders from the sdcard.
The bootloader is unlocked of course.
Anyone an idea what i can do without loosing all the data?
Thanks in advance
Download the full system image and extract it. There should be a flash_all-file (bat for windows of sh for linux). Open it with an editor and remove the "-w" option in fastboot. "-w" is the switch for wipe. After you removed it, you can flash the complete image and your system should boot again into android. After that you can install a custom recovery, etc. again.
Thank you peter, worked like a charm for the system flash. Now follows the TWRP etc again
EDIT: ok, the system flash was the only thing that worked like a charm. I tried flashing TWRP with NRT but didn't work. I am stuck now at a "no command" screen when i start the device.
To install the custom recovery NRT tells me that i will loose all my data, so i wanted to backup everything.
Unfortunately i can't backup everything now as the temp booted TWRP demands a password to decrypt the sdcard, but i only have a pattern and no password set.
So now i try to flash everything again and to install twrp without loosing all the data.
Hey everyone I have flashed android 7.1.2 August again and android started afterwards without any problems. I was able to restore the backup of all the apps from Google.
Than I wanted to get back root and flashed TWRP with Nexus Root Toolset, but now only TWRP starts every time I switch on the tablet. Any ideas what I can do?
EDIT: I fixed it somehow with flashing the whole firmware package again and than the TWRP wich broke the startup again so i ended up in a TWRP bootloop. Therefore i flashed android again and TWRP 3.0.0.0 than TWRP 3.0.2.4 (something like that) and after like 3 to 4 different flashing steps it worked again. I have no idea what happened during the first flash of Andoir 7.1.2 but i think that something broke there.
Hi everyone,
I tried to update my rooted Pixel C with Android 8 and TWRP 3.1.0.0 from August build to September build with FlashFire.
All of the following have I done on my Nexus 5x as well and it worked as a charm there.
Therefore i dl'd the corresponding zip-file from google dev page and started the update with FF. It said to me it can update the boot, system, recovery and vendor partition so I unchecked the recovery partition only to keep TWRP. I also told FF it should include SuperSU again to root the new Android.
After the update the device was unrooted, so i tried to start into recovery to install superSU manually. But TWRP was gone and i get everytime the android on the back with the text "no command".
Therefore I tried to flash TWRP with NRT again. But after the flash the device always starts into TWRP and Android isn't starting anymore.
I can use NRT again to flash Android without loosing my data but than TWRP is gone again.
So either the device always starts into TWRP or I have no recovery installed.
Anyone an idea what i can do to flash TWRP again and to fix the boot order or whats broken than?
Regards,
flattervieh
I don't have the C but here's what I would try. First, have your device booting normally with the stock recovery. Then use fastboot to boot into TWRP, not flash it. When it boots into TWRP then flash supersu. From TWRP then boot back into the bootloader and then flash TWRP with fastboot.
Flash the latest (beta?) TWRP. It allows reading the encrypted data folder.
Short notice, i'm still struggling with the problem.
In the meantime I tried the following:
1. I temporarely booted TWRP 3.1.0.0, with this version I was not able to encrypt the data partion (always invalid key) but I was able to see the system partition and I installed SuperSU. After that i restarted into the bootloader and flashed TWRP 3.1.0.0.
This led to the same phenomenon, that my pixel always boots into TWRP and not into Android itself.
2. Same thing as before but with TWRP 3.1.1.1.
With this version I was able to see the size of the data partition, but I was also not able to read or write onto it. (Again invalid code) I installed SuperSU and made a device restart without flashing TWRP 3.1.1.1.
This led to a totally softbricked device with a boot into "no command" screen.
After flashing Android again via fastboot Android starts correctly and I can use the device but root is still not working.
Regards
I'm not sure why twrp isn't sticking. But the android on its back with "no command"is the stock recovery. To get into it simultaneously press and release the power and vol up keys. You might have to try it a few times as the timing can be very finicky. From there you can boot into the system, you don't need to flash the factory image and start all over.
Can someone tell me how I can safely update from open beta 9 to open beta 20 while maintaining root. I just want to make sure if there are any extra steps since open beta 9 was before the treble update. I am rooted with magisk.
also can anyone share updated twrp links or links for anything else I need if possible. Thanks
I heard that, I followed the guide in the development section and got and error when trying to flash it. I'm on TWRP 3.2.3-1 as well.
Yes, everything is fine, I have root. It took me a while, because of TWRP. The only problem is, that while you can get magisk, twrp will get overwritten by stock and I could not prevent it.
Process:
1. Install stock recovery (from here: https://www.androidfilehost.com/?fid=674106145207488252) in fastboot (fastboot flash recovery filename.img)
2. Install the new open beta
3. Download magisk on your phone
4. Install TWRP by codeworkx (from here: https://forum.xda-developers.com/oneplus-5t/development/recovery-twrp-3-2-1-0-oreo-8-0-8-1-t3729673) in fastboot and boot to twrp immediately.
5. Install magisk from within TWRP's first boot
6. After reboot twrp will most likely get overwritten by stock recovery, but we don't care as we have magisk already.
7. Profit.
@jazzgott so is there no way for me to reinstall twrp after updating? How will I update to new versions after?
@jccspeed
1. flash twrp via fastboot (pc, usb cable and phone and everything in need for this needed)
2. after flashing the recovery, turn off your phone, this is important.. do NOT boot your phone into the OS after flashing.. turn it off (chose power off with your volume keys within the fastboot mode and press the standby button once shortly)
3. hold volume down und power button at the same time until you see the "boot loader unlocked" warning stuff.. keep it pressed there for 2 or 3 more seconds. then let loose of these buttons.
4. you should now be in TWRP. congratulations.
if you now flash magisk, you will keep twrp as long as you keep magisk installed. you can freely boot into the OS and still have TWRP installed. How ever, if you don't install magisk and boot into your OS, your OS will overwrite TWRP with stock recovery.
forgot to mention: please use codeworkx pie twrp. its the one I have installed and have gotten into no problems so far.
@jazzgott @moeq123
Does this method erase the user data? I am encrypted and rooted(magisk). I want to preserve all my data.
@ajithpoison
at first I want to mention something important: always do a full backup.
if you unroot your phone (say, if you uninstall magisk using the uninstall.zip from within the magisk app itself and reboot) you should be able to update to open beta 20 via system update settings (where you need to choose a .zip file for the update.. so you need to download the open beta 20 rom from onceplus website).
(please verify that you are on stock recovery after the uninstalling magisk and reboot process. do this by booting into recovery with the power and volume down method. if you don't know how, google how to boot into recovery for your device)
This updating process should not erase your user data at all.
But be aware, that, if you want to go back to stable releases, you have to wipe everything.. so your user data will be erased if you choose to go back to stable releases.
if you want root and twrp back again, follow my instructions mentioned above.
@moeq123
Let me explain my situation in brief.
I am on the open beta channel. I am rooted(magisk) and I have the official TWRP and I am encrypted.
This is how I update everytime:
1. Download the zip
2. Reboot to recovery
3. Wipe cache and dalvik
4. Install update.zip
5. Install Magisk
6. Wipe cache and dalvik again
7. Reboot
This time, the above method will not work due to the compatibility thingy. I want to preserve app data. There are specific apps which I use and I don't want to lose those app's data. Previously I used titanium backup to take backup of app data. I am not sure whether backing up the app data and then restoring it will work since I am upgrading from oreo to pie. Is there any definite way to backup and restore app data after upgrading to pie?
I am summing up the method which I have to follow now. Correct me if I am wrong.
There are two methods which I know as of now.
Method 1:
The official method given by FunkWizard which involves deleting the compatibility.zip for which some users have reported ERROR 7.
Method 2:
1. Download Magisk & OB20 and have it in internal storage and switch off the phone.
2. Install stock recovery via fastboot.
3. Install the new open beta via stock recovery and switch off.
4. Install TWRP by codeworkx and boot to recovery
5. Install magisk from within TWRP's first boot
6. Clear cache and dalvik
7. Reboot to system and Profit.
(Will TWRP remain as a recovery after following all this or will it get overwritten by the stock recovery?)
@moeq123
Nevermind. I have got it to work without losing any data. I followed all the steps which were in the post by @funkwizard who put up the OP5T OB20 Official update post. It worked well except for one thing. The magisk manager did not show up even after installing magisk through the recovery. (I use BluSpark recovery). So I did a manual installation of the magisk manager apk and everything worked fine. I did not lose any data and so far no bugs.