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
Related
I've had the phone for around 6 months, rooted it back in Feb or something.
Started having problems freezing and restarting a few weeks ago, has probably only done this only a handful of times, until this morning...
Phone locked up and restarted then started loading the splash screen directly after the samsung galaxy sII screen and got stuck in an infinite cycle. It doesn't vibrate when turned on and no buttons work the only means of turning it off when in the loop is pulling the battery.
I've searched this topic but all I can find are ppl that have un-rooted phones or ppl that just rooted their phones. I can get into recovery mode but don't know what to do after that... help!
oldblue05 said:
I've had the phone for around 6 months, rooted it back in Feb or something.
Started having problems freezing and restarting a few weeks ago, has probably only done this only a handful of times, until this morning...
Phone locked up and restarted then started loading the splash screen directly after the samsung galaxy sII screen and got stuck in an infinite cycle. It doesn't vibrate when turned on and no buttons work the only means of turning it off when in the loop is pulling the battery.
I've searched this topic but all I can find are ppl that have un-rooted phones or ppl that just rooted their phones. I can get into recovery mode but don't know what to do after that... help!
Click to expand...
Click to collapse
If you aren't on stock ics try a wipe
Sent from my SGH-I777
122ninjas said:
If you aren't on stock ics try a wipe
Sent from my SGH-I777
Click to expand...
Click to collapse
Could you elaborate on that?
oldblue05 said:
Could you elaborate on that?
Click to expand...
Click to collapse
Are you on the ics update that was sent over kies or are you on GB/rom
Sent from my SGH-I777
talk, benguie
I honestly don't know, I saw the update awhile back and wasn't on wifi so I didn't update it. Then heard on the offroad forum that I frequent that some were having problems with the update so I never actively seeked it out to install it and never saw it pop up again but I do update often so it automatically updates then most likely. I'm pretty savvy with electronics but don't really know any of the lingo yall use in these forums so please go light on it lol
oldblue05 said:
I honestly don't know, I saw the update awhile back and wasn't on wifi so I didn't update it. Then heard on the offroad forum that I frequent that some were having problems with the update so I never actively seeked it out to install it and never saw it pop up again but I do update often so it automatically updates then most likely. I'm pretty savvy with electronics but don't really know any of the lingo yall use in these forums so please go light on it lol
Click to expand...
Click to collapse
Hit about phone and tell me all the info please
Sent from my SGH-I777
miers CD Sura
I thought I listed all the info needed, what else are you looking for? It's a Galaxy SII, when I get to recovery mode at the top of the screen is: CWMR Touch v5.5.0.4 other than that I'll need more specifics as to what info you need.
oldblue05 said:
I thought I listed all the info needed, what else are you looking for? It's a Galaxy SII, when I get to recovery mode at the top of the screen is: CWMR Touch v5.5.0.4 other than that I'll need more specifics as to what info you need.
Click to expand...
Click to collapse
go into CWM, wipe cache and dalvik cache(under advanced) and fix permissions, also under andvanced i believe.
If that doesnt help, might have to wipe data.
oldblue05 said:
I thought I listed all the info needed, what else are you looking for? It's a Galaxy SII, when I get to recovery mode at the top of the screen is: CWMR Touch v5.5.0.4 other than that I'll need more specifics as to what info you need.
Click to expand...
Click to collapse
MotoMudder77 said:
go into CWM, wipe cache and dalvik cache(under advanced) and fix permissions, also under andvanced i believe.
If that doesnt help, might have to wipe data.
Click to expand...
Click to collapse
I want to make sure you don't brick your phone with the emmc bug. On stock ics if you wipe you can brick your phome
Sent from my SGH-I777
I did what you said and to no change other than the samsung logo being listed longer while it loaded, splash screen appeared and went into the loop.
oldblue05 said:
I did what you said and to no change other than the samsung logo being listed longer while it loaded, splash screen appeared and went into the loop.
Click to expand...
Click to collapse
The only thing left to try would be to use factory reset in cwm. If that doesnt work then youll have to flash new firmware
122ninjas said:
I want to make sure you don't brick your phone with the emmc bug. On stock ics if you wipe you can brick your phome
Sent from my SGH-I777
Click to expand...
Click to collapse
didn't see this post when I made the last one
BROKKANIC said:
The only thing left to try would be to use factory reset in cwm. If that doesnt work then youll have to flash new firmware
Click to expand...
Click to collapse
I did the factory reset and nothing changed, I'll start searching how to flash new firmware
Actually on second though after reading I'll wait for more advice as the last thing I wanna do is brick this thing
oldblue05 said:
Actually on second though after reading I'll wait for more advice as the last thing I wanna do is brick this thing
Click to expand...
Click to collapse
I would suggest you try flashing stock UCKH7 to see if that will clear the boot loop. To do that, follow the guide in my signature. If you want to try straight stock, use the guide to return the phone to the store. If you want to try stock plus root, use the guide about flashing custom binaries. The download link for the firmware you need is contained within the guides. After you flash, see if the phone boots. If it still loops, enter 3e recovery and do a wipe data/factory reset. If it still loops, or not, let us know the results. Doing the above will be safe since the firmwares contain no bootloaders, and also are free of the eMMC superbrick bug.
oldblue05 said:
I did what you said and to no change other than the samsung logo being listed longer while it loaded, splash screen appeared and went into the loop.
Click to expand...
Click to collapse
Get into download mode and flash the stock UCKH7. If it still persists then your phone is screwed
Thanks for the help, I finally was able to get ahold of a buddy that does this stuff for a living and he fixed it in like 5 min flat.
His business: mobiletechvideos.com
Either you've got one helluva friend, or this is one fail of a plug
Clay
Team Pirate
Sent from my PINK SGH-I777
You're welcome. I graduated with this guy and he lives within 30 minutes of my offices...
connexion2005 said:
You're welcome. I graduated with this guy and he lives within 30 minutes of my offices...
Click to expand...
Click to collapse
You are a BadAss at what you do my dude, I enjoy watching your videos on YT, you literally turn bricks in to phones!!! Much props for the solid work you do and helping people out.... :good::good: How did you fix his phone Factory/reset right?
Hi, folks.
I've been reading through this forum trying to find a solution to the problem i'm currently having, but none found.
The problem:
As said in the title, Desire X is called T329w, a model custom-made for China Unicom.
Trying to root it using the app by hasoon, and everything seems to work, except one thing: the phone will not boot right away if the battery is removed and installed back again, and will only boot normally after the phone is left with battery removed for a pretty long period, luckily, 45min, and sometimes 4~5 hours.
Just wonder what could be the cause for this?
OK
fan2fan said:
Hi, folks.
I've been reading through this forum trying to find a solution to the problem i'm currently having, but none found.
The problem:
As said in the title, Desire X is called T329w, a model custom-made for China Unicom.
Trying to root it using the app by hasoon, and everything seems to work, except one thing: the phone will not boot right away if the battery is removed and installed back again, and will only boot normally after the phone is left with battery removed for a pretty long period, luckily, 45min, and sometimes 4~5 hours.
Just wonder what could be the cause for this?
Click to expand...
Click to collapse
What you could do is:
1. Check if the protective battery case has been removed
2. Discharge Your Battery Completely
3. Remove It From Your Phone
4. leave it on the table and go to sleep
5. Wake Up Put it back in your phone
6. Make Sure Your Phone is Switched Off
7. Charge Your Phone Completely
8. Your Problem Should Be Solved by Now
Will give it a try.
Just wonder why this happens. Is this related rooting the phone?
Maybe...
fan2fan said:
Will give it a try.
Just wonder why this happens. Is this related rooting the phone?
Click to expand...
Click to collapse
Maybe because the phone is not purely genuine
If it has something to do with the rooting maybe your battery moved during the process?
SaadCrackz said:
Maybe because the phone is not purely genuine
If it has something to do with the rooting maybe your battery moved during the process?
Click to expand...
Click to collapse
i'm suspecting that it is related to rooting the phone. The question is the stock rom is not available at the moment, so we can't go back to stock rom to test.
fan2fan said:
i'm suspecting that it is related to rooting the phone. The question is the stock rom is not available at the moment, so we can't go back to stock rom to test.
Click to expand...
Click to collapse
I guess it's rooting process related; as you flashed a Recovery based on T328 boot.img but yours is T329. If you have the stock recovery for your device, flash that, it should work normal.
ckpv5 said:
I guess it's rooting process related; as you flashed a Recovery based on T328 boot.img but yours is T329. If you have the stock recovery for your device, flash that, it should work normal.
Click to expand...
Click to collapse
I was using the recovery of DesX from this forum.
And I finally found that DesX is a little different from T329w which is available in China. HTC T329w has dual-sim card support while DesX supports only one sim card.
This is the thing that makes the differenc.
ckpv5 said:
I guess it's rooting process related; as you flashed a Recovery based on T328 boot.img but yours is T329. If you have the stock recovery for your device, flash that, it should work normal.
Click to expand...
Click to collapse
Just got hand on stock ROM and made a Recovery with the stock recovery image. Will give it a try.
Hope it will work.
Dear Bro,
I Have T329W too and have similar problem, would you give me the link for download the stock rom? and give me suggestion step by step to solved the problem. I just already have android for a week, and find problem on my phone.
Thanks before for your help.
fan2fan said:
Just got hand on stock ROM and made a Recovery with the stock recovery image. Will give it a try.
Hope it will work.
Click to expand...
Click to collapse
2. Discharge Your Battery Completely BTW if you do that there is a chance the phone never to boot up again With the same battery ofcourse.
Help! The phone dropped to the ground once and had a crack on the digitizer and LCD screen. I replaced both of them and now, it is stuck in a boot loop (turns on, stays on splash screen) I've tried flashing the latest firmware thru Odin, but the same thing happens. All I can do on the phone is just getting to the download mode. I can't get to recovery, too.
Did you wiped cache and dalvick before reboot?
Before the first bootloop what did you do(Install an apk? Flash a zip?)? Were you rooted? A custom rom? A stock one?
During Odin did you wait for pass and blue color?
have you seen This? Is that similar for you?
Mukiai said:
Did you wiped cache and dalvick before reboot?
Before the first bootloop what did you do(Install an apk? Flash a zip?)? Were you rooted? A custom rom? A stock one?
During Odin did you wait for pass and blue color?
have you seen This? Is that similar for you?
Click to expand...
Click to collapse
Yes, I did wipe both, I didn't do anything weird except a reboot, not rooted, stock ROM, pass on Odin, not similar to the hard brick problem. I can get to download and recovery mode.
You can go now to recovery mode? Have you retry to flash a rom?
Do you remember last version before and the last you install? Couldn't it be you had try to flash an older version?
Mukiai said:
You can go now to recovery mode? Have you retry to flash a rom?
Do you remember last version before and the last you install? Couldn't it be you had try to flash an older version?
Click to expand...
Click to collapse
I'm going to flash a new one.
Acerpeng229 said:
I'm going to flash a new one.
Click to expand...
Click to collapse
Any news? Do you enjoy again your Mega? Hope that yes.
No news ?
got same problem
Mukiai said:
No news ?
Click to expand...
Click to collapse
hello fellas..this my first post here..im using samsung mega lte,and have a problem after root my phones..cant go recovery mode.couse there have a red text warranty bit kernel and 3more text avove in my screen..just stuck at samsung logo..dont know how to do..there any friend here know how to do?its been a month my phone stuckat the same problem
It seems this issue is a difference in screen compatibility. To fix this, you can turn the device on and let it boot into the Android OS, then (while still on), unplug the old LCD and plug in the new LCD. Hit the power button to ensure the new LCD is working properly, then turn the device on, and finish assembling your phone.
same issue
R960 stuck in loop after replacing screen and cant access recovery or odin mode
need help desperately
I just got a galaxy mega from someone an got ripped off because it's running 4.4 kit Kat and had the screen replaced right before I got it, so it doesn't work. Bootloops. Due to not an OEM screen and I don't really have the cash to risk ordering a screen claiming to be oem.
So how can I just downgrade to a version before the need for OEM screen??
Please any help would be greatly appreciated!!
-d.block- said:
I just got a galaxy mega from someone an got ripped off because it's running 4.4 kit Kat and had the screen replaced right before I got it, so it doesn't work. Bootloops. Due to not an OEM screen and I don't really have the cash to risk ordering a screen claiming to be oem.
So how can I just downgrade to a version before the need for OEM screen??
Please any help would be greatly appreciated!!
Click to expand...
Click to collapse
You can not in normal way (i.e flashing stock 4.2). But there is hope for you... look there:
http://forum.xda-developers.com/showthread.php?t=2608110
trurl3 said:
You can not in normal way (i.e flashing stock 4.2). But there is hope for you... look there:
http://forum.xda-developers.com/showthread.php?t=2608110
Click to expand...
Click to collapse
I'm still a bit confused as to what exactly I should do.. there's alot in that thread.. I really can't afford to buy another screen. This really sucks that the update requires OEM screen in order to function.. if I could find a way to fix the issue without buying a screen I'd be extremely grateful!
But I don't have much experience at all with rooting and flashing custom ROMs, and I'm kind of afraid to brick the phone..
Any help to get the touch screen up and running would be highly appreciated!!
Thank you!
I am the only one who only a part of upper screen works? (I can see status bar, and rotating enter to wifi settings and try to get out of welcome screen of att)
Mukiai said:
No news ?
Click to expand...
Click to collapse
OMG! Sorry for the very late reply. It works fine already. Went to download mode and flashed using Odin. Thanks!
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.
So i have no idea what i'm doing but i somehow made this recovery and it works lol. the only thing ive noticed so far is file transfer doesn't work in the recovery. You'll have to install the usual PB tools manually because again, i have no idea what i'm doing and only get the img when i compile it ctfu
nevermind, i lied. its a broken turd lol. it wont let me mount data after formating . any ideas on how to fix it and im all ears
tinman4209333 said:
So i have no idea what i'm doing but i somehow made this recovery and it works lol. the only thing ive noticed so far is file transfer doesn't work in the recovery. You'll have to install the usual PB tools manually because again, i have no idea what i'm doing and only get the img when i compile it ctfu
Click to expand...
Click to collapse
my phone already messed up, i dont mind trying it to help fix it. (ps if you think you can fix my phone i'll be grateful.. the issue, it's stuck in qualcomm crashdump after a rom change)
Lizzo said:
my phone already messed up, i dont mind trying it to help fix it. (ps if you think you can fix my phone i'll be grateful.. the issue, it's stuck in qualcomm crashdump after a rom change)
Click to expand...
Click to collapse
i can upload the qfil firmware for global if that would help. as for the recovery the phone still boots and i can switch in and out of recovery. it just wont mount /data. even after formatting the next time i go into it i get the same crap
if anyone can tell me why i cant mount data even after formatting and what id need to do to fix it Id be sincerely grateful. And yes i know the recovery logs are for orangefox and not PBRP but for the most part its the same sources. I think the main issue is the half assed programmer has no clue what the hell he's doing CTFU. Ive been going by the motto if ya throw enough Sh*T at the wall , sooner or later something will stick. i just keep adding more build flags and other things that sound interesting and slap em on there. Phone still works fine after each build so i think thats a plus