Hi, my girlfriend's Galaxy S2 fell to the floor and the screen is now broken and is completely black, replacing the screen cost almost as much as buying another used S2, so i want to use it connected to my TV via MHL.
The problem is the phone was using Cyanogenmod, so MHL was not working. I flashed latest stock firmware from samfirmware (MS3 i think), hoping the process to be simple, but although the flash process works fine, the phone can't completely boot, it gets stuck somewhere, so i think i might need to wipe user data / factory reset, the problem is: how? if i'm blindly pressing buttons.
Is there any way of wiping data with odin?
Do you guys have any idea that can help me?
Best regards!
You can wipe the phone by flashing the 3 part stock firmware linked in Hopper8's 'Odin troubleshooting' guide stickied in General.
As to the rest, no idea. I personally wouldn't bother with a phone in that state (I realise other people would, and that's fine, just stating what I'd do) I wasn't prepared to fix properly (I.E replace the screen).
MistahBungle said:
You can wipe the phone by flashing the 3 part stock firmware linked in Hopper8's 'Odin troubleshooting' guide stickied in General.
As to the rest, no idea. I personally wouldn't bother with a phone in that state (I realise other people would, and that's fine, just stating what I'd do) I wasn't prepared to fix properly (I.E replace the screen).
Click to expand...
Click to collapse
Thanks for the tip, i'm downloading the ROM right now.
The phone is definitely in a bootloop, i used AndroidScreenCast and i can see the Samsung logo, then goes to black and then again the Samsung logo, i'm hopeful this ROM will solve the problem. :fingers-crossed:
Edit:
It worked!!!
Now the ROM boots completely, i can hear the sound of the menu and back buttons, but i'm not at home right now so i can't try MHL. And AndroidScreenCaster won't work because i don't have USB debugging enabled. I will report later. Thank you very much for your help.
Good news Yep, keep posting here if you have further problems & someone will help.
Well, i have another problem now, i can't root the ROM because in recovery i have no MHL and AndroidScreenCaster won't work. I installed PhilZ kernel for XXLSJ with the help of Odin, but it doesn't root the phone, i think i need to flash SuperSu in recovery
I need root so i can install some remote control app like VNC Server, that would make everything so much easy.
Any idea about getting root via Odin or something like SuperOneClick? (i can't find information about this one, don't know if it works for i9100 on JB).
Thanks in advance.
1000bech said:
Well, i have another problem now, i can't root the ROM because in recovery i have no MHL and AndroidScreenCaster won't work. I installed PhilZ kernel for XXLSJ with the help of Odin, but it doesn't root the phone, i think i need to flash SuperSu in recovery
I need root so i can install some remote control app like VNC Server, that would make everything so much easy.
Any idea about getting root via Odin or something like SuperOneClick? (i can't find information about this one, don't know if it works for i9100 on JB).
Thanks in advance.
Click to expand...
Click to collapse
Seems like you will have to go blindly for a cwm flash to install the su binary, otherwise if you can find a firmware which is vulnerable to the Exynos Exploit, you can use Exynos Abuse by Chainfire to root the phone.
Sent from my GT-I9100 using Tapatalk
king_below_my_lord said:
Seems like you will have to go blindly for a cwm flash to install the su binary, otherwise if you can find a firmware which is vulnerable to the Exynos Exploit, you can use Exynos Abuse by Chainfire to root the phone.
Sent from my GT-I9100 using Tapatalk
Click to expand...
Click to collapse
It was a lot easier :victory:
I decompressed SuperSu zip, and took a look at the updater-script, the phone was in recovery mode, with root privileges in ADB, thanks to PhilZ kernel.
I followed line by line the script, executing the commands with ADB and after a reboot, my phone was rooted, just had to use "input tap X Y" in ADB to confirm the root access for apps. Now the fun starts
Thanks for your help.
Related
Hi I rooted my galaxy s2 and then unrooted it as I did'nt know what to do with it as overclockig and changing cpu frequencies did'nt seem to do anything. I read on your forum bit, that samsung can tell if you have rooted the device or not, how do I avoid that.
When I rooted I downloaded the original Kernal and the yellow triangle went away. Then I unrooted via superoneclick.
Then when I went on to samsung kies the firmware was'nt there, so I did a factory reset and now it is back and is up to date the firmware version is there now.
I'm guessing I should've back my phone up before hand but how and should I have done things the way I did?
My appologies for the war and peace but I am nooob and really want to learn.
What I have learned is off youtube and I could'nt get all the info I wanted, like where to download a safe superone click root.
In the video they used cwm I think but where do you get this and what does this do?
Any help you guys can give me please inbox me so I can learn a bit more.
Thanks guys and girls and all the best for the year ahead.
Kind regards Iamaspecialneedscase.
Iamaspecialneedscase said:
Hi I rooted my galaxy s2 and then unrooted it as I did'nt know what to do with it as overclockig and changing cpu frequencies did'nt seem to do anything. I read on your forum bit, that samsung can tell if you have rooted the device or not, how do I avoid that.
By not flashing or by using the>> SEARCH will find it >> USB Recovery Jig .
When I rooted I downloaded the original Kernal and the yellow triangle went away.
Then I unrooted via superoneclick.
Then when I went on to samsung kies the firmware was'nt there, so I did a factory reset and now it is back and is up to date the firmware version is there now.
I'm guessing I should've back my phone up before hand but how and should I have done things the way I did?
You have gone down a different route firmware wise is KIES official firmware once you change part or modify kernel part you may not get KIES upgrades .
download a safe superone click root.Thats a very old method .
In the video they used cwm I think but where do you get this and what does this do?
Any help you guys can give me please inbox me so I can learn a bit more.
Thanks guys and girls and all the best for the year ahead.
You need to start at the beginning and read and learn its not really hard .
start with the basics and take your time .
NEW HERE
http://forum.xda-developers.com/showthread.php?t=1134290
Guide
http://forum.xda-developers.com/showthread.php?t=1125282
Method of rooting and installs CWM recovery
Root + CWM .
http://forum.xda-developers.com/showthread.php?t=1103399
>>>>>>>>>>>>>
roughly
The process would be root and install CWM choose a custom rom and flash through CWM then backup via CWM .
jje
Click to expand...
Click to collapse
Where do I get cwm please
Sent from my GT-I9100 using XDA App
Well guys and girls, I am even more confused now! What is cwm and where do I get it?
If super one click is outdated then what do I use?
I have read quite a few forums but I'm lost, please somebody help!!!!!
Sent from my GT-I9100 using XDA App
I wasn't going to this question because 30 seconds of Googling would give you every answer you want and more but hey, it's new years, and I'm in a festive spirit.
So your question, first, "what is CWM?". CWM (Clockwork mod) is replacement for the standard Samsung recovery suite which allows you, in addition to the standard functions, to restore data, backup data, flash new zips and a wealth of other great stuff. Basically its your best friend when flashing new ROMS, Kernels, etc.
If you want to do anything above and beyond the bog standard tweaking with your phone (basically everything you find here on XDA) you will need to use CWM. It comes with any and every rooted Kernel you flash. Every Kernel which has root will have CWM. So if you had rooted your phone by installing a custom Kernel you would have it. (side note, you get to recovery by holding volume up + home button + power button for a few seconds).
Now down to how to get CWM and to super one click. If you made a timeline of XDA and rooting, super one click would be at the very very start. Its the dinosaur of rooting. I recommend strongly against using it, to be honest I didnt even know you could still use it. Anyway, the best way to root your phone is by flashing a rooted Kernel. I will presume your phone is now unrooted and you are running stock Kernel + stock ROM. You want to download Odin (http://www.mediafire.com/?a54dbk53vhpkjto) and then flash a corresponding rooted Kernel to your ROM (I recommend CF-Root by Chainfire). I'm not going to tell you how to flash stuff with Odin because there are millions of guides out there, just don't tick re-partitioning. What I mean by corresponding is it build of the Kernel should relate to your ROM. If you are running a XWKK5 ROM for example, you would flash a XWKK5 Kernel. It's pretty clear in Chainfire's CF Root thread what the builds of all the Kernels are.
Anyway I hope that helps you, and I hope you're grateful I've just taken 5 minutes to explain to you things that you could have found guides on written by people much more experienced than myself in 2 minutes of googling.
I thanked you because its New Year! (@postfatal)
Good luck with the rooting and make sure you use the search functions of these forums, a wealth of information is to be had and the stickies are well worth a look!!!
BTW rooting will void your warranty.
Thank you postfatal. I have done some googleing and have read up un quite a bit of stuff, but still getting boggled by all the info.
Maybe I will just give this up as abad job.
Thank you and happy new year.
Sent from my GT-I9100 using XDA App
Iamaspecialneedscase said:
Thank you postfatal. I have done some googleing and have read up un quite a bit of stuff, but still getting boggled by all the info.
Maybe I will just give this up as abad job.
Thank you and happy new year.
Sent from my GT-I9100 using XDA App
Click to expand...
Click to collapse
Hi,
Belive me, i was just like you for 3-4 days ago, and by now i almost can everything that's needed to be known about rooting. Almost everyone here make it sound so hard to rooting, that's because they can't eplain things in "noob languages".
If you still don't know how to do this, PM me back and i will help you.
thanks
Actually, Chainfire's CFRoot instructions couldn't be simpler. There's only 10 steps (7 that actually require you to do something)
I don't see what's difficult about:-
*checking your current kernel
*finding the corresponding CFRoot kernel
*downloading same (and downloading Odin if necessary)
*unzipping the tar
*firing up Odin
*putting your phone in download mode (volume down/home button/power button)
*plugging one end of a USB cable into the USB port on your PC/the other into the USB port of your phone
*clicking on PDA in Odin & navigating to where you saved the CFRoot kernel tar file
*clicking "start"
*waiting until the process completes/Odin saying "OK" then unplug the USB cable/wait for your phone to reboot
Or am I missing something ?
Darwichee said:
Hi, Almost everyone here make it sound so hard to rooting, that's because they can't explain things in "noob languages".
thanks
Click to expand...
Click to collapse
[ROOT/UNROOT/Custom Recoveries/Kernels/Roms] AT&T Galaxy Note ONLY!/ No Flash Counter
THIS IS A GINGERBREAD ROOTING METHOD, FOR WHEN YOU FIRST GET THE PHONE OUT OF THE BOX, THIS WILL NOT WORK WITH NEW OFFICIAL ICS.
This method is for people that have a AT&TGalaxy Note only and want to have root in the stock rom without tripping the flash counter only, For everything else look at the bottom of the first post!!
If you want root to flash a custom rom/kernel/CWM and you don't care about the flash counter and the warranty then this is not for you.
Go here for other root! http://forum.xda-developers.com/showthread.php?t=1504218
Now I went ahead and put the files together in one zip to make it simpler, it contains the root zip, the odin and the samsung usb drivers, all the files needed in one download .
DOWNLOAD: Big File: 532mb in size
http://goo.gl/aq2Wl
After the download follow this steps made by capite.
Extract Odin but don't launch it, run the samsung drivers for your phone on the PC and install it. Then plug in your phone to make sure it works -- it seems to take a while to get everything working. If you get an error, try rebooting and try again. Also, try using the cable that came with your phone -- 3d party cables don't always seem to work. If it still doesn't work, try another USB port.
1. Turn off your phone and uplug it. Take the battery out of your phone, put it back in, and hold the volume down button and power button at the same time. Keep them held down until the phone starts buzzing and you see the Samsung name.
2. At this point you are either in download mode or the phone will tell you to hit volume up, at which point you'll be ready.
3. Run Odin on your PC -- right click and choose "Run as Administrator" just to be safe.
4. Plug your phone into your PC.
5. In the Odin screen, wait until one of the top boxes turns yellow and displays some numbers.
6. UNCHECK all the boxes except for Auto Reboot.
7. Hit the PDA button and navigate to mashi's file that you unzipped.
8. Hit start
9. wait until your phone reboots.
10. If it didn't work, try rebooting and starting from scratch.
11. verify super user app now present. Update super user app (optional).
If you want to go back to unrooted, download this .tar file and flash thru odin! http://goo.gl/BBdow
Thanks to Da_G !
Flashing back to stock thru odin by using the stock tar in case of brick will increase the flash counter.
Enjoy and hit the thanks button if it helps you.
UPDATE: Custom Recoveries/Kernels/Roms without tripping the flash counter go here.! http://forum.xda-developers.com/showpost.php?p=23229071&postcount=57
UPDATE 2: Unrooting guide for AT&T go here.! http://forum.xda-developers.com/showpost.php?p=23499670&postcount=133
Since this is a System root, will it replace my Rogers ROM with AT&T ROM? I understand Rogers ROM has more features that are disabled on AT&T (NFC, Tethering, some apps).
zaptor99 said:
Since this is a System root, will it replace my Rogers ROM with AT&T ROM? I understand Rogers ROM has more features that are disabled on AT&T (NFC, Tethering, some apps).
Click to expand...
Click to collapse
This will change the Rom and give issues to any other Rom besides stock AT&T rom when making root permissions.
Sorry but I edited this post to inform the people that only scroll thru the first page only!
i used Da_G root
roloracer said:
So I'm making this thread because the one made by mashi has a dead link and it says it will increase the flash counter when it doesn't.
So thanks to mashi and thanks to capite for his instructions, I'm just doing a clean thread to avoid the multiple question threads in the Q&A about anybody having root without the flash counter going up.
anyone that finds this steps by capite helpful , please hit his thanks button.
http://forum.xda-developers.com/showpost.php?p=22920576&postcount=87
If the moderators find this thread unecessary you can delete it, just trying to help keep things organized.
Click to expand...
Click to collapse
to root my note, can you tell me if i use this if this will reverse the Counter.
zozodouce said:
to root my note, can you tell me if i use this if this will reverse the Counter.
Click to expand...
Click to collapse
no nothing will reverse your counter yet, this will not increase it, sorry.
roloracer said:
not to my knowledge, this shouldn't change anything but the root permissions, I didn't have to do anything after, not even a factory reset. this has the system.img.ext4 in it, I'm sorry but I don't know if it would change anything in your rom besides root permissions, I didn't create this file, just helping to provide it. .
Click to expand...
Click to collapse
i believe this method replaces the entire system partition so he will lose stuff like nfc. once cwm is working fully I'm sure someone will create a flashable zip that just adds root without replacing the whole partition.
EvoXOhio said:
i believe this method replaces the entire system partition so he will lose stuff like nfc. once cwm is working fully I'm sure someone will create a flashable zip that just adds root without replacing the whole partition.
Click to expand...
Click to collapse
Not sure how it's done, but the entire stock rom including nfc service 2.3.6 is still intact. There is nothing missing or unusable from the original LA1 rom. Also since there is no hard reset, user data isn't affected. Again, we need mashi or someone far smarter than me to tell us exactly how this works. All I know is that it does.
Sent via Tapatalk on my Samsung Galaxy Note™ SGH-I717
so I guess if you want cwm to work, you'll have to use Da_G's Kernel Root?
ukic said:
so I guess if you want cwm to work, you'll have to use Da_G's Kernel Root?
Click to expand...
Click to collapse
Why, you flash cwm thru Odin and cwm increases the flash counter so this method would be pointless if you're not worried about your flash counter, if you don't care about the flash counter then use DA_G method of rooting/overclock kernel, this method is just for the people that are concern about the flash counter and want to get root.
Sent from my awesome Galaxy Note!
Oh, cwm itself increases it....
ukic said:
Oh, cwm itself increases it....
Click to expand...
Click to collapse
Yes you're replacing the stock recovery with a custom recovery, even when is available thru Rom manager as an official version of cwm, is still considered a custom recovery. Even the stock modified replacement recovery in here it will come up as custom when you flash it and will trip the flash counter if Im correct.
Sent from my awesome Galaxy Note!
I assume this is doable via heimdall, correct? It looks like it's just a system image, which can be flashed with Heimdall.
Edit: Heimdall doesn't work on the Galaxy Note. Sad day.
When I follow the directions to root my device my entire computer freezes once I press start. This is happening when I try to root using Da_G's method or the method from this thread. All the help I can get would be greatly appreciated. Thank you
jasonblaine23 said:
When I follow the directions to root my device my entire computer freezes once I press start. This is happening when I try to root using Da_G's method or the method from this thread. All the help I can get would be greatly appreciated. Thank you
Click to expand...
Click to collapse
there must be something wrong with your pc, you're the first person that I hear is having issues with odin, make sure the drivers are properly working.
I may wait a bit before I root but if I was to use this method I or we wont have any issues flashing roms once they come available right?
Sent from my SAMSUNG-SGH-I897 using Tapatalk
nash2000 said:
I may wait a bit before I root but if I was to use this method I or we wont have any issues flashing roms once they come available right?
Sent from my SAMSUNG-SGH-I897 using Tapatalk
Click to expand...
Click to collapse
No, this is a system root to be able to have root on the stock rom and avoid tripping the flash counter, if you flash a rom I'm pretty sure you will loose this root, but if you are planning on flashing a rom and the counter is not a concern then you need the perm-root in DA_G thread.
Sent from my awesome Galaxy Note!
roloracer said:
No, this is a system root to be able to have root on the stock rom and avoid tripping the flash counter, if you flash a rom I'm pretty sure you will loose this root, but if you are planning on flashing a rom and the counter is not a concern then you need the perm-root in DA_G thread.
Sent from my awesome Galaxy Note!
Click to expand...
Click to collapse
Oh, I thought this method would allow root and flashing of roms without tripping the counter. So there is no fix for the counter? I've read posts off people asking how to remove trips etc. So in a nut shell if you are planning on flashing roms at this time there is no fix for the counter so use the other root method?
Sent from my SAMSUNG-SGH-I897 using Tapatalk
nash2000 said:
Oh, I thought this method would allow root and flashing of roms without tripping the counter. So there is no fix for the counter? I've read posts off people asking how to remove trips etc. So in a nut shell if you are planning on flashing roms at this time there is no fix for the counter so use the other root method?
Sent from my SAMSUNG-SGH-I897 using Tapatalk
Click to expand...
Click to collapse
no only this root won't, once you go flashing custom roms/kernels/recoveries it will trip the counter as of now, hopefully soon there will be a way to fix this.
roloracer said:
no only this root won't, once you go flashing custom roms/kernels/recoveries it will trip the counter as of now, hopefully soon there will be a way to fix this.
Click to expand...
Click to collapse
can u help me with my situation i am trying to flash this in oden but it just hangs there is this because of my flashing the cwm recovery , i thought that it might be so i tried to reflash the stock recovery and now that just hangs , everything shows as connected in device manager on this pc which is a clean xp ...also it boots up fine
Worked like a charm on the first go around.
Thanks rolo! +1
I was using Samsgung Galaxy SIII Toolkit v1.0 to root my (Sprint) device ( didn't realize v2.0 was out ) and at step 9 when the device was supposed to reboot on its own it just turned off and did not reboot. When I try to boot it I get a quick flash of SAMSUNG and then it turns off. I am able to boot into Download mode. USB Debugging is not enabled.
Any help is appreciated.
Thank you.
Update:
I tried downloading a few different versions of the toolkit, and they all seem to check for USB DEBUGGING before starting the rooting process. I'm not sure which version I had downloaded initially (just that it was v1.0) where it didn't... But that part of the process had a NOTE saying to turn it on, restart the phone and plug it back in to continue...
I also tried booting into recovery mode and factory resetting - no dice.
You're in the section of the international phone, not the US-version.
Most probably something went wrong with replacing the kernel, flash your RAM through Odin again and it should boot fine.
Just use CF-root (or whichever kernel applies to the US-version) through Odin instead of using these tools. People always recommend them and I'd had to revive my fair share of devices which were softbricked (that's what your device is) through their usage.
d4fseeker said:
You're in the section of the international phone, not the US-version.
Most probably something went wrong with replacing the kernel, flash your RAM through Odin again and it should boot fine.
Just use CF-root (or whichever kernel applies to the US-version) through Odin instead of using these tools. People always recommend them and I'd had to revive my fair share of devices which were softbricked (that's what your device is) through their usage.
Click to expand...
Click to collapse
This. Don't trust toolkits. Do yourself a favour and take time to learn how to use adb and on this phone, Odin, properly. It's unfortunate you had to learn why many people are against toolkits the hard way but if you follow the above advice and use Odin to flash a factory Rom for your phone all shall be well.
Sent from my GT-I9300 using Tapatalk 2
dr.m0x said:
This. Don't trust toolkits. Do yourself a favour and take time to learn how to use adb and on this phone, Odin, properly. It's unfortunate you had to learn why many people are against toolkits the hard way but if you follow the above advice and use Odin to flash a factory Rom for your phone all shall be well.
Sent from my GT-I9300 using Tapatalk 2
Click to expand...
Click to collapse
Mm.. I'm trying an Odin approach now. Initially I tried a Heimdall approach, but it kept failing. :\
Thanks for the response.
Odin and Heimdall both do the same stuff; they use the Samsung firmware update mode to push the device's firmware.
Download your ROM off samfirmware.com if you can't revive it through a simple kernel flash.
You might have to factory-reset your phone tough, hopefully not.
d4fseeker said:
Odin and Heimdall both do the same stuff; they use the Samsung firmware update mode to push the device's firmware.
Download your ROM off samfirmware.com if you can't revive it through a simple kernel flash.
You might have to factory-reset your phone tough, hopefully not.
Click to expand...
Click to collapse
I am currently writing a stock ROM to my phona via Odin. Once I'm back to stock I'll start messing around with it again. I just like touching base after I screw things up, if that makes sense.
I only bought the phone a few days ago so there's not much going on to lose, and I did do a full backup, so I'm not concerned. I already did a reset anyway when I first broke it.
I appreciate your help, and do now see that I'm in the wrong forum. In the future I'll post in the correct forum. Sorry again. Very embarrassing.
Thanks.
I just like touching base after I screw things up, if that makes sense.
Click to expand...
Click to collapse
Yep. That's how (and most other people learn their stuff. Learning by breaking (and after having gained some knowledge, fixing)
Sorry again. Very embarrassing.
Click to expand...
Click to collapse
It's more a problem for you than for us. If you were to flash a linked zip without really taking care you could hard-softbrick (only revivable through USB-Jig) or possibly hardbrick (only revivable through JTAG) your phone so it's best to stick in the correct section with the correct files =)
Hi Guys,
Sorry to bother you with this, but I'm out of ideas...
I decided to root my i9100 using this guide9.
As I was doing this, the recovery rom would reboot when using the volume buttons to navigate (only on the first "page") - This was easily worked around by using the touchscreen, but now I'm wondering if this was the start of my issues...
I applied the SU busy box installer, and got root. I installed rom manager, and noticed that it seemed to lock up when doing certain things. I put this down to CWM saying there was no official mod for the i9100.
The next day I decided to try and install a CM10.1 nightly, so I took a backup, wiped cache and data, and applied the rom and gapps.
When I rebooted, the phone wouldn't finished booting, it just sat at the initial logo screen.
After that, I tried following this recovery guide but the odin flash failed at around 80% (I retried and the same happened again).
Since then I've had difficulty getting in to recovery mode. I've tried flashing various stock roms with odin, and trying to restore with Kies.
In Kies I get as far as it conencting to the phone in download mode, but it pops up a "notice" in a foreign language - presumably Korean (and I can't copy the text to even attempt a google translation).
I tried flashing Siyah-s2-v5.0.1 to get a different recovery - that seemed to have a garbled progress bar, before hanging when I tried to wipe /data again.
When I use odin to flash a stock rom - is it supposed to restore absolutely everything? I'm not sure how I'm still getting problems if this is the case. Any ideas on what to try next?
(The current stock rom I'm try ing to use is this one)
Let me know if I'm missing any info, and thanks in advance for any help.
Using rom manager would have been the start of your problems-not the temp cwm recovery in the rooting guide.
If you can boot into download mode then I would download LP7 stock rom, disable kies and flash that with Odin.
{go back to your iphone since you are an android noob}
Thanks for the reply.
Rom manager didn't work properly for me, so I stopped using it. I used the temp cwm recovery to install the CM nightly.
I can boot in to download mode, but I've already tried an LP7 rom, - as with the others, it doesn't boot.
Any ideas on how to tell why it isn't booting? logcat doesn't seem to want to to work. Not sure if it's broken / too early in the boot process / etc
Silly Billy said:
Thanks for the reply.
Rom manager didn't work properly for me, so I stopped using it. I used the temp cwm recovery to install the CM nightly.
I can boot in to download mode, but I've already tried an LP7 rom, - as with the others, it doesn't boot.
Any ideas on how to tell why it isn't booting? logcat doesn't seem to want to to work. Not sure if it's broken / too early in the boot process / etc
Click to expand...
Click to collapse
I9100 right?
Try this:
- Download this ROM.
- Kies installed? uninstall it, re install it. Close it all up with Task manager (3 or 4 applications running).
- Flash ROM via Odin (CSC, MODEM, PHONE).
- If that doesn't fly, try another usb port & usb cable. Another PC would also be recommended.
- Repeat the process.
- Still no luck? try flashing a previous siyah version.
- No go? repeat all the above.
- Let us know how you did.
gastonw;37017081- Download this ROM.[/QUOTE said:
Thanks, I'll give it a go. (Will take a while for the file to download from hotfile...).
Are odin images for stock roms supposed to restore the stock recovery, or do they leave that alone?
Click to expand...
Click to collapse
As a matter of interest, how far did you go with Phistachios repair guide.
{go back to your iphone since you are an android noob}
Silly Billy said:
Thanks, I'll give it a go. (Will take a while for the file to download from hotfile...).
Are odin images for stock roms supposed to restore the stock recovery, or do they leave that alone?
Click to expand...
Click to collapse
Focus on getting a ROM to boot.
That ROM will install stock recovery.
gastonw said:
Let us know how you did.
Click to expand...
Click to collapse
For some reason, I can't get Odin to flash that rom - it just hands for a while at the start of data.img, before saying "Complete(Write) operation failed."
There a .pit file in the archive, although the link says not to repartition (so I didn't).
Some roms seem to get written, some don't, I'm not sure why...
theunderling said:
As a matter of interest, how far did you go with Phistachios repair guide.
Click to expand...
Click to collapse
Odin failed about 80% through flashing (step 4, after taking the ICS steps). I tried flashing the kernel afterwards, which flashed, but didn't help with my boot issues.
gastonw said:
Focus on getting a ROM to boot.
That ROM will install stock recovery.
Click to expand...
Click to collapse
Of course, I was just trying to get a better understanding of how things work - I'd settle for anything booting right now.
I was meaning how far did you go with his guide.He says (near the end) to flash a bootloader/kernel/rom.
You can try everything in his guide, but understand about the risks involved with pit and bootloaders.
{go back to your iphone since you are an android noob}
theunderling said:
I was meaning how far did you go with his guide.He says (near the end) to flash a bootloader/kernel/rom.
You can try everything in his guide, but understand about the risks involved with pit and bootloaders.
{go back to your iphone since you are an android noob}
Click to expand...
Click to collapse
He's right.
Keep trying, consider pit files & bootloaders as a last resort.
Tried everything?
Used another usb cable for the flash? tried in another PC? tried in a laptop?
Are you sure kies is all shut down?
I've read about so many people having the same issue than you, they keep on flashing as in trial & error and most times they come out winners.
GL!
gastonw said:
He's right.
Keep trying, consider pit files & bootloaders as a last resort.
Tried everything?
Used another usb cable for the flash? tried in another PC? tried in a laptop?
Are you sure kies is all shut down?
I've read about so many people having the same issue than you, they keep on flashing as in trial & error and most times they come out winners.
GL!
Click to expand...
Click to collapse
I guess I'll keep at it then.
I'd tried another cable with kies shut down. Just tried a different machine, and flashed the ROM you suggested with heimdall. It flashed without complaining (unlike odin), but I'm still getting a boot loop.
Looking at the initial recovery guide I was following - I suspect that I might've flashed the bootloader (the guide shows in bold which file goes in which box, so I probably loaded them all). Maybe this is the source of my troubles...
I also noticed that heimdall can pull data from the phone too - if I can pull and mount these, am I likely to find any useful log files?
For completeness (and anyone else who finds themselves with the same issue): It seems I hit the EMMC brick bug, which rendered some of my EMMC storage unusable.
This helpful chap came up with a workaround to partition around the dead space. (Please read the post carefully and make sure this really is your problem before flashing!)
That method will let you know what part of your memory is corrupted. It's done via recovery as far as I remember.
Did you bring your device back to life?
Sent from the little guy
gastonw said:
That method will let you know what part of your memory is corrupted. It's done via recovery as far as I remember.
Did you bring your device back to life?
Click to expand...
Click to collapse
Yes, that's right. IIRC, I flashed a working recovery with Odin, then did most of the work from adb shell.
I got my device back to life for the most part. I get the occasional hang but haven't investigated much (have since bought a Nexus 4, so not using the S2 so much).
Just thought I'd share for the next poor soul who has the same problem
Hi I tried to root my phone using this method ( http://forum.xda-developers.com/showthread.php?t=1504218 ) and it left my phone stuck on the reboot. I then tried to flash the stock kernel via odin, and when that didn't work I flashed cwm via odin and then a rogers kernel through cwm and it is still stuck on the rogers logo.......?
could someone help me......?
AirForce 1 said:
Hi I tried to root my phone using this method ( http://forum.xda-developers.com/showthread.php?t=1504218 ) and it left my phone stuck on the reboot. I then tried to flash the stock kernel via odin, and when that didn't work I flashed cwm via odin and then a rogers kernel through cwm and it is still stuck on the rogers logo.......?
could someone help me......?
Click to expand...
Click to collapse
I see your post count and realize you cannot post in the development section yet. that should not however stop you from reading. maybe you have but you may not have read the whole thread. i know that may seem like a daunting task, it is for me. so what I o is go to the most recent post or last page and start reading backwards. that way I get the most up to date information even on an older thread as you are referring to.
if you did that you would have seen a post from AGOATTAMER.
http://rootgalaxynote.com/galaxy-note-i717-roms/how-to-root-att-galaxy-note-sgh-i717-icsgingerbreadeasiest-method/
this is also the method I used. believe me, if I can pull it off, anybody can.
more tips..............
make sure you have all the files you need
rehearse the process
I know it sounds crazy, but these phones aint cheap and if you mess it up, can be pretty screwed.
so what is more valuable???? your phone or acting crazy and talking to yourself for a few minutes.
if you can still get download mode, your good, no brick
good luck
You flashed an older incompatible kernel with a newer ROM, but I guess you know that now. Flash the stock ROM found here using odin.
http://www.hotfile.com/dl/213010140/75bf7e2/I717RUXMD1_I717RRWCMD1_RWC.zip.html
Go into recovery after install and do a factory reset. Then start over. Many have used the link that captemo has mentioned. There are newer versions of recovery than the one listed on that site but it will get you rooted. Look at this thread also. Since you are installing the stock ROM via odin you will not have to deal with the script mentioned here.
http://forum.xda-developers.com/showthread.php?t=2485336
Just flash twrp with Odin, don't reboot into android, not directly into recovery after the flash finishes...
In recovery wipe data/factory reset.
When you go to boot it'll see you're not rooted and ask if you want to.
The easiest method to root.
Edit: note to self
Self,
check links before posting to avoid repeating yourself
studacris said:
Edit: note to self
Self,
check links before posting to avoid repeating yourself
Click to expand...
Click to collapse
Good advice is always worth repeating.
Sent from my Big Ass Outlaw Phone.