A few months ago, I successfully rooted my SM-A105FN/DS with Magisk and Odin. I remember I had TWRP on there, but I think I flashed my phone again, therefore causing my phone to lose TWRP. I recently decided to install the TWRP recovery again, yet I installed the wrong recovery, and after flashing with Flashify and rebooting, I was met with a boot loop. I only saw the Samsung logo with the official software warning and bootloader unlock warning. This would restart constantly until I plugged in my phone, to be met with the logo stuck on the screen. I cannot enter adb, fastboot, Odin mode or recovery mode. My PC doesn't recognise it. I spoke to some Samsung support people online, and they hand no clue whatsoever. I don't want to pay for a repair (I doubt they'd repair it anyways because I have bricked it with a rom and have rooted it). Is it possible to fix it with software, and if not, how can I, and is it possible to replace it with the motherboard of another A10?
you solved that?
i have the same problem, this situation is very nerve wrecking. anyone got a fix on this one?
You cold try to wait until the battety get flat,then you hold vol + and - buttouns then plug into a computer,you should see the download mode
can you open the fastboot mode with volume down + power? it may enables the odin again
Related
I used Odin yesterday to Flash the new JI6 OTA update, after doing so it Odin said Pass but on my phone the error message read:
E:Cant mount/dev/block/stl10
I flashed stock ROM T959UJFD prior to flashing the new JI6 and went without cause. I pretty comfortable with Odin and have used it many times.
After the error the phone with boot up into the Vibrant Boot screen then go straight to Recovery. I tried rebooting and same result.
I tried Deleting all user data and same result.
I tried all the options available in recovery and still will only boot into recovery mode.
I tried plugging it into my pc and using adb to reboot into download mode but it will only reboot back to recovery.
When i have it Plugged into my pc and Odin open, Odin sees the device and opens up the COM line but won't do anything unless its in download mode.
Any help would be appreciated. "Crap now I'm one of those threads"
Ugh... I know this problem all too well. Did you click on the partition option in Odin when flashing to JI6??? If so, I hope you don't have a hardware locked phone!
Edit: Should probably elaborate a bit more.
To fix this simply get yourself into download mode manually by powering off your phone/removing battery/etc, and then power it back up while holding vol up + vol down. There are numberous methods to get into this mode unless you're hardware locked like me. Hopefull this will throw you into download mode and allow you to flash back to stock rom. If you're able to get this far simply try flashing the update again.
If you're hardware locked the only way I know of to fix the phone is either have TMO replace it with a phone that's not HW locked, or get Samsung's customer service center to give you an RMA for replacement. Either should work since what is now an official update borked your phone. I'm still waiting for my wife's phone to be returned in a hopefully non-Hw locked state. We'll see!
Good luck!
Mod close thread please, phone being replaced.
Hello,
I have a S3 which is stuck in a bootloop at the samsung logo.
when i turn it on it shows the logo for some seconds then the screen goes black and the logo re-appears.
i can not boot into recovery mode, but download mode is working without a problem every time.
i tried flashing stock firmwares with odin and also tried kies emergency firmware recovery. the flashing always went without any problem, but it had effect. whatever i try, i am never able to boot into recovery and still stuck in the bootloop.
in some tries after flashing the screen just shows the samsung logo forever, but after rebooting it once it then is stuck in a bootloop again (shows the logo - screen goes black - shows the logo...)
i also tried flashing TWRP and CWM via odin, but again i can never boot into recovery mode.
what should i try next?
thx alot for any helpful comment
Varjo said:
Hello,
I have a S3 which is stuck in a bootloop at the samsung logo.
when i turn it on it shows the logo for some seconds then the screen goes black and the logo re-appears.
i can not boot into recovery mode, but download mode is working without a problem every time.
i tried flashing stock firmwares with odin and also tried kies emergency firmware recovery. the flashing always went without any problem, but it had effect. whatever i try, i am never able to boot into recovery and still stuck in the bootloop.
in some tries after flashing the screen just shows the samsung logo forever, but after rebooting it once it then is stuck in a bootloop again (shows the logo - screen goes black - shows the logo...)
i also tried flashing TWRP and CWM via odin, but again i can never boot into recovery mode.
what should i try next?
thx alot for any helpful comment
Click to expand...
Click to collapse
You can Try this:
1.) Pull out battery
2.) Put it in again
3.) Press Vol up + home + power
4.) When the Samsung Logo appears let it off
I think you press the Buttons too long.
I had the same problem!
S1ay3r666 said:
I think you press the Buttons too long.
Click to expand...
Click to collapse
i really tried everything, it's not working. btw with i am stuck at the very first image, where it says "samsung Galaxy sII GT-I9300".
i dont think it's just the way i press the buttons because i can reach it on my s1 and s2 without a problem, it's just not working on this device.
could some setting like "nand erase all" in odin help? in other threads there is sometimes mentioned that the internal file system might be screwed up and in those cases a simple odin reflash does not help anymore...
Nand erase will usually hard brick it. Try the rescue firmware from general forum, sticky thread. Follow the guide exactly as it includes a pit file.
Sent from my GT-I9300 using Tapatalk
boomboomer said:
Try the rescue firmware from general forum, sticky thread. Follow the guide exactly as it includes a pit file.
Click to expand...
Click to collapse
thx, but i already did that (multiple times) and flashing via odin always succeeds. then the phone reboots and is stuck at the first samsung galaxy s.. screen. twice i managed somehow to get into recovery (after flashing cwm6) but it then randomly rebooted.
and i dont think that the power button is stuck because when i am in download mode it is perfectly fine it never reboots itself unexpectedly.
Had a similar issue on my tab2 p3100. It all happened when I tried flashing a custom recovery from rom manager.
A bad flash of anything related to recovery or bootloader could be a probable cause.
I remember a knowledge share on one of the threads describing this issue and as mentioned on it all I had to do is this:
1) switch off the device and plug in the charger. This would light up the display showing you the charging status. The status has to show if at least your bootloader part of the phone is fine.
2) plug out the charger and immediately press the three buttons (home + vol up + power) get into recovery mode. This step has to work and help you get to recovery mode.
***Note : the interval within which this step has to be performed is too short since the display would turn off immediately as soon as you plug out the charger. A bit tricky too so you have to be fast. If this misses getting you into recovery, pull out the battery and put it back again. Repeat step1 and 2 again.
3) upon successfully getting into recovery, perform wipe data, cache and select reboot phone from option available on recovery again.
Allow the device to boot. This could take a while since you have performed a data wipe and may prompt for first time set up.
I was able to restore functionality on my tab after these steps and like ppl learn from their mistakes, I then learnt that recoveries and bootloaders are things that needs to be done with a pc only.
Worth a try if you have tried other alternatives and found no go. may help. Who knows..
all the best.
thats also not working. i tried to get into recovery since two days now...
i also tried the steps from this thread: http://forum.xda-developers.com/galaxy-s3/help/solved-pit-bricked-dead-problem-gt-t2535367
but again, after i flash the cf-root (successfully) the phone does neither boot into recovery by itself nor can i do it by hand...
its crazy... in download mode i can see the model number (GT-I9300) and i thought as long as the model number is there and i can enter download mode there should be a way to recover the device.
but i cannot think of anything to try that i have not done yet
If the rescue firmware didn't help then it looks like the emmc chip is damaged.
Sent from my GT-I9300 using Tapatalk
boomboomer said:
If the rescue firmware didn't help then it looks like the emmc chip is damaged.
Click to expand...
Click to collapse
is there a way to make certain of this? how can i tell if it is really a hardware damage and not just a software brick?
i just dont want to let the phone go, it looks still so shiny
is there anything else that could cause the phone not booting into recovery mode after flashing custom recoveries?
Varjo said:
is there a way to make certain of this? how can i tell if it is really a hardware damage and not just a software brick?
i just dont want to let the phone go, it looks still so shiny
is there anything else that could cause the phone not booting into recovery mode after flashing custom recoveries?
Click to expand...
Click to collapse
http://forum.xda-developers.com/gala...-help-t2737707
Same here, still didn't found how to fix it.. I guess our motherboard just died..
Howewer I have a solution that "almost" worked for me.
Get a stock firmware in odin and turn on Nand erase and T-flash
When it's done phone reboots and you'll see just "Downloading..." mode when you turn it on.
Then got to Kies and Select firmware recovery...
Enter s/n and model name and wait for the flash to complete.
With it , I got past boot logo and actually booted into android but the phone crashed because I guess I have a memory issue..
Well , gl. If you don't find anything else helpful , try going with this method..
Had a problem with my htc one m8, so i pulled out my i9100 backup phone.
it had neat rom 4.1.2 on it, and everything was working fine.
i have tried to flash onmi rom():
1. entered recovery mode
2. backed up CWM to external SDCARD.
3.flased "CWM-KitKatCompatible-i9100.zip" & rebooted into new recovery.
4.installed "omni-4.4.2-20140214-i9100-INFECTED.zip".
5.installed "pa_gapps-modular-micro-4.4.2-20140207-signed.zip"
6.installed "UPDATE-SuperSU-v2.46.zip".
after that, when i wanted to reboot, i got a message saying i could loose su and if i want to fix it, i choosed "NO".
device entered to a boot loop.
i tought no biggy, i would go back to recovery, flash philz CWM and recover my nandroid backup.
it will not get into recovery mode.
tried again, pulled the battery, put it back, hold down VOL-Down+home+power button, and nothing, boot loops over and over again.
tried to get into download mode, not going there as well.
connecting to a pc with ADB+samsung drivers, the device wont show up.
Any suggestions? did i bricked the phone forever?
K-a-M-u-Z-u said:
Had a problem with my htc one m8, so i pulled out my i9100 backup phone.
it had neat rom 4.1.2 on it, and everything was working fine.
i have tried to flash onmi rom():
1. entered recovery mode
2. backed up CWM to external SDCARD.
3.flased "CWM-KitKatCompatible-i9100.zip" & rebooted into new recovery.
4.installed "omni-4.4.2-20140214-i9100-INFECTED.zip".
5.installed "pa_gapps-modular-micro-4.4.2-20140207-signed.zip"
6.installed "UPDATE-SuperSU-v2.46.zip".
after that, when i wanted to reboot, i got a message saying i could loose su and if i want to fix it, i choosed "NO".
device entered to a boot loop.
i tought no biggy, i would go back to recovery, flash philz CWM and recover my nandroid backup.
it will not get into recovery mode.
tried again, pulled the battery, put it back, hold down VOL-Down+home+power button, and nothing, boot loops over and over again.
tried to get into download mode, not going there as well.
connecting to a pc with ADB+samsung drivers, the device wont show up.
Any suggestions? did i bricked the phone forever?
Click to expand...
Click to collapse
Are you sure that the phone doesn't boot into the download mode(Vol Up+Powe+Home) ??
If that's the case, then I'm afraid that your phone is hard bricked forever. You have to fix/replace the motherboard then(about $50). You can go to the service center and get it done, or check out this video(JTAG METHOD): https://www.youtube.com/watch?v=zN7le4GmxZs
I hope something works out for you.
Regards
warrior1208 said:
Are you sure that the phone doesn't boot into the download mode(Vol Up+Powe+Home) ??
If that's the case, then I'm afraid that your phone is hard bricked forever. You have to fix/replace the motherboard then(about $50). You can go to the service center and get it done, or check out this video(JTAG METHOD): https://www.youtube.com/watch?v=zN7le4GmxZs
I hope something works out for you.
Regards
Click to expand...
Click to collapse
yes, i'm sure :'( its not my first time with the device.
i have ordered a usb jig from ebay, maybe it will force the device into download mode...if not... :\
just got my USB jig i have ordered from ebay(less than a dollar), plugged it to the phone, and it got into download mode!
used odin to flash stock rom, and then installed cyanogenmod with the cm installer.
everything is working fine!
I know this is late, but I wanna ask a question. Firstly I'm happy that your bricked phone came back to life(like how many years ago).
Can a USB jig work on any other phone brand other than Samsung phones? Can it be used for tecno, infinix, and all that? Or it is dedicated to only Samsung mobiles?
Hi there,
I need your help with my device which I just bricked in a peculiar way...
So, something I flashed was not correct. That resulted in an infinite reboot loop (the logo is shown for half a second and it reboots... endlessly). I just used the volume-up rocker to go into fastboot mode to fix the thing as I usually do. I booted into fastboot and this is where it become weird: I cannot do anything!
If I try to use fastboot continue, the phone reboots endlessly again.
If I try to boot to any img (TWRP or signed recovery or signed boot), the device tells me it cannot because it is locked.
If I try to unlock the bootloader (again, because it was), I am told that I am not allowed to do it. The problem is that I cannot boot into a ROM to go into dev mode to allow this.
If I try to flash things, it obviously doesn't work either as the bootloader is considered locked.
The worse here is that since my phone is "not" hard-bricked, I cannot go into qhsusb_bulk mode and use Qualcomm tools to unbrick the thing.
Can I still do something myself or am I screwed?
Lltp said:
Hi there,
I need your help with my device which I just bricked in a peculiar way...
So, something I flashed was not correct. That resulted in an infinite reboot loop (the logo is shown for half a second and it reboots... endlessly). I just used the volume-up rocker to go into fastboot mode to fix the thing as I usually do. I booted into fastboot and this is where it become weird: I cannot do anything!
If I try to use fastboot continue, the phone reboots endlessly again.
If I try to unlock the bootloader (again, because it was), I am told that I am not allowed to do it. The problem is that I cannot boot into a ROM to go into dev mode to allow this.
If I try to flash things, it obviously doesn't work either as the bootloader is considered locked.
The worse here is that since my phone is "not" hard-bricked, I cannot go into qhsusb_bulk mode and use Qualcomm tools to unbrick the thing.
Can I still do something myself or am I screwed?
Click to expand...
Click to collapse
Still you can do that hard brick recovery method it will work for sure..switch off your phone completely and try to connect qhsusb mode.
I had no idea that I could force the qhsusb mode. It worked indeed. Damn ARM devices with their non-standard way of doing anything...
Hello,
Im new here and im not sure if here is the correct place to ask questions but,
I have a Huawei Y5 II and i was trying to put android 6.0 or higher but i had alot of problems.
I first unlocked my bootloader and then installed a custom recovery TWRP and CWM on it, but i never succeeded in booting into one of them.
What happened is that i saw in a post here on xda that with a certain command in fastboot mode i can remove the custom recoveries ( because they didnt work at all) but when i did it i ended up formatting my whole system,cache and boot.
Now my phone just stays on the huawei logo when i turn it on and nothing else.
i tried to install a custom recovery again throught the fastboot mode using adb on my pc, but when i press the vol up+ power my phone just keeps restarting and restarting and staying on the logo.
Thanks in advance for your time spent on reading my problem i just wanna use my phone again cuz i love it. <3
Hi, try to flash latest stock firmware for SD update here is example but do for your model and region !!!
http://huawei-firmware.com/rom/huawei-y5ii/cunu29/1719
Good Luck
Thanks you, but i would do that if i had access to my recovery!
If i press the keys my phone just restarts and restarts until i let the keys off, then again... just the logo.
my phone still is in warranty and i can give it to my distributor so their service fixes it.... but i dont really want that.. i just wanna fix it and use it as before.
well..
i had my phone to service and i got it fixed for 100 bucks. :/ i really am a sadman