Database Users

REMINDER about /efs

Well gentle man. I failed to back up my /efs folder. I lost my imei and can only get an edge connection. This is just a friendly reminder to please back up your /efs folder. I did not know about doing this until it was too late. I'm my s3 was not salvageable. But still works with Wi-Fi.
Sent from my SGH-T999 using Tapatalk 2

I thought we couldn't back that up yet?
Sent from my SAMSUNG-SGH-I747 using Tapatalk 2

corythug said:
I thought we couldn't back that up yet?
Sent from my SAMSUNG-SGH-I747 using Tapatalk 2
Click to expand...
Click to collapse
Inapplicable advice. Sorry.

Diviance said:
Provided you are rooted (which, if you aren't the folder isn't really in danger) you can use Root Explorer to copy it directly to the sdcard, or download dropbox and stick it in the dropbox folder and cloud back it up too.
Or Spideroak. Or Box.
Click to expand...
Click to collapse
Oooh ok, thanks. What directory is it located if you don't mind?
Sent from my SAMSUNG-SGH-I747 using Tapatalk 2

It is in the root of your phone. It is the file called efs.
Sent from my SGH-T999 using Tapatalk 2

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Sent from my SGH-T999 using Tapatalk 2

Which is weird because I have the file bit have no way of fixing it
Sent from my SGH-T999 using Tapatalk 2

Ah, seems my advice from above is not applicable to the S3 series. Samsung moved where the IMEI is actually located or something because, from what I have found, it is not located in /efs.
So uh, for the moment aside from literally backing up every single partition on your device I do not know of a working method of backing up your IMEI to prevent corruption.

dont feel to bad mac your not alone. quick question what recovery did you flash cwm touch? twrp

deeznutz1977 said:
dont feel to bad mac your not alone. quick question what recovery did you flash cwm touch? twrp
Click to expand...
Click to collapse
We need to focus on finding what is causing this so it can be avoided. It seems to be related to flashing a recovery. Please post any details that we can use to find a pattern.
Sent from my SAMSUNG-SGH-I747 using Tapatalk 2

its a known issue with all of the lte sgs 3's. backing up /efs wont help as there is no nv_data.bin which contains the imei number.
heres an ongoing thread about it http://forum.xda-developers.com/showthread.php?p=28710945

mobilehavoc said:
We need to focus on finding what is causing this so it can be avoided. It seems to be related to flashing a recovery. Please post any details that we can use to find a pattern.
Sent from my SAMSUNG-SGH-I747 using Tapatalk 2
Click to expand...
Click to collapse
Bump...a lot of people don't know about backing up their IMEI. This post should be stickied or something.

