I did go back to GB and i updated to newest GB nordic and i had my phone like that in hours without root or anything...and just like that i couldnt make call and when i went to setting it says baseband "unknown" so i asked around and ppl said wipe would fix the problem, when i made the wipe i got this error " E:failed to mount /efs (Invalid argument) " so i was thinkin maybe ill make a new flash in odin and i did that after that i couldnt start the phone, its turning on but i get only on samsung logo, i can go to download mode or CWM and i can use adb from pc to the phone but i cant do anything..so i check DATAFS and tested it and its corrupted, it goes to 5 % and then its stops.
So what can i do ? Please help..
wrong threads mate...this is devt...
wrong thread n you will not get answer here
It sounds like your EFS is corrupted, Do you by any chance have a back up of it ?
Check your IMEI number, I assume it will be Samsung generic 0044xxxxxxxxxxx something like that.
This happened to me a few times on the SGS1. I tried flashing GB via ODIN, with EFS clear ticked, It worked for me but i would advise you not to do this unless you have no other solutions.
When i check my IMEI *#06# then i dont get any IMEI, its empty and now when i try to flash gb stock or ICS then i cant start the phone..i get only to logo and when i try to wipe its gettin freezed
So is the phone booting at the moment ? Can you access recovery by any chance ?
Flashing a clean stock ODIN firmware usually fixes this issue.
azzledazzle said:
So is the phone booting at the moment ? Can you access recovery by any chance ?
Click to expand...
Click to collapse
I can access download mode and "CMW" without a problem and i can use the adb too but then i cant do anything else
ok, You definitely dont have an efs backup on your sd card or PC anywhere ? I have one on mine, I didnt create it, Some ROM or kernel created it but i cant recall which one.
azzledazzle said:
ok, You definitely dont have an efs backup on your sd card or PC anywhere ? I have one on mine, I didnt create it, Some ROM or kernel created it but i cant recall which one.
Click to expand...
Click to collapse
No sorry i dont have the efs backuped up, im new on this, everything happened without any reason, i didnt do anything...but i think the data is corrupted too cuz i cant do anything, i mean before i did the first time wipe i could go in the phone but i couldnt make call but now i cant do anything then download mode, recovery mode.
Ok, Well try this:
Go into CWM recovery, Wipe Cache partition and Dalvik Cache, DO NOT DO A FULL WIPE UNLESS YOUR KERNEL IS SAFE
then,
Flash stock GB via odin, After the flash, Reboot into recovery (will be stock android recovery) and do a full factory reset.
Then reboot, The phone should boot up normally, and hopefully EFS will be restored. If the phone doesnt boot, We can explore some other options.
The EFS corruption wont be preventing the phone from booting.
azzledazzle said:
Ok, Well try this:
Go into CWM recovery, Wipe Cache partition and Dalvik Cache, DO NOT DO A FULL WIPE UNLESS YOUR KERNEL IS SAFE
then,
Flash stock GB via odin, After the flash, Reboot into recovery (will be stock android recovery) and do a full factory reset.
Then reboot, The phone should boot up normally, and hopefully EFS will be restored. If the phone doesnt boot, We can explore some other options.
The EFS corruption wont be preventing the phone from booting.
Click to expand...
Click to collapse
Thanks ill try that and ill come back to u again, one question where can i get the fixed .pit files? cuz i had before mmc problem and i need special .pit files that someone modded here.. dont remember the link..do u ?
So your note is bricked ? or do you just think it could be ?
The pit files are on this thread http://forum.xda-developers.com/showthread.php?t=1667886
Only use them if you need to and are 100% sure your phone is bricked
azzledazzle said:
So your note is bricked ? or do you just think it could be ?
The pit files are on this thread http://forum.xda-developers.com/showthread.php?t=1667886
Only use them if you need to and are 100% sure your phone is bricked
Click to expand...
Click to collapse
This brick thing was long time ago and i fixed it with flashing pit...now after 3-4 week this happened with the radio but i was on stock GB nordic and didnt have root or anything and that happened...
Edit: btw can u give me safe KERNEL
Hmm i cant format /data, its gettin freezed.
Edit: now it says data wipe complete but it still get freezed, do you think i got problems with my /data ?
Right ok, Well Im not sure how flashing the pit files work, Luckily ive never had this issue, I assume you will flash them via ODIN combined with a firmware too ?
If thats the case, use GB as its always a safe option to go back to.
Or, I heard somewhere, that you could flash the NON patched pit files and this will put your phone back into the bricked state, Then you could send it out for warranty.
Anyway, this is the end of the line for me, I dont know what to do next im afraid But let me know how you get on
azzledazzle said:
Right ok, Well Im not sure how flashing the pit files work, Luckily ive never had this issue, I assume you will flash them via ODIN combined with a firmware too ?
If thats the case, use GB as its always a safe option to go back to.
Or, I heard somewhere, that you could flash the NON patched pit files and this will put your phone back into the bricked state, Then you could send it out for warranty.
Anyway, this is the end of the line for me, I dont know what to do next im afraid But let me know how you get on
Click to expand...
Click to collapse
When i made wipe in recovery mode, the phone got freezed but then it said its complete and it took time then i clicked to restart and now it take time to restart...i get to the samsung galaxy note gt n7000 and it get freezed for a bit then the phone restart again
Im confused, Is this happening before or after you flashed the patched pit files ?
Look here for a reference http://forum.xda-developers.com/showpost.php?p=26285877&postcount=12
Is there a way to remove the counts in adb or cmw or something if there is then i can go to service and go with my garanti.
azzledazzle said:
Im confused, Is this happening before or after you flashed the patched pit files ?
Look here for a reference http://forum.xda-developers.com/showpost.php?p=26285877&postcount=12
Click to expand...
Click to collapse
ive flashed with odin with stock and pit and the phone complete it and then after when it starts i get errors IU something...i do wipe and it freeze a bit then it complete then i reboot the phone and it gets freezed to logo
right i see,
So the phone is now completely stock right ? Including stock recovery also ?
if so, You can use a USB JIG to remove the yellow triangle and binary count, Thus resulting in a clean stock faulty phone of which you should get fixed under warranty.
Here's the guide on removing the binary count and triangle, you can make your own jig or buy one online. http://www.google.co.uk/url?sa=t&rc...vuz_Bg&usg=AFQjCNE_p2cZdwEpNAhP2QNPUyFYWAfmzQ
However Flashing stock firmware should have reset the binary count and removed the triangle.
Related
Phone won't boot past Galaxy Note Boot image
Phone will go in download mode by pressing Vol-Home Power buttons
Phone will go in recovery menu by pressing Vol+Home Power buttons but if i try to flash anything it shows verification error.
Anything flashed with Odin, goes successfully without any errors, but phone still won't boot past Galaxy Note boot image. When connected to PC in Odin mode USB recognised, when connected to PC with Galaxy Note boot image, USB not recognised (malfunctioning error appears)
I tried flashing ics/gb stock roms, kernels, pit files, and nothing helps
Please help
lastly
HAVE FLASHED N7000DDLC1_N7000ODDLC1_N7000DDLC1_HOME.tar.md5 using pc odin 3.04 and still stuck on gnote boot image
and lastly updated with :: N7000XXKL3_N7000ODDKL1_N7000DDKL1_HOME.tar.. but to no avail..
please help
do you have a custom kernal on such as hydroacore if you do or can try wiping cache and dalvic and factory reset then try reflashing if using pc maker sure kies is installed but dont use it use odin to flash a stock rom
anubis1126 said:
do you have a custom kernal on such as hydroacore if you do or can try wiping cache and dalvic and factory reset then try reflashing if using pc maker sure kies is installed but dont use it use odin to flash a stock rom
Click to expand...
Click to collapse
actually was on the stock ics and tried to install kingdroid by CWM.zip
and wiped data and cache from touch/temporary cwm..
then after install it got stuck on the first screen...
since then have tried to flash stock ics / gb firmwares but not getting past the first screen
first of all, make sure you don't make some foolish steps in wiping your phone., secondly, try to uninstall cmpletely PC kies and reinstall it again after. Once you've reinstalled that, don't open it, just open PC ODIN and try to boot back your phone in download mode. Make sure you have a yellow box on COM:1 in ODIN and use an extracted stock GB tar file and start flashing again.
EDIT: Since you've just mentioned you already wipe data in stock ICS.. are you using a safe kernel when you did the wiped?
if not, you may have toasted your Note.. imho...
it can take 5 to 10 mins after install to start however if it still goes no further and you can get into recovery can you flash any custom kernal,if you can do so then wipe and try to reflash if not i would ask dr ketan as he is awesome and may be able to help
^ No need to wait for that, as OP has already done a stupid thing of wiping on a touch CWM.. something that shouldn't be done at all....
only thing he can do is go to the section for the pit method partition to revive his phone... that's it!
letters_to_cleo said:
first of all, make sure you don't make some foolish steps in wiping your phone., secondly, try to uninstall cmpletely PC kies and reinstall it again after. Once you've reinstalled that, don't open it, just open PC ODIN and try to boot back your phone in download mode. Make sure you have a yellow box on COM:1 in ODIN and use an extracted stock GB tar file and start flashing again.
EDIT: Since you've just mentioned you already wipe data in stock ICS.. are you using a safe kernel when you did the wiped?
if not, you may have toasted your Note.. imho...
Click to expand...
Click to collapse
i was using the temp cwm used to gain root to flash .. very stupid i know..
my recovery and download modes are accessible so is my phone toast..
and if yes it is toast .. how to recover ??
letters_to_cleo said:
^ No need to wait for that, as OP has already done a stupid thing of wiping on a touch CWM.. something that shouldn't be done at all....
only thing he can do is go to the section for the pit method partition to revive his phone... that's it!
Click to expand...
Click to collapse
since i do have warranty on my phone left for another 2 months should i give it to the samsung repair center ?? what will they repair and how much time is expected it to repair ??
I suggest you ran first the partition scanner from here: http://forum.xda-developers.com/showthread.php?t=1823918, see if your partition don't have one of those bricked blocks....(courtesy of hg42)
Also consider this link - http://forum.xda-developers.com/showthread.php?t=1667886 for the pit file method
letters_to_cleo said:
I suggest you ran first the partition scanner from here: http://forum.xda-developers.com/showthread.php?t=1823918, see if your partition don't have one of those bricked blocks....(courtesy of hg42)
Also consider this link - http://forum.xda-developers.com/showthread.php?t=1667886 for the pit file method
Click to expand...
Click to collapse
but sadly the stock recovery is not accessing my memory card files and only internal sd and it has no option to mount storage ..
how to access the files i put in my memory card.. or should i flash some other ics stock rom as they have more options in stock recovery ??
no need to aggravate the problem by flashing another ICS... your Note's been bitten already.. don't let it bite twice...
Your last rom flashed is KL3 then have you wipe cache and data from recovery?
If not then do it, it should boot then.
Make sure last rom was flashed correctly and u are currently on KL3
If you have to press home button in recovery to enter your choice then it should be gb (kl3)rom (on ics you need to press power to select)
If wiping cache and data also not work, then flash wipe version of gb rom. If it stuck at data.img then yu have got damaged and should send to service Centre, without doing anything
Sent from my GT-N7000 using xda premium
After Rooting n using safe kernel, I was on RocketRom V3 and last week i updated to Ultimate Rom 5.1 JB and phone was working awasome, and then i tried to install awasome Beats throught CWM but i was not able to install it. then i again tried to install photo sphere through CWM but again same problem, when i select zip from SDCARd, after selecting nothing happens, so i thought CWM is corrupted and then i tried to restore the backup (rocketrom v3) but same thing happened, unable to even restore the backup so i was sure there's problem with CWM.
So i decided to to flash stock rom via PC ODIN and i installed stock rom N7000XXLPT, build number IML74K.XXLPY , android ver. 4.0.3.
after flashing, phone got stuck on samsung screen so i rebooted into recovery and wiped data factory n cache (i knw i was not supposed to do this but thr was no other option) and after wiping phone booted normally but i got many errors... unfortunately settings has stopped, unfortunately file manager has stopped, unfortunately software update has stopped has stopped etc etc.....
then i tried to install another stock rom (latest november) but now i m not even able to flash rom through PC ODin, FAIL... FAIL error with tht red color ...
So what could be done to get back to normal stock rom ?? Plzzz Help
is it stuck on factoryfs ?
if so, theres a big chance that doing the wipe caused the brickbug and only re-partition will fix it and bring it back to life.
before doing that, try to flash stock GB and see if it boots, if so, boot into recovery and do the wipes there, stock GB kernels are safe from the brickbug.
azzledazzle said:
is it stuck on factoryfs ?
if so, theres a big chance that doing the wipe caused the brickbug and only re-partition will fix it and bring it back to life.
before doing that, try to flash stock GB and see if it boots, if so, boot into recovery and do the wipes there, stock GB kernels are safe from the brickbug.
Click to expand...
Click to collapse
YEs, it stuck on factoryfs and the FAIL msg appears with REd background.
phone boots with many FCs and i mnot able to see any SDCARD, so its EMMC brick bug,
i guess i ll need to use PIT file method to revive from a MMC_CAP_ERASE brick
nitinbarve said:
YEs, it stuck on factoryfs and the FAIL msg appears with REd background.
phone boots with many FCs and i mnot able to see any SDCARD, so its EMMC brick bug,
i guess i ll need to use PIT file method to revive from a MMC_CAP_ERASE brick
Click to expand...
Click to collapse
Confirmed. Apologies. Notes once you repartition, there's a chance you won't be able to run full Roms with a larger file size due to damaged sections, you'll likely face fc's and freezes. After repartition look to cm based Roms as they take up less space and should work ok.
Sent from my GT-N7000 using xda premium
Hello, i have had my galaxy note for a couple of weeks now.
bit of this and that, you know how it is, flashing a few roms, checking things out, keeping it safe and stuff.
idiotic of me, didn't do a backup.
now
everything was working perfectly fine.
'till i decided to put some music on my sdcard
so i shut the phone down, open it up, take out the battery, take the sdcard, put it in pc, put some music (music i had on it before, so the files could've somehow magically ****ed up the device) then but it back on.
ever since, my device won't boot, it will go to CWM recovery, it will go to download mode, but not like, properly boot. all it does is show the Samsung Galaxy Note N7000 thingie, then screen goes black, and back again to Samsung Galaxy Note N7000, then black again, over and over again.
i figured, it must be something wrong with the bootanimation, had a custom one put there, so i deleted it, cuz that way it goes back to stock.
did that, didn't help, same thing.
then, decided to flash the rom again, even tho it was working perfectly for a few days now, (stock 4.0.4 deodexed zipaligned with hydracore safe kernel)
reflashed, didn't help, nothing happened.
things were weird, i thought i should go back to a GB rom, that always...fixes the problem.
tried to flash with ODIN, stuck at factoryfs, when i pulled the cable out, it would tell me the thingummyjig with firmware update has encountered an issue please bla bla kies.
then, I EVEN TRIED the kies, it won't connect, even tho my drivers are right, and i used kies with it before.
NOW, i thought to myself, ****, the phone won't go to recovery anymore, won't boot normaly, just in download, well, download a speedmod kernel which is safe and flash it, that should give you a CWM and safe kernel to flash from
did that, worked.
flashed the stock 4.0.4 rom again, then flashed philz latest kernel for the rom, and i'm back to square one.
nothing changed, i still can't use my note.
WHAT. DO?
right, well, i tried flashing alliance rom, and it gets stuck at mounting partitions....
the blue bar goes on and on till it gets out of the designated loading space
i can't wipe cache, i can't wipe dalvik, it just gets stuck.
Etnoscope said:
... tried to flash with ODIN, stuck at factoryfs ...
Click to expand...
Click to collapse
I just quoted the bad line in your post. This is a strong indicator that you have a bricked device.
So you should try to install a different stock GB or ICS Rom with Odin again. If it stucks there again: bricked.
Then you can try to use the workaround described in hg42's thread with repartition. Or send your device for a motherboard replacement to Samsung.
hg42 has a partition scanner which allows to check for emmc problems. Try this.
ThaiDai said:
I just quoted the bad line in your post. This is a strong indicator that you have a bricked device.
So you should try to install a different stock GB or ICS Rom with Odin again. If it stucks there again: bricked.
Then you can try to use the workaround described in hg42's thread with repartition. Or send your device for a motherboard replacement to Samsung.
hg42 has a partition scanner which allows to check for emmc problems. Try this.
Click to expand...
Click to collapse
Thing is, phone worked flawlessly before, safe kernel,could flash anything,then this just happened....
Phone doesnt have warranty, sending it to some service would only have me end up with extra costs for putting the motherboard there, which i can do myself
right, welll
i tried flashing speedmod kernel with odin, it worked.
then i tried installing a GB rom via CWM
works well till it gets stuck at flashing modem.
what does this mean?
Etnoscope said:
...what does this mean?
Click to expand...
Click to collapse
As I wrote before: possibility that you have a bricked device.
Why don't you try the partition scanner or why don't you try to flash a stock GB and check if you get stuck again with factoryfs.img.
As long as you try different things without a "plan" what you want to test you'll get nothing in the end.
ThaiDai said:
As I wrote before: possibility that you have a bricked device.
Why don't you try the partition scanner or why don't you try to flash a stock GB and check if you get stuck again with factoryfs.img.
As long as you try different things without a "plan" what you want to test you'll get nothing in the end.
Click to expand...
Click to collapse
tried flashing a stock gb with odin (tried 1 file in pda before, now i tried with 3 files(modem, rom, csc), same thing happened.)
stuck at factoryfs again
i didn't want to get to the partition scanner yet, wanted to clear out any other possibility first, using the scanner as a last resort.
what about pit files?
***
also, i really wanna thank you for showing some interest in my issue, means a lot to me, just wanted to let you know i really appreciate it, and i acknowledge the fact that you're a good, helping member.
thanks bro, you're awesome.
If you have tried also with the correct original pit, then it's time for the scanners to do its job
nokiamodeln91 said:
If you have tried also with the correct original pit, then it's time for the scanners to do its job
Click to expand...
Click to collapse
right
so, i've checked out this thread, about the pit method, and after i opened the emmc_find_brick_start.zip, it started scanning normally, and it finished without being stuck anywhere, and then at the end it said scanned 15027 MiB = 15757 MB completed --> OK then the ---end thingie and done.
so the brick start isn't there, which i assume means my phone is NOT bricked, at least not by the emmc thingummyjig
but if so, what the hell am i to do? like really?
tried flashing gb with cwm, stuck at flashing modem
tried flashing gb with odin, stuck at factoryfs
what the ****?
Get the pit file from this thread
http://forum.xda-developers.com/showthread.php?t=1424997
Then flash the GB rom using pc odin. Make sure pit is selected and the repartition is ticked.
Also if you still have access to cwm try to install a CM10 rom first before trying out the above method.
SOOOOO
bit of an update.
right, after the whole emmc scanning brick mbs and stuff, decided to try and flash allianceROM 4.0.4 final
did it, worked, the flashing.
now i'm stuck at a non blinking, non changing non nothing, Smasung Galaxy Note GT-N7000 screen, with the yello jello triangle, same as before, but its not blinking now.
Ok. Try booting into recovery and performing a full wipe.
nokiamodeln91 said:
Ok. Try booting into recovery and performing a full wipe.
Click to expand...
Click to collapse
full wipe means:
factory reset
wipe cache
wipe dalvik
reboot.
right?
did that, as soon as i hit reboot, it got stuck again there, the frozen CWM screen.
battery in/out, back to square 1
Still try a cm rom as it's small in size and easier to download. CM10.1 flash from recovwey
nokiamodeln91 said:
Still try a cm rom as it's small in size and easier to download. CM10.1 flash from recovwey
Click to expand...
Click to collapse
official 4.2.1 will do?
Yeah
nokiamodeln91 said:
Yeah
Click to expand...
Click to collapse
any way we could talk via IM?
would be much better conversation-wise
We could but where I am, it's 4 am. And I will be off to sleep in a while. Hehe
nokiamodeln91 said:
We could but where I am, it's 4 am. And I will be off to sleep in a while. Hehe
Click to expand...
Click to collapse
i get status 7 error when i try to flash a CM rom btw, i know what to do, updating philz kernel as we speak
i want you to know i really appreciate this bro, couldn't have come so far without you. thanks a lot man.
right, well, i was using kangbang kernel, tried to install the cm rom, and it gets stuck at installing update...
been there for too long now,so i guess thats a safe bet.
gonna try with a different cm rom
right, well, apparently anything i try to flash gets stuck at installing update....
any solutions?
Hey there, ive got a Galaxy Note that was attemped to wipe data from with cwm.zip and that caused it too reboot and the original rom was wrecked, my situation now is that i cant access CWM anymore, if boot phone with power button only i get the recovery mode telling me to connect to Kies.
But Kies doesnt see that the phone is in recovery mode and just keeps on saying "Connecting" in the top left panel.
When i boot into download mode and try to flash an original rom and .pit 16gb file, it sticks at "factoryfs.img"
I am out of ideas and desperate as its not my phone, i have googled and tried different solutions for hours but to no avail.
Thanks in advance.
If you have tried to wipe data using temp cwm them most probably it's bricked. Check hg42 repartition method. You will loose some GB of memory but the phone may boot.
http://forum.xda-developers.com/showthread.php?t=1667886
But always first try to install a GB rom first, incase that works. Most probably a 3 file rom.
nokiamodeln91 said:
If you have tried to wipe data using temp cwm them most probably it's bricked. Check hg42 repartition method. You will loose some GB of memory but the phone may boot.
http://forum.xda-developers.com/showthread.php?t=1667886
But always first try to install a GB rom first, incase that works. Most probably a 3 file rom.
Click to expand...
Click to collapse
I honestly dont care if i lose GBs, i use a 64gb SD card, but anyhow, could you link me the 3 file GB rom i need? phone is from sweden so i guess any european one should do, i just dont want to mess up things more, would be eternally grateful if you could link me what i need.
i cant do the "find brick" since im on the connect to kies recovery, not the standard recovery where i can flash stuff, either that or download mode.
thanks
http://hotfile.com/dl/141781856/f226b7d/N7000XXLA3_N7000OXALA3_OXA.rar.html
Here is how to get into recovery if only download mode and check for bad blocks. use this only if you dont have warranty and flashing GB fails as well a factoryfs.img.. also make sure you reboot into download mode if the flash is not successful. dont continue from there itself..
http://forum.xda-developers.com/showpost.php?p=26285877&postcount=12
EDIT: Got it working on GB, thank you sooo much!!!!
Good. Boot into recovery and do a factory reset.
HI all,
Today I decide to update my i9305t to the 4.3 rom. I unrooted my phone and reset the custom counter and all was good. I flashed the telstra rom and all was good. Because of the locked dock Icons I thought I would flash a different unbranded rom. During the installation (via odin) it went skew if and froze. It sat there for ages but I ended up having to do a battery pull.
When I went to the download menu on the phone, knox had been tripped and there was 47 instances. Any way I reflashed the telstra firmware. It passed but now the phone gets stuck on the Samsung logo.
OK now I have already.....
Pulled the battery.
Removed all cards sim and sd.
Restored different firmwares.
factory reset, clear cahce etc.
Installed custom recovery and cleared devalk cache.
Googled for similar events.
Nothing I have read has worked.
I cant think of what else to do. When I restore a firmware via odin everything is OK, it passes but on the reboot it just stops at Samsung logo and goes no further.
I gather that because the phone can still get into recovery and download mode there must be something can sort this out.
Thanks in advance.
flash the original firmware from samsung.....the 4.3 since you updated it...
after it finishes and reboots it will enter a boot loop....IT'S NORMAL.....pull out the battery and start the phone in recovery mode(stock one) and do a wipe data - factory reset and wipe cache partition...it should work without a problem...did this many times...
after you updated to 4.3 you should have done a full wipe...
spiderman07 said:
flash the original firmware from samsung.....the 4.3 since you updated it...
after it finishes and reboots it will enter a boot loop....IT'S NORMAL.....pull out the battery and start the phone in recovery mode(stock one) and do a wipe data - factory reset and wipe cache partition...it should work without a problem...did this many times...
after you updated to 4.3 you should have done a full wipe...
Click to expand...
Click to collapse
Yeah I have done that. I have tried it about 10 times. Im going to give it another bash today as I am stuck using my wife's old Iphone and its horrendous.
try installing your firmware with a .PIT file and check repartition box...search for the pit file....
if this doesn't work i suggest going to local repair shop and let them have a look...
maybe something got broke when you flashed the unbranded firmware...
spiderman07 said:
try installing your firmware with a .PIT file and check repartition box...search for the pit file....
if this doesn't work i suggest going to local repair shop and let them have a look...
maybe something got broke when you flashed the unbranded firmware...
Click to expand...
Click to collapse
Thanks for the info. Im unsure what a PIT file is. Are they phone specific or just model specific.
Cheers
Pat
Filipiak said:
Thanks for the info. Im unsure what a PIT file is. Are they phone specific or just model specific.
Cheers
Pat
Click to expand...
Click to collapse
Found the pit file and read up on it. Tried to use it but it fails as soon as it starts.
Best of luck
Well I was in the same pickle
whicever 4.3 rom i flashed through odin i got stuck in boot logo or even if i recovered device from odin through emergency frimware and intillation
Also tried customs 4.3 roms stuck a boot logo
Here what u should try and what i did
1 flash philz recovery + 4.1.2 rom
if it works back up efs
2 Using Philz recovery wipe data factory reset + wipe cache + dalvik cache
3 in mount and storage section format everything ( THINK THIS IS THE MOST IMPORTANT STEP )
4 Used odin to flash a 4.3 stock package it worked ( note u may get knox from this u may try a modifed stock package if u dont have knox and dont want to get it )
AMoizK said:
Well I was in the same pickle
whicever 4.3 rom i flashed through odin i got stuck in boot logo or even if i recovered device from odin through emergency frimware and intillation
Also tried customs 4.3 roms stuck a boot logo
Here what u should try and what i did
1 flash philz recovery + 4.1.2 rom
if it works back up efs
2 Using Philz recovery wipe data factory reset + wipe cache + dalvik cache
3 in mount and storage section format everything ( THINK THIS IS THE MOST IMPORTANT STEP )
4 Used odin to flash a 4.3 stock package it worked ( note u may get knox from this u may try a modifed stock package if u dont have knox and dont want to get it )
Click to expand...
Click to collapse
Knox was tripped when the firmware install crashed. So knox tripping is no issue. Thanks for the information. I will have a go tommorrow.
I did manage to restore a cm9 backup but my IMEI is now gone and I cant get to the menu to restore my back up. Seems like Samsung has done a number on my phone. In all the years ive been fingering phones with custom firmware and modding I have never had anything stuff up this bad. Its rather amusing that it has happened flashing a stock rom that belongs to my phone.
AMoizK said:
Well I was in the same pickle
whicever 4.3 rom i flashed through odin i got stuck in boot logo or even if i recovered device from odin through emergency frimware and intillation
Also tried customs 4.3 roms stuck a boot logo
Here what u should try and what i did
1 flash philz recovery + 4.1.2 rom
if it works back up efs
2 Using Philz recovery wipe data factory reset + wipe cache + dalvik cache
3 in mount and storage section format everything ( THINK THIS IS THE MOST IMPORTANT STEP )
4 Used odin to flash a 4.3 stock package it worked ( note u may get knox from this u may try a modifed stock package if u dont have knox and dont want to get it )
Click to expand...
Click to collapse
AMoizK you are the ****en man. Worked. The part that worked for me was the format everything. IMEI restored as well. Phone is perfect. Now i dont need to use my wifes crappy old iphone.
WOOT!!!!
Filipiak said:
AMoizK you are the ****en man. Worked. The part that worked for me was the format everything. IMEI restored as well. Phone is perfect. Now i dont need to use my wifes crappy old iphone.
WOOT!!!!
Click to expand...
Click to collapse
Cheers
Filipiak said:
HI all,
Today I decide to update my i9305t to the 4.3 rom. I unrooted my phone and reset the custom counter and all was good. I flashed the telstra rom and all was good. Because of the locked dock Icons I thought I would flash a different unbranded rom. During the installation (via odin) it went skew if and froze. It sat there for ages but I ended up having to do a battery pull.
When I went to the download menu on the phone, knox had been tripped and there was 47 instances. Any way I reflashed the telstra firmware. It passed but now the phone gets stuck on the Samsung logo.
OK now I have already.....
Pulled the battery.
Removed all cards sim and sd.
Restored different firmwares.
factory reset, clear cahce etc.
Installed custom recovery and cleared devalk cache.
Googled for similar events.
Nothing I have read has worked.
I cant think of what else to do. When I restore a firmware via odin everything is OK, it passes but on the reboot it just stops at Samsung logo and goes no further.
I gather that because the phone can still get into recovery and download mode there must be something can sort this out.
Thanks in advance.
Click to expand...
Click to collapse
It happened to me once, i found that 4.3 won't boot if baseband and imei are unknown. when you were trying to flash with odin and your phone got stuck it probably has damaged or ( erased ) your imei partition. try flashing 4.1.1 ( the package file without bootloader files ) it will definitely work for you. the reason is simple , Samsung's stock 4.3 never boots if the imei is corrupt or unknown (baseband is then usually too ) so, flash 4.1.1 , root your phone and install Persus kernel +any modem / baseband file, this is the only solution as i dont know how but does repair your imei , but you will be stuck at 4.1.1.