Develop Bugs

Error 7 on I747 AT&T CM10.0 to CM10.1 RC4

Ok so I was ultimatum 1.4 since the second day I got my phone back late last year. However recently I want to change up my rom so I thought of looking into CyanogenMod which has 10.0 stable version on there site with Jelly Bean 4.1.2. I went ahead and download the rom and flashed it on to my phone after having wiped my phone clean. Everything went as clockwork and I booted up into the new rom. I after restarting my phone I got a message that there was a update. I investigated further and it was just released 2 or 3 days ago. I would really like to have the new RC4 version since it has a lot of bugs worked out. However every time I try to flash my phone I get an error 7 and I fails. I have tried wipping everything and start from scratch and it doesn't work. Any suggestions would be greatly appreciated.

Have you tried searching??
The problem you have has literary hundreds of threads created.
I usually help out but seeing how this certain topic pops up every other day I strongly recommend using the search feature here in XDA or at least try Google.
Trust me its been answered tons of times. Take the time to search and read before posting.
Sent from my SAMSUNG-SGH-I747 using Tapatalk 2

re: problem solver
metadox said:
Ok so I was ultimatum 1.4 since the second day I got my phone back late last year. However recently I want to change up my rom so I thought of looking into CyanogenMod which has 10.0 stable version on there site with Jelly Bean 4.1.2. I went ahead and download the rom and flashed it on to my phone after having wiped my phone clean. Everything went as clockwork and I booted up into the new rom. I after restarting my phone I got a message that there was a update. I investigated further and it was just released 2 or 3 days ago. I would really like to have the new RC4 version since it has a lot of bugs worked out. However every time I try to flash my phone I get an error 7 and I fails. I have tried wipping everything and start from scratch and it doesn't work. Any suggestions would be greatly appreciated.
Click to expand...
Click to collapse
This guide will get your phone back up and running properly, this is a easy and sure way fix your error 7 problem.
In the future unless you like to do a lot of experimentation only flash Touchwiz Jellybean based Tmobile custom roms.
Any other kinds of roms are basically intended for developers and those people who like to experiment with their phones.
- Follow this step by step guide for best results:
Download the newest pre-rooted Samsung Galaxy S3 T999 Jellybean v4.1.2 rom: T999_UVDMD5
After downloading make a folder on your computer's desktop and unzip the file
using Winzip or 7zip so the .TAR file is in the new folder you just made.
Download and extract Odin into the same folder you made containing the TAR file.
Here is the link for Odin: http://d-h.st/Q14
• Download ODIN which is required for flashing the stock rooted firmware (a windows app)
• Download the Odin Flash firmware for T999 Tmobile then copy it to the same folder as Odin
• Run Odin by double clicking the Odin.exe within the same folder as the TAR file you extracted
• Turn off your phone and boot into DOWNLOAD MODE (Volume Down + Home + Power Hold until phone powers up, then release and press Volume Up to enter Download Mode)
• Once in Download Mode, connect the USB/Charger cable to the phone and plug into the USB port on your computer.
• You should now see a COM** port listed toward the top-left of Odin (under ID:COM)
• Click on the PDA button in the middle-right area of Odin.
• Browse to and select the Firmware you downloaded (TAR file)
• Make sure Auto-Reboot and F. Reset Time are the only options checked and that PDA is the only other thing checked.
• TRIPLE CHECK your settings and that you have selected the correct firmware for your model phone and are using the correct options.
• If you are using a laptop, make absolutely sure you are plugged in, or if on battery, that it is charged enough and will not go into sleep mode during flash.
• Click Start to begin the flash. This will take a while, so be patient!
• Once complete, in the top-left box in Odin, it will say PASS and the phone should have automatically rebooted.
• You may unplug the phone and close Odin if you wish.
• Wait at least 5-10 minutes for the system to boot the first time and then build its cache!
• (It may seem to hang during boot, this is normal and you must be patient!!!)
Good Luck!

metadox said:
Ok so I was ultimatum 1.4 since the second day I got my phone back late last year. However recently I want to change up my rom so I thought of looking into CyanogenMod which has 10.0 stable version on there site with Jelly Bean 4.1.2. I went ahead and download the rom and flashed it on to my phone after having wiped my phone clean. Everything went as clockwork and I booted up into the new rom. I after restarting my phone I got a message that there was a update. I investigated further and it was just released 2 or 3 days ago. I would really like to have the new RC4 version since it has a lot of bugs worked out. However every time I try to flash my phone I get an error 7 and I fails. I have tried wipping everything and start from scratch and it doesn't work. Any suggestions would be greatly appreciated.
Click to expand...
Click to collapse
See below
Sent from my SAMSUNG-SGH-I747 using xda app-developers app

re: link
KorGuy123 said:
http://forum.xda-developers.com/showthread.php?p=22
Post 2
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
Click to expand...
Click to collapse
What ever that link is in your post, it's NOT working, it goes to some xda error page.

