Develop Bugs

Problems flashing, need help please!!!

Ok, so here is what I have done: I have already rooted my phone, etc, and have flashed some different roms on my phone, and have not had any problems until now. I recently tried the miui rom, but didn't like it.I just flashed the newest miui rom, and it was acting really weird, so I decided to go back to the virtuous rom which I had used before. For whatever reason, I am getting this error: E: can't mount /dev/block/mmcblk0p1 (file exists), and the installation aborts. I did the wipe data deal, and I also tried to reinstall the miui rom. It says that installs fine, but it won't get past the htc incredible screen. Any suggestions? Also, I didn't want to try this and mess things up further, but can I restore a backup I had done when I had the virtuous rom installed, or do I have to have the rom already working properly? Kind of a noob question, I know.

calamari85 said:
Ok, so here is what I have done: I have already rooted my phone, etc, and have flashed some different roms on my phone, and have not had any problems until now. I recently tried the miui rom, but didn't like it.I just flashed the newest miui rom, and it was acting really weird, so I decided to go back to the virtuous rom which I had used before. For whatever reason, I am getting this error: E: can't mount /dev/block/mmcblk0p1 (file exists), and the installation aborts. I did the wipe data deal, and I also tried to reinstall the miui rom. It says that installs fine, but it won't get past the htc incredible screen. Any suggestions?
Click to expand...
Click to collapse
Hmmm... Do you have any Nandroids from earlier roms? That'd be the easiest route.
If not, since you can't even get to a homescreen, you might try an RUU reset, but let's hope it won't come to that for now.
I get that too, but only when going into the menu for Dalvik Cache wiping, and it never actually gets in my way, it just pops up and then I can keep going on about my business.

1. yes you can restore the backup whether a rom is currently working or not
2. post questions in the correct forum

If you can't get a nandroid backup to work, you may have to RUU back to stock.
Here's the older one that will still let you use unrevoked after. Just rename this PB31IMG.zip, load up H-boot, follow the prompts, and be patient. Then run unrevoked when it finishes and install rom manager to restore your backup. If the backup still won't work, try a fresh install of virtuous.

Sorry
g00s3y said:
1. yes you can restore the backup whether a rom is currently working or not
2. post questions in the correct forum
Click to expand...
Click to collapse
My apologies, where should I have posted? And can I move the thread so it is in the correct place?

calamari85 said:
My apologies, where should I have posted? And can I move the thread so it is in the correct place?
Click to expand...
Click to collapse
Probably in the Q & A General Forum, but don't worry about it this time, just as long as it doesn't end up being a frequent thing.
But I don't know about being able to move the thread, I think that's a Moderator power.
Regarding your issue though, either use the RUU link posted above, or try Nandroid-ing back.

No go
I tried restoring a backup, and got cannot mount /data, along with the previous error... It changed my boot animation, but has not restored my phone. should I do this RUU back to stock? Sorry for not being very good at this, and I definitely appreciate the help.

calamari85 said:
I tried restoring a backup, and got cannot mount /data, along with the previous error... It changed my boot animation, but has not restored my phone. should I do this RUU back to stock? Sorry for not being very good at this, and I definitely appreciate the help.
Click to expand...
Click to collapse
It's cool.
Yes, you'll need it on the root of your SD-card (not in any folders), run it through hboot, and then you'll have to re-run the unrEVOked tool from your PC. I would also suggest running the S-Off tool afterwards, just to be safe. That has saved me once before.
Make sure you have at least 50% battery before you do the hboot flash. VERY IMPORTANT. If your phone dies or loses power while updating the radio files from the RUU, your phone is as good as bricked.
If you get stuck with the unrEVOked tool at waiting for root for more than fifteen minutes, post back here again and we'll continue from there.
EDIT: Actually, run the unrEVOked Forever S-Off tool through CWM recovery before doing this, as a pure precautionary measure.

I'm an idiot apparently
Well, I am really sorry guys, I won't ask any more questions on here. Apparently I am super stupid. I figured it out, I left out some info because it didn't even register as relevant, but it was the key apparently. So I just go a new sd card, and I formated it on my computer, and just dropped the zip files on there, and was trying to flash like that, and apparently the phone didn't like the new sd card, or it needed info off the old one, because once I put it back in and tried flashing from it, it works fine now. Sorry for bothering everyone, I am going to go sit in the corner in shame now.

