Develop Bugs

Galaxy S 3 Rom installation Problem

I have a problem with my Galaxy S 3
When i bought it out the box i was able to root easily and install custom rom (Wicked) with no problems but then i had to restore back to stock using ODIN returning back to stock and running everything stock i also reset the counter beause i wanted to exchange the phone turn out i cannot
so i re-rooted the phone the same way and tried to install the custom rom it gave me status 7 error he only thing that worked is my Backups
so i returned back to stock again and re-root this time i didnt have the error i just get stuck at the boot logo
i have no idea what to do now. its very frustrating.

ChronoXzX said:
I have a problem with my Galaxy S 3
When i bought it out the box i was able to root easily and install custom rom (Wicked) with no problems but then i had to restore back to stock using ODIN returning back to stock and running everything stock i also reset the counter beause i wanted to exchange the phone turn out i cannot
so i re-rooted the phone the same way and tried to install the custom rom it gave me status 7 error he only thing that worked is my Backups
so i returned back to stock again and re-root this time i didnt have the error i just get stuck at the boot logo
i have no idea what to do now. its very frustrating.
Click to expand...
Click to collapse
same problem i had before. Bothered me for a few days.
1. download rooted stock ROM
2. download goo manager
3. user twpr to flash wicked ROM
hope this will help

Had that problem after Odin reboot into stock recovery and erase and reset, had to do it 2 days ago
Sent from my SGH-T999 using xda app-developers app

theory611 said:
same problem i had before. Bothered me for a few days.
1. download rooted stock ROM
2. download goo manager
3. user twpr to flash wicked ROM
hope this will help
Click to expand...
Click to collapse
Can you link me the rooted stock rom that you used
Plz ive tried everything its real annoying that my phone wont boot the custom rom
Its installed successfully but nothing after the reboot just the logo screen of the custom rom

Did you wipe the cache/dalvik?

psykhotic said:
Did you wipe the cache/dalvik?
Click to expand...
Click to collapse
Yeah I did
I do factory setting then I wipe cache then I do the dalvik cache
Then I finally install I do it everytime it doesnt work. Is it because maybe I unroot the phone wrong??? Is that even possible?? Lol

Try This:
http://forum.xda-developers.com/attachment.php?attachmentid=1404381&d=1350325570
Flash this TWRP Recovery Through ODIN, and try to reinstall the ROM

DroidDonX said:
Try This:
http://forum.xda-developers.com/attachment.php?attachmentid=1404381&d=1350325570
Flash this TWRP Recovery Through ODIN, and try to reinstall the ROM
Click to expand...
Click to collapse
ill try that when i get home
but note so far no rom has been working i can successfully install it with no errors
but when it wants to boot nothing happens just stuck at the Logo screen :/
i think its because i unroot using odin the wrong way or something idk but ever since i un rooted the device this started to happen..

I think status 7 error is a md5 mismatch. Redownload the rom you want. Also some people have had issues downloading to the phone so use a pc and transfer it.

jcbofkc said:
I think status 7 error is a md5 mismatch. Redownload the rom you want. Also some people have had issues downloading to the phone so use a pc and transfer it.
Click to expand...
Click to collapse
Ok ill do that but what if I dont get the error the rom finishes installing and the aroma installer says status 0 I do not know what it means

There are a couple possibilites here.
1) Your recovery is outdated. Update it. CWM will work just as well as TWRP. A lot of people have been advertising TWRP like they are being paid to do so. Either will work fine, but it must be updated to the latest version. The "CWM makes you lose IMEI" slander is starting to get old as well. There have been several documented cases on this forum where people have lost IMEI using TWRP. That's of course assuming the custom recoveries are actually causing it. We don't even know that. In any case, a reboot nvbackup would prevent all of this nonsense. I can't believe people still aren't doing this.
2) You are attempting to flash roms that are not for your device. Please give us a forum link to the rom you are attempting to flash.

Aerowinder said:
There are a couple possibilites here.
1) Your recovery is outdated. Update it. CWM will work just as well as TWRP. A lot of people have been advertising TWRP like they are being paid to do so. Either will work fine, but it must be updated to the latest version. The "CWM makes you lose IMEI" slander is starting to get old as well. There have been several documented cases on this forum where people have lost IMEI using TWRP. That's of course assuming the custom recoveries are actually causing it. We don't even know that. In any case, a reboot nvbackup would prevent all of this nonsense. I can't believe people still aren't doing this.
2) You are attempting to flash roms that are not for your device. Please give us a forum link to the rom you are attempting to flash.
Click to expand...
Click to collapse
I would gladly take this slightly off course and ask you to find me one with the issue, as I've read lots and lots about the issue, it is and has been a CWM issue. Here are the Docs Spreadsheet
https://docs.google.com/spreadsheet/ccc?key=0Arzp20hXNPi4dFg3UUozS2FQaERYNVJRVm1hWmJYQ3c#gid=0
and here is the huge thread about the issue
http://forum.xda-developers.com/showthread.php?t=1794657&highlight=imei

