Hey. First time posting i think. I got a sm t-719 that was infinitely restarting. I tried changing everything software wise. Original Samsung Android and custom rims but nothing worked. Now i got TWRP bootloader on it that works. Should i replace the whole motherboard or what now? Thanks
i'm in the same predicament as you. Seems its all over the web,
but nobody really knows how to fix it.
Related
hi everyone. i've been following the forum here for awhile and finally decided to root my brand new NC. i autorooted from 1.1. i saw some things weren't working so i quickly decided to unroot back to factory settings. i unrooted by unregistering the device and turning off the power 8 times. my NC boots up fine, but it gets stuck on the "Registering your Device" page and just remains there with the circle spinning. i think i left it there for more than 30 minutes and nothing happens. has anyone experienced this before? if so, how did you fix it? any help would be appreciated.
sorry if this topic has already been asked - i tried searching but didn't find anything on this specific issue. if there's already a thread, please feel free to share the link with me. thank you!
EDIT: really need some help here... i tried to fix it myself (i know i shouldn't have) and might have made it even worse. i tried to re-autoroot my NC but just completely failed. it was not loading anything anymore, so i tried to unroot again by powering off 8 times. when i restarted, everything looked normal, except the bootloader screen was not stock. it brought me back through the normal tutorial and same thing with it getting stuck on "registering your device". could someone please provide a thorough walkthrough on how to reset to factory settings? i'm seeing all these threads throwing around all these acronyms that i don't understand. seems like i need to try running some clockwork rom but not even sure how to do that. please help!!
Bump, i have just encountered this problem and i need help as well.
Update:
actually just figured it out and heres what fixed my problem, i wasn't doing the factory reset part only the 8 reboot interruptions.
hxxp://nookdevs.com/Flash_back_to_clean_stock_ROM
Thanks for your post, even though no one ever helped. I was having the same problem and doing a clear data/factory reset from Clockwork Recover booted from an SD card did the trick for me.
y helo thar :3
Okay, to sum it up, today I bought a used Bell Samsung GT-i9000M and realized that the owner never updated his phone to Gingerbread (2.3) from his current version of 2.1. Basically, I did the same procedure as in THIS (EDIT: I think I just realized that the stops shown in that link, having next to nothing to do with updating your phone to 2.3 - kjawekjawen - post still stands, of course) post.
In Odin, everything seemed like a success, until (after Odin labeled it as a success apparently) my phone just started rebooting and rebooting, not getting past the first booting screen (that first black screen showing Samsung i9000 logo, I think).
I can still access the download mode, but my phone just doesn't boot up anymore (gets stuck on this same logo and just keeps restarting 'til the pigs come round).
I'm just afraid to do anything with my phone right nao. Consisder the fact that I am pretty much a noob in this whole hackz0r, elite department of the internets and cellphones. I would love (no homo, hurhurhur) for somebody to assist me through this, because I don't want to end up turning my cellphone into something resembling a clay brick.
:3
Thanks in advance for whoever could help me.
PROBLEM SOLVED: http://androidadvices.com/update-samsung-galaxy-gt-i9000-gingerbread-xxjvr-234-firmware/6/
So here's my problem. I think I've bricked my device. Don't know if it's softbrick or hardbrick, but either way my phone just does not boot up. The only instance it works is when I remove the battery and try to charge the phone, it shows a picture that it didn't find a battery. All of this occurred while trying to unlock the bootloader. Something similar already happened to me like a month or two ago, but I was able to flash stock KDZ using the online LG Support Tool. Anyway, the part where it all messed up is probably the aboot.bin file, although I'm quite certain I flashed the right file for my device. Also, installed CWM recovery, and after restarting the device it just won't boot at all, not even the software upgrade mode or anything. So my guess is that something is wrong because of either a wrong aboot.bin file for my D405N or the custom recovery. I tried flashing stock KDZ, but I couldn't get my phone into software upgrade mode. Also, tried doing a hard reset, but an LG logo didn't even come up. The battery is at least half full. So is there anything I can actually do in this case? Any help is appreciated.
P.S. Yeah, I did post in another thread (though I didn't create it), but I'm quite desperate with this. Either I fix it myself somehow, or I'll have to take it to the warranty.
EDIT: Took it to a repair. Should be done in around a week. Got an old Samsung Galaxy Mini as a replacement.
linasj said:
So here's my problem. I think I've bricked my device. Don't know if it's softbrick or hardbrick, but either way my phone just does not boot up. The only instance it works is when I remove the battery and try to charge the phone, it shows a picture that it didn't find a battery. All of this occurred while trying to unlock the bootloader. Something similar already happened to me like a month or two ago, but I was able to flash stock KDZ using the online LG Support Tool. Anyway, the part where it all messed up is probably the aboot.bin file, although I'm quite certain I flashed the right file for my device. Also, installed CWM recovery, and after restarting the device it just won't boot at all, not even the software upgrade mode or anything. So my guess is that something is wrong because of either a wrong aboot.bin file for my D405N or the custom recovery. I tried flashing stock KDZ, but I couldn't get my phone into software upgrade mode. Also, tried doing a hard reset, but an LG logo didn't even come up. The battery is at least half full. So is there anything I can actually do in this case? Any help is appreciated.
P.S. Yeah, I did post in another thread (though I didn't create it), but I'm quite desperate with this. Either I fix it myself somehow, or I'll have to take it to the warranty.
EDIT: Took it to a repair. Should be done in around a week. Got an old Samsung Galaxy Mini as a replacement.
Click to expand...
Click to collapse
Remember Next time Unlock Bootloader before Installing CWM.
Hi all,
I downloaded the latest TWRP from https://dl.twrp.me/i9305/ - twrp-2.8.7.0-i9305.img.tar 8.1M
I installed it with ODIN. The flash was a success and when the phone rebooted the touchscreen was unresponsive.
I have tried another version of twrp for this phone and I can get into twrp, but the touchscreen doens't work. I tried replugging in the ribbon lead for the digitiser and that made no difference.
Do you think its a software problem or that I have fried something?
Many Thanks
Andrew
Hi,
there are plenty of issues with TWRP and 2.8.7.0. I'm actually surprised you could even boot up your phone. The new recovery messes up with partition sizes and some other things.
I hope you have a backup of the current ROM as I suggest you to install Stock ROM again and stay on TWRP 2.8.5.0 and see if your phones works normally again
Hi,
thanks so much for replying. I still have the stock rom. All I have done is install twrp. I have tried doing a factory reset and it made no difference. I can still use the buttons on the phone, but the touchscreen remains unresponsive.
So if I download the stock rom for the phone and install you think it might make a difference?
Andy
Update:
Downloaded and installed stock rom from samsung (4.4) ... installed with success via odin. The phone boots and the screen is still unresponsive. I just cant believe I have broken the digitiser by installing twrp?!
Andy
Hi,
sorry for the late reply. I didn't get a notification via tapatalk. But anyway to come back to your issue: it's the first time I hear that a "corrupted" recovery could break the digitizer. I did the same mistake with the broken recovery but fortunately no issues afterwards. But apparently it's possible judging by some google search results.
I never had such issues and I don't know how to help you. Maybe there is a possibility to fix it.
Thanks for your reply
I hope there is a way of fixing it. It doesn't seem economical to fix this phone? The digitiser kit is around £60 ... Plus because I can't be 100% why this happened in the first place, it might happen again with a new digitiser?
Thanks
Andrew
I was looking here in Germany right now what I would have to pay for fixing the digitizer - between £50 and £60 as well, some even charging a little more. For £80 I could get a decent looking used S3 4G.
If I were you I'd rather buy another S3 again (or any other device) instead of trying to fix the broken one.
Did you tried to Flash stock recovery
Hey XDA folks. Ever since I updated to MIUI 14 the problem mentioned in the title happens. I swept the internet but couldn't find anything that actually worked except for a data wipe from the recovery menu. I got the problem solved (or so I thought) and spent a long time reinstalling everything. After another restart just now however the stupid black screen is back. My question is whether anyone here knows a working solution and if not please let me know how I can downgrade back to MIUI 13 without voiding my warranty. Many thanks in advance.
saeedaraam said:
Hey XDA folks. Ever since I updated to MIUI 14 the problem mentioned in the title happens. I swept the internet but couldn't find anything that actually worked except for a data wipe from the recovery menu. I got the problem solved (or so I thought) and spent a long time reinstalling everything. After another restart just now however the stupid black screen is back. My question is whether anyone here knows a working solution and if not please let me know how I can downgrade back to MIUI 13 without voiding my warranty. Many thanks in advance.
Click to expand...
Click to collapse
Are you unlocked? If yes, then you can ROM. I don't believe there is an effective downgrade in stock MIUI, but I could be wrong.