rooted vi las vegas method, and got team win clockmod recovery. Whiped catch and data factory reset before installing this room
The jelly bean domination, for samsung galaxy sprint note 3 n900p
phone boots to samsung....then freezes and reboots. Sometimes it loads past it, but message pops up saying system crashed close it or wait and then it reboots its self few seconds after that. And it is a nonstop rebooting at samsung logo
now i made it wrose, i deleted the nand through odin mode and it says could not do normal boot and just loads into odin mode
and then did solution, downloaded offcial sprint rom from that website that took 4 hours, added the md5 file and flashed with odin, and it came back to life
You sure you got a Rom for Sprint variant?
Sent from my SM-N900P using XDA Premium 4 mobile app
twrp is highly recommended. the way to fix your phone is to odin it back to stock before your phone boots...put your phone into STOCK recovery and wipe it...wipe everything which will get rid of the custom tag...put the phone in download mode and odin it back to stock a second time. reroot your phone and then odin in twrp..flash the new rom you want in twrp the phone should make it to the yellow screen with a semiblinking blue light and then it should boot within 5min
what happened was....i downloaded a rom for the model n9005 and it loaded on my phone no problem, only problem was their was no wifi and no mobile internet...then i tried restoreing the stock i backed up, and that created a bootloop. Then i found only for like the s4 they selected the delete nand option on odin and i did that 2....and then my phone couldnt normal boot went into odion mode right away. After downloading stock all night everything got fixed in 20 mins, then got home after work and put the jelly bean domination rom no problem
Related
Hi there.
I had a custom rom on my Galaxy S3, and I wanted to go back to stock rom. Before I had a custom rom, I checked my product code, just in case if I ever wanted to flash stock rom. So, I downloaded a stock rom from sammobile and flashed it with Odin. I had a successful flash, but when the phone rebooted, it stopped at the samsung logo and it's like that every time I turn on the phone.
I aslo tried to flash it with the same rom, but from a different site (androidfirmwares), but every time I treid to do that, Odin crashed ( Odin downloader has stopped working).
I can't even boot into CWR to flash any custom rom, cuz it's gone. There is only stock recovery.
Please help
Which Rom were you trying to flash when this happened, and give details of how you flashed please
luka46 said:
Hi there.
I had a custom rom on my Galaxy S3, and I wanted to go back to stock rom. Before I had a custom rom, I checked my product code, just in case if I ever wanted to flash stock rom. So, I downloaded a stock rom from sammobile and flashed it with Odin. I had a successful flash, but when the phone rebooted, it stopped at the samsung logo and it's like that every time I turn on the phone.
I aslo tried to flash it with the same rom, but from a different site (androidfirmwares), but every time I treid to do that, Odin crashed ( Odin downloader has stopped working).
I can't even boot into CWR to flash any custom rom, cuz it's gone. There is only stock recovery.
Please help
Click to expand...
Click to collapse
if you are getting stuck on the boot screen after you flashed the stock rom this always works..go to recovery do a data reset and wipe cache.
this is really weird and a stupid thing I did when I was completely new to android..a little over a month ago.I got stuck on the boot screen and accidentally flash CF-Root instead of the stock firmware..when the phone rebooted it worked just fine.I dont think its supposed to work that way..:S
ahmedmaaiee said:
if you are getting stuck on the boot screen after you flashed the stock rom this always works..go to recovery do a data reset and wipe cache.
this is really weird and a stupid thing I did when I was completely new to android..a little over a month ago.I got stuck on the boot screen and accidentally flash CF-Root instead of the stock firmware..when the phone rebooted it worked just fine.I dont think its supposed to work that way..:S
Click to expand...
Click to collapse
I did as you said and it works :laugh:
Thank you :good:
Please help me save my phone, if still possible. These are the things I had done with my phone before the scenario I am having right now:
1. I rooted my Samsung Galaxy S II GT - i9100 running ICS 4.0.3 DXLP9 using update.zip in CWM.
2. I then ported resurrection remix v3.0.9 and went along just fine.
3. My SIM card's data network mode doesn't work so I restored the stock ROM using the backup file of what I was previously using.
4. Steps 2 and 3 went on for about 8 times then I finally stopped on the stock ROM.
5. I decided to update it again but this time using official 4.0.4 xxwlpx firmware.
6. I downloaded mobile ODIN and then flashed the update there.
7. The flash was successful but while using the phone I get "com.android..... is not responding".
8. I decided to do a factory wipe, and then when the phone is rebooting, it got stuck on the samsung galaxy logo.
9. I proceeded to go to recovery mode and install RR again but still got stock on boot.
10. I gave up and handed the phone over to my friend and tried flashing through ODIN, still he can't perform data wipe.
11. I got the phone back and then looked for the problem. I found a method of using a modified PIT file and then proceeded to do just that.
12. Now I am back using my phone with 4.0.4 xxwlpx. But then I found out it has a brick bug so I decided to reinstall RR again using CWM.
13. Now I cannot use the phone again. Everytime I put my phone into recovery it says "failed to mount..system"
14. I then proceeded to flash PIT files for about 5 times but to no avail. I get stuck at flashing in "factoryfs.img".
15. Now I flashed one last PIT file hoping it would work. Now I am stuck at "Firmware update encountered an issue.....Kies & try again".
16. I brought the phone to a local jtag service but they weren't able to do anything with it. I only have a budget of 1500php (37USD). They said that changing the motherboard would cost 4500-5000php(107-120USD). They said it was the emmc. Changing the motherboard at the local samsung center costs 10500PHP(250SUSD). I'm still a student and don't have that much money.
17. I then flashed i9100_u1_02_20110310_emmc_EXT4-patched-standard PIT file. flashing went successfully.
18. I tried to flash stock 4.0.3 dxlp9 but got stuck at boot.bin.
And that led me to what I am dealing with now. "Firmware update encountered". If anyone here in XDA knows how to fix this, please help me. What did I do wrong? Do I still have a chance to get this fixed?
I am so sorry for being a noob.:crying:
Hi there,
I got my SGS3 on Friday, it took two hours until I got bored and rooted it.
First everything was fine, I was using CWM (installed via ROM Manager) and tried some ROMS.
Today, when I wanted to flash CWM Touch via ROM Manager, the phone rebooted and since then in stuck in a boot loop.
There was no error during the process, according to ROM Manager the recovery was properly flashed. All I can do is entering the Download Mode.
I tried to flash two different stock images via ODIN3 (v3.07) but the phone keeps rebooting, even when i try to repartition it using "GT-I9300_mx_20120329.pit". I can boot the phone into recovery, I can see the recovery for a short moment and then the phone reboots. I made it to flash CWM 6.0.3.1 via ODIN, and when booting into recovery then I can see that it worked, but after a second the phone reboots.
Currently I'm downloading a 3-part/3-files factory image, hoping this can help. According to what I've read on the forums so far I don't think it will change anything, but who knows... Any other suggestions?
Greetz
// j_dee
rom manager is not supported on all the phones. probably that should have damaged your phone. hope you get your phone working. good luck :good:
I was using CWM (installed via ROM Manager)
Remove rom manager .
CWM says
Not compatible with ROM Manager !
That is if you recover from damaged pit .
jje
Hey guys,
thanks so far... According to the CWM homepage the SGS3 is supported, in fact there's current even a newer CWM version available for SGS3 than for GNEX.
Fortunatly I just made it to un-soft-brick the device:
- Removed the battery for a few minutes, then placed it back in the phone (for some reason the phone often booted as soon as the battery was back in its place, so I had to be quick).
- Tried to reboot into recovery again, holding "Vol+"+"Home"+"Power" until the recovery showed up, and the phone rebooted.
- Kept on holding "Vol+"+"Home"+"Power" until recovery showed up again, for some reason the phone didn't reboot this time, and then I released all buttons.
- Thanks to ODIN I could now use CWM 6.0.3.1 to flash S4 Revolution (by Elegant Team) from my internal storage, rebooted the phone and it worked. All my data was still in place, so it seems all my attempts to flash the stock images via ODIN did not succeed, save for the stock recovery.
Crap, I was really afraid of having my brand-new SGS3 hard-bricked only a few days after delivery. With my HTC Desire HD it took me almost 6 months to cause the first almost-brick.
There's only one thing I can image with ms SGS3 that might have affected the CWM / ROM Manager flash - I was running a S4-ported ROM ("S4 Revolution"), because this makes "TriangleAway" recognize it as "I9500" phone, so I cannot reset the counter at the moment.
But ROM Manager always showed "GT-I9300"... So in the end I've no clue what has happened so far.
Greetz
// j_dee
don't use rom manager
I tried ODIN and successfully got it back to stock rom. But the phone keeps looping back to the Vibrant logo screen. The method I used worked for me for the past three years, it started acting weird when all of a sudden an ICS custom rom from MIUI hanged on me. And then I was unable to get my phone working!
Is my phone permanently bricked?!
MiniGunnR said:
I tried ODIN and successfully got it back to stock rom. But the phone keeps looping back to the Vibrant logo screen. The method I used worked for me for the past three years, it started acting weird when all of a sudden an ICS custom rom from MIUI hanged on me. And then I was unable to get my phone working!
Is my phone permanently bricked?!
Click to expand...
Click to collapse
Can you get into recovery? Did you flash a custom gb boot loader? You wipe data and cache? You could try Odin again and flash stock with the correct pit file and re partition checked I've done this many times and have not had this problem you might just have had a corrupt flash like I've read Odin has been known to fail
Verizon S4 MDK
Background: I was on an MIUI port for the verizon s4, Wanted to flash to Chaos rom 3.0, recovery "Failed out every time, updated TWRP to 2.8.01, flashed Chaos 3.0 ( This rom requires a non stock kernal), Forgot to install Kernal before flashing (partly because i thought I already had one)< rom flashed successfully, rebooted and got a blue screen with pixels all over, rebooted again and the phone sits at a black screen that blinks every 5 seconds and vibrates, can ONLY get to Download mode no recovery.
*tried flashing twrp in ODIN and it fails, even on different Odin versions.
I want to atleast be able to get to recovery again so i can save my internal memory files (pictures mostly), how can i get there?
Trying to use MDK no wipe in ODIN now.
MDK no wipe.tar worked, allowed me to access my files. Thanks for all the help I didnt get! hope this post helps someone down the road