Related
Ok so I did the 1 click root and flashed the newest cyanogen mod and then put the enoch theme on, and I realized that I couldnt make any phone calls, so I tried to flash the new radio and I did the update.zip thing.
after that it showed a picture of the g1 with an arrow coming out of a box then it rebooted to the system recovery and now it says "formatting cache...."
what do I do?! im freaking out (((
Now when I reboot it gets past the "G1" screen and to the mod screen then it just goes to a black screen.
HELP ME SOMEONE!
Also since using the 1 click root method, Do I need to flash a new SPL and Radio?
if so, which are the newest?
Ummm. That's normal
It's normal for it to stay at a black screen!?
For awhile, if it takes longer than 5 mins, just pull the battery out and reboot, if still hangs just wipe and reflash your rom
ok ok cool
im reflashing the radio, how long should it say "formatting cache"
Normaly just a minute, up to 5, I just did the one click root for a guy yesterday and when I flash the hard spl for him and it hung for 10 so I just reboot and it was fine
Do I need to flash the SPL first before the radio?
No, you do not have to, if upgrade to the danger spl, than radio first, and your not making calls issuse was prob on account of the theme and not the radio, so reflash rom
I just wiped the phone and it just loads too the android screen and then to black
idk what to do
Did you wipe and before you ask, wiping does not wipe your radio or spl, they are lower in the system, so wipe, and flash rom
how do I re flash the rom?
I cant hook my phone up to the USB to put the rom file back on
How do I flash the rom if I cant mount my phone to the USB to put the rom file on it
Go to your recovery options list, goto in the console, hit enter when it comes on, than type ums_enable to mount your phone, put rom on, type ums_disable to unmount then typ reboot
You are my god!
10 billion thank you's!
What should I do after I re flash the rom, should I try to flash the radio and SPL then put a theme one?
Enjoy your phone, that' all, you only have to upgrade to the danger spl if you want to use a hero rom or jac's xrom, if not you do not need to upgrade the spl
One last question, How do I fix the problem with the enoch theme
When I put it on my phone it wouldnt let me make calls and it make my MMS service force close
It might be an issuse with your theme, try another one. Another important console command is fix_permissions whenever you get force closes or when you wipe, it fixes the ids of your apps, mostly paid ones
Ok cool, I really liked that them but its not worth that scare again.
Thank you soo much, I would have been so lost without the help.
No problem, just read up, learn more about how android works, than help the next person
Hi guys,
Tried to upgrade from Darchdroid 2.6.5 to 2.7 today and am now stuck with an unusable phone.
I get a boot loop OR I get stuck on the HTC boot screen for 20+ min. I'm not sure why I get stuck on either one.
This advice was given to me today in the 2.7 thread:
hold down menu+back+power and do a hard reset.
then wipe everything. [EVERYTHING ext4, ect.]
then flash DD2.7
then flash GoogleBits.
good luck.
edit: this has the newest kernel.
__________________
Click to expand...
Click to collapse
The problem is, in order to complete a hard reset, you have to reboot the phone!(right?) But when I reboot, I just get stuck on the HTC boot screen. Is there wiping instructions (i.e. do I need to do certain things from adb instead of the phone?) that I'm missing out on?
Thanks so much. Really loved 2.6.5. Don't know why I keep getting suckered into updating
A hard reset is the same thing as doing a factory reset. So, go into recovery, go tinto the wipe list, and wipe everything on that list. Then, flash it and reboot.
HeroMeng said:
A hard reset is the same thing as doing a factory reset. So, go into recovery, go tinto the wipe list, and wipe everything on that list. Then, flash it and reboot.
Click to expand...
Click to collapse
Thx, Heromeng. Did exactly what you said - wiped everything possible in AmonRa 1.7 and now I'm back to a boot loop.
Some further info: When I was upgrading from 2.6.4 to 2.6.5, Darch said I should push the boot.img from 2.6.4 to make things work. That did the trick for the last update (although I don't know why!).
Is pushing the boot.img from 2.6.4 the way to get 2.7 to work on my phone?
Alright, I went ahead and pushed the boot.img from 2.6.4 and now it's working. I guess it's just like 2.6.5.
My question:
What am I sacrificing by using this boot.img instead of the one from 2.7? I'm not clear what the trade-off is.
Thanks again.
Back up your sd card, then repartition it.
Sometimes ramswapz corrupts the sd card, so you have to format it and repartition before being able to flash a new ROM.
---------------------------------------
There isn't enough of a difference between the kernel where your phone shouldn't boot.
Decad3nce said:
Back up your sd card, then repartition it.
Sometimes ramswapz corrupts the sd card, so you have to format it and repartition before being able to flash a new ROM.
---------------------------------------
There isn't enough of a difference between the kernel where your phone shouldn't boot.
Click to expand...
Click to collapse
Decad3nce: I've re-partitioned it 3 separate times and every time it's a boot loop! Would you tell me if I'm doing this all in the correct order?
-Wipe everything.
-Re-partition sd card
-Enable USB toggle
-Move 2.7 and Googleshits from computer to Phone
-Flash ROM
-Flash googleshits.
-Reboot.
note: I was able to boot into 2.7 with the (pushed) 2.6.4 boot.img but I wasn't able to start wi-fi. So I'm assuming the 2.6.4 boot.img had something to do with that and that's why I'm trying a "virgin" 2.7 flash again.
All I can say is I'm in the same boat. It seemed to me, in my earlier tinkerings, that my phone needed a boot.img that was slightly less overclocked. The few DarchDroid successes I've had were from lower-clocked boot.img's. Without it, I just look at the HTC logo forever.
bohiti said:
All I can say is I'm in the same boat. It seemed to me, in my earlier tinkerings, that my phone needed a boot.img that was slightly less overclocked. The few DarchDroid successes I've had were from lower-clocked boot.img's. Without it, I just look at the HTC logo forever.
Click to expand...
Click to collapse
That's really helpful info, Bohiti. I thought I was alone here!
I am in 2.7 now with the 2.6.4 boot.img but I'm unable to start wi-fi.
This is a dealbreaker for me.
Why would the boot.img affect wi-fi??
Well sorry, kind of. While what I said was true, I just now tried the hard reset suggested to you. (Menu+Back+Power). And then I wiped everything and flashed 2.7 and GoogleShits. And it booted fine, quickly. Only on HTC screen for 10 seconds maybe.
So I'm not in the same boat, though in the past I've had the same symptom with my phone. I haven't rebooted again, maybe I just got lucky.
Darch made changes to his kernel(so it boots at a higher frequency); your phone probably can't handle it then.
Bug him, jus10o, or me(tomorrow) about making a 710mhz bootable.
Decad3nce said:
Darch made changes to his kernel(so it boots at a higher frequency); your phone probably can't handle it then.
Bug him, jus10o, or me(tomorrow) about making a 710mhz bootable.
Click to expand...
Click to collapse
Thanks decad3nce. I will do just that! And thanks for the info, bohiti.
Finally some positive news!
sariamanascar said:
Thanks decad3nce. I will do just that! And thanks for the info, bohiti.
Finally some positive news!
Click to expand...
Click to collapse
I lied. it defaults at 710 on boot. But, try booting 2.6.7 with no sd card in your phone. (do a full wipe, I mean everything)
Decad3nce said:
I lied. it defaults at 710 on boot. But, try booting 2.6.7 with no sd card in your phone. (do a full wipe, I mean everything)
Click to expand...
Click to collapse
OK, just tried this two different times.
No boot loop(!) but now it just hangs on the HTC logo.
Any other ideas?
Bout to go ask Darch and jus10o for ideas....Btw, should I PM them or create a thread?
Thanks again for your help.
sariamanascar said:
OK, just tried this two different times.
No boot loop(!) but now it just hangs on the HTC logo.
Any other ideas?
Bout to go ask Darch and jus10o for ideas....Btw, should I PM them or create a thread?
Thanks again for your help.
Click to expand...
Click to collapse
already told jus10o, but feel free to pm him or Darcj anyways. one of us just needs to compile a kernel that defaults and limits itself under 710.
Decad3nce said:
already told jus10o, but feel free to pm him or Darcj anyways. one of us just needs to compile a kernel that defaults and limits itself under 710.
Click to expand...
Click to collapse
Just PM'd them myself. Thanks for the help, Dec.
Has this issue been addressed? I am having the exact same issue. I have flashed just about every rom on XDA and never had any issues, but I am having the same problem with 2.7 and Buffed2.0...both overclocked kernels. On 2.7 if I do a few battery pulls the phone somehow gets past the HTC logo but everytime I reboot i get the boot loop again.
I have never had any issues like this so I have never had to pull a log. If this would be helpful i would be glad to do it but would need directions on how to.
For all future visitors: Dec was kind enough to modify a kernel that got GPS and Wifi working for me - so thanks Dec. Problem was, GPS eventually started crapping out and I had a whole bunch of force closes over the past week. Including my phone app even crashing on me.
Today, I finally gave up on 2.7 and am on to PureHero which is largely AOSP and (for the non-OC'd version) a lot more stable. While I don't like the look as much, for those of us on weak phones, I think it's the best option.
I had the same issue, but flashed the uv kernel and it booted fine ever since. Couldn't run 2.7 till then.
stand corrected
I recently flashed the UV kernel and I have to say, everything works great. I stand corrected - no one told me the uv kernel was the same thing as "under clocking" a a kernel but I guess that's what it does. Thx.
Worked for me too
Hi just wanted to add that the UV kernel also solved my bootloop problems with DD 2.7.
A few times before the UV I was lucky, and after the 2nd or 3rd iteration of the bootloop it would get past the htc screen and boot. Happened enough times to get hooked on 2.7 haha But the last time I rebooted the phone it was very stubborn and stayed stuck no matter what I tried. That sent me searching back here. Glad I found your post, I assumed the UV kernel was only for those having battery issues, based on the main 2.7 thread.
Hey guys i don't know if anyone of you had the same issue but any info/help could be helpful.
I used to flash my N1 A LOT! but today i have this strange issue. I wiped and flashed rodriguezstyle again for a clean start, but i only got the colorful X with the unlocked symbol at the bottom and then just a black screen. i thought I've done something wrong and flashed again, but with the same results.
i changed my sd and downloaded again the rom but still no luck, did a nandroid restore and the phone was working properly. then i got a bit frustrated. downloaded 2-3 more roms but the result was the same.
i read somewhere that flashing with battery <50% may cause some errors so left the phone off to fully charge and tried again... no luck
then i remembered i upgraded the radio and i downgraded it to the old one, but still the same results and nandroid doesn't work... jeeeesh... back to the new radio and to my nandroid, but its no fun owning a smart-phone if you cannot flash it.
anyone with the same issue or any helpful tips/instructions?
Try this:
When the phone hangs at boot, reboot to recovery, wipe cache and dalvik-cache and reboot from recovery. Does that work?
If not, you'll need to logcat the boot process and post the log somewhere for us to have a look at.
So, assuming adb is working on your computer, plug in via usb, use adb logcat > output.log and reboot the phone. Continue logging for about 60 seconds after the phone stops.
Post the log to www.pastebin.com and then link back here.
hmmmm ok i will post results in abt an hour. thanx!
hmmmm i think i sorted it out... reflashed recovery. propably i messed smthing in there! thanx for your effort!
Hello everyone!
Weird problem here, too.
I was backing up my SD card in view of a format/cleanup....and when I went to boot into recovery, my N1 was stuck on the black screen with the white letters at the bottom "Build : RA-nexus-v1.7.0.1"... The phone actually boots great, it is just not loading the recovery image. Is it possible that part of the flash got corrupted? If so, I'm pretty much done flashing my N1, right???
I'll post a log asap (if it could help any)...
Oh and btw i tried to re-flash Amon-RA's recovery twice already...Superboot said it was successful....but I doubt it...
Well try flashing stock rom! I flashed it through fastboot step by step and it worked. Also check if the rom you try to flash needs ext partition or if apps2sd is enabled
Sent from my Nexus One
Test
Sent from my Nexus One using XDA App
Thanks nica.
I had to flash stock boot and rom to fix it...
Sent from my Nexus One using XDA App
Okay...I'm at a loss. I've spent the last two days trying to root and install the deck gingerbread. I've focused on this page http://forum.xda-developers.com/showthread.php?t=694572 and this one http://forum.xda-developers.com/showthread.php?t=902493 and successfully rooted. However, that's where I'm stuck. I flashed the recovery.img (and since it rebooted, assumed that it took) and now want to complete the instructions for gingerbread from here http://forum.dev-host.org/viewtopic.php?f=9&t=7. Brackets after each step from that page describe my problems.
1. Reboot into recovery. [I assume I can do this? Because I flash_imaged recovery.img? If it doesn't hang, however, it just launches the phone into apparently normal state?]
2. *optional* make a nandroid backup. [I never got an option to do this. Ever.]
3. Wipe Everything. [I don't have an option for this anymore. I did at one time? It's no longer in the boot menu.]
4. Flash gingerbread rom zip. [I would love to. How? I have no options for this. No command prompt options.]
...and I'm stuck.
5. DO NOT REBOOT YET.
6. Flash gapps zip.
6a. Flash Kernel *if you are using a custom kernel*
7. Reboot.
8. Enjoy gingerbread!
When I reboot I either get a fastboot menu or hboot, neither of which have options other than each other, resetting device, booting into recovery (which 5/10x hangs the phone).
I would LOVE to know why this isn't working (e.g., my phone doesn't have options listed on these instructions) or what I could do to fix it. Believe me, I know there are instructions all over, and I've probably read most of them today. I'm going crazy trying to figure this out. On top of it all, ROM Manager/Toolbox won't even work because the free Manager is off the market. If anyone could help, I would be very grateful. I have adb installed on my PC, if that helps.
Thank you! I am totally frazzled.
eta: GRRRR I knew that if I posted here I'd find the answer on my own. Turns out the recovery image I was using was apparently wrong (but appeared to work correctly) so that's why I wasn't getting the error. Think things might be okay now...got the menu and am busily installing. Sorry for the interruption...
Well.....
Did you ever get it done?
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