Cant Reboot Into Recovery - G1 Q&A, Help & Troubleshooting

ok today i copied about 5 files to my sd via usb cable. then held down the power key to reboot and held home till it came back on. it did not boot into recovery. so i pulled the battery out and tried again still nothing. i do have fast boot and i can still power on my device and use it regular jus no recovery.
i searched around ( xda search and google search ) and came up with this thread closest to my issue. http://forum.xda-developers.com/showthread.php?p=6101871 it made a little sense but does not quiet answer my issue. i am installing adb now incase this is needed in any steps to a booting recovery.
i am running the cm507 test 3 with the adw launcher and the google add on. yesterday i was able to access recovery but this morning idk wut happened.
Any help Please I Need recovery ( Im A Flash Fiend, I Need My Fix )

i found a fix to this issue ( THANKS RENN9420 )
what i had to do was re root my phone and start back at rc29 or drea.nbh this corrected what ever miss hap that was there earlier. if anyone needs help in the future pm me and ill help till its fixed.

How come everyone reroots when they run into a situation such as this?
Did you even try reflashing the recovery image? That's fixes this 90% of the time.
Come on, if you accidentally put sausages on a pizza before you cooked it, wouldn't you simply remove them instead of throwing the pizza away and completely remaking it?
Either way, glad you fixed your problem. Just, next time, look into issues a bit deeper before resorting to rerooting.

Related

I dont think ive seen this before!! Please check this out and help

