[Completed] need help with my soft bricked android!! - XDA Assist

Hello:
I am fairly new to the android world and rooting, for a few months i've been tweaking with my phone and what not, got into a few situations that i was able to recover from, but this time i was messing with TWRP's boot menu and accidentally deleted the OS system, but for some reason I cant pull the image i flashed and saved on my sd card, i was able to do so before but not this time, long story short I would like to know if i can buy the same phone again which is a zte warp sync with kit kat 4.4.2 and root it, create an image or zip file of it and save it on a sd card and then load it into the soft bricked phone through TWRP's boot and fix the soft bricked phone, in my mind it seems like it would work but i really dont know if its possible, or if anyone has attempted it before. before i go and buy another identical phone

t3rice said:
Hello:
I am fairly new to the android world and rooting, for a few months i've been tweaking with my phone and what not, got into a few situations that i was able to recover from, but this time i was messing with TWRP's boot menu and accidentally deleted the OS system, but for some reason I cant pull the image i flashed and saved on my sd card, i was able to do so before but not this time, long story short I would like to know if i can buy the same phone again which is a zte warp sync with kit kat 4.4.2 and root it, create an image or zip file of it and save it on a sd card and then load it into the soft bricked phone through TWRP's boot and fix the soft bricked phone, in my mind it seems like it would work but i really dont know if its possible, or if anyone has attempted it before. before i go and buy another identical phone
Click to expand...
Click to collapse
Hi t3rice
Thanks for using XDA Assist.
Could you please state the Manufacturer & Model of your device so we could better approach your issue guiding you to the appropriate experts?
I will be waiting for your reply within the next 2 days.
Nice regards.
.

Related

Can my Nexus be fixed?

Hello all
I suspect that either my Nexus has a hardware fault (internal memory) or I bricked it somehow.
For the past few weeks the phone has been getting stuck on the google boot screen quite a lot - It takes several attempts
to start up each time so I've been trying to keep the battery from running down.
The other day while I was attempting to switch roms I put the stock img on my SD card but when I went to flash it CWM
couldnt mount my (internal) SD Card. Senior forum member Caliban2 suggested that it could be my recovery so I installed CWM 6.0.0.7 non-touch using fastboot and, like magic, the phone started up -though I suspect this may have been luck.
I rebooted the phone out of curiosity and it got stuck on the google boot screen - no amount of battery pulling and restarting could coax
it back to life, so I went into CWM again to discover that it could not mount the SD Card, I was getting the 'cannot mount' and 'E:Unable to open ums lunfile(no such file or directory)' error messages. My windows 7 PC could see the phone but said that their was non memory inserted. Out of curiosity I installed CWM 5.0.2.0 but that produced the same results.
So now my phone appears dead, is the internal memory or something related to it is broken? I have seen things on here about using an unbricking tool in Debian Linux or flashing stock using odin but I confess that I have not tried these solutions and don't fully understand them (yet).I wussed out and dropped the phone into a local repair workshop, I imagine they will be trying these same steps themselves and they say it will take them a few days to get back to me.
My problem is that I need a phone for work and I gave my backup phone (HTC Hero) to my dad recently. Should I just take the plunge
and go out today and buy a new phone? Or is there a reasonable chance that these guys can fix my nexus s, or that I might be able to?
I'm a relative 'noob' at this so I thank you all for your advice in advance, it's much appreciated.
Derek
Do a search for flashing fastboot images. Download the 4.0.4 fastboot image from google and flash it as directed through fastboot. This may sort out your problems.
Afterward, if necessary, format the /sdcard too. I would do this afterward so that maybe you can get a backup of all the stuff on it before it's gone forever.
Thanks, will do. It's in the shop at the moment, I suspect this is probably what they're doing now.
Perhaps subconsciously I'm just looking for someone to tell me it's irreparable so I can rush out
and pick up a Galaxy Nexus.
Harbb said:
Do a search for flashing fastboot images. Download the 4.0.4 fastboot image from google and flash it as directed through fastboot. This may sort out your problems.
Afterward, if necessary, format the /sdcard too. I would do this afterward so that maybe you can get a backup of all the stuff on it before it's gone forever.
Click to expand...
Click to collapse
Hey Harbb
Just wanted to give you an update on this, got it back from the shop who said they would need to send it to Samsung for a hardware repair, didn't expect it to work but fastbooted the stock bootloader, radio and image to the device and it's now working!
I've already moved onto a Galaxy Nexus on contract but at least now I can make a bit of money back off my old phone.
Thanks again for the advice
Derek
Harbb said:
Do a search for flashing fastboot images. Download the 4.0.4 fastboot image from google and flash it as directed through fastboot. This may sort out your problems.
Afterward, if necessary, format the /sdcard too. I would do this afterward so that maybe you can get a backup of all the stuff on it before it's gone forever.
Click to expand...
Click to collapse

