unit would reboot randomly flashed with rsd lite (4.1.2) random rebooting started shortly after, tried factory reset and multiple reflashings, did lots of research, found common hardware issue with xt875, ordered replacement motherboard from ebay, installed, new os 3.2.4, to my surprise the rebooting started again! so i thought maybe power button sticking, not the issue, could it be same hardware issue with different motherboard? any feedback would be greatly appreciated.
hugh a said:
unit would reboot randomly flashed with rsd lite (4.1.2) random rebooting started shortly after, tried factory reset and multiple reflashings, did lots of research, found common hardware issue with xt875, ordered replacement motherboard from ebay, installed, new os 3.2.4, to my surprise the rebooting started again! so i thought maybe power button sticking, not the issue, could it be same hardware issue with different motherboard? any feedback would be greatly appreciated.
Click to expand...
Click to collapse
Kind of a reach here, but could you have a problem with your battery, or intermittent interference on the contacts? Stability of the power supply is the first thing that comes to mind. I don't know exactly how a battery failure would manifest this way, but we can rule out firmware and the initial assumption should be that the motherboard is ok. Perhaps premature death of a cell in the battery has dropped the voltage just enough? Can you correlate reboots with heavy usage?
Shakkuras said:
Kind of a reach here, but could you have a problem with your battery, or intermittent interference on the contacts? Stability of the power supply is the first thing that comes to mind. I don't know exactly how a battery failure would manifest this way, but we can rule out firmware and the initial assumption should be that the motherboard is ok. Perhaps premature death of a cell in the battery has dropped the voltage just enough? Can you correlate reboots with heavy usage?
Click to expand...
Click to collapse
i have multiple batteries, not the issue, i am unable to use the device due to rebooting issues, will rebut every 5 to 10 mintents.
just reread my post found a little lack of info, it was rebooting before i did the first flash of 4.1.2 and rebooting started again after clean flash
hugh a said:
i have multiple batteries, not the issue, i am unable to use the device due to rebooting issues, will rebut every 5 to 10 mintents.
just reread my post found a little lack of info, it was rebooting before i did the first flash of 4.1.2 and rebooting started again after clean flash
Click to expand...
Click to collapse
So, the phone was rebooting constantly on (GB, ICS), you flashed it to 4.1.2 and it continued rebooting, flashed again and still rebooting, you replaced the system board and its still constantly rebooting in both stock and a safestrap slot?
Are you using the same microSD card? That's the next easiest component to rule out. That it was happening before suggests that the problem is not related to the integrity of your FXZ file, but that could be another avenue to explore. Will update if I can think of more, easy tests.
Shakkuras said:
So, the phone was rebooting constantly on (GB, ICS), you flashed it to 4.1.2 and it continued rebooting, flashed again and still rebooting, you replaced the system board and its still constantly rebooting in both stock and a safestrap slot?
Are you using the same microSD card? That's the next easiest component to rule out. That it was happening before suggests that the problem is not related to the integrity of your FXZ file, but that could be another avenue to explore. Will update if I can think of more, easy tests.
Click to expand...
Click to collapse
there is no sd installed or custom recovery, could it be the digitizer or the sd and sims slot its a removable piece on the board, this random rebooting is a commin issued with the bionic, i did a google search lots of issues and no solutions
hugh a said:
there is no sd installed or custom recovery, could it be the digitizer or the sd and sims slot its a removable piece on the board, this random rebooting is a commin issued with the bionic, i did a google search lots of issues and no solutions
Click to expand...
Click to collapse
If you're willing, safestrapping and installing (e.g.) CM11 could be used to rule out a software problem (assuming the phone doesn't reboot during installation). Does the phone tend to reboot while in recovery? Have you booted into safe mode, and does that also lead to reboots? If it reboots while in recovery, that would suggest that the issue is not software-based.
Since you're working with stock, it could be worth re-downloading and re-flashing vzw stock after verifying the integrity of the file you've downloaded. I see that this issue has arisen often, but a fresh flashing with RSDlite does seem to have helped some users. While I know you've already re-flashed it already, I would suggest giving it another try. I realize I'm listing pretty much every possible cause, but it's best to rule these out.
Shakuras said:
If you're willing, safestrapping and installing (e.g.) CM11 could be used to rule out a software problem (assuming the phone doesn't reboot during installation). Does the phone tend to reboot while in recovery? Have you booted into safe mode, and does that also lead to reboots? If it reboots while in recovery, that would suggest that the issue is not software-based.
Since you're working with stock, it could be worth re-downloading and re-flashing vzw stock after verifying the integrity of the file you've downloaded. I see that this issue has arisen often, but a fresh flashing with RSDlite does seem to have helped some users. While I know you've already re-flashed it already, I would suggest giving it another try. I realize I'm listing pretty much every possible cause, but it's best to rule these out.
Click to expand...
Click to collapse
it will reboot during installation, cant root because of rebooting, it does not reboot in recovery, well i dont think it does, will verify, it does reboot in safe mood for sure,
Shakkuras i have flashed this thing a dozen time, when one of these phones stumps me its hard for me to throw in the towel, ill lose sleep
i really appreciate the time and input.
update does not reboot while in recovery, this is very odd, any more ideas?
hugh a said:
it will reboot during installation, cant root because of rebooting, it does not reboot in recovery....
...update does not reboot while in recovery, this is very odd, any more ideas?
Click to expand...
Click to collapse
That's a bit peculiar, and probably indicates something about the cause of the problem, but I don't know how to proceed down that line of inquiry to cover something fixable. Does the phone reboot repeatedly if you leave the sim card out? That's the last of the "easy" things I can think of.
update: i recently purchased a lot of 50 phones and had 3 bionics in lot all 3 have random rebooting issues, so now i have 4 very nice bonics and 2 motherboards with all similar issues, 3 is on jb and 1 is gb, did extensive xda and google searches many similar issues on google but not xda, surprising, in between rebooting i have forced stopped many app that i thought could be culprit, i have tried multiple batteries, i have changed launchers, i've cleaned battery contacts, many flashes and factories resets, i've tries safe mode all to no avail, still rebooting, anyone reading this post with any knowledge of this issue or even better a fix i would be greatful for any feed back.
still having issues with bionic randomly rebooting, if you read this post and have any information or a link to similar issues your feedback would be greatly appreciated.
Definitely sounds like hardware issue. Like BGA solder Crack. Xbox 360... I would try swapping parts from a good unit. may be a on to something with the digitizer.
larski156 said:
Definitely sounds like hardware issue. Like BGA solder Crack. Xbox 360... I would try swapping parts from a good unit. may be a on to something with the digitizer.
Click to expand...
Click to collapse
not the digitizer, have multiple digitizers and parts, finley ran across a motherboard that worked which allowed me to father test, i thought it was hardware also but now im leaning towards software, some one has a fix to this issue, to commin of an issue not to have been address
bump
have you tried a full data/cache/dalvik format? Another idea would be to RSD up the latest FXZs for the SW version yr using. Another suggestion: remove sdcard and sim and see if maybe a bent guide might be causing intermittent contact of card(s) and thus rebooting.
Just some ideas FWIW
Edit:
1. Wipe cache n dalvik
2. remove sd/sim and retest
3. Full data partition format/factory reset
4. FXZ flash via RSD or house of moto.
If its SW issue, those 4 things will most definitively clear it up
---------- Post added at 02:15 PM ---------- Previous post was at 02:09 PM ----------
(1 being easiest and least destructive troubleshooting step, 4 being most drastic)
tom.etc said:
have you tried a full data/cache/dalvik format? Another idea would be to RSD up the latest FXZs for the SW version yr using. Another suggestion: remove sdcard and sim and see if maybe a bent guide might be causing intermittent contact of card(s) and thus rebooting.
Just some ideas FWIW
Edit:
1. Wipe cache n dalvik
2. remove sd/sim and retest
3. Full data partition format/factory reset
4. FXZ flash via RSD or house of moto.
If its SW issue, those 4 things will most definitively clear it up
---------- Post added at 02:15 PM ---------- Previous post was at 02:09 PM ----------
(1 being easiest and least destructive troubleshooting step, 4 being most drastic)
Click to expand...
Click to collapse
all advice welcomed on this issue! but nun listed are my issues, this issue is on multiple devices and motherboards, have no sims or sd installed, many data wipes and factory reset, multiple flashes, still randomly reboots, someone here has info on this issue
hugh a said:
all advice welcomed on this issue! but nun listed are my issues, this issue is on multiple devices and motherboards, have no sims or sd installed, many data wipes and factory reset, multiple flashes, still randomly reboots, someone here has info on this issue
Click to expand...
Click to collapse
bump
bump
bump
Related
Hi,
I managed to brick my Milestone, terminally I'm afraid, but the symptoms are different than what I see around the forum so they might interest someone else.
So, I first backed up everything with GOT Nandroid and Titanium Backup then modded CyanogenMod 7 RC4 0.08-11.04.05 (Android 2.3.3) successfully, except that the SIM was locked and would not unlock, although it works in another phone. This was a bug supposedly fixed in version 6 of Cyanogen...
Browsing the forums, the only thing that made a bit of sense was that maybe the GSM frequency was set to the wrong value. There is a Nandroid mod (but not GOT) that allows you to change that so I entered GOT Nandroid again. Since it had no such option, I Rebooted. Then, the fun begun.
The phone got stuck on the Motorola logo and no button, not even Power, worked anymore. After waiting for many minutes with no progress, I took out the battery - that made a change , the phone shut down. I then put it back - the phone immediatelly, no, instantly, cause there's no delay as when you were powering it up, lights up with the same Motorola logo. Tried several times, always the same behavior.
I left it booting (but also connected to the charger) for a whole night, no change.
The phone is not seen by the PC when connected to USB. It won't reboot, normally or to recovery. Buttons won't work at all. Yeah, tried with or without the SIM and the sdcard, no change. Tried to start without battery, just the charger, doesn't work.
Useless to say, I am getting bored of that Motorola logo
I suspect that the bootloader in the internal memory got corrupted. Can this be flashed even if the device is not seen by the PC (I mean by the RDSLite installed on it)?
Cheers
When the charger is connected to the phone try at the same timeull out and pull in the battery while holding the buttons who will get you in the OR
Yup, it worked. So first I got the battery with a question mark. Then I put in the battery and I got a battery at 60%. Since I was holding Power+Camera, it continued to the Recovery mode and now I have a working Milestone with Cyanogen mod!!
Thank you a lot, Mikicishte.
I still have to see about the initial locked SIM problem... but that will be mostly fun.
florinadrian said:
I still have to see about the initial locked SIM problem... but that will be mostly fun.
Click to expand...
Click to collapse
Have you tried to factory reset the Milestone, to see if after that the SIM is accessible again ?
http://forum.cyanogenmod.com/topic/14099-sim-card-not-detected-after-factory-reset/
You could try also to install a logger application catlog for example (https://market.android.com/details?id=com.nolanlawson.logcat&feature=search_result ) to see in the logs if you can find out more details to help you with the investigations...
I did the factory reset as part of installing the mod.
Even if the post quoted reports the wipe as the source of the problem and not as a solution, I just wiped again with no good result.
Will try catlog.
florinadrian said:
I did the factory reset as part of installing the mod.
Even if the post quoted reports the wipe as the source of the problem and not as a solution, I just wiped again with no good result.
Will try catlog.
Click to expand...
Click to collapse
or maybe you could try to use an unlock tool to see what error is reporting
https://market.android.com/details?id=com.droidgram.bladeunlock&feature=search_result
Hello everybody........Great website by the way very helpful all the time.If anybody can please help me it will truly be appreciated...Thanks in advance!Long story short.....My GF was taking a video with her LG P970 and then it stopped because the SD had just reached its limit so the camera just forced closed.After that I noticed the phone became laggy(More than it already is btw)then there was a message in the notifications bar "Removed SD card"although it was still in the phone.The phone then started to freeze so I took out the battery and turned it on again but still the phone kept saying "Removed SD card"and when I tried the camera it would never open just a black screen would pop up and nothing......Just force close....(Good grief)..........So heres what ive tried.1.Factory Data Reset from privacy menu in settings.2.Tried other SD cards (5 other ones by the way).3.LG support mobile tool updating.4.Smartflash program to reset the phone to stock.5.Tried a bunch of different DRIVERS to see if it could find the SD on the computer.6.Ive also tried downloading a camera app from market but they all just FC's.ETC,ETC,ETC.So there you have it after all that still no SD CARD found and the camera app still crashing.I would give up and say that its a HARDWARE problem but Ive had something like this happen before with my Nexus One and somebody flashed some camera thing on it and it worked again.Her P970 is not rooted or anything like that btw.Thanks again
Well, I think it's time for LG's repairservice.
If you haved played with the rom her a method to go back to an unrooted stock ROM, due you mentioned Smarttool, and this isn't a program for consumer purpose from LG. Aniway it may help:
Flash tool: http://forum.xda-developers.com/showpost.php?p=18946763&postcount=1
and Here the stock firmwares: http://lg-phone-firmware.com/index.php?id_mod=1
Regards.
Thank you very much for the response.......Ive tried both of the links but unfortunantly theyre dead links.......Also I forgot to mention that I am new to Root/Flash techniques so not so good.Using the Smartflash tool has been the only thing ive ever used............But I have a question?Do you think ROOTING and maybe putting a different Rom may solve the problem?Maybe CyanogenMod idk?Thanks in advance......And would you have a good link to view "ROOTING FOR DUMMIES"because I wouldnt know the first thing to do with a ROM.Thanks
Link updated!
I definitely don’t recommend to play with rooted roms with devices with hardware problems.
What I have linked is a tool to bring the device to stock conditions and so bring it to the service without trouble. You have said you have used Smartflashtool, this may have flashed some unofficial stuff which erase your guarantee claims.
Be aware that you do this things on your own risk!
nothing to do?
Pacos1 said:
Link updated!
I definitely don’t recommend to play with rooted roms with devices with hardware problems.
What I have linked is a tool to bring the device to stock conditions and so bring it to the service without trouble. You have said you have used Smartflashtool, this may have flashed some unofficial stuff which erase your guarantee claims.
Be aware that you do this things on your own risk!
Click to expand...
Click to collapse
someone really solved this problem? Is frustrating 'cause i can not use my card at all, my camera don't work and some days it freezes 20 times, I must to take out the battery and it freezes again after 2 minutes.. I tried flashing it, restore factory settings, not installing nothing, updating os, but it's getting worst. I am out of warranty.. I think I will crash it with a hammer.
personal_ionutz said:
someone really solved this problem? Is frustrating 'cause i can not use my card at all, my camera don't work and some days it freezes 20 times, I must to take out the battery and it freezes again after 2 minutes.. I tried flashing it, restore factory settings, not installing nothing, updating os, but it's getting worst. I am out of warranty.. I think I will crash it with a hammer.
Click to expand...
Click to collapse
i have the same problem...also the sensors are not working?somebody wrote that the cause might be a short circuit on motherboard?
Any solutions?
OK so heres my story of what happened to my Captivate. I plan on getting an SIII sometime in the next couple of weeks, but it would be nice to get my Captivate up and running again in case I need it sometime in the future.
So I was running CM9 on my phone, not sure which build, not sure if it matters. Phone was still in my pocket when I went swimming. Left it in a bag of rice, and it booted up. I got the message that said Encryption failed...reset phone or whatever. I figured it would just format it and didnt know that it would lead to more problems. So based on what I have read on the site, now my internal SD is fried im assuming. Now I tried following some guides for using an external SD card but I couldnt get it to partition from ClockworkMod, and I couldnt get into download mode for a few days because something probably got messed up internally from water damage. I managed to get into download mode today and tried running an Odin One-Click to see if it would help at all. Now my phone brings up the AT&T World Phone screen, then shuts off as soon as the screen normally transitions into the next step of the boot process.
So thats my story. I just want to know if anyone knows if this is still a problem with the SD card or if my phone is completely beyond repair. Thanks a lot to anyone that tries to help
You got hit by the EU (encryption unsuccessful) bug. From what I hear not a whole lot you can do now except try this. http://forum.xda-developers.com/showthread.php?t=1447303
There are a couple other threads in the dev section about this as well.
robm1911 said:
You got hit by the EU (encryption unsuccessful) bug. From what I hear not a whole lot you can do now except try this. http://forum.xda-developers.com/showthread.php?t=1447303
There are a couple other threads in the dev section about this as well.
Click to expand...
Click to collapse
Ya that was the guide I tried but my external SD card wont partition, at least not through clockworkmod. When i press the button to partition, the partition process is instant, and i know it just has to skip it because there is no way it would partition that fast.
You could always pay to have jtag performed. It will overwrite all the screwed up stuff and fix the problem.
mrhaley30705 said:
You could always pay to have jtag performed. It will overwrite all the screwed up stuff and fix the problem.
Click to expand...
Click to collapse
I think with the EU bug its just trashed. JTAG won't even fix it. There are a few stories of them coming back to life on their own, but no promises.
Hi we offer a work around re-map to have the partitions run on you external sdcard. Pm me if you need any help with this.
Sent from my GT-I9300 using xda premium
Ive searched and havent been able to find a solution to this, although Ive seen it asked before.
Galaxy Tab P100 bought from a pawn shop. It still has the prior owners (unknown) gmail info minus p/w. I cannot remove the account, or access market because of this. Everytime I tried to data reset (both via Privacy settings and also CWM), add a new rom, or add apps - after I reboot it goes back to the prior owner settings and apks.
I have Odin'd/Heimdall with different roms but they dont stick. Different kernels install though. Ive added two different CWMs. Superuser breaks after every reset - I gain, then lose, root. Ive rooted/added root explorer and deleted accounts.db and user.db - they go back after. Ive spoken with Sprint and we tried everything they had, as well as a ##786# and MSL number (resetting phone activation I think?). Their response was take it in to send back. I want to fix it myself.
It seems to me that this prior info is overriding and reinstalling every reboot, preventing any new flashing/etc from taking place.
Here is my question. I took it apart this morning and disconnected the battery (thinking maybe it will wipe any memory). But does it have a CMOS-type battery? I noticed there is a small round battery-looking connection soldered into the mainboard (see here - step 7/8 http://www.ifixit.com/Teardown/Samsung-Galaxy-Tab-Teardown/4103/1)
Does anyone know what this is? I dont really have anything to lose, but Im not great with a soldering iron, but will try. Im thinking this might be for the memory, and disconnecting/reconnecting this would erase any permanent user information, freeing it up for me to add mine.
Or if anyone has any new ideas I would appreciate it.
Thanks for the time. Ed
Sent from my rooted/rom'd PG86100 using XDA Premium App
It is not a battery backed memory, it is a NAND chip.
Sounds like the chip gone bad.
Sent from my GT-P1000 using XDA
Just an update.
I did not do anything with the round battery thing, as priyana stated the memory is stored on a nand chip. I put the tab back together.
I rooted again, and found the ea24 firmware and loaded it via odin. It took, but the prior user info was still there, and everything (I mean a crapload of apps) began force closing. I did confirm that ea24 was on it. I then flashed back to ef17.
I contacted Sprint repair store again, and they told me that they probably cant fix it, and its something they have to send back. They said that I have done all that they would do in-store.
I dont understand what could be wrong, as I found the prior owner and spoke with her. She had no issues with it. It worked fine prior to her getting rid of it. And it works fine, I just cant get rid of any prior info. I googled it and it seems like there are people out there who have the same problem, but no one has an answer, including sprint or samsung.
So much for my venting. Ill keep trying to find an answer.
roninep said:
I have Odin'd/Heimdall with different roms but they dont stick. Different kernels install though. Ive added two different CWMs. Superuser breaks after every reset - I gain, then lose, root.
Click to expand...
Click to collapse
First of all, I'd like to apologize for posting something that won't really help, but I recognize this from somewhere else. On some devices, there's some kind of file (that you can delete via the adb prompt when you're root) that on every bootup checks to see if the installed ROM matches stock, and if not, restores to stock. This sounds exactly what you're experiencing when you mention that no ROMs "stick".
I think you should try to look into if there's some files that need to be erased in order for a ROM to be cleanly installed that you haven't gotten rid of. It might also be some kind of feature that the previous user enabled, so maybe it's somewhere around in the settings that you can disable it, who knows.
It definitely does not sound like a memory issue because I don't see how a memory issue could make the stock ROM suddenly appear again after you've installed a custom ROM through CWM (assuming CWM gives no errors or anything and the custom ROM has actually been wiped).
Maybe you can do a more thorough wipe of the device memory manually with some guidance from someone who knows more about how these tablets work :fingers-crossed:
I agree with you about some type of file and bootup. Thats why I went with maybe it being a cmos/nand issue. I couldnt understand that I wiped everything, and information was still coming back. It makes me think that somewhere, something is being stored separate from the main drive.
Ive used the factory restore, CWM (2 different versions - 3 and 5 I believe), and wiped data (factory reset), cache and Davlik three times each before I flashed the CM ROMs. And I have not had any errors or problems installing any of the CWMs.
I spoke with the previous user, and she did nothing above turning it on/off, and using it. I am not on the Sprint network with it, and the wi-fi doesnt turn on until I set it up, so I cant see it being something that contacts Sprint and OTAs from them.
Can anyone tell me if, using ADB, there is a more thorough wipe I can perform ? More than the normal one done through CWM or Android factory restore?
Something similar to the reformatting of a hard drive?
Thanks
Ed
I have the same problem. Did you find any solution?
I believe the previous owner info is stored on sprint servers. When you reboot, it downloads all the crap.
The long time required to reboot explains the slow transfer of data - wireless.
These wireless service providers are pretty sneaky.
Thanks
Hi,
Have you tried formatting both internal and external Sd via Windows? (connecting via USB)
You can also try CM10, it has a different memory map which will write your device completely.
Regards
Sent from my GT-P1000 using Tapatalk 2
I have this same problem with a tab. Its not connected to sprint,has not been on the internet at all. Was there ever a fix for this?? Please let me know its a christmas present and i need to fix this issue. Thank you
I don't see EQC1 on sammobile, anyone else see the 127 MB update?
I'm on EQB1.
Yup, I see it, 127.53mb on both of mine SM-N910T3 and
SM-N910T
I have it as well. Have you flashed yet?
I have it too. I'm not sure I want to flash, especially if it patches the ability to root my phone.
My phone also suffers from the SD card / reboot issue (the phone constantly boot loops when both an SD card and SIM card are in the phone). I wonder if this update will fix that?
I tried flashing it and it failed, I'm running a stock highly modified rom. I'll try reflashing the original stock unmodified rom when I get a chance tomorrow and apply the update. It looks like it's just security updates
Says "Various system improvements" for the QC1 update.
https://support.t-mobile.com/docs/DOC-28899
I updated to this version the other day, now I'm looking to root. Anyone know if the old root method still works? I may try myself in the next few days myself and find out.
I upgraded to it yesterday. Took about 30 minutes from start of install to finish. It updates the security to March 2017, has the new Google Play Store. Other than that I do not notice any other differences
Can i root after upgrade?
Does anyone know if this fixes the mmc_read failed issue along with its constant lagging/freezing problem?
febzz88 said:
Does anyone know if this fixes the mmc_read failed issue along with its constant lagging/freezing problem?
Click to expand...
Click to collapse
I'm pretty sure the mmc_read failure issue is failing hardware and no firmware release can fix this. My understanding is some Note4's had dodgy flash memory and will eventually fail. I had this happen to my note4 last year and got it changed out under warranty at a tmobile store. My phone had the constant lagging/freezing for about a month before it would just no longer boot, it wouldn't do anything other than a quick vibrate on power up, no boot screen of any type.
If you are getting mmc_read I would suggest you get the phone replaced ASAP, and make backups of everything you have on it that you want to keep. At some point it probably just wont power back on again. Hopefully you are still under a warranty and can get it swapped out.
d0ug said:
I'm pretty sure the mmc_read failure issue is failing hardware and no firmware release can fix this. My understanding is some Note4's had dodgy flash memory and will eventually fail. I had this happen to my note4 last year and got it changed out under warranty at a tmobile store. My phone had the constant lagging/freezing for about a month before it would just no longer boot, it wouldn't do anything other than a quick vibrate on power up, no boot screen of any type.
If you are getting mmc_read I would suggest you get the phone replaced ASAP, and make backups of everything you have on it that you want to keep. At some point it probably just wont power back on again. Hopefully you are still under a warranty and can get it swapped out.
Click to expand...
Click to collapse
Hi,
That's certainly is one possible scenario (hardware failing). But based on my extensive research too, many have said that this could be faulty firmware. I went to a Samsung Experience Center and talked with a guy there and he said that it's a known issue affecting many Galaxy Note 4 Sprint users a few months ago. Samsung in the end replaced/repaired the affected units free of charge.
In the past 2 months or so, more and more Galaxy Note 4 users started experiencing this issue. And so it could be that the firmware triggered the issue, and eventually damaged the hardware.
Since we don't really have a 100% certain answer (of course, Samsung will never tell us), I'm just trying to see if anyone has updated the phone to the latest firmware and could tell us if it fixed the issue.
Soooo..... Is this rootable or not?
sino8r said:
Soooo..... Is this rootable or not?
Click to expand...
Click to collapse
Try this https://forum.xda-developers.com/no...rom-n910t3uvu3eqc1-stock-rooted-odex-t3592242
I can't seem to get TWRP to work on this. I've tried several times with Odin, it appears to be successful, phone reboots, but then when I try to reboot into recovery there's no TWRP, only stock. Anyone else have this issue or any suggestions?
Edit: Tried something I remembered reading in another thread. I pulled the battery immediately after Odin successfully finished and the booted directly into recovery. It worked. I'm flashing pvsgh's rooted EQC1 and will report back if TWRP sticks
Edit 2: Success. Seems like pulling the battery after Odin/TWRP before the phone reboots did the trick
ok, thanks for the suggestion.
Anybody have a link for the firmware?
thecrunked said:
Anybody have a link for the firmware?
Click to expand...
Click to collapse
https://forum.xda-developers.com/no...firmware-galaxy-note-4-n910tuvs2eqb1-t3569911
Can I autoroot with EQC1?
I tried auto root and got
RECORVERY IS NOT SEANDROID ENFORCING,
AM I screwed? I assume there's some way to get back to EQC1 and boot the phone. There has to be. But could I do it and keep the data. I was trying to get deleted photos back.