Database Info

[Q] HELP!!!!!!!

Hi everyone, so I have alreadty posted some threads on different forums, but I hope I can get some *real* help in here
So here´s my case:
Dead miniUSB connector(phone)
Flashed(mein fault) wrong kernel
Can ONLY access default recovery.
NO RSD access}
This phone is not sold in my country
Nobody would fix it's dead connector
I have no other phone, nor I can afford yo buy a new one, this one *was* working perfectly (besides the dead usb plug) I can charge the battery with a universal charger,I can only upload software to it via standard-factory recovery.
Any chance to get it working again? for now it just boot-loops.

donlloreda said:
Hi everyone, so I have alreadty posted some threads on different forums, but I hope I can get some *real* help in here
So here´s my case:
Dead miniUSB connector(phone)
Flashed(mein fault) wrong kernel
Can ONLY access default recovery.
NO RSD access}
This phone is not sold in my country
Nobody would fix it's dead connector
I have no other phone, nor I can afford yo buy a new one, this one *was* working perfectly (besides the dead usb plug) I can charge the battery with a universal charger,I can only upload software to it via standard-factory recovery.
Any chance to get it working again? for now it just boot-loops.
Click to expand...
Click to collapse
Get a sdcard reader, stick it to your computer, copy a ROM zip that includes the right kernel for your sdcard (CM7 or any other that includes a kernel), put it back into your phone, reboot into recovery, install zip, wipe data/cache and dalvik cache then reboot and see if it works.
edit:
you can only acess STOCK recovery, then maybe you can try flashing the bootmenu first (http://forum.xda-developers.com/showthread.php?t=1196590&highlight=bootmenu) by copying to your sdcard too with a sdcard reader, flash it from stock recovery, reboot and see if the blue led blinks, if yes then press volume up/down, enter clockworkmod recovery and do the steps above.
if it does not work then im out of ideas.

donlloreda said:
Hi everyone, so I have alreadty posted some threads on different forums, but I hope I can get some *real* help in here
So here´s my case:
Dead miniUSB connector(phone)
Flashed(mein fault) wrong kernel
Can ONLY access default recovery.
NO RSD access}
This phone is not sold in my country
Nobody would fix it's dead connector
I have no other phone, nor I can afford yo buy a new one, this one *was* working perfectly (besides the dead usb plug) I can charge the battery with a universal charger,I can only upload software to it via standard-factory recovery.
Any chance to get it working again? for now it just boot-loops.
Click to expand...
Click to collapse
Why the hell would you mess with the phone if you know the usb port is dead??
Anyways, time to try to help. Get an sd card reader, put it in a flash drive, find a froyo kernel zip and rename it to update.zip and place it in the root directory of the sd card , put the memory card back into the phone, boot into stock recovery, wipe data/factory reset, wipe cache, apply update.zip
Get back to us on this one.

Darin_Ram said:
Why the hell would you mess with the phone if you know the usb port is dead??
Anyways, time to try to help. Get an sd card reader, put it in a flash drive, find a froyo kernel zip and rename it to update.zip and place it in the root directory of the sd card , put the memory card back into the phone, boot into stock recovery, wipe data/factory reset, wipe cache, apply update.zip
Get back to us on this one.
Click to expand...
Click to collapse
afaik milestone 2's stock recovery can't flash kernel or an entire custom ROM, you need clockworkmod 3 (provided by the custom bootmenu) or above for that purpose.

