Database Info

[HOWTO][TAR][BLAZE 4G] THE ODIN THREAD :: Return to stock, fix soft brick :: 4/9/12

k0nane presents...
Odin: Return to Stock, fix soft brick
Sponsored by k0nane.info. Have you tipped your devs today?
DO NOT CHECK REPARTITION! YOU HAVE BEEN WARNED!​
Why the big red warning? Far too many people have broken their devices by not following these instructions! Search the forums, or drop by IRC - you'll see plenty of examples.
These instructions should fix your soft-bricked or broken phone as long as you can get it into download mode. Make sure you have drivers already installed on your Windows computer before starting. Please read them all the way through and then begin.
Code:
#include <external/cyanogenmod/std_disclaimer.h>
/*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/
Instructions​
Download Odin 1.85 - see section below.
Download the stock TAR for your device - see section below.
Extract the contents of odin-185.zip and the 7zip archive.
Run Odin 1.85.exe, and prepare Odin:
Check "auto-reboot", and uncheck all other options.
Click PDA and select the TAR you downloaded. Click PIT and select the PIT your downloaded.
Put your device into Download Mode:
Connect the USB cable to your PC, but NOT your device.
Remove the battery.
Reinsert the battery.
Hold down Volume Up + Volume Down + Power.
You should now be at Download Mode. Make sure Odin looks similar to the following:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Click Start in Odin.
Wait! When complete, Odin should appear like the following:
That's it! Your device will autoreboot, and your phone should be working properly again. Be sure to wipe data in recovery after completing this process if you have further issues.
Downloads​
Download Odin 1.85
Download PIT
Download Stock TAR
Download Stock TAR (Mirror)
​
Credits:​
DrTaru: stock device, remote access, lots of testing, screenshots, patience
Shabbypenguin: Shabbypenguin (do I need to say more?)

P-O-S-T :: R-E-S-E-R-V-E-D
Original artwork by Pendulum via Gasolin3.
...for future use.
Follow me on Twitter @k0nane and @publik0!​

boom! once again

No 4G or Wifi Afterwards...
I just did the Factory Recovery on my phone 'cause I messed something up and now I can't get the 4G or Wifi to work... I'm connected to the Wifi Network and 4G icon is on my phone but there's no internet connection...any help please?

Hi
I need 2 folder app and framework to build some app then send to my friend because my friend don't know how to copy it from system. Please use root explore to copy it then upload for me .
Thanks

Desertstorm00 said:
I just did the Factory Recovery on my phone 'cause I messed something up and now I can't get the 4G or Wifi to work... I'm connected to the Wifi Network and 4G icon is on my phone but there's no internet connection...any help please?
Click to expand...
Click to collapse
Wipe cache and data in factory recovery.
doantri said:
Hi
I need 2 folder app and framework to build some app then send to my friend because my friend don't know how to copy it from system. Please use root explore to copy it then upload for me .
Thanks
Click to expand...
Click to collapse
Extract them from the system image yourself.

stuck at param.lfs
anyone else stuck at param.lfs when trying to restore to stock??

mayesmwhite said:
anyone else stuck at param.lfs when trying to restore to stock??
Click to expand...
Click to collapse
Use a non-stock USB cable, and switch ports on your PC. If you continue to have issues, redownload the TAR or use another computer.

Ok, yes this is my first post and yes, the "don't check Re-Partition!" is in red everywhere... and I am a relatively experienced at rooting devices (this is the second Blaze I was doing, first one rooted with zero problems... That being said: What are the recovery options if one does open a new tar using oden and forgets to un-check re-partition (like I did earlier today)?
I have since flashed both the recovery rom and CWM, however the phone still prompts me for a password and after I input the correct password it goes into a boot loop.
Steps taken:
1. Flashed the k0nane root kernel and forgot to uncheck re-partition. ( Yes I know... laugh it up... )
2. Dropped the F-bomb in front of the kids about 1 second after pressing "Start" once I realized what I had done...
3. Followed the "THE ODIN THREAD: Return to stock instructions, fix soft brick"
4. At the hard reset part where you go into recovery mode I received the green/red dot screen response
5. Successfully flashed the CWM, therefore fixing the green/red dot recovery mode issue
6. Performed a hard reset using CWM, however...
After all this I still am getting the prompt for password (I would have expected a factory reset would make this go away) and subsequent boot loop upon entering the correct password.
Would saving a CWM recovery rom to my sd card of my "good' Blaze and transferring/flashing it to my broken blaze fix the issue?
Edit:
- I tried it (flashing my other blaze's recovery rom) and no it does not fix the password prompt to boot loop issue... (It didn't make anything worse either... how is it I can flash a rom and still have a password prompt (my working droid is not password protected...)?

chlor3 said:
Ok, yes this is my first post and yes, the "don't check Re-Partition!" is in red everywhere... and I am a relatively experienced at rooting devices (this is the second Blaze I was doing, first one rooted with zero problems... That being said: What are the recovery options if one does open a new tar using oden and forgets to un-check re-partition (like I did earlier today)?
I have since flashed both the recovery rom and CWM, however the phone still prompts me for a password and after I input the correct password it goes into a boot loop.
Steps taken:
1. Flashed the k0nane root kernel and forgot to uncheck re-partition. ( Yes I know... laugh it up... )
2. Dropped the F-bomb in front of the kids about 1 second after pressing "Start" once I realized what I had done...
3. Followed the "THE ODIN THREAD: Return to stock instructions, fix soft brick"
4. At the hard reset part where you go into recovery mode I received the green/red dot screen response
5. Successfully flashed the CWM, therefore fixing the green/red dot recovery mode issue
6. Performed a hard reset using CWM, however...
After all this I still am getting the prompt for password (I would have expected a factory reset would make this go away) and subsequent boot loop upon entering the correct password.
Would saving a CWM recovery rom to my sd card of my "good' Blaze and transferring/flashing it to my broken blaze fix the issue?
Edit:
- I tried it (flashing my other blaze's recovery rom) and no it does not fix the password prompt to boot loop issue... (It didn't make anything worse either... how is it I can flash a rom and still have a password prompt (my working droid is not password protected...)?
Click to expand...
Click to collapse
This thread might help you out. Brick 2 Fix

I was hoping i had stumbled upon a new way to fix my "soft brick" since not everyone has access to two phones..
-chlor3

chlor3 said:
I was hoping i had stumbled upon a new way to fix my "soft brick" since not everyone has access to two phones. I am still considering installing dropbear to the good phone using CWM and flashing to the broken phone in an attempt to get shell.
-chlor3
Click to expand...
Click to collapse
Do you have a working Blaze? If so, I only need two partitions... Anyone? Our only Blaze owner on IRC returned his.

I'm thinking of returning mine too. Its really a let down coming from my vibrant

k0nane said:
Do you have a working Blaze? If so, I only need two partitions... Anyone? Our only Blaze owner on IRC returned his.
Click to expand...
Click to collapse
I can attempt to help you get what you need. I'm fairly new to this stuff but would be happy to help if I can.

So I tried out the CM7 alpha and it froze at the loading screen. I'm doing it wrong and can't figure out how to get a logcat.
I'm trying to get back to stock and it seems to work other that the 'market' app is greyed out and it says that it's not installed on my phone. I've tried re-rooting and cwm and still the market app is greyed and doesn't show up anywhere other than the app drawer.
When I flash back to stock via Odin, I'm already past the gmail login part.
Even after adding cwm, I can't figure out how to get to recovery via hardware buttons to wipe or whatever.
Anybody have any ideas?
Nevermind maybe. I added a Google Play apk and now things are syncing up. I'm not sure what happened though.

So it looks like I may be the only one messing this up...
I flashed the cm7 alpha a bit ago. It's making progress.
Now that I'm trying to get back to stock I'm getting a loop between the Samsung logo and the Android blasting off.
I flashed the cwm but can't for the life of me figure out how to boot into recovery using hardware keys.
Anybody have any ideas? I'm lost w/ a useless phone ha.

Try this
1. Turn off phone
2. Remove battery
3. Plug USB from computer to phone
4. Insert battery
5. Hold volume up + volume down
6. While still held push and hold the power button keeping all three pressed
7. Wait for Samsung logo to appear
8. When screen goes black wait half a second and release all buttons
9. In a second or 2 should be in recovery
If that doesn't work please leave outcome, I have another method if that fails
Sent from my SGH-T769 using xda premium

xArcane1x said:
Try this
1. Turn off phone
2. Remove battery
3. Plug USB from computer to phone
4. Insert battery
5. Hold volume up + volume down
6. While still held push and hold the power button keeping all three pressed
7. Wait for Samsung logo to appear
8. When screen goes black wait half a second and release all buttons
9. In a second or 2 should be in recovery
If that doesn't work please leave outcome, I have another method if that fails
Sent from my SGH-T769 using xda premium
Click to expand...
Click to collapse
im boot looping like in the above thread between the samsung logo and the android screen - ive tried 2 different cables/and downloads
im coming from root and cwm - but needed to go back to stock...
...im not a noob but im stuck and kinda shrugging - help? lol
---------- Post added at 02:57 PM ---------- Previous post was at 02:56 PM ----------
of course im using odin - all succeeding - not failing as odin reports
getting to root and cwm were simple seems this should be but just looping
---------- Post added at 03:52 PM ---------- Previous post was at 02:57 PM ----------
well - nevermind my post although its apparently happening to some devices.
i found a nandroid backup on my SDCARD thankfully i hadnt deleted (as im going back to my g2x lol) - and after i ran it everythings fine; did a factory reset on it and it appears to be good; not sure if it's kept root and wont know until i install tb again on it - but thanks for now guys!

The stock tar file isn't being recognized by Odin b/c it's not a "tar" file. Can someone please advise how I can get Odin to recognize it? I really need to get back to stock.
Thanks

Did you unzip and extract the contents of the zip? Hopefully that will help you
Sent from my SGH-T769 using xda app-developers app

[Q] i9023 bricked. Secure: on (S-ON), radio XXXXX

The last week I have been struggling to unbrick my i9023 Nexus S. Without any luck... Let's start at the beginning, how I bricked my Nexus S. If you don't think this is relevant you can skip it.
Stay with me because it's going to be a long thread...
How I bricked my Nexus S
I was running a CM9 Nightly (from around 10 March) until a week ago, together with the matrix CFS 18.0 kernel. I had a problem with rebooting. Every time I rebooted, it would take 2 or 3 tries before it actually started. First it would just reboot again, or even freeze. So after almost a month I was kinda tired of that problem, so I decided to flash a new CM9 Nightly, the one from 7 April. I flashed the Nightly like I always do, wipe cache/dalvik, and I also flashed the new matrix CFS 18.5 kernel, + the latest gapps and the reloadedICS mod. It was working fine. I rebooted a couple of times more into recovery because I wasn't happy with the reloadedICS mod. Everything was still working fine.
The battery was draining very quickly though. I was watching TV for an hour and when I decided to go to bed the battery was already dead. So I put it in the charger because I wanted to check my facebook before I went to bed. It booted fine, but when I started loading facebook in the browser, my phone freezed. I wasn't really alarmed because, well, let's face it, that's the risk with nightlies. So I pulled out the battery, something I have done a lot of times since I started rooting/flashing. After that: dead. No reaction. No charging icon when it was plugged in the charger. No vibration when I pressed the power button, nothing. A brick...
What I've tried
Although it is uncommon, I wasn't the first to brick a Nexus S. Apparently it had something to do with updating to ICS 4.0.4, on which the april 7 nightly was based on I guess.
Luckily there was AdamOutler's Unbrickable Resurrector. After some setbacks I managed to get the Resurrector working. And against all odds I "unbricked" my Nexus S on the first try! Well, I got it into download mode (home and search button). The only problem was that I still didn't have a screen. The home and search button were lit up, but the screen was still black... And according to most people, it isn't supposed to be black...
Ignoring that fact, I downloaded fastboot and tried to flash bootloader.img, as instructed. It didn't work because my bootloader wasn't unlocked, something that struck me as very weird because it definitely was unlocked before the brick. So I tried to unlock the bootloader. But for that, you need a screen... With a lot of luck I managed to unlock the bootloader. Don't ask me how, but after a few tries I succeeded.
I was making progress. And I was happy about that . So I tried to flash the bootloader again. But it still didn't work. "Write failed". After some internet research I found out wat the problem was. It had something to do with the bootloader and radio being a different version. I used the command "fastboot getvar all" and it told me the following:
- Bootloader version: i9020XXKA3
- Radio version: i9020XXXXX
Apparently the radio version isn't supposed to be XXXXX, and that's why I couldn't flash bootloader.img or radio.img. Also, this is the reason that I couldn't boot my device in the first place.
Obviously I wasn't the only person with this problem. I found a guy that had the same problem as me. He used the command "fastboot boot recovery3101.img", using an older version of CWM recovery. If you used that command, your phone would always boot into recovery, so that you can flash a new OTA.
So I downloaded that older version of CWM, and I tried the same command. And it worked! The home and search button were off and the menu and back button were on! But, still no screen. And the guy that used the same command did have a screen...
I had no clue on what to do next, so I pressed the power button, in the hope that I could boot my device directly into recovery after that. I pressed the power button, the backlight of the soft keys went out... and that was my poor Nexus S' last breath of life...
I tried the resurrector tool after that... "failed to write"...
So, am I really f***ed?
I just can't comprehend that my Nexus S could be dead forever... The hardware is fine, it's just the software that keeps it from booting up! The idea of that is crazy... Certainly with a Nexus S for christ's sake!
So, what am I to do? I kinda gave up hope...
UPDATE: SITUATION ATM
1) With AdamOutler's Unbrickable Resurrector I can get into download mode. Sometimes it doesn't work but when I pull out the battery it works again.
Now I can flash every partition with fastboot, except for;
- the bootloader (which is XXKA3)
- the radio (which is XXXXX)
The probable cause for this is the fact that "secure: on", according to "fastboot getvar all". This is very weird because no one on the internet has a Nexus S with "secure: on". It is some security for i.a. HTC devices.
When flashing the bootloader or radio, I get the following error:
sending 'bootloader/radio' <file size>...
OKAY [time]
writing 'bootloader/radio'...
FAILED <remote: Write Fail>
finished. total time: time
Click to expand...
Click to collapse
Using "fastboot -w update image-******.zip":
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
After that the flash goes fine. When it reboots, my phone is dead again. This is because the radio didn't change with this zip. If there would be a radio in that zip, it would not have worked anyway.
The radio is booted first in android, and because of this I can't do anything (the XXXXX version is wrong). This is probably also why the recovery doesn't work properly (see below). And the "secure: on" prevents me from flashing another radio.
2) With "fastboot boot recovery.img" I can get in the recovery mode. ADB "shell" works, and so does "push" and "pull". The screen is black, though. Even with a very strong flashlight I still can't see anything. I can only see 2 or 3 lines (it is different with each recovery). When I press the volume buttons to scroll, I see no changes at all on my screen.
What I have tried in recovery:
- Installing an OTA zip. I can ADB "push" an OTA zip. I have checked that with ADB "shell". Since I can't see anything I have to guide myself using pictures from CWM menus. But nothing happens. There is no sign that the install worked. The only sign that I'm actually in recovery is that the menu and back softkey are lit up, and that when I press the power button without pressing the volume buttons first, my phone powers off (this is because "reboot system now" is on top of the list in recovery, I guess).
- ADB pushing anything on /sdcard. When I turn off my phone after that and resurrect it again, the file is gone. This could be because my memory is dead. But isn't this because the resurrector removes it? Anyway, when I push a file with ADB, it definitely is on my sdcard. Only after rebooting and resurrecting it isn't...
NOTE: Rebooting/booting in whatever mode doesn't work. The only two things I can do are listed above. The moment I plug out my device, I have to use the resurrector again. Because of this there it makes no sense to flash a recovery, since I can't boot anyway. The only way I can get into recovery is by using "fastboot boot recovery.img".
NOTE 2: Recovery.log shows some errors. I will post the whole log soon...
Possible solutions?
A) How can I flash a different radio, despite of "secure: on"?
B) Can we change "secure: on" to "secure: off"? For HTC users this is as normal as "fastboot oem unlock", but there is no one on the internet that has a Nexus S with "secure: on".

I've never really saw a Nexus S totally bricked by software. It's often a combo of small user errors and small software bugs.
There is a bug with the SLCD version of the Nexus S where the backlight doesn't come on and thus it looks like it doesn't work but the softkeys light up. However, if you take a flashlight to the screen and look at an angle, you will see what's being displayed.
Also, you do not need to use an old version of CWM specifically.
Are you able to hold vol + and power to get into bootloader? If not, pull the battery out for at least 10 minutes, then put it back in and try again.

polobunny said:
I've never really saw a Nexus S totally bricked by software. It's often a combo of small user errors and small software bugs.
There is a bug with the SLCD version of the Nexus S where the backlight doesn't come on and thus it looks like it doesn't work but the softkeys light up. However, if you take a flashlight to the screen and look at an angle, you will see what's being displayed.
Also, you do not need to use an old version of CWM specifically.
Are you able to hold vol + and power to get into bootloader? If not, pull the battery out for at least 10 minutes, then put it back in and try again.
Click to expand...
Click to collapse
I know about that bug where the backlight doesn't work, and that's how I managed to unlock the bootloader eventually.
My phone is as dead as a brick. The resurrector doesn't work anymore, so I can't get into bootloader. I can't get into download mode, I can't get into anything.
I know you don't really need to use an old version of CWM, but it got me into recovery. Unfortunately, after I shut down my device, I can't do anything anymore... I guess the resurrector doesn't work because recovery is now on the boot partition?

Androyed said:
I know about that bug where the backlight doesn't work, and that's how I managed to unlock the bootloader eventually.
My phone is as dead as a brick. The resurrector doesn't work anymore, so I can't get into bootloader. I can't get into download mode, I can't get into anything.
I know you don't really need to use an old version of CWM, but it got me into recovery. Unfortunately, after I shut down my device, I can't do anything anymore... I guess the resurrector doesn't work because recovery is now on the boot partition?
Click to expand...
Click to collapse
If the phone doesn't even power on AT ALL (not even a split second) when you press the power button i'd look into a hardware problem more than a software problem. You can get into the bootload using VOL+ and power usually, not only using the ressurector.

polobunny said:
If the phone doesn't even power on AT ALL (not even a split second) when you press the power button i'd look into a hardware problem more than a software problem. You can get into the bootload using VOL+ and power usually, not only using the ressurector.
Click to expand...
Click to collapse
Well, than that hardware problem occured when I pulled out the battery after my screen freezed...
But if it really is a hardware problem, isn't it strange that I was able to get it into download mode, and that I got it to communicate with my computer using fastboot? I even got it into recovery mode for a brief moment!

Androyed said:
Well, than that hardware problem occured when I pulled out the battery after my screen freezed...
But if it really is a hardware problem, isn't it strange that I was able to get it into download mode, and that I got it to communicate with my computer using fastboot? I even got it into recovery mode for a brief moment!
Click to expand...
Click to collapse
It is very weird indeed. If I had to pick something hardware related, I'd say your battery died. Just a guts feeling, and it goes with the quick discharge scenario...

polobunny said:
It is very weird indeed. If I had to pick something hardware related, I'd say your battery died. Just a guts feeling, and it goes with the quick discharge scenario...
Click to expand...
Click to collapse
I have used other batteries (luckily I have friends with a Nexus S), but that doesn't change anything.
The big question is, how can I get into download mode again? The resurrector worked at first, but when I flashed CWM to the boot partition and rebooted after that, I can't get any signs of life out of my Nexus S. Resurrector doesn't work anymore, nothing...
The weird thing is, the moment I used the "fastboot boot recovery.img" command, windows stopped recognising the device. But according to the soft keys, it did go from download mode into recovery mode. I still didn't see anything, but I guess that's because the SLCD bug.
I guess I should not have had rebooted when I was finally in recovery...

Hmmm... someone might have an idea. I still find it extremely strange it doesn't power on at all. Were you aware of any power button problem with your Nexus? Had to double click the power button to wake it?

polobunny said:
Hmmm... someone might have an idea. I still find it extremely strange it doesn't power on at all. Were you aware of any power button problem with your Nexus? Had to double click the power button to wake it?
Click to expand...
Click to collapse
Nope, no problem at all.
The only way I could get some life out of it, was by using the resurrector tool. But now even that isn't possible anymore...
Is it actually possible to really perma-brick a Nexus S? Or are people just saying that because they lack the knowledge to unbrick it. I'm pretty sure it can't be a hardware problem. It is the software that is preventing it to boot up. That's what a brick is, right?

WOW, GOOD NEWS!
After a few (totally random) tries, I managed to resurrect my phone again! I am now in the download mode. From here I can use fastboot boot recovery.img. I still don't have a screen though...
When I get into recovery (without screen), what should I do then? Because previous time, windows stopped recognizing my phone... Should I push an OTA to my Nexus S BEFORE I use fastboot boot recovery.img? And if so, how? And if I do so, how on earth am I going to manage to install that zip without a screen? There are a lot of files on my sd card... An option would be to wipe them all, if that's possible. Another option would be to give it something starting with a 1 or an A so that it comes up on top of the list.

The problem is that I can't flash anything because of that i9020XXXXX radio version.... Is there any way I can flash another radio? Just flashing with fastboot doesn't work because of that XXXXX version...

Got it into recovery again! Windows recognized USB mass storage for a second, but not anymore.
Using a flashlight I can see that there is SOMETHING on the screen, but when I press the volume buttons to scroll nothing changes...

Another breakthrough! I installed ADB drivers, and now I got ADB working!
Can you control CWM recovery from the computer, using ADB? Because now all I have to do is flash an OTA, but I can't see anything, not even with a flashlight...

I'm not real good at the technical stuff, but it seems like you should be able to put one of the ota's on your computer and when you connect the phone, it should take you through a flash sequence. Hopefully someone above my pay grade will jump in here and help.
Hang in there, we're all pulling for you.

wmdunn said:
I'm not real good at the technical stuff, but it seems like you should be able to put one of the ota's on your computer and when you connect the phone, it should take you through a flash sequence. Hopefully someone above my pay grade will jump in here and help.
Hang in there, we're all pulling for you.
Click to expand...
Click to collapse
I'm not really good at the technical stuff either. I'm like this dog:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
But I can learn quickly. I know how to push a file to the SD Card using ADB. I also now how to wipe all user data using fastboot. Combining that, I have a SD Card with only 1 file: the OTA I want to flash. That should make thinks a lot easier since I can't see a damn on my screen.
My problem wouldn't even that bad, if it weren't three problems combined. Normally when people unbrick their phone with the resurrector, they can flash a bootloader.img. But I can't, because of that i9020XXXXX baseband version. I tried to flash another radio.img but that doesn't work either. To top this off, my screen doesn't work. Even with a flashlight I only see that there's SOMETHING on the screen, but I don't see any changes when I press the volume buttons for example.
The problem with not seeing anything is that I don't know if what I did, worked. I can't confirm anything. Maybe when I flash the OTA it says: update failed. But I can't see that so how would I know?
That's why I was hoping for a way to not only push files to the SD Card using ADB and wipe all user data using fastboot, but also for a way to install zip from SD Card using ADB/fastboot.

Could this be a corrupt radio? There was a thread about the 4g radio that delves a little into what the radio actually does. I'll find it when I'm back home. Try flashing a radio through cwm if you can manage.

Harbb said:
Could this be a corrupt radio? There was a thread about the 4g radio that delves a little into what the radio actually does. I'll find it when I'm back home. Try flashing a radio through cwm if you can manage.
Click to expand...
Click to collapse
You think that would work? Because I can't flash via fastboot...
Anyway, it is worth a shot. I've tried flashing several OTAs through several recoveries without much luck, but at least now I have the knowledge to go back to where I was (download mode/recovery).
I don't know anything about radios, but the XXXXX baseband version isn't good, at least that's what people say. It prevents you from flashing a bootloader.img, and also from flashing another radio.img. And maybe it was the reason that my Nexus S bricked in the first place.
By the way, thank you all for your help!

[Q] i9023 very freaking bricked, lost all hope...
Pls help i am also facing same problem i have given NS to service center they said they will be changing its mother board is there any thing can b done.

Androyed said:
You think that would work? Because I can't flash via fastboot...
Anyway, it is worth a shot. I've tried flashing several OTAs through several recoveries without much luck, but at least now I have the knowledge to go back to where I was (download mode/recovery).
I don't know anything about radios, but the XXXXX baseband version isn't good, at least that's what people say. It prevents you from flashing a bootloader.img, and also from flashing another radio.img. And maybe it was the reason that my Nexus S bricked in the first place.
By the way, thank you all for your help!
Click to expand...
Click to collapse
Try installing factory images from fastboot, You dont need the screen for that just get it to download mode.
http://forum.xda-developers.com/showthread.php?t=1572307

in cmd it says waiting for device and nothing happened its blank

[Q] Infuse stuck on boot screen

Background: Trying to update my stock infuse to Jelly Bean. Looked into what was needed via hours of research. Used SuperOneClick to root phone (Success), installed ESFile Manager to help install mod 3e recovery (success), used ROM Manager to flash CWM (Success).
Upon testing the CWM by booting into recovery, this boot screen issue started.
- I've tried hard resetting, (no success, won't go past the Samsung screen).
- I'm currently using Odin to restore stock firmware, but it's been about 25 minutes so it's probably not working.
- I can only get to Samsung screen and download mode, that's it!
I need my phone and I need to get some sleep. what am I missing? Much appreciated
thanks

here's a shot of Odin right now. It's stuck on "setup connection"
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

Here is what I used to Un-boot loop my phone worked like a charm, the instructions we're a little un-clear but if you read through it, a few times, it's really rather easy. You need to download Java (Jave Runtime Enviorment, also known as JRE I used OpenJDK Java 7) on your computer, download the Heimdall one click packages, put your phone in download mode:
-Pull the battery out and make sure the phone is NOT connected by a usb cable.
-Put the battery back in!
-Hold vol up+Vol down. DO NOT PRESS POWER.
-Plug in the USB cable.
Open the downloaded heimdall one click with java (in Ubuntu Context menu Windowz is likely the same) and it will return your phone back to stock which is where you want to start for I believe almost all the JB ROMs. If you search around Quickster made some other One click packages to get you rooted and CWM installed as well as Kernels and other stuff. These things work great and to me are a million times easier than every other method.Good luck and if there's any other help I can provide I'll do my best

dginsd said:
Here is what I used to Un-boot loop my phone worked like a charm, the instructions we're a little un-clear but if you read through it, a few times, it's really rather easy. You need to download Java (Jave Runtime Enviorment, also known as JRE I used OpenJDK Java 7) on your computer, download the Heimdall one click packages, put your phone in download mode:
-Pull the battery out and make sure the phone is NOT connected by a usb cable.
-Put the battery back in!
-Hold vol up+Vol down. DO NOT PRESS POWER.
-Plug in the USB cable.
Open the downloaded heimdall one click with java (in Ubuntu Context menu Windowz is likely the same) and it will return your phone back to stock which is where you want to start for I believe almost all the JB ROMs. If you search around Quickster made some other One click packages to get you rooted and CWM installed as well as Kernels and other stuff. These things work great and to me are a million times easier than every other method.Good luck and if there's any other help I can provide I'll do my best
Click to expand...
Click to collapse
I can't get into download mode anymore. I used to be able to prior to trying Kies. Now I can only get to an icon with a white phone with two dots and a computer icon with a yellow hazard triangle in between them (emergency mode logo). I can't get to any download mode no matter what, at least that's not displayed. I think Odin recognized it last night with this new emergency mode, but everything i tried failed

mendozer said:
I can't get into download mode anymore. I used to be able to prior to trying Kies. Now I can only get to an icon with a white phone with two dots and a computer icon with a yellow hazard triangle in between them (emergency mode logo). I can't get to any download mode no matter what, at least that's not displayed. I think Odin recognized it last night with this new emergency mode, but everything i tried failed
Click to expand...
Click to collapse
Perhaps try to use the Heimdall "back to stock" while in that Emergency mode. The Heimdall program will also tell you if it recognizes a phone attached in download mode, and if it will recognize the phone and flash you back to stock, you can also have it put you back on stock bootloaders which sounds like your problem (though flashing bootloaders is dangerious but in your case may be nessessary). Maybe PM Quickster see if he recommends trying to flash with Heimdall on that mode you've entered, I might also try using an alternate USB cable if you haven't already.

mendozer said:
I can't get into download mode anymore. I used to be able to prior to trying Kies. Now I can only get to an icon with a white phone with two dots and a computer icon with a yellow hazard triangle in between them (emergency mode logo). I can't get to any download mode no matter what, at least that's not displayed. I think Odin recognized it last night with this new emergency mode, but everything i tried failed
Click to expand...
Click to collapse
The computer icon with a yellow hazard triangle in between them is a form of download. Use Heimdall after making sure you have the correct JRE and drivers.
Sent from my SGH-I997 using xda premium

psal217050 said:
The computer icon with a yellow hazard triangle in between them is a form of download. Use Heimdall after making sure you have the correct JRE and drivers.
Sent from my SGH-I997 using xda premium
Click to expand...
Click to collapse
I have the stock firmware from Samsung. that includes the drivers I presume? the md5 file

holy smokes I'm so relieved it worked!
So, I used Heimdall's froyo Uck3 firmware or whatever since that's what was in the package. I still want Jelly bean. I have the JB folder with what I suppose I need (think it was from android geeks). However, since this was painless, is there a Heimdall one click for JB?

mendozer said:
holy smokes I'm so relieved it worked!
So, I used Heimdall's froyo Uck3 firmware or whatever since that's what was in the package. I still want Jelly bean. I have the JB folder with what I suppose I need (think it was from android geeks). However, since this was painless, is there a Heimdall one click for JB?
Click to expand...
Click to collapse
I haven't seen a Heimdall for JB, or any custom ROM I think because it requires a special PIT file to make. I used this ROM http://forum.xda-developers.com/showthread.php?t=1776129 To flash It though you have to be on the Gingerbread bootloaders, and the instructions for flashing it want you to even flash CM9 ICS, before you flash the final JB ROM. Basically follow the instructions thoroughly or you'll end up in a boot loop ( Not that that's a big deal, now that you have a quick easy way out)

meanhs sal
darn, I'll have to see if JB is really worth it to take the chance again. I also noticed that froyo version from the Heimdall is quirky with some apps. I turn the phone on and several apps just close on me. I get the buzz of death (the one and three) as i like to call it

I'm pretty sure there's Gingerbread version of the Heimdall one click, I'd flash that as almost all the newer Roms are going to require you at least have upgraded to the Gingerbread bootloaders.

Recover bricked IDOL 3 5.5 and 4.7 all variants

Hi everyone,
As many of us know experimenting with stock roms and installing custom roms can lead to many problems, such as boot loops, random restarts, stuck on boot animation etc..
It happened to me, so here is the solution:
1. Power off the device
2. Download the Alcatel Mobile Upgrade app, you can find it on Alcatel site since I can't yet post links
3. Connect your device with USB to your PC while its off.
4. Wait until the battery icon disappears, and then press the both Volume up and Volume down button + Power button.
5. Now the screen will turn red.
6. Open the Mobile Upgrade app and select 6045(5.5) or 6039(4.7) respectivley.
7. Now just click next all the way until the button turns to Download.
8. Long press the volume up button until it vibrates then release.
9. Now press the download button and wait until the process completes.
NOTE: It will take a while since the Alcatel servers are quite slow, in my case it took 3+ hours, but hey it does the job!
Good luck and Cheers!

Hi Thanks for the post, By following those steps can i restore/downgrade my phone firmware to its initial release and remove all the updates ?
because i'm facing some problems and i want to reinstall the system updates properly.

AzizKhb said:
Hi Thanks for the post, By following those steps can i restore/downgrade my phone firmware to its initial release and remove all the updates ?
because i'm facing some problems and i want to reinstall the system updates properly.
Click to expand...
Click to collapse
I think that isn't possible because the software will instal the latest firmware on the device

relvas18 said:
I think that isn't possible because the software will instal the latest firmware on the device
Click to expand...
Click to collapse
Great, so the software will flash the phone and reinstall the firmware on the device ?

AzizKhb said:
Great, so the software will flash the phone and reinstall the firmware on the device ?
Click to expand...
Click to collapse
yes, will install the latest version

AzizKhb said:
Hi Thanks for the post, By following those steps can i restore/downgrade my phone firmware to its initial release and remove all the updates ?
because i'm facing some problems and i want to reinstall the system updates properly.
Click to expand...
Click to collapse
Absolutley, whatever you did or installed this restores the phone to its factory stock rom and settings. Good luck.

relvas18 said:
yes, will install the latest version
Click to expand...
Click to collapse
muderris said:
Absolutley, whatever you did or installed this restores the phone to its factory stock rom and settings. Good luck.
Click to expand...
Click to collapse
That's what i was looking for, i'm going to give it a try.
Great forum with great members, Thanks everyone

AzizKhb said:
That's what i was looking for, i'm going to give it a try.
Great forum with great members, Thanks everyone
Click to expand...
Click to collapse
Sure thing, any time. If you encouter any further issues don't hesitate to ask.

works...
thank you, it is this , I have a dual 6045K yes, and got back to stock ...
very good..
thank you!!!!!
just follow the steps .....
delay and error can give a first time, so back to the beginning

You're most welcome, happy modding.

I don't know if things have changed with Mobile Q, but this sw is janky JUNK.
If I attempt to update while off, it starts when identifying sw version and either craps out connecting to their server or tells me 'there is no greater' i.e. I'm running latest already (which I'm not as OTA is waiting to install). Choose Upgrade anyway after getting phone back off (or download mode) and rinse/repeat. If one didn't turn back off (or download mode), then it would just balk that it can't identify phone (that it just identified to tell me the phone is up to date (which it's not). It's like a mindless loop of step 3. :silly:
Just did chainfire full unroot and wanted to get last update the easiest way.
Maybe it's because phone downloaded latest update OTA, but have as of yet to install (because I didn't want boot loop due to recovery.img
The LGMobile support tool is so much better...
Now that I removed root, how in f-k do I even get back into TWRP.
---------- Post added at 11:42 AM ---------- Previous post was at 10:56 AM ----------
tried again after factory reset, then download mode (funny that's a blank screen after red screen long press vol up). PoS reboots when checking server for latest sw, then
'there is no greater software version available to ugprade your phone,actual version of your phone is the latest.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

I am waiting on 4.7 in a couple of days.
Trying to get my files together now.
This seems worth having since I love custom ROMs.
Thanks

muderris said:
Hi everyone,
As many of us know experimenting with stock roms and installing custom roms can lead to many problems, such as boot loops, random restarts, stuck on boot animation etc..
It happened to me, so here is the solution:
1. Power off the device
2. Download the Alcatel Mobile Upgrade app, you can find it on Alcatel site since I can't yet post links
3. Connect your device with USB to your PC while its off.
4. Wait until the battery icon disappears, and then press the both Volume up and Volume down button + Power button.
5. Now the screen will turn red.
6. Open the Mobile Upgrade app and select 6045(5.5) or 6039(4.7) respectivley.
7. Now just click next all the way until the button turns to Download.
8. Long press the volume up button until it vibrates then release.
9. Now press the download button and wait until the process completes.
NOTE: It will take a while since the Alcatel servers are quite slow, in my case it took 3+ hours, but hey it does the job!
Good luck and Cheers!
Click to expand...
Click to collapse
Thank you so very much for this.... Alcatel says nothing about booting into Download mode... this did the trick!
Was enjoying the Cyanogen Mod ROM and TWRP, until my phone was blown off a table and cracked the screen just above the USB port... So glad I bought the insurance, but it would have been null and void if still rooted and customized....
Making certain it's completely factory, and slogging up to Cricket tomorrow at 11 to get it replaced, then back to where I originally had this one....
You've saved my butt, and I'm eternally grateful!
(BTW, my PC is running Win10 Pro 64 and the 4.9..2 Mobile Upgrade works like a champ!)

You're welcome, glad it was useful and as always have fun!

anybody know if theres an adb command to get into download mode? im beginning to think my device reboots out of downloade mode when usinf the tool due to faulty power button

carnivalrejectq said:
anybody know if theres an adb command to get into download mode? im beginning to think my device reboots out of downloade mode when usinf the tool due to faulty power button
Click to expand...
Click to collapse
I thinks there is a command for download mode in adb, but only if you had USB debugging enabled previousley.

Thank you!
Thanks bro you saved me 1:40 min under windows 10.1
i love this forum, and i love the work that everyone is doing here!
good luck for you all!!! :victory:

I am currently experiencing book loops during startup of the phone on my alcatel one touch idol 3. Did not want to reset to factory settings, wondering if I can follow the steps to install 6045(5.5) without loosing data on the phone, please help.

Hello
sorry for my question : does this method relock the bootloader too ?
I mean: after install, the phone will be full-stock ?
thanks for answers

rameshidol said:
I am currently experiencing book loops during startup of the phone on my alcatel one touch idol 3. Did not want to reset to factory settings, wondering if I can follow the steps to install 6045(5.5) without loosing data on the phone, please help.
Click to expand...
Click to collapse
If you had USB debugging enabled you could flash the TWRP recovery and create a backup of your data then reset the phone and restore the data.

[Help] S8+ G955F Screen unresponsive, computer won't recognize phone which means. RIP

Hey guys! Posting here will be my last effort into trying to save my phone. I've tried everything... But before I get into that let me give you a little bit of background:
Phone is rooted with Magisk, I have a ROM on it (RENOVATED ICE 13.1). I had Xposed Framework on it with a handful of modules. Phone was running smoothly but I restart it to apply a Magisk module (WhatsApp Emoji) to systemlessly replace the stock Android Emoji with WhatsApp Emoji. When the phone restarted I no longer could interact with the screen, meaning that the display ins't registering my touches or reacting to them. Tried to unlock the phone with fingerprint but I can't because I have to put my 4 digit pin because the phone just restarted. Can't put my 4 digit password because the screen is not responding to my touch, swipes or anything. Power button + Vol down, battery disconnect and phone reboots. I try to access to TWRP just to realize I no longer have it on my phone for some strange reason. Which means it got deleted somehow or most likely it got corrupted and doesn't want to pop up. So.. No access to TWRP. I can't clean dalvik cache, format the phone or reinstall the ROM. All that is a perfect recipe for factory reset from Odin but my computer doesn't recognize my phone.
Things I've already tried:
Try to unlock the phone with Bixby voice (Sends me back to putting my pin).
Connect a mouse to try to click the pin numbers (Mouse doesn't turn on).
Connect a keyboard to try to put my pin from there (Keyboard also won't turn on).
Tried booting in safe mode (No difference at all from normal mode, same problems, same everything)..
Tried to access to TWRP (No TWRP access).
Tried to factory reset from Odin (Computer won't recognize the phone).
PD: I'm aware that Odin can be picky with cords and ports and the possibility that my computer may be missing some drivers and because of that won't recognize the phone but that is not the case.. I just successfully factory reset another S8+ from a friend and my computer and Odin recognized his phone instantly, so I know for a fact that my computer is alright. I wish I could say the same about my phone. I suspect the unresponsive screen is a software problem, the screen has zero damage, no falls, no reasons to believe is a hardware malfunction. To my eyes this phone is dead and have no foreseeable repair. I know there isn't much to do but feel free share any possible via of solution.
Thanks!

This will not help you. My phone, S8+ UK version, has periods of unresponsiveness, similar to yours. My phone is stock, never been rooted but screen was repaired 1 year ago. No problems until 10 weeks ago. Unresponsive for few minutes daily. I always get, 'System UI isn't responding' at least 10 times a day.
I'm just waiting to get more money. My next phone is not going to be a Samsung.
Sent from my SM-G955F using Tapatalk

adewfaw said:
This will not help you. My phone, S8+ UK version, has periods of unresponsiveness, similar to yours. My phone is stock, never been rooted but screen was repaired 1 year ago. No problems until 10 weeks ago. Unresponsive for few minutes daily. I always get, 'System UI isn't responding' at least 10 times a day.
I'm just waiting to get more money. My next phone is not going to be a Samsung.
Click to expand...
Click to collapse
Maybe it's an app you unintentionally installed. Do you have a theming app or something similar?
---------- Post added at 07:49 PM ---------- Previous post was at 07:46 PM ----------
vulkhead said:
Hey guys! Posting here will be my last effort into trying to save my phone. I've tried everything... But before I get into that let me give you a little bit of background:
Phone is rooted with Magisk, I have a ROM on it (RENOVATED ICE 13.1). I had Xposed Framework on it with a handful of modules. Phone was running smoothly but I restart it to apply a Magisk module (WhatsApp Emoji) to systemlessly replace the stock Android Emoji with WhatsApp Emoji. When the phone restarted I no longer could interact with the screen, meaning that the display ins't registering my touches or reacting to them. Tried to unlock the phone with fingerprint but I can't because I have to put my 4 digit pin because the phone just restarted. Can't put my 4 digit password because the screen is not responding to my touch, swipes or anything. Power button + Vol down, battery disconnect and phone reboots. I try to access to TWRP just to realize I no longer have it on my phone for some strange reason. Which means it got deleted somehow or most likely it got corrupted and doesn't want to pop up. So.. No access to TWRP. I can't clean dalvik cache, format the phone or reinstall the ROM. All that is a perfect recipe for factory reset from Odin but my computer doesn't recognize my phone.
Things I've already tried:
Try to unlock the phone with Bixby voice (Sends me back to putting my pin).
Connect a mouse to try to click the pin numbers (Mouse doesn't turn on).
Connect a keyboard to try to put my pin from there (Keyboard also won't turn on).
Tried booting in safe mode (No difference at all from normal mode, same problems, same everything)..
Tried to access to TWRP (No TWRP access).
Tried to factory reset from Odin (Computer won't recognize the phone).
PD: I'm aware that Odin can be picky with cords and ports and the possibility that my computer may be missing some drivers and because of that won't recognize the phone but that is not the case.. I just successfully factory reset another S8+ from a friend and my computer and Odin recognized his phone instantly, so I know for a fact that my computer is alright. I wish I could say the same about my phone. I suspect the unresponsive screen is a software problem, the screen has zero damage, no falls, no reasons to believe is a hardware malfunction. To my eyes this phone is dead and have no foreseeable repair. I know there isn't much to do but feel free share any possible via of solution.
Thanks!
Click to expand...
Click to collapse
Did you try to uninstall the drivers then reinstall. Try to reset straight from stock recovery if you can still get to it.

eddyo1993 said:
Maybe it's an app you unintentionally installed. Do you have a theming app or something similar?
---------- Post added at 07:49 PM ---------- Previous post was at 07:46 PM ----------
Did you try to uninstall the drivers then reinstall. Try to reset straight from stock recovery if you can still get to it.
Click to expand...
Click to collapse
I reinstalled all the drivers before I realize my computer wasn't the problem because as I said, I successfully achieve a stock reset with my friend's phone (also an S8+) and Odin recognized instantly without any hassle. I can't reset from stock recovery because I don't really have it, TWRP must be there, corrupted. I can't access to any form of recovery from the phone.

vulkhead said:
I reinstalled all the drivers before I realize my computer wasn't the problem because as I said, I successfully achieve a stock reset with my friend's phone (also an S8+) and Odin recognized instantly without any hassle. I can't reset from stock recovery because I don't really have it, TWRP must be there, corrupted. I can't access to any form of recovery from the phone.
Click to expand...
Click to collapse
I'm sure you tried to go into download mode then connect it to Odin right?

adewfaw said:
This will not help you. My phone, S8+ UK version, has periods of unresponsiveness, similar to yours. My phone is stock, never been rooted but screen was repaired 1 year ago. No problems until 10 weeks ago. Unresponsive for few minutes daily. I always get, 'System UI isn't responding' at least 10 times a day.
I'm just waiting to get more money. My next phone is not going to be a Samsung.
Sent from my SM-G955F using Tapatalk
Click to expand...
Click to collapse
Your case sounds like a software malfunction, try to stock reset everything with Odin and you should be good!

vulkhead said:
I reinstalled all the drivers before I realize my computer wasn't the problem because as I said, I successfully achieve a stock reset with my friend's phone (also an S8+) and Odin recognized instantly without any hassle. I can't reset from stock recovery because I don't really have it, TWRP must be there, corrupted. I can't access to any form of recovery from the phone.
Click to expand...
Click to collapse
Try this odin
https://forum.xda-developers.com/attachment.php?attachmentid=4446947&d=1521037501

eddyo1993 said:
I'm sure you tried to go into download mode then connect it to Odin right?
Click to expand...
Click to collapse
Yes sir! My phone goes into download mode perfectly but Odin doesn't detect it. That's my main problem, I wouldn't be here If I could stock reset from Odin.

vulkhead said:
Yes sir! My phone goes into download mode perfectly but Odin doesn't detect it. That's my main problem, I wouldn't be here If I could stock reset from Odin.
Click to expand...
Click to collapse
Yeah I'm sure. Had the same issue before I'm trying to help out. If you don't need it then good luck.

eddyo1993 said:
Try this odin
https://forum.xda-developers.com/attachment.php?attachmentid=4446947&d=1521037501
Click to expand...
Click to collapse
Thanks a lot for taking your time, I just tried you Odin and didn't work, I've also tried all these:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

vulkhead said:
Thanks a lot for taking your time, I just tried you Odin and didn't work, I've also tried all these:
Click to expand...
Click to collapse
I'm curious when you do Power+Bixby+Vol. Up what does it do in place of taking you to TWRP

eddyo1993 said:
I'm curious when you do Power+Bixby+Vol. Up what does it do in place of taking you to TWRP
Click to expand...
Click to collapse
It does nothing, it just perform a normal reboot that takes me back to where I'm stuck: the lockscreen.. I can see my wallpaper there, some notifications.. I can access to the camera by double pressing power button, I can access to Bixby, powermenu.. All that stuff. :crying:

vulkhead said:
It does nothing, it just perform a normal reboot that takes me back to where I'm stuck: the lockscreen.. I can see my wallpaper there, some notifications.. I can access to the camera by double pressing power button, I can access to Bixby, powermenu.. All that stuff. :crying:
Click to expand...
Click to collapse
I'm wondering how were you able to get into safe mode if the touch screen wasn't responsive. You can reset your phone through the maintenance menu by doing the Power+Vol. Down for 10 seconds wait till it goes black hold power button again till you feel a light vibrate.

eddyo1993 said:
I'm wondering how were you able to get into safe mode if the touch screen wasn't responsive. You can reset your phone through the maintenance menu by doing the Power+Vol. Down for 10 seconds wait till it goes black hold power button again till you feel a light vibrate.
Click to expand...
Click to collapse
I didn't have to use the screen at all to go into safe mode. You can enter safe mode by rebooting your phone, pressing Power until Samsung logo appears and quickly release Power button while press Vol Down until the phone finish the reboot. Unfortunately safe mode does nothing for me. I understand that Power+Vol Down virtually disconnect the battery to make a reboot, I didn't understand very well the part of accessing into the maintenance menu. I tried what you said but my phone but performed a normal reboot.

You may have to repartition and install the latest stock via Odin. When nothing works, repartition works well.

bluheart said:
You may have to repartition and install the latest stock via Odin. When nothing works, repartition works well.
Click to expand...
Click to collapse
Can't use Odin because phone doesn't get recognized by Odin nor the computer itself.

Just a stupid thought and may not help
Have you tried logging into your Samsung or Google account and tried to use the ' find my phone' feature. I believe you can unlock or at least wipe your phone using this. I've never used it so don't know if it will work or not.

spawnlives said:
Just a stupid thought and may not help
Have you tried logging into your Samsung or Google account and tried to use the ' find my phone' feature. I believe you can unlock or at least wipe your phone using this. I've never used it so don't know if it will work or not.
Click to expand...
Click to collapse
I didn't found such feature

send it to samsung, if you're lucky they will fix it under warranty.

lynxblaine said:
send it to samsung, if you're lucky they will fix it under warranty.
Click to expand...
Click to collapse
My phone had his malfunction while rooted. WARRANTY VOID: 1 (0x030c) Sadly I loosed any right to warranty.