Sooo, I'm new to rooting a note 4. I have the the international version, rooting is no issue now... I can do that quite quickly.
My issue is flashing a new from via TWRP. No matter what I do it fails everything, last night I managed to load CM12 but it just stayed in a bootloop for over 30minutes. I just restored it to factory. I thought maybe I'm not destined to have cyanageonmod
Anyways I found another decent room called Beanstalk, it seems like a pretty solid room (thoughts?) but when I go to flash the zip file it just says it can't mouth the file from what ever drive.
What am I doing wrong? I wiping the four things I'm meant to delete before I flash and still nothing
My phone: N910F running on 5.0.1
Baseband:n910fxxuibob4
Ive looked at ever forum possible but can't see what's wrong? I've also tried 3 different versions of Cm12 from different developers that are meant to work...
So again where am I going wrong?
If this is in the wrong place I am sorry! Could I be pointed in the right direction
did you follow instructions for installing and what to do after installing the roms?
xdm9mm said:
did you follow instructions for installing and what to do after installing the roms?
Click to expand...
Click to collapse
Yes followed the instructions like I was doing brain surgery! After... With CM12 it booted up and just kept going around in circles or about an hour, I left it because I thought I needed to, I have up an reverted back. With beanstalk I just got a message in TWRP saying failed to mount on e:/ or something like that.
Anyone have a clue what in doing wrong? I'm going crazy not being able to flash anything. Even a stable build of something. I'm 100% sure what I've downloaded is compatible but still nothing. Either bootlooping or having mount issues.
(bumps are probably not allowed but I've been trying this for 3 days and I'm not where)
Related
Hello. I have a ATT S4. I rooted and flashed this custom rom, http://forum.xda-developers.com/showthread.php?t=2356276. It was working fine no problems for a few months. Today I thought I wanted to try 4.3 and Paranoid Android and flashed the ParanoidAndroid 3.99-RC2 rom from this thread, http://forum.xda-developers.com/showthread.php?t=2314559. My recovery is TWRP. When flashing the new ROM I did get a warning of "no file_contexts". After this my phone has refused to boot. It will turn on, load the Samsung S4 screen, and then stay stuck with this image and never start up. I can still enter recovery. I have tried flashing my original rom which worked perfectly fine before and it acts the same way. I tried to recover a backup I made in TWRP but it fails every time. I have searched in the forums and a common suggestion for bootlooping is to reflash a stock image in ODIN, but most of these people were unable to enter recovery. I would like to get the photos I have on my phone off if at all possible, however it is not a big deal. Anyone know what the issue might be so I don't have to resort to trying ODIN.
It's sounds like you got a bad download of the pa rom. In the future always check the md5 of the files you down load.
If you wiped system, data, dalvik, cache, and android secure prior to flashing your nandroid and it's still not working you're going to have to use odin.
Thanks for replying. I restored it to stock and although it was frozen at the same spot at first, it booted up properly after waiting a bit and a reset from the stock recovery. I would say I'd be more careful next time, but I still don't really know what went wrong.
goldynchyld said:
Thanks for replying. I restored it to stock and although it was frozen at the same spot at first, it booted up properly after waiting a bit and a reset from the stock recovery. I would say I'd be more careful next time, but I still don't really know what went wrong.
Click to expand...
Click to collapse
Having to do a factory reset after Odin to get it past the boot loop is normal. I'm guessing it was a bad download that got you in the problem in the first place. It occurs more frequently than you'd think. That's why it's always good to check the md5 of the file you downloaded
I was suprised since i've flashed countless roms since my s2 and have never checked a single md5. Now I've found out how to check the md5 check sum of what I have downloaded, but for future reference how do I know the reference checksum to verify they are the same? I know it may be a stupid question, but I honestly feel like I am missing something.
goldynchyld said:
I was suprised since i've flashed countless roms since my s2 and have never checked a single md5. Now I've found out how to check the md5 check sum of what I have downloaded, but for future reference how do I know the reference checksum to verify they are the same? I know it may be a stupid question, but I honestly feel like I am missing something.
Click to expand...
Click to collapse
When you download the rom there should be the md5 there. I usually just check the last 5 characters, that's as good as my memory is lol. If they're the same it's highly unlikely the others won't check too.
Hi All,
I just got an SPH-i337 yesterday and attempted to Root + Install Mod.
I ended up rooting and installing Safestrap (TWRP 2.6.x.x). Upon first use I backed up my current OS to a removable SD card using the utility in TWRP. I then, because I was not clear on how to download install CM which was what I was going to, installed ROM Manager and selected CM without setting up a ROM slot. I think this is where I went wrong.
Upon reboot, I was unable to access the Stock ROM and had no options to go to CM. When I attempted to perform a restore from my backup on SD it failed as well and keeps going to the Android recovery screen (not TWRP).
I'm now just trying to go back to stock and have tried using both Heimdall and Odin to no avail. Odin at least provides an error message:
SW REV. CHECK FAIL: Fused:4, Binary:1. What does this mean? That I'm attempting to use an image (.tar.md5 file) which is not current? Is there a way that I can still recover my phone?
..also, please let me know if there are pieces of information that I'm missing. I don't have much to go off of since the firmware and other information (I believe) is not able to be accessed.
Again I just got the phone yesterday. I also have about 40 tabs open that are full of searches that I've been doing regarding this. As yet, no luck.
revolut10n said:
..also, please let me know if there are pieces of information that I'm missing. I don't have much to go off of since the firmware and other information (I believe) is not able to be accessed.
Again I just got the phone yesterday. I also have about 40 tabs open that are full of searches that I've been doing regarding this. As yet, no luck.
Click to expand...
Click to collapse
Look for the mk2 tar files. And do a lot of reading. You went wrong in a number of different areas
revolut10n said:
Hi All,
I just got an SPH-i337 yesterday and attempted to Root + Install Mod.
I ended up rooting and installing Safestrap (TWRP 2.6.x.x). Upon first use I backed up my current OS to a removable SD card using the utility in TWRP. I then, because I was not clear on how to download install CM which was what I was going to, installed ROM Manager and selected CM without setting up a ROM slot. I think this is where I went wrong.
Upon reboot, I was unable to access the Stock ROM and had no options to go to CM. When I attempted to perform a restore from my backup on SD it failed as well and keeps going to the Android recovery screen (not TWRP).
I'm now just trying to go back to stock and have tried using both Heimdall and Odin to no avail. Odin at least provides an error message:
SW REV. CHECK FAIL: Fused:4, Binary:1. What does this mean? That I'm attempting to use an image (.tar.md5 file) which is not current? Is there a way that I can still recover my phone?
Click to expand...
Click to collapse
revolut10n said:
..also, please let me know if there are pieces of information that I'm missing. I don't have much to go off of since the firmware and other information (I believe) is not able to be accessed.
Again I just got the phone yesterday. I also have about 40 tabs open that are full of searches that I've been doing regarding this. As yet, no luck.
Click to expand...
Click to collapse
Safestrap only works with other TW ROMS, so your first issue was trying to use CM. Second, it's not official TWRP and is not even installed to the recovery partition so using ROM Manager was your second issue. Trying to boot into recovery normally will take you to stock recovery since it isn't installed in the recovery partition, there should be a splash screen that comes up after the Samsung Galaxy S4 screen asking to either press for recovery or continue. If that works, you can use the backup from there. If it's gone, you have to use ODIN. The reason you get that SW REV. CHECK FAIL is because you're trying to flash an older firmware than you have. Depending on if you were on 4.2.2 or 4.3 you will either need the MF3 or MK2 .tar.md5 respectively.
jd1639 said:
Look for the mk2 tar files. And do a lot of reading. You went wrong in a number of different areas
Click to expand...
Click to collapse
Thanks for pointing me to those files. I'm sure I did go wrong in a few places as I felt that I was largely just winging it.. There's a TON of information out there. Is there anything specific that I was more wrong than the rest?
revolut10n said:
Thanks for pointing me to those files. I'm sure I did go wrong in a few places as I felt that I was largely just winging it.. There's a TON of information out there. Is there anything specific that I was more wrong than the rest?
Click to expand...
Click to collapse
Deadly sin said it all. Cm and rom manager. Here are the files you need http://forum.xda-developers.com/showthread.php?p=49687770
Thanks everyone. Hell of an introduction to Android, I have to say considering I just got off the WinPhone bandwagon yesterday (been using it for ~7 years).
revolut10n said:
Thanks everyone. Hell of an introduction to Android, I have to say considering I just got off the WinPhone bandwagon yesterday (been using it for ~7 years).
Click to expand...
Click to collapse
The s4 is a very difficult phone to use custom roms on. Once you're back up and running start here and read a lot before doing anything with it http://forum.xda-developers.com/showthread.php?p=42320391
jd1639 said:
The s4 is a very difficult phone to use custom roms on. Once you're back up and running start here and read a lot before doing anything with it http://forum.xda-developers.com/showthread.php?p=42320391
Click to expand...
Click to collapse
Now you tell me - after I've been trying to do this for 12+ hours. Many thanks though - it looks like the MK2 AiO files are working.
jd1639 said:
The s4 is a very difficult phone to use custom roms on. Once you're back up and running start here and read a lot before doing anything with it http://forum.xda-developers.com/showthread.php?p=42320391
Click to expand...
Click to collapse
Unfortunately, it seems that I can't use the method listed directly on that page on account of running the MK2 baseband. If I'm going to go forward it looks like I'll have to use SafeStrap and unofficial TWRM + TW mods for the time being.
Of course, if something about what I'm saying is wrong, I'd be glad to hear it.
revolut10n said:
Unfortunately, it seems that I can't use the method listed directly on that page on account of running the MK2 baseband. If I'm going to go forward it looks like I'll have to use SafeStrap and unofficial TWRM + TW mods for the time being.
Of course, if something about what I'm saying is wrong, I'd be glad to hear it.
Click to expand...
Click to collapse
Check my last Post #50 it should get u an idea and where to find related link. Also check that MK2 INDEX & ROM LIST ....:good:
ive had my note 3 for awhile and have avoided rooting or modding it in any way for quite sometime, but i rooted the stock firmware i believe it was 4.4.2???? im not 100% with towelroot and i was able to install safestrap thats where my success ended I didnt make any backups for whatever dumb reason and also it has been quite sometime since modding any phones, now my phone wont boot into any rom ive tried i have tried two so far and i cant get the factory one back, half the time i cant install roms and the rest of the time they work but they wont boot ive tried creating rom slots but those dont work, read somewhere they arent supported in 4.4.2 ???? and when i tried overwriting the factory it still didnt work, now my phone wont boot into anything anymore and im not quite sure what i did wrong and if there is any way to fix it, i would have like to install knoxraid on this phone since it supposedely fixes the gps issues lots of people have when i try to install that particular rom i get a successful message but then when i wipe cache/dalvik it work and then i hit reboot nothing happens, all i get is a black screen oh and its says that safestrap is disabled
can anyone help i could really use some help here
ecuadorche said:
ive had my note 3 for awhile and have avoided rooting or modding it in any way for quite sometime, but i rooted the stock firmware i believe it was 4.4.2???? im not 100% with towelroot and i was able to install safestrap thats where my success ended I didnt make any backups for whatever dumb reason and also it has been quite sometime since modding any phones, now my phone wont boot into any rom ive tried i have tried two so far and i cant get the factory one back, half the time i cant install roms and the rest of the time they work but they wont boot ive tried creating rom slots but those dont work, read somewhere they arent supported in 4.4.2 ???? and when i tried overwriting the factory it still didnt work, now my phone wont boot into anything anymore and im not quite sure what i did wrong and if there is any way to fix it, i would have like to install knoxraid on this phone since it supposedely fixes the gps issues lots of people have when i try to install that particular rom i get a successful message but then when i wipe cache/dalvik it work and then i hit reboot nothing happens, all i get is a black screen oh and its says that safestrap is disabled
can anyone help i could really use some help here
Click to expand...
Click to collapse
May I know which variant on Note3 you are using.
and what's the OS version? 4.3? or 4.4.2 or 4.4.4
what's your region (CSC).??
I would suggest you to go into download mode and download appropriate stock firmware from SamMobile or from Samsung Updates (Link for N9005) and flash Stock ROM using ODIN.
Thanks.
Hello there,
I am having a little bit of an issue with a new Galaxy Note 4 that i got for my wife. We both bought our devices yesterday, mine from Three, and hers from EE (we are in the UK), both SM-N910F, so i proceeded to root my device and it worked all great. So earlier today i started the exact same procedure, unfortunately, my wifes Note 4 got stuck in a Recovery Boot Loop, and i genuinely don't understand what is happening.
As for the rooting method, i went with the [SM-N910*] CF-Auto-Root and choose the right .tar file, or else it wouldn't of had worked on the first device.
I have read quite a few posts, saw a few videos on youtube, but it far beyond me. I have seen a few people mention that i need to download the German (?) version of the Stock firmware, and then flash it. I seem to have found a link for it on SamMobile but it's gonna take 5 hours to finish, and i don't understand why i would download the German Stock firmware, is that the correct one for her device ?
At this point, is there any way around it ? Why did my device which is the same work perfectly, but not hers ?
I would appreciate any and all help, if you could make it quite detailed for me i would appreciate it even more.
Thank you!
Hi @Vaskie!
Can you enter in download mode?
Hello there @_mone, the following has happened since i posted:
Went ahead and flashed the following: N910FXXU1BOB4_N910FOXA1BOB4_N910FXXU1BOB4_HOME.tar and it made the device reach the home screen, from there i attempted to root using the same method which worked, but it ended installing a few extra applications, which i don't understand how. I also don't understand how flashing a new stock rom didn't make me start the device from the beginning, it already had all my information and went straight to the home screen ready to use. I feel quite confused if im honest.
On the other hand, most things seem to be working perfect, but i am having some issues with the front camera. I have two Note 4s, both bought yesterday from the same place, but one was flashed with the Stock rom (N910FXXU1BOB4_N910FOXA1BOB4_N910FXXU1BOB4_HOME.ta r) due to being stuck in a boot loop. The front camera seems to be massively over exposed compared to the other Note 4, not just a little bit either, making it almost unusable.
Would anyone be able to help ?
Vaskie said:
I also don't understand how flashing a new stock rom didn't make me start the device from the beginning, it already had all my information and went straight to the home screen ready to use. I feel quite confused if im honest.
Click to expand...
Click to collapse
That's because you "dirty" flashed a new ROM on top of the old one.. it was like an "update".
What I suggest you (because you already rooted your phone and your knox is 0x1) is to flash TeamWin Recovery Project from ODIN and then flash a TW ROM from the Galaxy Note 4 Android Development (Snapdragon) page
To do so download "twrp-2.8.7.0-trltexx.img.tar" from here, put your phone in download mode, connect it to the pc via usb, from the pc launch odin, let it recognize your phone, add the downloaded .img.tar file on the pda button, click on the "start" button and let it flash the recovery.
Now download a TW ROM like _alexndr's DevBase from here and this modem and this bootloader.
Then put the downloaded ROM (N910FXXU1POF2_DevBase_alexndr.zip) in your external SDcard. Reboot your phone in recovery mode. From TWRP go Wipe/AdwancedWipe/ and tick DalickCache, System, Data, Internal Storage, Cache and "Swipe to Wipe". After go back to the first page, hit "Install" search "N910FXXU1POF2_DevBase_alexndr.zip" in "/external_sd" and install it. Wipe Dalvick and Cache again and reboot into download mode. Again connect your phone to the PC and launch ODIN now put the downloaded modem "CP_N910FXXU1POF1.tar.md5" in the CP button and the bootloader "BL_N910FXXU1POF2.tar.md5" in the BL button and click on the "start".
Once it is done switch off and on your phone and start again with the latest samsung rom for N910F already with root, busy box and all the fixes by _alexndr
And let us know if you still have problems.
Thank you very, very much for the very well detailed reply @_mone
I will attempt to go ahead with your explanation tomorrow. Would that somehow fix the camera, and i guess the other question is.. is the front camera issue that i explained myself above to do with me "dirty flashing" ?
Is there anything inherently wrong with "dirty flashing" ?
Thank you yet again!
Nothing wrong with dirty flashing.. but sometimes doing so you can create conflicts between old and new rom or leaving "bugs" from the old to the new generating problems in your new os that may wont be there if you performed a clean install. :good:
So, I can't remember what I did to this device, exactly. I got it already in a bootloop. I had seemingly fixed it for a few weeks, but then it started rebooting randomly and then eventually got into another bootloop. I can't remember if that just happened one day or if I was trying to fix the random reboots.
I stopped working on it when a family member gave me their old Nexus 5X. But the other day my Nexus 5X entered into a bootloop because of its well known hardware problem (I think anyway, I wasn't doing anything that should have bricked it). So I decided to pull out the old Galaxy s5 and see if I can fix that instead.
Normally when I flash ROMs onto devices, I do it when the process for the device is pretty well established. As we all know, Samsung devices aren't the easiest to work with. So I remember having to do a bunch of extra ****, download Odin and so forth.
By the way, I have the AT&T G900A version. I boot into recovery and see that it boots into CWM, thats good news obviously. I pick "update through adb". I run ADB through command prompt (btw, someone should update the guides on this site to mention that Powershell doesn't play nice with ADB commands, that was like 20 minutes of hair pulling frustration) and it recognizes the device. I wipe all the user data and cache etc and attempt to flash a custom ROM I found on this site: APTOS found here.
I get an
Finding update package. . .
Opening update package. . .
Verifying update package. . .
E:footer is wrong
E:signature verification failed
So then I downloaded the stock firmware ROM titled "SM-G900A 4.4.2 G900AUCU1ANCE Firmware.rar" and get the same errors.
So, obviously I am forgetting something. I know there are a lot of guides on here and the answer is probably out there somewhere, the problem is that most of those guides are for people starting at square 1 without CWM or TWRP installed. Can anyone help me from where I am at? I uninstalled Odin a while ago but could definitely reinstall it. Was hoping to do this from where I am at, since CWM is already installed.
Anyone have any ideas on what step I'm forgetting? Do I need to flash other things before the ROM? Should I just start completely over with ODIN and the rest of it?
P.S. I have more experience with TWRP than CWM but I remember having trouble getting TWRP to work but did manage to get CWM to install as an alternative.
Thanks in advance!