Misterjunky said:
What ever that link is in your post, it's NOT working, it goes to some xda error page.
Click to expand...
Click to collapse
I fixed it
http://forum.xda-developers.com/showthread.php?p=38880428
He needs to updates his bootloader.
This is brought up 2-3 times a day now.
The bootloader file would be a considerably smaller file than a stock rooted rom and is intended for the d2att instead of the t999 you suggested.
Not trying to step on toes. Just trying to help.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app

This is what I have tride
jayRokk Thank you for your suggestion. However I wouldn't have posted if I would have found a clear answer. I searched the forums and Google and thats what led me to post here. It seems with differrent bootloader version and ROMs not every case is the same. Maybe I'm wrong, if I am can you please explain?
Misterjunky I have a AT&T i747 version not tmobile so I don't think your suggestion would work.
KorGuy123 I have ClockWork Mod Recovery version 6.0.3.1 and I tried your suggestions with the wipe order but it still doesn't work.
Problem: I can install CyanogenMod 10.0 Stable, Ultimatum 1.4, Ultimatum 2.0 and Stock rom no problem. However If I try
aokp_d2att_nightly_2013-06-03
cm-10.1-20130602-NIGHTLY-d2att
cm-10.1.0-RC4
I get the error 7. Any suggestions?

metadox said:
jayRokk Thank you for your suggestion. However I wouldn't have posted if I would have found a clear answer. I searched the forums and Google and thats what led me to post here. It seems with differrent bootloader version and ROMs not every case is the same. Maybe I'm wrong, if I am can you please explain?
Misterjunky I have a AT&T i747 version not tmobile so I don't think your suggestion would work.
KorGuy123 I have ClockWork Mod Recovery version 6.0.3.1 and I tried your suggestions with the wipe order but it still doesn't work.
Problem: I can install CyanogenMod 10.0 Stable, Ultimatum 1.4, Ultimatum 2.0 and Stock rom no problem. However If I try
aokp_d2att_nightly_2013-06-03
cm-10.1-20130602-NIGHTLY-d2att
cm-10.1.0-RC4
I get the error 7. Any suggestions?
Click to expand...
Click to collapse
As I mentioned earlier your boot loader is out of date. That is separate from your recovery.
The link I put up would have lead you to this thread.
http://forum.xda-developers.com/showthread.php?p=41503727
That has the link for the updated at&t boot loader in it. Flash it in odin and you'll be able to flash the newer versions of CM10 and the newer AOKP if you wanted to.
If you search "status 7" or " bootloader " you'll find a handful of threads about this issue. It's been going on for a couple weeks now.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
---------- Post added at 09:22 AM ---------- Previous post was at 09:19 AM ----------
I'm a pretty patient person, and you are new here so I don't mind helping when ever I can.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app

You Rock!
KorGuy123 said:
As I mentioned earlier your boot loader is out of date. That is separate from your recovery.
The link I put up would have lead you to this thread.
http://forum.xda-developers.com/showthread.php?p=41503727
That has the link for the updated at&t boot loader in it. Flash it in odin and you'll be able to flash the newer versions of CM10 and the newer AOKP if you wanted to.
If you search "status 7" or " bootloader " you'll find a handful of threads about this issue. It's been going on for a couple weeks now.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
---------- Post added at 09:22 AM ---------- Previous post was at 09:19 AM ----------
I'm a pretty patient person, and you are new here so I don't mind helping when ever I can.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
Click to expand...
Click to collapse
Do you rock sorry for the misunderstand. I didnt know the bootloader and the recovery where different things. Flashed the newer bootloader and was able to install CM 10.1 RC 4. Thanks again!

metadox said:
Do you rock sorry for the misunderstand. I didnt know the bootloader and the recovery where different things. Flashed the newer bootloader and was able to install CM 10.1 RC 4. Thanks again!
Click to expand...
Click to collapse
Np. Glad to help. Don't forget the thanks button.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app

KorGuy123 said:
Np. Glad to help. Don't forget the thanks button.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
Click to expand...
Click to collapse
Dude. I also have been reading for Status 7 error for hours... trying to go from CM10.0.0 to Quantum 1.9.
You are the only person I found that remained patient and didn't just shout about updating CWM. I was done in by an old bootloader as well.
Thank you so much. Much appreciated. :good:

[Q] what's the deal with 4.3?

