Hi, I'm completely new on all this mobile/android stuff, also sorry my poor English.
Out of nothing my phone bricked and I just wanted to recover my files from the internal storage.
Why I've tried so far: to install a custom recovery using Odin. Installation process were OK, I guess, judging by Odin and phone messages (on phone download mode you can read "custom binary download: YES (3 counts)". That's 3 because I've tried twrp-2.8.6.1-i9300 (tar) twice and recovery-clockwork-touch-6.0.4.4-i9300 (tar) once.
Where I'm stuck: I cannot see the options to access these recoveries form the recovery mode, just the already existing options (reboot, apply update, ...).
Thanks you for any help!
Vinicius
First of all flash chainfire auto-root. You can download it from here: https://download.chainfire.eu/229/CF-Root/CF-Auto-Root/CF-Auto-Root-m0-m0xx-gti9300.zip
Then try again to flash TWRP. If it will go ok, you can copy from recovery data from internal storage to sd card
Hi There,
I am in a similar predicament.
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, the phone would NOT come on unless I held the power button.
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.
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).
-I am not very versed with computer programming so please use simple words to help me
As previously stated. flash cf-autoroot and then flash twrp, both via odin. Then you should be able to access twrp (hold home and vol+/- (cant remember which, opposite from download mode) and press power once.
If you can get to twrp you can use its built in file manager to move your data to an sd card.
If no twrp its what is technically known as f*cked.
I wish I stole my HTC M9.
shivadow said:
As previously stated. flash cf-autoroot and then flash twrp, both via odin. Then you should be able to access twrp (hold home and vol+/- (cant remember which, opposite from download mode) and press power once.
If you can get to twrp you can use its built in file manager to move your data to an sd card.
If no twrp its what is technically known as f*cked.
I wish I stole my HTC M9.
Click to expand...
Click to collapse
Hi,
Thanks for the reply.
How would I flash cf-autoroot and thenflash twrp (I have no clue what this means lol).
Also what is twrp?
bossman111 said:
Hi,
Thanks for the reply.
How would I flash cf-autoroot and thenflash twrp (I have no clue what this means lol).
Also what is twrp?
Click to expand...
Click to collapse
Short and sweet: TWRP is a popular recovery system; cf-autoroot is the preferred method for rooting some samsung devices by member Chainfire
I could lay out all that here again in detail, but it's safe to say you are better off in the long run if read up on that stuff by yourself...
Check the excellent threads I linked in my signature! Trust me, it's not as complicated as it seems.
Related
LG Escape running 4.1.2
here is the progression of events:
1. rooted device
2. root seemed successful and no malfunctions
3. backed up all apps and system data with Titanium backup
4. the lg escape has no way to unlock the bootloader, so I tried various other methods. one of which was entering recovery mode via terminal commands. this is basically a hard reset, and it wiped all my data
5. I restored all my apps and data from my external sd card with titanium
My best guess is this is where something went wrong
6. upon restoration it prompted me to reboot the device
7. reboot passes manufacturer logo, but resets when AT$T logo appears
8. as stated earlier, there is no way to enter recovery mode during boot.
9. there is a hard reset during boot, but mine will not work, as it requires touching buttons which do not seem to be active in my stage of the boot sequence
so, I understand this does NOT mean my phone is bricked, but I don't know how else to get it to boot back up, or what is even causing the boot loop, as I DO NOT HAVE ANY CUSTOM ROMS flashed. any help here is very appreciated!
EDIT: so I have attempted to use adb on my pc to reboot into recovery from there, but it occurred to me that while I was in recovery the first time, I never checked "usb debugging". as a result my adb console commands cant even see my device. any way to turn on usb debugging while locked in a boot loop?
also, I can get it to enter download mode. I was hoping I could just reflash the firmware to it without needing to enable usb debugging, but have no clue how to do that while locked out of the phone.
I realize this is a very specialized set of questions, but it is necessary to ask here as the most people will see it. im open to any ideas
whitechameleon said:
LG Escape running 4.1.2
here is the progression of events:
1. rooted device
2. root seemed successful and no malfunctions
3. backed up all apps and system data with Titanium backup
4. the lg escape has no way to unlock the bootloader, so I tried various other methods. one of which was entering recovery mode via terminal commands. this is basically a hard reset, and it wiped all my data
5. I restored all my apps and data from my external sd card with titanium
My best guess is this is where something went wrong
6. upon restoration it prompted me to reboot the device
7. reboot passes manufacturer logo, but resets when AT$T logo appears
8. as stated earlier, there is no way to enter recovery mode during boot.
9. there is a hard reset during boot, but mine will not work, as it requires touching buttons which do not seem to be active in my stage of the boot sequence
so, I understand this does NOT mean my phone is bricked, but I don't know how else to get it to boot back up, or what is even causing the boot loop, as I DO NOT HAVE ANY CUSTOM ROMS flashed. any help here is very appreciated!
EDIT: so I have attempted to use adb on my pc to reboot into recovery from there, but it occurred to me that while I was in recovery the first time, I never checked "usb debugging". as a result my adb console commands cant even see my device. any way to turn on usb debugging while locked in a boot loop?
also, I can get it to enter download mode. I was hoping I could just reflash the firmware to it without needing to enable usb debugging, but have no clue how to do that while locked out of the phone.
I realize this is a very specialized set of questions, but it is necessary to ask here as the most people will see it. im open to any ideas
Click to expand...
Click to collapse
i have now tried to flash the firmware while in download mode using a less than legitimately obtained lg R&D tool. however, i need V10F_00.kdz and i am facing a bit of censorship. any kind soul willing to host this file on dropbox or similar so i can download it?
Usually devices have a button combination to press when powering on to get into different modes. Maybe try searching for the button combination of your phone on Google? Try ' lg escape button recovery ' ?
J2270A said:
Usually devices have a button combination to press when powering on to get into different modes. Maybe try searching for the button combination of your phone on Google? Try ' lg escape button recovery ' ?
Click to expand...
Click to collapse
believe me i have. the only combo i can get to is download mode. there is a combo for a hard reset, but my touch buttons arent active during boot.
The phone was working fine until the battery was empty. I tried to charge it and turn it on, but it's stuck at the Samsung logo splash screen. Holding the power button only restarts the device, so to turn it off I'll have to take the battery out. I don't know how to fix this, and if a factory reset is the only option, I need to backup my data first which I currently don't know how to either (without accessing the OS).
I've got to the Android System Recovery 3e menu and tried clearing cache, which did not help. The option to do a factory reset is also there, but I need to backup my data first, and I don't even know if this will fix the problem.
I'm also able to enter download mode.
When connected to my PC it detects an unknown device named 'samsung_android", and it shows up in adb. I've tried doing a backup through adb, but it wanted me to unlock the screen to accept the backup, which I could not, because I'm stuck at the splash screen.
Is there anything I can do to save my data? Anything through adb? Install root (never done this before)?
dinho10r said:
The phone was working fine until the battery was empty. I tried to charge it and turn it on, but it's stuck at the Samsung logo splash screen. Holding the power button only restarts the device, so to turn it off I'll have to take the battery out. I don't know how to fix this, and if a factory reset is the only option, I need to backup my data first which I currently don't know how to either (without accessing the OS).
I've got to the Android System Recovery 3e menu and tried clearing cache, which did not help. The option to do a factory reset is also there, but I need to backup my data first, and I don't even know if this will fix the problem.
I'm also able to enter download mode.
When connected to my PC it detects an unknown device named 'samsung_android", and it shows up in adb. I've tried doing a backup through adb, but it wanted me to unlock the screen to accept the backup, which I could not, because I'm stuck at the splash screen.
Is there anything I can do to save my data? Anything through adb? Install root (never done this before)?
Click to expand...
Click to collapse
Hey mate, can you get into the recovery mode? Try flashing the TWRP recovery and boot by pressing power button + home button + volume up and find an option to mount your USB storage via USB cable and see if your phone's folder tree is available from the Windows Explorer and hopefully you can backup your data by then. Just make sure you have all the drivers ready.
Hope that helps.
cglegion said:
Hey mate, can you get into the recovery mode? Try flashing the TWRP recovery and boot by pressing power button + home button + volume up and find an option to mount your USB storage via USB cable and see if your phone's folder tree is available from the Windows Explorer and hopefully you can backup your data by then. Just make sure you have all the drivers ready.
Hope that helps.
Click to expand...
Click to collapse
Yeah, I can get into recovery mode. But how do I get the TWRP to my phone? Do I have to put it on my external memory card and then load it from there?
And I could only find it for a S2 Exhilarate SGH-i577 device. Does it matter if my phone is a S2 GT-I9100?
I've never rooted my phone earlier. Is a root necessary to flash a ROM?
dinho10r said:
Yeah, I can get into recovery mode. But how do I get the TWRP to my phone? Do I have to put it on my external memory card and then load it from there?
And I could only find it for a S2 Exhilarate SGH-i577 device. Does it matter if my phone is a S2 GT-I9100?
I've never rooted my phone earlier. Is a root necessary to flash a ROM?
Click to expand...
Click to collapse
Correct. Put the TWRP zip on your external and flash it normally via recovery mode such as CWM not the android 3e recovery. Or find an odin flashable zip for yoyr device.
I am very sure there is one for I9100 because I ran into the exact same problem before and managed to figure it out. You just have to search for it can't give you a link because I'm on mobile now.
You need to root your phone in order to install a new recovery such as TWRP/CWM or even flash new kernel and ROM.
Good luck.
Hello all,
So, let me keep it as short as possible.
The incident
I was talking on the phone, after the call i tried to hang the phone and there was just a black screen (phone stuck).
Pushed Power button steady and the phone rebooted and never boot again.
Mobile bio
The phone was rooted (2+years ago with CF Root)
Rom was stock European 4.1.2
I have available a full nandroid backup (boot.img etc)
The latest Custom recovery i had installed was CWM (ver. 4 something).
Current status
The phone is stuck at boot with a yellow triangle.
The phone can get to download mode (and be recognized by odin)
The phone cannot get to the recovery menu, (to be more precise when i press vol+, home, power the phone finally gets to a black screen {no backlight} but it is recognized by the command "adb devices" as in recovery status)
Kies cannot connect either in recovery mode or download mode. (Stays in connecting message).
Tried the following
Installed various kernels (Siyah-s2-v4.1.5, Siyah-s2-v5.0.1 etc)
Installed various roms (including stock roms) via odin with NO error.
Installed the original .pit file for 2Gb S2 system memory.
Tried the flashing method with 3 separate files (CODE_I9100XXLSJ.tar, CSC_HOME_OXX_I9100OXXLS1.tar, MODEM_I9100XXLS6.tar) via odin appropriate fields.
Tried two different Odin versions (1.85, 3.07)
So after trying all these, i finally rest my hopes in the community.
I really hope there is something more i can do, in order to fix my phone.
Thanks in advance for your time and effort.
Hello again...
Still trying to find a solution...
Some more info, in download mode i get the following info:
Custom binary download: YES (1 counts) and it doesn't change no matter how many times i flash anything through odin.
Does this count change only if you flash a new rom via recovery?
Anyway, i'm pretty desperate so i keep on trying to find a solution...
ANY help appreciated.
Hello a few days i restored my galaxy to factory settings from inside the own phone settings everything was working fine until a couple days ago the phone started to rebooting every now and then
Right now is stuck on the samsung logo after you turn it on and in the recovery menu i got this error
E: failed to mount /efs (invalid argument)
I try to wipe the cache date and even doing a wipe from the recovery menu but nothing when the phone turn on and gets to the samsung logo it stays there a while and reboots again
I try doing this instructions from this post from another forum
The key for me was selecting the second item in the Tools menu (Firmware Upgrade and Initialisation?) - it seemed to bypass that whole 'connecting' process and just went to work. Here's the writeup that I put together (I need to insert the Kies screenshots that I captured).
- if you don't already have the Kies software installed on your PC, download it (just search Google) and install it. The first time it runs it'll update itself to the latest version so make sure you run it once before proceeding.
- put your phone in Download mode: with the phone completely off, press and hold the Volume Down and Home and Power buttons simultaneously, and release them all when you see the Samsung splash screen
- connect the phone to your PC with the USB cable that came with the phone
-- if you've never had the phone connected to your Windows-based computer before, you'll see messages about installing drivers, etc - just wait until this is done (may take 5 or 10 minutes) [I don't know what happens if you have a Mac - it probably just works]
- in the Kies software, select the second item in the Tools menu and just follow the prompts to enter the model number (in CAPS) and IMEI/Serial Number (both found under the battery - it's ok to remove the battery at this point)
- the Kies software should start downloading the correct firmware for your phone from the Internet; once that's done (depending on your Internet connection speed) it'll begin downloading that to the phone (this probably takes 10 minutes or so)
Click to expand...
Click to collapse
I manage to do all the steps but nothing now the phone turns on and it gets stuck on the samsung logo but this time it doesn't reboot it just stays there and in the recovery menu still have the same error
Does anyone have any solucion or a guide that explaings well how can i fix this?
I have seen other guides that saids i need to either root the phone and install a custom recovery menu but since the phone doesn't boot i have no clue how to do this
Edit: A few moments ago i tried doing this as well (i cant post the complete youtube link)
watch?v=xJMJLdzHaAY
The phone now turn on but i have a black box with some yellow letters i'm guessing is the called safe mode is there anything i can do from here?
Been honest i'm completely lost here
Can someone please give a valid link to download?
Edit: Sorry, wrong post.
You can try flashing a recovery (cwm official is best) via odin but most likely you'll need to flash a stock rom, definitely if the cwm flash doesn't solve it.
Beamed in by telepathy.
shivadow said:
You can try flashing a recovery (cwm official is best) via odin but most likely you'll need to flash a stock rom, definitely if the cwm flash doesn't solve it.
Beamed in by telepathy.
Click to expand...
Click to collapse
is there any tutorial on how to that for the I9300? because i to be honest without a tutorial i dont have a clue on how to start doing this, i will actually prefer a stock rom is by stock rom is a official firmware from samsung
Hi everybody,
I tried to install Magisk 21.2 on my stock Oreo rom with Magisk 20.4 already installed. I've used the recommended method for installation in Magisk Manager, and I left the AVB/dm-verity option unchecked. It resulted in a bootloop.
Before updating I did a backup of the boot partition, so I could restore the previously working Magisk 20.4. Now I have two questions:
1) Is there something else I should do other than restoring the boot partition after a bootloop?
2) Is there a way to install the new Magisk or should I just dismiss the update notification?
Happened to me As well on my G6.
I had to reinstall the rom. good thing i had backup.
I've downloaded the zip file of Magisk 21.2 and flashed it with the rom after wiping almost everything, and even tried flashing a different rom with it (I'm using stock A9)., but it seems it resulted in a bootloop every time.
There is a new magisk 21.3 from yesterday, which i hope fixed those issues as i am not planning to go though that hassle again.
I tried the new 21.3, and still it causes bootloop, at least I'm glad I'm not the only one.
DannyynnaD said:
Happened to me As well on my G6.
I had to reinstall the rom. good thing i had backup.
I've downloaded the zip file of Magisk 21.2 and flashed it with the rom after wiping almost everything, and even tried flashing a different rom with it (I'm using stock A9)., but it seems it resulted in a bootloop every time.
There is a new magisk 21.3 from yesterday, which i hope fixed those issues as i am not planning to go though that hassle again.
Click to expand...
Click to collapse
It happened to me, same setup as the OP and did the direct install method from Magisk Manager. My phone is stuck in bootloop at the triangle/! scrren and I can't access TWRP via the normal buttons manner. Also, can't get any ADB to detect the phone (I am using a new PC that probably never connected to this phone despite loading ADB, drivers, etc. - I am going to resurrect the previous PC to see if can connect).
May I ask how you restored the saved boot image? via TWRP restore?
I've rooted and played with many ROMs on various android devices, but I'm no expert and this one has me stumped.
Yes, I did a backup of the boot partition before flashing Magisk and then I restored using TWRP restore. It's not the first time that a new Magisk version causes bootloops on the G5, to I was prepared this time.
By the way, if you don't have a backup, you may try to flash the Magisk Uninstaller zip, and without rebooting, the old Magisk 20.4. In theory it should do the job.
tremalnaik said:
Yes, I did a backup of the boot partition before flashing Magisk and then I restored using TWRP restore. It's not the first time that a new Magisk version causes bootloops on the G5, to I was prepared this time.
By the way, if you don't have a backup, you may try to flash the Magisk Uninstaller zip, and without rebooting, the old Magisk 20.4. In theory it should do the job.
Click to expand...
Click to collapse
Thanks, But how to access TWRP or flash the zip? I haven't found any technique to access recovery (Power+VolDn doesn't work, only allows Factory Reset screen). How to access Fastboot to use ADB (I assume that would be the technique)? I did manage to bring up some odd screen that had a two-line message about fastboot by, I believe, using Power+VolUp.
For clarification this is what I now have:
Phone off (remove battery). Insert battery. Press power button until brief vibrate (1-2 seconds). Release power button. Triangle with "!" displayed "Your device cannot be checked for corruption. Lock the bootloader. " screen displays for about 3 seconds, screen goes black a second or less. Back to the previous warning screen.
Press and hold Power button + Vol Dn acts just like the above, but if I press power + press/release/press/release... I can get the factory data reset (Yes or No(Exit) options) - I haven't accepted that.
I've tried connecting PC to the USB port and two things: as soon as I connect it, the phone powers on and does the looping again. My PC doesn't see the phone in Device Manager and ADB won't list it. I did (one time) manage to bring up the two-line fastboot message at the top of the screen.
BTW: when it first tries to power on, before the Lock the bootloader screen, there is a small, scrambled white area (text?) at the bottom of the screen.
I don't know when was the last time (if ever) I attached to the phone via USB (probably a few years ago when I initially installed TWRP). Haven't really done much other than upgrading TWRP (via TWRP), Magisk (via Magisk Manager), and the very occasional nandoid backup via TWRP (I have one from 3 months ago).
Any further assistance or info would be greatly appreciated.
To access TWRP, turn off the phone, then keep pressed Volume down+Power and once you see the LG logo release the power button and press it again. The phone should ask you if you want to reset everything: if you press yes and then confirm, you will:
1) Enter in TWRP, if you have TWRP installed, or
2) Erase the whole internal memory, if you don't have TWRP installed.
As you already have TWRP installed, it should be quite safe to go through the reset procedure, or at least that's what happens on my phone. If you don't want to take the risk, you can still use fastboot to boot a TWRP image you have on the pc, just write
Code:
fastboot boot <path_to_twrp.img_on_pc>/twrp.img
To do so, you first need to boot into fastboot: you can just turn off the phone and, keeping the Vol- pressed, connect the USB power cable to the phone. It will boot into fastboot.
One more method could be booting into download mode (Vol+ and connect the USB cable) and flashing an original firmware using LGUP, but that is way too much for a phone that already has both TWRP and fastboot accessible.
tremalnaik said:
To access TWRP, turn off the phone, then keep pressed Volume down+Power and once you see the LG logo release the power button and press it again. The phone should ask you if you want to reset everything: if you press yes and then confirm, you will:
1) Enter in TWRP, if you have TWRP installed, or
2) Erase the whole internal memory, if you don't have TWRP installed.
As you already have TWRP installed, it should be quite safe to go through the reset procedure, or at least that's what happens on my phone. If you don't want to take the risk, you can still use fastboot to boot a TWRP image you have on the pc, just write
Code:
fastboot boot <path_to_twrp.img_on_pc>/twrp.img
To do so, you first need to boot into fastboot: you can just turn off the phone and, keeping the Vol- pressed, connect the USB power cable to the phone. It will boot into fastboot.
One more method could be booting into download mode (Vol+ and connect the USB cable) and flashing an original firmware using LGUP, but that is way too much for a phone that already has both TWRP and fastboot accessible.
Click to expand...
Click to collapse
My phone never got past the bootloader screen (i.e. never got to the LG logo screen). When I booted into fastboot mode with the Vol+ button, I could issue commands like "fastboot devices" which would return that it saw my phone, but attempting to use fastboot to reload TWRP didn't work - some say the LG fastboot has been neutered.
Eventually, I had to indeed use LGUP/Uppercut and reload the stock Oreo and the phone came back up. BUT attempting to reboot into bootloader not only didn't come up in TWRP, but I got the little dead Android image. I ultimately had to downgrade to OEM nougat, jump through a few hoops, and finally got TWRP installed. Then it was just a matter of restoring a backup or reflashing a newer ROM (I ended up loading lineage 16, no gapps, with microg etc.).
Somehow the magisk upgrade really trashed my recovery partition somehow (??). I've always made sure to have at least a couple of TWRP backups, but this time I was screwed royally when I couldn't access recovery. I forgot what an ordeal it was to get TWRP & root on this phone originally.
Thanks for your help.