Related
Hey guys hope someone can help me out here. I just updated my phone to the latest OTA Rooted ROM and everything was working fine. Then I used Rom Manager to download the latest Fresh 3.0.?? ROM. When it downloaded it asked if I wanted to backup ROM and wipe data. I checked both on. Then phone rebooted and it wont get past white HTC Evo4G screen. I did vol down and power and I go to Recovey and again it freezes on this screen. I cant access my sd card to put any recovery stuff on the phone. How do I get past this?? This sucks
rgvsdigitalpimp said:
Hey guys hope someone can help me out here. I just updated my phone to the latest OTA Rooted ROM and everything was working fine. Then I used Rom Manager to download the latest Fresh 3.0.?? ROM. When it downloaded it asked if I wanted to backup ROM and wipe data. I checked both on. Then phone rebooted and it wont get past white HTC Evo4G screen. I did vol down and power and I go to Recovey and again it freezes on this screen. I cant access my sd card to put any recovery stuff on the phone. How do I get past this?? This sucks
Click to expand...
Click to collapse
I had the same issue this morning loading the new Fresh Rom. "Stuck at White HTC EVO" screen. Just do a battery pull to restart your phone and let it boot up normally. It should be able to load after that.
Thanks a lot fuzion. I could have sworn I tried that last night but I guess I didn't. So I guess no Fresh ROM ?? Anyway to get it on ?
You could try loading one of the PC36IMG zips on your sd using an adapter to go back to stock and start over
Well I got my phone back on and working with the 2.2 OTA rooted back the way it was. I go into ROM manager and I made sure to do the ClockworkMod Recovery install. When I turn on the phone with vol down + power I select Recovery it just freezes on the Evo 4g screen. Never takes me to the recovery menu like I used to have. Anyone have any idea why??
Let's do a checklist:
1. Full root including NAND unlock (i.e. NOT Unrevoked)?
2. Installed and re-installed latest ROM Manager, and then latest CWM?
3. Copied Fresh 3.1.0.1 to root of SD card?
4. Booted into recovery using either CWM option or power+volume up?
5. You don't have an old PC36IMG.zip on your SD card, do you?
6. If you can get into recovery, do all your flashing from there, and DON'T FORGET to do data, cache, and dalvik wipes.
7. If all else fails, maybe use CWM to flash Amon RA instead and try that way.
8. If all THAT fails, go back to toast's guides and re-root everything.
Other long shots: Install Titanium Backup and use that to install BusyBox. I have no idea if this would help, maybe it's totally unrelated. Also, you could use an app called Quick Boot to reboot into recovery, but if selecting the reboot option from CWM doesn't work, I don't know why QB would.
And one more thing: Don't be throwing the term "bricked" around when you're clearly not even close to bricked.
Hello all,
I flashed and rooted my SGIII about 6 months back using these threads
http://forum.xda-developers.com/showthread.php?t=2387423
http://forum.xda-developers.com/showpost.php?p=47747640&postcount=1
Everything was running fine until Saturday, I noticed my phone kept shutting off in my pocket. Once i got home and started doing diagnostics, i couldn't really tell what caused it, i uninstalled the realtor.com app i had downloaded Saturday during the day just in case and wiped the cache of a bunch of apps I had before the problem started. The problem still exists, the phone will randomly flicker 3 or 4 times, the shutdown menu shows up then goes away, then it turns off and i have to boot it back up manually.
Anyone else had this issue?
It seems as though these threads come pretty frequently here lately, I am going to suggest a power button, it is a fairly common failure. On a good working phone if you push and hold the power button for 10 seconds it will turn the phone off, but not before popping up the power/reset menu.
Good luck hope you get it fixed quickly and perhaps I'm wrong?
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
Starting to think this is hardware related, i did a complete factory reset and same issue occurred. Now I have to take it back to stock and see if I have a case for a replacement.
Since i updated and rooted as I did, am I screwed?
now it seems to be soft bricked.. this is fun
Did you ever install the 4.3 OTA update on your phone? If not, you should be able to flash back to rooted stock, install and run Triangle away, flash back to non-rooted stock, and you should be fine.
audit13 said:
Did you ever install the 4.3 OTA update on your phone? If not, you should be able to flash back to rooted stock, install and run Triangle away, flash back to non-rooted stock, and you should be fine.
Click to expand...
Click to collapse
Yea I did, I'm currently searching how to do this process post-4.3 update
update: so i can get into TWRP just fine, cannot reflash 4.3 update, getting an error no MD5 file found, and "assert failed: apply_patch_check ("system/app/Bo.. it cuts off from there.. then says E:Error executing updater binary in zip
if i reboot it just hangs at the ATT logo
what I have done so far was backed up before this brick started, then factory reset, data and all cache, since the factory reset I haven't gotten past the ATT logo.
Not going to sleep tonight until this is solved, I know someone can help me since I can still get into TWRP
Was thinking of trying to ODIN back to 4.1.1 then flash 4.2 then flash 4.3 but I am pretty sure that will hard brick it right?
$5 paypal to whoever fixes this for me!
wellppp think i bricked it
serstylz2 said:
wellppp think i bricked it
Click to expand...
Click to collapse
I had similar issue before.
Here is what I did to recover
1. Make sure you are using TWRP 2.6.3.1 (I used 2.6.3.0 tried the steps below, the device was stuck at AT&T logo, I thought you have the same version?)
(TWRP 2.6.3.1 is available here http://techerrata.com/file/twrp2/d2att/openrecovery-twrp-2.6.3.1-d2att.tar, you can flash it with ODIN v3.07)
2. Download a "almost official stock rom" from http://forum.xda-developers.com/showpost.php?p=47816011&postcount=18
3. Put the rom in SD card.
4. Boot into TWRP recovery.
5. Wipe->Format Data->Yes
6. Wide->Swipe to Factory Reset
7. Wide->Advanced Wipe->Check Dalvik Cache and Cache->Swipe to Wipe
8. Install->external_sd->AT&T_I747UCEMJB.zip
9. Reboot and done.
JEdad26 said:
I had similar issue before.
Here is what I did to recover
1. Make sure you are using TWRP 2.6.3.1 (I used 2.6.3.0 tried the steps below, the device was stuck at AT&T logo, I thought you have the same version?)
(TWRP 2.6.3.1 is available here http://techerrata.com/file/twrp2/d2att/openrecovery-twrp-2.6.3.1-d2att.tar, you can flash it with ODIN v3.07)
2. Download a "almost official stock rom" from http://forum.xda-developers.com/showpost.php?p=47816011&postcount=18
3. Put the rom in SD card.
4. Boot into TWRP recovery.
5. Wipe->Format Data->Yes
6. Wide->Swipe to Factory Reset
7. Wide->Advanced Wipe->Check Dalvik Cache and Cache->Swipe to Wipe
8. Install->external_sd->AT&T_I747UCEMJB.zip
9. Reboot and done.
Click to expand...
Click to collapse
Wish I saw this earlier, probably would have worked. It doesn't even turn on anymore. Thank you for the help though. Just going to put in a claim and say I ran it over with my car or something
serstylz2 said:
Wish I saw this earlier, probably would have worked. It doesn't even turn on anymore. Thank you for the help though. Just going to put in a claim and say I ran it over with my car or something
Click to expand...
Click to collapse
Did you brick it because you downgraded from 4.3 to 4.1.1? you might still have chance to unbrick it although I've never tried it.
Here is the thread. http://forum.xda-developers.com/showthread.php?t=2549068
JEdad26 said:
Did you brick it because you downgraded from 4.3 to 4.1.1? you might still have chance to unbrick it although I've never tried it.
Here is the thread. http://forum.xda-developers.com/showthread.php?t=2549068
Click to expand...
Click to collapse
Also would have probably worked if I had any life at all from this thing. I think this was destined to break, I believe hardware failed.
It broke when I tried flashing d2att_I747UCUEMJ2_bootloader_modem after flashing boot_CWM_I747UCUEMJB
UPDATE: Able to get back into Download mode, TWRP and it still hangs at the ATT logo. Was able to do that by sticking a debrick dump img on my sd card and doing that method. Now I am trying to fully follow thru with that thread (http://forum.xda-developers.com/showthread.php?t=2549068) but I still have never seen a stock 4.3 that i can flash via ODIN, i asked them where I can find that. I may try these directions in the meantime (Also, I tried to update to TWRP 2.6.3.1 and ODIN froze on the checking .md5 step so, maybe that's the issue to begin with?)
1. Make sure you are using TWRP 2.6.3.1 (I used 2.6.3.0 tried the steps below, the device was stuck at AT&T logo, I thought you have the same version?)
(TWRP 2.6.3.1 is available here http://techerrata.com/file/twrp2/d2a....3.1-d2att.tar, you can flash it with ODIN v3.07)
2. Download a "almost official stock rom" from http://forum.xda-developers.com/show...1&postcount=18
3. Put the rom in SD card.
4. Boot into TWRP recovery.
5. Wipe->Format Data->Yes
6. Wide->Swipe to Factory Reset
7. Wide->Advanced Wipe->Check Dalvik Cache and Cache->Swipe to Wipe
8. Install->external_sd->AT&T_I747UCEMJB.zip
9. Reboot and done.
Welp I'm finally back up.. here's what I had to do
First, had to get a debrick img from http://forum.xda-developers.com/showthread.php?t=2549068&page=3
Then carried out these steps
First:
I used "Win32DiskImage" Located here But you can also use dd to write the image to your sd card in Linux.
On Windows:
Open Win32DiskImage. Brows to the Debrick dump you have for your device. Select the drive letter if your micro sd in the drop-down, click write. Bam done.
On Linux:
For ease of example, and method. Open Gparted on your Linux install or live cd, check the dev your sd card is in the drop down menu. For example mine was /dev/sdb/ then use "dd if=/path/to/debrick/dump.img of=/dev/sdb/" This method also works. Be careful you are selecting the right dev or you will overwrite another disk on your system. YOU HAVE BEEN WARNED.
Second:
Put that SD card in your device insert the battery and if the SD card is written correctly with a proper debrick file. You can put a jig in the device and it will boot straight to download mode. If you dont have a jig hold Vol Down + Home + Power the device will boot to download. If it does not, either the image didn't write to the card properly ( I had to write it a few times with Win32DiskImager, DD worked fine the first try), the debrick dump is no good. Or your trying to debrink your 4.3 bootloader downgrade brick with a dump from 4.1.2 compatible bootloaders. this will not work the blown efuse will still prevent the bootloader from booting from the SD card as well as the EMMC. You will know pretty fast if it worked, as the device will vibe with the jig or it will vibe with the button combo almost immediately after being pressed and held.
booted to Recovery, then basically whipped through these steps
"You will need to copy all of the files you are going to flash (you can download them below) onto your 1GB or larger SD card. You then Need Put your Debrick SD card in the Phone, Remove and reinstall the battery,Put the Phone in Recovery Mode (Must Be Either TWRP or CWM Instructions and TWRP Download Below), Dismount the Debrick SD card, Insert your SD card with your Bootloaders, ROM, kernel, and Modem into the Phone, Mount the SD card, Flash your files one at a time, wipe the cache and dalvik between each file, Once you are done reboot the system, You Might have to put the debrick SD back in and do another battery pull, boot up the phone, after you get in the phone reboot it without the Debrick SD card in. If it will not Boot on its own see the link below."
My original problem came when i removed the debrick SD and inserted the file SD, i wasn't mounting so i was confused for a min. Then the ROM i was trying to flash was the "update43" from the OTA 4.3 update thread, that does not work, ended up using the "almost Stock" from here http://forum.xda-developers.com/showpost.php?p=47816011&postcount=18
And I was good after that. Basically I just went a long way to do what the tuts had already said to do, and the screen flickering is also gone along with the random reboots i was getting.
Very thankful for this forum and you all
Hello everyone. I was attempting to install the Liquid Smooth 3.0 Beta ROM but it said failed in red words. So i wiped again and installed my backup. Its been stuck in boot loop. I've looked and can't seem to find how to enter recovery mode. I tried holding power + volume up + home and it just restarts the phone before it gets to the boot loop screen. Also, once I get in recovery mode, what would be the next step to fix the boot loop? Right now im reinstalling the ROM I had on backup (intergalactic) . Or should I wipe and re-install the backup?
Thanks
EDIT: Found the combo ( Volume up + home ). Now restoring my backup. If this doesn't fix the bootloop what should I do? Also when I mount my USB in recovery it doesn't show up on my computer.
TrippyAzN said:
Hello everyone. I was attempting to install the Liquid Smooth 3.0 Beta ROM but it said failed in red words. So i wiped again and installed my backup. Its been stuck in boot loop. I've looked and can't seem to find how to enter recovery mode. I tried holding power + volume up + home and it just restarts the phone before it gets to the boot loop screen. Also, once I get in recovery mode, what would be the next step to fix the boot loop? Right now im reinstalling the ROM I had on backup (intergalactic) . Or should I wipe and re-install the backup?
Thanks
EDIT: Found the combo ( Volume up + home ). Now restoring my backup. If this doesn't fix the bootloop what should I do? Also when I mount my USB in recovery it doesn't show up on my computer.
Click to expand...
Click to collapse
If you get to recovery mode, try doing a hard wipe/reset to return your phone to its original settings. You will lose all saved data so please keep your backup. Your phone may not be recognized by the computer in recovery mode but in download mode. Are you using custom recovery or stock recovery? If custom, which one?
Larry2999 said:
If you get to recovery mode, try doing a hard wipe/reset to return your phone to its original settings. You will lose all saved data so please keep your backup. Your phone may not be recognized by the computer in recovery mode but in download mode. Are you using custom recovery or stock recovery? If custom, which one?
Click to expand...
Click to collapse
Hello. How do I Hard Reset? I am using TWRP recovery mode. I've tried download mode and still not recognized. I also downloaded the latest driver.
TrippyAzN said:
Hello. How do I Hard Reset? I am using TWRP recovery mode. I've tried download mode and still not recognized. I also downloaded the latest driver.
Click to expand...
Click to collapse
Good! With TWRP, you will see the wipe option on the home screen immediately you get into recovery mode. Just do the standard wipe and then reboot to system.
Larry2999 said:
Good! With TWRP, you will see the wipe option on the home screen immediately you get into recovery mode. Just do the standard wipe and then reboot to system.
Click to expand...
Click to collapse
Just did that, still at the boot screen
TrippyAzN said:
Just did that, still at the boot screen
Click to expand...
Click to collapse
Sometimes, it may take several minutes after the reset for your phone to finally boot up so you may have to wait a bit before deciding it didn't work. However, do you recall what (stock) Android version you had before you attempted to flash the custom ROM?
Larry2999 said:
Do you recall what (stock) Android version you had before you attempted to flash the custom ROM?
Click to expand...
Click to collapse
Before I rooted? I was Jelly Bean 4.1.2 I think. But I flashed many Custom ROMs, the last one was 4.3 . The one I was installing was 4.4.2. But I dont think thats the problem, It just said failed to flash. And the back up restore was successful, just a boot loop. If I could get my computer to recognize my phone I could put my original ROM download in and flash that.
TrippyAzN said:
Before I rooted? I was Jelly Bean 4.1.2 I think. But I flashed many Custom ROMs, the last one was 4.3 . The one I was installing was 4.4.2. But I dont think thats the problem, It just said failed to flash. And the back up restore was successful, just a boot loop. If I could get my computer to recognize my phone I could put my original ROM download in and flash that.
Click to expand...
Click to collapse
Normally, if it was just a case of your phone getting stuck in a boot loop, a hard wipe/reset will fix that. If it's still not coming on, then it could be a slightly more severe case of firmware failure which, thankfully, can be easily recovered from since you can get into download and recovery modes. Your best option now would be to flash an official (stock) ROM to get your phone back in working order. From what you've said about the firmware history, stock Android 4.3 would be your best bet as you probably have the 4.3 boot-loader already. You can download the zip file you will find in the discussion thread below and flash this via TWRP recovery. The process is fairly simple. Download the zip file to your PC - do not extract. Verify the MD5. Copy to a micro SDHC card. Place the card in your phone. Boot to recovery mode. Select install and navigate your way to the zip file you just copied. Swipe across the screen to confirm installation. Wait for installation to complete. Clear your cache/dalvik. Reboot your system. Good luck!
http://forum.xda-developers.com/showthread.php?t=2658486
Before flashing custom ROMs, it is always helpful to do a lot of research as there is no easier way to brick or backdoor your phone.
NB
You need a special app to verify MD5. It's just a check to ensure you have the correct file and it downloaded correctly. If you do not have the app, check that the zip you have is about 933MB after download.
Larry2999 said:
Normally, if it was just a case of your phone getting stuck in a boot loop, a hard wipe/reset will fix that. If it's still not coming on, then it could be a slightly more severe case of firmware failure which, thankfully, can be easily recovered from since you can get into download and recovery modes. Your best option now would be to flash an official (stock) ROM to get your phone back in working order. From what you've said about the firmware history, stock Android 4.3 would be your best bet as you probably have the 4.3 boot-loader already. You can download the zip file you will find in the discussion thread below and flash this via TWRP recovery. The process is fairly simple. Download the zip file to your PC - do not extract. Verify the MD5. Copy to a micro SDHC card. Place the card in your phone. Boot to recovery mode. Select install and navigate your way to the zip file you just copied. Swipe across the screen to confirm installation. Wait for installation to complete. Clear your cache/dalvik. Reboot your system. Good luck!
http://forum.xda-developers.com/showthread.php?t=2658486
Before flashing custom ROMs, it is always helpful to do a lot of research as there is no easier way to brick or backdoor your phone.
NB
You need a special app to verify MD5. It's just a check to ensure you have the correct file and it downloaded correctly. If you do not have the app, check that the zip you have is about 933MB after download.
Click to expand...
Click to collapse
Which do I download? First or second link? Also How should I get my computer to recognize my phone? And if I do that, flashing a fresh ROM wont fix the boot loop?
TrippyAzN said:
Which do I download? First or second link? Also How should I get my computer to recognize my phone? And if I do that, flashing a fresh ROM wont fix the boot loop?
Click to expand...
Click to collapse
You need the first one since you are on TWRP. You are not connecting your phone to the computer at all so there is no worry about that. You only need to download the image to your computer and then copy it to an external Micro SD card using another device like a camera, phone, SDHC card reader/writer or SDHC card adapter if your PC has the required slot. Once you have the recovery image saved on to the external SD card, insert the card into your phone and boot into recovery mode. You will then install the zip from the card. This ROM should not only fix the boot loop, it will restore your phone to as near factory settings as possible including resetting your flash counter, installing the complete stock system and stock recovery.
Once you have your phone back in working order, you can revert to flashing custom ROMs but please be very careful and do all the research you need. Specifically, you should avoid any ROMs that may attempt to mess with your boot-loader.
Larry2999 said:
You need the first one since you are on TWRP. You are not connecting your phone to the computer at all so there is no worry about that. You only need to download the image to your computer and then copy it to an external Micro SD card using another device like a camera, phone, SDHC card reader/writer or SDHC card adapter if your PC has the required slot. Once you have the recovery image saved on to the external SD card, insert the card into your phone and boot into recovery mode. You will then install the zip from the card. This ROM should not only fix the boot loop, it will restore your phone to as near factory settings as possible including resetting your flash counter, installing the complete stock system and stock recovery.
Once you have your phone back in working order, you can revert to flashing custom ROMs but please be very careful and do all the research you need. Specifically, you should avoid any ROMs that may attempt to mess with your boot-loader.
Click to expand...
Click to collapse
Thanks for your help! That was a great idea, moving my SD card to a different device then putting the .zip in there and flashing from my device. Worked Perfectly. Didn't even have to use the restore file you linked me, I just re-flashed the old ROM i was using ( brand new, not the back up ). And its starting up now, all of my apps, widgets, wallpapers, and messages are exactly how I left them. Which is weird because of how many times I wiped and the fact that I re-flashed a brand new ROM lol.
Man this makes me not want to change ROMs anymore. Small stuff like this makes me paranoid. I don't have a back up phone lol
TrippyAzN said:
Thanks for your help! That was a great idea, moving my SD card to a different device then putting the .zip in there and flashing from my device. Worked Perfectly. Didn't even have to use the restore file you linked me, I just re-flashed the old ROM i was using ( brand new, not the back up ). And its starting up now, all of my apps, widgets, wallpapers, and messages are exactly how I left them. Which is weird because of how many times I wiped and the fact that I re-flashed a brand new ROM lol.
Man this makes me not want to change ROMs anymore. Small stuff like this makes me paranoid. I don't have a back up phone lol
Click to expand...
Click to collapse
Glad to know your phone is now functioning normally. One of your earlier restore operations probably restored your data whilst the new ROM you flashed restored the system without deleting data. Thankfully, you didn't lose anything. Now the phone is back to normal, please be careful with flashing ROMs especially custom ones.
Hey guys,
New to the forum, if I need to post this elsewhere, please say so and I will!
So I have been successfully running cyanogenmod 11 for about 6mo now. Two days ago, my google account wouldnt sync anymore.
I read up on it and it was a corruption in a file and I needed to restore my cyanogenmod
Heres where I f'd up. I took the phone into TWRP, had my backup on my SD card so I wiped the rest of the phone. I accidentally did not uncheck the box for my SD card and wiped it too.
Now, I have no OS installed and im stuck in a boot loop.
I tried launching odin on my PC and reloading the factory firmware but it fails everytime. I took it to best buy and they couldnt fix it with their smart tool. And I cant send it back to samsung because it shows that Ive flashed it.
Any help would be greatly appreciated!
Thanks,
Josh
You can get into download mode? You tripped the knox counter on your phone?
Yes I can. And recovery as well. And yes, it's tripped
Personally, I would flash the latest version of Philz Touch in Odin, copy a custom ROM to your external SD card, boot into Philz recovery, wipe cache, wipe data, wipe Dalvik, flash the ROM, and reboot. This should at least get your phone up and running.
I consider myself decent at tech related stuff. However I have no idea what you just said. Link to a step by step or YouTube video?
The issue with Odin was that it failed seconds after I started the upload (last time) will that not be an issue here?
Odin probably failed because you were trying to downgrade the bootloader which is not allowed. Do you remember the error you got in Odin?
Download the latest tar.md5 file from here: https://goo.im/devs/philz_touch/CWM_Advanced_Edition/d2lte/
Download the latest CM10.2 and put it onto your external SD card. I know CM10.2 is but you need to get your phone working so you can determine the bootloader version on your phone. Place the SD card into the phone.
Launch Odin 3.07, make sure everything is unchecked except for F.reset time. Click on PDA, browse and select the tar.md5 file you downloaded, boot phone in download mode, connect phone to computer, flash recovery. When you see the word reset in the status window, disconnect the USB cable, pull the battery, boot into recovery mode, wipe cache, wipe data, wipe Dalvik, flash CM10.2, reboot.
Ok I'll give it a whirl tomorrow most likely. I'll keep you guys posted. Thanks for the help!
I was fooling around with my phone and decided to try to update to MM. I downloaded the update to my sd card and fastbooted into stock recovery. I selected apply update from sd card and then selected the update file. It stuck on verifying update package for about 40 minuets at which time I was thoroughly pissed and pulled the battery. It booted into twrp when I restarted it. I selected one of my backups which twrp said was installed successfully. When I reboot it comes right back to twrp every time. what can I do to fix this.
Edit: Twrp is permanently installed on my phone, the use of stock recovery was a one time deal.
My Phone: ZE551KL-ZOOTD
Rooted: Yes
Bootloader unlocked: Yes
You stopped it mid-install... 40 minutes is not a long time. Rule number one of updating firmware, ALWAYS let it finish.
You've corrupted the system and probably boot. You'll need to download and reflash system through ADB.
willcall said:
I was fooling around with my phone and decided to try to update to MM. I downloaded the update to my sd card and fastbooted into stock recovery. I selected apply update from sd card and then selected the update file. It stuck on verifying update package for about 40 minuets at which time I was thoroughly pissed and pulled the battery. It booted into twrp when I restarted it. I selected one of my backups which twrp said was installed successfully. When I reboot it comes right back to twrp every time. what can I do to fix this.
My Phone: ZE551KL-ZOOTD
Rooted: Yes
Bootloader unlocked: Yes
Click to expand...
Click to collapse
First you said you use stock recovery. And then you said it reboots into TWRP. Which one is it?
Sent from my ASUS_Z00AD using Tapatalk
kenbo111 said:
First you said you use stock recovery. And then you said it reboots into TWRP. Which one is it?
Sent from my ASUS_Z00AD using Tapatalk
Click to expand...
Click to collapse
Twrp is installed on my phone. I used fastboot to temporarily boot into stock recovery using the command "fastboot boot recovery.img" where the stock recovery is in my adb and fastboot folder. After I pulled the battery and restarted the phone it booted into twrp and that is where I am now
The problem has been solved. Apparently Twrp handles the factory reset differently than the stock recovery. I tried the factory reset in Twrp two or three times with no luck. I figured what the hell, before I wipe the everything and reinstall I would give stock recovery a try.
Fastbooted stock recovery, wiped the cache, did a factory reset, and when I rebooted my phone had been magically restored. I don't know how to delete this thread so if the moderators will, delete it. Thanks
hi i have a same problem . im stuck in my twrp . i already have a custom rom. but accidentally wipe my fone using restore factory data after that istuck on twrp.. i dnt have idea what should i do . i already put another custom rom but nothng happens still in twrp after rebooting.. btw im using asus zenfone 2 laser z00ld.. thank you plss help me
Fix for bootloop in twrp
Had the same issue earlier than i came to this simple trick(by experimenting).
Follow the steps:
1. Extract the boot.img from any rom zip file you have.
2. Move that boot.img to memory card and plug that memory card to the phone having reboot problem.
3. Now boot in twrp and click install--> image--> and locate the boot.img file in memory card.
4. Finally select boot option in twrp install screen, and finally slide to install.
Hope it will fix ur problem. Cant post the link. I am new to xda so.