- For android 4.3, there has been a lot of talk on the developer section, and from what I can see, the major bugs/issues have been fixed. Like the ROM not rebooting correctly. For those using 4.3, is this true?
- Also, from what I understand, this was due to the recoveries not being ready for 4.3, however CM released their own bare bone recovery to fix that issue. And then I've read that the TW recovery has also been updated to solve this problem.
-There is a lot of information in the development forums, but I have not seen any post on the steps on what to do in order to upgrade from 4.2 to 4.3.
-Right now I have CWM 5 recovery, because that's been working for me, and I never bothered changing (bad experience with trying to upgrade/change a recovery). Now from what I understand, I should be able to flash the newest touch recovery (via the goo app?), and then wipe and flash any 4.3 ROM. Any detail instructions would be a help, or if someone can create a tutorial post, that would be great.
Thanks in advance.

Here is a post I made yesterday about how I switched from 4.2 to 4.3
I hope it helps. I have been on hellybean 4.3 for two days and everything is running great.
http://forum.xda-developers.com/showpost.php?p=45021060&postcount=632

You could just install ROM Manager and update from there. It's super-easy (you need ROOT, but I presume you have that since you're flashing ROMs anyway). :good:

Sicily1918 said:
You could just install ROM Manager and update from there. It's super-easy (you need ROOT, but I presume you have that since you're flashing ROMs anyway). :good:
Click to expand...
Click to collapse
Many people have had bad experiences with ROM Manager. Especially in the Gingerbread days when its use was more common for this sort of thing.
Just my 2 cents.

monkeybuttons said:
Many people have had bad experiences with ROM Manager. Especially in the Gingerbread days when its use was more common for this sort of thing.
Just my 2 cents.
Click to expand...
Click to collapse
Interesting -- always been good to me, although I only use it to update the recovery; for the ROM itself I use Cyanogen's update util. I also use CWM, not TWRP, so there's that...

bobiscool07 said:
- For android 4.3, there has been a lot of talk on the developer section, and from what I can see, the major bugs/issues have been fixed. Like the ROM not rebooting correctly. For those using 4.3, is this true?
- Also, from what I understand, this was due to the recoveries not being ready for 4.3, however CM released their own bare bone recovery to fix that issue. And then I've read that the TW recovery has also been updated to solve this problem.
-There is a lot of information in the development forums, but I have not seen any post on the steps on what to do in order to upgrade from 4.2 to 4.3.
-Right now I have CWM 5 recovery, because that's been working for me, and I never bothered changing (bad experience with trying to upgrade/change a recovery). Now from what I understand, I should be able to flash the newest touch recovery (via the goo app?), and then wipe and flash any 4.3 ROM. Any detail instructions would be a help, or if someone can create a tutorial post, that would be great.
Thanks in advance.
Click to expand...
Click to collapse
Ur best and safest approach would be to DL Odin and the drivers for ur phone, then go to techerrata.com/browse/twrp2/hercules and DL twrp2.6.0.4, this is the 4.3 compatible version, then put ur device in DL mode and connect to odin, load the tar file in PDA and click start, 30 sec and u have the latest and greatest twrp recovery, now go get hellybean 4.3 or beanstalk4.3 and flash it, watch the beauty take place...
Sent from my SAMSUNG-SGH-T989 using XDA Premium 4 mobile app

I updated my rom today like I usually do from the CMUpdater and it updated from 4.2 to 4.3. I didn't mean or want to do that, but it didn't tell me otherwise. Now I'm having issues left and right......the one time I don't back it up...grrr.
I'm having the most issues with Gapps. I downloaded the new one and installed it and Google Music and Youtube keeps crashing. I guess I'll be doing the full wipe now.

Did u update to 4 3 gapps? It won't do it automatically, even if u updated through goo it just looks at what version is installed and updates that version, 4.3 gapps can be found in any 4.3 thread
Sent from my SAMSUNG-SGH-T989 using XDA Premium 4 mobile app

soupysoup said:
Ur best and safest approach would be to DL Odin and the drivers for ur phone, then go to techerrata.com/browse/twrp2/hercules and DL twrp2.6.0.4, this is the 4.3 compatible version, then put ur device in DL mode and connect to odin, load the tar file in PDA and click start, 30 sec and u have the latest and greatest twrp recovery, now go get hellybean 4.3 or beanstalk4.3 and flash it, watch the beauty take place...
Sent from my SAMSUNG-SGH-T989 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Why do some of those files say hercules, and others sgh-t989? Aren't they the same phone?

[How-To] Update to Official GPE Android 5.0 UDNL3 (12-12-2014)

