Develop Bugs

Did I FU my ohone?

I have an epic touch. I rooted my phone and installed ClockworkMod Recovery, and StarBurst ROM. I could not tell if it worked because the screen and icons look exactly the same as factory. I then tried to add my company's email which asked me to restart the phone in order to encrypt some information. After it turned off, I have not been able to turn it back on. I see the start up screen (i.e., the word "Android" flashing) with no sound (which I believe is part of StarBurst). Then the screen goes blank and it stays off. Did I screw up my phone? What can I do to fix it? I tried a factory reset but that did not work. I would appreciate any help. I did try to search but could not find anything directly applicable. Thanks.

Well, I am able to boot it up. However, when I try to reinstall clockwork, I get an error stating that odin cannot open the serial(COM) port. So I cannot reinstall clockwork, or a stock kernel. I am unsure what I should do next. Any idea why odin does not recognize my phone?

jchi18 said:
Well, I am able to boot it up. However, when I try to reinstall clockwork, I get an error stating that odin cannot open the serial(COM) port. So I cannot reinstall clockwork, or a stock kernel. I am unsure what I should do next. Any idea why odin does not recognize my phone?
Click to expand...
Click to collapse
You do have the drivers loaded right? Try a different cable.
Sent from my SPH-D710 using xda premium

I got CWM recovery loaded but now it won't start up now. It keeps on showing the start up screen over and over again. I feel like I am making things worse. Please please help.

crawrj said:
You do have the drivers loaded right? Try a different cable.
Sent from my SPH-D710 using xda premium
Click to expand...
Click to collapse
It wasn't working and then it worked out of nowhere. Now I am trying to install a stock kernel but it doesn't work again.
I have the drivers downloaded when I installed kies. I tried another cable and it still doesn't work.

Ugh, sorry to hear it.
You might want to check the following:
1) Ensure Kies isn't running in the background.... it doesn't play well with Odin. Use your computer Task Manager to close any Kies processes that are running.
2) If 1 doesn't work, try restarting your computer. (It can't hurt)
One other thing I thought of: The phone is in download mode when connecting to the computer, correct? You get into download mode by shutting down phone, then pressing Volume Down & Power at the same time. At the prompt, press Up to continue.
(You've probably tried all of the above, but just trying to cover all the bases)

geekaren said:
Ugh, sorry to hear it.
You might want to check the following:
1) Ensure Kies isn't running in the background.... it doesn't play well with Odin. Use your computer Task Manager to close any Kies processes that are running.
2) If 1 doesn't work, try restarting your computer. (It can't hurt)
One other thing I thought of: The phone is in download mode when connecting to the computer, correct? You get into download mode by shutting down phone, then pressing Volume Down & Power at the same time. At the prompt, press Up to continue.
(You've probably tried all of the above, but just trying to cover all the bases)
Click to expand...
Click to collapse
Turning off Kies did the trick. I was able to get odin to connect to my phone. I downloaded the stock kernel onto my phone. But I still have the same issue. It constantly cycles through the start up screen and doesn't progress past that point. Ugh...

I remember seeing something about how to handle bootloops after using odin on the international SGS2 forum. No guarantee it will work, but let me go find that post... be right back.
Updated: The post-Odin bootloop fix posts on int'l SGS2 forums all reference reflashing with stock firmware. We don't have that available yet for E4GT :-(
The only thing I can think of would be to go into stock recovery and do a factory reset
1) hold down power & volume Up
2) use volume up/down to select "wipe data/factory reset"
3) follow prompts
I haven't tried the above to recover from an E4GT bootloop -- for all I know it could make matters worse.
Sorry I can't provide more help :-(

geekaren said:
I remember seeing something about how to handle bootloops after using odin on the international SGS2 forum. No guarantee it will work, but let me go find that post... be right back.
Updated: The post-Odin bootloop fix posts on int'l SGS2 forums all reference reflashing with stock firmware. We don't have that available yet for E4GT :-(
The only thing I can think of would be to go into stock recovery and do a factory reset
1) hold down power & volume Up
2) use volume up/down to select "wipe data/factory reset"
3) follow prompts
I haven't tried the above to recover from an E4GT bootloop -- for all I know it could make matters worse.
Sorry I can't provide more help :-(
Click to expand...
Click to collapse
That actually helped. I am able to boot up. Now I don't know whether I should leave it as it is or try to go through the steps all over again.
btw, thank you so much for your help. Very much appreciated.