Aerowinder said:
There are a couple possibilites here.
1) Your recovery is outdated. Update it. CWM will work just as well as TWRP. A lot of people have been advertising TWRP like they are being paid to do so. Either will work fine, but it must be updated to the latest version. The "CWM makes you lose IMEI" slander is starting to get old as well. There have been several documented cases on this forum where people have lost IMEI using TWRP. That's of course assuming the custom recoveries are actually causing it. We don't even know that. In any case, a reboot nvbackup would prevent all of this nonsense. I can't believe people still aren't doing this.
2) You are attempting to flash roms that are not for your device. Please give us a forum link to the rom you are attempting to flash.
Click to expand...
Click to collapse
I have the latest CMW recovery touch
tried it with both of the recoveries same deal :/
and the ROm im trying to flash is
http://forum.xda-developers.com/showthread.php?t=1804260
ANd noob question what happens when i lose my Imei?? does it brick or prevent installation?

ANd noob question what happens when i lose my Imei?? does it brick or prevent installation?
Click to expand...
Click to collapse
Might as well be a brick. Just back it up the way I said and you don't need to worry about it.
mt3g said:
I would gladly take this slightly off course and ask you to find me one with the issue, as I've read lots and lots about the issue, it is and has been a CWM issue. Here are the Docs Spreadsheet
https://docs.google.com/spreadsheet/ccc?key=0Arzp20hXNPi4dFg3UUozS2FQaERYNVJRVm1hWmJYQ3c#gid=0
Click to expand...
Click to collapse
This spreadsheet doesn't prove anything. I see 18 CWM IMEI losses. 3 of which are on CWM v6. Out of 116 users reporting. The vast majority of reporting users are using CWM with success. This is hardly evidence. If anything, it implies CWM is more popular than TWRP. But, there is no proof of that in the spreadsheet, either. You would need thousands of reporting users to establish any kind of usable baseline. Last I checked, no one is sure why the IMEI loss happens or what, exactly, causes it. People do have their suspicions (or superstitions), though. I've flashed hundreds of files with CWM, and never had a single issue. And so have thousands of other XDA forum members.
and here is the huge thread about the issue
http://forum.xda-developers.com/showthread.php?t=1794657&highlight=imei
Click to expand...
Click to collapse
What about it? I think I posted a backup script there a couple months ago.

Aerowinder said:
Might as well be a brick. Just back it up the way I said and you don't need to worry about it.
This spreadsheet doesn't prove anything. I see 18 CWM IMEI losses. 3 of which are on CWM v6. Out of 116 users reporting. The vast majority of reporting users are using CWM with success. This is hardly evidence. If anything, it implies CWM is more popular than TWRP. But, there is no proof of that in the spreadsheet, either. You would need thousands of reporting users to establish any kind of usable baseline. Last I checked, no one is sure why the IMEI loss happens or what, exactly, causes it. People do have their suspicions (or superstitions), though. I've flashed hundreds of files with CWM, and never had a single issue. And so have thousands of other XDA forum members.
What about it? I think I posted a backup script there a couple months ago.
Click to expand...
Click to collapse
But no one lossed it using TWRP, that's my only point. With out a doubt CWM is more popular, think of it this way. More people are going to respond and or look for a thread regarding the issue compared to those (TWRP) users who never had the issue, I've been on CWM for a couple weeks try to lose my IMEI and haven't done so yet. Either way I'm not defending either but trying to help people out.
Sent from my SGH-T999 using xda premium

When installing a Rom it just flashes through is that normal?
doesnt it usually take like 2 or 3 minutes to flash a rom that big?
because almost everyone rom i try
Darthstalker
furioustock
wicked
aeonflux
when i format everything using this guide
http://forum.xda-developers.com/showthread.php?t=1946701
The installation for the rom just takes 1 to 2 seconds i that normal?
since i used to have a samsung nexus s it usually takes about 1 - 2 minutes to flash a rom that is greater than 100mb
i just wanted to know maybe that can spark any conclusions.
i am still failing to install a rom and seeing it boot up pass the boot screen.. i really need help please :/
the recovery does not give me any errors at all its installed " successfully "

It should take at least 20 to 45 seconds.
Sent from my SGH-T999 using xda premium

mt3g said:
It should take at least 20 to 45 seconds.
Sent from my SGH-T999 using xda premium
Click to expand...
Click to collapse
My phone takes 2 seconds to flssh it says starting flash please wait then it says complete about 2 seconds later

ChronoXzX said:
My phone takes 2 seconds to flssh it says starting flash please wait then it says complete about 2 seconds later
Click to expand...
Click to collapse
which is why it isn't working, how large are the files, what are download steps you are taking? Which recovery... You might have a borked recovery... Try reinstalling the recovery if all else seems normal.