I am sure you will soon begin seeing some Custom ROM's based on today's GPE 5.0 release. In the meantime here is a method to start enjoying 100% Stock GPE 5.0 now!
Instructions:
1. I recommend that you use the latest TWRP v2.8.4.0.
2. Perform and Advanced Wipe and wipe "Dalvick Cache", "System", "Data", and "Cache."
3. Flash the I9505GUEUDNL3_100%_Stock_Rooted_ROM.zip
4. Last, press "Home" then press "Reboot," reboot into "Download Mode" and flash the M919_NK2_Stock_Modem+Bootloader.tar.md5 in Odin's PDA slot(AP in Odin v.3.09+). Done!
Tip: For blazing fast speed turn off animations from developer options and reboot.
Notes:
1. 5.0 seems to require the 4.4.4 modem/non-hlos otherwise security settings will force close. Therefore as of 12/14 the above process will also update your modem/non-hlos + bootloader to NK2(4.4.4) in order to ensure a consistent user experience.
2. The NK2 modem may not stick on your first attempt when flashing the modem + bootloader file in Odin. Should that happen re-flash the file until it sticks.
Alternative Odin Method:
1. Extract the I9505G_UDNL3_GPE_5.0_for_M919.tar and flash in Odin's PDA slot(AP in Odin v3.09+).
2. Power down and boot into stock recovery and perform a factory data reset. Done!
Notes:
1. This is a pre-rooted "All-in-One" Odin package which will update your System and Kernel to 100% stock GPE 5.0 and your Modem, Non-hlos, Recovery, and Bootloader to NK2.
2. The NK2 modem may not stick on the first attempt causing security settings to force close. If that happens flash the M919_NK2_Stock_Modem+Bootloader.tar.md5 until it sticks.
XDA:DevDB Information
[How-To] Update to Official GPE Android 5.0 UDNL3 (12-12-2014), ROM for the T-Mobile Samsung Galaxy S 4
Contributors
muniz_ri
ROM OS Version: GPE 5.0
Version Information
Status: Stable
Created 2014-12-12
Last Updated 2014-12-29

reserved

reserved

does this have the knox and all that nonsense with the voided warranty stuff?
just wondering.

buntobo said:
does this have the knox and all that nonsense with the voided warranty stuff?
just wondering.
Click to expand...
Click to collapse
Are you referring to data drops without a knox bootloader? I'm assuming that will likely be an issue with this ROM but I'm on a knox BL and have not experienced any issues. As for warranty my warranty was void a long time ago so don't know. Others will have to chime in on that.

buntobo said:
does this have the knox and all that nonsense with the voided warranty stuff?
just wondering.
Click to expand...
Click to collapse
Knox is dependent on which Android version of TouchWiz you're running. It is on 4.3 and 4.4.2. If you are on TouchWiz 4.2.2, you can flash this rom without dealing with any of the Knox warranty crap at all.
EDIT: So far it works, but I get a FC on Settings everytime I access Security. If I remember correctly, it can be fixed if keystore.msm8960.so is deleted in /system/lib/hw

Vigz said:
Knox is dependent on which Android version of TouchWiz you're running. It is on 4.3 and 4.4.2. If you are on TouchWiz 4.2.2, you can flash this rom without dealing with any of the Knox warranty crap at all.
EDIT: So far it works, but I get a FC on Settings everytime I access Security. If I remember correctly, it can be fixed if keystore.msm8960.so is deleted in /system/lib/hw
Click to expand...
Click to collapse
Yes, deleting the keystore file solves that issue. I will upload a new version of the ROM without that file. Thanks for the heads-up!

Baseband?
I9505GUEUCNE3... does this have a baseband/modem update as well?

zavien3 said:
I9505GUEUCNE3... does this have a baseband/modem update as well?
Click to expand...
Click to collapse
No, the ROM only flashes system and kernel. I have not tested the NE3 modem on our device but the NB4 modem and non-hlos work just fine with this ROM.

This is a great Rom. I've been using it for a 2 days now and have 0 problems. why not move it to S4 Android Development?

youngwake said:
This is a great Rom. I've been using it for a 2 days now and have 0 problems. why not move it to S4 Android Development?
Click to expand...
Click to collapse
Thanks, glad to hear it's working well.
And since I kept it completely stock I'm not sure it meets the criteria to be in the development section. Anyway I put it together for my own use and just put it out there in case anyone wanted to try it out. Enjoy

muniz_ri said:
Thanks, glad to hear it's working well.
And since I kept it completely stock I'm not sure it meets the criteria to be in the development section. Anyway I put it together for my own use and just put it out there in case anyone wanted to try it out. Enjoy
Click to expand...
Click to collapse
Works great. I personally think people would enjoy this awesome rom. But hey I totally understand what you mean. I am glad I found it...3 days running..zero issues :good:

Great ROM, no problems, thanks for posting!
Sent from my 919 using XDA Free mobile app

I enjoy this ROM. everything running smoothly, I'm using art, too. No glitches at all. Thanks for posting.
Sent from my GT-I9505G using Tapatalk

Is there a way to add the navigation bar to this ROM?
Sent from my T 919 using XDA Free mobile app

CompConfig said:
Is there a way to add the navigation bar to this ROM?
Sent from my T 919 using XDA Free mobile app
Click to expand...
Click to collapse
You can do it with xposed module "Gravity box"
Sent from my GT-I9505G using XDA Free mobile app

