My Note has worked great from day 1. Its rooted, with the OTA upgrade.
Today for some reason it locked up with the phone app open. When I finally got it to restart, it got through the boot process and when the lockscreen came up, it rebooted again. This happened several times.
I finally got it to run and I tried a reboot, same thing happened.
Should I just Odin the firmware again? both the pit and modem? or just the pit section?
TW is a bit unstable. I'm not rooted and my Note 3 does a double boot pretty much every time. Phone works great so I don't worry about it.
Strange that it was fine until a couple hours ago. I was going to just reinstall the firmware to make sure I didnt have anything corrupt.
I just found the tar for the MJ7 firmware, waiting for it to download.
And it boots repeatedly.... not just a double boot. More like 5 or 6 times until it finally completes a restart.
Well, the tar I got has an invalid hash. Im downloading another one.
Reinstalling the MJ7 tar with ODIN wont trip knox right? I use Odin 3.07 and use the pda slot for the tar right?
OK, I reinstalled MJ7, but it didnt seem to help.
The phone boots to the lockscreen for a second, then reboots. This repeats 5 or 6 times, then finally completes the boot.
I noticed that the phone locked up in the phone app earlier today........
Anyone have any idea whats going on?
I think I found the solution!
However, there is one solution that seems to have worked for many Note 3 owners as posted by XDA member ketani73 -:
“I may have stumbled upon a workaround for the continuous boot problem. It seems that if you turn-off ‘Always allow scanning’ in the advanced Wi-fi settings then the problem will not occur. Your mileage may vary.
Follow these steps:
1. If your Galaxy Note 3 is in a continuous boot cycle or suffers from it then remove the back cover and remove the battery. Leave the back cover off.
2. Remove the SD card.
3. Insert the battery and boot. Wait for the device to fully boot.
4. Go to Menu -> System Settings -> Wi-Fi -> Menu -> Advanced
5. Uncheck ‘Always allow scanning’
6. Use back key until you’re home.
7. Turn off the device.
8. Insert the SD card.
9. Attach the back cover.
10. Turn the device on.
To confirm, I tried booting the device three times with the ‘Always allow scanning’ Wi-Fi setting checked and it ended up in a continuous boot cycle. With the ‘Always allow scanning’ Wi-Fi setting unchecked the device boots fine every time.”
Related
bought a Samsung s4 m919 (Tmobile) unlocked about 3 weeks ago. thought it had a lot of bloatware so I rooted it and put CyanogenMod on it and it worked great (first time for me so i took awhile, but i got it working with no problems). took it to the nearest metro store to put a sims card in it to be told me it was not unlocked. ended up going back to stock rom to try to unlock it. frustrated i took it to another metro store and learned it was actually unlocked and was able to leave the store with activated sims card in it. So then i decided to custom rom it again since I already did it. I don't know what the hell I did differently but nothing seemed to work and I ended up with no recovery mod or system. The only things that works is the download mode.
So Ive tried flashing the stock rom using odin like 4 times and each time everything seemed to go well except the phone still can't turn on. The Samsung "logo" flashes for a second and then the phone shuts off. Any advice, is it a lost cause?
This is the section for your device:
http://forum.xda-developers.com/galaxy-s4-tmobile
Download TWRP from here:
https://twrp.me/devices/samsunggalaxys4tmobile.html
Flash it with Odin, uncheck auto-reboot before flashing with Odin.
Then flash the custom rom you want.
did both and still nothing. Odin says everything passes but the Launcher and recovery still won't turn on.
Is it possible that you are pressing the power button for too long?
For twrp, I check everything on Odin except f.reset time, flash twrp, when you see the word "reset" in the status window, remove USB cable from the phone, remove battery, wait 5 seconds, replace battery, use button combination to boot into recovery.
Happy, happy, happy! Since I got it to work, thought I'd share.
~ caveat emptor, not responsible if this doesn't work for you ~
First off, I followed this very helpful post from DeeXii:
https://forum.xda-developers.com/note-4-tmobile/general/recovery-n910t-t3-marshmallow-pe3-guide-t3406870
I had flashed the N910TUVS2EPK2 stock from Odin after screwing up my phone doing other crap. In any case, after doing that, I obviously wanted root again! Note that this wasn't immediate - I flashed to this a couple months ago, so have been fully setup with gmail, and other account settings. So, the above link gave the best overall, simple step-through, with handy download links. It worked, and even better didn't lose any of my settings. (but, no guarantees, make sure you've backed up!)
Additional details that would be helpful:
- make sure you run Odin as Administrator.
- Odin: click the button next to AP, and then go select the twrp archive you downloaded
- Power off phone, hold boot into download mode (power, home, volume down at same time). click volume up when it says so.
- connect to Odin. you need to see the square just below ID:COM turn blue.
- Click Start to flash the twrp.
- IMPORTANT: after it flashes, the phone will auto-restart. *Quickly* pull out battery before it boots, otherwise it will put back stock recovery on you. (this happened to me - I had waited until it had fully booted, then powered down, then brought it up in recovery mode, and it wasn't twrp! - so remember, pull out battery right after it cycles after flashing)
- Put battery back in, and then boot into recovery by holding power-home-volume up simultaneously. If you end up seeing the nice pretty twrp squares, then this worked. It is interesting that there is also a message here stating that the kernel may very well write back the custom recovery. So, can't say if this will be permanent or not, but at least you can now flash the supersu. (subsequent reboot into recovery still seems to have twrp, so groovy!)
- (presuming you had already put the supersu on the sd card or internal memory - I used the systemless supersu), click install, select it and flash.
- just for kicks (not sure if this was needed or not), after flashing I saw an option to wipe cache/dalchik, so I did that too.
- rebooted (it took awhile, had to 'optimize' all the apps, etc.) - and I'm rooted!
If anyone has been trouble with specifically the N910TUVS2EPK2 build, then I hope this helps.
Thanks man, had the same issue. I figured it might be something to do with booting int OS. Sure enough with 6.0.1 EPK2 rom you MUST load into boot recovery right after flashing TWRP as you stated.
Something went wrong with my OTA update of EPK2 and it started to bootloop( 2 vibrates upon restart and then random amount of bootloops, and then random, soon-coming freeze upon loading in OS and continuing boot-looping) sometime after the update. I erased most of the old stuff via TWRP reinstalled EPK2 bootloader separately and then flashed EPK2 rom and it seems to be OK so far (knock on wood). We'll see hopefully it's not hardware issues like many people were reporting with bootlooping.
Can't you just uncheck the Odin option to reboot instead of the frantic battery pull?
Just wondering, as I'm going to do this later- thanks!
Steven.RN
Followup: Yep. Slip over to the options tab in Odin and uncheck "auto reboot". After Odin flashes TWRP, (the bar is all the way across the download screen, and the Odin Log says "succcess") go ahead, disconnect the phone from USB. Do your battery pull, replace battery. Close up the phone, then hit Volume up, home, and power at the same time- Bang! TWRP screen.
Further note: first time I did this flash, it didn't work, it just stopped in it's tracks. Then I realized I had to enable "developer mode" by clicking on the build number in the "About phone" sections in settings 5 times, going into Developer mode (the new option will present itself in the menu on settings), then: enable OEM unlock and USB debugging. Odin will flash TWRP just fine after that. (Duh on me!)
planetjeff said:
Happy, happy, happy! Since I got it to work, thought I'd share.
~ caveat emptor, not responsible if this doesn't work for you ~
First off, I followed this very helpful post from DeeXii:
https://forum.xda-developers.com/note-4-tmobile/general/recovery-n910t-t3-marshmallow-pe3-guide-t3406870
I had flashed the N910TUVS2EPK2 stock from Odin after screwing up my phone doing other crap. In any case, after doing that, I obviously wanted root again! Note that this wasn't immediate - I flashed to this a couple months ago, so have been fully setup with gmail, and other account settings. So, the above link gave the best overall, simple step-through, with handy download links. It worked, and even better didn't lose any of my settings. (but, no guarantees, make sure you've backed up!)
Additional details that would be helpful:
- make sure you run Odin as Administrator.
- Odin: click the button next to AP, and then go select the twrp archive you downloaded
- Power off phone, hold boot into download mode (power, home, volume down at same time). click volume up when it says so.
- connect to Odin. you need to see the square just below ID:COM turn blue.
- Click Start to flash the twrp.
- IMPORTANT: after it flashes, the phone will auto-restart. *Quickly* pull out battery before it boots, otherwise it will put back stock recovery on you. (this happened to me - I had waited until it had fully booted, then powered down, then brought it up in recovery mode, and it wasn't twrp! - so remember, pull out battery right after it cycles after flashing)
- Put battery back in, and then boot into recovery by holding power-home-volume up simultaneously. If you end up seeing the nice pretty twrp squares, then this worked. It is interesting that there is also a message here stating that the kernel may very well write back the custom recovery. So, can't say if this will be permanent or not, but at least you can now flash the supersu. (subsequent reboot into recovery still seems to have twrp, so groovy!)
- (presuming you had already put the supersu on the sd card or internal memory - I used the systemless supersu), click install, select it and flash.
- just for kicks (not sure if this was needed or not), after flashing I saw an option to wipe cache/dalchik, so I did that too.
- rebooted (it took awhile, had to 'optimize' all the apps, etc.) - and I'm rooted!
If anyone has been trouble with specifically the N910TUVS2EPK2 build, then I hope this helps.
Click to expand...
Click to collapse
thanks for the info, might give it a shot tonight. you have a link to the software update so i can load it with odin?
Thanks for the post. Where can I find the stock N910TUVS2EPK2 ROM?
Charlie Rock said:
Thanks for the post. Where can I find the stock N910TUVS2EPK2 ROM?
Click to expand...
Click to collapse
sammobile.com
Sent from my SM-N910T using Tapatalk
Hi! It's my first time making a thread here so guidance is greatly appreciated. Here's how everything started:
I was just casually using my phone (at the time I was using the built-in browser of google assistant, just looking at some news) then suddenly my phone crashed (I've experienced this before every time I was using the google assistant built-in browser, a simple browser can crash this phone?). It just restarted like it normally would, then, after using the phone for a few minutes, it froze again! I waited for it to reboot but now it just powered off and won't turn on (it won't show any sign of life, no logo, not even an icon when I tried to charge). D:
I figured to have it checked by a local technician and when he tried to plug a charger in, a display showed it charged (found it weird but happy at that time). I figured it was the charger so I bought a new one.
So I got home to charge it fully and when I turned it on, it worked normally. However, when I tried to turn my wifi on, notifications popped up and suddenly it froze again! After that, it turned off and when I tried to turn it back on, I got this dreaded red texts on a black screen:
Bootloader exception ( RST_STAT = 0x10000)
Exception: do_handler_sync: DABT_EL1(esr: 0x9600010)
RDX, do not reboot*** ext4_wait_block_bitmap:494: Cannot read block bitpc : 0x8f0261d0 lr : 0x8f02618c sp : 0x8f117fd0
This showed and the phone won't even let me turn it off, so I just waited for the battery to die out. When it did, I tried to charge it again and planned to do a factory reset thinking maybe an app was causing this. I managed to go to the no command icon and manual mode but no factory reset menu showed up (where you navigate using the volume up and down). So I tried to restart but now it died out completely- no button combination would work, it won't charge, no display can be seen. Is it hard bricked?
I tried to wait a whole day thinking I would be able to charge it again, but it has already been three days and I am not able to perform anything.
There it is, I tried to be as detailed as possible. Additional info: I never tried rooting it or flash roms with it, I haven't done anything with the software (or hardware since I am careful) but install apps (officially from the playstore). From how I see it, it's a firmware problem and I was hoping someone here can help me bring my phone back to life. Is this my fault? If I have this repaired, am I the one who should pay for this?
I mainly want to know what the error message means and if there is a way for me to access the phone. (I figured if I have the technician fix this, all they need is a computer with a software that could fix this since it's a problem with the firmware. If that's everything they would do then I could do that too, with your help of course.)
Thanks to all in advance!
Hi. This sounds pretty strange. Technically...it is hard bricked but you can bring it to life. I can tell you what I would do, when I run into such a problem.
ATTENTION: YOU WILL LOOSE ALL OF YOUR DATA EXPECT EXTERNAL SD CARD
First download the newest firmware for your S7 Edge (G-935FD) on SamMobile and unpacking the .zip.
Download Odin in the newest version, open it and put the downloaded files in the right order in Odin (BL, AP, CP and CSC - the files from the firmware from SamMobile has labeling with BL, AP etc.)
Now the tricky part because your phone won't charge and doesn't go on. You have to go in the download mode with your phone (press and hold volume down - home button - power button) than an window appears and press volume up
Connect your phone with your PC (in Odin you can see, that your device is connected) and press start. It will take some time transferring the ROM and your phone will reboot automatically and after some minutes of blinking Samsung logo...the phone should start normally into the SIM card pattern screen.
Now you have a fresh stock ROM installed and everything should work fine again.
But your phone won't get on or will charge...maybe when you connect it to your PC it will charge. Otherwise I see no option to solve your problem. Your phone must charge again that you can go into the download mode and bring your S7 Edge back to life with a clean stock firmware and an working system.
Hey, so I have had my phone rooted for a long time. I have a Galaxy S5 6.0.1 Marshmallow.
I decided I wanted to get Framework installed so I downloaded the right files and flashed it in TWRP.
My phone took way longer than 10 min to reboot into system so I thought I was stuck in a bootloop and decided to run my phone through TWRP again.
I tried rebooting but that didn't work. I have my phone's backup saved onto a micro SD so I did a factory reset and then tried rebooting.
I got past the rebooting logo and actually got to my lock screen where it asks for my password.
From there, I've been getting spammed with 3 different messages, one saying that IMS service is down, com.sec.vsimservice is down, and WfcService is down.
After I press ok to all 3 of the messages, my phone is still in the lock screen asking for my password but the phone doesn't recognize that im touching the screen to type. After letting the phone stay like that for a few minutes, the lock screen that asks for my password goes away and all I can see is my wallpaper background (no notification panel either) but now the phone recognizes me touching the screen ( I know that because the LED lights up for the windows button and back button )
So basically I decided to go into TWRP and flash my recovery that I had saved on the microSD.
After that didn't work, I've just been going through a series of factory resetting my phone and wiping Dalvik files and then flashing my recovery. My phone is getting unrealistically hot too.
Btw I never downloaded the Exposed Uninstaller from the forum so I tried downloading it onto my pc and then sending the file over to my phone through download mode using Odin so that I could flash the uninstaller through my TWRP but that didn't work because the PDA in Odin does not recognize the uninstaller file.
Please, I really need help and thanks to anyone who tries, it would mean a lot if someone could figure out what I can do. Thanks.
Since you've tried restoring your backup and everything seems to have failed (it sucks, I know) you should try to install a completely stock firmware which you can download from here: http://live.samsung-updates.com/index.php?device=SM-G900I Just make sure you select your exact phone model from the dropdown menu at the top right side as you didn't mentioned which of the 40 S5s you have lol. And after you flash stock firmware and successfully boot up try to restore your backup. If it's still bugged - flash stock again and start off fresh. Let me know how it turns out. I'll help with installing xposed later as well, first let's get your phone running again
Hi. Browsed for ages and always come here for answers.
Here's my problem.
2x S8s. SM-950f.
Updated to most recent software through software update. Both phones were glitchy and crashing and just generally irritating after.
Factory data reset etc. This did not resolve the problems, also led to one of them having issues with FRP (annoying)
Used Odin to try and flash the latest firmware (from sammobile, UK BTU) after flashing both, they reset and powered on. Got stuck at the S8 screen.
Restarted then both were at the "an error occurred during update" screen.
Managed to get back to download screen. Re checked the software and model numbers, even that the bootloader was the correct version etc. All was fine.
Connected to Odin, shows that it is connected, but nothing happens when clicking start.
Now after attempting that, both phones will not power on.
(One will when placed on the wireless charger, but just sticks at S8 screen) and download mode or reset screen can not be accessed. So, not exactly happy. And totally out of ideas
Any suggestions, beyond taking it to a shop to see if anyone can help.
yes .....dont tuch the phones for 24 hours let the battery die ...it will...connect to pc and then try download mode....u may need to press combination for like 1 minute to get to download mode....flash twrp reboot directly into it when odin says successfully .....wipe system data ....dont turn on phone download any custom rom flash and enjoy.....it will trip knox but worth than getting a new board....
Okay, will give that a try.
TWRP?
TWRP install
https://dl.twrp.me/dreamlte/twrp-3.2.3-0-dreamlte.img.tar.html: Download link for twrp SM-G950F (dreamlte)
Just said, wait until your device powers off due battery insufficience. Plug cable and hold at the same moment vol(down)+bixby+power. Then press vol(up) at the warning screen to proceed to odin mode. Let it charging a while like 1 h. Then unplug it and plug it to your pc. In Odin select ap the previous downloaded file. Take your mobile in your hand. With one hand, prepare your fingers to vol(up)+bixby and with the other hand start the flashibg process. Be careful, and take your hand directly from the mouse if you clicked start in odin, and position your one finger to power button, but dont click. If odin start pass, press immidiately the buttons (vol(up)+bixby+power) and let it to start into recovery. If you arrived to recovery, reply to us if not search for help!!!
Good luck
memreb
Still trying to get them on. Powered on to download mode but only for a couple of seconds and switched off again.
Can't get them to power on. Buggered
simonboyle said:
Still trying to get them on. Powered on to download mode but only for a couple of seconds and switched off again.
Click to expand...
Click to collapse
i have the same issue with my s8 but when i boot in download mode the screen goes black but if i press volupe up it connect to odin with black screen you shoud give it a try
Will try that
Okay, downloaded TWRP, can get phone calls nected to Odin but when I extract TWRP it doesn't give a valid file type.
Am I being dumb.
No files appear that Odin will recognise.
Also just shows as "recovery" no .tar or anything
Ignore above. Corrupted download.
Sorted.
Now when flashing TWRP is gets to a fail due to
"Complete (write) fail
Hi you should try flashing official firmware
itac47 said:
Hi you should try flashing official firmware
Click to expand...
Click to collapse
The point of the thread us that I am.unable to do that.
So kinda useless post buddy.
Read the OP.
Anyone want two bootlooped S8s? Hahahaha
simonboyle said:
Anyone want two bootlooped S8s? Hahahaha
Click to expand...
Click to collapse
Not sure what stage your at and maybe some more useless ideas
1. Trying to flash twrp is kinda of useless if you can't get into your system need oem unlock for that.
2. Have you tried taking out Sim card and SD card and reboot.
3. If you can at least boot try smart switch as it has a emergency recovery option.
4. Trying rebooting in safe mode.
All been attempted