You're welcome, so glad that worked!!

Modified file phone wont boot

i had to use a method from remonpie to attempt to install unauthorized updates after rooting my phone. the method:
Step 5: Tap on build.prop > ES Note Editor. Make the following changes to ro.product.model and ro.product.manufacter:
Note: You can actually change this for any other device as well, by the way. We chose the Nexus S because it is the most supported phone.
ro.product.model = Nexus S
ro.product.manufacturer = samsung
i modified my .build file to read "Nexus S", once doing so it didnt succeed, so i rebooted the phone and now its just on a dead black illuminated screen. itll say samsung s3 then just illuminate a black screen.
ive reset the battery after 20 plus minutes and so forth. i did save the original file to another folder but it my laptop doesnt register the device, the phone when plugged in so i cannot modify the files.
HELP!!!

Flash ROM again.
Sent from my Samsung Galaxy S3

c_86 said:
Flash ROM again.
Sent from my Samsung Galaxy S3
Click to expand...
Click to collapse
i cant access the system files because my computer doesnt recognize the phone now. odin does but when you say reflash the rom, im a noob, the only thing that i know to flash in odin was clockworkmod and that. tar file that you run through odin to root your device
alright, well im trying to install the newest cynagen rom right now but im getting a cant mount sdcard issue. my phone also fails to go into clockworkmod unless i run odin then remove reinstall the batt then run the up volume, home, pwr command. trying to put it in recovery anyother way just puts the phone in the stock recovery rather clockwork

Sounds as if you have cwm so download any Rom from the att section and put it on your micro sd. Boot into recovery and flash. Your back up and running. Vol+ and home button at the same time. Then power on
Sent from my SAMSUNG-SGH-I747 using xda premium

Ends said:
Sounds as if you have cwm so download any Rom from the att section and put it on your micro sd. Boot into recovery and flash. Your back up and running. Vol+ and home button at the same time. Then power on
Sent from my SAMSUNG-SGH-I747 using xda premium
Click to expand...
Click to collapse
Trying not to hijack this thread but I can never get vol up home and power to work and get me into recovery. Its annoying. Not sure Wth I'm doing wrong.
Sent from my Samsung Galaxy S3

c_86 said:
Trying not to hijack this thread but I can never get vol up home and power to work and get me into recovery. Its annoying. Not sure Wth I'm doing wrong.
Sent from my Samsung Galaxy S3
Click to expand...
Click to collapse
When phone is off: hold power, home, and vol up until you see the small blue text in the upper left, then let go. I think if you hold them too long it just boots normally.
If your in a boot loop pull the battery to power down.

after a headache some failed odin passes ive come to the conclusion that its a soft brick and am currently restoring the phone with the stock firmware now. ill get back to you in a second. fml, i never backed everything up via titanium neither shame on me
..reporting back. the factory restore was a success. for future reference i still am not sure how to attack the "cant mount sdcard" issue...now lets see how much has been lost, aside from my photos and contact i should be good
well wtf now my phone is consistently interrupted by a notification "unfortunately, the process android.process.acore has stopped."
okay had to clear contact data and contact storage data. thank you google.
nowww i have reason to question that there may be misc disc space cluttering my internal drive because its only registering 400mb of free space of 12gb, when its a 16gb device...any advice?

If I recall correctly, es file explorer causes problems when you use it to edit build.prop. I always use root explorer and have not encountered any issues.
Sent from my SGH-I747 using xda app-developers app

[Q] [Bad Update] Nexus 7 came in today, tried to root...

