Related
This is seriously bugging me ever since someone mentioned the PDS partition was a culprit for not being able to update PRL/Data profile, and can cause other issues with the phone. I do not know of anyway to restore the partition as I don't have any nandroid backups.
Looking with a root browser, its empty, im not sure if the files are hidden in some way, but I'm able to view /system/ , but nothing appears in /pds/
No one has had this issue or knows what it means?
I'd also like the answer to this. I had it working fine on a different rom, then flashed CM9 to it and since then haven't been able to get it to update, even with my lock code and MSID and programming manually. I also don't have any backups..
mattred said:
I'd also like the answer to this. I had it working fine on a different rom, then flashed CM9 to it and since then haven't been able to get it to update, even with my lock code and MSID and programming manually. I also don't have any backups..
Click to expand...
Click to collapse
A discussion was started in one of my other threads it might help
http://forum.xda-developers.com/showthread.php?t=1517192
Still searching for a fix for this...cmon xda...please save the day!
I understand that the pds partition has information that is unique to each phone. Would there be a way for someone to upload their pds without their personal information and then I could fill in the blanks with mine? Then could I flash it to my phone?
Flash the PDS partition fix from the Atrix forums to create the partition, then hopefully someone will be kind enough to either share us their PDS files or tell us how to edit our own.
This is what worked for me...
http://forum.xda-developers.com/showthread.php?t=1575035
Hi guys,
I have searched high and low for this issue. I have found a lot of forums on how to fix the problem but none of them pertain to my circumstances. I installed Omega ICS ROM v 13.1 a week or two ago. I then decided to install Omega JB v18. I then upgraded to Omega JB v21 as well. In preparation for the official Samsung JB ROM, I went back to ICS. I started by downgrading to Omega v13.1 ICS followed by stock Samsung ICS ROM I9300XXALE8. A couple of days after doing this, all of a sudden, whilst on a call, I lost signal and then the stop sign icon appeared in the top toolbar. I have no radio, no wifi, no bluetooth and no lock screen & power menu. After all of the reading I have done, I have managed to discover that my EFS has disappeared. I have rooted the phone and installed ES File explorer and have looked inside the EFS folder only to find that it is blank. I did have a Nandbackup but managed to delete it in my attempts to recover my phone (yes I know im stupid but I didnt realise the significance of the backup until I realised what was missing!!). So, no EFS backup. Seemingly nothing in the EFS folder on the phones root. Any help would be greatly appreciated. One thing I did notice, which I am sure is significant in some way, is that when I put Omega JB on it, my sdcard mounted as "sdcard0" or something along those lines. Again, because I am fairly new to the custom ROM world, I didnt realise the significance of this until I had down graded back to ICS.
Please help!!!!
Thanks again.
EFS
http://forum.xda-developers.com/showthread.php?t=1308546
No fix then its a paid for repair .
jje
Have you tried to flash back to stock
JJEgan said:
EFS
http://forum.xda-developers.com/showthread.php?t=1308546
No fix then its a paid for repair .
jje
Click to expand...
Click to collapse
this description:
http://forum.xda-developers.com/showthread.php?t=1264021
should be tried before repair as well...
marcedli said:
this description:
http://forum.xda-developers.com/showthread.php?t=1264021
should be tried before repair as well...
Click to expand...
Click to collapse
Thanks guys...I have tried this one. Didnt work. Just wondering if anyone knows how or if I might be able to restore from sdcard0, if it still exists. I assume not, but I guess it might be something. Does anyone know why Omega JB did that in the first place ?
Please use the Q&A Forum for questions &
Read the Forum Rules Ref Posting
Thanks ✟
Moving to Q&A
rosshwalker said:
Thanks guys...I have tried this one. Didnt work. Just wondering if anyone knows how or if I might be able to restore from sdcard0, if it still exists. I assume not, but I guess it might be something. Does anyone know why Omega JB did that in the first place ?
Click to expand...
Click to collapse
If you do not have backup of efs folder. You have no chance of getting imei back.
You can go to service centre for rebuilding efs folder.
rosshwalker said:
Thanks guys...I have tried this one. Didnt work. Just wondering if anyone knows how or if I might be able to restore from sdcard0, if it still exists. I assume not, but I guess it might be something. Does anyone know why Omega JB did that in the first place ?
Click to expand...
Click to collapse
Flashing any roms can destroy the EFS thats why its always rule one to backup EFS folder . Multiple flashing up down up down increases the risk .
Did not Omega backup your EFS .
You say
have no radio, no wifi, no bluetooth and no lock screen & power menu
Thats not the signs of IMEI corruption as it plays no part in power menu or lockscreen .
jje
JJEgan said:
Flashing any roms can destroy the EFS thats why its always rule one to backup EFS folder . Multiple flashing up down up down increases the risk .
Did not Omega backup your EFS .
You say
have no radio, no wifi, no bluetooth and no lock screen & power menu
Thats not the signs of IMEI corruption as it plays no part in power menu or lockscreen .
jje
Click to expand...
Click to collapse
I think that S3 has some problem in securing it's EFS folder.
I flashed my S2 with hundred's of roms and never faced this issue.
Secondly in my experience lock screen and power menu is efs folder issue.
muhammad.ali123 said:
I think that S3 has some problem in securing it's EFS folder.
I flashed my S2 with hundred's of roms and never faced this issue.
Secondly in my experience lock screen and power menu is efs folder issue.
Click to expand...
Click to collapse
Read all the SGS2 and one help IMEI /EFS posts i suggest .
lock screen and power menu is efs folder issue >>> If it was a continual factor in the posts regarding EFS/IMEI then i would have agreed .
jje
A reminder about 2 things:
1) swapping/changing/etc IMEI's is illegal
2) giving someone else your EFS folder wont work, your phone will just default to the generic IMEI which is normally no better.
https://play.google.com/store/apps/...GwsMSwxLDEsImNvbS5oZWxyb3ouR1NJSV9SZXBhaXIiXQ..
try this out mate might b it'll help yu...cuz once i rescue cuz of diz app,,,
I wouldn't do that : in gs3 efs is not in the same block as gs2. It'll be worse than before.
Send me your efs partition backup using efs backup pro. I'll tell you if something can be done or not to restore your data.
Sent from my GT-I9300 using xda app-developers app
I had the same issue with my SGS1, the solution was flashing a stock rom with odin.
spocky12 said:
I wouldn't do that : in gs3 efs is not in the same block as gs2. It'll be worse than before.
Send me your efs partition backup using efs backup pro. I'll tell you if something can be done or not to restore your data.
Sent from my GT-I9300 using xda app-developers app
Click to expand...
Click to collapse
Hey. This is one of the things I had read about and tried and it came back with nothing. I don't recall the error message but I think it said it couldn't find the partition or folder or something. I am certain that it has to do with Omega Jb and the fact that it installed and mounted sdcard as sdcard0 and somehow, when going back to omega ics, this has occurred. Another thing I have just now remembered is that I had also setup a swap partition on my ext sdcard and had it mounted. This was all working fine for a few days though so I don't see how that caused it. Was really odd. Anyways, thanks for all the help, but I am going to pay for it to be repaired.
veyka said:
A reminder about 2 things:
1) swapping/changing/etc IMEI's is illegal
2) giving someone else your EFS folder wont work, your phone will just default to the generic IMEI which is normally no better.
Click to expand...
Click to collapse
hmmmm what if he has the IMEI number written somewhere? (phones box or license purchase note), can't he copy the EFS folder from someone else and just edit the IMEI??? >.>
Cruzaders said:
hmmmm what if he has the IMEI number written somewhere? (phones box or license purchase note), can't he copy the EFS folder from someone else and just edit the IMEI??? >.>
Click to expand...
Click to collapse
thats a working solution, he just need someone who shares his efs....
Kies
Have you tried the Kies Restore????? i't worked for me!
marcedli said:
thats a working solution, he just need someone who shares his efs....
Click to expand...
Click to collapse
if it is so easy to edit, it won't have an "e" in the name, would it?
Imei NULL/NULL - EFS Folder Lost.
Hi, I have a i9300 which lost efs folder, already tried restoring it through the box octopus, but at the time of writing the imei, it reports the error. (Write imei fail). Anyone have any idea what I can do?
So this morning I woke up and i couldn't get on my carrier network.. Which made me wonder wtf was going on. So I tried to go into settings to connect, but it wouldn't let me. I then realized my IMEI number was "unknown" which made my face one huge questionmark. I've tried using this guide; http://forum.xda-developers.com/showthread.php?t=1264021
But I can't find my folder? BUT!!! I found a EFS backup on my internal sd card.. which is good. I just don't know how to use it now?
I have CM 10 Nightly built from about the 15th of December (2012) and Siyah kernel... I think..
The folder i'm talking about is a zip named efsbackup.tar.gz
Can anyone help me? I tried going back to an old backup I had from october, but it didnt work either..
Try using an app like kTool (there are others) to restore the EFS backup (but obviously you only want to try this if it's definitely borked). There's a thread devoted to it on here (and you can get it from Google Play) which should have instructions on how to restore with it (never had to restore one myself).
The backup would have come from Siyah, which automatically makes an EFS backup. If you manage to fix it, thank Gokhan
MistahBungle said:
Try using an app like kTool (there are others) to restore the EFS backup (but obviously you only want to try this if it's definitely borked). There's a thread devoted to it on here (and you can get it from Google Play) which should have instructions on how to restore with it (never had to restore one myself).
The backup would have come from Siyah, which automatically makes an EFS backup. If you manage to fix it, thank Gokhan
Click to expand...
Click to collapse
I downloaded the app just before I saw your comment.. and it all looks confusing, but I tried clicking the "Restore EFS from backup (DANGEROUS" and it says I don't have the files.. Is there a way I can browse into my internal SD card, choose the file and then restore it?
try root explorer
gastonw said:
try root explorer
Click to expand...
Click to collapse
That app costs like 5 bucks
5 buck to be available to make calls again.........and you got a wonderful app for life
anyway, you've got some root explorers for free in play store, not as good tho.
Gaston gets a commission on every sale (Root Explorer is the shizz tho).
MistahBungle said:
Gaston gets a commission on every sale (Root Explorer is the shizz tho).
Click to expand...
Click to collapse
I see.. But do you have any clue of what I can do?
MistahBungle said:
Gaston gets a commission on every sale (Root Explorer is the shizz tho).
Click to expand...
Click to collapse
oh man, don't go whistle blowing now
I did say "There's a thread devoted to it on here..." (kTool). I would have thought that would be a pretty big hint to read that thread from start to finish if necessary (it's not a big thread; 23 pages. Can flick through it in no time).
And as I've never had to restore EFS myself, I only know what I've read in threads on here (same as you) so can't offer you first-hand experience. I figure the answer will be in one of the threads devoted to restoring EFS (and there are heaps of them on here), up to you to find it.
Reading time:
http://forum.xda-developers.com/showthread.php?t=1264021
http://forum.xda-developers.com/showthread.php?t=2073082&highlight=imei
http://forum.xda-developers.com/showthread.php?t=1596842&highlight=imei
BTW: you original IMEI should be below your battery.
MistahBungle said:
I did say "There's a thread devoted to it on here..." (kTool). I would have thought that would be a pretty big hint to read that thread from start to finish if necessary (it's not a big thread; 23 pages. Can flick through it in no time).
And as I've never had to restore EFS myself, I only know what I've read in threads on here (same as you) so can't offer you first-hand experience. I figure the answer will be in one of the threads devoted to restoring EFS (and there are heaps of them on here), up to you to find it.
Click to expand...
Click to collapse
Its not a good combination when im tired and I really want to fix my phone.. But I see lots of issues.. The only thing is, I didn't have a EFS file when I looked ( I hooked my computer up, but i dont have an .etc map?) so.. I was confused, but then I saw the backups and immediately backed them up AGAIN... Hmm. And I can't factory reset, can I?
Rijna said:
Hmm. And I can't factory reset, can I?
Click to expand...
Click to collapse
Now you don't wanna do that.
I'm tired too but i'm gonna give you a hand. Go to the dialer and dial *#06#. Let me know what's your showing IMEI number.
MistahBungle said:
I did say "There's a thread devoted to it on here..." (kTool). I would have thought that would be a pretty big hint to read that thread from start to finish if necessary (it's not a big thread; 23 pages. Can flick through it in no time).
And as I've never had to restore EFS myself, I only know what I've read in threads on here (same as you) so can't offer you first-hand experience. I figure the answer will be in one of the threads devoted to restoring EFS (and there are heaps of them on here), up to you to find it.
Click to expand...
Click to collapse
gastonw said:
Now you don't wanna do that.
I'm tired too but i'm gonna give you a hand. Go to the dialer and dial *#06#. Let me know what's your showing IMEI number.
Click to expand...
Click to collapse
Well I've given this a few gos on myself, and I've tried several apps claiming to be able to fix this, which made a EFS folder or file, and then it restored the exact folder again.. But this is all I got. I got a IMEI number, but it's a fake one.. or standard one, either way, it is not mine and not acceptable to any carrier. When I dial that it says "Not registred on network"
Rijna said:
Well I've given this a few gos on myself, and I've tried several apps claiming to be able to fix this, which made a EFS folder or file, and then it restored the exact folder again.. But this is all I got. I got a IMEI number, but it's a fake one.. or standard one, either way, it is not mine and not acceptable to any carrier. When I dial that it says "Not registred on network"
Click to expand...
Click to collapse
yeah, you've got a generic IMEI. Did you look under the battery? there's your REAL IMEI.
Still, dial *#06# and tell me what number pops up.
In that case, leave it till you're not tired. Last thing you want to do is do something silly & bork your phone. It can wait.
Rijna said:
Its not a good combination when im tired and I really want to fix my phone.. But I see lots of issues.. The only thing is, I didn't have a EFS file when I looked ( I hooked my computer up, but i dont have an .etc map?) so.. I was confused, but then I saw the backups and immediately backed them up AGAIN... Hmm. And I can't factory reset, can I?
Click to expand...
Click to collapse
gastonw said:
yeah, you've got a generic IMEI. Did you look under the battery? there's your REAL IMEI.
Still, dial *#06# and tell me what number pops up.
Click to expand...
Click to collapse
Yeah.. I did so, and it's not even close. And when I dial it still says "Not registered on network"
downloaded any root explorer app yet? hc ktool?
you are gonna need 'em.
gastonw said:
downloaded any root explorer app yet? hc ktool?
you are gonna need 'em.
Click to expand...
Click to collapse
I downloaded following;
ES File Explorer
GSII_Repair
HC-kTool
BusyBox
Terminal Emulator ( because I found this http://forum.xda-developers.com/showpost.php?p=19522938&postcount=10713 but I don't know how to work with it, but it seems to be this might be able to fix my problem..) but I don't know how to work with this.. or what file I should use in this.. extracted or unextracted.. etc. haha I checked the #1234# or whatever.. For what I can see everything looks legit - still.
Rijna said:
I downloaded following;
ES File Explorer
GSII_Repair
HC-kTool
BusyBox
Terminal Emulator ( because I found this http://forum.xda-developers.com/showpost.php?p=19522938&postcount=10713 but I don't know how to work with it, but it seems to be this might be able to fix my problem..) but I don't know how to work with this.. or what file I should use in this.. extracted or unextracted.. etc. haha I checked the #1234# or whatever.. For what I can see everything looks legit - still.
Click to expand...
Click to collapse
Well, you got a couple of guides to use those apps.
First of all get try locating the efs back up with root explorer app, so you can move it to a folder where hc ktool can restore it.
If that doesn't work get busybox running in the background and open gsii repair.
and if all the above don't work, your up for reading threads time.
from sii xda-ded
I am a noob and I am not a developer or even really great at programming or PC's in general.
I've managed to mess up my phone and have been looking all over the web for how to fix it and I am at a loss.
I decided to register and ask for help. Please be patient and understanding if I ask a lot of questions or don't understand things you accept as basic, understood or common. I looked through existing threads for help and couldn't find the answer I needed. Many thanks in advance for the help. Readers digest of the issue below.
Samsung Galaxy S 4G. T-Mobile. T959V5B5-Custom.
I tried the non-mandatory firmware update from T-mobile and it wrecked the functionality of my phone. I tried to go back with a couple new Rom versions and think I more or less ended up with three roms installed on my internal storage which has given me basically no space which was never an issue for me before. I have used a disk viewer to verify there is unmounted data that is taking up space but I can't figure out how to get to it through the phone or my pc to delete it. I assume if I do this that the empty space will be absorbed and fix the internal storage issue.
Again, thank you for taking the time to read and respond. I love my phone and just want it working right again.
JBMFT said:
I am a noob and I am not a developer or even really great at programming or PC's in general.
I've managed to mess up my phone and have been looking all over the web for how to fix it and I am at a loss.
I decided to register and ask for help. Please be patient and understanding if I ask a lot of questions or don't understand things you accept as basic, understood or common. I looked through existing threads for help and couldn't find the answer I needed. Many thanks in advance for the help. Readers digest of the issue below.
Samsung Galaxy S 4G. T-Mobile. T959V5B5-Custom.
I tried the non-mandatory firmware update from T-mobile and it wrecked the functionality of my phone. I tried to go back with a couple new Rom versions and think I more or less ended up with three roms installed on my internal storage which has given me basically no space which was never an issue for me before. I have used a disk viewer to verify there is unmounted data that is taking up space but I can't figure out how to get to it through the phone or my pc to delete it. I assume if I do this that the empty space will be absorbed and fix the internal storage issue.
Again, thank you for taking the time to read and respond. I love my phone and just want it working right again.
Click to expand...
Click to collapse
The course of action I would recommend at this point is using a tool called Odin to re-flash the stock ROM to your phone. I would recommend taking a look at this guide for the step-by-step procedure on how to do this. Let me know if you still have questions .
shimp208 said:
The course of action I would recommend at this point is using a tool called Odin to re-flash the stock ROM to your phone. I would recommend taking a look at this guide for the step-by-step procedure on how to do this. Let me know if you still have questions .
Click to expand...
Click to collapse
Hey! Big thanks for the reply. Here come the questions...
I used Odin to put the other OS versions on the phone so I am familiar with the software though its been several months. I also still have the ROM that I flashed to phone. I am curious though that if it didn't wipe the previous partitions last time, what would keep it from doing the same thing this time and really messing me up? Or did I click or not click something in Odin or use the wrong option and doing it differently this time would fix the problem?
I located the files on the phone and have verified they are not mounted and looked at their size using DiskInfo. They are located at "/dev/block". Do you know what this is or why they are there? I can delete them using ES File Explorer with SuperUser. Is it ok to delete these and would I get the benefit of increased storage by doing so? I played around with moving them to the SD card and didn't see an increase in my internal storage but was afraid that a reboot after doing to might be bad.
Can you tell I am a little gun shy?
Here are the names of the files, the set starting with t starts at 0 and goes to 12 and the other 1 to 12.
tsfr0-tfsr12
bml1-bml12
Thanks again!
JBMFT said:
Hey! Big thanks for the reply. Here come the questions...
I used Odin to put the other OS versions on the phone so I am familiar with the software though its been several months. I also still have the ROM that I flashed to phone. I am curious though that if it didn't wipe the previous partitions last time, what would keep it from doing the same thing this time and really messing me up? Or did I click or not click something in Odin or use the wrong option and doing it differently this time would fix the problem?
I located the files on the phone and have verified they are not mounted and looked at their size using DiskInfo. They are located at "/dev/block". Do you know what this is or why they are there? I can delete them using ES File Explorer with SuperUser. Is it ok to delete these and would I get the benefit of increased storage by doing so? I played around with moving them to the SD card and didn't see an increase in my internal storage but was afraid that a reboot after doing to might be bad.
Can you tell I am a little gun shy?
Here are the names of the files, the set starting with t starts at 0 and goes to 12 and the other 1 to 12.
tsfr0-tfsr12
bml1-bml12
Thanks again!
Click to expand...
Click to collapse
Using Odin to re-flash the stock ROM will automatically setup the right configuration for. Do Not delete the files in /dev/block these are critical to the phones operation and part of the phones normal partitioning and operation as previously stated deleting these will cause a lot of problems if you delete them. If you really want to free up some internal storage space I would recommend deleting the carrier pre-installed bloatware, before you delete any bloatware makesure to backup the apps you deleted with Titanium Backup or a similar backup or flash Clockworkmod Recovery or Team Win Recovery Project and make a Nandroid Backup which is a complete backup of your phone. And don't worry about being gun shy we are all beginners at some point the only real way to become an expert if practice, practice, practice .
So I am working on the Heimdall One-Click.
Handshaking with loke, got no response. FML.
Help.
Edited: Apparently a low battery is not your friend...
after a little reading around on the net I tried a different one and BAM.
Back to stock. We'll see how this goes.
Being rooted with superuser had me spoiled...so much bloatware.
Hello everyone,
I was trying to compile loki with my aboot.img and boot.img, but it says "supportive device".
Is there a way we can get this device supportive? I don't know to much about finding the check_sigs and hdr. I have attached the aboot.img and boot.img if anyone is willing to help thanks!
PS: The password for the zip is "android"
Here is the GitHub for loki
https://github.com/djrbliss/loki
Are you really the only guy working on anything for this phone?
Sent from my LGMS500 using XDA Premium 4 mobile app
I will be helping him to I own this phone I have been trying to get cwm on this phone it is taking time though
I would totally donate to anyone who took the time to figure this phone out. When I went to the T-Mobile store, I was looking for the L9, which appears to have a strong modding community behind it, but they didn't have it in-store and I was in a pinch, so here I sit with a completely stock experience in my pocket. Not the worst stock experience, surely, but still stock.
killernos said:
I will be helping him to I own this phone I have been trying to get cwm on this phone it is taking time though
Click to expand...
Click to collapse
Playfulgod has been working on native cwm for this, but I found that the f3 2nd init recovery works. Check my thread in atr
sent using logic and reason from a device forged of witchcraft.
---------- Post added at 11:33 PM ---------- Previous post was at 11:33 PM ----------
tokenpoke said:
Playfulgod has been working on native cwm for this, but I found that the f3 2nd init recovery works. Check my thread in metropcs atr
sent using logic and reason from a device forged of witchcraft.
Click to expand...
Click to collapse
sent using logic and reason from a device forged of witchcraft.
I'm here to help in anyway people. Metropcs, rooted, limited experience from way back when android was a "sprocket"...ha ha. We can get this device cranking out kit kat crazy mods!
lg f6 help...Please help save a guy from bricking!
So I apologize if Im posting in the wrong spot but I noticed yall are still working on the F6...so I figured this made sense...
I thought I knew exactly what I wasdoing but did not....I was lucky enough to find patience enough to read up before flashing...I see the threads posted on how to root, backup, and restore this phone...but all those threads explain it using so0ftware other than I have... Since I made some moves before truly knowing what I was doing...I'd like to just stick wiith what i got for the moment and see if yall, as the experts can guide me down the runway...
Heres What I have so far:
1. I DO have root access
2. I DO have SuperSU and it seems to be working in the sense that it keeps logs...but sometimes it gives me a binary error. (I have NOT et converted SuperSU into a system app...bc im unclear if its necessary after reading a few different threads)
3. I DO have Root Browser' which I use to shuffle things around. (I DO have the /system and /data folders relocated on my external SD)
4. I DO have Titanium Backup which I used to BU my USER APPS/SYSTEM DATA.
5. I DO have Flashify which I also used to BU my STOCK RECOVERY/KERNEL (I cant seem to figure out where that recovery is being default stored though...Ive been searching high and low.
NOTE: Although im happy I have made it this far...I dont wanna go any further until I know exactly what im doing. I fear that I have missed something small. Something that would be a no brainer to you experts.
I'm unclear of storage requirements...I BELIEVE that I must store all my rooted tools on the external bc the goal is to wipe everything NOT on ext SD.
What I THINK I know is that hypothetically since im backed up...or when im 100% certain everything is....I can just click REBOOT TO RECOVERY MODE under the menu using Titanium.
IF I happen to be correct up to that point....I think my next move is using Titanium to put back the things ive stored on my SD.
In my mind that leaves me with the same ROM...but without the fluff...and now the ability to save to ext SD.....
If I underestand right....currently there are no MOD upgrades available due to difficulty of unlocking the bootlag....or something that sounds likethat...
I have ZERO experience with any of this....I hope what I just shared is at least in the ballpark of the right direction..
THANK YOU for any and all help!
I
RootinBootinGoodTime said:
So I apologize if Im posting in the wrong spot but I noticed yall are still working on the F6...so I figured this made sense...
I thought I knew exactly what I wasdoing but did not....I was lucky enough to find patience enough to read up before flashing...I see the threads posted on how to root, backup, and restore this phone...but all those threads explain it using so0ftware other than I have... Since I made some moves before truly knowing what I was doing...I'd like to just stick wiith what i got for the moment and see if yall, as the experts can guide me down the runway...
Heres What I have so far:
1. I DO have root access
2. I DO have SuperSU and it seems to be working in the sense that it keeps logs...but sometimes it gives me a binary error. (I have NOT et converted SuperSU into a system app...bc im unclear if its necessary after reading a few different threads)
3. I DO have Root Browser' which I use to shuffle things around. (I DO have the /system and /data folders relocated on my external SD)
4. I DO have Titanium Backup which I used to BU my USER APPS/SYSTEM DATA.
5. I DO have Flashify which I also used to BU my STOCK RECOVERY/KERNEL (I cant seem to figure out where that recovery is being default stored though...Ive been searching high and low.
NOTE: Although im happy I have made it this far...I dont wanna go any further until I know exactly what im doing. I fear that I have missed something small. Something that would be a no brainer to you experts.
I'm unclear of storage requirements...I BELIEVE that I must store all my rooted tools on the external bc the goal is to wipe everything NOT on ext SD.
What I THINK I know is that hypothetically since im backed up...or when im 100% certain everything is....I can just click REBOOT TO RECOVERY MODE under the menu using Titanium.
IF I happen to be correct up to that point....I think my next move is using Titanium to put back the things ive stored on my SD.
In my mind that leaves me with the same ROM...but without the fluff...and now the ability to save to ext SD.....
If I underestand right....currently there are no MOD upgrades available due to difficulty of unlocking the bootlag....or something that sounds likethat...
I have ZERO experience with any of this....I hope what I just shared is at least in the ballpark of the right direction..
THANK YOU for any and all help!
I
Click to expand...
Click to collapse
Love xda.....
Is the recovery in "clockworkmod" folder in internal or exteral sd (was on my Metro F6)
And
Have you found this .... MS500][F6] Freedom Kernel Overclocked by GameTheory?
Over at.... here
Its for Metro LG F6 but I already ran tmobile firmware on my metro f6 without any problems....
I hope I can place an external link, as I'm somewhat unclear on if I can or can't.
IF it is wrong, please remove. I've been a member since 06 (That's 2006) I should be able to do so?????
Recovering F6
I agree with MadeFree, that the recovery file should be found in the 'Clockwork Mod' folder, under External SD, when using File Manager. When in recovery mode it should automatically bring up your Rom-backup when you click on Recover from External / (creation date) file name / yes to confirm.
Also, I use the F6 and I have bricked it multiple times while trying to figure out what i can actually do on it, as it only currently has a custom recovery made for it. I have been trying to figure out myself how to recover all the apps, files, pics, videos, etc. when i have to flash to STOCK Rom during brick. Currently, my solution for this was not found in the 'nano-droid backup' (i have been led to believe it could be recovered in RECOVERY MODE) but rather in an app called ROM toolbox from Google store. This does so much more than Titanium Backup does but i still use titanium for backing up a single application if needed. Rom toolbox can also save a copy of the Kernel as well as monitor your apps, make CPU tweaks, make backups using Google drive and much more. But the easiest way I have found for me may be different for you. Currently, my only reliable solution for recovering my data is using ZIP ME, (downloaded from the ROM toolbox app) as well as backing everything up using Google drive. The zip files are nice when not near my computer though. All i have to do after booting up the 'factory reset' is open file manager and look for my zips.
do not be afraid to soft brick (looping, freezes, crashes) when all you have to do is factory reset your phone using key combo or use the firmware followed in from the link provided by Madefree, down below.
mrblown said:
I agree with MadeFree, that the recovery file should be found in the 'Clockwork Mod' folder, under External SD, when using File Manager. When in recovery mode it should automatically bring up your Rom-backup when you click on Recover from External / (creation date) file name / yes to confirm.
Also, I use the F6 and I have bricked it multiple times while trying to figure out what i can actually do on it, as it only currently has a custom recovery made for it. I have been trying to figure out myself how to recover all the apps, files, pics, videos, etc. when i have to flash to STOCK Rom during brick. Currently, my solution for this was not found in the 'nano-droid backup' (i have been led to believe it could be recovered in RECOVERY MODE) but rather in an app called ROM toolbox from Google store. This does so much more than Titanium Backup does but i still use titanium for backing up a single application if needed. Rom toolbox can also save a copy of the Kernel as well as monitor your apps, make CPU tweaks, make backups using Google drive and much more. But the easiest way I have found for me may be different for you. Currently, my only reliable solution for recovering my data is using ZIP ME, (downloaded from the ROM toolbox app) as well as backing everything up using Google drive. The zip files are nice when not near my computer though. All i have to do after booting up the 'factory reset' is open file manager and look for my zips.
do not be afraid to soft brick (looping, freezes, crashes) when all you have to do is factory reset your phone using key combo or use the firmware followed in from the link provided by Madefree, down below.
Click to expand...
Click to collapse
Hey mrblown;53026638,
Heads up to ya....
There is another app that ya all could try, but its FREE and works.Back Up Your Mobile. Go figure huh?
It stores on internal, but I copied to external_sd and that is where my backup is located.
You might want to THANK the following member pressy4pie....for this... he be here on xda more than likely on F6 excellent dev.
No I don't have the link SORRY!
CMD LOKI RECOVERY
adb push E:\Andoid\LG MOTION\pressy4pie-cwm-unofficial.lok /data/local/tmp
adb push E:\Andoid\LG MOTION\pressy4pie-cwm-unofficial.lok_flash /data/local/tmp
adb shell
su
cd /data/local/tmp
./loki_flash recovery cwm.lok
Click to expand...
Click to collapse
I have "Terminal Fever" so I have not tried it but it should work. Follow HIS STEPS. THX!
Good tweaking to ya.
madefree said:
Hey mrblown;53026638,
Heads up to ya....
There is another app that ya all could try, but its FREE and works.Back Up Your Mobile. Go figure huh?
It stores on internal, but I copied to external_sd and that is where my backup is located.
You might want to THANK the following member pressy4pie....for this... he be here on xda more than likely on F6 excellent dev.
No I don't have the link SORRY!
I have "Terminal Fever" so I have not tried it but it should work. Follow HIS STEPS. THX!
Good tweaking to ya.
Click to expand...
Click to collapse
whats up hroark13 me and a couple other devs have brought cyanogenmod 11 to this phone im trying to spread the word it is located here http://androidforums.com/metropcs-o...eta-4-4-4-cyanogenmod-11-0-unofficial-12.html