Hello i have a problem with my phone that suddenly i wake up and my phone was stuck at logo/loading screen i restarted and still stuck i tried most stuff on the internet to fix it and still no luck.
I ask for someone to help me with this problem since i need my phone and i can't find the stock rom for this phone maybe because i'm searching for the wrong stuff i don't know.
Things i tried:
Wipe/clean cache data etc- still same
Flash recovery.img through fastboot using "fastboot flash recovery recovery.img" -- still no luck and got error "recovery doesn't allow flash"
Downloaded some rom for this phone after searching the internet with this number that apparently it's the serial number that i get on "Android system recovery" 857413_v2.8_20150130 -- still nothing to help because after trying to install through adb i get error "installation aborted"
So if someone could help me out or tell me if i'm doing something wrong please tell me.
Thanks in advance.
Related
Ok so first off i have an x10i on 2.3.3 and rooted. I wanted to upgrade the kernel to DK, i did that and then i booted my phone and now its stuck on the DK xperia boot screen. Every time i reboot this happens. i can still get into xrecovery and connect to computer. Ive tried flashing it back but every time it says ABORTED. i tried repairing it with PC companion but it says that it cant update (i dont know why it has to update to repair but whatever). i have pretty much tried everything. i searched and searched for a sollution but nothing works. please help
urownreflection said:
Ok so first off i have an x10i on 2.3.3 and rooted. I wanted to upgrade the kernel to DK, i did that and then i booted my phone and now its stuck on the DK xperia boot screen. Every time i reboot this happens. i can still get into xrecovery and connect to computer. Ive tried flashing it back but every time it says ABORTED. i tried repairing it with PC companion but it says that it cant update (i dont know why it has to update to repair but whatever). i have pretty much tried everything. i searched and searched for a sollution but nothing works. please help
Click to expand...
Click to collapse
Hi! This may sound easy, but try changing your USB-port.. This could solve your ODIN problem.
Try Clearing Cache
Hey, try this, see what happens.
Get into recovery mode.
Select "Clear cache partition" BUT NOT "Factory reset"
after finishing, reboot
Hey guys hope someone can point me to the right direction or knows this problem:
Galaxy Tab 10.1 Wifi (P5110).
Device will only boot recovery no matter what. (both with stock or custom recovery AND stock or custom rom installed - tried all combinations already)
Stock rom has been installed with odin and pit-repartition has also been tried.
When I turn on the tablet it boots straight to recovery. On stock recovery it says something about update, then "no command" and when I then choose reboot system, it says error and powers the device off.
Please help.
nobody an idea?
I had this kind of behaviour on another device before - dont exactly remember if also was samsung - but the solution was to clear out a stuck OTA update which was stored in a special partition which would normally not get wiped of flashed over. (by reformating or writing it full with /dev/zero)
Thinking back I dont think it was a samsung device though - but the "error picture" is the same.
But in this case I'm unsure where ota updates would get stored other than cache partition. Already tried clearing out some partitions on this thing - since its a wifi only model - can I clear EFS or use "reformat all" (dunno how exactly that option is called in odin) without totally bricking it? (never had to do this but since I'm out of ideas... )
Please anyone.. =)
zroice said:
Hey guys hope someone can point me to the right direction or knows this problem:
Galaxy Tab 10.1 Wifi (P5110).
Device will only boot recovery no matter what. (both with stock or custom recovery AND stock or custom rom installed - tried all combinations already)
Stock rom has been installed with odin and pit-repartition has also been tried.
When I turn on the tablet it boots straight to recovery. On stock recovery it says something about update, then "no command" and when I then choose reboot system, it says error and powers the device off.
Please help.
Click to expand...
Click to collapse
Try rebooting while power is plugged in.
LāvLab / HostileSlothRecords
LavLab said:
Try rebooting while power is plugged in.
LāvLab / HostileSlothRecords
Click to expand...
Click to collapse
definitely tried that. But no longer have the device, so cant try it out again unfortunately. But thanks for your reply!
My phone (930A) seems to be stuck in a major bootloop or might even be bricked. Here's a list of issues I am having:
Get's to the AT&T screen, makes AT&T sound then freezes.
In recovery booting mode it says: DM-Verity Verification Failed
Factory Reset and wiping the cache does nothing
Bootloader itself freezes and doesnt get recognized by odin
Any help on this would be greatly appreciated
Yannks2424 said:
My phone (930A) seems to be stuck in a major bootloop or might even be bricked. Here's a list of issues I am having:
Get's to the AT&T screen, makes AT&T sound then freezes.
In recovery booting mode it says: DM-Verity Verification Failed
Factory Reset and wiping the cache does nothing
Bootloader itself freezes and doesnt get recognized by odin
Any help on this would be greatly appreciated
Click to expand...
Click to collapse
Sorry to hear it mate , but you are in the wrong forum
maybe here they can help you better
http://forum.xda-developers.com/att-galaxy-s7
Hi there, my mother have an XT1033 and some days ago the phone got bricked in a black screen. I don't know what she was doing when it happened, but i know that the phone have its storage almost full, maybe this is the cause.
But the problem is that i tried to do a hard reset, but got an "Boot up fail!" trying to access the Recovery.
So i tried to unlock the bootloader, aparently it was succesfull since i could access the Recovery. But the wipe data/cache option solved nothing and aparently no data was wiped.
I tried to flash a new recovery, got the "OKAY" output but the recovery stills the same. Tried to flash a stock rom and still nothing changed. And actually, for some reason the phone did a successfull boot after all this, and was still with the old system, with the same data as before, and spamming error messages on the screen untill going to the black screen again.
I tried almosst everything, someone have some tips?
And sorry, english is not my first language.
Hello, i've bought this Samsung SM-T210 like 3 years ago, i rooted it as soon as i got it and after a year or so i decided to go back to factory settings cos of too many trash files anyway as far as i can remember i've select the wipe data or somethin and it got stuck on "Boot Loop" thingy only samsung logo comes up over and over again till i turn it off so i have tried every single solution that i can find on google and forums best i could do was getting it out of boot loop, now it just directly boots into TWRP and i can not do anything over there can't install any roms nothing whenever i try to install somethin it just gives me bunch of errors with cant find cache, data etc . i saw people had same problem and they got solutions by installing a new os, rom whatever it's called, i know how to follow the instructions but those solutions about my problem didn't help at all, now after a year i've decided to fix it again do u guys have any other solutions about this ? i'm waiting for it the charge up gonna list the errors i get on each section of twrp. :crying: :crying: :crying:
When i press (power+home) i'm only getting a text on bottom left corner says POWER UPLOAD REASON: POWER KEY H/W REVISION : 0.3
(vlm down+power+home) only gets me to the black screen nothing comes up
(vlm up+power+home) TWRP interface
power key by itself does nothing anymore.
----
******i had access to download mode via adb by using "adb reboot download"
i tried to install my firmware using odin and surprisingly it started to work again and im sure i've tried this billions of time.***********
semavi said:
Hello, i've bought this Samsung SM-T210 like 3 years ago, i rooted it as soon as i got it and after a year or so i decided to go back to factory settings cos of too many trash files anyway as far as i can remember i've select the wipe data or somethin and it got stuck on "Boot Loop" thingy only samsung logo comes up over and over again till i turn it off so i have tried every single solution that i can find on google and forums best i could do was getting it out of boot loop, now it just directly boots into TWRP and i can not do anything over there can't install any roms nothing whenever i try to install somethin it just gives me bunch of errors with cant find cache, data etc . i saw people had same problem and they got solutions by installing a new os, rom whatever it's called, i know how to follow the instructions but those solutions about my problem didn't help at all, now after a year i've decided to fix it again do u guys have any other solutions about this ? i'm waiting for it the charge up gonna list the errors i get on each section of twrp. :crying: :crying: :crying:
When i press (power+home) i'm only getting a text on bottom left corner says POWER UPLOAD REASON: POWER KEY H/W REVISION : 0.3
(vlm down+power+home) only gets me to the black screen nothing comes up
(vlm up+power+home) TWRP interface
power key by itself does nothing anymore.
----
i had access to download mode via adb by using "adb reboot download"
i tried to install my firmware using odin and surprisingly it started to work again and im sure i've tried this billions of time.
Click to expand...
Click to collapse
I don't understand.
You're saying that you successfully flashed it with your firmware and it started working. Does this mean you don't have an issue now? Or is there still a problem?
I DO NOT PROVIDE HELP IN PM, KEEP IT IN THE THREADS WHERE EVERYONE CAN SHARE
yea i couldnt even open up the download mode it was saying RUN RDX TOOL but i just ignored whatever it says and tried to install it with odin till it succeeds after a few tries it just completed the installation and simply started to running.