Related
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.
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.
EDIT: The problem is fixed, the problem was my dead SD card, as soon as I took it out and boot into TWRP the recovery has been working well. Thank you all for your help anyways.
What's going on guys, today I'm in need of some aid. Couple days ago I was trying to swap ROMs from PsyRom to FlyMeOS and when I tried to access TWRP recovery, it would get stuck on the TeamWin logo. I softbricked my phone by restoring the stock recovery and kernel (lol) and flashed the latest Fastboot ROM. Now I'm fine with MIUI8, and I flashed TRWP again (with Fastboot flash) but everytime I try to access TRWP it gives me that stuck logo or a black screen. I don't know what to do because I already tried with a rooted Dev ROM and flashify and even the TWRP Manager but I can't get anywhere. Do you know what I can do?
I've seen several TWRP versions for RN2.
Did you try with the official one?
https://dl.twrp.me/hermes/
gnazio said:
I've seen several TWRP versions for RN2.
Did you try with the official one?
https://dl.twrp.me/hermes/
Click to expand...
Click to collapse
Yes I did, and with the 2.8.7, and the other 3.0.x
Always the same result. Did Xiaomi lock the Redmi Note 2 bootloader?
kiko9895 said:
Yes I did, and with the 2.8.7, and the other 3.0.x
Always the same result. Did Xiaomi lock the Redmi Note 2 bootloader?
Click to expand...
Click to collapse
AFAIK the bootloader is not locked.
Otherwise I think that you can't even install TWRP.
I any case, I would try with an older fastboot ROM and with the official TWRP.
Have you tried this one: http://forum.xda-developers.com/redmi-note-2/general/twrp2-8-7-0-light-materialized-theme-t3308492
DarthJabba9 said:
Have you tried this one: http://forum.xda-developers.com/redmi-note-2/general/twrp2-8-7-0-light-materialized-theme-t3308492
Click to expand...
Click to collapse
Yes, it's the last one I tried, I used the one on the first link, with MIUI8 compatibility.
gnazio said:
AFAIK the bootloader is not locked.
Otherwise I think that you can't even install TWRP.
I any case, I would try with an older fastboot ROM and with the official TWRP.
Click to expand...
Click to collapse
I'm sorry but do you know where I can find an older one?
kiko9895 said:
Yes, it's the last one I tried, I used the one on the first link, with MIUI8 compatibility.
Click to expand...
Click to collapse
I am using this one: https://drive.google.com/file/d/0BwdRTuyj12_yVlJoMzJoeUJKLVE/view
I have no problem with it (MIUI8). To be honest, I don't think any of them should cause the problem that you are having. Trying to solve the problem without identifying the cause will probably prove unfruitful. How did you install the first one that you had problems with? Did it ever work at all? If so, when did it start malfunctioning?
DarthJabba9 said:
I am using this one: https://drive.google.com/file/d/0BwdRTuyj12_yVlJoMzJoeUJKLVE/view
I have no problem with it (MIUI8). To be honest, I don't think any of them should cause the problem that you are having. Trying to solve the problem without identifying the cause will probably prove unfruitful. How did you install the first one that you had problems with? Did it ever work at all? If so, when did it start malfunctioning?
Click to expand...
Click to collapse
Yes it used to work, I already tried a lot of ROMs, I had the one compatible with Android 6.0 which I flashed with TWRP itself (It worked since I flashed CM13 with it).
I don't really know when it started malfunctioning because the last time I made a backup was at least one month ago when I swapped to PsyRom (it was functioning well). But two days ago when I tried to access it to change to FlyMe it wouldn't work. Anyways I'm flashing a MIUI7 fastboot ROM to see if it works.
I'm sorry if I can't explain myself very well but I'm doing the best I can lol. Thank you for your help too.
Perhaps something messed up your file system or partitions. If all attempts don't work, then you might want to use the SP Flash Tool to flash a compatible ROM and working TWRP.
DarthJabba9 said:
Perhaps something messed up your file system or partitions. If all attempts don't work, then you might want to use the SP Flash Tool to flash a compatible ROM and working TWRP.
Click to expand...
Click to collapse
I just flashed MIUI 7 with SP Flash Tool. Gonna try and flash TWRP through fastboot and with update.zip method, see if anything works.
kiko9895 said:
I'm sorry but do you know where I can find an older one?
Click to expand...
Click to collapse
I should have a MIUI7 on my mega account, it should be the last 7 stable, saved just in case something was wrong with 8.
I can send you the link if you are still searching.
OK, I just noticed that you have solved yet.
Good, I hope that this time everything will be fine.
gnazio said:
I should have a MIUI7 on my mega account, it should be the last 7 stable, saved just in case something was wrong with 8.
I can send you the link if you are still searching.
OK, I just noticed that you have solved yet.
Good, I hope that this time everything will be fine.
Click to expand...
Click to collapse
Thank you very much for your kindness, I'm still trying tho ahah using WinDroid Toolkit now.
gnazio said:
I should have a MIUI7 on my mega account, it should be the last 7 stable, saved just in case something was wrong with 8.
I can send you the link if you are still searching.
OK, I just noticed that you have solved yet.
Good, I hope that this time everything will be fine.
Click to expand...
Click to collapse
Hello, after one month the issue is still not fixed, the recovery still hangs. Perhaps you could send me that fastboot rom you talked about please? Thank you.
I'm going to send you the link.
In the meanwhile...reading the thread again...what is "update.zip method"?
Are you try to install TWRP from Mi recovery?
This is not going to work anymore.
You should better stay with the last ROM and flash TWRP from fastboot.
This is the recovery image: https://dl.twrp.me/hermes/twrp-3.0.2-0-hermes.img
This is the guide: https://twrp.me/devices/xiaomiredminote2.html
Just start your RN2 into fastboot (vol down+power on), run fastboot flash recovery twrp.img and finally keep pressed vol up and send fastboot reboot and wait with the key pressed until it enter TWRP.
BTW:
in the official forum there should be a thread with link to all officially released ROMs for RN2.
kiko9895 said:
Hello, after one month the issue is still not fixed, the recovery still hangs. Perhaps you could send me that fastboot rom you talked about please? Thank you.
Click to expand...
Click to collapse
Here you should find every MIUI Global ROM released for RN2:
http://en.miui.com/forum.php?mod=viewthread&tid=394496
I just realized that the one I have is China version, used just to clean the phone from reseller ROM.
gnazio said:
I'm going to send you the link.
In the meanwhile...reading the thread again...what is "update.zip method"?
Are you try to install TWRP from Mi recovery?
This is not going to work anymore.
You should better stay with the last ROM and flash TWRP from fastboot.
This is the recovery image: https://dl.twrp.me/hermes/twrp-3.0.2-0-hermes.img
This is the guide: https://twrp.me/devices/xiaomiredminote2.html
Just start your RN2 into fastboot (vol down+power on), run fastboot flash recovery twrp.img and finally keep pressed vol up and send fastboot reboot and wait with the key pressed until it enter TWRP.
BTW:
in the official forum there should be a thread with link to all officially released ROMs for RN2.
Click to expand...
Click to collapse
The problem is I already tried the fastboot method as well, and the problem is always the same, stuck TWRP logo. Even if it was a partition problem, flashing the fastboot ROM should fix it, but it didn't. I tried the SP Flash Tools method too, and the flashing methods are successful, they all Flash TWRP, but when I try to access it it's stuck. I don't know why this is happening, it used to work.
@kiko9895 Sounds like you have screwed your partitions. You will need to load a full ROM using SP Tools to correct it as this is the only way to set the partitions back at their correct memory locations. Fastboot and Recovery rewrite the partitions by name not memory location so any fault in that will never be fixed. If you have flashed an Android 6.0 based ROM or something intended for another model phone, this will definitely be the case. Anyone flashing custom ROMs should first gather the skills and tools to recover from disasters - luckily, MTK based phones are virtually unbrickable!
As far as the "official" TWRP goes, it is not official and not a good version. It is just someone who has used the TWRP build server to knock out a random version. How does that make it "official"?
jajk said:
@kiko9895 Sounds like you have screwed your partitions. You will need to load a full ROM using SP Tools to correct it as this is the only way to set the partitions back at their correct memory locations. Fastboot and Recovery rewrite the partitions by name not memory location so any fault in that will never be fixed. If you have flashed an Android 6.0 based ROM or something intended for another model phone, this will definitely be the case. Anyone flashing custom ROMs should first gather the skills and tools to recover from disasters - luckily, MTK based phones are virtually unbrickable!
As far as the "official" TWRP goes, it is not official and not a good version. It is just someone who has used the TWRP build server to knock out a random version. How does that make it "official"?
Click to expand...
Click to collapse
Ahah I have the skills and the tools, I've been flashing ROMs for more than two years. This never happened before. If you read what I said before on this thread, you'll see that I already flashed a new ROM through SP Flash Tools. And yes I flashed a 6.0 rom before so that must be the problem, but since I already flashed a fastboot rom through SP Flash Tools I can't see where the problem is. The partitions should be fixed by now but that isn't the case.
@kiko9895 Sorry if it sounded like I was coming down hard on you. You should only need to flash a matching preloader, uboot, logo plus TWRP recovery using SP Flash Tools with the correct scatter file to get back into booting to TWRP. Any other problems can be sorted from there.
I will attach a known good scatter file because I know there are several floating around that will reverse one or two partitions on you (such as the RN3 version)
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.