*MOVED FROM GENERAL BOARD*
Yes I'm a n00b, yes I've researched both this forum and the wider net.
I have just taken delivery of a brand new n7100 as a warranty replacement. My previous n7100 was rooted with CWM (can't remember the version, sorry). That phone was rooted using the simple method described at galaxynote2root.com and I had no issues either rooting or flashing several different ROMS.
My new phone is a very different story, I've tried several different versions of ODIN and various rooting methods. The closest I've come to a success (as reported by ODIN) actually caused the phone to reboot after flashing but instead of booting back to the script (on the phone) as I would expect, it just booted back to the regular Samsung splash screen, but distorted and then froze. I was able to reboot normally but whenever I attempted to enter CWM the same distortion/freeze would happen.
So, to recap; I was able to flash successfully (according to ODIN) and when the phone booted I had supers in the app drawer. I was NOT able to enter CWM at boot. I was able to flash the stock recovery and that is how the phone is configured at the moment.
I'm anxious about choosing the wrong root now I've had this problem as I fear I'll brick the phone.
I'm addition to the concern, I've also read that CWM can cause "sudden death"...which is something is really rather avoid...I don't want my new phone to suddenly due! However, I did really enjoy using CWM to switch ROMs on-the-fly before and, as that's what I'm familiar with I'd like to continue using that method if possible.
Can anyone suggest/recommend a method of rooting which might work for me?
Never mind, solved.
Related
I am planning on rooting my friend's stock i317 running the MC3 stock firmware. He recently got a carrier replacement i317 due to a hardware issue but I had also previously rooted his other i317 and installed a CM10.2 nightly ROM. Upon using the same method of rooting his first phone on the new one, I ended up soft bricking his second phone. I basically used ODIN to flash a few different recoveries but when I would boot to recovery each time then the Galaxy Note II logo would start flickering for a few seconds and then the screen would go blank. I tried using ODIN to restore to JL2 and upon successfully restoring, I couldn't get past the boot animation. I told my friend to replace the phone again as I couldn't even get the phone to boot up successfully no matter what I tried doing to fix it. Maybe I had to find and ODIN the MC3 firmware to successfully boot the device so please let me know what I did wrong which prevented the device from booting successfully.
I don't know whether there was recently a major AT&T firmware update that changed the security on the device which prevented previous methods of root from working so please update me on any changes. My friend just got a new i317 today and I would like to root it successfully as the AT&T warranty center was nice enough to replace his phone but had to void his warranty due to looking at the flash counter. I just found an app called Framaroot which looks much simpler to use
http://forum.xda-developers.com/showthread.php?t=2130276
I have been rooting and flashing ROMs on various Android devices for a long time now so I am up for using any root methods no matter how advanced they may be including using ADB. I did not have enough time to research about the i317 so it was my fault that I could not successfully root his device. Any help would be much appreciated.
Thank you
For rooting purposes start HERE:
http://forum.xda-developers.com/showthread.php?p=33854391
For recovery look HERE:
http://forum.xda-developers.com/showthread.php?p=33867032
Add I prefer TWRP recovery over CWM!!
From everything you said you did it sounded right. Cuz you even tried going back too the original firmware that was shipped with the device!! But I didn't seed that after you flash the Rom,, did you try to do a factory data reset. Sometimes that's all it takes to fix that bootloop problem.
One other thing if you can get into download mode then the phone is fixable. Think it was just over your head on the process on how to get it back to fully functioning... lol
We've all been there. Think it's because we panic when something isn't working the way we want it TO..
Sent from my SAMSUNG-SGH-I317 using Tapatalk 4
I have been using the i747z ROMs for quite some time and after trying a bunch of other ROMs I always reverted back to theirs. So when their 3.0 version came out with Android 4.3 I installed it, using ClockWorkMod recovery. Right after it installed, CWM displayed a message about the boot loader and to fix it. So I went ahead and did that (Don't really remember what the message was) What I know is that I lost root. Also the phone could not connect to the mobile network, only on Wifi. So this morning, I factory reset the phone again, and attempted to root the phone with Odin with CF-Auto-Root-d2att-d2uc-samsungsghi747 (which I had used when I first rooted the phone). Now the phone doesn't boot past the 2nd samsung logo, it starts out with the Samsung logo with the blue circle around it, then the AT&T Rethink Possible and then the plain white Samsung logo. Also, the LED has a slow blue flicker.
I can get the phone into download mode and I have used Odin to attempt to load the stock firmware and the stock bootloader. But after restarting the phone I can't get past the same screen described above.
I am pretty sure this is not related to the i747z v3.0 ROM but rather something a miss with the order in which things need to start in Android. I have done some reading on that but I am not sure what I need to do to correct this soft brick situation. ( I have googled "soft brick" as well)
Any thoughts would be greatly appreciated!
mozphoto said:
I have been using the i747z ROMs for quite some time and after trying a bunch of other ROMs I always reverted back to theirs. So when their 3.0 version came out with Android 4.3 I installed it, using ClockWorkMod recovery. Right after it installed, CWM displayed a message about the boot loader and to fix it. So I went ahead and did that (Don't really remember what the message was) What I know is that I lost root. Also the phone could not connect to the mobile network, only on Wifi. So this morning, I factory reset the phone again, and attempted to root the phone with Odin with CF-Auto-Root-d2att-d2uc-samsungsghi747 (which I had used when I first rooted the phone). Now the phone doesn't boot past the 2nd samsung logo, it starts out with the Samsung logo with the blue circle around it, then the AT&T Rethink Possible and then the plain white Samsung logo. Also, the LED has a slow blue flicker.
I can get the phone into download mode and I have used Odin to attempt to load the stock firmware and the stock bootloader. But after restarting the phone I can't get past the same screen described above.
I am pretty sure this is not related to the i747z v3.0 ROM but rather something a miss with the order in which things need to start in Android. I have done some reading on that but I am not sure what I need to do to correct this soft brick situation. ( I have googled "soft brick" as well)
Any thoughts would be greatly appreciated!
Click to expand...
Click to collapse
After flashing through odin did you format data?If not try it.
Go into recovery and wipe data.
**SOLVED**
Thanks xXFl4sh, I had tried that.
Solved!
Alright where do I start? How about RTFM Some how I had missed the part about flashing a bootloader and a modem after the ROM. Not recalling having to do that before, I skipped right over it. Once the recovery CWM 6.0.3.1 was finally loaded, getting the flashing the ROM, the bootloader and the modem was easy as usual.
The key was having to use Odin to install a recovery in .tar or .tar.md5 format since I could not access a Recovery Mode on the GS3, as well as a rooted stock image (I used root66_ATT_I747UCDLK3.tar.md5 which is a rooted Android 4.1.1 for AT&T) For the recovery, I couldnt' find a .tar or .tar.md5 for ClockWorkMod (did find a utility to convert it, but didn't want to introduce another variable into the mix) so I used one from Team Win Recovery (v2.6.3.0) and with that I loaded the CWM recovery. Once all of that was in place, I proceed to factory reset, clear data, cache, system and then flash the new ROM, bootloader and modem.
In all of this I learned quite a bit about the whole process and how to narrow down possible resolutions. I still see the "Rom may flash stock recovery on boot" message after flashing either a ROM, bootloader or modem, but just backing out without answering Yes or No seems to work. Also (and this may be related, I don't see the option to restart in recovery from shutdown menu). Don't really know what that's all about for now, and honestly don't want to mess around (at least for a while)
I know the steps are general, but I hope this can help some else if they get their devices in a soft brick situation. As for the i747z v3 ROM with 4.3, I really like it, everything works (Wifi,Blutooth,tethering) and the battery seems good as well.
Thanks!
Long time reader, first time poster.
I don't have anything worthy to contribute as most everyone on these forums is far more experienced than me. I do however run into problems - a lot. Working through those problems is quite possibly more enjoyable than experimenting with new ROMS, and I wouldn't be able to work through any of them without the help of this forum. That said, I'll give the short version of my problem first as I'm sure not everyone wants to read the lengths I've been to to unbrick this phone.
I used CyanogenMod's app to root my phone and flash CM10 (which felt like a bad idea at the time). I love CM10 on my Kindle, but I wasn't the biggest fan on my SIII. My phone updated to CM11; which I really hated, and in an effort to flash a new ROM I got stuck in a boot loop. Now I cannot boot into any recovery at all.
The long version:
I am a novice when it comes to flashing, but I'm learning as I screw up. This is the 4th device I've rooted and my second SIII. I have been using TWRP on my Kindle and I totally love it. After having CWM installed by CM's app, I was unable to flash any ROM, period. Rather than hurl my phone against the wall (which I really wanted to) I tried to flash the TWRP .img file, but no matter how I tried the only recovery I could get to was CWM. Finally I used CWM to flash the latest version of PAC-MAN - which I had bootloop problems with on my Kindle - and consequently found myself in a bootloop. I would get the regular Samsung screen, then the CM Samsung screen, then the PAC-MAN screen which it would stay in forever. Throughout all of this the only way I could access a bootloader was by restarting the phone into recovery from Android. Using the "Volume-up, Home Button, and Power" combo doesn't work. I can't remember it ever working to get me to recovery. Anyway, I now have the Dongle Jig which gets me to Download Mode and I can flash the Stock ROM through Odin, but now my boot is stuck on the black Samsung screen. I have also tried flashing the TWRP .tar file through Odin with no luck.
I'm open to any and all suggestions.
HELP!!!
GalaxyBob said:
Long time reader, first time poster.
I don't have anything worthy to contribute as most everyone on these forums is far more experienced than me. I do however run into problems - a lot. Working through those problems is quite possibly more enjoyable than experimenting with new ROMS, and I wouldn't be able to work through any of them without the help of this forum. That said, I'll give the short version of my problem first as I'm sure not everyone wants to read the lengths I've been to to unbrick this phone.
I used CyanogenMod's app to root my phone and flash CM10 (which felt like a bad idea at the time). I love CM10 on my Kindle, but I wasn't the biggest fan on my SIII. My phone updated to CM11; which I really hated, and in an effort to flash a new ROM I got stuck in a boot loop. Now I cannot boot into any recovery at all.
The long version:
I am a novice when it comes to flashing, but I'm learning as I screw up. This is the 4th device I've rooted and my second SIII. I have been using TWRP on my Kindle and I totally love it. After having CWM installed by CM's app, I was unable to flash any ROM, period. Rather than hurl my phone against the wall (which I really wanted to) I tried to flash the TWRP .img file, but no matter how I tried the only recovery I could get to was CWM. Finally I used CWM to flash the latest version of PAC-MAN - which I had bootloop problems with on my Kindle - and consequently found myself in a bootloop. I would get the regular Samsung screen, then the CM Samsung screen, then the PAC-MAN screen which it would stay in forever. Throughout all of this the only way I could access a bootloader was by restarting the phone into recovery from Android. Using the "Volume-up, Home Button, and Power" combo doesn't work. I can't remember it ever working to get me to recovery. Anyway, I now have the Dongle Jig which gets me to Download Mode and I can flash the Stock ROM through Odin, but now my boot is stuck on the black Samsung screen. I have also tried flashing the TWRP .tar file through Odin with no luck.
I'm open to any and all suggestions.
HELP!!!
Click to expand...
Click to collapse
You was not on the OTA MK3 build prior to all the flashing right? If not..
Flash TWRP 2.6.3.0 .tar in Odin (I read I am not the only one having trouble with 2.6.3.1)
Reboot Recovery
Saafir said:
You was not on the OTA MK3 build prior to all the flashing right? If not..
Flash TWRP 2.6.3.0 .tar in Odin (I read I am not the only one having trouble with 2.6.3.1)
Reboot Recovery
Click to expand...
Click to collapse
I'm not sure what OTA MK3 is, but I just tried flashing TWRP 2.6.3.0 via Odin with no luck. What is OTA MK3 and how would it affect my ability to flash?
So this may be a stupid question (but it's my first post so go figure) but I've read a few forum posts and I still can't seem to find a resolution.
I'm using a Rogers SGH i3170 with Android 4.3. I used the cf auto root file to root my phone with ODIN and otherwise did not modify the original software I manually installed the SuperSu apk to get around KNOX.
I was going to sell the phone so I went into the backup & reset option to clear out all my information. the phone seemed to clear itself just fine but now it won't go back the 'samsung' boot screen.
It'll show the device name, do the boot animation and otherwise just sits there.
The battery is at 80-90%
My main issue is that I would flash the stock ROM but it also won't go into recovery mode. It just reboots without actually going there.
Did I just brick my phone?
**I'm fairly new to rooting, I've rooted my S4 and Nexus 5 and was able to reset them without issue through the menus without using CWM or TWRP. I'm familiar enough with the processes just need some direction I guess!
Try this: Vol down& power& home. That'll put you into download mode so you can use Odin to return to stock...
You can also try THIS
If that doesn't help then goHERE for more INFO:thumbup:
Sent from my SAMSUNG-SGH-I317 using Tapatalk
LENT0N said:
So this may be a stupid question (but it's my first post so go figure) but I've read a few forum posts and I still can't seem to find a resolution.
I'm using a Rogers SGH i3170 with Android 4.3. I used the cf auto root file to root my phone with ODIN and otherwise did not modify the original software I manually installed the SuperSu apk to get around KNOX.
I was going to sell the phone so I went into the backup & reset option to clear out all my information. the phone seemed to clear itself just fine but now it won't go back the 'samsung' boot screen.
It'll show the device name, do the boot animation and otherwise just sits there.
The battery is at 80-90%
My main issue is that I would flash the stock ROM but it also won't go into recovery mode. It just reboots without actually going there.
Did I just brick my phone?
**I'm fairly new to rooting, I've rooted my S4 and Nexus 5 and was able to reset them without issue through the menus without using CWM or TWRP. I'm familiar enough with the processes just need some direction I guess!
Click to expand...
Click to collapse
My guess would be depending on what options you chose for wiping your data you probably wiped the root folder.
in which case there is nothing to boot to.
I have done that before in error and its a pain.
If you still have a recovery great you just need to flash a ROM.
Otherwise you might have to ODIN a recovery back on and then flash. Which is what I had to do.
So This is my first time posting on any forum site for help, and i was refereed to XDA by my roommate. so what happened is a few months ago i asked my roommate to root my galaxy s3 SGH-I747, after he rooted it through odin and all seemed well, BUT we never could get the phone to recognize the root and was still unable to access any root functions. so after a few different attempts we gave up. i assumed that my roommate had removed the root (bad call) but never gave it any thought. a few days ago at&t started bugging me with a software update. i just hit ignore and it would pop up again in a few hours and the icon would never go away. so i gave in and started the update. i didnt pay the phone any attention while it "updated" but later that morning i went to turn it back on and it would get to the Samsung screen then the next screen but after that it goes black and vibrates. i showed it to my roommate and he informed me that it was never restored back to official frimware like i had previously assumed. and that it never should have received the update bc it was still on a custom frimware. we tried flashing the stock frimware back on the phone and every time it would fail the nand write. i believe it was updated to 4.4.2 before i received the update from AT&T and we tried many different ways too restore it i even tried the recovery in Kies 3 but all it says is "connecting" then connection failed. so far nothing has worked. i believe that the update contained android 5.0 and maybe that is the reason none of the other ways we tried worked. i have been researching for hours trying to find a similar case but nothing matches, and i cant find a single working solution that doesn't involve possible making it worse. i can access both the recovery and download modes. please any information or help would be greatly appreciated.
Flash a custom recovery such as Philz Touch via Odin, install cm10.2 via your custom recovery. This should get the phone booted so you can determine the bootloader version on your phone. The NAND error is due to the fact that you are trying to downgrade the bootloader in Odin. Don't flash anything with Odin until you determine the bootloader. Doing so could hard brick your phone.
audit13 said:
Flash a custom recovery such as Philz Touch via Odin, install cm10.2 via your custom recovery. This should get the phone booted so you can determine the bootloader version on your phone. The NAND error is due to the fact that you are trying to downgrade the bootloader in Odin. Don't flash anything with Odin until you determine the bootloader. Doing so could hard brick your phone.
Click to expand...
Click to collapse
firstly, thanks for the fast help. i did as you advised and flashed philz touch 6.15.4 which is the latest version from what i understand. that worked flawlessly. the problem now, is with cm10.2 every time ive tried to install it i get an error in /storage/sdcard1/cm-10.2.0-d2att.zip.
im sure im doing everything correctly. any ideas?
Try flashing an older CM11 ROM for the d2lte.
audit13 said:
Try flashing an older CM11 ROM for the d2lte.
Click to expand...
Click to collapse
thanks so much man youve been a big help that worked.