Database Info

*REWARD -Tablet lost Imei and network after attempting root

I'll give as much info as i can and will REWARD whoever can help me with this situation!
I have experience with different samsung phones rooting through odin and others never having much issues. This is first attempt with a tablet fyi.
Samsung tab 2 lte edition from at&t i497 5100
Attempted http://forum.xda-developers.com/showthread.php?t=1957165
root method through odin and everything was going alright until halfway through it said failed. I then rebooted into download and attempted this version http://forum.xda-developers.com/showthread.php?t=2101044
This method seemed to work as i was able to boot into recovery cwm and go through the options. I then ran the supersu zip and verified that the appdrawer had it in there. things looked ok i thought. so now i was ready to download a rom. Attempted the most current CM10 nightly through recovery.- it failed giving me the status 7 error. i then went to the only post about status 7 in the all things tab 2 thread and attempted to download mobile odin but when i loaded the app it said not compatible with my device.
I then attempted to download a stock rom and remove root from phone because sometime in this all i lost the ability to use wifi and my imei showed missing in the settings. no attempt at unrooting seems to work because of the cwm not allowing me to use roms. I attempted to recover the nandroid i made the minute i "rooted" and its giving me the md5 sum error as well.
Please help!!

circa_rider said:
I'll give as much info as i can and will REWARD whoever can help me with this situation!
I have experience with different samsung phones rooting through odin and others never having much issues. This is first attempt with a tablet fyi.
Samsung tab 2 lte edition from at&t 5100
Attempted http://forum.xda-developers.com/showthread.php?t=1957165
root method through odin and everything was going alright until halfway through it said failed. I then rebooted into download and attempted this version http://forum.xda-developers.com/showthread.php?t=2101044
This method seemed to work as i was able to boot into recovery cwm and go through the options. I then ran the supersu zip and verified that the appdrawer had it in there. things looked ok i thought. so now i was ready to download a rom. Attempted the most current CM10 nightly through recovery.- it failed giving me the status 7 error. i then went to the only post about status 7 in the all things tab 2 thread and attempted to download mobile odin but when i loaded the app it said not compatible with my device.
I then attempted to download a stock rom and remove root from phone because sometime in this all i lost the ability to use wifi and my imei showed missing in the settings. no attempt at unrooting seems to work because of the cwm not allowing me to use roms. I attempted to recover the nandroid i made the minute i "rooted" and its giving me the md5 sum error as well.
Please help!!
Click to expand...
Click to collapse
I'm worried for you, in that you have corrupted your efs folder - did you make an efs backup? as far as i'm aware, you can only recover your efs if you have backed it up. good luck.

If it helps I am an At&t store manager, and i do have access to a identical tab that is about to be sent back from a return. I am scared though of corrupting that one and then being in a worse situation. If i knew i could create a backup that could be moved to my personal one i would do it. is that possible? I'm not familiar with an efs backup but am researching it to check now.
squ89r97 said:
I'm worried for you, in that you have corrupted your efs folder - did you make an efs backup? as far as i'm aware, you can only recover your efs if you have backed it up. good luck.
Click to expand...
Click to collapse

circa_rider said:
If it helps I am an At&t store manager, and i do have access to a identical tab that is about to be sent back from a return. I am scared though of corrupting that one and then being in a worse situation. If i knew i could create a backup that could be moved to my personal one i would do it. is that possible? I'm not familiar with an efs backup but am researching it to check now.
Click to expand...
Click to collapse
I'm not sure it would, as a store manager you will know imei numbers are specific to each device!...you could swap the tabs over, but I don't condone that

Did you by chance rename the backup after making it? That has caused me problems in the past.
Sent from my SPH-L900 using Tapatalk 2

circa_rider said:
Samsung tab 2 lte edition from at&t 5100
Click to expand...
Click to collapse
Sorry I can't help, but is this the 7" tab? I have the 10.1" tab 2 and my model number is i497... LTE edition.

I totally understand what you mean now, i wasn't thinking a backup would switch over the imei i just thought it would contain whatever identifiers needed not realizing it would have the actual number in that.. I used total commander to look into the root file and there is a efs folder with all the separate folders "bluetooth, wifi, and other folders".

patrao_n said:
Did you by chance rename the backup after making it? That has caused me problems in the past.
Sent from my SPH-L900 using Tapatalk 2
Click to expand...
Click to collapse
I did rename it when i was going through a fix for the md5 sum issue, i was going through adb and couldn't navigate to the folder so i did rename it... i cant imagine that the recovery would have an issue just because of that? i wouldn't be sure what to name it back to.
I wonder if Samsung has any option for me to send it in and get them to reboot the thing. This sucks!

circa_rider said:
I totally understand what you mean now, i wasn't thinking a backup would switch over the imei i just thought it would contain whatever identifiers needed not realizing it would have the actual number in that.. I used total commander to look into the root file and there is a efs folder with all the separate folders "bluetooth, wifi, and other folders".
Click to expand...
Click to collapse
There will be, but unforunately they are corrupt now. :crying:
I wonder if Samsung has any option for me to send it in and get them to reboot the thing. This sucks!
i'm pretty sure samsung has an option for you to send it in, but depending on what firmware your running/whether the flash counter has increased in download mode - your warranty would be void - or you may have to pay some $$$$ - they may even refuse. i don't know for sure though.

squ89r97 said:
There will be, but unforunately they are corrupt now. :crying:
I wonder if Samsung has any option for me to send it in and get them to reboot the thing. This sucks!
i'm pretty sure samsung has an option for you to send it in, but depending on what firmware your running/whether the flash counter has increased in download mode - your warranty would be void - or you may have to pay some $$$$ - they may even refuse. i don't know for sure though.
Click to expand...
Click to collapse
I appreciate you talking me through the different things, even if it doesn't fix my issue. I am probably going to call samsung to see but my flash counter is reset from triangle away and the firmware looks like it did before i ever rooted. but it says modified when i go to download mode so im sure they would know in a second that its my fault

