Hello,
I had a working setup with CM9 nightly 20120618, Siyah kernel 3.3.2 and LPX modem.
Due to phone call cuts, which seemed to be a known problem with the LPX modem, I tried to install LPS modem with RomManager premium.
I didn't watch my phone during the whole process, so I don't know if LPS install went successful. I guess it doesn't : I usually had to manually disable signature verification in CWM to be able to flash zip files.
I found my phone with a lighty flashing screen, as if backlighting was switching on and off on a black screen. I pulled off the battery, removed SD and SIM, and tried normal boot, boot to recovery and boot to download using the buttons combo : nothing works, I get the "GALAXY SII GT-I9100" screen and then the flashing black screen. If i press the home button while the screen is flashing black, it starts flashing white, and that's all.
I don't know what I can do now. Any help would be greatly appreciated...
Thank you
OK. Firstly, CWM & Rom Manager on the same phone is asking for trouble. Rom Manager does not play nice with CWM; has been known to cause bootloops, break recovery & cause 'soft bricks'. So if you're going to use Siyah (or any other kernel with CWM) with CM9, either freeze or uninstall Rom Manager.
Your OP is a bit vague, are you saying you have bootloop ? If you are, I'd do a factory reset in the first instance. If that doesn't work, I'd flash CM9 Resurrection in Odin, then flash latest CM9 nightly (read/follow the instructions in the CM9 discussion thread). From there, you can then flash Siyah if you want. And if you do use CM9 & Siyah again, don't forget to freeze/uninstall Rom Manager.
If you don't want to use CM9 anymore & the reset doesn't work, flash a stock rom (GB or ICS; up to you) in Odin, and go from there. That will give you a clean slate.
Now, if you don't have a bootloop & something else is happening to your phone, clarify exactly what your phone is/isn't doing & can/can't do (does it boot, do you have recovery, do you have download mode), and we can look at it further.
Many thanks for the fast help.
Searching XDA for solutions I had understood that CWM and RomManager doesn't get on very well. I won't make the same mistake again, I promise !
But now my problem is to get back in control of my phone.
To clarify the situation, I don't know what to do because :
* If I try a regular power on, I can see the "GT-I9100", and then a flashing black screen. It seems to flash for ever, but when I press the home button several times it flashes white/black, seems for ever too.
* If I power on pressing volume up, same thing
* If I power on pressing volume down, same thing
So that's not really a bootloop I think since I only see the "GT I9100" screen once.
I discovered a new thing : if I plug the power cable, I have the battery icon on the screen for a few seconds as usual, and then again the flashing screen.
So I wold be VERY happy if I could flash any rom, stock, CM9 of whatever, but as I am unable to go to download mode nor to recovery I don't know how to flash :crying:
Problem solved.
I'll look very noobish on this : I had forgotten to press the home button, that's why I couldn't go to download mode. Flashed CM9 resurrection with odin, then LPS modem, 20120622 nightly, and siyah 3.3.2 with recovery.
Then I freezed RomManager with titanium backup to avoid making the same mistake again.
My phone is back !
Good job sorting it out yourself like that. Glad you got it sorted ;-)
Hi,
Unfortunately i am one of the few who made the same mistake of having both CWM and Rom Manager. Same issues were experienced.
Now, i tried following the steps provided.
1. Downloaded RR cm9
2. Flash via odin
now the problem is i am stuck @
<ID:0/003> Added!!
<ID:0/003> Removed!!
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> cm-9-20120420-ODIN-galaxys2.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> zImage
<ID:0/003> NAND Write Start!!
<ID:0/003> Sbl.bin
Now i don't know what to do. it's been sitting here for around 20-30mins now w/ no signs of progress. Please help.
Well, just disregard. Took a risk by powering the device down and redoing the flash process. Changed the port and used a mobo port and it all worked.
Sent from my GT-I9100 using xda app-developers app
Related
I have flashed multiple roms to my phone and never had an issue...
I just flashed [ROM] Vibrant AOSP ish JK2 1.1 Official FROYO (Working GPS, WiFi Calling) *11/9/2010* to my phone.. Everything seemed fine. I wanted to test the new bionix, so I rebooted my phone to go into recovery and Im stuck at the Vibrant/Samsung Boot screen.. Great..
I hold down volume down and power and my PC Sees a ADB Samsung device.. Nice..
I downloaded Odin, it sees my phone.. I downloaed the ugene_2E_JK2_Froyo.zip
I put the Pit File, then load the PDA file and hit start and it gets stuck right here every time...
<ID:0/004> Added!!
<ID:0/004> Odin v.3 engine (ID:4)..
<ID:0/004> File analysis..
<ID:0/004> Enter CS for MD5..
<ID:0/004> Leave CS..
Thats as far as it goes... Am I doing something wrong or do u have any other ideas? I just need to get this phone up and running soon...
Thanks,
Andrew
xandrevvx said:
I have flashed multiple roms to my phone and never had an issue...
I just flashed [ROM] Vibrant AOSP ish JK2 1.1 Official FROYO (Working GPS, WiFi Calling) *11/9/2010* to my phone.. Everything seemed fine. I wanted to test the new bionix, so I rebooted my phone to go into recovery and Im stuck at the Vibrant/Samsung Boot screen.. Great..
I hold down volume down and power and my PC Sees a ADB Samsung device.. Nice..
I downloaded Odin, it sees my phone.. I downloaed the ugene_2E_JK2_Froyo.zip
I put the Pit File, then load the PDA file and hit start and it gets stuck right here every time...
<ID:0/004> Added!!
<ID:0/004> Odin v.3 engine (ID:4)..
<ID:0/004> File analysis..
<ID:0/004> Enter CS for MD5..
<ID:0/004> Leave CS..
Thats as far as it goes... Am I doing something wrong or do u have any other ideas? I just need to get this phone up and running soon...
Thanks,
Andrew
Click to expand...
Click to collapse
If you post your Q in the proper forum you're more likely to get an A (HINT).
I personally hate to start helping we these in the Development forum because then it's constantly bumped.
Just sayin'.
I think I got it.. Held down the vol up and down and power, then released power.. Phone wnet into the yellow downloading icon screen (new to me) had to do it a few times, Odin saw it.. Now its pushing files.. Wish me luck,...
First, I hope you fix your phone, this is not developement related and it didn't need yet another Odin help thread. My guess, you put a Vibrant ROM on a Captivate that hasn't been modded for a Captivate. Why are you trying to use Vibrant stuff on a Captivate? Odin didn't brick your phone, you did flashing stuff that isn't made for a Captivate.
Open Odin one click back to stock JF6, run as administrator, plug your phone into a rear usb port, put your phone in download mode and when Odin sees your phone click start. If you are in Recovery Mode than open a command shell and use ADB, type adb reboot downloaad. If Odin dosen't see your phone and it won't power on or you can't access the Recovery Screen then you may have to make a JIG to trick your phone into download mode.
Im on a Vibrant.. Not a captivate... Sorry for posting to the wrong forums.. Wont happen again... I fixed my phone...
Lol not even a captivate?
Sent from my SAMSUNG-SGH-I897 using Cognition 2.4.1
I have my S III for two and a half months. And today it started to boot loop. The phone was working and I leave it on the table. After few minutes I noticed that the phone is in boot loop.
This is my second android phone. Before the S III I had Desire. I have experience in rooting with the Desire (use it without root only 2 months and own it for 2 years). Also while flashing it many times I had boot loops on it -> re-flash always worked.
The S3's situation - it is in boot loop, when I try to start the stock recovery (volup+home+pwr and not releasing the) the phone starts to boot loop as long as I keep the buttons pushed. When I release them the phone stays in booting screen (Samsung logo) - same as I just try to start it. When I put it in download mode (voldown+home+pwr) it works and asks me if I want to continue.
Is there anybody with experience whit the same problem? And should I try to flash the stock rom from SGS3 ToolKit or to use the warranty and let the shop to fix it (probably will hold my phone for a month)?
shiSHARK said:
I have my S III for two and a half months. And today it started to boot loop. The phone was working and I leave it on the table. After few minutes I noticed that the phone is in boot loop.
The S3's situation - it is in boot loop, when I try to start the stock recovery (volup+home+pwr and not releasing the) the phone starts to boot loop as long as I keep the buttons pushed. When I release them the phone stays in booting screen (Samsung logo) - same as I just try to start it. When I put it in download mode (voldown+home+pwr) it works and asks me if I want to continue.
Is there anybody with experience whit the same problem? And should I try to flash the stock rom from SGS3 ToolKit or to use the warranty and let the shop to fix it (probably will hold my phone for a month)?
Click to expand...
Click to collapse
One boot to recovery Vol Up + Home + Power release immediately on splash screen .
No recovery then choice is return to service .
Or flash a stock rom via Odin from the stock rom threads .
jje
release the power vol up and power buttons as soon as you see android while entering recovery. Once you do that try factory reset.
Note: You will lose all your data on internal SD (pics, images etc)
If you want to save data first flash CWM then enter recovery and factory reset. You will be able to save pics, images, music etc by doing so (apps will still be removed)
JJEgan said:
One boot to recovery Vol Up + Home + Power release immediately on splash screen .
No recovery then choice is return to service .
Or flash a stock rom via Odin from the stock rom threads .
jje
Click to expand...
Click to collapse
Vol Up + Home + Power * *release immediately *on splash screen (Samsung logo) -
Stays on spash screen until I pull out the battery. No android logo is displayed.
If I try to flash stock rom via odin is it possible the service to deny my warranty?
shiSHARK said:
Vol Up + Home + Power * *release immediately *on splash screen (Samsung logo) -
Stays on spash screen until I pull out the battery. No android logo is displayed.
If I try to flash stock rom via odin is it possible the service to deny my warranty?
Click to expand...
Click to collapse
Okay follow the steps as mentioned:
Step 1: Download the stock firm ware for your region via sammobile.com/checkfus
Step 2: Open Odin 3.04
Step 3: Put your phone in Download mode
Step 4: Connect to PC
Step 5: Select the firmware (unzip it to get the .tar file if it is a .zip file) as pda..dont touch anything else
Step 6: Click Start and wait till the rom is flashed and your device reboots
Step 7: If the phone is stuck at boot screen after the flash, press vol up+menu+power untill you see a green droid..release immediately
Step 8: Clear Data+cache..you will loose everything on your internal sdcard
Step 9: Reboot
Now if you face any problem in any of the steps mentioned above..tell us which step and what is the error you get...
flashing stock will not void your warranty but the stock rom should be specific to your region..with correct CSC..
zoot1 said:
Okay follow the steps as mentioned:
Step 1: Download the stock firm ware for your region via sammobile.com/checkfus
Step 2: Open Odin 3.04
Step 3: Put your phone in Download mode
Step 4: Connect to PC
Step 5: Select the firmware (unzip it to get the .tar file if it is a .zip file) as pda..dont touch anything else
Step 6: Click Start and wait till the rom is flashed and your device reboots
Step 7: If the phone is stuck at boot screen after the flash, press vol up+menu+power untill you see a green droid..release immediately
Step 8: Clear Data+cache..you will loose everything on your internal sdcard
Step 9: Reboot
Now if you face any problem in any of the steps mentioned above..tell us which step and what is the error you get...
flashing stock will not void your warranty but the stock rom should be specific to your region..with correct CSC..
Click to expand...
Click to collapse
There is the log from odin:
<ID:0/006> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9300XXALF2_I9300GBLALF1_I9300XXLF2_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>
<ID:0/006> There is no PIT partition.
<ID:0/006> Added!!
<OSM> All threads completed. (succeed 0 / failed 1)
There are few pit files in the zip with the odin but I don't know which one to use:
GT-I9300_mx_20120220.pit
GT-I9300_mx_20120322.pit
GT-I9300_mx_20120329.pit
M0_20120220.pit
mx.pit
Also tried with latest pit this is the log file:
<ID:0/006> Removed!!
<ID:0/006> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9300XXALF2_I9300GBLALF1_I9300XXLF2_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> Set PIT file..
<ID:0/006> DO NOT TURN OFF TARGET!!
<ID:0/006>
<ID:0/006> Re-Partition operation failed.
<ID:0/006> Added!!
<OSM> All threads completed. (succeed 0 / failed 1)
Flash via 3 file method..search for the method in the threads..
It does not look good..flashing the pit file is dangerous
Sent from my GT-I9300 using xda app-developers app
De tick the Re-Partition checkbox and try? But your definately going to have to re flash using Odin
Guys thanks for your help. After few unsuccessful attempts to flash with odin, I returned the phone to customer service, and now I'll wait them to fix it. Now I'm with my old Desire until they fix my SGS 3.
shiSHARK said:
Guys thanks for your help. After few unsuccessful attempts to flash with odin, I returned the phone to customer service, and now I'll wait them to fix it. Now I'm with my old Desire until they fix my SGS 3.
Click to expand...
Click to collapse
Hi shiShark,
Any luck when you returned to customer service? I seem to have exactly the same problem.
Out of interest, did your phone show as system Custom in the recovery screen? - Similar to you, I have not rooted or flashed my phone but it says sytem:Custom on the recovery screen and customer service refuse to fix it under warranty.
Thanks.
Will
HI All
I'm wondering if you guys have seen similar problem. I have currently rooted stock ROM on my Mega but want to install CWM so I can take a backup of the system and try out CyanogenMOD11.
Yet, when I try flashing CWM with Odin it looks like this:
<ID:0/012> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> recovery.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> recovery.img
<ID:0/012> NAND Write Start!!
<ID:0/012> RQT_CLOSE !!
<ID:0/012> RES OK !!
<ID:0/012> Removed!!
<ID:0/012> Remain Port .... 0
<OSM> All threads completed. (succeed 1 / failed 0)
At this point phone reboots and when I go to recovery - there is no CWM
I will be grateful for any suggestions.
Thanks
I would suggest you try this http://goo.im/devs/philz_touch/CWM_Advanced_Edition/meliusltexx/philz_touch_6.25.0-meliusltexx.tar.md5 assuming you have the GT-I9205 of course.
Kangburra said:
I would suggest you try this _link_ assuming you have the GT-I9205 of course.
Click to expand...
Click to collapse
I will try that, thanks for suggestion :good:
So I tried the above but have same thing happening.
Everything looks as if it's working OK. Odin picks up the phone, I load the image in PDA.
Have Auto Reboot and F.Reset Time enabled (only).
I hit the start button and it's VERY fast - literally few seconds and I get blue RESET! in the top box in Odin.
What's interesting is that after another two minutes Odin will change to PASS!
But that's looong after my phone booted back to normal operation mode, it will also change to PASS even if I have disconnected my phone
Any suggestions anyone?
==== UPDATE ===
What I also noticed is that after I boot to recovery I'm getting ERROR and NO COMMAND - they will flash on the screen and instead of usual Android Robot I have one on it's side with red exclamation mark over it.
No Command and this point is displayed below the "robot".
This is really irritating
One thing when you are flashing a custom recovery on the mega is once you are done flashing with odin you MUST reboot the phone directly into the recovery mode again for like CWM to appear otherwise if you do not do this the stock recovery will be back, this only has to be done once when you first flash a custom recovery..then it will be okay after that.
And with odin that does the same thing for me it says RESET but it still works and after it will say PASS when the phone is disconnected already, not sure why odin does this but seems to have no effect on the flashing part...hope this helps you out.
starmaster10 said:
One thing when you are flashing a custom recovery on the mega is once you are done flashing with odin you MUST reboot the phone directly into the recovery mode again for like CWM to appear otherwise if you do not do this the stock recovery will be back, this only has to be done once when you first flash a custom recovery..then it will be okay after that.
And with odin that does the same thing for me it says RESET but it still works and after it will say PASS when the phone is disconnected already, not sure why odin does this but seems to have no effect on the flashing part...hope this helps you out.
Click to expand...
Click to collapse
That was is!
Thanks for pointing in the right direction.
I've all the same options in Odin but when it auto-rebooted my phone I have quickly pressed the the buttons for going to recovery and that worked. When powering off from recovery I was given an option to disable stock recovery and now it's all as intended.
THANKS!
Ch3rub said:
That was is!
Thanks for pointing in the right direction.
I've all the same options in Odin but when it auto-rebooted my phone I have quickly pressed the the buttons for going to recovery and that worked. When powering off from recovery I was given an option to disable stock recovery and now it's all as intended.
THANKS!
Click to expand...
Click to collapse
You are welcome.
Ch3rub said:
So I tried the above but have same thing happening.
Everything looks as if it's working OK. Odin picks up the phone, I load the image in PDA.
Have Auto Reboot and F.Reset Time enabled (only).
I hit the start button and it's VERY fast - literally few seconds and I get blue RESET! in the top box in Odin.
What's interesting is that after another two minutes Odin will change to PASS!
But that's looong after my phone booted back to normal operation mode, it will also change to PASS even if I have disconnected my phone
Any suggestions anyone?
==== UPDATE ===
What I also noticed is that after I boot to recovery I'm getting ERROR and NO COMMAND - they will flash on the screen and instead of usual Android Robot I have one on it's side with red exclamation mark over it.
No Command and this point is displayed below the "robot".
This is really irritating
Click to expand...
Click to collapse
I got same problem when i flashed cwm by phil with odin, what i did is to uncheck autoreboot in odin so after odin finish flash recovery image you need to turn off manually by long pressing power button, and then just boot into recovery, reboot system now and select yes disable stock recovery when prompted by cwm.
Sent from my GT-I9205 using XDA Free mobile app
This does not work for me?
SPH-L600 (Sprint) Galaxy mega
Android: 4.2.2
Baseband: L600vpubne4
Build: KOT49H.L600VPUBNE4
I tried to use KingoRoot and apparently it's "bricked" my tablet. I've done lots of reading and I'm stuck, and need help please.
1. I have latest Odin, 3.10.7 from odindownload
2. My tablet is a SM-T560NU, and came with 5.1.1
3. I found a recent image for my exact unit model, and have downloaded it: BNN-T560NUUEU1AOH6-20151215094559
The instructions I have seen everywhere say to launch Odin3, wait for the tablet to connect (it does), load the image into "AP" (I do), and turn ONLY on options "auto reboot" and "F. Reset Time" (which means keep re-partition off, which they stress). When I click start, it goes about 5 minutes, then says this:
<OSM> Enter CS for MD5..
<OSM> Binary Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/004> Odin engine v(ID:3.1100)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/004> Removed!!
<ID:0/004> Added!!
<ID:0/004> Removed!!
Help, any ideas? I've tried 2 images.. the one I said above, and another for a SM-T560 (non-NU), and both give the exact same above fail in Odin3.
figure anything out? in th eprocess of downloading and fixing my sm-t560nu tablet also.
make sure you have the correct firmware rom, there's sm-t560 and there's sm-t560nu
same problem, rooted it last night with kingroot, worked fine until i turned it off and tried to turn it back on
did it take forever to download your firmware? if not can i ask where you got it from cuz mine is taking 7 hours to download
well i got mine all up and running, if you're in canada you might have the wrong rom file because the one i needed for my samsung galasy tab E "sm-t560nu" the file name started with xac and not bnn, i had to get mine from
samsung-firmware . org
and pay i think it was 5.99 usd, did exactly what it said at the bottom of the page for the instruction in odin and everything worked great but make sure to use the same email account u used originally when your setting up that tablet on its first boot up
was a lil confused since the instructions said to click on ap/pda and there's only ap in odin3 but ap/pda is renamed to just ap in the new odin.
good luck
Loading a new ROM in Odin, although I 100% had correct one, did NOT help. I could try 1000 times, and it wouldn't budge. The trick was a post I found on another site that talked about a recovery mode.... a hard reset.
What I actually had to do was the following:
1. Go into RECOVERY MODE, and do a reset. (Doesn't unbrick, but allows Odin to work)
2. Go into DOWNLOAD mode, and then use Odin to load image.
Here are the steps for both:
Recovery Mode Samsung Galaxy J1 SM-J120F
Turn off the device
Press and hold Volume UP key + Home Key, while pressing these keys then press and hold Power key for a while
Release all key when Android or Samsung logo appear then you will see Android System Recovery
Use Volume keys to select Menu
Use Power key to Confirm
Download Mode or ODIN Mode
Turn off the device
Press and hold Volume Down key + Home Key, while pressing these keys then press and hold Power key for a while
Release all key when you see ODIN Mode / Download Mode
Use Volume Up key to continue
Use Volume Down key to cancel ( Restart the device )
As for firmware, I got mine from (I can't post url's here yet, forum rules) a place called : You Mobile dot Org. ... for free.
Now if we can find a way to actually ROOT it, I'd be thrilled.
Any help on this? i just got this message and waster an hour downloading the firmware, and still stuck with odin.
i dont see anything saying menu in Recovery Mode
This is my Odin message
<ID:0/004> Added!!
<ID:0/004> Odin v.3 engine (ID:4)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> SingleDownload.
<ID:0/004> PK-
<ID:0/004> NAND Write Start!!
<ID:0/004> FAIL!
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
I've rooted my tablet with kingroot and rebooted several times. My tablet still works fine. My tablet is a sm-t560nu
Use Odin 3.07
This method works best with Odin 3.07 using BNN rom.
hello same thing happened to me and when i try to boot my device it says custom binary locked by frp.is that what happened to you? if so please tell me exact steps.
Rovexx said:
hello same thing happened to me and when i try to boot my device it says custom binary locked by frp.is that what happened to you? if so please tell me exact steps.
Click to expand...
Click to collapse
Read what I wrote above... I tell you how to unbrick it.
First go into recovery mode on tab, then get odin and download image, then use odin to load image into tab using odin and tab in download mode.
I can't find this firmware anywhere. My 8yr old used kingroot n killed tab. Someone please help.. Sm-t560nu wife is Bout to kill him if I can't fix with odin.
DesertEagleSlim said:
I can't find this firmware anywhere. My 8yr old used kingroot n killed tab. Someone please help.. Sm-t560nu wife is Bout to kill him if I can't fix with odin.
Click to expand...
Click to collapse
ya i'm still ****ed up too. still haven't found a solution. sorry. wish i could help
kingroot and OEM unlock
use samsung smart switch to fix your SM-T560NU tablet if you used kingroot. I couldn't boot because it said ... "custom binary blocked by FRP" used smart switch it restored the tablet to factory settings. the solution is to unlock developer options and select "OEM unlock" then use king root. king root should warn the user about this issue. Good luck!
ThePopcanKid said:
ya i'm still ****ed up too. still haven't found a solution. sorry. wish i could help
Click to expand...
Click to collapse
Found a copy of firmware on sammobile just register and download. It's super slow if u don't pay but it will finish. Fixed tablet n wife didn't kill me. No more kingroot for that tab. Although kingroot did work for the tab4 that I found in a bush (obviously stolen and ditched cause they couldn't bypass the screen lock)
I have full root, sticks after multiple reboots. I used kingroot, forced it to root, then after de-bloating, unrooted. It has been hanging out in that state for a week while I worked up the nerve to try turning off OEM under development options and telling it to root again, which I did this morning. Is running like a champ now.
Next problem is there is no custom recovery, so I am working to get xposed installed by zip somehow and be able to backup.
Sent from my SM-T560NU using XDA Free mobile app
pushabutton said:
I have full root, sticks after multiple reboots. I used kingroot, forced it to root, then after de-bloating, unrooted. It has been hanging out in that state for a week while I worked up the nerve to try turning off OEM under development options and telling it to root again, which I did this morning. Is running like a champ now.
Next problem is there is no custom recovery, so I am working to get xposed installed by zip somehow and be able to backup.
Sent from my SM-T560NU using XDA Free mobile app
Click to expand...
Click to collapse
You can use Flashfire to install Xposed if you convert to supersu first.
I have been working on TWRP with a tester (I don't own this device) however it doesn't boot yet, I have a feeling I need a permissive kernel, but Samsung have not released the source code yet.
DEVICE TREE:https://github.com/ashyx/TWRP_Samsung_gtelwifi?files=1
I could not get supersu to install no matter what I do so am stuck for now. Has anyone had any experience using flash Gordon to install zips, or know how to get supersu to install?
pushabutton said:
I could not get supersu to install no matter what I do so am stuck for now. Has anyone had any experience using flash Gordon to install zips, or know how to get supersu to install?
Click to expand...
Click to collapse
See post #65 onwards.
http://forum.xda-developers.com/showthread.php?t=3262864
cablematicman said:
use samsung smart switch to fix your SM-T560NU tablet if you used kingroot. I couldn't boot because it said ... "custom binary blocked by FRP" used smart switch it restored the tablet to factory settings. the solution is to unlock developer options and select "OEM unlock" then use king root. king root should warn the user about this issue. Good luck!
Click to expand...
Click to collapse
How did you use smart switch when tablet won't boot. I tried hooking up to computer and it has it doesn't recognize tablet.
thinv said:
How did you use smart switch when tablet won't boot. I tried hooking up to computer and it has it doesn't recognize tablet.
Click to expand...
Click to collapse
Boot into download mode POWER + VOL DOWN +HOME
Please help, my S3 suddenly stuck at Samsung Galaxy S3 GT-1900 screen. Tried to press Home & Vol Down buttons together but no response.
Plug it in, hold just the power button for 10-15 seconds. If no response it's dead. If you get the samsung logo you should be able to get download mode so long as your volume keys work.
Beamed in by telepathy.
shivadow said:
Plug it in, hold just the power button for 10-15 seconds. If no response it's dead. If you get the samsung logo you should be able to get download mode so long as your volume keys work.
Beamed in by telepathy.
Click to expand...
Click to collapse
Hi Shivadow,
I have entered the the ODIN MODE.. then I'm stuck again at "Downloading... Do not turn off target!!!".
What will I do next. Thanks.
Dhongski said:
Hi Shivadow,
I have entered the the ODIN MODE.. then I'm stuck again at "Downloading... Do not turn off target!!!".
What will I do next. Thanks.
Click to expand...
Click to collapse
I tried downloading S3 firmware & Odin3.. but I always get Failed status. Please see below.
<ID:0/005> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9300XXUGNK1_I9300SVZGNJ1_I9300XXUGNA8_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/005> Odin v.3 engine (ID:5)..
<ID:0/005> File analysis..
<ID:0/005> SetupConnection..
<ID:0/005> Initialzation..
<ID:0/005> Get PIT for mapping..
<ID:0/005> Firmware update start..
<ID:0/005> SingleDownload.
<ID:0/005> sboot.bin
<ID:0/005> NAND Write Start!!
<ID:0/005> FAIL!
<ID:0/005>
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Any help please. thanks.
Corrupt or locked bootloader or firmware mismatch (device or carrier). Are you sure you have an I9300?. Check the sticker inside the battery compartment. Make sure it has I9300 on it.
If it is definitely an I9300 then I'd go with corrupt or locked bootloader. Is the device locked to a carrier?. Are you sure that the firmware is the correct one for your carrier?.
Beamed in by telepathy.
shivadow said:
Corrupt or locked bootloader or firmware mismatch (device or carrier). Are you sure you have an I9300?. Check the sticker inside the battery compartment. Make sure it has I9300 on it.
If it is definitely an I9300 then I'd go with corrupt or locked bootloader. Is the device locked to a carrier?. Are you sure that the firmware is the correct one for your carrier?.
Beamed in by telepathy.
Click to expand...
Click to collapse
Awww, I'm sorry, my device is I9305. I tried downloading firmwares for my device and got a PASS status at Odin, but still stuck at Samsung S3 screen after auto reboot. My device also is not locked to a carrier.
Any other options please. Thanks again.
You need to flash the i9305 firmware. I9300 and I9305 are two totally different phones with totally different firmware. What or who on earth made you believe that I9300 firmware would work on an I9305..
That's the equivalent of a man dressing in womans clothing and saying "I didn't realise I don't have a vagina"..
Beamed in by telepathy.
shivadow said:
You need to flash the i9305 firmware. I9300 and I9305 are two totally different phones with totally different firmware. What or who on earth made you believe that I9300 firmware would work on an I9305..
That's the equivalent of a man dressing in womans clothing and saying "I didn't realise I don't have a vagina"..
Beamed in by telepathy.
Click to expand...
Click to collapse
I've already downloaded 2 firmwares for I9305 and used Odin, and I got a Fail status on the first one while the other one I got a Pass but still not working. Do I need to download more firmwares? Do I need to choose what country I have to download even if my device is not locked to a carrier?
shivadow said:
You need to flash the i9305 firmware. I9300 and I9305 are two totally different phones with totally different firmware. What or who on earth made you believe that I9300 firmware would work on an I9305..
That's the equivalent of a man dressing in womans clothing and saying "I didn't realise I don't have a vagina"..
Beamed in by telepathy.
Click to expand...
Click to collapse
I've already downloaded 2 firmwares for I9305 and used Odin, and I got a Fail status on the first one while the other one I got a Pass but still not working. Do I need to download more firmwares? Do I need to choose what country I have to download even if my device is not locked to a carrier?
Sorry this is just my first time to do something on phones, I was just advised by a friend to get help here on this site.
If you get a pass after flashing with Odin, make sure to perform a factory reset before booting the phone for the first timer with the new ROM.
audit13 said:
If you get a pass after flashing with Odin, make sure to perform a factory reset before booting the phone for the first timer with the new ROM.
Click to expand...
Click to collapse
Exactly, but usually you must flash, wipe, flash again to get rid of any old data.
Beamed in by telepathy.
audit13 said:
If you get a pass after flashing with Odin, make sure to perform a factory reset before booting the phone for the first timer with the new ROM.
Click to expand...
Click to collapse
Hi Audit,
How can I get to factory reset option before booting? Thank you.
Try this:
open Odin and uncheck everything excepf f.reset time;
flash the stock ROM;
when you see the word "reset" in the status window, remove the USB cable from the phone, remove the battery, wait about 5 seconds, replace the battery;
boot into recovery mode by pressing the home, volume up, and power button. When the phone starts to boot, let go of the power button but not the home or volume button;
when the phone boots into recovery, perform a factory wipe; and
reboot the phone.
audit13 said:
Try this:
open Odin and uncheck everything excepf f.reset time;
flash the stock ROM;
when you see the word "reset" in the status window, remove the USB cable from the phone, remove the battery, wait about 5 seconds, replace the battery;
boot into recovery mode by pressing the home, volume up, and power button. When the phone starts to boot, let go of the power button but not the home or volume button;
when the phone boots into recovery, perform a factory wipe; and
reboot the phone.
Click to expand...
Click to collapse
Just to add, removing the battery and replacing it may cause the phone to boot automatically. In this case just pull the battery again and when you reinsert it the screen should stay black. If not, keep doing it. THEN you can safely get to recovery.
When you get the blue "pass" in odin the phone should reboot automatically. If it doesn't just wait 10 seconds and pull the cable, then pull the battery or hold the power button for about 20 seconds.
Beamed in by telepathy.
shivadow said:
Just to add, removing the battery and replacing it may cause the phone to boot automatically. In this case just pull the battery again and when you reinsert it the screen should stay black. If not, keep doing it. THEN you can safely get to recovery.
When you get the blue "pass" in odin the phone should reboot automatically. If it doesn't just wait 10 seconds and pull the cable, then pull the battery or hold the power button for about 20 seconds.
Beamed in by telepathy.
Click to expand...
Click to collapse
Hi guys,
I tried again just now to flash with Odin but unfortunately I'm getting a Fail status.. see below..
<ID:0/005> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> AP_I9305XXUEMKC_2051278_REV00_user_low_ship.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/005> Odin v.3 engine (ID:5)..
<ID:0/005> File analysis..
<ID:0/005> SetupConnection..
<ID:0/005> Initialzation..
<ID:0/005> Get PIT for mapping..
<ID:0/005>
<ID:0/005> There is no PIT partition.
<OSM> All threads completed. (succeed 0 / failed 1)
I think my phone is completely bricked because previously it is showing battery charge when i plug it in but now the screen shows zigzag white & gray colors. Anything else I can do? Thanks again.
Try another *good quality* usb cable. * = not a cheap crap cable, one supplied with a device.
As the last port to call, flash a pit file for your specific model.
In all honesty I'll tell you that the pit file may break your phone permanently (most likely) or it could just as easily fix it. The partition information table is "missing" and usually indicates hardware failure. The 'fuzzy screen' is another indicator of a totally buggered phone.
Beamed in by telepathy.