yashsingh1/xdaforums huggingface dataset:
[Galaxy S III Q&A, Help & Troubleshooting] baddooor1:
my phone is Samsung Galaxy SIII GT-I9300

can start the phone in download mode and in recovery mode.

When I start the phone in recovery mode i get the following errors:

E: failed to mount /efs (No such file or directory)

E: failed to mount /system (No such file or directory)

# Manual Mode#

E: failed to mount system (No such file or directory)

E: Can´t mount /system

E: failed to mount /cache (No such file or directory)

E: Can´t mount /cache/recovery/last_recovery

E: failed to mount /data (No such file or directory)

E: Can´t mount /data/log/recovery:log.txt

E: failed to mount /system (No such file or directory)

E: failed to mount /cache (No such file or directory)

E: Can´t mount /cache/recovery/log

E: Can´t open /cache/recovery/log

E: failed to mount /cache (No such file or directory)

E: Can´t mount /cache/recovery/last_log

E: Can´t open /cache/recovery/last_log

E: failed to mount /cache (No such file or directory)

E: Can´t mount /cache/recovery/last_install

E: Can´t open /cache/recovery/last_install

E: failed to mount /cache (No such file or directory)

I have tried to wipe cache partition and do a data/factory reset, but without any luck.

When i try to do a data/factory reset it says:

-- Wiping data...

Formatting /data...

E:format_volume: make_extf4s failed on /dev/block/mmcblk0p12

Formatting /cache...

E:format_volume: make_extf4s failed on /dev/block/mmcblk0p8

Data wipe complete

E:failed to mount /cache (Block device required)

E:Can´t mount /cache/recovery/log

E:Can´t open /cache/recovery/log

E:failed to mount /cache (Block device required)

E:Can´t mount /cache/recovery/last_log

E:Can´t open /cache/recovery/last_log

E:failed to mount /cache (Block device required)

E:Can´t mount /cache/recovery/last_install

E:Can´t open /cache/recovery/last_install

E:failed to mount /cache (Block device required)

I hope someone here can tell me what I can try out to fix it, since I have no clue what caused this or what I can do about it
[Galaxy S III Q&A, Help & Troubleshooting] mchagas:
same problem...

Any progress? I have the same problem with my GS3
[Galaxy S III Q&A, Help & Troubleshooting] GeekyDroid:
Does your device boot normally?
[Galaxy S III Q&A, Help & Troubleshooting] mchagas:
My S3 is stuck at samsung logo... when I try to get on recovery mode, it appears the same messages as described...
[Galaxy S III Q&A, Help & Troubleshooting] mchagas:
Image is inside the ZIP. I'm at work, could not do anything better.
[Galaxy S III Q&A, Help & Troubleshooting] GeekyDroid:
Seems like your partitions are messed up. Did you try to flash stock ROM through odin?
[Galaxy S III Q&A, Help & Troubleshooting] mchagas:
Yes, but no success... I get a error in the beggining of the process... I just don't remember the message exactly (maybe something related to NAND (?), I guess the preccess don't starts at all), and I haven't ODIN here to see the error... I tried wth diferent versions of ODIN, without success.

Everything started when my S3 started to shutdown ramdomly, I flashed it a stock rom and it worked for a week without so much problems, some reboots, but was fine.

Then it shutdown and got stuck at samsung logo... In recovery mode it showed me this screen... I'm new to ODIN, just don't know what to do next.
[Galaxy S III Q&A, Help & Troubleshooting] GeekyDroid:
Sorry, I also don't know how to help you further. I will do some research. Maybe I'll find something.
[Galaxy S III Q&A, Help & Troubleshooting] tallman43:
As suggested looks like your partitions are corrupt you can try the rescue firmware here >> http://xdaforums.com/showpost.php?p=30087735&postcount=6 << if not service recommended.:)
[Galaxy S III Q&A, Help & Troubleshooting] mchagas:
I'll try it when I get home!