mobilehavoc said:
We need to focus on finding what is causing this so it can be avoided. It seems to be related to flashing a recovery. Please post any details that we can use to find a pattern.
Click to expand...
Click to collapse
I've flashed half a dozen CWM recovery versions so far and haven't "lost my imei" yet, and don't see why it would.
(FWIW, I'm currently using http://download2.clockworkmod.com/recoveries/recovery-clockwork-touch-5.8.4.7-d2att.img for ATT and simply dd'd it over partition 18 like all the rest. CWM-flashable versions shouldn't make any difference, though)

zmore said:
I've flashed half a dozen CWM recovery versions so far and haven't "lost my imei" yet, and don't see why it would.
(FWIW, I'm currently using http://download2.clockworkmod.com/recoveries/recovery-clockwork-touch-5.8.4.7-d2att.img for ATT and simply dd'd it over partition 18 like all the rest. CWM-flashable versions shouldn't make any difference, though)
Click to expand...
Click to collapse
DD is much safer as you're just doing a block copy from one device to the other so it's a kernel level copy that is pretty safe as long as you're targeting the right partition. However flashing things could go wrong and it could overwrite a partition or unmount it or something that could lead to these issues
Sent from my SAMSUNG-SGH-I747 using Tapatalk 2

Okay so I have T-Mobile. I rooted using Odin. I installed cwm via Odin. On the 23rd of last month. What caused me to lose imei was that I flashed an updated cwm via Rom manager. The cwm I.flashed was the one that wouldn't let you restore any back ups from your back up restore file. But I flashed the aokp release 3 as well..I did a complete wipe. Then installed from as card. Then had no signal
Sent from my SGH-T999 using Tapatalk 2

MacTheRipperr said:
Okay so I have T-Mobile. I rooted using Odin. I installed cwm via Odin. On the 23rd of last month. What caused me to lose imei was that I flashed an updated cwm via Rom manager. The cwm I.flashed was the one that wouldn't let you restore any back ups from your back up restore file. But I flashed the aokp release 3 as well..I did a complete wipe. Then installed from as card. Then had no signal
Sent from my SGH-T999 using Tapatalk 2
Click to expand...
Click to collapse
I lost mine when i pushed the clockworkmod touch then flashed it then aokp. btw i still have calls and edge

Is this a carrier specific issue?
Sent from my SCH-I535 using xda app-developers app

I did pretty much the same exact thing.
Sent from my SGH-T999 using Tapatalk 2

MacTheRipperr said:
Okay so I have T-Mobile. I rooted using Odin. I installed cwm via Odin. On the 23rd of last month. What caused me to lose imei was that I flashed an updated cwm via Rom manager. The cwm I.flashed was the one that wouldn't let you restore any back ups from your back up restore file. But I flashed the aokp release 3 as well..I did a complete wipe. Then installed from as card. Then had no signal
Sent from my SGH-T999 using Tapatalk 2
Click to expand...
Click to collapse
Did you flash CWRT 5.8.4.7? I'm still on 5.8.4.5 and have flashed many things without losing my IMEI. Could the new CWR be the source of the problem?
Sent from my SGH-T999 using xda premium

I had the cwm used in the very first root method. I updated to the one right before touch and bam everything was gone.
Sent from my SGH-T999 using Tapatalk 2

[Q] Update from 4.1.1?

Screen shots attached, came back from mowing yard and i am prompt for an update. I'm rooted and unlocked on 4.1.1
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Has anybody else seen this yet?
Sent from my Nexus 7 using Tapatalk 2

I just got this update and installed it. The only change that I see so far is in the About tablet screen they added in the "FCC ID" and "IC". Android version still reads 4.1.1.

Just got this too
Sent from my Nexus 7 using xda app-developers app

can you guys use logcat and see what the download url is please

Questions go in the Q&A section

installed with the stock recovery now here is the new about screen shows model ME370T

I just got the notification, it seems to be something very small but who knows, the download is only 800kb.:what:
Sent from my Nexus 7 using Tapatalk 2

I had to tell it to check for the update, but I got it too.
Sent from my Nexus 7 using xda app-developers app

daraldf said:
I had to tell it to check for the update, but I got it too.
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
Well this update remove custom recovery + root or the custom DPI?

endiz said:
Well this update remove custom recovery + root or the custom DPI?
Click to expand...
Click to collapse
It probably won't even install.

So who has the file name or url from google?

I got the prompt too. After I agreed to it, phone rebooted into recovery and said failed to continue or something. Now when I check, there is no more update.

theoneofgod said:
I got the prompt too. After I agreed to it, phone rebooted into recovery and said failed to continue or something. Now when I check, there is no more update.
Click to expand...
Click to collapse
I assume you are running a "custom" recovery (clockwork)? This is why it failed. Only way to install will be to flash back to stock recovery as someone above mentioned. Probably not even worth the trouble.

Land Master said:
I assume you are running a "custom" recovery (clockwork)? This is why it failed. Only way to install will be to flash back to stock recovery as someone above mentioned. Probably not even worth the trouble.
Click to expand...
Click to collapse
Yep. I think I will restore the stock recovery since I won't be doing any kernel/rom flashing for a while. Stock rom is very stable.

I received this update on both of my N7's and I can't tell what it changed other than the about screen.
Sent from my Nexus 7 using xda app-developers app

JFMFT said:
I received this update on both of my N7's and I can't tell what it changed other than the about screen.
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
What changed on the about screen?

View my post on the first page for the pic of the new about.
If you want to force the update you can go into settings apps all and force stop "Google Services Framework" then clear the data on it. Exit settings then go back in and system update and its there

They seem to have added an FCC ID field and an IC field. Screenshot attached.
Sent from my Nexus 7 using xda app-developers app

It said on the update that it was adding swipe up on the bottom bar for Google Now.
Sent from my Nexus 7 using xda premium

Land Master said:
I assume you are running a "custom" recovery (clockwork)? This is why it failed. Only way to install will be to flash back to stock recovery as someone above mentioned. Probably not even worth the trouble.
Click to expand...
Click to collapse
Anyone mind letting me know how to flash back to stock recovery? Is there a stock recovery img that I just flash in CMW? I'd like to retain root but still be able to perform future updates.
It said on the update that it was adding swipe up on the bottom bar for Google Now.
karnovaran said:
It said on the update that it was adding swipe up on the bottom bar for Google Now.
Click to expand...
Click to collapse
My update failed and I'm able to swipe up on the bottom bar for Google. I wonder if that fuction was there initially.

How to use twrp to replace clockwork recovery -- uninstalling clockwork?

I want to uninstall clockwork completely, remove all instances of it and move to twrp. What is the best way I can do this? right now I see that cwr is using roughly 3gb of my storage (8gb) model, so I need to know the correct procedure to removing it. Thanks
Sent from my Nexus 7 using Tapatalk 2

ikn0wagh0st said:
I want to uninstall clockwork completely, remove all instances of it and move to twrp. What is the best way I can do this? right now I see that cwr is using roughly 3gb of my storage (8gb) model, so I need to know the correct procedure to removing it. Thanks
Sent from my Nexus 7 using Tapatalk 2
Click to expand...
Click to collapse
download the twrp package and flash it with fastboot.
Alternatively: go to twrp thread, follow directions.

thracemerin said:
download the twrp package and flash it with fastboot.
Alternatively: go to twrp thread, follow directions.
Click to expand...
Click to collapse
I know how to install twrp, I just want to know the correct process to remove all instances of clockwork mod from my device so I can free up some space
Sent from my Nexus 7 using Tapatalk 2

ikn0wagh0st said:
I know how to install twrp, I just want to know the correct process to remove all instances of clockwork mod from my device so I can free up some space
Sent from my Nexus 7 using Tapatalk 2
Click to expand...
Click to collapse
CWM lives in the recovery partition which doesn't show up as part of your storage, how is it using up so much space?

thracemerin said:
CWM lives in the recovery partition which doesn't show up as part of your storage, how is it using up so much space?
Click to expand...
Click to collapse
No idea..I have one backup and its taking up almost 3 gigs of space.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Sent from my Nexus 7 using Tapatalk 2

ikn0wagh0st said:
No idea..I have one backup and its taking up almost 3 gigs of space.
<clip>
Sent from my Nexus 7 using Tapatalk 2
Click to expand...
Click to collapse
That's nandroid backups, those have nothing to do with CWM other than you made them with it, just delete the folder. CWM itself is exactly 6635520 bytes and isn't on a partition you can look at in a file explorer.

cool. I just installed twrp, deleted the clockwork folder and freed up a bunch of space. I have no idea why clockwork was taking up so much space. I had one backup. That's it. My twrp backup is 500megs.
Sent from my Nexus 7 using Tapatalk 2

ikn0wagh0st said:
cool. I just installed twrp, deleted the clockwork folder and freed up a bunch of space. I have no idea why clockwork was taking up so much space. I had one backup. That's it. My twrp backup is 500megs.
Sent from my Nexus 7 using Tapatalk 2
Click to expand...
Click to collapse
No Idea, there have been some odd things reported with the new v6 versions of CWM, could be some sort of bug. It sounds almost like it backed everything up 2 or 3x in 1 backup based on my rough math.

My back up is 20 mb, is that wrong
Sent from my Nexus 7 using Tapatalk 2

desiresiscool said:
My back up is 20 mb, is that wrong
Sent from my Nexus 7 using Tapatalk 2
Click to expand...
Click to collapse
Sounds like it was never able to finish. I would re-do that backup
Sent from my Nexus 7 using XDA Premium HD app

desiresiscool said:
My back up is 20 mb, is that wrong
Sent from my Nexus 7 using Tapatalk 2
Click to expand...
Click to collapse
Yes your backup should definitely be larger than that. I have several I will open them and see what size they are, I'm guessing 500 mb to 1 GB approximately. Will update soon with the total.
Sent from my ADR6425LVW using xda premium

desiresiscool said:
My back up is 20 mb, is that wrong
Sent from my Nexus 7 using Tapatalk 2
Click to expand...
Click to collapse
clintkev251 said:
Sounds like it was never able to finish. I would re-do that backup
Sent from my Nexus 7 using XDA Premium HD app
Click to expand...
Click to collapse
Your backup should be the total size of the stuff in your device - the compression, i'm not sure how heavy the compression CWM uses for Nandroids is, but 20mb is way too small to be the full thing.

ASUS TF300T JB root how to that works......

Can anyone show me the correct way of rooting my TF300T I just exchanged it so its new in the box. I did the CWM to the last one and it bricked it HARD. Im assuming it has the Jb update already on it. And in what order do I put the steps in to get ROOT, RECOVERY, SU. Just looking for a good way not to brick it again thanks in advance.:fingers-crossed:

bradackman said:
Can anyone show me the correct way of rooting my TF300T I just exchanged it so its new in the box. I did the CWM to the last one and it bricked it HARD. Im assuming it has the Jb update already on it. And in what order do I put the steps in to get ROOT, RECOVERY, SU. Just looking for a good way not to brick it again thanks in advance.:fingers-crossed:
Click to expand...
Click to collapse
1st off I doubt your new unit "has the Jb update already on it", as it's likely been wrapped in it's packaging longer than 4.1.1 has been available.
2nd, use the search function in the future

Bolandk said:
1st off I doubt your new unit "has the Jb update already on it", as it's likely been wrapped in it's packaging longer than 4.1.1 has been available.
2nd, use the search function in the future
Click to expand...
Click to collapse
where is the recovery tool on 4.1 ? what do youy suggest I use to do a recovery ?

bradackman said:
where is the recovery tool on 4.1 ? what do youy suggest I use to do a recovery ?
Click to expand...
Click to collapse
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
See that link I posted above?
Follow from "== Part 3 - Install recovery and rooting =="

Bolandk said:
See that link I posted above?
Follow from "== Part 3 - Install recovery and rooting =="
Click to expand...
Click to collapse
awesome pic lol
ok thanks for the advise I just want to blow this one up too

bradackman said:
awesome pic lol
ok thanks for the advise I just want to blow this one up too
Click to expand...
Click to collapse
it says cannot load file what step am I missing

Haha!!!
OP man please read, read and then read. So many step by step instructions have already been laid out. You can do it my friend
Sent from my ASUS Transformer Pad TF300T using Tapatalk 2

bradackman said:
it says cannot load file what step am I missing
Click to expand...
Click to collapse
here is a pic of what I got back

bradackman said:
here is a pic of what I got back
Click to expand...
Click to collapse
1. Attached pic too small
2. Have you been reading the replies from other posters?

bradackman said:
here is a pic of what I got back
Click to expand...
Click to collapse
I guess I'm dumb and don't understand this
2) Extract the recovery with fastboot files zip and open a command prompt in the same folder of the adb and fastboot files (Shift + Right mouse)
I thought I did this part Im new to the asus rooting thing but I rooted my phone SGS|| with no problems

bradackman said:
I guess I'm dumb and don't understand this
2) Extract the recovery with fastboot files zip and open a command prompt in the same folder of the adb and fastboot files (Shift + Right mouse)
I thought I did this part Im new to the asus rooting thing but I rooted my phone SGS|| with no problems
Click to expand...
Click to collapse
here is a bigger pic

