I was using the Cyanogen 13 ROM for about 20 days it was working fine, however it did not load off, so far so good. When these days he stopped loading and kept rebooting alone on the boot screen of note 4 910C. I thought it was a problem in rom I restored my nano backup complete restoration however it did not work either, I tried to flash a rom via twrp the complete installation however it did not work too ... I tried other two rom custom too and it did not work. That's when I decided to use Odin I downloaded the original ROM and did the flash. Flash completed successfully, when the cell phone was to start its first boot. I have the message on the phone saying ... Install DRK files first. Does anyone know how I can solve this problem. I took in the technical assistance of my city after more than a week of waiting the boy said that the phone has no concert.
Related
Hello all hope you will be able to help me.
Device : Nexus S I 9020
So basicly iam kinda new to whole this world of "android" former Iphone user.
last mounth i got my nexus S wich is my first android phone.
As soon as i got it i started to read guids and etc.
Root the device and ofc the nexy step was trying Rom`s.
but then a problem , every time i try to flash a rom i get status 7 error.
tryed every possible combination of restore / wipe etc...
nothing helped , so i came back to the stock one (backup i made before i started)
after a while i discovered the app Rom mananger , wich install rom update recovery etc...
so i updated my recovery and installed CM7 using it.
used it for a while and went back to the stock.
after cople of days tryed to install MIUI using rom manger every thing went clear and after the intall device reboot it self and then stuck on the Google logo with the lock in the botom of the screen.
and nothing helped since then restore , factory reset/restore / wipe`s etc.
as last resort i tryed Odin and it worked like a charm got my device back and runing.
today i tryed to install a new rom AOASP(i think , or some thing like that) in the first time from the recovery (several times) with every possible wipe.
all the time status 7 error , then went to rom mananger and again same thing.
stuck on the google logo.
now iam gonna use Odin again hope it will work this time too.
Any idea how to resolve it , or why this is happen ?
and how can i resolve the status 7 error and what does it mean ?
Thank you all.
(sorry for this been so long , wanted to give as much details as possible)
Contact this guy. Looks like the same problem. If you can't get it going, I can also fix it so just PM me...
http://forum.xda-developers.com/showthread.php?t=1091789
doesnt seem to be the same problem like i had.
Any way at this point i was able to restore my phone using Odin , and then restore it into my stock backup (including all my data and etc...)
but the problem remain the same.
cant install any rom (status 7 error).
and when i try to install any rom using Rom mananger iam stuck on the google logo after the reboot.
so what can i do ?
Problem solved by using Odin ro restore it and after that flash Nanbackup and finally updating the CWM recovery.
If any one get the problem try this
Btw SuperAOSP is GREAT !!!!
gl all.
Hi everyone I just recently purchased a used S4 the GT-i9500. Everything seemed fine until I got home. It detected my T-Mobile Sim fine but I could only access 2G data and could not connect to any WiFi network I came across. The rom was stock 4.2.2 and the phone was rooted pre purchase. So after fiddling around for a few minutes I discovered the previous owner had flashed TWRP v2.4.1.0 as his choice for a Custom Recovery. Now at this point I had decided to flash on a Custom Rom and of course I first made a backup before flashing on WanamLite. Now after attempting to flash it I immediately received a failure. I tried turning off the signature verification and it did not flash. Now in my frustration i attempted to wipe everything and tried flashing Omega Rom v14. Now i was able to go through with the installation and choose what I wished to install and when I pressed Install things went along smoothly until I hit the app SecSafetyAssurance.apk where it freezes. This is a bump that I've run into at least 5 times already. I changed certain options I wanted to install and eventually made it past this and I am prompted to reboot. Now when I do this to my dismay I just receive a black screen. Upon pulling out the battery and attempting to reboot I still receive a black screen. when I boot back into the Recovery and attempt to reboot the system from within TWRP it warns me saying No OS Installed Are you sure you want to reboot. Im at a loss of what to do. I have read about other members suggesting to use ODIN but I am very confused about how to access Download Mode in order to flash a stock rom from SamMobile.com. I could use a few tips or maybe a few options that I'm left with in order to obtain the operation of my phone again. I would like to get my phone back and Im sure some users can relate to how Im feeling so any help at all would be greatly appreciated. Thank you very much in advanced!
JmastahJay56 said:
Hi everyone I just recently purchased a used S4 the GT-i9500. Everything seemed fine until I got home. It detected my T-Mobile Sim fine but I could only access 2G data and could not connect to any WiFi network I came across. The rom was stock 4.2.2 and the phone was rooted pre purchase. So after fiddling around for a few minutes I discovered the previous owner had flashed TWRP v2.4.1.0 as his choice for a Custom Recovery. Now at this point I had decided to flash on a Custom Rom and of course I first made a backup before flashing on WanamLite. Now after attempting to flash it I immediately received a failure. I tried turning off the signature verification and it did not flash. Now in my frustration i attempted to wipe everything and tried flashing Omega Rom v14. Now i was able to go through with the installation and choose what I wished to install and when I pressed Install things went along smoothly until I hit the app SecSafetyAssurance.apk where it freezes. This is a bump that I've run into at least 5 times already. I changed certain options I wanted to install and eventually made it past this and I am prompted to reboot. Now when I do this to my dismay I just receive a black screen. Upon pulling out the battery and attempting to reboot I still receive a black screen. when I boot back into the Recovery and attempt to reboot the system from within TWRP it warns me saying No OS Installed Are you sure you want to reboot. Im at a loss of what to do. I have read about other members suggesting to use ODIN but I am very confused about how to access Download Mode in order to flash a stock rom from SamMobile.com. I could use a few tips or maybe a few options that I'm left with in order to obtain the operation of my phone again. I would like to get my phone back and Im sure some users can relate to how Im feeling so any help at all would be greatly appreciated. Thank you very much in advanced!
Click to expand...
Click to collapse
Well first thing is get the latest stock firmware for your variant from my sign and get odin 3.07
For download mode power off phone unplug,, press volume down home and power all together till something pops up and release then press volume up and connect to pc
Open odin click pda and select that firmware u downloaded start the process
For more info check my sign help thread link it has more options on the same
.
JmastahJay56 said:
Hi everyone I just recently purchased a used S4 the GT-i9500. Everything seemed fine until I got home. It detected my T-Mobile Sim fine but I could only access 2G data and could not connect to any WiFi network I came across. The rom was stock 4.2.2 and the phone was rooted pre purchase. So after fiddling around for a few minutes I discovered the previous owner had flashed TWRP v2.4.1.0 as his choice for a Custom Recovery. Now at this point I had decided to flash on a Custom Rom and of course I first made a backup before flashing on WanamLite. Now after attempting to flash it I immediately received a failure. I tried turning off the signature verification and it did not flash. Now in my frustration i attempted to wipe everything and tried flashing Omega Rom v14. Now i was able to go through with the installation and choose what I wished to install and when I pressed Install things went along smoothly until I hit the app SecSafetyAssurance.apk where it freezes. This is a bump that I've run into at least 5 times already. I changed certain options I wanted to install and eventually made it past this and I am prompted to reboot. Now when I do this to my dismay I just receive a black screen. Upon pulling out the battery and attempting to reboot I still receive a black screen. when I boot back into the Recovery and attempt to reboot the system from within TWRP it warns me saying No OS Installed Are you sure you want to reboot. Im at a loss of what to do. I have read about other members suggesting to use ODIN but I am very confused about how to access Download Mode in order to flash a stock rom from SamMobile.com. I could use a few tips or maybe a few options that I'm left with in order to obtain the operation of my phone again. I would like to get my phone back and Im sure some users can relate to how Im feeling so any help at all would be greatly appreciated. Thank you very much in advanced!
Click to expand...
Click to collapse
Flashing through odin is one option.... some users have reported that there were some hiccups when installing omega 14 because of the aroma script.....try a different rom...there are many others to choose from....or you could flash stock via odin as said on the earlier comment good luck
Feedback
Today I attempted to use ODIN to flash now I am still currently attempting this. When I press the volume down key, power, and home button it takes me to the custom recovery TWRP instead of download mode. The phone did this when I first purchased it. When I still had what appeared to be the stock rom it would always take me to the recovery. When I would use the volume up instead of down it would take me to the factory test mode now mind you this happened when the OS was still installed. When i try that combination now i just receive a blank black screen. Are there any other ways to boot into download mode?
Hey guys, so I've had my Aussie Telstra Note 3 (SM-9005) for just under a month, rooted it with Knox 0x1, installed TWRP 2.6.3.5 and have tried out a few custom ROMs - all went fine. (Last ROM that worked properly was Foxhound 1.0.)
That is until I flashed X-Note Transformer Edition (MJ7). I flashed this through TWRP 2.6.3.5, everything was successful and standard as any other flash, rebooted into the ROM only to find a message saying "Can't play this video" on the very first Interactive Tutorial (Language Select) page. This message appeared multiple times, then more messages saying the system has crashed. Also, everything is extremely slow and barely anything works - including sound, camera, settings, etc. Also Wifi detects networks but cannot connect to them (system crashes). Any time I try to do anything settings related the system bootloops, and I cannot get a mobile signal at all.
Now here's the weird thing, I thought it was just an issue with the ROM not being compatible, so I rebooted to recovery, tried to reflash the previously-working Foxhound 1.0 ROM - SAME ERRORS. Tried a full wipe/format/rm -rf - and install stock ROM from zip - SAME ERRORS. Downloaded the completely stock Telstra Odin ROM, flashed through Odin successfully - SAME ERRORS. Tried to restore EFS (It said successful) - SAME ERRORS... hope you can see where I'm going with this. I've also tried CWM, flashing with different versions of TWRP, full wipe before installing any ROM, etc. tried basically anything I could find on xda without any luck - the ROMs all boot up, but as soon as they load it pops up with the same "Can't play this video" message and everything starts locking up.
This has me really worried since I tripped Knox at the very beginning before Root de la vega, I'm only hoping whoever Telstra use to fix these doesn't care about the counter.
I have literally spent two days without sleep trying everything to fix this and completely failing, so If anyone could help me out I would be forever in your debt, cheers.
zuuus said:
Hey guys, so I've had my Aussie Telstra Note 3 (SM-9005) for just under a month, rooted it with Knox 0x1, installed TWRP 2.6.3.5 and have tried out a few custom ROMs - all went fine. (Last ROM that worked properly was Foxhound 1.0.)
That is until I flashed X-Note Transformer Edition (MJ7). I flashed this through TWRP 2.6.3.5, everything was successful and standard as any other flash, rebooted into the ROM only to find a message saying "Can't play this video" on the very first Interactive Tutorial (Language Select) page. This message appeared multiple times, then more messages saying the system has crashed. Also, everything is extremely slow and barely anything works - including sound, camera, settings, etc. Also Wifi detects networks but cannot connect to them (system crashes). Any time I try to do anything settings related the system bootloops, and I cannot get a mobile signal at all.
Now here's the weird thing, I thought it was just an issue with the ROM not being compatible, so I rebooted to recovery, tried to reflash the previously-working Foxhound 1.0 ROM - SAME ERRORS. Tried a full wipe/format/rm -rf - and install stock ROM from zip - SAME ERRORS. Downloaded the completely stock Telstra Odin ROM, flashed through Odin successfully - SAME ERRORS. Tried to restore EFS (It said successful) - SAME ERRORS... hope you can see where I'm going with this. I've also tried CWM, flashing with different versions of TWRP, full wipe before installing any ROM, etc. tried basically anything I could find on xda without any luck - the ROMs all boot up, but as soon as they load it pops up with the same "Can't play this video" message and everything starts locking up.
This has me really worried since I tripped Knox at the very beginning before Root de la vega, I'm only hoping whoever Telstra use to fix these doesn't care about the counter.
I have literally spent two days without sleep trying everything to fix this and completely failing, so If anyone could help me out I would be forever in your debt, cheers.
Click to expand...
Click to collapse
What was the last version of firmware flashed?
You might need to flash the gsm modem for that firmware version to get it to work especially considering you have bootloops and no reception.
You might also need to use Megawipe to clear any errors that stay on your device after flash.
ultramag69 said:
What was the last version of firmware flashed?
You might need to flash the gsm modem for that firmware version to get it to work especially considering you have bootloops and no reception.
You might also need to use Megawipe to clear any errors that stay on your device after flash.
Click to expand...
Click to collapse
Hey mate, last version of firmware was the Stock Telstra SM-N9005 / TEL ROM I found on www . sammobile . com/firmwares/2/
I have tried at least 10 different ROMs with no luck, every single one does the same thing.
I did send it off to Telstra to try for a repair, they sent it back to me unrepaired due to nothing to do with the software but a 1/4mm scratch my keys made in the chrome plastic around the edge with the words "unable to be repaired due to physical damage" with a little sticker pointing to the scratch. ****ing ridiculous if you ask me.
Honestly I don't know all that much to do with the modems and csc's so it might be that causing my problems but I have tried a bunch of different ones without any change.
At my wits end here, phone is just over 30 days old and I can't use the damn thing.
try odin back to stock, then use kies to "emergency firmware restoore" Kies can be a life saver in some situation, make sure you use beta 3 version
Good morning,
I'm stuck with a big problem on my Note 3 HLTE.
Here's the story : I was previously on the PAC Rom 5.1 and I wanted to change to get the CM13.0 that was just released. So I've performed the full wipe (dalvik, cache and factory reset) and then when I wanted to update the OS, it didn't work. I ended up with a phone in recovery, telling me that there was no OS installed on it.
after several attempts, I then tried to revert back to a stock ROM based on 4.4.2 with Odin. The installation went on without any problems, I was able to get through the first install with my Gmail account and then the phone rebooted, and that's where I got the bootloop curse.
what I did then, was to redo an install via Odin with my carrier stock rom, and I got a FAIL message. So, I retried an install with Odin by adding a PIT file and another ROM still based on 4.4.2. the install worked, as I was able to set up my Gmail account and so on. At this stage, I wasn't able able to get any signal for calls, 4G . In parameters, the baseband was identified as "Unknown". Then, the phone rebooted again, and I got the bootloop curse again...
My last attempt has been to install my carrier stock ROM after performing a full wipe, with ODIN. The install was successful and I got the phone rebooted to stuck on bootloop.
So, here's where I am, and I would like to solve this problem, please. What I think is that, due to the fact that I was on Lollipop, the bootloop might be due to the downgrade attempt to KK. So if there's any way to solve this problem, I'm eager to take it.
Thank you !
Hey Guys,
I've been able to resolve my bootloop problem.
I've installed TWRP with Odin, made a full wipe including data (I've saved them before), and I installed the CM12.1 by Temasek, and way to go, the phone is running fine ^^
Now, I'm just stuck with the lost IMEI thing and baseband. SO my question now is : if I want to install my operator stock ROM for getting back, should I just choose the Lollipop ROM, or can I take the KK one without getting stuck in bootloop again ?
Thank you !
Hey guys, I've encountered a thorny problem on my wife's N910T3, and am running out of ideas about what this could be... so, could really use some help.
Some background: The phone's been working fine for over a year of ownership, mostly on the stock ROM, which gets pretty laggy at times. A few weeks ago I installed a custom ROM (the Acapolypse-X N7 port) to improve performance, and for the past few weeks it's been working perfectly fine on the custom ROM no problem.
Today, when my wife went to check Twitter, the phone crashed and started bootlooping. I had seen a similar issue on my Note 3 before (which turned out to be a specific issue with the kernel I was using), so I figured I would just go into recovery, flash a different kernel or at worst, do a clean install of the ROM.
That's when things started getting weird: The phone would crash while INSIDE recovery during ROM installation (I've never seen a phone crash inside recovery before...) After failing to successfully flash a ROM or, even in cases when it succeeds, fails to boot, I decided to do a full flash back to the latest unmodified stock ROM (since I couldn't find an ODIN-flashable image to download, I used Samsung Kies for this - typically this resolves any kind of left over from previous installations).
On the first attempt, it succeeded - the phone booted into the stock ROM and I was able to start customizing settings. Figuring the issue has been resolved, I went ahead and attempted to root by flashing TWRP through ODIN, and that's when the phone went back to rapidly bootlooping again (it reboots every 2 seconds, I can't even get into recovery when this is occuring). The only way I can return to Recovery is by flashing it again in ODIN (typically this trick will only work once; upon rebooting the phone after that it is prone to start bootlooping again).
Based on the symptoms I suspected the NAND going bad. However, I receive no emmc read/write errors during flashing - all write operations in ODIN results in success and my friend even ran a full storage check via ADB and this phone just doesn't seem to have any bad sectors (I almost wish it were since that would resolve the mystery).
Anyone have any ideas what may be the problem? I have a decent amount of experience installing custom roms on my phones and troubleshooting installation issues, but I've never seen anything like this (crashing/bootlooping directly inside recovery).