hey guys, i am not new to the scene but i have actually run into a big problem.
A few minutes ago i flashed a Hero rom followed by the ebi1 kernel, it booted up perfectly fine and went into installation, still no problems.
Once installation finished i learned that for some reason the home app(launcher) doesn't load, it just constantly gives an error force close when trying to go to the home.
Everything else does work.
I then decided to reflash the ROM, when booting my phone it would not go into recovery, i held the home button and it froze at rogers logo,
I tried again after a battery pull and same result, i thought uh oh, BRICK!
When i rebooted again( holding nothing down ) I learned that it apparently does boot! if i leave it alone, it does the whole buttons light up screen dims thing just before it boots, then the screen dies off and I hear a sound meaning usb connected, **(all this while it is still showing the second boot screen)**
The end button works to turn screen off and on but it it stuck at the second (MLGIN or whatever nexus style boot screen)
I nave now found a way to actually get past the boot screen, if i call the phone it will go into the dialer and I can actually use it as a phone!!, once in like this I can actually use the phone completely except for going to launcher(home), I can make calls (if someone calls me to get into the dialer), use the lockscreen, send a message (if someone sends one to me), enable usb mount.
I have a nandroid and a BART saved but like I said i cannot get into recovery.
Any help is GREATLY appreciated.
Please let me know if my post doesnt make any sense, i can try and get my thoughts out again!
EDIT I CAN get Droid explorer to work, this means i can install any apps that could help! but i dont think i could launch them
-with droid explorer i can use terminal, cant i launch stuff with that? also, when i click Bart manager it says i need to buy a license, aww
- I clicked on reboot into recovery in droid manager, the phone rebooted but it hung at the rogers logo, I really cant understand how the recovery doesn't work!
EDIT it WILL boot into fastboot mode!
Can i install an alternate launcher with droid explorer, I think that if i can do this, when i hit home it will give me the option of choosing which laucher right? i then choose the new one.
Any one know where to get a different launcher? or perhaps the launcher from this ROM so i can try and reinstall it
Because i can use droid explorer, the options are nice,
I still need help organising the above attempt, but if that fails I could also use the flash recovery image option in DE and try that.
Am i right in saying that I should first try and get a different launcher to work or should i go straight for the recovery. If the recovery doesnt wokr could I lose access to the phone booting? (thus droid explorer)
OK I would LOVE some community help here:
I think i wave 3 options
1) install any apk (namely a new launcher and get the phone to atleast function properly)
2) Re flash a recovery image
3) Flash a ROM
All of these would be done with droid explorer, i think i have listed them from least risky to most risky (if i flash ROM and that doesn't fix it i could be out of droid explorer)
Could you guys help me start up, where can i get what, my mind is racing too much!!!
ok, using droid explorer i re flashed the recovery, it now boots into recovery. i am going to reflash the hero rom as i really want to use it!

[Q] Phone won't display home screen.

So I was looking through the topics in this part of the forum today, and I saw "[Q] What is causing "Communication Failed" error?" (It won't let me post the link to it?) I followed the link in that topic and did what that guy said would help, and after doing that I restarted my phone. It did all of the startup animations correctly, I can still access the recovery menu out of it, but when I get past the startup animations, I'm just greeted with a black screen. The buttons on the bottom of the phone are lit up, but the screen gives no response. I can't turn it off without taking out the battery, and that doesn't help. If possible I'd like to try to fix this without sending my phone in, or without deleting the user data. Any fixes for this?
I would try re-downloading the ROM you want to use and then re-install it. But maybe there's a better fix, that's just what I've done whenever I encounter something strange.
sschrupp said:
I would try re-downloading the ROM you want to use and then re-install it. But maybe there's a better fix, that's just what I've done whenever I encounter something strange.
Click to expand...
Click to collapse
I can't exactly put anything onto my phone with this problem. I can't access the screen at all past the startup animations. It's just black.
Not Bricked!
You have a few options as it seems your phone is "on" and should be recognized by your computer still.
What was it you were doing to the phone before it started doing this behavior.. wasn't quite clear on that....
If it was a mod to change your framework-res.apk. You can find the "stock" one in the ROM you originally downloaded and revert back to stock by doing an ADB Push to your /system/media folder.
Or... you will need to flash your phone back to stock - which means you will need to go here and download Odin and run it.
Always helps to have that "plan b". Bottom line though - your phone isn't bricked and you should be able to restore it and continue on. But... please note that ODIN will wipe your phone and anything you had on it will go bye bye.
androidforums.com/captivate-support-troubleshooting/217905-cant-connect-t-server-updates.html
I followed the advice on how to fix that problem in the second post in that topic. When I restarted my phone the screen just ended up going black. I'm going to try that Odin thing, I hope it works.
e. It's kinda annoying how I can't post links.
Ok Edit again, I've tried the Odin thing, and it just isn't working. Now whenever I try to put my Simcard back in, It doesn't even do the startup things, it just goes to that Phone Caution symbol PC picture thing. I'm worried that I'd have to go get a replacement.
Can you please provide us with a list of everything you have done to your phone and how you tried to use Odin? That will help us help you. Please be specific, this will get you the help you need. I read the link, did you use ADB or the first method in that thread? Sounds like you messed up while trying to fix your device manager. I am not sure how it is you tried to use Odin, try using a rear usb port, Odin can be a pain, make sure you have the drivers installed.
Ok, Here's a list of what I've done to my phone over the past few days.
1. I rooted it.
2. I kinda sorta half-assed the process of allowing me to put on Non-Market apps onto my phone, I made it so that the settings.db file had the permissions all set up, but I never replaced the first settings.db file. (It's just sitting on my phone's interal SD card.)
3. I tried to do that Non-ADB method listed in that topic I linked to. After that I started having these problems.
4. I accidently ended up clearing the Data cache through the recovery menu thing. Just an accidental moving of the buttons. It didn't seem to effect anything.
5. I booted the phone into recovery mode and tried the Odin thing. It got stuck at File Analysis, and I tried again. It still got stuck, and I let it continue trying it while I was eating dinner. After I got back it was still on that, so I took out the USB cord and phone battery and put the Sim card back in. When I try to boot it up it goes to that PC error phone thing. (I can't exactly get an image of it, I hope you know what I'm talking about.)
And that's all I've done to it. I'd try a different USB port, but I don't have any more. I'd try my other computer, but that's a Linux machine, and Odin is a Windows/DOS executable file. I'm pretty sure the drivers are installed correctly, as I had been doing stuff with the phone via USB just yesterday.
I hope that's enough detail to help figure out something.
I'd hate to doulbe post, but I really really do need the help with this. If any of you have any advice for it all, please, feel free to contribute. If there is no fix for this, and my phone is actually bricked, just let me know so I can go get a replacement.
Did you make sure you had odin started up BEFORE you put your phone in download mode? Odin is very touchy and you have to do things exactly right or it won't work.
Yes, I've made sure to follow all of the steps right to the last peroid. I'm probably just going to have to go get a replacement anyway.

[Help]Milestone keeps repeating android boot!

So right now, my phone keeps on getting stuck at the 'android' word bootscreen. It keeps repeating and seems to go on forever! Someone please help me! I heard its due to rooting! Can anyone confirm this?
What did you do? I tried once to install aps 2 card and the phone stood in android screen about 20 min
Anyway if it doesn't start. Flash new android: nand restore or sbf
.
Sent from my Milestone using Tapatalk
Finally somebody replied back. Its been going on for days, I've removed the battery, placed it back, same thing.
Also, sorry but I have no idea how to flash something. How do I do it? And it doesn't even go past it.
I should spend on time in this sub-forum.
If you have flash a custom ROM then just reflash it or try another ROM.
It's highly, highly unlikely that your phone it breaked so don't worry about.
I have never flashed a custom rom. I don't even know how to flash in the first place.
turn off hp.try to hold up-dpad(towards screen) button and switch on your milestone.
then you see black screen written Bootloader.
battery OK.
OK to program
connect USB
data cable.
if you can go into this screen, then u can start to learn to flash vulnerable recovery.
and ready to install custom room.
google around on how to instal vulnerable recovery for milestone .
under18 said:
turn off hp.try to hold up-dpad(towards screen) button and switch on your milestone.
then you see black screen written Bootloader.
battery OK.
OK to program
connect USB
data cable.
if you can go into this screen, then u can start to learn to flash vulnerable recovery.
and ready to install custom room.
google around on how to instal vulnerable recovery for milestone .
Click to expand...
Click to collapse
Yep, I can go into it. But I checked, and can't find how to install a vulnerable recovery. Any help?
My site is down atm, but this may help;
http://forum.xda-developers.com/showthread.php?t=932196
shut down phone ->hold down hard keyboard x key and power button->when M logo appears release power button but keep pressing x key until recovery mode shows up
there is an option for clearing data/factory reset
you'll loose everything but it propably fix the problem
Including my contacts?
ray243 said:
Including my contacts?
Click to expand...
Click to collapse
your contacts if you have chosen it will be at your Gmail account and they will be restored.

[Q] Boot lopp w/ AP, Plz help.

Droid 4 running Stock Jb 4.1.2, Safestrap 3.11, Liquid smooth 2.9, CM (last stable)
Everything working fine for a number of months, installed Liquid smooth via -> delete romslot 3, create romslot 3, install Liquid 2.8.
It ran for a number of days no problems. Restarted fine, all features worked great, even the annoying random restart from 2.4 went away.
6 - 10 days in, im surfin' the news sites at work, put it down, screen goes black, i pick it up. Hit the power button cause i realize its off and it just boot loops... so bad i had to vol-/+ pwr, go to flash mode and THEN turn it off b/c it just kept trying to restart, hang on logo.
I got home and decided to AP flash the latest:
9.8.2O-72_VZW-18-2
Blur_Version.98.72.182.XT894.Verizon.en.US for the maserati.
Boot looped a few times, i was able to get it to go into recovery mode, after that it loaded up the stock JB system. First boot it crashed and restarted, second boot it loaded but only the keyboard worked, not the touch screen. Went to the in OS option of factory reset mode + delete storage.
Rebooted, worked. Checked it a few boots, everything is fine. I use Druid 4 Utility Xt894 JB version and apply the root. Works great. Install safestrap, Create new partition, install liquid smooth 2.9. Works for an afternoon... at work today the touch screen stops responding, i restart it a few times. I try to enter recovery mode. Now im in boot loop again...
I've tried re flashing it again, a few times. I tried even going down to the previous release of JB for the phone. STILL 4.1.2!!!! But nothing.... it just boot loops... what did i do wrong? It was running great. No tweaks or anything done to it prior to it having its melt down.
Help please.. ive provided as much information as possible and though i only joined XDA now to post for help, i have read it for a long time as my main source for my phone and have donated to both CM and Liquidsmooth teams previously..
help!!!
I can't see where you are doing anything wrong. You have obviously done your research and have a good idea of what you are doing. I see, after you fastbooted, you went back to Liquid. I think I would try running CM10.1 or even stock for a few days and see if you have the issue there as well. If you do than it sounds to me like it might be a hardware issue. If not, maybe try re-downloading Liquid. Perhaps your zip got corrupted somehow.
I would love too. In fact i would be willing to run it on the stock crappy 4.1.2 if i could get it out of boot loop this time...
It just keeps boot looping on the logo. AP Fashboot flash and BP flash work but recovery and normal boot/reboot mode just goes into M logo boot loop.
I've re downloaded the 4.1.2 jb SBFs from 2 different sources to ensure its not a corrupt file, tried 18_1 and 18_2 software versions...
Is there a way to use the abd shell to get into the filesystem and check whats going on? Is the SBF the last call? or is there another route to see whats going on or just flash EVERYTHING? Like completely back to stock?
I can find my way around a PC file system but im not familiar with linux. Please help me understand, Is it like having CMOS and BIOS settings or equivalent to damaged CMOS firmware? What am i not replacing/reverting by SBF and HOW can i replace/revert BEYOND the basic sbf...
If ya point me in a direction or to someone who can help me out i can do all the foot work just point me in the right direction?
Is this applicable? I found a site talking about using CWM in a ADB shell file push to possibly get access to more features?
The article also goes into reading the busybox / ADB command screen? (sorry for not proper jargin) and see what its doing during the boot loop before it restarts?
Id add the link but i need more posts....
Update: Flashed 18_2 again with a "factory cable" i made, let it boot loop a series of times before it started up into the stock system again.
At first, again the touch screen wouldn't work, random lockups and restarts, etc. Since i just got it into the main system again and i had to leave for the weekend for a trip(no wifi or network), i couldn't mess with it all weekend but i left it on the whole time and kept checking its functionality... gradually its come back to full function. Touch screen works and is accurate, no more lockups, no more restarting, even stopped boot looping when i restart and enter recovery..
Im not sure and i couldn't find any forum converstations or write ups to support to idea but i think after a major crash and you flash new or reflash your SBF, it seems the phone needs time to recalibrate and index? Not sure, but just an FYI. Gonna try loading SS and liquid again.

Soft brick help. Twrp installed Android won't boot custom rom

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

Categories

Resources