Can Viper be used on this ROM?
Sent from my GT-I9505G using Tapatalk

dawgdoc96 said:
Can Viper be used on this ROM?
Sent from my GT-I9505G using Tapatalk
Click to expand...
Click to collapse
Yes it does work...

muniz_ri said:
Thanks, glad to hear it's working well.
And since I kept it completely stock I'm not sure it meets the criteria to be in the development section. Anyway I put it together for my own use and just put it out there in case anyone wanted to try it out. Enjoy
Click to expand...
Click to collapse
are you going to do a 4.4.4? I've been checking to see if you updated. anyways, just wondering

youngwake said:
are you going to do a 4.4.4? I've been checking to see if you updated. anyways, just wondering
Click to expand...
Click to collapse
Lol, good timing......uploading now.

Confirmed - Any TW ROM after OE1 update using TWRP restore of modem/boot/EFS

Background - I took the OE1 update and faced the same issues with flashing that have been so widely discussed. In my attempts to revert I tried Odin, which failed every time, and restoring my most recent TWRP backups, which failed to boot. I was able to flash AOSP ROMs and assumed I'd be restricted to their use until a fix was found.
About the same time that the Noterized ROM and the latest emotion kernels were found to work, I was playing around with my older TWRP backups, one of which included every possible option including boot, modem, EFS, etc.
The first time I restored the entire back up and it wouldn't boot. Then I tried just restoring the modem and EFS, then flashing the Hybrid-X ROM and the latest emotion kernel figuring at least I'd have a working system. Strange thing was my baseband showed up as OB7 in settings.
I got excited and immediately made a backup in TWRP and tried to Odin the base OB7 ROM. It failed. So still using Odin I rerooted and installed TWRP again. Then restored my backup. Baseband still showed OB7.
So I decided to experiment and wiped my phone thoroughly (factory reset X3, format data X3, advanced everything but extsdcard X3, then flash Uberwipe.zip) and when TWRP had restarted I flashed the Echoerom TW ROM from mid march. No current kernels, no mods of any kind, just the base ROM. I walked away to finish a chore and 20 minutes later I returned to find, to my immense pleasure, that the setup screen was waiting for me.
So I can verify, at least for my phone, that if you have taken the OE1 update, but have a full OB7 backup (you backed up every option there is) in TWRP, it IS possible to restore the modem/radio firmware and flash any OB7 TW ROM you wish through TWRP!!!
Odin will still fail if you try to do more than root or install TWRP, but access to all OB7 ROMs is possible after the OE1 update has been taken.
Moral of the story for me - ALWAYS have at least one backup that contains everything in TWRP.

Thanks for posting this, it gives me hope. I have two Note 4's I purchased used about a week ago (one white, one black)... I needed to get MSL for both so I downgraded through odin to 4.4.4 (worked on white, not on black). After researching a bit more on here I realized the non-working Note 4 probably has the OE1 update - so this would explain why it's in a boot loop & not working....
Unfortunately I did not take a full TWRP backup of either phone at the time...
Steps I have tried to get my non-working Note 4 working again:
-attempted multiple odin restores (no dice of course)
-installed TWRP via odin
-attempted OE1 nandroid restore that was uploaded by you (lol) @ forum.xda-developers.com/showpost.php?p=60983327&postcount=55
-wiping 3x (everything but extSD) & install Noterzied rom via TWRP (I read this should work, but does not for me, black/blank screen on boot)
Why didn't the Noterized rom work for me?
Can I create/restore via TWRP using the working Note4 on the non-working Note4, or is that a bad idea?
Not quite sure exactly where to go from here... thanks!
UPDATE: I downloaded uberwipe, created a fresh 'full' nandroid backup of the white Note 4, then restored it to the black Note4 - now it is working!
.

Not overly familiar with nandroid backups... It would be interesting if one could be developed as a backup for those who took oe1 without making one?
Sent from my SM-N910P using Tapatalk

So if im completely stock OE1, theres no way to install the Hybrid X rom? Sorry, been reading all over the place and still confused about the whole ob7 vs oe1 issue

l330n said:
So if im completely stock OE1, theres no way to install the Hybrid X rom? Sorry, been reading all over the place and still confused about the whole ob7 vs oe1 issue
Click to expand...
Click to collapse
If you rooted while on OB7 and took a full nandroid, you could restore it then flash any OB7 ROM. But Odin would still be broken as far as stock tars are concerned.
Still an unknown if flashing baseband and bootloader from another individual's nandroid from OB7 is enough to accomplish same result. Maybe someone will post here when/if a working solution is found. I didn't confirm it but someone had posted baseband flash was a working solution on another note 4 forum.
If not, flashing Noterized Stable release 1 is the only TW custom ROM I'm aware of ATM. http://forum.xda-developers.com/showthread.php?p=60506574

