This morning I tried to do the OTA update to the stable versions listed above. The device rebooted to the blue man and stayed there for 30 minutes I figured something was wrong so I took off the battery and restarted. Now it's stuck on blue man every time I boot up the phone. I can get into download and recovery mode, I tried doing a data wipe on the phone and see if it would work from there, and nothing. I'm debating what should I do from here? I want cyanogenmod on my phone so I was wondering if I could flash it from ODIN. Any advice would be appreciated.
Pretty much the same thing happened to me, except on the d2att version. Wish I could give more help than just saying I'm in the same boat, sorry.
same
update put phone in boot loop so im going with nightly builds
Related
hi guys i need some help i downloaded cyanogen 11 lastnight just because my phone kept prompting me to update and i was rooted. I installed it and immediately noticed that i can not see my sd card, after researching i saw a couple of people was having the same issue. I tried to recover from the backup i made and it make my phone get stuck in a endless loop after about 10 hours of trying to get in recovery and failing it finally let me in and started loading the rom again. I keep trying to replace the rom with other roms and the phone will not see any of roms to push i tried odin and that failed as well . can someone help me get this stupid rom off my phone i tried everything.
Darkmanx said:
hi guys i need some help i downloaded cyanogen 11 lastnight just because my phone kept prompting me to update and i was rooted. I installed it and immediately noticed that i can not see my sd card, after researching i saw a couple of people was having the same issue. I tried to recover from the backup i made and it make my phone get stuck in a endless loop after about 10 hours of trying to get in recovery and failing it finally let me in and started loading the rom again. I keep trying to replace the rom with other roms and the phone will not see any of roms to push i tried odin and that failed as well . can someone help me get this stupid rom off my phone i tried everything.
Click to expand...
Click to collapse
Which recovery are you running?
joeyhdownsouth said:
Which recovery are you running?
Click to expand...
Click to collapse
I got it, I finally got stock a rom to load via Odin but it was getting stuck on the Samsung screen so I rooted it before it even let me in. Then i did a wipe and it started up and now all is well stock 4.3 rooted. This reminded me why i always choose stock rooted roms
I recently installed CyanogenMod 11 on my S3 about a month ago. Yesterday, I got a notification on my phone stating that an update was available for CyanogenMod. I let it install and when the phone rebooted, it was stuck on the bootloader for at least an hour or two. I figured that I must've bricked the phone. I can still get into recovery mode and download mode.
So, I tried to reinstall the stock AT&T GS3 ROM as I had never particularly liked CyanogenMod. I thought this would be a great time to reinstall the stock ROM. I factory reset the phone and flashed the stock ROM (which I downloaded from another thread) using Odin. It automatically rebooted, the Samsung logo flashed for a second and the CyanogenMod bootloader showed up and it has not gone away since. So, what have I done wrong here and is there a way to save my phone? Any help would be greatly appreciated.
Where did you get the ROM you flashed? Did your phone have the 4.3 bootloader? What about Knox?
If your phone has the 4.3 bootloader, you cannot flash the 4.3 ROM via Odin as it was never released as a complete ROM, only as an update. THis might help: http://forum.xda-developers.com/showthread.php?t=2658486
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
Ok so I have a samsung galaxy s3 att and I have been rooted for the past month or so, no issues. Then, I decide to install a custom rom so I get a stable cm11 and attempt to flash it and it says my cwm version is too low so the reboot my phone so I can update it. The phone starts to boot and gets stuck on the att globe logo with the blue light pulsing. I shut off the phone, pull out the battery and try again, still nothing. I start getting scared so I restore the nandroid backup I made right before this custom rom incident and boot it, still gets stuck at the same place. I really need my phone fixed so can someone help me please??
I was talking to @sd_shadow on another forum earlier and was wondering if he could help me?
supy99 said:
Ok so I have a samsung galaxy s3 att and I have been rooted for the past month or so, no issues. Then, I decide to install a custom rom so I get a stable cm11 and attempt to flash it and it says my cwm version is too low so the reboot my phone so I can update it. The phone starts to boot and gets stuck on the att globe logo with the blue light pulsing. I shut off the phone, pull out the battery and try again, still nothing. I start getting scared so I restore the nandroid backup I made right before this custom rom incident and boot it, still gets stuck at the same place. I really need my phone fixed so can someone help me please??
I was talking to @sd_shadow on another forum earlier and was wondering if he could help me?
Click to expand...
Click to collapse
this thread may help
http://forum.xda-developers.com/showthread.php?t=2549068
"all i can really do , is stay out of my own way and let the will of heaven be done"
Don't panic
Grab the latest version of philz touch recovery https://goo.im/devs/philz_touch/CWM_Advanced_Edition/d2lte/
The zips are made to be flashed from a recovery like cwm. Install it using cwm, reboot into recovery and philz should come up. You should be able to proceed with wiping and installing your custom rom at this point.
If the zip doesn't work out for some reason, you could also use Odin to flash a .tar.md5 from that link to update your recovery.
Try this: http://forum.xda-developers.com/showpost.php?p=60162192&postcount=2
So previous to yesterday I had a fully working Galaxy S9 G960F, running the latest version of crDroid 11 (from 2021 heh), and something like TWRP 3.5.1? A fairly old version anyway, since I'd been running the same OS for the past year. I recently noticed someone had gotten 13 working on the S9, so I downloaded it and installed it like I'd done every other time installing a custom OS before, rebooted, and then the phone starts automatically going to recovery on boot, but gets stuck on the TWRP splash screen each time.
So I figured maybe the version of TWRP was too old for Android 13, and grab the latest (3.7.0), flash that with Odin, start the phone and I can at least get into recovery this time. So I try installing crDroid again. Same deal, just instantly boots straight back into recovery. So, figuring I'd best just go back to what I was using before, I reinstalled the previous crDroid 11 I had been using, and.. for some reason with that installed it only boots into Download mode unless I force it into Recovery. I try wiping everything and trying again, same deal. I even tried installing a different rom (Evolution X) and that just straight reboot looped.
If I go back to 3.5.1 TWRP it gets stuck on the splash screen btw. I am not sure what to do from here. Can I go back to stock and start over? Is there something else I should be doing? I've changed roms a bunch of times in the past and this is the first time 'just reinstall what worked before' hasn't worked, heh.
(For clarification, with crDroid 13: Phone turns on, shows Samsung Galaxy S9 boot screen, then goes straight into TWRP. With crDroid 11: Phone turns on, Galaxy S9 boot screen, straight into Downloading. With Evolution X: Phone turns on, Galaxy S9 boot screen, shut down and reboot. Buttons don't seem to be pressed in.)
DeiwosN said:
..... Can I go back to stock and start over? Is there something else I should be doing? I've changed roms a bunch of times in the past and this is the first time 'just reinstall what worked before' hasn't worked, heh.
....
Click to expand...
Click to collapse
Similar thing happened to me on a different Samsung device.
I did:
Used at that time SamFirm_Reborn_0.3.6.2 to get latest stock from samsung servers directly after inserting correct device designation and csc code.
Checked "binary nature" to get the full multiple part stock rom.
Flashed that with Odin.
Started from scratch.
Thank you so much! That fixed it.
DeiwosN said:
Thank you so much! That fixed it.
Click to expand...
Click to collapse
Glad I could help.
Perhaps useful for other users that you mark this thread as solved.