Hello,
I hope someone can help in this weird situation that I try to explain in the shortest way possible:
1) I bought a second hand Galaxy S2 GT-I9100 with a broken home button as I was confident to be able to manage everything by Odin and that was the case as I was able to upgrade from ICS to JB
2) once JB was installed I made a backup and decided to install JellyBam which came with Android 2.2 but probably because I forgot to reset to factory testing before installing the rom, I ended up in a non booting up installation where the phone just remains stuck in the loading screen of JellyBam
3) because I can not enter neither in download mode nor in recovery due to the broken home button, I was confident to manage the booting in recovery through ADB, as I did before.
But the problem is that Android 2.2 introduced the whitelist method for connected devices and therefore when I connect the device it is just seen as offline.
Because I never boot up in Jellybam I did not have the chance to accept the certificate that allow the connection with ADB
So, apart changing the piece holding the home button, what I'd like to know is if there is any hack/crack for ADB allowing it to bypass the whitelisting or any other method that allow to connect my device to the adb server
Thanks in advance
Just a suggestion..
Try with a USB Jig to Boot into Download Mode. Then flash ROM with Odin??
Related
Hi all,
I need some help please.
I tried to root my sons galaxy young S6310N using a video on you tube
However at the 4.41 point I didnt have the yes- root option.
I themn rebooted and it went back into CWM recovery. v6.0.3.2
It's been stuck in this for 2 days now, I have searched everywhere for a solution but I'm lost now. I have information overload I think.
I have tried to install drivers through Kies but it won't recognise my phone in CWM recovery or in download mode.
I have tried to install a custom rom via sd card, it seems to work but reboots into CWM again.
I fear I may have made a mess of it now by messing around with things I know nothing about. I panicked really.
The phone was running jelly bean and is only a week old.
I can get adb but not sure how to use it properly.
Could someone please help?
Thanks in advance
sorted it myself
Hi, just in case anyone was interested I managed to sort this.
I put phone into download mode (holding vol - & menu & power) then pressed up at logo screen to enter download mode.
My pc then installed drivers automatically (something I had been struggling with in CWM recovery mode)
I then installed stock rom recovery.tar.md5 file using odin and the phone rebooted as normal.
I have given up trying to root it now, I may learn properly before attempting again, or may leave it.
Search for your device first before making a thread..!!
driller66 said:
Hi, just in case anyone was interested I managed to sort this.
I put phone into download mode (holding vol - & menu & power) then pressed up at logo screen to enter download mode.
My pc then installed drivers automatically (something I had been struggling with in CWM recovery mode)
I then installed stock rom recovery.tar.md5 file using odin and the phone rebooted as normal.
I have given up trying to root it now, I may learn properly before attempting again, or may leave it.
Click to expand...
Click to collapse
Good..but always use recovery for ur phone only..or make it for ur phone..
And do any changes in stock ROM after creating a BACKUP of the same..
ROOTING is not a difficult now-a-days but overcoming from the loss of time and data after BRICKING is so painful.
If you are not friendly with the commands and codes then use a software for that or follow up the WRITTEN guide..or use FARMAROOT app.
Head to thread...Thanks Mr. Bin4ry for this awesome method:
Rooting almost every phone
Enjoy..!!
LG Escape running 4.1.2
here is the progression of events:
1. rooted device
2. root seemed successful and no malfunctions
3. backed up all apps and system data with Titanium backup
4. the lg escape has no way to unlock the bootloader, so I tried various other methods. one of which was entering recovery mode via terminal commands. this is basically a hard reset, and it wiped all my data
5. I restored all my apps and data from my external sd card with titanium
My best guess is this is where something went wrong
6. upon restoration it prompted me to reboot the device
7. reboot passes manufacturer logo, but resets when AT$T logo appears
8. as stated earlier, there is no way to enter recovery mode during boot.
9. there is a hard reset during boot, but mine will not work, as it requires touching buttons which do not seem to be active in my stage of the boot sequence
so, I understand this does NOT mean my phone is bricked, but I don't know how else to get it to boot back up, or what is even causing the boot loop, as I DO NOT HAVE ANY CUSTOM ROMS flashed. any help here is very appreciated!
EDIT: so I have attempted to use adb on my pc to reboot into recovery from there, but it occurred to me that while I was in recovery the first time, I never checked "usb debugging". as a result my adb console commands cant even see my device. any way to turn on usb debugging while locked in a boot loop?
also, I can get it to enter download mode. I was hoping I could just reflash the firmware to it without needing to enable usb debugging, but have no clue how to do that while locked out of the phone.
I realize this is a very specialized set of questions, but it is necessary to ask here as the most people will see it. im open to any ideas
whitechameleon said:
LG Escape running 4.1.2
here is the progression of events:
1. rooted device
2. root seemed successful and no malfunctions
3. backed up all apps and system data with Titanium backup
4. the lg escape has no way to unlock the bootloader, so I tried various other methods. one of which was entering recovery mode via terminal commands. this is basically a hard reset, and it wiped all my data
5. I restored all my apps and data from my external sd card with titanium
My best guess is this is where something went wrong
6. upon restoration it prompted me to reboot the device
7. reboot passes manufacturer logo, but resets when AT$T logo appears
8. as stated earlier, there is no way to enter recovery mode during boot.
9. there is a hard reset during boot, but mine will not work, as it requires touching buttons which do not seem to be active in my stage of the boot sequence
so, I understand this does NOT mean my phone is bricked, but I don't know how else to get it to boot back up, or what is even causing the boot loop, as I DO NOT HAVE ANY CUSTOM ROMS flashed. any help here is very appreciated!
EDIT: so I have attempted to use adb on my pc to reboot into recovery from there, but it occurred to me that while I was in recovery the first time, I never checked "usb debugging". as a result my adb console commands cant even see my device. any way to turn on usb debugging while locked in a boot loop?
also, I can get it to enter download mode. I was hoping I could just reflash the firmware to it without needing to enable usb debugging, but have no clue how to do that while locked out of the phone.
I realize this is a very specialized set of questions, but it is necessary to ask here as the most people will see it. im open to any ideas
Click to expand...
Click to collapse
i have now tried to flash the firmware while in download mode using a less than legitimately obtained lg R&D tool. however, i need V10F_00.kdz and i am facing a bit of censorship. any kind soul willing to host this file on dropbox or similar so i can download it?
Usually devices have a button combination to press when powering on to get into different modes. Maybe try searching for the button combination of your phone on Google? Try ' lg escape button recovery ' ?
J2270A said:
Usually devices have a button combination to press when powering on to get into different modes. Maybe try searching for the button combination of your phone on Google? Try ' lg escape button recovery ' ?
Click to expand...
Click to collapse
believe me i have. the only combo i can get to is download mode. there is a combo for a hard reset, but my touch buttons arent active during boot.
Please can you assist me.
I've read through so many threads explaining that it is easy to fix if I use ODIN. However I cannot seem to get ODIN to recognize my Galaxy S3.
I was doing a factory reset on my device, which has Cyanogenmod installed. Upon rebooting, the phone is now stuck with the Teamwin logo and it continues to loop.
In cannot seem to charge the phone because it's stuck in this mode and when I install ODIN and along with the SAMSUNG USB Drivers. I have no luck with my computer recognizing the device. I am able to get into the Download mode by holding Power, Volume Down and Home buttons - I click Volume up to continue. I then check my ODIN screen and it never appears to say ADDED or anything of that sort.
I'm scared that my phone is going to soon run out of charge and then I will not be able to even attempt to fix this. Please help me.
I've tried the above steps in both Windows 8.1 and Windows 7 and cannot get either of them to recognize my device.
N.B. I have also tried different USB ports as well as different USB cables.
Once again, I plead for any assistance.
Can u go to the custom recovery ??
If so
Do a clean wipe
Do a factory reset (do not do a clean to install new rom,just erase your data)
Wipe your cache
Wipe dalvik cache and see if u can boot it up
Goodluck
Use the latest odin version and see
And why didint you take a nandroid backup before installing custom roms
If u took it
Just restore it
U will surely boot it up
Hi there,
Thanks for your reply.
I managed to solve the issue by using a computer which already had my device USB drivers installed.
The other 2 computers I tried didn't seem to want to recognize the device due to the bootloop - but when linking up to a computer which linked to my phone prior to the ordeal, ODIN then recognized the device and I was able to load stock rom back on.
FYI, I wasn't able to access recovery.
Thank you for your quick response.
A while back I unsuccessfully tried to root my Samsung Galaxy S3.
The phone still worked OK, rebooted fine, etc., was using it for months.
Just recently though I decided to factory reset so I can give my phone to a family member, and this happened (see pics below ). Now it just hangs on T-Mobile screen and never boots at all.
http://imgur.com/gallery/0BWqcUA
Can anyone point me in the right direction to flash the default factory image back on there.
This is with T-Mobile in case that matters.
Thanks in advance.
UPDATE:
I located this thread:
http://forum.xda-developers.com/galaxy-s3
Also tried downloading this driver:
http://www.samsung.com/us/support/owners/product/SGH-T999ZWATMB
The problem right now is neither ODIN nor ADB sees my device. I have the device in "Downloading" mode (boot power down key, home ,power button).
Also tried the up-volume boot and adb side load.
Uninstall all Samsung drivers, reboot, and install Samsung Kies. This will setup the drivers you need, then you can use Odin to restore. If this doesn't work, try different cables, ports, or another computer. Check in Device Manager to see which driver is loading and manually switch if needed.
PS. You're not going to be able to communicate with the phone via adb without it booted and USB Debugging enabled or with a custom recovery that you're booted into.
Hi. I'm new here, and I really need help!
It started today when I'm tired of a disaster lagging using android 5.1.1 rom on my Galaxy tab 10.1 (GT-P7500).
So, I decided to flash a stock rom to go back to honeycomb 3.2
And basically, a volume down button on my tablet is broken. so I won't be able to reboot in recovery mode.
I tried reboot in download mode by pressing power + volume up button but it won't work either.
Then I managed to reboot in download mode and use Odin to flash a rom by using adb cmd but I didn't boot to recovery mode and wipe data/factory reset first(I don't know if this has something to do with this problem.)
And that brought me to a dead end problem.. Stuck at the logo while booting up. :crying:
I don't really know what else to do or is there some hope with this situation. I plugged a usb to my pc while in logo screen and it showed up as SAMSUNG_Android so when I check by typing adb devices in command it's there but can't get it to work since adb required debugging mode.
I think I will probably end up order a new button for replacement but I feel like I should ask a professionals first.
PCruzio said:
Hi. I'm new here, and I really need help!
It started today when I'm tired of a disaster lagging using android 5.1.1 rom on my Galaxy tab 10.1 (GT-P7500).
So, I decided to flash a stock rom to go back to honeycomb 3.2
And basically, a volume down button on my tablet is broken. so I won't be able to reboot in recovery mode.
I tried reboot in download mode by pressing power + volume up button but it won't work either.
Then I managed to reboot in download mode and use Odin to flash a rom by using adb cmd but I didn't boot to recovery mode and wipe data/factory reset first(I don't know if this has something to do with this problem.)
And that brought me to a dead end problem.. Stuck at the logo while booting up. :crying:
I don't really know what else to do or is there some hope with this situation. I plugged a usb to my pc while in logo screen and it showed up as SAMSUNG_Android so when I check by typing adb devices in command it's there but can't get it to work since adb required debugging mode.
I think I will probably end up order a new button for replacement but I feel like I should ask a professionals first.
Click to expand...
Click to collapse
Can you flash a TWRP recovery with Odin now? TWRP can support touch screen.
987987ken said:
Can you flash a TWRP recovery with Odin now? TWRP can support touch screen.
Click to expand...
Click to collapse
Hi Ken,
I have the similar problem like him, and the recovery mode was lost, i've try to flash a TWRP with Odin (twrp3000-20160207-p4.tar.md5) with AP button, it was PASS and restart, but still stuck in logo Samsung Galaxy Tab 10.1.
I don't know what to do, this is the 1st time i get this problem.
Need someone helps, thank a lot.