Related
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!
Hi all. I'm in a real pickle here and hoping someone can tell me how to get out of this mess. It's a bit of a long story, but I'll summarise as best I can.
I've had my Galaxy Note 2 LTE (N7105) for a year and I rooted it pretty much the day after I got it. I'm not new to rooting at all (fourth Android device since 2010, all rooted), but I still feel like a noob at times. Over this 2014 Easter period I had time off so I decided to change ROMs.
I was previously using CM 11, which I had been using pretty much since I rooted. And I had updated CM at least once a month, sometimes more frequently. So I was looking for some new ROMs, downloaded about 5 and tried them out. The last two I tried was OmniROM (a 4.4.2 ROM) and CM 11 Remix (also a 4.4.2 ROM). I was using TWRP 2.7.0.2 to do the wipes, caches, flashes, etc. I had no issues flashing OmniROM, but when I flashed CM 11 Remix, I couldn't get in the first time. I was stuck in a boot loop. I pulled the battery, got back into recovery and tried flashing again. Still boot looping. I think the mistake I made was a Data Format. Either way, I finally got CM 11 Remix to load by first wiping, flashing the ROM, GApps, a sensor fix, a camera fix, Devil Kernel and then Super SU. However once in the ROM I was getting constant Google Play Store / Services FCs. Oh, and yes, I went through the typical brand new Android setups, entering my Google account and so on... I found that if I cleared data / caches on both Google Play Store app and Google Play Services app, it gave me temporary joy but as soon as I tried to download any app in Google Play I'd get the FC. Also, my signal was totally gone. I tried flashing back to OmniROM as it was my last known good and working ROM, but now that was boot looping. I even tried some of the other ROMs from that bunch I had, including AOKP. All would boot loop.
So after much trying different GApp packages, I decided to best thing to do would be restore it to stock, root again, then go for the custom ROM (hopefully CM 11 Remix) from a nice clean slate. So I did this. I downloaded the Android 4.3 stock ROM from SamMobile here. Installed Odin 3.07, then loaded it up and flashed the stock ROM. All seemed to go great, but when the ROM was done and phone rebooted, I get stuck in another boot loop! This time at the white "Samsung" logo with the glowing blue edges. Not the model number screen. Also my LED light is on blue, if that means anything.
So I found this thread (post at top of page) which suggests I need to flash the PIT file during the stock ROM installation with Odin. So I found the PIT file here, and I'm ready to flash this along with the stock ROM... HOWEVER, I read something somewhere (can't find it now) that implied if I'm on Android 4.3, flashing a PIT is a bad move. Can anyone comment on that? I guessing since the stock ROM is 4.3, I'm technically on 4.3 (even though I can't get into it).
Or if anything else I'm doing immediately stands out as a seriously stupid move, please let me know. I've been without normal use of my phone for a couple days now and ironically I'm at the point where I'm considering going without a phone for the rest of my life... LOL! AS IF I COULD!
Anyways, any help will be much appreciated!
EDIT: I just realised I should have posted in Troubleshooting, not General Questions... If mods want to move this, please do.
i just suggest that you flash the stock odin without the pit and see if its working out or not. sometimes playing with pit files can screw up your device even more...
btw... next time you play flashing... i'm suggesting you make a backup of your working custom. its will save you lots of time if this kind of problem happen.
edan1979 said:
i just suggest that you flash the stock odin without the pit and see if its working out or not. sometimes playing with pit files can screw up your device even more...
btw... next time you play flashing... i'm suggesting you make a backup of your working custom. its will save you lots of time if this kind of problem happen.
Click to expand...
Click to collapse
I don't have any working ROM. All I have now is a boot loop.
invertedskull said:
I don't have any working ROM. All I have now is a boot loop.
Click to expand...
Click to collapse
I had a problem with my device where I was stuck at boot loader as well, but it was from the rar file of the rom(cm 11) cause I tried downloading it again and it worked.
I suggest you prepare Odin and the stock firmware, wipe factory/cache dalvik, system (advanced), then flash stock firmware, to bring everything back to normal.
Banutu said:
I had a problem with my device where I was stuck at boot loader as well, but it was from the rar file of the rom(cm 11) cause I tried downloading it again and it worked.
I suggest you prepare Odin and the stock firmware, wipe factory/cache dalvik, system (advanced), then flash stock firmware, to bring everything back to normal.
Click to expand...
Click to collapse
Hmmm, I'm not stuck at boot loader, just boot loop. Maybe you meant that?
To clarify, all I can do now is...
1. Boot normally and end up in a boot loop (at "Samsung" white logo with glowing blue edges).
2. Boot into Download mode and from there I can use Odin to flash / install.
3. Boot into stock recovery, which I've never used before (only ever used custom recovery).
I've prepped Odin again, ready to flash the stock firmware, but I've never done a wipe / factory reset with Odin. I don't see any Advanced settings? Did you mean I can do it elsewhere? Cos I see I can do wipes / factory reset from stock recovery.
So should I do that AND then go into Download mode and flash stock firmware with Odin?
invertedskull said:
Hmmm, I'm not stuck at boot loader, just boot loop. Maybe you meant that?
To clarify, all I can do now is...
1. Boot normally and end up in a boot loop (at "Samsung" white logo with glowing blue edges).
2. Boot into Download mode and from there I can use Odin to flash / install.
3. Boot into stock recovery, which I've never used before (only ever used custom recovery).
I've prepped Odin again, ready to flash the stock firmware, but I've never done a wipe / factory reset with Odin. I don't see any Advanced settings? Did you mean I can do it elsewhere? Cos I see I can do wipes / factory reset from stock recovery.
So should I do that AND then go into Download mode and flash stock firmware with Odin?
Click to expand...
Click to collapse
ohhh my bad, I meant boot loop (stuck at samsung logo), mine was stuck there but then after it restarts and goes into recovery mode
do these following steps and you should be fine with your device.
1. Go into recovery mode
2. Wipe factory/reset
3. Wipe cache
4. Wipe dalvik
5. Advance > format/system
Now you have no rom or any OS to load,
1. Power off the device
2. Open Odin on your PC(right click run as administrator)
3. power on your note in Download Mode
4. Connect your device to your PC via USB
5. odin should recognize your device, something blue like " ID" or something there, you should be familiar with that.
6. click PDA, and find the official stock firmware zip you got it from samsung website, and make sure it fits your device(for example if you have your note from italy you should have ITV)
7. Hit Start and it should finish in 5-10 minutes.
Its the cleanest way with Odin, I did some crap on my device and that's how I return it to normal.
Banutu said:
ohhh my bad, I meant boot loop (stuck at samsung logo), mine was stuck there but then after it restarts and goes into recovery mode
do these following steps and you should be fine with your device.
1. Go into recovery mode
2. Wipe factory/reset
3. Wipe cache
4. Wipe dalvik
5. Advance > format/system
Now you have no rom or any OS to load,
1. Power off the device
2. Open Odin on your PC(right click run as administrator)
3. power on your note in Download Mode
4. Connect your device to your PC via USB
5. odin should recognize your device, something blue like " ID" or something there, you should be familiar with that.
6. click PDA, and find the official stock firmware zip you got it from samsung website, and make sure it fits your device(for example if you have your note from italy you should have ITV)
7. Hit Start and it should finish in 5-10 minutes.
Its the cleanest way with Odin, I did some crap on my device and that's how I return it to normal.
Click to expand...
Click to collapse
All good! Cheers man!
I actually went ahead and booted into stock recovery and did the factory reset and partition wipe before I saw your post. And the stock firmware I'd flashed with Odin previously is now booting and I'm finally back in!!! WOOOOOOOOO!!!
Just need to root this bad boy and get back to a nice shiny custom ROM.
Thanks for the advice everyone!
invertedskull said:
All good! Cheers man!
I actually went ahead and booted into stock recovery and did the factory reset and partition wipe before I saw your post. And the stock firmware I'd flashed with Odin previously is now booting and I'm finally back in!!! WOOOOOOOOO!!!
Just need to root this bad boy and get back to a nice shiny custom ROM.
Thanks for the advice everyone!
Click to expand...
Click to collapse
I'm glad to hear that man, peace ^^
Banutu said:
I'm glad to hear that man, peace ^^
Click to expand...
Click to collapse
I have another hurdle... Some built in security is stopping SuperSU from running. It's not Knox, but something like it. I get this error message:
"Unauthorized access to a secured area has been blocked. Tap here for more info."
How can I disable this? I've searched on Google already but so far nothing is helping and I can mostly only find info about Knox...
EDIT: It was goddamn Knox all along... And I just disabled it by means of SuperSU. Finally!
invertedskull said:
I have another hurdle... Some built in security is stopping SuperSU from running. It's not Knox, but something like it. I get this error message:
"Unauthorized access to a secured area has been blocked. Tap here for more info."
How can I disable this? I've searched on Google already but so far nothing is helping and I can mostly only find info about Knox...
EDIT: It was goddamn Knox all along... And I just disabled it by means of SuperSU. Finally!
Click to expand...
Click to collapse
Lolol, see your finding your way on your own ^_^, I was about to give you this link and suggest you to read the comments as well
http://www.w0lfdroid.com/2013/12/Fix-Root-Problem-on-Android-4.3-for-Galaxy-S3-S4-Note2-Note3.html
Unfortunately for me I don't have Note 2 =(, I have an S II Plus, I hope to get Note 2 next month can't wait =S
Banutu said:
Lolol, see your finding your way on your own ^_^, I was about to give you this link and suggest you to read the comments as well
http://www.w0lfdroid.com/2013/12/Fix-Root-Problem-on-Android-4.3-for-Galaxy-S3-S4-Note2-Note3.html
Unfortunately for me I don't have Note 2 =(, I have an S II Plus, I hope to get Note 2 next month can't wait =S
Click to expand...
Click to collapse
Heh, yeah, all is well in my world once again!
The Note 2 is a great device man. I am sure you'll love it. The Note 3 looks great also, but I don't like the ribbed sides (I'm fussy) and last I read there's an eFuze that goes off once rooted or something along those lines. That's sh!t.
invertedskull said:
Heh, yeah, all is well in my world once again!
The Note 2 is a great device man. I am sure you'll love it. The Note 3 looks great also, but I don't like the ribbed sides (I'm fussy) and last I read there's an eFuze that goes off once rooted or something along those lines. That's sh!t.
Click to expand...
Click to collapse
What do you think about the new oneplus one, do you think I should get that instead?
Sent from my GT-I9105P using Tapatalk
Banutu said:
What do you think about the new oneplus one, do you think I should get that instead?
Sent from my GT-I9105P using Tapatalk
Click to expand...
Click to collapse
Hmmm, I haven't seen that one... Feel free to PM me a link.
Help Me!
Banutu said:
I'm glad to hear that man, peace ^^
Click to expand...
Click to collapse
My case is the same case of Invertedskull. I already did all steps as you instructed. I wiped data/cache/system and flash a stock room 4.4.2 of Nordic Rom on SamMobile website.
After flashed, the looping still happens. When I put the charger, the looping stops and goes to the main screen normally. Sometimes, it suddenly restarts but not frequently.
OMG! How to stop it. Pls help me.
My Note 2 is N7105 LTE - Optus (Australia)
mroldman281 said:
My case is the same case of Invertedskull. I already did all steps as you instructed. I wiped data/cache/system and flash a stock room 4.4.2 of Nordic Rom on SamMobile website.
After flashed, the looping still happens. When I put the charger, the looping stops and goes to the main screen normally. Sometimes, it suddenly restarts but not frequently.
OMG! How to stop it. Pls help me.
My Note 2 is N7105 LTE - Optus (Australia)
Click to expand...
Click to collapse
If you have access to anything, and don't get JUST the boot loop, then you DO NOT have the same case I was in. You are probably able to recover from this. Try posting on the Tf Forums. The guys over there are "specialists" in Asus Tf tablets, and as you'll see on this thread (http://www.transformerforums.com/fo...-boot-loop-after-doing-routine-cm-update.html), they gave me a lot of help. Not that I was able to recover, but they were awesome dudes.
mroldman281 said:
My case is the same case of Invertedskull. I already did all steps as you instructed. I wiped data/cache/system and flash a stock room 4.4.2 of Nordic Rom on SamMobile website.
After flashed, the looping still happens. When I put the charger, the looping stops and goes to the main screen normally. Sometimes, it suddenly restarts but not frequently.
OMG! How to stop it. Pls help me.
My Note 2 is N7105 LTE - Optus (Australia)
Click to expand...
Click to collapse
mroldman281, You didn't post again, so I don't know, If You found solution, but since I had same simptoms, and after four days of reinstalling different stock roms, wiping and even messing with PIT via Odin etc..I can say, that in my case the reason for boot loop was faulty battery. The phone worked when it was plugged in and restarted soon after i unplugged USB cable, and just lopped afterwards. Replacement battery put everything back in order. And I am one happy Camper!
Hope this info helps someone else with boot loop problem
same problem stuck in bootloop
hey guys i have the same problem bootloop all the time i tryied stock firmware but nothing happend avec i rooted my note 2 and intalled a costom recovery and a many roms but stuck in bootloop i didn't chage baterry , by the way i wiped cache and reset factory and clear dalvick cache but the same always bootloop
what u suggest i do
ps : i can acces to bootloader or download mode it charge normally
woow get back my note 2 lte alone
hey guys i get back my note 2 i don't know how but it was a succes :victory:
first : i tried so many afficial firmware 4.4.2 and costom roms but didn't change the problem of bootloop
then i remembred what version i was in it was 4.1.1 so i download it from sammobiles thenks to them flash it and boooom the note 2 lte start like a charm
i want to thanks everyone for their help even if they didn't help directly but this past 3 days i read almost all the threads about note 2
well i thinks one of the selutions here is to revert back the the original stock firmware like i did so maybe will fix the bootloop
Hi all, hope somebody can rescue me!
I have an N7100. It's been running stock ROM 4.1.2 for ages (rooted). I've rooted and loaded ROMs on a fair few devices over the years, but typically by following step-by-step guides - I'm a noob to all intents and purposes.
Last night I decided to upgrade to 4.4.2.
I did it without performing a wipe first.
Backed up apps and settings using Titanium Backup Pro
Downloaded N7100XXUFNE1 from Sammobile (sammobile.com/firmwares/3/?download=32635)
Loaded it via Odin 3.9
It worked, in a fashion, maintaining most of my data and apps etc, but I couldn't get wifi to turn on and I kept getting error messages saying '[App X] could not be loaded'
I decided to bite the bullet and do a factory reset (by booting into recovery).
I still couldn't get wifi to work, but my bootloader had stayed at ME3, so I decided to apply the latest bootloader (ND3) as I read somewhere that this could be the issue (I wasn't overly concerned about Knox as the phone is almost 2 years old now anyway).
I applied it via ODIN again, except loading the file into the 'BL' section rather than the 'AP'.
Since doing that, it's stuck at the boot screen 'Samsung Galaxy Note II GT-N7100' and the only way to get out of it is to pull the battery.
I can got into 'Download Mode' but not into 'Recovery Mode'.
I have tried applying MJ5 bootloader.
I have tried reinstalling the whole stock again ROM again
I have tried applying Philz_Touch_6.07.9-n7100 recovery
All show as having completed successfully in Odin, but none of them changed anything - I'm still stuck at the boot screen
Does anybody have any ideas of what else I might try?
Thanks
Beardy
beardyweirdy said:
Hi all, hope somebody can rescue me!
I have an N7100. It's been running stock ROM 4.1.2 for ages (rooted). I've rooted and loaded ROMs on a fair few devices over the years, but typically by following step-by-step guides - I'm a noob to all intents and purposes.
Last night I decided to upgrade to 4.4.2.
I did it without performing a wipe first.
Backed up apps and settings using Titanium Backup Pro
Downloaded N7100XXUFNE1 from Sammobile (sammobile.com/firmwares/3/?download=32635)
Loaded it via Odin 3.9
It worked, in a fashion, maintaining most of my data and apps etc, but I couldn't get wifi to turn on and I kept getting error messages saying '[App X] could not be loaded'
I decided to bite the bullet and do a factory reset (by booting into recovery).
I still couldn't get wifi to work, but my bootloader had stayed at ME3, so I decided to apply the latest bootloader (ND3) as I read somewhere that this could be the issue (I wasn't overly concerned about Knox as the phone is almost 2 years old now anyway).
I applied it via ODIN again, except loading the file into the 'BL' section rather than the 'AP'.
Since doing that, it's stuck at the boot screen 'Samsung Galaxy Note II GT-N7100' and the only way to get out of it is to pull the battery.
I can got into 'Download Mode' but not into 'Recovery Mode'.
I have tried applying MJ5 bootloader.
I have tried reinstalling the whole stock again ROM again
I have tried applying Philz_Touch_6.07.9-n7100 recovery
All show as having completed successfully in Odin, but none of them changed anything - I'm still stuck at the boot screen
Does anybody have any ideas of what else I might try?
Thanks
Beardy
Click to expand...
Click to collapse
What happens when you try to reflash the stock 4.4.2 firmware via odin that u downloaded?
beardyweirdy said:
Hi all, hope somebody can rescue me!
I have an N7100. It's been running stock ROM 4.1.2 for ages (rooted). I've rooted and loaded ROMs on a fair few devices over the years, but typically by following step-by-step guides - I'm a noob to all intents and purposes.
Last night I decided to upgrade to 4.4.2.
I did it without performing a wipe first.
Backed up apps and settings using Titanium Backup Pro
Downloaded N7100XXUFNE1 from Sammobile (sammobile.com/firmwares/3/?download=32635)
Loaded it via Odin 3.9
It worked, in a fashion, maintaining most of my data and apps etc, but I couldn't get wifi to turn on and I kept getting error messages saying '[App X] could not be loaded'
I decided to bite the bullet and do a factory reset (by booting into recovery).
I still couldn't get wifi to work, but my bootloader had stayed at ME3, so I decided to apply the latest bootloader (ND3) as I read somewhere that this could be the issue (I wasn't overly concerned about Knox as the phone is almost 2 years old now anyway).
I applied it via ODIN again, except loading the file into the 'BL' section rather than the 'AP'.
Since doing that, it's stuck at the boot screen 'Samsung Galaxy Note II GT-N7100' and the only way to get out of it is to pull the battery.
I can got into 'Download Mode' but not into 'Recovery Mode'.
I have tried applying MJ5 bootloader.
I have tried reinstalling the whole stock again ROM again
I have tried applying Philz_Touch_6.07.9-n7100 recovery
All show as having completed successfully in Odin, but none of them changed anything - I'm still stuck at the boot screen
Does anybody have any ideas of what else I might try?
Thanks
Beardy
Click to expand...
Click to collapse
Have you tried flashing TWRP instead? This happened to me and got stuck on recovery boot, CWM and Philz Touch wonb't load. Flashed TWRP and worked like a charm.
I am having similar problem.
Tried to flash the TWRP Recovery from THIS via Odin.
Still phone isn't going past the Galaxy Note II logo.
Sidz4u said:
What happens when you try to reflash the stock 4.4.2 firmware via odin that u downloaded?
Click to expand...
Click to collapse
Thanks for the reply.
It processes OK and Odin says 'Pass!', but then it automatically restarts and gets stuck at the boot screen again. Still can't boot into recovery mode.
AliverMD said:
Have you tried flashing TWRP instead? This happened to me and got stuck on recovery boot, CWM and Philz Touch wonb't load. Flashed TWRP and worked like a charm.
Click to expand...
Click to collapse
Thanks for the suggestion. Just tried that, but unfortunately it just does the same thing ....
Man do this.....
Get older odin (personally my preferance nothing else)
Flash the latest stock rom that u have
It will say pass and the device will go into bootloop
Now remove battery any stick it in (just to stop bootloops)
Enter recovery (that shld be stock now)
And do a factory reset
If no recovery......get a custom one and do it
Then let the phone do its thing:good::good:
---------- Post added at 10:36 AM ---------- Previous post was at 10:32 AM ----------
If u have any wifi or other issues.....flash the new bootloader. ....with AP not the BL...and done....
Hope this helps......cheers:good:
devrog17 said:
Man do this.....
Get older odin (personally my preferance nothing else)
Flash the latest stock rom that u have
It will say pass and the device will go into bootloop
Now remove battery any stick it in (just to stop bootloops)
Enter recovery (that shld be stock now)
And do a factory reset
If no recovery......get a custom one and do it
Then let the phone do its thing:good::good:
---------- Post added at 10:36 AM ---------- Previous post was at 10:32 AM ----------
If u have any wifi or other issues.....flash the new bootloader. ....with AP not the BL...and done....
Hope this helps......cheers:good:
Click to expand...
Click to collapse
Thanks for the suggestion. I've tried doing just that (although not on an older version of Odin) and it hasn't helped, I can't get into recovery.
I will give flashing the Bootloader a go via the AP rather than BL when I get back from work tonight though. Cheers.
beardyweirdy said:
Thanks for the suggestion. I've tried doing just that (although not on an older version of Odin) and it hasn't helped, I can't get into recovery.
I will give flashing the Bootloader a go via the AP rather than BL when I get back from work tonight though. Cheers.
Click to expand...
Click to collapse
Yes try with older odin.......and also flashing bl via AP
Hope it helps......
DO HIT THAT THANKS BUTTON IF U FEEL I TRIED TO HELP U......
devrog17 said:
Yes try with older odin.......and also flashing bl via AP
Hope it helps......
DO HIT THAT THANKS BUTTON IF U FEEL I TRIED TO HELP U......
Click to expand...
Click to collapse
Just tried, but to no avail again. Thanks anyway. Anybody else got any suggestions as to what I might try? I'm starting to lose hope a bit here
Try to boot in recovery and do a factory reset
devrog17 said:
Try to boot in recovery and do a factory reset
Click to expand...
Click to collapse
Hi, I do appreciate you're only trying to help but, as explained numerous times in the thread, that's my whole problem.
In summary:
The phone gets stuck on the boot screen
I can't boot into recovery
I can only get into the odin download screen
Flashing a full stock rom doesn't change anything
Flashing Philz, TWRP or CW Recovery doesn't change anything
Reflashing the bootloader doesn't change anything
C
beardyweirdy said:
Hi, I do appreciate you're only trying to help but, as explained numerous times in the thread, that's my whole problem.
In summary:
The phone gets stuck on the boot screen
I can't boot into recovery
I can only get into the odin download screen
Flashing a full stock rom doesn't change anything
Flashing Philz, TWRP or CW Recovery doesn't change anything
Reflashing the bootloader doesn't change anything
Click to expand...
Click to collapse
Just to close this thread off, I've now paid to get the phone sorted at a local shop. Took them a while (think their first level support just tried all the things I'd already done), but their occasional staff member and all round guru managed to get it sorted. I don't know what he did as I didn't get the chance to speak to him. Cost me £30.
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.
Okay so heres the dealio. I am not a noob been rooting, flashing etc. since Cyanogen was actually Cyanogen back in the G1 and Mytouch days. I have read every tutorial available. I have tried Kies, Odin, different USB cords, various drivers, nandroid backups etc. I was on the 5.0 unoffical cyanogen rom I think it was 12-08 or 06. NB4 "MODEM" had the coveted MDL Baseband. I was running CWM recovery. was setting alarms whole screen turned bright pink and froze so I pulled battery waited several minutes, rebooted and it would make it to cm splash screen then go pink and reboot.
First thing I did was try all of my nandroid backups none did any good. Of course I wiped everything before restoring
Second tried several Roms I know worked I always keep a couple on SD just in case ones I have tested and are working
Third I tried to Odin to MDL passed boot loop did this several times with sd and without I even uninstalled kies to make sure no interference
After that I just started climbing firmware mk2, NB4, NH7 all same results. I did each one multiple times evry which way you can imagine
I tried multiple Roms 4.4.2 4.4.4 etc to no avail
Finally I tried Kies. Kies Upgraded me to NK2 still boot loop. Odin NK2 still boot loop.
I have tried super wiping then installing boot loop
I can get into DOWNLOAD MODE AND RECOVERY MODE NO PROBLEM. I can flash custom recovery through odin no problem I have tried Cwm I have tried Twrp. Twrp gives me more options.
Now I have had some success.... If I do it perfectly I usually have to format everything with aromas mega wipe takes a few attempts I can get Danvdh GE 4.4.4 Rom to boot but it constantly vibrates if i do anything like reboot it or anything back to boot loop.
I have checked my pit file and compared to a stock pit everything matches perfectly so I dont think any partitions are screwed..
Knox is tripped who cares its past warranty I am on NK2 firmware. I dont care if I am stuck on stock or some custom rom. I need my phone to work just dont have money to buy a new one.
Please help me. I am not a noob if I have to rebuild the whole system using ADB I will just need some guidance.
****UPDATE***** Currently Have SOPK 4.4.4 from Unified Dev up and running.... No audio at all, much more stability, occasionally freezes will bootloop unless plugged into usb on computer.
***********LOGCATS************* https://drive.google.com/folderview?id=0B479jD3Q_BOvZWYtRDZ2bjBZN2M&usp=sharing
Try this. Flash MDL baseband, flash NK2 with Odin, reboot to recovery and factory reset. After that perform a reboot and see if it works. This has seemed to work for a few people that had updated just the baseband and then later tried to flash full firmware and got stuck in bootloops
do you happen to have link to MDL baseband I have the NK2 firmware
I did find this I want to make sure I have the right one http://forum.xda-developers.com/showthread.php?t=2282342
Also am I flashing these back to back then reboot or flash MDL reboot to download then flash NK2? Just dont want to screw myself any further. Thank you very much for your help Thanks button hit 100x
Yeah that's the one, and just flash the modem, once it's done, do a battery pull, boot straight back into download mode and flash it again. After that, flash full NK2 firmware
Tried it twice with Odin 3.07 and 3.09 still looping.
I do remember having to push the NB4 Modem with ADB while maintaining the MDL baseband if that has anything to do with it.
I saw a pink screen scenario once after water damage on my nephews s4 (not saying you have water damage ) but phone never recovered, not even after disassembly and clean, had limited function, had to be replaced.
Pp
There was never water damage. Its hard to believe that its hardware since I can get dl mode and recovery no problem. But anything is possible. I only get the pink screen now when I try to reflash the 5.0 Cyanogen
ok right now ive got Danvidh GE 4.4.4 pure nexus up and running. its doing a little vibration loop every 30-60 seconds. i have a bug report for whoever wants it. i also have a recovery log from twrp. i'll leave it up and running until i get some advice. i do know if i reboot itll kick into boot loop.......
Update: Ive got about 15 minutes of logcat. and it did reboot on its on back into rom still doing the vibration loop. it freezes randomly no audio. Ill keep running logcat and keep this puppy up till I hear from someone.....
Ok so I'm posting from my SGH-M919. The one with problems. Here's what I think happened, I think while on The 5.0 CM ROM I received the lollipop OTA. This is just a guess as I'm seeing people have been getting OTA notifications for this Device. I'm not sure what I should do. I've done extensive debugging. All hardware looks good from what I can tell. I have tons of logcats and debug files for anyone willing to help. As of now still running DanvidH. 4.4.4 GPE pure nexus version baseband NK2. The vibrations continue. Apparently its due to Google play service update in the last 24 hours and this ROM. Since its literally the only thing that will run on here I'll keep it for now. It freezes constantly, cannot use it as a phone either as it just freezes on the way to dialer. Anyway hopefully someone can help...... Thanks
Sent from my GT-I9505G using XDA Free mobile app
Can you share a link to this 5.0 cm rom?
Just curious.
### Edit ###
Never mind just found it in development.
Pp.
---------- Post added at 09:21 AM ---------- Previous post was at 08:35 AM ----------
Just looking over this 5.0 Cm rom I get the impression that this is chuck full of bugs, since the beginning back on 11/13 and just 2 hrs ago op posted an update with potential bugs still present. If I had to have a reliable operating phone this is one rom I wouldn't touch.
Any input from op?
Pp.
http://forum.xda-developers.com/showthread.php?t=2539361&page=458 just got uploaded last night follow instructions explicitly look at last or so post
Can you check what bootloader and modem you have now? Upload the logcat right before the reboot happened
OK so I am able to run the 5.0 much more stable. Dialer crashes no audio at all system or other wise. It froze then rebooted and back to bootloop which logcats do you want i couldnt get catlog to run on 5.0 but I have about 3 hours worth of logcats from the 4.4.4 pure nexus. what logcats would you like. I also have adb setup and http://www.xda-developers.com/android/advanced-logcat-published-as-a-standalone-tool/ it was running great on 4.4.4 but couldnt get it to retrieve on 5.0
I did get about 2 hours of smoothness from 5.0 just no sound and dialer crashes no one else reporting issue. Texts work fine
NK2 boot loader with Twrp recovery
whats really really weird is I have to connect the phone to computer after flashing to get it to actual start the rom