[Q] SGS3 Kernel Panic / Soft Brick - Sprint Samsung Galaxy S III

Hi,
I have a rooted Sprint SGS3 SPH-L710 which I was attempting to update from 4.1.1 to 4.1.2. I never did get the update to work and afterwards, I started getting random reboots, which seemed like SDS. Now powering it on puts it into a reboot cycle and it never gets past the Samsung Galaxy S III logo. Attempting to go into recovery mode gives the following kernel panic message:
Kernel Panic
KRAIT INFO
Panic caller : __stack_chk_fail+0x10/0x14
Panic Msg: stack-protector: Kernel stack is corrupted in: c002
Thread : swapper:1
Wait....
Done
Kernel Panic
Upload Mode
I can get into download mode, and have attempted to use Odin to flash both the kernel with KERNEL-SPR-L710VPBMD4-1366019975.tar and the ROM SPR-L710VPBMD4-20130418114128.zip which I obtained from samsung-updates.com
When I attempt to flash the kernel, I get the following from Odin:
Firmware update start…
boot.img
NAND Write Start!!
RQT_CLOSE !!
RES OK !!
Remain Port …. 0
All threads completed (succeed 1 / failed 0)
But no change in behavior on the phone.
When I attempt to flash the ROM, I get the following from Odin:
Odin v.3 engine (ID:3)..
File analysis..
SetupConnection
Initialization..
Get PIT for mapping..
Firmware update start..
sbl2.mbin
NAND Write Start!!
FAIL! (Write)
All threads completed. (succeed 0 / failed1)
and I also get the following on the phone download mode screen:
ODIN : flash write failure
I've tried searching, but cannot seem to find much about the kernel panic. I'm guessing it is either a symptom of SDS or that I may have accidentally loaded an incompatible ROM when unrooting. I've tried flashing with Odin on different systems with different cables, but always get the same results.
tl;dr I have a soft bricked phone that gives a kernel panic error when I try to go into recovery mode and a write failure when flashing the ROM.
Any suggestions are appreciated.
Thanks!

I've never seen that before! Scary. Try using Odin with the files from this link, everything you need should be there.
http://rwilco12.com/downloads.php?dir=Files/Devices/Samsung Galaxy S3 (SPH-L710)/
Actually, use the tar file from this link
http://rwilco12.com/downloads.php?d...L710)/Stock ROMs/JB/MD4/Full Restore/Unrooted

Make sure you try different ports and cables when using Odin. Some things that helps me.
------------------------
Sprint Galaxy S3
Stock - Whiplashh Rom - MIUI - Wicked Sensations
Hit that "Thanks" Button if I helped you!

Thanks for the advice, Metalfan and Whiplashh. I have tried 3 difference cables and different usb ports. I also downloaded the file SPH-L710_MD4_1130792_Stock_Restore.tar.md5.gz that Metalfan linked, but got the same results from Odin as the other ROM I attempted loading.
I did notice something that changed before I attempted to load that ROM, the download mode screen now shows CUSTOM BINARY DOWNLOAD: No, it used to show 11. So I guess at some point in troubleshooting I must have reset the counter, but not sure that it really matters.
Now I'm condsidering trying this solution for hard bricked devices, I figure it can't hurt.
http://forum.xda-developers.com/showthread.php?t=2369125

I just thought I would post a follow-up to my own issue. All of my own attempts to flash a new ROM to the device were failing and the device was out of warranty, so I sent it off to a independent repair service who informed me the device had a bad eMMC (internal memory / memory controller) which I suppose matches up with the write fail errors that I was seeing. Not sure if I broke it while flashing it or if it was a result of the SDS symptoms that I had seen, either way its pretty much scrap now.

Related

[Q] noob who thinks he has .PIT trouble