calamari85 said:
Well, I am really sorry guys, I won't ask any more questions on here. Apparently I am super stupid. I figured it out, I left out some info because it didn't even register as relevant, but it was the key apparently. So I just go a new sd card, and I formated it on my computer, and just dropped the zip files on there, and was trying to flash like that, and apparently the phone didn't like the new sd card, or it needed info off the old one, because once I put it back in and tried flashing from it, it works fine now. Sorry for bothering everyone, I am going to go sit in the corner in shame now.
Click to expand...
Click to collapse
Hahaha! No worries, we all have our moments!

Glad you figured it out. Be sure to make a backup of your current rom on your new SD card right away haha.

I need help!!!!!

i downloaded an app to change the battery icon (i can't recall the exact app). it automatically reboots the phone to make the changes, but when it rebooted it got stuck at the startup screen where is says "Galaxy S" and it does the little vibration like when an app forcecloses.
Anyone know what i can do to fix my phone? i am on a rooted samsung epic 4g

Well you say you are rooted but do you have cwm installed?

musclehead84 said:
Well you say you are rooted but do you have cwm installed?
Click to expand...
Click to collapse
yes i do have Clockwork mod

That app, I believe, is used to grab specific versions of the mod for specific phones with specifc ROMs. Unless you're running the rom required, it will lock the phone like that. You will have to restore a backup through clockwork, you did make one I hope, or adb push the original file back...otherwise its time to wipe and reload.

camarojones said:
That app, I believe, is used to grab specific versions of the mod for specific phones with specifc ROMs. Unless you're running the rom required, it will lock the phone like that. You will have to restore a backup through clockwork, you did make one I hope, or adb push the original file back...otherwise its time to wipe and reload.
Click to expand...
Click to collapse
yeah i made a backup, i went into recovery mode and tried to restore but it just did the exact same thing as before!!!! i also tried to factory reset and it still does the same thing i am completely baffled.

mvelasquez21 said:
yeah i made a backup, i went into recovery mode and tried to restore but it just did the exact same thing as before!!!! i also tried to factory reset and it still does the same thing i am completely baffled.
Click to expand...
Click to collapse
I've had the battery mod cause me headaches before. CWM restores won't work, you'll need to Odin to revert back. Something to do with where the battery mod files write to.

Electrofreak said:
I've had the battery mod cause me headaches before. CWM restores won't work, you'll need to Odin to revert back. Something to do with where the battery mod files write to.
Click to expand...
Click to collapse
thanks for your help everyone... does anyone know where the link is on how to use odin? i have never used that before

http://forum.xda-developers.com/wiki/index.php?title=Samsung_Galaxy_S/SPH-D700#Odin_Stock_Flashing
I updated that wiki myself about a month ago, so all the links should work and everything should be accurate. Let me know if there are any issues with the wiki or ways it could be improved.

Electrofreak said:
http://forum.xda-developers.com/wiki/index.php?title=Samsung_Galaxy_S/SPH-D700#Odin_Stock_Flashing
I updated that wiki myself about a month ago, so all the links should work and everything should be accurate. Let me know if there are any issues with the wiki or ways it could be improved.
Click to expand...
Click to collapse
ok that worked great i appreciate the help. now back to square one with rooting the phone and adding clockwork lol

Random Shutoff after custom rom, now No messaging after flashing to stock.

Hey there everyone,
I am honestly at a bit of a loss.
I have an AT&T GS3, and I noticed that all the bloatware was SERIOUSLY draining the battery and hogging up RAM, so I thought it would be a great idea to get a custom rom to enhance my phone.
I used the GS3 Toolkit to flash TWRP recovery. - All went well
I read up on some different Roms, and i chose to install http://forum.xda-developers.com/showthread.php?t=2089821
I installed RLS16
I followed the instructions,
Wipe data/factory reset
Wipe dalvik cache
Wipe /system
I went through the Aroma installer and chose to install the Developer's Pick.
This includes a bunch of little addons like 4.2 camera, gallery, keyboard, etc.
but it also installs lean kernel.
The install went fine, nothing said it failed
but once i was in the rom. Things got terrible.
My phone randomly crashed and shut off, like within minutes each time, camera would crash the phone, causing it to shut off, etc.
So i went through the GS3 toolkit, downloaded and reflashed the stock Rom and recovery.
Once it booted, I keep getting "Unfortunately Messaging has Stopped" and I cannot receive or send text messages, even through other texting programs like Handcent SMS.
No matter what, it keeps crashing (the messaging, not the rom). I factory reset, wiped, everything. Nothing will fix it.
I thought that maybe the stock rom doesnt include stock kernel? So i went online, downloaded the stock kernel, flashed, reflashed stock rom, and STILL the same thing. Messaging has stopped working.
Also as a side note, when i tried to do a google voice search. I get a page saying Sorry and that my computer or phone might be sending network requests or something along those lines.
I cannot think of anything else I can do....
If anyone has any idea, please let me know...
Thanks!

eternalcold said:
Hey there everyone,
I am honestly at a bit of a loss.
I have an AT&T GS3, and I noticed that all the bloatware was SERIOUSLY draining the battery and hogging up RAM, so I thought it would be a great idea to get a custom rom to enhance my phone.
I used the GS3 Toolkit to flash TWRP recovery. - All went well
I read up on some different Roms, and i chose to install http://forum.xda-developers.com/showthread.php?t=2089821
I installed RLS16
I followed the instructions,
Wipe data/factory reset
Wipe dalvik cache
Wipe /system
I went through the Aroma installer and chose to install the Developer's Pick.
This includes a bunch of little addons like 4.2 camera, gallery, keyboard, etc.
but it also installs lean kernel.
The install went fine, nothing said it failed
but once i was in the rom. Things got terrible.
My phone randomly crashed and shut off, like within minutes each time, camera would crash the phone, causing it to shut off, etc.
So i went through the GS3 toolkit, downloaded and reflashed the stock Rom and recovery.
Once it booted, I keep getting "Unfortunately Messaging has Stopped" and I cannot receive or send text messages, even through other texting programs like Handcent SMS.
No matter what, it keeps crashing (the messaging, not the rom). I factory reset, wiped, everything. Nothing will fix it.
I thought that maybe the stock rom doesnt include stock kernel? So i went online, downloaded the stock kernel, flashed, reflashed stock rom, and STILL the same thing. Messaging has stopped working.
Also as a side note, when i tried to do a google voice search. I get a page saying Sorry and that my computer or phone might be sending network requests or something along those lines.
I cannot think of anything else I can do....
If anyone has any idea, please let me know...
Thanks!
Click to expand...
Click to collapse
When you flashed stock, did you flash the one for your carrier? (It should flash the kernel at the same time)
Did you try clearing the messaging app's data/cache?
Did you try flashing another custom ROM to see if you still get the errors? If not, could give 4.2.1 a shot.

BWolf56 said:
When you flashed stock, did you flash the one for your carrier? (It should flash the kernel at the same time)
Did you try clearing the messaging app's data/cache?
Did you try flashing another custom ROM to see if you still get the errors? If not, could give 4.2.1 a shot.
Click to expand...
Click to collapse
Yeah i flashed the one for my carrier. And i figured it would do the kernel, but just in case i tried flashing it separately....
and yeah i did try wiping the data/cache, but i will try it again.
and I could always try flashing another custom rom. Do you have any suggestions? i just want one that works quickly, is stable, and has messaging lol

eternalcold said:
Yeah i flashed the one for my carrier. And i figured it would do the kernel, but just in case i tried flashing it separately....
and yeah i did try wiping the data/cache, but i will try it again.
and I could always try flashing another custom rom. Do you have any suggestions? i just want one that works quickly, is stable, and has messaging lol
Click to expand...
Click to collapse
Look in my sig I don't give suggestion per say cause it's up to the user's preference but I'll always be running something that works.

BWolf56 said:
Look in my sig I don't give suggestion per say cause it's up to the user's preference but I'll always be running something that works.
Click to expand...
Click to collapse
I might try that one out. I was looking at some reviews, someone said there may be Bluetooth issues. I just bought the Moga, and i need BT to work perfecty...
Any input on that?

eternalcold said:
I might try that one out. I was looking at some reviews, someone said there may be Bluetooth issues. I just bought the Moga, and i need BT to work perfecty...
Any input on that?
Click to expand...
Click to collapse
Best thing to do is to read changelogs but for now I'll give you the answer, it has been fixed a few releases ago in Task650's AOKP.

BWolf56 said:
Best thing to do is to read changelogs but for now I'll give you the answer, it has been fixed a few releases ago in Task650's AOKP.
Click to expand...
Click to collapse
Alright, i'll flash that one, i'll post to here when it's finished. Thanks!

Did you check your IMEI?

xBeerdroiDx said:
Did you check your IMEI?
Click to expand...
Click to collapse
Just checked, my IMEI is there.
Also, i found this thread
http://forum.xda-developers.com/showthread.php?t=1804782
but their images wont show. Any idea what route they are taking to solve this??

eternalcold said:
Just checked, my IMEI is there.
Also, i found this thread
http://forum.xda-developers.com/showthread.php?t=1804782
but their images wont show. Any idea what route they are taking to solve this??
Click to expand...
Click to collapse
That guy flashed the bootloaders. I'm not sure what the pictures are supposed to be but they don't seem to lead to anything.
My take on it: Don't play with bootloaders, it's the only way to really brick your phone (if something goes wrong that is).

BWolf56 said:
That guy flashed the bootloaders. I'm not sure what the pictures are supposed to be but they don't seem to lead to anything.
My take on it: Don't play with bootloaders, it's the only way to really brick your phone (if something goes wrong that is).
Click to expand...
Click to collapse
Understood, I wont mess with them.
I really just want to understand a couple things.
1. Why did the ROM I installed before work for everyone else except me? and i followed the instructions.
and 2. after flashing to stock, how am I unable to fix this?
mainly to just learn what went wrong.

Sometimes the reason just...you had a bad flash or something broke down in there. I did the CF easy root method and flashed TWRP in goo manager and then started flashing. I've never tried the toolkit but like anything many times it just depends on the download you got or a bad flash. We've all had several...just hate when it involves rooting or using ODIN.

hednik said:
Sometimes the reason just...you had a bad flash or something broke down in there. I did the CF easy root method and flashed TWRP in goo manager and then started flashing. I've never tried the toolkit but like anything many times it just depends on the download you got or a bad flash. We've all had several...just hate when it involves rooting or using ODIN.
Click to expand...
Click to collapse
Thanks,
Is there any way to repair it?

Alright, so....
I think i have figured out what the issue was. Or by random chance got it fixed.
I was going to try to install the Synergy Rom. And while going through the custom setup, i noticed "Install AOSP Messaging" and "Install TW Messaging"
I chose the TW messaging, and went through the rest of the installer.
For some reason i kept hanging at the "Samsung Galaxy S3" logo, and it would not boot.
(Honestly, i've used custom roms since the HTC Touch Pro 2, and i've NEVER had such issues. And i personally think the TP2 was way more difficult lol)
So I ONCE AGAIN flashed to stock. and randomly the messaging works!
I only can guess that even when flashing the stock rom, it doesnt change something regarding the messaging app. I'm not sure. All i know is that i'm on stock again and everything is working. I highly doubt i'm going to try another custom rom for a while until i have a full understanding of what happened.
But in case anyone else was having this problem, i hope this helped.

[Q] Big Problem after Jeally Bean Update on Xperia S

Hi Guys,
I'm from India and I updated my Xperia S[LT26i] to JB 4.1.2 a week ago via Sony Update Service. The build no. is 6.2.B.0.211.
The phone was working PERFECTLY till today. It was a joy using the phone and suddenly today morning, the phone rebooted, all the apps and games and tweaks that I'd installed on my phone were gone. The language had automatically changed to Bosnian . All the wifi-passwords were gone. It was as if it restored to factory settings, without my permission in an alien language. I tried rebooting my device several times but to no avail. ALSO, all the data on my internal memory card is lost!!! :'(
There was a lot of important data, photos and files! ALL GONE!
What could be the reason for this happening? Is there anyway I can restore it to its previous glory as it was very tedious and took me weeks to customise it exactly as I wanted it.
Any help will be much appreciated.
Thank you.
P.S. - My phone was rooted before the updated, but it was automatically unrooted after the update to JB.

akaash_dudwani said:
Hi Guys,
I'm from India and I updated my Xperia S[LT26i] to JB 4.1.2 a week ago via Sony Update Service. The build no. is 6.2.B.0.211.
The phone was working PERFECTLY till today. It was a joy using the phone and suddenly today morning, the phone rebooted, all the apps and games and tweaks that I'd installed on my phone were gone. The language had automatically changed to Bosnian . All the wifi-passwords were gone. It was as if it restored to factory settings, without my permission in an alien language. I tried rebooting my device several times but to no avail. ALSO, all the data on my internal memory card is lost!!! :'(
There was a lot of important data, photos and files! ALL GONE!
What could be the reason for this happening? Is there anyway I can restore it to its previous glory as it was very tedious and took me weeks to customise it exactly as I wanted it.
Any help will be much appreciated.
Thank you.
P.S. - My phone was rooted before the updated, but it was automatically unrooted after the update to JB.
Click to expand...
Click to collapse
Settings once lost are lost , thats why everyone recommend to take a Nandroid backup of ROM.
if anything of "this" sort happen, you can just restore the backup and nothing is lost.
But your case is weird bro !!

Captain Droid said:
Settings once lost are lost , thats why everyone recommend to take a Nandroid backup of ROM.
if anything of "this" sort happen, you can just restore the backup and nothing is lost.
But your case is weird bro !!
Click to expand...
Click to collapse
It's really weird. And BOSNIAN?! I thought my phone was hacked or something. I have the recovery softwares to recover data, I just hope it works on cellphones since I've never tried it before. What I wanna know is, if it's a recognised bug or is something wrong particularly with my phone.

akaash_dudwani said:
It's really weird. And BOSNIAN?! I thought my phone was hacked or something. I have the recovery softwares to recover data, I just hope it works on cellphones since I've never tried it before. What I wanna know is, if it's a recognised bug or is something wrong particularly with my phone.
Click to expand...
Click to collapse
I suggest you reflash the ROM. then use DooMLoRD Easy Rooting Toolkit
Read the instructions carefully
Then Install recovery to take backup.
If this problem happens again, reflash to some stock based custom ROM which is more stable..

Captain Droid said:
I suggest you reflash the ROM. then use DooMLoRD Easy Rooting Toolkit
Read the instructions carefully
Then Install recovery to take backup.
If this problem happens again, reflash to some stock based custom ROM which is more stable..
Click to expand...
Click to collapse
I am using official JB from Sony, wouldn't it be easier if I just installed everything like and customise and then take backup instead of flashing the ROM with an unofficial one?

akaash_dudwani said:
I am using official JB from Sony, wouldn't it be easier if I just installed everything like and customise and then take backup instead of flashing the ROM with an unofficial one?
Click to expand...
Click to collapse
if dont want unofficial , then flash the stock jb.( the rom u using now, flash it again, clean install)
All your settings gone ,right?
try this if you dont wanna flash,
skip the flash , use the rooting kit then install all your tweaks, customizations etc then take a recovery backup. :fingers-crossed:

Captain Droid said:
Yes bro that too can be done. Now you are on JB right , but all your settings gone ,right?
skip the flash , use the rooting kit then install all your tweaks, customizations etc then take a recovery backup. :fingers-crossed:
like you said
Click to expand...
Click to collapse
I shall do that. In the meanwhile if someone else comes up with an explanation as to why something like this could happen, your thoughts are more than welcome.

Captain Droid said:
if dont want unofficial , then flash the stock jb.( the rom u using now, flash it again, clean install)
All your settings gone ,right?
try this if you dont wanna flash,
skip the flash , use the rooting kit then install all your tweaks, customizations etc then take a recovery backup. :fingers-crossed:
Click to expand...
Click to collapse
So, I can't recover the files because the phone is attached as portable media player to my laptop. Recovery works only if I attach it as Mass Storage Drive. Any idea how I can do that? I remember this feature was present in Gingerbread, but never saw it since ICS.

akaash_dudwani said:
So, I can't recover the files because the phone is attached as portable media player to my laptop. Recovery works only if I attach it as Mass Storage Drive. Any idea how I can do that? I remember this feature was present in Gingerbread, but never saw it since ICS.
Click to expand...
Click to collapse
Did u try enabling USB Debugging mode

Captain Droid said:
Did u try enabling USB Debugging mode
Click to expand...
Click to collapse
Yes. I rooted the device as well successfully.
The phone connects to the computer as portable media device giving me access to the files but its not quite same as the Mass Storage Device.
Tried certain apps as well but nothing would work. I want to mount my phone as MSD, like a pen drive or an extrernal HDD.

Try go asetting, app, the clear data for the album and walkman app to get back all Yr picture and music. Then the rest is slowly install back
Sent from my Nexus 7 using Tapatalk 2

Constant Rebooting

So my friends Boss' son tried to be all "l33t h4x3r" and mess with his S6(sm-g920p). First he ruined his EFS section of the phone, the Baseband is Unknown, no IMEI number, Software Version is Unknown, and his radio wasn't working. I think he then tried to do some crazy **** in ODIN, "No Clue he doesn't remember". Well i've never ran into a constant reboot issue with any Android phones i've owned. I've had bootloops but this is throwing me for a loop. I've tried:
Loading TWRP wiping everything and trying a Custom ROM
Using Odin to Recover back to Stock
Honestly im not sure whats up anymore or if his phone is even fixable at this time.
Link to Probs: http5://youtu.be/QVLgYF_7tGU

Hi, you certainly have a challenge there. It sounds like you need to restore both the partitions and the stock OS.
If the phone is a 32 GB model, please see the whole thread at http://forum.xda-developers.com/sprint-galaxy-s6/help/operating-smg920p-t3263325
There is a PIT file linked at post 16, instructions for using it at post 22. Also a link for the latest stock TAR file.
Again, this would be for 32 GB model, but you want to flash first the PIT and then the TAR.

I think I may have done that already too but I'll look again once in home and see if maybe I did it in the wrong order. Thanks for the quick reply friend. ?

Well i did as instructed but Baseband is still unknown and it is still rebooting over and over :/

jbowman21 said:
Well i did as instructed but Baseband is still unknown and it is still rebooting over and over :/
Click to expand...
Click to collapse
If he messed up the efs partition, like it's empty, without a backup. I'm pretty sure the phone is done.
Sent from my SM-G900P using Tapatalk

elesbb said:
If he messed up the efs partition, like it's empty, without a backup. I'm pretty sure the phone is done.
Sent from my SM-G900P using Tapatalk
Click to expand...
Click to collapse
I recommend he brings it to Sprint, after they "diagnose" it and declear its broken they should be able to replace it. Just make sure its as close to stock as possible that way it does not seem rooted.

1619415 said:
I recommend he brings it to Sprint, after they "diagnose" it and declear its broken they should be able to replace it. Just make sure its as close to stock as possible that way it does not seem rooted.
Click to expand...
Click to collapse
That is about the only option left. There are other options to restore the efs (pretty much rebuild it from scratch) but that is not something an every day user can do. I had an efs issue on my S4. I was tinkering with things I shouldn't have, forget exactly what I was doing, it was on T-Mobile so I think I was trying to remove the data cap (was on prepaid). Was pretty much in the same boat as OP but was able to completely from scratch rebuild the stuff that belongs in the efs directory. Some stuff I never restored but didn't seem to affect the device.

elesbb said:
That is about the only option left. There are other options to restore the efs (pretty much rebuild it from scratch) but that is not something an every day user can do. I had an efs issue on my S4. I was tinkering with things I shouldn't have, forget exactly what I was doing, it was on T-Mobile so I think I was trying to remove the data cap (was on prepaid). Was pretty much in the same boat as OP but was able to completely from scratch rebuild the stuff that belongs in the efs directory. Some stuff I never restored but didn't seem to affect the device.
Click to expand...
Click to collapse
Huh, if you remember, write a guide that way you can help people.

1619415 said:
Huh, if you remember, write a guide that way you can help people.
Click to expand...
Click to collapse
This was many many years ago. What saved me was the fact that Notepad++ keeps a copy of the file you have open even when you close the program. I just had to remember what things needed to be reverted back and the edits undone. I guess I didn't really rebuild it from scratch lol.

elesbb said:
This was many many years ago. What saved me was the fact that Notepad++ keeps a copy of the file you have open even when you close the program. I just had to remember what things needed to be reverted back and the edits undone. I guess I didn't really rebuild it from scratch lol.
Click to expand...
Click to collapse
Lol

1619415 said:
Lol
Click to expand...
Click to collapse
Yeah sadly I have no idea how the efs is populated. The second instance I get a new phone, dd is done on the efs partition and created into a .img file.

jbowman21 said:
So my friends Boss' son tried to be all "l33t h4x3r" and mess with his S6(sm-g920p). First he ruined his EFS section of the phone, the Baseband is Unknown, no IMEI number, Software Version is Unknown, and his radio wasn't working. I think he then tried to do some crazy **** in ODIN, "No Clue he doesn't remember". Well i've never ran into a constant reboot issue with any Android phones i've owned. I've had bootloops but this is throwing me for a loop. I've tried:
Loading TWRP wiping everything and trying a Custom ROM
Using Odin to Recover back to Stock
Honestly im not sure whats up anymore or if his phone is even fixable at this time.
Link to Probs: http5://youtu.be/QVLgYF_7tGU
Click to expand...
Click to collapse
Koop's firmware didn't work with my phone either. This version of it fixed mine for some reason. Try flashing it to yours
mediafire.com/download/c55xaeb7geq0i2d/G920PVPU3BOJ7_G920PSPT3BOJ7_SPR.zip

Now i got same issue i accidently restored efs and ah man ive tried every thing it reboots after 2 or 3 mins no matter what rom back up i have and i have efs and radio with all my back ups ive restored it also no luck. Guess im going to the sprint store tomorrow even after i flashed stock 6.0.1 i can get to about half way through wifi setup before it reboots no matter what 2-3 minutes phone reboots unless in twrp

Still no luck becareful and dont try to restore efs i suppose in twrp. Your phone may never stop rebooting ive flashed 2 different 6.0.1 builds one was the revo other was from sammobil both @koop1955 has them PB6 6.0.1 odin doesnt fix this.

YOYOYO
Well wtf or omg it completely died left it for a day. Now its working so far it hasnt rebooted in 30 mins LOL but dude sucks going to a phone with kitkat after using marshmallow and one of the fastest phones made for awhile. I did pull the sim card out and try it in a old boost maybe that reset something idk its working though.My problems were Rebooting constantly after 2-3 mins no matter what rom i had even stock.
---------- Post added at 12:31 PM ---------- Previous post was at 12:11 PM ----------
Saafir said:
Backed up my EFS before ever even rooting. Stuck that bad boy in Dropbox for safety. *pats self on back*
Last one of these topics I seen, end result was JTAG.
Click to expand...
Click to collapse
BEcareful if u restore that efs. i backed up too but once in twrp. Now all i did was check restore efs by accident just tried restoring a renegade rom system,boot, and data. Tell you what i wont be rushing through crap and am fine with stock for awhile. Probably will still take the replacement when it comes its white the black one i got is too blue.

Saafir said:
I've got a raw partition backup as well as one through TWRP. If you check md5/sha hashes for data integrity, and only install software instances specific to your device, aside from manually monkeyin around
Hey needless to say im researching full partition backups did you use a app by wanam partitions back up and restore? Or just simple adb commands. Last used adb on a moto e 2nd with success on unlocking. Once i got a new harddrive haven't needed it.
Click to expand...
Click to collapse

Theres similar issues happening on sprint note 5s as well and has a couple threads currently speaking about this problem. Strange strange. It happened to me after updating to mm and then rooting.

Well i did try the note rom right before and when i did hit restore efs it after wiping system data boot from moar MM rom phone rebooted for days then after few resets and odin flashes i let it die then a day later it worked.

Correct but have always preferred the 925p roms.

Well i helped another with the rebooting issue on any rom.
He tried everything then but let it die after battery died plug it in and bingo his worked to
IF CONSTANT REBOOTING.
LET THE BATTERY COMPLETLY DRAIN.
AFTER FLASHING STOCK.