Darin_Ram said:
Why the hell would you mess with the phone if you know the usb port is dead??
Anyways, time to try to help. Get an sd card reader, put it in a flash drive, find a froyo kernel zip and rename it to update.zip and place it in the root directory of the sd card , put the memory card back into the phone, boot into stock recovery, wipe data/factory reset, wipe cache, apply update.zip
Get back to us on this one.
Click to expand...
Click to collapse
Stock recovery can`t flash custom zip files.
Gustavo_s said:
afaik milestone 2's stock recovery can't flash kernel or an entire custom ROM, you need clockworkmod 3 (provided by the custom bootmenu) or above for that purpose.
Click to expand...
Click to collapse
I think, that stock recovery can flash kernel and / or entire rom, as OTA updates are made, but zip must be signed with motorola private key ..

ZyrByt said:
Stock recovery can`t flash custom zip files.
I think, that stock recovery can flash kernel and / or entire rom, as OTA updates are made, but zip must be signed with motorola private key ..
Click to expand...
Click to collapse
yea, i think that he needs the bootmenu in order to flash a custom rom (cm9, cm7 or whatever), or like you said a signed update from motorola, but i dont think we can find one.
anyways, im afraid that even flashing the bootmenu he will not able to get into it.

The plug is standard plug. You can buy it in any electronic schop. Any mobile phone service can replace it. It's simple and fast. Only 5 pins to soldier.

I said rename it!
I said to download a kernel, rename it to update.zip and flash it! I'll also upload a picture of my stock recovery so you can see what to select.
{
"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"
}

Hello everybody, I have similar problem.
My Mile2 is bootlopping the Motorola logo, I tried flashing various stock roms by RSD lite without result. Also not to get into the stock recovery by pressing X and @. Is there any other way to go back to work?
Sorry my poor english..

Do you can get into recovery with ! symbol? in android 2.3 you must prec vol - and vol + at the same time to get in there. You can also try flas newest sbf. If you flash 2.3 before now you can't flash 2.2. (maby this is your problem)

[MOD][TEST] ART WhatsApp Fix 4.4

I happened on this post whilst trying to get some SystemUI.apk mods to take on ART:
http://forum.xda-developers.com/showthread.php?p=47604251#post47604251
I tried the modified libart.so file by @cernekee on my Moto X VZW Dev Ed (because a working phone needs to be broken fixed) and it seems to work. I've made a flashable file to remove the leftover WhatsApp parts and flash the new libart.so if you'd like to give it a go.
Steps to install:
1. Switch to ART. (You need to have stock SystemUI.apk and SystemUI.odex - see attached).
2. Flash zip in recovery
3. DO NOT WIPE DALVIK/CACHE
4. Reboot and profit reinstall WhatsApp from Play Store if needed.
As usual, make a backup first and please don't flash this if you are uncomfortable fixing a bootlooped phone!
{
"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"
}
If you screw up and wipe dalvik/cache, just flash the stock libart.so zip (attached) reboot then reflash the Mod.

Will this work on the brazilian firmware?

No clue. But this is a Nexus 5 libart.so and it's working on a Vzw Moto X so it most likely should. This isn't something I'd try with a locked bootloader though.

Just tried here and it's working perfeclty! Thank you!
I didn't even have to reinstall Whatsapp.
One question though: what happens if I try to wipe cache one day? Will it bootloop the phone?

MaKTaiL said:
Just tried here and it's working perfeclty! Thank you!
I didn't even have to reinstall Whatsapp.
One question though: what happens if I try to wipe cache one day? Will it bootloop the phone?
Click to expand...
Click to collapse
Yes but the fix is easy:
Hold power button (shut off) > boot to fastboot > boot to recovery > flash the stock libart.so > reboot > flash nexus 5 libart.so > reboot.
It has happened to me once so far lol.

question
i dont understand what do i have to flash , moto x libart, moto x stock libart , o systm ui odex ... can i help me a bit plx

bastianvy said:
i dont understand what do i have to flash , moto x libart, moto x stock libart , o systm ui odex ... can i help me a bit plx
Click to expand...
Click to collapse
Do you have root and custom recovery?

chaoslimits said:
Do you have root and custom recovery?
Click to expand...
Click to collapse
yes i do

