Error Status 7 - Sprint Samsung Galaxy S III

So, I can't post in development yet, so hopefully enough folks here can help me out.
I've done everything I can to get my phone back to stock to bump up to LG8.
I'm unrooted and I flashed the bare bones stock LEN ROM back onto my phone so now both my baseband and build version match (LEN). No root, stock recovery and I'm still getting that same Status 7 error.
Anyone have any other suggestions?
B

batto1 said:
So, I can't post in development yet, so hopefully enough folks here can help me ong I can to get my phone back to stock to bump up to LG8.
I'm unrooted and I flashed the bare bones stock LEN ROM back onto my phone so now both my baseband and build version match (LEN). No root, stock recovery and I'm still getting that same Status 7 error.
Anyone have any other suggestions?
B
Click to expand...
Click to collapse
If you flashed a bare bones ROM ull be missin stuff and it will fail. Flash stock tar in Odin and all will be well. Stock tar: http://samsung-updates.com/get/1917/Samsung_Firmware_SPH-L710_SPR_L710VPALEN_Android_4_0_4.html
Really tho, the only important thing from the updates was the modem. Could always DL that here and flash seperately. Then manually chg or build so you don't get the update prompt. Seems like a lot of work on your end just for a worthless ota. At any rate tho that link should solve or problem

billard412 said:
If you flashed a bare bones ROM ull be missin stuff and it will fail. Flash stock tar in Odin and all will be well. Stock tar: http://samsung-updates.com/get/1917/Samsung_Firmware_SPH-L710_SPR_L710VPALEN_Android_4_0_4.html
Click to expand...
Click to collapse
Ah, let me clarify.
I tried through this thread: http://forum.xda-developers.com/showthread.php?t=1810341
So that is the ROM I used, that's what I meant by bare bones stock. No root, no patches, just the basic ROM
thanks though

Wow sprints network sucks. anyway this should work, did for me. would have a nandroid backup handy just in case https://www.dropbox.com/s/0ip3ck2gzdfk51b/lg8.zip Thats the update w/ no checks that will give you status 7. flash in cwm

billard412 said:
Wow sprints network sucks. anyway this should work, did for me. would have a nandroid backup handy just in case Thats the update w/ no checks that will give you status 7. flash in cwm
Click to expand...
Click to collapse
Gotcha, appreciate it, I'll let you know later how it goes (once I get somewhere I can reroot)
Any idea what may happen without that check?

batto1 said:
Gotcha, appreciate it, I'll let you know later how it goes (once I get somewhere I can reroot)
Any idea what may happen without that check?
Click to expand...
Click to collapse
if your on stock then i cant see there being any problems, i think ur failing the checks because of somethin small ur missing. At worst you wont boot/softbrick thats why the nandroid is reccommended so you can always reverse if it happens. was getting tired of status 7s myself which is why i did that when i was runnin stock. workd for me. But ya, worst case scenario, u gta restore ur nandroid, should be fine tho. You can flash it rooted btw. it will flash with root just fine although itll probly patch it. Needs cwm as well, will most likely fail in stock recovery as it is not signed anymore

billard412 said:
if your on stock then i cant see there being any problems, i think ur failing the checks because of somethin small ur missing. At worst you wont boot/softbrick thats why the nandroid is reccommended so you can always reverse if it happens. was getting tired of status 7s myself which is why i did that when i was runnin stock. workd for me. But ya, worst case scenario, u gta restore ur nandroid, should be fine tho.
Click to expand...
Click to collapse
gotcha, thanks,
I do wish that these errors were easier to decipher, would make life much easier...

softbrick oh well, rollback time

damn
Wonder wat stopped it from workin..

no clue, got stuck at the 'Samung' screen on boot.
ended up reflashing the stock LEN ROM via Odin.
know where I can just get a stock LG8 ROM?

how have I missed this thread the past 3 days.....
http://forum.xda-developers.com/showthread.php?t=174323
however, this is downloading at 35kbps....

Related

Update broke my phone!!!!!

