So I use to be familiar with flashing, unlocking, & rooting my Droid 2 Global, & my Nexus 7. And while I did successfully temp-root my note 4 a while ago, I have since fallen out of the whole procedure and have a plain old stock 'n locked note 4 that I would like to Flash EmotionOS on it.
I remember bits and pieces, but not the correct order and how exactly I flash a ROM to my note 4, would anyone be able to give me a few pointers on what order I need to do what in, and possibly what the best method(s) would be so that I can flash EmotionOS onto my note 4?
I am using this XDA guide as my current reference for EmotionOS
Thank you in advance
ChapDaddy65 said:
So I use to be familiar with flashing, unlocking, & rooting my Droid 2 Global, & my Nexus 7. And while I did successfully temp-root my note 4 a while ago, I have since fallen out of the whole procedure and have a plain old stock 'n locked note 4 that I would like to Flash EmotionOS on it.
I remember bits and pieces, but not the correct order and how exactly I flash a ROM to my note 4, would anyone be able to give me a few pointers on what order I need to do what in, and possibly what the best method(s) would be so that I can flash EmotionOS onto my note 4?
I am using this XDA guide as my current reference for EmotionOS
Thank you in advance
Click to expand...
Click to collapse
First, you'll need to root your device on stock 5.1.1 BPA1, this guide is fairly easy to follow. Then you'll need to upgrade to 6.0.1 CPD1 and root that too, using this guide. Then you'll need to flash the partial CPJ2 firmware also found here, before you can then flash EmotionOS.
Rooting the note 4 is a lot more work. I loved my note 3 and being able to do it with an app. "Towelroot" it made life so simple. Lol.
Sent from my SM-N910V using Tapatalk
quinciebee said:
First, you'll need to root your device on stock 5.1.1 BPA1, this guide is fairly easy to follow. Then you'll need to upgrade to 6.0.1 CPD1 and root that too, using this guide. Then you'll need to flash the partial CPJ2 firmware also found here, before you can then flash EmotionOS.
Click to expand...
Click to collapse
I'm on 5.0.1
Looks like I need to update..
Its just so time consuming its a daunting task.
I'm happy for now but may take a peek at emotion.
Nope, I'm not signing up for issues. The first page talks of re boots, no SMS service, no phone service I'll stick with the sure thing my phone is working I'll be at sometimes laggy but that's probably an overload issue with my apps
Sent from my SM-N910V using Tapatalk
quinciebee said:
First, you'll need to root your device on stock 5.1.1 BPA1, this guide is fairly easy to follow. Then you'll need to upgrade to 6.0.1 CPD1 and root that too, using this guide. Then you'll need to flash the partial CPJ2 firmware also found here, before you can then flash EmotionOS.
Click to expand...
Click to collapse
If I'm already on 6.0.1 stock, do I still need to downgrade & root to 5.1.1, just to upgrade back to 6.0.1 & root?
ChapDaddy65 said:
If I'm already on 6.0.1 stock, do I still need to downgrade & root to 5.1.1, just to upgrade back to 6.0.1 & root?
Click to expand...
Click to collapse
Yes you do.
ChapDaddy65 said:
If I'm already on 6.0.1 stock, do I still need to downgrade & root to 5.1.1, just to upgrade back to 6.0.1 & root?
Click to expand...
Click to collapse
That's exactly what you need to do, it's tedious, I know, but very worth it
ok, so I was able to load 5.1.1, root w/KingoRoot, enable dev mode, install TWRP 3.0.2, & reload 5.1.1, but now I'm stuck in a bootloop.
when I first loaded 5.1.1 stock w/o TWRP, I was able to get out of the bootloop by wiping the system and cache and it loaded fine, but now when I try to wipe the cache with TWRP it gets stuck in the bootloop.
How do I get out of the loop with TWRP?
ChapDaddy65 said:
ok, so I was able to load 5.1.1, root w/KingoRoot, enable dev mode, install TWRP 3.0.2, & reload 5.1.1, but now I'm stuck in a bootloop.
when I first loaded 5.1.1 stock w/o TWRP, I was able to get out of the bootloop by wiping the system and cache and it loaded fine, but now when I try to wipe the cache with TWRP it gets stuck in the bootloop.
How do I get out of the loop with TWRP?
Click to expand...
Click to collapse
Pull the battery and SD card, wait for like 30 seconds, then put only the battery back in. Boot into TWRP, pop the SD card back in, use the Advanced Wipe to wipe the SD card and cache, then reboot. If you don't want to wipe your SD, then don't put it back in.
quinciebee said:
Pull the battery and SD card, wait for like 30 seconds, then put only the battery back in. Boot into TWRP, pop the SD card back in, use the Advanced Wipe to wipe the SD card and cache, then reboot. If you don't want to wipe your SD, then don't put it back in.
Click to expand...
Click to collapse
just did all that, and still looping
ChapDaddy65 said:
just did all that, and still looping
Click to expand...
Click to collapse
Follow this guide, beginning at Phase 4.
okay, I think I may have lost root after the 5.1.1 reload, in that case I'll start over.
Is there a simple way to get the recovery.tar file so I can remove TWRP, or is there an alternative method without having to remove TWRP?
ChapDaddy65 said:
okay, I think I may have lost root after the 5.1.1 reload, in that case I'll start over.
Is there a simple way to get the recovery.tar file so I can remove TWRP, or is there an alternative method without having to remove TWRP?
Click to expand...
Click to collapse
Flashing the systemonlyN910V-5.1.1.tar should help you keep TWRP.
quinciebee said:
Flashing the systemonlyN910V-5.1.1.tar should help you keep TWRP.
Click to expand...
Click to collapse
well currently TWRP is what is preventing me from booting the phone, I didnt know if there was an alternate method to "re-doing" the guide without having to start from the very beginning. So long as I have TWRP installed, I can't seem to progress past the second bootloop.
Also Kies 3 is telling me it no longer supports the note 4 because of SmartSwitch (which is not currently installed on my PC) being capable of managing my note 4 now. Not really a huge deal now that I'm downloading the stock 5.1.1 from SamMobile, but that notice struck me as odd that Kies wont touch my note 4, even before all this happened.
ChapDaddy65 said:
just did all that, and still looping
Click to expand...
Click to collapse
TWRP doesn't format the sd properly. Pull the sd and do a diskpart on windows to clean it
ziggy71 said:
TWRP doesn't format the sd properly. Pull the sd and do a diskpart on windows to clean it
Click to expand...
Click to collapse
I dont have anything special on my SD card currently, would it be okay to just pull the SD for the whole process?
ChapDaddy65 said:
I dont have anything special on my SD card currently, would it be okay to just pull the SD for the whole process?
Click to expand...
Click to collapse
No, you need a sd in for the bootloader unlock process. Wipe it, unlock, wipe it, unlock. And wipe it with diskpart. TWRP doesn't properly wipe the card, and will result in a bootloop.
So after multiple attempts and flashes trying to get past bootlooping at the same point, I'm going to take a break from installing emotionOS for a bit, mainly because I havent been able to use wifi now for some reason. at this point im more concerned about getting wifi back.
I've tried flashing numerous times to 5.1.1, factory reset and wiping cache, and after I get my phone back to normal, I try turning on WiFi in the settings and it stalls, it waits for about 5 minutes and then shuts back off, never actually enabling wifi. Please Advise?
Hi guys..!
I'm wondering if this thread is to help about my issue. Please, let me talk about it: I have a samsung note4 sm-n910v in soft brick condition (I think), and was trying to flash it with Odin by 3 different ways: 1- flashing stock firmware 5.0.1 (N910VVRU2BOF1_N910VVZW2BOF1_N910VVRU2BOF1_HOME.tar), 2- flashing with factory binary file (COMBINATION_VZW_FA44_N910VVRU2APB1_VZW2APB1_2932719_REV00_user_mid_noship_MULTI_CERT.tar), and 3- flashing with partial firmware (N910VVRU2BOF1_PartialFirmware.tar). For by 3 ways, my phone is stuck (I can not access to call or text messages). If needs more details, please, let me know. Please, could anybody help me? I'm stuck in explained situation.
Good news update about my issue..! I did a good flashing by Odin few hours ago, just with a repair firmware file for my N910V Note4..!
If somebody has same issue or similar I think him/her could use it to resolve too. Thanks to xda user Trex888 who published the next link to download correct file for my phone: http://www.tsar3000.com/Joomla/inde...ader-csc-pit-files&catid=55:samsung&Itemid=82
Complete thread link is: https://forum.xda-developers.com/note-4/help/software-update-failed-sm910v-t3498246
P.D.: Sorry for my writed english, and thanks a lot again to Trex888..!
Related
Hey guys,
glad to say that ive been able to debrick my phone like 5 times in a row successfully which is a weight off my shoulders.
however, once im debricked, rooted, cwm installed, and all .img's pushed i try to flash a custom rom. i've tried every one and i get bootloops every time... they seem to install just fine. very normal timing and everything, no errors. any ideas?
Don't format /data. Are you doing that? Link the steps you're taking when you are in cwm to flash over the rom. Maybe something is amiss.
nope not formatting data. ive been doing wipe cache, wipe dalvik, and format /system.
Man I was in the same boat as you but was finally able to get it sorted this morning. What I highly, highly recommend is starting as fresh and as clean as you possibly can. That is before you do CWM or anything like that restore your phone with the Korean kdz, push all the images (system being last) then make sure you have a bootable, working phone. Also I would recommend using different/new/fresh .img files...I downloaded ones from the unbricking thread and only used a copy of my baseband.img. I had a feeling one of my files wasn't quite right so starting with all new ones may have helped.
Don't try anything from a backup or do a restore or anything-start fresh and make sure everything works as it should. From there do CWM and then do your ROMS. I know you're almost there and its a headache to keep starting from the bottom but do it all one step at a time, in order and you will find success.
Good luck!
good call. i havent been pushing all the .img's. just the three he mentioned above. let me try this for the 80th time. ill let you know how it goes. just curious, do you use the v10f or v10i kdz?
Are the ROMs installing in less than 30 seconds or 2-5 minutes? If its less than 30 seconds, you need to flash it again.
If i was you i would install the new CWM, once it installs the new CWM it'll work.
gte460z said:
Are the ROMs installing in less than 30 seconds or 2-5 minutes? If its less than 30 seconds, you need to flash it again.
Click to expand...
Click to collapse
yep i know that part. thanks
Revolution said:
If i was you i would install the new CWM, once it installs the new CWM it'll work.
Click to expand...
Click to collapse
new cwm?? as in the newest version available?does it work on the nitro?
[CWM][24/01] ClockworkMod 5 Recovery For LG Nitro HD
http://forum.xda-developers.com/forumdisplay.php?f=1448
Follow instruction's then try flashing a ROM it should fix your problem.
ive been using cwm... doesnt get rid of the bootloops
mic.mayorga said:
ive been using cwm... doesnt get rid of the bootloops
Click to expand...
Click to collapse
I'm not sure you understand bro, there is a NEW UPDATE
Update your CWM and it'll fix this issue.
I had the same problem for awhile. Had to use the Unbricker:http://forum.xda-developers.com/showthread.php?t=1412367
Followed ALL instructions, including "Restoring Nitro HD partition images" before flashing CWM. After that, no more bootloops and installed Revolutions rom w/out issue. Reboots just fine after.
I used the V10i-the direct download from LG...I think all the other recommendations are spot on but first and foremost get everything squared away with a fresh install of the kdz, all the images (in the proper order), the new version of CWM and then your rom of choice...Hope you're making some progress!
I'm on the new CWM and still have a loop if I reboot. Then I need to restore from CWM to get going again.
The soft brick boot loop I got was caused solely by format /system. I did not format /data.
I went through the whole deal last night and this morning and was able to get a fresh start on everything and am now running the HD ROM and haven't had a boot loop since I got everything back up and running...
I really think starting with the freshest install and making sure everything is functional step by step is where you'll be able to get through all that mess...just stay away from and restores or using any .img files that may have any software glitches as you'll get back to square one every time.
Hope you get it sorted out!
nah bro, i had the new update. no worries tho i pushed all the images in the debrick and fixed it. thanks for all the help guys B)
Tight work-glad you were able to get it straight! Now once you get it where you want make a new backup with Nandroid and CWM and you'll be golden in case anything else happens.
Hi all,
I'm in a boot loop too, so may I ask you guys a stupid question:
How to restore the previous system.img?
Thanks
huydq5000 said:
Hi all,
I'm in a boot loop too, so may I ask you guys a stupid question:
How to restore the previous system.img?
Thanks
Click to expand...
Click to collapse
Go look at the thread "[Solved] Unbricking solution...". Follow it to the T, however, i'd recommend using v10i.kdz rather than v10f.kdz. Definitely try the f version first but if it doesn't work try i. That's what I did. Basically what you're going to want to do is:
1. Restore the phone to a korean image using the v10i (or f) file and the LG software provided and referenced in the unblocking thread.
2. Once booted, root the phone. (specific instructions for v10i are in a thread somewhere linked by [email protected] v10f use either SuperOneClick root or DoomLord v4. Make sure you have adb installed for doomlord.
3. Once rooted use adb to push over stock .img files in this order: boot, recovery, firmware, baseband, system.
4. after the files are pushed boot into phone and root again (optional).
5. Install CWM5 through adb or terminal emulator.
Good luck, let me know if you have any questions and I can go into more detail.
Hello all-
I was just recently running CM 10.2 RC1 but had to do an install of the correct gapps as it was randomly rebooting. Well the device now is stuck on the Samsung Galaxy S3 screen with the BLUE cyanogen. I have access to TWRP and am able to reflash the .zip file for CM 10.2 RC1 yet it still won't boot? I did the wipe of dalvik, cache, data and system but still no luck? The device is NOT recognized in Odin. I just want to get the phone up and running again, even if it means root is lost.
Please help!!
DroidJay123 said:
Hello all-
I was just recently running CM 10.2 RC1 but had to do an install of the correct gapps as it was randomly rebooting. Well the device now is stuck on the Samsung Galaxy S3 screen with the BLUE cyanogen. I have access to TWRP and am able to reflash the .zip file for CM 10.2 RC1 yet it still won't boot? I did the wipe of dalvik, cache, data and system but still no luck? The device is NOT recognized in Odin. I just want to get the phone up and running again, even if it means root is lost.
Please help!!
Click to expand...
Click to collapse
Do you have it put into Download Mode before you plug it into the computer for Odin to recognize it? If I had it plugged in before I put mine in download mode Odin would not want to pick it up.'
Mr. Rageface
Mr.Rageface said:
Do you have it put into Download Mode before you plug it into the computer for Odin to recognize it? If I had it plugged in before I put mine in download mode Odin would not want to pick it up.'
Mr. Rageface
Click to expand...
Click to collapse
Yes it is recognized once in Download mode...sorry about that. What can I do to get it up and running? I am not new to flashing, etc so it's got me really upset that I cant get it to boot. What could possibly go wrong?
Get a sd card>download a new rom and put the rom in the sd card and flash like a normal ROM
http://fs1.d-h.st/download/00023/E5R/I747UCDLK3_I747ATTDLK3_I747UCDLK3_HOME.tar.md5 You can download that file and put it in the PDA section once you run Odin and run it from there. This will put your phone back to the Stock Rom 4.1.1 and you can restart from there if you want.
Mr. Rageface
xXFl4sh said:
Get a sd card>download a new rom and put the rom in the sd card and flash like a normal ROM
Click to expand...
Click to collapse
I do have an sd card. Phone isn't recognized in Windows so Im not familiar with how I can get the ROM file onto the card from the computer? Can I download the latest AT&T Stock ROM and flash it via Odin?
What your saying is flash a ROM from the external SD card?
DroidJay123 said:
I do have an sd card. Phone isn't recognized in Windows so Im not familiar with how I can get the ROM file onto the card from the computer? Can I download the latest AT&T Stock ROM and flash it via Odin?
What your saying is flash a ROM from the external SD card?
Click to expand...
Click to collapse
No, with the file I told you to download you do not need to have a SD card because you can't boot into the rom you have Windows will not recognize the phone like normal to drag and drop to it. So with this file you can save it to your computer, Open Odin, put your phone into Download Mode, plug it into the computer so that Odin detects it. Then Click PDA and browse to the file you downloaded and tell it to use that file and then Run the process and it will install the original rom onto your phone.
Mr. Rageface
Edit: Sorry I did not realize your previous comment was to xXFl4sh.
Mr.Rageface said:
No, with the file I told you to download you do not need to have a SD card because you can't boot into the rom you have Windows will not recognize the phone like normal to drag and drop to it. So with this file you can save it to your computer, Open Odin, put your phone into Download Mode, plug it into the computer so that Odin detects it. Then Click PDA and browse to the file you downloaded and tell it to use that file and then Run the process and it will install the original rom onto your phone.
Mr. Rageface
Edit: Sorry I did not realize your previous comment was to xXFl4sh.
Click to expand...
Click to collapse
Ok I did the process with the file you referenced. Everything succeeded in Odin with no errors. It's still stuck on just showing the Samsung Galaxy SIII screen but now without the blue cyanogen? What is wrong with this phone??
DroidJay123 said:
Ok I did the process with the file you referenced. Everything succeeded in Odin with no errors. It's still stuck on just showing the Samsung Galaxy SIII screen but now without the blue cyanogen? What is wrong with this phone??
Click to expand...
Click to collapse
Can you get into recovery mode by any chance? If you can do that then it should be possible to do a factory reset from within Recovery Mode and possibly get you past the boot screen. If that doesn't help let me know and I will see what else I can find out for you. Also what all did you have checked and unchecked when you Ran Odin to reinstall the Stock Rom? If you had any of them other than Auto-Reboot on that may also have caused a problem http://forum.xda-developers.com/showthread.php?t=1722686 here is a forum that will show you how to use Odin. I apologize for not remembering about telling you what to check and uncheck. But try recovery mode first and do a factory reset and if that does not work, redo the odin install this time only having Auto-Reboot checked.
Mr.Rageface
Mr.Rageface said:
Can you get into recovery mode by any chance? If you can do that then it should be possible to do a factory reset from within Recovery Mode and possibly get you past the boot screen. If that doesn't help let me know and I will see what else I can find out for you. Also what all did you have checked and unchecked when you Ran Odin to reinstall the Stock Rom? If you had any of them other than Auto-Reboot on that may also have caused a problem http://forum.xda-developers.com/showthread.php?t=1722686 here is a forum that will show you how to use Odin. I apologize for not remembering about telling you what to check and uncheck. But try recovery mode first and do a factory reset and if that does not work, redo the odin install this time only having Auto-Reboot checked.
Mr.Rageface
Click to expand...
Click to collapse
Thanks man! I went back into Recovery and did a factory reset/wipe data and it finally got past that screen. Thanks again for your guidance and help. Any ideas as to what could have possibly caused the issue in the first place? I do want to re-root the device again and I am assuming my best bet is to flash a Stock ROM like you referenced with ROOT injected? What order should I follow, flashing a Stock w/Root injected...and then the Recovery of choice? Or vice-versa? What do you recommend?
Again, your timely responses were greatly appreciated. Was really worried I would have to take it to ATT.
DroidJay123 said:
Thanks man! I went back into Recovery and did a factory reset/wipe data and it finally got past that screen. Thanks again for your guidance and help. Any ideas as to what could have possibly caused the issue in the first place? I do want to re-root the device again and I am assuming my best bet is to flash a Stock ROM like you referenced with ROOT injected? What order should I follow, flashing a Stock w/Root injected...and then the Recovery of choice? Or vice-versa? What do you recommend?
Again, your timely responses were greatly appreciated. Was really worried I would have to take it to ATT.
Click to expand...
Click to collapse
It could have been several things that could cause the ROM to do that. I recommend that you make sure that your Bootloader is up to date and then go from there. Download the newest CWM, do a backup of your current rom so that you can flash back to it if you phone messes up. Then when you try to install a new ROM make sure you Wipe: Data then Cache, then Dalvik Cache in Advanced then Format /System. Then from there Install the new Rom, then install the correct GApps, then wipe Cache and Dalvik cache then Reboot into System. It takes messing up a few times to get it right but as long as you follow the guides pretty close and keep a good backup that you know works or keep the knowledge of how to Inject the Stock Rom to your phone when it messes up you shouldn't have much to worry about.
Mr. Rageface
Mr.Rageface said:
It could have been several things that could cause the ROM to do that. I recommend that you make sure that your Bootloader is up to date and then go from there. Download the newest CWM, do a backup of your current rom so that you can flash back to it if you phone messes up. Then when you try to install a new ROM make sure you Wipe: Data then Cache, then Dalvik Cache in Advanced then Format /System. Then from there Install the new Rom, then install the correct GApps, then wipe Cache and Dalvik cache then Reboot into System. It takes messing up a few times to get it right but as long as you follow the guides pretty close and keep a good backup that you know works or keep the knowledge of how to Inject the Stock Rom to your phone when it messes up you shouldn't have much to worry about.
Mr. Rageface
Click to expand...
Click to collapse
Sounds good. Thanks for the info. Obviously the device is not currently rooted or did the Factory Rom file you gave me have root injected? Do you have a recommended way of achieving Root with the Samsung SG3? Just installing a custom Recovery won't achieve Root, correct?
Thanks!
DroidJay123 said:
Sounds good. Thanks for the info. Obviously the device is not currently rooted or did the Factory Rom file you gave me have root injected? Do you have a recommended way of achieving Root with the Samsung SG3? Just installing a custom Recovery won't achieve Root, correct?
Thanks!
Click to expand...
Click to collapse
BTW, how can I confirm I have the most recent bootloader version? It looks like my phone's current baseband version is i747UCDLK3. I did download the boot_CWM_i747UCDMG2.zip file and put it on the internal storage. Do I just want to flash that file to update my bootloader?
Thanks again!
-Jay
Yea that is the newest baseband and yea you just flash it. As far as rooting the phone and everything I recommend this forum. http://forum.xda-developers.com/showthread.php?t=1725839 It has just about everything you could need to know!
Mr.Rageface
Mr.Rageface said:
Yea that is the newest baseband and yea you just flash it. As far as rooting the phone and everything I recommend this forum. http://forum.xda-developers.com/showthread.php?t=1725839 It has just about everything you could need to know!
Mr.Rageface
Click to expand...
Click to collapse
Thanks for the information. The phone that has been all screwed up and the reason I posted a thread in the first place is my gf's GS3. I have her's rooted again and running. I am going to update her baseband version and then install a custom ROM so she's up to 4.3.1. As far as mine goes, I have been fine. I myself also still have the outdated bootloader version. Is it ok to just flash that update for the bootloader without it doing anything wrong? I'm asking this since I'm rooted and running a custom ROM with no current problems. In other words, I don't want to end up saying "it wasn't broke, why did I mess with it" ? I did bookmark that thread you referenced in your last message. Damn that thread is LOADED with just about everything one would possibly need to know about Android and making it their own.
So my g/f accepted the OTA update today (not knowing obviously) and she got updated to 4.3 via AT&T, unfortunately!! I attempted to flash the latest Liquid Smooth ROM and I continue to get a FAILED message during installation. It mentions a bunch of bootloader numbers ( I am assuming the only ones this ROM is compatible with?) So is there any way to roll the bootloader back to a compatible one or just go a different route for the custom ROM?
Also, I attempted flashing the file to update my baseband yet when I so into the device, it doesn't show as having the updated version? Is there a different way of doing it or maybe a different file?
I'm not to sure about the troubles that may come about since your gf went with the 4.3 OTA but If I am not mistaken it will need to be downgraded before you try doing anything else to it and if it is not showing that you updated your bootloader on your phone I recommend grabbing the App called Root Checker to double check then look for another file, tho unless it failed it should have updated it or messed up your phone one.
Hello everyone,
After a long fight to try and get this phone back to normal, everything seemed good,
except not really
I started on a buggy CM11 version. Sick of it, I downloaded a 4.4.4 stock rom. I had to disable firewall and defender, but I got Odin to flash my md5. I got through everything and it booted successfully. After signing in and all that jazz, I find out that my WiFi isn't working. After a few reboots, My 4G finally works and everything seems to be steady.
Then, after exploring the rest of the phone I find out that all my apps from last ROM are still there. I know that you are supposed to wipe before flashing, but I was told that Odin will take care of that. It obviously didn't.
After THAT, I try to boot into Recovery as the next sensible step is to try to wipe my data and cache. I turn the phone off and press (Vol up + Home + Pwr) and the first boot screen shows for a moment. It says in blue "RECOVERY BOOTING" in the corner. Right after, it disappears and in another second it does the same screen without the "RECOVERY BOOTING". And as presumed, it does a regular boot.
What did I miss? How can I wipe my phone from recovery? How can I fix my problem with Wifi?
Reflash in Odin.
Make sure you have the correct stock rom. If you flash the "md5" you may have flashed the wrong thing. The md5 is not tge firmware, that is just the code that verifies your firmware file is not corrupted.
If your old apps were still there, you flashed the wrong thing. There is no way to flash stock firmware in odin and not wipe the data partition.
You are correct then
Yeah, I flashed a tar.md5 in Odin. It gave me a new ROM but all my apps are there. After all that, I still can't go to recovery. I tried using the terminal and ROM Toolbox to go there, both didn't work. Can I just leave it as it is and find a way to recovery or is the only way to go to bootloader and flash a correct file to get to recovery?
Flash twrp and see if it will reboot into recovery, then factory reset and flash latest firmware with Odin right after. Odin will NOT wipe data. It has to be done manually
serio22 said:
Flash twrp and see if it will reboot into recovery, then factory reset and flash latest firmware with Odin right after. Odin will NOT wipe data. It has to be done manually
Click to expand...
Click to collapse
It depends on what you ate flashing.
If you are flashing a full stock factory image it will wipe user data. If you are just flashing a system partition it won't.
Essem G said:
Hello everyone,
After a long fight to try and get this phone back to normal, everything seemed good,
except not really
I started on a buggy CM11 version. Sick of it, I downloaded a 4.4.4 stock rom. I had to disable firewall and defender, but I got Odin to flash my md5. I got through everything and it booted successfully. After signing in and all that jazz, I find out that my WiFi isn't working. After a few reboots, My 4G finally works and everything seems to be steady.
Then, after exploring the rest of the phone I find out that all my apps from last ROM are still there. I know that you are supposed to wipe before flashing, but I was told that Odin will take care of that. It obviously didn't.
After THAT, I try to boot into Recovery as the next sensible step is to try to wipe my data and cache. I turn the phone off and press (Vol up + Home + Pwr) and the first boot screen shows for a moment. It says in blue "RECOVERY BOOTING" in the corner. Right after, it disappears and in another second it does the same screen without the "RECOVERY BOOTING". And as presumed, it does a regular boot.
What did I miss? How can I wipe my phone from recovery? How can I fix my problem with Wifi?
Click to expand...
Click to collapse
Fkash twrp and format system, data, cache and preload and install a deodexed stock os
g7755725 said:
Fkash twrp and format system, data, cache and preload and install a deodexed stock os
Click to expand...
Click to collapse
Also this. This gives you more control over the whole process
Skipjacks said:
Also this. This gives you more control over the whole process
Click to expand...
Click to collapse
How do I know whatever I download is deodexed? And I went to a page of ROMs someone gave me and I downloaded the NK2 version, which also gave me a tar.md5. If I want the correct thing to flash, what should I flash?
Essem G said:
How do I know whatever I download is deodexed? And I went to a page of ROMs someone gave me and I downloaded the NK2 version, which also gave me a tar.md5. If I want the correct thing to flash, what should I flash?
Click to expand...
Click to collapse
The first post of any customized stock rom will tell you if its deodexed. If it doesn't say it...its not.
@Essem G:
Any updates for us? I'm following this thread because I have similar problems with my WiFi not working after upgrading from 4.2.2.
Any luck getting TWRP flashed?
Also I believe that the stock firmwares do come as tar.md5's, as in the file: M919UVUFNK2_M919TMBFNK2_M919UVUFNK2_HOME.tar.md5 from ShinySide's stock firmware thread.
As for the WiFi issue, from the hours of reading I've done it looks like this problem occurs when you upgrade your firmware, but it no longer matches the bootloader. Such as bootloader (Baseband) showing MDL, but Build Number showing NH7, NK2, etc. What does your show?
This thread may be of use to you when you get back to a working ROM. Good luck!
@RavenMind1
Everyone has been saying different answers and i've put off fixing my device for a while. I'm just afraid i'll brick it forever and have another nightmare after this current one. So no, there has been no progress. I think i'm gonna try to flash Philz and format my system, then flash a deodexed rom. @g7755725 said that you can flash TWRP, but I usually use Philz. It appears to be that I have lost root access because no root features work and SuperSU won't recognize it. Will everything work or am I setting my self up for disaster?
Edit: Where can I find a deodexed rom? I desperately need one, thanks
Essem G said:
@RavenMind1
Everyone has been saying different answers and i've put off fixing my device for a while. I'm just afraid i'll brick it forever and have another nightmare after this current one. So no, there has been no progress. I think i'm gonna try to flash Philz and format my system, then flash a deodexed rom. @g7755725 said that you can flash TWRP, but I usually use Philz. It appears to be that I have lost root access because no root features work and SuperSU won't recognize it. Will everything work or am I setting my self up for disaster?
Edit: Where can I find a deodexed rom? I desperately need one, thanks
Click to expand...
Click to collapse
Look in the forums for deodexed rom theirs a bunch and untouched as well i had philz but it eoukdnt boot my s4 so i had to switch to twrp because it does better then any recovery
g7755725 said:
Look in the forums for deodexed rom theirs a bunch and untouched as well i had philz but it eoukdnt boot my s4 so i had to switch to twrp because it does better then any recovery
Click to expand...
Click to collapse
Thanks for the support so far, but has this problem occured before? do you think the steps i've listed will solve this? Im just trying to make sure that I know exactly what to do before I go in. Thanks
Essem G said:
Thanks for the support so far, but has this problem occured before? do you think the steps i've listed will solve this? Im just trying to make sure that I know exactly what to do before I go in. Thanks[/Q] it should
Click to expand...
Click to collapse
@g7755725 I downloaded a deodexed rom from the SkipJacks guy (different page than what you sent me) and it's a little under 9MB... how could this possibly be a ROM?
Essem G said:
@g7755725 I downloaded a deodexed rom from the SkipJacks guy (different page than what you sent me) and it's a little under 9MB... how could this possibly be a ROM?
Click to expand...
Click to collapse
Have you tried my gamerrom Ultimate 1 its basically stock touchwiz of if Official NK2 M919UVUFNK2 with stweaks and no bloatware here is the thread gru 1 is in.the botyom of the thread http://forum.xda-developers.com/galaxy-s4-tmobile/development/stock-os-gamerrom-ultimate-2-touchwiz-t3078467
Sounds cool but i would have been interested a few months ago. I'm trying to sell the phone so I need to get it back to stock. Appreciate all the help and I think it's cool that you make ROMs
Essem G said:
Sounds cool but i would have been interested a few months ago. I'm trying to sell the phone so I need to get it back to stock. Appreciate all the help and I think it's cool that you make ROMs
Click to expand...
Click to collapse
If you're trying to go back to complete stock then just Odin NK2 firmware. http://forum.xda-developers.com/galaxy-s4-tmobile/general/firmwares-official-mdl-mk2-nb4-t2816508 I used the NK2 from here about 2 days ago to go back to stock.
touch screen bugging out
Ok so my phone for some reason can't click on the exact location i seem to want to press
idk i was trying to flash the silly roms you guys have around here. for stock galaxy note 4 spr
i've been flashing for a while
and it seems none of them work anymore
i use the latest TWRP even used the other one CWM or something like that
i used odin even up to .10 from 1.85 even lower and still can't
even when i install (seems to be the only rom i can cm12)
the locations i press on my screen are buged out. so i have to press higher than i should to even get a click and its hard to text or anything.
i did factory resets, cashe wipes. deleted partitions.. what am i doing wrong ??
why can't this annoying this go away what am i missing guys ???
and why is it only 1 rom can flash on my phone ?? and i can't go back to any lollipop or anything ??
(i also tried flashing a superSU from the tWRP .. when i used CM 12 and it all successed but still
i have this thing where i can't click anywhere im on my phone directly i have to try and feel it out.. please help
1)what software version are you on now?
2)what rom are you trying to flash?
Note4 Rocking a Hybrid Rom
Not long ago, it was discovered flashing the wrong recovery will mess up the lock-screen.
Some were solved with KIES firmware restore; no root, straight to dialer type *#2663# and then TSP FW update. If KIES won't update it, power down, pull battery 30 seconds, Odin stock tar and boot then the dialer code and update.
Do that after you determine which stock tar or KIES update is recommended from Your response above.
Sent from my SM-N910P using Tapatalk
schlepprock said:
1)what software version are you on now?
2)what rom are you trying to flash?
Note4 Rocking a Hybrid Rom
Click to expand...
Click to collapse
I am using
Cyanogenmod version
12.1-20150814-nightly-trltespr 5.1.1
kernel 3.10.40-gef59855
baseversion
N910PVPU4COG5
GALAXY NOTE 4 SPRINT
How ever im trying to flash back to stock evrything.
so that i can flash a rom that uses stock fetures of note 4 (windows mode etc)
the cm 12 does not utilize these and i need those badly.
so i tried to go back even factory reset wipe all cashes
but some reasn during all those fails my system UI says fail. and my touchscreen is not in sync correctly.
i heard of wiping system cache not sure if i done that but with TWRP i wipe everything but SD
it seems this has been a common issue the word we are looking for is calibration issues
it seems it happens to this person exactly how it is happening to me
there was a solution at the bottom but those buttons do not work for galaxy note 4 spr
does anyone know the codes for doing so ?
source:
http://forum.xda-developers.com/note-4-tmobile/help/touch-screen-issues-root-t2986883
Did you see post 3?
I suspect you need to flash OG5 first. Use KIES or Odin. I would suggest wiping all but ExtSdCard and factory reset or format data partition, then power off; pull battery 30 seconds prior to stock tar or KIES recovery.
There's a guide you can follow as well as the OP in this post/thread. But see the steps on post 3, this thread. Boot into stock right after stock flash to try to recover your touch screen. If your touch screen is OK, then follow the guide below to root stock.
http://forum.xda-developers.com/showthread.php?p=62241991
Sent from my SM-N910P using Tapatalk
NatsarYAhu said:
I am using
Cyanogenmod version
12.1-20150814-nightly-trltespr 5.1.1
kernel 3.10.40-gef59855
baseversion
N910PVPU4COG5
GALAXY NOTE 4 SPRINT
How ever im trying to flash back to stock evrything.
so that i can flash a rom that uses stock fetures of note 4 (windows mode etc)
the cm 12 does not utilize these and i need those badly.
so i tried to go back even factory reset wipe all cashes
but some reasn during all those fails my system UI says fail. and my touchscreen is not in sync correctly.
i heard of wiping system cache not sure if i done that but with TWRP i wipe everything but SD
Click to expand...
Click to collapse
I recommend you flash this rom. Mostly stock but very stable,and the developer is working on some goodies.
http://forum.xda-developers.com/showthread.php?p=62336588
I recommend that you back up everything you want to keep because you need to wipe everything EXCEPT external SD card. Wipe cache, dalvik , system, and data three times. Then factory reset three times and then flash this rom.
Note4 Rocking a Hybrid Rom
samep said:
Did you see post 3?
I suspect you need to flash OG5 first. Use KIES or Odin. I would suggest wiping all but ExtSdCard and factory reset or format data partition, then power off; pull battery 30 seconds prior to stock tar or KIES recovery.
There's a guide you can follow as well as the OP in this post/thread. But see the steps on post 3, this thread. Boot into stock right after stock flash to try to recover your touch screen. If your touch screen is OK, then follow the guide below to root stock.
http://forum.xda-developers.com/showthread.php?p=62241991
Sent from my SM-N910P using Tapatalk
Click to expand...
Click to collapse
Ok so this stock actually went through will get with you shortly to let you know if sync is fixed,
edit: still not synced correctly but phone does finally work how i want just the main problem is bugged trying the link with *#2663# now
Edit: IT WORKED !!! big UPS BRO thank you !!!
i have same problem after install twrp and flash custom firmware phone working fine but touch won't work
i tried that *#2663# but not working on custom rom any solution to solve touch problem on custom firmware
thanks
imeicodes said:
i have same problem after install twrp and flash custom firmware phone working fine but touch won't work
i tried that *#2663# but not working on custom rom any solution to solve touch problem on custom firmware
thanks
Click to expand...
Click to collapse
Odin stock tar and try again.
There's also an update to CFAR (Chainfire auto root) for Note 4. After you fix your touchscreen, root with it and make a TWRP backup once that is installed. A TWRP restore plus full un-root in SuperSU may make OTA possible; CFAR backs up stock recovery.
You can use Flashify to install custom recovery. You may have installed the wrong recovery to have the touch screen out of cal like it is.
Sent from my SM-N910P using Tapatalk
Sorry to beat a dead horse, I come from the nexus forums and haven't used a samsung device in a while. My friend has the Note 4 with MM on it. Is flashing TWRP as simple as just flashing it via odin with his phone as is? Does he need to complete any process first, before being able to flash TWRP via odin?
Thanks all!
Sprint Note 4 already updated to PD1? If latest update is desired, update it first.
FYI: An ounce of prevention is worth a pound of cure!
The bootloader is already unlocked but the reactivation lock may have been locked by user. Goto to Settings/Security/Reactivation lock and disable it. You can also verify this while in download mode, the phone's display show reactivation lock disabled before your proceed.
Enable developer options by tapping build number in About device in Settings 7 times. Go into developer tab and enable USB debugging.
Using latest Odin and latest TWRP is recommended. You should only flash only the specified custom recovery for your device or the touch screen will not be accurate.
TWRP can be found in the original development thread.
https://dl.twrp.me/trltespr/twrp-3.0.2-0-trltespr.img.tar
Use AP slot and make sure the Samsung driver is installed; get that from Samsung support for Note 4. Make sure KIES and SmartSwitch is closed or uninstalled (may not work on rooted phone; manually backup files you wish to keep just in case). Run Odin as administrator; not required for Windows 10.
To flash, press the Odin exe, uncheck the auto reboot option, load the file using the AP slot, power down phone, hold the keys [volume down, menu and power] together until booted in download initial screen, connect the USB, volume up, verify your COM is connected and start. When you see the success, 0 failed, disconnect USB and pull battery, wait at least 30 seconds and replace battery and boot directly into recovery to ensure it sticks. Otherwise, you're back on stock recovery.
If swapping device owner, it's recommended to remove the Google account before factory resetting the device. Consider it as a good practice for all Settings menu selected factory resets. If you trip the factory reset protection circuit, you need to sign in with original Google account & password.
You can use Odin to downgrade to Android Lollipop 5.1 (most recent OK1 build recommended if going back to Lollipop) but you cannot use Odin to downgrade to Android 5.0 Lollipop or KitKat. The bootloader prevents lower security bootloaders from being installed.
Custom ROMs may remove ItsOn but may not remove it from root folder. Unless /carrier/ItsOn folder is deleted, you may suffer continual reboots if factory resetting device at some point. After following and verifying all the above, you may consider factory resetting, including wiping data, internal memory and Android folder in extSdCard to make a clean break with normal un-rooted conditions and Lollipop fragments on phone to prevent random reboots.
Sent from my SM-N910P using Tapatalk
samep said:
Sprint Note 4 already updated to PD1? If latest update is desired, update it first.
FYI: An ounce of prevention is worth a pound of cure!
The bootloader is already unlocked but the reactivation lock may have been locked by user. Goto to Settings/Security/Reactivation lock and disable it. You can also verify this while in download mode, the phone's display show reactivation lock disabled before your proceed.
Enable developer options by tapping build number in About device in Settings 7 times. Go into developer tab and enable USB debugging.
Using latest Odin and latest TWRP is recommended. You should only flash only the specified custom recovery for your device or the touch screen will not be accurate.
TWRP can be found in the original development thread.
https://dl.twrp.me/trltespr/twrp-3.0.2-0-trltespr.img.tar
Use AP slot and make sure the Samsung driver is installed; get that from Samsung support for Note 4. Make sure KIES and SmartSwitch is closed or uninstalled (may not work on rooted phone; manually backup files you wish to keep just in case). Run Odin as administrator; not required for Windows 10.
To flash, press the Odin exe, uncheck the auto reboot option, load the file using the AP slot, power down phone, hold the keys [volume down, menu and power] together until booted in download initial screen, connect the USB, volume up, verify your COM is connected and start. When you see the success, 0 failed, disconnect USB and pull battery, wait at least 30 seconds and replace battery and boot directly into recovery to ensure it sticks. Otherwise, you're back on stock recovery.
If swapping device owner, it's recommended to remove the Google account before factory resetting the device. Consider it as a good practice for all Settings menu selected factory resets. If you trip the factory reset protection circuit, you need to sign in with original Google account & password.
You can use Odin to downgrade to Android Lollipop 5.1 (most recent OK1 build recommended if going back to Lollipop) but you cannot use Odin to downgrade to Android 5.0 Lollipop or KitKat. The bootloader prevents lower security bootloaders from being installed.
Custom ROMs may remove ItsOn but may not remove it from root folder. Unless /carrier/ItsOn folder is deleted, you may suffer continual reboots if factory resetting device at some point. After following and verifying all the above, you may consider factory resetting, including wiping data, internal memory and Android folder in extSdCard to make a clean break with normal un-rooted conditions and Lollipop fragments on phone to prevent random reboots.
Sent from my SM-N910P using Tapatalk
Click to expand...
Click to collapse
Thanks bud. This was really great!
hate to be a stickler, but im a frickin nub.... after doing this how do i get root access?? pls help im new i just paid 10$ FOR A NOTE 4 , mint condition hahah but for real someone help..
CorporalCactus said:
hate to be a stickler, but im a frickin nub.... after doing this how do i get root access?? pls help im new i just paid 10$ FOR A NOTE 4 , mint condition hahah but for real someone help..
Click to expand...
Click to collapse
To get root after getting on desired update, whether it be current update, downgrading (be careful with downgrading; most likely you're only able to downgrade as low as Android 5.1 but that depends on your current bootloader) or upgrading, you flash TWRP and then you would do one of two things:
1) flash a pre-rooted ROM. Custom ROMs in our forum do this.
2) flash custom kernel and complete root with SuperSU zip. Both are flashed in recovery but both should be flashed before booting. Kernel first, then flash SuperSU zip and boot. You would also need to manually remove ItsOn and Knox.
Given the complexity of it, I'd suggest the custom stock ROM for you. The ROM should match your bootloader. I'd recommend stock, aka touchwiz ROMs. They're mostly stock and have less bugs and workarounds than others like CM.
We still don't have highly customized Marshmallow stockish ROMs but I don't think it will be long before we see them. By the time they're here, maybe you're ready.
Read the OP of the custom ROM. If you don't understand or need clarification, this thread is a good place to ask the question. Install this app to check your bootloader (baseband is relevant too):
https://play.google.com/store/apps/details?id=org.vndnguyen.phoneinfo
Hint: make sure you're on the the recommended bootloader and baseband first. If you have trouble with TWRP flash sticking, you may not be unchecking auto reboot and pulling battery after successful flash and booting directly into recovery to make it stick properly. You have to wait at least 30 seconds after battery pull and boot directly into recovery.
Sent from my SM-N910P using Tapatalk
samep said:
To get root after getting on desired update, whether it be current update, downgrading (be careful with downgrading; most likely you're only able to downgrade as low as Android 5.1 but that depends on your current bootloader) or upgrading, you flash TWRP and then you would do one of two things:
1) flash a pre-rooted ROM. Custom ROMs in our forum do this.
2) flash custom kernel and complete root with SuperSU zip. Both are flashed in recovery but both should be flashed before booting. Kernel first, then flash SuperSU zip and boot. You would also need to manually remove ItsOn and Knox.
Given the complexity of it, I'd suggest the custom stock ROM for you. The ROM should match your bootloader. I'd recommend stock, aka touchwiz ROMs. They're mostly stock and have less bugs and workarounds than others like CM.
We still don't have highly customized Marshmallow stockish ROMs but I don't think it will be long before we see them. By the time they're here, maybe you're ready.
Read the OP of the custom ROM. If you don't understand or need clarification, this thread is a good place to ask the question. Install this app to check your bootloader (baseband is relevant too):
https://play.google.com/store/apps/details?id=org.vndnguyen.phoneinfo
Hint: make sure you're on the the recommended bootloader and baseband first. If you have trouble with TWRP flash sticking, you may not be unchecking auto reboot and pulling battery after successful flash and booting directly into recovery to make it stick properly. You have to wait at least 30 seconds after battery pull and boot directly into recovery.
Sent from my SM-N910P using Tapatalk
Click to expand...
Click to collapse
damn thanks for this info! youre the man! you know ur stuff thats awesome. im confused regarding the kernel.. i just winged it tbh, i installed TWRP via odin. got it to stick, then flashed SUPERSU and got root. I made a full backup via twrp then i flashed a custom CM rom and it works awesome. i didnt do anything regarding kernels. My question now is, what is the easiest way to swap between roms?? Such as stock Rom to this New CM rom i have. Would i just create backups and restore when i want to switch??
CorporalCactus said:
damn thanks for this info! youre the man! you know ur stuff thats awesome. im confused regarding the kernel.. i just winged it tbh, i installed TWRP via odin. got it to stick, then flashed SUPERSU and got root. I made a full backup via twrp then i flashed a custom CM rom and it works awesome. i didnt do anything regarding kernels. My question now is, what is the easiest way to swap between roms?? Such as stock Rom to this New CM rom i have. Would i just create backups and restore when i want to switch??
Click to expand...
Click to collapse
You could make backups and factory reset before restoring. If you have issues restoring stock backups, wipe internal memory also.
You have to take care to read and adhere to changing trends with CM; they may not be compatible with Marshmallow baseband and bootloader yet but may even require a different kernel to run with Marshmallow bootloader and baseband. I'm not current on the latest and lack experience. Search the specific ROM threads for CM known issues, workarounds and trends.
As far as the kernel question, I did omit the fact you could flash SuperSU to patch the stock kernel; you didn't do any wrong there. I've abandoned use of stock kernel since Android 5.1 required an exploit to root. We didn't always have the boot image patch that SuperSU now includes. For some reason, users are randomly losing root with systemless root. If that happens, just flash SuperSU again; same version or higher should be OK.
Sent from my SM-N910P using Tapatalk
samep said:
You could make backups and factory reset before restoring. If you have issues restoring stock backups, wipe internal memory also.
You have to take care to read and adhere to changing trends with CM; they may not be compatible with Marshmallow baseband and bootloader yet but may even require a different kernel to run with Marshmallow bootloader and baseband. I'm not current on the latest and lack experience. Search the specific ROM threads for CM known issues, workarounds and trends.
As far as the kernel question, I did omit the fact you could flash SuperSU to patch the stock kernel; you didn't do any wrong there. I've abandoned use of stock kernel since Android 5.1 required an exploit to root. We didn't always have the boot image patch that SuperSU now includes. For some reason, users are randomly losing root with systemless root. If that happens, just flash SuperSU again; same version or higher should be OK.
Sent from my SM-N910P using Tapatalk
Click to expand...
Click to collapse
ugh i messed something up and cant find the restore files for the note 4. after flashing that CM rom, a lot of stuff didnt work so i restored a backup i just made. it bootlooped, i did it again and the phone came on, BUT i cannot place or delete and media from the device using a PC.. not sure why its say the device has either stopped responding or has been disconnected
CorporalCactus said:
ugh i messed something up and cant find the restore files for the note 4. after flashing that CM rom, a lot of stuff didnt work so i restored a backup i just made. it bootlooped, i did it again and the phone came on, BUT i cannot place or delete and media from the device using a PC.. not sure why its say the device has either stopped responding or has been disconnected
Click to expand...
Click to collapse
Did you factory reset and wipe internal memory when restoring the backup?
Put your micro sdcard in a card reader and transfer it. If you're trying to transfer while in recovery, that currently doesn't work.
If you're trying to copy your TWRP backup to micro sdcard, the path should be: TWRP/BACKUPS/(your device s/n recognized by TWRP)/(TWRP Backup folder)
Without proper path, TWRP may not see the backup as official. When saving TWRP backups, the TWRP folder as a whole with desired backups should be saved.
If you can't restore the backup, you can flash a ROM that matches bootloader. Like I said before, factory reset and wipe internal memory and flash the ROM.
Sent from my SM-N910P using Tapatalk
CorporalCactus said:
ugh i messed something up and cant find the restore files for the note 4. after flashing that CM rom, a lot of stuff didnt work so i restored a backup i just made. it bootlooped, i did it again and the phone came on, BUT i cannot place or delete and media from the device using a PC.. not sure why its say the device has either stopped responding or has been disconnected
Click to expand...
Click to collapse
At this point I would just recommend flashing a new ROM man.
Sent from my SM-N910P using Tapatalk