bradackman said:
awesome pic lol
ok thanks for the advise I just want to blow this one up too
Click to expand...
Click to collapse
I instantly believe you on this one!

OK so if it can't load it, that generally means it can't find it. Your command prompt says you were in root of C drive. Is that where you put the blob file?
Sent from my ASUS Transformer Pad TF300T using xda app-developers app

funnel71 said:
OK so if it can't load it, that generally means it can't find it. Your command prompt says you were in root of C drive. Is that where you put the blob file?
Sent from my ASUS Transformer Pad TF300T using xda app-developers app
Click to expand...
Click to collapse
yes here is a pic of it what do you think Im doing wrong ?

I got it, it had to be opened in the c:\ drive not in the fast-boot folder WTF its not really clear on that point on how to put the files where they belong thanks for everyone's help.

now the problem is getting into the recovery it just sits there it says booting recovery kernel image how long will it take to get there any help would be great.

bradackman said:
now the problem is getting into the recovery it just sits there it says booting recovery kernel image how long will it take to get there any help would be great.
Click to expand...
Click to collapse
I used the cwm recovery so I can't speak for others, but mine opens in about 5 seconds after selecting the RCK selection. Remember you need to upgrade to jb before you try using the jb recovery or it will not work.
Sent from my ASUS Transformer Pad TF300T using xda app-developers app

