Started boot loop after instilling xposed - Verizon Galaxy Note 4 Q&A, Help & Troubleshooting

I was trying to instill xposed so I could fix my sd card for twrp. I'm running the stock rom 5.1. Now I'm at a lose the phone won't stop boot loading. I can't put anything on the sd card cause twrp won't see it. If I go into recovery and hook it to the computer. The computer won't see the phone? I thought about just reloading the rom through obin, but will I brick the phone in the process? I have already rooted and unlocked the bootload. Pleaae help thank you

goodboyz358 said:
I was trying to instill xposed so I could fix my sd card for twrp. I'm running the stock rom 5.1. Now I'm at a lose the phone won't stop boot loading. I can't put anything on the sd card cause twrp won't see it. If I go into recovery and hook it to the computer. The computer won't see the phone? I thought about just reloading the rom through obin, but will I brick the phone in the process? I have already rooted and unlocked the bootload. Pleaae help thank you
Click to expand...
Click to collapse
I'd boot into recovery and wipe all applicable (Dalvik,Art Cache, system, data , cache, and storage) twice to rule out any further corruption then reboot into DL mode and Odin back to stock . if u have no way to push a zip to the phone I don't see what other option you have and no you won't brick with Odin as long as your flashing stock Samsung firmware

Related

[Q] Soft Bricked....can't unbrick or revert to stock rom...any thoughts?

I got a replacement GS3 through insurance and rooted it yesterday. Instead of flashing CWM I tried going with TWRP this time but didn't realize that TWRP doesn't read external SD cards and my roms were all saved on the external SD. And of course, this was after I wiped everything. So I tried unrooting and flashing back the stock firmware but it keeps failing in ODIN. So I tried re-rooting and flashing CWM which works but none of the roms will flash. I keep getting a system 7 error or something to that effect when I try flashing any rom. So now I can either get to recovery mode, or download mode. If I power the phone on it gets stuck on the Galaxy S3 screen. Any thoughts as to processes to try? Links? Threads? I've tried just about everything I could find.
kinjo1023 said:
I got a replacement GS3 through insurance and rooted it yesterday. Instead of flashing CWM I tried going with TWRP this time but didn't realize that TWRP doesn't read external SD cards and my roms were all saved on the external SD. And of course, this was after I wiped everything. So I tried unrooting and flashing back the stock firmware but it keeps failing in ODIN. So I tried re-rooting and flashing CWM which works but none of the roms will flash. I keep getting a system 7 error or something to that effect when I try flashing any rom. So now I can either get to recovery mode, or download mode. If I power the phone on it gets stuck on the Galaxy S3 screen. Any thoughts as to processes to try? Links? Threads? I've tried just about everything I could find.
Click to expand...
Click to collapse
Since when does TWRP not read external SD cards? It see's mine just fine, for well over a year. Where is your nandroid backup, you know the one you made before you did anything just incase it didn't go as planned? In any case you didn't give much information to help troubleshoot. 'I tried unrooting' - if you were going to flash a stock ROM there is no need to unroot anything as the stock firmware is just that, stock. How did it fail in ODIN? Did it say why it failed, what file were you trying to flash? More often than not the system 7 error is caused from an out of date recovery, normally i would tell you to start there but given the fact you admitted to just randomly attempting to flash things to the device you are going to want to start from stock. The second sticky thread in this sub-forum is where you should start reading, because based on your post you either need a refresher or never have read it to begin with.
dntesinfrno said:
Since when does TWRP not read external SD cards? It see's mine just fine, for well over a year. In any case you didn't give much information to help troubleshoot. 'I tried unrooting' - if you were going to flash a stock ROM there is no need to unroot anything as the stock firmware is just that, stock. How did if fail in ODIN? Did it say why it failed, what file were you trying to flash? More often than not the system 7 error is caused from an out of date recovery, normally i would tell you to start there but given the fact you admitted to just randomly attempting to flash things to device you are going to want to start from stock. http://forum.xda-developers.com/showthread.php?t=1725839
Click to expand...
Click to collapse
For whatever reason, TWRP wouldn't read my sd card. And when I said I tried unrooting - I just meant flashing back to the stock ROM. Odin fails when it gets to system write. It goes down a bunch of lines of code successfully but when it gets to system write, it fails every time. I've downloaded a few different stock ROM versions for AT&T and tried switching USB ports around my laptop. I've also tried a few different versions of ODIN but I'm not coming up with anything but a soft bricked phone still.
kinjo1023 said:
For whatever reason, TWRP wouldn't read my sd card. And when I said I tried unrooting - I just meant flashing back to the stock ROM. Odin fails when it gets to system write. It goes down a bunch of lines of code successfully but when it gets to system write, it fails every time. I've downloaded a few different stock ROM versions for AT&T and tried switching USB ports around my laptop. I've also tried a few different versions of ODIN but I'm not coming up with anything but a soft bricked phone still.
Click to expand...
Click to collapse
Did you have usb debugging enabled before you attempted to flash via ODIN? It sounds like it doesn't have permission to write to the /system partition. You can try doing a factory reset from recovery to get past the bootloader and make sure, or use Kies to flash to stock via this thread.
dntesinfrno said:
Did you have usb debugging enabled before you attempted to flash via ODIN? It sounds like it doesn't have permission to write to the /system partition. You can try doing a factory reset from recovery to get past the bootloader and make sure, or use Kies to flash to stock via this thread.
Click to expand...
Click to collapse
I could have swore I made sure to check before I started the process but I cant' check now because the phone won't boot. Can't flash back to stock. Can't flash any roms. I can get into download mode and recovery though. It's weird. I've reverted other phones back to stock plenty of times. It just keeps failing no matter what I do with this.
dntesinfrno said:
Did you have usb debugging enabled before you attempted to flash via ODIN? It sounds like it doesn't have permission to write to the /system partition. You can try doing a factory reset from recovery to get past the bootloader and make sure, or use Kies to flash to stock via this thread.
Click to expand...
Click to collapse
Here's another question for you, I've looked all over for the newest CWM in .tar format but everything comes in .img format. I can't use the .img in ODIN to flash to the phone and can't boot my phone to use the CWM app to flash. I suppose I could try TWRP again but when I flashed the first time - TWRP wouldn't read my EXT SD card.....
kinjo1023 said:
Here's another question for you, I've looked all over for the newest CWM in .tar format but everything comes in .img format. I can't use the .img in ODIN to flash to the phone and can't boot my phone to use the CWM app to flash. I suppose I could try TWRP again but when I flashed the first time - TWRP wouldn't read my EXT SD card.....
Click to expand...
Click to collapse
if you could wipe everything get on odin with 4.1.2 update reboot use cf root to root it (if you dont have root) after reboot download ROM Manager from Play Store install CWM recovery (easiest way to root) hope this works