circa_rider said:
I appreciate you talking me through the different things, even if it doesn't fix my issue. I am probably going to call samsung to see but my flash counter is reset from triangle away and the firmware looks like it did before i ever rooted. but it says modified when i go to download mode so im sure they would know in a second that its my fault
Click to expand...
Click to collapse
if the counter is at 0 it sounds like you still have root access, do you?
you could try flashing a stock firmware through odin , which ever came with the tab - 4.0.4??? get the firmware from sammobile.com - that may :fingers-crossed: get rid of the modified status.
---------- Post added at 05:20 PM ---------- Previous post was at 04:40 PM ----------
never thought to ask either - whats the *REWARD?

Try flash this jamaican firmware it works on at&t
http://www.hotfile.com/dl/189517896/ee3001a/I497UMAMA1_I497JDIAMA1_JDI.zip.html

mihaidenis said:
Try flash this jamaican firmware it works on at&t
http://www.hotfile.com/dl/189517896/ee3001a/I497UMAMA1_I497JDIAMA1_JDI.zip.html
Click to expand...
Click to collapse
You're missing the point! He has a corrupt imei number. He can flash that but still won't be able to get signal.

I had a simaler issue with my S3 (d2tmo) as well as many others. Qpst I believe is what I used to get the imei back. I had the links all save on the laptop but it died 3 moths back. (10 year old dell). http://forum.xda-developers.com/showthread.php?t=1801997 try that out see if it will help. I have some of the other stuff saved that I will upload to you. Search the issue on S3 (us variants) it could help.

Samsung Rocks!
Great news! Samsung had me send it in and they repaired it in less than 2 days of having it. their ticket email says this
Problem found: ESN corrupted
Solution: Replaced PBA
-- not sure what a pba is but they didn't charge me for the repair! I'm taking this as a gracious sign from above that i should leave it well enough alone and enjoy it the way it was made! I'll just stick to rooting my s3 and doing what im comfortable with. I appreciate all your words of help and advice to try and narrow down a solution.

First of all, you flashed some things not meant for your device. the CF-Autoroot method is designed for the Pxxx models, NOT the SGH/SCH models. Flashing this on your device flashed partitions it shouldn't have.
Second, the PBA is the mainboard. I bricked my tab a few weeks ago (typo in my updater script) and they replaced the PBA also. Samsung warranty is pretty great. Glad you got it fixed.
Always, ALWAYS, be sure you flash a ROM/recovery/etc designed for your specific device. The pxxx tabs and sgh/sch tabs are 100% different in hardware AND partition layout. If you flash a ROM for the Pxxx tab on a SGH/SCH tab, it will overwrite imei. Moderators REALLY need to suck it up and create separate forums for the lte tabs.

MrHyde03 said:
If you flash a ROM for the Pxxx tab on a SGH/SCH tab, it will overwrite imei. Moderators REALLY need to suck it up and create separate forums for the lte tabs.
Click to expand...
Click to collapse
Don't think this will happen, too small community and even no CM.
I think the verizon Tab is the Xperia Pro in the Xperia Arc Forum

Dexxmor said:
Don't think this will happen, too small community and even no CM.
I think the verizon Tab is the Xperia Pro in the Xperia Arc Forum
Click to expand...
Click to collapse
I know... very unlikely which is why I'm currently setting up my own forums to alleviate the issue :good:

get my tab 2 imei back to normal
Dexxmor said:
Don't think this will happen, too small community and even no CM.
I think the verizon Tab is the Xperia Pro in the Xperia Arc Forum
Click to expand...
Click to collapse
How I can get my tab 2 10.1 original imei back ? I lost my orignal imei and network not registered after my tab is root...please tell me how I can get it back, hope to have a solutions soon...

New root method

Anyone read about the new root method for all G4s?
I can't link it for some reason but it is in the non carrier G4 section

Yup. Already rooted and debloated.
Sent from my LG-H810 using XDA Free mobile app

Link, pics, and/or video or it didn't happen.

Or you could not be lazy and go look in the main forums for it.
Sent from my LG-H810 using XDA Free mobile app

See this:
[ROOT] TMO/VZW/ATT/SPRINT/INTL Root your LG G4 with Low Effort Root!

Yeah, works like a charm.

Has anyone tried this on a H810 10B VERSION?

How did you do the debloat? I tried manually going through and nuking various things with Titanium Backup and have managed to get into a spot where I randomly get errors like existing apps are missing dependencies. I should have stopped at nuking all ATT stuff and having most of the LG stuff not being loaded but not removing them completely. .
Anyone know where I can find all the LG Apps or a way to pull them back down without going back to a stock image then rerooting?
soulysephiroth said:
Yup. Already rooted and debloated.
Sent from my LG-H810 using XDA Free mobile app
Click to expand...
Click to collapse

soulysephiroth said:
Yup. Already rooted and debloated.
Sent from my LG-H810 using XDA Free mobile app
Click to expand...
Click to collapse
I see that you had success with your root on the AT&T variant. I'm using to rooting Samsung phones, so this is definitely different.
Did you encounter any weirdness by just following the original post instructions? Any tips you can pass along before I take the plunge?
Thanks!

I found it very easy but I'm also familiar with low level tools.
If you follow the guide exactly, it should be easy. Just be careful with what you "clean" afterward or you'll end up like me with some weird issues.
JacenSolo2001 said:
I see that you had success with your root on the AT&T variant. I'm using to rooting Samsung phones, so this is definitely different.
Did you encounter any weirdness by just following the original post instructions? Any tips you can pass along before I take the plunge?
Thanks!
Click to expand...
Click to collapse

darkriff said:
Has anyone tried this on a H810 10B VERSION?
Click to expand...
Click to collapse
Don't do it, it'll brick the phone. They only have a rooted image up for the H81010g.
Follow their directions for making a system image file of your phone.
There are directions somewhere on how to root your image file so look around if you feel comfortable with that.
You can also upload your 10b image to Mega or Androidfilehosts for others to use.
---------- Post added at 07:54 PM ---------- Previous post was at 07:50 PM ----------
sorozco said:
How did you do the debloat? I tried manually going through and nuking various things with Titanium Backup and have managed to get into a spot where I randomly get errors like existing apps are missing dependencies. I should have stopped at nuking all ATT stuff and having most of the LG stuff not being loaded but not removing them completely. .
Anyone know where I can find all the LG Apps or a way to pull them back down without going back to a stock image then rerooting?
Click to expand...
Click to collapse
Block or freeze first! There may be some files you need uploaded on Androidfilehosts.com.
If you post a list of files you need in a new thread here, someone will help you. My phone is bricked, so I can't help today.

