Database Users

Someone just .. help :(

Ok so i was normally using my phone and it randomly just said UI system crashed and the homescreen and everything wouldnt show so i restarted the phone and then it was just stuck on the intro screen..
after waiting for 20 min of it doing that i went in recovery and formated system cache and all that and now it wont go past google..
i tried to go in MOUNT and mount system and data it works but it wont let me Mount the sdCard why is that? how do i fix this
-
Any help would be appreciated .

ronnyg12 said:
Ok so i was normally using my phone and it randomly just said UI system crashed and the homescreen and everything wouldnt show so i restarted the phone and then it was just stuck on the intro screen..
after waiting for 20 min of it doing that i went in recovery and formated system cache and all that and now it wont go past google..
i tried to go in MOUNT and mount system and data it works but it wont let me Mount the sdCard why is that? how do i fix this
-
Any help would be appreciated .
Click to expand...
Click to collapse
Do you have a custom recovery? If yes use adb to push a custom rom to the sdcard: adb push namerom.zip /sdcard/. If you have stock recovery try to get in fastbootmode and push a custom recovery (TWRP pr CWM) and do the above.
I assume you have root, if you don`t you have to reflash a factory image in fastbootmode from here https://developers.google.com/android/nexus/images#occam.

gee2012 said:
Do you have a custom recovery? If yes use adb to push a custom rom to the sdcard: adb push namerom.zip /sdcard/. If you have stock recovery try to get in fastbootmode and push a custom recovery (TWRP pr CWM) and do the above.
I assume you have root, if you don`t you have to reflash a factory image in fastbootmode from here https://developers.google.com/android/nexus/images#occam.
Click to expand...
Click to collapse
Yes my phone is rooted. and i do have a custom recovery (CWM) . and so i open CMD in my SDK file and say this line " adb push namerom.zip /sdcard/"?

ronnyg12 said:
Yes my phone is rooted. and i do have a custom recovery (CWM) . and so i open CMD in my SDK file and say this line " adb push namerom.zip /sdcard/"?
Click to expand...
Click to collapse
Yes, that`a all. Place the rom you want to push in the platform-tools folder though or adb will not find it. It`s best to open CMD with a right click and open as administrator.

gee2012 said:
Do you have a custom recovery? If yes use adb to push a custom rom to the sdcard: adb push namerom.zip /sdcard/. If you have stock recovery try to get in fastbootmode and push a custom recovery (TWRP pr CWM) and do the above.
I assume you have root, if you don`t you have to reflash a factory image in fastbootmode from here https://developers.google.com/android/nexus/images#occam.
Click to expand...
Click to collapse
Ok it worked. Really great help man thanks

ronnyg12 said:
Ok it worked. Really great help man thanks
Click to expand...
Click to collapse
Happy you fixed it mate :good:

[Q] Stuck in a bootloop, think EFS is corrupt - anyone know of a fix?

N900W8 - unlocked Canadian version
Long story short, phone's stuck in a bootloop.
I can get into Download/Recovery, but can't mount anything in recovery. I can connect via Odin, but Win7 doesn't see the phone (so I can't transfer files).
I have a feeling my EFS is ****ed, which is why it won't boot. Is there a way to fix this, considering my connectivity situation?
I'm coming from a GNEX, which is obviously much easier to deal with than the note 3.
Any help is (obviously) greatly appreciated.

In case anyone else has this problem, I figured out the solution.
1 - boot to custom recovery (TWRP).
2 - follow steps outlined here: http://forum.xda-developers.com/showthread.php?t=2471421
Using TWRP Terminal Command To Complete this evolution...
1. Reboot to recovery
2. Hit "Advanced" Select "Terminal Command"
3. Hit "Select" (lower right corner)..Do not select any specific folder, just hit select..
4. keyboard will open, type in the following commands, make sure you put the spaces and / where they need to be, it needs to look exactly as outlined..
mke2fs /dev/block/mmcblk0p12
Hit Go - The command will run. Clear the box, type the following command
mkdir /efs
Hit Go - The command will run. Clear the box, type the following command
mount -t ext4 /dev/block/mmcblk0p12 /efs
Hit Go - The command will run.
Click to expand...
Click to collapse
3 - reboot to recovery
4 - follow the steps outlined here: http://forum.xda-developers.com/showthread.php?p=47530627#post47530627
Download latest MJ4 firmware from SamMobile for the N900W8
Boot into custom recovery wipe System, Data, Cache, Dalvik
Boot into download mode and flash MJ4 via Odin (brings you back to stock)
Click to expand...
Click to collapse

n900w8
hi I have a samsung galaxy note 3 SM-N900W8
I lose my efs folder
My phone gets the bootloop
I can get download mod and recovery mod but the phone always rebooted (bootloop)
I'm trying all solution like
-fix boot loop .zip
-terminal commanded with TWRP
-flash it with a stock ROM ........
But no way my phone always bootloop
I think the problem about my efs folder
Can you give me efs folder N9020W8??
Please help ….
I’m sorry about bad English & thxxxxxxxxxxxxxxxxxxxxxxxxx a lot

Anyone know where I can get twrp for SM-G390W?
I am having the same problem as you are efs folders won’t mount and phone is stuck in bootloop. If anyone can help with this problem it would be greatly appreciated thx.

TWRP is twrp.me
Or the forum for your phone .

How to Fix Galaxy S2 i9100 e: failed to mount /efs (invalid urgument)

If you are hard core droid user, then you already know that a broken or corrupt efs partition can be your worst nightmare yet, causing all kinds of trouble, more so like having hard bricked device, not easy to troubleshoot. It so happened that my friend's S2 lost the baseband and IMEI got blank. Efs professional and Samsung Tools failed to repair the corrupt efs partition or restore data.
Then, I encountered this error in stock recovery. "E: failed to mount /efs (Invalid urgument)"
Tried upgrading the device from 2.3.3 to official jellybean 4.1.2 ROM in hope that a complete wipe would enhance the chances of troubleshooting the efs partition to recover the imei and baseband and hopefully get the network working again. I tried different Odin flashable ROMS but after Odin finished with no errors, device could not boot past the samsung boot logo, kept restarting frequently. I soon found that no ROM flash,kernels or CWM jigs could resolve this error. I dug up thorough the net but I could not find a working solution for my i9100.
So today am posting this solution in the hope to save many other users the agony.
NOTE: This solution worked on GS2 i9100, if you are having the same problem with another samsung device, the same could work but you MUST change the EFS mount point 'mmcblk0p...' part to match to your device.
Most Epic part; Repairing the bad EFS partition also fixed the Blank Imei and Unknown Baseband issue for GS2!!!!!
Now that's utterly spectacular!
Instructions:
Download and flash official firmware for your phone in odin. I flashed the i9100VJMS1 4.1.2 Jelly bean.
Flash a CWM recovery&root your device in recovery. For S2 I used PhilZ CWM.zip recovery which is root ready for your installed firmware.
Install ADB on your computer. See How to install ADB, Fastboot drivers the Easier way
Boot your device into recovery mode.
Connect your device to the PC via USB cable.
In CWM recovery Choose “mount and storage > mount /system” (If it indicates unmount/system, then leave it as that)
Open ADB command window&type:
Code:
adb shell
su
mke2fs /dev/block/mmcblk0p1
mount -w -t ext4 /dev/block/mmcblk0p1
reboot
NB. If you get this error: can't find /dev/block/mmcblk0p1 in /etc/fstab just reboot and cross your fingers that it works.
After you run the above adb commands your device should reboot all the way up&Voila u should be up and running! Celebrations!!!
You may find that your power key menu&lock screen are not working after this. Thus far, you shouldn't panic. You are probably stuck in factory mode like i was.
This post from XDA member Kunterk fixed that. http://www.forum.xda-developers.com/galaxy-s2/help/solved-official-jb-ls8-lock-screen-t2116497Here
If I provided any help to you, kindly hit that thanks button.
Happy G:victory::victory:king!!
UPDATE:
I have long since written a detailed post about this on my blog http://www.selftechgenius.com/?p=284

thank you

Many thanks.
Sent from my GT-I9100 using XDA Premium 4 mobile app

Omg Thank you Droidsan, I have had the same problem with my daughters S2 been searching all over and trying all sorts then came across this.
Simple and easy.
Phone now boots and works. Im so Grateful.
Only problem I have is the no service, which is how i ended up with nof efs folder in the first place after following a number of guides.
Thanks again Droidsan.

If this post helped you in any way, just HIT that THANKS BUTTON! instead of saying thank you.

TWRP boot loop

Hi, I was switching rom cuz of many errors and I stucked on TWRP. Im able to enter download mode and adb and internal storage via PC. Whenever Im trying to flash new ROM twrp just restarts. I search whole the forum and no one of guide work for me. Additional full wipe and hard reset doesnt remove previous system. When Im connecting to lg mobile flash he says that I have still OptimusROM. Please help me
@edit:
After a few hours I find a simple solution. If u got the same situation like me just lanuch adb via cmd and write "adb reboot fastboot". After u can restore stock with LG flash tool. Just be sure that u have .kdz file in the same direction.

Xematos said:
Hi, I was switching rom cuz of many errors and I stucked on TWRP. Im able to enter download mode and adb and internal storage via PC. Whenever Im trying to flash new ROM twrp just restarts. I search whole the forum and no one of guide work for me. Additional full wipe and hard reset doesnt remove previous system. When Im connecting to lg mobile flash he says that I have still OptimusROM. Please help me
@edit:
After a few hours I find a simple solution. If u got the same situation like me just lanuch adb via cmd and write "adb reboot fastboot". After u can restore stock with LG flash tool. Just be sure that u have .kdz file in the same direction.
Click to expand...
Click to collapse
Given what you're saying, I'm guessing you're using at least 1 f2fs partition in the custom rom.
This has caused TWRP to panic and reboot for a few people (myself included) when trying to reformat f2fs partitions. The only way to fix that is like you're doing, or wiping the affected partitions back to EXT4, then going back to f2fs if you REALLY want to use it. The reason that this would cause the reboots on install, is because one of the first things most roms do is format cache.

A6000 Plus stuck on Bootloader

I may or may not have TWRP installed. Because, it's stuck on the bootloader when it switches on. I can only get into fastboot. Not more than that. No more Recovery mode. All the tutorials I see online for flashing with QFIL is only for A6000 (not Plus). I have A6000 Plus. What do I have to get it back on the track?
I've searched on other topics about this. But, they're all for A6000. I don't wanna brick more. So, any help would be appreciated.

If u can enter into fast boot then flash the twrp
U can watch at YouTube about flashing twrp
If u cant flash the twrp or get into the twrp !!!
Then flash the stock ROM ...!!!

kamesh_kraken said:
I may or may not have TWRP installed. Because, it's stuck on the bootloader when it switches on. I can only get into fastboot. Not more than that. No more Recovery mode. All the tutorials I see online for flashing with QFIL is only for A6000 (not Plus). I have A6000 Plus. What do I have to get it back on the track?
I've searched on other topics about this. But, they're all for A6000. I don't wanna brick more. So, any help would be appreciated.
Click to expand...
Click to collapse
Most tutorials for A6000 work for the "Plus" variant and vice versa, so it might be worth checking them out.
Also if you had usb debugging on and can send commands to your device from ADB, you can boot into recovery by this command:
fastboot boot recovery xxxx.img
Where "xxxx" is the name of the recovery file which must be in the adb folder.
Feel free to ask if any query

StillrunsKK said:
Most tutorials for A6000 work for the "Plus" variant and vice versa, so it might be worth checking them out.
Also if you had usb debugging on and can send commands to your device from ADB, you can boot into recovery by this command:
fastboot boot recovery xxxx.img
Where "xxxx" is the name of the recovery file which must be in the adb folder.
Feel free to ask if any query
Click to expand...
Click to collapse
I was like why didn't I try this before.
You know what happened? The boot process on "Command Prompt" screen went fine. I heard the unplugging the device and replugging the device sound very well. But during all these process it stays on Fastboot mode forever.
I have the latest TWRP loaded for temporary boot process. (3.2.1)
Besides from that
I was finally able to flash with QFIL tool. But still stucks at Lenovo POWERED BY android logo. QCom Downloader didn't work. But QFIL tool did work. I was able to finally come over the "sahara error" by quickly clicking "Download" button after connecting the cable. Then it flashed all the files. Then it finished downloading. But then if I try to switch it on, it wouldn't boot. Still stucks at the screen that I mentioned earlier.

StillrunsKK said:
Most tutorials for A6000 work for the "Plus" variant and vice versa, so it might be worth checking them out.
Also if you had usb debugging on and can send commands to your device from ADB, you can boot into recovery by this command:
fastboot boot recovery xxxx.img
Where "xxxx" is the name of the recovery file which must be in the adb folder.
Feel free to ask if any query
Click to expand...
Click to collapse
Sorry!
I tried it with Stock Recovery of A6000 (not plus). It booted into recovery.
Now, I can boot into TWRP. Looks like all the partitions are gone. How do I recover that?

StillrunsKK said:
Most tutorials for A6000 work for the "Plus" variant and vice versa, so it might be worth checking them out.
Also if you had usb debugging on and can send commands to your device from ADB, you can boot into recovery by this command:
fastboot boot recovery xxxx.img
Where "xxxx" is the name of the recovery file which must be in the adb folder.
Feel free to ask if any query
Click to expand...
Click to collapse
Sorry for previous post.
I tried to boot with Stock Recovery. It booted to recovery. But then I tried with TWRP again. It worked.
Looks like all the partitions are gone. How do I retain it?

kamesh_kraken said:
Sorry for previous post.
I tried to boot with Stock Recovery. It booted to recovery. But then I tried with TWRP again. It worked.
Looks like all the partitions are gone. How do I retain it?
Click to expand...
Click to collapse
Just flash a new ROM

StillrunsKK said:
Just flash a new ROM
Click to expand...
Click to collapse
Nope. Doesn't work. Tried that too. Ends up with Error 7 and Error 6. Modified Updater Scripts. Still same problem. Shows Failed to mount /system /data /cache.

jameeljb6 said:
If u can enter into fast boot then flash the twrp
U can watch at YouTube about flashing twrp
If u cant flash the twrp or get into the twrp !!!
Then flash the stock ROM ...!!!
Click to expand...
Click to collapse
Haha. I know how to do that. Thing is, I can't boot into System or Recovery normally even if I flash via Fastboot. I can only boot to recovery by "fastboot boot recovery.img" Then in TWRP there, I can't flash any roms as it shows Failed to mount /system /data /cache all the time. Tried fixing with "repair file system" option in TWRP. Still doesn't work.

kamesh_kraken said:
Nope. Doesn't work. Tried that too. Ends up with Error 7 and Error 6. Modified Updater Scripts. Still same problem. Shows Failed to mount /system /data /cache.
Click to expand...
Click to collapse
What os version were you previously upon? what TWRP version are you using?
Which ROM are you trying to flash?

StillrunsKK said:
What os version were you previously upon? what TWRP version are you using?
Which ROM are you trying to flash?
Click to expand...
Click to collapse
This one had 5.0.2. The latest stock ROM provided by Lenovo. I used both 3.2.1-0 and 3.1.0 both seems to provide same "Failed to mount /system /data /cache" error. Even stock recovery shows that.
Trying to flash RR 5.8.5

kamesh_kraken said:
This one had 5.0.2. The latest stock ROM provided by Lenovo. I used both 3.2.1-0 and 3.1.0 both seems to provide same "Failed to mount /system /data /cache" error. Even stock recovery shows that.
Trying to flash RR 5.8.5
Click to expand...
Click to collapse
Use the TWRP provided in the RR thread.
Wipe everything except MicroSD, if it shows any error while wiping, repair the partition in which the error arises and then wipe. After that flash the HEX firmware in RR thread and then flash ROM.
(Side Question : how did you land up in this situation?)

StillrunsKK said:
Use the TWRP provided in the RR thread.
Wipe everything except MicroSD, if it shows any error while wiping, repair the partition in which the error arises and then wipe. After that flash the HEX firmware in RR thread and then flash ROM.
(Side Question : how did you land up in this situation?)
Click to expand...
Click to collapse
The TWRP I mentioned 3.1.0 was obtained from RR forum only where dev mentions "F2FS" support. It does show the same error that I mentioned earlier. I did repair, resize, format, change file system. What ever I do, I always get the mount error on 3 partitions. Can't flash any ROMs either. Shows that error 7 and 6. I even deleted the assert line. It would only land me on error 6. I even googled and tried to get rid of that error. But after the error 6 or 7, it shows the same "mount failed".
Not my device. One of my client's. Received as not working.