Related
Hi All,
I'm on ics stunner 1.4.26_1 LP6 kernel. I wish to go back to stock GB after seeing some bricked notes. whats the best way to go about it?
can i just download the stock firmware i was using before from samfirmware and simply flash pda using ODIN desktop?
if so, any options i should check before flashing?
many thanks!
http://forum.xda-developers.com/showthread.php?p=25181479
Sent from my GT-N7000 using xda premium
Solution
Here's what I Did:
Downloaded the stock jpkk2 firmware from sammobile.com
Used PC ODIN to flash the stock ROM. Re-Partition option was not selected.
Once done, the phone rebooted and went into a bootloop.
To cure that I went into recovery and did a factory reset, Wipe Cache and next time it rebooted normally.
For those who had the same situation as mine and dont wish to go into lengthy procedure in the linked thread above, you can do what i did
jakhan86 said:
Here's what I Did:
Downloaded the stock jpkk2 firmware from sammobile.com
Used PC ODIN to flash the stock ROM. Re-Partition option was not selected.
Once done, the phone rebooted and went into a bootloop.
To cure that I went into recovery and did a factory reset, Wipe Cache and next time it rebooted normally.
For those who had the same situation as mine and dont wish to go into lengthy procedure in the linked thread above, you can do what i did
Click to expand...
Click to collapse
+1 to that. I used the exact same procedure, everything went fine and I'm now running RocketROM v23, as I think it's the ok-est ROM so far on GB
I do so miss ICS though sometimes...
EDIT: apparantly I might be very wrong.
bioweb said:
If you already flashed Stunner then in my opinion you have nothing to worry about. Once the rom is flashed your phone won't magically brick itself at some point.
Click to expand...
Click to collapse
According to the opinion of Entropy512, you may indeed have something to worry about. Even after flashing your eMMC can still be damaged. No offence, but I'm more inclined to believe him than you!
Some posts that might be of interest to you:
http://forum.xda-developers.com/showpost.php?p=25356877&postcount=28
http://forum.xda-developers.com/showpost.php?p=25385420&postcount=69
Neh, don't trust those guys that know what they're talking about, have faith in little old me
That's troubling news indeed. I've done a crapload of wiping and flashing ICS roms and kernels but so far I've had no problems whatsoever. But after reading that thread I might just revert back to a GB rom. I love Stunner's rom and ICS in general but would be devastated if my Note cries 'mein Leben' a week before the official, hopefully problem-free ICS update.
I hope Samsung is aware of these faulty driver settings, otherwise we'll see loads of bricked Notes in a couple of weeks.
bioweb said:
Neh, don't trust those guys that know what they're talking about, have faith in little old me
That's troubling news indeed. I've done a crapload of wiping and flashing ICS roms and kernels but so far I've had no problems whatsoever. But after reading that thread I might just revert back to a GB rom. I love Stunner's rom and ICS in general but would be devastated if my Note cries 'mein Leben' a week before the official, hopefully problem-free ICS update.
I hope Samsung is aware of these faulty driver settings, otherwise we'll see loads of bricked Notes in a couple of weeks.
Click to expand...
Click to collapse
Yes, it's very troubling! I've changed to the DAFUQ kernel, which is not based on the faulty Samsung leaks and is supposedly safe. It's a little bit buggy on Stunner (no boot anim, sometimes colours are screwed up and you have to turn the screen on and off, but no major bugs so far). For me it beats going back to GB because I simply love tablet mode. EDIT: Also, no external sdcard...
Personally I think a big fat warning about the leaked kernels should be stickied on the forum or something because lots of people don't seem to be aware of the issues, including more experienced members.
I just flash abysnotekernel and restore my GB backup. It takes less then 5 mins.
bioweb said:
Neh, don't trust those guys that know what they're talking about, have faith in little old me
That's troubling news indeed. I've done a crapload of wiping and flashing ICS roms and kernels but so far I've had no problems whatsoever. But after reading that thread I might just revert back to a GB rom. I love Stunner's rom and ICS in general but would be devastated if my Note cries 'mein Leben' a week before the official, hopefully problem-free ICS update.
I hope Samsung is aware of these faulty driver settings, otherwise we'll see loads of bricked Notes in a couple of weeks.
Click to expand...
Click to collapse
are you implying ICS is coming to Note in two weeks? any official word on it?
Sorry to hijack the thread, I just downgraded from STUNNER to GB,
Flashed the pre-rooted "N7000DXLC2_CSC_N7000OLBLC2",
how can I install CWM on this? I don't find any thread for LC2 installation.
Thanks...
luckygolf said:
Sorry to hijack the thread, I just downgraded from STUNNER to GB,
Flashed the pre-rooted "N7000DXLC2_CSC_N7000OLBLC2",
how can I install CWM on this? I don't find any thread for LC2 installation.
Thanks...
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1329360
I checked this thread where they post all the rooted kernels and CWM for those ROMS. LC2 is not in the list. Why not flash a compatible ROM from that thread?
jakhan86 said:
are you implying ICS is coming to Note in two weeks? any official word on it?
Click to expand...
Click to collapse
Oh, no, haha, sorry for the misunderstanding. It was just an example of Murphy using his law to mess up my Note right before ICS is finally released
bioweb said:
Oh, no, haha, sorry for the misunderstanding. It was just an example of Murphy using his law to mess up my Note right before ICS is finally released
Click to expand...
Click to collapse
lol. I got excited!
i just went back to GB (cassie's Xtralite rom) from stunner using Chasmodo's method mentioned.
install abyss kernel 4.2
reboot into recovery
do the wiping
install custom GB rom
no problems whatsoever.
vivek2701 said:
i just went back to GB (cassie's Xtralite rom) from stunner using Chasmodo's method mentioned.
install abyss kernel 4.2
reboot into recovery
do the wiping
install custom GB rom
no problems whatsoever.
Click to expand...
Click to collapse
Unless I've misunderstood Entropy512s posts on the matter, you still risked a hardbrick because you used the leaked kernel in stunner to flash the abysskernel.
The safest way to revert to GB is to flash an original or prerooted ROM using PC Odin thusly:
1. Odin flash a prerooted rom from here:
http://forum.xda-developers.com/showthread.php?t=1535025
Do a factory reset wipe from the recovery menu (volume up + home + power) if you are stuck in a boot loop.
2. Flash a CF-rooted kernel from here:
http://forum.xda-developers.com/showthread.php?t=1331784
3. Flash your preferred flava from CWM
Sent from my GT-N7000 using xda premium
For me this is the safest way to do this:
1. Download the Abyss 4.2 Red Pil kernel and put it on your internal sd card.
2. Boot into recovery
3. Flash the Abyss kernel and do not exit recovery yet
4. Go to the advanced menu and choose"reboot recovery"
5. Now you're in the Red Pil recovery
6. Wipe Cache, then Wipe Dalvik Cache, then Wipe data/factory settings
7. Install the GB Rom of your choice
8. Reboot. At this point, I leave the phone alone for 10 minutes - I don't set up anything, just let the phone sit. Then I reboot again.
9. Set up your phone and enjoy
glensta said:
For me this is the safest way to do this:
1. Download the Abyss 4.2 Red Pil kernel and put it on your internal sd card.
2. Boot into recovery
3. Flash the Abyss kernel and do not exit recovery yet
4. Go to the advanced menu and choose"reboot recovery"
5. Now you're in the Red Pil recovery
6. Wipe Cache, then Wipe Dalvik Cache, then Wipe data/factory settings
7. Install the GB Rom of your choice
8. Reboot. At this point, I leave the phone alone for 10 minutes - I don't set up anything, just let the phone sit. Then I reboot again.
9. Set up your phone and enjoy
Click to expand...
Click to collapse
Technically you could still brick your Note because you're flashing Abyss with the flawed ICS kernel you're on. I did the same however to revert back to a GB rom (thanks again pboesboes for posting the links) and at the moment I'm using Checkrom with Abyss 4.2 and Nemus Launcher.
To make absolutely sure you won't run into any problems Hawklan_D's method is the safest.
Hawklan_D said:
Unless I've misunderstood Entropy512s posts on the matter, you still risked a hardbrick because you used the leaked kernel in stunner to flash the abysskernel.
The safest way to revert to GB is to flash an original or prerooted ROM using PC Odin thusly:
1. Odin flash a prerooted rom from here:
http://forum.xda-developers.com/showthread.php?t=1535025
Do a factory reset wipe from the recovery menu (volume up + home + power) if you are stuck in a boot loop.
2. Flash a CF-rooted kernel from here:
http://forum.xda-developers.com/showthread.php?t=1331784
3. Flash your preferred flava from CWM
Sent from my GT-N7000 using xda premium
Click to expand...
Click to collapse
Thanks for that... But it wont get bricked now?? Right...?
Lol all is good when the end is good..
Sent from my GT-N7000 using Tapatalk
vivek2701 said:
Thanks for that... But it wont get bricked now?? Right...?
Lol all is good when the end is good..
Sent from my GT-N7000 using Tapatalk
Click to expand...
Click to collapse
I'm not the person to say for sure, but I think if you've successfully flashed away from the leak repack ICS kernels by whatever method with no ill effects, you're in the clear.
That's my hope anyway, having messed with a lot of the flashing methods / kernels with (touch wood) no damage to my Note.
Sent from my GT-N7000 using xda premium
here is my situation:
rooted galaxy mini with CM9 installed.
i remember when i installed this i first flashed my stock phone using odin. that process rooted it. then i installed CWM in recovery mode. then i installed the CM9 file again in recovery mode.
now i want to go back to GB. i am downloading the official rom for my country from sammobile. my query is that do i simply install that rom from recovery mode or do i again have to flash it using odin or something? also is there a way to UNROOT my mobile or not?
kindly give me a detailed procedure. i looked in the threads for this but did not find detailed info.
thanks in advance
flash the official rom with odin and there you go
Either flash any custom gb-based rom, or just flash stock with odin, the second option will also unroot your phone. Search on yagyagaire.blogspot.com for detailed instructions.
Flash the latest stock rom again..
But first wipe data/cache
Sent From Mobile Network
yackovsky said:
Either flash any custom gb-based rom, or just flash stock with odin, the second option will also unroot your phone. Search on yagyagaire.blogspot.com for detailed instructions.
Click to expand...
Click to collapse
i did as you told. i checked for the detailed instructions from the website. i followed each and every detail. even odin showed the PASS sign. but the problem is that my phone starts then the samsung galaxy mini screen shows up. it doesn't fo further from here. its like stuck on the same screen.
kindly instruct me now what to do.
khurram6050 said:
i did as you told. i checked for the detailed instructions from the website. i followed each and every detail. even odin showed the PASS sign. but the problem is that my phone starts then the samsung galaxy mini screen shows up. it doesn't fo further from here. its like stuck on the same screen.
kindly instruct me now what to do.
Click to expand...
Click to collapse
oh man, have you wiped data and cache before flashing? since i installed custom rom on my phone i didn't even think about getting back to stock, but i know that you have to wipe before you do...
yackovsky said:
oh man, have you wiped data and cache before flashing? since i installed custom rom on my phone i didn't even think about getting back to stock, but i know that you have to wipe before you do...
Click to expand...
Click to collapse
nah, i didn't wipe the cache. ok let me try that. get back to u in 5min
yackovsky said:
oh man, have you wiped data and cache before flashing? since i installed custom rom on my phone i didn't even think about getting back to stock, but i know that you have to wipe before you do...
Click to expand...
Click to collapse
i wiped the cache and data and flashed again using odin. no errors during flashing. nut still its stuck on boot animation. what to do?
khurram6050 said:
i wiped the cache and data and flashed again using odin. no errors during flashing. nut still its stuck on boot animation. what to do?
Click to expand...
Click to collapse
what version of odin did you used? for galaxy mini it's recommended to use odin 4.38. here's instruction that i used to upgrade my phone to gingerbread http://yagyagaire.blogspot.ie/2011/12/how-to-upgrade-samsung-galaxy-pop-to.html#more just replace firmware with your region, for me it was europe
firmware is not important..any region is fine...
samsung is racist XD for dividing the same old AOSP gingerbread into different locales and simply adding new lockscreens in new builds XD
lol
khurram6050 said:
i wiped the cache and data and flashed again using odin. no errors during flashing. nut still its stuck on boot animation. what to do?
Click to expand...
Click to collapse
Wipe data and cache before and after flashing. Or try using the firmware which has 4 files... use XWKTN.
Sent from my SGM using Official Cyanogenmod 7.2 (STABLE)
Today I tried to update my phone to a new custom rom.
I followed the instructions of the threads and tried to get it to work.
Of course it didn't work or else I wouldn't be here right now asking for help.
Here's the current situation.
I am able to boot into download mode + recovery mode and also boot into cwmr and install a different kernel.
I used pc odin to install it each time and it does pass and the rom (i've tried installing a gingerbread rom so that I can try everything again) does install.
the problem is that it is currently stuck in a boot loop at the "Samsung galaxy note gt-N7000" screen.
I have looked up dr.ketan's posts and tried some too.
currently i am booting abyss note kernel 42cwt touch original. (I know for sure it is a workable kernel because I've been using it this whole time.
here's what i've done. please tell me what i've done wrong and the possible ways to reverse it.
1. backed up everything
2. went into recovery
3. factory reset/cache clear
4. use pc odin to install new kernel (since I was looking into switching to another kernel anyways)
5. use pc odin again to install gingerbread rom (I do get the green light saying it did get installed
6. phone auto reboots
7. it gets stuck at the boot loop like i have mentioned above
i will try to attach a few pictures of my note as soon as I can so you can see what's going on with it.
What rom is there on the phone now ? if you boot into recovery .. what recovery do you get now ? CWM or stock ardroid 3e recovery ?
nokiamodeln91 said:
What rom is there on the phone now ? if you boot into recovery .. what recovery do you get now ? CWM or stock ardroid 3e recovery ?
Click to expand...
Click to collapse
Right now it reboots to 3e recovery.
The rom that I tried to inject to it is currently a the stock gingerbread rom from dr. Ketans thread.
The rom that I had on it is the official ics rom for the hk region.
The rom that I wanted to inject to it was a custom jb rom that uses hydracore as a kernel.
Thanks!!
try installing a prerooted Gb rom or an ICS stock rom using PC odin.. if you choose ICS, after flash install a safe kernel..
nokiamodeln91 said:
try installing a prerooted Gb rom or an ICS stock rom using PC odin.. if you choose ICS, after flash install a safe kernel..
Click to expand...
Click to collapse
If I do a stock ics update can I just do it through kies or do I have to do it through pc odin? Also. Would abyss or hydracore considered as a safe kernel???
yes if kies can do it then good but at this situation i dont think. its better to use PC odin for now. yes both are safe kernels
nokiamodeln91 said:
yes if kies can do it then good but at this situation i dont think. its better to use PC odin for now. yes both are safe kernels
Click to expand...
Click to collapse
I've tried your suggestions...and it didn't seem to work out too well.
I am able to flash to different kernels and get in and out of different recovers and such, but ya...still no luck with running a rom.
Well I am not sure but I soft bricked my phone when I tried that Abyss Kernel. In my view Hydracore is safe. Philz is super safe.
Flash ICS which matches your region using Odin. If phone boots flash Philz, If not, then be ready to read a lot of stuff or get phone repaired.
asian_boi said:
I've tried your suggestions...and it didn't seem to work out too well.
I am able to flash to different kernels and get in and out of different recovers and such, but ya...still no luck with running a rom.
Click to expand...
Click to collapse
instead of flashing kernels. flash a complete rom using PC odin.
nokiamodeln91 said:
instead of flashing kernels. flash a complete rom using PC odin.
Click to expand...
Click to collapse
You have so much patience
Sent from my Amazon Kindle Fire using Tapatalk 2
the only thing i have...
Hey guys. my note seems to have cooperated and allowed me to flash a new rom and also a new kernel. Here's the catch though, now it's stuck in the samsung logo and won't boot beyond that. Any suggestions of what to do? I am continually searching on the forums to find a solution.
At least I'm happy to know it's not a brick that can't be fixed.
Thanks nokiamodeIn91 for your help so far. I really appreciate it.
which rom did you flash and which kernel? how?
He spent a lot of time helping you. Be sure to hit thanks button
Sent from my GT-N7000 using Tapatalk 2
I currently flashed the abyss note kernel 42 cw touch and I downloaded an old gb rom from sammobile .
Here's what I did.
1. Put my phone into download mode
2. Run as admin on PC Odin
3. Selected the Abyss kernel then flashed it.
4. Boot into the cmw, wiped cache then booted the phone into download mode again.
5. Then I installed the old GB Rom on to my phone and restarted it.
6. Phone starts, loads past the GT-N7000 logo and goes into the samsung boot logo.
7. Phone repeats the animation of the samsung logo a time or two then restarts on its own. This loops until the phone is completely drained. I know that the rom works because that was the rom that I used to root my phone. I definitely don't mind downloading another rom if I have to.
my current goal, if we can fix this, is to quickly just update to the official jb rom for n7000 and not play around with the rooting and such until I have even more time to learn more.
at least I know for sure my phone isn't hardbricked, I would imagine I have either missed a step or something that caused the problem.
I have read through the forum and I did come across one post talking about checking my phone's partition and such.
I got to be honest, I'm really not technically skilled enough at this point in time to dare to mess around with that type of thing yet especially with so much coding to make sense of it. (I know this is kind of dumb to say especially when I rooted my phone and screwed up this bad). More importantly, I don't even know for sure if I need to do a partition or not.
Please let me know what I did wrong and how I can fix it.
I got a question though (out of curiosity), how come there's no toolkit for the n7000 like the S3 and also the note 2???
this is the name of the old gb rom that I tried flashing.
N7000ZSKJ6_N7000OZSKJ6_N7000XXKJ6_HOME.tar
I actually have tried several other roms as well (from GB-JB, official and custom) and all of them so far has gotten to the samsung boot logo
I have read on the forums to try using Philz-cwm 6 kernel but I don't know if it'd solve my problem.
let me show you one of the threads I have read, if I dived into the wrong material let me know and I won't consider using it (or learn how to use it) for my current situation
http://forum.xda-developers.com/showthread.php?t=1661590&highlight=samsung+logo+bootloop&page=2
like I was saying before, I really have no experience in coding so all the things that really made near no sense to me. I understand the basic concept of what its trying to do it's just seems like a very unsafe method for me to try especially when I lack the necessary knowledge in this area of expertise.
did you flash the GB rom using the standard PIT file ?
also you could try with the 5 file flashing method from this thread
http://forum.xda-developers.com/showthread.php?t=1530501
Hello..
Why are you only wiping cache.
You should have done a factory reset on that step.
Sent from my GT-N7000000000 using Tapastalker 2
asf58967 said:
Hello..
Why are you only wiping cache.
You should have done a factory reset on that step.
Sent from my GT-N7000000000 using Tapastalker 2
Click to expand...
Click to collapse
Yeah true... should also format system..
**** if you can boot into recovery , do a facotry wipe now
Hi all
N7000 @ 4.1.2 with PhilZ.Speedmod
Odd behaviour began a few days ago: Single tap power button would cause the Reboot/Airplane mode menu followed by a crash a few seconds later. This became more and more likely to happen so I wiped user data and performed a full factory reset/cache wipe etc.
Went through the android start up as per usual and only installed non-root apps just to be on the safe side (except Titanium Backup - which i use to freeze Touchwiz).
About 4 hours after, same problem only this time it wont get past Samsung Galaxy Note GT-N7000 Splash screen image at all.
A new battery was inserted a few days ago - could this have damaged the board maybe?
Recovery STILL works but I don't have any backup images.
Odin recognizes the phone in download mode
Should I try a different kernel/rom?
Really lost without my note.
Any help gratefully receieved!
Regards
Warnoceros
I am having the same issue. Was on Carbon Rom and everything was working fine, then after a restart the phone cannot pass the boot animation. It just shuts off right in the middle of booting. Have tried to reflash back to GB and still the same issue.
Flash a new fresh 4.1.2 rom thorugh pc odin after doing all necessary wipes
Sent from my GT-N7000 using Tapatalk 2
try use another battery...
RickR78 said:
I am having the same issue. Was on Carbon Rom and everything was working fine, then after a restart the phone cannot pass the boot animation. It just shuts off right in the middle of booting. Have tried to reflash back to GB and still the same issue.
Click to expand...
Click to collapse
That was weird never happened before with me as i have been using carbon rom almost 3months now.. And when you falshed back to a gb rom have performed a factory reset in recovery? If not then do it first
Sent from my GT-N7000 using Tapatalk 2
zai89 said:
try use another battery...
Click to expand...
Click to collapse
Thanks - tried a different Battery - same problem
abhinav quietly brilliant said:
Flash a new fresh 4.1.2 rom thorugh pc odin after doing all necessary wipes
Sent from my GT-N7000 using Tapatalk 2
Click to expand...
Click to collapse
Thanks Abinav
Will try in the morning. Do I need a new Kernel first?
Warnoceros
No let it be the stock after first flash
Sent from my GT-N7000 using Tapatalk 2
abhinav quietly brilliant said:
No let it be the stock after first flash
Sent from my GT-N7000 using Tapatalk 2
Click to expand...
Click to collapse
Okay, so reflashed and the phone booted fine but i'm still getting this intermittent 'power button causing crash' fault. Tried a couple of different Roms and am still getting the same problem.
Could it be a hardware problem?
Thanks
Warnoceros
Yeah it seems to be a hardware issue.. Wait for someone else more experienced then me to see this thread maybe he/she can suugest you a way to get out of this problem.. If you have warranty then do claim it before it's too late
Sent from my GT-N7000 using Tapatalk 2
the battery might be failing and have caused something that messed up the filesystem; try installing another battery and reflash any rom with wipes etc and see if it boots up
What kernel do you use exactly?..philz or speedmod?...
If you on philz or speedmod kernel I suggest you make a clean install,
Reboot recovery full wipe..
Reboot to download mode,
Flash stock GB or JB..
If you flash JB, download philz kernel.zip and flash through stock recovery...
Sent from my GT-N7000 using Tapatalk HD
Stuck on Splash Screen. No recovery. Odin not able to flash roms.
zai89 said:
What kernel do you use exactly?..philz or speedmod?...
If you on philz or speedmod kernel I suggest you make a clean install,
Reboot recovery full wipe..
Reboot to download mode,
Flash stock GB or JB..
If you flash JB, download philz kernel.zip and flash through stock recovery...
Sent from my GT-N7000 using Tapatalk HD
Click to expand...
Click to collapse
Hi
My stock JB official unrooted rom suddenly went to a bootloop. I looked up online for solutions and flashed an official JB ROM for my phone and Odin failed to flash it. I tried Philz recovery but Odin failed to flash it. I got a yellow triangle which I was able to removie through Odin. Currently my phone is stuck on the splash screen. Recovery doesn't work. Odin fails when I try to reflash with a md5.tar file. Please experts help me with my problem. would really appreciate it.
Thanks in advance.
fahad.anwar.xda said:
Hi
My stock JB official unrooted rom suddenly went to a bootloop. I looked up online for solutions and flashed an official JB ROM for my phone and Odin failed to flash it. I tried Philz recovery but Odin failed to flash it. I got a yellow triangle which I was able to removie through Odin. Currently my phone is stuck on the splash screen. Recovery doesn't work. Odin fails when I try to reflash with a md5.tar file. Please experts help me with my problem. would really appreciate it.
Thanks in advance.
Click to expand...
Click to collapse
you usually get stuck in a boot loop when you forget to wipe dalvik cache and factory reset the phone before installing a custom rom
Be patient...
makyubex said:
you usually get stuck in a boot loop when you forget to wipe dalvik cache and factory reset the phone before installing a custom rom
Click to expand...
Click to collapse
Just Got philz kernal for your device ..(i know you have done it but just do it again)...
go to samfirmware and download your firmware...and flash through odin...
Dr.Ketan thread is always available for u...
---------- Post added at 05:25 AM ---------- Previous post was at 05:19 AM ----------
makyubex said:
you usually get stuck in a boot loop when you forget to wipe dalvik cache and factory reset the phone before installing a custom rom
Click to expand...
Click to collapse
If you want the indian ROM and recovery and unable to install from the Hotfile just download these links serial wise...
1. https://drive.google.com/file/d/0B9lXWJxj84B6Z2pkQ3RhV0lIbEU/edit?usp=sharing
2. https://drive.google.com/file/d/0B9lXWJxj84B6dGVpWDZXemNZckU/edit?usp=sharing
3. https://drive.google.com/file/d/0B9lXWJxj84B6dzRZYWU3aVV0MDg/edit?usp=sharing
Try the following please, you must have Android SDK installed beforehand:
http://forum.xda-developers.com/showthread.php?t=2165870
Instead of using the "-n" argument, I used "-y" and "-f" to force checking the partitions and to automatically answer yes to all questions.
Hello knowledgeable people!
I did a very stupid thing!... I took an official Samsung ROM package .tar.md5, remove the .md5 extension, extracted it, replaced boot.img with a custom kernel boot.img and re-compressed into a .tar package.
Then I took this .tar package and flashed it on the phone with Odin on my PC.
That didn't work, as expected.
The process blocked at one point.
I thought I will then just have to flash the Samsung official ROM to get everything back.
Well... not! I can flash the Samsung official ROM with Odin on my PC, but when the phone starts, it get stucked on bootloop on the glowing samsung logo.
I tried many things, including:
* wipe cache
* wipe data
but nothing worked...
At this point, I think I need to repartition/format everything and start from scratch but I don't know how to do this...
I tried to flash the Partition Identification Table kindly uploaded by @lyriquidperfection, but it didn't work (see here: http://forum.xda-developers.com/showthread.php?t=1950591) and it gets stuck in Odin as @narcarsiss mentions here: http://forum.xda-developers.com/showpost.php?p=33145970&postcount=2
Anyone has an idea?
> How to re-partition/re-format properly?
> Any other method to solve the bootloop?
Thanks for your help!
Why not to flash stock Sammy rom through Odin? This time - not modified?
Flash stock Sammy latest ROM .
Wipe everything in recovery and it should work.
I always have to wipe **** when installing official Sammy ROM.
Else it will stay at Samsung screen with flashing letters
Sent from my GT-I9305 using xda app-developers app
Hbohd said:
Why not to flash stock Sammy rom through Odin? This time - not modified?
Click to expand...
Click to collapse
This is what I tried... but it still get stuck at glowing samsung logo...
toeterbaas said:
Flash stock Sammy latest ROM .
Wipe everything in recovery and it should work.
I always have to wipe **** when installing official Sammy ROM.
Else it will stay at Samsung screen with flashing letters
Sent from my GT-I9305 using xda app-developers app
Click to expand...
Click to collapse
Thanks for the answer.
What do you mean "wipe ****"?
Could you detail the steps?
1. Flash official sammy ROM through odin
2... enter recovery? (please confirm)
3... wipe what?
Thanks!
Have you tried flashing another kernel?Boeffla Etc then use KIES or Odin to flash back to stock
Sent from my GT-I9305 using xda app-developers app
Yes enter recovery after flashing with Odin.
When u power on hold volume up home key and power all at the same time release them when u see Samsung gt i9305 then wipe cach and wipe the other one. There are 2 wipe options.
Your phone should boot now it takes some time the first time around a minute.
Let me know if it worked
- flash stock Samsung ROM for your country with Odin
- go to recovery wipe the 2 options When u power on hold volume up home key and power all at the same time release them when u see Samsung gt i9305
-phone should boot takes a minute before he goes trough the flashing Samsung screen.
Sent from my GT-I9305 using xda app-developers app
---------- Post added at 09:51 AM ---------- Previous post was at 09:47 AM ----------
All you have to do is follow my steps.
It should work now
Sent from my GT-I9305 using xda app-developers app
Looki75 said:
Hello knowledgeable people!
I did a very stupid thing!... I took an official Samsung ROM package .tar.md5, remove the .md5 extension, extracted it, replaced boot.img with a custom kernel boot.img and re-compressed into a .tar package.
Then I took this .tar package and flashed it on the phone with Odin on my PC.
That didn't work, as expected.
The process blocked at one point.
I thought I will then just have to flash the Samsung official ROM to get everything back.
Well... not! I can flash the Samsung official ROM with Odin on my PC, but when the phone starts, it get stucked on bootloop on the glowing samsung logo.
I tried many things, including:
* wipe cache
* wipe data
but nothing worked...
At this point, I think I need to repartition/format everything and start from scratch but I don't know how to do this...
I tried to flash the Partition Identification Table kindly uploaded by @lyriquidperfection, but it didn't work (see here: http://forum.xda-developers.com/showthread.php?t=1950591) and it gets stuck in Odin as @narcarsiss mentions here: http://forum.xda-developers.com/showpost.php?p=33145970&postcount=2
Anyone has an idea?
> How to re-partition/re-format properly?
> Any other method to solve the bootloop?
Thanks for your help!
Click to expand...
Click to collapse
Tnx for the mention, but i heade bad news. I had to send my phone away to fix the issue.
This was a long time ago that this happened and better methods may of been discovered. Good luck:good:
narcarsiss said:
Tnx for the mention, but i heade bad news. I had to send my phone away to fix the issue.
This was a long time ago that this happened and better methods may of been discovered. Good luck:good:
Click to expand...
Click to collapse
Thanks for your answer!
I fear sending S3 to Samsung for repair is the only way, unfortunately... This is what I will do tomorrow (in 10hrs from now) unless a white knight arrives on this thread and gives me the golden solution!
You havent mentioned what rom version you tried.
I guess you used 4.3 official?
I could only guess but ther is probably more then just boot.img containing Knox code.
Knox is hindering users from downgrading bootloader and that maight be your problem now.
You did not mention wich version you try to recover to either.
So if you try with the old 4.1.2 it may be impossible.
Perhaps you need the newest official rom to get it working.
Sent from my GT-I9305 using XDA Premium 4 mobile app
tissot said:
You havent mentioned what rom version you tried.
I guess you used 4.3 official?
I could only guess but ther is probably more then just boot.img containing Knox code.
Knox is hindering users from downgrading bootloader and that maight be your problem now.
You did not mention wich version you try to recover to either.
So if you try with the old 4.1.2 it may be impossible.
Perhaps you need the newest official rom to get it working.
Sent from my GT-I9305 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Thanks for your answer.
The home made package was on 4.3 base.
Then I tried to reflash official 4.3.
I will give a try with 4.1.2...
Well... didn't work either... since I already had knox bootloader...
It shows "unsupported version".
Oh well...
tissot said:
You havent mentioned what rom version you tried.
I guess you used 4.3 official?
I could only guess but ther is probably more then just boot.img containing Knox code.
Knox is hindering users from downgrading bootloader and that maight be your problem now.
You did not mention wich version you try to recover to either.
So if you try with the old 4.1.2 it may be impossible.
Perhaps you need the newest official rom to get it working.
Sent from my GT-I9305 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
You can't flash the old version. Odin will revert it back while installing.
Sent from my GT-I9305 using xda app-developers app
Looki75 said:
Thanks for your answer.
The home made package was on 4.3 base.
Then I tried to reflash official 4.3.
I will give a try with 4.1.2...
Click to expand...
Click to collapse
Okey
A bit far feched but is it possible your download is broken? Try DL again.
And either it is or not you could try installing 4.3 from different region as yours. Just to try every possability.
It shouldnt be impossible to fix this stupid phone
You dont have any nandroid backup some where.
Last option. Throw it on a brick wall to release som aggrevation and then you buy a Nexus 5. Problem solved.
Sent from my GT-I9305 using XDA Premium 4 mobile app
tissot said:
Okey
A bit far feched but is it possible your download is broken? Try DL again.
And either it is or not you could try installing 4.3 from different region as yours. Just to try every possability.
It shouldnt be impossible to fix this stupid phone
You dont have any nandroid backup some where.
Last option. Throw it on a brick wall to release som aggrevation and then you buy a Nexus 5. Problem solved.
Sent from my GT-I9305 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
You made me laugh!
Seriously: DL is OK (I flashed this very official ROM many times in the past) and I do have a nandroid, but result is the same (stuck at glowing samsung logo).
The issue is way deeper.
Thanks for your help! Before trying the brick wall, I will try to make it repaired by Samsung!
Looki75 said:
You made me laugh!
Seriously: DL is OK (I flashed this very official ROM many times in the past) and I do have a nandroid, but result is the same (stuck at glowing samsung logo).
The issue is way deeper.
Thanks for your help! Before trying the brick wall, I will try to make it repaired by Samsung!
Click to expand...
Click to collapse
I had a brick once, butthe situation was a bit different. I have knox bootloader and tried to downgrade to a 4.1.2 rom without the bootloader package. The flash went ok, but my phone was stucked on Samsung Galaxy S3 GT-I9305 screen. After that, i was quite desperate and tried to reflash stock 4.3 via odin, but it failed :S
Then i tried to flash official Germany's 4.3 again, this time with the ODIN version inside CF-Root package (http://download.chainfire.eu/232/CF-Root1/CF-Auto-Root-m3-m3zh-gti9305.zip?retrieve_file=1), put the cable in another USB port, killed every kies proccess and rebooted phone in dowwnload mode. This time the flash went ok, i rebooted the phone into recovery (got bootloop) and wipe cache and factory reset. After this the phone booted up normally. Hope you can fix your phone
shucrut said:
I had a brick once, butthe situation was a bit different. I have knox bootloader and tried to downgrade to a 4.1.2 rom without the bootloader package. The flash went ok, but my phone was stucked on Samsung Galaxy S3 GT-I9305 screen. After that, i was quite desperate and tried to reflash stock 4.3 via odin, but it failed :S
Then i tried to flash official Germany's 4.3 again, this time with the ODIN version inside CF-Root package (http://download.chainfire.eu/232/CF-Root1/CF-Auto-Root-m3-m3zh-gti9305.zip?retrieve_file=1), put the cable in another USB port, killed every kies proccess and rebooted phone in dowwnload mode. This time the flash went ok, i rebooted the phone into recovery (got bootloop) and wipe cache and factory reset. After this the phone booted up normally. Hope you can fix your phone
Click to expand...
Click to collapse
Thanks! Any idea is valuable!
How did you create the ball pack of "4.1.2 rom without the bootloader" - in other words: how did you remove the bootloader from there?
Looki75 said:
Thanks! Any idea is valuable!
How did you create the ball pack of "4.1.2 rom without the bootloader" - in other words: how did you remove the bootloader from there?
Click to expand...
Click to collapse
I'd used this tutotial (just the part of commands, added everything that the original ".md5" has, removing just the "sboot.img", i'm not 100% sure if this is the only file to be off the new package, as i said, didnt work for me ), the only difference is that i'm using cygwin instead of linux itself, it worked like a charm
Basically all u need to do is unpack a original .md5 firmware (use winrar or so) and move the files (except sboot.img) to your home directory of linux or, in my case, cygwin (originally C:\cygwin\home\user-name), start the console and type the command bellow, switching the ".imgs" to match yours, of course:
Code:
cd $HOME
tar -H ustar -c image_1 image_2 > your_odin_package.tar
After this you must have a 1Gb+ .tar file (considering you will make a stock samsung flashable), now you will add md5 checksum to that, just to avoid troubles:
Code:
md5sum -t your_odin_package.tar >> your_odin_package.tar
mv your_odin_package.tar your_odin_package.tar.md5
and voilà, you have your flashable odin package. Of course you can try making one with just the system.img, boot.img and modem.img. If the phone boots up, do a factory reset. I have no idea if this will work in any occasion having knox bootloader trying to flash official 4.1.x, but you can also try with a samsung 4.3 rom.
In the last scenario, try to CF auto-root your phone, then flash an official CWM recovery via odin using this method i told u, boot into recovery and flash a custom rom, do a factory reset and wiping cache and dalvik cache. I hope one of the options work for you.
I'd recommend trying to flash a custom recovery and then a custom rom. If phone boots up and is functional, try to flash samsung official 4.3 again (if your desire is having the stock of course), not forgeting to factory reset via cwm first to avoid troubles.
Been in maybe like pratically the same situation
1st flash philz touch recovery ( install latest version)
2nd backup ur efs in external sd and copy it to a pc just in case (important if u mess up imei )
3rd Copy and rom in the external sd
4th Wipe data,cache,dilvik
5th In mount and storage Format everything except external sd ( u can backup ur internal sd card with 3rd step)
6th Flash Rom and reboot
7th If no imei then try a newer modem
http://forum.xda-developers.com/showthread.php?t=2572432
http://forum.xda-developers.com/showthread.php?t=2607279
Notice I only could get to run 4.3 to run after formating everything through philz touch recovery