Phone has been in the ****ter for the past day. Stuck on boot loop. I tried flashing the most recent stock firmware. It would not do it and kept throwing auth failed signs at me. I tried other stock firmwares for tmobile with no sucess. I Tried throwing them on my sdcard and installing through there in TWRP, but I keep getting md5 auth failures. I have wiped, factory reset, and cleaned house many times. Nothing works. Im at my wits end. Someone please help
I'm a guest to this forum..but same thing happened to me about 5 days ago. Last thing I remember seeing is the 5. update trying to take place and I was just about OUT of Internal memory (with NO microSD card). Phone just kept rebooting. I was able to do a Factory Wipe (Both in the OS and in the Recovery Mode)....Neither worked even though they appeared to be successful. Phone just came back with ALL of my data still intact. The other weird thing...I had about 60 seconds before phone decided to reboot each time. During those 60 seconds I was able to delete files, pictures, etc. to save space. As soon as the phone rebooted those same files were back! Very frustrating. Still having the issue.
im not sure what states either of you guys are in, but you can look on craigslist for people that do flashing. you make need to do a odin rebuild because the partitions are ****ed.
you can repair it yourself but with pure caution.
Have you tried flashing in download mode with your computer through ODIN? If twrp doesn't work, that's what I go to next.
You could also try flashing the firmware without the MD5 file and I believe twrp will skip the check. (not positive on this one)
Figured it out on my own. Flashed CF autoroot. Then flashed 5.1.1 which is the most up to date firmware. Im not sure if the issue was because I was doing 5.1.0 and didnt realize that was the most UTD version, or if CF to 5.1.1 was the trigger. Either way, it worked.
Related
I've been looking all over this site but I can't find anything. I suppose that it's partly because I'm not sure about the problem myself.
A couple of months back (maybe more) I upgraded to the ICS infinitum rom (blue version) with midnight kernel. It was great - the phone worked fine. Well I'm exaggerating, it ****ed up every once in a while. Programs would automatically shut down and it would get really slow after a while. But all in all it wasn't bad, and it was stable enough for me most of the time....
Then, last Thursday everything seemed to go apart, every program on the phone was shutting down. So I thought I'll just restart and it will be fine. When I did, the phone did not come back on. the kernel would load and then it was stuck on the start-up animation in infinite loops.
Now, to be frank, this isn't the first time this has happened. So I didn't panic. Last time I just used the CMW recovery to re-install the kernel and the rom (I keep the files on the sd card). But this time, I wanted to try to avoid the factory wipe for as long as I could, and try finding a different option, knowing that if all else fails, I have something to revert back to.
Then I did the mistake of deleting the init.d file without re-installing anything. I wanted to, but accidentally clicked on the 'reboot now' option. And then all went to ****. The kernel didn't load. I went to recovery and it couldn't mount the sd card so I couldn't re-install it.
I tried flashing a new kernel using odin, and it did get me a bit better: my CWM recovery can read the sd. However, I still can't mount the system. Even worse, when I get to the infinitum zip roms and re-installing it brings up the status 7 error (which, after searching, seems to come up for different reasons for each person)
Despite installing a new kernel, when I reboot the phone now it doesn't load the kernel anymore, it just stays stuck on the welcome screen. I tried using the recovery to re-install a different kernel, it worked, but the phone still won't start - it now automatically skips to the recovery mode. I don't know if I should try flashing a rom through odin, and I'm too afraid to try anything at all now...
Can anyone help me? Is there any way to restore the init.d file or maybe that has nothing to do with my problem?
uvii said:
I've been looking all over this site but I can't find anything. I suppose that it's partly because I'm not sure about the problem myself.
A couple of months back (maybe more) I upgraded to the ICS infinitum rom (blue version) with midnight kernel. It was great - the phone worked fine. Well I'm exaggerating, it ****ed up every once in a while. Programs would automatically shut down and it would get really slow after a while. But all in all it wasn't bad, and it was stable enough for me most of the time....
Then, last Thursday everything seemed to go apart, every program on the phone was shutting down. So I thought I'll just restart and it will be fine. When I did, the phone did not come back on. the kernel would load and then it was stuck on the start-up animation in infinite loops.
Now, to be frank, this isn't the first time this has happened. So I didn't panic. Last time I just used the CMW recovery to re-install the kernel and the rom (I keep the files on the sd card). But this time, I wanted to try to avoid the factory wipe for as long as I could, and try finding a different option, knowing that if all else fails, I have something to revert back to.
Then I did the mistake of deleting the init.d file without re-installing anything. I wanted to, but accidentally clicked on the 'reboot now' option. And then all went to ****. The kernel didn't load. I went to recovery and it couldn't mount the sd card so I couldn't re-install it.
I tried flashing a new kernel using odin, and it did get me a bit better: my CWM recovery can read the sd. However, I still can't mount the system. Even worse, when I get to the infinitum zip roms and re-installing it brings up the status 7 error (which, after searching, seems to come up for different reasons for each person)
Despite installing a new kernel, when I reboot the phone now it doesn't load the kernel anymore, it just stays stuck on the welcome screen. I tried using the recovery to re-install a different kernel, it worked, but the phone still won't start - it now automatically skips to the recovery mode. I don't know if I should try flashing a rom through odin, and I'm too afraid to try anything at all now...
Can anyone help me? Is there any way to restore the init.d file or maybe that has nothing to do with my problem?
Click to expand...
Click to collapse
I suggest flash 3-file GB rom via odin with ticked re-partirion and phone bootloaderupdate.
First of all init.d has nothing to do with the boot of kernel and ROM itself. It's just like autostart in Windows, so if it's missing it shouldn't cause problems.
My solution is to flash a complete stock Gingerbread ROM using Odin. You can get them at sammobile.com. Then afterwards flash a custom kernel and then whatever you like.
If you need help,feel free to ask me
Sent from my Gameboy Color
Yes! Thank you! That worked!!
It happened again! just 10 days later.
Is the Infinidtum rom ****ed up in any way?
it's stuck on the loading part of the rom
I was running CM 9 nightly builds for the last year, and decided to upgrade to CM10. In my system settings there was a handly little "upgrade" button which I mistakenly used- and my phone got stuck in a reboot loop. I booted into recovery mode, and tried to restore the phone, but it did not work. It kept sticking at the blue circle boot image for over 20 minutes.
I tried recovery mode again, and every time I went to CW recovery I would get several lines saying can't mount SD card. OK, I broke it.
I then downloaded the factory firmware from samsung-updates.com - and flashed with Odin- just to get my phone to work. It's been 2 hours where I cna't get anything up. After rebooting (from factory firmware) I have the regular samsung s repeatedly coming up, and I'm still in a reboot circle.
Any suggestions or ideas? I need my phone for work, so I really just want to get it up at this point, with whatever will work.
I found the EZBase recovery kit thread, fixed myself Of course, it's the 101th thread I read in my search!
http://forum.xda-developers.com/showthread.php?t=2095519
Sorry, next time will keep searching. Worked to get my phone up and running,w ill now attempt CM10 again...
Hey all. Appreciate any help, because Im out of ideas here. A friend brought me his Vzw G2 yesterday morning, which he had bricked trying to install cm12 (He's had it rooted and unlocked since he got it), and he apparently tried to install a cm12- compatible twrp, and thats when he got a secure boot error. I fixed it just by using the lg flashing tool and a tot and restoring it to stock, but when I tried to flash it, I ran into the issue of twrp wouldn't flash anything, some drinks were had, and out of drunken stupidity last night we tried to dd a new copy of twrp, from twrp's shell onto it, which sent it back into a brick. Now, its worse, download mode cant even be accessed. I've been at this all day trying to fix it. Trying to go to recovery takes it to fastboot, but, it goes blank after about 10 seconds, and then no fastboot connection can actually be made to the device so I cant use fastboot. I'm on linux, so it does show all of the devices partitions under /dev, so I tried another post's idea of manually dding the entire bootstack onto the device, partition by partition, but that didnt seem to change anything. It's on the 39a lollipop update. Any one have any other suggestions?
Any luck?
No, sadly still nothing. I've tried re-dding a few times, but I cant think/read anything else to try.
My S6 edge is in a bootloop. I put off the 5.1.1 OTA for a while when my wifi would not turn on. Rebooted, still didnt work. I decided to do the update. installation went great but now its in a boot loop. I flashed the firmware (BOG7) using Odin. It worked. The phone was back on again but then it shut off after a few hours.
Its been stuck in the bootloop again. I flashed BOG7 again. Ive Flashed BOG9. Ive flashed the stock PIT. Ive tried ADB sideload. Smartswitch and Kies do not recognize the device. Of course, Ive wiped cache and factory reset. Attempted booting in safemode. All flashes were successful but when it reboots, It says "erasing" and goes to bootloop (Samsung powered by android).... Drivers are installed and working. MTP is not installed and I cant find the file.
Please .
same problem
I'm having the same problem with boot loop on g925v stock. I'm wondering if the op or anyone else can help!
No mater what I do, phone reboots after almost exactly 1min9 sec. Just enough time to select a language, but not get past the next "activation" screen.
Background: Phone has never been rooted, at first was on og5 and started freezing on the verizon logo, so I factory data reset, and after that nothing has really changed. knox has not been tripped, frp not tripped
First I tried flashing og5 with odin,
(of course checked md5, and odin=pass, then after flashing, I always tried several combinations of booting to recovery for wipe cache partition/ factory reset / and also power down by holding volume down and power button, then select boot in safe mode)
Then tried flashing og7, still boot loop
then tried flashing og9, 3 times, again, also many attempts of factory data reset/ wipe cache partition / safe mode.
I am starting to think this may be a hardware problem, BUT unfortunately I do not have samsung warranty available on this phone so I am pretty much stuck messing with it.
In researching the issue, I have run across quite a few similar freeze/boot loop problems all over the web, and never any real solutions, for both g925v, g920v, and other s6 models. I've also seen a stock s6 g920v that freezes randomly, flashing stock og9 never helped, owner was planning to replace the battery and see if that helps (I have not heard back).
I've tried looking at the boot log but I'm no expert. I know I can't downgrade, but I'm wondering if there is anything I can do with adb, or any other bootloaders that I could try flashing over the og9 (even if just temporarily, assuming I will flash stock og9 again after).
Thanks for any encouragement, help or advice.
I finally gave up on my GS6 Edge because upon carefully taking it apart for the 3rd time I noticed physical damage up by the wifi receiver and SIM card slot. My advice would be to try the things I tried (above) and, if it's not a hardware issue, it may fix the problem. Good luck.
beefriendly said:
I'm having the same problem with boot loop on g925v stock. I'm wondering if the op or anyone else can help!
No mater what I do, phone reboots after almost exactly 1min9 sec. Just enough time to select a language, but not get past the next "activation" screen.
Background: Phone has never been rooted, at first was on og5 and started freezing on the verizon logo, so I factory data reset, and after that nothing has really changed. knox has not been tripped, frp not tripped
First I tried flashing og5 with odin,
(of course checked md5, and odin=pass, then after flashing, I always tried several combinations of booting to recovery for wipe cache partition/ factory reset / and also power down by holding volume down and power button, then select boot in safe mode)
Then tried flashing og7, still boot loop
then tried flashing og9, 3 times, again, also many attempts of factory data reset/ wipe cache partition / safe mode.
I am starting to think this may be a hardware problem, BUT unfortunately I do not have samsung warranty available on this phone so I am pretty much stuck messing with it.
In researching the issue, I have run across quite a few similar freeze/boot loop problems all over the web, and never any real solutions, for both g925v, g920v, and other s6 models. I've also seen a stock s6 g920v that freezes randomly, flashing stock og9 never helped, owner was planning to replace the battery and see if that helps (I have not heard back).
I've tried looking at the boot log but I'm no expert. I know I can't downgrade, but I'm wondering if there is anything I can do with adb, or any other bootloaders that I could try flashing over the og9 (even if just temporarily, assuming I will flash stock og9 again after).
Thanks for any encouragement, help or advice.
Click to expand...
Click to collapse
So first off thanks for reading and trying to help.
I am having the following problem:
First of no updates were installed recently. I did update to the latest December update in early January.
Few days ago my phone SM-N910T froze up and seemed to have shut down. After being unable to restart i pulled the battery, put it back in and nothing happened. I left it out for 5 minutes plugged it back in and the phone booted up. But as soon as the screen turned off the phone heated up and would not turn on. I've been dying to just start anew anyway so I tried using Kies to restore the phone however this failed twice.
I downloaded Odin and Stock N910T3UVS3EPK2.
I flashed TWRP Recovery. And then tried to Flash the firmware which failed several times and i started getting errors.
“Could not do normal boot, mmc_read failed”
Kernel is not seandroid enforcing
as well as others.
After rebooting it several times it started working I was able to log in and set everything up, but the phone started freezing up again.
I blew everything away did a Data Wipe in TWRP. I then downloaded N910T3UVS3EPK2 Stock Rooted Odex from here.
When trying to flash it, it failed several times. and i started getting No Pit Binary errors. After trying several times with different cables and USB ports it finally took. But i am still having the same problems with freezing and restarting.
THE ONLY THING THAT HELPED: And this is a band aid fix, is I installed the wake lock app from the google store and enable Partial Wake Lock.
The phone is stable but only until i restart it at which point it goes into Download Mode and i have to restart several times and prey it boots up.
HALP! :crying:
I had the same problem, and MANY MANY others have this issue too. For months i fought with it without any success. I ordered new motherboard and now my phone is working again.
Please check General forum. There is a big thread about installing KitKat from another phone which apparently fixed this issue. Dig around that thread and read about it, might be a solution!
AntonJart said:
I had the same problem, and MANY MANY others have this issue too. For months i fought with it without any success. I ordered new motherboard and now my phone is working again.
Please check General forum. There is a big thread about installing KitKat from another phone which apparently fixed this issue. Dig around that thread and read about it, might be a solution!
Click to expand...
Click to collapse
I saw that thread, but most of those people started having the issue after the update. If the kit kat update fixes it then i'm at a loss. And since a new board fixed the issue for you that means most likely the the memory is beginning to fail. That's how SSDs die anyway.
tempy1 said:
So first off thanks for reading and trying to help.
I am having the following problem:
First of no updates were installed recently. I did update to the latest December update in early January.
Few days ago my phone SM-N910T froze up and seemed to have shut down. After being unable to restart i pulled the battery, put it back in and nothing happened. I left it out for 5 minutes plugged it back in and the phone booted up. But as soon as the screen turned off the phone heated up and would not turn on. I've been dying to just start anew anyway so I tried using Kies to restore the phone however this failed twice.
I downloaded Odin and Stock N910T3UVS3EPK2.
I flashed TWRP Recovery. And then tried to Flash the firmware which failed several times and i started getting errors.
“Could not do normal boot, mmc_read failed”
Kernel is not seandroid enforcing
as well as others.
After rebooting it several times it started working I was able to log in and set everything up, but the phone started freezing up again.
I blew everything away did a Data Wipe in TWRP. I then downloaded N910T3UVS3EPK2 Stock Rooted Odex from here.
When trying to flash it, it failed several times. and i started getting No Pit Binary errors. After trying several times with different cables and USB ports it finally took. But i am still having the same problems with freezing and restarting.
THE ONLY THING THAT HELPED: And this is a band aid fix, is I installed the wake lock app from the google store and enable Partial Wake Lock.
The phone is stable but only until i restart it at which point it goes into Download Mode and i have to restart several times and prey it boots up.
HALP! :crying:
Click to expand...
Click to collapse
Do you have "T3"or "T" model?
The files given below is for "T" variant do not try if you have T3.
It sounds crazy to tell you but trust me this will work.
Put your phone in freezer for about 2 hours then do the steps below if you want to recover your device as it was before.
Go to download mode
Flash 5.0.1 modem via odin choose (CP) tab this will fix emmc read fail error.
https://www.androidfilehost.com/?fid=24052804347820086
Dont reboot to system go to download mode again.
Then flash full 5.1.1 lollipop ok1 firmware
https://www.androidfilehost.com/?fid=312968873555011894
.once it pass dont let the phone reboot.
Go to stock recovery and wipe cache & data factory reset.
Reboot wait 10 minutes dont touch anything let the phone rest.
Complete setup and dont download anything any apps go to software update and take all marshmallow ota updates.
Once finish do factory reset again and you will get clean operating system without any issues.
Trex888 said:
Do you have "T3"or "T" model?
The files given below is for "T" variant do not try if you have T3.
It sounds crazy to tell you but trust me this will work.
Put your phone in freezer for about 2 hours then do the steps below if you want to recover your device as it was before.
Go to download mode
Flash 5.0.1 modem via odin choose (CP) tab this will fix emmc read fail error.
https://www.androidfilehost.com/?fid=24052804347820086
Dont reboot to system go to download mode again.
Then flash full 5.1.1 lollipop ok1 firmware
https://www.androidfilehost.com/?fid=312968873555011894
.once it pass dont let the phone reboot.
Go to stock recovery and wipe cache & data factory reset.
Reboot wait 10 minutes dont touch anything let the phone rest.
Complete setup and dont download anything any apps go to software update and take all marshmallow ota updates.
Once finish do factory reset again and you will get clean operating system without any issues.
Click to expand...
Click to collapse
I have the " T " variant
I've read this before. I am a logical person I want to understand why this would work. Also when placing the phone in the freezer (i feel like i'm being pranked) do i place it in there with the battery?
I will definitely try this since I have nothing to lose. But i have a phone heavy next few weeks and i don't have a backup
tempy1 said:
I have the " T " variant
I've read this before. I am a logical person I want to understand why this would work. Also when placing the phone in the freezer (i feel like i'm being pranked) do i place it in there with the battery?
I will definitely try this since I have nothing to lose. But i have a phone heavy next few weeks and i don't have a backup
Click to expand...
Click to collapse
Without battery in freezer.
No idea how it works but good thing is hopefully it will work cuz lot of users even recover their hard bricked devices by this.
As you said you have nothing to lose so give it a try and make sure be patient dont give up and do this when you have enough time to do at least couple of hours.
I should mention that I had an 'injured' 910t after upgrading, and the freezer thing worked for months. I think there is a thermal issue and something is physically getting de-soldered in the motherboard. @Trex888, I will try your fix - I got a NEW Note4 2 weeks ago and it is running 5.0.1 and it bricked....
IF ANY OTHER COMPANY SOLD A PHONE WITH STYLUS, i WOULD TOSS THE NOTE4 IN THE TRASH....
keithwwalker said:
I should mention that I had an 'injured' 910t after upgrading, and the freezer thing worked for months. I think there is a thermal issue and something is physically getting de-soldered in the motherboard. @Trex888, I will try your fix - I got a NEW Note4 2 weeks ago and it is running 5.0.1 and it bricked....
IF ANY OTHER COMPANY SOLD A PHONE WITH STYLUS, i WOULD TOSS THE NOTE4 IN THE TRASH....
Click to expand...
Click to collapse
so wait the freezer thing was not even a permanent fix?
No, the freezer sometimes helps you get a bricked device so that it turns on. It doesn't fix thermal issues. I believe it helps some electrical connection that has broken come into contact again.
I can't go to download mode or recovery. I tried both ways But there is no way to use my device.
Trex888 said:
Do you have "T3"or "T" model?
The files given below is for "T" variant do not try if you have T3.
It sounds crazy to tell you but trust me this will work.
Put your phone in freezer for about 2 hours then do the steps below if you want to recover your device as it was before.
Go to download mode
Flash 5.0.1 modem via odin choose (CP) tab this will fix emmc read fail error.
https://www.androidfilehost.com/?fid=24052804347820086
Dont reboot to system go to download mode again.
Then flash full 5.1.1 lollipop ok1 firmware
https://www.androidfilehost.com/?fid=312968873555011894
.once it pass dont let the phone reboot.
Go to stock recovery and wipe cache & data factory reset.
Reboot wait 10 minutes dont touch anything let the phone rest.
Complete setup and dont download anything any apps go to software update and take all marshmallow ota updates.
Once finish do factory reset again and you will get clean operating system without any issues.
Click to expand...
Click to collapse
So i recently had a baby, thus i had no time at all to get my phone to work. WakeLock app was working alright.
But last night the phone just died. all attempts to revive failed. I left it in the freezer until the morning and it booted up but quickly locked up after about 5 minutes of use and became unresponsive.
I tried your method.
I failed right away. Modem could not be written..
I tried flashing the pit files like i did previously and that failed as well.
Any suggestions are appreciated. I am phoneless
EDIT#2: After I left the phone in the freezer for longer (3 hours). The odin firmware update went through !!!! This furtherst i've gone so far.
I went into recovery and did everything you said.
BUT now i have Kernel Panic Upload Mode on my screen with a little green android
EDit#3 few battery pulls later. And an over 15 minute wait time on the android logo and then about the same on the t-mobile logo i got into the OS. I did the OTA update, the phone heated up and a few restarts later it froze up like it did previously
Back to square 1
EDIT: THIS helped for a few days
https://forum.xda-developers.com/note-4-tmobile/general/ddi-mmcread-failed-boot-error-fix-t3434335
Day 2: and all went back to the phone not waking up and after screen is turned off