mt3g said:
which is why it isn't working, how large are the files, what are download steps you are taking? Which recovery... You might have a borked recovery... Try reinstalling the recovery if all else seems normal.
Click to expand...
Click to collapse
the files that im trying to install into my phone are about 600mb +
the wiked rom is about 809mb
the darthstalker rom is about 776mb
im using internet download manager to download the roms
ive reinstalled the recovery via the apps ( rom manager and goomanager )
nothing seems to work :/

SGS III L710 Unable to Mount /anything

A strange predicament indeed. Two identical SPH-L710 phones, both came packaged running 4.1.2 build MD4 and, using this toolkit, I was able to successfully root, flash TWRP recovery and proceed to flash a custom ROM with no issues...at least to one of the phones.
My problems began with the second device. I was able to successfully root and flash recovery (TWRP or CWM) here as well. I question the success of the recovery flash due to the picture as indicated where I get numerous 'unable to...' everything. I might also add that on recovery entry TWRP asks for a password. I am not bricked as I can boot normally into the OS and use the rooted phone. I feel like I have tried everything I could find on this forum as well as several other sites to no avail. I have downgraded to 4.1.1 build LJ7 with the exact same results. I have repartitioned as well. Right now the second device is running build LJ7 since I have come to a screeching halt until I find more things to flash and hack away at this stubborn thing!
This is by no means my first bout with the Android platform, but if anyone can give me a pointer or two to set me on the right path, I will gladly hand out some thank yous!!

I had the same issue on mine. Dropping back to TWRP 2.3.1 solved it for me. Some L-710s just seem to not like the updated version.
Sent from my SPH-L710 using XDA

You can try Flash Image GUI from the Play Store. Or maybe even Rom Manager. Then Uninstall it when you are done.

jdonmc1948 said:
I had the same issue on mine. Dropping back to TWRP 2.3.1 solved it for me. Some L-710s just seem to not like the updated version.
Sent from my SPH-L710 using XDA
Click to expand...
Click to collapse
I initially flashed all the way back to the TWRP build before 2.3.1 but stopped there. I'll report back with results of your recommendation in the morning!
prboy1969 said:
You can try Flash Image GUI from the Play Store. Or maybe even Rom Manager. Then Uninstall it when you are done.
Click to expand...
Click to collapse
ROM Manager was something I tried as a last resort as well, it flashed the custom recovery alright, but soft bricked it with a redundant recovery bootloop. I got past that by Odin-ing back to stock.

Odd. I've used the Toolkit you mentioned in your OP. Also the other methods to install a Recovery. Did you manage to Root again, and install a Recovery ?

prboy1969 said:
Odd. I've used the Toolkit you mentioned in your OP. Also the other methods to install a Recovery. Did you manage to Root again, and install a Recovery ?
Click to expand...
Click to collapse
Yes, I can easily root every time with Mark's toolkit as well as install a recovery, but I always get the 'unable to mount...' message when I attempt to do anything and it will not recognize neither the internal nor the external sdcard.
jdonmc1948 said:
I had the same issue on mine. Dropping back to TWRP 2.3.1 solved it for me. Some L-710s just seem to not like the updated version.
Sent from my SPH-L710 using XDA
Click to expand...
Click to collapse
UPDATE: Still in the same boat even after flashing all the way back to TWRP 2.2.2.0. Recovery can't find or mount anything!
Although I'm not sure why (since I used the same methods and the same toolkit on both phones), I have a feeling that the internal memory and/or partitions somehow got corrupted. The only thing I haven't tried is using Odin to repartition and reflash everything including the bootloader. Hopefully someone has posted the files for us!

n3td3v said:
Yes, I can easily root every time with Mark's toolkit as well as install a recovery, but I always get the 'unable to mount...' message when I attempt to do anything and it will not recognize neither the internal nor the external sdcard.
UPDATE: Still in the same boat even after flashing all the way back to TWRP 2.2.2.0. Recovery can't find or mount anything!
Although I'm not sure why (since I used the same methods and the same toolkit on both phones), I have a feeling that the internal memory and/or partitions somehow got corrupted. The only thing I haven't tried is using Odin to repartition and reflash everything including the bootloader. Hopefully someone has posted the files for us!
Click to expand...
Click to collapse
I believe you can do that with mskip's Toolkit. I would also reformat the SD Card. To format the SD Card you can use SD Formatter.

prboy1969 said:
I believe you can do that with mskip's Toolkit. I would also reformat the SD Card. To format the SD Card you can use SD Formatter.
Click to expand...
Click to collapse
I tried formatting the sdcard as well as without the sdcard and even with a different one to no avail. I'm still on the hunt for pda, csc, etc. Odin files. My last resort will be to figure out how to get it replaced at Sprint as a defective device lol
Sent from my SPH-L710 using xda premium

Have you tried using stock recovery? obviously not to flash anything but just to try and navigate the sd or wipe the cache for example. Just curious if the mounting issues are present in all recoveries or just twrp/cwm. Also a bit intrigued by the fact that the phone still boots and operates normally
Sent from my SPH-L900 using xda premium

