Hey guys, i just want to ask if it's possible to fix emmc corrupt in yp-g70? okay, so i took it to a technician because it is hardbricked, he was able to fix it however the problem is, he said that the emmc is corrupt and the its status now is "bootlooping" he resurrected the device but it's stuck in bootloop because emmc is corrupt, and he said there is no solution unless the emmc is replaced. so, is there any possible way to fix this? or roms that can fix the bootloop? any reply would be much appreciated.
sewel wolcott
any advice?
Have you tried to flash the stock ROM?
TheKryptonite said:
Have you tried to flash the stock ROM?
Click to expand...
Click to collapse
The device itself is still at the technician, he just updated me the status of my device, i'll try to flash the stock rom if it fixes the emmc problem. by the way, thanks for the reply sir!
TheKryptonite said:
Have you tried to flash the stock ROM?
Click to expand...
Click to collapse
It may need a little more than that. If that doesn't work, try this:
Boot to cwm
Wipe data
Wipe system
Wipe cache, and dalvik
Boot into download mode
Reflash stock
Sent from my Amazon Kindle Fire using Tapatalk 4 Beta
goldflame09 said:
It may need a little more than that. If that doesn't work, try this:
Boot to cwm
Wipe data
Wipe system
Wipe cache, and dalvik
Boot into download mode
Reflash stock
Sent from my Amazon Kindle Fire using Tapatalk 4 Beta
Click to expand...
Click to collapse
OK, sir, i'll try that when i have my device tomorrow. thanks!
hellfrozer said:
Hey guys, i just want to ask if it's possible to fix emmc corrupt in yp-g70? okay, so i took it to a technician because it is hardbricked, he was able to fix it however the problem is, he said that the emmc is corrupt and the its status now is "bootlooping" he resurrected the device but it's stuck in bootloop because emmc is corrupt, and he said there is no solution unless the emmc is replaced. so, is there any possible way to fix this? or roms that can fix the bootloop? any reply would be much appreciated.
Click to expand...
Click to collapse
If he means that there are bad blocks on the emmc, then he is right; your device will not be usable unless the board is replaced. The only other possible way to work around that would to be moving partitions around with fdisk, but there would still be unusable space on the storage chip.
Mevordel said:
If he means that there are bad blocks on the emmc, then he is right; your device will not be usable unless the board is replaced. The only other possible way to work around that would to be moving partitions around with fdisk, but there would still be unusable space on the storage chip.
Click to expand...
Click to collapse
OK, sir, but, if flash it with odin, with the stock rom and PIT files, and check re-partition, would it be able to fix the issue? or it's still unusable?
just askin' .
i still don't have my device, it's still in him (technician).
How'd this happen anyway?
hellfrozer said:
OK, sir, but, if flash it with odin, with the stock rom and PIT files, and check re-partition, would it be able to fix the issue? or it's still unusable?
just askin' .
i still don't have my device, it's still in him (technician).
Click to expand...
Click to collapse
If there are bad blocks, it means that the chip hardware itself is burnt out, so writing to it will not fix it.
TheKryptonite said:
How'd this happen anyway?
Click to expand...
Click to collapse
OK, so before my device was hardbricked. i was trying to install the PACMAN ROM, by the way, i was on CHIP ROM that time, i followed the procedure,unfortunately the installation was aborted. After so much frustration i deleted the "/emmc", i thought that would fix it, but because of my stupidity, i admit that. all of my files in internal was wiped out and it cannot mount the internal itself. so i flashed a rom using odin. However, with the blessing of Bad Luck Brian, odin got freezed, so i eject my device from my computer and then turned it off, after that it wont boot anymore. so, now, i decided to bring it to a technician to be repaired using JTAG because i dont have the proper resources to do the resurrection.
OK, so he [technician] said that he was able to resurrect it but somehow, it is bootlooping, because the emmc is corrupt.
and now i already have my device, i will try to do "fdisk" as what Sir Mervodel suggested to partition my internal.
Mevordel said:
If there are bad blocks, it means that the chip hardware itself is burnt out, so writing to it will not fix it.
Click to expand...
Click to collapse
OK, sir. but i will try the method of using "fdisk" that you suggested lately. i hope that'll fix it.
It's already fixed!
Hey guys, it's already fixed, maybe the technician misunderstood the problem, all i did was to boot into recovery and wipe cache then factory reset. it's already fixed now,
Anyway, thanks for all your response!
TheKryptonite
goldflame09
and especially Mevordel!
:cyclops:
hellfrozer said:
Hey guys, it's already fixed, maybe the technician misunderstood the problem, all i did was to boot into recovery and wipe cache then factory reset. it's already fixed now,
Anyway, thanks for all your response!
TheKryptonite
goldflame09
and especially Mevordel!
:cyclops:
Click to expand...
Click to collapse
Good thing it wasn't a hardware issue!
Make sure you're more careful this time around. I should know, lol.
TheKryptonite said:
Make sure you're more careful this time around. I should know, lol.
Click to expand...
Click to collapse
:laugh: OK, dude. lesson learned. i'll try the PACMAN ROM later. Hope it's successful. :fingers-crossed:
Related
Hello, so I ran out of battery on my way home, when I got home I plugged the phone and went to sleep. Today when I woke up, I turned on the device, but it got stuck @ galaxy s3 boot animation, the animation you get before your ROM's boot animation kicks in, so I went to recovery and tried to recover one of my recoveries. it didn't help. I did a factory reset, it still was the same, stuck on galaxys3 boot animation. So I decided to flash stock samsung rom using ODIN. But now I'm stuck at the samsungs stock ROM boot animation, I tried factory reset couple of times but it didn't help.
Any idea what might be the issue, I have flashed this rom
Edit: Also the line "E: failed to mount /efs" is something to worry about when you boot into recovery?
So flashing via Odin works w/o errors?
Glebun said:
So flashing via Odin works w/o errors?
Click to expand...
Click to collapse
Yeah, when i flashed using odin, I didn't encounter any error, more one thing to mention, when I boot to recover I get
E: failed to mount /efs
Is that something to have concern about?
oh yes. do you have an efs backup? that's the first thing you should do before flashing anything. if yes, restore it. if not, send it to service
Glebun said:
oh yes. do you have an efs backup? that's the first thing you should do before flashing anything. if yes, restore it. if not, send it to service
Click to expand...
Click to collapse
Nope I got no efs backups... I had a custom ROM installed will it void my warranty?
alentor said:
Nope I got no efs backups... I had a custom ROM installed will it void my warranty?
Click to expand...
Click to collapse
Yes you will find that the vendor or Samsung refuse warranty .
Your option is to fight that as not relevant to your problem .
jje
JJEgan said:
Yes you will find that the vendor or Samsung refuse warranty .
Your option is to fight that as not relevant to your problem .
jje
Click to expand...
Click to collapse
You are kidding me, so basically if I didn't root my device, vendor/samsung wouldn't had a choice but to replace my device, but because of I did root my device, vendor/samsung will refuse to replace my device, am I correct?
Is there any other way to unbrick my device?
alentor said:
You are kidding me, so basically if I didn't root my device, vendor/samsung wouldn't had a choice but to replace my device, but because of I did root my device, vendor/samsung will refuse to replace my device, am I correct?
Click to expand...
Click to collapse
you are correct, in the EU you still can get lucky due to some regulations and you have to show that the root did not cause the problem, outside the EU I am not sure. The restriction of the internals of every device is not for nothing in place don't you think so? Otherwise manufacturers would get hundreds of complains because someone messed up something...
chrismast said:
you are correct, in the EU you still can get lucky due to some regulations and you have to show that the root did not cause the problem, outside the EU I am not sure. The restriction of the internals of every device is not for nothing in place don't you think so? Otherwise manufacturers would get hundreds of complains because someone messed up something...
Click to expand...
Click to collapse
Can yon give me a few examples on how can I prove that the ROOT didn't cause the problem? I belong to EU regolations.. Is there any other way to fix it?
Thank in advance.
alentor said:
Can yon give me a few examples on how can I prove that the ROOT didn't cause the problem? I belong to EU regolations.. Is there any other way to fix it?
Thank in advance.
Click to expand...
Click to collapse
I got not really an example but maybe this helps: Link
chrismast said:
I got not really an example but maybe this helps: Link
Click to expand...
Click to collapse
Hey, I just came back from my vendor, they say they can't fix it. Can I some how restore EFS? I have the Phones IMIE/S/N written, on the back of the phone, can I make a new efs folder/files? using this DATA?
Thank you!
EDIT: If I'll have to ship to samsung, do I have to talk with them first? or just find their ARMA address and ship there?
alentor said:
Hey, I just came back from my vendor, they say they can't fix it. Can I some how restore EFS? I have the Phones IMIE/S/N written, on the back of the phone, can I make a new efs folder/files? using this DATA?
Thank you!
EDIT: If I'll have to ship to samsung, do I have to talk with them first? or just find their ARMA address and ship there?
Click to expand...
Click to collapse
Do you not have a local Samsung service centre ??
jje
JJEgan said:
Do you not have a local Samsung service centre ??
jje
Click to expand...
Click to collapse
I don't know.. I just sent an email to their support, asking if they have a samsung service center in my area..
But if they don't, can someone provide me with the details how to restore your lost EFS folder using ADB or at least try to?
Thank you!
alentor said:
I don't know.. I just sent an email to their support, asking if they have a samsung service center in my area..
But if they don't, can someone provide me with the details how to restore your lost EFS folder using ADB or at least try to?
Thank you!
Click to expand...
Click to collapse
If you do not have an EFS backup I guess it will be difficult to restore. Only solution then will be to send it in for service if I am not wrong.
chrismast said:
If you do not have an EFS backup I guess it will be difficult to restore. Only solution then will be to send it in for service if I am not wrong.
Click to expand...
Click to collapse
You are correct, it would be difficult to restore, or there is another option, make my cellphone not boot at all, so the vendor won't be able to check flash counter.. in that case the vendor won't have a choice but to replace the device.. got any suggestion how to brick your device so it won't boot at all? disconnect the cable while flashing?
alentor said:
You are correct, it would be difficult to restore, or there is another option, make my cellphone not boot at all, so the vendor won't be able to check flash counter.. in that case the vendor won't have a choice but to replace the device.. got any suggestion how to brick your device so it won't boot at all? disconnect the cable while flashing?
Click to expand...
Click to collapse
Not the correct forum/website to ask such a question.
alentor said:
You are correct, it would be difficult to restore, or there is another option, make my cellphone not boot at all, so the vendor won't be able to check flash counter.. in that case the vendor won't have a choice but to replace the device.. got any suggestion how to brick your device so it won't boot at all? disconnect the cable while flashing?
Click to expand...
Click to collapse
that would be warranty fraud , hence I don't think you will get an answer here.
Hi Everyone
One of the senior contributors on here has been helping me via pm but I don’t want to keep bothering him and it would probably help to open up this issue anyway.
In essence, I’ve been unable to flash a variety of ROMS suggested by my friend on my 5380i (CM7, Extremesis etc).
Although the ROMs themselves are fine (checked MD5 etc), they have been mainly failing with abort message status 7. I finally got the Extremesis to install properly but then the phone got stuck at the first Samsung Galaxy screen.
I’ve had no probs restoring to stock with Odin but then keep repeating the problem when I try to flash.
Throughout the recovery process I’ve noticed various error messages when trying to wipe data, format system etc. One is when attempting wipe data from CWM. I get E format _volume rfs format failed on /dev / Stl.11 and similar with wipe cache but Stl.10 instead.
I’ve done some research and understand that this could be due to a corrupted internal card. Can anyone confirm this with a possible solution for my model?
II also get another one when wiping the dalvik cache in CWM. It says "Unknown volume for path sd-ext" I guess that must be linked to external sd. I've reformatted this many times so don't know what else that could relate to.
Either way it seems that I am “corrupted” internally as well as externally.
I’d really be delighted to hear from anyone who ever got any ROM to work on this damn model.
Many thanks Simon
Flash multiformater and there select rfs and then clear data and cache and then mount system and flash extremiss rom or any stock based custom roms..if u want to flash cm roms then u have to also flash cm7 kernel and and make system to ext4 thru multiformater and then flash any cm7 rom
amolgosavi said:
Flash multiformater and there select rfs and then clear data and cache and then mount system and flash extremiss rom or any stock based custom roms..if u want to flash cm roms then u have to also flash cm7 kernel and and make system to ext4 thru multiformater and then flash any cm7 rom
Click to expand...
Click to collapse
Hi again
Think I've tried most of those things without success. I'll try the multiformatter as suggested then see how I go.
Not at all optimistic as been here before many times!
Simon Sudbury said:
Hi again
Think I've tried most of those things without success. I'll try the multiformatter as suggested then see how I go.
Not at all optimistic as been here before many times!
Click to expand...
Click to collapse
Tried Extremesis again but phone still freezes on Samsung Galaxy opening screen!!
This is what I did:
1. Used multiformatter to set RFS and clear data and cache.
2. Used CWM to wipe data/factory reset.
3. Used CWM to wipe cache.
4. Wipe dalvik cache.
5. Mount system.
6. Format data, system and cache.
7. Installed Extremesis from zip.
I haven't tried CM7 as that involves the extra steps of cm kernel and mutiformatter to set to ext 4.
During this process I did note two error messages. First when wiping dalvik cache-unknown volume for path sd-ext and then when booting into CWM-Can't mount cache /recovery /latest log
Really confused and frustrated now.
Simon Sudbury said:
Tried Extremesis again but phone still freezes on Samsung Galaxy opening screen!!
This is what I did:
1. Used multiformatter to set RFS and clear data and cache.
2. Used CWM to wipe data/factory reset.
3. Used CWM to wipe cache.
4. Wipe dalvik cache.
5. Mount system.
6. Format data, system and cache.
7. Installed Extremesis from zip.
I haven't tried CM7 as that involves the extra steps of cm kernel and mutiformatter to set to ext 4.
During this process I did note two error messages. First when wiping dalvik cache-unknown volume for path sd-ext and then when booting into CWM-Can't mount cache /recovery /latest log
Really confused and frustrated now.
Click to expand...
Click to collapse
Further update
Tried flashing CM7 (kernel and multiformatter to set to ext4) but process aborting with status 7 error yet again.
Simon Sudbury said:
Further update
Tried flashing CM7 (kernel and multiformatter to set to ext4) but process aborting with status 7 error yet again.
Click to expand...
Click to collapse
Time to give up I guess.
Simon Sudbury said:
Time to give up I guess.
Click to expand...
Click to collapse
No help again. Zilch in fact. What a waste of time this forum is. It's like people are just making it up as they go along.
Simon Sudbury said:
No help again. Zilch in fact. What a waste of time this forum is. It's like people are just making it up as they go along.
Click to expand...
Click to collapse
How about, use odin and flash stock rom. Use all 5 files (pit file, pda, modem, csc boot)
After restars phone into recovery. Format system, data and cache. Mount everything, flash rom(redownload it just incase).
Stop complaining, theyre are over 100 android forums which you can ask for help, and this phone is just under 4 years old, every single problem has been encountered from atleast one of us, so it is somewhere in this forum, so look harder. Nobody gives a sh*t about this phone anymore and rightfully so.
Envy-X said:
How about, use odin and flash stock rom. Use all 5 files (pit file, pda, modem, csc boot)
After restars phone into recovery. Format system, data and cache. Mount everything, flash rom(redownload it just incase).
Stop complaining, theyre are over 100 android forums which you can ask for help, and this phone is just under 4 years old, every single problem has been encountered from atleast one of us, so it is somewhere in this forum, so look harder. Nobody gives a sh*t about this phone anymore and rightfully so.
Click to expand...
Click to collapse
I'm sure nobody gives a sh***t, aside from my good lady wife, who kindly bought it for me. I know it's ancient history, but doyouknowot? it's still being sold in stores so has a certain currency, so to speak.
I know there are millions of android forums and I've spent the best part of two weeks combing thru them!!!!
I've also been liaising with my Indian friend who hasn't been able to assist, despite being more affable and articulate than you (not difficult!).
I don't really have a problem restoring with Odin. The errors and freezes occur when trying to install Extremesis and CM7, 9, 10,11...............
Having said that, there may be an issue as I'm only using PDA the version of Odin I've been using, and although that gets me back to stock it may contribute to the subsequent errors when trying to install the ROM. I'll try the multiple files when restoring to stock but not confident.
I think you need to go back to your comics son.
Simon Sudbury said:
I'm sure nobody gives a sh***t, aside from my good lady wife, who kindly bought it for me. I know it's ancient history, but doyouknowot? it's still being sold in stores so has a certain currency, so to speak.
I know there are millions of android forums and I've spent the best part of two weeks combing thru them!!!!
I've also been liaising with my Indian friend who hasn't been able to assist, despite being more affable and articulate than you (not difficult!).
I don't really have a problem restoring with Odin. The errors and freezes occur when trying to install Extremesis and CM7, 9, 10,11...............
Having said that, there may be an issue as I'm only using PDA the version of Odin I've been using, and although that gets me back to stock it may contribute to the subsequent errors when trying to install the ROM. I'll try the multiple files when restoring to stock but not confident.
I think you need to go back to your comics son.
Click to expand...
Click to collapse
Sure. Good luck getting help fag.
Envy-X said:
Sure. Good luck getting help fag.
Click to expand...
Click to collapse
How old are u. No let me guess, somewhere between 12-13.
If you spent more time with your homework than the Dandy and Beano, then you might sound a bit more coherent (long word for you I guess).
Simon Sudbury said:
How old are u. No let me guess, somewhere between 12-13.
If you spent more time with your homework than the Dandy and Beano, then you might sound a bit more coherent (long word for you I guess).
Click to expand...
Click to collapse
Good one old man, im 17 with already more qualifications then you. Good luck with your phone.
Envy-X said:
Good one old man, im 17 with already more qualifications then you. Good luck with your phone.
Click to expand...
Click to collapse
If you had a brain instead of a lettuce you'd be dangerous boy.
Also have to say that "Dorby" is a ****hole and makes Mumbai seem like Las Vegas:laugh:
Simon Sudbury said:
If you had a brain instead of a lettuce you'd be dangerous boy.
Also have to say that "Dorby" is a ****hole and makes Mumbai seem like Las Vegas:laugh:
Click to expand...
Click to collapse
Holy sh*t, that's a terrible comeback. Seriously not gonna waste my time on you. Have fun throwing your phone into the bin.
Envy-X said:
Holy sh*t, that's a terrible comeback. Seriously not gonna waste my time on you. Have fun throwing your phone into the bin.
Click to expand...
Click to collapse
Hi Boy
Thought you'd like to know that I installed Cryinghshame 7 on my phone and what an enormous anti climax it was
Couldn't have been you who contributed to the code could it? Nah, you can't read or write can you:victory:
Simon Sudbury said:
Hi Boy
Thought you'd like to know that I installed Cryinghshame 7 on my phone and what an enormous anti climax it was
Couldn't have been you who contributed to the code could it? Nah, you can't read or write can you:victory:
Click to expand...
Click to collapse
Good logic, its not like i havent been reading and replying for the last 10 or so posts.
And are you sure you flashed 2.3.7? Or do you think its 4.2.2? Shall i tell you how to "activate" it?
Envy-X said:
Good logic, its not like i havent been reading and replying for the last 10 or so posts.
And are you sure you flashed 2.3.7? Or do you think its 4.2.2? Shall i tell you how to "activate" it?
Click to expand...
Click to collapse
Says 2.3.7 Android and kernel as 2.6.35.7 .
Simon Sudbury said:
Says 2.3.7 Android and kernel as 2.6.35.7 .
Click to expand...
Click to collapse
Shut up You retard.
I've just done a demolition job on you in the other thread so don't want to waste any more time here.
However I am curious why they tolerate imbeciles on here
Simon Sudbury said:
I've just done a demolition job on you in the other thread so don't want to waste any more time here.
However I am curious why they tolerate imbeciles on here
Click to expand...
Click to collapse
Lol you call that a demolition job ? Loooool you really are retarded [emoji23]
I wish I knew exactly what caused this to happen. I was using a Malaysk ROM and starting having the issues. I thought maybe it was the ROM so I downgraded back to the original ROM that came with my unit and I'm still having the same issues. I downgraded through system updates in settings.
I can get it to boot into recovery, but it's just a black screen with pulsating light blue lights on the side of my unit. I have a Joying RK3188 1024x600 with the touch buttons on the left side.
Also when the unit boots up I don't get the Android splash screen anymore, it's also black. The first sign of life is when the car logo screen pops up.
There have also been multiple cases where when I am using the unit the screen has turned black ( if the radio is playing it will continue to play though ) and I can't do anything on the screen. This has to be a related issue.
Does anyone have any idea whats going on here?
I appreciate any help I can get!
Anyone have any ideas?
ahfunaki said:
Anyone have any ideas?
Click to expand...
Click to collapse
Try reflashing both MCU and ROM.
Use USB method for recovery of brick unit.
Or try reflashing from GPS card by mimicking procedure as it should be done on screen working even if you don't see it (look for screenshots of recovery and try to perform needed actions - somewhere here was such hint for someone whose screen brightness was completely darked out and has to perform factory reset from recovery on the blind).
pa.ko said:
Try reflashing both MCU and ROM.
Use USB method for recovery of brick unit.
Or try reflashing from GPS card by mimicking procedure as it should be done on screen working even if you don't see it (look for screenshots of recovery and try to perform needed actions - somewhere here was such hint for someone whose screen brightness was completely darked out and has to perform factory reset from recovery on the blind).
Click to expand...
Click to collapse
What is USB method? Just load the files on to a flash drive?
And I've found a picture of the recovery menu and I've tried that multiple times with no success.
Thank you for your help!
pa.ko said:
Try reflashing both MCU and ROM.
Use USB method for recovery of brick unit.
Or try reflashing from GPS card by mimicking procedure as it should be done on screen working even if you don't see it (look for screenshots of recovery and try to perform needed actions - somewhere here was such hint for someone whose screen brightness was completely darked out and has to perform factory reset from recovery on the blind).
Click to expand...
Click to collapse
Putting the stock MCU and ROM on the GPS card fixed it! I did the update from the settings menu and it worked! I have recovery again! Thank you so much for the help!
I really want to install the custom ROM again, but I really don't want to keep having this issue though. Does anyone have any idea what is causing this to happen?
ahfunaki said:
Putting the stock MCU and ROM on the GPS card fixed it! I did the update from the settings menu and it worked! I have recovery again! Thank you so much for the help!
I really want to install the custom ROM again, but I really don't want to keep having this issue though. Does anyone have any idea what is causing this to happen?
Click to expand...
Click to collapse
I had bad experience with MCU v2.83
After some time it started to make touch screen not working, factory settings pass not recognising standard 126 etc.
After restart - all normal. Then for no reasons next day problems rrapear...
Reverting to stock v2.80 resolves issue. And Nalaysk ROM works with no prob.
So, if you upgraded MCU - that may be a reason.
If not, then maybe your ROM file was corrupted. Or your internal memory got corrupted somehow.
My prob with newer MCU, not working on cold morning first start but working after reset, points out that there is some HW related issue. With new version only though! Figure it out...
pa.ko said:
I had bad experience with MCU v2.83
After some time it started to make touch screen not working, factory settings pass not recognising standard 126 etc.
After restart - all normal. Then for no reasons next day problems rrapear...
Reverting to stock v2.80 resolves issue. And Nalaysk ROM works with no prob.
So, if you upgraded MCU - that may be a reason.
If not, then maybe your ROM file was corrupted. Or your internal memory got corrupted somehow.
My prob with newer MCU, not working on cold morning first start but working after reset, points out that there is some HW related issue. With new version only though! Figure it out...
Click to expand...
Click to collapse
I never updated the MCU so I'm really not sure what happened.
I'm actually don't mind using the stock ROM minus the fact I've already ran out of storage, is there anything I can do about that? So many things are working better for me now. Before I wasn't able to get an OBDII adapter to connect to torque and now it works perfect.
I'd love to go back to the Malaysk ROM but I just had so many issues...
Use link2sd to store your apps on an external sd card.
Sent from my SM-G920F using Tapatalk
ahfunaki said:
I never updated the MCU so I'm really not sure what happened.
I'm actually don't mind using the stock ROM minus the fact I've already ran out of storage, is there anything I can do about that? So many things are working better for me now. Before I wasn't able to get an OBDII adapter to connect to torque and now it works perfect.
I'd love to go back to the Malaysk ROM but I just had so many issues...
Click to expand...
Click to collapse
There is also another ROM, look for thread named Interesting ROM with FUSE support.
It is almost stock but with FUSE partitioning so you have all space for both sys app and data.
BTW your prob with OBD2 is known issue in Malaysk ROM if you enabled xposed BT module.
gk66 said:
Use link2sd to store your apps on an external sd card.
Sent from my SM-G920F using Tapatalk
Click to expand...
Click to collapse
I actually tried that, but I couldn't get it to run on boot. It didn't seem like it was working too well for me but maybe I was just doing something wrong.
pa.ko said:
There is also another ROM, look for thread named Interesting ROM with FUSE support.
It is almost stock but with FUSE partitioning so you have all space for both sys app and data.
BTW your prob with OBD2 is known issue in Malaysk ROM if you enabled xposed BT module.
Click to expand...
Click to collapse
I will look into this, thanks again!
ahfunaki said:
I actually tried that, but I couldn't get it to run on boot. It didn't seem like it was working too well for me but maybe I was just doing something wrong.!
Click to expand...
Click to collapse
You need to root your head unit. Use the root code from the wiki. Then install super su and give permissions to link2sd. Remember to properly partition sd card ss well
Sent from my SM-G920F using Tapatalk
gk66 said:
You need to root your head unit. Use the root code from the wiki. Then install super su and give permissions to link2sd. Remember to properly partition sd card ss well
Sent from my SM-G920F using Tapatalk
Click to expand...
Click to collapse
Thank you for the help, I ended up just installing that other rom with FUSE so everything is good now.
Really enjoying this thing...
ahfunaki said:
Putting the stock MCU and ROM on the GPS card fixed it! I did the update from the settings menu and it worked! I have recovery again! Thank you so much for the help!
I really want to install the custom ROM again, but I really don't want to keep having this issue though. Does anyone have any idea what is causing this to happen?
Click to expand...
Click to collapse
How did you doing this, did you do this from the system update menu? I have same problem but if I try your way, I only get a black screen.
MueKo said:
How did you doing this, did you do this from the system update menu? I have same problem but if I try your way, I only get a black screen.
Click to expand...
Click to collapse
Please check the solution here:
http://forum.xda-developers.com/showpost.php?p=66415327&postcount=3139
oscyp said:
Please check the solution here:
http://forum.xda-developers.com/showpost.php?p=66415327&postcount=3139
Click to expand...
Click to collapse
Thank you for your support. My problem was that my recovery image was damaged. I fixed it by reflashing the recovery image.
thx
I have the same problem now. I just went into recovery mode and installed update_4_4_4_FUSE_1024X600_RK3188_17_MAL_23_04_2016.
All was well until the Android loader image just sat there pulsing. The unit still had not started up after 40 mins of this logo being on screen.
Going into recovery mode just shows a black screen now. So my unit is effectively dead, or can it be rescued?
RS-TLS said:
I have the same problem now. I just went into recovery mode and installed update_4_4_4_FUSE_1024X600_RK3188_17_MAL_23_04_2016.
All was well until the Android loader image just sat there pulsing. The unit still had not started up after 40 mins of this logo being on screen.
Going into recovery mode just shows a black screen now. So my unit is effectively dead, or can it be rescued?
Click to expand...
Click to collapse
Anybody able to help me out here?
RS-TLS said:
Anybody able to help me out here?
Click to expand...
Click to collapse
Is it possible to start your device normal?
No. It just sits at the bootloader.
Sent from my SM-G928F using Tapatalk
Try in recovery mode to enter back in normal boot mode. It's difficult to explain in englisch. I had to pin a small needle into my radio and ca. 0,5 seconds before the LED are flashing, stop with pushing. When you stop pushing you must wait 5-10 second and see if you device boot up normal.
You have to try this often to find the correct moment. Thats how I entered back to normal boot mode.
A good day to all!
I have had an issue with my S6 edge (SM-G925F, Philippines Globe Carrier Version) for months now wherein it keeps restarting/crashing. The problem persists so randomly, sometimes multiple times a day or sometimes a day or two without it. I've already tried everything I could find in the internet, such as; deleting the cache in recovery, factory wiping the phone, and flashing the newest firmware i found for it on sammobile. Noting seemed to work. This is my last attempt in fixing the phone before I give up. I hope someone can give me good advice about this.
So nobody knows how to fix this? I don't care if it's a hardware problem i just wanna know
yh man,same problem...i cant even boot to the system..is your led flashing blue?
buzzsaw345 said:
So nobody knows how to fix this? I don't care if it's a hardware problem i just wanna know
Click to expand...
Click to collapse
Is the phone currently working?
It sounds like it could be the hardware failing, could be the emmc failing.
The only thing to suggest at this point is to wipe data/cache in recovery and flash a new firmware.
Or try a custom ROM. If it happens on the custom ROM also then it's possibly hardware.
pexluka said:
yh man,same problem...i cant even boot to the system..is your led flashing blue?
Click to expand...
Click to collapse
Mine can actually boot to the system but it always crashes after some time of use.
callumbr1 said:
Is the phone currently working?
It sounds like it could be the hardware failing, could be the emmc failing.
The only thing to suggest at this point is to wipe data/cache in recovery and flash a new firmware.
Or try a custom ROM. If it happens on the custom ROM also then it's possibly hardware.
Click to expand...
Click to collapse
That's EXACTLY what i was thinking although i did not know that was the name of the part. I was just thinking the memory module was maybe defective already. Dang it so the logic board should be replaced right? Because as far as I know the memory is soldered to the board and hard to remove by itself let alone replacing it.
I've already tried the wiping of data/cache and flashed the newest firmware using Odin but the problem still persists.
Also tried the custom ROM and I've tried a lot of them non actually boots to the system. Only flashing the official firmware allows me to boot to the system.
Thank you for the reply I will now just give up on this and just buy a OnePlus 3T.
buzzsaw345 said:
That's EXACTLY what i was thinking although i did not know that was the name of the part. I was just thinking the memory module was maybe defective already. Dang it so the logic board should be replaced right? Because as far as I know the memory is soldered to the board and hard to remove by itself let alone replacing it.
I've already tried the wiping of data/cache and flashed the newest firmware using Odin but the problem still persists.
Also tried the custom ROM and I've tried a lot of them non actually boots to the system. Only flashing the official firmware allows me to boot to the system.
Thank you for the reply I will now just give up on this and just buy a OnePlus 3T.
Click to expand...
Click to collapse
If it's the emmc then only way to fix is to replace the full motherboard, which isn't cheap.
It's a known problem on note 4. Emmc chip fails and eventually completely packs in.
Which custom Roms did you try? Carhd rom is a good one to try very reliable. Also when flashing a custom ROM it can take 20-30 minutes to boot into the system.
callumbr1 said:
If it's the emmc then only way to fix is to replace the full motherboard, which isn't cheap.
It's a known problem on note 4. Emmc chip fails and eventually completely packs in.
Which custom Roms did you try? Carhd rom is a good one to try very reliable. Also when flashing a custom ROM it can take 20-30 minutes to boot into the system.
Click to expand...
Click to collapse
True they are very expensive that's why I'd rather just buy a new phone. I just didn't want to give up such good hardware until I've tried everything.
Oh really? I wonder why that's the case
I actually forgot which ones already but I'm sure I tried Carhd and it didn't boot for more than an hour. But I'll go and check again just to be thorough.
buzzsaw345 said:
True they are very expensive that's why I'd rather just buy a new phone. I just didn't want to give up such good hardware until I've tried everything.
Oh really? I wonder why that's the case
I actually forgot which ones already but I'm sure I tried Carhd and it didn't boot for more than an hour. But I'll go and check again just to be thorough.
Click to expand...
Click to collapse
Yeah it's a shame really. I could be wrong that might not occur on yours. Normally when you get emmc failure, the phone will reboot to download mode and give you an error along the lines of emmc Write fail. And then keep repeating this.
3T is a good choice to go for if that's what you decide
callumbr1 said:
Yeah it's a shame really. I could be wrong that might not occur on yours. Normally when you get emmc failure, the phone will reboot to download mode and give you an error along the lines of emmc Write fail. And then keep repeating this.
3T is a good choice to go for if that's what you decide
Click to expand...
Click to collapse
It's alright I feel like whatever the hardware issue is it'll require the motherboard to be swapped out anyways. I can finally let the phone rest in peace haha thank you very much.
Yeah it's perfect for an android enthusiast. Already ordered one. Good bye and thanks again!
buzzsaw345 said:
It's alright I feel like whatever the hardware issue is it'll require the motherboard to be swapped out anyways. I can finally let the phone rest in peace haha thank you very much.
Yeah it's perfect for an android enthusiast. Already ordered one. Good bye and thanks again!
Click to expand...
Click to collapse
No problem buddy enjoy your one plus 3
thanks guys,i get the same problem,no rom wants to boot,i can install twrp and custom roms ut cant boot the rom..i once managed to oot to i think it was custom rom,but apps still kept crashing and i couldnt finish the welcoming screen
i got it with android m and apps were crashing all the time,and phone was restarting..
so motheroard it is?
pexluka said:
thanks guys,i get the same problem,no rom wants to boot,i can install twrp and custom roms ut cant boot the rom..i once managed to oot to i think it was custom rom,but apps still kept crashing and i couldnt finish the welcoming screen
i got it with android m and apps were crashing all the time,and phone was restarting..
so motheroard it is?
Click to expand...
Click to collapse
Wouldn't say it was motherboard yet. After you flash your rom you need to boot to recovery and wipe data/cache. This will fix the apps crashing
done,cant boot the system.
gave a visit to a few services,they sad around 50e would be reparation,but im student and now dont have cash for that ****..you have any other suggestions? i tried custom roms,at first magisk would always faild,last time it was ok but still couldnt boot
pexluka said:
done,cant boot the system.
gave a visit to a few services,they sad around 50e would be reparation,but im student and now dont have cash for that ****..you have any other suggestions? i tried custom roms,at first magisk would always faild,last time it was ok but still couldnt boot
Click to expand...
Click to collapse
Do not pay for it. Chances are if you can't fix it they can't either.
So have you tried flashing stock firmware?
What Android version do you have and what region? What's full model number g925?
Reduce the cpu frequencies to 1200-800mhz for big and little and userspace governor. This the only fix.
ok,so one more thing,on the glass back of the phone sits one imei that is not correct,and on the battery is another,which reports 64g version,while next to that number is printed 32gb and phone actually has 32gb lool
it is supposed to be g925f,but after i installed some custom rom,pc showed it as g925s? i think it is due to rom signing the wrong model number
the last thing i have done was yesterday,and it was flashing firmware through kies again.
and this is what i get :
s6 edge powered by android,followed by blue screen 'installing system update',and then recovery
in the recovery,i get this :
android recovery
samsung/zeroltexx/zerolte
7.0/NRD90M/G925FXXU5EQBG
user/release-keys
*recovery options*
No suppoer SINGLE-SKU
Supported API: 3
dm-verity error...
i realy dont know what else to try,and i am open to all suggestions..i have read that emmc storage is broken so this kind of problems can occur,so maybe service would do that?
thank you,i know this is confusing and boring problem
i tried with odin once more,and it failed at 25% instaing system update,then i restarted it and it got up to 32% and started erasing and it turned off..tf with this phone?? i guess its broken...
pexluka said:
i tried with odin once more,and it failed at 25% instaing system update,then i restarted it and it got up to 32% and started erasing and it turned off..tf with this phone?? i guess its broken...
Click to expand...
Click to collapse
https://www.sammobile.com/firmwares/galaxy-s6-edge/SM-G925F/VOD/download/G925FXXU5EQBG/125195/
Download and flash that firmwsre through odin before you try anything else. Let me know what happens.
I can tell you it's likely not emmc failure. For this you would get random reboots and it would reboot to download mode. There you would have an error emmc_write_error.
wowo thanks,i just gave up on that phone,i will try again,i will report back!
just one question,why vodafone?
oh,and i did have random reboots on android m,but it would reboot to optimizing android and boot
I'm left clueless here. I just can't get it to boot, no matter what ROM/Kernel i'd flash. It was originally running OOS 2.3.1 but flashing it now won't work anymore. It worked briefly for 1 hour with that AOSP 8.1 but then after trying to flash gapps it stuck again in a bootloop. Sometimes it also freezes and reboots while i am flashing sometimes. I really have no idea what should i do next, hope you can help me.
You need to give more information on which TWRP you have.
Did you upgrade the bootloader at one point ?
OOS 2 is the old one.
You should have upgraded to MM bootloader and the use a TWRP compatible.
If not, you'll have to follow the Mega Unbrick Guide...
Kéno40 said:
You need to give more information on which TWRP you have.
Did you upgrade the bootloader at one point ?
OOS 2 is the old one.
You should have upgraded to MM bootloader and the use a TWRP compatible.
If not, you'll have to follow the Mega Unbrick Guide...
Click to expand...
Click to collapse
I updated the bootloader like over a year ago or so. I also tried 2 different versions of TWRP, now i am using the latest one.
ALSO, very sorry it actually is OOS 3.1.4, not 2.3.1, i just typed briefly what i could remember, i haven't been using this phone for months now but i would like to give it to a relative so there's that. Hope you can help me out, i have no clue why is it acting up like that.
Have you ever think that could be the emmc problem that need to get replaced?
Our phone is old enough...
(just my thoughts btw)
Try to flash official ROM after having wiped everything
Kéno40 said:
Try to flash official ROM after having wiped everything
Click to expand...
Click to collapse
That's what i first tried, mentioned it in the main post.
yayakuya said:
Have you ever think that could be the emmc problem that need to get replaced?
Our phone is old enough...
(just my thoughts btw)
Click to expand...
Click to collapse
I don't know what to make of this, thought maybe anyone else encountered this problem and has a clue.
gabytzu338 said:
That's what i first tried, mentioned it in the main post.
Click to expand...
Click to collapse
You didn't mentionned you wiped everything : System, data, cache, Internal...
Then usb mount to pussh OOS 3 and flash
Kéno40 said:
You didn't mentionned you wiped everything : System, data, cache, Internal...
Then usb mount to pussh OOS 3 and flash
Click to expand...
Click to collapse
I don't really understand what you are trying to say. I did wipe everything and the only way to flash anything is through adb sideload anyway since the device is not recognized as storage while in TWRP. I think I am gonna give up on it, I was gonna sell it but I can't risk having it act up days/weeks after i sold it.