Anything else I should do? Or just flash it?
[Galaxy S III Q&A, Help & Troubleshooting] tallman43:
It contains a pit file so follow the instructions exactly.;)
[Galaxy S III Q&A, Help & Troubleshooting] mchagas:
I forgot to mention, my S3 is from Brasil, any problem? May I use the files from the URL you sent me?
[Galaxy S III Q&A, Help & Troubleshooting] tallman43:
Mmm..Depends what model is it the Galaxy S3 I9300 international? if not no! Also if it is not this model maybe the reason your phone is messed up is if you have flashed anything from this forum!:crying:
[Galaxy S III Q&A, Help & Troubleshooting] mchagas:
No, I flashed a stock ROM for brazilians devices! And it worked for a week, after I flashed it

I don't know the S3 model exactly...

This is the tutorial I followed, it is in PT-BR and is designed for the brazilian model

http://www.smartzone.com.br/2013/12...d-4-3-oficial-do-brasil-para-o-galaxy-s3.html

May I use the PDA from this tuto and the others files from the URL you sent me?
[Galaxy S III Q&A, Help & Troubleshooting] mchagas:
When I try to flash the s3 again, this is what happens:

<ID:0/003> Added!!

<OSM> Enter CS for MD5..

<OSM> Check MD5.. Do not unplug the cable..

<OSM> Please wait..

<OSM> I9300UBUGNE1_I9300ZTOUGNE1_I9300UBUGNF1_HOME.tar.md5 is valid.

<OSM> Checking MD5 finished Sucessfully..

<OSM> Leave CS..

<ID:0/003> Odin v.3 engine (ID:3)..

<ID:0/003> File analysis..

<ID:0/003> SetupConnection..

<ID:0/003> Initialzation..

<ID:0/003> Get PIT for mapping..

<ID:0/003> Firmware update start..

<ID:0/003> sboot.bin

<ID:0/003> NAND Write Start!!

<ID:0/003>

<ID:0/003> Complete(Write) operation failed.

<ID:0/003> Added!!

<OSM> All threads completed. (succeed 0 / failed 1)

:crying:
[Galaxy S III Q&A, Help & Troubleshooting] GeekyDroid:
I guess you just have to flash it. :)
[Galaxy S III Q&A, Help & Troubleshooting] mchagas:
Nothing seems to work... tried some pit files, without success.

Starting to guess it's a eMMC problem

Any ideas?
[Galaxy S III Q&A, Help & Troubleshooting] Darke5tShad0w:
Yip as tallman43 says it sounds like this http://xdaforums.com/galaxy-s3/general/sudden-death-sds-dont-android-4-1-2-cwm-t2091045
[Galaxy S III Q&A, Help & Troubleshooting] Pascal06:
Hello,

I've got the same issue on a GT-S7710 (aka "Skomer") since I did a bad flashing.

I tried to flash again from the sdcard, but it is impossible. Lauching a file manager from sdcard is impossible too.

Concerning ADB, the phone is detected, but flashing is impossible. Odin doesn't detect the phone.

Anybody can help me ?
[Galaxy S III Q&A, Help & Troubleshooting] Darke5tShad0w:
Nope, everything here is for the i9300. Flash anything from here and it will ruin your phone further. You need to go into the threads for your model.
[G3 Q&A, Help & Troubleshooting] voldrix:
After rooting, and uninstalling a massive amount of lg bloatware, I decided to switch to the android runtime (ART) before I installed all my apps. Once it rebooted and compiled all the apps, the settings would no longer function. My guess is it compiled wrong. Perhaps due to the missing lg crap that it linked to.

With the settings not functioning, I could not use the phone really. Could not even get it to connect to my computer. So my only option was to try a factory reset. This just made things worse. The settings app would still not work, but now I can't even get past the error, because it has to load as part of the setup. It was functionally bust. I had to bring it back to verizon and they replaced it.

I want to use ART, so my question is this; Do the missing apps that settings refers to affect it's ability to compile? should I switch to ART before deleting bloatware? Has anyone used ART successfully, and if so, did you delete lg's crap first?
[G3 Q&A, Help & Troubleshooting] Pilz:
I used art for a while, but I stopped because in using xposed. I uninstalled a lot of apps and I had no issues. What model are you using?
[G3 Q&A, Help & Troubleshooting] voldrix:
Tried Again