can I put the CWM one on here over TWRP one

bradackman said:
can I put the CWM one on here over TWRP one
Click to expand...
Click to collapse
That is not something I've done myself but all my reading indicates yes you can. It will just overwrite it. Again, make sure you install the recovery version which matches your version of android.
Sent from my ASUS Transformer Pad TF300T using xda app-developers app

bradackman said:
awesome pic lol
ok thanks for the advise I just want to blow this one up too
Click to expand...
Click to collapse
ralph075 said:
I instantly believe you on this one!
Click to expand...
Click to collapse
LOL!! + 1
Serioulsy OP, seems like you got a great return/replacement policy but you should explore a bit XDA forums and posts before trying to modify your new toy!
Good luck!

[APP] RecoverX - Q&A Official Thread

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
RecoverX - Q&A Thread​
Hello members !
Here is the Questions and Answer Thread for the RecoverX project. I've created this thread in order to help people who meets problems, bug, or who needs help for their device. So don't hesitate, I will try to help you as much as possible.
For further informations about this app, please go on the project thread (link bellow)
RecoverX Project Thread​
Enjoy

Reserved
Reserved for later use​

Reserved
Reserved for later use​

Download failed on xperia p, rooted stock ics rom, unlocked bootloader
Sent from my LT22i using Tapatalk 2

