Database Develop

[A] Solved the Seven Vibration Brick

\\\Disclaimer: I am not responsible if you mess this up & break your phone///
Checking Your Situation:
*Phone only boots to Fastboot
*Phone does/Doesn't charge
*Power button Seems useless
*Phone Turns on and only shows-
the X screen & Vibrates 7x's
*LED Only shows Green/ Orange
indication light
Things You'll Need:
*Wall Charger
*USB Cable
*Computer (duh)
*Battery (of course)
*FRG83 ROM file http://tinyurl.com/6bym3vg
*Android ADB Setup
*Fingers Crossed
(Tip: if you are using the same Sdcard when the phone messed up, reformat it or use a new one)
Step One:
Download FRG83 ROM file http://tinyurl.com/6bym3vg
and unzip the package into your AndroidSDK Tools Folder
Step Two:
Watch the battery trick video
http://youtu.be/2O5adV-jj64 (Thanks n1newbie)
Once you've analyzed the video enough
plug your phone (while it's off) to the wall
charger and while doing the wall trick !!Make
sure you hold down the Volume-Down Button!! so
you can boot into fastboot.
Step Three:
Once established fastboot, plug the phone
to your computer and let your computer discover the
device.
!!Make sure the device says Fastboot USB!!
Open Command Promt (CMD). If you already
know how to use Android ADB type these commands:
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
fastboot devices
!!Make Sure You Device ID Shows UP!!
fastboot erase userdata
fastboot flash system system.img
fastboot flash boot boot.img
fastboot reboot
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Let the phone run everything through and you should
be one Froyo.
Step Four:
Power down your phone
Reboot into Recovery (to see if your phone is still rooted)
If you are able to get into recovery flash any ROM
you like and Enjoy your UnBricked Nexus One

lilj4321 said:
If anyone needs the fix for this soft brick
let me know so i can post instructions!
Click to expand...
Click to collapse
You might as well write them out. You never know when someone will need them.

taodan said:
You might as well write them out. You never know when someone will need them.
Click to expand...
Click to collapse
+1. will be very useful n helpful when that occurs. so pls explain the method. thanx
Sent from my Nexus One using Tapatalk

n1newbie said:
+1. will be very useful n helpful when that occurs. so pls explain the method. thanx
Sent from my Nexus One using Tapatalk
Click to expand...
Click to collapse
+2, hope it won't occurs

hi lilj4321. thanx for the steps frnd
the youtube link that you provided returns 404 error. so you might use this link for video trick (by myself )
PS- sry if i am wrng. will the device boot into fastboot mode after the seven vibration brick happens
Sent from my Nexus One using Tapatalk

fixed the link!
no the phone will stay on the X screen until your battery dies
which is why you have to do the battery trick while holding the
volume-down button during the whole process.

lilj4321 said:
fixed the link!
no the phone will stay on the X screen until your battery dies
which is why you have to do the battery trick while holding the
volume-down button during the whole process.
Click to expand...
Click to collapse
oh okies. thanx for using my video buddy
will try this if seven vibration brick happens. but ill pray it shdnt happen
will be helpful for all if it is stickied :thumbup:
just my 2 cents ...
Sent from my Nexus One using Tapatalk

I hoped for something much more useful.
The method of reflashing to stock using fastboot commands has been posted on Nexus One Wiki for 2.5 years now.
And of course, it won't solve any overheating phone, and no "7-vibration brick".
Thanks for trying to help, but the post is kinda (very) useless.

Stuck in fastboot
My phone went into this rare phenomonen "7vibrations no boot"... its been 2weeks. Im not able to fix it till now.
Firstly , My phone doesnt respond in hboot screen when the sdcard is inserted. So for entering fastboot, I will take out sdcard and go to fastboot and then put my sdcard when the phone is connected to PC so that it doesnt turnoff when i pullout the battery. this i have been facing for quite long. cudnt fix it.
I tried exactly what you said.. but im stuck in the fastboot now.. im not able to flash anything using adb in fastboot.
im getting errors in fastboot.
when i typed 'fastboot flash system system.img"
it gives an error like "error: cannot load 'system.img' : unknown error"
did "fastboot erase" and it worked.
but flashing is not happening.
please help me out
---------- Post added at 08:22 PM ---------- Previous post was at 08:02 PM ----------
i somehow managed to flash all those things what u said in your post...
but still when rebooted after flashing via fastboot, the same 7 vibrations happening.
My phone doesnt boot..
i havent done the battery trick as you said. Im not able to do it. That video doesnt have any instruction and no audio too.
any instruction on how to do it will be helpful.

ajaymkd said:
My phone went into this rare phenomonen "7vibrations no boot"... its been 2weeks. Im not able to fix it till now.
Firstly , My phone doesnt respond in hboot screen when the sdcard is inserted. So for entering fastboot, I will take out sdcard and go to fastboot and then put my sdcard when the phone is connected to PC so that it doesnt turnoff when i pullout the battery. this i have been facing for quite long. cudnt fix it.
I tried exactly what you said.. but im stuck in the fastboot now.. im not able to flash anything using adb in fastboot.
im getting errors in fastboot.
when i typed 'fastboot flash system system.img"
it gives an error like "error: cannot load 'system.img' : unknown error"
did "fastboot erase" and it worked.
but flashing is not happening.
please help me out
---------- Post added at 08:22 PM ---------- Previous post was at 08:02 PM ----------
i somehow managed to flash all those things what u said in your post...
but still when rebooted after flashing via fastboot, the same 7 vibrations happening.
My phone doesnt boot..
i havent done the battery trick as you said. Im not able to do it. That video doesnt have any instruction and no audio too.
any instruction on how to do it will be helpful.
Click to expand...
Click to collapse
After doing all the stuffs, and after fastboot reboot.. The phone on the same state.. Brick state with 7 vibrate + X sign. Why is that so?

[Q] One is stuck in bootloader

I just got my HTC One less than a week ago, rooted and flashed my first ROM with no issues. Decided to try out a different one today, but after flashing it, my phone rebooted into bootloader and has been stuck there. Anytime I try to reboot the phone or reboot into recovery, it just goes back to the bootloader screen. Same thing when I attempt a factory reset. I've tried reinstalling TWRP recovery and although it says the install is successful, it's still stuck in bootloader. I also tried to install my previous ROM via fastboot command (which is failing), but to no avail. I got the following output:
sending 'zip' (994092 KB)...
OKAY [ 38.486s]
writing 'zip'...
(bootloader) zip header checking...
(bootloader) zip info parsing...
FAILED (remote: 24 parsing android-info fail)
finished. total time: 54.083s
I'm on the Sprint version, and I'm aware that 4.2 ROMs don't work on Sprint yet so I'd be using older versions of them for the time being, but I guess I inadvertently used an incorrect version.
Any ideas?

hmm...must really be bricked. :-\

if it is booting into bootloader, it is not bricked...
try connecting your USB cable , select fastboot in bootloader... it should show the FASTBOOT USB
now on your PC, where you have the ADB/Fasboot files, SHIFT+RIGHT CLICK on that folder and select Open command window here.
In command window, enter FASTBOOT ERASE CACHE
and try booting again...it might work.....

mathrania said:
if it is booting into bootloader, it is not bricked...
try connecting your USB cable , select fastboot in bootloader... it should show the FASTBOOT USB
now on your PC, where you have the ADB/Fasboot files, SHIFT+RIGHT CLICK on that folder and select Open command window here.
In command window, enter FASTBOOT ERASE CACHE
and try booting again...it might work.....
Click to expand...
Click to collapse
nope, no luck I also tried flashing recovery again in addition to it, still going straight to bootloader.

nsuviolin2005 said:
nope, no luck I also tried flashing recovery again in addition to it, still going straight to bootloader.
Click to expand...
Click to collapse
Try using the HTC one AIO toolkit to flash a new recovery and see if that helps.
It uses the FASTBOOT method to flash. Plus you have options to try CWM and TWRP.
If that works you should be able to flash a different rom to get your device up and running

gazlufc said:
Try using the HTC one AIO toolkit to flash a new recovery and see if that helps.
It uses the FASTBOOT method to flash. Plus you have options to try CWM and TWRP.
If that works you should be able to flash a different rom to get your device up and running
Click to expand...
Click to collapse
When I click to flash a recovery, it gives me a prompt that there will be 2 screens and to close the 1st one once I'm in bootloader...I do that, then the 2nd screen comes up but nothing happens. Same thing for both the Sprint options

You need to be in the fastboot menu not bootloader menu.
Sent from my HTC One using xda app-developers app

gazlufc said:
You need to be in the fastboot menu not bootloader menu.
Sent from my HTC One using xda app-developers app
Click to expand...
Click to collapse
I was...FASTBOOT USB mode, my phone is booting into that menu by default

nsuviolin2005 said:
I was...FASTBOOT USB mode, my phone is booting into that menu by default
Click to expand...
Click to collapse
hmmmmm thats strange.
What you could try is download one of the recoveries and unzip the file so you get the .img file of that recovery.
Then try to flash your own recovery option. see if that works

gazlufc said:
hmmmmm thats strange.
What you could try is download one of the recoveries and unzip the file so you get the .img file of that recovery.
Then try to flash your own recovery option. see if that works
Click to expand...
Click to collapse
Is this supposed to be automated or something? All I get with any option is an command line screen that's in the folder but nothing's happening.

nsuviolin2005 said:
Is this supposed to be automated or something? All I get with any option is an command line screen that's in the folder but nothing's happening.
Click to expand...
Click to collapse
could you post screenshots so I could see what happening?
---------- Post added at 07:46 PM ---------- Previous post was at 07:38 PM ----------
The only other thing I could think of is to try an RUU if all else fails but I can't guarantee that it will work
Sent from my HTC One using xda app-developers app

gazlufc said:
could you post screenshots so I could see what happening?
---------- Post added at 07:46 PM ---------- Previous post was at 07:38 PM ----------
The only other thing I could think of is to try an RUU if all else fails but I can't guarantee that it will work
Sent from my HTC One using xda app-developers app
Click to expand...
Click to collapse
Profit! Turns out the flash your own recovery option worked, I just didn't follow it all the way through, initially...after I closed the command prompt screen, the Open file menu came up and I was able to pick my TWRP recovery and boot into it. I restored my backup I made right before flashing the bad ROM and the phone is booting past the bootloader now
But.....next issue is that it's booting to a black screen instead of the regular lock screen, and after sitting there in that state for a few minutes, it reboots. :-\ I'm wondering if this is just because I deactivated the phone and switched back to my EVO LTE while trying to fix the One...that would be a first, though, as the phones are usually operational even if they don't have service.

nsuviolin2005 said:
Profit! Turns out the flash your own recovery option worked, I just didn't follow it all the way through, initially...after I closed the command prompt screen, the Open file menu came up and I was able to pick my TWRP recovery and boot into it. I restored my backup I made right before flashing the bad ROM and the phone is booting past the bootloader now
But.....next issue is that it's booting to a black screen instead of the regular lock screen, and after sitting there in that state for a few minutes, it reboots. :-\ I'm wondering if this is just because I deactivated the phone and switched back to my EVO LTE while trying to fix the One...that would be a first, though, as the phones are usually operational even if they don't have service.
Click to expand...
Click to collapse
Glad to hear the recovery worked. As for the phone staying on black. I would just advice to flash a nother rom if the problem still persists mate

gazlufc said:
Glad to hear the recovery worked. As for the phone staying on black. I would just advice to flash a nother rom if the problem still persists mate
Click to expand...
Click to collapse
Well, flashing and restoring didn't quite work, so I wound up having to do a factory reset (thankfully I had all my files on my PC from when I had to move them from my EVO, and since I'd only upgraded a few days ago, I didn't lose a whole lot) and a re-lock of the bootloader.
Only weird thing is, even re-locking it, the phone remained in S-OFF state. But I was able to rerun the HTC Dev Unlock to unlock the bootloader again and flashed a correct ROM. Back in business.
Thanks for your help...that toolkit you linked me to saved my ass.

No problem man glad I could help
Sent from my HTC One using xda app-developers app

nsuviolin2005 said:
Well, flashing and restoring didn't quite work, so I wound up having to do a factory reset (thankfully I had all my files on my PC from when I had to move them from my EVO, and since I'd only upgraded a few days ago, I didn't lose a whole lot) and a re-lock of the bootloader.
Only weird thing is, even re-locking it, the phone remained in S-OFF state. But I was able to rerun the HTC Dev Unlock to unlock the bootloader again and flashed a correct ROM. Back in business.
Thanks for your help...that toolkit you linked me to saved my ass.
Click to expand...
Click to collapse
\question i am having the same problem you have but i think its due to water damage i am going straight into the bootloader are sometime i can get it into safe mode

nsuviolin2005 said:
Well, flashing and restoring didn't quite work, so I wound up having to do a factory reset (thankfully I had all my files on my PC from when I had to move them from my EVO, and since I'd only upgraded a few days ago, I didn't lose a whole lot) and a re-lock of the bootloader.
Only weird thing is, even re-locking it, the phone remained in S-OFF state. But I was able to rerun the HTC Dev Unlock to unlock the bootloader again and flashed a correct ROM. Back in business.
Thanks for your help...that toolkit you linked me to saved my ass.
Click to expand...
Click to collapse
To be S-ON again you need to reboot into bootloader
Then FASTBOOT USB
then run fastboot and write "fastboot oem writesecureflag 3" and enter. Now you will be S-ON

But do NOT S-ON unless you absolutely need to.

[Q] Need to unlock bootloader, but borked device

Basically, I tried to flash the latest 5.1 image but unsuccessfully as the system.img wasn't extracted. For some reason I locked the bootloader and now I can't boot into a working system, and I can't reflash anything as the bootloader is locked. When attempting to unlock, it is telling me to go into dev settings to allow unlock.
Is there anything I can do?

Few threads about this today. Seems a regular user error. Can't think of a fix right now..

rootSU said:
Few threads about this today. Seems a regular user error. Can't think of a fix right now..
Click to expand...
Click to collapse
Hmm, thanks anyway. I think this means I'm bricked. Moto E time I think.

boot to bootloader, fastboot oem unlock from fastboot command console on computer.

TheAmazingDave said:
boot to bootloader, fastboot oem unlock from fastboot command console on computer.
Click to expand...
Click to collapse
Can't be done.

Have the same problem and try to solve it with Motorola. No luck at the moment.

lee.jarratt said:
Basically, I tried to flash the latest 5.1 image but unsuccessfully as the system.img wasn't extracted. For some reason I locked the bootloader and now I can't boot into a working system, and I can't reflash anything as the bootloader is locked. When attempting to unlock, it is telling me to go into dev settings to allow unlock.
Is there anything I can do?
Click to expand...
Click to collapse
try flashing the factory img via your bootloader/fastboot

simms22 said:
try flashing the factory img via your bootloader/fastboot
Click to expand...
Click to collapse
Can't. Boot loader is locked and requires a setting in android to be changed but android can't boot. Catch 22

rootSU said:
Can't. Boot loader is locked and requires a setting in android to be changed but android can't boot. Catch 22
Click to expand...
Click to collapse
Are you positive? I just flashed a Nexus 7 from 5.0.2 to 4.4.4 with fastboot. fastboot oem unlock worked without checking that box.

TheAmazingDave said:
Are you positive? I just flashed a Nexus 7 from 5.0.2 to 4.4.4 with fastboot. fastboot oem unlock worked without checking that box.
Click to expand...
Click to collapse
That's what all the threads about this today are saying... Including the op of this thread.

rootSU said:
That's what all the threads about this today are saying... Including the op of this thread.
Click to expand...
Click to collapse
Damn, that's really lame...

Wow this craps really ticking me off with this update and all. I have been rooting modding for years and every damn time I get a device that uses fastboot I get nothing but trouble. I hard bricked three devices in the past with fastboot and it seems over the years fastboot hasn't gotten any better or easier. What a shame I love the nexus 6 but I'm seriously starting to reconsider and going back to the good old Odin devices.

I'm an idiot.
I made the mistake of trying to update my Nexus 6 (Stock 5.0 encrypted, rooted, Xposed) while talking to AT&T customer service on my other phone. Distracted flashing is a bad idea. I am sure I made SEVERAL mistakes.
I too was trying to flash the new 5.1 image and got an error when running ./flash-all.sh (I'm on a Macbook). Friend suggested I try to do it by flashing the boot.img recovery.img and then system.img manually. Got the boot to flash. Recovery flashed. System failed. Unfortunately I have closed the terminal windows and don't have the errors anymore. When it failed it said something about insufficient space. So (I'm assuming this is where I f**ked up) I hit start from the boot loader screen to boot into the system and delete some things even though I had plenty of space (over 20gb). It booted fine. When I went to reboot into bootloader, I accidentally selected recovery. It booted back into TWRP which confused me. I thought best bet would be to wipe the device and start over fresh. I wiped everything and booted back into bootloader... blackness. Now I have no response from the device at all. Nothing. No response from the power button. Nothing when I plug to a charger. Just blackness. Just a pretty, 2 day old Nexus 6 (warranty replacement from T-Mobile on Tuesday).

You wiped the boot partition too? Ouch...
Last time I did that, it was with my Nook Color. Thankfully that was able to boot from SD cards...
I have a similar problem with another Nexus 7 right now. Flash went corrupt, won't boot at all. No bootloader, no Google logo, nothing.
My only hope is that the device still talks to the computer, it shows up as a Qualcomm device under Ports in Windows Dev Manager. QPST picks it up and says it's in download mode. If I can source the hex files to flash, I think I can bring it back. I'm only sharing that because it might be your only hope too. Godspeed, sir.

beachbum40 said:
Wow this craps really ticking me off with this update and all. I have been rooting modding for years and every damn time I get a device that uses fastboot I get nothing but trouble. I hard bricked three devices in the past with fastboot and it seems over the years fastboot hasn't gotten any better or easier. What a shame I love the nexus 6 but I'm seriously starting to reconsider and going back to the good old Odin devices.
Click to expand...
Click to collapse
lol, whats so hard with fastboot? fastboot oem unlock is rocket science? how about fastboot flash recovery recname.img? only way to hardbrick with fastboot is to flaah something to your device that doesnt belong there, or flash something into the wrong partition. how did you "hard brick" with fastboot???

simms22 said:
lol, whats so hard with fastboot? fastboot oem unlock is rocket science? how about fastboot flash recovery recname.img? only way to hardbrick with fastboot is to flaah something to your device that doesnt belong there, or flash something into the wrong partition. how did you "hard brick" with fastboot???
Click to expand...
Click to collapse
The problem is that bootloader got relocked, and the OP is unable to get to the setting to enable oem unlock. Fastboot is errors out saying to Check "Allow OEM unlock", and FAILED (remote failure).

I would find it hard to believe that there is no solution to this. With all the bright minds here on XDA, I'm sure it can be figured out. The unlock setting must be stored somewhere, and it should be accessible.
When I first got my Nexus 6, I booted into the bootloader right after taking it out of the box (i.e., without booting into Android), and I was able to unlock the bootloader without having checked "Allow OEM unlock" in developer options. This could mean that the setting could potentially be located in /data somewhere.
OP, have you tried a factory reset in recovery? Have you tried playing around with the other bootloader menu items (e.g., "Factory", etc.)?

efrant said:
I would find it hard to believe that there is no solution to this. With all the bright minds here on XDA, I'm sure it can be figured out. The unlock setting must be stored somewhere, and it should be accessible.
When I first got my Nexus 6, I booted into the bootloader right after taking it out of the box (i.e., without booting into Android), and I was able to unlock the bootloader without having checked "Allow OEM unlock" in developer options. This could mean that the setting could potentially be located in /data somewhere.
OP, have you tried a factory reset in recovery? Have you tried playing around with the other bootloader menu items (e.g., "Factory", etc.)?
Click to expand...
Click to collapse
Thank you for taking a look at my post. I have tried all the options in the bootloader menu with no dice. Things aren't looking promising for me...

You're all using the newest fastboot?

flash the factory img
edit.. nevermind, i see ive already said that

Nexus 6 bricked and locked bootloader!?!?!?

Hi
I was side loading the new 5.1 to both my N5 and N6. N5 was ALL GOOD. N6 however is not. After waiting for a rediculous time for it to reboot when it was stuck on the white Google Image, I disconnected the USB cable. Now it won't boot past the Google screen at all.
I can see it as a fastboot device and can boot into bootloader. There appears to be no recovery. When I try to re flash or side load, I get the warning along the lines of 'unlock before flash'.
So........can anyone assist please?
Thanks in advance of responses.
Cheers
Thommo

Look here..
http://forum.xda-developers.com/nexus-6/general/fix-fix-qhusbbulk-cm12-t3059518
That might help, otherwise since you can get into BL mode can you try flashing stock recovery from the image you originally had? I guess I don't know if that works or not or if that is what you were trying to reflash..
fastboot command to flash recovery is
fastboot flash recovery recovery.img <--replace recovery.img with the name of the recovery you are trying to flash. It's most likely recovery.img if you are taking it from a stock image.
Good luck.

Ha66is said:
Hi
I was side loading the new 5.1 to both my N5 and N6. N5 was ALL GOOD. N6 however is not. After waiting for a rediculous time for it to reboot when it was stuck on the white Google Image, I disconnected the USB cable. Now it won't boot past the Google screen at all.
I can see it as a fastboot device and can boot into bootloader. There appears to be no recovery. When I try to re flash or side load, I get the warning along the lines of 'unlock before flash'.
So........can anyone assist please?
Thanks in advance of responses.
Cheers
Thommo
Click to expand...
Click to collapse
did you solve? how you solved?
i have a similary problem with my nexus 9.. locked bootloader and can't do anythings.. please help me

we need help
paviz96 said:
did you solve? how you solved?
i have a similary problem with my nexus 9.. locked bootloader and can't do anythings.. please help me
Click to expand...
Click to collapse
i have the same prob bro i am waiting for a fix i still have hope

So the lesson learned is: Always unlocking the bootloader once you have the phone/tablet should be the first thing to do so you can fix issues !

I also need someone to find a way to unlock the bootloader ! btw try booting into recovery (it will say no command) and then hold the volume up and power for 10 seconds and then let go, then select adb sideload ...let it time out...then try to clear data and cache. I tried to clear that when i had a bootloop but wouldnt work, i got it to work by selecting adb sideload and then letting it time out(takes a while to timeout)..must mount the partitions...

jordy787 said:
I also need someone to find a way to unlock the bootloader ! btw try booting into recovery (it will say no command) and then hold the volume up and power for 10 seconds and then let go, then select adb sideload ...let it time out...then try to clear data and cache. I tried to clear that when i had a bootloop but wouldnt work, i got it to work by selecting adb sideload and then letting it time out(takes a while to timeout)..must mount the partitions...
Click to expand...
Click to collapse
If you do not have TWRP recovery, there's nothing you can do. RMA.

Evolution_Tech said:
If you do not have TWRP recovery, there's nothing you can do. RMA.
Click to expand...
Click to collapse
think i can rma with a cracked glass but still works?

jordy787 said:
think i can rma with a cracked glass but still works?
Click to expand...
Click to collapse
Doubt it. There are some GooglePlay versions that have been RMA'd as it was a promo. Still gonna go back to original Account for the RMA.

stupid question . if this is Motorola you cant use RSD this with the correct FXZ. or they no longer use this since its a nexus.

Urgent advice needed on Razr i XT890

hi, my phone Razr i XT890 is showing the Red Moto Logo, I tried to factory reset by going into fastboot also but nothing happened, I can find many thread here about the same problem but nothing conclusive could be found in those threads, hence I sent my phone for repairs, the technician hooked it up to a computer and said that most likely it is a software issue and the phone would be ok, after waiting for an hour I was told that the emmc has died and it cannot be replaced and the only solution would be to change the motherboard, since the mother board is not avaible in the market I looked it up on aliexpress and it costs around 70$ where as a new/refurbished phones are listed for 75$, need you guys advice on whether it can be repaired or not and if yes then how. I am a regular user and not an expert like you guys so if you suggest any thing plz do it in detail. FYI its a factory unlocked phone which had jelly bean OS and I never rooted it or did any hanky panky to it. Thanks

What u could try to test if the mechanic is right (I suppose he is), is to flash stock firmware by hand and see what the device gives for error.
If the error is an i/o error the emmc is corrupted and we can't help that. It will need a replacement of the motherboard.
To test it, extract all images from the stock firmware. Then flash them while your Phone is in fastboot modes and connected to your pc, like this:
Use a compatible fastboot executable like mfastboot.
- fastboot flash boot boot_signed
- fastboot flash recovery recovery_signed
- fastboot flash system system_signed
- fastboot erase cache
- fastboot erase userdata
Every one of them should return an "OK". If there is an error in one of them that partition is most likely damaged and if u can't boot in recovery there is most likely no turning back.

Hazou said:
What u could try to test if the mechanic is right (I suppose he is), is to flash stock firmware by hand and see what the device gives for error.
If the error is an i/o error the emmc is corrupted and we can't help that. It will need a replacement of the motherboard.
To test it, extract all images from the stock firmware. Then flash them while your Phone is in fastboot modes and connected to your pc, like this:
Use a compatible fastboot executable like mfastboot.
- fastboot flash boot boot_signed
- fastboot flash recovery recovery_signed
- fastboot flash system system_signed
- fastboot erase cache
- fastboot erase userdata
Every one of them should return an "OK". If there is an error in one of them that partition is most likely damaged and if u can't boot in recovery there is most likely no turning back.
Click to expand...
Click to collapse
ok, thanks for the suggestion and say if they all come ok then?? and If an error comes in one of them then what ?? I will only be able to post in detail tomorrow after I have visited the mechanic.

cooljatt18 said:
ok, thanks for the suggestion and say if they all come ok then?? and If an error comes in one of them then what ?? I will only be able to post in detail tomorrow after I have visited the mechanic.
Click to expand...
Click to collapse
If it all says OK, u should have a working device. No doubt about that. But if one of them doesn't we found the issue. Most likely i/o. Can u still boot to recovery? Or is that even impossible, because u said u tried a factory reset?

Hazou said:
If it all says OK, u should have a working device. No doubt about that. But if one of them doesn't we found the issue. Most likely i/o. Can u still boot to recovery? Or is that even impossible, because u said u tried a factory reset?
Click to expand...
Click to collapse
I tried factory reset and the same screen appeared, then I tried recovery option in fastboot menu rather then factory reset the android robot with exclamation mark appeared when I pressed volume key I got some options partition cache etc I did that and also there was an option erase all data did that to got message both times that it has been done, then I chose the option of restart and again got the red logo screen !

cooljatt18 said:
I tried factory reset and the same screen appeared, then I tried recovery option in fastboot menu rather then factory reset the android robot with exclamation mark appeared when I pressed volume key I got some options partition cache etc I did that and also there was an option erase all data did that to got message both times that it has been done, then I chose the option of restart and again got the red logo screen !
Click to expand...
Click to collapse
This is most likely solvable. Try that flash methods a few post above and see what happens s

Hazou said:
This is most likely solvable. Try that flash methods a few post above and see what happens s
Click to expand...
Click to collapse
so I went to the mechanic today and told him to flash with stock firmware and he told be that he did not have it !! Since the phone was never officially launched in my region I am guessing hardly any mechanic would have it, is there any place from where I can download it

cooljatt18 said:
so I went to the mechanic today and told him to flash with stock firmware and he told be that he did not have it !! Since the phone was never officially launched in my region I am guessing hardly any mechanic would have it, is there any place from where I can download it
Click to expand...
Click to collapse
Which country and carrier is it from? That way I can post the link to the correct firmware file for your phone.
Sent from my XT1095 using Tapatalk

AGISCI said:
Which country and carrier is it from? That way I can post the link to the correct firmware file for your phone.
Sent from my XT1095 using Tapatalk
Click to expand...
Click to collapse
It is an unlocked phone, not linked to any carrier I am not 100% sure but most likely England/Great Britain, I remember the Reading GB as in short for Great Britain in the firmware name once !

cooljatt18 said:
It is an unlocked phone, not linked to any carrier I am not 100% sure but most likely England/Great Britain, I remember the Reading GB as in short for Great Britain in the firmware name once !
Click to expand...
Click to collapse
http://www.filefactory.com/file/6b396l5ar4tf/CFC_9.8.2I-50_SMI-26_S7_USASMIJBORAGB.xml.zip
Sent from my XT1095 using Tapatalk

AGISCI said:
http://www.filefactory.com/file/6b396l5ar4tf/CFC_9.8.2I-50_SMI-26_S7_USASMIJBORAGB.xml.zip
Sent from my XT1095 using Tapatalk
Click to expand...
Click to collapse
thanks a ton!!!

hi, guys sorry for posting so late, was super busy, any how haven't got a mechanic to flash the phone, guess I will have to do it myself, request you to answer my queries
.1) a mechanic to whom I went convinced me to believe that the problem was due to a faulty battery and he could fix it in 5 mins flat, He opened the phone did some tinkering with it, I am not sure what but the phone was in same condition ie Red logo on booting. Was very disappointed came back home and I tried to restore it through fast boot and I noticed that the Battery Current was coming as 4.1 V earlier it was 3.7 !!! I am sure that the mechanic messed it up. Now my question is will it harm the phone, battery or any other part?? Should I just leave it the way it is ie 4.1V and not try to rectify it to bring it to 3.7V.
.2) I am not able to get a mechanic who can flash the phone as suggested in previous posts, pl tell how I can do it myself, I am a newbie at this and have zero knowledge of the process, pl tell what all software are needed! And hardware if any. All I have got currently is the firmware posted in previous posts.
Thanks