Verizon model: VS985 4G

So I went at it again with my new phone. Seems to have worked this time. Everything running smoothly on ART.

The play store wouldn't download anything, but I realized that was a dependency issue. It needs download manager. Reinstalled that, and everything seems fine. Not sure what went wrong last time.

I am getting random shutdowns though. Frozen shutdowns, where power wont restore until the battery has been pulled. I don't know if the issue is related.
[G3 Q&A, Help & Troubleshooting] tehpud:
I had a bunch of freezes when I was running art. All requires a battery pull. I am back to dalvik and getting significantly better battery life and no more freezing.
[G3 Q&A, Help & Troubleshooting] Sparty73:
I'm currently running ART on my VS985. Also getting the random freezes. Battery life hit appears to be tied, at least for me, with the Phone.apk. The dialer barely ever works, and my battery graph shows its frozen butt to be a hog. Actually have to voice dial through Google Now to call anyone :silly:
[G3 Q&A, Help & Troubleshooting] slimc84:
http://www.androidcentral.com/verizon-lg-g3-has-problems-art-think-twice-switching-runtimes
[G3 Q&A, Help & Troubleshooting] tehpud:
Something tells me that ART is not worth the problems you are having and should just go back to Dalvik? :P
[G3 Q&A, Help & Troubleshooting] voldrix:
Problems not just in ART

So I did a factory reflash of my original firmware. This time I stuck with Dalvek to try to avoid problems. But Apps were downloading very slowly from the play store, so I went to settings, app manager, and cleared the data for the play store. Apps downloaded better. But after a reboot, the settings app wont work, crashes every time something tries to load it. And with that the case, I cannot even get it connected to my computer.

the last time this happened - not only to me - not even a factory reset fixed it.

at least it isn't shutting down randomly anymore... I guess.

This is by far the most buggy phone I've ever had. And the model I have, the VS985, is one that has yet to have the bootloader unlocked.

Anyone been able to fix a broken settings app without reflashing the whole rom?
[ONE Q&A, Help & Troubleshooting] stone1269:
Is there any way to root the Oneplus without unlocking the bootloader and wiping the device?
[ONE Q&A, Help & Troubleshooting] zephiK:
Just unlock the bootloader and root. You're making it too difficult for yourself, the whole point of the bootloader being locked is to prevent changes being made to the system.

Its like saying, you're going to break your windows to get into your house when you can just unlock the door.

Just unlock the bootloader and flash supersu for root.
[ONE Q&A, Help & Troubleshooting] The Jack of Clubs:
yes, just run fastboot boot recovery.img and flash the superuser zip there. dont listen to people that say "just unlock bootloader!" because you dont need to and it sets a tamper flag which can be used against you if you try to warranty.

---------- Post added at 05:27 PM ---------- Previous post was at 05:23 PM ----------

thats a terrible analogy. thats like saying "ill bulldoze this whole wall and then ill never need to unlock my door!"
[ONE Q&A, Help & Troubleshooting] stone1269:
I want to avoid unlocking the bootloader simply because I have everything set up on the phone the way I like, and do not want to wipe it. I know I should have rooted it before installing anything, but nothing I can do about that now....
[ONE Q&A, Help & Troubleshooting] stone1269:
---------- Post added at 05:27 PM ---------- Previous post was at 05:23 PM ----------

Thanks for the suggestion! I will give it a try.
[ONE Q&A, Help & Troubleshooting] RalphLauren:
I'm a bit lost here....

To root the phone with locked bootloader, man has to have an "exploit"...which is not discovered (yet) for OPO.

And now you are saying that the exploit and hence an unlocked bootloader is not needed and we can just push SuperSU into system via adb....

Please elaborate how it's possible?????
[ONE Q&A, Help & Troubleshooting] zephiK:
What he said. The OPO does not need a "exploit" to root the phone with a locked bootloader because you can unlock it simply by typing a command.

