Related
I tried to unroot my phone via OCLF from the market. It went dark, then got the normal Vibrant screen, the the Galaxy S screen, then it went dark again. Now, it just sits. Black screen. All the buttons at the bottom are lit up. :-/
Anyone?
Silly question, I know. But did you have a nandroid backup, by any chance?
This is probably a last resort, but try boot into recovery and wipe everything. This fix the problem for me, the downside is you lose all you data.
Sent from my SGH-T959 using XDA App
If you are anything like me, recovery didn't work and using Odin and reflashing Stock with repartition didn't work either.
You'll need to use odin to flash Eugenes "Vibrant that doesn't brick" (NO REPARTITION), then use odin again to flash Stock (check repartition this time) and you'll be good to go.
You can try to flash the froyo rom with odin...... I had that same exact problem and this is what fixed it for me. Once froyo us flashed then you can flash whatever rom you want. Hth
Ok, I probably should have stated that I'm a complete newby and have no idea what I'm doing. I believe I do have nandroid, but other than that you all are speaking French to me.
Right now I'm in the recover mode (I think). It's hooked up to my computer and I'm in the "Downloading... Do not turn off target!!" mode. This is where I'm stuck...I have no idea where to go from here.
Please talk to me like I'm a 5 year old, because as far as this is concerned, I am!
Oh, and thank you so much for any help you can give me!
hospo said:
Ok, I probably should have stated that I'm a complete newby and have no idea what I'm doing. I believe I do have nandroid, but other than that you all are speaking French to me.
Right now I'm in the recover mode (I think). It's hooked up to my computer and I'm in the "Downloading... Do not turn off target!!" mode. This is where I'm stuck...I have no idea where to go from here.
Please talk to me like I'm a 5 year old, because as far as this is concerned, I am!
Oh, and thank you so much for any help you can give me!
Click to expand...
Click to collapse
Well, good news is... you didn't brick your phone, this is recoverable. Best idea would be to search the forums on how to ODIN back to Stock. Theres plenty of posts on how to do it. You should also be able to find this in the tips & tricks threads. Good Luck.
Thank you all for your help! I recovered it!! Seems as though I was just going about it the wrong way!! I got into the actual recovery mode and cleared it all out. Now it's as good as new!
Again, appreciate your help and patience with what I'm sure is the 120,000th post on this subject. ;-)
Kienz said:
Silly question, I know. But did you have a nandroid backup, by any chance?
Click to expand...
Click to collapse
Is it even possible to make a nandroid backup before rooting?
hospo said:
Thank you all for your help! I recovered it!! Seems as though I was just going about it the wrong way!! I got into the actual recovery mode and cleared it all out. Now it's as good as new!
Again, appreciate your help and patience with what I'm sure is the 120,000th post on this subject. ;-)
Click to expand...
Click to collapse
Hey - what does you doing? Please told me, I've the same problem:
If I start the phone with an USB cable and the battery symbol with the running point under this, the PC recognize that something is connected, but Windows found no driver....
How could you could flash the Stackfirmware back, if the recovery and download menu does not work ?
PLS help !!!
Check out this thread http://forum.xda-developers.com/newreply.php?do=newreply&p=8129898
Go to the section where it says "Did You Flash Something Before Disabling Voodoo? 2 Fixes to Help You Out."
And do fix #1 it is pretty easy and it wont take you more than 20 minutes.
Let us know if that works
And do fix #1 it is pretty easy and it wont take you more than 20 minutes.
Let us know if that works
Click to expand...
Click to collapse
If I following the link and the next one, I can read:
Caution!!! You Must be on STOCK Vibrant Rom & NEVER Have Already Flashed the JP3 Froyo Image
Click to expand...
Click to collapse
It isn't -> it's a Firmware for the normal Galaxy (3key)[I'm a idiot]
First,
You must already Have Odin installed & Know how to boot into Down-loader Mode!!
Click to expand...
Click to collapse
Thats also the problem as described in front : I have had no chance to received the DL Mode.. maybe I make something wrong? The phone is booting up till the "S" is there, after that, the screen is black, keys are lightning...
The recovery 3button are blocked from the beginning; the DL Menu - I did not have reached it successfully
The PC recognize, that is something on USB, but not what ... so Odin did not see the Mobile, too.
This Thread Is For Them Who Bricked There Phones
Don't start a new thread for your bricked phone & post here.
We will help you with every possible solutions.
Here are some quick tips :
(Here I'll use the terms like Download-Mode & Recovery-Mode, If you dont know what are they please click here. There "BOOT to RECOVERY" & "BOOT to BOOTLOADER" means how to enter into Recovery-Mode & Download-Mode respectively.)
A Bricked Phone May Have One or More (Below Problems) :
1. Booting to the ROM(Android) not possible.
2. Booting to the Recovery-Mode not possible.
3. Black screen or Bootloop(Repeated Restarting of Phone at Boot Animation or Samsung Galaxy Y Logo).
Possible Solutions :
(Remember there'll be data loss using these solutions so always try to keep a backup)
1. If you can still enter into Recovery-Mode
(a). Try to clear Data & Cache then check.
(b). Try Installing a Custom ROM using CWM(ClockWorkMod Recovery) & check.
(For Custom ROM & CWM Visit here.)
2. If Recovery-Mode didn't helped Enter into Download-Mode & flash an odin supported stock rom(using ODIN 1.84 or 1.85) from Doky73's Thread(Flashing Guide in 2nd post).
*You can inform me, if anything left out.
Note :
1. I'll be not held responsible for anything that happens to your phone.
2. Before posting try to search for similar type problems out there & try the solution, if that doesn't solve your problem then post here.
Make this a sticky.. there are many users who say that their phone is bricked
help! bricked SGY
galaxy y bricked
i bricked my sgy last 3 weeks.
here's what i did.
-installed creedsix rom.
-installed UOT kitchen Themes.
-wipe data
problem
-stuck in bootlogo
-softbricked.
-cant go to recovery mode
-flashed too many times, still stuck in bootloop
i flashed at least 20 times, with different firmwares.
but still no luck, still boot lop.
my professor said something about secondary bootloader that might help. but i had definitely no idea what it is.
i asked some techies on the mall, and they said that this phone must undergo the JTAG process. but it cost $20.
help me. thanks.
jmpotter said:
galaxy y bricked
i bricked my sgy last 3 weeks.
here's what i did.
-installed creedsix rom.
-installed UOT kitchen Themes.
-wipe data
problem
-stuck in bootlogo
-softbricked.
-cant go to recovery mode
-flashed too many times, still stuck in bootloop
i flashed at least 20 times, with different firmwares.
but still no luck, still boot lop.
my professor said something about secondary bootloader that might help. but i had definitely no idea what it is.
i asked some techies on the mall, and they said that this phone must undergo the JTAG process. but it cost $20.
help me. thanks.
Click to expand...
Click to collapse
can you go to download mode??
(try pressing volume down+ home button + power button all at the same time)
if it still can, then your SGY is still good
go to this ---> thread
and just flash your country's firmware
From where you got the firmwares.... How you flashed...
Ever tried re partitioning.... Ever flashed boot loader....
For info... Jtag or boundary-scan is used for testing & servicing high technology electronic boards...
Sent from my GT-S5360 using Tapatalk 2
Millan.SIS said:
From where you got the firmwares.... How you flashed...
Ever tried re partitioning.... Ever flashed boot loader....
For info... Jtag or boundary-scan is used for testing & servicing high technology electronic boards...
Sent from my GT-S5360 using Tapatalk 2
Click to expand...
Click to collapse
just for info, jtag will not fix the problem. IT IS SCANNING.. like trouble shooting.
that only means that those technicians are pretending to be well educated but the truth is that they only wanted to get some cash out of your pocket.
static28 said:
just for info, jtag will not fix the problem. IT IS SCANNING.. like trouble shooting.
that only means that those technicians are pretending to be well educated but the truth is that they only wanted to get some cash out of your pocket.
Click to expand...
Click to collapse
ya, that's what those wannabees really do..
Sent from my GT-S5360 using Tapatalk 2
this one will a little bit off topic...what is creedsix?is it a rom for SGY?
if the phone still can boot that means everything is fine. pull out the battery, wait 10 seconds, reinsert the battery, do three magic combo button, you'll enter recovery mode. don't worry about our bootloader. our bootloader is stored in different partition thus installing any custom rom won't affect our bootloader. as far as i know, there is only one person who have messed up with bootloader and got an ultimate hard brick.
kurotsugi said:
this one will a little bit off topic...what is creedsix?is it a rom for SGY?
if the phone still can boot that means everything is fine. pull out the battery, wait 10 seconds, reinsert the battery, do three magic combo button, you'll enter recovery mode. don't worry about our bootloader. our bootloader is stored in different partition thus installing any custom rom won't affect our bootloader. as far as i know, there is only one person who have messed up with bootloader and got an ultimate hard brick.
Click to expand...
Click to collapse
Really its great thread ........ Many many thanks for helping ppl ......
is it possible repair hard brick ..... what is hard brick... if device hard brick device gos life time dead ??
Sent from my GT-S6102 using xda premium
a hard brick is when our device doesn't respond to power button.
the guy that I've mentioned above is doky73. he accidentally flash a bootloader for sgs2 into his sgy. last time he said that he send his sgy to samsung service center and buy a new one. I'm not sure if samsung has revived his sgy.
edit: I didn't to offend him but I think I've mispelled doky's username. edited.
manoranjan2050 said:
Really its great thread ........ Many many thanks for helping ppl ......
is it possible repair hard brick ..... what is hard brick... if device hard brick device gos life time dead ??
Sent from my GT-S6102 using xda premium
Click to expand...
Click to collapse
whatever It may be... You should never mess up with bootloaders, if you don't actually know what's there significance...
Brief description on android starting process :
pbl(primary boot loader "boot.bin") executes first and then it executes sbl ...
Sbl(secondary boot loader "sbl.bin") is responsible for responding to combos...download mode.. Intercepting odin commands..... booting system...booting kernel.... Charging your battery while switch off... Etc etc
Harm anyone of them... And Your phone goes into lifetime hibernation, Hard-bricked.
Sent from my GT-S5360 using Tapatalk 2
thanks for the big info friend...... so hard bricl is mot repairble ......
Sent from my GT-S6102 using xda premium
my device might be bricked, can you please help me out
Hi to all, it's only my second post but i have a major problem with my samsung s-5360. it's won't boot anymore, but it can enter cmw and recovery. This is what i did wrong i believe. At first i installed morocs 1.8 kernel on creed fusion version 3.1 and it wouldn't boot anymore, so i ended up using a back-up i made before with cmw. And it worked well and phone was booting again and was on stock again. ( because back-up was made with stock-version obviously )
Then i thought: well let's try repensis noob version. And installed it and there was also an update 2 and installed it over it as well before booting the os, maybe this is what i did wrong dunno .. But afterwards it didn't boot anymore and whatever i tried, restoring one of the 3 images i made, or using one of the roms posted here like Creed fusion 3.1 rom or Aurora 2 nor Chobits didn't work.
I also tried reverting to stock with odin 1.85 but when i connected my phone via usb to the pc, odin didn't see my phone. ( after selecting the 3 tar files in odin ) Maybe i'm doing wrong something there.
What i also have to add is that when doing factory wipe in recovery it says formatted E: but unable to format E:\dev10 and dev11. clearing cache is no problem and also cleared dalvik cache. Can you please help me out ? I know, it sounds very noobish but well, i have to face it because can't do it myself without help anymore it seems ... Thanx a lot in advance.
please make sure that you've installed the driver and plug the usb to computer only on download mode when flash with odin. dev10 and dev11 are the partition for data and cache. that error means something was wrong with your recovery mode. you'll need to install a fresh stock rom with odin.
kurotsugi said:
please make sure that you've installed the driver and plug the usb to computer only on download mode when flash with odin. dev10 and dev11 are the partition for data and cache. that error means something was wrong with your recovery mode. you'll need to install a fresh stock rom with odin.
Click to expand...
Click to collapse
Thanx a lot for responding ! I only used kies for connecting my phone because i couldn't find a driver for it, and had to disconnect it, but i will search for it again now and hopefully it will work now. i have to go now and return back in three hours. i'm very curious ! i'll come back in a couple of hours and gonna tell if it worked out of course
kurotsugi said:
a hard brick is when our device doesn't respond to power button.
the guy that I've mentioned above is doky77. he accidentally flash a bootloader for sgs2 into his sgy. last time he said that he send his sgy to samsung service center and buy a new one. I'm not sure if samsung has revived his sgy.
Click to expand...
Click to collapse
to be precise: the guy was Doky73...
I was playing with different revisions of SBLs because on SGS2 some old SBL gives the possibility to reset custom bin counter via JIG. At a given point accidentally browsed SGS2 bootloader instead of SGY one...
But I did perfect job, the service center wasn't able to detect the cause of bricking, but they recovered my phone under warranty. (I think they're not reading this forum )
Doky73 said:
to be precise: the guy was Doky73...
I was playing with different revisions of SBLs because on SGS2 some old SBL gives the possibility to reset custom bin counter via JIG. At a given point accidentally browsed SGS2 bootloader instead of SGY one...
But I did perfect job, the service center wasn't able to detect the cause of bricking, but they recovered my phone under warranty. (I think they're not reading this forum )
Click to expand...
Click to collapse
Thanks friend.............
if i install some custom rom custom kernel via odin or CWN its gos to hard brick ???
in odin re-partition option for why ............ its disbl by default if i enable it wats problem........
dear friend if u have any odin full tutorial /guide /ref please provide me for learn syep by step one by one option or problem......
ops...my mistake. I guess I'm too sleepy when was typing your name. I'll edit it. sorry.
manoranjan2050 said:
Thanks friend.............
if i install some custom rom custom kernel via odin or CWN its gos to hard brick ???
in odin re-partition option for why ............ its disbl by default if i enable it wats problem........
dear friend if u have any odin full tutorial /guide /ref please provide me for learn syep by step one by one option or problem......
Click to expand...
Click to collapse
if u flash something through odin or cwm then you wouldnt hard brick ur phone.. it would be just a temporary brick which can be easily revived... i dont know abt that partioning thing
Sent from my GT-S5360 using XDA
kurotsugi said:
please make sure that you've installed the driver and plug the usb to computer only on download mode when flash with odin. dev10 and dev11 are the partition for data and cache. that error means something was wrong with your recovery mode. you'll need to install a fresh stock rom with odin.
Click to expand...
Click to collapse
Hi, there i am and sry for disturbing you again or someone else but i managed to install a non kies usb driver and i'm flashing thru odin 1.85 right now but i'm stuck at BcmCP.img for over an hour . Is it because i forgot to remove the sd card ? I only removed the sim and is it safe to stop the process and start over again or should i wait ?
---------- Post added at 02:35 AM ---------- Previous post was at 01:47 AM ----------
mickeyindahouse said:
Hi, there i am and sry for disturbing you again or someone else but i managed to install a non kies usb driver and i'm flashing thru odin 1.85 right now but i'm stuck at BcmCP.img for over an hour . Is it because i forgot to remove the sd card ? I only removed the sim and is it safe to stop the process and start over again or should i wait ?
Click to expand...
Click to collapse
Well after trying this proces for the 5th time i finally managed to go to stock rom and it only lasted a couple of minutes Of course thanx to doky73 who made all this possible ! So i unbricked it for the second time i guess
Hey I'm from india and own an i9500
bought 5 months ago
I was using my phone normally and flashed a stock rom with ODIb
the phone booted up.
The problem is that I have emergency calls only and my IMEI has been changed to Fake IMEI
1) my phone is out of warranty as some moisture traces have gone into iy and samsung asks for 200$ for every small problem they need to change the board
2) I don't think so I have the EFS backup
Please Oh please someone guide me what to do?
usama492 said:
Hey I'm from india and own an i9500
bought 5 months ago
I was using my phone normally and flashed a stock rom with ODIb
the phone booted up.
The problem is that I have emergency calls only and my IMEI has been changed to Fake IMEI
1) my phone is out of warranty as some moisture traces have gone into iy and samsung asks for 200$ for every small problem they need to change the board
2) I don't think so I have the EFS backup
Please Oh please someone guide me what to do?
Click to expand...
Click to collapse
There's a thread on that here. You could try that, but I think that without a backup, it's going to be pretty hard to get it back up. First thing I do when I get a new phone is to backup the EFS.
http://forum.xda-developers.com/showthread.php?t=2346136
no help man.
any other help please anyone?
Flashing a different stock rom did not help?
usama492 said:
no help man.
any other help please anyone?
Click to expand...
Click to collapse
Did you actually tried to flash your original Stock ROM with Odin? If not, try other stock ROMs.
There's another ref link here: http://forum.xda-developers.com/showthread.php?t=2393289
I recommend you read through that thoroughly.
Cloxed said:
Did you actually tried to flash your original Stock ROM with Odin? If not, try other stock ROMs.
There's another ref link here: http://forum.xda-developers.com/showthread.php?t=2393289
I recommend you read through that thoroughly.
Click to expand...
Click to collapse
Yes I did flash the stock rom with ODIN which I successively used before
I read it but this is actually getting impossible for me.
After the phone shows generic IMEI.
will backing up the efs help now?
Also I flashed CM 10.
that also didn't give me back my IMEI.
really appreciate your help
and would be really grateful if someone guides me through this catastrophe.
Also I forgot to mention that I update to stock MJ5 4.3
I read that it changes the directory of efs?
Please someone help me!
usama492 said:
Also I forgot to mention that I update to stock MJ5 4.3
I read that it changes the directory of efs?
Please someone help me!
Click to expand...
Click to collapse
Since you updated to mj5 you'll have to use that firmware version in odin.
maybe
Maybe you could wipe Dalvik and cache memory, then do a factory reset through the recovery menu. This will reset everything of your phone, so your IMEI should go back to it's real number(you'll lose all your data so make a backup before doing it).
Have you also tested if it's not the SIM that doesn't work by putting it into another cell-phone?
Eastkap said:
Maybe you could wipe Dalvik and cache memory, then do a factory reset through the recovery menu. This will reset everything of your phone, so your IMEI should go back to it's real number(you'll lose all your data so make a backup before doing it).
Have you also tested if it's not the SIM that doesn't work by putting it into another cell-phone?
Click to expand...
Click to collapse
Sim isn't the problem.
Also wipin dalvik Cache might now fix the problem. But I will try it
thanks
any more suggestion?
A factory reset/wipe Dalvik ain't magically fixing this. If you've gone back to stock (a rom released by your carrier) & your IMEI hasn't returned & you have no backup, you're boned. Service centre (more expensive option), or ask around local mobile repair shops; they might be able to help more cheaply.
I bought Nexus 4 from Ebay (this is the item number 271321747280,please check it) its 16gb but all i could see is 8gb, someone said the seller messed the phone up,so he suggested i should First flash the stock recovery,then wipe cache and wipe data factory reset,please will this fix the issue, please if yes how do i do this,please explain in details,am new to this... or give me link that will help me... the seller stated this "Used, but in great condition. Kept in case. Owned for less than a year; first owner. Bootloader unlocked. Running stock Android 4.3 with custom recovery." your help will be Really appreciated , thanks in advance!!!
boinero1 said:
I bought Nexus 4 from Ebay (this is the item number 271321747280,please check it) its 16gb but all i could see is 8gb, someone said the seller messed the phone up,so he suggested i should First flash the stock recovery,then wipe cache and wipe data factory reset,please will this fix the issue, please if yes how do i do this,please explain in details,am new to this... or give me link that will help me... the seller stated this "Used, but in great condition. Kept in case. Owned for less than a year; first owner. Bootloader unlocked. Running stock Android 4.3 with custom recovery." your help will be Really appreciated , thanks in advance!!!
Click to expand...
Click to collapse
[HOW-TO] How to flash a factory image / return to stock / unlock / root #
It includes steps to fix the half storage issue.
If you want to check immediately before doing the above walkthrough, power off your phone completely, hold the volume down button and power on your phone to get into the bootloader. At the bottom of the screen, next to"Variant", you should see either "mako 8GB" or "mako 16GB". That tells you the storage size in the phone. In your case, it should say "mako 16GB."
Spasticdroid said:
[HOW-TO] How to flash a factory image / return to stock / unlock / root #
It includes steps to fix the half storage issue.
If you want to check immediately before doing the above walkthrough, power off your phone completely, hold the volume down button and power on your phone to get into the bootloader. At the bottom of the screen, next to"Variant", you should see either "mako 8GB" or "mako 16GB". That tells you the storage size in the phone. In your case, it should say "mako 16GB."
Click to expand...
Click to collapse
i did it n luckily is mako 16gb,, please what next?
boinero1 said:
i did it n luckily is mako 16gb,, please what next?
Click to expand...
Click to collapse
Since you're new to the phone, I highly recommend reading that thread I posted a link to earlier to set everything up on your computer and phone, which also includes how to fix the wrong storage size issue.
Spasticdroid said:
Since you're new to the phone, I highly recommend reading that thread I posted a link to earlier to set everything up on your computer and phone, which also includes how to fix the wrong storage size issue.
Click to expand...
Click to collapse
the steps are too hard, can't even download any software, pls any shortcut???
boinero1 said:
the steps are too hard, can't even download any software, pls any shortcut???
Click to expand...
Click to collapse
You could try using wugfresh's toolkit to install the factory rom.
That's about as simple as it gets.
If you can't do it using the toolkit, then bring it to someone/some place that can flash it for you.
I would do it if I lived near you. The hardest part is the computer setup, imo, just getting the proper drivers installed but even that is fairly easy to do using the toolkit.
Good luck.
Can you just return to ebay seller? It's not as described and you paid for 16gb without this additional work. Possibly it's a listing error and actually is a 8gb?
Sent from my iPhone using Tapatalk
boinero1 said:
i did it n luckily is mako 16gb,, please what next?
Click to expand...
Click to collapse
mowgie said:
Can you just return to ebay seller? It's not as described and you paid for 16gb without this additional work. Possibly it's a listing error and actually is a 8gb?
Sent from my iPhone using Tapatalk
Click to expand...
Click to collapse
It is a 16GB apparently, just the OS needs to be reflashed to fix the misreported space.
just clear the damn cache on stock recovery.
goofball2k said:
It is a 16GB apparently, just the OS needs to be reflashed to fix the misreported space.
Click to expand...
Click to collapse
pls how do i go about this, i boot to recovery n mistakenly flashed SYSTEM n now am stocked with Google each i switch on my device...
besides am downloading this Factory images "occam" for Nexus 4.. will it fix this??? thanks
goofball2k said:
It is a 16GB apparently, just the OS needs to be reflashed to fix the misreported space.
Click to expand...
Click to collapse
pls how do i reflash becos i already flash it, my device is currently empty ,, thanks
boinero1 said:
pls how do i go about this, i boot to recovery n mistakenly flashed SYSTEM n now am stocked with Google each i switch on my device...
besides am downloading this Factory images "occam" for Nexus 4.. will it fix this??? thanks
Click to expand...
Click to collapse
Factory image will fix it assuming you can flash it. The toolkit can do it or you can use fastboot commands. Whatever you prefer
hi
i just flash the Android N Preview it worked normaly then i flash TWRP through Temporary Recovery then i reboot and BAM . Nothing there.
Black display , no bootloader,nothing
just when pluging the device it showed qhsusb_Bulk Driver on Windows
Any Help ?
and if i send it back to google does it cover the Warranty?
Google probably won't do anything for you as you installed it at your own risk
mustafa alzubaidy said:
hi
i just flash the Android N Preview it worked normaly then i flash TWRP through Temporary Recovery then i reboot and BAM . Nothing there.
Black display , no bootloader,nothing
just when pluging the device it showed qhsusb_Bulk Driver on Windows
Any Help ?
and if i send it back to google does it cover the Warranty?
Click to expand...
Click to collapse
No it won't be covered by warranty. What do you mean you flashed TWRP through temporary recovery? Exactly what TWRP did you flash? The filename please.
Good news: your phone is not dead. I've had this issue once with my OnePlus One and I was able to get if fixed.
Bad news: process was a little bit harder than standard flashing, unlocking, etc. stuffs.
Heisenberg said:
No it won't be covered by warranty. What do you mean you flashed TWRP through temporary recovery? Exactly what TWRP did you flash? The filename please.
Click to expand...
Click to collapse
i use the NRT toolKit to flash TWRP (it provide temporary Recovery to flash any zip then it goes back to stock , i did this earlier its not the cause) it boot the recovery and i flashed this file :
twrp-3.0.0.0-s2vep-20160208 (then i realized it is the wrong file in the wrong folder)
after that i reboot the device and got bricked.
anmar21 said:
Good news: your phone is not dead. I've had this issue once with my OnePlus One and I was able to get if fixed.
Bad news: process was a little bit harder than standard flashing, unlocking, etc. stuffs.
Click to expand...
Click to collapse
ok can you give me a link or something ? i am a techy guy and can learn easily.(hopefully)
mustafa alzubaidy said:
i use the NRT toolKit to flash TWRP (it provide temporary Recovery to flash any zip then it goes back to stock , i did this earlier its not the cause) it boot the recovery and i flashed this file :
twrp-3.0.0.0-s2vep-20160208 (then i realized it is the wrong file in the wrong folder)
after that i reboot the device and got bricked.
Click to expand...
Click to collapse
Yeah, wrong recovery, big mistake.
mustafa alzubaidy said:
ok can you give me a link or something ? i am a techy guy and can learn easily.(hopefully)
Click to expand...
Click to collapse
You need special Qualcomm tools to recover, I haven't seen such a tool for this device yet though.
Heisenberg said:
Yeah, wrong recovery, big mistake.
You need special Qualcomm tools to recover, I haven't seen such a tool for this device yet though.
Click to expand...
Click to collapse
i search the net i found that for lG G2 , LG G3
any idea
how much time should i wait if such a tool appears?
thanks for you help
mustafa alzubaidy said:
i search the net i found that for lG G2 , LG G3
any idea
how much time should i wait if such a tool appears?
thanks for you help
Click to expand...
Click to collapse
It's impossible to say if or when it might become available.
@Heisenberg
Flashing the wrong recovery should have corrupted( or affected ) only the recovery partition, shouldn't it. From the description the OP has given it looks like the bootloader is corrupt, which is kind of weird
Have you seen this kind of problem on any other device ( coming from a moto g to n6p I thought the bootloader corruption things were over for me , but after reading this thread I am little terrified )
sjandroiddeveloper said:
@Heisenberg
Flashing the wrong recovery should have corrupted( or affected ) only the recovery partition, shouldn't it. From the description the OP has given it looks like the bootloader is corrupt, which is kind of weird
Have you seen this kind of problem on any other device ( coming from a moto g to n6p I thought the bootloader corruption things were over for me , but after reading this thread I am little terrified )
Click to expand...
Click to collapse
It corrupts the partition table which affects the other partitions.
mustafa alzubaidy said:
ok can you give me a link or something ? i am a techy guy and can learn easily.(hopefully)
Click to expand...
Click to collapse
For my OPO I used a tool and as @Heinsenberg mentioned I've never seen such a tool for the 6P yet. RMA would be the best solution, just say your not able to turn your phone on (which is true) .
sjandroiddeveloper said:
@Heisenberg
Flashing the wrong recovery should have corrupted( or affected ) only the recovery partition, shouldn't it. From the description the OP has given it looks like the bootloader is corrupt, which is kind of weird
Have you seen this kind of problem on any other device ( coming from a moto g to n6p I thought the bootloader corruption things were over for me , but after reading this thread I am little terrified )
Click to expand...
Click to collapse
me too!
i have flashed many rom with many devices , i even flashed a rom by enterning a download rom on a black screen and it worked!
but flashing wrong recovery i dont think it will cause such brick
FYI when i connect it to the PC it is recognized and when i contiously press the power buttuon it re-connected to the pc
If he really sends the device in and Google finds out HOW exactly the phone died, he might face severe consequences. It´s dishonest after all.
If you flash the wrong recovery for a different device, it´s your own bad luck. Now here´s the deal, you can still repair the device if a) Huawei would fix it or b) find a phone shop which could replace the motherboard. Once the Bootloader is bricked, there´s barely anything a regular user could do except for some complicated methods which require the knowledge and the special tools which most people don´t have.
anmar21 said:
For my OPO I used a tool and as @Heinsenberg mentioned I've never seen such a tool for the 6P yet. RMA would be the best solution, just say your not able to turn your phone on (which is true) .
Click to expand...
Click to collapse
mustafa alzubaidy said:
me too!
i have flashed many rom with many devices , i even flashed a rom by enterning a download rom on a black screen and it worked!
but flashing wrong recovery i dont think it will cause such brick
FYI when i connect it to the PC it is recognized and when i contiously press the power buttuon it re-connected to the pc
Click to expand...
Click to collapse
Flashing the wrong recovery can and does cause such a brick, this is what you're experiencing. I've seen it happen on many devices, it borks the partition table.
mustafa alzubaidy said:
but flashing wrong recovery i dont think it will cause such brick
Click to expand...
Click to collapse
You can tell yourself this all day long, but the phone that is in your hands that is now a doorstop, is proof otherwise.
Very crappy situation, but this is why toolkits stink, and why you need to be VERY careful when you mess w the device.