billard412 said:
Have you tried using stock recovery? obviously not to flash anything but just to try and navigate the sd or wipe the cache for example. Just curious if the mounting issues are present in all recoveries or just twrp/cwm. Also a bit intrigued by the fact that the phone still boots and operates normally
Sent from my SPH-L900 using xda premium
Click to expand...
Click to collapse
Yes, stock recovery allows clearing of cache, depending on whose stock recovery I flash. If I flash the toolkit version of stock, I can clear no problems. There are a couple of other stock recoveries, such as this one, in which everything fails as well.
FYI, I have even flashed the stock builds you have on sxtp with the same results.

Thanks for this -- you solved my problem...at least mostly.
I tried to root a new Sprint SG3 by ODIN'ing CWM and then flashing a root.zip file. That epic failed just like your situation where nothing would mount in recovery whether I used CWM or TWRP. I am assuming that something must've changed on the Sprint S3's and that root method must not work anymore (for whatever reason). So I decided to go back to stock recovery and just wait and see if anything further is discovered about this here (I'm not a dev, so I have to wait for other more talented people to solve my problems). However, the stock recovery image that I downloaded from the same "Easy Root" tutorial here didn't work and I still couldn't mount anything.
Saw your post where you stated that the Toolkit stock recovery image worked, so I just tried that and score! However...my poor little recovery android is on his back with a red triangle and a "!". Everything mounts, I can wipe cache, browse around for an update, etc., but I'm a little concerned that my little Android is sick. Should I be? Is that because I have a flash count of 5 so it thinks I have a custom ROM?
Sorry to hijack your thread a little, but my problems seems to be related.

n3td3v said:
A strange predicament indeed. Two identical SPH-L710 phones, both came packaged running 4.1.2 build MD4 and, using this toolkit, I was able to successfully root, flash TWRP recovery and proceed to flash a custom ROM with no issues...at least to one of the phones.
My problems began with the second device. I was able to successfully root and flash recovery (TWRP or CWM) here as well. I question the success of the recovery flash due to the picture as indicated where I get numerous 'unable to...' everything. I might also add that on recovery entry TWRP asks for a password. I am not bricked as I can boot normally into the OS and use the rooted phone. I feel like I have tried everything I could find on this forum as well as several other sites to no avail. I have downgraded to 4.1.1 build LJ7 with the exact same results. I have repartitioned as well. Right now the second device is running build LJ7 since I have come to a screeching halt until I find more things to flash and hack away at this stubborn thing!
This is by no means my first bout with the Android platform, but if anyone can give me a pointer or two to set me on the right path, I will gladly hand out some thank yous!!
Click to expand...
Click to collapse
I just got a brand new GS3 today and am having the exact same problem you describe. I have rooted several GS3s before... normally is child's play. I am a bit embarrassed to get stuck here. CWM nor TWRP mount anything... major bummer. TWRP prompts me for a password as if it thinks it is an encrypted /data partition... strange.

swiggs98 said:
I just got a brand new GS3 today and am having the exact same problem you describe. I have rooted several GS3s before... normally is child's play. I am a bit embarrassed to get stuck here. CWM nor TWRP mount anything... major bummer. TWRP prompts me for a password as if it thinks it is an encrypted /data partition... strange.
Click to expand...
Click to collapse
Same boat. Rooted probably 6 S3 before now and my wife's new S3 I am seeing same thing.
Sent from my SPH-L900 using xda app-developers app

I'm having the same issue. I finally downloaded an image that allowed me to flash it but I still cannot mount anything in recovery? Any help would be nice

Thanks guys, it is comforting to know I'm not the only poor soul stuck in this rut! I'm pretty sure I have exhausted all flashing resources out there at this point, but I'm eager to try whatever new that has potential of working that anyone cares to conjure up.
One strange thing I have also noticed on the problematic phone is that the signal is significantly weaker than my phone, even when both were at stock. It is always dropping calls and/or going into roaming, etc. I haven't been able to produce a log of any sort as they won't write since recovery cannot mount ANYTHING! Lol

n3td3v said:
Thanks guys, it is comforting to know I'm not the only poor soul stuck in this rut! I'm pretty sure I have exhausted all flashing resources out there at this point, but I'm eager to try whatever new that has potential of working that anyone cares to conjure up.
One strange thing I have also noticed on the problematic phone is that the signal is significantly weaker than my phone, even when both were at stock. It is always dropping calls and/or going into roaming, etc. I haven't been able to produce a log of any sort as they won't write since recovery cannot mount ANYTHING! Lol
Click to expand...
Click to collapse
Folks, A quick search would have led ya here : http://forum.xda-developers.com/showthread.php?t=2183910&page=4 This is a known issue with both TWRP and CWM recoveries on newer S3's. Devs are working on it to find a solution. Just a matter of being patient and waiting. IF you just want root access, you can odin a pre-rooted rom to the phone with no issues. You'll atleast have root at that point. Just unable to change rom/kernels on the fly.