You can't flash SuperSU without having access to a custom recovery such as TWRP/CWR which requires a unlocked bootloader.
[ONE Q&A, Help & Troubleshooting] RalphLauren:
I think you mixing the things up.... I'm NOT talking that a man needs to have an exploit in order to unlock bootloader.

I'm wondering if OPO system (or better to say CM) designed in a such way that it can be indeed rooted without exploit and with still locked bootloader by simply pushing SuperSU.

That what I want to hear from [MENTION=411488]The Jack of Clubs[/MENTION].

Of course you can by simply booting into whatever recovery in adb. I do not need a custom recovery and never install it.
[ONE Q&A, Help & Troubleshooting] zephiK:
No you cannot root the phone without a exploit with a locked bootloader. If that was the case, then the OPO would not be Google certified for Google Apps.

Still need a unlocked bootloader.
[ONE Q&A, Help & Troubleshooting] RalphLauren:
That's exactly what I was reading and thinking for years.

But somehow, [MENTION=411488]The Jack of Clubs[/MENTION] got probably a different idea (referring to his post #3 : "yes, just run fastboot boot recovery.img and flash the superuser zip there. dont listen to people that say "just unlock bootloader!" because you dont need to and it sets a tamper flag which can be used against you if you try to warranty.")

That's why I got so exited and anxious to hear some explanation and elaboration from him!
[ONE Q&A, Help & Troubleshooting] The Jack of Clubs:
You do not need to unlock the bootloader to root. The locked bootloader only protects the kernel and recovery partitions. Do not run "fastboot oem unlock" and do not run "fastboot flash recovery recovery.img". Instead just run "fastboot boot recovery.img" and flash the supersu zip from there. I've done this already. I know because I'm writing this on my rooted and bootloader locked oneplus.
[ONE Q&A, Help & Troubleshooting] RalphLauren:
Thank you very much for some enlightening :)

I know about the recovery trick, always was doing this way and never bother with the custom one.

But the information about the rooting in a such way comes to the big surprise!

Well in this case I just hope it's not a flaw in CM build and it will stay this way and won't be fixed in next OTAs
[ONE Q&A, Help & Troubleshooting] Wisiwyg:
I did this... It works. Installed SuperSU using this method, I"m running Titanium Backup Pro, which requires root.
[ONE Q&A, Help & Troubleshooting] The Jack of Clubs:
having read and write access in an alternate environment and being able to load a kernel in untrusted space kind of negates the point of the locked bootloader. which is why on something like a nexus 5, you have to unlock to root. its a security measure to block alternative access and destroying data when tampered. the international/cyanogenmod version of the phone may be running a different version of the bootloader that is on the chinese/coloros phone. you do see a cyanogenmod logo when booting into fastboot. so cyanogen may have an alternative fastboot that gives you access like this so you can mod you phone.

as far as root goes, theres two parts, the su binary which has to be copied to the system partition, and the app that gives root permissions to apps (a sudo app). you can install supersu from the playstore https://play.google.com/store/apps/details?id=eu.chainfire.supersu&hl=en but it doesnt do anything without the su binary. so when you are in recovery, which gives you full write access to the system partition, you flash the superuser zip, which copies the su binary to the system partition.
[ONE Q&A, Help & Troubleshooting] stone1269:
I can confirm that this method definitely works. My Oneplus is rooted, I never had to unlock the bootloader and my data is safe. Thank you!
[ONE Q&A, Help & Troubleshooting] RalphLauren:
I really think that this thread has to go to the General from Q&A and has become sticky.

Also these findings has to be communicated to [MENTION=4883664]Chromium[/MENTION] in order to enhance his Guide
[ONE Q&A, Help & Troubleshooting] r8zer:
This method works, I can confirm also.

Fastboot boot recovery.img

then install the su.zip file

MAKE SURE YOU BACKUP WHILE YOU ARE IN TWRP!!
[ONE Q&A, Help & Troubleshooting] kirbo20:
Works perfectly. Thanks!
[ONE Q&A, Help & Troubleshooting] bajen:
Can you explain little more for a dummie ;) [MENTION=411488]The Jack of Clubs[/MENTION]

