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.
Related
Ive flashed back to the stock rom many many times after playing with roms here and wanting to go back. Almost every time before I did I would use a zip through clockwork that wipes everything and I did this time too but for some reason after odin installs the stock firmware successfully the phone reboots as usual then goes through its checks and it always fails to wipe data. So my biggest issue is the phone is unusuable until I can do this because it boots to the tmobile screen and then the screen goes black but the phone is on as the capacative keys at the bottom still light up when touched. Any help on this would be great but its looking like Im going to have to get another one.
pablo1215 said:
Ive flashed back to the stock rom many many times after playing with roms here and wanting to go back. Almost every time before I did I would use a zip through clockwork that wipes everything and I did this time too but for some reason after odin installs the stock firmware successfully the phone reboots as usual then goes through its checks and it always fails to wipe data. So my biggest issue is the phone is unusuable until I can do this because it boots to the tmobile screen and then the screen goes black but the phone is on as the capacative keys at the bottom still light up when touched. Any help on this would be great but its looking like Im going to have to get another one.
Click to expand...
Click to collapse
Are you sure you didn't get this after you installed the Voodoo lag fix??? You will have to read through this, but it looks like there's a fix in this thread.
http://forum.xda-developers.com/showthread.php?t=781456
Got to page three and read from there.
You are correct. I finally narrowed it down because I had done several updates through clockwork today but that was it. I am reading through forums to see about a fix, good thing I have other phones to play with too.
i got the same thing. did you figure it out?
menacetwosociety said:
i got the same thing. did you figure it out?
Click to expand...
Click to collapse
I hope someone answered you.
It messed up because I flashed the Vibrant Voodo Lag-fix w/OC-Optimized 2.6.29 Kernel - Beta4 9/19/2010
To disable, simply place a new folder in the "Voodoo" folder on your SDcard (the internal one) name it "disable lagfix" (e.g /sdcard/Voodoo/disable lagfix") no extention just that exact name and reboot. After your phone boots and you check that your /data partition is again RFS you can re-apply any other kernel you were using.
now redo the stock kernel and stock rom via odin and you should be fine.
yea im having same issue, how do you put the folder in if the phone doesn't show anything, just a black screen?!
I have same problem
How can i add the folder if the screen is black?
please help
thanks
update: http://forum.xda-developers.com/showpost.php?p=8698655&postcount=150
this fixed my problem
gottijr said:
I have same problem
How can i add the folder if the screen is black?
please help
thanks
update: http://forum.xda-developers.com/showpost.php?p=8698655&postcount=150
this fixed my problem
Click to expand...
Click to collapse
Thanks!!!!!!!!!!!!! This fixed my mess up too.
how can i do it with my vibrant turn black after booting ?
yep, this fixed me right up... once i realized i needed odin 1.3 to do it... but it did work and all is well...
thanx this worked for me as well
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.
Hello. I'm annoyed
I rooted to get rid of problems... So
I followed these tasks: http://forum.xda-developers.com/showthread.php?t=1653566 and the root worked for a few days - then moved into a boot loop.... how/why... I don't know.
Ive tried many of the different .aos files to find a correct one for my 101g9 250gb, but I still can't get it out of the loop.
This is where I've been getting the different Aos files: http://forum.xda-developers.com/showthread.php?t=1468925
I get 2 different results 1)error 207 (update failed) or 2) boot loop.
One stange thing did happen once - It's managed to reload the android installer, I selected a language, then it crashed again. Of course I tried the same thing again, but it never got past the boot loop again.
After 2 weeks of trying, I'd like some help.
I always have it plugged in. It's not the battery. It's the HDD model and I don't know exactly which version came with the device. I think 4.0.25.. not 100% sure
Please help
I don't have the HDD model so don't know what to tell you exactly..
What I would do on my flash model is boot into recovery. completely reformat the system and use recovery to update the firmware with an Archos firmware (aos file) onto it.
Reformating it from recovery would bring the filesystem back to stock so it should fix anything wierd any of the other roms might have done. So dropping an Archos firmware on it should in theory fix it. Though you WILL lose your root and anything else you have on the drive.
Djirin said:
I don't have the HDD model so don't know what to tell you exactly..
What I would do on my flash model is boot into recovery. completely reformat the system and use recovery to update the firmware with an Archos firmware (aos file) onto it.
Reformating it from recovery would bring the filesystem back to stock so it should fix anything wierd any of the other roms might have done. So dropping an Archos firmware on it should in theory fix it. Though you WILL lose your root and anything else you have on the drive.
Click to expand...
Click to collapse
Thanks for your help, but no luck- that didn't work. I'm sure I lost all my data a long time ago with the amount of reformats I've done. What I'm curious about is, can the tablet actually become a brick just by using these rooted firmwares? I'm assuming that it's fine and that I just have to 'crack to code' to installing the right firmware in the right order.....
I'm still curious if anyone else has had this problem..
Hmm.. Try going back into recovery and try the Reset Android option?
Maybe do Reset Android. Reformat Device. Upgrade Firmware?
The device boots.. so it has to be something causing it.. Have you tried to see if you can use ADB to get into the device and look at any log entries?
Djirin said:
Hmm.. Try going back into recovery and try the Reset Android option?
Maybe do Reset Android. Reformat Device. Upgrade Firmware?
The device boots.. so it has to be something causing it.. Have you tried to see if you can use ADB to get into the device and look at any log entries?
Click to expand...
Click to collapse
ADB? ok, I didn't know what it was. But it's now installed and I followed a random setup on youtube, but when I type ADB devices, nothing comes up.
So now I have it installed, but I so far I can't get win7 to detect the tablet in device manager
Regarless, can the ADB detect problems on the tablet when the archos is only connected waiting for the AOS file (A101H-REC - 299MB)?
Btw, you've already got me waaaaay over my head on this stuff - but still, I'm learning.
pwnami said:
ADB? ok, I didn't know what it was. But it's now installed and I followed a random setup on youtube, but when I type ADB devices, nothing comes up.
So now I have it installed, but I so far I can't get win7 to detect the tablet in device manager
Regarless, can the ADB detect problems on the tablet when the archos is only connected waiting for the AOS file (A101H-REC - 299MB)?
Btw, you've already got me waaaaay over my head on this stuff - but still, I'm learning.
Click to expand...
Click to collapse
Let me join the conversation
Adb works only is it is enabled in developer settings.
What kind of system do you have in use?
In your case i would probably try exporting hdd in sde. This allows you to browse files inside your hdd in linux operating system through usb.
If it is empty, i would export data partition through sde. This allows you to see if there are any files in your data partition.
You said that the device bootloops, yes? That means that the reformat device is not working. It would remove the system, so you shouldnt even see the bootanimation.
Sent from my ME301T using xda app-developers app
julle131 said:
Let me join the conversation
Adb works only is it is enabled in developer settings.
What kind of system do you have in use?
In your case i would probably try exporting hdd in sde. This allows you to browse files inside your hdd in linux operating system through usb.
If it is empty, i would export data partition through sde. This allows you to see if there are any files in your data partition.
You said that the device bootloops, yes? That means that the reformat device is not working. It would remove the system, so you shouldnt even see the bootanimation.
Sent from my ME301T using xda app-developers app
Click to expand...
Click to collapse
Hi, thanks - any advice is welcome. I only have windows7 - Sorry.
As for the bootloop, yes that's the status. I hadn't even considered that the reformatting process wasn't actaully working [but it is] - I reformatted the device and didn't install an AOS. now every restart brings me straight into the Recovery menu [which should happen i assume].
So, with a "clean" but stubborn device, what would you advise to try to isolate the problem? (rather than me simply blindly trying random things)
Thanks
pwnami said:
Hi, thanks - any advice is welcome. I only have windows7 - Sorry.
As for the bootloop, yes that's the status. I hadn't even considered that the reformatting process wasn't actaully working [but it is] - I reformatted the device and didn't install an AOS. now every restart brings me straight into the Recovery menu [which should happen i assume].
So, with a "clean" but stubborn device, what would you advise to try to isolate the problem? (rather than me simply blindly trying random things)
Thanks
Click to expand...
Click to collapse
So reformat works. Have you tried to flash the official 4.0.28(http://update.archos.com/9/gen9/gen9_4.0.28/firmware_archos_it4.aos)?
After searching about your error 207, I found this:http://forum.archosfans.com/viewtopic.php?f=35&t=56037
Code 207 is issued by aosparser when the .aos upgrade file doesn't
pass the signature check.
...
There's more bad news... If the genuine original .aos files are also
giving the same error it means the signing keystore may also have been
damaged.
Click to expand...
Click to collapse
Of course, this is for Archos 5, so hopefully this is not the case.
julle131 said:
So reformat works. Have you tried to flash the official 4.0.28(http://update.archos.com/9/gen9/gen9_4.0.28/firmware_archos_it4.aos)?
After searching about your error 207, I found this:http://forum.archosfans.com/viewtopic.php?f=35&t=56037
Of course, this is for Archos 5, so hopefully this is not the case.
Click to expand...
Click to collapse
Yeah, I've used the aos from the archos site a bunch of times - still no luck. btw, that link to the 4.0.28 didn't work....
by "Flash" I hope you mean install.... not some other random process
pwnami said:
Yeah, I've used the aos from the archos site a bunch of times - still no luck. btw, that link to the 4.0.28 didn't work....
by "Flash" I hope you mean install.... not some other random process
Click to expand...
Click to collapse
Yeah... I just noticed it was broken. And yes, I meant install.
I am sorry, but I'm out of ideas.
Sent from my GT-I9100 using xda app-developers app
julle131 said:
Yeah... I just noticed it was broken. And yes, I meant install.
I am sorry, but I'm out of ideas.
Sent from my GT-I9100 using xda app-developers app
Click to expand...
Click to collapse
So, do you know if I can access/use ADB on a win7 pc when the archos doesn't have an aos on it?
http://forum.xda-developers.com/showthread.php?t=2104491&highlight=wlan
You could try this. it's written that it doesn't work on hdd model. but it can't get much worse it think. If I understand things correctly, you don't need to have installed any aos before installing this rom. with other roms you get a archos.ext4.update so you need a running system. yust give it a try but don't blame me if your tablet's completely dead afterwards. i don't know what will happen.
Or you could just follow the steps 1-7 (from link above!) to get cwm, maybe that helps for sth, but i don't know.
sry, but my writing style is bad. and do it on your own risk, I'm not that expirienced but that's what I would do...
Good luck
noaddress said:
http://forum.xda-developers.com/showthread.php?t=2104491&highlight=wlan
You could try this. it's written that it doesn't work on hdd model. but it can't get much worse it think. If I understand things correctly, you don't need to have installed any aos before installing this rom. with other roms you get a archos.ext4.update so you need a running system. yust give it a try but don't blame me if your tablet's completely dead afterwards. i don't know what will happen.
Or you could just follow the steps 1-7 (from link above!) to get cwm, maybe that helps for sth, but i don't know.
sry, but my writing style is bad. and do it on your own risk, I'm not that expirienced but that's what I would do...
Good luck
Click to expand...
Click to collapse
I gave up on this 6 months ago. but I turned it on 2 days ago and it magically worked.... Now, it's back in a bootloop again. Everything was working for two days, except sometimes the HDD wasn't reading the files, or the system wasn't detecting the HDD...
Could the HDD be damaged? If so, is there a way to check if it is (I was thinking about the ssd option)
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!
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