Nah, it hasnt been rooted before, kinda been holding off but damn phone been kinda goofy lately so i figured it was time to go ahead and get it cleaned up and root while i was at it. Thanks ill go check out that Notarized

samep said:
If you rooted while on OB7 and took a full nandroid, you could restore it then flash any OB7 ROM. But Odin would still be broken as far as stock tars are concerned.
Still an unknown if flashing baseband and bootloader from another individual's nandroid from OB7 is enough to accomplish same result. Maybe someone will post here when/if a working solution is found. I didn't confirm it but someone had posted baseband flash was a working solution on another note 4 forum.
If not, flashing Noterized Stable release 1 is the only TW custom ROM I'm aware of ATM. http://forum.xda-developers.com/showthread.php?p=60506574
Click to expand...
Click to collapse
So, if I flashed Tx's stock, rooted, de-knoxed and de-itson rom, made a nandroid (minus EFS) it could be used to get OE1 folks back to OB7?

jhill110 said:
So, if I flashed Tx's stock, rooted, de-knoxed and de-itson rom, made a nandroid (minus EFS) it could be used to get OE1 folks back to OB7?
Click to expand...
Click to collapse
From what I understand, it may allow them to flash OB7 ROMs but Odin would still be broke as far as stock tars are concerned.
I believe there was a recent request for a nandroid sans the data and EFS partitions.
I don't think stock-ish was the request. Maybe Noterized or Hybrid X with latest Emotion kernel would be more likely to work?

samep said:
From what I understand, it may allow them to flash OB7 ROMs but Odin would still be broke as far as stock tars are concerned.
I believe there was a recent request for a nandroid sans the data and EFS partitions.
I don't think stock-ish was the request. Maybe Noterized or Hybrid X with latest Emotion kernel would be more likely to work?
Click to expand...
Click to collapse
Did it. Re-flashed it a couple of times to make sure it good and it is.
No Data no EFS.

jhill110 said:
Did it. Re-flashed it a couple of times to make sure it good and it is.
No Data no EFS.
Click to expand...
Click to collapse
Great. Any takers?
@Droid2drummer was interested.
http://forum.xda-developers.com/showthread.php?p=61228198
Drop him a PM if he doesn't chime in soon.
Thanks for the effort. Maybe someone will find it useful or worth a try?

samep said:
Great. Any takers?
@Droid2drummer was interested.
http://forum.xda-developers.com/showthread.php?p=61228198
Drop him a PM if he doesn't chime in soon.
Thanks for the effort. Maybe someone will find it useful or worth a try?
Click to expand...
Click to collapse
Ok, I'm just about ready to start a thread with the DL link. I'll come back here with a link to that thread.

Here's The HYBRID-X 2.2 Nandroid For Those On The OE1 OTA Download Thread
Going to shutdown the link temporarily... Be back up ASAP. Have a report of boot issues
Go Here And Follow The Link In The N910P XDA Note 4 General Section.
HERE

Spent yesterday trashing and fixing my phone. I figured out that I didn't revert the baseband through a TWRP restore. (I have an OE1 base backup and I flashed the modem from that half a dozen times and it never changed to OE1 baseband). That means it must have been through one of the Odin flashes I did (that failed, but apparently AFTER writing the modem.bin)
Does anyone have an OE1 modem.bin? I can pull the boot.img from my TWRP backup, but the modem isn't stored in a bin format. I need one so I can test my theory.
Or, if there is a brave soul out there, I made an Odin flashable tar file of the OB7 modem and the r16 emotion kernel. I have flashed it multiple times on my phone with no issues. I know it changes the kernel because I have another file with the OB7 modem and the OB7 stock kernel that I was using as a base.
If anyone is willing to try the OB7modem/emotion kernel file and report back you can download it here.
As you can see from the following pic my bootloader is OE1 my baseband is OB7 and I'm running Hybrid-X 2.2

Actually. If dreamingwolf could post a nand of his current backup minus data and efs we would be golden. I think?
Sent from my SM-N910P using XDA Free mobile app