Download failed on xperia tx lt29i locked bl.
Download worked. But it won't load to recovery. Was this only intended for unlocked bl?
Sent from my LT29i using XDA Premium 4 mobile app

izuall187 said:
Download failed on xperia tx lt29i locked bl.
Download worked. But it won't load to recovery. Was this only intended for unlocked bl?
Sent from my LT29i using XDA Premium 4 mobile app
Click to expand...
Click to collapse
shtresatu said:
Download failed on xperia p, rooted stock ics rom, unlocked bootloader
Sent from my LT22i using Tapatalk 2
Click to expand...
Click to collapse
Depending of the device. I'm working on an update to add security steps in order to check if the recovery has been correctly installed.
Non-official custom recovery (especially for Sony devices) are not reliable and the installation may fail even if there RecoverX says it's complete.
Moreover, depending of the device, you have to hold volume +, or to tap the screen on boot. Details in the first post.
Try to go in /system/bin and tell me if there is a file called "recovery.tar".
Ps : on my device, i'm perfectly able to download unofficial cwm

File is present in /system/bin. Already tried other button combinations. I always end in bootloop.
Will wait for the update. Thanks, dev!
Sent from my LT29i using XDA Premium 4 mobile app

Does it worked for anyone else guys ???

This is interesting. I reflashed stock rom again via pc comp then installed the recovery using this and was succesful. But i lost it after flashing mount fiz for tx and selected no on getting stock recovery before reboot. Same thing happened when i flash the original recovery installer before. It always happens after the mount fix.
Sent from my LT29i using XDA Premium 4 mobile app

Great ! The app works well. For the issue of mount fix, it's due to the unofficial custom recovery. Do you know a stable custom recovery for your device ?

Oh yes please, boss! I would appreciate it. Thank you!
Sent from my LT29i using XDA Premium 4 mobile app

Well, I don't need this, but I just want to say thanks to @LEDelete, for make life easier for who need it:good:

izuall187 said:
Download failed on xperia tx lt29i locked bl.
Download worked. But it won't load to recovery. Was this only intended for unlocked bl?
Sent from my LT29i using XDA Premium 4 mobile app
Click to expand...
Click to collapse
shtresatu said:
Download failed on xperia p, rooted stock ics rom, unlocked bootloader
Sent from my LT22i using Tapatalk 2
Click to expand...
Click to collapse
Could you tell me when the download fail ? Is it when you click on the "Let's start" button on RecoverX startup or on the "Here we go" button ?
Thanks in advance,
LEDelete

RecoverX v1.0.1 beta has been published on Google Play. The "Download failed" bug should be solved so tell me what's going on

download worked after 3 attempts. must have been my connection. Will test update in a bit. Hit you up a report.
Download worked better. But still can't boot to recovery.

izuall187 said:
download worked after 3 attempts. must have been my connection. Will test update in a bit. Hit you up a report.
Download worked better. But still can't boot to recovery.
Click to expand...
Click to collapse
But which button did you clicked when the download failed ? "Let's start" button or "Here we go" button ?

LEDelete said:
But which button did you clicked when the download failed ? "Let's start" button or "Here we go" button ?
Click to expand...
Click to collapse
I was able to download the recovery. It also installed correctly on the right folders in /system. But i can't reboot to recovery. Always end up in bootloop and i tried various button combinations thougj i know that it should be multiple presses on vol -. Weird though is that it reads the busybox in xbin and not in bin folder. This is in chargemon file in cache.
Sent from my LT29i using XDA Premium 4 mobile app

Btw i just saw update 1.0.2 so i tried it. Still no luck. Maybe it's my busybox or the folder where it should be. Want me to post chargemon.log and chargemon.log.old, dev?
XT line users. Please refer to this thread: http://forum.xda-developers.com/showthread.php?t=2317432 and this will fix it.
Sent from my LT29i using XDA Premium 4 mobile app

Dude, i just tested the update with fresh install. Works better now for my TX! Thanks!
Sent from my LT29i using XDA Premium 4 mobile app

An update is available : RecoverX v1.1.1 beta
Enjoy