So about a month ago...I was messing with my Photon and "long story short", formatted my PDS Partition. I thought the menu I was in was for formatting my external SD card...but I formatted the Internal SD storage.
The PDS partition holds various information about your photon, some of it only unique to each phone. And if you delete it, the only real problem that arises is that you cannot update your Profile or your PRL. A good indication that the problem is with your PDS is that if you ##786#, under HW Version it will say "Unavailable".
Now a few people had the same problem in these forums, and its taken about a month to finally figure it out. Plancy, another member here actually deserves most of the credit in leading to a fix.
Over in the Atrix forums, people were having issues that required PDS recovery and some cool ass dudes over there came up with a fix....and whats awesome is that you can directly flash this file to restore your Photon PDS partition.
I am not sure if these steps are all needed but this is what I did to fix my phone...
1. RSD'd to 1FF-sunfire-user-2.3.4-4.5.1A-1_SUN-154_5-CM-release-keys-signed-Sprint-US
2. Performed a Factory Reset.
3. Updated the Motorola Software to 45.3.6
4. Rooted
5. RSD'd derpunlock.sbf to unlock
6. In this thread - http://forum.xda-developers.com/showthread.php?t=1131649
I downloaded the gingerbread (*_v8) version of the fix.
7. Using "Method 2" I placed the image in the folder that FASTBOOT is in....
moto-fastboot flash pds pdsfix.img
moto-fastboot reboot
8. Updated my profile...yay
9. Updated my PRL...yay
10. RSD'd nopudding4u.sbf to relock
11. Got my 4g back
12. CAKE
This worked for me and I hope this can help anyone that messes up their PDS partition.
I think only 6 through 9 is necessary if you didnt sbf and were unlocked prior
Sweet, I'm about to do this now.
This worked great, finally I can update my profile and prl!
hoslayer13 said:
I think only 6 through 9 is necessary if you didnt sbf and were unlocked prior
Click to expand...
Click to collapse
Yes you are right, but even then I would have had to start at least with step 5 because I like my 4g
Yeah you're right. Sbfing would give the boot screen back too. Lol. Thanks for testing and documenting that atrix fix. Should have done it earlier though! You would have saved my photon from a reconned one due to exchange Lol
Nice . I'll have to try this, is HW information available now?
HW version does indeed show....
Plancy said:
Nice . I'll have to try this, is HW information available now?
Click to expand...
Click to collapse
Plancy, yes under ##786# it shows P3F0 under HW version....
It worked! Thanks it got my HW to show. BT adr not showing though... I wonder if it was liek this before.
were you able to update your profile/prl? It's funny...I've never used BT on my photon so honestly I don't know if mine isn't showing...I will check here in a few.
gemini6180 said:
were you able to update your profile/prl? It's funny...I've never used BT on my photon so honestly I don't know if mine isn't showing...I will check here in a few.
Click to expand...
Click to collapse
Yes I was able to update profile and prl, and same HW version as you. Though, it looks like that all this data is not our photon's own but what ever was written to the pdsfix.img fti and never overwritten, we still need to modify the fti and other files with our /serial number/etc, but that's probably hardly necessary if we're able to update prl/profile.
Well what can we use to input the information? I wrote down all the hardware info I could possibly find. (mac addresses and what not) How can we modify the fti and files. For what its worth, my photon is running like a champ, and I havent had a single problem or noticed any side effects of flashing this fix. Ive made backups just in case, but Im wondering if I should just leave it be...in my case I don't mind not having BT, because I never use it, and if I do, well I'll cross that bridge when it comes? What do you plan to do Plancy? Being able to update was all I really wanted and since updating my phone is golden.
My BT address shows up on my phone...so I am not sure why yours does not.
Well I'm able to connect to a BT Keyboard anyway, so I think we're fine.
From my understanding, the addresses only show if you enable bluetooth to begin with. Same goes with wifi and 4G addresses. I was looking at the files the fix has and it seems the information was pulled from an Atrix (obviously). Ive found that the camera lsc.isp from my Photon backup is about .1 kb bigger and has different information from the zip file that KeRmiT80 provided. I'm thinking that the information specific to the Photon hardware like BT and wifi generates automatically while the info from the fti file needed for updating and such sticks. Like Plancy said, everything should be fine. Was using windoze Notepad to look at this so some things i was unable view some things lol
Edit: The fix is missing the omadm folder that has some property files that I don't know what its for and that's about it. I'll look into how to edit it in a bit
gemini6180 said:
So about a month ago...I was messing with my Photon and "long story short", formatted my PDS Partition. I thought the menu I was in was for formatting my external SD card...but I formatted the Internal SD storage.
The PDS partition holds various information about your photon, some of it only unique to each phone. And if you delete it, the only real problem that arises is that you cannot update your Profile or your PRL. A good indication that the problem is with your PDS is that if you ##786#, under HW Version it will say "Unavailable".
Now a few people had the same problem in these forums, and its taken about a month to finally figure it out. Plancy, another member here actually deserves most of the credit in leading to a fix.
Over in the Atrix forums, people were having issues that required PDS recovery and some cool ass dudes over there came up with a fix....and whats awesome is that you can directly flash this file to restore your Photon PDS partition.
I am not sure if these steps are all needed but this is what I did to fix my phone...
1. RSD'd to 1FF-sunfire-user-2.3.4-4.5.1A-1_SUN-154_5-CM-release-keys-signed-Sprint-US
2. Performed a Factory Reset.
3. Updated the Motorola Software to 45.3.6
4. Rooted
5. RSD'd derpunlock.sbf to unlock
6. In this thread - http://forum.xda-developers.com/showthread.php?t=1131649
I downloaded the gingerbread (*_v8) version of the fix.
7. Using "Method 2" I placed the image in the folder that FASTBOOT is in....
moto-fastboot flash pds pdsfix.img
moto-fastboot reboot
8. Updated my profile...yay
9. Updated my PRL...yay
10. RSD'd nopudding4u.sbf to relock
11. Got my 4g back
12. CAKE
This worked for me and I hope this can help anyone that messes up their PDS partition.
Click to expand...
Click to collapse
I tried this in my xt1068 with unlocked bootloader.but it shows (bootloader) premission denied.. Help me!!!
Related
I was on 1.2.6 and decided that it was time to update to 1.5.7 since GingerBlur was out. I went back and decided to go to 1.2.6 SBF reflash to root, to 1.5.7 update, to root. Then I install the recovery ROM. Booted into there, made a backup on my SD card, changed my internal SD card (for Ubtunu, is that where it went wrong, had my SD card in and I think it was mounted). I exited the recovery adn was greeted with "Failed to boot 1. Launching RDS mode". I went into RDS and reflashed to 1.2.6. It did it's business and came back, but when I set up my motorblur, I realized something was off. The touchscreen was literally off by about 4-5CM. Click next required me to hit my search key, OFF the screen. If I was typing on the screen, I would have to go below that letter. The back key no longer works since it acts like a 'screen' touch if you will.
What's going on?! Already tried another reflash 1.2.6 again. Going to try 1.5.6.
If it doesn't work, I'm just going to take it back to AT&T and get it exchanged.
I was just about to start a new thread for this EXACT same problem...if anyone can help it would be great. I tried data wipe through android recovery mode but it didn't help. I was going to try to format the internal sd card but other than that i've got no idea. Anyone?
Did either of you try re-flashing? If it started with a flash first step to fixing is re-flashing.
Dennis's troubleshooting guide
1) ensure the gripe is a gripe
2) step back two steps and redo what you just did.
3) remove any mods and try again
4) verify on another device that it is/is not reproducable.
5) read the manual (not applicable to troubleshooting hardware on maany phones, though ifixit has some good guides)
6) take it to an expert.
Sent from my HTC Desire using Tapatalk
_Dennis_ said:
Did either of you try re-flashing? If it started with a flash first step to fixing is re-flashing.
Dennis's troubleshooting guide
1) ensure the gripe is a gripe
2) step back two steps and redo what you just did.
3) remove any mods and try again
4) verify on another device that it is/is not reproducable.
5) read the manual (not applicable to troubleshooting hardware on maany phones, though ifixit has some good guides)
6) take it to an expert.
Sent from my HTC Desire using Tapatalk
Click to expand...
Click to collapse
Reflashing is a no go...same problem
Edit: Okay...was able to re-install Tenfar's CWM. Going to try to format my internal SD and wipe everything, then reflash. I'll update with results...
No go...still the same problem. Also tried formatting the internal memory through the Settings app...didn't help. Does anyone have any other suggestions?
Anyone? The phone is pretty much unusable in this state...would really appreciate any input
chbearsrock said:
Anyone? The phone is pretty much unusable in this state...would really appreciate any input
Click to expand...
Click to collapse
Just an idea... have you tried:
1) Flashing 1.2.6, pre-root, 1.5.7, post-root
2) Installing Tenfar (not sure how, with your screen like that, maybe there is a shell command that lets you install via adb)
3) Using Tenfar to clear pretty much EVERYTHING (i.e., re-format, clear caches, all that jazz)
4) Re-do step 1
Well, an update: Went to the ATT store and got it exchanged. I'm pretty sure they really don't like me anymore. Haha.
As for the fix chbeaesrock posted, if he were to make a mistake he has to restate his device since he has no home button.
Check this thread out nosit1:
See if it matches the issue u have:
https://supportforums.motorola.com/message/362154/
Which part of the screen were u having issues with? the whole screen?
GO HERE FIRST:
http://forum.xda-developers.com/showthread.php?t=1426062
I have not tested this on a Photon, but the Photon version tenfars latest does work on the dx2 and the md5 on the update-recovery.zip with in the Photon apk is the same as in this zip.
Edit. I am 99% sure it will work and if not it can easily be changed in the script.
I WOULD PREFER POSTS BE MADE TO THE PARENT THREAD if it works on the Photon as other issues will be the same.
Thank you.
Edit after going through the pho apk script I see NO evidence that it won't work. My flash writes to /preinstall, /system/bin, and /data and the binaries used come from cwr itself(my flash binary is from tenfars apk and the dx2 is the same as the pho. 6 files total to make cwr run in this unique way. If you find these folders present on the photon IT SHOULD WORK.
skwoodwiva said:
http://forum.xda-developers.com/showthread.php?t=1426062
I have not tested this on a Photon, but the Photon version tenfars latest does work on the dx2 and the md5 on the update-recovery.zip with in the Photon apk is the same as in this zip.
Edit. I am 99% sure it will work and if not it can easily be changed in the script.
I WOULD PREFER POSTS BE MADE TO THE PARENT THREAD if it works on the Photon as other issues will be the same.
Thank you.
Click to expand...
Click to collapse
Anyone willing to try this?
My phone is near death to try...
It sounds an awful lot like the bootstrap we currently have. What functions or features will this give over that?
It is the same. But a feature of cwr w/ an unlocked BL is you flash a rom and wipe data the bootstrap does not rely on anything in data or system. Not so with a locked BL. It can be a head ache when the rom crashes yet you can sill boot but YOU JUST WIPED AWAY YOUR BOOTSTRAP!
THIS allows you to refresh bootstrap as the last step above.
I have flashed LOTS OF MOTO stuff, D3 Bionic atrix photon and at worst a SBF and a nandroid put me back FWIW.
Sounds interesting, does it work? Also how do you apply it?
skwoodwiva said:
It is the same. But a feature of cwr w/ an unlocked BL is you flash a rom and wipe data the bootstrap does not rely on anything in data or system. Not so with a locked BL. It can be a head ache when the rom crashes yet you can sill boot but YOU JUST WIPED AWAY YOUR BOOTSTRAP!
THIS allows you to refresh bootstrap as the last step above.
Click to expand...
Click to collapse
Read the op in the parent Dx2 therad. I posted your Q and my A. The BootstrapPHOTON_signed.apk and MOTODX2_Bootstrap_signed.apk have the same md5. They are different in name only!!! The atrix does have different md5 yet when I install it it works the same!
It works fine. The method of installing is unique.
Yeah my bad blonde moment. I see so basically ths is a quick flash you would apply to keep the bootstrap..
Just flash this before the reboot as your last step before rebooting.. I am following what you wrote now.
So u gonna try it?
Bump for edits in op.
Not the first post a noob really wants to make...but I've been searching the forums for an answer to my problem, but can't seem to find the info on the issue I'm having. I've seen some that were close & tried what was posted there without any success. I've checked out the Don't Panic -- Please Read First, includes troubleshooting guide Thread By: om4
A few days ago, I tried to install CM10 on my 4G LTE w/S-ON / HBOOT- 1.19. I was able to unlock the bootloader & install TWRP. Everything seemed to go okay until I rebooted my phone after installing CM10. It just hung on the Cyanogenmod splash screen. I tried re-installing it & kept getting the same problem. Today, I tried to install MeanROM ICS v6.5, but it keeps saying install failed. If I let the phone boot up, it'll hang on the MeanRom splash screen. I can still get into fastboot so I know it has to be a software issue. I've been beating my head against the wall for the past few days & just don't know how to fix it. Right now I have a very expensive paperweight. I'm hoping someone can help me fix this & get my phone back up & running.
TIA
for the millionth time
flash the boot.img seperately in hboot
Get (Flash Image GUI) off the Play Store.
If yr S-ON then u have to flash the kernel separate. That's why the ROM's keep hanging.
sent from my EVO LTE
http://forum.xda-developers.com/showthread.php?t=1772769&highlight=fastboot+gui
flex360 said:
for the millionth time
flash the boot.img seperately in hboot
Click to expand...
Click to collapse
I've been trying this all day, but must be doing something wrong. I found this: http://forum.xda-developers.com/showpost.php?p=29417266&postcount=1397, but was wondering if you might have more info on option 3.
TIA
if you know how to Fastboot, go for it, but use the Boot.img from the ROM you are flashing.
popper668 said:
if you know how to Fastboot, go for it, but use the Boot.img from the ROM you are flashing.
Click to expand...
Click to collapse
It's the only option I have now, so I hope I can figure it out. Wish me luck. I know it's probably something stupid that I'm missing & it's driving me crazy. lol
For meanrom make sure you have twrp 2.2.2.0 or later to be able install. The kernel installer will force the phone to reboot upon first run, this is when the kernel installs. For cm10 or other aosp based roms be sure to properly wipe phone. Cache, dalvik, factory reset, and system. Fastboot the kernel using SDK, mini SDK, uniflash, or boot image flasher. Do not use clockwork mod recovery to install roms as it is known to damage internel storage and or misc partitions.
ADB Tools Mini SDK
Thanks for all the info!!! I'm glad I found this place!!! I was able to get my phone working again. I found this post: http://forum.xda-developers.com/showthread.php?t=1937949 from back in October and found out that I was putting the boot.img in the wrong location. Once I fixed that, I have my phone back. Now I have to get it re-activated because I had to switch back to my Hero because I wasn't sure how long this would take. I hope Sprint will activate it even though is not stock anymore.
buddahj said:
Thanks for all the info!!! I'm glad I found this place!!! I was able to get my phone working again. I found this post: http://forum.xda-developers.com/showthread.php?t=1937949 from back in October and found out that I was putting the boot.img in the wrong location. Once I fixed that, I have my phone back. Now I have to get it re-activated because I had to switch back to my Hero because I wasn't sure how long this would take. I hope Sprint will activate it even though is not stock anymore.
Click to expand...
Click to collapse
have your first thanks
lol
the thanks is for using the search function lol
Well now I have another small problem. When I try to use the camera or go into gallery, it says no external storage available. Looks like I'm off to search the forums again for a fix. I'm sure it's something minor.
It looks like it's the internal SD card. Under storage in settings it shows the external card's total space & the 3 GBs used for app data, ect...
When I try and mount the SD card, it says preparing card but doesn't do anything. I think I say something about changing something in TWRP.
Forgot to mention, I can't connect the phone via USB either.
Ha, fixed my SD card/USB issues by following the directions in this thread - http://forum.xda-developers.com/showthread.php?t=1812774
OK so let me start off with, great site. I have read a ton of information.
First: Siyah 4.3.3 (Latest) Kernel which now has been put to AJK v1.48s
ROM; SHOstock3 v2.5.9
PreMod Settings: SGS2 AT&T SGH-i777. Started with GB > AT&T OTA (KIES) 4.0.3 > AT&T OTA WIFI 4.0.4 (caused huge freaking headaches with battery, charging, turn off the phone loop, battery draining, etc.)
Issues:
Original Issue posted in this thread (viewing Single Post) http://forum.xda-developers.com/showpost.php?p=39350619&postcount=18
Creepy offered something to try. That never worked as all I was able to do was download mode or stare at the Samsung Galaxy S2 Splash Screen. Well, I took to his download repository and other links and used his One-Click Recovery to stock GB Rom to make part of my phone usable, using this link here: http://forum.xda-developers.com/showpost.php?p=18859438&postcount=199
While it is Gingerbread at least my phone is usable. I want to try his STOCK ICS method but that mentions the eMMC super-brick bug.
So this is what I have tried so far. I have tried installing Siyah 4.3.3 nomswap for my kernel using Mobil-Odin Lite. That works but it never reboots or actually says finished. What it does do is stay at the wicked purple splash with the yin yang symbol. I left it like that last night until I woke up this morning and it never changed. So I rebooted the phone and the Kernel is on there. I reboot into recovery so that I can install SHOstock3 v2.5.9. That goes off flawlessly except here the last few times it won't reboot when I go to the GO BACK. It sticks and doesn't do anything. Rebooting shows the SHOstock3 Engine Boot Animation. Once it stops it goes to ask me for the encryption password. Well I put in my password (was the same one to the unlock screen) and it reboots and you see the nifty Samsung animation logo and then goes to the Samsung Galaxy S2 Animation Logo and then just stays there. It really pisses me off.
So after all that I finally put a new Kernel on there,AJK 1,48s. Pretty cool it loads up and then reboots. Well AJK shows up after the light-blue bar fills up and then goes black and the 4 touch sensitive row keys are lit up for a bit before going dark but the phone is still on. So I rebooted to recovery (CWM now with the Kernel) fixed tweaks, went to advanced and saw all sorts of options. Tried clearing caches for ROM 2 and restarting,no effect. I removed ROM 2 and went through reboot and nothing. Restored ROM 2 and nothing. Re installed SHOstock3 v2.5.9. Did the same thing after install and not backing out when I hit GO BACK. Rebooted, same scenario that happened before with requiring password. Entering password does the same thing with a reboot and then staying on Samsung Splash Screen. If I Don't enter the password and reboot,same thing happens. So after being irritated and pissed off I ran Creepy's One-Click Fix again and paid attention to the phone and noticed it mentioned not being able to access the AT&T section or partition or something like that. So while part of my phone works under normal circumstances I want to figure out how to remove that encryption part of the phone and get full access (even though full memory and space are shown under Windows 7 and the files on the phone). The password I put on there isn't taking and I don't know if using PC methods for removing encryption (which could take awhile I know) needs to be employed (and if so which methods) or if that part is just screwed and I can't put on any other kernels or custom ROMs. Perhaps tell me where I messed up. Should I try swapping the ROMs from Advanced setting in CWM Recovery? Can I try a different ROM (kernel didn't seem to help)? I have done several factory resets dalvik cache wipes cache wipes formats,etc. and it is still there. I can say that before the whole encryption debacle (even though I was encrypted I did get in my phone after encrypting it) my pin unlock for my SIM wouldn't work and I actually SIM locked my phone. Had to go to AT&T and get a new SIM and was up and running. I put a 4 digit pin lock for the SIM (it let me do it) and when I went to unlock it after a reboot, it wanted an 8 pin for the PUK and wouldn't take what I put. I tried to change the PIN but to no avail. Once that happened I guess it snowballed. Any help is appreciated. I have searched and tried some things that looked to match my issue but none have totally helped. I do have ADB set up on my wife's laptop which I use to restore my phone to GB Stock ROM. I haven't been able to reboot the phone into Bootloader to do any fastboot commands as when I tried to do it the commands just sent the phone into normal reboot (though adb reboot recovery does boot to recovery). I Haven't tried booting to the bootloader using the new Kernel though so I will wait for confirmation or additional information before I try. Thanks guys.
Eagle
Couple of comments. Siyah 4.3.3 (and ajk) kernels are for 4.x ICS and JB so that explains why your stock Gingerbread system would not flash after you installed it. If you flash back to stock Gingerbread again, and then flash a custom kernel, use a kernel that is compatible with Gingerbread if you want to boot the system.
After doing a little research, it seems that a wipe data/factory reset will not clear the encryption, but a format data will. This information is not from a Samsung forum; it's from the Droid DNA forum. I'm thinking that the same thing may apply to the I777. See the thread here.
It might be worth a try anyway. Flash stock plus root Gingerbread, install mobile odin or mobile odin lite, and use it to flash Siyah 2.6.14. Boot into recovery and go to the Mounts and Storage section. There you can format data, (and all the other partitions, separately.)
creepyncrawly said:
Couple of comments. Siyah 4.3.3 (and ajk) kernels are for 4.x ICS and JB so that explains why your stock Gingerbread system would not flash after you installed it. If you flash back to stock Gingerbread again, and then flash a custom kernel, use a kernel that is compatible with Gingerbread if you want to boot the system.
After doing a little research, it seems that a wipe data/factory reset will not clear the encryption, but a format data will. This information is not from a Samsung forum; it's from the Droid DNA forum. I'm thinking that the same thing may apply to the I777. See the thread here.
It might be worth a try anyway. Flash stock plus root Gingerbread, install mobile odin or mobile odin lite, and use it to flash Siyah 2.6.14. Boot into recovery and go to the Mounts and Storage section. There you can format data, (and all the other partitions, separately.)
Click to expand...
Click to collapse
Thank you so much creepy. I will give that a try later and see how it goes. I hope the information I gave actually gives enough info. I know folks usually want enough. Ill post back my findings.
Eagle
quick follow up and what I tried
creepyncrawly said:
Couple of comments. Siyah 4.3.3 (and ajk) kernels are for 4.x ICS and JB so that explains why your stock Gingerbread system would not flash after you installed it. If you flash back to stock Gingerbread again, and then flash a custom kernel, use a kernel that is compatible with Gingerbread if you want to boot the system.
After doing a little research, it seems that a wipe data/factory reset will not clear the encryption, but a format data will. This information is not from a Samsung forum; it's from the Droid DNA forum. I'm thinking that the same thing may apply to the I777. See the thread here.
It might be worth a try anyway. Flash stock plus root Gingerbread, install mobile odin or mobile odin lite, and use it to flash Siyah 2.6.14. Boot into recovery and go to the Mounts and Storage section. There you can format data, (and all the other partitions, separately.)
Click to expand...
Click to collapse
Hey Creepy, I have a quick follow up and want to tell you what I have tried.
So I had already used Kies to move to AT&T v 4.0.4 ICS on my phone when I read your post. Rather than flashback again to GB I went ahead and put Siyah 4.3.3 on my phone. Went great, rebooted and installed quick and everything. Well I rebooted into recovery and went to mounts and storage and formatted the data and all that there and even formatted the secondrom data and all that. Did it a couple times to make sure everything was clean and good to go. Even put AJKs kernel on there after I ran the cleanrom script and it went flawlessly. I did factory resets and wipes and all that and installed SHOstock3 v2.5.9 and started up great. Well it got past the animation and the damn Password for encryption popped up. Well I put the wrong password in and it rebooted without the SAMSUNG screen and went through the boot ani and back to the password for encryption screen. I put the right password in, it reboots and you see the Samsung logo flash quickly and then it sticks on the Samsung Galaxy S2 Splash screen. I don't know what is holding it up from going forward unless when I messed up the first go around and it deleted everything if it didn't take out the bootload command or what have you. So I don't know if this idea will work but I am going to flashback to GB and put the siyah version on there that you linked and see if that will work.
One tihng, when Iencrypted the device the first go round, I onlydid the used data and area not the whole thing. Is this affecting it somehow? Any other ideas to try? I figured a full data format would remove the encryption but it never pops up saying all encryption will be removed. What I need is access to that area of the phone if I could just mount it on the computer. Is it possible after formatting the data, or before, that I should mount internal USB, DATA, etc and try another format/wipe or at least mount them to see if they can be used? Thanks for the help. For anyone else viewing this post (which actually is a lot) any help or ideas are appreciated. I am thinking I may need to format everything and get ahold of Samsung to see if they will reset my phone for me. I just wonder if the PIN lock on my SIM card that got locked when it wouldn't take my PIN didn't mess something up as well.
Eagle
WarEagleUS said:
Hey Creepy, I have a quick follow up and want to tell you what I have tried.
So I had already used Kies to move to AT&T v 4.0.4 ICS on my phone when I read your post. Rather than flashback again to GB I went ahead and put Siyah 4.3.3 on my phone. Went great, rebooted and installed quick and everything. Well I rebooted into recovery and went to mounts and storage and formatted the data and all that there and even formatted the secondrom data and all that. Did it a couple times to make sure everything was clean and good to go. Even put AJKs kernel on there after I ran the cleanrom script and it went flawlessly. I did factory resets and wipes and all that and installed SHOstock3 v2.5.9 and started up great. Well it got past the animation and the damn Password for encryption popped up. Well I put the wrong password in and it rebooted without the SAMSUNG screen and went through the boot ani and back to the password for encryption screen. I put the right password in, it reboots and you see the Samsung logo flash quickly and then it sticks on the Samsung Galaxy S2 Splash screen. I don't know what is holding it up from going forward unless when I messed up the first go around and it deleted everything if it didn't take out the bootload command or what have you. So I don't know if this idea will work but I am going to flashback to GB and put the siyah version on there that you linked and see if that will work.
One tihng, when Iencrypted the device the first go round, I onlydid the used data and area not the whole thing. Is this affecting it somehow? Any other ideas to try? I figured a full data format would remove the encryption but it never pops up saying all encryption will be removed. What I need is access to that area of the phone if I could just mount it on the computer. Is it possible after formatting the data, or before, that I should mount internal USB, DATA, etc and try another format/wipe or at least mount them to see if they can be used? Thanks for the help. For anyone else viewing this post (which actually is a lot) any help or ideas are appreciated. I am thinking I may need to format everything and get ahold of Samsung to see if they will reset my phone for me. I just wonder if the PIN lock on my SIM card that got locked when it wouldn't take my PIN didn't mess something up as well.
Eagle
Click to expand...
Click to collapse
Should I try TWRP instead of CWM and if so where should I grab it from?
Status Update
So this is what I have tried so far as of this moment.
I reflashed using your Stock + Root Gingerbread ROM.
Wiped DATA and everything in recovery menu several times.
Used Kernel Wipe and ROM Nuke for extra cleaning power.
Reinstalled the Kernel AJK and SHOstock3 ROM
Haven't installed any themes though I had Johns Blue and Villians Poison Base Theme (I believe that is what it is) on there when this all went down. Should I put them back on there?
Password still pops up. So what it looks like is that unless I stick with the unencrypted portion of the phone, I am screwed with any custom ROMs as the correct password has the phone restart and then stick at the Samsung Galaxy S2 Splash Screen. Apparently I still cannot access that area of the phones memory to wipe it at all no matter what I do. I need to access it somehow. Really driving me crazy and thinking I may need to talk with AT&T(as Samsung told me to earlier this morning lol) and see what they can do.
One thing I do notice is when I use your stock root program it actually removes the encryption or decrypts the section of the phone for the stock ROM to go on the phone which is cool.
Eagle
Any other things to try from anyone is greatly appreciated.
Been away all day. Sorry, I can't offer any other suggestions, but I have no experience with encryption. As you said, what you need to know is where the encryption is stored in memory so you can wipe or format that and restore it to original. If you can get to the right person, probably not level 1 tech support, then maybe you can find out. Somebody somewhere knows the answer to this.
would restoring my original EFS before this whole process help or is the encryption section totally blocked off?
WarEagleUS said:
would restoring my original EFS before this whole process help or is the encryption section totally blocked off?
Click to expand...
Click to collapse
I have no idea whether the encryption is stored there. What kind of efs backup did you take?
creepyncrawly said:
Been away all day. Sorry, I can't offer any other suggestions, but I have no experience with encryption. As you said, what you need to know is where the encryption is stored in memory so you can wipe or format that and restore it to original. If you can get to the right person, probably not level 1 tech support, then maybe you can find out. Somebody somewhere knows the answer to this.
Click to expand...
Click to collapse
Thx bro. yeah I need to run some forensic tools and see if I can mount the whole phone system on my PC and run the tools.
creepyncrawly said:
I have no idea whether the encryption is stored there. What kind of efs backup did you take?
Click to expand...
Click to collapse
a full efs backup. I made two or three actuakky using advanced efs, nitrality, and recovery.
WarEagleUS said:
a full efs backup. I made two or three actuakky using advanced efs, nitrality, and recovery.
Click to expand...
Click to collapse
A little research indicates that there is quite a bit of stuff stored in efs besides carrier specific data. So maybe encryption could be in there. Of those tools, nitrality for sure and maybe advanced efs should be able to restore the entire efs partition. If you are comfortable with the risk - a damaged efs would render the phone useless - then you might try this to see if it clears up the encryption issue. BTW, you should learn how to back up the efs partition yourself using terminal and linux commands.
creepyncrawly said:
A little research indicates that there is quite a bit of stuff stored in efs besides carrier specific data. So maybe encryption could be in there. Of those tools, nitrality for sure and maybe advanced efs should be able to restore the entire efs partition. If you are comfortable with the risk - a damaged efs would render the phone useless - then you might try this to see if it clears up the encryption issue. BTW, you should learn how to back up the efs partition yourself using terminal and linux commands.
Click to expand...
Click to collapse
Yeah I should have used ADB to do that from the get go. I should have used the wife's laptop like I started to instead of my WIN 8 machine has it seems to be finicky with Android SDK (the portion at least needed to run ADB). Linux commands really aren't much different than terminal and I have done both. I was actually trying to get fastboot commands to work but my bootloader wasn't cooperating and for the life of me I couldn't find how to unlock it. I may try restoring that EFS. If nothing else I would love to be able to format that EFS and replace it with my original copy though as you said a damaged EFS may actually cause issues (who knows if it is damaged). I do know that I am fixing to chat with AT&T support. I hope I don't have to drive down to Hoover, AL to the repair facility. I would rather them send me a phone and send this one back. I am on stock 4.0.4 ICS from AT&T and any root that may be on there (though I doubt there is now) I can remove and what not
Thanks for the advice and insight Creepy. I know you tried like hell to get me an answer but in doing research on here with other problems I found out some useful information going forward my friend.
Eagle
Well, looks like I will be getting a special early upgrade and the wife will as well. I will be keeping this phone, however, to mess with this and see if I cannot get this problem fixed. Thanks Creepy so much. I appreciate your research and help more than you know. If possible I would love to keep this thread open for a while just in case I figure this out and fix the issue. It may take me a week or so but I will get back to messing with it again.
A side note. You don't need the whole sdk to get adb. You can download just the files you need from my signature.
Sent from my SGH-I777 using xda premium
Hello.
I have a Motorola Atrix that is not working and I have no clue about the history of the phone. I have no idea how it was messed up, or what was done to the phone.
Currently I see a screen with the M logo on it and the word unlock in the top left corner. I have seen many other people with this phone have had this same issue. I tried doing the common tip of wiping data and cache but nothing worked.
Can anyone help me out here. I dont care what the phone looks like I simply need it to turn on without a hitch and be able to navigate the menus. I could go completely stock and be thrilled. My only problem is that I am a complete beginner and cant figure out what to do or where to find current files. I have done a lot of searching here and a lot of the links seem to be broken, probably because this is an older phone...
Thanks anyone in advance!
PS: Im trying to fix this to turn into ATT for a credit towards a new phone, anyone who helps me solve the problem gets a free meal!
xda_bob said:
Hello.
I have a Motorola Atrix that is not working and I have no clue about the history of the phone. I have no idea how it was messed up, or what was done to the phone.
Currently I see a screen with the M logo on it and the word unlock in the top left corner. I have seen many other people with this phone have had this same issue. I tried doing the common tip of wiping data and cache but nothing worked.
Can anyone help me out here. I dont care what the phone looks like I simply need it to turn on without a hitch and be able to navigate the menus. I could go completely stock and be thrilled. My only problem is that I am a complete beginner and cant figure out what to do or where to find current files. I have done a lot of searching here and a lot of the links seem to be broken, probably because this is an older phone...
Thanks anyone in advance!
PS: Im trying to fix this to turn into ATT for a credit towards a new phone, anyone who helps me solve the problem gets a free meal!
Click to expand...
Click to collapse
Try flashing the 4.5.141 (2.3.6) SBF file via RSD for a full stock experience. This makes the phone "forget" that its unlocked (the unlock at the top left disappears). If you want to keep it unlocked, flash a fruitcake via CWM.
Sent from my MB860 using xda app-developers app
palmbeach05 said:
Try flashing the 4.5.141 (2.3.6) SBF file via RSD for a full stock experience. This makes the phone "forget" that its unlocked (the unlock at the top left disappears). If you want to keep it unlocked, flash a fruitcake via CWM.
Sent from my MB860 using xda app-developers app
Click to expand...
Click to collapse
Where can I find the 2.3.6 file? The ones I have found here are all broken links thus far.. I cant find the most current list I suppose.
xda_bob said:
Where can I find the 2.3.6 file? The ones I have found here are all broken links thus far.. I cant find the most current list I suppose.
Click to expand...
Click to collapse
Here's the post that gives you 4.5.145 (2.3.6). It returns the phone to stock and unlocked, but gets rid of the recovery. You'll need to dig through your system partition to delete the file that forces the stock recovery to show up before flashing a new recovery.
Warning : This may brick your phone . I am not responsible for damaged devices.
OTA IS ONLY FOR AT&T
Here is the OTA update zip
CAUTION!!!!
Some users reported bricks
failed to boot 1
http://db.tt/ATldH97n
And 38P Radio Rom (pulled from ota)
http://db.tt/AkQHXIc8
I dont prefer to flash ota
And the fruitcake
All credits goes to NYG-SBXLII
THIS IS FOR UNLOCKED DEVICES ONLY
BE SURE TO BACKUP BEFORE FLASHING
DONT FORGET TO WIPE USER DATA
Download here http://www.mediafire.com/?yofp249u4bcc26m
Also, here's another way to do it. Either method will work. The method below tells you where the recovery file i mentioned earlier is in the system partition.
I have made a cwm flashable zip for anyone that would like to test the new build. It includes kerrnel, system and webtop. I have tested this on my device and seems to work fine. However i will not be responsable for any bricked devices. flash at your own risk.
i have rooted this build with an older method so su binarys may need to be updated
also you will need to have a way to reflash your recovery there is a recovery-from-boot.p file in /system that will overwrite recovery with a stock one on every boot. it should be a very easy fix just find the file in /system and delete it reflash whatever recovery you like and the problem should be solved (sorry i just didnt have time to fix this)
For non AT&T users if you would like to try this build you can probably use the ramfix or one of faux123's kernnel. I can not tests this so i have no idea if it will work
THIS IS FOR UNLOCKED DEVICES ONLY
BE SURE TO BACKUP BEFORE FLASHING
DONT FORGET TO WIPE USER DATA
Download here
http://www.mediafire.com/?yofp249u4bcc26m
If 4.5.145 isn't what you want, try this link for other versions/carriers
www.das8nt.com/downloads
Sent from my MB860 using xda app-developers app