Related
I think my infuse finally died completely. For the past couple days I was getting SOD every 2 or 3 hours. Finally I decided to do the back to stock http://forum.xda-developers.com/showthread.php?t=1092021. I follow all of the instructions, but the program stopped working. Then I decided to try again, but this time only pixels came up. I removed the battery and tried again and all I'm getting is a white screen with pixels. Recovery mode does not work, nor does download mode. The phone also starts overheating if I plug it into a charger. Is there anything I can do?
Update: After trying to blindly navigate download mode and 20 tries of odin, it finally succeeded
Fireaxil said:
Update: After trying to blindly navigate download mode and 20 tries of odin, it finally succeeded
Click to expand...
Click to collapse
One more proof to prove that as long as you can see something on screen, it is not dead.
diablo009 said:
One more proof to prove that as long as you can see something on screen, it is not dead.
Click to expand...
Click to collapse
I had a similar problem but that same day i became a DL mode pro so i knew the combination by heart LOL.
I couldn't for the life of me do it now but thankfully it's good to know it's possible, glad you got yours working OP!
Plz Reply to get my infuse back
hello there,
i was trying to update my infuse 4g via odin, but something went wrong,, now my phone is showing only download mode, no samsung logo, no cwm recovery mode, not restarting. i m trying to get back the stock rom via GTG pack but process is getting stuck on following —
Added!!
Enter CS for MD5..
Check MD5.. Do not unplug the cable..
Please wait..
PDA_UCKD5.tar.md5 is valid.
PHONE_UCKD5.tar.md5 is valid.
Checking MD5 finished Sucessfully..
Leave CS..
Odin v.3 engine (ID:8)..
File analysis..
SetupConnection..
Initialzation..
Set PIT file..
DO NOT TURN OFF TARGET!!
Get PIT for mapping..
Firmware update start..
factoryfs.rfs
plz help me to get my infuse back coz i m in india now and samsung service center deny to help me.
bindas.sanju said:
hello there,
i was trying to update my infuse 4g via odin, but something went wrong,, now my phone is showing only download mode, no samsung logo, no cwm recovery mode, not restarting. i m trying to get back the stock rom via GTG pack but process is getting stuck on following —
Added!!
Enter CS for MD5..
Check MD5.. Do not unplug the cable..
Please wait..
PDA_UCKD5.tar.md5 is valid.
PHONE_UCKD5.tar.md5 is valid.
Checking MD5 finished Sucessfully..
Leave CS..
Odin v.3 engine (ID:8)..
File analysis..
SetupConnection..
Initialzation..
Set PIT file..
DO NOT TURN OFF TARGET!!
Get PIT for mapping..
Firmware update start..
factoryfs.rfs
plz help me to get my infuse back coz i m in india now and samsung service center deny to help me.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1524081
Ok you have download mode so that is good...I dont use odin much I prefer the one click method, check these links out...
post one will give you stock...post two will give you cwm to install a custom rom if you want to..
If you want to go stock with root...try these links.
http://forum.xda-developers.com/showthread.php?t=1629079
I just did post two works great...
read all op directions and give us a status or if you need more if, just holler..
hi sanju
Try this package of Qkster
http://forum.xda-developers.com/showthread.php?p=23118134
For me it always work when Odin fails.
best of luck.
ndhanta said:
hi sanju
Try this package of Qkster
http://forum.xda-developers.com/showthread.php?p=23118134
For me it always work when Odin fails.
best of luck.
Click to expand...
Click to collapse
Ha...we are on the same thought process...I never use odin...qkster one clickers for me.... "why u no 1 click?"
Tru Universal Brotherhood makes our thoughts same Joi
Had same problem
I had kinda same problem and it always failed at facory.rfs. i tried everything but then i discovered the weirdest fix ever. i switched usb cable and worked perfectly so you should try new usb cable. good luck
ndhanta said:
hi sanju
Try this package of Qkster
http://forum.xda-developers.com/showthread.php?p=23118134
For me it always work when Odin fails.
best of luck.
Click to expand...
Click to collapse
^ This. Let us know results please.
bindas.sanju said:
hello there,
i was trying to update my infuse 4g via odin, but something went wrong,, now my phone is showing only download mode, no samsung logo, no cwm recovery mode, not restarting. i m trying to get back the stock rom via GTG pack but process is getting stuck on following —
Added!!
Enter CS for MD5..
Check MD5.. Do not unplug the cable..
Please wait..
PDA_UCKD5.tar.md5 is valid.
PHONE_UCKD5.tar.md5 is valid.
Checking MD5 finished Sucessfully..
Leave CS..
Odin v.3 engine (ID:8)..
File analysis..
SetupConnection..
Initialzation..
Set PIT file..
DO NOT TURN OFF TARGET!!
Get PIT for mapping..
Firmware update start..
factoryfs.rfs
plz help me to get my infuse back coz i m in india now and samsung service center deny to help me.
Click to expand...
Click to collapse
I had the same thing happen to me last night when flashing the Entropy Kernel GB BL and all that jazz wtih odin. I unplugged cable after it froze up pulled battery attempted to return to dl mode but it went to the firmware update failed try kies recovery or whateves then I just tried odin again and it worked like a charm. I don't know what the deal was but froze up at factoryfs.rfs place and everything. So might just try that if this hasn't been resolved.
When its running rfs you should se a blue progress bar it takes about 5-8 mins to finish in my experience how long are you giving it
pink unicorn with swagga
This should work!
1. Download Blue CWM recovery on ur pc. http://www.mediafire.com/?2000k5y512spft4
2. Use odin and flash blue recovery (PDA)
3. May reboot into recovery or ull need todo 3 putton
4. Wipe/factory reset
5. Flash gingerbread rom on
6.go to advance>reboot recovery
7. Reflash that gingerbread rom on
8. Reboot!!
Hello,
I have been using this site for days now and accomplished everything I have needed to so far.
I rooted and flashed about 6 roms and found the Aeon v1.4 to be the best for me regarding my infuse 4g.
I tried to install the " Unofficial CM9 rom" for the ics look and it turned my phone into a paperweight.
Symptoms:
-Phone will not go into recovery
-will not turn on
-when attempting to turn it on, i get a barely noticable millisecond flash and then nothing.
The phone, however, will go into download mode.
I tried odin and did the repartition, pit, etc..
I tried heimdal (however its spelled) and it wont recognize drivers. (i installed drivers and they worked for odin)
I basically just want to put Aeon back on my phone and actually use my phone.. nothing else. I would appreciate any insight into the matter.
Thank you very much.
Chris.
I recently had the same problem when I tried to downgrade back to GB. I used Odin to reflash my phone using this.....http://forum.xda-developers.com/showthread.php?t=1613523.....
Thanks
omansteveo said:
I recently had the same problem when I tried to downgrade back to GB. I used Odin to reflash my phone using this.....http://forum.xda-developers.com/showthread.php?t=1613523.....
Click to expand...
Click to collapse
Thanks, ill definitely give it a whirl.. I have tried many different versions of Odin and different PIT, PDA files. Most of the time it just says:
<ID:0/012> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> NewStock.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<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> factoryfs.rfs
and sits there... stuck for like 20 min+ (currently)... no progress bar or anything. Currently, this one is PDA .tar only. No pit or anything else with only auto-reboot and f. reset time checked.
I'll definately let you know how it worked out though, thank you!
Try other usb ports & another usb cable if possible.
Sent from my SGH-I997 using xda app-developers app
use gtg ultimate unbrick
Azrael-09 said:
Thanks, ill definitely give it a whirl.. I have tried many different versions of Odin and different PIT, PDA files. Most of the time it just says:
<ID:0/012> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> NewStock.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<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> factoryfs.rfs
and sits there... stuck for like 20 min+ (currently)... no progress bar or anything. Currently, this one is PDA .tar only. No pit or anything else with only auto-reboot and f. reset time checked.
I'll definately let you know how it worked out though, thank you!
Click to expand...
Click to collapse
You need to go back to stock. Look for it in the software part. It is the ultimate gtg unbrick. It works flawless.
OP no need to double Post Threads of the same issue, your Thread in the General Section is no longer, utilize this thread for your issues. Thank You.
Is there an average time for Odin to pass?
andros11 said:
Try other usb ports & another usb cable if possible.
Sent from my SGH-I997 using xda app-developers app
Click to expand...
Click to collapse
I've been trying all 3 ports and decided to just stick to the on directly connected to the motherboard. Also have been using "USB Deview" to remove usb connections in order for phone to recognize the infuse drivers i unzipped and put on the desktop. Ill try another cord as well, thank you.
kenetix said:
You need to go back to stock. Look for it in the software part. It is the ultimate gtg unbrick. It works flawless.
Click to expand...
Click to collapse
I have tried that one i beleive, but my phone was originally Froyo and "GTG's ultimate unbrick" is for Gingerbread.. (GB PIT file) (it said my phone couldnt upgrade to GB when i was unrooted). I'll Try again though, couldnt hurt. Thanks.
You should go back to stock rom via Odin
When in doubt go stock
Sent from my GT-S5360 using xda app-developers app
Azrael-09 said:
I have tried that one i beleive, but my phone was originally Froyo and "GTG's ultimate unbrick" is for Gingerbread.. (GB PIT file) (it said my phone couldnt upgrade to GB when i was unrooted). I'll Try again though, couldnt hurt. Thanks.
Click to expand...
Click to collapse
Really no way to go back to Froyo. You have to now assume GB is the beginning...
Sent from my SGH-I997 using xda premium
Going stock
An1mus said:
You should go back to stock rom via Odin
When in doubt go stock
Sent from my GT-S5360 using xda app-developers app
Click to expand...
Click to collapse
I would absolutely love to flash it back stock, problem is I can find good files to drop me back to stock.. or maybe its the phone, idk. I even tried files used from the dump of someones stock phone to recreate a "stock" version. Next step is trying Gtg's Ultimate unbrick again.
I'll keep you guys updated, thanks for all your help.
I dont have enough posts to be able to put in outside links but if someone needs the GTG's_Ultimate_Unbrick.zip link, i found it. )Most of the links are broken and its a pain to find) Just PM me.
Odin update
20 min into it.
Odin shows this:
<ID:0/013> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> PDA_UCKD5.tar.md5 is valid.
<OSM> PHONE_UCKD5.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/013> Odin v.3 engine (ID:13)..
<ID:0/013> File analysis..
<ID:0/013> SetupConnection..
<ID:0/013> Initialzation..
<ID:0/013> Set PIT file..
<ID:0/013> DO NOT TURN OFF TARGET!!
<ID:0/013> Get PIT for mapping..
<ID:0/013> Firmware update start..
<ID:0/013> factoryfs.rfs
And phone is in DL mode with the blue progress bar showing about 1% since the beginning and hasnt moved. Odin isnt saying that its not responding or anything... any ideas?
If you want stock Froyo: http://forum.xda-developers.com/showthread.php?t=1629079
If you want stock GB : http://forum.xda-developers.com/showthread.php?t=1524081
Many thanks to qkster for this.
5 days and counting.. =(
Pony Express said:
If you want stock Froyo: http://forum.xda-developers.com/showthread.php?t=1629079
If you want stock GB : http://forum.xda-developers.com/showthread.php?t=1524081
Many thanks to qkster for this.
Click to expand...
Click to collapse
Thank you very much, I have tried those. This is my fifth day doing this and i cant seem to get Heimdall to work. I tried doing as much research as possible before posting a problem.
For Heimdall even though when it asks for drivers I can click on "Samsung usb composite device" and reflash but it just says "installing drivers" and loops over again.
For Odin its just not continuing to increase the progress bar or add anything new to the log screen.. Pretty confused at this point.
My phone is bricked from flashing the wrong rom. I dont mind which OS i go to because im going to end up flashing Aeon v1.4 again anyways since it looked and worked great.
Thanks for the links!
Update
[Well, i still cant get odin to get past the factoryfs.rfs ...
Phone is still only showing an 1/8 inch progress bar..
I keep trying Heimdall but no luck... i do not have file upload options in Heimdall though... is that normal?
If anyone has any other ideas, please share..
Here is a post I did for someone else, I hope it will be helpful to you.
http://forum.xda-developers.com/showpost.php?p=33215877&postcount=15
(The link I mention in post 13 is qkster's Heimdall link)
I'll get right on it. Thank you.
I think im missing some tar files... only thing in the video i can think of is that he mentions having odins tar files for some reason while using heimdall on-click.. I do have some files on my desktop > pit, phone and pda files but no other ones..
Also in the video it mentions the binary at the top of your screen in download mode. Mine says: Custom binary download: NO
Current binary: Samsung official
That normal for someone who flashed 6 roms?
On top of it all dev-host isnt downloading anything for me... click and click and nothing.
I think i just need some expert phone help, lol...
I just put mine in download and binary also says 'no'. I have lost count as to the number of roms I have flashed.
I think you are close but from my end I can't tell what is missing. I have used odin with no problem and yet my preference is Heimdall.
Maybe take some time and go through some of qkster's threads, including the link to his Heimdall tutorial. Some have found that they did not have the latest version of Java while others did not know that you have to use the same port you were using each time you use Heimdall. Others did not know that Heimdall has it's own drivers or that they should uninstall kies first.
Qkster may drop by this thread and if he has suggestions he will post. He has forgotten more about the Infuse than I know.
I installed then uninstalled Kies
I do have the latest version of Java.
I downloaded a binary version of Heimdall for the Zadig driver file so that i can manually put in the samsung driver before opening the one click Heimdall
I have followed tutorials to the letter so much that when i watched the video it seemed like I was knowledgeably far beyond the video's tutorial.
Im am however, unsure what you mean by using the same port (please keep in mind that im on the computer trying to fix my phone about 45 min out of every hour for about 8 hours a day for the past 5 days)... I actually had to erase all the zip files and tar files and such just to re-grasp where i was at because my desktop was overloaded...
Oh and i read a thread about bricking your phone (good read) and i think i screwed it up somewhere in the bootloaders... its not enough to hard brick it since i can still go into DL mode but something is definately wrong.
I do appreciate your advice and concern. Thank you again.
Hopefully we can come to a conclusion soon and i can pass on my knowledge...
Pony Express said:
Qkster may drop by this thread and if he has suggestions he will post. He has forgotten more about the Infuse than I know.
Click to expand...
Click to collapse
Thanks for the vote of confidence, Pony. I'm not very good at getting the drivers installed.
What you noted is all that I can recommend.
Update java. Install Samsung USB device. Install Zadig from Heimdall. Sometimes it take a reboot or two with the PC. Other times, it takes a different PC altogether. It may also work by moving the USB cord to a different usb port.
It has been almost a year since I tried Odin. No help there.
I can tell you that after you get the heimdall to work, save that cord and that usb port only for heimdall and don't install Odin over it.
With all the heimdall-1-click packages available, there are many options to restore from soft brick or return to stock.
jscott30 made a bunch of Odin packages as well if Heimdall is not working for that person.
Perseverance is the key. We have all been there. I can tell you that the more mistakes you make, the more you will learn.
Hi guys,
My galaxy note 10.1(2013) is was on <Stock> Android Kitkat .
Out of curiosity of rooting, i flashed CF Auto Root using odin.
The device restarted, and features seemed fine with new Root App too.
In few minutes however, device rebooted.. and went into a bootloop. :crying:
which still is, as long as device is on - has battery.
SUMMARY:
1. Recovery mode is not accessible now - device goes into recovery mode and restarts.
2. Normal boot is going into bootloop.
3. Download mode - HOWEVER is available !
PROBLEM :
-on trying to reflash stock rom/any Tar File for my device using odin,
odin fails with message :
NAND WRITE START
FAIL
----------------------------------------------------------------------------------------------------------------
Please help solve.
I do not want my beloved<soft bricked> device to die a sudden death .
Will appreciate you guys putting life back in it !
Oh, that's weird. Try updating your drivers and using Odin 3 1.85. Tell me if that helps.
chrismin13 said:
Oh, that's weird. Try updating your drivers and using Odin 3 1.85. Tell me if that helps.
Click to expand...
Click to collapse
Having the exact same problem.
Tryed:
Flashing a 4.0.4 stock rom trough odin: sucess flash but still bootloop
Flashing a 4.0.4 stock rom trough odin + pit file for 8010 4.0.4: sucess flash but still bootloop
Flashing CWM and TWRP trough ODIN with auto-reboot and without autoreboot checked: sucess flash but still bootloop and no access do recovery
Flashing 4.1.2 or 4.4.2 stock: same error as OP
Getting pretty desperate now
chrismin13 said:
Oh, that's weird. Try updating your drivers and using Odin 3 1.85. Tell me if that helps.
Click to expand...
Click to collapse
will get back with update tomorrow.
glorifiedg said:
Having the exact same problem.
Tryed:
Flashing a 4.0.4 stock rom trough odin: sucess flash but still bootloop
Flashing a 4.0.4 stock rom trough odin + pit file for 8010 4.0.4: sucess flash but still bootloop
Flashing CWM and TWRP trough ODIN with auto-reboot and without autoreboot checked: sucess flash but still bootloop and no access do recovery
Flashing 4.1.2 or 4.4.2 stock: same error as OP
Getting pretty desperate now
Click to expand...
Click to collapse
.. mine is not exactly the same.
you are able to write/flash onto NAND .. odin success for you.
My nand write itself fails.
End result is same, true there.
Anand.prashar said:
.. mine is not exactly the same.
you are able to write/flash onto NAND .. odin success for you.
My nand write itself fails.
End result is same, true there.
Click to expand...
Click to collapse
'Cause you probably didn't try the 4.0.4. I have nand write fail with the most recent versions also :S
Suggestion to no avail
chrismin13 said:
Oh, that's weird. Try updating your drivers and using Odin 3 1.85. Tell me if that helps.
Click to expand...
Click to collapse
<ID:0/006> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N8000XXUDNE6_N8000ODDDNE4_N8000DDUCNE2_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<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> system.img
<ID:0/006> NAND Write Start!!
<ID:0/006>
<ID:0/006> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Flashing OS failed.
What could be hindering or preventing NAND write ?
Anand.prashar said:
<ID:0/006> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N8000XXUDNE6_N8000ODDDNE4_N8000DDUCNE2_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<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> system.img
<ID:0/006> NAND Write Start!!
<ID:0/006>
<ID:0/006> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Flashing OS failed.
What could be hindering or preventing NAND write ?
Click to expand...
Click to collapse
You have the N8000. Correct? If you're working on a desktop try plugging the tablet in the back ports of your pc without using a USB hub or a usb 3.0 port. It sounds weird, I know, but that was the problem multiple times for me because the front ports of the computer use a usb hub that sometimes creates issues. And if you flash twrp what happens? I hope that it's not the chipset that's damaged. Also, what does download mode say? Does it write in binary status official? If yes, then flash stock frimware and recovery and try going it for warranty replacement. They won't understand what has happened I believe. And if all of this doesn't do anything try a different computer and a new usb cable. A computer with an OS older than Windows 8 would be great and without usb 3.0 ports. You can also try re-downloading all the files. Have you seen zedomax's video about unbricking our tablet? It covers everything I told you and much more so here's a link. http://rootgalaxynote.com/galaxy-note-10-1-2/how-to-unrootunbrick-galaxy-note-10-1-factory-firmware. Another idea is to use a toolbox for our device. Just tell me if anything of all of these methods works. I hope something does the trick!
---------- Post added at 11:22 AM ---------- Previous post was at 11:20 AM ----------
Wow. Have you realized how many people have issues with kitkat? So many people report broken devices and they all run kitkat. That's wierd.
[/COLOR]
chrismin13 said:
You have the N8000. Correct? If you're working on a desktop try plugging the tablet in the back ports of your pc without using a USB hub or a usb 3.0 port. It sounds weird, I know, but that was the problem multiple times for me because the front ports of the computer use a usb hub that sometimes creates issues. And if you flash twrp what happens? I hope that it's not the chipset that's damaged. Also, what does download mode say? Does it write in binary status official? If yes, then flash stock frimware and recovery and try going it for warranty replacement. They won't understand what has happened I believe. And if all of this doesn't do anything try a different computer and a new usb cable. A computer with an OS older than Windows 8 would be great and without usb 3.0 ports. You can also try re-downloading all the files. Have you seen zedomax's video about unbricking our tablet? It covers everything I told you and much more so here's a link. http://rootgalaxynote.com/galaxy-note-10-1-2/how-to-unrootunbrick-galaxy-note-10-1-factory-firmware. Another idea is to use a toolbox for our device. Just tell me if anything of all of these methods works. I hope something does the trick!
---------- Post added at 11:22 AM ---------- Previous post was at 11:20 AM ----------
Wow. Have you realized how many people have issues with kitkat? So many people report broken devices and they all run kitkat. That's wierd.[/QUOTE
same problem here but i thing we need to clear all those built up cache in order to proceed right? but no boot recovery just the Odin downloading image. now if we can find a way to clear all those cache i'm sure'll work but don't know how to clear it from the "downloading do not turn off target" unless somebody figure this out.
Click to expand...
Click to collapse
* Serious issue awaiting resolution *
chrismin13 said:
You have the N8000. Correct? If you're working on a desktop try plugging the tablet in the back ports of your pc without using a USB hub or a usb 3.0 port. It sounds weird, I know, but that was the problem multiple times for me because the front ports of the computer use a usb hub that sometimes creates issues. And if you flash twrp what happens? I hope that it's not the chipset that's damaged. Also, what does download mode say? Does it write in binary status official? If yes, then flash stock frimware and recovery and try going it for warranty replacement. They won't understand what has happened I believe. And if all of this doesn't do anything try a different computer and a new usb cable. A computer with an OS older than Windows 8 would be great and without usb 3.0 ports. You can also try re-downloading all the files. Have you seen zedomax's video about unbricking our tablet? It covers everything I told you and much more so here's a link. Another idea is to use a toolbox for our device. Just tell me if anything of all of these methods works. I hope something does the trick!
---------- Post added at 11:22 AM ---------- Previous post was at 11:20 AM ----------
Wow. Have you realized how many people have issues with kitkat? So many people report broken devices and they all run kitkat. That's wierd.
Click to expand...
Click to collapse
Sorry for delay, work kept busy.
You have the N8000. Correct?
-Yes
If you're working on a desktop ?
-No
- On laptop :
same laptop i used to root my tab using CF-Auto Root.
and have flashed ones in past on the older rom for this tab.
- Port : used USB 2.0
TWRP recovery ?
- Getting same error on odin as stock Rom.
<< I am attaching 3 snapshots >>
- Odin desktop Software in work
- Download mode of device
- Texts on download mode screen of device
<i believe it says custom, coz i had already 'seemingly' rooted stock rom>
------------------------------------------------------------------------------------------------------------
It would be worthwhile to mention the last flashing trial.
- it was upgraded to Kitkat released for this device
2 months ago : using Odin [as i had rooted the previous Default firmware too]
- having gotten bored with non-SU controls,
i flashed CF Auto Root
that would give me "SuperSU app" control without changing existing Firmware.
- Device rebooted after flashing (hopefully correct steps, i think)
"Super SU" app was available for me.
- Note : Upon opening app, i was prompted with a message
"KNOX has been detected on this device... would i like to remove/disable ?"
- I hit Yes.
Got a popup soon, that KNOX was successfully removed.
- and then, it went FINE for about an hour.
AND THEN CAME THE BOOTLOOP all of a sudden.
------------------------------------------------------------------------------------------------------------
Summary:
I am not able to figure out what could have caused this...
flashing/knox/ anything else ?
I have the same problem except that I can get too Recovery mode, but it's useless. It's been since April, so far no hope.
ayeladawy said:
I have the same problem except that I can get too Recovery mode, but it's useless. It's been since April, so far no hope.
Click to expand...
Click to collapse
Did you already tried to flash the 4.4 leaked version with the 5 files over odin?
And also the pit file provided there.
That solved my problem a couple of months ago.
ayeladawy said:
I have the same problem except that I can get too Recovery mode, but it's useless. It's been since April, so far no hope.
Click to expand...
Click to collapse
hey,
what do you mean by "useless" ?
please explain clearly.
i just got one of these the other day,gt-n8013, maybe it's possible to whip up a fix.
a thought i have is that a boned odin install may take on the same behaviour
as a certain kernel function where a temporary kernel to be booted to
may be being stored into ram, meaning when you reboot to odin mode
you basically pick up where you left off. poweroff your tab and then plug in
your charger like normal. if your battery image shows up then, your kernel is intact or mostly so.
if that's the case maybe running your battery dead or disconnecting it will
work like pulling the cmos battery in a pc to correct a bad bios configuration.
meaning after the power is finally and truly off then ram will clear completely and when
you recharge and reboot back to odin you will be at baseline again.
the above approach has worked with some lower end tabs i've owned
including the galaxy tab 2 7.0
m
Hey, I ran the battery dead on it and when plugged there no charging indictor but instead it power back on but blank black screen no boot logo or nothing what does that mean?
dough30i said:
Hey, I ran the battery dead on it and when plugged there no charging indictor but instead it power back on but blank black screen no boot logo or nothing what does that mean?
Click to expand...
Click to collapse
okay, try for odin now, but try recovery first.
@dough30i
going back through this thread if you did the same thing with cf-root-crap you may have
damaged you bootloader. which is very not good. if you've gotten recovery up let me know.
you will need to get adb running and just for verification i need your model i.d.
No recovery but I can get into Odin.see I done try all the step and every step no go. It something got to do with NAND FILE it won't write or something...
dough30i said:
No recovery but I can get into Odin.see I done try all the step and every step no go. It something got to do with NAND FILE it won't write or something...
Click to expand...
Click to collapse
okay, are you trying to write a full firmware image or just a recovery or boot tar.md5?
or is it flat out no go?
Full Firmware..oh i forget to mention at the beginning I had recovery boot logo, but then my stupid ass just had to mess with it more in the Odin to PC thing while I was trying to fixed it -_- my dumb ass got to anxious so I thought that when "NAND file not writing" I figure ohh maybe I needed to clear cache right so in the Odin I check repartition and I think that's why I have no samsung logo and recovery and now I back to somewhat square if u call it that. -__-
dough30i said:
Full Firmware..oh i forget to mention at the beginning I had recovery boot logo, but then my stupid ass just had to mess with it more in the Odin to PC thing while I was trying to fixed it -_- my dumb ass got to anxious so I thought that when "NAND file not writing" I figure ohh maybe I needed to clear cache right so in the Odin I check repartition and I think that's why I have no samsung logo and recovery and now I back to somewhat square if u call it that. -__-
Click to expand...
Click to collapse
okay,
first, we do not put ourselves down. technology is unnatural, we make mistakes.
second, we do not panic or act rashly.
that being said if you can still get into odin, all is not yet lost. while i am pulling the pit file from
my device you will need to look up the correct way to write it to your device using odin.
i will be back in about 10 - 15 minutes.
use the force.
m
@dough30i
okay,
this is the pit file pulled from my n8013 . what i've read it should do the trick.
however, let's be clear.
1 you are in a bad situation, with nothing to lose.
2 this may not work but, then again it might.
3 you are the the final say as to wether or not you will attempt this
4 you have secured the correct knowledge on applying the pit file and writing in odin.
if yes to all of the above, download the attached file and remove the .txt extension
m
this is the thread i pulled the information from
http://forum.xda-developers.com/showthread.php?t=2268735
Hey People
I posted this on S5 cf auto root tread but no one is helping me. has been 2 days
Im new here so if this is the wrong place to post delete or please point me in the right direction
I just tried rooting my SM G900I (LTE)?
Im brand new to android and thought it would be a good idea to root my phone right off the bat follow a guide off you tube using these softwares:
CF-Auto-Root-kltelgt-kltelgt-smg900l
Odin3_v3.09
Anyway it didnt work and ive just peed my pants (just a little) : have the feeling ive bricked a $500 new phone
this is what it says on the download screen with its stuck on (have tried a soft reset battery out for over a Minuit) ;
could not do normal boot
odin mode
Product name: SM G900I
Current Binary: custom
System Reset: official
Reactivation Lock (kk): off
knox warranty void: 0x1 (4)
qualcom secure boot: enable (CSB)
AP SWREV: S1 T1 R1 A1 P1
UDC Start
Ive always run it in administrator mode and have tried 2 different usb cables, one is brand new with the phone and a mates one . one of the guides I was following said to use a 2.0 cable not 3.0 im pretty sure mine are all 2.0
anyway heres some of the dialog from odin if it helps:
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> CF-Auto-Root-kltelgt-kltelgt-smg900l.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> cache.img.ext4
<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)
Odin seems to think everything is fine as it says Pass in green but the phone is still stuck in download mode with the same dialog .
By the way I've tried a lot more than 4 time with the same method I think it must be stuck on (4) though
Any help would be appreciated
Thanks
You can try a couple things. From a powered off state, hold volume up, power, home button. It should boot into the custom recovery, from there you want to wipe - cache, dalvik, and see if it boots. If not, Odin back to stock and start over. You'll need to find the correct file for your phone, probably on sammobile.com.
metalfan78 said:
You can try a couple things. From a powered off state, hold volume up, power, home button. It should boot into the custom recovery, from there you want to wipe - cache, dalvik, and see if it boots. If not, Odin back to stock and start over. You'll need to find the correct file for your phone, probably on sammobile.com.
Click to expand...
Click to collapse
Thanks bro
I tried the vol up, power and home but it goes straight to the download screen its stuck on , with the : could not do normal boot. etc
If I try odin back to stock firmware with the phone stuck like this is there any chance it would work?
Yes, it will work. Basically, you would be flashing the same thing Samsung does to restore a phone to factory status.
this why i don't do experiment to my phone before this phone all my phone was root because was cheap phones
metalfan78 said:
Yes, it will work. Basically, you would be flashing the same thing Samsung does to restore a phone to factory status.
Click to expand...
Click to collapse
thanks for that man
BennyDubz said:
thanks for that man
Click to expand...
Click to collapse
You're welcome
emanuelrv said:
this why i don't do experiment to my phone before this phone all my phone was root because was cheap phones
Click to expand...
Click to collapse
There is nothing wrong with rooting an expensive phone, as long as you are prepared and have the files you need to recover from something gone wrong.
emanuelrv said:
this why i don't do experiment to my phone before this phone all my phone was root because was cheap phones
Click to expand...
Click to collapse
metalfan78 said:
There is nothing wrong with rooting an expensive phone, as long as you are prepared and have the files you need to recover from something gone wrong.
Click to expand...
Click to collapse
Yeah defiantly naive of me especially after coming from using apple not really knowing the first thing about android. although there's no info on there that mattered too much.
my only reason for rooting is so I can get an app like guardian I think its called or something similar made by XDA so I can regulate the apps I use as its pretty stupid some of the permissions you have to give to even basic apps such anything from browser history, access to contacts and caller id etc. when there is really no need.
im not paranoid I just don't believe you should give private info so readily. but im back to square one anyway haha
So you got it running?
metalfan78 said:
So you got it running?
Click to expand...
Click to collapse
Yeah seems to be working fine, is weird as nothings been wiped even text messages still there
Should I have another go at rooting it hahaha
I would, worst case scenario is you'll have to reflash original tar in Odin again
Sent from my SM-G900P using Tapatalk
Are you sure you have Auto Reboot checked?
Also......check CP, not AP. In fact, I used Odin 3.10 instead of 3.09.
Good luck.
elwood said:
I would, worst case scenario is you'll have to reflash original tar in Odin again
Sent from my SM-G900P using Tapatalk
Click to expand...
Click to collapse
jpgranger said:
Are you sure you have Auto Reboot checked?
Also......check CP, not AP. In fact, I used Odin 3.10 instead of 3.09.
Good luck.
Click to expand...
Click to collapse
Choice, think ill give it another go
Whatsup guys, i'm new to xdadev, i'm loving how elaborate and informative all these threads are as well as the community.
Long story short, i got an S7 Tmobile here (i found it, it was blacklisted google locked and all sorts of ****ed)
So i replaced the screen and it looks brand new.
As far as google lock and the blacklisting, i went to a guy who basically did his magic and he wont tell me what he did exactly but i'll ASSUME, he did a flash ROM ?
When it boots it says Android Custom Rom or some****.
It was working fine despite it being kind of laggy.
left it on the table for a week, now that i want to turn it on, it's stuck on the T-Mobile Screen, and i hear a repetitive buzzing sound every minute or so. (is this a brick or a bootloop?)
Anyways, i go to the boot options menu (Power, volume down, and home), and I run Odin as admin, and followed through as instructed. (Yes, I've tried BOTH versions of Odin)
and i made sure I used the right custom firmware (its the T-Mobile Samsung Galaxy 7) (Not edge)
On my phone screen I get this:
ODIN MODE (HIGH SPEED)
Product name: SM-G930T
Current binary: Samsung Official
System Status: Custom
FRP Lock: OFF
Warranty Void: 0x0
QUALCOMM SECUREBOOT: ENABLE
RP SWREV: B4(2, 1, 1, 1, 1) K1 S3
SECURE DOWNLOAD: ENABLE
SW REV CHECK FAIL : [system]Fused 3 > Binary 2
(all of that is on my phone screen)
_________________________
Now for my Odin Screen:
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Odin engine v(ID:3.1203)..
<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> Firmware update start..
<ID:0/003> SingleDownload.
<ID:0/003> boot.img
<ID:0/003> FAIL! (Auth)
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
______________________________
Does anyone have any solutions?
I'm only attempting the unroot in hopes that i can simply get past the tmobile screen to get the phone running so I can sell it.
**UPDATE**
So i've been playing around with it. I tried 'kies' (Smart Switch.. i think? correct me if im wrong) and tried the emergency software recovery/ initialization but it asks for a Model Name and i guess i'm a really low scrub noob but i can't even get past that part.
It'd be cool if someone can pass me the model name (i swear i had it and i can't even find it now on google, maybe its because i'm running on no sleep and filled with frustration and rush, i gotta get this phone sold by tomorrow)
But yeah, so the Kies method is on pause.
So now I'm trying to do a hard reset through recovery mode (Power, Vol up, Home).
Here's what I have:
Android Recovery
MMB29M.G930TUVU3APG1 (lmfao i think i just figured out the model number here <(G930TUVU3APG1) >_<
samsung/heroqltetmo/heroqltetmo
6.0.1/MMB29M/G930TUVU3APG1
user/release-keys
Use Volume up/down and power.
[then the menu of what i can do]
and on the bottom:
Supported API:3
dm-verity verification failed...
So I try 'Wipe data/factory reset' and here's what I get:
-- Wiping data...
Formatting /data...
Formatting /cache...
-- Set Factory Reset done...
-- Copying media files...
-- preload checkin...
E: failed to mount /preload (No such file or directory)
Data wipe complete.
And basically when I reboot the system, it shows
Samsung Galaxy S7 Custom (Unlock icon),
Then the android loading (installing system update...)
and back to the recovery menu.
What could have caused this?
I was playing around with Odin earlier as well and i feel as though i mightve ****ed it up because i played with options like NAND Erase All and Re-Partition.
Could that be why?
or does it have to do with something called KNOX? I have no clue what KNOX is but based off what i read off other threads, there's a knox count or something to whether it's 0 or 1 or some****
and FRP unlock/bypass may have something to do with it?
Again, keep in mind that i let someone else do something to this phone (no clue what that person did in practice, but ill assume a custom flash rom and frp unlock to bypass google cloud lock and also clean imei from blacklisting)
All this stuff is beyond my knowledge so i'm sorry if i sound extra ignorant but im trying haha.
Anyways, enough of my ranting.
Help me get this phone up and running ASAP and you'll be rewarded a small incentive. ($10-$15 Paypal)
Thank you!
When you do the whole emergency recovery thing, you should see your serial number on the back of your phone. punch that in, and wait for the download, it's going to download the firmware for your exact model/country branding blah blah blah.
See if that helps.
If not, try flashing a TWRP and putting a custom rom at least so you can boot.
So you stole a phone (Theft by finding here in good old UK - Theft), got someone to illegally change the IMEI and remove the FRP lock, now it doesn't work and you want help to get your stolen phone working again? ... Hmm let me see...
.................
....
...
..
.
.
.
.
tampitzel said:
When you do the whole emergency recovery thing, you should see your serial number on the back of your phone. punch that in, and wait for the download, it's going to download the firmware for your exact model/country branding blah blah blah.
See if that helps.
If not, try flashing a TWRP and putting a custom rom at least so you can boot.
Click to expand...
Click to collapse
thanks man, ill give it a try and let you know
biffwitch said:
So you stole a phone (Theft by finding here in good old UK - Theft), got someone to illegally change the IMEI and remove the FRP lock, now it doesn't work and you want help to get your stolen phone working again? ... Hmm let me see...
.................
....
...
..
.
.
.
.
Click to expand...
Click to collapse
oh look its an online smartass who thinks he knows it all!
Eiji.exe said:
oh look its an online smartass who thinks he knows it all!
Click to expand...
Click to collapse
ohh look.. a closed thread.....
With this attitude your stay on XDA will not last long iam afraid.
Please return the phone to your local Lost and Found department.
biffwitch said:
So you stole a phone (Theft by finding here in good old UK - Theft), got someone to illegally change the IMEI and remove the FRP lock, now it doesn't work and you want help to get your stolen phone working again? ... Hmm let me see...
Click to expand...
Click to collapse
Eiji.exe said:
oh look its an online smartass who thinks he knows it all!
Click to expand...
Click to collapse
Whiskey103 said:
ohh look.. a closed thread.....
With this attitude your stay on XDA will not last long iam afraid.
Please return the phone to your local Lost and Found department.
Click to expand...
Click to collapse
Finding a phone does not constitute as theft, so let's clear that up.
Finding a phone and deciding to keep it without returning it to the carrier in an attempt to have it restored to it's rightful owner who actually paid for the device, is theft.
@Eiji.exe, as has been instructed to you, please return the lost and found equipment. I'm sure you would want the same done for you.
This thread was closed not due to bullying or for imposed authority, but because we do not allow discussion of bypassing securities on stolen equipment.
Have a good day.