B63M bricked?

Hi There,
Please forgive me I am a complete novice when it comes to Android phone.
I have a chinese Dual sim phone that I have routed with superoneclick. I have put clockworks recovery on it with rom manager as I was trying to create a copy of the ROM. I also installed Droid X Recovery Bootstrap, however in droid x I pressed the fix permission option and the phone started changing permissions everywhere and now my phone wont start. It keeps booting up in a loop and I cannot get to the recovery to wipe the memory and start again
What SOC does the device use?
If its Allwinner based, you could boot from mmc or reflash with livesuit.
21ss, thank you for the reply.
Sorry my friend, I have no idea what you mean by What SOC does the device use?
You say that you can boot from the mmc slot, please tell how and with what software.
Never heard of livesuit.
I have attached a word document in rar of the ebay item that I purchest.
Any help that you can give me would be very much appreciated.
At the moment I have a paper weight.
Regards chunky2.
similar problem /
chunky2 said:
21ss, thank you for the reply.
Sorry my friend, I have no idea what you mean by What SOC does the device use?
You say that you can boot from the mmc slot, please tell how and with what software.
Never heard of livesuit.
I have attached a word document in rar of the ebay item that I purchest.
Any help that you can give me would be very much appreciated.
At the moment I have a paper weight.
Regards chunky2.
Click to expand...
Click to collapse
Sir
i have a dual sim android 2.3.4 chineese mobile with brand name ilus
i have the same problem after rooting the phone , i opened ROM MANAGER and when clicked for backup , it asked for clockworkmod recovery and searched for the models , as i didnt find my model , i scrolled any other options, i found fix permission , when i clicked it permissions were altered and asked me to boot and when i went for boot the phone stopped booting and is in boot loop
Kindly help me how to recover the phone , as i dont have the custom rom
nvksrinivas
Hey guys the good thing about this phone is that you cant brick it, it cant be hard bricked easily... but I suggest you go to this discussion and find possible solutions, I had same issue and even tho I never managed to fully sort the issue, its because of my laziness... I could if I wanted, I managed to get it to a position I can use it and I have been using it like so for months now... here is the link http://forum.xda-developers.com/showthread.php?t=1618775&page=3

Grand X Max Z787 Stuck on Recovery Screen

