Develop Bugs

Yet another bricked A100 - Need to restore locked bootloader

So, I'm on vacation last week, watching a movie on my tablet when it starts to become very laggy. After a minute or two, it locks up completely. Just like everyone else, I reboot it to find that it doesn't get any farther that the green Acer logo. I was running CWM recovery, but nothing seems to work... every command gives me an error. After reading this thread by NighPlayer32: http://forum.xda-developers.com/showthread.php?t=1749967 I switch to TWRP recovery and am able to push an update.zip to the internal sdcard, but still can't install it because none of my partitions will mount.
At this point, I've given up on getting this thing to work. I can get into fastboot and recovery, but beyond that I've had no luck and I'm guessing it's fault hardware (EMMC?). It was purchased in December, so it should be under warranty but it has a unlocked bootloader, which will cause some problems if I send it to Acer. Does anyone know of a way to restore it to a stock bootloader via fastboot or recovery? OR... has anyone with missing partitions been able to load an update.zip successfully?
Any help would be GREATLY appreciated!
Thanks in advance!

ED2O9 said:
So, I'm on vacation last week, watching a movie on my tablet when it starts to become very laggy. After a minute or two, it locks up completely. Just like everyone else, I reboot it to find that it doesn't get any farther that the green Acer logo. I was running CWM recovery, but nothing seems to work... every command gives me an error. After reading this thread by NighPlayer32: http://forum.xda-developers.com/showthread.php?t=1749967 I switch to TWRP recovery and am able to push an update.zip to the internal sdcard, but still can't install it because none of my partitions will mount.
At this point, I've given up on getting this thing to work. I can get into fastboot and recovery, but beyond that I've had no luck and I'm guessing it's fault hardware (EMMC?). It was purchased in December, so it should be under warranty but it has a unlocked bootloader, which will cause some problems if I send it to Acer. Does anyone know of a way to restore it to a stock bootloader via fastboot or recovery? OR... has anyone with missing partitions been able to load an update.zip successfully?
Any help would be GREATLY appreciated!
Thanks in advance!
Click to expand...
Click to collapse
Sorry to hear another one died. We've attempted a few methods but none have so far worked. If you can still push to internal SD you can try to push the a100 boot loader in recovery via adb but you'll lose cwm and fast boot so it will still go back with a custom recovery. There is a stock recovery image around which can also be flashed in recovery via abd which should put it back to normal aside from any custom ROM you may be running. If you're interested I'll try to find the stuff for you and setup some instructions. It'll be tomorrow though I'm about to head to bed.
Tapatalked from my A100 - CM10

I'm scared
How can I prevent my own a100's death
Sent from my LG-P500 using xda premium

-DarkKnight- said:
I'm scared
How can I prevent my own a100's death
Sent from my LG-P500 using xda premium
Click to expand...
Click to collapse
Hardbricks you can't , its faulty emmc, you either have it or you don't.
Tapatalked from my A100 - CM10

-DarkKnight- said:
I'm scared
How can I prevent my own a100's death
Sent from my LG-P500 using xda premium
Click to expand...
Click to collapse
me too lol, i just have rooted my tab but i preffer to not touching the bootloader.
---------- Post added at 05:19 PM ---------- Previous post was at 05:17 PM ----------
pio_masaki said:
Hardbricks you can't , its faulty emmc, you either have it or you don't.
Tapatalked from my A100 - CM10
Click to expand...
Click to collapse
hey pio! sorry but my english is a lil short, i dont understand that part, what do u mean?

pio_masaki said:
If you're interested I'll try to find the stuff for you and setup some instructions.
Click to expand...
Click to collapse
Thanks! Like I said, I've tried everything to get a ROM to load and all I get is "can't mount" failures, so I'm assuming that it need to go back to Acer. If you could give me any tips to restore it to the stock bootloader, I'd really appreciate it. There was a thread I found that had a link to a LOCKED bootloader restore script, but the link was dead.