Droid2drummer said:
Actually. If dreamingwolf could post a nand of his current backup minus data and efs we would be golden. I think?
Sent from my SM-N910P using XDA Free mobile app
Click to expand...
Click to collapse
It's uploading to Google Drive as I write this. As soon as it finishes I will edit in the link.
Fair warning though, I run Nova Launcher at 480dpi. If you are used to the default 640dpi, everything is going to appear tiny. You will need to edit the screen density line of the build.prop to change it.
EDIT: I just pulled the data, cache, and EFS then zipped the folder (so you don't have to create your own this time). The file can be downloaded here.

Lmao. I do too. Usually especially when on aosp
Sent from my SM-N910P using XDA Free mobile app

DreamingWolf said:
It's uploading to Google Drive as I write this. As soon as it finishes I will edit in the link.
Fair warning though, I run Nova Launcher at 480dpi. If you are used to the default 640dpi, everything is going to appear tiny. You will need to edit the screen density line of the build.prop to change it.
EDIT: I just pulled the data, cache, and EFS then zipped the folder (so you don't have to create your own this time). The file can be downloaded here.
Click to expand...
Click to collapse
It wont download
Sent from my SM-N910P using XDA Free mobile app

Droid2drummer said:
It wont download
Sent from my SM-N910P using XDA Free mobile app
Click to expand...
Click to collapse
What browser are you using?
Sent from my SM-N910P using XDA Premium HD app

DreamingWolf said:
What browser are you using?
Sent from my SM-N910P using XDA Premium HD app
Click to expand...
Click to collapse
Chrome. I finally got it. But its not allowing me to change the name. Crdownload at end. Anyway its saying its only 338 mb. It was 1.4 gigs it downloaded. Lol. No worries man.
Sent from my SM-N910P using XDA Free mobile app

Droid2drummer said:
Chrome. I finally got it. But its not allowing me to change the name. Crdownload at end. Anyway its saying its only 338 mb. It was 1.4 gigs it downloaded. Lol. No worries man.
Sent from my SM-N910P using XDA Free mobile app
Click to expand...
Click to collapse
I'll try and get it pushed to Android File Host later today.
And I had a thought as I was waking up this morning. When I first got my baseband reverted to OB7 I had been flashing a lot of failed tars through Odin and I ended up also rerooting and reinstalling TWRP. So I wonder if it would work better if, as a starting point, the modem/kernel got flashed, immediately followed by CF-AutoRoot, followed by TWRP, then go into TWRP to wipe and flash Hybrid-X.

Stuck in reboot loop after CF-Auto-Root

Hi All,
I purchased my Note 4 from Swappa, it already came in with Knox 0x1 (4) but it was restored back to stock everything. I recently upgraded to 5.1.1 (via Official OTA) and Sprint has turned my phone into an Ad Beacon. I get all sorts of stuff get installed from Sprint Zone to Avatars for Voicemail and a ton of apps that I need out of my phone.
I decided to try the CF-Auto-Root method. This worked for me in the past with my Note II. Well, I was not so lucky this time. I booted to Download Mode, ran Odin, and PDA installed the autoroot TAR.
I got the red pirate droid screen, and then the phone rebooted. Since then it's been stuck in a reboot loop over and over.
Is my phone bricked? I realize I made a very dumb mistake by doing this now. Because I need my phone the next 2 days and I might have to call Sprint and have them re-activate one of my dumb phones if I can't figure this out.
Question is, is the phone done for? Or is there a way I can bring it back from the dead? I am currently download what I think is the stock FW for the Note 4 (5.1.1) from Sammobile. Its going at 200kb/s so It won't finish for another 2 hours. Only problem is. I have no idea what to do with this file once I get it.
If someone here can please point me in the right direction. I'd greatly appreciate it.

CF autoroot does not work on 5.1.1....odin stock sprint rom and then flash a custom rom with root baked in the rom...recommend Sprint HybridX ver3 as it has anything you could want in a rom and is very stable...you'll need to install custom recovery such as TWRP to flash the custom rom
Sent from my SM-N910P using Tapatalk

gdempsey1 said:
CF autoroot does not work on 5.1.1....odin stock sprint rom and then flash a custom rom with root baked in the rom...recommend Sprint HybridX ver3 as it has anything you could want in a rom and is very stable...you'll need to install custom recovery such as TWRP to flash the custom rom
Sent from my SM-N910P using Tapatalk
Click to expand...
Click to collapse
Thanks for the response. I'm currently flashing using:
ALL_SPT_N910PVPU4COG5_N910PSPT4COG5_CL5303209_QB5691107_REV00_user_low_ship_MULTI_CERT.tar.md5.zip
It's doing it's thing at the moment.
I tried flashing TWRP earlier, but had no luck. Could you please point me at any resource that can help me get that? Assuming this stock I'm using will work.
EDIT: It finished, rebooted. Now stuck at the Sprint Spark screen for about 5 minutes now.
EDIT2: It's preparing device for first time use. Looks like the stock made it through.
Just need to know how to flash TWRP at this moment and if you can kindly point me to that HybridX ROM I'd be grateful!

Go to XDA developer (install app from playstore) and the go to sprint samsung galaxy note4 forum under android development and find sprint hybrid x rom thread...at the beginning of thread are all the file downloads you'll need and instructions to install....when you're done give @tx (the developer) a thank you...he's an awesome developer and creates the best roms out there for our devices.
Sent from my SM-N910P using Tapatalk

Thanks for the headsup. I managed to get TWRP working and I booted to it.
I'm just confused regarding Deodexed vs Nondeodexed roms. What's the difference? That's my last obstacle in my way.
Again, I appreciate your help.

Odexed is for performance and deodexed is for mods...deodexed alittle slower but highly customizable (themes..5way boot...etc.)...odexed is fast but can't customize.
Sent from my SM-N910P using Tapatalk

gdempsey1 said:
Odexed is for performance and deodexed is for mods...deodexed alittle slower but highly customizable (themes..5way boot...etc.)...odexed is fast but can't customize.
Sent from my SM-N910P using Tapatalk
Click to expand...
Click to collapse
So unfortunately I rebooted from TWRP after testing that it works and I'm back to the boot loop.. I get the Sprint logo and it keeps rebooting....
When I was in TWRP, before I rebooted it asked it I wanted to installed SuperSU and I agreed. Could that have done it?
Does that mean I need to reflash again?

Possibly incompatible...you flashed a stock rom and tried to add SU without root....reflash stock...and then flash the Hybrid X rom if you want root and SU as they are baked into the rom so when you reboot you'll have everything you need...no need to add anything else.
Sent from my SM-N910P using Tapatalk
---------- Post added at 08:38 PM ---------- Previous post was at 08:32 PM ----------
After you install xda read some of the threads....you'll learn alot on the peculiarities of the new 5.1.1 update and OG5 problems and workarounds....much info in these threads...especially Hybrid X threads

gdempsey1 said:
After you install xda read some of the threads....you'll learn alot on the peculiarities of the new 5.1.1 update and OG5 problems and workarounds....much info in these threads...especially Hybrid X threads
Click to expand...
Click to collapse
Looks like I managed to boot into HybridX finally. My only worry at this point is it looks like I lost LTE. I only see 3G connection now.
I'm guess that's what you're referring to with OG5 problems?
EDIT: I can't really tell at this point. Whenever I reboot. I see the LTE logo. I ran the browser real quick managed to load a page fast. But lost the signal and went back to 3G. I'll have to give this a full day of testing before I judge it.
That being said, I got rid of all the Sprint junk and I think the phone runs a bit faster. So thank you for all your help!

You're welcome...and the lte/3g will switch back and forth depending on the available signals inorder to maintain the most stable data connection for your location....not to worry....you probably won't even notice the difference other than the icons
Sent from my SM-N910P using Tapatalk
---------- Post added at 10:21 PM ---------- Previous post was at 10:12 PM ----------
You're gonna love the battery usage...and all the bells and whistles like audio mods that @tx baked into the rom
Sent from my SM-N910P using Tapatalk

I had this same thing happen to me. My phone is stuck in a boot loop. Where do I get the file I need to flash to restore everything back to normal? I'm inexperienced in rooting so any help would be appreciated.

frenchiethefry94 said:
I had this same thing happen to me. My phone is stuck in a boot loop. Where do I get the file I need to flash to restore everything back to normal? I'm inexperienced in rooting so any help would be appreciated.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showpost.php?p=62241991&postcount=56
You'll need Beastmode kernel and SuperSU zip links from that post. There's also notes that will help if you continue to experience boot loops.
Sent from my SM-N910P using Tapatalk

Hey guys I'm in the same boat using 910W8 Telus reboot loop. What do I need to do to unbrick this note 4 fairly new to this and bit off way more than I could chew lol please helppp

Easy Root for SM-G900T1 klte (Any Device) Lollipop 5.0-5.1.1 or CFAutoRoot btloop fix
Will work on any device. So I was having the same issue and had actually just wasted 2 whole days trying to root my S5 with the 5.1.1 and couldnt seem to find a working download link for the 4.4.2 Gingerbread so being the stubborn ass I am when it comes to hacking and finding faster alt. solutions by like editing script or binary persay. So out of irritation and many times flashing back to my previous firmware lol I had a crazy idea. I used the CF Auto Root and sure enough bootloop, but....then I thought well I need the TWRP recovery if I wanna try and maybe manually update or swap the boot.img or security protocol somehow so I flashed TWRP recovery and all I had to do to end the bootloop was install update from ext sdcard<SuperSU v1.65 update which it just so happens I coincidentally copied and pasted onto my sd card (via sd card adapter in laptop or the mass storage mode when hooked to usb) and boom it booted up and started perfect as if I didnt even have Lollipop 5.1.1 lol made my night/morning at 6 am previously frustrated and about to give up. So to sum it up....
1. Download/Install: Odin v3.10.6
2. Download/OdinFlash: CF Auto Root
3. Download/OdinFlash: openrecovery-twrp-2.7.0.0-klte
4. Download: SuperSU-v1.65-update
5. Recovery Reboot
6. Install Update: SuperSU-v1.65-update
slide to flash it, wipe Dalvik cache, reboot normally and wahlah you've now rooted you Galaxy S5 klte on Lollipop 5.1.1 and up (when they update the klte this method should still work guaranteed due to the fact its more of a technical loophole in the firmware than the exploit package itself)