Related
If im running the 2.2 leak version and am having bootlooping issues and am unable to get into clockwork, can I just SBF to official 2.2?
yes you can
Cool reason I asked is because I did it last night and it just keeps boot looping now tried to flash it about 3 different times. Any suggestions as to how i can get it going? The SBF file fully flashes to the phone RSD doesn't give any errors and reboots phone as it normally would but when it starts up it just boot loops I actually left it going for about 30mins last night to see if it would strat up, so far it has not.
Just to make sure- and I know this is a lame question - but just to make sure - you are using the new 2.2 SBF...
VRZ_MB810_2.3.15_1FF_01
Yeah the SBF im using matches that file name. It was late last night so only really got to try and flash it a few times and im stuck at work now just trying to see if anyone else had any similar issues really. Also im on windows 7 64bit if that may cause any issues.
You may want to try wiping the data and cache from the default recovery. Power on your phone with the home key pressed and press the search key. You'll have options for wiping data and cache. Maybe you could still have remnants of the 2.2 leaks in there?
Sent from my DROIDX using XDA App
I think I tried that last night will do again to be sure though and thanks for all the help.
when I SBF'd back to stock 2.2 I had to boot back into recovery and apply the update.zip, once I did that it booted back up without issue.
Lol facepalm. The update.zip heh, did not try that yet. Gonna try it as soon as I get home and ill update when I do. Thanks for all the suggestions.
Got it to boot after doing factory reset thanks again for all the help
Hi guys,
I think I finally managed to brick my phone. Everything was working perfectly fine, until today when decided to try GB's Steam kernel.
So a little background first, to make things quicker:
- I was able to open download and recovery mode before, even after doing a odin3 one click restore twice.
- I've tried a Cognition and moved to DarkyYtt3r. Went from 7.0.1 to 7.5 to 7.8 to 8.0.1, no issues.
- Changed the kernel and modem several times. The last one I tried was glitterball's uc/ov stable (no charging death).
- Current set up before this mess:
-- ROM: DarkyYtter v8.0.1 > http://forum.xda-developers.com/showthread.php?t=890429
-- Kernel: gb-reorient-fixed-ocuv-f-cwm.zip > http://forum.xda-developers.com/showthread.php?t=887315
-- Modem: TLJL3 I think.
Everything working beautifully.
Today I saw this thread: http://forum.xda-developers.com/showthread.php?t=903238 ... gb's steam kernel. since no one was having major issues, I made a backup of my current rom using CWNand decided to install the kernel using SGS Kernel flasher, according to instructions.
Cool. I've flashed kernels before a few times. No big deal. And I figured, I'm able to get into Recovery or worst case scenario into download mode. I flashed the kernel, reboot, got into Steam's recovery. Looked around. Activated a couple of tweaks although I don't remember which ones.
Rebooted and this is where the issues began. I got the "intro" window you get with i9000 roms (keyboard intro, syncing, etc). A lot of apps were force closing, including facebook, twitter, rom manager, ADW Launcher, etc.
Ok, so I rebooted to Steam recovery and deleted the cache. Went back and the same problem. At least I was able to boot the system.
I said, oh well, let's go back to our backup. Booted Steam's recovery, and tried to recover from the last backup.
It worked for one boot. Not sure what I did, I don't remember, but after trying to boot again, the phone displays the AT&T screen, the GT-I900 screen and then the Galaxy S screen. I then feel the force close vibration, and the screen goes black. I can touch the softkeys and they blink, but I feel the FC vibration every 10 or 15 seconds.
Somewhere along the line something bad happened.... but here is what's bothering me. I cannot get back into download or recovery mode anymore. Been there all day trying to make it work with no luck at all.
So, more importantly, somewhere along the line, between rom flashes, or something, I lost the ability to get into recovery or download mode. I've heard that I900 roms have different button combos, but nothing works
I'll buy a few resistor packs tomorrow, and some cables just in case. I'm afraid that I won't be able to boot into download mode this way either.
also, adb is not detecting the phone. tried both windows and linux. if I could only get it even for one second so I can send a adb reboot download... but no
Do you guys have any ideas?
Thanks!
cumanzor said:
Hi guys,
I think I finally managed to brick my phone. Everything was working perfectly fine, until today when decided to try GB's Steam kernel.
So a little background first, to make things quicker:
- I was able to open download and recovery mode before, even after doing a odin3 one click restore twice.
- I've tried a Cognition and moved to DarkyYtt3r. Went from 7.0.1 to 7.5 to 7.8 to 8.0.1, no issues.
- Changed the kernel and modem several times. The last one I tried was glitterball's uc/ov stable (no charging death).
- Current set up before this mess:
-- ROM: DarkyYtter v8.0.1 > http://forum.xda-developers.com/showthread.php?t=890429
-- Kernel: gb-reorient-fixed-ocuv-f-cwm.zip > http://forum.xda-developers.com/showthread.php?t=887315
-- Modem: TLJL3 I think.
Everything working beautifully.
Today I saw this thread: http://forum.xda-developers.com/showthread.php?t=903238 ... gb's steam kernel. since no one was having major issues, I made a backup of my current rom using CWNand decided to install the kernel using SGS Kernel flasher, according to instructions.
Cool. I've flashed kernels before a few times. No big deal. And I figured, I'm able to get into Recovery or worst case scenario into download mode. I flashed the kernel, reboot, got into Steam's recovery. Looked around. Activated a couple of tweaks although I don't remember which ones.
Rebooted and this is where the issues began. I got the "intro" window you get with i9000 roms (keyboard intro, syncing, etc). A lot of apps were force closing, including facebook, twitter, rom manager, ADW Launcher, etc.
Ok, so I rebooted to Steam recovery and deleted the cache. Went back and the same problem. At least I was able to boot the system.
I said, oh well, let's go back to our backup. Booted Steam's recovery, and tried to recover from the last backup.
It worked for one boot. Not sure what I did, I don't remember, but after trying to boot again, the phone displays the AT&T screen, the GT-I900 screen and then the Galaxy S screen. I then feel the force close vibration, and the screen goes black. I can touch the softkeys and they blink, but I feel the FC vibration every 10 or 15 seconds.
Somewhere along the line something bad happened.... but here is what's bothering me. I cannot get back into download or recovery mode anymore. Been there all day trying to make it work with no luck at all.
So, more importantly, somewhere along the line, between rom flashes, or something, I lost the ability to get into recovery or download mode. I've heard that I900 roms have different button combos, but nothing works
I'll buy a few resistor packs tomorrow, and some cables just in case. I'm afraid that I won't be able to boot into download mode this way either.
also, adb is not detecting the phone. tried both windows and linux. if I could only get it even for one second so I can send a adb reboot download... but no
Do you guys have any ideas?
Thanks!
Click to expand...
Click to collapse
Did you ever get this problem fixed? The reason I ask is because I'm in this same situation.
We seem to be having the same problem also... Nothing has worked for me so far
http://forum.xda-developers.com/showthread.php?t=960419
Pull your battery, pull your sd card, hold the volume button and plug in the usb cord, this will get you into download
Sent from my GT-I9000 using XDA App
Keep hope alive glaze!
Sent using XDA App
Im going to get a jig hopefully all goes well.
I've been looking all over this site but I can't find anything. I suppose that it's partly because I'm not sure about the problem myself.
A couple of months back (maybe more) I upgraded to the ICS infinitum rom (blue version) with midnight kernel. It was great - the phone worked fine. Well I'm exaggerating, it ****ed up every once in a while. Programs would automatically shut down and it would get really slow after a while. But all in all it wasn't bad, and it was stable enough for me most of the time....
Then, last Thursday everything seemed to go apart, every program on the phone was shutting down. So I thought I'll just restart and it will be fine. When I did, the phone did not come back on. the kernel would load and then it was stuck on the start-up animation in infinite loops.
Now, to be frank, this isn't the first time this has happened. So I didn't panic. Last time I just used the CMW recovery to re-install the kernel and the rom (I keep the files on the sd card). But this time, I wanted to try to avoid the factory wipe for as long as I could, and try finding a different option, knowing that if all else fails, I have something to revert back to.
Then I did the mistake of deleting the init.d file without re-installing anything. I wanted to, but accidentally clicked on the 'reboot now' option. And then all went to ****. The kernel didn't load. I went to recovery and it couldn't mount the sd card so I couldn't re-install it.
I tried flashing a new kernel using odin, and it did get me a bit better: my CWM recovery can read the sd. However, I still can't mount the system. Even worse, when I get to the infinitum zip roms and re-installing it brings up the status 7 error (which, after searching, seems to come up for different reasons for each person)
Despite installing a new kernel, when I reboot the phone now it doesn't load the kernel anymore, it just stays stuck on the welcome screen. I tried using the recovery to re-install a different kernel, it worked, but the phone still won't start - it now automatically skips to the recovery mode. I don't know if I should try flashing a rom through odin, and I'm too afraid to try anything at all now...
Can anyone help me? Is there any way to restore the init.d file or maybe that has nothing to do with my problem?
uvii said:
I've been looking all over this site but I can't find anything. I suppose that it's partly because I'm not sure about the problem myself.
A couple of months back (maybe more) I upgraded to the ICS infinitum rom (blue version) with midnight kernel. It was great - the phone worked fine. Well I'm exaggerating, it ****ed up every once in a while. Programs would automatically shut down and it would get really slow after a while. But all in all it wasn't bad, and it was stable enough for me most of the time....
Then, last Thursday everything seemed to go apart, every program on the phone was shutting down. So I thought I'll just restart and it will be fine. When I did, the phone did not come back on. the kernel would load and then it was stuck on the start-up animation in infinite loops.
Now, to be frank, this isn't the first time this has happened. So I didn't panic. Last time I just used the CMW recovery to re-install the kernel and the rom (I keep the files on the sd card). But this time, I wanted to try to avoid the factory wipe for as long as I could, and try finding a different option, knowing that if all else fails, I have something to revert back to.
Then I did the mistake of deleting the init.d file without re-installing anything. I wanted to, but accidentally clicked on the 'reboot now' option. And then all went to ****. The kernel didn't load. I went to recovery and it couldn't mount the sd card so I couldn't re-install it.
I tried flashing a new kernel using odin, and it did get me a bit better: my CWM recovery can read the sd. However, I still can't mount the system. Even worse, when I get to the infinitum zip roms and re-installing it brings up the status 7 error (which, after searching, seems to come up for different reasons for each person)
Despite installing a new kernel, when I reboot the phone now it doesn't load the kernel anymore, it just stays stuck on the welcome screen. I tried using the recovery to re-install a different kernel, it worked, but the phone still won't start - it now automatically skips to the recovery mode. I don't know if I should try flashing a rom through odin, and I'm too afraid to try anything at all now...
Can anyone help me? Is there any way to restore the init.d file or maybe that has nothing to do with my problem?
Click to expand...
Click to collapse
I suggest flash 3-file GB rom via odin with ticked re-partirion and phone bootloaderupdate.
First of all init.d has nothing to do with the boot of kernel and ROM itself. It's just like autostart in Windows, so if it's missing it shouldn't cause problems.
My solution is to flash a complete stock Gingerbread ROM using Odin. You can get them at sammobile.com. Then afterwards flash a custom kernel and then whatever you like.
If you need help,feel free to ask me
Sent from my Gameboy Color
Yes! Thank you! That worked!!
It happened again! just 10 days later.
Is the Infinidtum rom ****ed up in any way?
it's stuck on the loading part of the rom
Yes yes it seems Im totally ****ed. Looking at a GS II X now for $230, I was on Boypes CM7, then went to CM10 Official without data wipe, worked fine, and then went to AOKP without data wipe, worked fine, then went over to CM10 unofficial without data wipe, worked fine, but WiFi wasn't working anymore, I guess somewhere in the go over to AOKP stage I messed that up, whatever, I didn't wipe data its cool Ill just flash another JB Rom and it should be all good so I flash CM10 Official and nothing, just bootloop.
So now im thinking, HMM I'll just go into recovery and start fresh with CM7 and leave it there til CM10 is stable, but of course my G-Key is broken and Im pretty sure CM10 Official doesnt even have G Recovery, so NOW Im thinking well it seems Im ****ed.
So NNNNNNNNOW Im like well, I'll have to plug it into S/W Update mode and let that LG Updater Tool take me back to Froyo, so I did it, but bootloop.
Now Im scared. And I remember Oh yes, the wonderful Smartflash tool and that completely fun method, so I dl Canadian Koodo .kdz, get it over to CP/AP FLS/BIN whatever and plug it all in and set it up and its all good to go and what do you know, it STILL won't get past bootloop.
It's possible to end your OB folks, just saying, don't feel too invincible.
Edit: My G-Key works, just have to press really hard
Do you know that forst boot takes time?
Leave it for about 7 mins
You could have installed titanium back up via sd card mate and recover
If you did erase entire cp, i'll probably do the work but your imei won't be here!
If they fix it and still no imei...make as if you didnt know xD
theaks30 said:
Do you know that forst boot takes time?
Leave it for about 7 mins
You could have installed titanium back up via sd card mate and recover
If you did erase entire cp, i'll probably do the work but your imei won't be here!
If they fix it and still no imei...make as if you didnt know xD
Click to expand...
Click to collapse
I dont understand what you mean sorry
But yeah I left it booting for about 30 minutes
Don't worry. He's mistaken. You can't accidentally wipe CP with flashing you need to forcefully do it in Smart Flash Tool. If you get bootloop your phone is recoverable. If it is bootloop when phone buttons flash on and off slowly the whole time. If no LG logo appears and no lights then it dead though.
Do this to get into SW Update
Code:
Take the battery out.
While Holding Vol-up plug it into your computor (Keep holding up until it says SW Update)
Use a Tool Like Smart Flash Tool to Recover. Here's a [URL="http://forum.xda-developers.com/showthread.php?t=1448803"]link[/URL]
I've done that twice, still bootloop with blinking leds
If its that you in the picture. Thats normal, Well, Hot People always suffer from over heating objects (a)
No its not I have a **** and balls, I find it funny that you want to hit on some random guy on XDA though lol...
I didn't want to make a new thread. But I've searched high and low.. And nothing has been answered. So here's my story. I have a note 4 sm-n910T. When I rooted the phone everything was fine and good. I then decided to give it to a family member. I flashed it back to stock.. All was fine for a while but it started acting up. Like randomly turning off and not responding to a charge or any commands to turn on into other modes... I had flashed stock again. All was good.. Till now. My madre and received a Ota update, downloaded and installed the update. When I pressed ok to reboot new update. The phone never came back on. So I went through all the fun stuff. I tried kies.. Kies days unsupported device connected.. There is however talk between the two because it's pushed errors onto my phone as well as has tried to download the stock rom. But every which way I've tried it fails. Next. I decided to go for custom roms... And flash cf-chainfire auto root. Then twrp.. Then install supersu.. Then a rom from twrp. Now here's where it gets interesting. Nothing would pass odin if I had auto-reboot and f.reset time checked.. Any and all roms.. Files..etc would only pass with auto reboot checked and f. Reset time unchecked. At first everything seemed ok.. I was able to actually get cm 12.1 installed as well as gapps. But only the one time.. Which you'd think was good enough. But here's what has happened and what I can't seem to fix. The phone yesterday after having everything installed and sitting at home untouched.. I came home clicked the home button.. And it came on.. I scrolled a few pages.. Thought.. OK cool.. Let's get madres Sim card in and call it a night.. When I turned the phone over.. (didn't even take our the battery) tried to see if I could fit the sim in.. Which didn't.. I then turned the phone back around just Cuz I wanted to make sure it was awake.. The screen was black.. I figured it was in sleep mode.. So I hit the home button.. No response.. I hit the power button.. No response. .. The phone had turned itself off.. And when I tried to turn it on it wouldn't. Now mind you the phone has these weird phases where when I try to install or flash a rom and it fails.. And I'm forced to remote battery.. A good portion of the time it won't turn back on.. Sometimes it can be instant.. Others.. A few mins.. Sometimes even longer for it to respond.. Right now I have been accessing twrp.. Wiping all data.. Davik...cache.. System.. One by one.. Then installing a rom.. I go for a reboot.. And I get a black screen. I need help.. I'm running out of ideas and basically just fishing random idea attempts. I'm no scared to brick it.. So all ideas are welcome. Plz. Thank you.
Malistoff said:
I didn't want to make a new thread. But I've searched high and low.. And nothing has been answered. So here's my story. I have a note 4 sm-n910T. When I rooted the phone everything was fine and good. I then decided to give it to a family member. I flashed it back to stock.. All was fine for a while but it started acting up. Like randomly turning off and not responding to a charge or any commands to turn on into other modes... I had flashed stock again. All was good.. Till now. My madre and received a Ota update, downloaded and installed the update. When I pressed ok to reboot new update. The phone never came back on. So I went through all the fun stuff. I tried kies.. Kies days unsupported device connected.. There is however talk between the two because it's pushed errors onto my phone as well as has tried to download the stock rom. But every which way I've tried it fails. Next. I decided to go for custom roms... And flash cf-chainfire auto root. Then twrp.. Then install supersu.. Then a rom from twrp. Now here's where it gets interesting. Nothing would pass odin if I had auto-reboot and f.reset time checked.. Any and all roms.. Files..etc would only pass with auto reboot checked and f. Reset time unchecked. At first everything seemed ok.. I was able to actually get cm 12.1 installed as well as gapps. But only the one time.. Which you'd think was good enough. But here's what has happened and what I can't seem to fix. The phone yesterday after having everything installed and sitting at home untouched.. I came home clicked the home button.. And it came on.. I scrolled a few pages.. Thought.. OK cool.. Let's get madres Sim card in and call it a night.. When I turned the phone over.. (didn't even take our the battery) tried to see if I could fit the sim in.. Which didn't.. I then turned the phone back around just Cuz I wanted to make sure it was awake.. The screen was black.. I figured it was in sleep mode.. So I hit the home button.. No response.. I hit the power button.. No response. .. The phone had turned itself off.. And when I tried to turn it on it wouldn't. Now mind you the phone has these weird phases where when I try to install or flash a rom and it fails.. And I'm forced to remote battery.. A good portion of the time it won't turn back on.. Sometimes it can be instant.. Others.. A few mins.. Sometimes even longer for it to respond.. Right now I have been accessing twrp.. Wiping all data.. Davik...cache.. System.. One by one.. Then installing a rom.. I go for a reboot.. And I get a black screen. I need help.. I'm running out of ideas and basically just fishing random idea attempts. I'm no scared to brick it.. So all ideas are welcome. Plz. Thank you.
Click to expand...
Click to collapse
Also how important is f. Reset time? I don't totally understand it. Next.. What about having the roms and files I flash on internal memory instead of sd. I'm not sure if I can access the Internal storage. But if I can does that help. Also I cannot access Android at all.. I can either access download mode or recovery. I have been using an external battery charger to charge my battery as well. Due to it doesn't read the charge... But! It did read a charge just fine when I had cm 12.1 working.
I would suggest:
1) In twrp wipe system, both the cache's and also data
2) use ODIN to install the stock Note 4 ROM
see -> http://forum.xda-developers.com/not...uide-odin-to-stock-unrooted-firmware-t2957156
3) When it is finished unplug the usb from your computer as the phone is rebooting
NOTE you might want to uncheck Reactivation Lock in Settings - Security first
w8wca said:
I would suggest:
1) In twrp wipe system, both the cache's and also data
2) use ODIN to install the stock Note 4 ROM
see -> http://forum.xda-developers.com/not...uide-odin-to-stock-unrooted-firmware-t2957156
3) When it is finished unplug the usb from your computer as the phone is rebooting
NOTE you might want to uncheck Reactivation Lock in Settings - Security first
Click to expand...
Click to collapse
Answering question one.. I do that already. I wipe everything one by one except sd... Answering question two. I have tried that already and odin fails.. However I'm sure if I tried to flash the rom and didn't check f. Reset time it might work. But as for flash stock.. I have tried several times.. I can't say one error or another I'd a cause because I get a different one each time.. What is the purpose of f. Reset time in Odin? I've searched it and to me the explanation didn't make since.
Malistoff said:
Answering question one.. I do that already. I wipe everything one by one except sd... Answering question two. I have tried that already and odin fails.. However I'm sure if I tried to flash the rom and didn't check f. Reset time it might work. But as for flash stock.. I have tried several times.. I can't say one error or another I'd a cause because I get a different one each time.. What is the purpose of f. Reset time in Odin? I've searched it and to me the explanation didn't make since.
Click to expand...
Click to collapse
Reactivation is unlocked. Also I wouldn't be able to change any setting in the phone.. As the phone does not boot into Android. I was just lucky enough to have usb debugging active before this all happened
I am not sure what that is for
But every time I have done a flash it works if you use the steps I had there. (Not really questions)
Sorry I do not have anymore ideas.
---------- Post added at 02:38 PM ---------- Previous post was at 02:37 PM ----------
Are you booting your phone into download mode before you use ODIN?
(I know it's proly a dumb question but just in case)
Yes I am in download mode when using odin.
Malistoff said:
Yes I am in download mode when using odin.
Click to expand...
Click to collapse
Just now I did another full wipe and wipe of cache, davik, system, internal memory and had a successful install of cm12. 1 with gapps.. Everything installed.. Clicked reboot and the phone never came back on. I will try your idea next. I have not tried an idea where I use twrp to wipe everything and reboot into download then do stock rom via odin. If the phone does boot into download from twrp recovery I will try this one time with auto reboot and f. Reset time checked.. If it fails I will try it again with f. Reset time unchecked. I am currently not by my laptop to try this so it will have to be much later in the day.
To boot into download mode: Power off Note 4, hit all 3 of these at the same time until it wakes and vibrates - Power Button, Home Button and Volume Down
I know how to do that lol. I know I'm a junior member. But I'm somewhat intermediate. So cm12. 1 has booted.. However it didn't from a reboot of a flash.. I just took a while shot.. And powered the phone on.. And it booted.. I'm pretty sure in going to run into the problem again.
OK - Well you never know!
I am only a senior member 'cause I am older than Dirt!
Lol. I'm oldish. And trust me this lucky catch I got.. Is temporarily. There is still boot issues. I fear when the phone goes off or is turned off that it won't come on. I do not have a sim card in the phone at the moment which means I can download helpful apps. Like supersu. .. But so far I was able to check settings and get what I can prepared. Also if like to keep this thread open as a log or research tool.
Alright so I like the rom sit most the day.. With minimal to no use.. Most of the day it was fine.. At one point I took a picture and it did as it should.. I cleared all open tabs.. Took another picture and I got a error saying camera wasn't connected.. Finally the phone froze up and rebooted.. And the Camera worked.. Gave it another rest.. Came back to it checked the camera and it was fine.. I put it away for like 10mins then decided to check recording. When I did the phone was not responding to turning back on from sleep mode. Now for as long as I can remember even before this initial issue started.. I was having thr same problems with the phone not coming back on from when in sleep mode.. I dunno what the cause is or hoe to approach it to fix it.
First attempt was to put it to a charger... Registered no charge.. So I removed the battery.. Gave it a few mins.. Pushed down power button.. No response. Something is off with the boot menu.. Like the boot img. File
And finally it's back on.. Normal boot.. I didn't boot from download menu or recovery.. But in all honesty I'm 100% sure this will just happen again.. It seems to happen when I put the phone in the charger.. Then take it out and play with it.. For now in going to let it sit till the battery is in caution. Then charge it. I still have not added the Sim and loaded apps.. I feel that will be a overload of cpu and will most certainly freeze up and crash the phone
Ok, so up to date now.. Here's what's going on. The phone struggles to reboot from any on screen commands.. Like if I'm in Android.. And hold power.. Click reboot.. Then say like recovery.. Or anywhere.. It just turns off... If I also do this in twrp.. Say like install a rom or supersu.. It won't reboot... But! After it turns off.. And I wait a while and power it back on.. The file.. Rom etc was installed. So I do now have supersu installed and busybox. But the issue remains..which is a unstable OS.. Nothing to do with it being custom os.. But there is something wrong with the booting process.. What can I download if any apks.. Or files to help this?
Malistoff said:
Ok, so up to date now.. Here's what's going on. The phone struggles to reboot from any on screen commands.. Like if I'm in Android.. And hold power.. Click reboot.. Then say like recovery.. Or anywhere.. It just turns off... If I also do this in twrp.. Say like install a rom or supersu.. It won't reboot... But! After it turns off.. And I wait a while and power it back on.. The file.. Rom etc was installed. So I do now have supersu installed and busybox. But the issue remains..which is a unstable OS.. Nothing to do with it being custom os.. But there is something wrong with the booting process.. What can I download if any apks.. Or files to help this?
Click to expand...
Click to collapse
Might be stupid I know, but try wiping clean your SD card (back up a copy on your pc first) as well when you factory wipe and make sure that after that, you only add the files you need for recovery. Start up the phone after reset. To get a backup, if you're synced through google, you'll get everything back. If not, only copy your backup from titanium back into your SD card.
I went through a very similar situation last week. Long story short, it seemed the SD card had copied files which would interfere with the system.
Curious, did it happen after marshmallow update?
And did you try to downgrade back to previous lollipop version?
I assume it was Marsh that I was trying to Ota too. I was unable to boot successfully after that first try, so I honestly don't know.. I'm going to try your SD card idea. .. But once all that's done. Are you wanting me to redo a full rom install like through and wipe system, Davik etc etx? Or like wipe everything and start from like odin installing a recovery and so forth?
I ask these questions because.. What if I was to just take the sd card. And format the whole thing.. And out it back into the phone? I mean I might try that first then the other option.
Malistoff said:
I ask these questions because.. What if I was to just take the sd card. And format the whole thing.. And out it back into the phone? I mean I might try that first then the other option.
Click to expand...
Click to collapse
Well even if you format and you put the SD card back in with all previous files, same might happen.
When you format, just wipe all. Then if you want to downgrade, you need to have the previous version bootloader and baseband FIRST prior to putting the firmware ROM.
A simple (restore) wipe would just keep you at current version. And you can't easily downgrade the easy way from marsh to lollipop. Believe me, I learned the hard way
Flash through ODIN