hello all,
I'm having trouble understanding something with my SIII. I have a Canadian Rogers SIII currently running DJJOHNNYBLAZE's rom.
great rom, no problems at all!
But when I try to, I haven't been able to install any CM, AOKP or AOSP rom on my phone through TWRP or CWM recovery... only the stock based roms work when I install them..
is there something I'm missing? or doing rom? I'm quite familiar with the flashing process, I've done it a million times on my SIII and my previous Sony Xperia..
Any help, tips or direction to an answer is much appreciated
RoshanDoon said:
But when I try to, I haven't been able to install any CM, AOKP or AOSP rom on my phone through TWRP or CWM recovery... only the stock based roms work when I install them..
Click to expand...
Click to collapse
First question: what fails about the install process?
Second question: how did you install the recovery images?
Most of the time when I hear something like this on a Canadian S3, it's because of the different device code (d2can vs. d2att) of the Canadian model; the images you get through goomanager or ROM Manager or similar will see that you're trying to install a d2att ROM on a device it sees as a d2can, fails to get that the two are software-compatible, and aborts with a "status 7" error.
If that's the case, you can manually flash, say, the d2att TWRP image (look here for the image and instructions), which will happily flash d2att ROMs onto your device.
smelenchuk said:
First question: what fails about the install process?
Second question: how did you install the recovery images?
Most of the time when I hear something like this on a Canadian S3, it's because of the different device code (d2can vs. d2att) of the Canadian model; the images you get through goomanager or ROM Manager or similar will see that you're trying to install a d2att ROM on a device it sees as a d2can, fails to get that the two are software-compatible, and aborts with a "status 7" error.
If that's the case, you can manually flash, say, the d2att TWRP image (look here for the image and instructions), which will happily flash d2att ROMs onto your device.
Click to expand...
Click to collapse
thanks for the quick reply
to answer your first question: when i flash any of them, in recovery it just says "Failed" in red letters.. the funny part is I've installed a couple open source roms before and they worked (ie Liquid, Ktoonez AOKP rom), now i can't :S the ones i flashed were d2att, possibly my problem now, however, why did they work before?
to answer the second: i do a factory reset, wipe cache, flash rom, install gapps, wipe dalvik (as stated in most forums)
also, i've installed TWRP by installing GooManager on my phone and installing it from there, is that wrong? is it different than manually doing it with the command?
thanks again
RoshanDoon said:
i've installed TWRP by installing GooManager on my phone and installing it from there, is that wrong? is it different than manually doing it with the command?
Click to expand...
Click to collapse
Yes - that means you have the d2can TWRP image and not the d2att recovery image, which causes the problem I described. You will probably want to manually install the d2att image in its place.
smelenchuk said:
Yes - that means you have the d2can TWRP image and not the d2att recovery image, which causes the problem I described. You will probably want to manually install the d2att image in its place.
Click to expand...
Click to collapse
ahhhh... gracias!
will do that now then, thanks
I'm having a similar problem.
I've rooted my s3 i747m (virgin), and I have backed up using TWRP.
Attempting to install Cyanogen mod from a .zip on internal sdcard. In recovery mode I've gone in and tried to install from the zip, but I'm getting status 7. Any ideas?
ultrashaun said:
I've rooted my s3 i747m (virgin), and I have backed up using TWRP.
Attempting to install Cyanogen mod from a .zip on internal sdcard. In recovery mode I've gone in and tried to install from the zip, but I'm getting status 7. Any ideas?
Click to expand...
Click to collapse
Exactly the same problem, exactly the same cause; read the earlier posts in this thread for an idea of what to do.
smelenchuk said:
Exactly the same problem, exactly the same cause; read the earlier posts in this thread for an idea of what to do.
Click to expand...
Click to collapse
Again! You've done it sir. This worked exactly right. Thank you so much.
Related
Hi, so I'm trying to make this quick so that i can install CM10 tonight...
so I rooted my phone tonight, did everything right and stuff, but I went to go download the CM10 nightly build for my phone which is the Rogers (Canadian version). So I download the d2att version, did a backup, wiped everything and I tried installing it using CWM-Based recovery v5.5.0.4. But when I tried install it gave me status 7 aborted. I installed cwm using odin3 v1.85, what am I doing wrong, am I trying to install the wrong version? Sorry if this is a noob question but I'm new to this stuff :/
thanks for any help
Can anyone explain to me how I can update CWM? I downloaded the latest img from their website, but idk how to install it...I'm really confused...and I really need help :crying:
Go look at QBKing77 videos on YouTube or QBKing77.com he has the best videos in my opinion and installing CM10 and CWM. I am on CM10.1 without any problems.
hmm, did you use the v5 recovery? Did it work, because the version i had was cwm 5.5 and I couldn't update because of system 7 error, which is because the CWM version was too old.
If possible, could you link me the one you used?
Ok..so now I installed TWRP and I tried flashing CM10 it still didnt work and gave me status 7 error and it says:
assert failed: getpro ("ro.product.device")
E: Error in /sdcard/cm- 10.....d2att.zip
Is this because with goomanager i installed it for the d2can version and now I can't install the d2att even though thats the only version i can use? goomanager only lets me get d2can...and when I try to install the never cwm recover img using android terminal it keeps giving me No such file or directory.
Can anybody help me with this...
PhoenixBlitz said:
Ok..so now I installed TWRP and I tried flashing CM10 it still didnt work and gave me status 7 error and it says:
assert failed: getpro ("ro.product.device")
E: Error in /sdcard/cm- 10.....d2att.zip
Is this because with goomanager i installed it for the d2can version and now I can't install the d2att even though thats the only version i can use? goomanager only lets me get d2can...and when I try to install the never cwm recover img using android terminal it keeps giving me No such file or directory.
Can anybody help me with this...
Click to expand...
Click to collapse
have you tried flashing another ROM, like an-aosp or aokp-based one? If you followed their instructions, it may help you determine whether it was a bad download or something s more specific to your device. just throwing this one out there....
captican said:
have you tried flashing another ROM, like an-aosp or aokp-based one? If you followed their instructions, it may help you determine whether it was a bad download or something s more specific to your device. just throwing this one out there....
Click to expand...
Click to collapse
oh...hahaha
I just flashed AOKP and everything worked great! Thanks for that little suggestion! Custom ROMs are now my favorite!
PhoenixBlitz said:
oh...hahaha
I just flashed AOKP and everything worked great! Thanks for that little suggestion! Custom ROMs are now my favorite!
Click to expand...
Click to collapse
If you want to flash a CM ROM you will need to be on the most current d2att recovery for either CWR or TWRP. If you were getting a status 7 error, I'm going to assume that you have a d2can phone.. make sure you have a d2att recovery and you'll be able to flash anything. ROM Manager will let you install CWR or Goo Manager will let you install TWRP (which is what I use).
BAM1789 said:
If you want to flash a CM ROM you will need to be on the most current d2att recovery for either CWR or TWRP. If you were getting a status 7 error, I'm going to assume that you have a d2can phone.. make sure you have a d2att recovery and you'll be able to flash anything. ROM Manager will let you install CWR or Goo Manager will let you install TWRP (which is what I use).
Click to expand...
Click to collapse
Yes, I highly recommend TWRP.
Sent from my SPH-D710 using xda premium
HeadBlader911 said:
Yes, I highly recommend TWRP.
Sent from my SPH-D710 using xda premium
Click to expand...
Click to collapse
I tried using TWRP but when I installed it through GooManager it installed the d2can version so I couldn't install CM10. Unless there is a way to manually select which TWRP version to install through GooManager, then I'm more or less stuck on CWM.
edit: Just got TWRP for d2att installed so now I can flash whatever I want, man TWRP seems a lot better than CWM!
I know this has been asked hundreds of times, and i searched the forums for days for a way to fix it, but with no use.
I have a rooted AT&T Galaxy SIII with JB 4.1.1. I am trying to install the CM 10.1(4.2.2) Nightly version, but i always get the infamous "Status 7 Installation Aborted" error.
Yes i am sure im downloading the correct ROM zip file for my phone and carrier.
I have CWM 6.0.2.1, and i followed the steps correctly. (Clear data -> Clear Cache Partition -> Clear Dalvik Cache -> install ROM)
I have tried so many times, i also re-rooted my phone, reinstalled CWM, and redownloaded different nightly versions of the ROM, as well as other ROMS like JellyBam.
I also tried to delete the assert lines in the update-script file, but that also wouldnt work.
Thank you. :good:
And please dont hate on me, im new to rooting and flashing. :crying:
Improper recovery.
samelaryan said:
I know this has been asked hundreds of times, and i searched the forums for days for a way to fix it, but with no use.
I have a rooted AT&T Galaxy SIII with JB 4.1.1. I am trying to install the CM 10.1(4.2.2) Nightly version, but i always get the infamous "Status 7 Installation Aborted" error.
Yes i am sure im downloading the correct ROM zip file for my phone and carrier.
I have CWM 6.0.2.1, and i followed the steps correctly. (Clear data -> Clear Cache Partition -> Clear Dalvik Cache -> install ROM)
I have tried so many times, i also re-rooted my phone, reinstalled CWM, and redownloaded different nightly versions of the ROM, as well as other ROMS like JellyBam.
I also tried to delete the assert lines in the update-script file, but that also wouldnt work.
Thank you. :good:
And please dont hate on me, im new to rooting and flashing. :crying:
Click to expand...
Click to collapse
BAM1789 said:
Improper recovery.
Click to expand...
Click to collapse
if you can boot into the phone, download ROM manager and update your cwm recovery. latest version is 6.0.2.8.
CM10 and 10.1 are picky about you having the most recent version. cheers
xBeerdroiDx said:
if you can boot into the phone, download ROM manager and update your cwm recovery. latest version is 6.0.2.8.
CM10 and 10.1 are picky about you having the most recent version. cheers
Click to expand...
Click to collapse
I did that and it worked thank you :good:
samelaryan said:
I did that and it worked thank you :good:
Click to expand...
Click to collapse
thats what we're all here for, buddy
Status 7: installation aborted.
xBeerdroiDx said:
thats what we're all here for, buddy
Click to expand...
Click to collapse
Hi guys, I'm having same issue but on N7000 international version. I'm able to go in the recovery mode and download mode but phone won't boot normally. It's stuck on Samsung logo so can you please advise something? How can I update CWM if that's the issue. I was on ICS 4.0.4 XXLRK before trying to install CM10.1 on Note.
Thanks in advance for your help.
perceptorz said:
Hi guys, I'm having same issue but on N7000 international version. I'm able to go in the recovery mode and download mode but phone won't boot normally. It's stuck on Samsung logo so can you please advise something? How can I update CWM if that's the issue. I was on ICS 4.0.4 XXLRK before trying to install CM10.1 on Note.
Thanks in advance for your help.
Click to expand...
Click to collapse
I would be doing my research in an N7000 forum, friend.
Also, your post seems confusing as you seem to be saying you also got a status 7 error but then you appear to have installed abroad and are stuck at the boot logo. If you successfully flashed the correct rom for your device without any errors, pull battery, replace and wipe data in recovery. Reboot
xBeerdroiDx said:
I would be doing my research in an N7000 forum, friend.
Also, your post seems confusing as you seem to be saying you also got a status 7 error but then you appear to have installed abroad and are stuck at the boot logo. If you successfully flashed the correct rom for your device without any errors, pull battery, replace and wipe data in recovery. Reboot
Click to expand...
Click to collapse
Apologies for both confusion and using the S3 that to find some help. I just found the situation quite familiar so I couldn't help myself from asking the question
On the situation, I was able to install CWM and am able to go to recovery or download mode but the error displays when I try to update the zip of any rom.
perceptorz said:
Apologies for both confusion and using the S3 that to find some help. I just found the situation quite familiar so I couldn't help myself from asking the question
On the situation, I was able to install CWM and am able to go to recovery or download mode but the error displays when I try to update the zip of any rom.
Click to expand...
Click to collapse
If the phone itself is functioning fine but you simply cannot flash a new rom or rom update, you need to update your recovery. Go to clockworkmods website and download version 6.0.1.2.
xBeerdroiDx said:
If the phone itself is functioning fine but you simply cannot flash a new rom or rom update, you need to update your recovery. Go to clockworkmods website and download version 6.0.1.2.
Click to expand...
Click to collapse
Right now, phone doesn't get pass Samsung boot logo so will I be able to update new CWM using Odin? (Sorry, if the question appears to be basic or stupid)
perceptorz said:
Right now, phone doesn't get pass Samsung boot logo so will I be able to update new CWM using Odin? (Sorry, if the question appears to be basic or stupid)
Click to expand...
Click to collapse
I would take up this situation in the correct forum. The more we discuss your device issues the more likey you are to download the wrong file or use a procedure not designed for your device software.
If you came from stock, flashed a rom and are stuck at the samsung logo, boot into recovery, wipe data and cache. Reboot to see if that helped. If not, seek advice in the N7000 forum. Cheers
Thanks for the guidance.
I tried to flash omnirom today, and it gave an error that my phone isn't t0ltetmo, and is instead t03g. what's the deal? how do I fix this? thanks.
theoilman said:
I tried to flash omnirom today, and it gave an error that my phone isn't t0ltetmo, and is instead t03g. what's the deal? how do I fix this? thanks.
Click to expand...
Click to collapse
I have the SGH-T889, not the N7100, so I'm guessing this is because of an old ROM I flashed? I just flashed the phone back to stock with the latest stock image but it still registers as t03g, so there has to be something else I have to do.
If you get this error in recovery, it'd be because of a failed check in the OmniROM's install script.
I'll assume you've flashed a N7100 recovery instead of an N7105 one? That's certainly the first thing I'd check.
Good luck,
Darkshado
Darkshado said:
If you get this error in recovery, it'd be because of a failed check in the OmniROM's install script.
I'll assume you've flashed a N7100 recovery instead of an N7105 one? That's certainly the first thing I'd check.
Good luck,
Darkshado
Click to expand...
Click to collapse
I flashed T889UVBMD1 from teshxx's post in development (http://forum.xda-developers.com/showthread.php?t=2102380). is this the correct recovery? should I try a different recovery instead?
That'd be the stock recovery, which will do you little good when it comes to installing custom ROMs. Just get the latest t0lte or t0ltetmo TWRP or Clockworkmod Recovery.
Darkshado said:
That'd be the stock recovery, which will do you little good when it comes to installing custom ROMs. Just get the latest t0lte or t0ltetmo TWRP or Clockworkmod Recovery.
Click to expand...
Click to collapse
I'll try flashing a new recovery, thanks for the info!
[Q] Need help in solving "Unfortunately, settings have stopped working" error
Problem: My unrooted SGH-I747 model AT&T GS3 recently gave me this error whenever trying to access the settings. The error shows up even after a full factory reset and I can no longer access my phone. Stuck a little after the language selection in the beginning stages of the setup.
Attempted fixes: Obviously, the initial factory reset. Then clearing the cache + factory reset.
After those failed to work, I tried to flash to a AT&T stock rom from this forum (http://forum.xda-developers.com/showthread.php?p=33570269#post33570269) using Odin. I tried to use the first row of downloads but the first row but it did not have a MD5 file, so I used the second row of downloads instead but this rom failed to install. My guess is that it may be too old of a version.
I would appreciate any help.
[SOLVED]
The problem may have arose from a critical error in the phone's software that had affected the OS system of the phone. I resolved the issue by flashing a new custom OS (cyanogenmod) to my phone. These are the steps that I took:
1. Installing Odin (http://forum.xda-developers.com/showthread.php?t=1722686)
2. Rooting my cellphone with CFAutoRoot using Odin (http://forum.xda-developers.com/showthread.php?t=1725839)
3. Installing a custom recovery TWRP -- highly recommended very user friendly (http://forum.xda-developers.com/showthread.php?t=1793224)
4. Installing a new custom rom through TWRP-- used Cyanogen (http://forum.xda-developers.com/showthread.php?t=1778270)
5. Installing gapps (http://opengapps.org/?api=5.1&variant=nano)
6. Identifying the correct bootloader by downloading and installing Samsung Phone Info by vndnguyen through the Play Store.
7. Installing the correct bootloader and modem (http://forum.xda-developers.com/galaxy-s3-att/general/rooted-ucufnj1-stock-rom-t2985006)
Please refer to respective installation guides for more instructions regarding installation of any new software.
I hope this helps anyone who may have run into the same problem.
Before attempting to flash anything, confirm the bootloader on your phone. An easy way to determine if the bootloader is 4.3 or newer, boot into download mode. If you see anything about warranty bit, your phone has at least a 4.3 bootloader and no attempts should be made to flash anything from sammobile.com.
If you have a 4.3 or newer bootloader, I recommend flashing a custom recovery such as TWRP, and then flashing a stock ROM from recovery.
First off, thank you for the reply audit!
Now I have officially rooted my phone using CF-Autoroot and have installed TWRP. I have also confirmed that the bootloader is at least 4.3 because it does show the warranty bit.
Which of the stock roms are compatible with this bootloader?
Do you want to stay on a stock ROM? If not, you could flash a custom ROM such as cm12.1 using TWRP. Once you have flashed a custom ROM, you can look under settings to determine the baseband on the phone which is another clue as to which bootloader is on your phone.
audit13 said:
Do you want to stay on a stock ROM? If not, you could flash a custom ROM such as cm12.1 using TWRP. Once you have flashed a custom ROM, you can look under settings to determine the baseband on the phone which is another clue as to which bootloader is on your phone.
Click to expand...
Click to collapse
Just to be clear, cm12.1 is the cyanogenMod nightly?
Yup. If you flash it, your baseband may be unknown which tells me you are probably not running a 4.4.2 bootloader and modem.
audit13 said:
Yup. If you flash it, your baseband may be unknown which tells me you are probably not running a 4.4.2 bootloader and modem.
Click to expand...
Click to collapse
I'll try it out and see if I can get past the language screen this time.
Got the latest Cyanogenmod Zip file onto my phone. Tried flashing it through TWRP with the install option but it failed.
Log reads that no MDS file was found, detected filesystem ext4 for /dev/block/platform msm_sdcc.1/byname system. Can't install this package on top of incompatible data.
CM12.1 won't have an md5 file. You're trying to install cm12.1 for the d2att or d2lte? You're running the latest TWRP which I believe is 2.8.7.0? or 2.8.7.1?
5K posts.
"all i can really do , is stay out of my own way and let the will of heaven be done"
I'm pretty sure that CM de-unified the variants for CM 12.
From: https://wiki.cyanogenmod.org/w/D2lte_Info
Note: Unified device
Between the release of CM 11 M3 and CM11 M12, all Qualcomm-based variants of this device were merged into a single build: d2lte. The device information pages for the individual variants should be used to reference any device-specific unlock instructions, download recoveries, to build CM 10.2, or to install CM 12.1: d2att, d2cri, d2mtr, d2spr, d2tmo, d2usc, d2vzw.
Click to expand...
Click to collapse
I think this was just to make searching a bit harder/ more complicated.
audit13 said:
CM12.1 won't have an md5 file. You're trying to install cm12.1 for the d2att or d2lte? You're running the latest TWRP which I believe is 2.8.7.0? or 2.8.7.1?
Click to expand...
Click to collapse
For d2att and running 2.8.7.0 for TWRP.
You should be good then.
The file should be left unzipped/unrared when using it right? I'm using it as such but it keeps returning the same error message saying that it won't install it.
Yes, leave it zipped. What is the TWRP error message?
The error log:
detected filesystem ext4 for /dev/block/platform msm_sdcc.1/byname system.
Can't install this package on top of incompatible data.
Please try another package or run a factory reset
E: Error executing updater binary in zip '/sdcard/Download/cm-12.12015913-NIGHTLY-dtatt.zip
Error flashing zip '/sdcard/Download/cm-12.120150913-NIGHTLY-D2att.zip
Weird, did you do a full wipe before trying to install?
Can't believe it was that simple. I thought I had already made the wipe when I did it with the original recovery but making a second wipe through TWRP actually helped make it happen. I finally got through and have full access to my phone.
Unfortunately, the cell service doesn't seem to work but I'm guessing that I need to do more for the set up?
Edit: Not recognizing the sim card for some reason
Sounds like you need to update the bootloader and modem to the older KK version which I think is ne4.
Sorry for the late reply I've been busy the past week. I'm guessing the modem won't work without the proper bootloader? I've tried flashing the latest and original modem from the Modem list (http://forum.xda-developers.com/showthread.php?t=1831898). While they installed successfully I still don't get a signal.
I was worried which bootloader to take because it may lead to bricking. Which one are you referring to and are they in the Bootloader updates topic here? (http://forum.xda-developers.com/showthread.php?t=2321310)
Good evening everyone!
I've recently wanted to update my Hercules from 4.1 (I know it's reeealy outdated) to version 6.0 Marshmallow.
So I did a few steps and now I cant' seem to go any further, and I need your help.
So far, I've done the following:
-Installed TWRP 2.8.7.0
-Used Odin to flash the TWRP mentioned above
Now, I know there are a few problems regarding this version of the TWRP on the Hercules, so I tried fixing it by using Odin again and flashing the updated 2.8.7.1 and even the 3.0 version that I found on some threads, but with no sucess.
I haven't even had the chance to install Marshmallow on my phone in the first chance, because I couldn't find any .ZIP folders on the TWRP instalation menu.
I really appreciate your help guys, I'm a noob at this and I'm just starting to figure what is what, I just need my phone updated. It's running so far atleast, so it's not hard bricked I guess.
Did you follow the instructions to flash TWRP using Odin?
olafo73 said:
Did you follow the instructions to flash TWRP using Odin?
Click to expand...
Click to collapse
I'm pretty sure I did everything I was intended to do. I installed Samsung Kies so I could install the drivers on my mobile, and then TWRP through Odin properly with the blue light showing up. After flashing it, it turned green and said PASS or PASSED. So I think I did everything right on that end, I can even access TWRP with no real problems.
I even tried to do a ROOT on my system, but again, I couldn't use ZIP or any other files on the TWRP installation option because they simply do not appear
bump
Watching this thread as I have the same problem.
I can boot to TWRP 2.8.7, but if I try to install, there's no file to install from.
I can go back to TWRP 2.6.0, and then mount the card and see the ROM, but every ROM I try fails. Something about non-virtual partitions if I try 4.4 or better, and error executing updater binary if i try 4.1
aguycalled80 said:
Watching this thread as I have the same problem.
I can boot to TWRP 2.8.7, but if I try to install, there's no file to install from.
I can go back to TWRP 2.6.0, and then mount the card and see the ROM, but every ROM I try fails. Something about non-virtual partitions if I try 4.4 or better, and error executing updater binary if i try 4.1
Click to expand...
Click to collapse
How did you go back to TWRP 2.6.0?
N1ZUW said:
How did you go back to TWRP 2.6.0?
Click to expand...
Click to collapse
With Odin.
I can boot in download mode no problem.
N1ZUW said:
Good evening everyone!
I've recently wanted to update my Hercules from 4.1 (I know it's reeealy outdated) to version 6.0 Marshmallow.
So I did a few steps and now I cant' seem to go any further, and I need your help.
So far, I've done the following:
-Installed TWRP 2.8.7.0
-Used Odin to flash the TWRP mentioned above
Now, I know there are a few problems regarding this version of the TWRP on the Hercules, so I tried fixing it by using Odin again and flashing the updated 2.8.7.1 and even the 3.0 version that I found on some threads, but with no sucess.
I haven't even had the chance to install Marshmallow on my phone in the first chance, because I couldn't find any .ZIP folders on the TWRP instalation menu.
I really appreciate your help guys, I'm a noob at this and I'm just starting to figure what is what, I just need my phone updated. It's running so far atleast, so it's not hard bricked I guess.
Click to expand...
Click to collapse
I don't know of any problems with any of the recoveries. However there are different recoveries for different roms which need to be used in a specific order and in a specific way, the first time that you virtually repartition your phone.
Have you gone through the process of applying the "virtual partition" and installing the modified "virtual partition" recovery? This is required for most of the MM roms on this phone (Hercules). The process is very well documented here http://forum.xda-developers.com/galaxy-s2-tmobile/help/guidance-sgh-t989-updating-issue-t3414641 in the #2nd post.
markusrow said:
I don't know of any problems with any of the recoveries. However there are different recoveries for different roms which need to be used in a specific order and in a specific way, the first time that you virtually repartition your phone.
Have you gone through the process of applying the "virtual partition" and installing the modified "virtual partition" recovery? This is required for most of the MM roms on this phone (Hercules). The process is very well documented here http://forum.xda-developers.com/galaxy-s2-tmobile/help/guidance-sgh-t989-updating-issue-t3414641 in the #2nd post.
Click to expand...
Click to collapse
Hi, thanks for replying
No, I dont' take I have taken that step actually. I'm pretty new to this and I tried following every step correctly, but I know that I failed or skipped something at some extent and I've been trying to figure out what exactly, so I can fix it. I guess I need to Virtual Partition my phone then, could you post me the link do to so? Because I think you posted one that would take back to this post
aguycalled80 said:
With Odin.
I can boot in download mode no problem.
Click to expand...
Click to collapse
How do you go in download mode if you have TWRP installed? Does TWRP work as download mode aswell? Thanks for your help man, hope you can fix your phone too!
N1ZUW said:
How do you go in download mode if you have TWRP installed? Does TWRP work as download mode aswell? Thanks for your help man, hope you can fix your phone too!
Click to expand...
Click to collapse
I shut it down in TWRP then hold volume down and power to go into download mode.
My phone has gone backwards now though - it doesn't matter what I load in Odin now, it won't boot up. The SAMSUNG screen is on, with a progress bar, but it never gets to the end. It stops right near the end and it sits there until I reboot it again.