Related
Hey guys,
The GT-N7100 of my friend does not boot.It is stuck at the first screen ( Black screen with samsung galaxy note II gt-n7100).
He tried to install a custom rom and installed a Custom Recovery. In Custom Recovery the cache partition couldnt be load. So I cant wipe or format anything. If I want to install a zip, the Recovery just get stuck before even selecting a zip file.
I can access download mode. So I tried to flash another recovery. Odin says successful but the recovery is still the same ????
I also tried to flash a stock rom with Odin... nothing changed
So I dont know what to do next
Please help me!
Thanks in advance
Luke44 said:
Hey guys,
The GT-N7100 of my friend does not boot.It is stuck at the first screen ( Black screen with samsung galaxy note II gt-n7100).
He tried to install a custom rom and installed a Custom Recovery. In Custom Recovery the cache partition couldnt be load. So I cant wipe or format anything. If I want to install a zip, the Recovery just get stuck before even selecting a zip file.
I can access download mode. So I tried to flash another recovery. Odin says successful but the recovery is still the same ????
I also tried to flash a stock rom with Odin... nothing changed
So I dont know what to do next
Please help me!
Thanks in advance
Click to expand...
Click to collapse
well flash philz recovery via odin
untick "autoreboot" in odin. Once flash is done, keep pressing power button until it reboots (normally will go to recovery)
when in recovery, if you choose option "reboot system now" and you get "yes - disable flash recovery", select that option to avoid stock recovery overwriting cwm
now proceed with wipe and after flashing rom ,fix permission and wipe cache and dalvic cache twice then reboot
shhbz said:
well flash philz recovery via odin
untick "autoreboot" in odin. Once flash is done, keep pressing power button until it reboots (normally will go to recovery)
when in recovery, if you choose option "reboot system now" and you get "yes - disable flash recovery", select that option to avoid stock recovery overwriting cwm
now proceed with wipe and after flashing rom ,fix permission and wipe cache and dalvic cache twice then reboot
Click to expand...
Click to collapse
I flashed philz recovery. After pressing the power button just the battery symbol appeared... no reboot. So I treid to boot into the new recovery... but still the old recovery boots
Heres the log from Odin:
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> philz_touch_5.11.2-n7100.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<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
<ID:0/003> NAND Write Start!!
<ID:0/003> RQT_CLOSE !!
<ID:0/003> RES OK !!
<ID:0/003> Removed!!
<ID:0/003> Remain Port .... 0
<OSM> All threads completed. (succeed 1 / failed 0)
<ID:0/004> Added!!
http://forum.xda-developers.com/showpost.php?p=32273406
I wanted to try this, but this download contains just one file. Even if I extract the tar, there are not the files included which are discribed in the thread...
quite strange....
I simply cant flash anything with Odin. Odin says success, but nothing happened to the phone. I didnt read something about people who are having the same issue
This drives me mad .....
Luke44 said:
http://forum.xda-developers.com/showpost.php?p=32273406
I wanted to try this, but this download contains just one file. Even if I extract the tar, there are not the files included which are discribed in the thread...
quite strange....
I simply cant flash anything with Odin. Odin says success, but nothing happened to the phone. I didnt read something about people who are having the same issue
This drives me mad .....
Click to expand...
Click to collapse
well its not sds for sure so it seems either recovery has gone corrupted as,the pit file u said is not required though u can find it here to http://forum.xda-developers.com/showthread.php?t=1896696 post 4 no4 pit file16gb
but i would suggest you to try the recovery thing as mentioned in the link as see as the one i mentioned is used when it does not enter recovery try this version http://d-h.st/vCc
keep the power button pressed it should enter recovery leave the power button when u see samsung logo
I did it long time back so dont remember exactly whether to keep pressing power button or to hold power button worked for me as auto reboot was not working for me so did the other way round as mentioned to you
shhbz said:
well its not sds for sure so it seems either recovery has gone corrupted as,the pit file u said is not required though u can find it here to http://forum.xda-developers.com/showthread.php?t=1896696 post 4 no4 pit file16gb
but i would suggest you to try the recovery thing as mentioned in the link as see as the one i mentioned is used when it does not enter recovery try this version http://d-h.st/vCc
keep the power button pressed it should enter recovery leave the power button when u see samsung logo
I did it long time back so dont remember exactly whether to keep pressing power button or to hold power button worked for me as auto reboot was not working for me so did the other way round as mentioned to you
Click to expand...
Click to collapse
Im glad to hear that it is not sds.
I tried to flash the recovery of your link:
If I leave the phone connected if I press the power button after flashing just the battery symbol apears after a while.
If I disconnect the phone, it tries to boot normal...no recovery...
If I tap on the power button again and again nothing happens.....
If I try to boot into recovery with the 3 button combo there is still the old clockwork recovery.
I also tried to do a emergency recovery with kies. Kies does download all the files and when it starts to flash it gets stuck at 0 % and sais phone is not connected in the right way but it is...
In Odin mode the phone displays
custom binary downloads : Yes ( 1 counts)
But did flash the recovery at least 3 times ...So why does it still display 1
Luke44 said:
Im glad to hear that it is not sds.
I tried to flash the recovery of your link:
If I leave the phone connected if I press the power button after flashing just the battery symbol apears after a while.
If I disconnect the phone, it tries to boot normal...no recovery...
If I tap on the power button again and again nothing happens.....
If I try to boot into recovery with the 3 button combo there is still the old clockwork recovery.
I also tried to do a emergency recovery with kies. Kies does download all the files and when it starts to flash it gets stuck at 0 % and sais phone is not connected in the right way but it is...
In Odin mode the phone displays
custom binary downloads : Yes ( 1 counts)
But did flash the recovery at least 3 times ...So why does it still display 1
Click to expand...
Click to collapse
do u have kies installed when u trying odin if yes then delete it just install the samsung drivers nothing else and disable your antivirus too.
orelse u may try
thats quite strange ok now its time to try the mskip tool just delete all old samsung drivers and kies
and start fresh from here http://forum.xda-developers.com/showthread.php?t=1923956
and as far as the count in concerned its 1 as you were only able to enter recovery once thats why after that u were not able to so as many times u enter custom recovery the count increases
http://forum.xda-developers.com/showthread.php?t=1896696
Do you think it makes sense todo re-partition with the pit file?
There is also a Bootloader to download on this site...
Luke44 said:
http://forum.xda-developers.com/showthread.php?t=1896696
Do you think it makes sense todo re-partition with the pit file?
There is also a Bootloader to download on this site...
Click to expand...
Click to collapse
i would say no until there is an error which shows no pit partition found but after the above steps if it does not then u can give it a fresh start flash the pit first then the firmware . check youtube as how to do it there are vidoes described on how to flash pit and then the firmware.
i would suggest not to do something which you are not sure of and land urself in other issues though flashing pit and firmware is fine but i am not sure about the bootloader maybe u can ask in that specific thread , keten might be the best person to guide you in that case if its safe
shhbz said:
i would say no until there is an error which shows no pit partition found but after the above steps if it does not then u can give it a fresh start flash the pit first then the firmware . check youtube as how to do it there are vidoes described on how to flash pit and then the firmware.
i would suggest not to do something which you are not sure of and land urself in other issues though flashing pit and firmware is fine but i am not sure about the bootloader maybe u can ask in that specific thread , keten might be the best person to guide you in that case if its safe
Click to expand...
Click to collapse
Sorry but I cant find such a viedo...
Luke44 said:
Sorry but I cant find such a viedo...
Click to expand...
Click to collapse
I tried to flsh this, but odin says:
<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> Set PIT file..
<ID:0/003> DO NOT TURN OFF TARGET!!
<ID:0/003> Get PIT for mapping..
<ID:0/003>
<ID:0/003> There is no PIT partition.
<OSM> All threads completed. (succeed 0 / failed 1)
What exact information you can see on Download Mode Rt Upper corner.
post full details here
dr.ketan said:
What exact information you can see on Download Mode Rt Upper corner.
post full details here
Click to expand...
Click to collapse
In the right upper corner is nothing...
In the left upper corner:
ODIN MODE (written in red)
PRODUCT NAME: GT-N7100
CUSTOM BINARY DOWNLOAD: Yes (1 counts)
CURRENT BINARY: Custom
SYSTEM STATUS: Custom
Try different USB port, don't use any extension cable to connect device.
close firewall and still issue try different cable and PC
Download PIT
select it for PIT tab (It will auto select re-partition, keep it selected) - Flash
Also confirm Kies is not running in BG
Luke44 said:
Sorry but I cant find such a viedo...
Click to expand...
Click to collapse
There is I am on phn so would be difficult for me to find but its simple u just select the pit file first in odin and flash keeping ur phn in download mode and then the firmware tar file
Try different USB port, don't use any extension cable to connect device.
close firewall and still issue try different cable and PC
Download PIT
select it for PIT tab (It will auto select re-partition, keep it selected) - Flash
Also confirm Kies is not running in BG
Click to expand...
Click to collapse
I tried a different computer with different cable. On the computer I used this time there is not even kies installed.
Same result as before...
dr.ketan said:
Try different USB port, don't use any extension cable to connect device.
close firewall and still issue try different cable and PC
Download PIT
select it for PIT tab (It will auto select re-partition, keep it selected) - Flash
Also confirm Kies is not running in BG
Click to expand...
Click to collapse
I tried it a few more times..it really doesnt work
Whats wrong with this !"§$%& phone:crying::crying::crying:
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.
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
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.....
I have a Samsung SGH-M919 T-Mobile S4 phone which ran stock 4.2.2 firmware. It was brick when I tried to root it. It is able to go to download mode.
I downloaded M919 4files repair firmware (Odin3 v3.09.3, AP_M919UVUFNB4 stock rom , JFLTE_USA_TMO.pit..) from TSAR3000.com. I uninstalled Samsung Kies. It passed when run Odin3 with JFLTE_USA_TMO.pit. But it failed with message showed: Complete(Write) operation failed when I flashed downloaded stock 4.2.2 rom.
Do you have any experience to resolve this issue?
Do I use any wrong version of Odin3, M919 stock rom or .pit file?
Do you have exact worked SGH-M919 stock 4.2.2 firmware, Odin3 and .pit file so that I can fix my phone?
Thank you very much!
The Odin3 message:
<ID:0/004> NAND Write Start!!
<ID:0/004> recovery.img
<ID:0/004> persdata.img.ext4
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/004> Removed!!
Try the stock firmware from sammobile.com. The pit file may not be required unless Odin cannot read the partition table from the phone.
I'd recommend flashing the lastest stock firmware:
http://forum.xda-developers.com/showthread.php?p=64431358
Odin v3.09 has never given me problems. Follow the directions in the first post of the thread.
Can Not Enter Recovery Mode By Three Keys
Thank you very much for helping. I used another computer to run Odin3 and flashed full version 4.4.4 stock firmware successfully. Now the Samsung S4 is able to run 4.4.4 stock rom without any problem after root and TWRP 2.8.7.0 installed. I am able to reboot it to recovery mode from TWRP Manager which was downloaded from Play Store. But it NOT able to going to recovery mode by press Vol up+Home+Power buttons, even stock recovery installed before TWRP installed. It still is able to going to download mode by press Vol down+Home+Power buttons. How to fix "Can Not Enter Recovery Mode By Three Keys" issue?
Thank you very much!