Related
Rooted Att Note 2. I changed my fonts using Rom Tools and now my phone just sits at the Samsung splash screen. I did factory reset in recovery, still no dice. The recovery install only let's my flash updates and no I don't have a Nandroid. Kinda ran outta of ideas.
when you say the recovery install only lets you flash updates do you mean your still using stock revocery or have you flashed custom recovery and just dont have a ROM?
If you have custom recovery Id try to flash this :http://forum.xda-developers.com/showthread.php?t=1984546 Its been tested and works on our system. Its not stock but should at least get ya up and running again until a true stock is posted and you can flash that.
search in forums for an Odin tar file to reload the stock ROM. GL & do a nandroid before doing anything next time.
RMXO said:
search in forums for an Odin tar file to reload the stock ROM. GL & do a nandroid before doing anything next time.
Click to expand...
Click to collapse
I always do, didnt think much of fonts
cjsspape said:
when you say the recovery install only lets you flash updates do you mean your still using stock revocery or have you flashed custom recovery and just dont have a ROM?
If you have custom recovery Id try to flash this :http://forum.xda-developers.com/showthread.php?t=1984546 Its been tested and works on our system. Its not stock but should at least get ya up and running again until a true stock is posted and you can flash that.
Click to expand...
Click to collapse
not custom, thats the problem. I flashed twrp thru odin but it didnt take, even though it went thru
Try to flash cwm then and see if that takes. You'll need the Odin version of this file at the bottom of the OP http://forum.xda-developers.com/showthread.php?p=33955697
Sent from my SAMSUNG-SGH-I317 using xda premium
Sloved
the cmw tar worked. flash the rom in the general section
Good stuff. Glad it worked out for ya!
Sent from my SAMSUNG-SGH-I317 using xda premium
esincho said:
Rooted Att Note 2. I changed my fonts using Rom Tools and now my phone just sits at the Samsung splash screen. I did factory reset in recovery, still no dice. The recovery install only let's my flash updates and no I don't have a Nandroid. Kinda ran outta of ideas.
Click to expand...
Click to collapse
I had the same problem with Sprint note 2 and i just went to download screen and then flashed the cwm tar file and then all was good. Whew!!! Thought I bricked it! I made the mistake of using a quick boot app to reboot in to recovery. DON'T DO IT!
chidochuck said:
I had the same problem with Sprint note 2 and i just went to download screen and then flashed the cwm tar file and then all was good. Whew!!! Thought I bricked it! I made the mistake of using a quick boot app to reboot in to recovery. DON'T DO IT!
Click to expand...
Click to collapse
Just bought a ATT GN2... coming from SkyRocket... on the SR, I used to always use "Quick Boot" app to reboot, or reboot into CWM Recovery. When you reference "quick boot app", are you referring to this? When my GN2 arrives, want to be sure I avoid using "Quick Boot" app if it doesn't play well on the GN2 and JB. Thx.
DoctorQMM said:
Just bought a ATT GN2... coming from SkyRocket... on the SR, I used to always use "Quick Boot" app to reboot, or reboot into CWM Recovery. When you reference "quick boot app", are you referring to this? When my GN2 arrives, want to be sure I avoid using "Quick Boot" app if it doesn't play well on the GN2 and JB. Thx.
Click to expand...
Click to collapse
Most of the custom ROMs here use the built in 4 way Rebooter so ya really shouldn't need a quick boot program
Sent from my SGH-I317 using xda premium
I've had rom tools boot loop the phone after a font change. Moral of the story-nandroid.
Sent from my SAMSUNG-SGH-I317 using Tapatalk 2
That's the one I used. Wish I knew why it happened.
Sent from my SPH-L900 using xda app-developers app
Much like the others here I rooted my T-mobile galaxy s3. The root worked fine and all. Then I downloaded this font changer app (I forget the name but it required a root) I go on to select a font then I go on to reboot like it said. Then bam, my phone gets stuck on the samsung screen. I then proceeded to use odin to put the stock image back on it (I think that's what it's called) It went through. I also did the factory wipe via the recovery screen. But now my phone would turn on, show "Samsung Galaxy S3," go to a black screen, play the t-mobile jingle, and the only thing that happens is the LED flashes but still nothing on the screen. I've tried virtually everything and I still think there is something else I need to do.
Help please?
I had a similar problem, this is what I did. Try and boot into cwr by hilding the vol up +power+home when it vibrates let go. Now u should b in cwr. Now wipe everything, dalvic, factory wipe fix permission. And flash a new rom cm10 will do..
Sent from my SGH-T999 using xda premium
kipster3001 said:
I had a similar problem, this is what I did. Try and boot into cwr by hilding the vol up +power+home when it vibrates let go. Now u should b in cwr. Now wipe everything, dalvic, factory wipe fix permission. And flash a new rom cm10 will do..
Sent from my SGH-T999 using xda premium
Click to expand...
Click to collapse
The problem is that he may be rooted but doesn't have cwm recovery.
If that's the case then you need to flash cwm recovery first.
I would also try flashing stock rom again or after flashing cwr download nandroid backup of stock rom.
Good luck and let us know if that worked
Sent from my SGH-T999 using xda app-developers app
HajmeR said:
The problem is that he may be rooted but doesn't have cwm recovery.
If that's the case then you need to flash cwm recovery first.
I would also try flashing stock rom again or after flashing cwr download nandroid backup of stock rom.
Good luck and let us know if that worked
Sent from my SGH-T999 using xda app-developers app
Click to expand...
Click to collapse
That sounds like a reasonable solution. Can I get a link to the CWM recovery file as well as a guide to it so I don't dig myself into a deeper hole? lol
Actually if you're stock recovery, factory reset should wipe everything. Including internal sd, just so you know.
If that doesn't work it'd probably be cleaner to just odin the root66 fw. But if you prefer the other way, you can find recovery files at the top of post 2 in the fw thread. Root66 is at the top of post 1.
I still need to add a few recoveries so if you don't see one you want let me know.
Sent from my SGH-T999 using xda premium
DocHoliday77 said:
Actually if you're stock recovery, factory reset should wipe everything. Including internal sd, just so you know.
If that doesn't work it'd probably be cleaner to just odin the root66 fw. But if you prefer the other way, you can find recovery files at the top of post 2 in the fw thread. Root66 is at the top of post 1.
I still need to add a few recoveries so if you don't see one you want let me know.
Sent from my SGH-T999 using xda premium
Click to expand...
Click to collapse
OMG!!! It is working now!!! Thank you so so so much!!!! lol
Hey guys,
Was trying to root my stock T-Mobile Galaxy S3, and everything was going fine but after it rebooted from Odin, the screen stayed black, and only the blue LED was pulsing. I assume it has something to do with my phone being on 4.1.1 and the S3 toolkit not liking that. I tried to flash the stock Rom to get it out of this, but now the same thing is still happening. I have tried multiple cache wipes/factory resets and multiple other stock ROMs. I always without fail get the same thing Samsung splash screen/Blue pulsing LED/start up sound and black screen. I'm getting really frustrated and worried. Can anyone help?
Misfit77 said:
Hey guys,
Was trying to root my stock T-Mobile Galaxy S3, and everything was going fine but after it rebooted from Odin, the screen stayed black, and only the blue LED was pulsing. I assume it has something to do with my phone being on 4.1.1 and the S3 toolkit not liking that. I tried to flash the stock Rom to get it out of this, but now the same thing is still happening. I have tried multiple cache wipes/factory resets and multiple other stock ROMs. I always without fail get the same thing Samsung splash screen/Blue pulsing LED/start up sound and black screen. I'm getting really frustrated and worried. Can anyone help?
Click to expand...
Click to collapse
That's actually the exact problem I just solved. You would need Odin 3.04 (well that's what I used) and you need to flash root66 like one of the previous posters here said. It recovered my phone AND rooted it. So try that and tell us what happened.
treythetree said:
That's actually the exact problem I just solved. You would need Odin 3.04 (well that's what I used) and you need to flash root66 like one of the previous posters here said. It recovered my phone AND rooted it. So try that and tell us what happened.
Click to expand...
Click to collapse
When I try the root66 it fails in odin. I used the root66_TMO_T999UVDLJA one. First, I had toolkit convert it into a .tar. Then I chose option 8 to flash a stock rom. I skipped ahead to flashing the rom and factory reset like it prompted. Then I tried to flash the .tar and it fails. ..:/. I don't know what else to do.
Misfit77 said:
When I try the root66 it fails in odin. I used the root66_TMO_T999UVDLJA one. First, I had toolkit convert it into a .tar. Then I chose option 8 to flash a stock rom. I skipped ahead to flashing the rom and factory reset like it prompted. Then I tried to flash the .tar and it fails. ..:/. I don't know what else to do.
Click to expand...
Click to collapse
Actualy I don't use toolkit so I might be wrong, but I don't think you need to convert root66 to tar. Just skip the toolkit. Put your phone into download mode, open odin, connect your phone to pc and flash root66. Check root66 thread for some info about unziping it or converting to anything. All info should be in op. If there is nothing about it then flash it as it is. Make sure that you have phone drivers installed and turn off kies.
I hope it helps.
Sent from my SGH-T999 using xda app-developers app
---------- Post added at 07:05 PM ---------- Previous post was at 06:49 PM ----------
I've just checked root66 thread. You don't have to convert it or unzip it. Just flash as it is. Your problem might came from converting that file to tar.
Sent from my SGH-T999 using xda app-developers app
Misfit77 said:
When I try the root66 it fails in odin. I used the root66_TMO_T999UVDLJA one. First, I had toolkit convert it into a .tar. Then I chose option 8 to flash a stock rom. I skipped ahead to flashing the rom and factory reset like it prompted. Then I tried to flash the .tar and it fails. ..:/. I don't know what else to do.
Click to expand...
Click to collapse
Unzip the fw using 7zip. Then odin flash the .tar.md5 file you just extracted.
Sent from my SGH-T999 using xda premium
Don't use toolkit for that just go to root66 thread. Download everything what you need from there and follow steps in 2 post under odin use.
Good luck
Sent from my SGH-T999 using xda app-developers app
Originally Posted by Misfit77
When I try the root66 it fails in odin. I used the root66_TMO_T999UVDLJA one. First, I had toolkit convert it into a .tar. Then I chose option 8 to flash a stock rom. I skipped ahead to flashing the rom and factory reset like it prompted. Then I tried to flash the .tar and it fails. ..:/. I don't know what else to do.
Click to expand...
Click to collapse
Actualy I don't use toolkit so I might be wrong, but I don't think you need to convert root66 to tar. Just skip the toolkit. Put your phone into download mode, open odin, connect your phone to pc and flash root66. Check root66 thread for some info about unziping it or converting to anything. All info should be in op. If there is nothing about it then flash it as it is. Make sure that you have phone drivers installed and turn off kies.
I hope it helps.
Sent from my SGH-T999 using xda app-developers app
---------- Post added at 07:05 PM ---------- Previous post was at 06:49 PM ----------
I've just checked root66 thread. You don't have to convert it or unzip it. Just flash as it is. Your problem might came from converting that file to tar.
Sent from my SGH-T999 using xda app-developers app
Click to expand...
Click to collapse
Thanks for the help, I'll try it when o get home.
Sent from my WX435 using xda app-developers app
Actually I was a bit wrong, like DocHoliday wrote, you just have to unzip it and use tar.md5 file inside. The rest is as I wrote before.
Good luck and let us know how it went
Sent from my SGH-T999 using xda app-developers app
HajmeR said:
Actually I was a bit wrong, like DocHoliday wrote, you just have to unzip it and use tar.md5 file inside. The rest is as I wrote before.
Good luck and let us know how it went
Sent from my SGH-T999 using xda app-developers app
Click to expand...
Click to collapse
It worked!!! Thank you both so much!! I was really getting frustrated.
Misfit77 said:
It worked!!! Thank you both so much!! I was really getting frustrated.
Click to expand...
Click to collapse
Good to hear that! If you will have some problems with sgs3 in the future you can pm me and I will try to help. Just saying that because I'm not looking into q&a very often. Good luck and happy flashing
Sent from my SGH-T999 using xda app-developers app
HajmeR said:
Good to hear that! If you will have some problems with sgs3 in the future you can pm me and I will try to help. Just saying that because I'm not looking into q&a very often. Good luck and happy flashing
Sent from my SGH-T999 using xda app-developers app
Click to expand...
Click to collapse
I will, thanks again!
Did the same thing
I did the same thing. I used the toolkit and was distracted by my son which ended up in me skipping over areas I thought I read and missed the part about JellyBean creating soft-brick.. It did install CWM though . Low and behold, I soft-bricked my phone with the pulsing blue LED from HELL. I kept having issues flashing everything, luckily the toolkit DID install CWM for me which was of no help. When I used Odin 3.0.4 it worked flawlessly with the stock rooted t999 rom which I have attached along with Odin 3.0.4.
Here is how to fix your soft-brick with the black screen and blue LED from hell:
1.) Download files attached and EXTRACT > root66_TMO_T999UVDLJA.7z AND Odin_3.0.4_Files.zip
2.) Boot into download updates screen by pressing and holding Home Button, Volume Down Button, and Power Button at same time until you boot into downloading updates screen.
3.) Plug in your phone to your pc
4.) Open Odin 3.0.4 make sure Auto Reboot and F . Reset Time are checked
5.) Click the PDA button at the right, select boot-stock-tmobile-sgh-t999
7.) Click the START button.
8.) Repeat Steps 2-4
9.) Click the PDA button at the right, select root66_TMO_T999UVDLJA.tar.md5
10.) Click the START button and you should see it install things you never saw before like BOOT, SYSTEM, MODEM, etc. (not in that order) at the top left where it shows installation progress (that little green rectangle)
I am trying to upgrade my Virgin ROM to the 9.12 build but get a fail upon trying to flash it. The background.... I'm using TWRP recovery and have tried the chainfire root method. Here are the results:
As you can see you can see some conflicting information... all shots were taken in sequence. I'm thinking the fail in twrp is coming from the system not having root but the info is telling me otherwise....
Bump... Anybody???
Sent from my GT-I9505G using xda app-developers app
th3h0ff said:
Bump... Anybody???
Sent from my GT-I9505G using xda app-developers app
Click to expand...
Click to collapse
Do you have the latest SuperSU version?
I'm a little lost at what you are saying.
You flashed a rom, and it said fail, and you think it has to do with Root?
If you have TWRP installed it doesn't matter if you are rooted or not. It's going to over right the system partition regardless if you have root or not.
So it's either a bad download or bad transfer for it to fail.
Sent from my SGH-M919 using Tapatalk 4
I do have the latest SU version by chain fire. And maybe I'm doing something wrong the because I am running the virgin gpe ROM now and that flashed in twrp with no issues. Now when I go to install (after wiping) and select the 9.12 update that I downloaded it hangs on trying to open the zip and fails... I haven't changed any twrp settings but in the write options of twrp what boxes should be checked because system is not by default... Thanks for the replies!
Sent from my GT-I9505G using xda app-developers app
I previously only used cwm so I'm not sure if I should just try that or what... And I've checked the download and md5 for verification
Sent from my GT-I9505G using xda app-developers app
th3h0ff said:
I previously only used cwm so I'm not sure if I should just try that or what... And I've checked the download and md5 for verification
Sent from my GT-I9505G using xda app-developers app
Click to expand...
Click to collapse
You can give CWM a try, I've been using it for a while without any issues. Out of curiosity what version if TWRP you are using? I think most people recommend TWRP 2.5.0.2. I'm using the latest version of CWM.
Sent from my GT-I9505G using xda app-developers app
If all else fails, just start from scratch, get stock UVUAMDL tar, flash it with Odin, make sure to do a factory wipe after you flash it, sometimes bootloops occur if you don't. You don't even have to go past the first screen where you pick the language. Just shut it down from there and boot into download mode and root with Chainfire with Odin, then shut down and boot up again into download mode again and flash custom recovery tar of ur choice with Odin. Then download whatever custom rom zip and install it via custom recovery.
norml said:
If all else fails, just start from scratch, get stock UVUAMDL tar, flash it with Odin, make sure to do a factory wipe after you flash it, sometimes bootloops occur if you don't. You don't even have to go past the first screen where you pick the language. Just shut it down from there and boot into download mode and root with Chainfire with Odin, then shut down and boot up again into download mode again and flash custom recovery tar of ur choice with Odin. Then download whatever custom rom zip and install it via custom recovery.
Click to expand...
Click to collapse
Thanks again to everyone... not going to have time to mess with it tonight but I'll update tomorrow. Thanks again
th3h0ff said:
Thanks again to everyone... not going to have time to mess with it tonight but I'll update tomorrow. Thanks again
Click to expand...
Click to collapse
heyyy saw your reply in my thread.
just as @byron1985 suggested there, it sounds like you got a bad download. the flashing scripts are essentially exactly the same from previous version. the flashing process has absolutely zero to do with SuperSU.
edit: re-read. so you've verified the download. if you had success with CWM previously, i would go back to that. i do not use TWRP.
mrvirginia said:
heyyy saw your reply in my thread.
just as @byron1985 suggested there, it sounds like you got a bad download. the flashing scripts are essentially exactly the same from previous version. the flashing process has absolutely zero to do with SuperSU.
edit: re-read. so you've verified the download. if you had success with CWM previously, i would go back to that. i do not use TWRP.
Click to expand...
Click to collapse
Im going to give the twrp 2.5.2 a try as it seems most of my troubles keep happening on the 2.6.3 build. Hopefully that works either way its back to CWM for me as well. Thanks again for taking the time to help out and again sorry about hijacking the thread for a page... Your ROM is absolutely perfect so I appreciate the efforts and time!,
Andrew
SOLVED... tried 2.5 version of TWRP and all went well... odd but apparently my device doesnt like 2.6 versions of TWRP! Thanks to everyone who helped me out and gave me suggestions and thank you to the dev for taking some of his time to assist! It was a great help to me!
th3h0ff said:
SOLVED... tried 2.5 version of TWRP and all went well... odd but apparently my device doesnt like 2.6 versions of TWRP! Thanks to everyone who helped me out and gave me suggestions and thank you to the dev for taking some of his time to assist! It was a great help to me!
Click to expand...
Click to collapse
Good to know you are out of trouble
Sent from my Nexus 10 using xda app-developers app
See you shoulda said you were running 2.6.3 lol
word of advice (and to all who run twrp)
DO NOT RUN ANYTHING GREATER THAN 2.5.2!!!!!!!!!!!!!!
I accidentally installed the wrong kernel on my Galaxy Note 2 (T-Mobile T-889). I think it was a kernel for a GT-N7100. With the installation of this wrong kernel, it changed my custom recovery from TWRP to "Devil Recovery". This recovery does work, and I am able to do things with it. With it, I reinstalled the original kernel back and the phone is working (whew!!). So all is well in that regard, but I cannot seem to fix the recovery back to TWRP. When I use the Devil Recovery to install the TWRP zip (which worked ok before) it fails. I tried using Goo Manager as well, but it also fails. Is there a way to wipe this recovery so that I can reinstall TWRP??
Thank you in advance!
Wingmann
Try flashing TWRP tar via odin.
Sent from my SGH-T889 using xda app-developers app
ciphercodes said:
Try flashing TWRP tar via odin.
Sent from my SGH-T889 using xda app-developers app
Click to expand...
Click to collapse
Good thought, and I apologize that I didn't write that into my original question. I did try to use Odin, but since the phone (sort of) thinks its now a GT-7100, I haven't been able to get Odin to recognize (connect) to the phone. I'll keep working at it!! Thank you for the idea though!
Wingmann
wingmann said:
Good thought, and I apologize that I didn't write that into my original question. I did try to use Odin, but since the phone (sort of) thinks its now a GT-7100, I haven't been able to get Odin to recognize (connect) to the phone. I'll keep working at it!! Thank you for the idea though!
Wingmann
Click to expand...
Click to collapse
You could try mobile Odin then there's no problem with connecting
Sent from my LG-D959 using Tapatalk
Basically I do have common sense and and I'm pretty knowledgeable when it comes to working with phones but this problem I have is different.
I purchased this phone(I747) already bricked thinking I can fix since I have before. It goes to cwm 6.0.3.4 and boots to Odin. Last known os was cm but don't know what version. Not even clear what bootloader it's but when trying to boot up there's the blue cm Android guy.
So here's what I tried so far to fix my problem.
1. Tried to flash the mjb restore posted somewhere on here. Flashed with no errors but when I reboot still the blue Android.
2. Wipe and formatted the proper things and tried flashing a couple of roms but all gave me error 7.
3. Tried flashing a different recovery thru Odin, all passed but non stuck. Can't get rid of my current recovery.
4. Tried to Odin 4.3 firmware but that failed.
Kinda running out of ideas on what to try next, can someone help me figure out what I'm doing wrong or what's the problem?
Sent from my SM-N900T using XDA Premium 4 mobile app
donutkidd said:
Basically I do have common sense and and I'm pretty knowledgeable when it comes to working with phones but this problem I have is different.
I purchased this phone(I747) already bricked thinking I can fix since I have before. It goes to cwm 6.0.3.4 and boots to Odin. Last known os was cm but don't know what version. Not even clear what bootloader it's but when trying to boot up there's the blue cm Android guy.
So here's what I tried so far to fix my problem.
1. Tried to flash the mjb restore posted somewhere on here. Flashed with no errors but when I reboot still the blue Android.
2. Wipe and formatted the proper things and tried flashing a couple of roms but all gave me error 7.
3. Tried flashing a different recovery thru Odin, all passed but non stuck. Can't get rid of my current recovery.
4. Tried to Odin 4.3 firmware but that failed.
Kinda running out of ideas on what to try next, can someone help me figure out what I'm doing wrong or what's the problem?
Sent from my SM-N900T using XDA Premium 4 mobile app
Click to expand...
Click to collapse
What did you try to flash? Status 7 means you don't have the right device for what you were trying to flash or that your build.prop was modified by the previous owner to another device name.
I believe you'll need to flash a ROM matching the current device name and work from there.
Although, I find it odd that flashing with Odin doesn't work. Have you tried flashing stock?
BWolf56 said:
What did you try to flash? Status 7 means you don't have the right device for what you were trying to flash or that your build.prop was modified by the previous owner to another device name.
I believe you'll need to flash a ROM matching the current device name and work from there.
Although, I find it odd that flashing with Odin doesn't work. Have you tried flashing stock?
Click to expand...
Click to collapse
Yep I tried stock 4.1.1 and 4.3 thru Odin and failed. I tried installing a new recovery thru the current recovery using a zip file and it went thru with no errors but reboot and nothing has changed. Something when flashing the restore and the bootloader.
Sent from my SM-N900T using XDA Premium 4 mobile app
donutkidd said:
Yep I tried stock 4.1.1 and 4.3 thru Odin and failed. I tried installing a new recovery thru the current recovery using a zip file and it went thru with no errors but reboot and nothing has changed. Something when flashing the restore and the bootloader.
Sent from my SM-N900T using XDA Premium 4 mobile app
Click to expand...
Click to collapse
You can try flashing another/updated recovery through Odin. But until you find out what device your build.prop is setup to, you won't be able to flash a ROM through recovery.
BWolf56 said:
You can try flashing another/updated recovery through Odin. But until you find out what device your build.prop is setup to, you won't be able to flash a ROM through recovery.
Click to expand...
Click to collapse
I tried every recovery for this phone that's up to date so yeah I don't know what else to do. And how can I figure that out? The build.prop part?
Sent from my SM-N900T using XDA Premium 4 mobile app
donutkidd said:
I tried every recovery for this phone that's up to date so yeah I don't know what else to do. And how can I figure that out? The build.prop part?
Sent from my SM-N900T using XDA Premium 4 mobile app
Click to expand...
Click to collapse
It's in your System folder. Should be able to navigate to it using your recovery.
BWolf56 said:
It's in your System folder. Should be able to navigate to it using your recovery.
Click to expand...
Click to collapse
Will it still be there even if I formatted the system? If so what are the adb commands so I can pull it and post it?
donutkidd said:
Will it still be there even if I formatted the system? If so what are the adb commands so I can pull it and post it?
Click to expand...
Click to collapse
Hopefully it is. And I duno about the command, you'll have to look that one up (or perhaps someone here knows it).
If you formatted /system, its gone and shouldn't matter. But imo you should never format system manually. Otherwise you end up with nothing to boot or troubleshoot if things go wrong.
From your recovery, find where you can use the terminal emulator and enter
getprop ro.boot loader
This is what firmware you need to be flashing via odin.
Sent from my SGH-T999 using Tapatalk
Ok I will try that when I get home.
Sent from my SM-N900T using XDA Premium 4 mobile app
DocHoliday77 said:
If you formatted /system, its gone and shouldn't matter. But imo you should never format system manually. Otherwise you end up with nothing to boot or troubleshoot if things go wrong.
From your recovery, find where you can use the terminal emulator and enter
getprop ro.boot loader
This is what firmware you need to be flashing via odin.
Sent from my SGH-T999 using Tapatalk
Click to expand...
Click to collapse
Ok I did the getprop ro.bootloader command and it's I747UCDLK3. I have already tried the lk3 Odin but let me try to re download a fresh copy of it.
Sent from my SM-N900T using XDA Premium 4 mobile app
No dice, I even downloaded a 4.1.1 lk3 rom. It flashed and said successful so I rebooted and back to the blue Android. Is it possible NY partitions or whatever are corrupt and if so anyway to fix it?
Sent from my SM-N900T using XDA Premium 4 mobile app
I'm kinda at a loss. Wondering if its a partition not flashed by Odin that's been corrupted...
No idea if this'll help or not, but download this.
http://www.androidfilehost.com/?fid=23060877489996938
(It is a 16gb model right?)
Now flash firmware in Odin in like usual, but check the repartition checkbox, then click the PIT button and browse to and select the file I just linked. Verify.
Click start and cross fingers.
Another thing you can try...flash twrp with Odin, but uncheck auto reboot. After it says PASS, pull the battery. Put it back in and boot recovery. Hopefully it'll stick now.
Now you can try flashing some roms again, and use the built in file manager to look for any issues/anomalies.
I'm not sure what version LK3 is, but it sounds kinda old, so you may want to look for a 4.1.1 rom to start with. That shouldn't give you any status 7 errors. Or if you want to flash newer roms you'll need to edit the asserts in the updater script.
DocHoliday77 said:
I'm kinda at a loss. Wondering if its a partition not flashed by Odin that's been corrupted...
No idea if this'll help or not, but download this.
http://www.androidfilehost.com/?fid=23060877489996938
(It is a 16gb model right?)
Now flash firmware in Odin in like usual, but check the repartition checkbox, then click the PIT button and browse to and select the file I just linked. Verify.
Click start and cross fingers.
Another thing you can try...flash twrp with Odin, but uncheck auto reboot. After it says PASS, pull the battery. Put it back in and boot recovery. Hopefully it'll stick now.
Now you can try flashing some roms again, and use the built in file manager to look for any issues/anomalies.
I'm not sure what version LK3 is, but it sounds kinda old, so you may want to look for a 4.1.1 rom to start with. That shouldn't give you any status 7 errors. Or if you want to flash newer roms you'll need to edit the asserts in the updater script.
Click to expand...
Click to collapse
I honestly think I tried what you suggested already but just to triple check I will do so again in the morning and report back with hopefully good news.
Sent from my SM-N900T using XDA Premium 4 mobile app
@BWolf56
Do you guys have a recovery flashable package for the 4.1.1 or 4.1.2 firmware? (I'm guessing that's what LK3 is.)
If so maybe flashing that would help?
DocHoliday77 said:
@BWolf56
Do you guys have a recovery flashable package for the 4.1.1 or 4.1.2 firmware? (I'm guessing that's what LK3 is.)
If so maybe flashing that would help?
Click to expand...
Click to collapse
No, nothing for 4.1.1 (LK3).
I don't think that's his issue though. Last time I saw that issue was on the S1 (Captivate) and the solution was to use Heimdall.
If the repartition doesn't work though, I'm not exactly sure what will.
DocHoliday77 said:
@BWolf56
Do you guys have a recovery flashable package for the 4.1.1 or 4.1.2 firmware? (I'm guessing that's what LK3 is.)
If so maybe flashing that would help?
Click to expand...
Click to collapse
I was just reading what you said in this post - > ([Q] Can't flash stock rom through Odin, phone only boots in download mode. Help!) and it does sound awfully like my situation being that nothing sticks after flashing.
donutkidd said:
I was just reading what you said in this post - > ([Q] Can't flash stock rom through Odin, phone only boots in download mode. Help!) and it does sound awfully like my situation being that nothing sticks after flashing.
Click to expand...
Click to collapse
Do you have the actual link to that thread? Search is derping on me.
BWolf56 said:
Do you have the actual link to that thread? Search is derping on me.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2415409
Sent from my SM-N900T using XDA Premium 4 mobile app
donutkidd said:
http://forum.xda-developers.com/showthread.php?t=2415409
Sent from my SM-N900T using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Ouff that's one bad issue, it can take a while to figure out which partition got messed up. And sadly, I can't be much help there :/