Hello I am new to the forums and even though I've rooted a phone once (Anyone remember the HTC Incredible?) I've fallen out of the loop so to speak. Here is the situation.
I have a friend who is contently attempting to root phones. And he gave me the Grand X Max Z787, after he soft bricked it. He now has a Plus. After weeks of looking and some frustration on my part.
Here's what I now know he did, he was using a program called KingRoot and after it said success it booted to the recovery screen where it stays.
Here is what I've tried, factory reboot wiping data.
I've tried sideloading a Rom.rar I found in another thread. Side load doesn't work at all, and it's just this phone.
So I've tried loading different packages through the sd card. It says they're corrupt (Which it seems is correct when checking the information to the site it doesn't match)
So do I just need a stock copy of the OS or is there something else I can do? He said he didn't make a backup which isn't surprising to me at all. However I'm currently using a windows phone and need an android phone and would like to take advantage of this if possible. Also as most probably know when trying to load from the SD Card only .zip files show up. It was on the stock for a ZTE Grand X Max with cricket. So if someone has that backup and it's what I need (at least that's what I think, thank you in advance.) If this post is in the wrong place please move it to the right place or tell me where to place it. Thank you.

[Completed] Cant seem to find a way to boot recovery my ''Clone S7'' after reboot. :(

I will be as specific as I can in order to save time
So I was in need of a cheap phone and always liked the look of the S7 since release. It came today but there was very little internal memory so I decided to root the device via ''Kingo Root'' in order to install an app called FolderMount. The app was meant to merge my SD card memory with my Internal Memory allowing me to install apps without a problem. As far as I can tell the root stage went fine, it said successful, rebooted and SuperSU worked a treat.
When I installed FolderMount it claimed the patch it applied was successful and my phone just needed to reboot in order to apply. So I rebooted and then it was stuck on the boot logo :crying: I have tried every combination to boot it into recovery in order to do a hard reset but nothing seems to work. No matter what button combination I seem to use the device to reboots, I have searched the all over the web for a solution but because it is a clone phone and its origins are unclear finding a relevant solution has being a nightmare.
So I have decided to turn to you fine folks in a hope someone could point me in the right direction. I will post everything about the phone I know below and if anybody has some suggestions that would be great.
Thanks guys
The phone is an HDC S7 - I can't post a link due to my account limitations.
Danny1231732 said:
I will be as specific as I can in order to save time
So I was in need of a cheap phone and always liked the look of the S7 since release. It came today but there was very little internal memory so I decided to root the device via ''Kingo Root'' in order to install an app called FolderMount. The app was meant to merge my SD card memory with my Internal Memory allowing me to install apps without a problem. As far as I can tell the root stage went fine, it said successful, rebooted and SuperSU worked a treat.
When I installed FolderMount it claimed the patch it applied was successful and my phone just needed to reboot in order to apply. So I rebooted and then it was stuck on the boot logo :crying: I have tried every combination to boot it into recovery in order to do a hard reset but nothing seems to work. No matter what button combination I seem to use the device to reboots, I have searched the all over the web for a solution but because it is a clone phone and its origins are unclear finding a relevant solution has being a nightmare.
So I have decided to turn to you fine folks in a hope someone could point me in the right direction. I will post everything about the phone I know below and if anybody has some suggestions that would be great.
Thanks guys
The phone is an HDC S7 - I can't post a link due to my account limitations.
Click to expand...
Click to collapse
Greetings!
Thank you for using XDA Assist.
I recommend you post your question in this friendly help thread:
http://forum.xda-developers.com/showthread.php?t=2259645
There's not much support for cloned devices on XDA but someone may be able to help you there.
Good luck!

Hard bricked

I just hard bricked my phone, and I'm hoping I can try to get it working again.
I have made backups using flashfire in the past. (I had a few different backups I made).
Prior to getting hard bricked, I was running the PIA firmware, but I was trying to restore from a backup that I had through flash fire, and due to a total rookie move I ended up restoring (or attempting to) restore to a PG1 unintentionally, and well now I can't do anything.
I think I may have a jig at home from a previous samsung phone (I believe an S3), would that work for my S7?
I also came across this thread: http://forum.xda-developers.com/showthread.php?t=2476353
Would that work for me?
I have a macbook pro I can use terminal with, I have a microSD card and reader, and I already have the stock PIA rom on my hard drive.
Is there hope still?
Right now regardless of what key combination I hold down my phone has a black screen.
Any help would greatly be appreciated.
Thanks in advance!
If you can't get into download mode then you don't have much to lose by trying what the other thread suggested.
@sacnotsack, thanks for the response, and that is my intention, however I am missing 1 crucial part to that thread and that is the debrick.img
Can someone with the PIA (G930TUVU4APIA) rom please post a dump of a partial system img for me? If I'm not mistaken, you can dump it with these commands in ADB.
adb shell
dd if=/dev/block/sda20 of=/sdcard/debrick.img bs=4096 count=128
Just to clarify...
sda20 should be the system partition. Any way that's what it is for me.
You can check yourself by doing typing this in ADB:
ls -al /dev/block/bootdevice/by-name
You will get something like this:
lrwxrwxrwx root root 2016-01-08 10:35 system -> /dev/block/sda20
And to get the block size you would type this:
blockdev --getbsz /dev/block/sda20
So the command
"dd if=/dev/block/sda20 of=/sdcard/debrick.img bs=4096 count=128"
If I get this working, I'll compile a nice tut for S7 users and post all the results with files in case anyone else runs into this issue.
Thank you in advance
I don't mean to be an annoyance, but does anyone have any thoughts or could point me to some direction? I know there are a lot of you that are much more knowledgable in this than I am, and all I'm hoping I can get assistance for is if someone can just make a dump of the debrick.img file so I can try to load it on my SD card.
Thanks
Hi, the easiest way to restore back to stock is to download Odin. I think it's Windows exclusive so you'll need bootcamp and install windows. After that, download Odin and extract it. Download stock firmware from androidfilehost.com, then extract. Open Odin and you'll see the options BL, AP, CP, and CSC. The firmware will have 4 or 5 files and will include these labels. Put each respective files into each options in odin. (Sometimes Odin will freeze, but let it do it's thing) After that, go into download mode (hold Volume down, Power, and Home whole turning on). Wait for Odin to recognize your device, if it doesn't, then download Samsung drivers. After it recognizes, press start and wait for the process to finish. That's it! Hopefully I was able to help.
MetalPhoenix45 said:
Hi, the easiest way to restore back to stock is to download Odin. I think it's Windows exclusive so you'll need bootcamp and install windows. After that, download Odin and extract it. Download stock firmware from androidfilehost.com, then extract. Open Odin and you'll see the options BL, AP, CP, and CSC. The firmware will have 4 or 5 files and will include these labels. Put each respective files into each options in odin. (Sometimes Odin will freeze, but let it do it's thing) After that, go into download mode (hold Volume down, Power, and Home whole turning on). Wait for Odin to recognize your device, if it doesn't, then download Samsung drivers. After it recognizes, press start and wait for the process to finish. That's it! Hopefully I was able to help.
Click to expand...
Click to collapse
MetalPhoenix45, thanks for your response. I have a Windows computer as well and I am very familiar with ODIN. The issue is, that in your explanation my guess is you are thinking the phone is in a "soft bricked" mode. The difference between a hard brick phone and a soft brick phone is that in a hard brick phone nothing is recognized when plugged in, it doesn't power on and it also doesn't show any sign of charge when it's plugged into the power.
In a soft brick mode, your phone can be stuck in a boot loop, or at the very least it still shows signs of it getting power. In which case I can just force into download mode and do what you stated above. I don't think that the things you mentioned above would work for me because when I have my phone plugged in to my computer, in device manager it doesn't detect anything. It doesn't even say unknown device or unrecognized hardware. It doesn't see it at all, and I have loaded the Samsung drivers on my pc because ODIN recognized the device prior to my issue.
I do have the stock firmware and everything on my machine, but I just can't get my phone to power or on into download boot even with a JIG.
m0d hipp¥ said:
I just hard bricked my phone, and I'm hoping I can try to get it working again.
I have made backups using flashfire in the past. (I had a few different backups I made).
Prior to getting hard bricked, I was running the PIA firmware, but I was trying to restore from a backup that I had through flash fire, and due to a total rookie move I ended up restoring (or attempting to) restore to a PG1 unintentionally, and well now I can't do anything.
I think I may have a jig at home from a previous samsung phone (I believe an S3), would that work for my S7?
I also came across this thread: http://forum.xda-developers.com/showthread.php?t=2476353
Would that work for me?
I have a macbook pro I can use terminal with, I have a microSD card and reader, and I already have the stock PIA rom on my hard drive.
Is there hope still?
Right now regardless of what key combination I hold down my phone has a black screen.
Any help would greatly be appreciated.
Thanks in advance!
Click to expand...
Click to collapse
Have you had any luck on fixing s7 I've got same issue I've even got device broken down minus the charger port due to cost of screen replacement! Not sure exactly how to test battery itself but every combination of testing battery externally I've nothing any ideas? I'd rather replace the battery vs charger port or is it completely done? This is.the first root I've ever had go wrong and haven't found any solutions yet and been looking since November
Thanks in advance for any advice
On rooted 910v now have a 920t rooted but let's just say my temper got the best of me and we'll will be replacing screen? Oddly enough as many times as the note 4 has been dropped either by myself or son not even a single scratch s7 definitely a pot more brittle!!
crazynate121 said:
Have you had any luck on fixing s7 I've got same issue I've even got device broken down minus the charger port due to cost of screen replacement! Not sure exactly how to test battery itself but every combination of testing battery externally I've nothing any ideas? I'd rather replace the battery vs charger port or is it completely done? This is.the first root I've ever had go wrong and haven't found any solutions yet and been looking since November
Thanks in advance for any advice
On rooted 910v now have a 920t rooted but let's just say my temper got the best of me and we'll will be replacing screen? Oddly enough as many times as the note 4 has been dropped either by myself or son not even a single scratch s7 definitely a pot more brittle!!
Click to expand...
Click to collapse
Unfortunately, I had no luck. I ended up haing to replace the PCB to fix the issue. Basically I learned the hard way that samsung isn't very "dev friendly". I don't blame them, but for any phone enthusiasts that plan on tinkering with their phone if you get the snapdragon version of the S7 vs the exynos version, you WILL run into trouble.
This is because the bootloader can't be unlocked on the SD models. Furthermore, if you get flagged for custom roms your warranty gets void. Over the years I've noticed Samsung is getting more and more strict about this. Honestly if you want a phone that will play nice with modding it, you should look into the google variants, Nexus, or the OnePlus. I can tell you from personal experience, OnePlus plays well with dev users. In fact they don't void the warranty for using custom roms or anything like that; in fact they're very pro and open about supporting the user base and providing a phone that the user is happy with.
Any way, that was my experience. I don't want to go off topic here, so if you have any questions you can PM me if you like, but the short answer is, if you're hard bricked then you will need to replace the motherboard/pcb. I even contacted places to see if they can jtag or jig or anything and they're not able to do it with the snapdragon S7.
bah double post, sorry I can't delete this
Funny you said nexus just ordered 2 two days ago older 7 but 4g and and what not strictly for experimental and ethical purposes of course was actually shocked at the still high priced note 5 Screen tbh but we live and learn!! SOMETIMES? LOL
m0d hipp¥ said:
Unfortunately, I had no luck. I ended up haing to replace the PCB to fix the issue. Basically I learned the hard way that samsung isn't very "dev friendly". I don't blame them, but for any phone enthusiasts that plan on tinkering with their phone if you get the snapdragon version of the S7 vs the exynos version, you WILL run into trouble.
This is because the bootloader can't be unlocked on the SD models. Furthermore, if you get flagged for custom roms your warranty gets void. Over the years I've noticed Samsung is getting more and more strict about this. Honestly if you want a phone that will play nice with modding it, you should look into the google variants, Nexus, or the OnePlus. I can tell you from personal experience, OnePlus plays well with dev users. In fact they don't void the warranty for using custom roms or anything like that; in fact they're very pro and open about supporting the user base and providing a phone that the user is happy with.
Any way, that was my experience. I don't want to go off topic here, so if you have any questions you can PM me if you like, but the short answer is, if you're hard bricked then you will need to replace the motherboard/pcb. I even contacted places to see if they can jtag or jig or anything and they're not able to do it with the snapdragon S7.
Click to expand...
Click to collapse
I am in the same boat, and considering your experience after this sore event, maybe you can help a lot of us guys here in the same situation.
My case is even worst, because, here in my country, there are NO Snapdragons, just G930F Equinoxes.
You may help im providing us lames the debrick.img file, but you must be rooted to do so. This would ve much appreciated.
Another way is to insert a blank 16GB+ SD card on the phone and format it through Odin. You just insert the card on the slot, enter download mode in the phone and load all files in Odin including the .pit. In Odin options select "Re-format" and "T Flash" that will say to the phone to format the ExtSDCard and use the ExtSDCard as destination instead of the internal emmc!
Post the image of the SD, that you can extract it with the Win32DiskImage, and you and your family will be blessed for ten generations. Also save the file in case you mess things again.
There is one method using QFil,but i'm stil trying to asemble all required files and don't now if it will even work. Should work...!!!
Anyway, can you please help us?
Best regards..
PadsPCB said:
I am in the same boat, and considering your experience after this sore event, maybe you can help a lot of us guys here in the same situation.
My case is even worst, because, here in my country, there are NO Snapdragons, just G930F Equinoxes.
You may help im providing us lames the debrick.img file, but you must be rooted to do so. This would ve much appreciated.
Another way is to insert a blank 16GB+ SD card on the phone and format it through Odin. You just insert the card on the slot, enter download mode in the phone and load all files in Odin including the .pit. In Odin options select "Re-format" and "T Flash" that will say to the phone to format the ExtSDCard and use the ExtSDCard as destination instead of the internal emmc!
Post the image of the SD, that you can extract it with the Win32DiskImage, and you and your family will be blessed for ten generations. Also save the file in case you mess things again.
There is one method using QFil,but i'm stil trying to asemble all required files and don't now if it will even work. Should work...!!!
Anyway, can you please help us?
Best regards..
Click to expand...
Click to collapse
Unfortunately, I won't be of much help. If you have the exynos S7, you would need to ask someone else with the same version of your phone for the software because the SD versions would run on different software due to different hardware.
Is there a reason why you don't try sending it out to get serviced so they can replace your PCB ?
I tried to get the debrick.img file a while back as well, but had no luck in doing so and actually I don't have my S7 phone anymore. I bought the OnePlus 3T and it's been working much better for my needs. I'm sorry to say this, but If you have any intention of modding a phone you have 2 options. 1. Get a phone that supports modding and allows you to unlock the bootloader 2. Get the unlocked variant of the phone.
If I have learned anything from my experience, it's that it is incredibly important to do your research. Not only look at the specs of the phone, but look at reviews from other users with the phone. Also if you plan on modding it, go through some threads and see how easy/difficult it is to mod that version of phone you're interested in.
m0d hipp¥ said:
Unfortunately, I won't be of much help. If you have the exynos S7, you would need to ask someone else with the same version of your phone for the software because the SD versions would run on different software due to different hardware.
Is there a reason why you don't try sending it out to get serviced so they can replace your PCB ?
I tried to get the debrick.img file a while back as well, but had no luck in doing so and actually I don't have my S7 phone anymore. I bought the OnePlus 3T and it's been working much better for my needs. I'm sorry to say this, but If you have any intention of modding a phone you have 2 options. 1. Get a phone that supports modding and allows you to unlock the bootloader 2. Get the unlocked variant of the phone.
If I have learned anything from my experience, it's that it is incredibly important to do your research. Not only look at the specs of the phone, but look at reviews from other users with the phone. Also if you plan on modding it, go through some threads and see how easy/difficult it is to mod that version of phone you're interested in.
Click to expand...
Click to collapse
Then i think got stuck, beacause in these forums there is no one willing/able/interested in helping anyone.
I said i'm in the SAME boat == I got an SM-G930T (from T-Mobile) that has a SnapDragon cpu but HERE in my country THERE ARE NO Snapdragons only Equinoxes. If we had such phones here surely i would have done this already, but G930F's won't do, as i have already tried.
So, as you know how i feel about a brand new SM-G930T Bricked, you wold be my last hope. There is no way to send it back to Samsung beacause it was bought from a friend and surely no warranty.
Anyway, best regards and rest in peace
Oh sorry, I misunderstood you. I'd like to think that it's not so much people don't want to try to help out, it's just that there is nothing that can be done for users on the snapdragon device so no one bothers unfortunately. Sorry to hear about this, and it really is unfortunate that you had to go through the same thing I went through with no help. Trust me, if I was able to do anything to provide any guidance I would.
Good luck!

Categories

Resources