[Q] CWM Recovery on i317M - AT&T Samsung Galaxy Note II

Hi,
I'm having issues installing CWM Recovery on my Rooted GN2. It's the Canadian variant, SGH-I317M.
It does go through the process of flashing the recovery, but never gets to saying PASS in ODIN. When I try to get into the Recovery, it still has the stock Samsung Recovery. It does, however trip the flash counter.
I'm followiing the instructions here: http://forum.xda-developers.com/showthread.php?t=1988785
This is what I get after flashing in ODIN.

Maybe a bad download? Have you checked to see if it installed? I dont usually recommend this but koush's Rom Manager supports our device now, you can use the app to flash it if your already rooted:thumbup:
Sent from my SAMSUNG-SGH-I317 using Tapatalk 2

In your screen shot it shows the f-reset box checked I believe it should be unchecked.

Slff said:
In your screen shot it shows the f-reset box checked I believe it should be unchecked.
Click to expand...
Click to collapse
I tried it with the f-reset box unchecked, and I got it to say PASS, but still no CWM...
cdshepherd said:
Maybe a bad download? Have you checked to see if it installed? I dont usually recommend this but koush's Rom Manager supports our device now, you can use the app to flash it if your already rooted:thumbup:
Sent from my SAMSUNG-SGH-I317 using Tapatalk 2
Click to expand...
Click to collapse
I've also tried to download the file again, and still... No dice...

BlueBagodah said:
I tried it with the f-reset box unchecked, and I got it to say PASS, but still no CWM...
I've also tried to download the file again, and still... No dice...
Click to expand...
Click to collapse
Try rom manager?
Sent from my SAMSUNG-SGH-I317 using Tapatalk 2

cdshepherd said:
Try rom manager?
Sent from my SAMSUNG-SGH-I317 using Tapatalk 2
Click to expand...
Click to collapse
ROM Manager doesn't have a Recovery for the Rogers i317M...

http://forum.xda-developers.com/showthread.php?t=1988785
Sent from my SAMSUNG-SGH-I317 using xda premium

twanskys204 said:
http://forum.xda-developers.com/showthread.php?t=1988785
Sent from my SAMSUNG-SGH-I317 using xda premium
Click to expand...
Click to collapse
Thanks,
I've been following that thread, and it doesn't work. It will trip the flash counter, but doesn't actually install the recovery. It appears that I'm not the only one having this issue after the most recent OTA update...

Can u try and flash a kernel
Then try flashing cwm ...just a hunch
Sent from my SAMSUNG-SGH-I317 using xda premium

BlueBagodah said:
Thanks,
I've been following that thread, and it doesn't work. It will trip the flash counter, but doesn't actually install the recovery. It appears that I'm not the only one having this issue after the most recent OTA update...
Click to expand...
Click to collapse
I'm also having problems after the OTA update. Before OTA update, I was able to flash CWM without problems. Following exact same procedure as before when it was working. Only variable that changed is the OTA update.

wiser212 said:
I'm also having problems after the OTA update. Before OTA update, I was able to flash CWM without problems. Following exact same procedure as before when it was working. Only variable that changed is the OTA update.
Click to expand...
Click to collapse
I was able to install CWM by following this post: http://forum.xda-developers.com/showpost.php?p=36201055&postcount=54
But I'm starting to think that it may have been my fault the whole time...
While doing the 3 button combo to try to boot into Recovery, I was using Vol-DOWN, instead of Vol-UP. So I was going into download mode. I'm going to try flashing the CWM through ODIN again and see if I was just an idiot the whole time.
***EDIT***
It looks like I was just an idiot the whole time...

*facepalm*
Sent from my SAMSUNG-SGH-I317 using Tapatalk 2

.. so ROM manager doesnt work to insall cwm recovery after rooting on the i317m? i tried it and didnt succeed. i guess flashing is my only option but i dont want to lose anything on my phone. just install the bootloader/ recovery with no other changes. i want to start flashing some roms... jedi first.. skynote after.. any thoughts or help would be great!!

Clean rom I would suggest its awesome battery life I have a universal theme flashed over clean rom and a custom blue keyboard if I find the link to the themes ill post em on here
Sent from my sgh-1317 aka MY BLUE DEVIL using xda premium