bastianvy said:
yes i do
Click to expand...
Click to collapse
OK.
Make a backup of your phone.
Download all 3 zip files.
Enable ART if you have not done so already
Reboot and let Android optimize itself. Whatsapp should crash at this point.
Reboot into recovery and Flash Moto X_ART_Libart.so.zip
Do NOT wipe cache/dalvik and reboot.:fingers-crossed:
If your phone boots fine, launch Whatsapp. :victory:
If your phone boots but you have no status or notification bar, flash SystemUI_VZW_Odex_Stock.zip; a mod is breaking SystemUI.apk.
If your phone does not boot (most likely because you wiped cache/dalvik), shut it down (hold power button). Then boot into recovery via fastboot and flash Moto X_ART_Libart_Stock.so.zip.

chaoslimits said:
OK.
Make a backup of your phone.
Download all 3 zip files.
Enable ART if you have not done so already
Reboot and let Android optimize itself. Whatsapp should crash at this point.
Reboot into recovery and Flash Moto X_ART_Libart.so.zip
Do NOT wipe cache/dalvik and reboot.:fingers-crossed:
If your phone boots fine, launch Whatsapp. :victory:
If your phone boots but you have no status or notification bar, flash SystemUI_VZW_Odex_Stock.zip; a mod is breaking SystemUI.apk.
If your phone does not boot (most likely because you wiped cache/dalvik), shut it down (hold power button). Then boot into recovery via fastboot and flash Moto X_ART_Libart_Stock.so.zip.
Click to expand...
Click to collapse
thanks ^^, i will let u know how it goes to me, (sorry for my bad english)

is there a whatsapp fix for ART without flashing this file via recovery?
i've only root permissions on my 4.4 AT&T

P910iii said:
is there a whatsapp fix for ART without flashing this file via recovery?
i've only root permissions on my 4.4 AT&T
Click to expand...
Click to collapse
I would strongly advise against touching anything in /system/lib without having a backup via recovery. Don't do it.
Edit: It's especially dangerous if you mistakenly wipe dalvik/cache.

Thank you, i'll wait 4.4.2

Is there any way to flash this on a stock recovery or by any other means? I have 4.4 with stock recovery, SlapMyMoto root and MotoWPNoMo.

dicarli said:
Is there any way to flash this on a stock recovery or by any other means? I have 4.4 with stock recovery, SlapMyMoto root and MotoWPNoMo.
Click to expand...
Click to collapse
The new version of Whatsapp supports ART i guess.... Try it once...

Bricked Moto G XT1032?

My phone is hard-bricked:
I have a Moto G XT1032 GPE Convert with 4.4.4, the phone out of the blue just rebooted and doens't pass from the ''Google'' screen.
Try with the MotoTool convert again to a GPE, these errors appear:
{
"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"
}
When the phone reboot, doesn't pass from the screen with the Google Logo.
I Try restore to stock firmware.
I try flashing CM11 through recovery but show up errors like: ''e:unable to mount ' /cache'', ''e:unable to mount ' /system'', ''e:unable to mount the internal storage'' and in the end a FAILED error in red.
I can acess to the Bootloader, the Recovery, not the system.
Dont think my phone is lost, I can acess the Bootloader so,.. but i dont know what to do anymore, can someone help me with some guidance to bring back the phone to life?
sorry my bad english.

You only tried do flash system? Haven't you flashed anything before system?

kirmr said:
You only tried do flash system? Haven't you flashed anything before system?
Click to expand...
Click to collapse
That image is from MotoTool, when i try to convert again to GPE, the moden, bootloader etc flash just fine, until come to the part of flashing the system that error appears 3 times, then the process continues and the phone reboot, appears the screen with the Google Logo, the phone vibrate and that's it, the phone don't even go to the boot animation, get's stuck in the Google logo screen.

_Drifter_ said:
That image is from MotoTool, when i try to convert again to GPE, the moden, bootloader etc flash just fine, until come to the part of flashing the system that error appears 3 times, then the process continues and the phone reboot, appears the screen with the Google Logo, the phone vibrate and that's it, the phone don't even go to the boot animation, get's stuck in the Google logo screen.
Click to expand...
Click to collapse
Chupista, try this guide it worked for me in some occasions.
https://www.youtube.com/watch?v=laU6NQ0LxR0&list=PLB0RKQDFm9rQe5_SlE8zZwBPboy8nzQlf

