Hi y'all,
I have this issue and I'm really clueless about how to solve it.
I flashed this ROM on my i9305: Slim-i9305-4.3.build.2-UNOFFICIAL-20131028-1013
it's one of the ROMs suggested in this forum. and it worked great.
I later on tried to flash an update to my twrp (it was version 2.6.3.0) with flashify (BIG mistake never doing it again).
the image I tried to flash was (openrecovery-twrp-2.7.0.0-t0ltespr)
I understand now it was not a good image for my phone.
at first the phone was bricked and I was only able to enter 'download mode'.
however, after I flashed the correct twrp, and reflashed the ROM, i got it working again, except the touch screen isn't working, all other buttons are working fine (back, home, power, volume up/down), but the touch doesn't respond not even in recovery mode(!!!).
my best result so far was when i flashed PhilzTouch and so I could navigate through recovery with the up/down volume, but still no touch.
can anyone help me here?
any clue?
I thought of maybe trying to use the 'NAND erase all' option via odin but I understood I need to get a pit file and a stock ROM first (I'm currently downloading the stock but have no idea of where to get the pit file)
Thanks.
:cyclops::cyclops::cyclops:
Flash CWM recovery and install another ROM clean flash, should fix everything
Sent from my GT-I9195 CarbonKat 4.4.2
or you can flash the original samsung rom from their website... http://www.sammobile.com/firmwares/
flash it with odin 3.07 as PDA and should work fine...after you flash it, might not boot...enter stock recovery...volume up + home + power and do factory reset and cache partition...after that you should work flawless..
Related
Hi
I've tried a few custom ROM on my nexus. But today I was thinking to downgrade my phone to a Stock ROM, Stock-GRH55-Unsigned. So I downloaded the zip-file and upload it to the sdcard and then I run Clockworkmod -> install zip from sdcard and choose Stock-GRH55-Unsigned.zip.
The install of the Stock ROM looked fine so I rebooted my phone and after that is the phone dead .
When I press the on/off-button the phone vibrates and the home and search button lights up and after a while they go out and the two other buttons start to slowly blink.
Does anyone have any idea how I can solve my problem or is my phone dead?
//mille7
If you can get into the bootloader (volume up + power) then you can try and get into CWM (doubt it will still be intact). From CWM you can wipe and try flashing something else. If you can't get into CWM, you can reflash the recovery image from the bootloader using fastboot.
If you can't do any of the above, then start looking into Odin. I have no experience in Odin though, so can't help you there. Good luck!
I was running Alliance rom and decided I wanted to try a couple different roms. I had previously installed Philz touch recovery 6.48.4 and had no issues with it. So I went into recovery and did the 'clean to install new rom' option and then I installed the Beanstalk 4.4.285 rom and checked it out and then was going to wipe it and try out Paranoid Android 4.45 so I rebooted to recovery again using the script in Rom Toolbox which is how I had been rebooting in to recovery since having installed Philz Touch because it's just simpler than holding the hardware keys. I had never tried booting in to Philz recovery using hardware keys. So anyways once in recovery again I once again do the 'clean to install new rom' option and then I went to flash Paranoid Android and I get a message about (can't remember exactly what it said) root being lost and was asked If I want to (again not sure exactly what it said) push su back to system/xbin and I said yes at which point the phone rebooted and now I can not reenter Philz recovery. I have tried numerous key combos including V+,home, power ; V+,power : V-,Power : V-,home,power ; V-,V+,power, V-,V+,home,power and nothing. It just boots to the Samsung Galaxy SIII screen and sits there. When I tried the V-,Home,power combo I get a screen that reads something like "Warning a custom os can cause critical problems in phone and installed applications. If you want to download a custom OS press the volume up key...." I think that is download mode but not sure. How can I get back in to Philz and or regain root if lost and reflash back to Alliance? Hope I didn't brick it.
DuhCiphered said:
I was running Alliance rom and decided I wanted to try a couple different roms. I had previously installed Philz touch recovery 6.48.4 and had no issues with it. So I went into recovery and did the 'clean to install new rom' option and then I installed the Beanstalk 4.4.285 rom and checked it out and then was going to wipe it and try out Paranoid Android 4.45 so I rebooted to recovery again using the script in Rom Toolbox which is how I had been rebooting in to recovery since having installed Philz Touch because it's just simpler than holding the hardware keys. I had never tried booting in to Philz recovery using hardware keys. So anyways once in recovery again I once again do the 'clean to install new rom' option and then I went to flash Paranoid Android and I get a message about (can't remember exactly what it said) root being lost and was asked If I want to (again not sure exactly what it said) push su back to system/xbin and I said yes at which point the phone rebooted and now I can not reenter Philz recovery. I have tried numerous key combos including V+,home, power ; V+,power : V-,Power : V-,home,power ; V-,V+,power, V-,V+,home,power and nothing. It just boots to the Samsung Galaxy SIII screen and sits there. When I tried the V-,Home,power combo I get a screen that reads something like "Warning a custom os can cause critical problems in phone and installed applications. If you want to download a custom OS press the volume up key...." I think that is download mode but not sure. How can I get back in to Philz and or regain root if lost and reflash back to Alliance? Hope I didn't brick it.
Click to expand...
Click to collapse
I've used philz but only on my tablet. I prefer using terminal emulator to reboot if I need to. And the last part yes that is download mode. You can always try Odin
Sent from my SCH-I535 using Xparent ICS Tapatalk 2
ShapesBlue said:
I've used philz but only on my tablet. I prefer using terminal emulator to reboot if I need to. And the last part yes that is download mode. You can always try Odin
Sent from my SCH-I535 using Xparent ICS Tapatalk 2
Click to expand...
Click to collapse
I figured it out. I feel stupid though. I was really freaking out hoping I didn't brick my phone, couldn't you just hear the panic in my post. The first key combo I used to boot recovery was correct I just wasn't doing it right. I was pressing V+,home,power and waiting for the samsung logo before letting go and that's why it wasn't working. But I found out the correct method is to hold down V+ and home then hold down power also and wait for the phone to vibarate then let go of the power button but continue to hold down V+ and home until recovery boots.
I was about ready to try reflashing recovery via odin but I was a bit concerned about a few things when it comes to that. If I do need to use odin in the future is there a specific version I should use for the S3. I downloaded Odin3 v3.07 and also have 1.85. I know your phone needs to be in download mode to use it, so now I know how to boot to download mode at least. My bootloader is unlocked and I was wondering if using odin would lock it or affect that in anyway or have any other type of ill effect on my phone?
DuhCiphered said:
I figured it out. I feel stupid though. I was really freaking out hoping I didn't brick my phone, couldn't you just hear the panic in my post. The first key combo I used to boot recovery was correct I just wasn't doing it right. I was pressing V+,home,power and waiting for the samsung logo before letting go and that's why it wasn't working. But I found out the correct method is to hold down V+ and home then hold down power also and wait for the phone to vibarate then let go of the power button but continue to hold down V+ and home until recovery boots.
I was about ready to try reflashing recovery via odin but I was a bit concerned about a few things when it comes to that. If I do need to use odin in the future is there a specific version I should use for the S3. I downloaded Odin3 v3.07 and also have 1.85. I know your phone needs to be in download mode to use it, so now I know how to boot to download mode at least. My bootloader is unlocked and I was wondering if using odin would lock it or affect that in anyway or have any other type of ill effect on my phone?
Click to expand...
Click to collapse
No Odin has nothing to do with the bootloader.
Sent from my SCH-I535 using Xparent ICS Tapatalk 2
My model number is SM-G920F, after the new update my phone has been having issues, recently it just got stickstuck on the boot screen and I can't even do a hard reset, I downloaded the latest stock rom to see if that will work, after flashing successfully phone restarts but it's right back to the boot loop, I tried couple more times with the same results, I don't know what to do from here, I am out of ideas, will appreciate a lot if someone can try to help me with this problem, thanks
You downloaded and flashed the stock via the update on the phone or you do it manually? You just bricked your phone. You should be able to get into download mode. Flash the Rom update through odin, making sure you flashed the right model
Updated through OTA, my phone is international I'm thinking it's Malaysia, which I did download the stock rom and flashed it though Odin with no luck, I don't know if I have to flash something before flashing the rom? Thanks for the reply back
BA0714 said:
Updated through OTA, my phone is international I'm thinking it's Malaysia, which I did download the stock rom and flashed it though Odin with no luck, I don't know if I have to flash something before flashing the rom? Thanks for the reply back
Click to expand...
Click to collapse
You should have installed TWRP as a custom recovery first via Odin, then use TWRP to flash the ROM file.
Great how-to: how to root S6 5.1.1
If you're stuck on bootloop, try holding volume down button & power button at least 7 seconds, the phone should power off.
Put it in d/l mode then again, connect it to Odin and go ahead.
Good luck!
I tried that with no luck, I don't know what to do anymore? I ran out if ideas, thanks for the reply, any others that had same issue and got it fixed?
Have you tried the method on this thread:
http://forum.xda-developers.com/galaxy-s6/help/sm-g920f-stuck-samsung-logo-5-1-1-update-t3150727
There's no way that I can get into recovery to wipe data & cache for the fist step, when I do try to go into recovery, the blue guy comes up and nothing happens, thanks for the reply
Did you figure out a solution? I'm in the same boat.
Hi, this is not my first time flashing TWRP on this phone. And I have been successful so far.
Today I use Odin to flash TWRP, and it went through just fine (see screenshot), but when I enter the recovery mode, it says "Android system recovery <3e> LMY47X.G920FXXU2COH2 on top and I am very confused. I tried a few times and apparently I cannot enter TWRP while Odin kept telling me I have flashed it successfully...
Did you have "Auto-Reboot" ticked on Odin? On my Note 4 that used to mean the kernel would reflash the stock recovery upon booting. You need to untick this, turn the S6 off after flashing and then boot directly into recovery using power + home + vol up
Nope. On the S6 auto-reboot menas what it does. The phone gets rebooted after the flash is done.
To the OP: You used the correct file to flash? USed AP mode in ODIN?
I had same problem. I think you need to have rooted kernel through odin first. Idk, that us what i did.
Just so everyone knows how I solved this. I wiped everything and flash TWRP and it worked. I am not sure why, but that's how I got it to work.
Greetings, community
I had a hard time yesterday figuring out how to revive my Tab2... My device is (or was) a Tab 2 Wifi P5110 with the Germany 4.2.2 stock ROM installed.
I accidentially (...) flashed TWRP image with ODINs BL (!) option... (3.13) don't ask why... gave me no error... After that it wouldn't want to boot nor it wanted to go to recovery anymore... just a blank screen with backlight on. The only thing that still worked was the download mode.
So to rescue the OS I downloaded the stock 4.2.2 tar (Germany / DBT-P5110XXDMI1-20131118182728) and flashed it with ODIN 3.07 / AP. That worked without errors and after reboot the tablet booted normally to the GUI. :angel:
So far so good, but as I want to get a CustomROM to the device I wanted to get into recovery mode. I tried to get to stock recovery with Pwr+Vol- but the Android Robot didn't show up (I did before my BL-FLash... the day before) and I ended up with just a blank black screen (with backlight on). I tried flashing TWRP with ODIN 3.07 / AP with no other result.
How can I fix that? Have I destroyed some part of my bootloader (?) or bricked my recovery mode with that BL flashing action? What else can I do to get at least the stock recovery and/or TWRP back?
Anybody a glue?
Thanks in advance,
stefl0n