What do you freeze to stop the automatic over the air updates?

I removed most of what on the list in the "debloater" link to stop updates. Only drawback is I think I destoryed my MMS because I removed some thing I shouldn't have.

soulysephiroth said:
I removed most of what on the list in the "debloater" link to stop updates. Only drawback is I think I destoryed my MMS because I removed some thing I shouldn't have.
Click to expand...
Click to collapse
Check my Debloat thread, I think someone mentioned which file nuked MMS for them, but on another carrier. You can also try another MMS app. I don't like the stock one.

I also got carried away and deleted some necessary apps. I did a factory reset and went through the root process again and it restored the deleted apps and now all is well.

I didn't freeze the apps, I removed them completely. I need to return to stock to resolve it more than likely hah

Did you do the basic factory reset on the phone? If that's all you did, I might do the same .
ry7669 said:
I also got carried away and deleted some necessary apps. I did a factory reset and went through the root process again and it restored the deleted apps and now all is well.
Click to expand...
Click to collapse

I couldn't get past the startup screen once I reset because of the blocks. LGstartup keeps crashing making it so I can't get past it. Stock it is. And now the damn stock restore keeps failing too.

Does anyone know what could be stopping photo lock from working? I'm hoping that's what it is anyeay

knoshann said:
Does anyone know what could be stopping photo lock from working? I'm hoping that's what it is anyeay
Click to expand...
Click to collapse
Just an fyi it's called "content lock" just found it
Sent from my LG-H810 using XDA Free mobile app

Android Pay

Just wondering if anyone had any luck with the workarounds for our device? If so please post what ROM's work and which workaround worked. Also post whether the boot loader needed to be locked or not. I have been working since I found the official app last night, but So far no luck. I'm trying many custom ROMS as I don't really want another stock ROM, Hence why I am rooted. Anyway, any help would be boss! Thanks!

For me, it just has Google Play Services crashing whenever I try to add a card. This was after disabling SuperSU.

walkwithdeath said:
Just wondering if anyone had any luck with the workarounds for our device? If so please post what ROM's work and which workaround worked. Also post whether the boot loader needed to be locked or not. I have been working since I found the official app last night, but So far no luck. I'm trying many custom ROMS as I don't really want another stock ROM, Hence why I am rooted. Anyway, any help would be boss! Thanks!
Click to expand...
Click to collapse
did you try stock rooted thats my next attempt after I charge phone up a little. I been reading up and it seems stock rooted with supersu removing stock or xposed rootcloak work. Just nandroid and try it out nobody says you have to use it but if that works it may give us an insight on what to target for getting it to work

Yes, so far I believe thats what I read. At this point I have read a lot. The two methods involve unchecking enable superuser in supersu and then the root cloak method via xposed. Neither have worked in every custom ROM so far. I may try CM nightlies tho.

just an fyi i tried stock for the hell of it and it worked with just unchecking supersu root option. Maybe a buildprop edit to trick it to think its a basic stock rom may work