_Drifter_ said:
My phone is hard-bricked:
I have a Moto G XT1032 GPE Convert with 4.4.4, the phone out of the blue just rebooted and doens't pass from the ''Google'' screen.
Try with the MotoTool convert again to a GPE, these errors appear:
When the phone reboot, doesn't pass from the screen with the Google Logo.
I Try restore to stock firmware.
I try flashing CM11 through recovery but show up errors like: ''e:unable to mount ' /cache'', ''e:unable to mount ' /system'', ''e:unable to mount the internal storage'' and in the end a FAILED error in red.
I can acess to the Bootloader, the Recovery, not the system.
Dont think my phone is lost, I can acess the Bootloader so,.. but i dont know what to do anymore, can someone help me with some guidance to bring back the phone to life?
sorry my bad english.
Click to expand...
Click to collapse
This is caused because you updated to 4.4.4 previously, and the partition table changed. When you tried to downgrade, the partition table didn't accept the old system image. Now you must wait for a 4.4.4 GPE image, that is the only thing that can unbrick your phone, since it will have the updated gpt.bin.

kirmr said:
Chupista, try this guide it worked for me in some occasions.
https://www.youtube.com/watch?v=laU6NQ0LxR0&list=PLB0RKQDFm9rQe5_SlE8zZwBPboy8nzQlf
Click to expand...
Click to collapse
Unfortunately didn't work. But thanks for the help.
tatazeuz said:
This is caused because you updated to 4.4.4 previously, and the partition table changed. When you tried to downgrade, the partition table didn't accept the old system image. Now you must wait for a 4.4.4 GPE image, that is the only thing that can unbrick your phone, since it will have the updated gpt.bin.
Click to expand...
Click to collapse
So... no idea when the Image is release it? Could be tomorrow, next week or month right? Theres really nothing i can do to reverse this?

Well, good luck mate
I'm sure you'll that fixed very soon.
If flashing original file through adb won't do the trick..
Can't do anything more to help u. Propz.