I achieved root with virtually no issues but thank you for the link!
Sent from my SPH-L710 using xda premium

[Q] how to install a modem in android 4.3 ATT SGH-i747 SGS3

hello
i flashed a leaked version of ATT android 4.3 for my galaxy s3 2 days ago and everything work great except the data won't work and i can't open the option to create new access point it tells me insert sim ..after couple research i found out i have to install the modem in the link below
http://www.androidfilehost.com/?fid=23196940996968656
but my problem is my CWM recovery doesn't install it and keep telling me INSTALLATION ABORTED any help please .. i really need data worked i'm with tmobile now my phone in unlocked and i need a custom access point

I had the same problem when flashing StockMOD, but it turns out I wasn't using the right modem file. I was using a 4.3 modem from the roll-up sticky thread and not the file from the StockMOD thread. Once I flashed that one, everything worked as it should.
I use TWRP for my recovery, so you might try that.
Also, I'm on ATT, not TMobile. You may want to go through all the pages of the thread where you got your ROM to see if there is anything about using that ROM on TMobile. It might be that you flashed a modem that is not really compatible with your device. I'm new to this whole flashing thing though, so all I can really say is read read read. I spent all afternoon yesterday reading the entire StockMOD thread and other posts before trying to flash, so that I would feel comfortable in what to expect. Good Luck!
Cymbrogi

Cymbrogi said:
I had the same problem when flashing StockMOD, but it turns out I wasn't using the right modem file. I was using a 4.3 modem from the roll-up sticky thread and not the file from the StockMOD thread. Once I flashed that one, everything worked as it should.
I use TWRP for my recovery, so you might try that.
Also, I'm on ATT, not TMobile. You may want to go through all the pages of the thread where you got your ROM to see if there is anything about using that ROM on TMobile. It might be that you flashed a modem that is not really compatible with your device. I'm new to this whole flashing thing though, so all I can really say is read read read. I spent all afternoon yesterday reading the entire StockMOD thread and other posts before trying to flash, so that I would feel comfortable in what to expect. Good Luck!
Cymbrogi
Click to expand...
Click to collapse
I did tried the exact modem they created for the room and posted it with the rom.. but I just can't install it it tells me installation aborted and I just downloaded TWRP but still when i reboot in recovery mod it will open CWM recovery

Just to be sure, you did flash TWRP to replace CWM, right? I have only had TWRP on my S3, but I'm pretty sure you can just flash TWRP over top of CWM, which will replace CWM. Of course, this means any backups you have made with CWM won't be able to be used with TWRP, but I'd save them anyway and just reflash CWM to recovery if you prefer that one.
I am surprised that CWM isn't installing the modem, however, since I can't believe there's any difference between TWRP and CWM in that process. Perhaps the modem from the thread is only for ATT?

[Q] [SOLVED] T-Mobile Samsung Galaxy S4 (SGH-M919) Soft-bricked