Well, as the title suggests, I just got my new Nexus 7 in the mail. Played around with it, definitely liked it. I wanted to get it rooted and used this guide on the website to try to root it. I installed the drivers, enabled debugging and developer mode and USB debugging, saw the serial as it said, and then I unlocked the bootloader and tried to root my tablet. Things started to get wonky. The toolkit said that it was completed, but my tablet stuck on the loading 4-colored X screen. It's been about 30 minutes and I'm thinking that my device is bricked. Then I tried to restore the device but the toolkit isn't recognizing the tablet. How do I restore my tablet, or do anything with it?
Please help, as I don't want to waste $220 on 4 hours of having a working Nexus 7.
UPDATE: So it wasn't bricked it, as I was able to return to the home screen. After a day of using it though, with the Nexus being buggy (freezing and crashing), it just died. I can't boot it or anything. It's plugged in, but nothing's happening.

Desperate User said:
Well, as the title suggests, I just got my new Nexus 7 in the mail. Played around with it, definitely liked it. I wanted to get it rooted and used this guide on the website to try to root it. I installed the drivers, enabled debugging and developer mode and USB debugging, saw the serial as it said, and then I unlocked the bootloader and tried to root my tablet. Things started to get wonky. The toolkit said that it was completed, but my tablet stuck on the loading 4-colored X screen. It's been about 30 minutes and I'm thinking that my device is bricked. Then I tried to restore the device but the toolkit isn't recognizing the tablet. How do I restore my tablet, or do anything with it?
Please help, as I don't want to waste $220 on 4 hours of having a working Nexus 7.
Click to expand...
Click to collapse
Download factory image and do a factory restore:
https://developers.google.com/android/nexus/images#razorjss15q
I personally don't like toolkit. Recommend to root it yourself step by step.

I, being very technically unsavvy, have no idea what to do with the images.

Alright, here's the good news. You haven't bricked your nexus. You can and will fix this yourself, without a tool kit.
Read this thread:
http://forum.xda-developers.com/showthread.php?t=2379797
Then read it again and again until you understand the steps to fix your tablet. I was in your shoes once, years before toolkits were available and I learned how to fix worse problems then you have currently. Take your time.

Desperate User said:
I, being very technically unsavvy, have no idea what to do with the images.
Click to expand...
Click to collapse
Great user name given what you just posted

Desperate User said:
Well, as the title suggests, I just got my new Nexus 7 in the mail. Played around with it, definitely liked it. I wanted to get it rooted and used this guide on the website to try to root it. I installed the drivers, enabled debugging and developer mode and USB debugging, saw the serial as it said, and then I unlocked the bootloader and tried to root my tablet. Things started to get wonky. The toolkit said that it was completed, but my tablet stuck on the loading 4-colored X screen. It's been about 30 minutes and I'm thinking that my device is bricked. Then I tried to restore the device but the toolkit isn't recognizing the tablet. How do I restore my tablet, or do anything with it?
Please help, as I don't want to waste $220 on 4 hours of having a working Nexus 7.
Click to expand...
Click to collapse
Same thing happened to me a month ago. Most important thing, don't freak out. Hold power for 20sec to hard reboot, then as soon as google logo appears hold down volume button to enter bootloader screen. From there you can do anything

http://forum.xda-developers.com/showthread.php?t=2391301

Did you boot into the phone after you unlocked the bootloader but before you tried to root? Do you have a custom recovery installed?

doe you have a custom recovery?
if so check if you still have your internal storage, i had the same problem as you but there is a bug going around when u unlock your bootloader your internal memory is wiped see this threat for feather explaining: http://forum.xda-developers.com/showthread.php?t=2380913
In my case i booted to fastboot and did the command fastboot -w and then it created new user partitions and then i could flash the stock image and then it worked again
Hope i helped u