I'm running cwm 5.8.4.5 and the new update just pushed and now my phone won't reboot help!!!!!.
can you go in Download? No?
if yes no worries re flash.
can you go in Recovery? No?
if yes no worries re flash.
If both are No. im Sry but you have a Hard bricked phone. Ether send it back to Samsung might have a chance of re flashing it there, or give a call to Mobile tech videos and talk to josh.
GL.
Ditto-trolling said:
can you go in Download? No?
if yes no worries re flash.
can you go in Recovery? No?
if yes no worries re flash.
If both are No. im Sry but you have a Hard bricked phone. Ether send it back to Samsung might have a chance of re flashing it there, or give a call to Mobile tech videos and talk to josh.
GL.
Click to expand...
Click to collapse
I can restore but the darn thing keeps updating and I keep having to rstore. What should I flash?
I would recommend to put it in download mode and use odin to go back to stock look for your phone firmware @ samsung-updates.com
yea, as long as you can get into either of those modes already mentioned then you can always revert back to stock then try custom roms and kernels after

[Q] HELP I seem to be stuck.....

Good Evening all,
I have a T-mobile Galaxy S3 that was rooted. That I took back to stock and unrooted using Odin and T999UVALEM_T999TMBALEM_T999UVALEM_HOME.tar......I let the phone sit for about 25-30 min and it never really made it past the pulsing SAMSUNG screen. Now I rebooted into Flashing Mode (Odin) and Flashed CF-Auto-Root-d2tmo-d2tmo-sght999.tar, thinking that would help.......however.....I still seem to be stuck.....How do I get myself unstuck? Thanks so much for any help .....
Mic
Have you tried using stock recovery and perform a factory reset? I also took mine back to stock via Odin, performed the factory reset and worked fine
Sent from my SGH-T999 using Tapatalk
Hellfireworks said:
Have you tried using stock recovery and perform a factory reset? I also took mine back to stock via Odin, performed the factory reset and worked fine
Sent from my SGH-T999 using Tapatalk
Click to expand...
Click to collapse
I did do that.....and was able to update to 4.3 through t-mobile, however, now I have a black block which appears over all screens giving or listing what seems to be the information about my phone, and a warning that the phone is in "Factory Mode" and I need to reset it back to user.....or something like that...it comes and goes kinda fast....I wanted to flash a different ROM but I went back to stock to kinda clean up my internal SD....it was getting kinda bulked down with all the roms I was trying.........but now I am stuck with this......any ideas??
jinx0117 said:
I did do that.....and was able to update to 4.3 through t-mobile, however, now I have a black block which appears over all screens giving or listing what seems to be the information about my phone, and a warning that the phone is in "Factory Mode" and I need to reset it back to user.....or something like that...it comes and goes kinda fast....I wanted to flash a different ROM but I went back to stock to kinda clean up my internal SD....it was getting kinda bulked down with all the roms I was trying.........but now I am stuck with this......any ideas??
Click to expand...
Click to collapse
Did you update to 4.3 while you were in stock? If you did that, maybe Knox is causing you these issues, if you havent been in 4.3 in stock, you shouldn't have that issue.
I would suggest flashing 4.1.2 version via odin, after that enter recovery and do a factory reset, after that reboot and it should start properly
Sent from my SGH-T999 using Tapatalk
Hellfireworks said:
Did you update to 4.3 while you were in stock? If you did that, maybe Knox is causing you these issues, if you havent been in 4.3 in stock, you shouldn't have that issue.
I would suggest flashing 4.1.2 version via odin, after that enter recovery and do a factory reset, after that reboot and it should start properly
Sent from my SGH-T999 using Tapatalk
Click to expand...
Click to collapse
I originally went to Stock 4.1.2....then got tried to root the phone thinking that flashing different Rom would fix the issue.....no dice...So I flashed back to the 4.1.2 Stock. Made my way around the block that pops up telling me I need to set it back to user mode and did the OTA update. After the update it was still saying that I was in Factory Mode....and needed to reset it to User Mode.....In did a hard reset and wipe....and it is still there.....I may be able to change it through root explorer but I need to root my phone again.....and I have no idea where a safe place to start would be for that....
@jinx0117
Sounds like your EFS folder might have been erased. You can root the phone and check with a file explore. If you don't have a backup of it, there is no way to recover it.
If you have updated to official 4.3 don't try to downgrade with odin or you will end up with a full brick.
sswb27 said:
@jinx0117
Sounds like your EFS folder might have been erased. You can root the phone and check with a file explore. If you don't have a backup of it, there is no way to recover it.
If you have updated to official 4.3 don't try to downgrade with odin or you will end up with a full brick.
Click to expand...
Click to collapse
Thank you so much for telling me that.....I was able to root and reset my phones Factory Mode by use of a Emulator. Now I did follow some steps I found here on XDA to get around the Knox Security that T mobile put on the 4.3 update......I am able to flash Roms now with no issues.....thanks so much everyone for all your help!!!!
I will assume that if I want to take it back to stock again I would need to flash a 4.3 stock with Odin???? That way I don't brick my phone? Is that correct?:good:
jinx0117 said:
Thank you so much for telling me that.....I was able to root and reset my phones Factory Mode by use of a Emulator. Now I did follow some steps I found here on XDA to get around the Knox Security that T mobile put on the 4.3 update......I am able to flash Roms now with no issues.....thanks so much everyone for all your help!!!!
I will assume that if I want to take it back to stock again I would need to flash a 4.3 stock with Odin???? That way I don't brick my phone? Is that correct?:good:
Click to expand...
Click to collapse
Yea, Stick with 4.3 odin for now on. The 4.3 Bootloader wont let you downgrade.
sswb27 said:
Yea, Stick with 4.3 odin for now on. The 4.3 Bootloader wont let you downgrade.
Click to expand...
Click to collapse
Thank you so much for that....I have tried to flash a few custom roms but I see there are some issues with certain parts of the phone if they are not 4.3 and above. Do you know of a good ROM that would work on my phone that has alot of customizing.....I'm a chick....so....In like to theme.....lol
I can't use anything from Team Dirt.....my phone won't load it....I have Dandroid on there now....but that is pretty much stock.....Tried StockRom custom.....but it never loaded the Aroma installer......it just sat there saying it was loading it...... Thanks again for all the help. :laugh:
jinx0117 said:
Thank you so much for that....I have tried to flash a few custom roms but I see there are some issues with certain parts of the phone if they are not 4.3 and above. Do you know of a good ROM that would work on my phone that has alot of customizing.....I'm a chick....so....In like to theme.....lol
I can't use anything from Team Dirt.....my phone won't load it....I have Dandroid on there now....but that is pretty much stock.....Tried StockRom custom.....but it never loaded the Aroma installer......it just sat there saying it was loading it...... Thanks again for all the help. :laugh:
Click to expand...
Click to collapse
Aroma is buggy, you just have to keep rebooting into recovery and keep trying, it will go. Some say it seems to work better without the usb plugged in.
As for team dirt I believe it is a aosp rom. If it is you will have to edit the updater script in the zip file so it know's your new 4.3 bootloader. META-INF>com>google>android>updater-script. If your on windows I suggest downloading notepad++ to edit the file. Just delete every thing down to where it
say's mount then save the file.
Update: I edited the updater for you https://www.dropbox.com/s/xucl47rh1wxg9rt/updater-script
Just put it in the zip file where I told you above, save and copy it to the zip and flash away.
sswb27 said:
Aroma is buggy, you just have to keep rebooting into recovery and keep trying, it will go. Some say it seems to work better without the usb plugged in.
As for team dirt I believe it is a aosp rom. If it is you will have to edit the updater script in the zip file so it know's your new 4.3 bootloader. META-INF>com>google>android>updater-script. If your on windows I suggest downloading notepad++ to edit the file. Just delete every thing down to where it
say's mount then save the file.
Update: I edited the updater for you https://www.dropbox.com/s/xucl47rh1wxg9rt/updater-script
Just put it in the zip file where I told you above, save and copy it to the zip and flash away.
Click to expand...
Click to collapse
Wow!!!! Thank you sooooo much....I admit I don't know it all just enough to be dangerous....but I am always willing to learn.....thank you so much for doing that for me....that was really awesome of you......
jinx0117 said:
Wow!!!! Thank you sooooo much....I admit I don't know it all just enough to be dangerous....but I am always willing to learn.....thank you so much for doing that for me....that was really awesome of you......
Click to expand...
Click to collapse
Well, this is the place to learn. We are all here to help each other, that's why i love android.:highfive:
Just use that thanks button to people that help you is all we ask in return.

