So,after i failed to install Carbon Rom i got bootloop and i flashed Eu firmware and i can't open up wifi,i mean that toogle. I got the phone from italy,what should i do?
Wipe your phone throughly. I.e. Wipe /system /data /cache through recovery. And then reflash the firmware and you'll have your WiFi working as usual.
Yeah,i resolved that,but know the mobile data is not working...I have this problems..Now what i should do?... I am leaving in some hours in another country and i need 3G..Help me please..
Do the same mentioned in 2nd post, all you issues will be resolved.
As you said you're in other country, you might not have access to PC and assuming that you have a recovery installed on your phone. Backup your phone (in case to revert back if anything goes wrong). Do a factory test. Don't mess with system only wipe user data and cache only. Reboot your phone. It should with fine .
Just for your knowledge: Mostly 3G and WiFi issue occurs when a dirty flash is done.
Related
I was following a guide to root and flash a ROM for my LG Optimus V. I got to the step where I wipe data/factory reset, cache, and dalvik-cache, but I decided to continue the guide later and powered off my phone and ended up in fastboot. I got out of fastboot by installing the zip files for BACKside ROM from the recovery menu, so now my phone works but a few things are off like I can't receive calls, getting server errors on google play, and getting an error that com.phone.android stopped working. I'm not sure what to do next to resolve those issues.
Edit: I realized that before installing BACKside, I didn't wipe caches or format anything since I had done them before my phone went into fastboot. Does this make a difference and means I need to re-install BACKside (by wiping caches, formatting, and then flashing)?
flowerTea said:
I was following a guide to root and flash a ROM for my LG Optimus V. I got to the step where I wipe data/factory reset, cache, and dalvik-cache, but I decided to continue the guide later and powered off my phone and ended up in fastboot. I got out of fastboot by installing the zip files for BACKside ROM from the recovery menu, so now my phone works but a few things are off like I can't receive calls, getting server errors on google play, and getting an error that com.phone.android stopped working. I'm not sure what to do next to resolve those issues.
Edit: I realized that before installing BACKside, I didn't wipe caches or format anything since I had done them before my phone went into fastboot. Does this make a difference and means I need to re-install BACKside (by wiping caches, formatting, and then flashing)?
Click to expand...
Click to collapse
1)maybe the rom and ur baseband don't match
2) maybe bcoz u didn't wipe so ders problem
3) or the rom itself has prob
so do a full wipe including formatting system.
Last night I flash a custom kernel and then decided to wipe cache/davik but it froze mid-way, so I did a hard reboot back into recovery and to my surprise I can't mount cache and usb-otg and to make things worse, the sdcard is not recognized. I can boot into the rom but sdcard is still not recognized and there is no cellular service. Question is there anyway for me to fix this, I have data on the phone that is very important to me.
utstudent said:
Last night I flash a custom kernel and then decided to wipe cache/davik but it froze mid-way, so I did a hard reboot back into recovery and to my surprise I can't mount cache and usb-otg and to make things worse, the sdcard is not recognized. I can boot into the rom but sdcard is still not recognized and there is no cellular service. Question is there anyway for me to fix this, I have data on the phone that is very important to me.
Click to expand...
Click to collapse
Fastboot flash the cache.img from the factory image
somebody made a guide for getting your data back and fixing this issue on the nexus 5. It was posted in the n5 general section a day or so back.
The Wifi on my phone wasn't turning on, even after factory reset, so I reflashed stock ROM via Odin (v3.07)
I got stuck in a bootloop, and after factory reset via the stock recovery + wipe of cache partition, it was still stuck.
I then re-flashed the stock ROM. Still stuck.
Tried using Kies 3, with the firmware upgrade and installation tab. Said something about not supporting my phone when I was prompted to plug it in. (SM-G355H; Samsung Galaxy Core II Duos)
I then found an unofficial version of CWM v6 for my phone (there's no official support), and quickly flashed that (via Odin 3.09; which is what I use from this point on), forgetting that my phone was no longer rooted. I wiped davlik cache and data. Still stuck. Then I rooted my phone. Stuck.
Then I reflashed stock ROM (this time, I downloaded from another website) (to test my luck, I tried seeing if simply a factory reset and cache wipe would work. It did not) rooted my phone, and flashed CWM. Wiped davlik cache. Still stuck.
By the way, when I wipe davlik cache it says:
Warning: no file_contexts
E:unknown volume for path [/sd-ext]
Davlik Cache wiped.
Any ideas on what to do now? I can't send it to a manufacturer / repair store where I live. I'm thinking maybe I should untick Auto Reboot and/or F. Reset Time when flashing, use an earlier version of Odin or the ROM itself, or maybe there is something I can do with ADB? I'm not very familiar with it, but I'm more than willing to learn. I just need some direction...
Update: Flashed with Auto Reboot unticked. Still in bootloop.
Flashed with same ROM, different country. Still in bootloop.
Alright, I fixed it by using Kies, via firmware upgrade and installation. You have to ignore where it says that your device is not supported, and just leave it to download. If you get stuck on the setup screen like I did, try cache wipe + factory reset. If it doesn't work flash an earlier version of the firmware. You might be using the wrong region (It's not always your country), use Kies to check. When it tells you what pda/ modem / csc it wants to update the region will be in parentheses ( eg ACR). Use all of them possible
Hello i recently use SlimLP rom until suddenly it was stuck on boot loop . I thought that it must be the problem of the custom ROM and i try to flash other ROM but it seems that i can't proceed to the procedure of wipe data/factory reset because it kept restarting after i checked that option . wiping dalvik cache is fine though . I also did format/data on my solo attempt to fix it but still it won't work.After reading some forum I decided to flash stock firmware but it kept failing on Odin . anyone know what might be the problem of this ? Did I just hardbricked my tab to the point of can't be repaired ? thanks in advance
Try to delete everything in data manually through twrp file manager (Advanced->File Manager)
john99ap said:
Try to delete everything in data manually through twrp file manager (Advanced->File Manager)
Click to expand...
Click to collapse
Im using CWM recovery T.T
iqbaladeee said:
Im using CWM recovery T.T
Click to expand...
Click to collapse
Then, install the latest common twrp by Andi from here: http://andi34.github.io/recoveries_tab2.html
and try it (first try also to wipe data with twrp)
iqbaladeee said:
Hello i recently use SlimLP rom until suddenly it was stuck on boot loop . I thought that it must be the problem of the custom ROM and i try to flash other ROM but it seems that i can't proceed to the procedure of wipe data/factory reset because it kept restarting after i checked that option . wiping dalvik cache is fine though . I also did format/data on my solo attempt to fix it but still it won't work.After reading some forum I decided to flash stock firmware but it kept failing on Odin . anyone know what might be the problem of this ? Did I just hardbricked my tab to the point of can't be repaired ? thanks in advance
Click to expand...
Click to collapse
I can't change my rom, wipe / format doesn't work. Nothing changed after flashing with Odin.
16 GB Tab 2 have a known faulty EMMC (MAG2GA). It can happen, that your EMMC get “read only”, so you can’t perform any write actions (also you can’t format) anymore.
From the EMMC data sheet:
5.1.7 End of Life Management:
The end of device life time is defined when there is no more available reserved block for bad block management in the device. When the device reaches to end of its life time, device shall change its state to permanent write protection state. In this case, write operation is not allowed any more but read operation are still allowed.
But, reliability of the operation can not be guaranteed after end of life.
On a faulty EMMC firmware it happens a lot faster.
What are the symptoms?
Uninstalled apps and deleted files are back after a rebootFormating the storage doesn’t work (after reboot the old rom and apps are back)You can flash whatever you like via Odin - it showes “passed” but after reboot nothing changed (e.g. still no StockRom or still the old Recovery you had previously installed)… there might be some more, but only to mention some …
In most cases, the issue can be fixed by a EMMC firmware update, but you need someone who’s able to do it (possible via ISP, nothing you can do esylie at home yourself). In some bad cases you need to find someone who can replace your EMMC.
source: http://andi34.github.io/faq.html
Hello, thanks for your help.
It seems I bricked my galaxy s7 while trying to format the /data partition.
I installed TWRP 3.2 and a custom rom, and everything went smoothly until then.
I tried installing an audio mod which throwed a " can't mount /data" error, searching for solutions I read that formatting the data partition to fat and back to ext4 should solve the problem, I tried formatting it to fat with TWRP, however on the first try I got a message that it suceeded, followed by a message that /data could not be mounted, TWRP seemed to be still working (there was no reboot button or any other buttons, just a "working" bar). After giving the phone 3 hours I decided to restart it, now I can't access TWRP; it stays on it's "splashcreen", and of course the phone won't boot.
I'm having a rough time with this so I will appreciate it a lot if you can help me.
Thank you.
Boot to download mode, flash stock firmware using Odin, then retry the TWRP installation.
For wiping data, you have to make sure you use the wipe option that makes you type out 'yes' to wipe, the other factory wipe methods don't actually properly wipe the partition.
iirc you also then need to flash the dm no verity zip from the TWRP thread.
Bro you didn't have to do anything but just formating the phone in the first place. Aassuming you're on oreo , it happens to a lot of people and myself, after flashing a kernel twrp was unable to munt data, all i had to do is a data format in twrp that fixed the problem .