I have rooted and modded over 5 diffrent phones and 3 difrrent tablets. I have brought dead tablets that no PC repair place would or could fix. they said unfixable.. I was able to fix.. No problem. I hae had my own phones, LG Optimus L9 and F6 Both MetroPCS I have had a few tablets. I root everything withen the first 5 mins..
I just recently started using TWRP over CWM. I like TWRP most.. I never had problems with TWRP.. On my F6 when I fo a partition SDcard(External) it works wit no problem.
On my G3 Using the same commands as I did on my F6. Hardbricked my phone.. and that was with the latest TWRP using TWRP manager.. Everything worked up to that point
of Partitioning my sdcard. Only diffrents from this and my other phones is Unlocked bootloader.. I dont know if that made such a differents as to why it deleted my
internal Partitions insted of the the external.. I now have a $600.00 paper weight. (lucky for me I just got it..( So I was able to get a refund))....
When I used the partition sdcard. it seemed to work then it gave error then said failed.. after trying again. I decided I would just take my sdcard out and format it on my PC. so I used the shutdown command in the reboot area.. After getting the sdcard formated.. I stuck it back in and closed the cover. Now it wouldnt boot back up.. No power or anything. Just a black screen.. I thought it might be something with my phone, till my friend that was over with his, had the very same thing happend using the same commands as I did with the same version of TWRP as I did.. Im surprised my friend didnt want to kick my butt for that.. Not that he would of been able too. but hes getting his replaced for nothing also just gota pay shipping, Now what I want to know is this,
Has anyone here know what happend and why this happend? I searched google and couldnt find anything with the answers I need. I only used TWRP to partition my SDcard but ended up deleting my internal somehow at least it seems. but that doesnt do that on my f6 with TWRP.. so I dont get it, I used the same commands on my
other phone(f6) and even my tablet which they all have TWRP. and nothing like that has ever happend before.
I need a little expert knowledge from someone that might have some clue as too what I did wrong or what could I have done that caused this. So that I dont do this again.
I have another G3 on the way.. it seems like out of all the LG's I have had this one is easy to brick. ( I have never hardbricked a phone before this)
Try this
http://forum.xda-developers.com/showthread.php?t=2799647
kroukes2000 said:
Try this
http://forum.xda-developers.com/showthread.php?t=2799647
Click to expand...
Click to collapse
Thanks, but I have tried all the flashing tools and stock rom approach.. Cant even get into Download mode.. so nothing will work.. its hardbricked..
anyhow I already sent the phone back to T-Mobile. and I already have a new one comming..
Thank you for your input though.....
What about this?
http://forum.xda-developers.com/lg-g3/help/lg-g3-bricked-tried-everything-experts-t2852962
Sent from my LG-D851 using XDA Free mobile app
Are you using a T-Mobile g3? You shouldn't have to format your SD card through twrp. You should do it through the PC or phone. I wonder if you accidentally deleted your partitions on your phone. Did you try pluging in your phone into your charger and turning it on that way?
I dont get it. Why are you trying to format the sd card to the computer and all that. If you already had twrp going you simply wipe than install new room and reboot...
why is this even here and not in Q&A
My advice...DO NOT ROOT ANOTHER PHONE. Reading your post it is VERY obvious you have no clue what you're doing. Also, it's within, not withen...
Cant really figure out what happened by what you described...I'll have to agree with Mikeyinid, just leave the phones alone or be prepared for your own consequences, not sending it back to t-mobile because you screwed it up. These are some of the reasons phones come locked down, development is so hard on these devices and will just get worse as time goes on.
I'm sure this will come out wrong. Why is this post in here? This is a development area right?
aclegg2011 said:
Are you using a T-Mobile g3? You shouldn't have to format your SD card through twrp. You should do it through the PC or phone. I wonder if you accidentally deleted your partitions on your phone. Did you try pluging in your phone into your charger and turning it on that way?
Click to expand...
Click to collapse
I should have. but like I said. I have never had that problem before. and Yes I think I deleted the phones partition when it shoudnt of let me do that With my F6 it only formates
the External Sdcard.. On here it seem to format a little more then just the external SD card.. Thank you for your input
yanowman said:
I dont get it. Why are you trying to format the sd card to the computer and all that. If you already had twrp going you simply wipe than install new room and reboot...
Click to expand...
Click to collapse
EXTERNAL SDcard. was on my LG Optimus F6 with a 4 gig swap partition and a 5 gig 2nd partition for link2sd since that phone wont let you install to SDcard..
I needed to wipe that whole card so that I could reformat it with the 64 gigs that it was. instead of the 50 gigs that I had because it was split in 3 parts.
thats the only reason. I had to delete the partitions and reformat it, I didnt want the phone partitions formated.. Only the EXTERNAL sdcard....
Thank you for your input.,.
mikeyinid said:
My advice...DO NOT ROOT ANOTHER PHONE. Reading your post it is VERY obvious you have no clue what you're doing. Also, it's within, not withen...
Click to expand...
Click to collapse
Just because I dont type and spell that great doesnt mean I dont know what I am doing.. I have rooted many phones in the past With no problem.. I just happend to run into a problem with this one phone. thats why I asked if anyone here has had that problem before or have heard of it before.. it seemed very strange that it would do that.
Ducter said:
Cant really figure out what happened by what you described...I'll have to agree with Mikeyinid, just leave the phones alone or be prepared for your own consequences, not sending it back to t-mobile because you screwed it up. These are some of the reasons phones come locked down, development is so hard on these devices and will just get worse as time goes on.
Click to expand...
Click to collapse
I do agree that the phones are getting harder and harder to deal with.. Most of the LG's are almost hard to brick. well at leat hardbrick. this one on the other hand was pretty easy.. Yes I know you can brick anyphone on per pus. but you know what I mean..
Burley1 said:
I'm sure this will come out wrong. Why is this post in here? This is a development area right?
Click to expand...
Click to collapse
Sorry, I might be out of line by posting in here.. but this has to deal with Dev and rooting questions. not a gen. question. so alot of them people in there wouldnt have any clue as to what happend.. but I thought maybe someone over here would.. but if this is out of place.. then I am sorry.. please move it to a place that it should be..
Eliminater74 said:
Just because I dont type and spell that great doesnt mean I dont know what I am doing.. I have rooted many phones in the past With no problem.. I just happend to run into a problem with this one phone. thats why I asked if anyone here has had that problem before or have heard of it before.. it seemed very strange that it would do that.
I do agree that the phones are getting harder and harder to deal with.. Most of the LG's are almost hard to brick. well at leat hardbrick. this one on the other hand was pretty easy.. Yes I know you can brick anyphone on per pus. but you know what I mean..
Sorry, I might be out of line by posting in here.. but this has to deal with Dev and rooting questions. not a gen. question. so alot of them people in there wouldnt have any clue as to what happend.. but I thought maybe someone over here would.. but if this is out of place.. then I am sorry.. please move it to a place that it should be..
Click to expand...
Click to collapse
I apologize. My post came out very douchey. I honestly think there is alot you need to learn. I'm just trying to give you advice. And I shouldn't have corrected your misspelling. It isn't something I would generally do.
Eliminater74 said:
I should have. but like I said. I have never had that problem before. and Yes I think I deleted the phones partition when it shoudnt of let me do that With my F6 it only formates
the External Sdcard.. On here it seem to format a little more then just the external SD card.. Thank you for your input
EXTERNAL SDcard. was on my LG Optimus F6 with a 4 gig swap partition and a 5 gig 2nd partition for link2sd since that phone wont let you install to SDcard..
I needed to wipe that whole card so that I could reformat it with the 64 gigs that it was. instead of the 50 gigs that I had because it was split in 3 parts.
thats the only reason. I had to delete the partitions and reformat it, I didnt want the phone partitions formated.. Only the EXTERNAL sdcard....
Thank you for your input.,.
Click to expand...
Click to collapse
Makes sense. Its pretty hard to hardbrick the g3 though. Does your phone at least turn on and goes to the lg screen? If you do have the T-Mobile version g3 you should be able boot into recovery doing the hard button reset and flash a ROM from your SD card. As long as twrp was installed right. I don't think you can format twrp, but I could be wrong.
Did your get taken care of by Google? I'm surprised they honored the warranty with it being rooted.
Sent from my LG-D851 using XDA Free mobile app
I've been posting this kind of problem for the past month. No one posted this but your motherboard malfunctioned due to no partition/boot.img that unable the phone to boot. QPST is a hit/miss most of the time but the lg recovery tool doesnt work due to lost IMEI and S/N. The only way is to get a replacement or lose all your data and repair it to LG. They're going to replace your motherboard and it takes around 2 weeks to get the phone back with same IMEI
xmagiicsx said:
I've been posting this kind of problem for the past month. No one posted this but your motherboard malfunctioned due to no partition/boot.img that unable the phone to boot. QPST is a hit/miss most of the time but the lg recovery tool doesnt work due to lost IMEI and S/N. The only way is to get a replacement or lose all your data and repair it to LG. They're going to replace your motherboard and it takes around 2 weeks to get the phone back with same IMEI
Click to expand...
Click to collapse
Thank you so much for a Realistic answer to my question/problem.. I cant understand why nobody else could figure out what I was talking about..
But the question still rises to how did I format my boot partition though TWRP Advanced settings / Partition SD card ? That should only format my External SD not the Internal sd..
I was wondering if it could be the fact that this one if the first LG phone that I have had that has a unlocked bootloader and that opened it up to more (be very carefull) as to my other phones used LOKI to get around the boot lock. (LG Optimus L9 and F6 both MetroPCS. ) because with both of them phones TWRP does what I wanted it to do. that is format only External SD.. even all the tabs that I have installed TWRP on.. only formated the External...
Eliminater74 said:
Thank you so much for a Realistic answer to my question/problem.. I cant understand why nobody else could figure out what I was talking about..
But the question still rises to how did I format my boot partition though TWRP Advanced settings / Partition SD card ? That should only format my External SD not the Internal sd..
I was wondering if it could be the fact that this one if the first LG phone that I have had that has a unlocked bootloader and that opened it up to more (be very carefull) as to my other phones used LOKI to get around the boot lock. (LG Optimus L9 and F6 both MetroPCS. ) because with both of them phones TWRP does what I wanted it to do. that is format only External SD.. even all the tabs that I have installed TWRP on.. only formated the External...
Click to expand...
Click to collapse
I know its not the main point but wanted to clear up that the L9 did not use loki. It doesnt use an aboot.img, it uses omap. That was one of the biggest pita phones ever..
Swizzle82 said:
I know its not the main point but wanted to clear up that the L9 did not use loki. It doesnt use an aboot.img, it uses omap. That was one of the biggest pita phones ever..
Click to expand...
Click to collapse
Your right.. But its been so long since I had that phone.. I didnt think about it.. My bad........... Most LG's are all locked up tight. Thank God this G3 has a unlocked bootloader...
xmagiicsx said:
I've been posting this kind of problem for the past month. No one posted this but your motherboard malfunctioned due to no partition/boot.img that unable the phone to boot. QPST is a hit/miss most of the time but the lg recovery tool doesnt work due to lost IMEI and S/N. The only way is to get a replacement or lose all your data and repair it to LG. They're going to replace your motherboard and it takes around 2 weeks to get the phone back with same IMEI
Click to expand...
Click to collapse
Dont mean to hijack this thread but do you think you can look at this post http://forum.xda-developers.com/showthread.php?p=56391046
Im kinda in the same boat on nexus4 any insight would be great. Thanks
Sent from my LG-D851 using XDA Free mobile app
Related
So I think i have officially bricked my Evo. Apologies if this is the wrong sections. Didnt know where to put it.
Well I had rooted with Simpleroot and everything was just fine. But when i tried to install a copy of the Fresh root suddenly i was stuck at the white screen. So i went into recovery and and wiped everything. I also partitioned the sd card... Dont know if i should have done that but i figured it would wipe everything.. It did and now my zip files are gone. I Dont know what to do.. Yikes
Help much appreciated .
Lol because lol
Sent from my PC36100 using XDA App
Probably shoulda gone into Q&A....but u erased all.the data on ur card when u formatted it. You should probably follow the root instructions again from the start including copying the files to your sd card and u should be fine.
You could have done a simple search and fixed ur issue.
Sent from my Evo using the XDA App
Sorry I thought this my be the wrong forum section. I cant access my Sd card though?
Your Evo isn't bricked.
Select the USB-MASS toggle feature in recovery mode, that'll mount your SD card to your computer, then drop a ROM or two onto the root of your SD card, wipe, then flash one.
Or pull the SD card out and put it in an adapter and plug into computer, then drop a couple roms on it
Sent from my PC36100 using XDA App
This is your second posting of this type. Please read these before doing anything else http://forum.xda-developers.com/showthread.php?t=695878 and http://forum.xda-developers.com/showthread.php?t=709267.
alisha898 said:
So I think i have officially bricked my Evo. Apologies if this is the wrong sections. Didnt know where to put it.
Well I had rooted with Simpleroot and everything was just fine. But when i tried to install a copy of the Fresh root suddenly i was stuck at the white screen. So i went into recovery and and wiped everything. I also partitioned the sd card... Dont know if i should have done that but i figured it would wipe everything.. It did and now my zip files are gone. I Dont know what to do.. Yikes
Help much appreciated .
Click to expand...
Click to collapse
Youre definitely not bricked. Pull the battery out, boot into fast boot, wait a sec while it does its thing, then select wipe/restore factory defaults. Then it should be fine. This happened to me 2 days ago. When bricked, the phone won't even turn on. It does nothing, thus the term.
nunyabiziz said:
This is your second posting of this type. Please read these before doing anything else http://forum.xda-developers.com/showthread.php?t=695878 and http://forum.xda-developers.com/showthread.php?t=709267.
Click to expand...
Click to collapse
That's a pretty douchie comment. Just because notify likes you, and everyone treats you like **** in the real world, doesn't give you an excuse to be a " richard" in a forum.
adelaney said:
That's a pretty douchie comment. Just because notify likes you, and everyone treats you like **** in the real world, doesn't give you an excuse to be a " richard" in a forum.
Click to expand...
Click to collapse
Im sorry you feel that way maybe you need to hug from someone but not me. There was nothing rude or wrong with my posting. There are basic knowledge required to do what the OP wants to do and so I directed toward that direction. If you would like to continue to express your PERSONAL feelings please PM me.
Yeah Anyways. The problem now is that everytime i try and boot from a zip file i just get a white screen. Is there anyway to bypass this?
alisha898 said:
Yeah Anyways. The problem now is that everytime i try and boot from a zip file i just get a white screen. Is there anyway to bypass this?
Click to expand...
Click to collapse
Which ROM's are giving you theses problems?
Ive tried the fresh 1.0.1 thats when it all started then i tried the EVO-NonSense.
I had been flashing roms before the Fresh one now im just stuck at the white screen.
Are you using Koush's Clockwork recovery? Try flashing Yay 4 Juggs ROM.
Im using the RA recovery that came with SimpleRoot
Yeah, just try flashing a different ROM.
Hmm i'll try. Is there anyway to earse my root and start over? Because for now im just get the htc Evo 4g white logo everytime i try and flash a new ROM
Did you update the radios and all that too? Did you make sure and use the right version of simple root for your software?
Yeah Yesterday I was flashing ROMS normally. Something may have happened when i tried to flash a radio and wimax
alisha898 said:
Hmm i'll try. Is there anyway to earse my root and start over? Because for now im just get the htc Evo 4g white logo everytime i try and flash a new ROM
Click to expand...
Click to collapse
http://www.youtube.com/watch?v=KBu6GsRZMdI Some random video I looked up on YouTube that shows you how to unroot. It's a hassle, to unroot, then root again, I'd give flashing a different another shot before I did that.
Stupid question: Are you wiping data and dalvik cache before flashing a ROM?
hello,
This morning i was using my phone like every day, but i notice that i had no signal so i decided to restart the phone. When it restarted out of nowhere the phone started to boot loop.. i didnt do anything for it to start doing that.. after a long while trying to fix it i gave up and got into recovery and decided to clean install the rom. It did install but after 1 minute of being on the screen it would boot loop.. I download it the same rom and installed it and still kept doing the same thing.. i had a back up so i decided to install it which i did but again after 40 seconds of start up it would boot loop.. finally, i decided to use the LG Flash tool TWICE and it did work but again after a little while the phone turns off and on.. idk what lese to do??? any ideas?
Check if it displays your IMEI in the Settings. If not you should check if you've got a EFS Backup.
vixman said:
hello,
This morning i was using my phone like every day, but i notice that i had no signal so i decided to restart the phone. When it restarted out of nowhere the phone started to boot loop.. i didnt do anything for it to start doing that.. after a long while trying to fix it i gave up and got into recovery and decided to clean install the rom. It did install but after 1 minute of being on the screen it would boot loop.. I download it the same rom and installed it and still kept doing the same thing.. i had a back up so i decided to install it which i did but again after 40 seconds of start up it would boot loop.. finally, i decided to use the LG Flash tool TWICE and it did work but again after a little while the phone turns off and on.. idk what lese to do??? any ideas?
Click to expand...
Click to collapse
mmeidl78 said:
Check if it displays your IMEI in the Settings. If not you should check if you've got a EFS Backup.
Click to expand...
Click to collapse
I already checked and everything says unknown. I do not have any type of backup! is there something i can do?
Congratulations! Now your on the same step as I am. Don't know how to fix this without a EFS Backup.
vixman said:
I already checked and everything says unknown. I do not have any type of backup! is there something i can do?
Click to expand...
Click to collapse
mmeidl78 said:
Congratulations! Now your on the same step as I am. Don't know how to fix this without a EFS Backup.
Click to expand...
Click to collapse
OHH wow!! so im basically stock with a brand new phone that boots on and off ..Wow.. well if you ever find an answer can you please share it with me!!! thank you in advance.
I have no idea what kind of backup you are talking about but could we use it from another G2?
Maybe this will help you find out what a EFS-Backup is:
http://forum.xda-developers.com/showthread.php?t=2451390
I've seen the question somewhere else (to use a backup from another g2) and they said, that it will boot but don't login into the network, cause you'll get a IMEI with 00000 or something like this.
Don't know a answer. I think I must send my G2 to LG and pay a lot of money IF they'll fix it.
vixman said:
OHH wow!! so im basically stock with a brand new phone that boots on and off ..Wow.. well if you ever find an answer can you please share it with me!!! thank you in advance.
I have no idea what kind of backup you are talking about but could we use it from another G2?
Click to expand...
Click to collapse
mmeidl78 said:
Maybe this will help you find out what a EFS-Backup is:
http://forum.xda-developers.com/showthread.php?t=2451390
I've seen the question somewhere else (to use a backup from another g2) and they said, that it will boot but don't login into the network, cause you'll get a IMEI with 00000 or something like this.
Don't know a answer. I think I must send my G2 to LG and pay a lot of money IF they'll fix it.
Click to expand...
Click to collapse
OHH i see what you mean... I have added EFS backup to the IOroot scripts so that everyone that roots will have a copy of their EFS partitions on the computer you run IOroot from. Regardless, this current thread will still be a good "heads up" and an alternative for those who insist on using other shady root methods or for those who just want another way to back things up.
I did use IOroot, does that mean that if i connect it to the computer and try to root it again it would fix it? you think???
vixman said:
OHH i see what you mean... I have added EFS backup to the IOroot scripts so that everyone that roots will have a copy of their EFS partitions on the computer you run IOroot from. Regardless, this current thread will still be a good "heads up" and an alternative for those who insist on using other shady root methods or for those who just want another way to back things up.
I did use IOroot, does that mean that if i connect it to the computer and try to root it again it would fix it? you think???
Click to expand...
Click to collapse
In the Thread is a step-by-step tutorial how to restore EFS-Files. Make a Backup of these 2 files before you root your phone again! Don't know, if those 2 files got overwritten (maybe with the damaged data) when you root your phone again.
Fixed my phone
mmeidl78 said:
In the Thread is a step-by-step tutorial how to restore EFS-Files. Make a Backup of these 2 files before you root your phone again! Don't know, if those 2 files got overwritten (maybe with the damaged data) when you root your phone again.
Click to expand...
Click to collapse
Well just wanted to let you know that i sent my phone to LG for them to fix it. They didnt charge me and all they did was re-flash the rom. if you havent fixed it you should try sending it to them.
So I think my phone is hard bricked. I was on G+ ealier today, clicked on a link that opened Chrome. got through a third of the web page and my phone freezes then the screen goes black... I have tried every troubleshoot trick provided by tmobile and samsung and the phone wont respond in any way. Just a black screen. Is it possible to brick your phone with out trying to flash a custom ROM??? The only thing new I have done in the past week was install "graph ti89" and "aviate." I dont know if this has anything to do with it but tmobile has being try to get me to install the kitkat OTA for the last week and I keep ignoring it.
just update
jcampana28 said:
So I think my phone is hard bricked. I was on G+ ealier today, clicked on a link that opened Chrome. got through a third of the web page and my phone freezes then the screen goes black... I have tried every troubleshoot trick provided by tmobile and samsung and the phone wont respond in any way. Just a black screen. Is it possible to brick your phone with out trying to flash a custom ROM??? The only thing new I have done in the past week was install "graph ti89" and "aviate." I dont know if this has anything to do with it but tmobile has being try to get me to install the kitkat OTA for the last week and I keep ignoring it.
Click to expand...
Click to collapse
Hi,
Do the update or factory reset your phone. You can always use KIES also.
Ms. K
Ms. K said:
Hi,
Do the update or factory reset your phone. You can always use KIES also.
Ms. K
Click to expand...
Click to collapse
Thanks for your input but the phone won't turn on at all. Can'T turn it on to update. Won't go into safe mode by pressing vol. up&home&power. When I plug it into the computer it says it needs drivers for "QHSUSB_BULK." Kies doesn't see it as a connected device...
If you haven't done anything to the phone why not call Tmobile and get a replacement..
Sent from my bad ass Kryon infused Note 3
deeznutz1977 said:
If you haven't done anything to the phone why not call Tmobile and get a replacement..
Sent from my bad ass Kryon infused Note 3
Click to expand...
Click to collapse
because i'd like to recover the data that is on the phone.
jcampana28 said:
because i'd like to recover the data that is on the phone.
Click to expand...
Click to collapse
A few threads down you would have found this... http://forum.xda-developers.com/showthread.php?p=47555043
My recovery image is here: http://www.mediafire.com/view/?6nu61z43y51v3k4
You need a 32 GB sd card and some luck. Also reading is a requirement.
Yours may be a special case though, as you claim nothing was going on besides you clicked a link. Should have absolutely nothing to do with ota, and everyone else who had done this was messing with their phone. This definitely works for 4.3, but no one had reported working on 4.4 (you were on 4.3 anyways). Good luck.
Sent from my SM-G900T using Tapatalk
noobtoob said:
A few threads down you would have found this... http://forum.xda-developers.com/showthread.php?p=47555043
My recovery image is here: http://www.mediafire.com/view/?6nu61z43y51v3k4
You need a 32 GB sd card and some luck. Also reading is a requirement.
Yours may be a special case though, as you claim nothing was going on besides you clicked a link. Should have absolutely nothing to do with ota, and everyone else who had done this was messing with their phone. This definitely works for 4.3, but no one had reported working on 4.4 (you were on 4.3 anyways). Good luck.
Sent from my SM-G900T using Tapatalk
Click to expand...
Click to collapse
Mr Noobtoob, has anyone reported un-bricking a N900t running 4.4.2 (1st release, believe it ends in N94 or similar, NOT NE6)?
If so, did they do anything different?
Be well.
golfcartguy said:
Mr Noobtoob, has anyone reported un-bricking a N900t running 4.4.2 (1st release, believe it ends in N94 or similar, NOT NE6)?
If so, did they do anything different?
Be well.
Click to expand...
Click to collapse
I have not seen a successful report back of the nb4 firmware. Doesn't mean it doesn't work, just don't have confirmation.
Fusionized tweaking tapatalker here...
Thanks for the quick response!
Going to try, and will report back.
To clarify, it must be a Class 10 microsd card, and must be the same size (32gb), 1st formatted to exfat, correct?
Sent using XDA Free mobile app
golfcartguy said:
To clarify, it must be a Class 10 microsd card, and must be the same size (32gb), 1st formatted to exfat, correct?
Click to expand...
Click to collapse
Those are the magic ingredients!
Frank
Frank Westlake said:
Those are the magic ingredients!
Frank
Click to expand...
Click to collapse
Got it! So, to be clear;
1st - Format class 10 card to Exfat file system or structure
2nd - Using Win32Diskmapper, just point to the file (in my case kk900tunbrick image) and write to card. *Nothing special, should I verify Md5 sum, or just leave it as default settings?
3rd, Proceed to attempt to Unbrick (Battery at 100%, Put Sd card in slot, Then Add Battery, Connect cable - some say, some say doesn't matter, to computer, then attempt to boot with button sequence to download mode, or may boot by itself?)
Also, if the 1st image I downloaded does not work, can I reformat or wipe the sd card and start again with the other file (I believe a Pit file??)
It sucks I have to ask this. I actually left XDA because of people who decided it was no longer good enough to do it for the community and they needed to get their bills paid, but screw it, I don't feel like buying a new phone. Hardbricked after flashing the MM ROM like everyone else, tried the willcracker diag thing, looked on Google until my eyes turned red, now I'm just aggravated and ready to get this fixed... Just point me and my wallet in the right direction.
However, if you know a way that doesn't involve me having to spend my last it would be greatly appreciated. I'm hoping a good Samaritan on XDA will come to aid instead of someone looking to make a quick buck but my hands are tied here...
Sent from my draconis using Tapatalk
Oh no...
mingolianbeef said:
It sucks I have to ask this. I actually left XDA because of people who decided it was no longer good enough to do it for the community and they needed to get their bills paid, but screw it, I don't feel like buying a new phone. Hardbricked after flashing the MM ROM like everyone else, tried the willcracker diag thing, looked on Google until my eyes turned red, now I'm just aggravated and ready to get this fixed... Just point me and my wallet in the right direction.
However, if you know a way that doesn't involve me having to spend my last it would be greatly appreciated. I'm hoping a good Samaritan on XDA will come to aid instead of someone looking to make a quick buck but my hands are tied here...
Sent from my draconis using Tapatalk
Click to expand...
Click to collapse
You can't boot into a custom recovery? Otherwise you could just flash a different rom...
hallosup said:
You can't boot into a custom recovery? Otherwise you could just flash a different rom...
Click to expand...
Click to collapse
Thanks for the reply bro. The issue is that it's hard bricked, though. Nothing happens, though, not even a charge light. I'm by far no stranger to this modding gaming lol, been doing it since I was 15 and I hard bricked my Evo 3D back in the day. It goes into the QCOM 9008 mode and that's about it. The only other screen it goes to is that if I short it sometimes the screen will come on with a battery icon and a triangle with an exclamation point.
Like I said, hours of Google pointed to me having to blow money because nobody has successfully unbricked the D851 yet. Which is why I asked for the above solution. However, again, if you know another way that doesn't involve spending money please share ?
Sent from my draconis using Tapatalk
mingolianbeef said:
Thanks for the reply bro. The issue is that it's hard bricked, though. Nothing happens, though, not even a charge light. I'm by far no stranger to this modding gaming lol, been doing it since I was 15 and I hard bricked my Evo 3D back in the day. It goes into the QCOM 9008 mode and that's about it. The only other screen it goes to is that if I short it sometimes the screen will come on with a battery icon and a triangle with an exclamation point.
Like I said, hours of Google pointed to me having to blow money because nobody has successfully unbricked the D851 yet. Which is why I asked for the above solution. However, again, if you know another way that doesn't involve spending money please share
Sent from my draconis using Tapatalk
Click to expand...
Click to collapse
don't mean to get on your case or anything but why would you flash mm rom for your d851 if it's not even out for our phones yet?....
Still_living714 said:
don't mean to get on your case or anything but why would you flash mm rom for your d851 if it's not even out for our phones yet?....
Click to expand...
Click to collapse
Here's my logic...
I'm no stranger to modding/devving/etc. Used to have ROMs and stuff myself, but back in the day with my old phones partition layouts were device specific (i.e. the "boot" partition would have a path of /blah/blah/blah/mmcblk0p##), and you absolutely could not flash that to any device other than your own. With my most recent devices, I've noticed that the partition layout would go as follows:
/dev/block/platform/msm_sdcc.1 (or similar)/by-name/boot
And they all have that generic path setup which has rendered many of my devices unbrickable (from a basic ROM flashing standpoint). I have a ROM for the ZTE ZMAX, and someone else from a different device altogether flashed it with only minor issues like WiFi, but it booted. I flashed a moto G ROM to the phone just to live a little dangerously and it simply didn't boot and I flashed a ZMAX ROM.
So... You are reading this and saying "I still don't understand why you did it"
I did it because I figured worse case scenario it wouldn't boot and that the partition layout for the boot/userdata/system partitions that these phones use would be the same since they are the same phone sans a couple partitions for the modem and bootloader and stuff. I didn't bank on a hard brick from a default partition layout that [shouldn't] flash to lower level partitions.
Sent from my draconis using Tapatalk
mingolianbeef said:
Here's my logic...
I'm no stranger to modding/devving/etc. Used to have ROMs and stuff myself, but back in the day with my old phones partition layouts were device specific (i.e. the "boot" partition would have a path of /blah/blah/blah/mmcblk0p##), and you absolutely could not flash that to any device other than your own. With my most recent devices, I've noticed that the partition layout would go as follows:
/dev/block/platform/msm_sdcc.1 (or similar)/by-name/boot
And they all have that generic path setup which has rendered many of my devices unbrickable (from a basic ROM flashing standpoint). I have a ROM for the ZTE ZMAX, and someone else from a different device altogether flashed it with only minor issues like WiFi, but it booted. I flashed a moto G ROM to the phone just to live a little dangerously and it simply didn't boot and I flashed a ZMAX ROM.
So... You are reading this and saying "I still don't understand why you did it"
I did it because I figured worse case scenario it wouldn't boot and that the partition layout for the boot/userdata/system partitions that these phones use would be the same since they are the same phone sans a couple partitions for the modem and bootloader and stuff. I didn't bank on a hard brick from a default partition layout that [shouldn't] flash to lower level partitions.
Sent from my draconis using Tapatalk
Click to expand...
Click to collapse
well I guess it's a lesson learned lol. I get what you're saying but by doing so you still dont know how the phone might react.
mingolianbeef said:
Here's my logic...
I'm no stranger to modding/devving/etc. Used to have ROMs and stuff myself, but back in the day with my old phones partition layouts were device specific (i.e. the "boot" partition would have a path of /blah/blah/blah/mmcblk0p##), and you absolutely could not flash that to any device other than your own. With my most recent devices, I've noticed that the partition layout would go as follows:
/dev/block/platform/msm_sdcc.1 (or similar)/by-name/boot
And they all have that generic path setup which has rendered many of my devices unbrickable (from a basic ROM flashing standpoint). I have a ROM for the ZTE ZMAX, and someone else from a different device altogether flashed it with only minor issues like WiFi, but it booted. I flashed a moto G ROM to the phone just to live a little dangerously and it simply didn't boot and I flashed a ZMAX ROM.
So... You are reading this and saying "I still don't understand why you did it"
I did it because I figured worse case scenario it wouldn't boot and that the partition layout for the boot/userdata/system partitions that these phones use would be the same since they are the same phone sans a couple partitions for the modem and bootloader and stuff. I didn't bank on a hard brick from a default partition layout that [shouldn't] flash to lower level partitions.
Sent from my draconis using Tapatalk
Click to expand...
Click to collapse
Well, i am in the same or almost the same pot as you. I flashed Fulmics ROM which was supposed to give me MM. But after downloading the almost 2GB rom, i noticed that my device wasnt part of the supported devices in Aroma Installer. But i went ahead and flashed the D855 version thinking that it might work with my D851 and incase it didnt work, the worst that could happen would be the device getting stuck on the LG Splash Logo. And when that happened, all i would have to do would be to boot into recovery and restore my backup. Little did i know that the ROM dev had added tz.img,rpm.img,boot.img and modem.img to the ROM. And what this means is that, the ROM wasnt just replacing my stock KK with Fulmics, but it was also overwriting and patching my D851 tz.img,rpm.img,boot.img and modem.img with that of the D855. The ROM flashed smoothely without an error and when it finnished, i hit the reboot button. Waiting for the device to bootup up into MM, but sadly, the the device never booted again. All i get now is Battery notifications.
For example, if i connect a USB to the phone without battery inserted, i get an empty battery with a yellow triangle with an exclamation mark in the middle of the yellow triangle. And when i exhaust the battery, and i press the power button, i get presented with an empty battery notification on the screen. Thats all i ever get.
I have tried shorting the pins... which gets me into QDownloader 9008 mode but Board Diag tool doesnt seem to work on the D851. My reasons for saying this is because i helped someone who had a D855 with the Board Diag process and it was able to flash all the files. The only pain was that, after every flash with board diag, we had to disconnect the device and re-short the pins and flash the files till we flashed all the files.
But for some unkown reason, this tool wont work on our device (D851). Apparently, the D851 motherboard is different from the D855. As i compared mine with the D855.
I just hope someone makes a tool to unbrick our D851.
Hello every one! so yesterday while doing nothing but leaving my phone on a markipilers youtube video, I see my screen go off I try to turn it back on and nothing happens. I tried power cycling and its still off, just not responding to anything, no sound no light no nothing. I tried then going to recovery mode but well... nothing happened. The only thing that actually makes any responses is when I connect it using a USB to my laptop, my laptop beeps, its not suposed to beep it is broken so is it bricked?
My device is a rooted Samsung galaxy s4 mini i19192 or so I hope it is.
I really hope that this is the right place to be redirected to assistant if not then Iam really sorry, thank you so much every one and have a fantastic day!
Edit: I forgot to mention two things.
1st: It does not seem to charge the battary, I kniw this because I have another identical one though the battary works fine in the working one
2nd: My PC reads it as (something?)_dload, Sadly I do not have acess to a computer just yet. Thanks again
Any help.. please?
Khaled125 said:
Hello every one! so yesterday while doing nothing but leaving my phone on a markipilers youtube video, I see my screen go off I try to turn it back on and nothing happens. I tried power cycling and its still off, just not responding to anything, no sound no light no nothing. I tried then going to recovery mode but well... nothing happened. The only thing that actually makes any responses is when I connect it using a USB to my laptop, my laptop beeps, its not suposed to beep it is broken so is it bricked?
My device is a rooted Samsung galaxy s4 mini i19192 or so I hope it is.
I really hope that this is the right place to be redirected to assistant if not then Iam really sorry, thank you so much every one and have a fantastic day!
Edit: I forgot to mention two things.
1st: It does not seem to charge the battary, I kniw this because I have another identical one though the battary works fine in the working one
2nd: My PC reads it as (something?)_dload, Sadly I do not have acess to a computer just yet. Thanks again
Click to expand...
Click to collapse
probably QHSUSB_DLOAD, which is a hard brick, you might be able to fix with a debrick image
Sent from my Galaxy S4 Mini using XDA Labs
its in fact qshusb_dload but iam still a bit clueless on the reason or which method to solve. I read its because the cpu is trying to boot from the sd card and has something to do with something called emmac that is terrible in the s4 so I read three methods to solve
1- Just your method
2- Cooling the emmc?
and three, this
http://cellphonetrackers.org/qhsusb_dload-fix-qualcomm-soc.html
so Iam a bit distracted on what to even do or how to do it, any help would be apriciated plus any further notices about how to even avoid the problem
and thank you so much @IronRoo for your noticable contributions to these stuff!
Khaled125 said:
its in fact qshusb_dload but iam still a bit clueless on the reason or which method to solve. I read its because the cpu is trying to boot from the sd card and has something to do with something called emmac that is terrible in the s4 so I read three methods to solve
1- Just your method
2- Cooling the emmc?
and three, this
http://cellphonetrackers.org/qhsusb_dload-fix-qualcomm-soc.html
so Iam a bit distracted on what to even do or how to do it, any help would be apriciated plus any further notices about how to even avoid the problem
and thank you so much @IronRoo for your noticable contributions to these stuff!
Click to expand...
Click to collapse
Yes, the eMMC is prone to fail/corruption on our phones, at least I think. The eMMC is the internal SD memory. Hopefully yours is just corrupt.
The cooling trick is probably only good if there is a bad soldier joint on the chip and will probably only work a few minutes as the board will heat up once turned on
I would try the debrick file as that's probably the easiest. See also Valenti's post on other Samsung device, as better write up on one (Samsung Mega maybe?) as well as by the others who originally come up with the debrick idea to get a better idea of what to do.
I guess (without researching) the method in your link is the same principle as the debrick file but may work even if debrick doesn't work as not dependant on having a matching file from phone with same bootloader (???? I don't know as haven't looked into that method)
Also you can send phone away for jtag if nothing else works
Sent from my Galaxy S4 Mini using XDA Labs
IronRoo said:
Yes, the eMMC is prone to fail/corruption on our phones, at least I think. The eMMC is the internal SD memory. Hopefully yours is just corrupt.
The cooling trick is probably only good if there is a bad soldier joint on the chip and will probably only work a few minutes as the board will heat up once turned on
I would try the debrick file as that's probably the easiest. See also Valenti's post on other Samsung device, as better write up on one (Samsung Mega maybe?) as well as by the others who originally come up with the debrick idea to get a better idea of what to do.
I guess (without researching) the method in your link is the same principle as the debrick file but may work even if debrick doesn't work as not dependant on having a matching file from phone with same bootloader (???? I don't know as haven't looked into that method)
Also you can send phone away for jtag if nothing else works
Click to expand...
Click to collapse
Thats great! thank you. however can you give me a link to download that file / tutorial as iam not sure google would help me in that. second off I have no idea where Valenti's post either so that would just be fantastic if you can, Thanks again for every thing!
Khaled125 said:
Thats great! thank you. however can you give me a link to download that file / tutorial as iam not sure google would help me in that. second off I have no idea where Valenti's post either so that would just be fantastic if you can, Thanks again for every thing!
Click to expand...
Click to collapse
There are some debrick files here for some of the S4 Mini models (some have broken links but some still work, or find others on internet. This is also one of the thread started by @ValenteL
http://forum.xda-developers.com/showthread.php?t=2625628&page=10
Sent from my Galaxy S4 Mini using XDA Labs
IronRoo said:
There are some debrick files here for some of the S4 Mini models (some have broken links but some still work, or find others on internet. This is also one of the thread started by @ValenteL
http://forum.xda-developers.com/showthread.php?t=2625628&page=10
Click to expand...
Click to collapse
Wanderful, Thank you! should I mark this as solved?
IronRoo said:
There are some debrick files here for some of the S4 Mini models (some have broken links but some still work, or find others on internet. This is also one of the thread started by @ValenteL
http://forum.xda-developers.com/showthread.php?t=2625628&page=10
Click to expand...
Click to collapse
I have been searching for ever and still zero luck on finding either a way through the s4 mini nor the actual debrick file... all I could find was for the s3 all over, any help?
Khaled125 said:
I have been searching for ever and still zero luck on finding either a way through the s4 mini nor the actual debrick file... all I could find was for the s3 all over, any help?
Click to expand...
Click to collapse
Did you try the two debrick images in my post dated the 22nd March in the thread I posted above?
Actually I also pulled one from my phone after I read you can generate one from Cyanogenmod phones that will also work, I will post that on the above thread also a bit later.
Sent from my Galaxy S4 Mini using XDA Labs
IronRoo said:
Did you try the two debrick images in my post dated the 22nd March in the thread I posted above?
Actually I also pulled one from my phone after I read you can generate one from Cyanogenmod phones that will also work, I will post that on the above thread also a bit later.
Click to expand...
Click to collapse
Just found it, Though if your link would have directed to page 8 rather than 10 that would have been fantastic! I thought You ment the main post which also helped me alot. How ever do I really have to downoad monster legands to be able to download the foking file?
oh never mind, Just a damn ad
IronRoo said:
Did you try the two debrick images in my post dated the 22nd March in the thread I posted above?
Actually I also pulled one from my phone after I read you can generate one from Cyanogenmod phones that will also work, I will post that on the above thread also a bit later.
Click to expand...
Click to collapse
Oh and how do you flash that thing to recovery, How do you pull that debrick file? is really confusing me
And please pardon me if my questions are spammy or annoying, There are a whole lot of steps through it and neither google nor the forum seem to be answering it so I might just consult you for that.
From what I understand, You flash the debrick file to the sd card using this 32 bit sd flasher thing and then it just works because the booting files are on the sd card but it will not boot without it. So how can you fix the corrupted boot loader AND how can I restore my sd card back to normal, I have seen a video for it but he is using ubuntu and command lines and stuff.
Khaled125 said:
Oh and how do you flash that thing to recovery, How do you pull that debrick file? is really confusing me
Click to expand...
Click to collapse
The original post by @ValenteL was a file to generate a debrick image, but you need a working phone to use that.
People with phones that are already bricked have to get a debrick file from someone else. This debrick image must be put onto an 16Gig (some report success with 32gig) SD card that is formatted (so you will lose everything else on it) and then the phone will boot with it instead of internal mmc to get your phone going (you have to keep the SD in) so you can then recover data and also hopefully flash a new rom later so you don't need to always boot from SD.
Sent from my Galaxy S4 Mini using XDA Labs
IronRoo said:
The original post by @ValenteL was a file to generate a debrick image, but you need a working phone to use that.
People with phones that are already bricked have to get a debrick file from someone else. This debrick image must be put onto an 16Gig (some report success with 32gig) SD card that is formatted (so you will lose everything else on it) and then the phone will boot with it instead of internal mmc to get your phone going (you have to keep the SD in) so you can then recover data and also hopefully flash a new rom later so you don't need to always boot from SD.
Click to expand...
Click to collapse
Yes, that was what I understood already but thank you anyway! My question was How? on both creating the debrick file and restoring both sd card (too make it work as a readable card rather than a booting device if it does not already) and fix the phones internal memory without actually reseting the whole phone and if there are no way else to fix internal memory... to back up the whole thing.
thank you!
IronRoo said:
Did you try the two debrick images in my post dated the 22nd March in the thread I posted above?
Actually I also pulled one from my phone after I read you can generate one from Cyanogenmod phones that will also work, I will post that on the above thread also a bit later.
Sent from my Galaxy S4 Mini using XDA Labs
Click to expand...
Click to collapse
WANDEFUL! My phone actually viperated and showed color!
however.. it gives this on a black screen.
boot recovery
check boot partitions
copy from t flash
boot recovery
write 139008
reboot
and obviously reboots, thoughts?
My last two posts are the most important now, if you or any one else can answer that would be fantastic!
some notes: after searching the thing does not mention emmc nor odin at all like for some others with the same issue... just this plain text.
I had upgraded my android version to 4.4.2 not 4.2.2 so I assume that is important, thanks again and please answer as soon as you can as that would be great! thank you for every thing @IronRoo
Khaled125 said:
My last two posts are the most important now, if you or any one else can answer that would be fantastic!
some notes: after searching the thing does not mention emmc nor odin at all like for some others with the same issue... just this plain text.
I had upgraded my android version to 4.4.2 not 4.2.2 so I assume that is important, thanks again and please answer as soon as you can as that would be great! thank you for every thing @IronRoo
Click to expand...
Click to collapse
I think the important thing is the bootloader (& pit must be the same) that if I recall was updated from the version you mention to ver 2. So you need a debrick with the ver 2 bootloader. (but I am not 100% sure about this, only read some stuff last year) My phone BL is ver 1
a guy on the below Mega thread with an I9195 did get a stop further by repeating multiple times
http://forum.xda-developers.com/showthread.php?t=2600976&page=4
But still didn't fix phone fully
read next few pages, one guy used freeze fix white partial success, might be useful if you want to get data off phone.
Also another link that may offer help
but probably your emmc is bad, is my guess
gotta go now, work calls
Sent from my Galaxy S4 Mini using XDA Labs
IronRoo said:
I think the important thing is the bootloader, that if I recall was updated from the version you mention to ver 2. So you need a debrick with the ver 2 bootloader. (but I am not 100% sure about this, only read some stuff last year) My phone BL is ver 1
a guy on the below Mega thread with an I9195 did get a stop further by repeating multiple times
http://forum.xda-developers.com/showthread.php?t=2600976&page=4
But still didn't fix phone fully
read next few pages, one guy used freeze fix white partial success, might be useful if you want to get data off phone.
Also another link that may offer help
but probably your emmc is bad, is my guess
gotta go now, work calls
Sent from my Galaxy S4 Mini using XDA Labs
Click to expand...
Click to collapse
Thats great! good luck at your work, when you are back though I need to tell you this
I have another device of the exact same model that is kikkat not rooted (kitkat will have bootloader version 2 right?) if only I knew how to get the file out and then do all the stuff again, ill keep searching since you are at work now, will keep you updated. please help about it though if you can*
so if someone say for example has android 5 on an s4 mini, he will never get his phone back to work unless some one made a debrick file for it? if the previous statments were true?
My questions are:
Extract that file from the other phone, if I managed to answer it ill tell you.
To get my SD card back to work and fix my emmc
Iam not giving up on my emmc yet though, iam sure there is a way to solve it, if not then how to fix that failed emmc?
thanks again!