Hi to anyone that has this device and reads this :highfive: I'm sorry this is not a thread on how you can unbrick your device . this is for those who have started getting issues on their device and are thinking of flashing and wanna have some guidance on what to expect first ill say its not hard and nothing to be afraid of I'm writing this on hindsight so that you can avoid the mistakes I made.(theres a bit of back story but if you don't care just jump to the bricking)
the reason I flashed my device is that about 8 months prior to my bricking I was acting as the caregiver for an elderly relative and by a set of circumstances the phone got peed took it to get cleaned and all everything was fine the back camera was shot the rest of the phone was fine the front camera was still working but was been disabled by the the device so I rooted the device and forced to get the front camera to work since I had done some test and I could get it take pictures all well till this point about 3 moths before the bricking the phone started to have issues with the contact app then a few days latter I would get stuck in a reboot cycle so I went into the developer screen and ran a root diagnose 14 files were corrupted according to the device so i decided to flash it i had already done this on a different phone so I figured nothing to worry there are many INTERNET guides and videos to this process so I won't link or describe much of this part key words are [sp flash tool(to connect your computer to your device and load the new firmware), CDC driver (an uncertificated* driver to actually use sp flashtool), firmware tab 3 7 essential TB3 710I**(to find the ROM for the device be very carefull for there are 2 diferent ROMs for the device the first ending on 0I and the second ending on 0F)].
*this driver has some issues running on windows 8 if you have this one like i do you only need to search how to run uncertificated driver most of the time it will be explained on the same page you download it but in case its not you don't have to worry.
**you can find this out on the box of your device or when you run developer screen (power + plus volume)
moving on the flash was successful and all well and to my surprise the front camera was working fine without me having to do anything then about a month after again I was at family meeting and I wanted to try to take a picture with the front camera of my meal and me as you can guess this was not easy and i already had taken pictures before this way but this time the app crashed then the device started sending messages of other apps and systems crashing and blocking me out so I figured guess its time to re flash again....
the BRICK
I went home and first thing I checked was root integrity now there were 44 files that failed First bad sign so I used the flash tool with the same ROM I was already using (Lenovo_Tab_3_TB3-710I_MT6580_S000032_160921) restarted the phone like usual it was still booting at this point but for some reason it would not load past the lenovo logo (first mistake I was feeling anxious cocky and rushed I should have given it time) I waited few moments and nothing so I figured "its the same ROM of course it will still be crashing" and the basis that the system could not tell the difference that I had just made a fresh install so I emptied the cache and flashed again did not seem to work so i download a new ROM an older version s000029 it still did not work then I tried a newer one s000035 nothing and I noticed on the developer screen the ROM that was supposed to be on my device was still the s000032 I figured something must be happening to the sp tool so I tried using the developer screen tools to upgrade the firmware as a fool I presed the first option on the OTA update option while trying to use the sdcard option it got stuck there a while i was not in a waiting mood so I forced stopped the device (second mistake don't do this ever I figured since nothing was been sent and it had not picked up anything i would just go on as intended) I tried again with the zip file on the sd card now in the right option but it would simply not load it would just insta stop and say installation aborted I new this was BAD I again ran a check on the root again and this was all it would show:
Now check begins, please wait...
Load source zip file fail
System check fail!
after that I knew I had just soft bricked the tablet and that I had just about tried all that I could to fix something like this I spent the next 8 hours reading surfing and trying to come up with a solution to this none worked and then I had a suggestion why didn't I use the lenovo smart assistant it had a rescue feature for bricked phones! (my last and worst mistake) so I downloaded the program strait from the lenovo page for the tab 3 7 essential and it indeed had the rescue feature all it required was me to be sure of the model and the right i/o which i check on the box and on the back plate of the tab and the ROM appear seeing the name it was about the same as the ROMs i had already downloaded about the same size too over 900 Mb so pressed start and it was on after downloading the steps were the same as with the sp tool turn off phone then connect wait then disconnect and done so I did and the tab now was bricked as before the lonovo assistant while i could not start android i could still run and start the dev screen but after the phone simply got stuck on a restart loop and i was locked off the dev screen now i could not check or do anything i have ran a few more sp flashes even full format and memory checks (all successful) the usb connection still works but i have not been able to unbrick the TAB so I'm moving on got my sight on a xioming for now
lessons
*don't rush when flashing if you have things to do and you don't need your phone do them then flash in peace
*if you have flashed once before successfully do a back up on the dam dev screen it only takes an 8Gb sdcard and 30 minutes tops
*the coding on the contact app is a bit faulty just download the contact app from google
*if you suspect theres hardware damage disable the parts that are damage not sure but i suspect this is what corrupted my root files
*the back plate is a bit hard to remove but you should always try to do sp before you start flashing to disconnect the battery and have very small screwdriver philipshead i also suspect this may have had a part on this
*never use the lenovo assitant i think this is why most people don't even mention it on a first dive when you search
Related
I tried to upgrade my brothers samsung galaxy gio with a leaked version of it's 2.3.4 upgrade via "Odin".It kinda got stuck in the process and following the guide for it I removed the battery (it said to remove the battery if it stuck at a process for more than 10 minutes). After that when I tried to power it up it got stuck with an image of a phone and a pc connected with dots and a caution mark in between. For extra info recovery mode doesn't open but the download mode does. And I have tried to upgrade it a few times but gets stuck at the process named "ididb download"or something like that.
Is the phone bricked?????? Plz reply quick.
Hi,
Don't worry: as long as you can turn the phone on you should be OK, it's only a soft brick . Have you tried going in download mode again, and reflashed another ROM or even the one you attempted? Got evering right? OPS? Evering you must tick? Re-read the whole tutorial cause generally people mess up because they don't pay enough attention ^^
P.S. At least a million threads exist for this, you obviously haven't looked far before posting..
I wanted to share my knowledge and experience from the past 2 days. Most of the help came from guides and posts on this forum so I wanted to give that back.
We were trying to root the SGS4G and because we're noobs we made the mistake of thinking it was a Vibrant. Got a Vibrant ROM and tried to flash it though Odin WITH re-partition checked. Everything we read said if you do either one of these things, you will brick your phone.
Sure enough we bricked the phone. It was trying to boot into the Vibrant ROM but was getting stuck on the word 'Vibrant' and then showing a whole lot of weird colored pixels. We then learned we'd made a massive mistake and that the phone wasn't a Vibrant after all.
We got a stock ROM for SGS4G and started trying to push them through Odin. Faced countless FAILS and freezes and finally it took us to the Recovery Mode and we tried the Restore option. It booted into a crippled SGS4G ROM. When it booted, it vibrated every 10 seconds or so and it had a null IMEI and unknown baseband.
We tried following a guide that wanted to change some text in the nv_data.bin but the numbers we were meant to be editing (0018810?) didn't exist in our nv_data.bin. So that didn't work for us.
In the meantime we tried to flash the stock ROM in Odin but kept getting FAILs and Freezes. With this step we lost even the crippled operating system and couldn't reach anything except the 'phone --!-- computer' screen. Luckily, this acts the same as download mode, so not bricked. We kept trying to push the stock SGS4G stock ROM (Froyo 2.2) several times and failing.
At one point we got a completely black screen, wouldn't turn on. Bricked again. We found this post on RootzWiki and it worked for us that time and brought it back from the black screen to download mode http://rootzwiki.com/topic/1820-how-to-unbrick-your-sgs4g/
Somehow we ended up at this guide here on XDA for fixing the "null/null" IMEI http://forum.xda-developers.com/showthread.php?t=1142829
We followed that guide. When you add the PIT file it automatically checks 'Re-Partition' in Odin, we didn't uncheck it. Bricked again. It was stuck on the Samsung logo and when we tried to get to download mode it got stuck on a black screen with the loading circle/lines and 2 computers were giving 'The USB device has malfunctioned' when we plugged it in. The unbrick guide above (RootzWiki) didn't help this time. We tried restarting the computer, let the phone rest without battery for half an hour, held power button for a minute without battery, still nothing.
Finally I accidentally pressed the power button (rather than the volume buttons to get into download mode) and it went to the samsung logo (as expected) and after that I was able to get into download mode. The key to this I think is to keep on trying powering on normally then try download mode over and over and eventually it should get unstuck and the computer should recognize it again.
Once I had it back in download mode, I followed this guide again BUT!!! I made sure to un-check re-partition and I did not check "Phone EFS Clear" (because I had tried that already before it was bricked and wanted to see if a straight ROM would work first). Everything worked perfectly, I got my IMEI and Baseband back, without modifying anything.
I don't know if this was a miracle, or if any of it will work for anyone else, but the moral of the story is don't give up even if you've done the absolute worst possible thing. I don't even think hardbrick exists on this phone after everything we were able to save it from.
Cheers
Hardbricks do exist on this phone but you have to try really hard to do it. A few people have managed it. Way to stick with it and recover your phone. I've done that more times than I can count.
hechoen said:
Hardbricks do exist on this phone but you have to try really hard to do it. A few people have managed it. Way to stick with it and recover your phone. I've done that more times than I can count.
Click to expand...
Click to collapse
I didn't feel like i really hard bricked it until i saw the USB computer connection error "device pluged in malfunctioned" in more than one PC.
Then i really felt like its a hardware BIOS chipset level problem now but man...
That story cracked me up. That is exactly why I spend days reading before I even root my phone. I made the mistake one time on my old G1 and it could not be revived.
Congrats on getting it working. (especially without flooding the q&a with redundant questions that have been described in detail several places )
hani1400 said:
I wanted to share my knowledge and experience from the past 2 days. Most of the help came from guides and posts on this forum so I wanted to give that back.
We were trying to root the SGS4G and because we're noobs we made the mistake of thinking it was a Vibrant. Got a Vibrant ROM and tried to flash it though Odin WITH re-partition checked. Everything we read said if you do either one of these things, you will brick your phone.
Sure enough we bricked the phone. It was trying to boot into the Vibrant ROM but was getting stuck on the word 'Vibrant' and then showing a whole lot of weird colored pixels. We then learned we'd made a massive mistake and that the phone wasn't a Vibrant after all.
We got a stock ROM for SGS4G and started trying to push them through Odin. Faced countless FAILS and freezes and finally it took us to the Recovery Mode and we tried the Restore option. It booted into a crippled SGS4G ROM. When it booted, it vibrated every 10 seconds or so and it had a null IMEI and unknown baseband.
We tried following a guide that wanted to change some text in the nv_data.bin but the numbers we were meant to be editing (0018810?) didn't exist in our nv_data.bin. So that didn't work for us.
In the meantime we tried to flash the stock ROM in Odin but kept getting FAILs and Freezes. With this step we lost even the crippled operating system and couldn't reach anything except the 'phone --!-- computer' screen. Luckily, this acts the same as download mode, so not bricked. We kept trying to push the stock SGS4G stock ROM (Froyo 2.2) several times and failing.
At one point we got a completely black screen, wouldn't turn on. Bricked again. We found this post on RootzWiki and it worked for us that time and brought it back from the black screen to download mode http://rootzwiki.com/topic/1820-how-to-unbrick-your-sgs4g/
Somehow we ended up at this guide here on XDA for fixing the "null/null" IMEI http://forum.xda-developers.com/showthread.php?t=1142829
We followed that guide. When you add the PIT file it automatically checks 'Re-Partition' in Odin, we didn't uncheck it. Bricked again. It was stuck on the Samsung logo and when we tried to get to download mode it got stuck on a black screen with the loading circle/lines and 2 computers were giving 'The USB device has malfunctioned' when we plugged it in. The unbrick guide above (RootzWiki) didn't help this time. We tried restarting the computer, let the phone rest without battery for half an hour, held power button for a minute without battery, still nothing.
Finally I accidentally pressed the power button (rather than the volume buttons to get into download mode) and it went to the samsung logo (as expected) and after that I was able to get into download mode. The key to this I think is to keep on trying powering on normally then try download mode over and over and eventually it should get unstuck and the computer should recognize it again.
Once I had it back in download mode, I followed this guide again BUT!!! I made sure to un-check re-partition and I did not check "Phone EFS Clear" (because I had tried that already before it was bricked and wanted to see if a straight ROM would work first). Everything worked perfectly, I got my IMEI and Baseband back, without modifying anything.
I don't know if this was a miracle, or if any of it will work for anyone else, but the moral of the story is don't give up even if you've done the absolute worst possible thing. I don't even think hardbrick exists on this phone after everything we were able to save it from.
Cheers
Click to expand...
Click to collapse
Wheooooooooowwww,..you just UNBRICKED mine, I know of the Battery pull etc...but the post you referenced
is MAGIC
This was not my first Rom nor Root on this phone, it weirdly happened while doing the GB starter....via ODIN, which i also used before..no clue what went wrong, oh well...
Thank you, thank you "i did"....Yohoooo
Yup i agree i like to read, reread then read as i do. This way i got a pretty good understanding of what I'm doing. Btw i have just started using one click and it is sooooo simple. I love it.
Sent from my SGH-T959V using XDA App
The link for fixing null/null IMEI is not working.
http://forum.xda-developers.com/showthread.php?t=1142829
diavel said:
The link for fixing null/null IMEI is not working.
http://forum.xda-developers.com/showthread.php?t=1142829
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=881162
Im still carrying this phone, stupid baseband unlock for iphone won't come out now I am carrying 2 phones, one as an ipod touch and the galaxy s! Good story, hope it can help others, but I am prepared to jump off of this bandwagon anytime now!
Good morning everyone,
I have a zopo zp980t 32gb 2gb ram model whihc from reading and checking mine does not have fcc or b logo under battery if that helps to know what rom i can use.
BUT i have a big problem.
Phone was working very well on latest firmware which it came with a month ago.
I changed boot animation once from someone on a site and all good as original was annoying.
He made me a custom animation and when i clicked on update as with other's, this time the screen went bright screen and went onto the blue adnroid icon with spinning circle going around it and now it just stays on this.
I am gutted as phone will not boot.
I can only get into recovery menu with usb cable conencted to pc and pressing vol up and power, this will not work without usb attached?
Anyway i am trying in vain to at least get it working again and flashing a rom original with flashtool 4.2, this now is into 2nd day and getting nowhere.
I am running windows 7 home edition and the driver is the issue as i get BROM error ...............port etc (1013) which i assume is driver not installed which i have tried way too often.
Is there a clear tut how to get this done as i feel once i get this corrected i will hopefully be able to get phone running again, maybe?
I don't like asking for much and always will work and learn myself by reading but their are so many models of this 980 it is not possible to know which rom i can use etc.
Any guidance is really much apprecaited.
Absolutley gutted what's happened not long after buying it.
Thank you so much for any advice given.
Fixed & how to
This is for other's that may have same problem or simply want to know how to reflash from fresh.
First of all i was having issues with the usb driver i.e port not installing.
So i used my wifes netbook and installed perfectly without issue.
I then went to zopo main original roms page and downloaded BOTH roms to save hassle.
As my phone is 32gb 1.5 quad core, Black under battery, no FC, no B and no replies to help me find out what model i have i went testing.
I started the flashtool 4.2, then i tried firstly the:-
ZP980/C2 4.2 ZP980_0610 341.4MB 2013/6/10 Normal Version (PHONE DOESN'T BOOT)
Secondly I then flashed:-
ZP980/C2 4.2 ZP980_0610 341.4MB 2013/6/10 B version (THIS WORKS FULLY)
So now completed flash and phone working.
Then i connected the phone to my wireless network, and in the phone i clicked on the WIRELESS UPDATE app.
This then provided me straight away with the latest update being:- BUILD NUMBER ZP980 20130818-173942.
I rebooted phone and now latest firmware.
I wanted to root it now and easiest way is simply using a program called EROOT.
Make sure USB DEBUGGING is ON, wait few seconds and hit ROOT.
Super user now in phone and fully rooted.
Job done
Hello everyone, I do believe I have officially broken my phone, however, something tells me I shouldn't give up quite yet.
My cool-story lookin ass decided "Gee, I have done a lot with my phone, and I really want to try and use Cyanogen Mod on it because I am cool!"
Well, I am definitely not that cool. It failed, and then after sadly being turned to my stock ROM, I decided to try Clockwork Mod, it seemed that some were doing it quite easily, so I attempted this myself.
Another failed attempt there, so I figured, well, the Clockwork Mod app had some cool stuff to it, maybe I will just satisfy myself by trying to change the bootup animation to Nyan Cat to make myself feel better about it.
The original purpose of me flashing a ROM over was to allow me to install apps to my SD card without having to go though a Myriad of things. Turns out, that was probably the better option.
Allow me to tell you the current symptoms, and let you know what methods I have tried.
Stuck on LG boot screen, does not load OS
Now no longer will power on or even try to without being connected to my PC (not sure how that came about)
Recovery (Power + Vol Down) does not work, freezes when telling me to wait (gave it a good 30 minutes)
Factory Reset does not work (freezes after second confirmation gave it about 30 minutes)
Methods I am trying but have so far had no success with:
LG Support Tool - (Tells me it stopped working at the beginning of the 3rd step in Upgrade Recovery) (I am letting it sit right now and is still there after about 20 minutes or so)
Unsoft Brick (OneClick Unbrick Java tool) - Flat out fails.
The Connect.img for VMWare fails ultimately
KS360 Util ENG (So far no luck. It crashes douring the upgrade.)
LGFlash Tool - I got it to say Ready and then boom, I unplug and replug in (as per instructions) and no dice, I get no "PASS" on it.
What I can do
Get it to the Download Mode screen.
So far I have tried these methods with and without both the SD Card and SIM card.
The phone IS out of service right now and I did soft-root it at one point using Ngyuen Root method King User, so I don't believe I will get any support, even if I do take it into Sprint (Got it through Boost Mobile).
What I am thinking I may be able to do (no research on this yet)
Is be able to run Linux Distro Ubuntu, force wipe it, and then force the stock ROM back into it to make it run again..
But so far, I have mostly broken down far and needed to post a thread about it here.
If any of you have any suggestions as to what I might do in order to get my phone back up and running (loss of data is irrelevant and already happened) again, that would be fantastic.
Much appreciated everyone.
(Thread posted by myself in Android Forums as well so as to prevent any confusion)
[[ SIDE NOTE: I wasn't sure where to post this, so when I searched for a thread regarding this device, it was posted here, and I scrolled and saw other device support threads. I hope this was the way to go! Sorry if I didn't get it right. ]]
Just a quick update on the goings on:
Yesterday I was able to get it to try and boot without it being plugged in but it did only attempt so ONCE. I do know that after all of the tinkering I have been doing the battery should be at least 90% if not 100%.
This was also a great excuse to bump the thread and let you know I am still watching and hopeful
Hi everyone,
I'm hoping that someone can help me out with my device. I have a rooted sm-p900 that was working fine until a month ago when I tried to flash [ROM][7.1.x|SM-P900| Unofficial LineageOS 14.1 (v1awifi). I was busy multi-tasking and made the stupid mistake of flashing the rom before updating the BL. Since trying to do so, I have not been able to get past the first screen that says "Samsung sm-p900" . After the logo disappears, my screen remains lit but is just black.I could not restore my backup after either.
Where I am now:
- I can still access and use T.W.R.P. (latest 3.1.1) (If TWRP is left alone for too long, the device will reset to the same black screen and hang forever. If flashing a rom is taking long, the device will restart mid-flash as well.)
- I can still access download mode and use odin as well.
- I have since flashed the appropriate BL but that has not changed anything.
-I have tried clean flashing a magnitude of different roms and still come across the same problem.
I honestly have no idea how I can fix the device and have tried everything I know how. I would love to get it back as soon as possible. Any help is greatly appreciated, so thank you in advance!
jp2572 said:
Hi everyone,
I'm hoping that someone can help me out with my device. I have a rooted sm-p900 that was working fine until a month ago when I tried to flash [ROM][7.1.x|SM-P900| Unofficial LineageOS 14.1 (v1awifi). I was busy multi-tasking and made the stupid mistake of flashing the rom before updating the BL. Since trying to do so, I have not been able to get past the first screen that says "Samsung sm-p900" . After the logo disappears, my screen remains lit but is just black.I could not restore my backup after either.
Where I am now:
- I can still access and use T.W.R.P. (latest 3.1.1) (If TWRP is left alone for too long, the device will reset to the same black screen and hang forever. If flashing a rom is taking long, the device will restart mid-flash as well.)
- I can still access download mode and use odin as well.
- I have since flashed the appropriate BL but that has not changed anything.
-I have tried clean flashing a magnitude of different roms and still come across the same problem.
I honestly have no idea how I can fix the device and have tried everything I know how. I would love to get it back as soon as possible. Any help is greatly appreciated, so thank you in advance!
Click to expand...
Click to collapse
Have you tried taking it completely back to stock via Samsung Kies on your PC?
Sorry I don't have complete details, but it goes something like this (and if you search this site or Google, you'll find a good write-up on how to do a complete recovery using Kies):
1. If you can, make a backup using TWRP - if not, you are going to lose everything because of the next steps
2. Download and install the Kies software from the Samsung site and install it on your PC (I grabbed both versions, can install both on the same PC at the same time)
Make sure that it installs the Samsung USB driver
3. Connect to the tablet using the OEM cable - if you get a reaction from Kies, great
4. Somewhere in the Kies menu, you can tell it to do a complete recovery, including bootloader- if I remember correctly, you'll need your serial number (Sorry, been 18 months since I did just about the same thing and was able to recover it from my FUBAR, and I no longer run Windows so I can't step thru it)
It will go through downloading and flashing your tablet back to the state it was when you pulled it out of the box.
If you get to that point, you will have to go the whole route (including loading TWRP) to get it back to Lineage. It took me about two weeks to get it back to the way I had it before I was flashing and reading a book and talking to my wife all at the same time and didn't pay attention to what I touched on screen.
I apologize for the rambling and not having definitive statements, but I'm drugged up and been awake for the last 36 hours, and at my age that isn't a good combination.
Thank you so much for your help! I couldn't end up using that method because kies would not recognize my device for anything. It did get me inspired to try fixing it again however and it worked!
If anyone ever encounters the same or a similar problem, I just tried re-rooting it using odin and cf's autoroot file. It allowed me to be able to install roms again.
rhricik447 said:
Have you tried taking it completely back to stock via Samsung Kies on your PC?
Sorry I don't have complete details, but it goes something like this (and if you search this site or Google, you'll find a good write-up on how to do a complete recovery using Kies):
1. If you can, make a backup using TWRP - if not, you are going to lose everything because of the next steps
2. Download and install the Kies software from the Samsung site and install it on your PC (I grabbed both versions, can install both on the same PC at the same time)
Make sure that it installs the Samsung USB driver
3. Connect to the tablet using the OEM cable - if you get a reaction from Kies, great
4. Somewhere in the Kies menu, you can tell it to do a complete recovery, including bootloader- if I remember correctly, you'll need your serial number (Sorry, been 18 months since I did just about the same thing and was able to recover it from my FUBAR, and I no longer run Windows so I can't step thru it)
It will go through downloading and flashing your tablet back to the state it was when you pulled it out of the box.
If you get to that point, you will have to go the whole route (including loading TWRP) to get it back to Lineage. It took me about two weeks to get it back to the way I had it before I was flashing and reading a book and talking to my wife all at the same time and didn't pay attention to what I touched on screen.
I apologize for the rambling and not having definitive statements, but I'm drugged up and been awake for the last 36 hours, and at my age that isn't a good combination.
Click to expand...
Click to collapse
Try updating the bootloader again using odin
When this has happend factory reset
Flash the rom, addonsu and gapps in the same TWRP session
The rom should work then, I've been happily using it for about 6months now