Hi All,
I've searched through the forums for answers to my particular problem but haven't found anything that's worked bla bla bla... you guys go through a lot of this every day, don't you? I honestly have been scouring the web, looking for answers to my problem (I'm a member on other, unrelated forums and I know how annoying lazy noobs can be) but I only found a single response in a single thread that might be helpful (but I'll get back to that at the end).
Here's a brief history of my failure, followed by my problem:
1. Tried rooting with motochopper, it installed Superuser but SU didn't work properly (kept going off about updating binary but would always shoot back errors when I tried to update) and Rootchecker said phone wasn't rooted.
2. Tried rooting via Odin, I don't remember exactly what happened (it's been hours since this happened) but I ended up with a failure notice halfway through the download, I read somewhere to pull the battery so I did. Waited a minute, plugged it back in, now the phone won't boot (I get a "Firmware upgrade encountered an issue. Please select recovery mode in Kies and try again" error), and it gives me the same error message if I try to boot to recovery mode, but I can still boot to download mode.
3. At this point, I figured I'd screwed the pooch and should flash the original, stock Samsung ROM back on to the phone and start from scratch. (I don't have a backup file but I've only had the phone for two days, I don't care if I lose personal data).
4. Downloaded the 1.6 GB stock ROM zip file.
5. Deleted temporary files, restarted computer, booted phone into download mode, opened Odin, loaded the ROM .tar file into the PDA slot of Odin (left all the Odin settings as they were).
6. Connected phone to computer, blue light from Odin (this means it added the device if I understand correctly).
7. Started Odin, download failed. Here's the transcript from Odin:
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> M919UVUAMDL_M919TMBAMDL_M919UVUAMDL_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Added!!
<ID:0/003> Odin v.3 engine (ID:3)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> sbl2.mbn
<ID:0/003> NAND Write Start!!
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/003> Added!!
I hit start again, another failure. Transcript:
<ID:0/003> Odin v.3 engine (ID:3)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> There is no PIT partition.
<OSM> All threads completed. (succeed 0 / failed 1)
So do I need to flash a new PIT partition? The one relevant thread (http://forum.xda-developers.com/showthread.php?t=2320066&highlight=partition+file) says that the PIT information is imbedded in the tar file, why isn't Odin reading it correctly?
I'm very new to the realm of Android and Linux, I've been trying to learn the basics about rooting, kernels, ROMs, etc. over the last few days to better understand how to fix these problems on my own. But I haven't found anything that will fix this. Thanks to anyone and everyone who answers, I'll make you cookies.
I'm not joking, if you live in or around the San Francisco bay area and you help me fix this, I'll deliver cookies, donuts, brownies, etc.
Read my second post on that thread. PIT information is stored in the Odin file. Get the download from Sammobile.com
Sent from my SGH-M919 using Tapatalk 2
re: pit file
WetbehindEars said:
Hi All,
I've searched through the forums for answers to my particular problem but haven't found anything that's worked bla bla bla... you guys go through a lot of this every day, don't you? I honestly have been scouring the web, looking for answers to my problem (I'm a member on other, unrelated forums and I know how annoying lazy noobs can be) but I only found a single response in a single thread that might be helpful (but I'll get back to that at the end).
Here's a brief history of my failure, followed by my problem:
1. Tried rooting with motochopper, it installed Superuser but SU didn't work properly (kept going off about updating binary but would always shoot back errors when I tried to update) and Rootchecker said phone wasn't rooted.
2. Tried rooting via Odin, I don't remember exactly what happened (it's been hours since this happened) but I ended up with a failure notice halfway through the download, I read somewhere to pull the battery so I did. Waited a minute, plugged it back in, now the phone won't boot (I get a "Firmware upgrade encountered an issue. Please select recovery mode in Kies and try again" error), and it gives me the same error message if I try to boot to recovery mode, but I can still boot to download mode.
3. At this point, I figured I'd screwed the pooch and should flash the original, stock Samsung ROM back on to the phone and start from scratch. (I don't have a backup file but I've only had the phone for two days, I don't care if I lose personal data).
4. Downloaded the 1.6 GB stock ROM zip file.
5. Deleted temporary files, restarted computer, booted phone into download mode, opened Odin, loaded the ROM .tar file into the PDA slot of Odin (left all the Odin settings as they were).
6. Connected phone to computer, blue light from Odin (this means it added the device if I understand correctly).
7. Started Odin, download failed. Here's the transcript from Odin:
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> M919UVUAMDL_M919TMBAMDL_M919UVUAMDL_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Added!!
<ID:0/003> Odin v.3 engine (ID:3)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> sbl2.mbn
<ID:0/003> NAND Write Start!!
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/003> Added!!
I hit start again, another failure. Transcript:
<ID:0/003> Odin v.3 engine (ID:3)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> There is no PIT partition.
<OSM> All threads completed. (succeed 0 / failed 1)
So do I need to flash a new PIT partition? The one relevant thread (http://forum.xda-developers.com/showthread.php?t=2320066&highlight=partition+file) says that the PIT information is imbedded in the tar file, why isn't Odin reading it correctly?
I'm very new to the realm of Android and Linux, I've been trying to learn the basics about rooting, kernels, ROMs, etc. over the last few days to better understand how to fix these problems on my own. But I haven't found anything that will fix this. Thanks to anyone and everyone who answers, I'll make you cookies.
I'm not joking, if you live in or around the San Francisco bay area and you help me fix this, I'll deliver cookies, donuts, brownies, etc.
Click to expand...
Click to collapse
Never flash a .pit file, it contains the partition information for your phone.
It is also a sure way to end up with a shiny brick.
You wrote an lot of specifics but you forgot to say if your phone can get into cwm or twrp recovery?
Do you have a cwm/twrp flashable custom rom zip file on your sdcard in your phone?
An other question have you recently flashed any AOSP/AOKP/CM/MIUI roms?
If you don't, download the wicked v3 custom rom from this forum for your M919 Tmobile S4 phone.
What happens if you do a full wipe in cwm/twrp recovery and afterwards flash a cwm/twrp flashable zip file custom rom?
Be sure to do a full wipe which includes Factory Reset, Wipe System, Wipe Cache and Wipe Dalvik Cache before flashing.
If you do all these things there is a good chance your phone will work properly and then afterwards if you still want to
Odin flash the stock un-rooted firmware which you were trying to flash it most likely will be successful.
Good luck!
Misterjunky said:
Never flash a .pit file, it contains the partition information for your phone.
It is also a sure way to end up with a shiny brick.
You wrote an lot of specifics but you forgot to say if your phone can get into cwm or twrp recovery?
Do you have a cwm/twrp flashable custom rom zip file on your sdcard in your phone?
An other question have you recently flashed any AOSP/AOKP/CM/MIUI roms?
If you don't, download the wicked v3 custom rom from this forum for your M919 Tmobile S4 phone.
What happens if you do a full wipe in cwm/twrp recovery and afterwards flash a cwm/twrp flashable zip file custom rom?
Be sure to do a full wipe which includes Factory Reset, Wipe System, Wipe Cache and Wipe Dalvik Cache before flashing.
If you do all these things there is a good chance your phone will work properly and then afterwards if you still want to
Odin flash the stock un-rooted firmware which you were trying to flash it most likely will be successful.
Good luck!
Click to expand...
Click to collapse
Sorry, I should have mentioned all of that...
As far as I know, I cannot enter into any type of recovery... the only thing that's working right now is download mode, no other button combinations work (volume up+home+on gives me the "Firmware upgrade encountered an issue" story, same with volume up+volume down+power). So I have no way of doing a wipe, unless there's something else I can do. Is there a way I can wipe the phone remotely, from my computer?
A couple other specifics that I should have mentioned in OP:
This phone is only five days old and has not be rooted or modded at all up until yesterday.
I've never put an SD card into the phone (though I have one handy, if there's something I need to do that requires one).
elesbb said:
Read my second post on that thread. PIT information is stored in the Odin file. Get the download from Sammobile.com
Sent from my SGH-M919 using Tapatalk 2
Click to expand...
Click to collapse
Vielen Dank, elesbb... I went to sammobile.com and started the download, but when I clicked through to the download server, it was the exact same file (from the exact same server) that I had just downloaded... So I have the sammobile file, I think the issue is that I need to wipe the phone before I flash it but I have no way of wiping it (that I am aware of).
Thank you both for your time and energy!
Restart your phone and computer. Try a different USB cable or usb port and see if odin will work. I've seen so many times problems because of a usb cable. And no, I wouldn't use a PIT file. Just the PDA tar.
Then you can use CF-Auto-Root to root or follow these instructions to root the MDL build.
Atmazzz said:
Restart your phone and computer. Try a different USB cable or usb port and see if odin will work. I've seen so many times problems because of a usb cable. And no, I wouldn't use a PIT file. Just the PDA tar.
Then you can use CF-Auto-Root to root or follow these instructions to root the MDL build.
Click to expand...
Click to collapse
Thanks, I haven't tried a different usb port... I'll try that when I get home. The USB cable I'm using is the brand new Samsung cable that came with the phone, I don't think it's the problem but I'll give it a try anyway.
Thanks!
Edit:
After some more digging, I think I might have NAND rw corruption issues (since I can boot into download mode but not into any kind of recovery/bootloader mode). I get this notion from reading http://forum.xda-developers.com/showthread.php?t=1457458, which isn't for the GS4 but I figure it's probably a good diagnostic tool for both. In the thread, Phistachio says that reflashing the kernel (and if that fails, the bootloader) will fix the problem. Will this fix the problem for the GS4 as well?
At this point, I will try a different USB port and/or cable and if that fails, I'll try reflashing the kernel.
Does that sound good?
WetbehindEars said:
Vielen Dank, elesbb... I went to sammobile.com and started the download, but when I clicked through to the download server, it was the exact same file (from the exact same server) that I had just downloaded... So I have the sammobile file, I think the issue is that I need to wipe the phone before I flash it but I have no way of wiping it (that I am aware of).
Thank you both for your time and energy!
Click to expand...
Click to collapse
You make sure it wasn't a bad download? Check md5. I've had failed Odin's before. Just had to keep trying. I also unchecked "f reset time" when I flash. Also, try "wipe nand" option. I'd Google that first though.
Sent from my SGH-M919 using Tapatalk 2
elesbb said:
You make sure it wasn't a bad download? Check md5. I've had failed Odin's before. Just had to keep trying. I also unchecked "f reset time" when I flash. Also, try "wipe nand" option. I'd Google that first though.
Sent from my SGH-M919 using Tapatalk 2
Click to expand...
Click to collapse
This might be revealing my noobness a bit too much, but I'm not sure how to check md5 :/
I'll research the "wipe nand" option, might be worth a shot...
Is there anywhere I can download the stock SGH-M919 kernel?
Thanks again for all the help!
re: cable, usb port, drivers
WetbehindEars said:
This might be revealing my noobness a bit too much, but I'm not sure how to check md5 :/
I'll research the "wipe nand" option, might be worth a shot...
Is there anywhere I can download the stock SGH-M919 kernel?
Thanks again for all the help!
Click to expand...
Click to collapse
Why would you want to download the kernel?
The kernel is in the TAR file which you were trying to odin flash.
Best bet, try different cable, different usb port and it might even be a good idea if you go to the
Samsung USA website and download the latest usb drivers too.
If you do download the drivers, be sure to uninstall ALL samsung drivers, kies or any other Samsung
utility you have installed before installing the new samsung usb drivers.
I can tell you this for sure, if you cannot flash the stock firmware using Odin with your phone
you will need to take it to a Tmobile store and get it exchanged.
You should have no problem exchanging it since it's only 5 days old and you have not even
rooted it or flashed any custom firmwares to it.
Good luck!
Misterjunky said:
Why would you want to download the kernel?
The kernel is in the TAR file which you were trying to odin flash.
Best bet, try different cable, different usb port and it might even be a good idea if you go to the
Samsung USA website and download the latest usb drivers too.
If you do download the drivers, be sure to uninstall ALL samsung drivers, kies or any other Samsung
utility you have installed before installing the new samsung usb drivers.
I can tell you this for sure, if you cannot flash the stock firmware using Odin with your phone
you will need to take it to a Tmobile store and get it exchanged.
You should have no problem exchanging it since it's only 5 days old and you have not even
rooted it or flashed any custom firmwares to it.
Good luck!
Click to expand...
Click to collapse
Why would I want to download the kernel, you ask? I'll tell you why! Because I'm an Android infant and I have no idea what I'm doing!
It was because I was reading on an un-soft-brick how-to for a different phone and it mentioned flashing the kernel. But as you mentioned, it was completely unnecessary.
Last night, I made sure I was straight on the driver front (updated drivers, no Kies, etc.) and double checked the tar file I downloaded... the one thing I didn't do that I should have was plug my phone directly into my laptop; I only have one functioning USB port at the moment and it's occupied by a cooling fan. But the cooling fan has a USB port in it that I run my mouse through and it works fine, that's what I've had my phone plugged into during this whole process. Just plugged it directly into PC, ran Odin, worked flawlessly. I feel like an idiot for going through the fan, but the relief that came from seeing my S4 boot properly made up for it.
Thanks everyone for your help and attention, I know it's annoying getting inundated by greenhorns who need direction and I appreciate that you would be willing to help us get on our feet.
Thanks!
WetbehindEars said:
Why would I want to download the kernel, you ask? I'll tell you why! Because I'm an Android infant and I have no idea what I'm doing!
It was because I was reading on an un-soft-brick how-to for a different phone and it mentioned flashing the kernel. But as you mentioned, it was completely unnecessary.
Last night, I made sure I was straight on the driver front (updated drivers, no Kies, etc.) and double checked the tar file I downloaded... the one thing I didn't do that I should have was plug my phone directly into my laptop; I only have one functioning USB port at the moment and it's occupied by a cooling fan. But the cooling fan has a USB port in it that I run my mouse through and it works fine, that's what I've had my phone plugged into during this whole process. Just plugged it directly into PC, ran Odin, worked flawlessly. I feel like an idiot for going through the fan, but the relief that came from seeing my S4 boot properly made up for it.
Thanks everyone for your help and attention, I know it's annoying getting inundated by greenhorns who need direction and I appreciate that you would be willing to help us get on our feet.
Thanks!
Click to expand...
Click to collapse
Glad everything is working great! It was probably just a bad flash through odin. They happen from time to time. I am also wondering now if the USB on the cooling fan didn't have enough juice to fully power the whole process?
elesbb said:
Glad everything is working great! It was probably just a bad flash through odin. They happen from time to time. I am also wondering now if the USB on the cooling fan didn't have enough juice to fully power the whole process?
Click to expand...
Click to collapse
Yeah, the USB was probably already busy powering the fan and didn't want any of my Odin nonsense.
Thanks again for all the help!