[Q] Downgrade T999L back to 4.1.2?

Is it possible or will I face a brick? I wanna try the MIUI v5 Rom but I can't flash since I don't have the old LTE bootloader
alfadog77 said:
Is it possible or will I face a brick? I wanna try the MIUI v5 Rom but I can't flash since I don't have the old LTE bootloader
Click to expand...
Click to collapse
From personal experience..
Only flashing an older boot-loader if coming from the more recent one, that will brick your device..
Dont quote me on that.. But im pretty sure thats the case
Zaphodspeaks said:
From personal experience..
Only flashing an older boot-loader if coming from the more recent one, that will brick your device..
Dont quote me on that.. But im pretty sure thats the case
Click to expand...
Click to collapse
So i can't flash miui v5 at all? That's annoying i wanted to try it
alfadog77 said:
So i can't flash miui v5 at all? That's annoying i wanted to try it
Click to expand...
Click to collapse
Sounds about right..
There a a few roms that I'd like to try for my T999L, but I wont mess with my bootloader..
I dont want anything to do with Knox. Even though you can install a 4.3 rom with out it..
The Bootloader still contains remnants of Knox..
Miui v5, looks like a 4.2 rom.
I dont see a problem.. Make a Nandroid first.. Then do a factory wipe, and give it a try..
if it doesnt work.. you can always go back..
Zaphodspeaks said:
Sounds about right..
There a a few roms that I'd like to try for my T999L, but I wont mess with my bootloader..
I dont want anything to do with Knox. Even though you can install a 4.3 rom with out it..
The Bootloader still contains remnants of Knox..
Miui v5, looks like a 4.2 rom.
I dont see a problem.. Make a Nandroid first.. Then do a factory wipe, and give it a try..
if it doesnt work.. you can always go back..
Click to expand...
Click to collapse
I've tried to flash it and i keep getting assert failed error. I looked at the built prop in the log on TWRP and it list all the bootloaders but MK4. So i'm assuming its because of the bootloader it won't let me flash. Even though it says d2tmolte is supported
alfadog77 said:
I've tried to flash it and i keep getting assert failed error. I looked at the built prop in the log on TWRP and it list all the bootloaders but MK4. So i'm assuming its because of the bootloader it won't let me flash. Even though it says d2tmolte is supported
Click to expand...
Click to collapse
Sounds like the Rom your flashing isnt meant for your Carrier/Device..
Just to be sure.. Id check to see if you have the most recent version of TWRP installed..
Zaphodspeaks said:
Sounds like the Rom your flashing isnt meant for your Carrier/Device..
Just to be sure.. Id check to see if you have the most recent version of TWRP installed..
Click to expand...
Click to collapse
It's the latest one from Goo Manager. twrp 2.6.3.1. And blackwing made it work for the t-mo s3 and lte version but it still won't flash. Is it just my phone?
alfadog77 said:
It's the latest one from Goo Manager. twrp 2.6.3.1. And blackwing made it work for the t-mo s3 and lte version but it still won't flash. Is it just my phone?
Click to expand...
Click to collapse
I doubt its the phone...
Im a semi novice on this phone.. I fare better with Nexus devices..
Im sure your just missing a step.. If your phone is working put it off, and wait until someone with more experience might be able to help..
If your getting an Error 7, that is likely due to the Update Script which TWRP looks at before any kind of flash, its mainly to protect people from flashing the wrong things on their devices.. Its saved my ass a couple of times..
Find the original thread for that Rom..
and post your question there..
Zaphodspeaks said:
I doubt its the phone...
Im a semi novice on this phone.. I fare better with Nexus devices..
Im sure your just missing a step.. If your phone is working put it off, and wait until someone with more experience might be able to help..
If your getting an Error 7, that is likely due to the Update Script which TWRP looks at before any kind of flash, its mainly to protect people from flashing the wrong things on their devices.. Its saved my ass a couple of times..
Find the original thread for that Rom..
and post your question there..
Click to expand...
Click to collapse
I did and i'm waiting for a reply. And yeah i'm getting a Error 7
alfadog77 said:
I did and i'm waiting for a reply. And yeah i'm getting a Error 7
Click to expand...
Click to collapse
CAN WE install 4.1.2 non rooted firmware without bricking ???? i m on 4.3 n i want go back for miui
londheaakash said:
CAN WE install 4.1.2 non rooted firmware without bricking ???? i m on 4.3 n i want go back for miui
Click to expand...
Click to collapse
No. Just flash miui with a custom recovery and you should be good. In the future please do not ask similar questions in different threads

