So here's the back story. I'm usually good with roms/recovery/flashing. Even did some custom rom work on my old Galaxy S 4G, so not a noob. I have a Wind T999V.
Had Touch-CWM installed, ran a few 4.4 ROM's for a while, tried LP, Liquid smooth. Liked it ok, but wanted to try OctoROM LP. It needs TWRP. Had a few problems with TWRP before on my phone, the Wind variant seems somewhat different in small ways, but figured I'd give it a try again to flash OctoROM since it needs TWRP. Thought maybe the TWRP has improved since I tried last, so installed TWRP, tried to flash Octo, but TWRP wouldn't see my internal SD card at all. The same problem I had before. I didn't feel like digging out a SD card from my camera to put Octo on, so rebooted the phone, installed CWM back, rebooted again, got a bootloop somewhere along the way.
Figured I'd go with Odin back to stock and start over. Grabbed odin (hard now, lots of spam/scam copies) and my stock firmware for the Wind version from Doc's thread. Flash the tar, which took forever (used a sort of crappy cable) and it auto rebooted after like 20 mins of flashing, just stuck at the sammy logo for like 20 mins. Too long, still looped I think.
Grabbed a different cable and a newer version of a good odin I know from my network I had laying around, 3.09, and tried again. At the pulsing samsung logo again, going to wait, but if I did softbrick it, do I need to repartition and a pit file to get the FS back to something different than any of the KK or LP rom's I ran?
EDIT:
Read some threads and took doc's advice and booted into stock recovery and wiped data and cache, and it finally booted. Phew.
Related
So I decided to try out the new cyanogen mod 7.1. I followed These instructions and everything went fine until it was time for the phone to reboot after heimdall's flash.
It didnt reboot, but stayed on the splash screen. I could still both boot in recovery (recovery was CVM) and download. I thought everything was ok, and put the cyanogen-update zip onto the external memory card. However, as all of you (and now I) already know, it doesnt work that way, as the zip has to be on the internal SD.
"Sucks to be me" I thought, but I applyed the update.zip that was already on the card, hoping that it would reset everything (did a factory wipe as well). It didnt.
So, I started kies, set the phone to download and hoped. Kies detects the phone, but it couldnt connect (it just tries infinitly). So, here comes the retard part: I found a guide for installing the same kernel with odin, so I tried that. Odin found the device, but stopped right after (SetupConnection). So, I pulled the battery, waited 5 minutes, and the dreaded "download error" came up. So I restarted the phone, tried to put it in download mode, and it worked! So, now Im back at square retard, becuase heimdall can still flash it and kies still finds the phone (without succeding in connecting), but it doesnt do anything else.
So: what do I do? At the present, I am prepared to settle for stock everything, as long as I get my phone back (I will probably try to install cyanogen again, and come back with new questions, but that is a later problem).
Thanks in advance<3
Prob better posting this in General or on a CM 7 thread/post...
You shouldn't have a problem flashing a stock rom with odin. Just remember to pick repartition, with the correct pit file for the rom.
Sent from my GT-I9000 using XDA App
I was messing with my Gs2, trying out some new roms (it has been rooted and custom flashed since i got the phone a while ago) and ended up with a soft brick getting stuck at the Samsung screen during boot. No big deal I though (since this is my backup phone I didnt worry about it) and planned on flashing back to stock with Odin and starting over. I flashed the stock 4.1 via odin and it all seemed to go fine, but when it rebooted it got stuck at the same samsung screen. I left it there for like 20 minutes and it never booted. I then downloaded the stock 4.0 and same thing. I am about to try going back in time to the stock 2.3 and see if i can work my way forward from that, but if it doesnt work, what is the cause of the phone not being able to boot after all these stock flashes?
jay-red said:
I was messing with my Gs2, trying out some new roms (it has been rooted and custom flashed since i got the phone a while ago) and ended up with a soft brick getting stuck at the Samsung screen during boot. No big deal I though (since this is my backup phone I didnt worry about it) and planned on flashing back to stock with Odin and starting over. I flashed the stock 4.1 via odin and it all seemed to go fine, but when it rebooted it got stuck at the same samsung screen. I left it there for like 20 minutes and it never booted. I then downloaded the stock 4.0 and same thing. I am about to try going back in time to the stock 2.3 and see if i can work my way forward from that, but if it doesnt work, what is the cause of the phone not being able to boot after all these stock flashes?
Click to expand...
Click to collapse
Im stuck in the same boat with my S4
which ODIN version are you using and are you using the links from SAMMOBILE to get the firmware you need ? also what are your methods of procedure and is odin giving out any errors or saying pass and still no boot ?
So, i have a Samsung Galaxy S III i747... Flashed it with CyanogenMod, and saw horrible battery life, and the phone stayed hot... Flashed back to an older version of CyanogenMod, and it was just unstable and a mess, so i formatted everything from recovery, and installed the stock ROM via Odin... Stock ROM worked, but i wanted back to Cyanogen, so i rooted the phone, downloaded the ROM manager, downloaded the ROM, and installed it... And it failed. So, i figured i'd hit the NAND Erase All button in Odin, and then repartition the phone, thinking the buttons wouldn't blow up the world... Now i'm stuck at the Samsung logo at boot. I've tried several different versions of the stock ROM, i can still get into recovery, and i can still get into download mode, but it always get stuck at the Samsung Logo after the AT&T carrier video.
Anyone have any ideas? I'm really hoping i didn't brick my phone... Odin sees it, and everything still works, i just can't boot the stock ROM, which means i can't get anywhere else.
try a factory reset in recovery after flashing rom
PhoneTamer said:
So, i have a Samsung Galaxy S III i747... Flashed it with CyanogenMod, and saw horrible battery life, and the phone stayed hot... Flashed back to an older version of CyanogenMod, and it was just unstable and a mess, so i formatted everything from recovery, and installed the stock ROM via Odin... Stock ROM worked, but i wanted back to Cyanogen, so i rooted the phone, downloaded the ROM manager, downloaded the ROM, and installed it... And it failed. So, i figured i'd hit the NAND Erase All button in Odin, and then repartition the phone, thinking the buttons wouldn't blow up the world... Now i'm stuck at the Samsung logo at boot. I've tried several different versions of the stock ROM, i can still get into recovery, and i can still get into download mode, but it always get stuck at the Samsung Logo after the AT&T carrier video.
Anyone have any ideas? I'm really hoping i didn't brick my phone... Odin sees it, and everything still works, i just can't boot the stock ROM, which means i can't get anywhere else.
Click to expand...
Click to collapse
I Odin'd to stock a couple days ago and was at the Samsung Logo for a WHILE (over and hour). It did just go eventually.
Not sure what did it... Got a PIT file, and then did the NAND Erase All bit again when i installed the stock ROM again. Wiped data as soon as install finished, and it booted right up. I'm happy again
Now if i can just figure out the LTE glitch...
Okay so heres the dealio. I am not a noob been rooting, flashing etc. since Cyanogen was actually Cyanogen back in the G1 and Mytouch days. I have read every tutorial available. I have tried Kies, Odin, different USB cords, various drivers, nandroid backups etc. I was on the 5.0 unoffical cyanogen rom I think it was 12-08 or 06. NB4 "MODEM" had the coveted MDL Baseband. I was running CWM recovery. was setting alarms whole screen turned bright pink and froze so I pulled battery waited several minutes, rebooted and it would make it to cm splash screen then go pink and reboot.
First thing I did was try all of my nandroid backups none did any good. Of course I wiped everything before restoring
Second tried several Roms I know worked I always keep a couple on SD just in case ones I have tested and are working
Third I tried to Odin to MDL passed boot loop did this several times with sd and without I even uninstalled kies to make sure no interference
After that I just started climbing firmware mk2, NB4, NH7 all same results. I did each one multiple times evry which way you can imagine
I tried multiple Roms 4.4.2 4.4.4 etc to no avail
Finally I tried Kies. Kies Upgraded me to NK2 still boot loop. Odin NK2 still boot loop.
I have tried super wiping then installing boot loop
I can get into DOWNLOAD MODE AND RECOVERY MODE NO PROBLEM. I can flash custom recovery through odin no problem I have tried Cwm I have tried Twrp. Twrp gives me more options.
Now I have had some success.... If I do it perfectly I usually have to format everything with aromas mega wipe takes a few attempts I can get Danvdh GE 4.4.4 Rom to boot but it constantly vibrates if i do anything like reboot it or anything back to boot loop.
I have checked my pit file and compared to a stock pit everything matches perfectly so I dont think any partitions are screwed..
Knox is tripped who cares its past warranty I am on NK2 firmware. I dont care if I am stuck on stock or some custom rom. I need my phone to work just dont have money to buy a new one.
Please help me. I am not a noob if I have to rebuild the whole system using ADB I will just need some guidance.
****UPDATE***** Currently Have SOPK 4.4.4 from Unified Dev up and running.... No audio at all, much more stability, occasionally freezes will bootloop unless plugged into usb on computer.
***********LOGCATS************* https://drive.google.com/folderview?id=0B479jD3Q_BOvZWYtRDZ2bjBZN2M&usp=sharing
Try this. Flash MDL baseband, flash NK2 with Odin, reboot to recovery and factory reset. After that perform a reboot and see if it works. This has seemed to work for a few people that had updated just the baseband and then later tried to flash full firmware and got stuck in bootloops
do you happen to have link to MDL baseband I have the NK2 firmware
I did find this I want to make sure I have the right one http://forum.xda-developers.com/showthread.php?t=2282342
Also am I flashing these back to back then reboot or flash MDL reboot to download then flash NK2? Just dont want to screw myself any further. Thank you very much for your help Thanks button hit 100x
Yeah that's the one, and just flash the modem, once it's done, do a battery pull, boot straight back into download mode and flash it again. After that, flash full NK2 firmware
Tried it twice with Odin 3.07 and 3.09 still looping.
I do remember having to push the NB4 Modem with ADB while maintaining the MDL baseband if that has anything to do with it.
I saw a pink screen scenario once after water damage on my nephews s4 (not saying you have water damage ) but phone never recovered, not even after disassembly and clean, had limited function, had to be replaced.
Pp
There was never water damage. Its hard to believe that its hardware since I can get dl mode and recovery no problem. But anything is possible. I only get the pink screen now when I try to reflash the 5.0 Cyanogen
ok right now ive got Danvidh GE 4.4.4 pure nexus up and running. its doing a little vibration loop every 30-60 seconds. i have a bug report for whoever wants it. i also have a recovery log from twrp. i'll leave it up and running until i get some advice. i do know if i reboot itll kick into boot loop.......
Update: Ive got about 15 minutes of logcat. and it did reboot on its on back into rom still doing the vibration loop. it freezes randomly no audio. Ill keep running logcat and keep this puppy up till I hear from someone.....
Ok so I'm posting from my SGH-M919. The one with problems. Here's what I think happened, I think while on The 5.0 CM ROM I received the lollipop OTA. This is just a guess as I'm seeing people have been getting OTA notifications for this Device. I'm not sure what I should do. I've done extensive debugging. All hardware looks good from what I can tell. I have tons of logcats and debug files for anyone willing to help. As of now still running DanvidH. 4.4.4 GPE pure nexus version baseband NK2. The vibrations continue. Apparently its due to Google play service update in the last 24 hours and this ROM. Since its literally the only thing that will run on here I'll keep it for now. It freezes constantly, cannot use it as a phone either as it just freezes on the way to dialer. Anyway hopefully someone can help...... Thanks
Sent from my GT-I9505G using XDA Free mobile app
Can you share a link to this 5.0 cm rom?
Just curious.
### Edit ###
Never mind just found it in development.
Pp.
---------- Post added at 09:21 AM ---------- Previous post was at 08:35 AM ----------
Just looking over this 5.0 Cm rom I get the impression that this is chuck full of bugs, since the beginning back on 11/13 and just 2 hrs ago op posted an update with potential bugs still present. If I had to have a reliable operating phone this is one rom I wouldn't touch.
Any input from op?
Pp.
http://forum.xda-developers.com/showthread.php?t=2539361&page=458 just got uploaded last night follow instructions explicitly look at last or so post
Can you check what bootloader and modem you have now? Upload the logcat right before the reboot happened
OK so I am able to run the 5.0 much more stable. Dialer crashes no audio at all system or other wise. It froze then rebooted and back to bootloop which logcats do you want i couldnt get catlog to run on 5.0 but I have about 3 hours worth of logcats from the 4.4.4 pure nexus. what logcats would you like. I also have adb setup and http://www.xda-developers.com/android/advanced-logcat-published-as-a-standalone-tool/ it was running great on 4.4.4 but couldnt get it to retrieve on 5.0
I did get about 2 hours of smoothness from 5.0 just no sound and dialer crashes no one else reporting issue. Texts work fine
NK2 boot loader with Twrp recovery
whats really really weird is I have to connect the phone to computer after flashing to get it to actual start the rom
Well I am truly stumped, I'm not new to flashing phones I've been flashing rooting and repairing androids for 6 years but have never seen this happen. Came across a tmobile t889 note 2 that had Jedi Master on it and it was bootlooping. (not sure which jedi master I think x2) first I tried to boot into recovery, saw the twrp logo then it just rebooted went back to booting jedi. So I tried to reflash twrp through odin... Nothing, same thing. So then I tried to flash cwm, odin said success no errors but goes right back to twrp, tried philz, same thing. Tried the stock 4.1 rom, 4.3 rom basically every stock rom available, each time odin says success and yet each time jedi master and twrp remain. I tried every single version of odin from 1.85-3.12. I just don't know what else to try, I can't find any threds with even a similar problem except one from an s3 and the solution was only return to samsung... Anyone have sny ideas? Note:it's s not a power button issue the phone doesn't turn off when booting jedi master just syayscon the jedi master bootscreen indefinitely.
Just an update my problem remains, but I found the t889 pit that didn't work, tried to uncheck auto reboot and manually reboot that didn't work. Gave up on odin and tried heimdall with both the command line and the user interface, same thing flashed successfully but nothing really flashed. If anyone has ever used the windows program "deep freeze" It seems like as if that's what happened to the phone... No matter what you flash it just reverts back. I even went as far as trying to purposely brick it by flashing an impropper kernel, I know what that would have done but I just had to see, but nope... Didn't brick... Did nothing... Still has twrp still has jedi master still boot loops
If anyone is interested in seeing a visual of the problem I made a video https://www.youtube.com/watch?v=W3zL069w8io
were you able to solve this?
Just went through this
I was changing roms
And this happened.
Odin the latest Twrp for your phone and do all the rules
Flash the exact Rom that was on it before.
That worked on my t889
You'll probably get partition mount problems..wasn't an issue for me....couldn't flash anything but that Rom.
I'm on jedi x2
It probably had a dual boot