Fix: semi bricked/bricked SPH-L710 Sprint S3

when I 1st rooted my s3 on 4.3, I messed it up lol I fixed it this way, which is installing a clean slate of 4.3 OTA via Odin...mine was a semi brick and keyboard was somehow gone as well, so this was my only choice:
1st download my bundle I made here
-once downloaded, extract the bundle preferably to your open desktop or wherever is easiest for you to guide through
your phone must have USB debugging mode enabled if you haven't done it already
-settings>more>developer options>enable usb debugging
-if you've never done this before, you'll have to go to: settings>more>about device>build number (tap on build number several times until the countdown states you're now a developer, once done press back once and developer options will now be present)
now once that's done, pull the battery, reinsert the battery and reboot into recovery by: holding volume up/home and power keys
once in recovery, do a factory data/cache wipe (fully wipe it out!)
now once that's done, pull your battery, reinsert your battery, hold: volume down/home and power keys and you'll be prompted with a warning and to press volume up to proceed, press volume up...this is "download mode"
on your computer, open the extracted bundle and run Odin 3.09 and make sure ONLY "auto reboot" and "f. reset time" boxes are checked
-connect your phone via usb cord and the ID: com will now light up and indicate it has detected your phone (if not, you'll need samsung drivers which can be found here)
-once recognized, load the necessary file by checking the box by the AP tab and then clicking the AP tab and load the .tar.md5 file in the bundled folder...this may take a few seconds, it's a large file so be patient
-once file is loaded, hit the "start" button and DO NOT INTERRUPT THIS PROCESS! once it's finished, again this is a large file and will take some time to finish, you'll see a "PASS" in Odin and also in the log box it will say "all threads completed (succeed 1/fail 0)
your phone will now reboot itself and restart with a freshly installed 4.3 OTA operating system! if it fails, try again and if it fails again, your phone may just be beyond repair...heard they can make a nice paper weight decoration lol GOOD LUCK!
To Reroot your phone: use my rooting guide
Nice post, I am sure that it will save someone.
Thanks OP!
I had a software brick and it worked out perfectly
phone_dude said:
Thanks OP!
I had a software brick and it worked out perfectly
Click to expand...
Click to collapse
thanks for the feedback and glad it worked! if you're looking to root it again, I have a guide up as well on doing that for 4.3, you won't brick by following that guide
Question, will doing this while on 4.3 and reinstalling 4.3 reset Knox counters? Or is there anyways yet to return to an unroofed stock with all Knox trips reset?
Sent from my SPH-L710 using Tapatalk
it should...this would be just like going to the sprint service techs and having them completely wipe and reinstall the 4.3 ota firmware like new
THANK YOU!!!!
Had a soft brick of my wife's phone. Had NO OS on the phone, wasn't able to flash ANY custom ROMs, even after ODINing and reODINing various recoveries.... Anyway... just nothing... Then THIS!
Great work. Wish I could hit Thanks 1000 more times. Cheers!
---------- Post added at 08:27 PM ---------- Previous post was at 08:26 PM ----------
Seriously. THIS is what should be stickied for returning to stock. Easy Peasy.
beejmeister said:
THANK YOU!!!!
Had a soft brick of my wife's phone. Had NO OS on the phone, wasn't able to flash ANY custom ROMs, even after ODINing and reODINing various recoveries.... Anyway... just nothing... Then THIS!
Great work. Wish I could hit Thanks 1000 more times. Cheers!
---------- Post added at 08:27 PM ---------- Previous post was at 08:26 PM ----------
Seriously. THIS is what should be stickied for returning to stock. Easy Peasy.
Click to expand...
Click to collapse
thanks for the compliments and glad it worked out for you, that's all that matters
Count my @$$ as saved
Well, looks like you saved my @$$. My phone noted that there was an update for cyanogenmod.... and bricked on reboot.
hi @goku2778
i'm about to try these instructions. you responded to my post in another thread. basically i'm still stuck. i've attempted several times to format data/wipe everything in the hopes of clearing the PIN code, or is it called PUC/PUK code that the phone wants to decrypt and boot into the ROM home screen. i used up the 10 attempts and it said "invalid PIN/password" or something like that, and keeps booting back to recovery to perform an automatic data reset.
but the problem is it still asks for a PUK/PIN code.
will your unbricking instructions that care of this?
-----------------------
WOOHOOO!!!! My ordeal has is over. Thank you very much for posting this. This cleared that pesky PIN code prompt like a champ.
And was able to update my PRL and Profile. Now I'll jump to one of the other ROMs, using your other thread.:good::laugh:
mister-crackers said:
hi @goku2778
i'm about to try these instructions. you responded to my post in another thread. basically i'm still stuck. i've attempted several times to format data/wipe everything in the hopes of clearing the PIN code, or is it called PUC/PUK code that the phone wants to decrypt and boot into the ROM home screen. i used up the 10 attempts and it said "invalid PIN/password" or something like that, and keeps booting back to recovery to perform an automatic data reset.
but the problem is it still asks for a PUK/PIN code.
will your unbricking instructions that care of this?
-----------------------
WOOHOOO!!!! My ordeal has is over. Thank you very much for posting this. This cleared that pesky PIN code prompt like a champ.
And was able to update my PRL and Profile. Now I'll jump to one of the other ROMs, using your other thread.:good::laugh:
Click to expand...
Click to collapse
just saw your post...glad it worked for you! let me know how you make out on your next tasks bro!
"Process com.android.phone has stopped"
How do you think I can modify to get this idea to work on my semi-bricked Sprint SGS3? I just can't get past that error message once the phone starts. It was a result of a bad flash of CM11, unified yesterday where i must have lost the connection somehow. I do have it set for debugging. but I can't use phone buttons to enter the recovery or download modes. Everytime I pull the battery and try to enter recovery, it says it is going there,but then the CM logo appears and then that darn message shows up again not allowing for me to get past it. I can see it with the computer via the USB however. Would you suggest or recommend something else(ie. trying to get it back to factory reset)? If so, then please leave a link for instx.
neadams99 said:
How do you think I can modify to get this idea to work on my semi-bricked Sprint SGS3? I just can't get past that error message once the phone starts. It was a result of a bad flash of CM11, unified yesterday where i must have lost the connection somehow. I do have it set for debugging. but I can't use phone buttons to enter the recovery or download modes. Everytime I pull the battery and try to enter recovery, it says it is going there,but then the CM logo appears and then that darn message shows up again not allowing for me to get past it. I can see it with the computer via the USB however. Would you suggest or recommend something else(ie. trying to get it back to factory reset)? If so, then please leave a link for instx.
Click to expand...
Click to collapse
damn...if you can't get into recovery, then I don't know what else you could do to be honest. 1 of those cm unifieds wrecked my phone also, my backup stock rom wouldn't load either, I could get into recovery but no other roms I downloaded would install, I had to do this method again...it took about 25 mins or so to do start to finish, finish meaning resetting up the phone after reinstalling 4.3 again and signing into it with Google id, updating the prl and profile to enable my data.
then spent another 20mins or so to reroot it, remove knox, and reinstall my cm11 package I have with the 2/03/2014 build release which I'm still on and phone has been awesome all over again. so if you can't get into recovery at all, I'd do the Odin 4.3 reinstall
Followed your steps using ODIN -passed- stuck on s'sng logo
goku2778 said:
damn...if you can't get into recovery, then I don't know what else you could do to be honest. 1 of those cm unifieds wrecked my phone also, my backup stock rom wouldn't load either, I could get into recovery but no other roms I downloaded would install, I had to do this method again...it took about 25 mins or so to do start to finish, finish meaning resetting up the phone after reinstalling 4.3 again and signing into it with Google id, updating the prl and profile to enable my data.
then spent another 20mins or so to reroot it, remove knox, and reinstall my cm11 package I have with the 2/03/2014 build release which I'm still on and phone has been awesome all over again. so if you can't get into recovery at all, I'd do the Odin 4.3 reinstall
Click to expand...
Click to collapse
Woah. THat is rough, but I need it to be awesome again. It's been 4+ hours and I am still going on trying to fix it. Total noob. So, you must slow down the steps you mentioned above for me to follow along. Should I try getting into DL mode again and rerun ODIN? Please advise.
neadams99 said:
Woah. THat is rough, but I need it to be awesome again. It's been 4+ hours and I am still going on trying to fix it. Total noob. So, you must slow down the steps you mentioned above for me to follow along. Should I try getting into DL mode again and rerun ODIN? Please advise.
Click to expand...
Click to collapse
lol try getting into download mode and if that works, just follow this guide along from download mode, don't worry about the debug part...let me know what happens with that part:
download mode, if it works, proceed with Odin flashing and report back
2nd attempt failed.
goku2778 said:
lol try getting into download mode and if that works, just follow this guide along from download mode, don't worry about the debug part...let me know what happens with that part:
download mode, if it works, proceed with Odin flashing and report back
Click to expand...
Click to collapse
Failed to get past the logo again on second ODIN attempt. Does your .tar file include CM11 or another? I'm wondering if there is any ROM on the device to upgrade to as I had an interruption when flashing to CM11. Also ve second screw up was that I did not wipe the data / cache prior to that attempt to upgrade. I did have TWRP and TiBackup Pro (ran on Sunday last) on device. How can I recover those files to reinstall to device?
neadams99 said:
Failed to get past the logo again on second ODIN attempt. Does your .tar file include CM11 or another? I'm wondering if there is any ROM on the device to upgrade to as I had an interruption when flashing to CM11. Also ve second screw up was that I did not wipe the data / cache prior to that attempt to upgrade. I did have TWRP and TiBackup Pro (ran on Sunday last) on device. How can I recover those files to reinstall to device?
Click to expand...
Click to collapse
wait...can you get into download mode? sounds like you can't, and if you can't get into that or recovery, dude you're probably pretty screwed.
um, there's a boot image unbrick method but it's quite complex and I've never done it myself, you'd have to search here for if in the general thread and it was made by cnexus...without the ability to go into recovery, you cannot flash a rom, without the ability to get into download mode, you can't use Odin
can get into DL mode passed ODIN but then stuck w/logo
goku2778 said:
wait...can you get into download mode? sounds like you can't, and if you can't get into that or recovery, dude you're probably pretty screwed.
um, there's a boot image unbrick method but it's quite complex and I've never done it myself, you'd have to search here for if in the general thread and it was made by cnexus...without the ability to go into recovery, you cannot flash a rom, without the ability to get into download mode, you can't use Odin
Click to expand...
Click to collapse
I can get into DL mode. Here is the readout from second ODIN attempt ( which shows it passed). <ID:0/006> Odin v.3 engine (ID:6)..
<ID:0/006> File analysis..
<ID:0/006> SetupConnection..
<ID:0/006> Initialzation..
<ID:0/006> Get PIT for mapping..
<ID:0/006> Firmware update start..
<ID:0/006> SingleDownload.
<ID:0/006> sbl2.mbn
<ID:0/006> NAND Write Start!!
<ID:0/006> sbl3.mbn
<ID:0/006> aboot.mbn
<ID:0/006> rpm.mbn
<ID:0/006> tz.mbn
<ID:0/006> boot.img
<ID:0/006> recovery.img
<ID:0/006> system.img.ext4
<ID:0/006> NON-HLOS.bin
<ID:0/006> cache.img.ext4
<ID:0/006> RQT_CLOSE !!
<ID:0/006> RES OK !!
<ID:0/006> Removed!!
<ID:0/006> Remain Port .... 0
<OSM> All threads completed. (succeed 1 / failed 0)
<ID:0/006> Added!!
<ID:0/006> Removed!!
<ID:0/006> Added!!
Why would it not allow me into recovery mode?? that just makes no sense to me. I've tried it a dozen times and know to hold the three buttons for a long while. Then the phone shows "recovery reboot" or something like that in blue micro font up in the left top corner but then the CM logo comes on and then I get stuck again on Samsung logo forever. looks like your .tar files have the MD5 only, right? WHat more do I need to push onto phone? Can we send these msgs to another person to help further?
Plus, as I said I've been auto backing up weekly so how to restore old files, ROM, etc...via USB?
neadams99 said:
I can get into DL mode. Here is the readout from second ODIN attempt ( which shows it passed). <ID:0/006> Odin v.3 engine (ID:6)..
<ID:0/006> File analysis..
<ID:0/006> SetupConnection..
<ID:0/006> Initialzation..
<ID:0/006> Get PIT for mapping..
<ID:0/006> Firmware update start..
<ID:0/006> SingleDownload.
<ID:0/006> sbl2.mbn
<ID:0/006> NAND Write Start!!
<ID:0/006> sbl3.mbn
<ID:0/006> aboot.mbn
<ID:0/006> rpm.mbn
<ID:0/006> tz.mbn
<ID:0/006> boot.img
<ID:0/006> recovery.img
<ID:0/006> system.img.ext4
<ID:0/006> NON-HLOS.bin
<ID:0/006> cache.img.ext4
<ID:0/006> RQT_CLOSE !!
<ID:0/006> RES OK !!
<ID:0/006> Removed!!
<ID:0/006> Remain Port .... 0
<OSM> All threads completed. (succeed 1 / failed 0)
<ID:0/006> Added!!
<ID:0/006> Removed!!
<ID:0/006> Added!!
Why would it not allow me into recovery mode?? that just makes no sense to me. I've tried it a dozen times and know to hold the three buttons for a long while. Then the phone shows "recovery reboot" or something like that in blue micro font up in the left top corner but then the CM logo comes on and then I get stuck again on Samsung logo forever. looks like your .tar files have the MD5 only, right? WHat more do I need to push onto phone? Can we send these msgs to another person to help further?
Plus, as I said I've been auto backing up weekly so how to restore old files, ROM, etc...via USB?
Click to expand...
Click to collapse
you're making me wanna beat you!! lol jk OK, read me/hear me and follow lol
you flashed 4.3 with Odin and looks like it worked, it should have auto reset itself after it worked and started booting back up into it's now completely stock rom...with me? you should see the Samsung logo working, it takes a good minute or 2 to finish its initial boot up after Odin, then like the 1St day you bought it you'll need to connect to a Wi-Fi source, sign in with a Google ID
did you do that or are you skipping the most important part of restoring your phone into working condition by right away trying to get into recovery mode?????? if so, please slap yourself hard!!! lol it must boot up and fully initialize, forget about recovery and back up roms right now, it must initialize like you just bought the phone new and set it up
THEN........
you have to reinstall philz recovery with Odin, remove the knox again and reroot by reinstalling supersu
saying it 1 last time...let the phone reboot itself after you performed the Odin steps from this guide and set up your phone like you just bought if brand new from sprint
do that, report back and stop messing with recovery steps and rom this and that or I'm not helping you bro!! lol report back
Not getting past Samsung logo
goku2778 said:
you're making me wanna beat you!! lol jk OK, read me/hear me and follow lol
you flashed 4.3 with Odin and looks like it worked, it should have auto reset itself after it worked and started booting back up into it's now completely stock rom...with me? you should see the Samsung logo working, it takes a good minute or 2 to finish its initial boot up after Odin, then like the 1St day you bought it you'll need to connect to a Wi-Fi source, sign in with a Google ID
did you do that or are you skipping the most important part of restoring your phone into working condition by right away trying to get into recovery mode?????? if so, please slap yourself hard!!! lol it must boot up and fully initialize, forget about recovery and back up roms right now, it must initialize like you just bought the phone new and set it up
THEN........
you have to reinstall philz recovery with Odin, remove the knox again and reroot by reinstalling supersu
saying it 1 last time...let the phone reboot itself after you performed the Odin steps from this guide and set up your phone like you just bought if brand new from sprint
do that, report back and stop messing with recovery steps and rom this and that or I'm not helping you bro!! lol report back
Click to expand...
Click to collapse
So so Sorry, if you were in CA, I'd come by so you could do it yourself. I;d even pay you good money. OK, sorry, I was freakin out, brah.
I did use ODIn and waited for a long time and the Samsung logo just hangs there. There is no progress, nothing. I can't get to the signing into Google or anything at all.
You said, " THEN you have to reinstall philz recovery with Odin, remove the knox again and reroot by reinstalling supersu." But I cant get past the logo. I see the "Samsung" for two secs, then "Samsung Galaxy Slll" then the Sprint logo goes by with music, then back to the "Samsung" logo where it sits forever. This is killing me.

[Q] Soft-bricked and Need Help - [d2att]

Hey all,
After hours of intense Googling, I've finally reached my limit and decided to make a forum post. I don't know what kind of info you guys need to help me out so I'm including everything I know.
Before you guys say anything, I've looked at the sticky and went through the soft-bricked guide, but it says to just flash back to stock, which I already tried.
Here is the backstory:
I had Cyanogenmod 10.2 installed (using the default get.cm installing process) for about a month when a notification popped up prompting me to install a system update. I had it only set up to install stable updates (or so I thought), so I installed it and it ended up being stuck in a boot loop. Unfortunately, all of my data was encrypted and I couldn't figure out how to recover it, but I just thought screw it, formatted everything, and reinstalled Cyanogenmod 10.2.1 using Clockwork Recovery. I also ended up trying to install gapps using a zip using Clockwork Recovery as well, but it still wouldn't show up even though the install passed in Clockwork without any problems. Soo, I figured to try to install using get.cm again and during the reboot process during install, it froze (I left it running for an hour to no avail).
Now I'm stuck in this situation:
~ The phone is stuck on the waving blue alien and won't finish booting.
~ Cannot access Clockwork Recovery. Just goes back to the blue alien even though I see the blue debug text in the upper left on the Samsung screen when holding Power, Vol. Down, and Home that suggests it will open Clockwork Recovery.
~ I can still access the Download mode.
~ My computer can still see the phone in ODIN v3.07.
Here's the troubleshooting I've tried to do:
~ I made a TAR archive with the boot.img file from the CM10.2.1 zip and renamed the boot.img to zImage (no extension). Tried flashing it in the PDA input and I get this ODIN output:
<ID:0/003> Added!!
<ID:0/003> Odin v.3 engine (ID:3)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> zImage
<ID:0/003> NAND Write Start!!
<ID:0/003> FAIL!
<OSM> All threads completed. (succeed 0 / failed 1)
Here is my phone's text in the top right:
ODIN MODE
PRODUCT NAME: SGH-I747
CUSTOM BINARY DOWNLOAD: Yes (7 counts)
CURRENT BINARY: CUSTOM
SYSTEM STATUS: Official
QUALCOMM SECUREBOOT: ENABLE
WARRANTY Bit: 1
BOOTLOADER RP SWREV: 2
SW REV CHECK FAIL : Fused 2 > Binary 0
Unsupport dev_type
~ Tried the same thing above with stock rom too. Same errors and everything.
~ I've tried installing Clockwork Recovery again using heimdall and it looked like it installed fine, but I still can't access it.
Any help is greatly appreciated. Thanks!
UPDATE: I tried installing adb but it can't detect my device in download mode.
UPDATE 2: I found a small glimmer of hope that seems like it's a similar issue to what I'm having: http://forum.xda-developers.com/showthread.php?t=2427016
Problem is, is that it looks like my internal SD might be corrupted and I might have to resort to a hardware mod. I'd rather not take out my internal SD if I don't have to, so do any of you guys have any ideas or thoughts on fixing this?
[SOLVED] Woo!
So I noticed after leaving my phone plugged in for a while that the bootloop started occurring on the other cyanogenmod loading screen with the arrow circling around the logo. Seeing something was different, I rebooted my phone and lo and behold, I managed to get into Clockwork Recovery! I installed the cyanogenmod zip I had from earlier and managed to boot it up fully! I got Google Apps on there and updated successfully to CM11.
I guess the thing to take from this is to make sure your phone is fully charged before troubleshooting.
Glad to see you solved it w/o having to replace the motherboard.
When I saw you renamed the bootloader to zImage I caught my breath. I think the kernel is zImage and the bootloader is boot.bin, or Sbl.bin for the secondary bootloader. (At least for flashing in Heimdall.)
dawgdoc said:
Glad to see you solved it w/o having to replace the motherboard.
When I saw you renamed the bootloader to zImage I caught my breath. I think the kernel is zImage and the bootloader is boot.bin, or Sbl.bin for the secondary bootloader. (At least for flashing in Heimdall.)
Click to expand...
Click to collapse
Thanks for the info For some reason it never occurred to me to flash CM using Heimdall, haha. Still kinda new to this stuff and good thing ODIN caught my mistake. I was blindly trying things on forums and renaming boot.img to zImage was one of the things I read, but looking at more forum answers, I'm now realizing that zImage is actually in the boot.img file in the CM zip.

[Q] Tab pro 12.2 stuck in bootloop

Hi everyone!
My Galaxy tab pro (SM-T900) is stuck in bootloop. More precisely I can see the first Samsung galaxy tab pro screen but it restart before the samsung animation.
The tab was initially with official rom rooted with CF-Auto-Root-v2wifi-v2wifixx.
I have already tried several things without significative improvement.
At first I tried to reinstall with Kies. Kies says my version is: PDA:NB5/CSC:NB2 (XEF). But after the window asking to reboot in download mode kies stops saying my device can not be recovered. I have read it could be due to a discrepancy of CSC or things like that between Kies and the Tab.
Recovery mode says:
Odin mode
Product name: SM-T900
Current binary: Official samsung
System status: Custom
KNOX waranty void: 1
RP SWREV: A1
My Knox flag was turned to 1 and I don't know how to set System status back to official.
I have also downloaded the stock ROM XEF from Sammobile and flashed it with odin 3.09. The process goes smoothly but the tab doesn't boot.
Even after a wipe (data/factory reset and cache) in recovery mode.
In recovery mode I could not install Cyanogenmod or other Zip files. The process stop during the package verification and says:
E:footer is wrong
E:signature verification failed
I flashed a TWRP 2.8 to try with a different recovery but again the Zip are not installed.
Have you any idea or any direction to investigate?
Thank you
If ur tab is US version then u have to flash XAR(cellular south) available through sammobile through odin and then let tab update itself after reboot. U will loose root
Sent from my LG-D800 using XDA Free mobile app
lingarajug said:
If ur tab is US version then u have to flash XAR(cellular south) available through sammobile through odin and then let tab update itself after reboot. U will loose root
Sent from my LG-D800 using XDA Free mobile app
Click to expand...
Click to collapse
Actually my tab is from France so XEF version is the most adapted.
I think flashing a different version would be rejected. Right?
Yes it can brick too
Sent from my LG-D800 using XDA Free mobile app
You can flash any ROM as long as it is for SM-T900. The builds may have different apps, keyboards, and WiFi connectivity can be an issue due to WiFi channels being slightly different for each region.
The thing is that flashing zip in recovery mode leads to the error: footer is wrong.
Is there any log file I could read to find where the boot process loops?
If dodo99x is right u can flash xar version which is for usa and flash it through odin
Sent from my LG-D800 using XDA Free mobile app
I tried to flash XAR and XAC stock roms but Odin return a Fail with the following log:
<ID:0/012> Added!!
<ID:0/012> Odin v.3 engine (ID:12)..
<ID:0/012> File analysis..
<ID:0/012> SetupConnection..
<ID:0/012> Initialzation..
<ID:0/012> Get PIT for mapping..
<ID:0/012> Firmware update start..
<ID:0/012> SingleDownload.
<ID:0/012> sboot.bin
<ID:0/012> NAND Write Start!!
<ID:0/012> boot.img
<ID:0/012> recovery.img
<ID:0/012> system.img
<ID:0/012> FAIL!
<ID:0/012>
<ID:0/012> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
As tar.md5 files doesn't have exactly the same size, I wonder if it is necessary to check Re-partition in Odin.
Never ever touch repartition. Super dangerous if you don't have the correct .pit file to recreate them. Those sound like bad downloads. You can also try to use a different usb cable and usb port on your pc.
I have successfully downloaded and installed the last rom stock revision for France: T900XXUANI1_T900XEFANI2_XEF
But I'm still stucked in Bootloop.
Other versions (XAR and XAC) still fail.
How can I get the PIT file for SM-T900?
As I can see and copy files with TWRP, is there any log file I should check to see what is wrong?
I would try wiping cache, sytem, dalvik, data and internal storage in twrp, then reinstall the france image file in Odin. This will of course erase all data you have on the tablet, but it should take you out of your bootloop. I have yet to see any valid PIT files for the SM-T900, or SM-P900. If you mess with the partitions without one, you won't even be able to flash anything in Odin afterwards.
No problem for the personnal data. I just would like to recover my tab.
I have wiped all the internal partitions: Dalvik, cache, system, internal data.
I have reboot in download mode and launched a flash of the T900XXUANI1_T900XEFANI2_HOME.tar.md5 with Odin 3.09
I also used voodoo magic!
But still the bootloop
I think the problem comes from an other partition not flashed with this process.
What other partitions are used to start Android?
Is there any log file to check?
Very unusual... try flashing cm11 for SM-T900 via TWRP. Will that one boot?
No The Cyanogen ROM doesn't boot either.
I'm still looking deeper in the boot process to identify the problem.
While I was reading this: http://en.miui.com/thread-15659-1-1.html
I just realized that the misc partition was absent from my tab.
I create an empty one and reflashed a stock rom but it doesn't solve the boot problem.
What files are usualy inside misc? Where can I find a copy of them?
At this point I would just get Samsung to fix it. Unless you can find a PIT file for ODIN...
Even with Knox value to 1 and custom Rom/kernel/recovery?
Do you think Samsung will reset my tab in those conditions?
By the way, when I look in the Boot folder with TWRP file manager, I don't see any file. The boot partition indicates an occupied size of 8Mo.
Where are those files? How can I acces to them?
Knox warranty has nothing to do with your hardware warranty. Just reflash stock rom via ODIN and send it back. Tell them you can't get it to boot, and that's it.
Do u know if u have usb debugging enabled. Maybe try booting into rom after complete wipe of all. It will probably sit on sam logo and will not boot due to no firmware and wait for few minutes and restart into download mode and flash correct firmware from sammobile. I did this in my old galaxy s 2 long long ago and it worked.
Sent from my LG-D800 using XDA Free mobile app
Hi,
Just a short feedback.
I finally succeed to finish the restoring process of Kies but it didn't fixed my bootloop and the Download mode indicated:
Current binary: Samsung official
System status: Custom
Knox warranty void: 0x1
I decided to return the device to Samsung (France).
3 weeks after: tadaam! Everything was fixed. Samsung changed my motherboard and battery.
No charge and no warranty void due to knox or rom modification.
I am so released
... I am now looking for a way to root the device without triggering knox
Is triangle away working with SM-T900?
Moklockus said:
Even after a wipe (data/factory reset and cache) in recovery mode.
In recovery mode I could not install Cyanogenmod or other Zip files. The process stop during the package verification and says:
E:footer is wrong
E:signature verification failed
I flashed a TWRP 2.8
Click to expand...
Click to collapse
To fix this try
Advanced wipe with everything ticked except recovery then try to flash zip without reboot.
Helped me on the footer issue and if this succeeds you should be able to boot.
Hope that helps

Looking for a debrick.img for Android 5.1.1

Is anyone able to point me in the right direction or is willing to make one?
The i747 does not have a stock 5.1.1 rom; therefore, there is no debrick image for a 5.1.1 rom.
What bootloader is on the phone? Did any of the images from the debrick thread boot the phone?
Does installing 5.1 change your bootloader?
As in Cyanogenmod 12.1?
Softbricked my S3, and I'm not sure which way to attempt to recover/debrick & would appreciate any advice.
SGH I747 (ATT)
rooted 2 years ago just after 4.3 OTA updated, flashed with CM 11.
Had that on there for almost a year, got bored & installed carbonrom.
Beginning of december, flashed CM 12.1.
A week ago it got stuck on the boot logo.
Still able to get into both Recovery & download modes.
Clockwork mod 6.0.4.7
trying to flash from a new image or wipe & factory restore both give me
Code:
detected file system ext4 for /dev/block/platform/msm_sdcc.1/by-name/system
patching unconditionally
E: error in /storage/sdcard1/cm-12.1-201511117-sna[status 0] installation aborted
trying to use Odin, it gives me
Code:
<ID:0/003> Added!!
<ID:0/003> Odin v.3 engine (ID:3)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> recovery.img
but never does anything, even hours later.
At unplug, I get
Code:
<ID:0/003> __Xmit Write fail
<ID:0/003> XmitData Fail..
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/003> Removed!!
The info on the download screen is
Code:
odin mode
product name: sgh-i747
custom binary download: yes (6 counts)
current binary: custom
system status: custom
qualcomm secureboot: enable
warranty bit: 1
bootloader ap swrev: 2
My guess from another thread is that the /system and /data partitions are not wiped properly, causing those partitions to be formatted with read-only (R/O) permissions rather than read-write (R/W)? But those files are definitely not right for my phone, so what now?
Use twrp to as cwm is out of date. Once on twrp, you can try flashing cm12.1 again.
Flashing a custom rom via twrp does not touch the bootloader or modem.
Do not flash any files via Odin as doing so could result in a hard brick. Once the phone is on a 4.3 or newer bootloader, Odin cannot be used.
audit13 said:
Use twrp to as cwm is out of date. Once on twrp, you can try flashing cm12.1 again.
Flashing a custom rom via twrp does not touch the bootloader or modem.
Do not flash any files via Odin as doing so could result in a hard brick. Once the phone is on a 4.3 or newer bootloader, Odin cannot be used.
Click to expand...
Click to collapse
Good to know.
Thanks.
But how do I get twrp onto the phone?
was actually trying to put twrp on with odin, but that's not working.
The downloads I've seen are for:
app-phone doesnt boot
odin- aint working
TWRP Install - Requires TWRP 2.8.4 or higher already installed
dd Install Method - oh, didn't see that one. I'll try that & let you know.:laugh:
---------- Post added at 06:54 AM ---------- Previous post was at 06:16 AM ----------
well, I'm not figuring it out....
As per the twrp page, tried: dd if=/sdcard/twrp-2.8.7.0-d2att.img of=/dev/block/mmcblk0p18
file not found error
tried: dd if=/storage/sdcard1/twrp-2.8.7.0-d2att.img of=/dev/block/mmcblk0p18
file not found error
did ls (hey it's like linux!)
got possible locations: external_sd, sd-ext, sdcard, also looked under mnt.
file not found error
cd'ed & ls'ed to /storage/sdcard1/ there it frickken is!
ran the command there, sans path, and still get file not found error
arrrrgh.
Try this:
1) download Odin 3.07 from here: https://www.google.ca/url?sa=t&rct=j...07763241,d.dmo
2) download the tar version of TWRP 2.8.7.0 from here: https://dl.twrp.me/d2att/
3) download the latest cm12.1 for the phone from here ( http://www.cmxlog.com/12.1/d2att/) and save it to a micro SD card;
4) download the version of cm12.1 gapps you want from here (https://wiki.cyanogenmod.org/w/Google_Apps) and save it to the same sd card where you saved CM12.1;
5) place the micro SD card into the phone;
6) boot the phone into download mode;
7) open Odin 3.07 and uncheck everything except f. reset time;
8) click on PDA and browse to the tar TWRP file and select it;
9) connect the phone and it should show up as a com port in Odin;
10) flash TWRP;
11) when you see the word RESET in the status window, remove the USB cable, remove the battery, replace the battery, use the button combination to get into recovery which should now be TWRP;
12) perform a full wipe of system, data, and cache;
13) flash CM12.1 and gapps from the micro SD card;
14) reboot and enjoy
very detailed response, thanks. I've tried most of that, as some thread I was reading said that twrp probably has the capability to fix the issue, and CWM definitely doesn't.
Odin never really does anything, though. How long should I wait?
This step is the one I haven't done "7) open Odin 3.07 and uncheck everything except f. reset time;" Just left everything alone the multiple times I tried. Hopefully that'll make a difference.
Tried 3.07, 3.09, 3.10.6. I'll try again.
By default in Odin 3.07, only auto reboot and f reset time are checked.
What do you mean when you say Odin does nothing? Does the phone appear as a com device in Odin? Are there error messages in Odin during the flash process?
never gives anything other than:
Code:
<ID:0/003> Added!!
<ID:0/003> Odin v.3 engine (ID:3)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> recovery.img
not at a windows computer for a couple days. stuck on linux mint with no internet. has heimdall & adb, though....
have twrp img & tar, cm12.1, and gapps on the sdcard.
All I can suggest is to try and get access to a pc or try VMware with win7.
Tried again last night for about 12 hours, no response from Odin.
Decided to give jtag a shot.
Contacted the jtag guy & gave him all the above info.
He says
"Unfortunately there are many indicators that your phone has a hardware failure.... Most likely a failed emmc memory chip.
1) the phone getting stuck on boot logo for no reason.
2) Odin not flashing...
3) files not found or... Not being able to do.
These are all indicators that the emmc memory chip is toast...... The biggest clue is finding the phone stuck on boot logo... Out of nowhere for no reason.
Jtag would not be able to fix it.
Thank you"
:crying::crying::crying::crying::crying::crying:
Thanks for the help.
Might sell the remains.
16G I747 blue, normal wear & tear, small chip in one corner, the case covers it.
2 stock batteries
1 7800mah best4power battery
1 otterbox defender modified to hold extended battery without the turtleback
any offers?
i suggest trying on a Windows machine before giving up. I am not convinced the memory is damaged.
That was on a windows machine...
Odin recognizes the phone but it won't flash twrp? Have you tried different USB cables and USB ports?
I found that my s4 and s3 would fail to flash if I don't use the USB cable that came with my Samsung or LG phones.
yes to both cable & ports.
bought an LG K7, which I mostly hate, and can not root.
keeping my S3, looking for someplace cheap to replace the chip.
I bought my lg k7 today(LGMS330)metropcs i rooted it in 2 mins.with xda's KINGROOT..then removed Kingroot with WOLFDROIDS script...and now im running BUSYBOX STERICSON 1.24.1 and ChainFires SUPERSU 2.49..IT KILLS me when people cant root there devices...i did this ALL in the BURGERKING BATHROOM GOIN BOO BOO
Ok so i rooted my darn k7 ...but like a jackars i bricked it...no TWRP...NO KDZ FIRMWARE...CAN ANYONE PLEASE ...PRETTY PLEASE SEND ME A LINK TO THE METROPCS variant of the LG K7 (TRIBUTE 5) KDZ STOCK FIRMWARE..I JUST BOUGHT A $150 ELECTRONIC PAPERWEIGHT...the k7 is so new there is no support anywhere...in fact all u really find is the ads for the debut of the device in stores ...major noob mistake..im truly embarassed..PLZ HELP
yeah, got it rooted. was missing the "enable oem unlock" step. d'oh.
thanks for the tip on the script.
no idea on the firmware. if you find one, let me know.
just got a $150 paperweight...lg ms330 i do hate you now...
o4tuna said:
yeah, got it rooted. was missing the "enable oem unlock" step. d'oh.
thanks for the tip on the script.
no idea on the firmware. if you find one, let me know.
Click to expand...
Click to collapse
I'm in the same boat as you...unfortunately tht step was completely left out in the directions I used so I now have a $150 paper weight as well....if anyone finds the stock firmware plz plz plzzzzzz let me know I would be forever gratefull....
AbErCrMbPlAyA said:
I'm in the same boat as you...unfortunately tht step was completely left out in the directions I used so I now have a $150 paper weight as well....if anyone finds the stock firmware plz plz plzzzzzz let me know I would be forever gratefull....
Click to expand...
Click to collapse
I had a amazing talk with the lg develeopers yesterday....since I am in the same boat since my lg k7 is bricked....I ask them for the kdz firmware so I can reflash my phone....you wanna know what they told me?
first they ask: whats a kdz file?
their answer: We don't make those thing you need the official lg tools to update your device firmware....so we cant help you...
Me: I am extremely pissed now since they are lying to me & then I showed them a link from their server to DOWNLOAD a kdz file firmware for another device that I had....
their answer: we dont know what you are talking about...sorry we can't help you!
I even went to my nearby metropcs store & explained to him what happen...
first. he didn't understand the following:
1-bootloader
2. boot image
3. recovery mode
4. download mode
5. kdz firmware
6. bricked & softed-bricked
the f-cking guy told me I can't do anything, but "report my phone lost or stolen" so I can get a new one....
How the hell are these idiots getting jobs when they have NO IDEA what to do on how to fix a phone
My level of anger is now over 9000.....

Categories

Resources