After flashing ROM and then installing gapps (aroma) my phone automatically rebooted to TWRP again before complete installing gapps and now my phone can't turn it off just keep rebooted to TWRP can't run to fastboot also my phone storage was not detected in desktop using USB cable when in TWRP. tried some dd misc command in TWRP Terminal didn't work. any idea how to fix this?
I have an stock android backup and tried to restore and still didn't work always boot to TWRP when rebooted system/bootloader even power off
I tried to run fastboot in TWRP by holding pow+vol+usb cable didn't work, luckly my phone battery runs out so its forced to shutting down, so i charge my phone then i can run fastboot mode hmmm this problem looks weird in fastboot i tried to replace TWRP and run TWRP then restore my backup and my phone working again not looping in TWRP
I'm having the same issue, you resolved it by letting the battery die?
mzman said:
I'm having the same issue, you resolved it by letting the battery die?
Click to expand...
Click to collapse
Did you ever figure this out?
Yes I ended up holding the power button down+vol sequence to get back to fastboot mode then loading TWRP via ADB again.
Related
So, i installed A LOT of custom roms on my gs3, and the last one screwed it up, so i got android 5.1.1 on my gs3 and when it tried to boot up (after optimizing apps stuff...) it just stopped at "Finishing Boot" and it stayed like that for couple of hours, then since i don't have a power button to enter download mode i made my own homemade usb jig and got my gs3 in download mode and i got it back to stock, then it stopped at samsung logo and it was just booting like that whole night. Then i tried diffrent versions of stock roms, kernels, even new pit file, still nothing. So i've read on couple of forums that i need to enter recovery mode and wipe data & cache(but odin does that automatically right ?) and i can't enter recovery mode cause i have a broken power button(and no i can't connect wires cause when i got rid of the power button i accidentally pulled out one of the connectors).So how can i enter recovery without a power button if i can't boot up the phone ? Or is there any other fix ? Or it's dead ?
P.S I can't take it to service no warranty + binary count is 14 and i can't reset it without my phone booted up.
No power, no phone. It's that simple. Fix the power button and then you can boot it up. No other way possible.
I wish I stole my HTC M9.
you could try thru usb then adb command: fastboot reboot recovery (if i remember correctly)
edit: just read you can't even turn it on
shivadow said:
No power, no phone. It's that simple. Fix the power button and then you can boot it up. No other way possible.
I wish I stole my HTC M9.
Click to expand...
Click to collapse
Phone worked 1 year without a power button and it worked just fine, that isn't the problem here...
hansonchen said:
you could try thru usb then adb command: fastboot reboot recovery (if i remember correctly)
edit: just read you can't even turn it on
Click to expand...
Click to collapse
How do i send adb command, since gs3 doesn't have fastboot mode only download mode, and adb commands are only available thru recovery mode...
mr.r0ot said:
How do i send adb command, since gs3 doesn't have fastboot mode only download mode, and adb commands are only available thru recovery mode...
Click to expand...
Click to collapse
go to this link:
http://forum.xda-developers.com/galaxy-nexus/development/adb-fb-apx-driver-universal-naked-t1379875
download the driver, install once while gs3 booted, then in download mode install the driver again - while phone is connected
i haven't been able to get a "fastboot devices" respond while in download mode, maybe i'm not doing it right
the driver supposed to support galaxy s3 international with adb and fastboot
hansonchen said:
go to this link:
http://forum.xda-developers.com/galaxy-nexus/development/adb-fb-apx-driver-universal-naked-t1379875
download the driver, install once while gs3 booted, then in download mode install the driver again - while phone is connected
i haven't been able to get a "fastboot devices" respond while in download mode, maybe i'm not doing it right
the driver supposed to support galaxy s3 international with adb and fastboot
Click to expand...
Click to collapse
I can't boot up the phone ... it stuck on samsung logo not even boot loop...
mr.r0ot said:
I can't boot up the phone ... it stuck on samsung logo not even boot loop...
Click to expand...
Click to collapse
installing the drivers only need any gs3 but since it's stuck on logo only, you can't do anything.
i thought you said you have a home-made jig to boot into download mode
Odin don't wipe data and cache automatically. I had bootloop problem after flashing stock too you have to get to recovery anyway you can and format cache and data from there. As I know you can flash files through odin with your home-made USB jig. So there are some recovery zips that will boot into recovery directly after flashing them. You can either find one of them or you can ask someone to edit one of the recovery zips for you. The final way I can think about is adb. You can go to download mode with your USB and then you can use adb. Give adb this command. Adb reboot recovery and it will reboot to recovery. If I helped you in any case press the ? tnx button.
Hi, I was just messing around my phone and installed five Magisk modules and then after reboot, my phone didn't want to turn back on. It was stuck at the boot animation and nothing else was happening. I kept it overnight plugged in to see if it turns on by any change. But on the next day, I found it to be super warm and it was still stuck at the boot animation.
Now all I have to do is, reboot to recovery mode, clear its whole data and reinstall the ROM (as I didn't make any backup).
But the main problem is that the Volume+ button in my phone is broken, and it does not work! Somehow I can still access the fastboot mode. I can use a command to delete all my data. As they're Magisk modules, clearing the data might not unbrick my phone (I'm not sure).
Is there any way I can reboot my phone into TWRP recovery through fastboot mode? Or can clearing the data in fastboot mode fix the problem?
SGoraiCS said:
Hi, I was just messing around my phone and installed five Magisk modules and then after reboot, my phone didn't want to turn back on. It was stuck at the boot animation and nothing else was happening. I kept it overnight plugged in to see if it turns on by any change. But on the next day, I found it to be super warm and it was still stuck at the boot animation.
Now all I have to do is, reboot to recovery mode, clear its whole data and reinstall the ROM (as I didn't make any backup).
But the main problem is that the Volume+ button in my phone is broken, and it does not work! Somehow I can still access the fastboot mode.
As they're Magisk modules, clearing the data might not save my phone. My phone's not going to turn on (I'm not sure).
Is there any way I can reboot my phone to TWRP recovery through fastboot mode? Or can clearing the data in fastboot mode fix the problem?
Click to expand...
Click to collapse
Two Methods.
1- Some phones actually respond to fastboot reboot recovery. This is quite natural given adb reboot recovery, but unfortunately is non-standard. I found lots of people suggesting this method so I offer it here in the hopes that it works for some, but it didn't for me.
2- Some phones will actually let you book into an image via fastboot without flashing it. This will allow you to load a recovery image without needing to reboot the phone at all. You need a copy of the recovery image on your computer, but running fastboot boot image.img should do the trick. I was able to load up TWRP using this method.
Sent from my Pixel 3 XL using Tapatalk
Hi, so I flashed TWRP recovery and booted into it immediately. However, I forgot to flash the lazyflasher zip and rebooted straight away. Now the device is stuck at the logo and I can't seem to get to fastboot or recovery mode using the command line. I read a few other threads similar to my issue but apparently, they could access fastboot mode and I can't. Am I missing something?
ProBlast said:
Hi, so I flashed TWRP recovery and booted into it immediately. However, I forgot to flash the lazyflasher zip and rebooted straight away. Now the device is stuck at the logo and I can't seem to get to fastboot or recovery mode using the command line. I read a few other threads similar to my issue but apparently, they could access fastboot mode and I can't. Am I missing something?
Click to expand...
Click to collapse
Have you tried pressing Volume plus + power button to boot into recovery or Volume minus + power button to boot into fastboot mode?
Solution
It also happened to me but I booted into twrp and flashed an custom rom and also the lazy flasher.zip after couple of minutes it booted up. It may help you
Hello, My phone (Col L29) is currently softbricked and I can only access fastboot and ERecovery, TWRP when flashed won't boot when using the right process to boot and ERecovery cant download the firmware, I've tried flashing various parts of the stock update firmware to no success, if anyone can help that'd be really good!
Thanks
Andrew
Could you confirm what have you done before leading to this condition? May be can help
shashank1320 said:
Could you confirm what have you done before leading to this condition? May be can help
Click to expand...
Click to collapse
before it was bricked I was going through the process to install a new OS, i was using twrp bekerly (view 10) and it froze on the splash screen, so after a few minutes i held the power button and after that i couldn't access the recovery whatso ever.
I've tried ERecovery via wifi and OTG (not sure if i set up the folder correctly for otg of if otg just doesn't work), flashing stock recovery, flashing as many things as i could from the UPDATE.APP (do note that i couldnt flash ramdisk as that command was "not allowed" as with many other partitions), i have also tried wiping then flashing (be that through ERecovery or Fastboot).
When I try to access Recovery (rebooting after flashing, removing USB cable and holding Vol +), it goes to the Device is not trusted screen and then to ERecovery if i don't let go of the vol button.
I've softbricked my Moto G4 before but man, this is a ***** in comparison.
Try to flash the correct twrp via fastboot and should be fine. You may have incorrectly flashed the erecovery to the regular ramdisk_recovery(probably) which may lead to only erecovery and fastboot.
Erecovery doesn't work in most of the cases for many(though i have success rate of over 90%).
Also, flashing cust.img, version.img and vendor.img helps sometime.
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.