Deshabilitado said:
me too lol, i just have rooted my tab but i preffer to not touching the bootloader.
---------- Post added at 05:19 PM ---------- Previous post was at 05:17 PM ----------
hey pio! sorry but my english is a lil short, i dont understand that part, what do u mean?
Click to expand...
Click to collapse
emmc is the part of the device where the storage is, everything from recovery, bootloader, system, data, internal sd, etc, are all on this chip, if it's damaged or faulty, you can't use that portion of the the memory. The first sign of it failing generally seems to be laggy, slow running, followed by a freeze. Then you are forced to hard reboot, and then you have problems of any partitions mounting.
@ED209 - I'll see if I have some time to hunt this stuff down, although the script pack that zeronull has for unlocking the bootloader also has the a100 and a revert script to restore the stock locked bootloader. The script may or may not work in recovery as it was meant to run from android, but it should be easy enough to either adapt to recovery, or just manually issue the commands over adb in recovery. The PC side will push the bootloader.blob and the script for the tablet side, then run the script on the tablet which will do the bootloader flash, then reboot, however we don't want it to reboot until you have stock recovery or you get locked out.

I know that flashing update.zip fails due to corrupt or missing partitions, but do you think restoring a backup package might work? I guess I'd need a stock backup image, push it to the internal sdcard and just try to run a restore from TWRP. I have a feeling it won't get any farther than the update.zip, but at this point I'll try anything. Do you remember ever seeming if someone posted a link to a stock restore .img?
Beyond that, is it possible to recreate the partitions through ADB?
Thanks again...

ED2O9 said:
I know that flashing update.zip fails due to corrupt or missing partitions, but do you think restoring a backup package might work? I guess I'd need a stock backup image, push it to the internal sdcard and just try to run a restore from TWRP. I have a feeling it won't get any farther than the update.zip, but at this point I'll try anything. Do you remember ever seeming if someone posted a link to a stock restore .img?
Beyond that, is it possible to recreate the partitions through ADB?
Thanks again...
Click to expand...
Click to collapse
There is parted in custom recovery which would in theory work, but its never been attempted before. I'm supposedly getting a brick sent to me (not 100% if it will happen or not) and it's one of the many things I plan to try.
Flashing and restoring will fail since the partitions can't be accessed.
A restore image will fail for the same reason.
I have tons of ideas but until I get ahold of a brick its all purely theory and speculation and until I'm sitting there looking at it I can't figure out how to do it, its weird I know but I can't just bust out what I want to do, I have to be doing it.....
Tapatalked from my A100 - CM10

I suggest you erase all evidence of it being rooted/modded then your warrenty is ok
Do you have a method to check if it is there so i can pretend to wipe everything and brick it, while pretending it wasn't my fault while my warrenty is still here?

-DarkKnight- said:
I suggest you erase all evidence of it being rooted/modded then your warrenty is ok
Do you have a method to check if it is there so i can pretend to wipe everything and brick it, while pretending it wasn't my fault while my warrenty is still here?
Click to expand...
Click to collapse
A pretend wipe is obvious. And what you just suggested isn't exactly honorable, returning an item as broken when its not. And wiping isn't bricking, during my time making the black hole tools I soft bricked at least 20 times, full out wrecked corrupted effed up partitions, always came back. You can't invoke this brick, you have it or you don't.
As for wiping it clean of mods, that is what we were discussing in this thread already. Its also kinda shady as the warranty expires when you root and again when you unlock, and yet again with the custom recovery and also the custom ROM. However it is a straight hardware failure, an issue Acer knows of. I would suggest calling or maybe chatting on their site, I'm pretty sure another brick victim is getting a replacement even rooted and unlocked.
As for checking, no I don't know of a way. The brick thread had aimed to condense all known information to try to isolate it to any build dates or anything specific, but not enough information was provided to do it. For awhile I thought cm9 was safe, but recently a brick occurred on cm9 as well.
I would advise your next step be to visit the Acer site, try to chat with a rep and ask about the hardware failure and your options with it rooted. You may get the same deal the other user did and just pay shipping.
Tapatalked from my A100 - CM10

