Related
Hello guys,
I have recently bought my first android phone, the Samsung Galaxy Nexus.
On the second day I decided to root it since I needed market enabler, as my local market (UAE) has literally no apps.
I rooted using the SDK tools, fastboot and superboot. Everything worked fine for 1 day.
However, the next day, the phone just died on me, and would not boot at all. It kept getting stuck on the "Google" image at startup. At that point, I could still go into the bootloader. I tried locking/unlocking the bootloader again, since that basically wipes all the date on the phone, but it still refused to load, it would get stuck at the startup animation.
After a few more attempts, it kept spam restarting every time I tried to switch it on.
At that point, I was downloading the default OEM ROM so I could reflash that onto the phone. However, I thought I could try using the superboot bat file again, and maybe that would fix the problem. BIG MISTAKE.
As soon as I ran that file, the phone COMPLETELY died. It will not start at ALL, it will not go into Bootloader, not go into Recovery mode, and not even go into Download (odin) mode.
The ONLY possible response you can get from it, is when you plug it into the PC. My PC seems to play that "detection" sound, same sound as when you plug in a USB, but it would just play that sound over and over again, as if im plugging/unplugging a device really quickly. It seems like the phone is continously restarting itself. When I connect the phone to the PC and that disconnect/reconnect sound comes up, I went into my device manager and I could see the following:
An item under "Other Devices" called "OMAP4440" keeps appearing and dissapearing all the time, with the little "!" mark next to it indicating that there is a driver error. The drivers for this phone are fully installed on this same PC, and it use to work fine before it went dead.
Now the problem is since I cant get into any mode whatsoever, its a bit hard to diagnose the phone. I know there is a "recovery" slot at the bottom of the phone that is accessible with a small pin, but I dont for the life of me know how that works or what it does. Does anybody know how to work that or what it actually does?
Any help would be appreciated! Thanks fellas.
wrong forum mate...if you go to this link, they might be able to help you there
http://forum.xda-developers.com/forumdisplay.php?f=1431
hi, i have same problam with my galaxy nexus. i just want to ask how to fix my phone, thanks
IamPoison said:
Hello guys,
I have recently bought my first android phone, the Samsung Galaxy Nexus.
On the second day I decided to root it since I needed market enabler, as my local market (UAE) has literally no apps.
I rooted using the SDK tools, fastboot and superboot. Everything worked fine for 1 day.
However, the next day, the phone just died on me, and would not boot at all. It kept getting stuck on the "Google" image at startup. At that point, I could still go into the bootloader. I tried locking/unlocking the bootloader again, since that basically wipes all the date on the phone, but it still refused to load, it would get stuck at the startup animation.
After a few more attempts, it kept spam restarting every time I tried to switch it on.
At that point, I was downloading the default OEM ROM so I could reflash that onto the phone. However, I thought I could try using the superboot bat file again, and maybe that would fix the problem. BIG MISTAKE.
As soon as I ran that file, the phone COMPLETELY died. It will not start at ALL, it will not go into Bootloader, not go into Recovery mode, and not even go into Download (odin) mode.
The ONLY possible response you can get from it, is when you plug it into the PC. My PC seems to play that "detection" sound, same sound as when you plug in a USB, but it would just play that sound over and over again, as if im plugging/unplugging a device really quickly. It seems like the phone is continously restarting itself. When I connect the phone to the PC and that disconnect/reconnect sound comes up, I went into my device manager and I could see the following:
An item under "Other Devices" called "OMAP4440" keeps appearing and dissapearing all the time, with the little "!" mark next to it indicating that there is a driver error. The drivers for this phone are fully installed on this same PC, and it use to work fine before it went dead.
Now the problem is since I cant get into any mode whatsoever, its a bit hard to diagnose the phone. I know there is a "recovery" slot at the bottom of the phone that is accessible with a small pin, but I dont for the life of me know how that works or what it does. Does anybody know how to work that or what it actually does?
Any help would be appreciated! Thanks fellas.
Click to expand...
Click to collapse
onlinemoon said:
hi, i have same problam with my galaxy nexus. i just want to ask how to fix my phone, thanks
Click to expand...
Click to collapse
i have same problem. can you fix it now?
---------- Post added at 08:21 PM ---------- Previous post was at 08:20 PM ----------
IamPoison said:
Hello guys,
I have recently bought my first android phone, the Samsung Galaxy Nexus.
On the second day I decided to root it since I needed market enabler, as my local market (UAE) has literally no apps.
I rooted using the SDK tools, fastboot and superboot. Everything worked fine for 1 day.
However, the next day, the phone just died on me, and would not boot at all. It kept getting stuck on the "Google" image at startup. At that point, I could still go into the bootloader. I tried locking/unlocking the bootloader again, since that basically wipes all the date on the phone, but it still refused to load, it would get stuck at the startup animation.
After a few more attempts, it kept spam restarting every time I tried to switch it on.
At that point, I was downloading the default OEM ROM so I could reflash that onto the phone. However, I thought I could try using the superboot bat file again, and maybe that would fix the problem. BIG MISTAKE.
As soon as I ran that file, the phone COMPLETELY died. It will not start at ALL, it will not go into Bootloader, not go into Recovery mode, and not even go into Download (odin) mode.
The ONLY possible response you can get from it, is when you plug it into the PC. My PC seems to play that "detection" sound, same sound as when you plug in a USB, but it would just play that sound over and over again, as if im plugging/unplugging a device really quickly. It seems like the phone is continously restarting itself. When I connect the phone to the PC and that disconnect/reconnect sound comes up, I went into my device manager and I could see the following:
An item under "Other Devices" called "OMAP4440" keeps appearing and dissapearing all the time, with the little "!" mark next to it indicating that there is a driver error. The drivers for this phone are fully installed on this same PC, and it use to work fine before it went dead.
Now the problem is since I cant get into any mode whatsoever, its a bit hard to diagnose the phone. I know there is a "recovery" slot at the bottom of the phone that is accessible with a small pin, but I dont for the life of me know how that works or what it does. Does anybody know how to work that or what it actually does?
Any help would be appreciated! Thanks fellas.
Click to expand...
Click to collapse
i have same problem. can you fix it now?
adesos said:
i have same problem. can you fix it now?
---------- Post added at 08:21 PM ---------- Previous post was at 08:20 PM ----------
i have same problem. can you fix it now?
Click to expand...
Click to collapse
Well done for not reading the thread and realising you were asking the question in the *wrong forum*!
Hey man I have the same problem and my phone is also from UAE. Did you figure it out??
Sorry posting here.
WTF are these guys for real? This thread should have been deleted the day it was started!!
This is posted in wrong section.
**Reported**
Thread Closed
This forum is for the galaxy note, please post in the correct forum
Hello, my name is TNSM and i'm new here. I signed up because i can't find anything on the internet that can help me, so i thought maybe someone here may be able to help me.
I have a Samsung Galaxy S3 Mini GT-I8190 and i'm experienced with rooting and flashing custom roms stuff. So, i was looking everywhere for a rom that included the HALO feature and after days of failed research, i found a link on Youtube to download a rom with Halo for my smartphone. I went into the recovery, backed up my current rom, wiped data and performed a factory reset, installed the rom and rebooted the phone... but after i chose the "Reboot" option, the phone never again gave a sign of life. It doesn't turn on, it doesn't show any lights whatsoever, i've tried to charge it overnight, but still nothing, considered buying a USB JIG but didn't work, my cousin says the phone seems like it doesn't even have the bootloader anymore... is my phone more than hard-bricked? Is there a way to wake my phone up again? Just for the record, it has no physical damage, it just seems like it has no software inside, that it's just hardware. By the way, when i connect it to the pc using the usb cable, the pc keeps playing the sound that something was plugged in and that something was plugged out right after, and it loops forever.
I'll give more information about the phone if needed. And i hope someone's able to help me.
- TNSM
TNSM said:
Hello, my name is TNSM and i'm new here. I signed up because i can't find anything on the internet that can help me, so i thought maybe someone here may be able to help me.
I have a Samsung Galaxy S3 Mini GT-I8190 and i'm experienced with rooting and flashing custom roms stuff. So, i was looking everywhere for a rom that included the HALO feature and after days of failed research, i found a link on Youtube to download a rom with Halo for my smartphone. I went into the recovery, backed up my current rom, wiped data and performed a factory reset, installed the rom and rebooted the phone... but after i chose the "Reboot" option, the phone never again gave a sign of life. It doesn't turn on, it doesn't show any lights whatsoever, i've tried to charge it overnight, but still nothing, considered buying a USB JIG but didn't work, my cousin says the phone seems like it doesn't even have the bootloader anymore... is my phone more than hard-bricked? Is there a way to wake my phone up again? Just for the record, it has no physical damage, it just seems like it has no software inside, that it's just hardware. By the way, when i connect it to the pc using the usb cable, the pc keeps playing the sound that something was plugged in and that something was plugged out right after, and it loops forever.
I'll give more information about the phone if needed. And i hope someone's able to help me.
- TNSM
Click to expand...
Click to collapse
You may try to pull off the battery for few mins, then with someone's help hold the 3 buttons for download mode and then plug in the battery...
If you can't turn it in download mode there's no way to fix it, except jtag maybe.
Greetings, for the first time ever in my life I never experianced getting a Bricked phone, it did not happen while flashing or doing something wrong. I just did a normal flash, it was sucessfull was running the custom Rom there since months. I just woke up grab my phone while it was charging (It was at 100%) used the Instagram app and it randomly froze, I was just thinking it's normal, every Android phone freezes sometimes somewhere , plugged out the battery plug in and tried to boot it up, but nothing no vibration, no lights nothing. After some time, in the holidays I decided to plug in the phone into my PC, I heard noises that my win10 laptop tried to reconize something, so I had still hopes for it that it still works. I heard about that a JIG will may work for it, so I bought one that was "inteded" to be for my S3 Mini GT-I8190 waited for it to arrive and plug it in finally, well you could guess it, nothing happend. I knew a friend who had the same phone and I asked him if I may plugin the JIG inside, all it done was just vibrate and nothing else. On other phones it just works flawless. I tried to look up for a debrick image for the phone but it seems there is nothing like it, like it never existed, only the S3 somewhat got it. The only thing now I could help people is, is how to get your system back while TWRP/CWM/Recovery is still there or get the recovery back while the system is still there. My only option now is create some how a own JIG, buy a JTAG and get a debrick.img but the third option appears nowhere here nor in a search engine (Or maybe only mine).
If you have questions, please aks and don't be shy. The current state of the battery right now is 2.8V (Must be at ~60%)
Hello everyone,
Having major issues with my Idol4S. It is the unlocked version (Cricket). It was working just great until a few days ago when I plugged it into the car charger. Phone instantly shut off, and got stuck with a blinking (rapid) LED light. This happens if plugged into my PC, or my Alcatel charger (both the wall and car).
The phone has suffered no damage (had a cover, but it was never dropped or exposed to external weather damage, nor water - I took great care of it), and was working quite well. I'm unable to boot it into any sort of recovery mode (as the screen is black, so I wouldn't be able to see anything anyways). The only indication of life is the flashing LED when plugged in ..(charging loop, maybe?)
I am using my idol4S Win10 (TMO/unlocked) phone in the meantime, but the base model was working just fine before this happened. I was also mindful of checking voltage/Amps when using chargers, so I would not have exposed it to any incorrect input/output. QuickCharge worked great too (sorely missed on Win10 model).
The phone was never rooted so it has the stock ROM, and whatever the last update Alcatel had pushed out for it. I did have developer mode and USB debugging on for MSVC/NSDK.
Is there anything I can do? After awhile being plugged in, the LED shuts off. I kind of need it as I was porting my game engine to it (using the SDK), plus it was my primary. I love the Win10 version too, but the Android idol4S was my primary phone. Kind of disappointed in Alcatel - I read it doesn't have an external battery otherwise I would attempt to transplant the battery (if that is even the issue). . .
Any tips, advice, or suggestions would be greatly appreciated! <3
what you describe is what the phone does when it's plugged into the PC in download mode. Since you have the Cricket version which is also what I have, it is very easy to start from scratch and reflash everything. I have released a newer version TWRP and also have the ~CricketRom~ available if you're interested.
PizzaG said:
what you describe is what the phone does when it's plugged into the PC in download mode. Since you have the Cricket version which is also what I have, it is very easy to start from scratch and reflash everything. I have released a newer version TWRP and also have the ~CricketRom~ available if you're interested.
Click to expand...
Click to collapse
Okay, but would it work even though the phone gives no indication of being plugged in to the computer, or the chargers for it? I plugged it into the PC just now, brief flash of light and then nothing. .
Should mention again that the screen does not turn on, ever since that day, the screen has not came back on -- so I really can't do anything, even accessing 'download mode' does not show anything on-screen, nor does Windows 10 alert me of the USB device being connected.
I wouldn't mind starting from scratch at this point. I'm definitely interested in getting up and running again! It's not like I can do anything else at this point except spend money and get it repaired by TCL.
Would it be rude of me to ask for links to the TWRP/CricketROM from you? Maybe a quick-start guide, I pick up on things easy, but I've never properly flashed with TWRP =)
Also @PizzaG, THANK YOU for your help!! Definitely appreciated <3
Oh! @PizzaG, I also have an older Onetouch Idol 3 that has the _exact_ same symptoms, I wonder if that too could be recovered? ... ^__^
well I guess the first thing to do would be plug it into the PC. Hold volume+ and volume- then hold power until you feel the buzz and let go of power. Hopefully you get the red Download mode screen? I didn't realize it had no life at all, I thought it was just messed up. It's sounding like more may be wrong then just a simple reflash.
New TWRP and ~CriketRom~ Beta5: https://forum.xda-developers.com/idol-4s/development/rom-twrp-recovery-t3792659
Hi,
A few days ago, I replaced a USB socket on friend's old Samsung Note 1 (GT-N7000). Soldering may not be very professional, but it does the job - the phone is charging and it can connect to the computer.
Today (3 days after replacing the USB) he came back to me with another problem -
after turning on the phone, only the white brand name and model appear at the start and then nothing, a black screen. I think it's turning off. He says he had some problems with the battery in the meantime and the screen was flickering strangely.
He had a custom ROM loaded for a long time that worked normally and worked well on this phone.
Today, despite not starting the system, I was able to enter TWRP recovery and DL mode. However, if I wanted to do anything in recovery (backup, factory reset, etc), the screen turned off. After a few attempts, it stopped going into recovery.
I have restored the original software using Odin and N7000XXLSZ_OXELS7_4.1.2_Repair_Firmware
- still after the white inscriptions at the start, the screen goes black and nothing
- trying to enter recovery, overturned android appears for a moment and the screen goes black
- DL mode works
Maybe someone knows what could have happened and most importantly how to get this phone work? Preferably on some "custom ROM" to have at least Android 7.
I was thinking, I was looking, I was tearing my hair out of my head. I searched half the internet and suddenly stumbled upon this - https://forum.xda-developers.com/t/...bricked-only-download-mode-available.3096409/
The phone is the same, the problem is the same - the battery is to blame. I immediately called the owner to give all the batteries he has.
OH, OF COURSE! The one I got along with the phone and its problems was the only one that caused all the restarts and errors. After inserting a different battery, the problems were resolved.
All that's left is to clean up Android and the case is closed.
By the way - I have collected in one place the files and information (Polish language only) on how to install NightOwl LineageOS 14.1 Android 7.1.
2 on this phone. If anyone needs this information, please visit here - https://drive.google.com/drive/folders/1libYpWC4qJbjGJRE1Szf8L3eTdoHPTpE?usp=sharing