Please can you assist me.
I've read through so many threads explaining that it is easy to fix if I use ODIN. However I cannot seem to get ODIN to recognize my Galaxy S3.
I was doing a factory reset on my device, which has Cyanogenmod installed. Upon rebooting, the phone is now stuck with the Teamwin logo and it continues to loop.
In cannot seem to charge the phone because it's stuck in this mode and when I install ODIN and along with the SAMSUNG USB Drivers. I have no luck with my computer recognizing the device. I am able to get into the Download mode by holding Power, Volume Down and Home buttons - I click Volume up to continue. I then check my ODIN screen and it never appears to say ADDED or anything of that sort.
I'm scared that my phone is going to soon run out of charge and then I will not be able to even attempt to fix this. Please help me.
I've tried the above steps in both Windows 8.1 and Windows 7 and cannot get either of them to recognize my device.
N.B. I have also tried different USB ports as well as different USB cables.
Once again, I plead for any assistance.
Can u go to the custom recovery ??
If so
Do a clean wipe
Do a factory reset (do not do a clean to install new rom,just erase your data)
Wipe your cache
Wipe dalvik cache and see if u can boot it up
Goodluck
Use the latest odin version and see
And why didint you take a nandroid backup before installing custom roms
If u took it
Just restore it
U will surely boot it up
Hi there,
Thanks for your reply.
I managed to solve the issue by using a computer which already had my device USB drivers installed.
The other 2 computers I tried didn't seem to want to recognize the device due to the bootloop - but when linking up to a computer which linked to my phone prior to the ordeal, ODIN then recognized the device and I was able to load stock rom back on.
FYI, I wasn't able to access recovery.
Thank you for your quick response.
Hi all,
I recently installed Lineage 14.1 on my XT912 using safestrap, I decided that I wanted a larger Gapps package than pico, so I went to reinstall lineage and Gapps.
I was doing this away from home with a Linux PC instead of my normal windows one, and I ended up not being able to push over the larger Gapps file.
Then I did a really dumb thing that I didn't know would be a problem at the time, I restarted the device before reinstalling Lineage.
So I had softbricked it.
Then I tried using RSD lite to flash the stock XT912 ROM, but I ended up finding out that it would fail unless I erased the partitions I was trying to write to, so I went and erased every partition
including the boot partition.
When I went back to flash it I found that the battery had dropped below 80%, so fastboot no longer let me flash it.
So not knowing that I absolutely could not turn it off now that I had erased the boot partition, I went and disconnected the battery and soldered my Li-Po charger to the battery so I could charge it manually manually.
Stupid me.
When I went and tried to boot into fastboot I got a black screen and when I plugged the phone into my PC it would just keep throwing USB errors while disconnecting and reconnecting over and over again.
I'm pretty dang sure it's hardbricked now, but it there's anyone out there who has a solution to this, I'd love to hear it.
Thanks,
-Alec
I'd need some help:
I have a Mediatek phone with TWRP 3.2.3.
I charged my phone using Qualcomm 3.0 fast charger which destroyed the data circuit of my phone.
So the data connection (with the computer, USB stick etc, USB audio with my car) doesn't work.
I tried to reset my phone back to factory settings. But the mistake I made was that I went to the settings of the phone and made a factory reset. The phone booted to TWRP where I tried to restore the backup I had. Restore process went OK and the phone booted - but back to TWRP. It doesn't seem to boot normally at all and I cannot flash it via USB connection. It boots to TWRP each'n'every time.
Is it gone/bricked for good or are there still some ways to get it fixed. Mainboards are not available anymore so if I cannot fix it then it's totally bricked.
Thanks in advance.
Hello One and All,
Apologizes if this is in the wrong section. As the post stated, i did a dirty flash of a rom on-top of itself (https://forum.xda-developers.com/lg-v30/development/stock-t-mobile-lg-v30-stock-collection-t3980701) to force the kernel to change. This, somehow, removed TWRP from the recovery (even tho the rom said that it wouldn't touch the recovery) so now when i do the button dance, it master resets the phone instead of going into TWRP. Phone still has the bootloader unlocked, but download mode will load, sit for a moment, then restart. 3 computers, running Win10, and FWUL bootable USB doesn't recognize the download mode, also tried different USB cables.
Attempted to use LGUP to essentially follow the rooting process from start to finish, but once the LGUP attempts to load the 10D.kdz onto the phone, the phone just reboots and LGUP does nothing but complain about connectivity to the phone.
Anyone have any suggestions or am I SOL? At least my phone still functions, it's just in the odd middle ground of not having root, but some applications wont work because it thinks it's rooted (Google Pay NFC).
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.