I wouldn't send it in under warranty coverage if I felt that the issue was due to improper modifications that I made to the device. I'm typically pretty meticulous about following directions, and I was running the stock ROM. I had unlocked the bootloader and added CWM for back-up purposes (which I never got around to because I needed to make space on my SD card), and the lock-up occurred when I was watching a video clip I recorded that afternoon. Based on the severity of the "brick", I'm fairly certain that it's a hardware issue. I'm hearing people mention $150 repair bills, and I'd hate to pitch this tablet because of a EMMC failure, which appears to be increasingly common on this device.

ED2O9 said:
I wouldn't send it in under warranty coverage if I felt that the issue was due to improper modifications that I made to the device. I'm typically pretty meticulous about following directions, and I was running the stock ROM. I had unlocked the bootloader and added CWM for back-up purposes (which I never got around to because I needed to make space on my SD card), and the lock-up occurred when I was watching a video clip I recorded that afternoon. Based on the severity of the "brick", I'm fairly certain that it's a hardware issue. I'm hearing people mention $150 repair bills, and I'd hate to pitch this tablet because of a EMMC failure, which appears to be increasingly common on this device.
Click to expand...
Click to collapse
That wasn't aimed at you, no worries. I still suggest you go chat with Acer on their site, calling charges you, and see what they say about the tablet in its current state.
Tapatalked from my A100 - CM10

ED2O9 said:
I wouldn't send it in under warranty coverage if I felt that the issue was due to improper modifications that I made to the device. I'm typically pretty meticulous about following directions, and I was running the stock ROM. I had unlocked the bootloader and added CWM for back-up purposes (which I never got around to because I needed to make space on my SD card), and the lock-up occurred when I was watching a video clip I recorded that afternoon. Based on the severity of the "brick", I'm fairly certain that it's a hardware issue. I'm hearing people mention $150 repair bills, and I'd hate to pitch this tablet because of a EMMC failure, which appears to be increasingly common on this device.
Click to expand...
Click to collapse
Well 150 is less than the original price
And pio said its the hardware fault its either broken or not broken so modding wouldn't do anything
Sent from my LG-P500 using xda premium

fastboot oem unlock?

droc.noles said:
fastboot oem unlock?
Click to expand...
Click to collapse
What does that have to do with anything in this thread?
Tapatalked from my Galaxy S II - CM10

Probably trolling
Sent from my Full AOSP on a100 using XDA Premium HD app

pio_masaki said:
What does that have to do with anything in this thread?
Tapatalked from my Galaxy S II - CM10
Click to expand...
Click to collapse
Misinterpreted what OP was trying to get done, don't mind me.
I had an issue where I was locked out due to ignorantly running the revert to locked bootloader script. Boot verified failed, recovery verified failed. fastboot oem unlock got me back to the toggle between lock and unlock. My apologies, carry on.

droc.noles said:
Misinterpreted what OP was trying to get done, don't mind me.
I had an issue where I was locked out due to ignorantly running the revert to locked bootloader script. Boot verified failed, verified failed. fastboot oem unlock got me back to the toggle between lock and unlock. My apologies, carry on.
Click to expand...
Click to collapse
Ah ok. And glad you got that squared away, that info may be useful should that occur again.
Tapatalked from my A100 - CM10

pio_masaki said:
That wasn't aimed at you, no worries. I still suggest you go chat with Acer on their site, calling charges you, and see what they say about the tablet in its current state.
Tapatalked from my A100 - CM10
Click to expand...
Click to collapse
In looking back over the brick threads, I realized that you are the member that posted the scripts to return the tablet to a locked bootloader. The link is dead, so I was wondering if you could repost it.
Thanks!

[RESOLVED] Formatted Factory - Lost IMEI - Please Help!

Hi, apparently some genius developing CWM decided it would be fun to allow the factory partition to be formatted with the newest versions of CWM (I'm on 6.0.4.6). Well guess what, I managed to format it on my GNex (it's quite easy to do actually).
Anyways, I've lost my IMEI data and unable to access mobile network (data connectivity is fine, however, surprisingly). Somebody please help me restore my IMEI because I don't have a nandroid backup either.
Thanks a lot!