[Q]I can get into TWRP, can't reflash 4.3, hangs @ ATT logo.$5 Paypal if you can fix!

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

[SOLVED] How do you enter recovery mode for TWRP ? (Bootloop)

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.

Stuck in Custom Recovery!

Hi. I was trying to install new rom. Haven't done this in years. My phone has been laying in the closed for a year. Wanted to try putting new rom on it and let my son play with it.
I am running CWM v. 6.0.3.4.
I know I was supposed to install the newest, but I forgot how and tried to install DarkCyanogenMod v. 9.00.
I did format system and factory reset the phone. And then tried the installation. Error every time.
Now it's stuck in bootloop.
Another thing. My computer only reads my internal storage as sd card. I don't even have a sd card in the phone.
Best regards, Bogi
BentCleanson said:
Hi. I was trying to install new rom. Haven't done this in years. My phone has been laying in the closed for a year. Wanted to try putting new rom on it and let my son play with it.
I am running CWM v. 6.0.3.4.
I know I was supposed to install the newest, but I forgot how and tried to install DarkCyanogenMod v. 9.00.
I did format system and factory reset the phone. And then tried the installation. Error every time.
Now it's stuck in bootloop.
Another thing. My computer only reads my internal storage as sd card. I don't even have a sd card in the phone.
Best regards, Bogi
Click to expand...
Click to collapse
I suggest to get the recovery and ancora.ops from here: http://forum.xda-developers.com/showthread.php?t=1446593
Follow this guide to flash the recovery with odin: http://forum.xda-developers.com/showthread.php?t=1467128
Boot into recovery, mount usb to your pc, copy this file http://forum.xda-developers.com/showpost.php?p=55445744&postcount=313 on your sdcard, flash it, reboot into recovery.
After that do a factory reset again, format system and flash rom & gapps.
regards
Odin does not recognize the phone. I'm still stuck in recovery. An old CWM.
BentCleanson said:
Odin does not recognize the phone. I'm still stuck in recovery. An old CWM.
Click to expand...
Click to collapse
here http://forum.xda-developers.com/showpost.php?p=55445744&postcount=313

[Q] S3 Gets stuck on ATT screen no root

I apologize in advance if this is in the wrong thread or section, I'm new to this and am kind of stuck on what to do next. If it is in the wrong section can you let me know where to post?
I'm not sure what the previous version my phone was on but in the recovery menu I see KOT49H.I747UCUFNE4 so I assume it was 4.4.2
Over the weekend I tried to update my stock I747 (no root) through menus using check for update and when it completed my phone would no longer boot.
It gets stuck on the ATT logo and when I try to wipe it in recovery mode it still gets stuck on the same screen.
I have also tried to use Kies but the devise does not show up under the emergency recovery option even though my phone can connect to the computer.
However I have no problems connecting to Odin in download mode.
So what would be the best option for me if I dont want to root my device? Can I use Odin or should I be using a different program?
If I have to root should I follow enewman17 tutorial? If so what step should I start at?
Thanks!
Are you running a stock recovery? Did you wipe everything in recovery?
yep stock recovery, tried to wipe everything but i get the same problem.
If I were in your situation, I would install a custom recovery and custom rom such as cm10.2 to get the phone up and running to verify the bootloader and modem currently on the phone.
Should I be installing the recovery through odin or an sd card? Do you have a link for a tutorial, I've looked through t3chn0s1s's sticky but most instructions seem like they are for phones that can boot.
The method I see using an sd card needs a terminal but i don't think i can get one because I can't boot my phone, is that correct?
Download the latest tar.md5 file from here: https://goo.im/devs/philz_touch/CWM_Advanced_Edition/d2lte/
Copy the latest CM10.2 or CM11 to your SD card. Place the SD card in the phone.
Flash Philz in the PDA section of Odin 3.07 and don't check anything except F.Reset Time. When you see "Reset" in the status window, disconnet the USB cable, pull the battery, replace the battery, boot into recovery, wipe cache, data, Dalvik, system, flash CM from the SD card, and reboot.
Thanks got it working last night!
If you want to run the latest CM11 or AOSP ROMs, you may have to update to the latest bootoader and modem.

Categories

Resources