Thanks
[ONE Q&A, Help & Troubleshooting] reinerlee:
Isn't that we are able to lock the bootloader on OPO after we unlocked it ?
[ONE Q&A, Help & Troubleshooting] bajen:
I got it working now.
[ONE Q&A, Help & Troubleshooting] RalphLauren:
yes, you can
[ONE Q&A, Help & Troubleshooting] maj1016:
I used the guide at the link below to download:

slimmed version of the android sdk

twrp recovery

zip file for supersu,

and the universal ADB drivers.

http://xdaforums.com/showthread.php?t=2788632

I moved the twrp recovery image it to the "platform-tools folder located on your desktop within the android-sdk-windows folder." as instructed by the guide and named it recovery.img to keep it simple.

I downloaded the the superSU zipfile on my phone but you can also download it to your computer and push it to your phone using adb,

I opened the command prompt and went to the directory platform-tools there you just issue the command fastboot boot recovery.img or if you didn't rename the recovery file you downloaded type out the correct name.

give it 30 secs to boot up:

then from within twrp click install and find the zip file for superSU after that's done I read it was good to clear dalvik so I did then reboot.

worked perfect for me.

thanks again to [MENTION=411488]The Jack of Clubs[/MENTION] for showing that it could be downne without unlocking bootloader saved me a lot of time!:good:
[ONE Q&A, Help & Troubleshooting] RISHI RAJ:
Can someone guide me step wise step
[ONE Q&A, Help & Troubleshooting] playya:
what do you mean? all the tutorials is a step by step of what to do
[ONE Q&A, Help & Troubleshooting] RalphLauren:
more step-by step than in the post above yours (#23) can not be
[ONE Q&A, Help & Troubleshooting] RISHI RAJ:
ok,thanks
[ONE Q&A, Help & Troubleshooting] &roid:
Thank you...this works just fine. Thank you for sharing and clearing some things up here.
[ONE Q&A, Help & Troubleshooting] adanteny:
Great thread! thanks to all contributors!
[ONE Q&A, Help & Troubleshooting] Hullie NL:
I can also confirm that the method from The Jack of Clubs works.

I used the Toolkit made by Scumpi and used the option *boot twrp*

Have root and locked bootloader

So thanks [MENTION=411488]The Jack of Clubs[/MENTION] :good: was also looking for option to root and have locked bootloader.
[ONE Q&A, Help & Troubleshooting] vinas1:
How To: Root OnePlus One without modifying bootloader or anything else

Here are my notes for gaining root w/o flashing or unlocking the boot loader.

Thanks to Chromium and The Jack of Clubs for their concepts and documentation.

Download ADB and set up Tools

Download the full Android SDK here:

http://developer.android.com/sdk/index.html#download

(scroll to the bottom of the page -> DOWNLOAD FOR OTHER PLATFORMS -> SDK Tools Only)

Extract the android-sdk-windows zip to c:\android-sdk

Browse to C:\android-sdk\android-sdk-windows\

Double Click and run SDK Manager.exe

Uncheck everything except the Android SDK Tools and Android SDK Platform-tools

Hit the Install xx Packages button

Download Super SU and TWRP

Download the latest TWRP here:

http://techerrata.com/browse/twrp2/bacon

Extract the TWRP image file and save it as recovery.img in the following folder:

C:\android-sdk\android-sdk-windows\platform-tools

Download SuperSU here: http://download.chainfire.eu/452/SuperSU/UPDATE-SuperSU-v2.02.zip

Plug your phone into your computer and Copy SU zip to the phone... (anywhere will work)

Get your Phone into Fastboot

Reboot the phone in fastboot mode (hold volume up + power). You should get a cyanogen guy smiling at you, this indicates the phone is in fastboot mode.

Open a command prompt and do:

cd C:\android-sdk\android-sdk-windows\platform-tools

Type:

fastboot devices

NOTE: You should receive a list of connected devices, this means your PC is connected to your phone. If not, something is wrong with ADB or your USB driver and you need to fix it before you can proceed!

Boot with TWRP and Flash

If “fastboot devices” worked without error, type this:

fastboot boot recovery.img

After the recovery.img transfers, your phone reboots into TWRP. Hit “Install” and choose the SuperSU.zip from the location on your phone that you saved it to earlier.

Once flashing is done, reboot and enjoy root. No re-imaging or unlocking your bootloader necessary.
[ONE Q&A, Help & Troubleshooting] zaibrockstar:
Thanks for the Steps.

I am rooted now. Also got One more Question. I just wanted to try to make a Nandriod Backup using this method. ?

1) fastboot boot recovery.img