Deleted, did a search on IMEI and found a bunch of threads. Reading them now...

pherder said:
Deleted, did a search on IMEI and found a bunch of threads. Reading them now...
Click to expand...
Click to collapse
Paul how did you manage to mess up your phone? Was it the same way I did? The thing is, all is not lost, I'm absolutely certain of that. It's not a brick until it absolutely and completely refuses to power up...
@osm0sis, can you please help me out here? I know there was even an IMEI changing tool but most probably considered illegal or something by the "powers that be" and hence removed most likely. I just need my original phone IMEI back, that's all. Thanks a lot!

rahimali said:
Paul how did you manage to mess up your phone? Was it the same way I did? The thing is, all is not lost, I'm absolutely certain of that. It's not a brick until it absolutely and completely refuses to power up...
@osm0sis, can you please help me out here? I know there was even an IMEI changing tool but most probably considered illegal or something by the "powers that be" and hence removed most likely. I just need my original phone IMEI back, that's all. Thanks a lot!
Click to expand...
Click to collapse
I think I screwed up and flashed my phone with the wrong image (LTE instead of CDMA) that wiped the factory info and all the attempts I have tried do not do anything to get the phone back. I have a nice tablet that just upgraded to 4.3 via WiFi since it isn't on the Verizon network.
Paul

pherder said:
I think I screwed up and flashed my phone with the wrong image (LTE instead of CDMA) that wiped the factory info and all the attempts I have tried do not do anything to get the phone back. I have a nice tablet that just upgraded to 4.3 via WiFi since it isn't on the Verizon network.
Paul
Click to expand...
Click to collapse
My maguro CWM thread has all the info you need explained several times. Check it out.

osm0sis said:
My maguro CWM thread has all the info you need explained several times. Check it out.
Click to expand...
Click to collapse
i have gone through your cwm thread. it's suggested taking it to a shop and getting it fixed with spt box or something. unfortunately, i can't do that because nobody in my location has anything even remotely similar to one of those. apart from that, i've done everything i could think of, flashed radios, flashed stock samsung rom, flashed google factory images. what else would you suggest?
i don't have a prior nandroid either

Resolved
Problem solved. Took it to repair shop and got it fixed. Everyone that helped or tried to help, thanks a lot! Mods please close thread, thanks!

I was thinking more along the lines of restoring a backup and grabbing what you need to fix Factory from Radio, which was detailed a couple of times.
Glad you got it fixed, nonetheless. :good:

rahimali said:
Problem solved. Took it to repair shop and got it fixed. Everyone that helped or tried to help, thanks a lot! Mods please close thread, thanks!
Click to expand...
Click to collapse
Did you ask them how they fixed it?? we need to know so we can help others..:--))

osm0sis said:
I was thinking more along the lines of restoring a backup and grabbing what you need to fix Factory from Radio, which was detailed a couple of times.
Glad you got it fixed, nonetheless. :good:
Click to expand...
Click to collapse
i didn't have a nandroid, nothing in factory since i had wiped it accidentally via the new cwm's new ""feature". i didn't like twrp until now but i ain't budging from it now that cwm has screwed me up so bad!
buhohitr said:
Did you ask them how they fixed it?? we need to know so we can help others..:--))
Click to expand...
Click to collapse
the guy connected it to a couple of external devices which in turn were connected to his pc, i guess one of them was something along the lines of an spt box, the other thing looked like a miniature spaceship, so maybe ET was involved in fixing it as well...

Not CWM's fault, though I definitely understand your sentiment. But "with great power.."
I make damn sure I know what I'm pressing Yes on when I'm wiping.

osm0sis said:
Not CWM's fault, though I definitely understand your sentiment. But "with great power.."
I make damn sure I know what I'm pressing Yes on when I'm wiping.
Click to expand...
Click to collapse
with great power comes great tragedy
anyways, I was just browsing through my phone with root explorer and with twrp's file manager and surprisingly there's no efs folder there! is that normal?
i've taken a twrp nandroid backup to include efs as well but i'm thinking to take a raw backup as well as described here. i've also copied the /factory and /data/radio folders.
i was wondering whether flashing a stock samsung ROM might result in the creation of the efs folder? on yakju 4.2.2 stock google image right now...

