Hello,
Yesterday I wanted to partition my SD card for my Samsung Galaxy S II Plus (i9105p). And I followed those steps on a website (sorry, I'm new on this forum, I can't post the link... Googled "How to manually partition your SD card for Android Apps2SD" and go in the first website).
On this website, I used Android Device Bridge (ADB). (Step 1: in ADB, I wrote "adb shell". Step2: "parted /dev/block/mmcblk0". Step3: "print". Step4: "rm 1", "rm 2"...).
I think that I did a very very very bad thing in step 4. I removed all the partitions of my internal memory (including the SYSTEM).
I followed all steps. At the end, I push the Power button to select "Reboot your system". And the screen became black and then nothing !
My phone can't power on. I can't go into recovery mode. I can't go into download mode. My phone is not detected in my computer !
So my phone is completly bricked !!
Before doing this, I had Cyanogenmod 11 thanks to the post :
http://forum.xda-developers.com/galaxy-s2-plus/orig-development/rom-cyanogenmod-11-t2800254
Please tell me that there is a solution.
Thank you.
try a usb jig
safariking said:
try a usb jig
Click to expand...
Click to collapse
Hi, Thanks for replying.
I didn't know the usb jig. When I googled it I found that
http://forum.xda-developers.com/galaxy-s2/general/ref-usb-jig-faq-frequently-questions-t1402286
I think that it's only for the Samsung Galaxy S2 (but I have the Samsung Galaxy S2 Plus (i9105P)).
And, according to this website, it solved only soft bricked phones. However, my phone is hard bricked, and maybe worse (if it's possible...) !
Indeed, I think that I completely removed the OS (since I removed all the partitions !) and it cannot boot !
Are you sure that it can solve my problem (before I buy it) ?
My phone had at the beginning 8GB.
Is there a way to boot the phone on a SD card ? (I have 8GB on it)
If there is, can you explain me how to do it step by step (I'm a newbie, I don't understand everything sorry).
Thank you again.
Usb jig works every Samsung phones. Usb jig can safe your hard bricked phone too.
When u put jig in, ur phone boots to download mode and you are able download Stock firmware to your phone.
I am not completely sure if it will help. If the download mode stuff is also stored on the mmc chip, how could it boot to download mode then?
CoolDevelopment said:
I am not completely sure if it will help. If the download mode stuff is also stored on the mmc chip, how could it boot to download mode then?
Click to expand...
Click to collapse
I agree with you. I don't know how it could work if I deleted everything...
So is it possible to boot on an SD card ? and how?
Meridianlow said:
I agree with you. I don't know how it could work if I deleted everything...
So is it possible to boot on an SD card ? and how?
Click to expand...
Click to collapse
No even your bootloader is erased(at least I think so). And even if you can boot to anything, your efs partition is wiped and things like radio, bluetooth, wifi may not work anymore
CoolDevelopment said:
No even your bootloader is erased(at least I think so). And even if you can boot to anything, your efs partition is wiped and things like radio, bluetooth, wifi may not work anymore
Click to expand...
Click to collapse
So.. You're saying that there is no solution ?
Is my phone actually dead ?
I can't do anything ?
Meridianlow said:
So.. You're saying that there is no solution ?
Is my phone actually dead ?
hey man you have to go to any Maintenance Shop and he will fix you phone I have this problem befor and they fixed it
Click to expand...
Click to collapse
Related
Hello everyone ! I will try to explain my problem as clear as possible, hope it will be solved.
-Samsung galaxy GTi-9300, this was rooted few months ago.
-It was working fine until I uninstalled touchwiz using Nobloat app. Now, nothing besides SAMSUNG appears in the dark screen. I am not able to do anything or see anything else.
-Being smart, I connected phone with pc and opened kies , but pc/kies do not recoginise the device.
-Then tried to unroot the device, where I failed again.
So, my question is how I can install touchwiz in this case? Or any other soloution ?
ps: (there is no micro SD card in device, no back up etc )
Great thanks in advance !
Was your usb debugging turned on? or do you have a custom recovery like clockworkmod or twrp? then you can install a launcher.
chiragjn said:
Was your usb debugging turned on? or do you have a custom recovery like clockworkmod or twrp? then you can install a launcher.
Click to expand...
Click to collapse
I guess it wasn't turned on and custom recovery you mentioned were not installed. But there was Titanium backup installed, if that helps ??
So if you put the device in download mode, does ODIN recognize it? If so, you should be able to restore to stock from there. Your data may be lost though if you are unable to obtain files from the internal storage.
ryebread761 said:
So if you put the device in download mode, does ODIN recognize it? If so, you should be able to restore to stock from there. Your data may be lost though if you are unable to obtain files from the internal storage.
Click to expand...
Click to collapse
Guys I got it solved.... thanks ! I am not tech/IT guy but managed to solve it with the help of other posts in xda forums.
Hello everybody,
I got my hands on this phone and I tampered too much with Qualcomm's FAT partition with the secondary bootloader, hardbricking the phone itself.
Trying to turn the phone on, shows the Samsung logo for some seconds then shuts down and disconnects, Download Mode is unaccessible but with VolUP+Home+Power the phone just stays connected (with the screen being black), but ignores any attempt to flash, Odin staying stuck on "SetupConnection...".
What I've tried already:
- Flashing with Heimdall -- phone isn't even recognized
- Removing the battery "trick" etc, etc, etc
- Changing .tar.md5 package
- Forcing a repartition with the .pit
Any clue might be useful, thanks in advance to anyone replying.
LucentW said:
Hello everybody,
I got my hands on this phone and I tampered too much with Qualcomm's FAT partition with the secondary bootloader, hardbricking the phone itself.
Trying to turn the phone on, shows the Samsung logo for some seconds then shuts down and disconnects, Download Mode is unaccessible but with VolUP+Home+Power the phone just stays connected (with the screen being black), but ignores any attempt to flash, Odin staying stuck on "SetupConnection...".
What I've tried already:
- Flashing with Heimdall -- phone isn't even recognized
- Removing the battery "trick" etc, etc, etc
- Changing .tar.md5 package
- Forcing a repartition with the .pit
Any clue might be useful, thanks in advance to anyone replying.
Click to expand...
Click to collapse
in my opinion go to coustmer service and you know it but i think
@ShadowsDie can help you
LucentW said:
Hello everybody,
I got my hands on this phone and I tampered too much with Qualcomm's FAT partition with the secondary bootloader, hardbricking the phone itself.
Trying to turn the phone on, shows the Samsung logo for some seconds then shuts down and disconnects, Download Mode is unaccessible but with VolUP+Home+Power the phone just stays connected (with the screen being black), but ignores any attempt to flash, Odin staying stuck on "SetupConnection...".
What I've tried already:
- Flashing with Heimdall -- phone isn't even recognized
- Removing the battery "trick" etc, etc, etc
- Changing .tar.md5 package
- Forcing a repartition with the .pit
Any clue might be useful, thanks in advance to anyone replying.
Click to expand...
Click to collapse
You shouldnt had to play with the bootloader neither the SBL
Im sorry to tell you that if your phone doesnt acces neither recovery and download mode it is hard bricked
that is why odin doesnt recognize the device
however, USB JIG is the best solution (the other one is changing the motherboard)
You can follow this instructions http://forum.xda-developers.com/galaxy-s2/help/guide-how-to-make-usb-jig-reset-binary-t1604707 to build one
using this SHOULD work but its even possible your bootloader is so messed up that will not open
You told me there about download mode, what about recovery mode? althought it should not work maybe God gives you a second chance
ShadowsDie said:
You shouldnt had to play with the bootloader neither the SBL
Im sorry to tell you that if your phone doesnt acces neither recovery and download mode it is hard bricked
that is why odin doesnt recognize the device
however, USB JIG is the best solution (the other one is changing the motherboard)
You can follow this instructions http://forum.xda-developers.com/galaxy-s2/help/guide-how-to-make-usb-jig-reset-binary-t1604707 to build one
using this SHOULD work but its even possible your bootloader is so messed up that will not open
You told me there about download mode, what about recovery mode? althought it should not work maybe God gives you a second chance
Click to expand...
Click to collapse
Actually ODIN recognizes the phone, but hangs on "SetupConnection...", sure the simplest solution might be the jig if there's a secondary bootloader in situ.
Obviously the recovery mode is dead, but still, I saw that it bypasses Samsung's logo and just reboots.
Since it's Qualcomm, probably the microSD emergency procedure used on the S3s might be a fair try.
If someone has still a working phone, can please do a dd image of the first 100 MB of the EMMC so I can see if this option is viable?
Might be a nice solution for hard bricked Qualcomm-based Samsung phones to unbrick those.
LucentW said:
Actually ODIN recognizes the phone, but hangs on "SetupConnection...", sure the simplest solution might be the jig if there's a secondary bootloader in situ.
Obviously the recovery mode is dead, but still, I saw that it bypasses Samsung's logo and just reboots.
Since it's Qualcomm, probably the microSD emergency procedure used on the S3s might be a fair try.
If someone has still a working phone, can please do a dd image of the first 100 MB of the EMMC so I can see if this option is viable?
Might be a nice solution for hard bricked Qualcomm-based Samsung phones to unbrick those.
Click to expand...
Click to collapse
First, for the SetupConnection try changing the ports but first BE SURE Kies is closed or end the task as Kies closes your connections using third-party programs
then reinstall samsung usb drivers or even adb drivers are good.
if you will find anyway to execute the command adb reboot-bootloader you could probably save the phone
2. I just read about the microSD procedure, it looks like a pretty clever idea
I wonder how do you know how many MB's you need
so i have done here a 70MB IMG, and with 100 didnt worked so I did a 99 MB one
Remember you need Class10 16 GB Card
If somehow this solved your problem, i will do a post in our General Section
Good Luck, i'll stay tuned.
EDIT: I just noticed the files have 169 MB so I can't post them here, tell me your email and i send you, my email is [email protected]
ShadowsDie said:
First, for the SetupConnection try changing the ports but first BE SURE Kies is closed or end the task as Kies closes your connections using third-party programs
then reinstall samsung usb drivers or even adb drivers are good.
if you will find anyway to execute the command adb reboot-bootloader you could probably save the phone
2. I just read about the microSD procedure, it looks like a pretty clever idea
I wonder how do you know how many MB's you need
so i have done here a 70MB IMG, and with 100 didnt worked so I did a 99 MB one
Remember you need Class10 16 GB Card
If somehow this solved your problem, i will do a post in our General Section
Good Luck, i'll stay tuned.
EDIT: I just noticed the files have 169 MB so I can't post them here, tell me your email and i send you, my email is [email protected]
Click to expand...
Click to collapse
I don't have Kies installed, since I never kept any Samsung phone with the stock TouchWiz ROM, but only the USB Drivers package for ODIN and so on.
I sent you a PM with my e-mail address, but you could upload the img to MEGA or whatever file locker service...
In the case this get sorted, I'll upload the IMG over my server and drop the link, so you don't need to worry about the link expiring or whatever
LucentW said:
I don't have Kies installed, since I never kept any Samsung phone with the stock TouchWiz ROM, but only the USB Drivers package for ODIN and so on.
I sent you a PM with my e-mail address, but you could upload the img to MEGA or whatever file locker service...
In the case this get sorted, I'll upload the IMG over my server and drop the link, so you don't need to worry about the link expiring or whatever
Click to expand...
Click to collapse
check your email
ShadowsDie said:
check your email
Click to expand...
Click to collapse
Tried to burn the SD card, it seems that the 7227A doesn't support boot-from-SD.
Anyways, I ordered off eBay for some change a jig dongle, as soon as I get that I'll try that way, but I think that it won't work since most of the hardware components (except for the NAND) are not made by Samsung.
I'll let you know how it proceeds
Until yesterday,my nexus 5 16GB (Imported from Canada to India) runs fine, but it give some error after rebooting a device. "UID's inconsistent Error (I'm feeling Lucky)" .
I searched on XDA Forum and find a solution that it needs to fix permission through TWRP recovery.
The error had gone but my internal SD storage shows empty in any file manager but works fine on PC (it shows all files and folders on PC).
I got this storage problem second time in last two months and it happens when i do some task through TWRP like cleaning cache,Dalvik cache etc.
Last time i fixed it by simply re-installing the firmware.
But this time i read somewhere to use a command "dd if=/dev/zero of=/dev/block/mmcblk0" in Terminal emulator app.
So i go for this solution.But after this when i reboot my device,it never turns ON.
No combination of button works to get in recovery or bootloader.
It is detected as " Qualcomm hs-usb qdloader 9008" port in device manager.
and if i press and hold volume up then connect it via usb to pc ,it shows unknown device.
other than this, nothing works and no screen activity.
i had already tried LG flash Tool,but it says device is in unknown mode.
Please tell me if my device is Hard Bricked or not?
If Yes ,how much it will cost to get repaired here in INDIA?
Device Details:
Nexus 5 16GB Android L LPV81C (rooted with custom TWRP recovery)
Bootloader Unlocked.
Looks like you nuked your eMMC...
Where did you find that command?
Bhupideol said:
Until yesterday,my nexus 5 16GB (Imported from Canada to India) runs fine, but it give some error after rebooting a device. "UID's inconsistent Error (I'm feeling Lucky)" .
I searched on XDA Forum and find a solution that it needs to fix permission through TWRP recovery.
The error had gone but my internal SD storage shows empty in any file manager but works fine on PC (it shows all files and folders on PC).
I got this storage problem second time in last two months and it happens when i do some task through TWRP like cleaning cache,Dalvik cache etc.
Last time i fixed it by simply re-installing the firmware.
But this time i read somewhere to use a command "dd if=/dev/zero of=/dev/block/mmcblk0" in Terminal emulator app.
So i go for this solution.But after this when i reboot my device,it never turns ON.
No combination of button works to get in recovery or bootloader.
It is detected as " Qualcomm hs-usb qdloader 9008" port in device manager.
and if i press and hold volume up then connect it via usb to pc ,it shows unknown device.
other than this, nothing works and no screen activity.
i had already tried LG flash Tool,but it says device is in unknown mode.
Please tell me if my device is Hard Bricked or not?
If Yes ,how much it will cost to get repaired here in INDIA?
Device Details:
Nexus 5 16GB Android L LPV81C (rooted with custom TWRP recovery)
Bootloader Unlocked.
Click to expand...
Click to collapse
Try this: download android driver,change usb port ad use nexus root tolkit http://forum.xda-developers.com/goo...olkit-wugs-nexus-root-toolkit-v1-8-3-t2517778 . The software has a system to try to recover bricked nexus. Sorry for my incomprensible english, i'm italian
All Bricks are hard.
If you cant fix with LG flashtool, yes it's bricked
Hi,
Try this [bootloader] [unbrick] Second Bootloader on Nexus 5
With those instructions I was able to recover my nexus 5.
ZammyHedgeFox said:
Looks like you nuked your eMMC...
Where did you find that command?
Click to expand...
Click to collapse
Somewhere a post on androidforums.com
manolito1998 said:
Hi,
Try this [bootloader] [unbrick] Second Bootloader on Nexus 5
With those instructions I was able to recover my nexus 5.
Click to expand...
Click to collapse
He destroyed mmcblk0 which is the entire eMMC partition...
So, no second bootloader.
manolito1998 said:
Hi,
Try this [bootloader] [unbrick] Second Bootloader on Nexus 5
With those instructions I was able to recover my nexus 5.
Click to expand...
Click to collapse
I had tried this but no luck....
Bhupideol said:
I had tried this but no luck....
Click to expand...
Click to collapse
Man, if your phone enter in fastboot mode, download theka first firmware from google site, maybe 4.4, and install it via fastboot, i didn't read all the thread but it save me when something similar happens to me, but if your phone didn't enter in fastboot, soo I think it's hard bricked
eng.Colombo said:
Man, if your phone enter in fastboot mode, download theka first firmware from google site, maybe 4.4, and install it via fastboot, i didn't read all the thread but it save me when something similar happens to me, but if your phone didn't enter in fastboot, soo I think it's hard bricked
Click to expand...
Click to collapse
Ok Thanks!
as none of the method works, I assumed phone is hard bricked.
Should i go for a warranty claim in Canada (i can manage to send it to canada through relative to my brother (who live in canada) for this purpose)????
Or just give here in India to LG service center for repair or motherboard replacement ????
Anyone knows how much motherboard replacement will cost ???
Bhupideol said:
But this time i read somewhere to use a command "dd if=/dev/zero of=/dev/block/mmcblk0" in Terminal emulator app.
So i go for this solution.But after this when i reboot my device,it never turns ON.
Click to expand...
Click to collapse
This here alarms me... You read "Somewhere? where exactly? you obviously didn't know what it was or what it could have done, so why do it?
Yeah, seems it's hard bricked, but you've been taught a lesson here.. make sure you know what you're doing... and don't just "read" something and try it..
If in doubt, read, then read again, then read some more.. if you are stuck. Ask.
radicalisto said:
This here alarms me... You read "Somewhere? where exactly? you obviously didn't know what it was or what it could have done, so why do it?
Yeah, seems it's hard bricked, but you've been taught a lesson here.. make sure you know what you're doing... and don't just "read" something and try it..
If in doubt, read, then read again, then read some more.. if you are stuck. Ask.
Click to expand...
Click to collapse
Yep because what he has done here is overwrite the entire partition layout.
Bhupideol said:
Ok Thanks!
as none of the method works, I assumed phone is hard bricked.
Should i go for a warranty claim in Canada (i can manage to send it to canada through relative to my brother (who live in canada) for this purpose)????
Or just give here in India to LG service center for repair or motherboard replacement ????
Anyone knows how much motherboard replacement will cost ???
Click to expand...
Click to collapse
LG in indai will not do anything because the D820 variant sold in canada and the D821 variant sold in india. It does not matter if you have LG warranty or not. Maybe they will offer you to replace the D820 board with a D821 board, but you have to pay the costs of the repair and motherboard change. The price can go above 100 USD.
If you facing this "UID's inconsistent Error (I'm feeling Lucky)" problem in the future then you have to make a factory reset. You get this error if you dirty flash roms
Bhupideol said:
But this time i read somewhere to use a command "dd if=/dev/zero of=/dev/block/mmcblk0" in Terminal emulator app.
Click to expand...
Click to collapse
somewhere... sounds fishy
Actually when I saw this I was reminded of how I used to tell folks on MMO's that I played that pressing ALT+F4 was how you pick up rare items when they drop and that you had to press it repeatedly so no one else got it...
Dude i had the same problem and fixed it with TWRP ( Fix Permissions ). Sorry for your phone btw. Looks like a nuked emmc as others said...
If it turn on I recommend you try nexus toolkit
I use that for my N7
MasterX007 said:
If it turn on I recommend you try nexus toolkit
I use that for my N7
Click to expand...
Click to collapse
Dude, it doesnt turn on. It's hard bricked. You do the dd command he did and I guarantee it'll hard brick it every time.
Sent from my Nexus 5 using XDA Free mobile app
Ok
Ok,
I got all of this.
Thanks for your replies.
Learned a lesson from my stupidity.
Now,I am sending it back to Canada.
It's kinda said that you can wipe the most important partition of the device without it warning you about the possible outcome.
Tapatalk-kal küldve az én Nexus 5-el
Guys I REALLY NEED your HELP.
Here's What I did..
1. Installed CWM on my NOKIA X
2.Got into Recovery mode(It's Cool actually)
3.Thought of installing minirom kitkat on it..(I had already copied it to my removable sd card.)
4.Went through all the menus,,, did nothing,,, and somewhere I saw advanced,, got into it (I didn't know what I was thinking) I cleared every option that it had including cache, memory,sd card, emmc and also some boot related stuff..
5.All of a sudden I couldn't move the options so I just removed the battery and tried to power it on....(**** Happens)-Phone is not powering on.... no boot no light just A DEAD PHONE.
plz gus I Really NEED HELP. How Can I Solve this Problem.........................................................................................Plz plz plz plz.......:crying::crying::crying::crying::crying::crying::crying::crying::crying::crying::crying:
I think this is hard brick.(very hard to fix) are you able to open factory mod now? if no then wait for developers to help you to fix hard brick. or if your device showing on pc then you can flash stock rom...
•axe• said:
I think this is hard brick.(very hard to fix) are you able to open factory mod now? if no then wait for developers to help you to fix hard brick. or if your device showing on pc then you can flash stock rom...
Click to expand...
Click to collapse
no my phone's not powering up and i'm not able to open factory mode....... Plz help
Aztile said:
no my phone's not powering up and i'm not able to open factory mode....... Plz help
Click to expand...
Click to collapse
download and open ADB driver installer
is your device showing here? or download and open adb shell and type adb devices
is your device listed here?
if yes then download stock rom for nokia x
and flash is with any flash tool (like odin)
(make sure you have installed your phone to the same pc before means you have drivers)
if your device not showing then contact nokia care (dont tell them your story otherwise your warrenty will over tell them only that your mobile is not turning on )
•axe• said:
download and open ADB driver installer
is your device showing here? or download and open adb shell and type adb devices
is your device listed here?
if yes then download stock rom for nokia x
and flash is with any flash tool (like odin)
(make sure you have installed your phone to the same pc before means you have drivers)
if your device not showing then contact nokia care (dont tell them your story otherwise your warrenty will over tell them only that your mobile is not turning on )
Click to expand...
Click to collapse
Sorry buddy...... Tried it... but no use
All we can do is to refer you to a service center. Sorry.
Moderators, please verify my account. I am sick of the five-minute post wait.
Sent from my XT1022 using the XDA Premium 4 app.
Try this..power the phone off, wait 5 mins, then press and hold power for 60 seconds, and check if you see any signs of the phone coming back to life. If not, then the next option is the service center
that too is not working.................Is there no one inthis whole XDA Universe who can help me..... come on guys there must be someone................:crying::crying::crying:
tech_master said:
Moderators, please verify my account. I am sick of the five-minute post wait.
Click to expand...
Click to collapse
The five-minute post limit is lifted once you have reached 10 posts. The moderators have nothing to do with it, as the process is automated to lift the wait after you post 10 times.
The reason for this wait is to keep new users from rapidly posting uselessly just to achieve 10 posts.
Dude This is crazy
thenookieforlife3 said:
The five-minute post limit is lifted once you have reached 10 posts. The moderators have nothing to do with it, as the process is automated to lift the wait after you post 10 times.
The reason for this wait is to keep new users from rapidly posting uselessly just to achieve 10 posts.
May I have a post thank for helping?
Click to expand...
Click to collapse
Dude this is really crazy....... I thought it was someone trying to help me there and now this............................................ AAAhhhhhhh:crying::crying::crying:
Aztile said:
Dude this is really crazy....... I thought it was someone trying to help me there and now this............................................ AAAhhhhhhh:crying::crying::crying:
Click to expand...
Click to collapse
Oops, sorry to get your hopes up.
I do actually have a few things to say about the real problem here:
1. Are you sure that your device is charged up? If not, make sure to plug it in to charge.
2. If charging isn't the problem, I'm going to give it a safe bet that your device is bricked. Like, turned into nothing more than a brick. (That's what "bricked" actually means ) If the device doesn't respond to the power button (which your posts have led me to believe), then there is no way to revive your device.
aah come on
thenookieforlife3 said:
Oops, sorry to get your hopes up.
I do actually have a few things to say about the real problem here:
1. Are you sure that your device is charged up? If not, make sure to plug it in to charge.
2. If charging isn't the problem, I'm going to give it a safe bet that your device is bricked. Like, turned into nothing more than a brick. (That's what "bricked" actually means ) If the device doesn't respond to the power button (which your posts have led me to believe), then there is no way to revive your device.
Post thank for the real answer?
Click to expand...
Click to collapse
Jesus!!!! Did you just say "NO WAY" come on buddy don't do this to me..................................................... It's like i'm half dead...... there must be some way to unbrick it.........................Come on PLZ plz plz:crying::crying::crying::crying::crying::crying::crying:
aah come on
thenookieforlife3 said:
Oops, sorry to get your hopes up.
I do actually have a few things to say about the real problem here:
1. Are you sure that your device is charged up? If not, make sure to plug it in to charge.
2. If charging isn't the problem, I'm going to give it a safe bet that your device is bricked. Like, turned into nothing more than a brick. (That's what "bricked" actually means ) If the device doesn't respond to the power button (which your posts have led me to believe), then there is no way to revive your device.
Post thank for the real answer?
Click to expand...
Click to collapse
Jesus!!!! Did you just say "NO WAY" come on buddy don't do this to me..................................................... It's like i'm half dead...... there must be some way to unbrick it.........................Come on PLZ plz plz:crying::crying::crying::crying::crying::crying::crying:
Aztile said:
Jesus!!!! Did you just say "NO WAY" come on buddy don't do this to me..................................................... It's like i'm half dead...... there must be some way to unbrick it.........................Come on PLZ plz plz:crying::crying::crying::crying::crying::crying::crying:
Click to expand...
Click to collapse
You said you've cleared eMMC and also some boot related stuff.
Well, messing with your eMMC and boot partition isn't a good idea, if you wiped your entire eMMC partition it means you've also wiped bootloader stuff...
I'm sorry but looks like your phone is totally bricked....
First of all stop shouting...!
Are you sure you choose "advaneced menu" and not "mount and storage" ....?
Also me too I think your device is bricked...
If you can't recognise it from fastboot and adb and you can boot to bootloader and recovery mode it is bricked...
root-expert said:
First of all stop shouting...!
Are you sure you choose "advaneced menu" and not "mount and storage" ....?
Also me too I think your device is bricked...
If you can't recognise it from fastboot and adb and you can boot to bootloader and recovery mode it is bricked...
Click to expand...
Click to collapse
Ooops Sorry.....
Ok I understood..... IT'S BRICKED..........
Well then how to unbrick it
Aztile said:
Ooops Sorry.....
Ok I understood..... IT'S BRICKED..........
Well then how to unbrick it
Click to expand...
Click to collapse
If your phone won't turn on at all, it's totally bricked. Only a motherboard replacement will fix it...
As you know your phone has hard bricked buddy
then you should also know you cant fix it
try odin and flash bootloader (if u can without open download mode)
or Nokia care is the best way...
Need a bit of help. Phone is bricked. Can't get it into recovery or download mode.
Odin doesn't recognize the phone. My laptop recognizes it as QHSUSB_BULK. Is there a way to fix this phone? Any help would be appreciated.
ZodaZo said:
Need a bit of help. Phone is bricked. Can't get it into recovery or download mode.
Odin doesn't recognize the phone. My laptop recognizes it as QHSUSB_BULK. Is there a way to fix this phone? Any help would be appreciated.
Click to expand...
Click to collapse
The first question is :
What were you doing with the phone when this happened?
What version of Odin are you using?
Do you have the Samsung USB drivers installed on your computer?
What is your computer's operating system?
Use battery and back in phone
Charging on 100%
Turn off phone.
Download samsung driver on laptop
Download last Odin
Download first firmware for 915A, search on this forum. Kit kat.
Turn on phone in download mode
And flash first official rom.
Sent from my SAMSUNG-SM-N915A using XDA-Developers Legacy app
The Radius Kid said:
The first question is :
What were you doing with the phone when this happened?
What version of Odin are you using?
Do you have the Samsung USB drivers installed on your computer?
What is your computer's operating system?
Click to expand...
Click to collapse
I wasn't doing anything, this is my father's phone. From what he told me, he was having some software issues and then he let one of his co-workers reset the phone. It was working fine for a while but then it just shut off which is how it got to its current state.
I'm using v3.12.3
Yes I have the USB drivers installed
Windows 10
androidBH said:
Use battery and back in phone
Charging on 100%
Turn off phone.
Download samsung driver on laptop
Download last Odin
Download first firmware for 915A, search on this forum. Kit kat.
Turn on phone in download mode
And flash first official rom.
Click to expand...
Click to collapse
Like I said, I can't get the phone in download mode.
Someone with N915A can create for you the debrick.img. With that debrich.img you flash it to the external Sdcard (not internal storage) via win32diskimager. Make sure your batterycapacitiy is not less than 30%. Try to start the phone and it should flash the debrick.img and then boot to rom.
Or you can try putting this in your 16GB Sdcard formatted as Fat32. It is for N910A but they are similar, only the edge panel.
Bordo_Bereli51 said:
Someone with N915A can create for you the debrick.img. With that debrich.img you flash it to the external Sdcard (not internal storage) via win32diskimager. Make sure your batterycapacitiy is not less than 30%. Try to start the phone and it should flash the debrick.img and then boot to rom.
Or you can try putting this in your 16GB Sdcard formatted as Fat32. It is for N910A but they are similar, only the edge panel.
Click to expand...
Click to collapse
I put the file on the SDCard, with it being formatted to fat32. Nothing happens.
Also I'd like to try the debrick method but I don't know anyone with a N915A so if anyone could make one I'd appreciate it.
ZodaZo said:
I put the file on the SDCard, with it being formatted to fat32. Nothing happens.
Also I'd like to try the debrick method but I don't know anyone with a N915A so if anyone could make one I'd appreciate it.
Click to expand...
Click to collapse
please did you find a way to fix the problem? i need help
---------- Post added at 09:04 AM ---------- Previous post was at 09:03 AM ----------
ZodaZo said:
I put the file on the SDCard, with it being formatted to fat32. Nothing happens.
Also I'd like to try the debrick method but I don't know anyone with a N915A so if anyone could make one I'd appreciate it.
Click to expand...
Click to collapse
please did u get a fix? also facing the same problem
I had this same problem with my sisters galaxy note edge and i used this video to fix it.
https://www.youtube.com/watch?v=jLPHWtb0StI