Hi all, hope you are doing well (I also hope that you can help me ).
I just recently got a replacement phone because my other one had a faulty speaker (crackling, etc.). The other one was rooted (via CF-AutoRoot) and had TWRP on it, and I made a complete nandroid backup of it onto my MicroSD card.
I rooted the new phone using CF-AutoRoot via Odin and installed TWRP on it as well (also via Odin). Then I swapped the SD card and SIM card and restored the complete backup to the new phone.
It took a while, but the phone booted up and I had two working clones, the only way to tell which was which was by changing the volume and hearing the crackling on the old one.
So the new phone worked all day (was able to make calls and everything, and the GUI that was customized with Wanam Xposed even looked good), however when I restarted it to put in my backup battery, I didn't have root for some reason. I tried and tried to get it back (reinstalled SuperSU, tried the TWRP method) to no avail.
I re-flashed CF-AutoRoot just to see, and the phone booted up but and for some reason SuperSU was gone (and I didn't have root). When I restarted, I got a boot loop and could not even get back into a recovery.
I got tired of this and wanted a fresh start, so I just flashed the stock ROM via ODIN and did a factory reset. However now if I try to boot, the Samsung logo will flash and just shut down, and I won't be able to get into the recovery no matter what. If I flash a recovery (CWM, TWRP or even stock), the recovery will work until I try to actually try to boot the phone. I've tried taking the battery out for a good 5 minutes and retrying (also tried swapping batteries), I've tried doing complete resets galore from all three recoveries mentioned with no success. Obviously Download mode still works so I know it's not completely bricked, but I am getting a little scared.
Any and all help is extremely appreciated as I would prefer not to have such an expensive paper-weight.
Thanks a bunch!

I would suggest going all the way back stock on stock firmware via Odin. Then re-root, TWRP, and re-download the rom of your choice. Dont restore the backup. Just start fresh.
I Think My S4 Is Insane
SICK MADE DEVELOPMENT

alloycowboy said:
I would suggest going all the way back stock on stock firmware via Odin
Click to expand...
Click to collapse
Thanks for the reply.
And okay, I tried that.
I flashed stock using the T-Mobile ROM I found here: galaxys4root_(dot)_com/galaxy-s4-stock-firmware/
This is the same ROM file I used to completely restore the phone I had to return, and that worked fine.
But it still won't boot up or go into recovery mode (just shows the Samsung logo for a split second before shutting down).
One thing I did do on the other phone was flash a kernel which had set-MUID to off so I could WiFi tether, but I thought flashing the stock ROM would revert that back as well. Do you think that's the reason it messed up so badly? I restored the backup from the other phone with a different kernel? Right after I restored the backup to the new phone and everything was working, I remember checking the kernel info in the About Phone section of the settings, and it was in fact the kernel I'd installed on the other phone.
TLDR: Tried flashing stock ROM to no avail. Download mode still works but can't enter recovery mode or boot.

Are you doing a factory reset after flashing stock firmware?
I Think My S4 Is Insane
SICK MADE DEVELOPMENT

I'd flash a stock rooted ROM. Get that root and recovery back. The konane tar file from the stickies, perhaps.
Sent from my SGH-M919 using xda app-developers app

alloycowboy said:
Are you doing a factory reset after flashing stock firmware?
Click to expand...
Click to collapse
Yeah, as soon as it finished installing I went into stock recovery and did a factory reset.
Karakoram2 said:
I'd flash a stock rooted ROM. Get that root and recovery back. The konane tar file from the stickies, perhaps.
Click to expand...
Click to collapse
Alright, I'll try that.
Is the konane tar an actual ROM? And what do you mean in the stickies?
Sorry, not very familiar with XDA forums.

Samsung GT-I9500 flashes n switches off!
BallisticallySimilar said:
Hi all, hope you are doing well (I also hope that you can help me ).
I just recently got a replacement phone because my other one had a faulty speaker (crackling, etc.). The other one was rooted (via CF-AutoRoot) and had TWRP on it, and I made a complete nandroid backup of it onto my MicroSD card.
I rooted the new phone using CF-AutoRoot via Odin and installed TWRP on it as well (also via Odin). Then I swapped the SD card and SIM card and restored the complete backup to the new phone.
It took a while, but the phone booted up and I had two working clones, the only way to tell which was which was by changing the volume and hearing the crackling on the old one.
So the new phone worked all day (was able to make calls and everything, and the GUI that was customized with Wanam Xposed even looked good), however when I restarted it to put in my backup battery, I didn't have root for some reason. I tried and tried to get it back (reinstalled SuperSU, tried the TWRP method) to no avail.
I re-flashed CF-AutoRoot just to see, and the phone booted up but and for some reason SuperSU was gone (and I didn't have root). When I restarted, I got a boot loop and could not even get back into a recovery.
I got tired of this and wanted a fresh start, so I just flashed the stock ROM via ODIN and did a factory reset. However now if I try to boot, the Samsung logo will flash and just shut down, and I won't be able to get into the recovery no matter what. If I flash a recovery (CWM, TWRP or even stock), the recovery will work until I try to actually try to boot the phone. I've tried taking the battery out for a good 5 minutes and retrying (also tried swapping batteries), I've tried doing complete resets galore from all three recoveries mentioned with no success. Obviously Download mode still works so I know it's not completely bricked, but I am getting a little scared.
Any and all help is extremely appreciated as I would prefer not to have such an expensive paper-weight.
Thanks a bunch!
Click to expand...
Click to collapse
The same thing has happened to me! Did you find any solustion for this?? Please help!! This was my first attempt and i have no idea wats going on!

Here are the stickies for our forum: http://forum.xda-developers.com/showthread.php?t=2419828
Sent from my SGH-M919 using XDA Premium 4 mobile app

What I did to unbrick my T-Mobile S4 (SGH-M919)
killerwolf2121 said:
The same thing has happened to me!
Did you find any solutions for this? Please help if you can; this was my first attempt and I have to idea what's going on.
Click to expand...
Click to collapse
Well, for the first problem, flashing the stock ROM did it for me. I followed this tutorial.
For the second issue of not booting up after displaying the Samsung logo; my battery just simply was too dead and didn't have enough juice to start. You have no idea how stupid I felt.
Let your phone charge from the wall cable for a good while before trying all this again; then see if that works. It did it for me. If it doesn't, I'm not sure what else to try.
After that (if it works), if you still want root, just flash CF-Auto-Root and then a custom recovery if you want (like ClockworkMod Recovery (click the little version link, not the "Download ROMs" button) or TWRP via GooManager) (I use TWRP)
All the best and let me know how it went!
Keep in mind that I did this on an SGH-M919 (T-Mobile S4) running Android 4.2.2, so if you don't have that, I have no idea if any of the above will work for you. Also I'm pretty sure if you do have 4.3, you will ruin your warranty forever due to the Knox restriction they added (if you haven't already).
Android_Monsters said:
Here are the stickies for our forum: http://forum.xda-developers.com/showthread.php?t=2419828
Click to expand...
Click to collapse
Thanks

BallisticallySimilar said:
Well, for the first problem, flashing the stock ROM did it for me. I followed this tutorial.
For the second issue of not booting up after displaying the Samsung logo; my battery just simply was too dead and didn't have enough juice to start. You have no idea how stupid I felt.
Let your phone charge from the wall cable for a good while before trying all this again; then see if that works. It did it for me. If it doesn't, I'm not sure what else to try.
After that (if it works), if you still want root, just flash CF-Auto-Root and then a custom recovery if you want (like ClockworkMod Recovery (click the little version link, not the "Download ROMs" button) or TWRP via GooManager) (I use TWRP)
All the best and let me know how it went!
Keep in mind that I did this on an SGH-M919 (T-Mobile S4) running Android 4.2.2, so if you don't have that, I have no idea if any of the above will work for you. Also I'm pretty sure if you do have 4.3, you will ruin your warranty forever due to the Knox restriction they added (if you haven't already).
Thanks
Click to expand...
Click to collapse
I am on 4.3 and yes, flashing the stock rom worked for me too! relief thanks a ton!

Having trouble unbricking M919 T-Mobile
Hi, I'm trying to unbrick my M919 through Odin. I have all the updated software, but I keep getting a fail message. Any help would be appreciated.

Stuck on Noterized rom and aosp. Battery life is horrible.

Hi, When I got my Note 4 it had stock lollipop. I was happy with it and it had great battery life but I wanted xposed so I found a tutorial for sprint note 4 lollipop. after i flashed xposed my phone got stuck in a boot loop and i didn't have a backup. i tried to Odin back to stock but that kept failing, i gave up and flashed noterized rom through TWRP. now i want to got back to stock or at least get a different rom (maybe Vision or hybrid i tried both) but i tried flashing a couple of different rom but they never work, my phone just keeps rebooting (goes to "Samsung galaxy note 4 powered by android" screen and then restarts i tried waiting 30 mins but no luck) however i am able to flash an AOSP rom but i don't like them i really like TW. what can i do to restore to stock, downgrade to 4.4.4, or flash vision rom?
for battery life i tried restarting, factory restore, clearing cache and dalvic cache, and formatting everything and re-flashing the rom but nothing seems to work.
if you have any question or need more information please ask. any help is appreciated

ismaeel96 said:
Hi, When I got my Note 4 it had stock lollipop. I was happy with it and it had great battery life but I wanted xposed so I found a tutorial for sprint note 4 lollipop. after i flashed xposed my phone got stuck in a boot loop and i didn't have a backup. i tried to Odin back to stock but that kept failing, i gave up and flashed noterized rom through TWRP. now i want to got back to stock or at least get a different rom (maybe Vision or hybrid i tried both) but i tried flashing a couple of different rom but they never work, my phone just keeps rebooting (goes to "Samsung galaxy note 4 powered by android" screen and then restarts i tried waiting 30 mins but no luck) however i am able to flash an AOSP rom but i don't like them i really like TW. what can i do to restore to stock, downgrade to 4.4.4, or flash vision rom?
for battery life i tried restarting, factory restore, clearing cache and dalvic cache, and formatting everything and re-flashing the rom but nothing seems to work.
if you have any question or need more information please ask. any help is appreciated
Click to expand...
Click to collapse
Youre stuck on Noterized. Enjoy.

No way out? What if somone gives me their back up?

I was stuck i tried different stock tar files from different sources. Finally found one that work the other tar files kept failing in odin. Your not stuck just go online and find the solution yourself . If it's not affecting anybody else they careless if you fix it man and that's with life too just sayin . Good help hard to come by nowadays

Might wanna go through the Q&As and rethink your post. As to avoid contradicting your post all together, could you at least provide a link to the file that got you unstuck to help in the first place.

I pm'ed the guy already

So what did you flash to get back to stock??....HmmmHmmm

EpicBarbecue said:
So what did you flash to get back to stock??....HmmmHmmm
Click to expand...
Click to collapse
so what I did was root using odin installed twrp from the playstore and flashed the twrp recovery from the app. once I had recovery I flashed a stock rom from the forum in twrp. that booted up fine then I hooked my phone into the pc and open kies to see if it reconized my phone and it did so I hit the tools tab at the top of the program and clicked on firmware upgrade and initialization and it stared updating my phone back before the oel update
credit: @bonebeatz1234

I have a update I flashed off of stock and went back then flashed cm12 and the method I used earlier didn't work I was stuck for 2 hours. I flashed a tw rom in twrp when it finished installing I pulled the battery and flashed the modem from bob firmware and bootloader before I restarted the phone I found a bootloader and modem from bob firmware on the forum flashed both and both failed but from what I cant tell it installed enough for the phone to reboot on back on tw and from there I used kies to get back on stock 2nd time bringing it back very long process just finding the right solution

xxSTARBUCKSxx said:
so what I did was root using odin installed twrp from the playstore and flashed the twrp recovery from the app. once I had recovery I flashed a stock rom from the forum in twrp. that booted up fine then I hooked my phone into the pc and open kies to see if it reconized my phone and it did so I hit the tools tab at the top of the program and clicked on firmware upgrade and initialization and it stared updating my phone back before the oel update
credit: @bonebeatz1234
Click to expand...
Click to collapse
So you were actually able to downgrade from OE1? What stock rom did you flash that actually booted up? Thanks.

Yeah i was on hybrid x. I saw someone needed help so i tried to mess my phone up to replicate what the guy did yes the method i used earlier works but only if your on a tw rom . So i flashed cm12 and was stuck before i got back on touchwiz yeah i see what people mean you can't flash ****. So i went to twrp flashed hybrid x didnt restart phone i pulled battery and went to odin and flashed the bob bootloader tar and modem tar i found on the forum i flashes both they both failed but one of them flashed about 75% on odin and i rebooted and tw was back then i went to kies upgraded to stock now back on stock. Unzip these and flash in odin https://www.dropbox.com/s/cvkynp4kmkw8f8c/bootloader lolipop and modem.zip?dl=0 hope this help but if you live in Rockford ,illinois i could just fix it for you

dteze88 said:
So you were actually able to downgrade from OE1? What stock rom did you flash that actually booted up? Thanks.
Click to expand...
Click to collapse
I personally havent been on OE1. A few people who havent been plagued by this horrible and unnecessary update have been trying to help those who have and are. The guy i mentioned at the bottom(of the post you quoted), those were his steps. But it seems some of the information has changed since that post. Look above this post and he explains the differences whether on TW or non TW rom.
One thing Samsung is telling us though through their actions, if theyre pushing out updates and its not over a GB, i wouldnt take it, or I'd at least wait until seeing the ramifications of the update through other users taking it, which there will always be.

ismaeel96 said:
Hi, When I got my Note 4 it had stock lollipop. I was happy with it and it had great battery life but I wanted xposed so I found a tutorial for sprint note 4 lollipop. after i flashed xposed my phone got stuck in a boot loop and i didn't have a backup. i tried to Odin back to stock but that kept failing, i gave up and flashed noterized rom through TWRP. now i want to got back to stock or at least get a different rom (maybe Vision or hybrid i tried both) but i tried flashing a couple of different rom but they never work, my phone just keeps rebooting (goes to "Samsung galaxy note 4 powered by android" screen and then restarts i tried waiting 30 mins but no luck) however i am able to flash an AOSP rom but i don't like them i really like TW. what can i do to restore to stock, downgrade to 4.4.4, or flash vision rom?
for battery life i tried restarting, factory restore, clearing cache and dalvic cache, and formatting everything and re-flashing the rom but nothing seems to work.
if you have any question or need more information please ask. any help is appreciated
Click to expand...
Click to collapse
Did you get it working?
---------- Post added at 01:55 PM ---------- Previous post was at 01:55 PM ----------
bonebeatz1234 said:
Yeah i was on hybrid x. I saw someone needed help so i tried to mess my phone up to replicate what the guy did yes the method i used earlier works but only if your on a tw rom . So i flashed cm12 and was stuck before i got back on touchwiz yeah i see what people mean you can't flash ****. So i went to twrp flashed hybrid x didnt restart phone i pulled battery and went to odin and flashed the bob bootloader tar and modem tar i found on the forum i flashes both they both failed but one of them flashed about 75% on odin and i rebooted and tw was back then i went to kies upgraded to stock now back on stock. Unzip these and flash in odin https://www.dropbox.com/s/cvkynp4kmkw8f8c/bootloader lolipop and modem.zip?dl=0 hope this help but if you live in Rockford ,illinois i could just fix it for you
Click to expand...
Click to collapse
So, were you on OE1 when you did this???

13druber said:
Did you get it working?
---------- Post added at 01:55 PM ---------- Previous post was at 01:55 PM ----------
So, were you on OE1 when you did this???
Click to expand...
Click to collapse
Fyi, the latest update tar just dropped today on Sammobile (OF5). Download, odin, and prosper again
Sent from my SM-N910P using Tapatalk

Androidious said:
Fyi, the latest update tar just dropped today on Sammobile (OF5). Download, odin, and prosper again
Sent from my SM-N910P using Tapatalk
Click to expand...
Click to collapse
Thank you sir, i did that yesterday. I am rooted and bloat ware removed.

13druber said:
Thank you sir, i did that yesterday. I am rooted and bloat ware removed.
Click to expand...
Click to collapse
Glad you were able to get back finally
Was getting worried that us N4 users would be stuck forever, LOL!
Sent from my SM-N910P using Tapatalk

Androidious said:
Glad you were able to get back finally
Was getting worried that us N4 users would be stuck forever, LOL!
Sent from my SM-N910P using Tapatalk
Click to expand...
Click to collapse
Me too.

Using noterized over of 5 it works ok