Dewaynelives said:
Clean rom I would suggest its awesome battery life I have a universal theme flashed over clean rom and a custom blue keyboard if I find the link to the themes ill post em on here
Sent from my sgh-1317 aka MY BLUE DEVIL using xda premium
Click to expand...
Click to collapse
I thought of cleanROM but it is pretty stock. I feel if im going to flash any rom i might as well go with something modded and tweaked rather then stock, while keeping most of the note 2 and s-pen features. If i start finding them being a little buggy or draining my battery or anything, ill settle with cleanROM and just flash some custom mods.
i flashed my CWM through MobileODIN. worked like a charm. then i ran into issues with backing up to extSD, which ended up working after i formatted it but i took way longer then onto internal SD.
i know its off topic for this thread..Any suggestions or thoughts on the JEDI X9 and SKYNOTE roms will be great guys. Im all backed up and ready to flash pretty quick here.

I guess you have custom ROM. You must root and rename recovery restore files before you boot to android or stock recovery will be restored.

Related

Help with root!

Ok, So i've successfully rooted my epic 4g touch and I successfully installed the rogue CWM found on this forum. Now whenever I try to flash the CM7 zip (trying to get AOKP), it will only boot into CWM and the phone won't boot. I've tried re-rooting, wiping dalvik (gives me volume patch error), and wiping cache, etc.
Any help?
No need to boot flash aokp in the recovery and on pretty sure aokp will boot
Sent from my SPH-D710 using Tapatalk
It also seems to be installing the zips very fast.
iSaint said:
No need to boot flash aokp in the recovery and on pretty sure aokp will boot
Sent from my SPH-D710 using Tapatalk
Click to expand...
Click to collapse
No, it doesn't boot. Gets stuck on Galaxy S II screen.
Help please!
Flash it twice. This is a common occurrence
And by that I mean flash it twice successively, one after the other. Should fix you up. Let us know if that doesn't work.
Sent from my SPH-D710 using XDA
Fendulon said:
Flash it twice. This is a common occurrence
Sent from my SPH-D710 using XDA
Click to expand...
Click to collapse
I've done that. It didn't work.
You don't need to install CM7 to install AOKP.
Try this: ODIN to stock EL29, use one click root (choose option C, then I (this'll root your device and give stock CWM recovery)).
Then boot into recovery, flash AOKP, gapps and FD02 modem if you'd like.
Stock EL29: http://forum.xda-developers.com/showthread.php?t=1352310
Root: http://forum.xda-developers.com/showthread.php?t=1342728
3meister said:
You don't need to install CM7 to install AOKP.
Try this: ODIN to stock EL29, use one click root (choose option C, then I (this'll root your device and give stock CWM recovery)) then boot into recovery, flash AOKP, gapps and FD02 modem if you'd like.
Stock EL29: http://forum.xda-developers.com/showthread.php?t=1352310
Root: http://forum.xda-developers.com/showthread.php?t=1342728
Click to expand...
Click to collapse
I'll try that.
^ that start from scratch and relax you're far from bricked
Sent from my SPH-D710 using Tapatalk
batting1000 said:
I've done that. It didn't work.
Click to expand...
Click to collapse
Really? Interesting. Ok well most people are actually flashing AOKP and Codename from the EL26 CWM that is linked in the OP of those threads. That is actually how I have flashed over 15 times with different builds. So if you can Odin EL26 with clockwork mod you should be able to flash AOKP after you flash a calkulin format all to wipe all relevant partitions and don't forget to install Google apps.
Sent from my SPH-D710 using XDA
3meister said:
You don't need to install CM7 to install AOKP.
Try this: ODIN to stock EL29, use one click root (choose option C, then I (this'll root your device and give stock CWM recovery)).
Then boot into recovery, flash AOKP, gapps and FD02 modem if you'd like.
Stock EL29: http://forum.xda-developers.com/showthread.php?t=1352310
Root: http://forum.xda-developers.com/showthread.php?t=1342728
Click to expand...
Click to collapse
If I'm already rooted can I do option I over the root?
batting1000 said:
If I'm already rooted can I do option I over the root?
Click to expand...
Click to collapse
Yes, root works a bit different on this phone. Pretty much every single rom available will provide with root and superuser when it is installed via some sort of custom recovery or Odin. Odin is actually a very safe and convenient method of flashing.
Sent from my SPH-D710 using XDA
Fendulon said:
Yes, root works a bit different on this phone. Pretty much every single rom available will provide with root and superuser when it is installed via some sort of custom recovery or Odin. Odin is actually a very safe and convenient method of flashing.
Sent from my SPH-D710 using XDA
Click to expand...
Click to collapse
I'll try that and report back.
Didn't work. Zips are installing way too fast. Isn't booting into AOKP. Guess I gotta go back to stock.
batting1000 said:
Didn't work. Zips are installing way too fast. Isn't booting into AOKP. Guess I gotta go back to stock.
Click to expand...
Click to collapse
Hmm that's strange. A lot of people definitely have the fast zip installing issue but when they flash it for the second time without ever rebooting recovery or the phone it takes a good 15+ seconds to flash and it successfully writes to your phone and boots up. Going back to stock certainly can't hurt. Perhaps start from there.
Sent from my SPH-D710 using XDA
Fendulon said:
Hmm that's strange. A lot of people definitely have the fast zip installing issue but when they flash it for the second time without ever rebooting recovery or the phone it takes a good 15+ seconds to flash and it successfully writes to your phone and boots up. Going back to stock certainly can't hurt. Perhaps start from there.
Sent from my SPH-D710 using XDA
Click to expand...
Click to collapse
I've started from stock twice, reinstalled rooted via odin (twice), then tried to do CWM. Thanks anyway guys! Appreciate it!
Have you tried redownloading the ROM? If you downloaded via your device you could have had some dropped packets.
Sent from my SPH-D710 using Tapatalk

Stuck in a boot loop

Rooted Att Note 2. I changed my fonts using Rom Tools and now my phone just sits at the Samsung splash screen. I did factory reset in recovery, still no dice. The recovery install only let's my flash updates and no I don't have a Nandroid. Kinda ran outta of ideas.
when you say the recovery install only lets you flash updates do you mean your still using stock revocery or have you flashed custom recovery and just dont have a ROM?
If you have custom recovery Id try to flash this :http://forum.xda-developers.com/showthread.php?t=1984546 Its been tested and works on our system. Its not stock but should at least get ya up and running again until a true stock is posted and you can flash that.
search in forums for an Odin tar file to reload the stock ROM. GL & do a nandroid before doing anything next time.
RMXO said:
search in forums for an Odin tar file to reload the stock ROM. GL & do a nandroid before doing anything next time.
Click to expand...
Click to collapse
I always do, didnt think much of fonts
cjsspape said:
when you say the recovery install only lets you flash updates do you mean your still using stock revocery or have you flashed custom recovery and just dont have a ROM?
If you have custom recovery Id try to flash this :http://forum.xda-developers.com/showthread.php?t=1984546 Its been tested and works on our system. Its not stock but should at least get ya up and running again until a true stock is posted and you can flash that.
Click to expand...
Click to collapse
not custom, thats the problem. I flashed twrp thru odin but it didnt take, even though it went thru
Try to flash cwm then and see if that takes. You'll need the Odin version of this file at the bottom of the OP http://forum.xda-developers.com/showthread.php?p=33955697
Sent from my SAMSUNG-SGH-I317 using xda premium
Sloved
the cmw tar worked. flash the rom in the general section
Good stuff. Glad it worked out for ya!
Sent from my SAMSUNG-SGH-I317 using xda premium
esincho said:
Rooted Att Note 2. I changed my fonts using Rom Tools and now my phone just sits at the Samsung splash screen. I did factory reset in recovery, still no dice. The recovery install only let's my flash updates and no I don't have a Nandroid. Kinda ran outta of ideas.
Click to expand...
Click to collapse
I had the same problem with Sprint note 2 and i just went to download screen and then flashed the cwm tar file and then all was good. Whew!!! Thought I bricked it! I made the mistake of using a quick boot app to reboot in to recovery. DON'T DO IT!
chidochuck said:
I had the same problem with Sprint note 2 and i just went to download screen and then flashed the cwm tar file and then all was good. Whew!!! Thought I bricked it! I made the mistake of using a quick boot app to reboot in to recovery. DON'T DO IT!
Click to expand...
Click to collapse
Just bought a ATT GN2... coming from SkyRocket... on the SR, I used to always use "Quick Boot" app to reboot, or reboot into CWM Recovery. When you reference "quick boot app", are you referring to this? When my GN2 arrives, want to be sure I avoid using "Quick Boot" app if it doesn't play well on the GN2 and JB. Thx.
DoctorQMM said:
Just bought a ATT GN2... coming from SkyRocket... on the SR, I used to always use "Quick Boot" app to reboot, or reboot into CWM Recovery. When you reference "quick boot app", are you referring to this? When my GN2 arrives, want to be sure I avoid using "Quick Boot" app if it doesn't play well on the GN2 and JB. Thx.
Click to expand...
Click to collapse
Most of the custom ROMs here use the built in 4 way Rebooter so ya really shouldn't need a quick boot program
Sent from my SGH-I317 using xda premium
I've had rom tools boot loop the phone after a font change. Moral of the story-nandroid.
Sent from my SAMSUNG-SGH-I317 using Tapatalk 2
That's the one I used. Wish I knew why it happened.
Sent from my SPH-L900 using xda app-developers app

Root issues (moved from Virgin rom as requested) Help

I am trying to upgrade my Virgin ROM to the 9.12 build but get a fail upon trying to flash it. The background.... I'm using TWRP recovery and have tried the chainfire root method. Here are the results:
As you can see you can see some conflicting information... all shots were taken in sequence. I'm thinking the fail in twrp is coming from the system not having root but the info is telling me otherwise....
Bump... Anybody???
Sent from my GT-I9505G using xda app-developers app
th3h0ff said:
Bump... Anybody???
Sent from my GT-I9505G using xda app-developers app
Click to expand...
Click to collapse
Do you have the latest SuperSU version?
I'm a little lost at what you are saying.
You flashed a rom, and it said fail, and you think it has to do with Root?
If you have TWRP installed it doesn't matter if you are rooted or not. It's going to over right the system partition regardless if you have root or not.
So it's either a bad download or bad transfer for it to fail.
Sent from my SGH-M919 using Tapatalk 4
I do have the latest SU version by chain fire. And maybe I'm doing something wrong the because I am running the virgin gpe ROM now and that flashed in twrp with no issues. Now when I go to install (after wiping) and select the 9.12 update that I downloaded it hangs on trying to open the zip and fails... I haven't changed any twrp settings but in the write options of twrp what boxes should be checked because system is not by default... Thanks for the replies!
Sent from my GT-I9505G using xda app-developers app
I previously only used cwm so I'm not sure if I should just try that or what... And I've checked the download and md5 for verification
Sent from my GT-I9505G using xda app-developers app
th3h0ff said:
I previously only used cwm so I'm not sure if I should just try that or what... And I've checked the download and md5 for verification
Sent from my GT-I9505G using xda app-developers app
Click to expand...
Click to collapse
You can give CWM a try, I've been using it for a while without any issues. Out of curiosity what version if TWRP you are using? I think most people recommend TWRP 2.5.0.2. I'm using the latest version of CWM.
Sent from my GT-I9505G using xda app-developers app
If all else fails, just start from scratch, get stock UVUAMDL tar, flash it with Odin, make sure to do a factory wipe after you flash it, sometimes bootloops occur if you don't. You don't even have to go past the first screen where you pick the language. Just shut it down from there and boot into download mode and root with Chainfire with Odin, then shut down and boot up again into download mode again and flash custom recovery tar of ur choice with Odin. Then download whatever custom rom zip and install it via custom recovery.
norml said:
If all else fails, just start from scratch, get stock UVUAMDL tar, flash it with Odin, make sure to do a factory wipe after you flash it, sometimes bootloops occur if you don't. You don't even have to go past the first screen where you pick the language. Just shut it down from there and boot into download mode and root with Chainfire with Odin, then shut down and boot up again into download mode again and flash custom recovery tar of ur choice with Odin. Then download whatever custom rom zip and install it via custom recovery.
Click to expand...
Click to collapse
Thanks again to everyone... not going to have time to mess with it tonight but I'll update tomorrow. Thanks again
th3h0ff said:
Thanks again to everyone... not going to have time to mess with it tonight but I'll update tomorrow. Thanks again
Click to expand...
Click to collapse
heyyy saw your reply in my thread.
just as @byron1985 suggested there, it sounds like you got a bad download. the flashing scripts are essentially exactly the same from previous version. the flashing process has absolutely zero to do with SuperSU.
edit: re-read. so you've verified the download. if you had success with CWM previously, i would go back to that. i do not use TWRP.
mrvirginia said:
heyyy saw your reply in my thread.
just as @byron1985 suggested there, it sounds like you got a bad download. the flashing scripts are essentially exactly the same from previous version. the flashing process has absolutely zero to do with SuperSU.
edit: re-read. so you've verified the download. if you had success with CWM previously, i would go back to that. i do not use TWRP.
Click to expand...
Click to collapse
Im going to give the twrp 2.5.2 a try as it seems most of my troubles keep happening on the 2.6.3 build. Hopefully that works either way its back to CWM for me as well. Thanks again for taking the time to help out and again sorry about hijacking the thread for a page... Your ROM is absolutely perfect so I appreciate the efforts and time!,
Andrew
SOLVED... tried 2.5 version of TWRP and all went well... odd but apparently my device doesnt like 2.6 versions of TWRP! Thanks to everyone who helped me out and gave me suggestions and thank you to the dev for taking some of his time to assist! It was a great help to me!
th3h0ff said:
SOLVED... tried 2.5 version of TWRP and all went well... odd but apparently my device doesnt like 2.6 versions of TWRP! Thanks to everyone who helped me out and gave me suggestions and thank you to the dev for taking some of his time to assist! It was a great help to me!
Click to expand...
Click to collapse
Good to know you are out of trouble
Sent from my Nexus 10 using xda app-developers app
See you shoulda said you were running 2.6.3 lol
word of advice (and to all who run twrp)
DO NOT RUN ANYTHING GREATER THAN 2.5.2!!!!!!!!!!!!!!

[Q] Odin a stock firmware

If i use odin to flash a stock firmware will it delete all of the pictures inside the phone?
No. I have pictures and music and all SD card contents dating back to the time I bought the phone and I used Odin last week to return to stock.
Sent from my SGH-T999 using Tapatalk
No, but you may need to factory reset, which would delete all the files in your device..
There are possible ways trying to get around this, but its safer to just back up your important files in case something unexpected happens
Sent from my SGH-M919 using Tapatalk
serio22 said:
No, but you may need to factory reset, which would delete all the files in your device..
There are possible ways trying to get around this, but its safer to just back up your important files in case something unexpected happens
Sent from my SGH-M919 using Tapatalk
Click to expand...
Click to collapse
well the phone im doing it on doesnt start and just stays stuck on the samsung logo so do you think itll still work.
lmendoza23 said:
well the phone im doing it on doesnt start and just stays stuck on the samsung logo so do you think itll still work.
Click to expand...
Click to collapse
Don't know, often times that means a factory reset might be needed, but can you tell me what happened to it? There may be other ways to fix it
Sent from my SGH-M919 using Tapatalk
The phone belongs to a buddy of mine but he told me it just randomly happened.
btw nice e90
lmendoza23 said:
The phone belongs to a buddy of mine but he told me it just randomly happened.
btw nice e90
Click to expand...
Click to collapse
Hmm.. Ok try flashing firmware with Odin, if that doesn't fix it then flash twrp recovery and reboot to recovery, after that do a factory reset within twrp.. This will perform a factory reset without wiping user files.. Reboot and it should boot up
Edit: oh and yes I know, wish it was mine :/
Sent from my SGH-M919 using Tapatalk
serio22 said:
Hmm.. Ok try flashing firmware with Odin, if that doesn't fix it then flash twrp recovery and reboot to recovery, after that do a factory reset within twrp.. This will perform a factory reset without wiping user files.. Reboot and it should boot up
Edit: oh and yes I know, wish it was mine :/
Sent from my SGH-M919 using Tapatalk
Click to expand...
Click to collapse
so the first odin shouldnt delete anything from the gallery? no matter which rom i flash
ohhh, if it was an m3 id be wishing too
lmendoza23 said:
so the first odin shouldnt delete anything from the gallery? no matter which rom i flash
ohhh, if it was an m3 id be wishing too
Click to expand...
Click to collapse
Right, but you're not flashing a rom, you're flashing firmware.. You could also just flash a rom, but I don't know how your buddy wants his device
Bro I love m3's!! Been in love with them since day one.. I just have that display pic because it looks nice lol
Sent from my SGH-M919 using Tapatalk
serio22 said:
Right, but you're not flashing a rom, you're flashing firmware.. You could also just flash a rom, but I don't know how your buddy wants his device
Bro I love m3's!! Been in love with them since day one.. I just have that display pic because it looks nice lol
Sent from my SGH-M919 using Tapatalk
Click to expand...
Click to collapse
Alright well here goes nothing!
Hopefully when im done with my e36 ill be chasing those e90s
EDIT: When i attempt to flash with odin it says <OSM> All threads completed. (succeed 0 / failed 1) and the phone says odin flash write faliure
What firmware version did you try to flash? If it was ever updated to 4.3 you can only ever flash the same or newer firmware again. So if it had been updated to NC2 before, you can only flash NC2 firmware. (Latest version). If this doesn't apply, you might want to try reinstalling drivers. Also, only use Odin v3.07 or 3.09.
You can try to odin flash twrp recovery though, then make a nandroid backup to be safe. It also has a built in file manager and you can use it to copy the picture folder from internal to external sd card.
Sent from my SGH-T999 using Tapatalk
DocHoliday77 said:
What firmware version did you try to flash? If it was ever updated to 4.3 you can only ever flash the same or newer firmware again. So if it had been updated to NC2 before, you can only flash NC2 firmware. (Latest version). If this doesn't apply, you might want to try reinstalling drivers. Also, only use Odin v3.07 or 3.09.
You can try to odin flash twrp recovery though, then make a nandroid backup to be safe. It also has a built in file manager and you can use it to copy the picture folder from internal to external sd card.
Sent from my SGH-T999 using Tapatalk
Click to expand...
Click to collapse
I downloaded the latest 4.3 and tried to flash that but didnt work im not sure what the phone had before and can i flash the twrp recovery if the phone wasnt rooted?
Yes, you can flash a custom recovery without root. Its actually the original root method if I'm not mistaken. (Flash recovery, then from that recovery flash the SuperSU update zip. )
Since youre using the latest firmware, we know that's not the cause at least.
Few other things that are known to cause Odin to fail...
Make sure you are using the correct firmware for the device. (Make sure if its a T999, T999L, T999N, T999V and use the corresponding firmware)
If kies is on your computer, uninstall it
Try different usb cables, yes they quite often do go bad.
Try every usb port on your computer. I've seen more than a few people find it only worked on one usb port! No idea why...
Try different driver versions. Make sure you uninstall through device manager. Drivers are in my sig.
If all else fails, try a different computer if possible.
If I think of anything else ill add it.
Sent from my SGH-T999 using Tapatalk
Yup, everything Doc said.. Double check firmware or Odin may be a little picky
Sent from my SGH-M919 using Tapatalk
I tried what you guys said and none of it worked and then i tried to install a recovery through odin and that worked. Through recovery I tried to install a zip firmware that i got from another firmware and now the phone does not start at all no boot screen no download mode no nothing. Is it fully gone now?
lmendoza23 said:
I tried what you guys said and none of it worked and then i tried to install a recovery through odin and that worked. Through recovery I tried to install a zip firmware that i got from another firmware and now the phone does not start at all no boot screen no download mode no nothing. Is it fully gone now?
Click to expand...
Click to collapse
Firmware or ROM? And what zip is this you're talking about? Can you get into recovery? If not then you might have bricked it
Sent from my SGH-M919 using Tapatalk
serio22 said:
Firmware or ROM? And what zip is this you're talking about? Can you get into recovery? If not then you might have bricked it
Sent from my SGH-M919 using Tapatalk
Click to expand...
Click to collapse
I used this thread http://forum.xda-developers.com/showthread.php?t=2403060 at the bottom of the first post
and yeah no recovery
but when i plug it into my computer it beeps like if something just was plugged in
That thread is pretty old and I think that was for LJA, if the phone was updated to 4.3 and you tried that it makes sense that it would brick.. Does it give you message in the connected devices?
Sent from my SGH-M919 using Tapatalk
serio22 said:
That thread is pretty old and I think that was for LJA, if the phone was updated to 4.3 and you tried that it makes sense that it would brick.. Does it give you message in the connected devices?
Sent from my SGH-M919 using Tapatalk
Click to expand...
Click to collapse
Nope
lmendoza23 said:
Nope
Click to expand...
Click to collapse
Try the debrick thread
Sent from my SGH-M919 using Tapatalk

Soft Bricked? Stuck at boot screen.

Basically I do have common sense and and I'm pretty knowledgeable when it comes to working with phones but this problem I have is different.
I purchased this phone(I747) already bricked thinking I can fix since I have before. It goes to cwm 6.0.3.4 and boots to Odin. Last known os was cm but don't know what version. Not even clear what bootloader it's but when trying to boot up there's the blue cm Android guy.
So here's what I tried so far to fix my problem.
1. Tried to flash the mjb restore posted somewhere on here. Flashed with no errors but when I reboot still the blue Android.
2. Wipe and formatted the proper things and tried flashing a couple of roms but all gave me error 7.
3. Tried flashing a different recovery thru Odin, all passed but non stuck. Can't get rid of my current recovery.
4. Tried to Odin 4.3 firmware but that failed.
Kinda running out of ideas on what to try next, can someone help me figure out what I'm doing wrong or what's the problem?
Sent from my SM-N900T using XDA Premium 4 mobile app
donutkidd said:
Basically I do have common sense and and I'm pretty knowledgeable when it comes to working with phones but this problem I have is different.
I purchased this phone(I747) already bricked thinking I can fix since I have before. It goes to cwm 6.0.3.4 and boots to Odin. Last known os was cm but don't know what version. Not even clear what bootloader it's but when trying to boot up there's the blue cm Android guy.
So here's what I tried so far to fix my problem.
1. Tried to flash the mjb restore posted somewhere on here. Flashed with no errors but when I reboot still the blue Android.
2. Wipe and formatted the proper things and tried flashing a couple of roms but all gave me error 7.
3. Tried flashing a different recovery thru Odin, all passed but non stuck. Can't get rid of my current recovery.
4. Tried to Odin 4.3 firmware but that failed.
Kinda running out of ideas on what to try next, can someone help me figure out what I'm doing wrong or what's the problem?
Sent from my SM-N900T using XDA Premium 4 mobile app
Click to expand...
Click to collapse
What did you try to flash? Status 7 means you don't have the right device for what you were trying to flash or that your build.prop was modified by the previous owner to another device name.
I believe you'll need to flash a ROM matching the current device name and work from there.
Although, I find it odd that flashing with Odin doesn't work. Have you tried flashing stock?
BWolf56 said:
What did you try to flash? Status 7 means you don't have the right device for what you were trying to flash or that your build.prop was modified by the previous owner to another device name.
I believe you'll need to flash a ROM matching the current device name and work from there.
Although, I find it odd that flashing with Odin doesn't work. Have you tried flashing stock?
Click to expand...
Click to collapse
Yep I tried stock 4.1.1 and 4.3 thru Odin and failed. I tried installing a new recovery thru the current recovery using a zip file and it went thru with no errors but reboot and nothing has changed. Something when flashing the restore and the bootloader.
Sent from my SM-N900T using XDA Premium 4 mobile app
donutkidd said:
Yep I tried stock 4.1.1 and 4.3 thru Odin and failed. I tried installing a new recovery thru the current recovery using a zip file and it went thru with no errors but reboot and nothing has changed. Something when flashing the restore and the bootloader.
Sent from my SM-N900T using XDA Premium 4 mobile app
Click to expand...
Click to collapse
You can try flashing another/updated recovery through Odin. But until you find out what device your build.prop is setup to, you won't be able to flash a ROM through recovery.
BWolf56 said:
You can try flashing another/updated recovery through Odin. But until you find out what device your build.prop is setup to, you won't be able to flash a ROM through recovery.
Click to expand...
Click to collapse
I tried every recovery for this phone that's up to date so yeah I don't know what else to do. And how can I figure that out? The build.prop part?
Sent from my SM-N900T using XDA Premium 4 mobile app
donutkidd said:
I tried every recovery for this phone that's up to date so yeah I don't know what else to do. And how can I figure that out? The build.prop part?
Sent from my SM-N900T using XDA Premium 4 mobile app
Click to expand...
Click to collapse
It's in your System folder. Should be able to navigate to it using your recovery.
BWolf56 said:
It's in your System folder. Should be able to navigate to it using your recovery.
Click to expand...
Click to collapse
Will it still be there even if I formatted the system? If so what are the adb commands so I can pull it and post it?
donutkidd said:
Will it still be there even if I formatted the system? If so what are the adb commands so I can pull it and post it?
Click to expand...
Click to collapse
Hopefully it is. And I duno about the command, you'll have to look that one up (or perhaps someone here knows it).
If you formatted /system, its gone and shouldn't matter. But imo you should never format system manually. Otherwise you end up with nothing to boot or troubleshoot if things go wrong.
From your recovery, find where you can use the terminal emulator and enter
getprop ro.boot loader
This is what firmware you need to be flashing via odin.
Sent from my SGH-T999 using Tapatalk
Ok I will try that when I get home.
Sent from my SM-N900T using XDA Premium 4 mobile app
DocHoliday77 said:
If you formatted /system, its gone and shouldn't matter. But imo you should never format system manually. Otherwise you end up with nothing to boot or troubleshoot if things go wrong.
From your recovery, find where you can use the terminal emulator and enter
getprop ro.boot loader
This is what firmware you need to be flashing via odin.
Sent from my SGH-T999 using Tapatalk
Click to expand...
Click to collapse
Ok I did the getprop ro.bootloader command and it's I747UCDLK3. I have already tried the lk3 Odin but let me try to re download a fresh copy of it.
Sent from my SM-N900T using XDA Premium 4 mobile app
No dice, I even downloaded a 4.1.1 lk3 rom. It flashed and said successful so I rebooted and back to the blue Android. Is it possible NY partitions or whatever are corrupt and if so anyway to fix it?
Sent from my SM-N900T using XDA Premium 4 mobile app
I'm kinda at a loss. Wondering if its a partition not flashed by Odin that's been corrupted...
No idea if this'll help or not, but download this.
http://www.androidfilehost.com/?fid=23060877489996938
(It is a 16gb model right?)
Now flash firmware in Odin in like usual, but check the repartition checkbox, then click the PIT button and browse to and select the file I just linked. Verify.
Click start and cross fingers.
Another thing you can try...flash twrp with Odin, but uncheck auto reboot. After it says PASS, pull the battery. Put it back in and boot recovery. Hopefully it'll stick now.
Now you can try flashing some roms again, and use the built in file manager to look for any issues/anomalies.
I'm not sure what version LK3 is, but it sounds kinda old, so you may want to look for a 4.1.1 rom to start with. That shouldn't give you any status 7 errors. Or if you want to flash newer roms you'll need to edit the asserts in the updater script.
DocHoliday77 said:
I'm kinda at a loss. Wondering if its a partition not flashed by Odin that's been corrupted...
No idea if this'll help or not, but download this.
http://www.androidfilehost.com/?fid=23060877489996938
(It is a 16gb model right?)
Now flash firmware in Odin in like usual, but check the repartition checkbox, then click the PIT button and browse to and select the file I just linked. Verify.
Click start and cross fingers.
Another thing you can try...flash twrp with Odin, but uncheck auto reboot. After it says PASS, pull the battery. Put it back in and boot recovery. Hopefully it'll stick now.
Now you can try flashing some roms again, and use the built in file manager to look for any issues/anomalies.
I'm not sure what version LK3 is, but it sounds kinda old, so you may want to look for a 4.1.1 rom to start with. That shouldn't give you any status 7 errors. Or if you want to flash newer roms you'll need to edit the asserts in the updater script.
Click to expand...
Click to collapse
I honestly think I tried what you suggested already but just to triple check I will do so again in the morning and report back with hopefully good news.
Sent from my SM-N900T using XDA Premium 4 mobile app
@BWolf56
Do you guys have a recovery flashable package for the 4.1.1 or 4.1.2 firmware? (I'm guessing that's what LK3 is.)
If so maybe flashing that would help?
DocHoliday77 said:
@BWolf56
Do you guys have a recovery flashable package for the 4.1.1 or 4.1.2 firmware? (I'm guessing that's what LK3 is.)
If so maybe flashing that would help?
Click to expand...
Click to collapse
No, nothing for 4.1.1 (LK3).
I don't think that's his issue though. Last time I saw that issue was on the S1 (Captivate) and the solution was to use Heimdall.
If the repartition doesn't work though, I'm not exactly sure what will.
DocHoliday77 said:
@BWolf56
Do you guys have a recovery flashable package for the 4.1.1 or 4.1.2 firmware? (I'm guessing that's what LK3 is.)
If so maybe flashing that would help?
Click to expand...
Click to collapse
I was just reading what you said in this post - > ([Q] Can't flash stock rom through Odin, phone only boots in download mode. Help!) and it does sound awfully like my situation being that nothing sticks after flashing.
donutkidd said:
I was just reading what you said in this post - > ([Q] Can't flash stock rom through Odin, phone only boots in download mode. Help!) and it does sound awfully like my situation being that nothing sticks after flashing.
Click to expand...
Click to collapse
Do you have the actual link to that thread? Search is derping on me.
BWolf56 said:
Do you have the actual link to that thread? Search is derping on me.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2415409
Sent from my SM-N900T using XDA Premium 4 mobile app
donutkidd said:
http://forum.xda-developers.com/showthread.php?t=2415409
Sent from my SM-N900T using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Ouff that's one bad issue, it can take a while to figure out which partition got messed up. And sadly, I can't be much help there :/

Categories

Resources