Is it possible to flash Touchscreen firmware on my 9295?
(like the Modem-firmware)
My touchscreen is not responsive in CWM or TWRP (both touch-versions) but works 100% when booted into GUI.
Came across some (old) threads on XDA and here and there this option was mentioned.
I already tried to flash the original firmware (containing this Touchscreen-firmware?) but that didn't solve the problem.
Right now i'm stuck....so any ideas are very welcome!
Related
Hello guys,
I wonder if you can help. I am trying to root and install CWM on my tab 8.9 but am running into issues as the system will not allow me to install from the SD card under the official recovery. I have read that this can be an issue with the ICS firmware.
I then did a bit of searching and found an odin flashable CWN (chainfire 5.1.6.2 I think) which I flashed and it installed, but the problem is that the recovery screen constantly scrolls and it is too fast to see what the options are.
Do any of you know of an alternative odin flashable CWM which I could try, or have you experienced the same issue and discovered a solution?
Many thanks in advance for your help!
Chongy!
Hi!
Today i wanted to update my firmware just because Samsung Kies asked me if i wanted to. I couldn't have been more wrong when i chose to update.
The update froze at 3% and after a lot of time i unplugged the phone and ended up with a brick instead of a phone.
If i try to turn it on, i get a black screen with a "phone--!--pc" picture. I can enter Download Mode by pressing VolumeDown + HomeButton + PowerButton and i get an android logo with ''Downloading... Do not turn off target'' written under it.
My phone was never rooted, nor updated ( it remained with its out-of-the-factory OS and everything ).
For the past 6 hours i've been trying to use Odin v4.43 along with AriesVE.ops (the one from the well-known WORKED2 archive) to try and get recovery-clockwork to work.
So my questions are:
Given the fact that my phone was not rooted, how can i get my GT-I9001 to work again? Is this even possible?
Can i first root it in its condition, then flash a custom rom like cyanogenmod? Or do i need to install a stock rom and then try a custom one?
What other options do i have?
Everything i've tried so far with Odin froze while downloading and i have no other solution to this problem. Please help!
zerkylo said:
Hi!
Today i wanted to update my firmware just because Samsung Kies asked me if i wanted to. I couldn't have been more wrong when i chose to update.
The update froze at 3% and after a lot of time i unplugged the phone and ended up with a brick instead of a phone.
If i try to turn it on, i get a black screen with a "phone--!--pc" picture. I can enter Download Mode by pressing VolumeDown + HomeButton + PowerButton and i get an android logo with ''Downloading... Do not turn off target'' written under it.
My phone was never rooted, nor updated ( it remained with its out-of-the-factory OS and everything ).
For the past 6 hours i've been trying to use Odin v4.43 along with AriesVE.ops (the one from the well-known WORKED2 archive) to try and get recovery-clockwork to work.
So my questions are:
Given the fact that my phone was not rooted, how can i get my GT-I9001 to work again? Is this even possible?
Can i first root it in its condition, then flash a custom rom like cyanogenmod? Or do i need to install a stock rom and then try a custom one?
What other options do i have?
Everything i've tried so far with Odin froze while downloading and i have no other solution to this problem. Please help!
Click to expand...
Click to collapse
Yes it is possible as long as your device boots into Download mode.
No you can't root it in its current condition.
You need to download a stock firmware, flash it using Odin or Heimdall (recommended), then root it and finally install a custom ROM if you want.
kalpetros said:
Yes it is possible as long as your device boots into Download mode.
No you can't root it in its current condition.
You need to download a stock firmware, flash it using Odin or Heimdall (recommended), then root it and finally install a custom ROM if you want.
Click to expand...
Click to collapse
Thank you for answering!
I fixed the issue. Tried different usb port along with a different version of CWM (5.5.0.4) which I installed with Odin v4.43. CWM 5.5.0.4 caused a bootloop, but i used it only to install CWM 6.0.4.9 from external_sd, so the bootloop problem was gone. Then flashed CyanogenMod 11 and now works like a charm !
I attached an archive with CWM 5.5.0.4, AriesVE.ops and Odin v4.43, so that anyone having my problem can solve it the way i did. But keep in mind that this version of CWM *may* cause a bootloop, so prior to installing it, you should have a working version of CWM on your external_sd. Use CWM 5.5.0.4 to install the better version of CWM from your external_sd. Also, whatever you do is at your own risk!
So I've rooted my Z3c using dual recovery method, and later on flashed the Rectify mod, and everything seemed to be working well until I wanted to flash a file in recovery (I know I had CWM working at one point) but it is not working. I found the little NDR tool in the Rectify mod and tired the various recovery options (previously I would just use up on volume key). Well this is when I started noticing it not working and so I tried the manual volume key approach and still it is not working. I installed busy box and have found that can sometimes cause problems with NDR/Recovery however I attempted to uninstall was going to try different location but that's broken now too... I think.
So anyway, my problem is, if I re-install DualRecovery it still does not go to recovery.
Please help me get to Recovery mode so I can reflash rom.
Thank You
Have you installed a different busybox, most others aren't compatible with XZDR and will cause this kind of issue.
I'll tell you what I did, I downgraded firmware using flashtool, followed the dualboot method to upgrade while re-rooting and confirming recovery along the way (this seems to work) then as soon as I install rectify (making sure to flash dualboot flashable zip file before reboot) I'm no longer able to access recovery, not manually or using NDR. I also didn't intall busybox yet.
Oh boy what now, I'm back to square one.
I'm an idiot, what's the rectify mod? Point me to a download link and I'll see if there's something in it that's causing issues with XZDR.
Edit : I see its rectify rom. Well it most likely includes it's own version of busybox, hence the issue.
Hi guys,
First of all, i made a new thread after looking for a solution for days and pretty much everywhere.
• My issue : i can't get any custom rom to boot. Everytime i flash one, i get stuck with endless bootanim
• so you know :
- flashing original firmwares from sammobile or stock based roms (i.e N4elite) with odin or recovery works perfectly. roms boot and everything work flawlessly.
- i tried almost every lollipop roms (RR, Nameless 2.0 and 2.1, cm12.1, asop, aicp)
- i tried different recoveries (CWM, TWRP, PSN_TWRP)
- i tried different gapps packages
- all downloaded files were good
- i tried wiping everything, even tried changing file system to f2fs (and reverted back to ext4)
- i guess flash memory is ok since Sammy roms work
- my battery is almost new, i changed it not so long ago
- i was running an early cm12.1 build and everything was ok, the issue occured when i tried to flash cm12.1 stable 3 build
As i'm now out of idea, any suggestion would be appreciated.
Thanks !
fraydz said:
Hi guys,
First of all, i made a new thread after looking for a solution for days and pretty much everywhere.
• My issue : i can't get any custom rom to boot. Everytime i flash one, i get stuck with endless bootanim
• so you know :
- flashing original firmwares from sammobile or stock based roms (i.e N4elite) with odin or recovery works perfectly. roms boot and everything work flawlessly.
- i tried almost every lollipop roms (RR, Nameless 2.0 and 2.1, cm12.1, asop, aicp)
- i tried different recoveries (CWM, TWRP, PSN_TWRP)
- i tried different gapps packages
- all downloaded files were good
- i tried wiping everything, even tried changing file system to f2fs (and reverted back to ext4)
- i guess flash memory is ok since Sammy roms work
- my battery is almost new, i changed it not so long ago
- i was running an early cm12.1 build and everything was ok, the issue occured when i tried to flash cm12.1 stable 3 build
As i'm now out of idea, any suggestion would be appreciated.
Thanks !
Click to expand...
Click to collapse
Hello,
I got the same issues ...
Trying to root the Stockrom results in the disappearance of baseband. Maybe this could help? I need to get some sleep first.
Regards
Heiko
EDIT: I thought maybe I fill in a bit more detail. I had CM 11 running which also flashed my recovery to cwm. So I used the TWRP Manager to install new Recovery, but I didn't check the Partition! So it didn't work as planned. Phone was in a boot loop and restartet every 5s. But TWRP via Odin worked. I wiped every partition available in Odin and installed Stock. Which seems to work without root.
CM 11 results in a boot loop.
CM 10.3 boots up, bud doesn't find the modem (same as Stock with root)
I hope there is some help. I like this phone a lot.
I did reinstall Samsung Stock via Kies.
And thank god that solved the Problem.
Restored my backup and everything is working again.
Heikoles said:
I did reinstall Samsung Stock via Kies.
And thank god that solved the Problem.
Restored my backup and everything is working again.
Click to expand...
Click to collapse
thanks for your feedback and ideas.
i tried to flash stock with kies, it ended with an error, but flashing stock firmware with odin worked, and everything was ok (including modem)...
for now i'm stuck with stock firmware flashed with odin
EDIT :
i finally succeeded.
- flashed old 4.3 firmware with odin without auto reboot
- the flash failed at the end
BUT
- manual reboot in download
- flashed TWRP tar
- reboot in recovery
- flashed 4.3 modem zip
let system boot
reboot in recovery
flash any rom and gapps !
Hello,
first post, trust I did not miss aynthing.
Bought a cheap used SM-T810N as "damaged" believing it is a software problem and I can fix it.
Flashed everything I found (Lollipo, Marshmallow, CM, TWRP recovery, etc.)
Tablet stucks at Samsung Logo and shows some strange color effects (lines, artefacts) but screen works fine in Recovery, TWRP, etc.
Anyone any idea how to identify the real problem?
Thanks a lot, you all are doing a great job here.
DaWool
wool242 said:
Hello,
first post, trust I did not miss aynthing.
Bought a cheap used SM-T810N as "damaged" believing it is a software problem and I can fix it.
Flashed everything I found (Lollipo, Marshmallow, CM, TWRP recovery, etc.)
Tablet stucks at Samsung Logo and shows some strange color effects (lines, artefacts) but screen works fine in Recovery, TWRP, etc.
Anyone any idea how to identify the real problem?
Thanks a lot, you all are doing a great job here.
DaWool
Click to expand...
Click to collapse
Have you tried a full wipe before using Odin to flash a ROM? Including the data partition? Or tried booting to "download" instead of TWRP to use Odin?
edit: And you do need to use Odin to get things working before trying to flash anything via TWRP.
Seems like a mismatched bootloader and kernel issue to me.
Flashing stock firmware with ODIN should fix it if it is.
lewmur said:
Have you tried a full wipe before using Odin to flash a ROM? Including the data partition? Or tried booting to "download" instead of TWRP to use Odin?
edit: And you do need to use Odin to get things working before trying to flash anything via TWRP.
Click to expand...
Click to collapse
Tried both, Odin and flashing from recovery... Even different Odin versions