Hello All:
I have been using and tinkering with phones for years now, note 2,3,4 and 5. I say this so you understand I'm not new to fixing usual issues with rooting and flashing custom roms, etc. There may be a solution to this, but I haven't been able to find it after weeks of searching and trying different things.
After flashing Tek's Rom with COJ -> COK my phone gets the "This phone has been flashed with unauthorized software and has been locked..." error no matter what I do. I have completely wiped, formatted, Odin'd stock firmware and flashed and flashed every bit of software I can find, including using at least ten fresh md5 verified new downloads of the firmware, etc. I have tried arter97's kernels including last several versions, and several other kernels I can't remember.
Anyway, when I complete wipe and format, and then Odin flash the stock firmware (COK), my phone never leaves the Samsung Note 5 boot screen. If I flash a kernel, I can get to the setup mode, but I get the error message that my device has been locked and cannot make calls or register my phone on the tmobile network. My sim card works just fine with other phones. I am using it as we speak on a Lumia 950, but I cannot stand not having the spen.
I have tried flashing kernels through philz, twrp, and the stock recovery. I have tried OTG and flashing kernels from the internal SD card once I flash a kernel and get past the setup. Since I use two step verification, and cannot receive texts, it's a real pain to get into my google account.
When I try to login to my Samsung account, it says, "processing failed," each time. Tmobile has been less than helpful. I am at wit's end. Anyone have any thoughts? I'd really appreciate the help.
Thanks.
Make sure you have everything backed up. Odin to stock be sure OEM unlocking is on. Do a full wipe in stock recovery. then try to root again.
steve97ta said:
Make sure you have everything backed up. Odin to stock be sure OEM unlocking is on. Do a full wipe in stock recovery. then try to root again.
Click to expand...
Click to collapse
Forgive me, and thank you for your reply, but I am not sure if I could have been any more clear that I have full wiped, odin'd back to the stock firmware, etc. no less than a hundred times. Not only that, but I have tried COJ, COK, all three recoveries, different kernels, etc. I can assure you OEM unlocking is on, and has been on each and every time.
In ODIN Mode (Download Mode), my phone reads:
Download Speed: Fast
Product Name: SM-N920T
Current Binary: Samsung Official
System Status: Custom
FRP LOCK: OFF
Secure Download: Enabled
KNOX WARRANTY VOID: 1 (0x0301)
RP SWREV: B:2 K:0 S: 0
It does not change much when I flash a kernel or a custom rom, other than current binary to "Custom"
Anyway, I want to be clear:
I have turned on OEM unlocking, no fingerprint lock or any lock mechanism, full wiped through philz recovery, twrp, etc. and ODIN flashed the STOCK firmware from this forum, from Tek's thread, from Sammobile (I even paid the $10.00 to make sure), and I absolutely cannot get my Sim card to register on the network.
I tried again this morning. First, I full wiped and ODIN'd COJ. Then, I full wiped and ODIN'd COJ w/NAND Erase All. I should note that each time I boot to recovery, I get the same old message, "DM-Verity Verification Failed... Need to check DRK first..."
I also get this error when I wipe, "preload checkin... E: failed to mount /preload (no such file or directory)"
I then full wiped and ODIN'd COK. I rinsed and repeated. I still get the exact same errors I mentioned above. The phone sits still at the Samsung boot screen (it does not get to the colored logo screen or the T-Mobile screen, just the black and white) for as long as I will allow it (sometimes hours).
Update:
I have now individually full wiped and flashed the BL, AP, CP, CSC, and PIT files multiple times with no changes. I have read somewhere that I may need to unpack the firmware file itself and remove the cache.img file?
If you are using odin you should only need to put the tar in the AP slot. Are you using the factory note 5 cable? Also what version of odin?
steve97ta said:
If you are using odin you should only need to put the tar in the AP slot. Are you using the factory note 5 cable? Also what version of odin?
Click to expand...
Click to collapse
Yes. I am trying additional methods because, as I have said, I have already tried to do the basic methods of wipe data / internal storage / system / cache /dalvik cache (10x), ODIN stock firmware, rinse repeat.
Yes, I am using the factory cable.
Odin version 3.10.7
I am however having additional issues caused by my efforts. My E:/data partition seems to be missing.
Thanks
er0k02 said:
Yes. I am trying additional methods because, as I have said, I have already tried to do the basic methods of wipe data / internal storage / system / cache /dalvik cache (10x), ODIN stock firmware, rinse repeat.
Yes, I am using the factory cable.
Odin version 3.10.7
I am however having additional issues caused by my efforts. My E:/data partition seems to be missing.
Thanks
Click to expand...
Click to collapse
That happened to me if you have a backup of your efs partition you can restore and it should fix verify your imei that is the same as the one it has on the box on a sticker @Jammol can help in here he is the one that helped me he is good at this kind of stuff and remember to always do a backup i learned from this thing too
This only means your imei is messed up same things that you mention happened to me even that samsung account failed stuff and all it was the imei lol
Sent from my SM-N920T using Tapatalk
Ok, thanks. What happens if I do not have an EFS backup? I may have a NANDROID from TWRP somewhere, but I doubt it.
I know you did a million things.
For me, after I flash stock unrooted thru Odin, I will get bootloop until I wipe in Stock recovery.
I appreciate that, but yes I had also tried that. At this point I think the poster above is correct in that I need to restore the EFS partition. I have read tricks of switching the mount point, and also about using some "magic" tools online. Does anyone know how I can fix the missing partition? Tmobile isn't helpful, and I can't get on the phone with anyone from Samsung.
Also, update: I was able to successfully flash the android 6.0 rom on cokc firmware last night, but it is still giving me the same problems not recognizing my sim and not working as far as registering on the network. I also cannot login to my Samsung account.
I really appreciate the help.
er0k02 said:
I appreciate that, but yes I had also tried that. At this point I think the poster above is correct in that I need to restore the EFS partition. I have read tricks of switching the mount point, and also about using some "magic" tools online. Does anyone know how I can fix the missing partition? Tmobile isn't helpful, and I can't get on the phone with anyone from Samsung.
Also, update: I was able to successfully flash the android 6.0 rom on cokc firmware last night, but it is still giving me the same problems not recognizing my sim and not working as far as registering on the network. I also cannot login to my Samsung account.
I really appreciate the help.
Click to expand...
Click to collapse
Just as cautionary reminder, always make sure that OEM Unlock is turned on before flashing anything whatsoever. Even if you're on a custom rom already. I flash almost daily and I check every single time before I flash something. YOU NEVER KNOW!
You said earlier up that you have a TWRP right? If you still do check it to see if it has a backup of the EFS partition. If you do have the EFS partition backed up, try and remember what firmware you were on. You'll need to be on that firmware when you restore it. In other words, if you were on COKC when you made it, you'll have to be on that when you restore it. Also try restoring it on TekHD rom if you were on COKC when you made the backup. Don't wipe anything, and reboot after the restore. ONLY RESTORE THE EFS, NOTHING ELSE!!! Upon reboot, if you have a fully working phone again, do a factory reset from inside the rom. Once it reboots, if it works still, download his Stock Rooted Rom in post 5. Do a full wipe and flash that, your EFS should not wipe. Once rom is done flashing, reboot and see if you still have a fully working device. If you do, go ahead and try an Odin flash to full stock. Do a full wipe before using Odin.
Jammol said:
Just as cautionary reminder, always make sure that OEM Unlock is turned on before flashing anything whatsoever. Even if you're on a custom rom already. I flash almost daily and I check every single time before I flash something. YOU NEVER KNOW!
You said earlier up that you have a TWRP right? If you still do check it to see if it has a backup of the EFS partition. If you do have the EFS partition backed up, try and remember what firmware you were on. You'll need to be on that firmware when you restore it. In other words, if you were on COKC when you made it, you'll have to be on that when you restore it. Also try restoring it on TekHD rom if you were on COKC when you made the backup. Don't wipe anything, and reboot after the restore. ONLY RESTORE THE EFS, NOTHING ELSE!!! Upon reboot, if you have a fully working phone again, do a factory reset from inside the rom. Once it reboots, if it works still, download his Stock Rooted Rom in post 5. Do a full wipe and flash that, your EFS should not wipe. Once rom is done flashing, reboot and see if you still have a fully working device. If you do, go ahead and try an Odin flash to full stock. Do a full wipe before using Odin.
If you need further help, add me to Google Hangouts [email protected]mail.com
Click to expand...
Click to collapse
Thanks, I'll add you to hangouts. I don't have a backup EFS, for sure.
Possible to fix a corrupt EFS partition without a backup?
Man, I am in the same boat. I do not have an EFS backup. Any help would be appreciated.
I've done it. I am no longer locked out of the network, no longer getting the error, EFS fixed without a backup, Samsung account accessed.
I'll write out the steps and post in a bit. Battery is dying.
Thanks
Do you have the steps to recover the EFS? I've been stuck for few days now and feel it is a crime to exhaust every option as you already figured it out. Thanks for the share either way!
just throwing in my two cents...I have this same bizarre boot loop, Odin not sticking crap. the fact it still says your system is custom tells me it's in the same ball park.
do everything you usually do, then reset twrp settings to default, reboot to recovery, wipe all cache blah blah, then reformat to ext4, repair, resize every partition. to get davlik, select it and system together, then file system to ext4, to get the internal storage, select it with data. then reboot recovery...MOUNT SYSTEM...do it all again...
reboot, let it get stuck at logo...reboot to recovery clear caches, MOUNT SYSTEM, DO IT AGAIN.. just the caches...
you're welcome
you're
er0k02 said:
I've done it. I am no longer locked out of the network, no longer getting the error, EFS fixed without a backup, Samsung account accessed.
I'll write out the steps and post in a bit. Battery is dying.
Thanks
Click to expand...
Click to collapse
It would be interesting to know how you solved this. I just made sure I have an efs backup.
I completely forgot about this thread. I apologize to everyone for the delay.
To recap:
My phone was cellular bricked. It turns out I had a corrupted EFS partition. The way I managed to "fix" the problem was tedious and may not work for everyone.
1. I ODIN flashed the stock firmware multiple times;
2. I erased the data in my Samsung account. I had to do this online through their website. I think this was crucial.
3. During each initial ODIN flash, I selected Phone EFS clear, Phone Bootloader Update, Nand Erase All, Repartition, etc. in ODIN.
4. I then re-flashed stock COJ without selecting EFS clear, Phone Bootloader Update, Nand Erase All, Repartition, etc. I just let it select the normal options.
5. I then ODIN flashed TWRP, and flashed Jovy's ROM after flashing the Stock Modified Kernel.
6. I used the tool inside Jovy's Aroma installer [Fix Corrupt EFS Partition, or whatever it is called];
7. I didn't install any of the Samsung apps.
8. I then installed the ROM.
9. As soon as the ROM booted, I connected to WiFi as quickly as possible and ran through the steps as fast as I could before I gave T-Mobile the chance to display the message that my phone had been rooted and would no longer be able to connect to the cellular network. I logged into my google account and rebooted quickly before anything else happened. This took less than 30 seconds.
10. I went back into TWRP, full wiped and formatted.
11. Back to ODIN flashing Stock COJ.
12. ODIN flash TWRP.
13. Flash Jovy's ROM + Stock Modified Kernel.
14. Restore EFS partition.
15. Install ROM.
16. Finished.
It has been working since the day I posted above.
Try this tool
You might want to verify if Smart Switch tool by Samsung works on your device. I had a problem flashing my note 5 with the oem lock and this program saved the day. Is free and you can google it, I hope it helps.
Sorry, thanks, but no, if you choose to read this thread, you will understand that Samsung (in this situation), including Smart Switch, Kies, and other utilities, not only fail to rescue the firmware, but get in the way of ODIN, require resetting your Samsung account additional times, take up hours of bandwidth, ram, proc power, and gigs of hdd space. At best, Smart Switch is horrible, worthless, and stupid waste of time for those with an actual corrupted EFS partition, no backup, tripped Knox, and the other deets mentioned herein.
Related
Hi,
My SGT 7.7 seems brick after I took it out of my bag. It gets stuck and stays on the boot screen where says "Samsung Galaxy Tab 7.7" for a few seconds, and then just keep rebooting.
It is able to go into the Download Mode when I press "Power+Vol-", but no response when I press "Power+Vol+". I tried to flash all kinds of firmware with Odin, but nothing work.
I also tried to flash it with .pit, PDA, PHONE and CSC. I got this screen and then stopped and Odin says "Now Writing, Please wait about 2 minutes."
I appreciate your help!
same problem here, but caused from rom-manager! did nothing more than using the "reboot into recovery" option, i did NOT flash anything with rom-manager before!
download mode works, recovery works, but i can flash what i want, after turning the device on the "samsung 7.7" stays for about 30sec, then it reboots ad infinitum!
any ideas?
i'm within the one week were i can exchange the device without any problems, but i want to fix it myself if possible!
thx in advance!
TML1504 said:
same problem here, but caused from rom-manager! did nothing more than using the "reboot into recovery" option, i did NOT flash anything with rom-manager before!
download mode works, recovery works, but i can flash what i want, after turning the device on the "samsung 7.7" stays for about 30sec, then it reboots ad infinitum!
any ideas?
i'm within the one week were i can exchange the device without any problems, but i want to fix it myself if possible!
thx in advance!
Click to expand...
Click to collapse
I have seen similar symptoms on mine. it turned out to be corrupt /data filesystem. I had to use the sammy 3e recovery wipe data/factory reset option. And then reflash with odin.
(CWM could not fix this filesystem problem.)
(areyou sure rom manager is compatible with the different partitions on the 7.7)
Remember you will loose all user data !!!!!
davp said:
I have seen similar symptoms on mine. it turned out to be corrupt /data filesystem. I had to use the sammy 3e recovery wipe data/factory reset option. And then reflash with odin.
(CWM could not fix this filesystem problem.)
(areyou sure rom manager is compatible with the different partitions on the 7.7)
Remember you will loose all user data !!!!!
Click to expand...
Click to collapse
again thx,
but the problem is seems to be "deeper" than only a corrupt /data!
The tab doesnt boot further then "samsung 7.7", if data is corrupt then
at least android will load (bootanimation) and go into a bootloop in some stage!
Also, I didn't change or install or flash anything in rom-manager, I "only" used the reboot function!
After reflashing the device with repartition and HongKong.pit I think I messed up the partitions totally, so I would really need the PIT for 6810 (6800 has different partition layout) to repair this!
But as it seems no one has this PIT or is willing to provide it,
so I ordered an new tab which will arrive in the next hours, and return this one within the next days!
Where did you find the PIT file ? You may just destoried the partition. God bless you!
matth3w said:
Hi,
My SGT 7.7 seems brick after I took it out of my bag. It gets stuck and stays on the boot screen where says "Samsung Galaxy Tab 7.7" for a few seconds, and then just keep rebooting.
It is able to go into the Download Mode when I press "Power+Vol-", but no response when I press "Power+Vol+". I tried to flash all kinds of firmware with Odin, but nothing work.
Click to expand...
Click to collapse
I have a familiar problem....
I have not flashed or rooted my device - it is exactly how it came out of the box...
One morning while using it it froze - I did are reset by holding the power button down and then let it reboot but when it did it can not get past the "Samsung Galaxy Tab 7.7" screen.
Can get it into download mode, but if I go to recovery mode then all I get it a headline saying "Manual Mode" which grabs some manual .apk files and then just goes back into the boot mode with the "Samsung Galaxy Tab 7.7" screen.
Any ideas?
Had a Galaxy Tab Original and got the Galaxy SII and have mod them to death - just though for this one I would leave it original and enjoy the OTA updates as the were delievered - especially considering ICS in a matter of days
If you can boot into download mode you can call this a soft brick..
dont use ROM manager and install clockworkmod from that, incompatibility of cwm recovery will brick your phone..
Use odin only on PDA slots, you dont need repartition or pit files..it seems you got a corrupt recovery..
suwandiapr said:
Use odin only on PDA slots, you dont need repartition or pit files..it seems you got a corrupt recovery..
Click to expand...
Click to collapse
Suwandiapr - Thank you for this. When you say "Use odin only on PDA slots" you are suggesting that I will have to download and install a stock ROM aren't you?
Cheers (and again thank you)....
Aspi914 said:
Suwandiapr - Thank you for this. When you say "Use odin only on PDA slots" you are suggesting that I will have to download and install a stock ROM aren't you?
Cheers (and again thank you)....
Click to expand...
Click to collapse
yes, that is what he means.
Also, if you still have trouble after the first flash, you may need to go into samsung 3e recovery and do a data wipe/factory reset. Then flash again. Since these are non-wipe firmwares, simple flashing may not clear a corrupt filesystem.
Obviously you will lose all user data!
suwandiapr said:
If you can boot into download mode you can call this a soft brick..
dont use ROM manager and install clockworkmod from that, incompatibility of cwm recovery will brick your phone..
Use odin only on PDA slots, you dont need repartition or pit files..it seems you got a corrupt recovery..
Click to expand...
Click to collapse
thx, but as i said i DID NOT FLASH OR INSTALL ANYTHING with rom-manager, i only used the option "reboot into recovery"!
and i used odin to try to unbrick my device (i flashed a dozen roms as well as the sbl etc.), without any success. also, till now nobody has provided a 16GB PIT for 6810, therefore i returned the tab and grabbed a new one!
davp said:
Also, if you still have trouble after the first flash, you may need to go into samsung 3e recovery and do a data wipe/factory reset. Then flash again. Since these are non-wipe firmwares, simple flashing may not clear a corrupt filesystem!
Click to expand...
Click to collapse
Thank you Davp...
Ok...got the P6800ZSLA2 stock ROM and have managed to get it back...while I don't want to have to re-do all the data, I think I will take your advise and do a data wipe/reset.
Aspi914 said:
Suwandiapr - Thank you for this. When you say "Use odin only on PDA slots" you are suggesting that I will have to download and install a stock ROM aren't you?
Cheers (and again thank you)....
Click to expand...
Click to collapse
Yes you right, thats what i mean..
TML1504 said:
thx, but as i said i DID NOT FLASH OR INSTALL ANYTHING with rom-manager, i only used the option "reboot into recovery"!
and i used odin to try to unbrick my device (i flashed a dozen roms as well as the sbl etc.), without any success. also, till now nobody has provided a 16GB PIT for 6810, therefore i returned the tab and grabbed a new one!
Click to expand...
Click to collapse
Im sorry , my answer cannot solve your problem.. You say your device "stuck on Samsung logo" right? your recovery and download mode seem ok, from my experience its because /data corrupt or something crash on your filesystem..
If you can go to recovery menu, do factory reset,..
I cannot help you with pit.file coz i actually dont have the device right now..
Aspi914 said:
Thank you Davp...
Ok...got the P6800ZSLA2 stock ROM and have managed to get it back...while I don't want to have to re-do all the data, I think I will take your advise and do a data wipe/reset.
Click to expand...
Click to collapse
Good luck..
davp said:
I have seen similar symptoms on mine. it turned out to be corrupt /data filesystem. I had to use the sammy 3e recovery wipe data/factory reset option. And then reflash with odin.
Click to expand...
Click to collapse
I've experienced a similar problem with corrupt /data and couldn't overcome it.
How did you use Samsung recovery when you had CWM recovery flashed?
白い熊 said:
I've experienced a similar problem with corrupt /data and couldn't overcome it.
How did you use Samsung recovery when you had CWM recovery flashed?
Click to expand...
Click to collapse
You either get it from a full flash of stock firmware, or make your own tar with just recovery.img in it (extracted from stock). And flash with odin in the pda.
It is handy to be able to switch recoveries. CWM doesn't seem to match the 3e data wipe/factory reset.
The problem was:
I was playing a game, in the middle of it the Tab reset, I've never had it reset. Then it rebooted to the Samsung Tab 7.7 logo.
I thought, I'm lucky, made a CWM backup. So tried to restore the CWM backup. When the restore got to /data the tab rebooted again, i.e. something was messed with it.
So got stock firmware, flashed it from PC odin, flashed with success. But rebooted to the logo again.
Tried to get into the stock recovery, but it would only show "Updating..." something, I don't remember anymore, but the stock recovery wouldn't boot. Flashed it a couple of times, same result. Had to take the Tab back to the store...
Am kinda afraid to mess with it now, since I don't want it to happen.
So am wondering what to do if the same happens, or just forget CWM and flash stock recovery.img just to be safe?
I had similar issues after hard power-off [long hold power button]. Confirmed with adb into insecure cwm recovery that /data was corrupt. It explained why my restores stopped at /data.
Cwm data wipe, or format data did not help.
I flashed the stock 3e recovery.img in a tar with odin.
3e data wipe/factory reset. Reflash whole stock firmware with odin.
Check system boots ok.
Reflash cwm, then do restore ok.
I have seen stock 3e recovery fail to start properly. It seemed to be related to files/directories on the external sd card. It came up and said something like 'manual mode', 'updating'.
I tried clearing cache and hidden.
I know I deleted at least tmp_sec_fota directory off the external sd card, maybe someting to do with fota is upsetting our tabs from time to time.
Yep, exactly, that's it, it was "Manual mode" and "Updating", same symptoms, I couldn't get past it.
So what you're saying, I had a MicroSD in it, and that's why it was stuck at this? Not sure if I had an SD in it, but I flashed stock like three times, and then still couldn't enter 3e recovery, all the time had this "manual mode" come up...
Thanks for the guide of what you did.
Am downloading the latest Thai firmware now, to extract the stock recovery, so that I'm ready just in case.
Do you just tar the recovery.img and use that for flashing if necessary? No special permissions, nothing?
Sorry, not as clear cut as that... I did three things, cleared cache, cleared hidden, and
then started deleting files on sd. It is possible the problems are in multiple locations,
It is also possible that multiple attempts have an effect.
I personally feel I need both stock 3e and insecure cwm [and odin and adb] to be able to recover this tab. The broken 3e/reboot was my worst experience on this so far.
Use linux tar or the tab's busybox tar, to create an uncompressed tar with recovery.img as the only file. Do not use 7zip to create the tar, it didn't work for me (although it works fine to extract from the stock).
davp said:
Sorry, not as clear cut as that... I did three things, cleared cache, cleared hidden, and
then started deleting files on sd.
Click to expand...
Click to collapse
You mean you did this in CWM recovery? Because I hastily flashed the stock ROM when it wouldn't boot, and then I couldn't get into the recovery anymore and there was no way to flash CWM recovery from PC Odin, or is there?
SD you mean internal? Since with external you just pull it out...
This was my worst experience as well, and want to be ready if it ever happens again.
So to sum it up. If the /data is messed up, should we do the following?
1. In CWM recovery clear cache, clear hidden.
2. Flash stock e3 recovery.
3. In stock recovery wipe everything.
4. Flash stock ROM.
5. Boot.
6. Flash CWM recovery.
7. Restore backup.
please i have the same problem,where i find the stock e3 recovery?
thanks Davp!
---------- Post added at 03:29 PM ---------- Previous post was at 02:53 PM ----------
please,post a link for download the recovery.img tar for to flash with odin.this is my last hope!
I have soft bricked and then recovered a lot of devices but this one has me stumped. I tried to install a custom kernel that I compiled myself using odin. When that didn't work I tried to copy the image using dd. My theory is that I wrote to the wrong block device and broke something. When it wouldn't boot I figured it was no big deal, I'll just revert to stock. I have tried flashing the stock rom with Odin and by using Kies emergency recovery. Both seem to succeed but whenever I boot I just get stuck at the samsung logo which displays on the screen forever. I can still get into download mode and recovery mode just fine.
Things I have tried:
- Factory reset (I've done this many times from stock recovery and TWRP)
- Cache wipe (Also tried several times from stock recover and TWRP - in TWRP I tried all the different wiping options)
- Flash stock ROM
- Turn off device and wait for more than an hour (since there is no way to do a battery pull)
My understanding is that the bootloader must be functioning otherwise I would not be able to get as far as I do. And since flashing stock ROM doesn't do anything there must be a partition with corrupt data that is not being rewritten when I install the ROM. Any ideas what this might be? Are there any resources I can use to completely repartition the device?
Any ideas are appreciated.
I fixed my problem so I just though I'd post the solution here in case someone finds this on Google or something.
It seems that I did indeed corrupt a partition that is not rewritten when you flash a stock rom or do an emergency system restore with kies (which I believe does nothing more than download the stock rom and then flash it). I actually had to buy a second device and use dd to copy over all the partitions and then returned the second device
So if you have this problem you might have to ask someone on this forum to give you an image of whichever partition you broke.
Phone Info:
Samsung Galaxy s5 (sm-g900p) (Sprint)
Android Version 5.0
Build: LRX21T.G900PVPU1BOA6
Hi, Thank you ahead of time to anyone who might have a minute to help me out. I have been combing XDA and as well as some other sites trying to find a solution myself but given my limited experience in this area Im at the point where I thought it best to stop and ask for help rather than do the wrong thing and have my phone blow up in my hands TNT style
I rooted my s5 a few weeks ago using Odin with C-f--auto-root, which went perfectly and I had zero issues afterwards.. This was only my second rooted device so of course I was exploring all of my new options out there to customize my phone.
The problem occurred after installing the apps Layers Manager and Layers Showcase (BitSyko Development) from the Playstore. Both seem like great apps and were not to blame for this problem, I just happened to be using them when I jacked something up.
Basically, over a day or two I tried several Layers Themes and they applied just fine, but one did not. Shortly after applying the Layer, and rebooting my phone I ended up on the bright Yellow Sprint Spark startup screen and my phone wont budge past this point.
I am able to boot into Recovery Mode as well as Download mode. I tried wiping the cache Partition as i had read to do as well as doing a full data clear and reset ,but it still; wouldnt move past the yellow screen. Then I very carefully followed directions to flash the stock firmware using Odin, making sure i used the right one for this phone and Odin displayed PASS! at the end. From what i could tell, it all went fine... But it STILL wont move past that enraging yellow screen!!
I think I may have missed something in regards to flashing stock firmware but i dont know. Ive read some other suggestions and things to try but, like i said, at this point and with my limited experience, I thought it best to concede and ask the experts for some help.
I hope I included any information needed...
Are you waiting long enough to allow for loading? Did you try installing a stock rom that matches bootloader version?
gdrocks said:
Are you waiting long enough to allow for loading? Did you try installing a stock rom that matches bootloader version?
Click to expand...
Click to collapse
Hi, thank you for your reply. Yes, the stock rom i used matched the original rom on the device. I had taken some screen shots of the Device Info screen a while back for something else, so luckily i had a lot of general info right there shot the s5. And i waited a good amount of time. Odin took a few minutes and it read PASS at the end. From what i could tell, it was all done and i still waited just to be sure. But the more i think about it, the more i feel that i did do something wrong at this step. I'm just not certain what
Amandajbee86 said:
Hi, thank you for your reply. Yes, the stock rom i used matched the original rom on the device. I had taken some screen shots of the Device Info screen a while back for something else, so luckily i had a lot of general info right there shot the s5. And i waited a good amount of time. Odin took a few minutes and it read PASS at the end. From what i could tell, it was all done and i still waited just to be sure. But the more i think about it, the more i feel that i did do something wrong at this step. I'm just not certain what
Click to expand...
Click to collapse
Flash the TWRP recovery in odin
After that enter in recovery mode and format system, data, cache, dalvik cache, sdcards.
Then put the phone into download mode, and flash with odin the last stock rom (OG1) but make sure you don't have selected the "reboot" option in odin
After you got your phone flashed, take the battery out put it again and enter in recovery mode, choose "wipe data/factory reset"
Then put your phone in download mode and flash again the stock rom (OG1) this time with the "reboot" option selected
After you flashed your phone the first boot takes some minutes (in the yellow screen), just be patient.
After this you should have your phone complety clean and your problem solved.
DOWNLOADS
Odin 3.10.7
Stock Rom OG1
TWRP 2.8.7.0
daniel3x said:
Flash the TWRP recovery in odin
After that enter in recovery mode and format system, data, cache, dalvik cache, sdcards.
Then put the phone into download mode, and flash with odin the last stock rom (OG1) but make sure you don't have selected the "reboot" option in odin
After you got your phone flashed, take the battery out put it again and enter in recovery mode, choose "wipe data/factory reset"
Then put your phone in download mode and flash again the stock rom (OG1) this time with the "reboot" option selected
After you flashed your phone the first boot takes some minutes (in the yellow screen), just be patient.
After this you should have your phone complety clean and your problem solved.
Click to expand...
Click to collapse
Thank you so much! I am going to give this a try hopefully tonight, or in the morning if I cant make time tonight. I will report back once I do. Again, thank you so much for taking the time to help me out. It really means a lot! :fingers-crossed:
i had the same problem and tried over 10 other ways to fix it. i finally found this post and it worked! ty so much. was almost ready to throw the phone out
daniel3x said:
Flash the TWRP recovery in odin
After that enter in recovery mode and format system, data, cache, dalvik cache, sdcards.
Then put the phone into download mode, and flash with odin the last stock rom (OG1) but make sure you don't have selected the "reboot" option in odin
After you got your phone flashed, take the battery out put it again and enter in recovery mode, choose "wipe data/factory reset"
Then put your phone in download mode and flash again the stock rom (OG1) this time with the "reboot" option selected
After you flashed your phone the first boot takes some minutes (in the yellow screen), just be patient.
After this you should have your phone complety clean and your problem solved.
DOWNLOADS
Odin 3.10.7
Stock Rom OG1
TWRP 2.8.7.0
Click to expand...
Click to collapse
see, nw this is the type of post i like to see!! @daniel3x , for future reference, idoneapps.com has WAAAAAAY faster downloads then sammobile and the tar.md5 files are 100% legit! But youre reply is pretty much exactly what i would have said. I personally would have advised on OK4 vs OG1. OK4 is just easier to mess with on TWRP and stuff.
wait a while for first stock boot from yellow screen
I've read that flashing a stock firmware will take 10 to 20 or more minutes on your first boot. Let the heat sink from your body and give it time.
I want to flash to a stock as well. Can I just full system wipe in twrp and Odin og1 or ok4>what I'm currently on and would like to keep it? Should I take out my SIM? Should I take out my sd card? Will I need to re partition my ext2/4 on the sd? Does the stock image replace the bootloader? I have a twrp backup on my extsd, can I use it after attempting to flash stock? Flash stock tar/zip should stock be a tar?, Odin kltespr twrp in pda mode, leave everything alone, root method of choice, phh su so flash in twrp, should I update Odin? I have 3.07 and 3.10.6. Then wait out that initial boot. I don't want a backup of what I have now because I've done things I wantedd to revert and do differently this time as I'm not AS clueless
Amandajbee86 said:
Phone Info:
Samsung Galaxy s5 (sm-g900p) (Sprint)
Android Version 5.0
Build: LRX21T.G900PVPU1BOA6
--SNIP--
I hope I included any information needed...
Click to expand...
Click to collapse
Oh, some app permissions can cause a bootloop. Instead of flashing the whole stock rom, you can flash the recoveries through odin.
You can either:
-Flash stock recovery through Odin (BL slot) and perform a factory reset/cache wipe
-Go through TWRP and restore your backup
-Go through TWRP and wipe your cache partitions on ADVANCED WIPE
SAMSUNG S5 SPRINT STOCK RECOVERIES:
mega(DOT)nz/#!bRxE1QRD!1-mAR_T6tvb-83xohTD6Q8uNxW4TdpcqnDT3Uq6s5ms
mega(DOT)nz/#!mEwQCDrS!I8pGn8Wa4TSlCpsazD2_ZOh7t1r9sy5kJZ_ujk6viOY
Bl is the recovery? Odin can't flash a bootloader?
This salvaged my sprint phone
I had to flash back from LineageOS 14.1 to stock rom temporarily to "update profile" so I could make phone calls again after moving the phone to a new line. I tried several different versions of stock rom and flashed via ODIN, but all got stuck on the boot loop. It felt like I had searched endlessly for a solution until I came across this thread. I followed the process (Thank you @daniel3x & @youdoofus) using the stock rom ending in OK4; it worked flawlessly!
If possible, I would like to see this thread "stickied" for Sprint Galaxy S5. It will likely save other users a lot of time.
:good: :victory:
kentc said:
I had to flash back from LineageOS 14.1 to stock rom temporarily to "update profile" so I could make phone calls again after moving the phone to a new line. I tried several different versions of stock rom and flashed via ODIN, but all got stuck on the boot loop. It felt like I had searched endlessly for a solution until I came across this thread. I followed the process (Thank you @daniel3x & @youdoofus) using the stock rom ending in OK4; it worked flawlessly!
If possible, I would like to see this thread "stickied" for Sprint Galaxy S5. It will likely save other users a lot of time.
:good: :victory:
Click to expand...
Click to collapse
glad to help
Hi there, first post on here!
I've bought a nexus 5 off of eBay from some person who tried to root it and failed, thinking it would be an easy matter of restoring it.
However, the standard stock recovery process did not work, and I've encountered a number of issues:
When the device gets to erasing 'cache', it stays there for upwards of half an hour with no results.
With stock recovery flashed, pressing power + volUp immediately makes it erase /data, with no other options given.
It also does not show the stock recovery icon, instead a standing up android figure with a spinning poly in front of it.
Flashing TWRP and booting into recovery, it says 'e' is locked and goes into a boot loop.
Also no options in CWM recovery
I thought I would ask on here because it's out of my league now, I've tried on both windows and mac with no luck and I'm not sure what to try next, maybe just leave it until cache finally erases?
Thanks in advance!
You need to read read and read some more.
Start here:
http://forum.xda-developers.com/google-nexus-5/general/resource-guides-info-threads-linked-read-t2784527
It sounds like the bootloader is locked.
It's almost impossible to brick a nexus.
I've managed to get a version of CWM loaded.
Performing factory reset gives the error that /data cannot be mounted for wiping.
Bootloader is definitely open.
M1kesky said:
I've managed to get a version of CWM loaded.
Performing factory reset gives the error that /data cannot be mounted for wiping.
Bootloader is definitely open.
Click to expand...
Click to collapse
Ok :good:. That means you can install TWRP 3.0.
Try this: flash back to a completely stock MM or LP ROM by manually flashing each partition, inlcuding the userdata.img file. When you have finished flashing all partitions, boot directly to recovery from fastboot mode, perform a factory wipe, and reboot.
I've tried doing that but it just results in the standing up android icon, with power+up leading to it trying to wipe data again. no option to do a factory wipe.
I put TWRP 3.0.0 on just to test and ended up in a worse bootloop, which failed to load TWRP but occasionally got into it and displayed this:
imgur.com/RKyZIJf
Sorry as I am a new user it doesn't let me use links
audit13 said:
Try this: flash back to a completely stock MM or LP ROM by manually flashing each partition, inlcuding the userdata.img file. When you have finished flashing all partitions, boot directly to recovery from fastboot mode, perform a factory wipe, and reboot.
Click to expand...
Click to collapse
Thanks, I gave it another try and did the recovery partition last, and made sure I manually put it into recovery mode from bootloader.
The red triangle and recovery menu are back, I can't thank you enough!
Glad you got it to work. I suggest using TWRP 2.8.7.1. For some reason version 3.0 does not work properly with all N5 phones.
It's still happening.
I've been away for a few days so only had the chance to respond now.
I got into the ususal recovery screen as mentioned previously and tried to do a factory reset, but it had problems with /data again.
I left it the entire night while I slept and it was still saying formatting /data in the morning, nothing had changed.
Anybody got any more suggestions? It's also back to the android with the rotating poly instead of the android with the exclamation mark.
EDIT: when flashing userdata, no matter what version of android I try, it always hangs.
It started on 6.0.1 if that helps.
The userdata.img file is included with each stock rom. I advise against mixing userdata.img files from different stock ROMs.
Sorry, I mean that I've flashed completely whole different versions of android and the result is the same across all of them, not that I've used different userdata img's on the same version of android.
Could be an emmc problem which would require a motherboard swap.
Is that likely to happen when the previous owner said it was fine before they tried to root?
Hi, i just got my old 5 year old (now retired) device to bootup because someone had made a kernel for the device which supports overclocking so for the fun I wanted to try it
but there was one weird problem, it seemed that though the root permissions from years ago remained just like they were but magisk manager itself had lost root permissions though I was still able to grant root permissions to other applications normally
I was on an unofficial Lineage OS build and thought of returning to original Miui for the device, got the fastboot rom, got Mi flash, flashed it, booted up
but there was a catch, it would always throw an error on the login Miui account screen at startup saying "Couldn't check device security, please try again"
I had tried everything possible including:
adding a Xiaomi account
skipping sign in
Inserting a sim
None of them seemed to do anything so i flashed twrp recovery again as using mi flash to flash ur device's stock rom gets rid of custom recovery
Now here is the mistake I made
**I wiped the device clean using TWRP**
now i tried going into adb sideload mode, no matter what I did my PC wouldn't detect my device, tried going into fastboot mode and still my PC wouldn't recognise the device and same goes for Mi flash tool
additionally the device would automatically exit out of fastboot mode within 2 minutes and go on to the power off screen
I do have charge on the device it says it's at 87% on the TWRP menu
I can no longer bootup, im stuck at the MI logo on bootup
Device: Mi Max 2
Additional notes: I am not in a hurry as that is not my primary device so it is okay if you want to take your time to reply, even if there's no way i can get my phone to see the light of day again it's alright as the phone was retired and sitting collecting dust for 2 years now
I do not wish to visit a service center as it's not worth it for a device I'm just gonna use for a few hours then put it back into its grave again
just download that same, or another custom ROM, and flash it via TWRP (just put ROM in SD card).
Nothing is gone, i mean if you delete system via twrp of course it will bootloop as it don't have system.
And for reverting back to original stock ROM , i think it have to do something with encryption, or maybe just the fact you unlocked bootloader.
Best is to stay away from stock ROM, find some custom ROM which have similar to MIUI (stock rom) , somewhat improved, if you want to get as much stock ROM experience.
kraken-gz said:
just download that same, or another custom ROM, and flash it via TWRP (just put ROM in SD card).
Nothing is gone, i mean if you delete system via twrp of course it will bootloop as it don't have system.
And for reverting back to original stock ROM , i think it have to do something with encryption, or maybe just the fact you unlocked bootloader.
Best is to stay away from stock ROM, find some custom ROM which have similar to MIUI (stock rom) , somewhat improved, if you want to get as much stock ROM experience.
Click to expand...
Click to collapse
Hi, thanks for the reply, I tried using an SD card and unfortunately it wouldn't detect that too, what i found was I didn't wipe System it still shows that it's taking up some place (3597 MB)
i would be fine getting a custom rom on the device infact i have crdroid ready to be installed
could it be that the TWRP i installed (yes I downloaded the latest version and didn't flash the old one i had years ago) have some bugs? (I did install it from official TWRP website)
also note: though you see a Senior Member title below my name, im a complete and utter noob
BR4UTAL said:
Hi, thanks for the reply, I tried using an SD card and unfortunately it wouldn't detect that too, what i found was I didn't wipe System it still shows that it's taking up some place (3597 MB)
i would be fine getting a custom rom on the device infact i have crdroid ready to be installed
could it be that the TWRP i installed (yes I downloaded the latest version and didn't flash the old one i had years ago) have some bugs? (I did install it from official TWRP website)
also note: though you see a Senior Member title below my name, im a complete and utter noob
Click to expand...
Click to collapse
Lol I thought I was the only proper noob here on xda but nice to meet other noobs here too .
I think Kraken-gz is right, once the older devices are OEM off-support its best to stay away from OEM servers, I lost couple of old lesser-known-brand devices to OEM mischief i'd say coz it happened twice to me when I reloaded the original ROMs and tried to connected to the net they went dead on the next bootup, I think the OEMs have something going on there to boot out the older devices so newer ones could be pushed in the market sooner than they were supposed to. Possible.
so, first, in twrp, try to completely format it, follow this to do it
Just, a note: in advanced wipe delete system, data, dalvik cache and cache.
When trying to reboot into system, make sure twrp complains that it have no system. (that way, you know you deleted it)
reboot it, again in twrp.
try to flash custom ROM, should work as it have clean memory.
If it doesnt flash, then make sure to note all log file from twrp while flashing, and post it here, in order to see, what failed in flashing. If it succeds, it should load custom rom . If custom rom dont work, try another one, maybe older, or one that you had previous time (before trying to go into stock rom) (just, to try to boot it somehow. But before trying another custom rom, if one fails, do proper wiping described above.
If that fails try to download oldest stock ROM, and flash it. Maybe newest is blocking it.
If that fails, there is something called EDL mode, when fastboot is not available (for hard brick, like this).
here is video just to give you overview how to do it
and text also
Edit:
WAIT, try to format it, without wiping system. maybe it will boot again.
If not, other solutions are not applicable, if you dont find way to detect that sd card. Only EDL remains.
kraken-gz said:
so, first, in twrp, try to completely format it, follow this to do it
Just, a note: in advanced wipe delete system, data, dalvik cache and cache.
When trying to reboot into system, make sure twrp complains that it have no system. (that way, you know you deleted it)
reboot it, again in twrp.
try to flash custom ROM, should work as it have clean memory.
If it doesnt flash, then make sure to note all log file from twrp while flashing, and post it here, in order to see, what failed in flashing. If it succeds, it should load custom rom . If custom rom dont work, try another one, maybe older, or one that you had previous time (before trying to go into stock rom) (just, to try to boot it somehow. But before trying another custom rom, if one fails, do proper wiping described above.
If that fails try to download oldest stock ROM, and flash it. Maybe newest is blocking it.
If that fails, there is something called EDL mode, when fastboot is not available (for hard brick, like this).
here is video just to give you overview how to do it
and text also
Edit:
WAIT, try to format it, without wiping system. maybe it will boot again.
If not, other solutions are not applicable, if you dont find way to detect that sd card. Only EDL remains.
Click to expand...
Click to collapse
Tried wiping data, cache and dalvik cache and formatting data, none seemed to help
and still no sd card being detected
Now edl mode
I would love to boot into edl mode but the thing is my device isn't being recognised by adb nor is it being recognised by fastboot commands
so that's where I'm stuck for now
OldNoobOne said:
Lol I thought I was the only proper noob here on xda but nice to meet other noobs here too .
I think Kraken-gz is right, once the older devices are OEM off-support its best to stay away from OEM servers, I lost couple of old lesser-known-brand devices to OEM mischief i'd say coz it happened twice to me when I reloaded the original ROMs and tried to connected to the net they went dead on the next bootup, I think the OEMs have something going on there to boot out the older devices so newer ones could be pushed in the market sooner than they were supposed to. Possible.
Click to expand...
Click to collapse
Perhaps that is true