_Drifter_ said:
So... no idea when the Image is release it? Could be tomorrow, next week or month right? Theres really nothing i can do to reverse this?
Click to expand...
Click to collapse
I made a method to recover your phone for use! Sadly, you will only be able to use custom ROMs (at least until there's a 4.4.4 image)
Check it in my thread
http://forum.xda-developers.com/moto-g/help/recover-4-4-4-downgrade-brick-temporal-t2801946

Soft-- Bricked after Phone Died, Please Help.

Ive looked through all the bricked threads and elsewhere and nothing seems to match my problem.
{
"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"
}
S-off. As you can see its been awhile since I have messed with my phone so forgive me. I found something that had what I needed and was stable(until now) and stuck with it.
So I connected my phone to a friends charger and it wasnt charging and it died. I got it charged and booted it up and it ran fine for about 2 minutes then apps started stopping and it rebooted, it now does this over and over. I tried the battery reset. The last apps to crash are always google play services related so I tried to flash a gaaps zip in hboot.I tried uninstalling/deleting those apps, it still crashes. I tried to wipe and restore/install in twrp recovery(which it usually says is successful). Ive tried flashing RUUs in hboot they stop after the first reboot and boot normally instead of back to hboot. It wont connect to adb(I may have done something wrong there). But whatever I do it boots up exactly how it was before. If I delete/uninstall anything it comes back, if I add something anywhere other than the external sd it disappears.
Please help I cant afford a new phone right now.
Update: Without an sd card in the phone it wont reboot but all other things are the same, apps still crash, still cant do anything to recover.
Update: I tried another sd card and it prevents the reboot, but still wont flash anything in the bootloader.
Update: I formatted my sd card and it doesn't reboot with it in now, atleast not automatically, it reboots when certain apps are opened or randomly after a long period. Apps still crash and still no luck with any flashing or recovery. I tried clearing all app caches with titanium, no change.
I think the internal and system partitions may be corrupted and stuck as is after reboot, the weird thing is I can delete things or add things and the changes stay until reboot, then its back to its original state, is that possible?

Did you rename the RUU file to OP6BIMG.zip before placing it in sd card? And since you are s on u should use the RUU from this thread - http://forum.xda-developers.com/verizon-htc-one-m8/general/official-ruu1-55-605-2-t2883845
And if u think there is a problem with partitions download a 4.4.x ruu flash it on ur phone then boot into recovery and reset all data in phone. Remember in stock recovery u need to press vol and mayb power at same time(just press dont hold them to long).
You can flash the recovery from bootloader also, but remember it should be 4.4.x

piyushkohli97 said:
Did you rename the RUU file to OP6BIMG.zip before placing it in sd card? And since you are s on u should use the RUU from this thread - http://forum.xda-developers.com/verizon-htc-one-m8/general/official-ruu1-55-605-2-t2883845
And if u think there is a problem with partitions download a 4.4.x ruu flash it on ur phone then boot into recovery and reset all data in phone. Remember in stock recovery u need to press vol and mayb power at same time(just press dont hold them to long).
You can flash the recovery from bootloader also, but remember it should be 4.4.x
Click to expand...
Click to collapse
Im s-off usinf twrp 2.7 something. Ruu flash starts but at first reboot it just boots normally instead of back to the bootloader. I've flashed roms, ruus, nandroids, from both the bootloader and recovery nothing sticks. The phonereboots to identical to how it was dec6 no matter what I do, flashes, wipes, installs, deletions, everything goes back how it was after reboot.

Kane5581 said:
Im s-off usinf twrp 2.7 something. Ruu flash starts but at first reboot it just boots normally instead of back to the bootloader. I've flashed roms, ruus, nandroids, from both the bootloader and recovery nothing sticks. The phonereboots to identical to how it was dec6 no matter what I do, flashes, wipes, installs, deletions, everything goes back how it was after reboot.
Click to expand...
Click to collapse
So u keep the ruu or flash some ROM after that?
Have you tried different RUUs?
I also recommend flashing the firmware for whichever Android version you are using.
Try firmware from this link http://forum.xda-developers.com/verizon-htc-one-m8/development/wip-4-17-605-9-stock-resources-firmware-t3196906
Flash firmware after RUU flashing.
I recommend the latest ruu if you flash it u will not need to flash firmware.
In previous post I told you to reset your phone from stock recovery did you try that?

[Completed] Samsung Galaxy Note II stuck on bootloop

So, here's the full details. I tried to increase the ram of my Note II even if its kernel does not support swap because I saw a thread here that will help me increase my ram even if my kernel is not compatible with swap. It didn't work so I uninstalled all the apps required to do it (Swapper2, Terminal Emulator) then it suddenly restarts then goes bootloop. Then I installed a custom rom (CM 0.14) changed my kernel to AGNI but still, bootloop. Then I decided to go back to stockrom by flashing it through odin then still stuck on bootloop. I tried to wipe data/cache after flashing and this is what it showed me:
-- Wiping data...
Formatting /data...
E:failed to mount /efs (Invalid argument)
Formatting /cache...
Data wipe complete.
I followed the steps required to flash the stock rom but I'm still stuck on bootloop. Can you help me what to do? Thanks!

canega2596 said:
So, here's the full details. I tried to increase the ram of my Note II even if its kernel does not support swap because I saw a thread here that will help me increase my ram even if my kernel is not compatible with swap. It didn't work so I uninstalled all the apps required to do it (Swapper2, Terminal Emulator) then it suddenly restarts then goes bootloop. Then I installed a custom rom (CM 0.14) changed my kernel to AGNI but still, bootloop. Then I decided to go back to stockrom by flashing it through odin then still stuck on bootloop. I tried to wipe data/cache after flashing and this is what it showed me:
-- Wiping data...
Formatting /data...
E:failed to mount /efs (Invalid argument)
Formatting /cache...
Data wipe complete.
I followed the steps required to flash the stock rom but I'm still stuck on bootloop. Can you help me what to do? Thanks!
Click to expand...
Click to collapse
Greetings and welcome to xda, first can I ask if you have a back up of your efs folder ? I don't think you will need it but just in case. If you boot into download mode and connect to kies/smart switch and select emergency firmarew recovery you should be fine. It sounds like you need to install a pit file which this will do, alternatively you can just flash a stock rom through odin that contains a pit file or I think mskips toolkit has a pit file
Good Luck
Sawdoctor

sawdoctor said:
Greetings and welcome to xda, first can I ask if you have a back up of your efs folder ? I don't think you will need it but just in case. If you boot into download mode and connect to kies/smart switch and select emergency firmarew recovery you should be fine. It sounds like you need to install a pit file which this will do, alternatively you can just flash a stock rom through odin that contains a pit file or I think mskips toolkit has a pit file
Good Luck
Sawdoctor
Click to expand...
Click to collapse
Thanks for the response! Unfortunately I don't have any backup efs folder. Gonna try those 2 methods you mention and will reply here if something happens; thanks!

So, I've tried all the methods and none of them worked for me. This is what happened:
First, I tried to do emergency firmware recovery method but its stuck on connecting even after I updated to latest drivers. Some says that its skies problem I did the second option. I search for GT-N7100 pitfile on xda which is 3kb in size and flashed it using odin together with the md5 file and this is what it looks like.
{
"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"
}
The flashing process is completed. I wiped the data/cache as usual but same results. Did I do it wrong?

canega2596 said:
So, I've tried all the methods and none of them worked for me. This is what happened:
First, I tried to do emergency firmware recovery method but its stuck on connecting even after I updated to latest drivers. Some says that its skies problem I did the second option. I search for GT-N7100 pitfile on xda which is 3kb in size and flashed it using odin together with the md5 file and this is what it looks like.
The flashing process is completed. I wiped the data/cache as usual but same results. Did I do it wrong?
Click to expand...
Click to collapse
After flashing the pit file did you try flashing a stock rom through odin or kies emergency firmware recovery again ?

sawdoctor said:
After flashing the pit file did you try flashing a stock rom through odin or kies emergency firmware recovery again ?
Click to expand...
Click to collapse
Yes I did through odin only since kies always stuck at connecting then becomes unresponsive. And as I said, I flashed the pit file together with md5 from stock rom. Same results. I checked the version of pitfile which is the international one and I'm still stuck on bootloop.

canega2596 said:
Yes I did through odin only since kies always stuck at connecting then becomes unresponsive. And as I said, I flashed the pit file together with md5 from stock rom. Same results. I checked the version of pitfile which is the international one and I'm still stuck on bootloop.
Click to expand...
Click to collapse
If kies emergency firmware recovery and mskips toolkit do not work then I'm afraid I am out of ideas. If you ask in the note 2 forums here
http://forum.xda-developers.com/galaxy-note-2/help
Hopefully the experts there may be able to think of something
Hope you figure it out
Sawdoctor

I'm always redirected to wheretowatch.com whenever I click a link

So, after a lot of murmuring I finally identified the root of the problem: the efs. This guide helped me fixed the problem:
http://forum.xda-developers.com/galaxy-s3/general/how-to-fix-efailed-to-mount-efs-invalid-t2858056
After I input the command on ADB, what I did was wipe data/cache and mount/efs then reboot. This method fixed E: failed to mount /efs Invalid Argument error. Thanks for all the help!

canega2596 said:
So, after a lot of murmuring I finally identified the root of the problem: the efs. This guide helped me fixed the problem:
http://forum.xda-developers.com/galaxy-s3/general/how-to-fix-efailed-to-mount-efs-invalid-t2858056
After I input the command on ADB, what I did was wipe data/cache and mount/efs then reboot. This method fixed E: failed to mount /efs Invalid Argument error. Thanks for all the help!
Click to expand...
Click to collapse
Thats great news, I'm glad you fixed it so I'll close this up
Regards
Sawdoctor