Nah efs is the partition but it's mounted to /factory :good:

osm0sis said:
Nah efs is the partition but it's mounted to /factory :good:
Click to expand...
Click to collapse
That's great thanks!., I'll clean flash 4.3 yakju in a day or two and see if the IMEI sticks after the wipes. Unfortunately, I wasn't able to backup using EFS Commander or the terminal/shell commands (got error both ways) so I'm hoping the TWRP backup (without MD5) and manual file copy should be sufficient insurance...

My phone is bricked?

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!

Twrp asking for password after flashing 4.1.0 full zip

i have flashed the full rom.zip on latest twrp . now when i boot into recovery, twrp is asking to enter password ?? what should i need to do ?? i guess phone got encrypted .. How can i get my files back ???
when i boot the phone, its shows encryption unsuccessful. Encryption was interupted and cant complete. As a result, the data on your phone is no longer accessible.
kindly tell me how can i get my data back and bypass the password which is asking on twrp ?

Just Hit Forgot Password ...

M.Dinesh said:
Just Hit Forgot Password ...
Click to expand...
Click to collapse
if i do so , i need to wipe my internal storage.

Dirty flash OOS 4.0.3 and see if it can decrypt your files.

I had the same and I have to clear data. I don't know how solve this.

HatRiGt said:
i have flashed the full rom.zip on latest twrp . now when i boot into recovery, twrp is asking to enter password ?? what should i need to do ?? i guess phone got encrypted .. How can i get my files back ???
when i boot the phone, its shows encryption unsuccessful. Encryption was interupted and cant complete. As a result, the data on your phone is no longer accessible.
kindly tell me how can i get my data back and bypass the password which is asking on twrp ?
Click to expand...
Click to collapse
Hi,
I'm sorry to hear that. When Open Beta 12 came out I had the same problem. After several days, despite all help that I got, I was forced to clean storage and make a clean flash.
Did you do a backup? If yes, did you transfer it to your PC?
If at least one answer is 'no' I've got bad news for you
Losing your personal data is never fun...
---------- Post added at 13:52 ---------- Previous post was at 13:27 ----------
https://forum.xda-developers.com/showpost.php?p=71240249&postcount=30
https://forum.xda-developers.com/showpost.php?p=71241372&postcount=2426
https://forum.xda-developers.com/oneplus-3/how-to/guide-mega-unbrick-guide-hard-bricked-t3405700
These are three most important hints I've been given.
Keep in mind that you should try a lot of times and don't give up! Maybe there's some way to at least recover your files that hasn't been discovered yet. Good luck
PS: If you can't transfer big files (like a ROM) via adb, then there's a solution:
https://forum.xda-developers.com/showpost.php?p=71246192&postcount=59

youknownothing said:
Hi,
I'm sorry to hear that. When Open Beta 12 came out I had the same problem. After several days, despite all help that I got, I was forced to clean storage and make a clean flash.
Did you do a backup? If yes, did you transfer it to your PC?
If at least one answer is 'no' I've got bad news for you
Losing your personal data is never fun...
---------- Post added at 13:52 ---------- Previous post was at 13:27 ----------
https://forum.xda-developers.com/showpost.php?p=71240249&postcount=30
https://forum.xda-developers.com/showpost.php?p=71241372&postcount=2426
https://forum.xda-developers.com/oneplus-3/how-to/guide-mega-unbrick-guide-hard-bricked-t3405700
These are three most important hints I've been given.
Keep in mind that you should try a lot of times and don't give up! Maybe there's some way to at least recover your files that hasn't been discovered yet. Good luck
PS: If you can't transfer big files (like a ROM) via adb, then there's a solution:
https://forum.xda-developers.com/showpost.php?p=71246192&postcount=59
Click to expand...
Click to collapse
Lost ol my personal data bro . ??
Tried every method .but nothing worked .
Somehow google photos has backup of my few photos .
But lost app data's n important files completely .??

