Hi, I think I have a major problem with my phone.
When doing a rom install the phone got stuck and did not respond to anything. Eventually got the phone back to life using NVflash. Re-installed the blazing rom from a back up and the phone was back to normal. However less than 24hrs later the phone spontaneously crashed to dead again. Nothing will restore it. Using NVflash again its get stuck at "waiting for bootloader to intialize. I have read all the other similar post and tried all their suggestions...but to no avail. Is there any thing else I could try. Is there a different boot.img file I can use...since this is the only thing that gets loaded when I run nvflash.bat.
thanks for any help you can offer.
You should try to restore a Stock ROM, see http://forum.xda-developers.com/showthread.php?t=1127849.
Or flash another ROM, like Cyanogen or another, to see if the problem still occurs: if it still occurs, it doesn't come from boot.img but from a deeper problem.
I can't even load a recovery image via NVFlash let alone choose a stock rom!
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
Two weeks ago my phone randomly started to think it was charging every now and again. I thought nothing of it until One day it wouldn't boot. It would get stuck at the Samsung n7000 logo screen. I was able to boot into CWM so I did that and I tried to do a back up just because, but then it failed at backing up /data. It said it was corrupted. I went ahead and flashed another ROM and it booted just fine after that, but the charging problem persisted so I just ignored that. My phone just decided to not boot again so I was wondering if there was anything that could be done to save my phone. Also, I've always used a safe kernel.
TL;DR Phone doesn't boot. Randomly thinks it's charging and when I use CWM it says /data is corrupt. Flashing a new ROM only fixes it temporarily.
I think it is a hardware problem take a look at this thread http://forum.xda-developers.com/showthread.php?t=2008657
Thanks for the reply. f it persists I was probably gonna result in doing that. I am mainly looking for a solution to my other problem though.My phone sometimes just wont turn on at all.
I just went to a stock rom with ODIN installed a new kernel and then a new ROM so I'll see how that goes for a while, but if it's anything like before it wont last very long.
Droid 4 running Stock Jb 4.1.2, Safestrap 3.11, Liquid smooth 2.9, CM (last stable)
Everything working fine for a number of months, installed Liquid smooth via -> delete romslot 3, create romslot 3, install Liquid 2.8.
It ran for a number of days no problems. Restarted fine, all features worked great, even the annoying random restart from 2.4 went away.
6 - 10 days in, im surfin' the news sites at work, put it down, screen goes black, i pick it up. Hit the power button cause i realize its off and it just boot loops... so bad i had to vol-/+ pwr, go to flash mode and THEN turn it off b/c it just kept trying to restart, hang on logo.
I got home and decided to AP flash the latest:
9.8.2O-72_VZW-18-2
Blur_Version.98.72.182.XT894.Verizon.en.US for the maserati.
Boot looped a few times, i was able to get it to go into recovery mode, after that it loaded up the stock JB system. First boot it crashed and restarted, second boot it loaded but only the keyboard worked, not the touch screen. Went to the in OS option of factory reset mode + delete storage.
Rebooted, worked. Checked it a few boots, everything is fine. I use Druid 4 Utility Xt894 JB version and apply the root. Works great. Install safestrap, Create new partition, install liquid smooth 2.9. Works for an afternoon... at work today the touch screen stops responding, i restart it a few times. I try to enter recovery mode. Now im in boot loop again...
I've tried re flashing it again, a few times. I tried even going down to the previous release of JB for the phone. STILL 4.1.2!!!! But nothing.... it just boot loops... what did i do wrong? It was running great. No tweaks or anything done to it prior to it having its melt down.
Help please.. ive provided as much information as possible and though i only joined XDA now to post for help, i have read it for a long time as my main source for my phone and have donated to both CM and Liquidsmooth teams previously..
help!!!
I can't see where you are doing anything wrong. You have obviously done your research and have a good idea of what you are doing. I see, after you fastbooted, you went back to Liquid. I think I would try running CM10.1 or even stock for a few days and see if you have the issue there as well. If you do than it sounds to me like it might be a hardware issue. If not, maybe try re-downloading Liquid. Perhaps your zip got corrupted somehow.
I would love too. In fact i would be willing to run it on the stock crappy 4.1.2 if i could get it out of boot loop this time...
It just keeps boot looping on the logo. AP Fashboot flash and BP flash work but recovery and normal boot/reboot mode just goes into M logo boot loop.
I've re downloaded the 4.1.2 jb SBFs from 2 different sources to ensure its not a corrupt file, tried 18_1 and 18_2 software versions...
Is there a way to use the abd shell to get into the filesystem and check whats going on? Is the SBF the last call? or is there another route to see whats going on or just flash EVERYTHING? Like completely back to stock?
I can find my way around a PC file system but im not familiar with linux. Please help me understand, Is it like having CMOS and BIOS settings or equivalent to damaged CMOS firmware? What am i not replacing/reverting by SBF and HOW can i replace/revert BEYOND the basic sbf...
If ya point me in a direction or to someone who can help me out i can do all the foot work just point me in the right direction?
Is this applicable? I found a site talking about using CWM in a ADB shell file push to possibly get access to more features?
The article also goes into reading the busybox / ADB command screen? (sorry for not proper jargin) and see what its doing during the boot loop before it restarts?
Id add the link but i need more posts....
Update: Flashed 18_2 again with a "factory cable" i made, let it boot loop a series of times before it started up into the stock system again.
At first, again the touch screen wouldn't work, random lockups and restarts, etc. Since i just got it into the main system again and i had to leave for the weekend for a trip(no wifi or network), i couldn't mess with it all weekend but i left it on the whole time and kept checking its functionality... gradually its come back to full function. Touch screen works and is accurate, no more lockups, no more restarting, even stopped boot looping when i restart and enter recovery..
Im not sure and i couldn't find any forum converstations or write ups to support to idea but i think after a major crash and you flash new or reflash your SBF, it seems the phone needs time to recalibrate and index? Not sure, but just an FYI. Gonna try loading SS and liquid again.
Hi everyone. I have a problem I can't seem to resolve. I tried updating to the OTA jellybean update a couple weeks ago, it seemed to go ok. I then tried to go back to an earlier version of eclipse rom I was using. Now when I power on the phone I get AP Fastboot Flash Mode (S) (Flash Failure). I can select normal boot and it will go into my ICS Rom that I have loaded in slot 1 after going thru my safestrap recovery program. So the phone is not unusable, just very annoying to use. My question is, how can I get the fastboot flash mode flash failure warning to not show up every time I reboot the phone? I've tried loading the Stock JB Rom from verizon, Blur_Version.6.7.246.xt875.verizon.en.us with RSD Lite, but when I try to extract the files with RSD, I get the error "Please check input file. Either XML format is wrong or image files associated with it are missing." I just want to be able to get a stock rom back on my phone, without any errors when I boot it, I don't care if I have root, safestrap, or anything else, I just want a properly working phone. Any suggestions how to get rid of the boot flash failure warning? Thanks!!!! Richard
Update.... Looks like I really screwed it up now. Tried to rsd lite a JB rom, got about 1/2 way, to copying system image, then hung up. Now when I reboot, it won't even go into recovery or normal mode... Stoopid operator malfunction..... Any suggestions on which rom I can try to install via RSD Lite to help get it back going? It will still go into AP fastboot mode.
He's dead, Jim. Nothing is working, no rom will load, they either fail or hang up. Now both of my batteries are dead, and it won't even try to do anything. Any suggestions?? Guess I'm in the market for another phone. Maybe some of the gurus on here have some advice. Thx.
He's alive, Jim!!!!!
rlg999 said:
He's dead, Jim. Nothing is working, no rom will load, they either fail or hang up. Now both of my batteries are dead, and it won't even try to do anything. Any suggestions?? Guess I'm in the market for another phone. Maybe some of the gurus on here have some advice. Thx.
Click to expand...
Click to collapse
Thanks to some other posts on here, http://forum.xda-developers.com/showthread.php?t=2236980 I tried installing the system and preinstall img files manually thru moto fastboot. They seemed to hang up after a few minutes, but I tried to install the files anyway. Afterwards, I was able to get into recovery mode and do a system wipe and reinstall the JB rom that I had on my SD card. Now a couple hours later, I got the pageplus 4g issue fixed again, and just finished rooting it with the tutorial on XDA http://forum.xda-developers.com/showthread.php?t=2256439.
You guys are awesome! Thanks for all your hard work.
Hello everyone. I have encountered something I don't understand. My note suddenly turned off and wouldn't restart. I thought maybe my battery was low so I plugged it in and it started. I decided to get a new battery and charged it up same thing was going on sometimes it would restart and be fine I was running stock rooted rom twrp recovery never dropped it never messed with it. Then since i was having trouble I took it to a cell repair shop. I could boot to download and twrp but when i tried to back up the rom it would get to about 2 percent and shutdown. The only way the phone stayed on is if i am in download or twrp but i couldn't do anything repair shop couldn't help either. I was desperately trying to save some data off the phone when i gave up I said ok i will reflash it all goes well in odin it reboots then says applying update but never gets past the boot farthest i have got is the tmobile screen. then it shuts down and keeps vibration and trying to restart only to shut down and do it all over again. so I am now stuck in a boot loop it seems not sure if that is accurate. I have no idea how to fix this any ideas anyone i have reflashed the latest rom twice and everything should be fine but it isnt. I am wondering what to do next I tried to flash twrp but it didnt take and also tried cf oneclick root didnt take either but odin says success and pass. I am at the end of my idea list and out of google searches no idea what to try next. So I have come to the one place i may find some help XDA. Thanks in advance
your phone partition got messed up you have to put TWRP back and then go in wipe and then you have to do file repairwhen you fix file then ran back the stock firmware which will fix bootloader
then go back install twrp and install custom rom with root
---------- Post added at 04:03 PM ---------- Previous post was at 04:02 PM ----------
rayhawk said:
Hello everyone. I have encountered something I don't understand. My note suddenly turned off and wouldn't restart. I thought maybe my battery was low so I plugged it in and it started. I decided to get a new battery and charged it up same thing was going on sometimes it would restart and be fine I was running stock rooted rom twrp recovery never dropped it never messed with it. Then since i was having trouble I took it to a cell repair shop. I could boot to download and twrp but when i tried to back up the rom it would get to about 2 percent and shutdown. The only way the phone stayed on is if i am in download or twrp but i couldn't do anything repair shop couldn't help either. I was desperately trying to save some data off the phone when i gave up I said ok i will reflash it all goes well in odin it reboots then says applying update but never gets past the boot farthest i have got is the tmobile screen. then it shuts down and keeps vibration and trying to restart only to shut down and do it all over again. so I am now stuck in a boot loop it seems not sure if that is accurate. I have no idea how to fix this any ideas anyone i have reflashed the latest rom twice and everything should be fine but it isnt. I am wondering what to do next I tried to flash twrp but it didnt take and also tried cf oneclick root didnt take either but odin says success and pass. I am at the end of my idea list and out of google searches no idea what to try next. So I have come to the one place i may find some help XDA. Thanks in advance
Click to expand...
Click to collapse
once you fix file then do the format within twrp
rayhawk said:
Hello everyone. I have encountered something I don't understand. My note suddenly turned off and wouldn't restart. I thought maybe my battery was low so I plugged it in and it started. I decided to get a new battery and charged it up same thing was going on sometimes it would restart and be fine I was running stock rooted rom twrp recovery never dropped it never messed with it. Then since i was having trouble I took it to a cell repair shop. I could boot to download and twrp but when i tried to back up the rom it would get to about 2 percent and shutdown. The only way the phone stayed on is if i am in download or twrp but i couldn't do anything repair shop couldn't help either. I was desperately trying to save some data off the phone when i gave up I said ok i will reflash it all goes well in odin it reboots then says applying update but never gets past the boot farthest i have got is the tmobile screen. then it shuts down and keeps vibration and trying to restart only to shut down and do it all over again. so I am now stuck in a boot loop it seems not sure if that is accurate. I have no idea how to fix this any ideas anyone i have reflashed the latest rom twice and everything should be fine but it isnt. I am wondering what to do next I tried to flash twrp but it didnt take and also tried cf oneclick root didnt take either but odin says success and pass. I am at the end of my idea list and out of google searches no idea what to try next. So I have come to the one place i may find some help XDA. Thanks in advance
Click to expand...
Click to collapse
there is the list of stock firmware try them see which one works with twrp, you have to install twrp first so you can fix the problem using repair files in twrp
https://www.sammobile.com/firmwares/galaxy-note4/SM-N910T/
also read this for installing twrp on 910t
https://forum.xda-developers.com/no...nt/tool-utility-twrp-2-8-1-0-teamwin-t2915588
rayhawk said:
Hello everyone. I have encountered something I don't understand. My note suddenly turned off and wouldn't restart. I thought maybe my battery was low so I plugged it in and it started. I decided to get a new battery and charged it up same thing was going on sometimes it would restart and be fine I was running stock rooted rom twrp recovery never dropped it never messed with it. Then since i was having trouble I took it to a cell repair shop. I could boot to download and twrp but when i tried to back up the rom it would get to about 2 percent and shutdown. The only way the phone stayed on is if i am in download or twrp but i couldn't do anything repair shop couldn't help either. I was desperately trying to save some data off the phone when i gave up I said ok i will reflash it all goes well in odin it reboots then says applying update but never gets past the boot farthest i have got is the tmobile screen. then it shuts down and keeps vibration and trying to restart only to shut down and do it all over again. so I am now stuck in a boot loop it seems not sure if that is accurate. I have no idea how to fix this any ideas anyone i have reflashed the latest rom twice and everything should be fine but it isnt. I am wondering what to do next I tried to flash twrp but it didnt take and also tried cf oneclick root didnt take either but odin says success and pass. I am at the end of my idea list and out of google searches no idea what to try next. So I have come to the one place i may find some help XDA. Thanks in advance
Click to expand...
Click to collapse
Befour flashing twrp make sure you uncheck Auto reboot....when it's done flashing pull your battery, put it back in the phone but don't power on....you want to boot right into recovery......then twrp will stick