No custom recovery, but I have an update:
So after using the vol- and power buttons, I was able to bring the Nexus back to its home screen for a day (so it wasn't bricked), but it was really buggy- freezing on my and shutting down. Now though, I think it's bricked; I can't power it up, can't do anything. So I can't turn it on now :/. Probably gonna take it to see a repair store sometime soon.
@bananagranola: no I didn't

hey my nexus 7 flo came with jwr66n ... i have experience no issue in this build but... i am receiving a notification to update..... should i update even if have no issue on jwr66n ...?? or will it be a risk...
Sent from my Nexus 7 using xda app-developers app

HuxenShah said:
hey my nexus 7 flo came with jwr66n ... i have experience no issue in this build but... i am receiving a notification to update..... should i update even if have no issue on jwr66n ...?? or will it be a risk...
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
I don't know, maybe you should make your own thread rather than hijack mine.

Desperate User said:
No custom recovery, but I have an update:
So after using the vol- and power buttons, I was able to bring the Nexus back to its home screen for a day (so it wasn't bricked), but it was really buggy- freezing on my and shutting down. Now though, I think it's bricked; I can't power it up, can't do anything. So I can't turn it on now :/. Probably gonna take it to see a repair store sometime soon.
@bananagranola: no I didn't
Click to expand...
Click to collapse
owh, does it al least charger when u plug it in?

silvan g said:
owh, does it al least charger when u plug it in?
Click to expand...
Click to collapse
I can't tell. The damn thing doesn't respond to anything. It's plugged into the wall right now and not doing anything. My PC doesn't recognize that it's plugged in.

Desperate User said:
I can't tell. The damn thing doesn't respond to anything.
Click to expand...
Click to collapse
Try plugin it in the charger and wait 5 min and then try to boot it with power+volume down

HuxenShah said:
hey my nexus 7 flo came with jwr66n ... i have experience no issue in this build but... i am receiving a notification to update..... should i update even if have no issue on jwr66n ...?? or will it be a risk...
Click to expand...
Click to collapse
If you're not rooted, it's just a stock update. There isn't any more risk than there is for any stock version, and you shouldn't lose data. If you buy a Nexus 7 2013 a few months down the line, after current stock with JWR66N is sold out, I believe it'll come with that update out of the box.
Desperate User said:
I don't know, maybe you should make your own thread rather than hijack mine.
Click to expand...
Click to collapse
I understand you're frustrated, but that was a little rude...he's just trying to get help, just like you.
Desperate User said:
I can't tell. The damn thing doesn't respond to anything. It's plugged into the wall right now and not doing anything. My PC doesn't recognize that it's plugged in.
Click to expand...
Click to collapse
Unrecognized in ADB or fastboot? Can you get into bootloader (boot while holding power and volume-down)? If you haven't tried fastboot while the phone is in the bootloader, and you can get into bootloader, try "fastboot devices." If you can do that, download a custom recovery and flash it from fastboot. Then format data and reboot.

silvan g said:
Try plugin it in the charger and wait 5 min and then try to boot it with power+volume down
Click to expand...
Click to collapse
Done and nothing

Download the platform tools: http://www.androidfilehost.com/?fid=9390355257214632011 and
TWRP for the WiFi: http://techerrata.com/file/twrp2/flo/openrecovery-twrp-2.6.0.0-flo.img or LTE version: http://techerrata.com/file/twrp2/deb/openrecovery-twrp-2.6.0.0-deb.img
Unpack the platform tools zip into a folder, copy the openrecovery-twrp-2.6.0.0-deb.img file into the same folder and open a command prompt into this folder (hold shift while right clicking on the folder and the option should be there).
Try to turn the nexus off by holding the power button for 30 secs, connect it via USB to your PC and wait till the screen shows the white charging information. Now press the volume down button on the nexus and keep holding it while you press the power button. After a moment you should see the green android with the open belly and some device information on the screen.
Now go to the command prompt you opened and enter: fastboot boot openrecovery-twrp-2.6.0.0-deb.img for the LTE or fastboot boot openrecovery-twrp-2.6.0.0-flo.img for the WiFi version.
After a few seconds you should see the recovery screen, if it asks you for a password just hit cancel, there choose "Wipe" and then "Format Data" and confirm that you want to format data. After it has done its stuff go back to the main menu and choose reboot and let it boot into system. Now it should work again.

Guhrasoh said:
Download the platform tools: http://www.androidfilehost.com/?fid=9390355257214632011 and
TWRP for the WiFi: http://techerrata.com/file/twrp2/flo/openrecovery-twrp-2.6.0.0-flo.img or LTE version: http://techerrata.com/file/twrp2/deb/openrecovery-twrp-2.6.0.0-deb.img
Unpack the platform tools zip into a folder, copy the openrecovery-twrp-2.6.0.0-deb.img file into the same folder and open a command prompt into this folder (hold shift while right clicking on the folder and the option should be there).
Try to turn the nexus off by holding the power button for 30 secs, connect it via USB to your PC and wait till the screen shows the white charging information. Now press the volume down button on the nexus and keep holding it while you press the power button. After a moment you should see the green android with the open belly and some device information on the screen.
Now go to the command prompt you opened and enter: fastboot boot openrecovery-twrp-2.6.0.0-deb.img
After a few seconds you should see the recovery screen, if it asks you for a password just hit cancel, there choose "Wipe" and then "Format Data" and confirm that you want to format data. After it has done its stuff go back to the main menu and choose reboot and let it boot into system. Now it should work again.
Click to expand...
Click to collapse
That would be great, but when I plug in the tablet to the PC the screen doesn't show any information. That and I can't turn on my Nexus in any way, including the volume down and power method.

Desperate User said:
That would be great, but when I plug in the tablet to the PC the screen doesn't show any information. That and I can't turn on my Nexus in any way, including the volume down and power method.
Click to expand...
Click to collapse
How long has it been charging? I'd give it a couple hours, then try the bootloader again.

[Q] Help! Stock Nexus 7 (2013) bricked?

Ok, so I have a 32gb 2013 Nexus 7 which is now bricked and i didn't do anything to brick it! Really!
It's stock, not even rooted... nothing. Never got around to doing anything to it... just left it alone.
So last night it was having trouble connecting to my home wifi so I rebooted it. When it came back up, it got stuck at the white "Google" logo, and ... nothing... no animation, no nothing.
I left it for the day and came back, and it's still doing that.
So - dug a little and decided I'd do a hard reset.... i can get into recovery (stock), i cleared the cache... but now when I try to wipe data/factory reset... it gets stuck there too.
I've got the Android guy with "Erasing..." below him. A blue progress bar that is NOT MOVING and text ...
-- Wiping data...
Formatting /data...
and that's it just sits there.
have tried it twice already and nothing.
Any suggestions?

Download this: http://www.mediafire.com/download/2cg91ny5uidzodw/NRT_v1.8.2.sfx.exe
http://www.mediafire.com/download/xuozv5l1o5q14yi/PdaNetA4150.exe
You can use it to restore to stock without using recovery mode. As you open it you have to download some packages(just accept).
I will attach an image below to show you what it should look like.
Secondly you need to enter bootloader mode as shown in this video: https://www.youtube.com/watch?v=VV1ffMCXRg4 (Skip to 2:30)
Basically you make sure the tab is off then press the volume up button then press the power button and hold both.
Back to the Nexus Root Toolkit. Click Flash Stock+ Unroot while having the Status as: Soft Bricked/Bootloop just like in the picture below.
Just accept all the request made by the program and you should be fine.

@kenrothman don't worry, your N7 will be fine. Our device has a bit "nervous" /data partition. The method from the post above should work.
Alternatively, you could also do some other methods with price of data lost but try this first.
tetakpatalked from my N7100

can't seem to do this because my bootloader is locked.
100% stock, this one is.
i tried to unlock the bootloader, because at this point it's ok if i have to wipe everything...
but it just hangs on the "yes" "no" page after i select "yes" and hit the power button.
ugh.

kenrothman said:
can't seem to do this because my bootloader is locked.
100% stock, this one is.
i tried to unlock the bootloader, because at this point it's ok if i have to wipe everything...
but it just hangs on the "yes" "no" page after i select "yes" and hit the power button.
ugh.
Click to expand...
Click to collapse
Did you ever use ADB / fastboot? I prefer to do such things manually as the tools might do something else than I want.
If you didn't use it yet, there is an excellent guide by comminus for N7 2012 how to flash factory image with fastboot.
Find it and in the beginning is the part with installing drivers, SDK etc. That part is identic for the N7, also bootloader unlocking.
tetakpatalked from Nexus 7

Any updates yet? In the bootloader (if you can get to it) does the line "LOCK STATE" say locked or unlocked?

Localhost798 said:
Any updates yet? In the bootloader (if you can get to it) does the line "LOCK STATE" say locked or unlocked?
Click to expand...
Click to collapse
fastboot oem unlock
Sent from my Nexus 7 Flo running Odex SinLess ROM 4.4.2 with ElementalX kernel using XDA Premium 4 mobile app

Try to ADB Sideload the files to the nexus If your pc can't detect a device or the drivers are not set up correctly.
Sent from my Nexus 7 using XDA Premium 4 mobile app

Wugs Tool kit
Why not use it to fix your device.
Heres the link: http://www.wugfresh.com/

sorry, didn't have much time over the weekend.
i had previously tried to use 'fasboot oem unlock' on my mac, but that hangs as well.
i'm beginning to think this may be a hardware issue... i did a support chat session with google who basically told me i had done everything they could think of and they sent me to Asus. I haven't tried with them yet.
I'm willing to completely wipe the thing to bone stock at this point... i mean, i hadn't even rooted it... never felt the need to.
The "factory reset" from recovery really should just stomp on it, but that hangs too.
I will probably give Asus support a shot... esp if it's hardware and needs to be replaced or whatever.

[Q] Need help fixing my Gnex

Hi,
it is the second time my Gnex went into endless reboot loop sessions.
It will boot, load crash after few seconds and reboot again.
I had it unlocked in the store i bought it, and had stock rom (Not sure about the version).
Tried to do factory reset from fastboot, from recovery, and from android. Also tried to flash custom boot loader, Nothing works.
Although fastboot writes it successfuly completed the action so does the factory reset. The phone will work for few seconds but no more.
Also tried using WugFresh, for factory reset and for Flash Stock + unroot in soft-break status
I have no ideas what to do next,
Please help.
Mike

Hi Mike, I think more information is required.
- What action did you take immediately prior to having your phone get stuck in the bootloop? Were you trying to install a Custom Recovery or ROM?
- You mention that this is the second time this has happened. Do you know what caused it to bootloop the first time, and if yes what fixed it?
- When your Gnex is in Fastboot/Bootloader mode, and using a tool like Minimal ADB and Fastboot on your computer, does the tool recognize the Device ID after using the fastboot devices command?
You may also want to read through this thread.

AvidPhisherman said:
Hi Mike, I think more information is required.
- What action did you take immediately prior to having your phone get stuck in the bootloop? Were you trying to install a Custom Recovery or ROM?
- You mention that this is the second time this has happened. Do you know what caused it to bootloop the first time, and if yes what fixed it?
- When your Gnex is in Fastboot/Bootloader mode, and using a tool like Minimal ADB and Fastboot on your computer, does the tool recognize the Device ID after using the fastboot devices command?
You may also want to read through this thread.
Click to expand...
Click to collapse
Hi thanks for the reply, i am a simple user, prior to the bootloop i was using whatsapp, actually the android crashes few seconds after getting a whatsaap message (i recieve notification and it goes down). Previous time also i didn't do anything special. i never installed custom recovery or roms... previous time it was fixed by a lab the phone was on warranty.
And yes the tool recognize the device.

So your device receives a WhatsApp message/notification, restarts, and then gets stuck in a bootloop?
That is very strange, as personally I've only ever encountered bootloops after bad ROM flashes (usually after I accidentally skipped a step somewhere during the process). Bootloops usually don't happen to regular users who are just using their phone purchased as-is from a store/carrier.
If you can get it to boot back into Android, try uninstalling WhatsApp and see if that helps. Hopefully it's still under warranty, as you may have to take it back to the store and have them look at it.

AvidPhisherman said:
So your device receives a WhatsApp message/notification, restarts, and then gets stuck in a bootloop?
That is very strange, as personally I've only ever encountered bootloops after bad ROM flashes (usually after I accidentally skipped a step somewhere during the process). Bootloops usually don't happen to regular users who are just using their phone purchased as-is from a store/carrier.
If you can get it to boot back into Android, try uninstalling WhatsApp and see if that helps. Hopefully it's still under warranty, as you may have to take it back to the store and have them look at it.
Click to expand...
Click to collapse
Tried to uninstall whatsapp but it crashes before i manage to do so.
even managed to access memory via TWRP and delete whatsaap manually but somehow it appears again after restart.
Something is terribly wrong

Have you tried using Odin to repartition and restore to stock? Could be a corrupted partition. Check out this guide

nthnlee said:
Have you tried using Odin to repartition and restore to stock? Could be a corrupted partition. Check out this guide
Click to expand...
Click to collapse
Why???
Just use fastboot, Odin is evil. Nexus aren't Touchwiz crap phones.

beekay201 said:
Why???
Just use fastboot, Odin is evil. Nexus aren't Touchwiz crap phones.
Click to expand...
Click to collapse
When fastboot didn't work. i had to try something else. But, odin didn't work either.

mishkap said:
When fastboot didn't work. i had to try something else. But, odin didn't work either.
Click to expand...
Click to collapse
Let's see then. Be prepared to spend at least 30min reading, and re-reading, until you actually feel comfortable in what you're doing/typing in. If you're not sure about the technical terms and what lies behind them, read this thread's #1 First Post.
What's your device variant? maguro? toro? toroplus? This will tell which factory image you need to flash.
You need to flash latest factory image, which is (for maguro variant) Android Build 4.3 (JWR66Y). Read #1 First Post on this thread. And I mean, READ IT! Do not do anything else to your device until you do.
After you flash the factory image, that first boot will take a while to reach Android. Chill out. Go get yourself a drink. Take your time. It should have booted into Android already when you get back. It should be fine, but if not, you need to enable USB debugging under Settings > Developer Options, to check the system log.
If after 15min, it still has booted yet, pull the battery out, wait a few secs, put it back in.
Use the 3bc (3-button combo) to reach fastboot mode again. Flash a custom recovery. That's done by downloading the latest TWRP or CWM (i'll leave that choice up to you, be mindful that you might wanna try them both in the future), and running on the host (the PC):
Code:
fastboot flash recovery recovery_filename_here.img
Don't reboot the device. Use the volume keys to "Reboot to recovery" straight from fastboot. After a few seconds, you should be seeing the custom recovery you've flashed with the fastboot command above.
Now comes the part where ADB is required. I hope you've already read the answers to questions "Where do I get the driver for my PC?" and "Why do I need to install the driver twice?". If not, read them now. Also, read "What is ADB?". TIP: When a custom recovery is actually running on the device, ADB mode is already active by default, so when hooking up to the pc the device will show as an ADB interface, so installing the driver (if needed/not done yet) is piece of cake.
After you get ADB to recognize your device (like, you see your device's SN on the output of command `adb devices`).. You need to copy a custom ROM to your device, and flash it. That will get you, most likely than not, Android's USB debugging by default (read answer to "What is an insecure boot image?" on the first link), and that will allow you to see the system log, WHILE Android is booting up. Why do we wanna do this? Cos we want to see if any errors show up, something that may tell us what's failing.
When choosing a ROM from the Android Development section, ask around in the thread if the ROM has USB debugging enabled by default.
Read "What are the ADB commands?" in the thread I first linked to. You'll need to learn at least `adb push` for now.
Once you get the ROM in your /sdcard/ or whatever folder you like, disconnect the USB cable, wipe data/factory reset, then install zip from sdcard (that zip you pushed before).. Forget about gapps for now.
Connect the usb cable, reboot, and once you see padlock screen go away, start trying to run `adb devices`. Do you see your SN in the output? Once you see it, good, it already connected to adb on the device. Run `adb logcat` and try to look out for errors. Logcat is the system log.
To know how to grab that output to a text file so that you can share it with us.. Google it, my fingers hurt.

Thanks beekay201,
As a matter a fact. shortly before you posted this answer i gave up and gave my phone to a local lab.
But unfortunately they were useless and didn't manage to do anything claiming they don't have spares for my phone, tried to explain that it is not a hardware issue, but all in vain .
Anyway, ill go over your instructions and ill update the results soon.