HatRiGt said:
Lost ol my personal data bro .
Tried every method .but nothing worked .
Somehow google photos has backup of my few photos .
But lost app data's n important files completely .
Click to expand...
Click to collapse
I'm really sorry for your loss. But at least some photos have survived
Well, we have learned our lesson - always do a backup and keep it in a safe place.
Cheers

youknownothing said:
I'm really sorry for your loss. But at least some photos survived
Well, we have learned our lesson - always do a backup and keep it in a safe place.
Cheers
Click to expand...
Click to collapse
Hmm.. OK bro.. ?

I need a help-Mi Max bricked-Need Debrick.img

Hello users, I have my Mi Max Hydrogen 3/32 bricked since time ago, I tried all the threads out there to revive my device, as a hard bricked no fastboot, no download mode responsive, of course no recovery.
I guess that bootloader is messed due to a bad flashing of a file uploaded by error.
I found a method, idea is to force device to enter to download mode restoring bootloader or turn on responsive again to allow a new flashing cycle.
I´m now using a Redmi 5 Plus and I did this method to prevent any trouble in the future, one never knows.
If some user wants to help just I need that this zip should be flash it through recovery and the file just will dump/backup the first 125MB aproximately of system and it will kept in sdcard with the name of debrick.img and kindly can upload it to the cloud. This will be greatly appreciated and I hope that also can help to other users with same/similar issue now. If things go fine I´ll explain in details to accomplish that
View attachment Partial_Sys_Dump_for_debrick.zip

Reserved.
A brief explanation:
I have found this tutorial https://forum.xda-developers.com/showthread.php?t=2369125 (applying concerning to this model) among several of the same type, the idea behind this is that in a cell phone bricked because the bootloader is damaged and trying to boot it does not find that partition readable, so burning/writing the first lines of the operating system in a sdcard, then putting it in the device then it will search these files to try to boot. If the emmc/motherboard is not totally damaged or the measurement of the files is sufficient for it to do it then after this it will come to turn on, stay or spend a little more of the bootlogo and that will indicate that it is in a condition of flashing all the system files again through the fastboot or MiFlash to make it functional back and bring it back to life.
In my case I have damaged the buttons, the back cover opened in the repair shop and this may have a negative influence to try it properly, therefore I could not recover it yet, or the size of the files is not completely sufficient since the tutorial is based on a Galaxy S3 with a memory lower than This device or plainly emmc is definitely damaged.
However, each case is different and I think that this explanation can help others who are in similar cases.

There you go: deleted
Please, explain what you are doing even if it didn't work.

nijel8 said:
There you go: hydrogen_3-32_debrick.img
Please, explain what you are doing even if it didn't work.
Click to expand...
Click to collapse
A great thanks, my device has sleeping maaaany time. I will try it and I´ll report even if this doesn´t work.

nijel8 said:
There you go: hydrogen_3-32_debrick.img
Please, explain what you are doing even if it didn't work.
Click to expand...
Click to collapse
If you want to give me a second chance, I explained the idea behind this. It´s based on a device the half of ram/rom than this so I think that maybe it´s needed at least 200 mb to find working files to let it run. i´m not sure that if you are running in a custom rom and non miui rom it works anyway.
Your help is greatly appreciated and I recommend any user that can keep the zip dumper and Debrick image in a safe place just in case in the future could need it.
View attachment Partial_Sys_Dump_for_debrick-200MB.zip

hydrogen_3-32_debrick.img
Don't think this is going to work...

nijel8 said:
hydrogen_3-32_debrick.img
Don't think this is going to work...
Click to expand...
Click to collapse
Why do you think so? difference in sizes between 128 and 200 doesn´t matter? or plainly this method can´t work in this device in your opinion? I saw this method in other non Samsung devices like Lenovo totally bricked and cause is a similar device I thought that maybe..... and of course one don´t want resign.
Google sent a confirmation to grant access to your file. Thanks for support.