BRICKED... help?

Hey all, I need some help. I bricked my phone, and I can only get into download mode and recovery. Flashing through odin fails each time, and so does flashing through recovery. Gives me a status 7 error. Ive made sure I'm downloading all the proper files, but Im stumped here. My phone also isnt recognized in Kies. Ive uninstalled and reinstalled the drivers multiple times now. Im too nervous to go to an AT&T store because theyll see I voided my warranty from the recovery (using philz recovery).
Anyone got any clue on what Im doing wrong? Any help would be much appreciated.
Syst3m Deadlock said:
Hey all, I need some help. I bricked my phone, and I can only get into download mode and recovery. Flashing through odin fails each time, and so does flashing through recovery. Gives me a status 7 error. Ive made sure I'm downloading all the proper files, but Im stumped here. My phone also isnt recognized in Kies. Ive uninstalled and reinstalled the drivers multiple times now. Im too nervous to go to an AT&T store because theyll see I voided my warranty from the recovery (using philz recovery).
Anyone got any clue on what Im doing wrong? Any help would be much appreciated.
Click to expand...
Click to collapse
EDIT: In your sig, it says you have an S2? this is the S3 section.
What happened exactly to soft-brick?
The software you're flashing with Odin might not be good, try another one. Also, since you can get in recovery, you can try clean flashing the ROM you had running previous to the brick.
BWolf56 said:
EDIT: In your sig, it says you have an S2? this is the S3 section.
What happened exactly to soft-brick?
The software you're flashing with Odin might not be good, try another one. Also, since you can get in recovery, you can try clean flashing the ROM you had running previous to the brick.
Click to expand...
Click to collapse
I have an S3 now, just havent updated my sig.
And I was trying to root. I was on the latest stock 4.4.2 and flashed the wrong file by mistake. Forgot what it was. So now I cant flash any files in recovery or odin. It just fails each and every time. I know all these files cant be bad
So root wasnt successful and now I cant even revert back to stock
Kies interferes with odin. Uninstall it from your computer and try odin again.
DocHoliday77 said:
Kies interferes with odin. Uninstall it from your computer and try odin again.
Click to expand...
Click to collapse
Still didnt work. Odin let me install a recovery file, but it just wont let me install files to restore back to stock. Same with recovery, I'm still getting the status 7 error. It doesnt make any sense. Ive downloaded and redownloaded from different places, so I highly doubt that all these files are bad
Are you running the latest Philz? Sometimes, the status 7 error occurs with an outdated recovery. Have you tried flashing a custom ROM with TWRP?
audit13 said:
Are you running the latest Philz? Sometimes, the status 7 error occurs with an outdated recovery. Have you tried flashing a custom ROM with TWRP?
Click to expand...
Click to collapse
I'm running 6.0.5 - no I haven't tried TWRP
What rom were you running before? What do you want to be running now?
And what is your current firmware/bootloader version? Not sure about philz recovery, but status 7 errors usually occur when you dont have the required firmware build.
Also, at least for the T999, cm roms updater-scripts are outdated. So if we have the newest available, it still gives the status 7 errors because the new builds haven't been added. Just thought I'd mention this in case you're updated to the new kk firmware and are trying to flash a cm rom.
DocHoliday77 said:
What rom were you running before? What do you want to be running now?
And what is your current firmware/bootloader version? Not sure about philz recovery, but status 7 errors usually occur when you dont have the required firmware build.
Also, at least for the T999, cm roms updater-scripts are outdated. So if we have the newest available, it still gives the status 7 errors because the new builds haven't been added. Just thought I'd mention this in case you're updated to the new kk firmware and are trying to flash a cm rom.
Click to expand...
Click to collapse
I was running official 4.4 unrooted. I'm trying to install Likewise S5.
Install terminal emulator from the play store and enter this:
getprop ro.bootloader
If it returns I747UCUEMJB you should be ok to flash likewise and something else is preventing it. If its anyway but that, you probably need to update your base firmware/bootloaders first.
If you're still unable to boot anything, the build should be shown on the Download Mode screen. You can probably reflash your previous rom and boot to that for right now though.
I was able to get a custom ROM installed, but now I have no reception. Im guessing the bootloader needs to be updated. So I tried updating it via odin. That failed. I also tried flashing it in recovery and still got a status 7 error. Im at my whits end here
You probably need to flash your modem. Run the Terminal Emulator command I posted before, and if it returns I747UCUEMJB, flash the MJB modem. If it returns anything else, flash the modem that matches, but let us know first just to be on the safe side.
DocHoliday77 said:
You probably need to flash your modem. Run the Terminal Emulator command I posted before, and if it returns I747UCUEMJB, flash the MJB modem. If it returns anything else, flash the modem that matches, but let us know first just to be on the safe side.
Click to expand...
Click to collapse
Terminal Emulator tells me my bootloader is 1747UCUFNE4
Syst3m Deadlock said:
Terminal Emulator tells me my bootloader is 1747UCUFNE4
Click to expand...
Click to collapse
So yeah, you need the 1747UCUFNE4 baseband. Look in Settings/About Phone to know which one you have before going and flashing it.
BWolf56 said:
So yeah, you need the 1747UCUFNE4 baseband. Look in Settings/About Phone to know which one you have before going and flashing it.
Click to expand...
Click to collapse
I cant seem to find the 1747UCUFNE4 baseband,
Syst3m Deadlock said:
I cant seem to find the 1747UCUFNE4 baseband,
Click to expand...
Click to collapse
Did you check which one you have atm?
And here, from Doc http://forum.xda-developers.com/showpost.php?p=53626873&postcount=4
BWolf56 said:
Did you check which one you have atm?
And here, from Doc http://forum.xda-developers.com/showpost.php?p=53626873&postcount=4
Click to expand...
Click to collapse
Thanks a bunch, it worked!!!