http://forum.xda-developers.com/oneplus-one/development/rom-cyanogen-os-12-1-rooted-cleaned-t3187016
Update. I have found a mothod that works, haven't tried the "pay" part, but I have Android Pay activated and working. The above link is the a rooted ROM with some mods that works. Its CM OS 12.1 and seems pretty stable, etc.
The method I used
1 Bootloader is locked. Just so you know. But all operations will function that you need.
1 Install ROM (use the link above for details, NO GAPPS NEEDED)
2 DENY ROOT/SUPERSU installation.
3 Boot ROM as normal
4 Open SuperSU
5 Click Enable SuperSU (This disables it/Unchecks the box. You will see a prompt saying uninstalling SuperSU)
6 Reboot
7 Install Google Play Services then Android Pay (APK's found on the web, GPS is 8.1.13)
8 Open Android Pay and follow prompts to install cards
9 Open SuperSU and recheck Enable SuperSU
At this point the phone is rooted and Android Pay is set up. I tried to do another card but got the same old error "cannot verify Android bs."
My conclusions:
If the ROM has a root option under developer settings, then Android Pay will not work. This ROM does NOT have that but instead has SuperSU installed. ROMS that have both will NOT function, I tried 3 or 4 today that did not work. I imagine they need to be CM based at this time as well. I bet someone better than me will come up with a better solution. This combination works for me. If anyone needs help, PM me. Also, If anyone has anything to add, Please do! Thanks!!!

walkwithdeath said:
http://forum.xda-developers.com/oneplus-one/development/rom-cyanogen-os-12-1-rooted-cleaned-t3187016
Update. I have found a mothod that works, haven't tried the "pay" part, but I have Android Pay activated and working. The above link is the a rooted ROM with some mods that works. Its CM OS 12.1 and seems pretty stable, etc.
The method I used
1 Bootloader is locked. Just so you know. But all operations will function that you need.
1 Install ROM (use the link above for details, NO GAPPS NEEDED)
2 DENY ROOT/SUPERSU installation.
3 Boot ROM as normal
4 Open SuperSU
5 Click Enable SuperSU (This disables it/Unchecks the box. You will see a prompt saying uninstalling SuperSU)
6 Reboot
7 Install Google Play Services then Android Pay (APK's found on the web, GPS is 8.1.13)
8 Open Android Pay and follow prompts to install cards
9 Open SuperSU and recheck Enable SuperSU
At this point the phone is rooted and Android Pay is set up. I tried to do another card but got the same old error "cannot verify Android bs."
My conclusions:
If the ROM has a root option under developer settings, then Android Pay will not work. This ROM does NOT have that but instead has SuperSU installed. ROMS that have both will NOT function, I tried 3 or 4 today that did not work. I imagine they need to be CM based at this time as well. I bet someone better than me will come up with a better solution. This combination works for me. If anyone needs help, PM me. Also, If anyone has anything to add, Please do! Thanks!!!
Click to expand...
Click to collapse
basicaly what I was saying it works on stock ONEPlus roms only it seems and you just have to deny root when adding cards. I tried to use lil while ago but it said my cards were not available yet to use with Android Pay

Just wanted to chime in with my post from another thread to consolidate threads:
I am running COS 12.1, rooted, with an unlocked bootloader. I recently upgraded to Android Pay after using Google Wallet for NFC payments for years on my old GS4 and my OnePlus One.
At first, I was unable to add my payment card due to being rooted. Easily fixed, I unrooted using SuperSU to do a full unroot and was able to add my card and complete the app setup.
The showstopper is that whenever I try to use it at a merchant, I end up with a screen that says Confirm your password - you must unlock to use Android Pay. No matter how many times I enter my password it just keeps asking over and over. I disabled the quick unlock feature under lock screen settings just in case that was the issue, but it made no difference. An ongoing support case with Google just came back with the following:
"The specific error message that you saw means that your device can't support Android Pay's advanced security. It seems that the phone manufacturer has modified the operating system to the point where it is no longer compatible with our software. You may want to use Android Pay on a different device for the most secure payments."

just as an update i re-flashed stock rom and realized using xposed and make any additional changes to the system folder causes it not to work whether I have supersu checked off or not. Now with that said i have it working fine with stock and having supersu loaded from twrp and play store nothing else. I also set up a tasker command to uncheck supersu prior to me using Android Pay. 1 click I guess I waas being lazy

Is your bootloader unlocked?
Sent from my Nexus 10 using XDA Premium 4 mobile app

playya said:
just an fyi i tried stock for the hell of it and it worked with just unchecking supersu root option. Maybe a buildprop edit to trick it to think its a basic stock rom may work
Click to expand...
Click to collapse
I have tried disabling root and root cloak. I am on Exodus rom and it has "morph mode" where I tried both methods in Exodus mode and AOSP mode. If this helps narrow down the problem.

For me on Exodus (haven't tried any of the morph modes), the unlocked bootloader seems to be the culprit. Hopefully someone figures out a workaround.

Hurricane Andrew said:
Is your bootloader unlocked?
Sent from my Nexus 10 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
yes... if you are asking me
---------- Post added at 02:29 PM ---------- Previous post was at 02:27 PM ----------
Digil said:
For me on Exodus (haven't tried any of the morph modes), the unlocked bootloader seems to be the culprit. Hopefully someone figures out a workaround.
Click to expand...
Click to collapse
bootloader is not the problem. Android Pay is looking for more than likely specific files in your system that are missing in AOSP or custom roms. I flashed stock and as long as I uncheck SuperSu its been working fine for me. I have added several cards over the past week

Deleted
---------- Post added at 10:57 PM ---------- Previous post was at 10:56 PM ----------
playya said:
yes... if you are asking me
---------- Post added at 02:29 PM ---------- Previous post was at 02:27 PM ----------
bootloader is not the problem. Android Pay is looking for more than likely specific files in your system that are missing in AOSP or custom roms. I flashed stock and as long as I uncheck SuperSu its been working fine for me. I have added several cards over the past week
Click to expand...
Click to collapse
What Rom are you Using ?!?

Hurricane Andrew said:
Is your bootloader unlocked?
Sent from my Nexus 10 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
No need for a locked bootloader on 1+ it works fine but strictly with stock

Skitts said:
Deleted
---------- Post added at 10:57 PM ---------- Previous post was at 10:56 PM ----------
What Rom are you Using ?!?
Click to expand...
Click to collapse
I am running a stock rooted rom I found here. I tried to do it with Calkulins rom but it failed install for me. also no xposed or anything extra in system that may not need to be there. Its been working fine like this for a week now. I just used it again last night. I turn off SuperSu prior to using just for good measure

playya said:
I am running a stock rooted rom I found here. I tried to do it with Calkulins rom but it failed install for me. also no xposed or anything extra in system that may not need to be there. Its been working fine like this for a week now. I just used it again last night. I turn off SuperSu prior to using just for good measure
Click to expand...
Click to collapse
Thank Man I'll Give it A try see if I get the same results. As Of right now I'm Running Blisspop And I keep On getting the error.

Skitts said:
Thank Man I'll Give it A try see if I get the same results. As Of right now I'm Running Blisspop And I keep On getting the error.
Click to expand...
Click to collapse
So was I and I left them for crdroid which has a lot less issues. But I flashed stock to try out Android Pay and I have been surprisingly pleased. It will work just don't flash SuperSU but use built in version or update via TWRP option if asked after flashing rom

Does anyone have the apk for the version of Google Wallet right before the update to Android Pay? I'd like to at least have something that works.

rbrugman said:
Does anyone have the apk for the version of Google Wallet right before the update to Android Pay? I'd like to at least have something that works.
Click to expand...
Click to collapse
android authority has it and if you do a google search for it you will find it. also know that you have to un-tick auto updates in Google Play. I wiped data in Google play, Google Play Services prior to installing the now outdated version. I had to do this so that when I loaded the older version it will try and update the moment you try and set it up.

Nandroid backup needed

Woudl anyone kindly give me a copy of your nandroid backup please? I have a corrupted file system. My /system/app and my /system/priv-app have both been combined together in /data/data. There are some other unique changes too. I don't even know how the phone can operate like this, but it works flawlessly. Unfortunately, I have been hacked and nothing works to get rid of it. If anyone has good adb command skills and can guide me, I'd be happy with that. My adb commands are not extended, and not of them work thus far. I want my phone back in good shape. As of now, there is a bootloader script that erases any changes upon boot.. I need help here. I keep asking, and I see dozens of you reading... but not one reply. Help would be nice. Lol

Why do you just use Odin and reflash the tar
Sent from my SM-N920P using XDA-Developers mobile app

Yes, odin flash will wack the bootloader partitions as well.

rayraycarter4 said:
Why do you just use Odin and reflash the tar
Sent from my SM-N920P using XDA-Developers mobile app
Click to expand...
Click to collapse
If it was that simple I wouldn't be here asking for help. I've been flashing for 4 years. Hundreds of times. More than 20 devices. There is a modified bootloader that wipes any updates and keeps the script alive. It takes over my whole OS. I know because I have two Note 5's. One I just got from my friend. It has never been rooted. So when I compare the two, I see lots of major differences. Some of my settings are completely gone. Like the ability to use fingerprints to open websites and verify Samsung account. Then, on the unrooted phone, when I swipe left to briefing, it says "Briefing" wants permission. On my previously rooted, but currently unrooted phone, it says "Touchwiz Home" wants permission. On top of that, I'm not getting the prompts for permissions when I open a app. They are already granted. when I first flash BPC3 and immediately flash TWRP I can see my system files in place. When I boot and look again form ROM Toolbox, the /system folder is empty and I found everything loaded in /data/data. I see several locations with recovery scripts, and one with a fstab.storage in the cache folder. If I delete the cache, the phone will not boot. If I take any of the /data/data apps out, the phone will not boot. I have successfully got it to boot one time and everything seemed fine. However, over the course of a day, little by little, everything reinstalls itself. I'm assuming from a masked backup location. This is a real hack job, and I need some help. I'm not a complete idiot, however, this kind of thing is WAAAAAY over my head. I could start snapping screenshots and posting them here if any of you want to learn more about this and help me get it fixed. I can't use this phone like this. Somebody has complete control of my device.

tdunham said:
Yes, odin flash will wack the bootloader partitions as well.
Click to expand...
Click to collapse
Help me bro. This isn't something normal. Please. I'll provide you with whatever information you need. Read the above post.

Oh yeah, one other thing. When I use ODIN I am getting a message that says... "receiving message from bootloader. Please wait two minutes." Then it go the next file and says the same thing, On the third file it fails.

Okay, so I found some logs in the dropbox folder and found a bunch of code linked to a GitHub account owned by this guy. http://forum.xda-developers.com/member.php?u=1897326 I'm not saying that he is responsible, but I am saying that someone is using his code maliciously. I have it on my phone, I have system logs to verify it, and I have tons of problems with all my accounts being hacked. My phone will not reinitialize on Smart Switch. Nothing works. Sombebody please help me update my bootloader. I don't know how to do this myself and I can not find any information anywhere. Flashing a new sboot.tar with ODIN does not work. Upon reboot, it gets erased and the same old crap comes back.

Sleepycloud said:
Okay, so I found some logs in the dropbox folder and found a bunch of code linked to a GitHub account owned by this guy. http://forum.xda-developers.com/member.php?u=1897326 I'm not saying that he is responsible, but I am saying that someone is using his code maliciously. I have it on my phone, I have system logs to verify it, and I have tons of problems with all my accounts being hacked. My phone will not reinitialize on Smart Switch. Nothing works. Sombebody please help me update my bootloader. I don't know how to do this myself and I can not find any information anywhere. Flashing a new sboot.tar with ODIN does not work. Upon reboot, it gets erased and the same old crap comes back.
Click to expand...
Click to collapse
So what happened ? Did you get it fixed ?
Sent from my SM-N920P using Tapatalk

djxn40 said:
So what happened ? Did you get it fixed ?
Sent from my SM-N920P using Tapatalk
Click to expand...
Click to collapse
I'm still working on it. This has some incredibly complicated scripts designed to stop any fixes. I haven't figured it out yet. I have been working non-stop for a week now. I think I'm close to figuring it out, but I'm not as good or even close to his skill set. A lot of this stuff is like looking at Chinese. I'm working on a new initramfs to get everything in order again. I hope to be finished soon. I'll post a detailed fix when I am finished. I'm not going anywhere, I'm here to help others as much as possible. I'll be posting a fix soon.

Somebody share their 100% stock nandroid with me. If you are worried about your data, restore the backup, do a factory reset then back up that nandroid and send me a link in a pm. I need it badly. This crap that i have isnt going away with anything. In four years, this is the ONLY device that I have not been able to fix. I know somebody was smart and backed up their factory image before they rooted. I need that person to step forward please. My device is severely f**ked up. ODIN doesnt fix it, neither does smartswitch. It has been altered with linux folders that get over looked. Please. Im a good guy. Im not gonna abuse anything you send me. Promise on everything. If you prefer to email me a link, its [email protected].

Sleepycloud said:
Somebody share their 100% stock nandroid with me. If you are worried about your data, restore the backup, do a factory reset then back up that nandroid and send me a link in a pm. I need it badly. This crap that i have isnt going away with anything. In four years, this is the ONLY device that I have not been able to fix. I know somebody was smart and backed up their factory image before they rooted. I need that person to step forward please. My device is severely f**ked up. ODIN doesnt fix it, neither does smartswitch. It has been altered with linux folders that get over looked. Please. Im a good guy. Im not gonna abuse anything you send me. Promise on everything. If you prefer to email me a link, its [email protected].
Click to expand...
Click to collapse
If you have two note 5 why dont you just root the other one and make a nandroid backup or just use one of the many resources here like the marshmellow tar or a custom rom to get what you need. Just seems odd

greco2003 said:
If you have two note 5 why dont you just root the other one and make a nandroid backup or just use one of the many resources here like the marshmellow tar or a custom rom to get what you need. Just seems odd
Click to expand...
Click to collapse
If I could use a .tar or a zip file to fix my phone, I wouldn't be here asking for a nandroid. Rooting my second Note 5 would be stupid because I see the same app data already infected on this one. Once I fix my 64GB Note 5 I'm going to sell this 32GB . Nobody buys a rooted phone. I own a cell phone repair shop. I know they won't buy rooted phones unless they are stupid. They always come back complaining about Samsung pay or something security wise that alerted them to the fact that is has been rooted. I'm seeing some of the same **** on my unrooted phone that I see on my rooted phone. It is the app-data, but at least with this phone, I can factory reset and get rid of it and start over. I 'm going to send emails to Google and ask them to clear my stored app-data on every app that is on my account. I can't keep this **** off my phone. This mother***ker wrecked my device. I have removed two of the 6 extra partitions, and now it won't boot. Even if I flash a new .tar with a pit file and nand erase. This is my first phone is four years of flashing and modding that I have not been able to fix. I am not getting any help. Just dumb questions like this one over and over. Lol IF I COULD DO ANY OF THAT, I WOULD NOT BE ASKING FOR HELP. I need a nandroid because that will fix my phone. The one I have is altered and the rest got wiped from my computer when I posted that I had logs. Those got wiped too. This person behind this is all up in my computers and phones and I can't keep them out. I've done everything. Wiped hard drives and started with a clean install on both, bought a new router and set up new passwords. and flashed my phones. It slows them down, but hey get right back in everything over the course of a week. I'm so f**king sick of this. The funny part, I bet more that half of you have the same problems, but you aren't intimate with your devices enough to know that someone is there. This person behind this is highly skilled.... to say the least. This **** was on my phone for at least 3 months, maybe four, before I even realized something was wrong. That is how smooth this is. The phone works flawlessly still. (until I removed two partitions anyways. Now it won't boot.) Share your stock nandroid after wiping it with a factory reset. I don't need any of your personal information.... Just your legit partitions layout. What is so funny about that? I have seen this request a few times in the last four years. I never thought it would happen to me though.

You wanna know a little secret? The app power saving feature has been hacked to allow apps to retain some of the battery power when the device is turned off. Here is the deal. It is not really turned off. It is in a hibernate mode that retains the app-data so that when you turn the phone back on, everything comes back. You think this is not possible? Lol you better study more, and start opening scripts on your device and reading them. You'll find all sorts of neat things if you have been flashing and modding.

Sleepycloud said:
You wanna know a little secret? The app power saving feature has been hacked to allow apps to retain some of the battery power when the device is turned off. Here is the deal. It is not really turned off. It is in a hibernate mode that retains the app-data so that when you turn the phone back on, everything comes back. You think this is not possible? Lol you better study more, and start opening scripts on your device and reading them. You'll find all sorts of neat things if you have been flashing and modding.
Click to expand...
Click to collapse
I'm a flashaholic I've been flashing and rooting since my first smartphone back in 2009 the HTC Evo 4g but I always remember rule number one make a nandroid backup I make them weekly even if I change nothing on my phone
Sent from my SM-N920P using XDA-Developers mobile app
---------- Post added at 07:58 PM ---------- Previous post was at 07:56 PM ----------
Are you wanting a marshmallow one or a lollipop one they take different bootloaders
Sent from my SM-N920P using XDA-Developers mobile app

greco2003 said:
I'm a flashaholic I've been flashing and rooting since my first smartphone back in 2009 the HTC Evo 4g but I always remember rule number one make a nandroid backup I make them weekly even if I change nothing on my phone
Sent from my SM-N920P using XDA-Developers mobile app
---------- Post added at 07:58 PM ---------- Previous post was at 07:56 PM ----------
Are you wanting a marshmallow one or a lollipop one they take different bootloaders
Sent from my SM-N920P using XDA-Developers mobile app
Click to expand...
Click to collapse
I'll take anything that I can get as long as you are 100% sure that it is unaltered. I'd love to have the L and the M if you don't mind. Just so I have options. I'm dying to end this b.s. Please send me either one or both. I promise I"m not gonna abuse you in any way.

The truth is, it doesn't matter. You can still revert all the way back to OI6 from PC3. I tried AOK but it wouldn't flash. Send me anything bro. I'd be grateful.

I'll see what I can do when I get home at work now what version is your phone currently running??
Sent from my SM-N920P using XDA-Developers mobile app
---------- Post added at 08:08 PM ---------- Previous post was at 08:06 PM ----------
Also is rooted gonna be OK because all of my backups are from a rooted device
Sent from my SM-N920P using XDA-Developers mobile app

greco2003 said:
I'm a flashaholic I've been flashing and rooting since my first smartphone back in 2009 the HTC Evo 4g but I always remember rule number one make a nandroid backup I make them weekly even if I change nothing on my phone
Sent from my SM-N920P using XDA-Developers mobile app
---------- Post added at 07:58 PM ---------- Previous post was at 07:56 PM ----------
Are you wanting a marshmallow one or a lollipop one they take different bootloaders
Sent from my SM-N920P using XDA-Developers mobile app
Click to expand...
Click to collapse
You are absolutely correct. I used to always make nandroids, but I got cocky and lazy and quit doing it. Now I regret totally regret that. I will never in my life root another phone without making a nandroid and keeping it safe in two spots. One in the cloud, and the other on a OTG all by itself. I need you bro. Please send me a good nandroid so I can end this nightmare. Lol

greco2003 said:
I'll see what I can do when I get home at work now what version is your phone currently running??
Sent from my SM-N920P using XDA-Developers mobile app
---------- Post added at 08:08 PM ---------- Previous post was at 08:06 PM ----------
Also is rooted gonna be OK because all of my backups are from a rooted device
Sent from my SM-N920P using XDA-Developers mobile app
Click to expand...
Click to collapse
Yeah, that is fine. Rooted is great as long as you didn't mod it before that nandroid. If so, the partition layout will be intact and when I flash it, it will wipe my device completely and I'll be good again. I have seen a few others with this problem over the years, and the only way they fixed it was by using someone's nandroid. I'm am a big fan of the Evo 4G! That is what started it all for me! Lol I made some pretty awesome JB roms for the Evo. You can see them here. http://android.aokforums.com/roms-vf3.html When I get this cleared up, I'm going to make something nice for the Note 5. It's been awhile since I've compiled any roms, but I am suddenly eager to start up again. Thank you for stepping up here bro. I won't forget this.

I can send you a backup of my current setup now but it's the deodexed marshmallow rom with sky-high kernel version 3.0
Sent from my SM-N920P using XDA-Developers mobile app

Microphone issue with Oneplus one

I have a oneplus one that I just returned to stock using the method in this thread: http://forum.xda-developers.com/onep...stock-t2826541
Problem is that at some point, while it was rooted, I used this method to make my phone microphone work (changing the build.prop file): https://forums.oneplus.net/threads/f...-issue.284449/
If I had remembered that I'd done that, I might have just left the phone alone. So, now that I'm back to stock and unrooted, my microphone doesn't work and I can't use the above method to make it so. Is there a solution out there I can use without going back to root?
My exact problem with the mic is that when I talk into the phone, the person on the other end can't hear me but I can hear myself (echo) in my earpiece. I can hear the person on the other end fine. If I switch to speaker phone I still have the same issue. Any help would be appreciated.

You'll need to go root again. Lucky this isn't too hard especially if you maintained a custom recovery. If not, then you will have to use adb. Or bacon root toolkit (the easy way).
Sent from my A0001 using Tapatalk

Not really what I wanted to hear, but I guess I gotta do what I gotta do. How can I tell if I maintained a custom recovery or not? I don't think I did.
And can I root without installing a custom recovery or custom rom? All the guides I've found so far talk about all these steps and unlocking the bootloader.

anonymous93 said:
Not really what I wanted to hear, but I guess I gotta do what I gotta do. How can I tell if I maintained a custom recovery or not? I don't think I did.
And can I root without installing a custom recovery or custom rom? All the guides I've found so far talk about all these steps and unlocking the bootloader.
Click to expand...
Click to collapse
You can use KingRoot to root without custom recovery. After changing the values you can then unroot it to get future OTA updates

anonymous93 said:
Not really what I wanted to hear, but I guess I gotta do what I gotta do. How can I tell if I maintained a custom recovery or not? I don't think I did.
And can I root without installing a custom recovery or custom rom? All the guides I've found so far talk about all these steps and unlocking the bootloader.
Click to expand...
Click to collapse
Just boot into recovery (power off then power on pressing volume down+power) and see what you get.
Sent from my A0001 using Tapatalk

Elius2676 said:
Just boot into recovery (power off then power on pressing volume down+power) and see what you get.
Sent from my A0001 using Tapatalk
Click to expand...
Click to collapse
I got Cyanogen Recovery. Options are "reboot system now", "Apply update", "factory reset", and "advanced".

So I used the baconroot toolkit to unlock the bootloader. Then rooted it with a custom recovery. My phone is now stuck in the bootloop. I can boot into TWRP, which I know is a good thing. Just not sure what to do next now to fix it. I'm doing some searching on the forums, but if someone can point me in the right direction, it would be appreciated.

anonymous93 said:
So I used the baconroot toolkit to unlock the bootloader. Then rooted it with a custom recovery. My phone is now stuck in the bootloop. I can boot into TWRP, which I know is a good thing. Just not sure what to do next now to fix it. I'm doing some searching on the forums, but if someone can point me in the right direction, it would be appreciated.
Click to expand...
Click to collapse
Recovering from this will require fastboot magic. The bacon root toolkit should've already gotten your drivers all setup. Now search the web for how to push and install files from your computer in fastboot mode.
Sent from my A0001 using Tapatalk
---------- Post added at 01:03 PM ---------- Previous post was at 01:02 PM ----------
Oh, you can boot into TWRP! Nevermind, just follow the steps to a clean install of your ROM (which one is it, btw?)
Sent from my A0001 using Tapatalk

Elius2676 said:
Recovering from this will require fastboot magic. The bacon root toolkit should've already gotten your drivers all setup. Now search the web for how to push and install files from your computer in fastboot mode.
Sent from my A0001 using Tapatalk
---------- Post added at 01:03 PM ---------- Previous post was at 01:02 PM ----------
Oh, you can boot into TWRP! Nevermind, just follow the steps to a clean install of your ROM (which one is it, btw?)
Sent from my A0001 using Tapatalk
Click to expand...
Click to collapse
Clean install of my ROM from TWRP is good because I failed to mention that I can't get into fastboot mode. The ROM I had was the factory image from this thread: http://forum.xda-developers.com/oneplus-one/general/guide-return-opo-to-100-stock-t2826541
What steps do I take to do a clean install of that?

anonymous93 said:
Clean install of my ROM from TWRP is good because I failed to mention that I can't get into fastboot mode. The ROM I had was the factory image from this thread: http://forum.xda-developers.com/oneplus-one/general/guide-return-opo-to-100-stock-t2826541
What steps do I take to do a clean install of that?
Click to expand...
Click to collapse
I'm assuming you've tried to follow the steps given in the link you just sent?
Sent from my A0001 using Tapatalk

Elius2676 said:
I'm assuming you've tried to follow the steps given in the link you just sent?
Sent from my A0001 using Tapatalk
Click to expand...
Click to collapse
Yes and no. Turns out I was actually able to boot my phone into fastboot mode. So I did that, used the baconroot toolkit option of "flash stock + unroot" and I was back to the start. My device now has an unlocked bootloader, but I think I have issues with the tamper bit. When I get my device info the "Device tampered" is set to "false" and the "device unlocked" is set to "true". I know they should both be true, but I can't for the life of me figure out how to use the zip file to change the tamper bit. I did it before, but I'm just not figuring it out this time. I hate doing this stuff.
I think once the tamper bit is correct I should be able to go back to baconroot to root and reinstall the custom recovery.
Update: I finally figured this out, now rooting with bacon root, hoping it works.

I'm all set, now to make the adjustments so my microphone works. Thanks to everyone that helped!

So, I forgot that one of the reasons I unrooted was because I couldn't update and I was tired of getting notices that there was an update and not being able to execute it.
So I now have cyanogen OS version 12.1 and I have a notice for an incremental update. I made sure that "update cm recovery" was unchecked so that I didn't lose root, hit the update button and I got the error message "error executing updater binary in zip '@/cache/recovery/block.map' "
From what I could find it looks like I need to download and flash the update rather than using the OTA updates. Is that correct? Can I update to 13 or 14 or are there issues with those roms? where do I go to get these downloads? when I flash updates does it wipe my phone? will I have to reinstall all my apps and settings?
I really dislike doing this stuff. I can do it, but I hate it. any very clear step by step instructions would be GREATLY appreciated.

anonymous93 said:
So, I forgot that one of the reasons I unrooted was because I couldn't update and I was tired of getting notices that there was an update and not being able to execute it.
So I now have cyanogen OS version 12.1 and I have a notice for an incremental update. I made sure that "update cm recovery" was unchecked so that I didn't lose root, hit the update button and I got the error message "error executing updater binary in zip '@/cache/recovery/block.map' "
From what I could find it looks like I need to download and flash the update rather than using the OTA updates. Is that correct? Can I update to 13 or 14 or are there issues with those roms? where do I go to get these downloads? when I flash updates does it wipe my phone? will I have to reinstall all my apps and settings?
I really dislike doing this stuff. I can do it, but I hate it. any very clear step by step instructions would be GREATLY appreciated.
Click to expand...
Click to collapse
So sounds like you just wiped everything and your phone is back to stock now, but I'm getting the impression you still have a custom recovery or modified system partition and the OTA updates don't like that. So yes, you'll need to flash updates in your recovery. It's not as bad as it sounds.
And about Android versions available to you, the stock COS (which might actually say "CM..." when you check your Android version in "about phone" in settings - confusing, I know) can normally receive the OTA updates (except in the cases mentioned above) or you can get the official updates online in zip form and flash them yourself (even with the stock recovery -which I'm pretty sure you have still, unless one of your methods to fix the phone installed a custom one like TWRP or CWM). The other ROM/OS options you have are about as plentiful as the stars in the heavens (since android is open source). I personally like to stick with CM especially since they do what they do very well and they have a particular interest in there OnePlus One. They just released CM 14 nightlies (which basically means it's the latest version of the OS, bugs and all, built every day). Though, to be honest, this CM 14 nightly is ridiculously stable for a freshly released nightly. At this point, though, cyanogen hasn't implemented a fair number of their customizations that are in their previous versions. So if you want the best complete CM experience right now, go with CM 13.
And to answer your question, updates like the ones that are OTA, don't wipe your data or storage. However, if you switch from COS to CM, you'll have to clean install and that will lose your data at the least (your internal storage can usually be kept between ROMs if you've got a custom recovery).
Sorry, in throwing a lot at you right now. Probably just created more questions than answers...
Sent from my A0001 using Tapatalk

Thanks for your help and the explanations. When you talk about COS vs. CM is that Cyanogen OS vs. Cyanogen Mod?
I was able to root and I have TWRP installed. In about phone it says "Cyanogen OS version" is "12.1-yog4pas1n0". That's the Cyanogen OS correct?
Where do I go to download the update for 13 (whatever matches what I already have) and is there a guide for doing that? I'm reading about updating to 13 and everything I see (so far) states that the update has to happen with stock recovery. Is there an option to run the update with TWRP?

Wait a minute... If I unroot but keep the bootloader unlocked then it won't wipe my phone and I'll be able to take the ota updates right? What about the change I made to the build.prop file for my phones microphone? Will that get wiped if I unroot? That's the big question.
Nevermind about unrooting. After some searches it seems that a full unroot would require a rest which would delete the mod I made for the microphone. I found that supersu can "unroot", but it's not actually a fill unroot which means that I still probably wouldn't be able to do the ota updates.

Maybe I need to gain a better understanding of your original problem... But I think that there are plenty of ROMs out there that have addressed microphone issues with the OnePlus One (I think a lot of the problems come from it having 2 noise cancelling mics). Not 100% sure if cyanogen ever implemented a fix for the mic in later updates - probably a good thing to look into. Otherwise, look into alternative ROMs. I personally don't have issues with the latest CyanogenMod nightlies, but it almost seems like there are differences between OnePlus ones (inconsistency in the manufacturing process, perhaps).
Oh, and yes when I say COS and CM, they are cyanogen OS and CyanogenMod, respectively.
Sent from my A0001 using Tapatalk
---------- Post added at 01:34 PM ---------- Previous post was at 01:33 PM ----------
And if you don't want to use something potentially as unstable as a nightly, CyanogenMod also has snapshots that are more like monthly, stable versions.
Sent from my A0001 using Tapatalk

Elius2676 said:
Maybe I need to gain a better understanding of your original problem... But I think that there are plenty of ROMs out there that have addressed microphone issues with the OnePlus One (I think a lot of the problems come from it having 2 noise cancelling mics). Not 100% sure if cyanogen ever implemented a fix for the mic in later updates - probably a good thing to look into. Otherwise, look into alternative ROMs. I personally don't have issues with the latest CyanogenMod nightlies, but it almost seems like there are differences between OnePlus ones (inconsistency in the manufacturing process, perhaps).
Oh, and yes when I say COS and CM, they are cyanogen OS and CyanogenMod, respectively.
Sent from my A0001 using Tapatalk
---------- Post added at 01:34 PM ---------- Previous post was at 01:33 PM ----------
And if you don't want to use something potentially as unstable as a nightly, CyanogenMod also has snapshots that are more like monthly, stable versions.
Sent from my A0001 using Tapatalk
Click to expand...
Click to collapse
I'm pretty sure my problem is related to the 2 noise cancelling mics issue. It works great with the build.prop changes. Once I get an update installed on my phone I'll have to see how the microphone works.
So if I want to go to cyanogenmod 13, I would have to wipe my device and install that OS. When I do a backup in twrp, can I restore that backup (i.e., all my apps & settings) once the new os is installed? Or does that option restore the old OS?

anonymous93 said:
I'm pretty sure my problem is related to the 2 noise cancelling mics issue. It works great with the build.prop changes. Once I get an update installed on my phone I'll have to see how the microphone works.
So if I want to go to cyanogenmod 13, I would have to wipe my device and install that OS. When I do a backup in twrp, can I restore that backup (i.e., all my apps & settings) once the new os is installed? Or does that option restore the old OS?
Click to expand...
Click to collapse
A backup in TWRP (or nandroid backup) is like a perfect picture of what you phone was running just before you booted it into recovery. So when you restore one of them, it is like the phone steps back in time to when you made the backup, restoring the system (read: OS), data (read: apps), and cache.
In other words, you do a backup so that you always have something you can restore if you break your phone/have boot loops or what have you when flashing new ROMs.
If you go from COS to CM, it will require a clean install which means you will need to setup your phone the way you like it again. That being said, there is an app called Titanium backup that doesn't work the same as a nandroid, but can backup your apps and data and is capable of restoring them from one ROM to the next. It's not always perfect, but it can do a lot.
I personally have just chosen to embrace the chance of needing to start fresh every once in a while. I use Nova launcher and I have a Kustom LWP, both of which I made backups of in their respective app settings. I save those backups and whatever else I want to internal storage and I just don't wipe that partition in TWRP. To be safe, I also keep backups in the cloud. Everything else I just download again from the play store and setup the way I like.
Sent from my A0001 using Tapatalk

Well, its looking more and more like I might go to cm. Once I do that will I still have to wipe my phone to flash updates? Or will I still have to do that for updates every once in a while?