Hello everybody,
I have an S3 Mini here that was in the water. I disassembled and dried it - but the display is not ok: It flickers, sometimes off, sometimes very dark and wrong colours. All buttons and the USB plug work.
So i thought about uploading TWRP with ODIN and boot into it (hoping that when TWRP is running, i cann access the file system). When i start it normal, it shows the unlock screen, but because i cannot touch i cannot unlock it.
I launched ODIN, downloaded the TWRP here from the forum, and i can flash it - but i cannot boot into the recovery. When i try it - the first samsung logo just stays and nothing happens anymore. Is there some more to do / may i have missed something ?
Or is there a different way to access the data?
Related
Hello guys, I have a big problem with my GT-I9001,
I have installed the clockworkmod and cyanogenmod by ivendor, (Alpha 7) http://forum.xda-developers.com/showthread.php?t=2000828
If I try to start my Galaxy it stuck's on the Splashscreen where I can see the Galaxy S Plus and the Cyanogenmod logo. After a few Minutes the screen goes of but you have to take the batterie out of the Handy to start it again.
If I try to boot into recoverymode, after the samsung logo the screen goes off, and again I have to take the batterie out.
At both Situations, if i touch the menu or return button it lights up, but not off anymore. At Situation 2 after a few Minutes.
The Download mode still works but if I try to Flash, for example with a Stock Firmware, it seems to go through with no problem, but instead of rebooting it only gets a blackscreen.
When i have flashed it and I start it the Splashscreen still has the Cyanogenmod logo on it, also if i flashed it with a Stockfirmware.
Another thing is, that if i try to charge my Smartphone, the normal shown batterie is stuck too.
Some people already mentioned the BroodRom, but on the download mode appears the Sentence: MMC boot: MBR read failed, and at Booting normaly is no change.
I tried to connect with adb to the Handy while it is on that black screen. It works, but if i try to enter: recovery --wipe_data, but in the cmd it only says: "/sbin/postrecoveryboot.sh not found" and nothing changed.
So this is the List of things that don't work or i already tried. I hope you guys will find a solution. If not i want to ask what Smartphone you would buy.
Problem found
I searched the whole net and i think i found the problem, It seems to be the memory controller.
I came to this because if i pushed something onto my Handy via adb it was there only till a restart. And some communities tell me, that the problem can be solved by exchanging the memory controller. But i don't think i can do that.
Hi all,
I use CM12 from MacLaw in combination with TWRP 2.8.1.0 recovery for about 3 weeks now.
Yesterday the phone didn't respond properly, was very very slow and I basically couldn't use the phone. It felt like the CPU was at 100% all the time, so unlocking the phone, calling and so was nearly impossible. A reboot (battery removal) didn't solve it, also the pin code for the sim card came after a few minutes while usually this will come right after starting.
So eventually I did a factory reset from the menu as I did on other occasions just to get rid of this kind of problems.
Well, right after the Samsung s3 mini logo I get the TWRP logo and it will be stuck in there, I see it blinking every few seconds and that's it. When I connect the phone to USB I hear it connecting-disconnecting every few seconds (bing-bong, bong-bing sound).
After a while I flashed TWRP using Odin again, this didn't give any problem but it will still hang in this TWRP loop.
I found some references to this problem but no real solutions. Someone suggested to use ADB but I don't know how to do that, nor could I find a suitable guide on this.
Can anyone help me? Or is it bricked somehow?? I suspect not, download mode is still working.
Thanks for any help!
my device was working fine after replacing the battery (0onite 2070mah) and screen. i lend the phone to a friend, when he tried to charge the device, it went to boot loop.
so my phone is stuck on boot loop ( it shows the blue motorola ( a google company) logo,on and off)
device wont charge,can only be on when connected to charger or laptop.
when i go to recovery mode,it blacks out in a second, then goes to startup
i dont know what to do. i got some flash tools from youtube.
Motorola drive
Driver Installation 6.4.0
and a firmware restore lock and more (cant post link)
help!
its not a rooted phone......
well,i dont know wich stickies i should read about my situation?
Hello,
First of all, sorry for my english as it is not my mother language
I've tried today flashing CM13 on my Wiko Rainbow, but I either failed following the instructions or the files I had were corrupted, leading to a never-ending boot.
I don't know if it was already a soft-brick back then, as the phone turned off while booting just after the installation, but 40min after it (obviously because of en empty battery, which was at 37% before installation)
At first, when the phone was plugged into the computer, the phone was booting up, showing the charging icon for a few seconds, and then was going into the infinite boot for 10 seconds, and then rebooting for the same process.
When I was charging the phone on a wall plug, the phone was just in an infinite loop.
The problem was that, when I did the Volume down + Volume up + power thing, I had a choice between Factory mode and Custom mode, but both of them led me to a black screen, and the phone powered off.
I then searched how to install a custom recovery with a soft-bricked phone, and I got a tutorial on SP Flash Tool, that told me to use a MT6582 scatter file, and to select only a Recovery. I downloaded a TWRP for my phone, and then started download, retracted the battery and plugged the phone on the computer.
I got this message : "brom error s_fthnd_file_is_not_loaded_yet"
The software told me to format the Flash, which I did, and this error now became this : "BROM ERROR : S_DL_GET_DRAM_SETTING_FAIL (5054)"
The thing is that now, the soft brick is now a hard brick, and I can't get the phone to boot anymore, adb doesn't recognize my device, and after installing and reinstalling my phone drivers, no solution came out yet, so I'm hopping that you'll find a solution to help my problem
Thanks.
Regards.
MichelFou said:
Hello,
First of all, sorry for my english as it is not my mother language
I've tried today flashing CM13 on my Wiko Rainbow, but I either failed following the instructions or the files I had were corrupted, leading to a never-ending boot.
I don't know if it was already a soft-brick back then, as the phone turned off while booting just after the installation, but 40min after it (obviously because of en empty battery, which was at 37% before installation)
At first, when the phone was plugged into the computer, the phone was booting up, showing the charging icon for a few seconds, and then was going into the infinite boot for 10 seconds, and then rebooting for the same process.
When I was charging the phone on a wall plug, the phone was just in an infinite loop.
The problem was that, when I did the Volume down + Volume up + power thing, I had a choice between Factory mode and Custom mode, but both of them led me to a black screen, and the phone powered off.
I then searched how to install a custom recovery with a soft-bricked phone, and I got a tutorial on SP Flash Tool, that told me to use a MT6582 scatter file, and to select only a Recovery. I downloaded a TWRP for my phone, and then started download, retracted the battery and plugged the phone on the computer.
I got this message : "brom error s_fthnd_file_is_not_loaded_yet"
The software told me to format the Flash, which I did, and this error now became this : "BROM ERROR : S_DL_GET_DRAM_SETTING_FAIL (5054)"
The thing is that now, the soft brick is now a hard brick, and I can't get the phone to boot anymore, adb doesn't recognize my device, and after installing and reinstalling my phone drivers, no solution came out yet, so I'm hopping that you'll find a solution to help my problem
Thanks.
Regards.
Click to expand...
Click to collapse
You're going to need the firmware (not just TWRP) to fix your phone. Have you been able to download it?
Hovatek said:
You're going to need the firmware (not just TWRP) to fix your phone. Have you been able to download it?
Click to expand...
Click to collapse
using SP Tool gives directly through the USB
I tried installing a custom ROM and rooting my Tab A 10.1 2019 and now it is stuck in a bootloop and will not turn off. What happens:
1. I get the Galaxy Tab A screen
2. Get a message about boot loader unlocked
3. Tablet starts showing the Samsung logo loading screen
4. Tablet restarts
I can't get it to break this loop, it won't even turn off., just keeps looping. Any advice?
When you see the boot-up logo quickly use adb to reboot into recovery and re-flash
Hi. How did manage the problem.? I have mine at the same behavior. Cable was dettached while flashing with Odin.
Can you still boot-up at all? i.e. does any boot screen show up? If the screen turns on make sure its plugged in and then use ADB reboot recovery to get back into recovery if it hasn't been overwritten. From there you can mount storage if its TWRP and push files to your device for the ROM, and then flash from recovery. Also you could try to find an app that can fully restore your device to factory, I know there are apps that can do that. Good luck bro. Try drfone?