Related
Hi,
I've flashed multiple times before without an issue until today.
First, here's my background information:
Samsung Captivate (ATT)
Was running Continuum 5.4.1 but it felt laggy so I attempted to flash MIUI 1.5.13.
Here's what I did:
I wiped my phone using the Odin One click tool, then flashed CM7's kernel and then performed formats of the cache, system, and data, then installed MIUI RC2. After this step the phone should have restarted, then I planned to shut it down and reboot into recovery and flash 1.5.13 onto it.
My problem(s):
-Boot into recovery/download mode using key combinations is not working.
-The ADB console reports device not found when I try to run adb shell.
-The phone is undetected in Droidexplorer.
-When I attempt to download an app to boot to recovery with the phone says there is no space even though nothing has been installed other then MIUI.
What I would like to do:
Get back to stock with download/recovery modes working.
On a side note: MIUI works, but in a very limited way. I can navigate through it, but it won't allow the installation of applications due to there not being room on the phone (as said before).
Thanks!
Update - my phone was being identified as a Nexus S, so without those drivers my phone could not be debugged via USB. I now have the drivers and can perform ADB commands, however rebooting into recovery and into download mode both result in the phone restarting without going to the download or recovery mode.
Try using ODIN and repartitioning. I have good videos on standard ODIN and Heimdall on YouTube just search them. If you can not get out of this contact me, I have been able to partition debrick in the past and it's actually considered by me far more annoying than standard bootloader JTAG in certain situations. Let's hope yours is easier to bail out of!
First of all thanks for the reply and direction.
Secondly:
After working on this all last night I was able to get the phone recognized by Odin and my computer, now I am stuck at one of two screens depending on what I do.
If the phone is powered off then plugged in, the battery charging screen appears but there is no animation and after unplugging it the battery charging image remains.
If I power the phone on it hangs on the Samsung boot screen.
Repartitioning does sound like the proper direction for me to take, but, when I use Odin it freezes while setting up the connection to the phone.
when the phone is powered off try holding both vol keys and plugging in the cable. That could possibly get you to download mode. If not try vol down/pwr at the same time since you are now on GB bootloaders the keys are a bit different. Let me know what happens and good luck
maybe you should try to build a jig and use it to get into the download mode first. or you can buy it on ebay, just search for "micro usb jig".
I've tried every volume and power combination possible to no avail, I can't get into download mode. I've given in and am exchanging my phone. Thanks for the help anyway guys!
OK, where do I begin with this one.......I will try explain things as they happened.
My i9000 took a fall along with me getting off a bus, I went over on my ankle and landed on my phone in my pocket.
When I looked at my phone everything seemed fine (with the screen at least) but I noticed the volume down button no longer worked.....so I rebooted and ever since my phone has only worked in 'safe mode' - I've never seen safe mode before, it boots the phone normally but it says safe mode in bottom left of homescreen and all the app's installed after the ROM are missing...
So, after taking my phone apart several times to see if I can find out why the down button doesn't work I came to the conclusion taking the volume down button completely off the PCB was my best bet. So I did this last night very carefully with a low heat soldering iron and hey presto my phone has booted normally for the first time in ages.... All my apps are there etc etc....
But now....................I have no baseband or imei, so I have no signal at all.
This is where lots of problems begin for me - my i9000 is running ICS333 ROM from on here and because the imei is buggered I want to get it back to GB stock using odin to see if my stock EFS backup will fix things....
I can't get any communication between my phone and odin because I can't get into download mode...
I've tried;
adb reboot download (this just reboots the phone back into the rom)
adb reboot recovery (this takes me to CWM recovery but doesn't work with odin)
an app that give different boot options, but download mode just doesn't happen.
Any advice guys? Oh, I've ordered one of these download mode jigs but it isn't here yet....
Hello All,
Hoping someone will be able to assist me, though I'm starting to lose hope.
I have spent all day so far reading threads, and trying various suggestions and fixes, but nothing has really helped and I'm beginning to think the phone may just be kaput.
Initial issue was nothing out of the ordinary; woke up to find the phone was not responding so pulled the battery. After putting the battery back in, the phone would no longer turn on. Uh oh. Did the obvious, repull the battery, try again. Nothing. Connect to charger (nothing happens, no charging icon on screen). At this point I think the battery has died so I bought a new one. No change, phone still won't turn on and nothing happens when I plug it in to charge.
So now I connect it to my PC, and I get the installing hardware message trying to install the APX stuff which fails. After some research, I manage to get the APX drivers installed such that the phone is detected when I plug it in. More research, decide to try the AOI Toolkit to backup everything first. This works ok.
So now I try and enter recovery mode via Power key + Volume Down key. Nothing. Ok, change the recovery image then. Device is not detected via ADB method. NVFlash method instead then. The bootloader loads fine, the screen wakes up and shows the S/W Download... message. I figure this is a hopeful sign. I try all 3 (ics-cwm-5, ics-cwm-6, twrp-2.5). They all flash successfully. However, I can't enter recovery mode with any of them. Once I disconnect the phone, insert the battery and then hold down the Power + Volume Down buttons, nothing ever happens.
I've also tried the LG Update Tool and the Smartflash options, but the phone is never detected.
As a last resort I repartitioned. This also worked ok, but still no recovery mode.
tl;dr
Phone won't turn on, show as charging, or enter recovery mode. Works when connected as APX with AOI Toolkit.
Am I missing something? Doing something wrong? Any assistance is greatly appreciated. Thx.
Bump
Okay, I'm bumping this thread myself (mostly because I'm an idiot and this could happen to me, too), but to give you my two cents: Have you tried the Full Brick Repair tool? You flash it through NVFlash and apparently "it cures any brick". Try it and tell us how it went.
NoDze said:
Okay, I'm bumping this thread myself (mostly because I'm an idiot and this could happen to me, too), but to give you my two cents: Have you tried the Full Brick Repair tool? You flash it through NVFlash and apparently "it cures any brick". Try it and tell us how it went.
Click to expand...
Click to collapse
Thanks for the suggestion. The flash process itself completed without issue, but still nothing once the battery is inserted and the power button is pressed. I'm going to assume there is some sort of hardware issue at this point and consider the phone officially dead. Now, where's my hammer...?
xda_fanboy said:
Thanks for the suggestion. The flash process itself completed without issue, but still nothing once the battery is inserted and the power button is pressed. I'm going to assume there is some sort of hardware issue at this point and consider the phone officially dead. Now, where's my hammer...?
Click to expand...
Click to collapse
Don't give up yet. Try smartflash and flash stock, or whatever. Seriously. Just keep on trying. I had a Samsung Captivate a year back and something similar happened where I woke up one beautiful morning, tried to unlock my phone: no response. I thought I had an SOD, so I pulled the battery out, reinserted: bootloop. Entered recovery, can't flash anything, unable to mount system/data partitions. Turns out my internal memory/ROM got fried. Yay. But until then, I tried every possible option. Wow, this turned out to be a bit depressing. Just try more stuff. After you've tried everything, and I mean everything, declare the phone dead.
I think i have a similar problem. Just woke up to find my phone to be dead. Tried the usual methods, nothing. Best it could do was from time to time show me a battery sign with a red triangle and a whtie exclamation mark in it. Then sometimes i manage to get into the recovery mode, there i tried practically everything. Used restore, it shows that restore was a success, but when i reboot my phone i get into an endless circle of bootloader icon appearing and dissappearing,
EDIT: somehow from the countless attempt it fired up.
Make sure to have the right bootloader before nvflashing unbrick roms....
xda_fanboy said:
Hello All,
Hoping someone will be able to assist me, though I'm starting to lose hope.
I have spent all day so far reading threads, and trying various suggestions and fixes, but nothing has really helped and I'm beginning to think the phone may just be kaput.
Initial issue was nothing out of the ordinary; woke up to find the phone was not responding so pulled the battery. After putting the battery back in, the phone would no longer turn on. Uh oh. Did the obvious, repull the battery, try again. Nothing. Connect to charger (nothing happens, no charging icon on screen). At this point I think the battery has died so I bought a new one. No change, phone still won't turn on and nothing happens when I plug it in to charge.
So now I connect it to my PC, and I get the installing hardware message trying to install the APX stuff which fails. After some research, I manage to get the APX drivers installed such that the phone is detected when I plug it in. More research, decide to try the AOI Toolkit to backup everything first. This works ok.
So now I try and enter recovery mode via Power key + Volume Down key. Nothing. Ok, change the recovery image then. Device is not detected via ADB method. NVFlash method instead then. The bootloader loads fine, the screen wakes up and shows the S/W Download... message. I figure this is a hopeful sign. I try all 3 (ics-cwm-5, ics-cwm-6, twrp-2.5). They all flash successfully. However, I can't enter recovery mode with any of them. Once I disconnect the phone, insert the battery and then hold down the Power + Volume Down buttons, nothing ever happens.
I've also tried the LG Update Tool and the Smartflash options, but the phone is never detected.
As a last resort I repartitioned. This also worked ok, but still no recovery mode.
tl;dr
Phone won't turn on, show as charging, or enter recovery mode. Works when connected as APX with AOI Toolkit.
Am I missing something? Doing something wrong? Any assistance is greatly appreciated. Thx.
Click to expand...
Click to collapse
Try to flash a new recovery image in apx mode.
And edit the /dev/block/mmcblk0p3 partition your self.
seek=6144 count=75 bs=1 / boot-recovery
Thanks for the added input and encouragement folks.
Just reporting an update:
Having been unsuccessful more times than I could count, I decided to physically disassemble the phone (normally Engineering fix #2, but performed out of order on this occasion). I have zero idea why it should have made a difference, as all I did was take it apart and then put it back together, but the phone has groaned back to life.
Of course, then sausage-fingers here managed to tear the digitizer cable when doing the final reassambly... /facepalm
Anyhow, I have a replacement on order, so I'm hopeful that when I receive that in a few days I'm back to a fully functional Optimus 2x!!
Greetings,
My internal sd card died slowly over time. It failed to mount on some occasions at first. After a few weeks I had massive app crashes.
Everything I did on the phone (installing apps, deleting files, even doing a factory reset) seemed to revert back after rebooting the phone. I mean I delete some files, and after reboot, the files came back from the dead. Same thing for factory reset.
Installing other roms made the situation even worse, and I had to revert back to stock 2.3 rom.
And since last week, the phone is on permanent bootloop. It won't go into download or recovery mode (it used to activate those modes with 3 button combo before).
I tried the USB JIG method. Built a 301k resistor, connected pins to the usb thingie. It did power the phone on, but failed to trigger the download mode. The phone still goes into a boot loop.
Anyone has any ideas? I don't know what more information I can provide about the issue.
Regards,
No download mode?
If your phone won’t enter download mode, you can try three things:
A USB jig. Don’t pin your hopes on this, they rarely succeed in this scenario.
‘Jump starting’ – You might need someone else to give you a hand for this. Take the battery out of your phone and wait 30 seconds. Now, press the button combination to enter download mode, and with this combination still depressed, get someone to put the battery back in. Hopefully this will jolt your phone into download mode.
Take out the phone battery, and re-insert it, but don’t turn the phone on. Now, plug in the charger while holding the volume down button. Keep holding volume down till you enter download mode.
If your phone won’t enter download mode, and will do nothing but get hot when you attempt to do anything to it (charge it, turn it on), then your motherboard is in need of replacement.
Your options
I’ve seen a lot of people, when their Odin flash fails, either:
Give up. Not a good option.
Flash a .pit file. That should be used as an absolute last resort. There’s a lot to try before getting to that stage! If a flash of a .pit file fails in Odin, your phone is well and truly unrecoverable, and you will need a motherboard (MB) replacement.
Quoted from a quite by Hopper8, try these steps. Can't really do anything since recovery/download mode is dead. If you can get into download mode, flash a .pit file (get all the files ready beforehand). Be quick, since you don't know when your device will die again.
N7105 rocking AOSB with AGNi kernel,
Click "Thanks" if I was of any help!
FraggyDav said:
Greetings,
My internal sd card died slowly over time. It failed to mount on some occasions at first. After a few weeks I had massive app crashes.
Everything I did on the phone (installing apps, deleting files, even doing a factory reset) seemed to revert back after rebooting the phone. I mean I delete some files, and after reboot, the files came back from the dead. Same thing for factory reset.
Installing other roms made the situation even worse, and I had to revert back to stock 2.3 rom.
And since last week, the phone is on permanent bootloop. It won't go into download or recovery mode (it used to activate those modes with 3 button combo before).
I tried the USB JIG method. Built a 301k resistor, connected pins to the usb thingie. It did power the phone on, but failed to trigger the download mode. The phone still goes into a boot loop.
Anyone has any ideas? I don't know what more information I can provide about the issue.
Regards,
Click to expand...
Click to collapse
My little sister had the same problem.
But now the phone is complete dead.
Not booting after bootloop.
No customroms ever installed.
Dear all,
I have a Samsung Galaxy Tab S2 8.0 WIFI purchased last year (exactly to the day) in Cali. I believe it came with 5.1.1 XAR version.
A month later, my troubles began. I flashed with 6.0 Samsung WIFI ROM from some other country and the tab soon started to randomly turn off while being used. I am not sure if this is coincidental or not. When restarted, it would sometime fully boot, only to turn off while doing any mundane task surfing etc. and at other times, start and turn off as soon as the SAMSUNG logo comes. Weirdly, when I wait a day or two, it would start fully and work for a few minutes to half an hour
When I put it to charge, only rarely does the green battery logo came up, but most frequently I got a flashing thunderbolt sign.
I sent it to Samsung and it came back apparently with the correct firmware installed and the repair note said, faulty data cable replaced. But in a week of usage, the same problems started. I don't live in the US currently and so I don't have local warranty and don't have any means to send it back to Samsung USA. I've tried all remedies I could find, charging it to 100%, holding volume down and power for 15-30 seconds to simulate a battery reset, etc. to no avail. These days. it wouldn't even stay on long enough to access recovery mode, before turning off.
Yesterday, I installed Nougat 7.0 ROM from XAR on it and tried to start it. same problem. It says updating applications xx out of 26, and then turn off. When I try to access recovery, I got the android logo and when it gets to "Erasing", it would turn off. Then now that the warranty has expired, I installed TWRP (twrp_3.1.0-1_sm-t710_13317.tar) and this time I somehow goto to TWRP recovery mode, I just left it on there to see how long it would last, instead of immediately erasing the caches and restarting.
After that once, I couldn't get it to stay on long enough to access recovery. So I tried to go back to OEM ROM using Smart Switch, but to no avail once again. The Download mode still says Custom even after Smart Switch emergency recovery
I have tried flashing various other things (5.1.1 Samsung ROM, 6.0 ROM from UK with AP, BL and CSC files, TWRP 5.1.1 permissive ROM, TWRP), in various jumbled orde,r out of frustration. Nothing worked. here's a list of ROMs I've tried:
T710XXU2DQCL_T710UVS2DQC1_EON
SM-T710_1_20170406180713_vd28gnex7t_fac
SM-T710_1_20170330211239_qkurg70e9y
5.1.1_T710XXU1BOH7_T710XAR1BOH7_XAR
twrp_2.8.7.1_LL_5.1.1_t710
twrp_3.1.0-1_sm-t710_13317
t710_5.1.1_boot
Right now, the only thing I can access is Download mode and it says Current Binary: Custom, System Status: Custom, AP SWREV B:2 K:0 S:0 and worse than before, the tab turns off at the Powered by Android logo and when I plug it in, it doesn't charge but I get this boot loop (with the just the powered by android screen flashing)
would it help to re-partition and nand erase all and install a fresh ROM with a PIT file, if so can someone please share me their PIT file for this model??
I am out of ideas, and ready to break this expensive brick
appreciate any help,
thanks
V
vvsarana said:
Dear all,
I have a Samsung Galaxy Tab S2 8.0 WIFI purchased last year (exactly to the day) in Cali. I believe it came with 5.1.1 XAR version.
A month later, my troubles began. I flashed with 6.0 Samsung WIFI ROM from some other country and the tab soon started to randomly turn off while being used. I am not sure if this is coincidental or not. When restarted, it would sometime fully boot, only to turn off while doing any mundane task surfing etc. and at other times, start and turn off as soon as the SAMSUNG logo comes. Weirdly, when I wait a day or two, it would start fully and work for a few minutes to half an hour
When I put it to charge, only rarely does the green battery logo came up, but most frequently I got a flashing thunderbolt sign.
I sent it to Samsung and it came back apparently with the correct firmware installed and the repair note said, faulty data cable replaced. But in a week of usage, the same problems started. I don't live in the US currently and so I don't have local warranty and don't have any means to send it back to Samsung USA. I've tried all remedies I could find, charging it to 100%, holding volume down and power for 15-30 seconds to simulate a battery reset, etc. to no avail. These days. it wouldn't even stay on long enough to access recovery mode, before turning off.
Yesterday, I installed Nougat 7.0 ROM from XAR on it and tried to start it. same problem. It says updating applications xx out of 26, and then turn off. When I try to access recovery, I got the android logo and when it gets to "Erasing", it would turn off. Then now that the warranty has expired, I installed TWRP (twrp_3.1.0-1_sm-t710_13317.tar) and this time I somehow goto to TWRP recovery mode, I just left it on there to see how long it would last, instead of immediately erasing the caches and restarting.
After that once, I couldn't get it to stay on long enough to access recovery. So I tried to go back to OEM ROM using Smart Switch, but to no avail once again. The Download mode still says Custom even after Smart Switch emergency recovery
I have tried flashing various other things (5.1.1 Samsung ROM, 6.0 ROM from UK with AP, BL and CSC files, TWRP 5.1.1 permissive ROM, TWRP), in various jumbled orde,r out of frustration. Nothing worked. here's a list of ROMs I've tried:
T710XXU2DQCL_T710UVS2DQC1_EON
SM-T710_1_20170406180713_vd28gnex7t_fac
SM-T710_1_20170330211239_qkurg70e9y
5.1.1_T710XXU1BOH7_T710XAR1BOH7_XAR
twrp_2.8.7.1_LL_5.1.1_t710
twrp_3.1.0-1_sm-t710_13317
t710_5.1.1_boot
Right now, the only thing I can access is Download mode and it says Current Binary: Custom, System Status: Custom, AP SWREV B:2 K:0 S:0 and worse than before, the tab turns off at the Powered by Android logo and when I plug it in, it doesn't charge but I get this boot loop (with the just the powered by android screen flashing)
would it help to re-partition and nand erase all and install a fresh ROM with a PIT file, if so can someone please share me their PIT file for this model??
I am out of ideas, and ready to break this expensive brick
appreciate any help,
thanks
V
Click to expand...
Click to collapse
Well i hve the same problem like you.. idk wht should i do with this condition.. bootloop.. always restart until logo.. :crying:
Please anyone help to solve our problem..
Your issue seems related to power. It seems your device doesn't charge correctly and is turning off due to running out of battery.
What does TWRP report as the charge state?
Do you get the same issue when the device is plugged in to the mains?
ashyx said:
Your issue seems related to power. It seems your device doesn't charge correctly and is turning off due to running out of battery.
What does TWRP report as the charge state?
Do you get the same issue when the device is plugged in to the mains?
Click to expand...
Click to collapse
hi ashyx, I am pretty sure that battery isn't the issue here. even though the grey battery logo with a thunderbolt flashes while turned off and plugged in for charging, after a while it does charge anyhow. I can get it to 100%. Plugging in makes no difference.
I am thinking it could be a power button problem or a faulty usb port perhaps, if it is indeed a hardware fault?
vvsarana said:
hi ashyx, I am pretty sure that battery isn't the issue here. even though the grey battery logo with a thunderbolt flashes while turned off and plugged in for charging, after a while it does charge anyhow. I can get it to 100%. Plugging in makes no difference.
I am thinking it could be a power button problem or a faulty usb port perhaps, if it is indeed a hardware fault?
Click to expand...
Click to collapse
Did you ever resolved this issue? Curious if you have a solution.