Hello guys,
I have an s4mini i9190 that somehow got bricked (no idea what the reason was). I was using a MM ResurrectionRemix Rom and one night shut down and never could make it work again.
I can access Download Mode (Odin apparently doesn't install things, it says it does, with no errors and yet the phone still has the bootloop of the RR animation).
I can access recovery but a bunch of errors come up, I share them with you in the attachments if you have any clue what it might be that's failing inside my phone. I have a beacon of hope that it might be something software-related and not hardware so I can just fix it easily :crying:. Through recovery I tried flashing cm13 but the huge red list appears.
The list goes like this:
Error opening data/lost+found
error opening data/data/com.google.android-gms/cache/sdsc
error opening data/[...]
over 100 red lines of errors X_X
I can certainly tell that the phone is not being able to mount /data which doesn't let me do anything to make it work apparently.
I think the Emmc are defect.
Any solution my friend?
Related
I recently was given an lg g3 that was supposed to have a damaged kernel, and it being my second g3 I thought I could simply flash a new kernel and OS no problem, WRONG! I worked on it for two days, I found that it has different screens with different crashes but all handled by a program called DEMIGOD CRASH HANDLER.I am able to access the recovery but nothing on there seems to do anything but reboot back to crash screen. I have been able to get win 10 to recognize the device (recent drivers already installed), but none of my linux distros will mount it! I have tried LGFlashtool, adb on CMD admin, i have tried many combinations of button pushes and battery pull/cord unplug, replug maneuvers! I am stuck! I have realized this problem may be bigger than I am able to handle, so I registered with lg and requested repair, I just hate giving up! So I am reaching out hoping someone has dealt with this problem before and knows how to take care of this mess before I raise the white flag! there isn't much back story on the device but as far as i know it has never been modified! LG Flash tool said "model check error" it seems like there is no esn imei or p# is available or downloaded. I have considered it being a case of misplaced data on the partitions, but I am not completely sure how to rearrange or reinstall the partition tables to make it work! Most of the threads that talked about this problem, the author gave up and sent it in. I also heard that this was a prevalent case in older lg models (g2, optimus, etc.) but was also a problem on nexus 6. Help please, frustrated and cold in Colorado.
still no results
To no avail I have tried everything! I have seen some changes but nothing that tells me that its fixed! I have tried qpst, but either I don't know how to run it or it wont connect properly, as a matter of fact I dont think it connects properly to any of the programs I run on it. It doesn't help that the only way the computer recognizes it is when it is on demigod mode.has anyone out there in android land had some experience or any idea of how to format the internal sd and start over from scratch?
shiftykidd said:
I recently was given an lg g3 that was supposed to have a damaged kernel, and it being my second g3 I thought I could simply flash a new kernel and OS no problem, WRONG! I worked on it for two days, I found that it has different screens with different crashes but all handled by a program called DEMIGOD CRASH HANDLER.I am able to access the recovery but nothing on there seems to do anything but reboot back to crash screen. I have been able to get win 10 to recognize the device (recent drivers already installed), but none of my linux distros will mount it! I have tried LGFlashtool, adb on CMD admin, i have tried many combinations of button pushes and battery pull/cord unplug, replug maneuvers! I am stuck! I have realized this problem may be bigger than I am able to handle, so I registered with lg and requested repair, I just hate giving up! So I am reaching out hoping someone has dealt with this problem before and knows how to take care of this mess before I raise the white flag! there isn't much back story on the device but as far as i know it has never been modified! LG Flash tool said "model check error" it seems like there is no esn imei or p# is available or downloaded. I have considered it being a case of misplaced data on the partitions, but I am not completely sure how to rearrange or reinstall the partition tables to make it work! Most of the threads that talked about this problem, the author gave up and sent it in. I also heard that this was a prevalent case in older lg models (g2, optimus, etc.) but was also a problem on nexus 6. Help please, frustrated and cold in Colorado.
Click to expand...
Click to collapse
You managed to fix it?
am facing the same issue.
Not yet i am thinking about just sending it back to lg. It's mixed up partitions, due to power surge from unauthorized power cords.
Do you have your phone rooted and with a custom recovery?
If yes,
Give this a try:
1.Enter recovery
2.Wipe data
3.Wipe cache
4.Wipe dalvic cache
5.Reboot
I've had the same problem with an LG L9 ii and this one fixed it.
So i really hope this will help. Inform me after doing this.
Greetings.
About five months ago I was able to access recovery but nothing was functional, now I cant even turn it on, if you left it on a different charger, kernal crash handler popped up half the time. Before it quit turning on the lg boot logo started going fuzzy, logic leads me to believe its a messed up Q C mother and the partitions are scrambled due to me using a non-oem charging cord and block, I also suspect the power button mounted to the back, on top of mother might have caused some hw problems. But those are just theories, it could simply be a bad battery!
Hi, this is causing me a lot of distress so any help would be greatly appreciated.
I have a D855 with TWRP and CloudyG3 2.5 on Optus (Aus). I haven't changed anything on the phone in a while, so I don't know what would have caused this. Yesterday I looked at my phone and it was stuck at the boot logo. Continual attempts to reboot haven't achieved anything. I've gone into recovery and found that the internal memory simply isn't being recognised and I'm getting errors like 'OS not found'. Sometimes it can see the SD and sometimes it can't. Half the time it's impossible to get it to power on at all without taking the battery out and in a few times. If anyone knows what I should do to resolve this I'd be very grateful.
Regards
When I try to restore to a backup I get
"E : Unable to mount '/data'
E : Unknown MTP message type: 1"
My daughter has been using this phone, but never backed her photos up. Now it won't boot and she is worried they are lost forever. I've been trying to help, but only seem to make things worse.
1. She never enabled USB debugging, or rooted it
2. She could not tell me whether she had allowed the OTA upgrades.
3. It got into a reboot loop a few days ago. It would start to boot, then say it was optimising a random number of apps (anything between 90 and 158) and then start over. Wileyfox tech support told me that this was due to an incompatibility between Cyanogen and the latest Facebook Update.
4. They sent me a link to the FOTA files with instructions how to progressively upgrade to Android 7 (TOS111B)
5. They couldn't tell me how to determine whether it was running CM12 or CM13 (I now realise that I could have looked at the log files in the recovery partition)
6. I therefore assumed that it was running CM12. I used their instructions to go into recovery and manually update from SD card to ZNH0EAS2NH from there to ZNH2KAS7EB and then to TOS111B
7. Fatally I did not reboot between updates. At the end I had the Wileyfox splash screen black on white, and then got an animation with it red on white. It then got stuck.
8. I then tried using fastboot to go back to the original version of the OS so I could start over. I found the fastboot image and I flashed the boot and system partitions.
9. Now on boot it either gets stuck on the black on white boot screen, or it displays it for a second and then turns off.
Can anyone help me? - I think my daughter will have a nervous breakdown if I don't find a way of recovering her photos. Recovering the photos is more important than unbricking the phone.
jerrytaff said:
My daughter has been using this phone, but never backed her photos up. Now it won't boot and she is worried they are lost forever. I've been trying to help, but only seem to make things worse.
1. She never enabled USB debugging, or rooted it
2. She could not tell me whether she had allowed the OTA upgrades.
3. It got into a reboot loop a few days ago. It would start to boot, then say it was optimising a random number of apps (anything between 90 and 158) and then start over. Wileyfox tech support told me that this was due to an incompatibility between Cyanogen and the latest Facebook Update.
4. They sent me a link to the FOTA files with instructions how to progressively upgrade to Android 7 (TOS111B)
5. They couldn't tell me how to determine whether it was running CM12 or CM13 (I now realise that I could have looked at the log files in the recovery partition)
6. I therefore assumed that it was running CM12. I used their instructions to go into recovery and manually update from SD card to ZNH0EAS2NH from there to ZNH2KAS7EB and then to TOS111B
7. Fatally I did not reboot between updates. At the end I had the Wileyfox splash screen black on white, and then got an animation with it red on white. It then got stuck.
8. I then tried using fastboot to go back to the original version of the OS so I could start over. I found the fastboot image and I flashed the boot and system partitions.
9. Now on boot it either gets stuck on the black on white boot screen, or it displays it for a second and then turns off.
Can anyone help me? - I think my daughter will have a nervous breakdown if I don't find a way of recovering her photos. Recovering the photos is more important than unbricking the phone.
Click to expand...
Click to collapse
Since posting this I have had a partial success. A more complete set of fastboot flashing using the TOS111B fastboot images has got me to a phone that boots. Many of the apps work. However...
a) I get an "unfortunately the process com.android.phone has stopped" appearing almost as fast as I can close the app making it very difficult to get anything off the phone. However, I did manage to set up a google sync to upload the photos.
b) my daughter now tells me that her SMS's are vital.... and the messaging app says " getting message" then closes down
c) I cannot enable developer setting to enable usb debug mode. I can get into the phone status page under settings. Repeated tapping on the android version brings up the nougat splash screen, but the 7 taps (or 700 for that matter) on build number does nothing whatsoever.
Does anyone have any ideas how to recover to a fully working system without doing a factory reset?
I suspect that the sms database would have gone when the cache was cleared. Can anyone confirm that to be the case before I spend any more time trying to recover them?
Hi Jerry ,
Exactly the same problem here. Could you tell me where you've found the TOS111B fastboot images?
Thx!
Have you tried booting into safe mode?
I think you do that by pressing and holding the volume down down button during reboot.
If you can manage that you may be able to dissable the apps that are causing the crash.
Hey Everyone,
I did a lot of reading in last 2 days on different threads in this forum. I find my case to be a little different. Can some experts advise me on what else can I try before concluding this to be a hardware error that cant be fixed.
Here is where I am, in details:
N7100 bought in 2012 and used extensively till 2015-16. I had installed Cyanogen Mod with TWRP 2.7.0.2 custom recovery on it. It was all good till one morning it wont go past the boot logo. This was a phone bought in india and the issue happened in Australia which I was visiting for a couple of weeks. I had left the phone on charging overnight and next morning it wont boot (could this be important, could this have fried the hardware?).
Anyways, I gave up on it in 2016. but last week my mom needed a phone, so I decided to check this phone again. Here is what I can or cannot do with the phone:
1. I can goto recovery mode but it says 0mb for internal storage and external SD card. The error log starts from 'Unable to find partition size for /boot, /recovery, /modem' and goes on into 'unable to mount efs, data, cache,system'
2. I can goto downloading mode and it reads the product name 'GT N7100', Custom Binary Download 'Yes 4 counts', current binary and system status as 'Custom'
3. I went into ODIN and flashed the N7100XXUFND3 PDA downloaded from sam mobile. It failed on first go and then I found a PIT file which I used and it went through fine. It takes 10-15 minutes but I get a BIG GREEN PASS on ODIN. I was very happy. But no good, it continues to be stuck on boot logo along with point 1 and 2. It still says internal storage 0mb. So where is is flashing the ROM.
I have read that if it is emmc failure or SDS, then in downloading mode you wont see the product name.
At this point, i have no idea what else to try. I am able to flash properly so I think I am in clear as far as hardware failure is concerned. What else can I try or do you think anything above is a good indication of a certain issue. Let me know your thoughts. Thanks
Hi i have bootloop problems on this device. When i do factory reset in recovery mode samsunf logo blinks as it wants to start system but it restarts. Then second time samsung logo doesnt even finish until i do factory reset then logo blinks again and restarts after some time.
The code is (reboot recovery cause is check_boot_mode recoverybootmodewithkey)
Block based ota
Ive tried to flash device multiple times with different stock roms with same results.
If i flash with oreo its the same error code but with addition when doing fastory reser something about some cache in first deletion and a number 0
In pie that code is not present which i assume that device is ment for pie. Both frp and oem are locked.
When i flash combination file its rpmb provisioned and rpmb fused 1. In z3x box there is no option to fix that. And that is strange because as i remember while i was doing repair on samsung s8 it was easy. Factory binary was there but not on this budget model which is strange. I even tried to force error so it triggers emergency recovery mode for smart switch but smart switch is just aweful. I dont even get recognition in that program. It shows as unsuppported model. I reinstalled drivers as well it just doesnt work. Now i would be glad and it would be awesome to get into fastboot mode just so i write down commands. Adb sideload doesnt have those options. Since i understood adb and fastboot for me its number one solution for everything. But how the hell am i supposed to get into fastboot on this model. Im pretty sure block based ota is sign that its blocked becuase of oem unlock aka locked bootloader. Its a friends phone and i tell people dont do stuff if you dot know ehat you are doing. But even locked bootloaders and frp locked are fixable. Especially with multiple brains on XDA and GSMforums.
Does anybody have any solutuon to this problem because this is some kind of new security method which was not present on like 2 years before.
P. S Is there any combination out there made out of Pie?
I fixed the issue. Front camera was defected. Some type of short circuit. Main camera auto focus mechanism also defected. It works allright as soon you detach all cameras. The only problem which i have with this device is that Samsung is using same concept as HTC. One camera defected all cameras not working. This is new from Samsung because in past when one camera brakes camera app still works. Autofocus mechanism can break with fall of the phone. Its not an software issue!!!
i have a similar problem do find solution?
I recently tried to install a custom ROM in my samsung j6+ but halfway through it my PC turned off.
Then the problem starts i decided to reboot my phone but it shows this error "No command" " #Reboot recovery cause is [[check_bootmode]RebootRecoveryWithKey]#
Block-based OTA
Supported API: 3
# MANUAL MODE v1.0.0#
E:Failed to mount / cache: Invalid argument
The error message keeps appearing for just a fraction of a second then disappear and appear again
I tried to go to recovery mode but no luck i cant get to it
I drained the battery to turn off the device then go download mode but after get to it, it also keep restarting
help me please. thank you