Ok well first i gotta say sorry if this is the wrong thread, first one tho.
So, 2 days ago i got a i9001 and it was already rooted.
I installed cwm via odin(cuz i wanted cm10) but little did i know the cwm was messed up
when i first booted into it i saw "E:Can't mount /cache/recovery/command" since im kinda noobish
in all of this i ignored it(i still do, dunno if that was the cause)and when i rebooted from cwm just to
get into the android system to call a friend before i start installing cm10, the phone booted into cwm
again, i though i pressed smth so i rebooted again, and then i knew it was a stuck bootloop.
Then my brain made up this weird conclusion that if i install cm10 and gaps maybe it will fix the bootloop
.. so i did and it did nothing, i wiped the dalvik cache and everything, and then in a german forum i found
this little thing "9001_stock_recovery-signed.zip" i flashed it with cwm aaand now, every time i boot it
with the power key, it shows the samsung first logo, that only says SAMSUNG and then it goes black
it does nothing after that, if i try to volume up+power it boots past the samsung logo but goes into some
box with an arrow coming out of it and some android logo, if i try to enter download mode, it says RAMDUMP
MODE Cause: Force Upload.
Thats all i can give as info. If anyone has the good heart to help me.. please do so.
And please be really specific like ur explaining to a total newcomer.
have a read here http://forum.xda-developers.com/showthread.php?p=30415128
Thx, but i just lost all hope, after i fixed everything.. Installed a stock 2.3.6 i tried to flash another cm10,by
Some doomsday dude and the camera wsnt working so i decided to try the other cm10 that bricked my
Device , after flashing it and gapps i pressed reboot system and after it went black to reboot i expected
The usual samsung logo but unfortunately it never came, the phone is now literally a brick, no sign of
Life i tried to get the battery off and press the power button for some minutes.. Nothin happens..
IceVip said:
Ok well first i gotta say sorry if this is the wrong thread, first one tho.
So, 2 days ago i got a i9001 and it was already rooted.
I installed cwm via odin(cuz i wanted cm10) but little did i know the cwm was messed up
when i first booted into it i saw "E:Can't mount /cache/recovery/command" since im kinda noobish
in all of this i ignored it(i still do, dunno if that was the cause)and when i rebooted from cwm just to
get into the android system to call a friend before i start installing cm10, the phone booted into cwm
again, i though i pressed smth so i rebooted again, and then i knew it was a stuck bootloop.
Then my brain made up this weird conclusion that if i install cm10 and gaps maybe it will fix the bootloop
.. so i did and it did nothing, i wiped the dalvik cache and everything, and then in a german forum i found
this little thing "9001_stock_recovery-signed.zip" i flashed it with cwm aaand now, every time i boot it
with the power key, it shows the samsung first logo, that only says SAMSUNG and then it goes black
it does nothing after that, if i try to volume up+power it boots past the samsung logo but goes into some
box with an arrow coming out of it and some android logo, if i try to enter download mode, it says RAMDUMP
MODE Cause: Force Upload.
Thats all i can give as info. If anyone has the good heart to help me.. please do so.
And please be really specific like ur explaining to a total newcomer.
Click to expand...
Click to collapse
THIS - to go back to stock firmware
After flashing CWM and you get stuck in a bootloop into recovery, do THIS.
Additionally, read from HERE and HERE
Good Luck
I have the same issue, I took my phone to a service and even JTAG failed, it seems the emmc is broken. How can a ROM update physically damage the memory?!
eminence84 said:
I have the same issue, I took my phone to a service and even JTAG failed, it seems the emmc is broken. How can a ROM update physically damage the memory?!
Click to expand...
Click to collapse
JTAG has failed?
The emmc-chip has a special function for erasing partitions. this function is only useable by kernels over 3.x. it is bad that our emmc-chip has a bug. when using this function of the chip to erasing the data partition, the chip damages itself. the data partition cant be used anymore.
for more infos read in the threads and in the links for sgs2 and note.
if i'm wrong please correct me
So is there absolutely nothing I can do to recover my phone?
i would say no.
but if you store the data partition on ext.sd and make a rom that can use it, it is possible to use the phone as normal... like Ivendor did for a short time (if i'm right?)
Can you please detail the steps, what should I do?
Right now the phone is hard-bricked, absolutely no signs of life, can't enter download mode, nothing.
does odin detects your phone? nothing on the screen?
Not sure about Odin, but besides that nothing on the screen, not even when plugging the charger. I took it to a phone service to rewrite the memory with JTAG, and they said it hangs at about 20% and the memory is damaged. I don't understand, the phone is almost new, all I wanted was a lousy update from CM9 to CM10...
i assume that the problem at 20% was the damaged emmc data partition
edit:
but theres a big chance that i'm wrong and your chip is really fully broken. maybe you get the people at service center to be interested in your phone. maybe they can give you more information.
i don't know my phone is working.
what recovery had you installed to update? what did you do? wipe data/cache,... ?
Yes, probably. So, you say there's a posibility to use an external SD card as data partition?
edited my post...
eminence84 said:
Yes, probably. So, you say there's a posibility to use an external SD card as data partition?
Click to expand...
Click to collapse
yes, but you must be able to flash roms to your phone,.as example.by odin.
or the JTAG repair center can flash roms?
Probably they can, but I think I'll buy a JTAG interface and study this myself...
eminence84 said:
Probably they can, but I think I'll buy a JTAG interface and study this myself...
Click to expand...
Click to collapse
I think it takes a lot of time to know how things work...
what if your phone memory is completely dead? the you have bought the JZAG box for nothing...
but for sure it will be interesting how it works.
how much does such a interface cost about? (^^ more than a quarter of a phone? )
I found one at about 12$... I think it might be worth a shot
But yeah, I'm aware it would take some time until I can handle it well, and I'm not sure I have it.
I also considered buying another i9001, but I'm not sure what caused mine to fail, I want Android 4.1 in the new one, too, it really bugs me off I don't know the exact cause of the failure, so I won't repeat it again. I did everything exactly by the steps I found here on the forum, I used ivendor's ROM and updated CWM to 6.0.2.8.
be sure it is not only an adapter.
someone knows if you can write parts of the memory with something like these?
Related
It won't start unless plugged it shows empty battery. sometimes when i unplug it stays connected. In usb settings if choose mass storage it seems to get in a loop of connect-disconnect. I have tried flashing different roms but it didn't fix. Any idea of what is happening? Could it be hardware problem?
I've got the same problem, I've tried every kind of wipe, flash with repartition, clearing stats and so on. I'm starting to suspect it's a hardware issue. The Phone seems to always think it's plugged into USB no matter what, it keeps rebooting to the battery icon over and over until I plug it onto a power source and then it boots fine.
After that I can get it back to normalish by rebooting with the power disconnected using the extended power menu in Darkys Rom.
Can anyone help? When I get back from my trip I'll likely flash it back to stock and send it in for repair, or just ***** at bell and get another new phone.
I'm having the same issue, I've searched all over internet and I found other posts with the same problem.. and no one has found a solution for this.
I think is a hardware problem. after having this I've bought a chinese compatible battery, and when I put that battery in, the phone boots up without even pressing the power on button, so weeeird!
With the original one.. there is no way to boot up without plug the phone. I've had the phone working well for more than 5 months
if someone finds a solution please tell!
thanks in advanced!
I had the some problem and more. I did something and this one has gone. I think i replaced a new update.zip in the phone and that solve it but i am not 100% sure. My phone starts normal but when its off sometimes the battery still flashes. In a week or so i will send it to waranty i think.
grofudaniel said:
I had the some problem and more. I did something and this one has gone. I think i replaced a new update.zip in the phone and that solve it but i am not 100% sure. My phone starts normal but when its off sometimes the battery still flashes. In a week or so i will send it to waranty i think.
Click to expand...
Click to collapse
what did you did? so do you think it's a software problem?
I tried to use a non-original battery and when I put in this new battery, the phone boots up without even press any button. so something it's really wrong. if I try the same with the original battery.. nothing happens, the screen is black unless I plug the phone to the charger.
well, at least I can boot my phone without plugging it this way.
I look forward to know more details about this issue.
thanks!
I look forward to know more details about this issue.
Search loads of posts on this topic . Dont know if problem solved or not .
jje
JJEgan said:
I look forward to know more details about this issue.
Search loads of posts on this topic . Dont know if problem solved or not .
jje
Click to expand...
Click to collapse
unfortunately I've done the search in this forum and I haven't found any solution for this, I can't believe it!
regards!
This problem is back again. I can`t start the phone unless it is plugged. I am with the nervs down at this moment.
what makes me crazy is to not know if it's a software or hardware failure!
in my case seems to be a hardware problem unless the phone recognize the non original battery and that makes a software change that makes the phone to boot.
I'll wait until the gingerbread update, and if after update it doesn't work, I will bring the phone to samsung repair point.
I see that I'm not alone with this problem.
Maby if i could connect the phone on usb to pc i would do something but that dosent work either for me so god have mercy.
I had that problem for a few weeks. Went away with a firmware change. Flashed back to stock and then docs rom. No idea what it was. Just went away.
Are you sure the battery is charged? I had the exact same problem on cm7, turned out my battery ran flat overnight
Sent from my GT-I9000 using XDA Premium App
Try this:
Format all your mounts in recovery mode with Clockworkmod. You can do this by going to 'mounts and storage' and formatting boot, system, data, cache. I did sdcard and sd-ext to be sure).
When you have done that install a 2.2.1 stock rom and the problem should be fixed. From here you can install custom rom's again.
Also try disabling any lagfixes (also via CMW)
KeesKaas said:
Try this:
Format all your mounts in recovery mode with Clockworkmod. You can do this by going to 'mounts and storage' and formatting boot, system, data, cache. I did sdcard and sd-ext to be sure).
When you have done that install a 2.2.1 stock rom and the problem should be fixed. From here you can install custom rom's again.
Also try disabling any lagfixes (also via CMW)
Click to expand...
Click to collapse
OK, I'll do that thanks for the suggestion.
I only have one more doubt left, If I do that, after formating everything in clockworkmod.. What does it happens to the phone? is it going to be able to boot after formating all of this? I'm asking this because I don't know how to download the official rom without using kies and the phone booted up and connected via usb cable.
thanks so much!
I've got the same problem.
I thought it was me trying to flash JVK, but after flashing and reflashing 2.2.1 and 2.3.3 and back with bootloaders the problem stayed. I'll try the format "everything" from CWM, hope this will work.
Still abit strange
(BTW I recently was in sub 15 degrees temperatures, surely this isn't the case??)
I had a problem like this where I was getting USB connected coming up again and again and my phone not starting when it wasn't plugged in.
This sounds dumb and I may just have been lucky but I turned USB debugging off and it stopped, left it off for a day or so, a couple restarts later I thought I'd see if it was still playing up so re-enabled it and nope everything's ok again. That was a couple weeks ago and so far so good, I hadn't seen any reports of anyone else with this.
Might be worth a try
Oh I'm using Darkys 9.5 by the way
My problem got worst! My phone would not charge at all until i reflashed. It now charge and boot normaly without to have it plugged, but my pc don't recognize it, not even in download mode with odin. I quess it has something to do with the hardwhare because both times the problem started when i charged it in the same plug.
i had the same problem,I just cleaned the usb port,plugged in the cable without connecting it to the pc or power source,and it started now it's ok
Me too
Another victim of this issue.
I was running a Darky Rom when I first noticed it... I think I was on Ficeto's 2.3.5 JVT. s
I have tried several steps to rid myself of this issue, with no success:
1. Reflashed ROM CWM
2. Reflashed Kernal CWM
3. Factory Reset, format internal SD, & ODIN flash Stock ROM.
4. Wipe & Flash Juwe ROM.
5. Each time, I also wiped the Dalvik Cache and battery stats.
I have tried leaving the battery out for a lengthy period, I have tried draining the battery all the way down, charging all the way up.
At least with the Launcher I am using now, it has the "Reboot" option instead of just turn off. However, I have to make sure I have a USB cable close by and charger in the car all the time now, just in case it runs out of juice or locks up for some reason and needs a battery pull.
Frustrating... Of course, the warranty expired the end of October.
If anyone has successfully completed the recommendation of formatting boot, system, data and cache and flashing stock Froyo? If you have done it, PLEASE post your detailed steps and the result so we don't waste time repeating something that won't work.
I was eyeing the SGS 2, but with all of the issues the market went through with the SGS, I am thinking maybe I should get away from Samsung...
MM
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...
This is yet another thread on an GT I9000 stuck at boot, but with a twist!
The diference is that it hapened without me doing anything to it. No flashing roms, no rooting, no unlocking, nothing.
One day it turned itself off, turned on again, get pass the initial screen, gets pass the carrier animation, and it is stuck at the big shiny S screen.
I'm not new to XDA or to flashing (old windows mobile), so I decided to come here and look as usually I can find my answers. The thin is it seems no one else has a similar problem! Not here nor the entire web!
I've been searching and experimenting (it doesn't work anyway, so it is ok to test every solution) for 2 consecutive weeks and still nothing!
I am able to get into download mode, into recovery mode, I am able to flash rooted (or rooting) kernels, I can do everything (except update from SD card with Cyanogenmods, it always says the file is BAD).
I've flashed stock roms, following all the procedures, with Odin, with Heimdall, I've tried everything suggested by "Android Solutions" but nothing!
I'm really frustrated, so I'm reaching to see if there's someone that can shine some light on how to solve this... I feel I'm about to smash the thing with a hammer! (but this won't solve the problem, right...)
Thank you in advance
G
GAlves said:
(except update from SD card with Cyanogenmods, it always says the file is BAD).
Click to expand...
Click to collapse
I assume you had rooted and had CWM when trying to flash CM from SD cards? if not, it will not work, using 2e or 3e recovery
First powerdown, pull out Battery, SIM CARD, and EXT.SD card, press power button for a minute, than powerup without SIM and Ext.SD Card....Do remember to backup your contacts, data, images etc and also your EFS folder before flashing a ROM and make sure you have more than 50% battery charge before you attempt any sort of flashing.
Also assume you had tried everything in My Android Solutions did not get you out of bootloops?
so, boot into CWM > mounts and Storage> to copy your entire SD card to PC, after which you should format every partition (you will in-effect lose everything by doing this,) and do not reboot
after this, you must pull out battery and powerup into download mode to flash JVU+Root ROM with 512 PIT (repartition and update boot loader ticked in odin3) from My Android Collections
Hi xsenman,
Thank you for the reply.
in fact, I tried to CM from the SD card after having flashed CWM rooted kernel with Odin, but at this point the phone was not booting anymore. The whole reason I wanted to flash it in the first place was because it started bootlooping by itself while completely stock.
So I came here to xda, and follewed the instructions. I thought it would be a simple matter of flashing with a new rom and everything would be a-ok. It didn't.
I've tried every single trick mentioned in "my android solutions" (great information repository by the way, lots of work there) and still nothing. Today when I get home (forgot the phone at home) I'll flash the stock everything and try to follow the SD format procedure you mention.
I'll post back
Cheers
G
Hi again,
I've tried xsenman's suggestion and still nothing.
I could understand if this was a SD card error (because it was damaged in some way), but I have no indication of a SD card error. It can read everything and I even can see the file structure inside the SD card (and I do not mena the external SD card ofc). I was even able to copy some files to and from it!
I think I'll "fix it" with a big hammer and buy me an iphone! This is soooo frustrating!
anyone has any other ideas? I'll try anything and everything.
Cheers
G
GAlves said:
in fact, I tried to CM from the SD card after having flashed CWM rooted kernel with Odin, but at this point the phone was not booting anymore.
Click to expand...
Click to collapse
CM needs to be flashed twice, try this method or this
Check Here to chose your forum/Guide by Version of your phone or you will have more problems by using wrong solutions due to different versions of Galaxy S
Use only ROM and solution for your model and Wipe x3
But First powerdown, pull out Battery, SIM CARD, and EXT.SD card, press power button for a minute, than powerup without SIM and Ext.SD Card....
(Do remember to backup your contacts, data, images etc and also your EFS folder before flashing a ROM and make sure you have more than 50% battery charge before you attempt any sort of flashing.)
Hi again,
Tried everything and got always the same result. Nothing.
Maybe the problem was with some piece of hardware (but I find it strange). As I said before I firstly tried to flash it because it had come to a bootloop by itself so maybe it had a deeper problem.
Now I got it solved. I bought me a brand new iPhone 5 (LOL) and flashed a stock rom on the SGS and sent it to the carrier customer support. It had one year guaranty. Lets see what they say about it.
If they can solve it I'll have 2 very nice phones!
Thank you anyway for you help.
Had same problem some time ago.
THIS should help you too
Hi again!
I had tried that too, and the result was the same as all the other things I've tried. Nothing.
Today I had some feedback about the phone (I sent it to repair). The phone is on its way back to my hands, and the repair status says:
"Software update and power circuit repair. Tested OK".
Let's see if it does tests ok when I get it back!
Two weeks ago I got an e-mail from the tech support asking what was wrong with the phone because they could find nothing wrong with it. I asked them to turn it on and try to make a phone call for example, or connect to a wi-fi network. It doesn't really matter, I just wanted them to try to do something that involved turning it completely on and use the device in any way they wanted. Clearly they hadn't even tried to turn it on. Otherwise they would have figured out that there was a problem...
This was the carrier support, not Samsung (I think). Anyway it SUCKS bigtime!
Now I need to figure out what to do with it...
Thanks anyway for your support!
Cheers
G
Just to let people know how this ended up.
My SGS i9000 went to the repair shop for two times. The first they replaced the charger plug, the second they say they replaced nothing (but I don't belive them )
As I still think this was some sort of issue with the samsung firmware, I just flasher CM10 and it's been stable since then.
My girlfriend got it as a present and she's quite happy with it!
Thank you all for the help!
Hey people, I have been on this forum and using the CM12.1 ROM by New Maclaw since it came out, but I'm afraid my S3 Mini is dead now Saturday night it turned off by itself while charging, and it wouldn't turn on again. I let it charge a little, and after a while it turned on again, but was stuck on the CM12.1 boot animation. I tried rebooting multiple times, but it always got stuck on the boot animation. I tried booting into TWRP, but it got stuck on the Galaxy SIII Mini splash screen and wouldn't even go any further.
I was getting my hopes up when I saw download modus still working, so I flashed TWRP again with Odin, but nothing changed. I flashed the entire CM12.1 package again with Odin, but it had no effect whatsoever, can't boot into TWRP and regular boot is stuck on CM boot logo.
Since I had no options left, I decided to follow this guide: [GUIDE] Unroot / Unbrick, Flash official stock firmware on Galaxy SIII Mini GT-I8190 to flash original ROM again, first flashing the original recovery as linked in the thread, then the ROM itself, and checking after each step if anything changed. But even after I flashed the stock ROM, it would show the CM 12.1 boot animation on boot, and recovery was still not working at all. I continued by flashing the params.tar as linked in the post, but my phone still shows the CM 12.1 boot animation, and I can't get any further
What's really concerning to me is the fact that all the flash operations via Odin are going through, I get a PASS every time, but it doesn't seem to have any effect, so I'm afraid the memory chip on my phone has died There are so many great minds in here that know everything about this phone, maybe someone has an idea to help me get my trusted S3 mini back
Super weird. It's not soft bricked, it's completely f#cked up:laugh: OK, have you tried to remove the battery for some minutes!? Or go in recovery through adb instead!? If you have a backup (that's why, we always need a backup) maybe you can restore it through adb. Search on XDA for adb tutorials or something like that or some case like yours. I want to believe that you're not the first one with that issue. I know that's frustrating when we don't know what's going on. Good luck
mauam said:
Super weird. It's not soft bricked, it's completely f#cked up:laugh: OK, have you tried to remove the battery for some minutes!? Or go in recovery through adb instead!? If you have a backup (that's why, we always need a backup) maybe you can restore it through adb. Search on XDA for adb tutorials or something like that or some case like yours. I want to believe that you're not the first one with that issue. I know that's frustrating when we don't know what's going on. Good luck
Click to expand...
Click to collapse
I don't really care about backups, all my important data is on the SD anyway, I just want to bring the phone back to life if possible at all.
While on the CM12.1 boot screen I can find the phone with adb, but since I never set up adb my computer is unauthorized, and I can't authorize it without being able to boot. I'm not all that familiar with adb, I asked some people, but nobody has an idea how I can authorize my computer without having access to the phone system.
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