Update Stoped On Galaxy Note II Screen

Hello, I used to be rooted with custom ROMs ect but went back to stock I317ATTALJ2 so I can give the phone to my daughter. Well everything went smooth until an update from AT&T came through and she ran it when the battery was at 21% but I'm not sure it that matter but didn't help in matters... Anyhow it ran the upgrade and on reboot it stayed on the Galaxy Note II screen and wont do anything but sit there. I let it sit for a long time before pulling the battery and booting but it goes to same screen and same thing. I can not get into recovery (Volume Up, Home, Pwr) but I can go into download mode. With the battery being so low I read that it charges while in download mode so for the remainder of the day I put the phone in download mode and plugged into charger.
Suggestions?
After you get it charged up some and you're in download mode. Just Odin back to stock Att firmware should fix the problem hopefully...
You can find the stock firmware here>> http://bit.ly/1HNVFVJ
Guess the phone didn't like that update ?.
Bajanman said:
After you get it charged up some and you're in download mode. Just Odin back to stock Att firmware should fix the problem hopefully...
You can find the stock firmware here>> http://bit.ly/1HNVFVJ
Guess the phone didn't like that update .
Click to expand...
Click to collapse
Ok, Ill give the stock firmware (At&t Firmware I317UCALJ2 Uploaded By-Bajanman) that Bajanman supplys ill let you guys know in an hour or two its downloading now. I did try re installing the stock firmware I had that worked the first time and it was from SamMobile and it too sent me to the Galaxy Note II screen and froze so its not looking good.....
Thanks!
Oxicottin said:
Ok, Ill give the stock firmware (At&t Firmware I317UCALJ2 Uploaded By-Bajanman) that Bajanman supplys ill let you guys know in an hour or two its downloading now. I did try re installing the stock firmware I had that worked the first time and it was from SamMobile and it too sent me to the Galaxy Note II screen and froze so its not looking good.....
Thanks!
Click to expand...
Click to collapse
Ok.
Hopefully everything works out next time around.
Another thing you could try is flashing which ever recovery you previously had installed. Last time I was having issues with something similar, after re flashing my recovery everything started working again. Just just a thought that might work.
I'm monitoring this thread too see what happens ok.
Bajanman said:
Ok.
Hopefully everything works out next time around.
Another thing you could try is flashing which ever recovery you previously had installed. Last time I was having issues with something similar, after re flashing my recovery everything started working again. Just just a thought that might work.
I'm monitoring this thread too see what happens ok.
Click to expand...
Click to collapse
Recovery? can I flash the stock recovery using ODIN? If so where do I get it.... I always have used TWRP I wanted to use custom ROMs never really experimented with anything else.
Oxicottin said:
Recovery? can I flash the stock recovery using ODIN? If so where do I get it.... I always have used TWRP I wanted to use custom ROMs never really experimented with anything else.
Click to expand...
Click to collapse
Yes you can flash a custom recovery from Odin. You just have to use the (Twrp) tar file found here>>>
http://bit.ly/1y0Tyg7
Find your device model and download the tar. And make sure you're downloading the correct file for your device ok!
I to use Twrp and luv it.?
OK, well its not looking good....
1) Flashed the stock firmware suggested...... Still get same results!
2) Flashed TWRP through ODIN and it made it to the same screen and froze. Did a battery pull and button combo and it wont go into recovery.
Is there a application that will force your phone into recovery and download modes? I remember back when I messed with the captivate there was a application someone built that did such a thing.
Any suggestions?
Oxicottin said:
OK, well its not looking good....
1) Flashed the stock firmware suggested...... Still get same results!
2) Flashed TWRP through ODIN and it made it to the same screen and froze. Did a battery pull and button combo and it wont go into recovery.
Is there a application that will force your phone into recovery and download modes? I remember back when I messed with the captivate there was a application someone built that did such a thing.
Any suggestions?
Click to expand...
Click to collapse
Not sure you were on the newer 4.4.2 bootloader or not. If it was on a newer bootloader then you won't be able to downgrade.. This might help you get the phone working again since you just flashed the original firmware.
Go to this thread here>>http://forum.xda-developers.com/showthread.php?t=2502464.
Download
4.3 Param.bin and Tz.img
http://d-h.st/OYC
Step 2 (no bootloader in here)
flash this to bring wifi back
but keep your knox free 4.1.2 bootloader.
Allowing you to freely flash between 4.1.2 roms and the latest 4.3 leak
Without having to one click,Keeping Wifi Throughout and removing Knox
Click to expand...
Click to collapse
Unzip, Boot into Download mode, Open ODIN, put tar file in PDS slot, click Start.
Then you can go here for the latest stock Att firmware. If the above steps don't help you, then you could try flashing one one the rooted stock packages from this thread.
Bajanman said:
Not sure you were on the newer 4.4.2 bootloader or not. If it was on a newer bootloader then you won't be able to downgrade.. This might help you get the phone working again since you just flashed the original firmware.
Go to this thread here>>http://forum.xda-developers.com/showthread.php?t=2502464.
Download
4.3 Param.bin and Tz.img
http://d-h.st/OYC
Unzip, Boot into Download mode, Open ODIN, put tar file in PDS slot, click Start.
Then you can go here for the latest stock Att firmware. If the above steps don't help you, then you could try flashing one one the rooted stock packages from this thread.
Click to expand...
Click to collapse
Ok that worked and it booted!!!! Now im on 4.1.1 with TWRP
Not really sure what I just did? Did I downgrade my bootloader? Also, now how do I get it to the most up to date version without this again?
I downloaded an app and it says im on.....
Bootloader Version: 1317UCUBMK6
Thanks!
Oxicottin said:
Ok that worked and it booted!!!! Now im on 4.1.1 with TWRP
Not really sure what I just did? Did I downgrade my bootloader? Also, now how do I get it to the most up to date version without this again?
Thanks!
Click to expand...
Click to collapse
Ok not is back working again, which is great news ?. Go to the link I posted for the stock firmware, and use the rooted one.
But first make a backup of your working system first ok.
Bajanman said:
Ok not is back working again, which is great news . Go to the link I posted for the stock firmware, and use the rooted one.
But first make a backup of your working system first ok.
Click to expand...
Click to collapse
Ok, Im On 4.3 now and its working great.... Thank You!
Oxicottin said:
Ok, Im On 4.3 now and its working great.... Thank You!
Click to expand...
Click to collapse
You're very welcome glad I could help fix it.
Have a good day...
Ok problem solved so unsubscribing from this thread. If you run into any other problems you can always hit me up thru pm ?.

Categories

Resources