2) select Backup and Save.

3) Reboot and Copy the Backup to PC.

Will this work Just in Case I mess it up so that I can again get into TWRP and use the Nandriod for restoring it back ?

NOTE: Here I have a locked bootloader and default recovery.
[ONE Q&A, Help & Troubleshooting] vinas1:
It should work fine, as once you are in TWRP you can do what you want.
[ONE Q&A, Help & Troubleshooting] maj1016:
root after OTA

Did anyone get the OTA to 4.4 yet? Did root persist?
[ONE Q&A, Help & Troubleshooting] The Jack of Clubs:
Root is lost when you update to 4.4.4. You can not unlock using fastboot boot if you have not unlocked your bootloader. Towelroot doesn't work.

Time to unlock your bootloaders! As far as I know, you can still reset the tamper bit.
[ONE Q&A, Help & Troubleshooting] zephiK:
You can't.. the 4.4.4 update updated the bootloader causing the tamper bit zip to not work because its in a new location.

This method doesn't work anymore either because the boot.img is for 4.4.2, will need a update to 4.4.4 with the changes OP did. Be very careful on what you flash.
[ONE Q&A, Help & Troubleshooting] RalphLauren:
Wait a minute, just want to be sure that I understand you correct.

You are saying that CM closed the possibility to unlock bootloader on new 30O and we can not "fastboot oem unlock"????

And you suggest to unlock it while on 25R before accept OTA?

Please advise
[ONE Q&A, Help & Troubleshooting] zephiK:
You can still fastboot oem unlock, but there are contents in the bootloader that says whether or not you "tampered" with your device. Previously with the zip, we are able to change the values of this so OnePlus wouldn't know. Also it would cause problems unlocking the bootloader once it was locked. Read http://xdaforums.com/oneplus-one/development/mod-reset-unlock-tamper-bit-t2820912 for the full conceptual idea.
[ONE Q&A, Help & Troubleshooting] The Jack of Clubs:
Typo. I meant you can't root using the old method and no unlock.
[ONE Q&A, Help & Troubleshooting] RalphLauren:
Thank you very much , I know the concept, was reading this before.

Just when you read Jack's that one specific sentence:"You can not unlock using fastboot boot if you have not unlocked your bootloader.", it makes you wonder what the first "unlock" is referring to ?

That's why I asked, just double check.

---------- Post added at 12:37 AM ---------- Previous post was at 12:31 AM ----------

Great :)

Now I'm fine :)

Suppose such situation:

-Unlock bootloader on 25R

-Reset tamper flag

-Update to 30O

What we will have now?

1. New unlocked bootloader with no flag

or

2. New locked bootloader with no flag

0r

3. New unlocked bootloader with a flag
[ONE Q&A, Help & Troubleshooting] andresantos:
so there is no way to root the new ota update without unlocking boot loader? do you guys think someone will find a way soon?
[ONE Q&A, Help & Troubleshooting] Heisenberg:
You can install it with the stock recovery.

Transmitted via Bacon
[ONE Q&A, Help & Troubleshooting] RalphLauren:
I thought that The Jack of Clubs (post #35 ) said that you can not do it anymore....
[ONE Q&A, Help & Troubleshooting] Heisenberg:
I misread start you posted, sorry. No, there's no way unless you unlock your bootloader. Why not just unlock it? You don't lose anything by doing so (as long as you backup) and you don't gain anything to keeping it locked.

Transmitted via Bacon