Recently just received a warranty replacement Note 2 and of course first thing I did was root and unlock it. After flashing a rom a indicator would pop up saying TWRP had lost root permissions and after selecting okay, fix permissions for it. I wrote it off not thinking much of it but after flashing a different rom the same pop up appeared again, still no problems. Finally my phone started locking up and today it eventually bricked up as I flashed a rom. No biggie, I flashed back to stock and am good to go but I just want to know if anyone else has come across this same issue as well?
Sent from my SCH-I605 using Tapatalk 4 Beta
endo689 said:
Recently just received a warranty replacement Note 2 and of course first thing I did was root and unlock it. After flashing a rom a indicator would pop up saying TWRP had lost root permissions and after selecting okay, fix permissions for it. I wrote it off not thinking much of it but after flashing a different rom the same pop up would appear again, still no problems. Finally my phone started locking up and today it eventually bricked up as I flashed a rom. No biggie, I flashed back to stock and am good to go but I just want to know if anyone else has come across this same issue as well?
Sent from my SCH-I605 using Tapatalk 4 Beta
Click to expand...
Click to collapse
Only time I've seen this it has been an issue with the rom I'm flashing.
Sent from my SAMSUNG-SGH-I957 using xda app-developers app
jd1639 said:
Only time I've seen this it has been an issue with the rom I'm flashing.
Sent from my SAMSUNG-SGH-I957 using xda app-developers app
Click to expand...
Click to collapse
For some reason it happened with every rom I would flash. Possibly mucked something up when I rooted and unlocked in the first place.
Sent from my SCH-I605 using Tapatalk 4 Beta
I is twrp that causes the issue, if I'm mistaken they have updated to fix that bug.
M.A.D.NoTe.||
Going through the exact same thing right now, same situation and all, did you get this worked out? I flashed back to stock just a couple minutes ago and am now in the process of flashing a custom rom again. Never experienced this before and been flashing on this phone the Note 2 since October. New phone, new problem. Used the Toolkit to do everything every time I get a new phone. This is my third.
StevetotheH said:
Going through the exact same thing right now, same situation and all, did you get this worked out? I flashed back to stock just a couple minutes ago and am now in the process of flashing a custom rom again. Never experienced this before and been flashing on this phone the Note 2 since October. New phone, new problem. Used the Toolkit to do everything every time I get a new phone. This is my third.
Click to expand...
Click to collapse
Sorry for such a long delay in responding. I found a fix for this issue. I ended up just flashing all the way back to the original stock rom when the Note 2 was released then went about using the unlocking/rooting methods and have not ran into a single problem.
Sent from my SCH-I605 using Tapatalk 4 Beta
endo689 said:
Sorry for such a long delay in responding. I found a fix for this issue. I ended up just flashing all the way back to the original stock rom when the Note 2 was released then went about using the unlocking/rooting methods and have not ran into a single problem.
Sent from my SCH-I605 using Tapatalk 4 Beta
Click to expand...
Click to collapse
I was having this issue a few days ago and formatting my internal SD with TWRP and reflashing my ROM fixed it.
Sent from my SCH-I605 using XDA Premium HD app
I wipe internal every time along with the normal wipes when I flash a rom. Gives you the best chance of everything being stable and having a great gps lock even on aosp or tablet roms
Sent from my SCH-I605 using Tapatalk 2
hopesrequiem said:
I wipe internal every time along with the normal wipes when I flash a rom. Gives you the best chance of everything being stable and having a great gps lock even on aosp or tablet roms
Sent from my SCH-I605 using Tapatalk 2
Click to expand...
Click to collapse
I do this as well but for some reason twrp still lost root permissions.
Oh well having no issues anymore so I am a happy camper.
Sent from my SCH-I605 using Tapatalk 4 Beta
USB connection problems
Now I keep running into USB driver issues as of late. Don't understand why this keeps happening. Uninstalled and reinstalled all drivers and Note 2 connects for awhile and then completely stops. I can browse/edit items on the phone but cannot copy files over to it. A pop up saying it has been disconnected and cannot copy files to said device. WTF?!
endo689 said:
Now I keep running into USB driver issues as of late. Don't understand why this keeps happening. Uninstalled and reinstalled all drivers and Note 2 connects for awhile and then completely stops. I can browse/edit items on the phone but cannot copy files over to it. A pop up saying it has been disconnected and cannot copy files to said device. WTF?!
Click to expand...
Click to collapse
What OS you on? Try a different cable and different usb port. Use the drivers from mskips all in one tool from the forum. Have you tried adb devices to see if it recognizes your device? If you haven't rebooted you rig lately do that and your device as well. I had this happen for a minute on Win8 I had to manually point the driver update to the file I wanted to use.
Rock, Flag and Eagle!
Way back when I got my Note 2.... the version of casual actually flashed a wrong TWRP , it was the one for the international Note 2.
The fix was to simply install the newest TWRP for our phone (SCH-i605)
Milimbar said:
Way back when I got my Note 2.... the version of casual actually flashed a wrong TWRP , it was the one for the international Note 2.
The fix was to simply install the newest TWRP for our phone (SCH-i605)
Click to expand...
Click to collapse
What?
Rock, Flag and Eagle!
StevetotheH said:
What OS you on? Try a different cable and different usb port. Use the drivers from mskips all in one tool from the forum. Have you tried adb devices to see if it recognizes your device? If you haven't rebooted you rig lately do that and your device as well. I had this happen for a minute on Win8 I had to manually point the driver update to the file I wanted to use.
Rock, Flag and Eagle!
Click to expand...
Click to collapse
I will definitely give this a shot when I have a chance.
Sent from my SCH-I605 using Tapatalk 4 Beta
Make sure youre using the latest TWRP version.
Related
K I'm using boot manager to install a cm9 Rom and it keeps failing at creating boot.img. I don't know what I'm doing wrong since I've herd of others installing cm9 roms sucessfully using boot manager. Maybe it's something in my settings? Tried making a thread at init2winit forums but have not gotten any response over there. Anyone here willing to help me out? I would greatly appreciate it.
Sent from my ADR6425LVW using Tapatalk 2
that usually means you dont have enough space
Thanks for the advice. I did check my SD storage and it said that I only had 1.16GBs left. So I thought that this could be true I suppose. So I switched to int. Storage as the install location(which I have 9.67GBs available on) and its causing my phone to lock up and freeze. Happened right at the part "extracting Rom please wait..." Weird...
Sent from my ADR6425LVW using Tapatalk 2
boot manager doesnt surport rexound officially，maybe thats the final answer. i encounterred the same issue too，but when i reinstall the app，it works just fine.
Sent from my ADR6425LVW using xda premium
anubis2k3 said:
Thanks for the advice. I did check my SD storage and it said that I only had 1.16GBs left. So I thought that this could be true I suppose. So I switched to int. Storage as the install location(which I have 9.67GBs available on) and its causing my phone to lock up and freeze. Happened right at the part "extracting Rom please wait..." Weird...
Sent from my ADR6425LVW using Tapatalk 2
Click to expand...
Click to collapse
Remember to disable logging in Superuser. That also causes some major issues. Just open superuser hit settings icon, and where it says logging set it to off. You should have much better luck that way
Cool, I will try that. I've uninstalled and reinstalled multiple times, with no luck. I'm interested though. What do you guys have setup in settings?
Sent from my ADR6425LVW using Tapatalk 2
live2die said:
boot manager doesnt surport rexound officially，maybe thats the final answer. i encounterred the same issue too，but when i reinstall the app，it works just fine.
Sent from my ADR6425LVW using xda premium
Click to expand...
Click to collapse
The Rezound is supported by bootmanager.
I've never been able to get boot manager to work correctly since I've started using it back on my dinc2. Had issues installing some roms on that phone too. Which is why I think my problem may be the settings I am using. Is there specific settings I need to use for the rezound?
EDIT: After I changed the settings SU I tried again at work and it froze still and even rebooted during the install.
Sent from my ADR6425LVW using Tapatalk 2
Ok, so I finally got cm9 roms to install correctly and now when I try to boot to them it just shows the splash screen for a couple seconds and my display turns off and it never boots. I've tried with kang and paranoid with the same results. I've tried going into recovery and manually flashing the update zip for rom 1, didnt work. Can't think of what could be the problem....
Sent from a galaxy far..far..away....
anubis2k3 said:
Ok, so I finally got cm9 roms to install correctly and now when I try to boot to them it just shows the splash screen for a couple seconds and my display turns off and it never boots. I've tried with kang and paranoid with the same results. I've tried going into recovery and manually flashing the update zip for rom 1, didnt work. Can't think of what could be the problem....
Sent from a galaxy far..far..away....
Click to expand...
Click to collapse
Doesnt look like anyone has asked you this, but are you S-Off?? You need to be S-off for this to work. Also make sure when installing you wipe system/data/cache. You should be able to use the ext.4/2 either one will work. I use the ext.4 since it installs faster....alot faster.
dalvear88 said:
Doesnt look like anyone has asked you this, but are you S-Off?? You need to be S-off for this to work. Also make sure when installing you wipe system/data/cache. You should be able to use the ext.4/2 either one will work. I use the ext.4 since it installs faster....alot faster.
Click to expand...
Click to collapse
He can be HTC unlocked and s-on it will still work bootmanager still hasn't updated since the rezound got s-off... His problem sound like the boot.img does not have the right kernel installed or something
Sent from my Dinc... I mean Rezound
yojoe600 said:
He can be HTC unlocked and s-on it will still work bootmanager still hasn't updated since the rezound got s-off... His problem sound like the boot.img does not have the right kernel installed or something
Sent from my Dinc... I mean Rezound
Click to expand...
Click to collapse
only mentioning that because in the instructions for the app. If he doesnt have to be S-Off then thats strange. Only thing i could suggest after that would be redownload ROM and check MD5
dalvear88 said:
only mentioning that because in the instructions for the app. If he doesnt have to be S-Off then thats strange. Only thing i could suggest after that would be redownload ROM and check MD5
Click to expand...
Click to collapse
i understand... he could probably do a dirty install of the same rom over top and make sure it has a boot.img in the zip that is not in any of the folders
I unrooted, installed stock ROM and downloaded the OTA ics but when I clicked OK to install it the phone rebooted, showed the unpacking symbol, progressed about 1/4 inch and then stopped with the error symbol.
Hitting the power button reboots into recovery, rebooted and went through the same thing.
I wondered if the download was faulty so next time I was in recovery I wiped and rebooted, re-downloaded the ICS update with the same results.
I thought I'd install the OTA ICS before trying to sell the phone but how can I? Anyone know what's wrong?
Temporary fix: Removed SIM, put SIM back in Galaxy S3 and all is well but that doesn't help the T'bolt get updated!
The ota won't apply to the stock Rom if you have any system apps removed.
Sent from my ADR6400L using Tapatalk 2
disconnecktie said:
The ota won't apply to the stock Rom if you have any system apps removed.
Click to expand...
Click to collapse
I've done nothing to the stock ROM other than install it. When setup starts I selected English, skipped on ahead and went to setting, clicked stay awake, etc. and then downloaded the ROM.
NOTE: I unrooted, I can't remove any system apps can I?
Well my next suggestion would be to use the all-in-one tool to root,unlock and get s off. Flash the new radios, and then flash the official ics Rom in the development section.
Sent from my ADR6400L using Tapatalk 2
I thought of that but that puts me back where I was yesterday, I don't know why but I really don't like to sell a rooted phone, I'd prefer getting it back to stock.....
OTOH I hate to spend more time with it...
I didn't realize you were selling it. Put it on swappa. Sell it rooted.
Sent from my ADR6400L using Tapatalk 2
I guess I'll have to, I'll probably put NuSenseX on it, that's what was on it when I unrooted..... Might as well give the buyer a nice present.
Damn, another project for tomorrow, still got a scooter to finish wiring...
xs11e said:
I guess I'll have to, I'll probably put NuSenseX on it, that's what was on it when I unrooted..... Might as well give the buyer a nice present.
Damn, another project for tomorrow, still got a scooter to finish wiring...
Click to expand...
Click to collapse
I would put something a little more responsive on there like Nusense Reborn or Nuborn 2.
Sent from my Nexus 7 using Tapatalk 2
Anyone have an idea why every time I install an aosp rom it glitches at the Samsung boot screen then just goes black and I have to pull the battery? I've installed clean, jelly beans and jedi Rom without issue. Any help is appreciated.
Update your twrp then try again. Make sure your doing full wipes and flashing gapps
Sent from my SCH-I605 using Tapatalk 2
hopesrequiem said:
Update your twrp then try again. Make sure your doing full wipes and flashing gapps
Sent from my SCH-I605 using Tapatalk 2
Click to expand...
Click to collapse
Just updated my TWRP to 2.4 and did what you suggested with the wiping and same problem.
The Samsung Galaxy screen glitches to half way off the screen, then goes off, then comes back on then the whole thing goes black and nothing.
I'm going to try another rom and see if it still does it as well.
dudeicles said:
Just updated my TWRP to 2.4 and did what you suggested with the wiping and same problem.
The Samsung Galaxy screen glitches to half way off the screen, then goes off, then comes back on then the whole thing goes black and nothing.
I'm going to try another rom and see if it still does it as well.
Click to expand...
Click to collapse
Even with another ROM it doesn't seem to want to work. It's really weird, because any Touchwiz ROM works fine, it only does it on AOSP roms..... I'm hoping someone knows what the fix for this is.
dudeicles said:
Even with another ROM it doesn't seem to want to work. It's really weird, because any Touchwiz ROM works fine, it only does it on AOSP roms..... I'm hoping someone knows what the fix for this is.
Click to expand...
Click to collapse
Odin to stock then re unlock and try this all again? I'm not sure what else you can try. I flip between aosp and tw almost daily
Sent from my SCH-I605 using Tapatalk 2
The Note 2 that couldn't...
Sent from my SCH-I605 using Tapatalk 2
1ManWolfePack said:
The Note 2 that couldn't...
Sent from my SCH-I605 using Tapatalk 2
Click to expand...
Click to collapse
Heh I think I can I think I can...I was thinken are you trying to flash the file that the post links to because thats not the right one you need to get the note 2 lte one tolte..just a though I downloaded the wrong one first but caught it
http://changelog.bbqdroid.org/#t0lte/cm10.1/next
in my experience, you need to do a factory wipe again AFTER you install or you will get a bootloop.
I think CM10.1 mentions that in their install process.
Acery said:
in my experience, you need to do a factory wipe again AFTER you install or you will get a bootloop.
I think CM10.1 mentions that in their install process.
Click to expand...
Click to collapse
Yeah it can't hurt even if they don't say that
Sent from my SCH-I605 using Tapatalk 2
Acery said:
in my experience, you need to do a factory wipe again AFTER you install or you will get a bootloop.
I think CM10.1 mentions that in their install process.
Click to expand...
Click to collapse
Would it help in any way to change to CWM when flashing my AOSP roms?
dudeicles said:
Would it help in any way to change to CWM when flashing my AOSP roms?
Click to expand...
Click to collapse
I would try cwm, I had a gs3 that couodnt flash anything with cwm but could with twrp, my note was the opposite, cwm was awful on it.
Just ran into something very interesting . When I installed Rom Manager and flashed the CWM recovery, I rebooted and my boot screen did the exact same thing it was doing installing AOSP roms. It would seem my problem may just be CWM.
dudeicles said:
Just ran into something very interesting . When I installed Rom Manager and flashed the CWM recovery, I rebooted and my boot screen did the exact same thing it was doing installing AOSP roms. It would seem my problem may just be CWM.
Click to expand...
Click to collapse
I've heard too many issues with cwm to even try it. Twrp has been flawless for me so why switch? If it ain't broke, don't fix it.
Sent from my SCH-I605 using Tapatalk 2
Ok, so update - Odin'd back to stock and re-rooted using the Casual method. I have the most recent TWRP installed and when i install the AOSP rom it does the exact same thing. I'm thinking about videotaping what the boot animation does and maybe someone can look at it and see what the cause may possibly be.
If anyone has any other suggestions i'm all ears. Again, any rom based on STOCK works without issue (Clean Rom, Jelly Beans and Jedi), but only AOSP roms (And CWM) crash the phone at "Samsung Galaxy Note II" screen on startup.
Thanks for the suggestions so far, just weird it's not working. I may have the single note 2 to never run AOSP roms. LOL
so... oddly enough i still have trouble installing AOSP roms. the only AOSP rom i have been able to install so far is Paranoid Droid. I am slowly trying each one just to see which one i can force to work. Am I the only person who can't just flash whichever rom I want whenever?
Anyone with other ideas on this? I was frequently flashing back and forth between TW and AOSP. The other day I tried to flash AOSP again and get a failed message in TWRP. Already using latest version of TWRP. I then restore a backup of TW. Download again, verify md5, get failed message again. And yes, I wiped everything...same thing I do everytime. Now I have tried to DL and flash multiple different AOSP roms and I get failed everytime. Decided to try CWM recovery and that just aborts. I have NO problems flashing TW roms though
Follow the advice to Odin back to stock and start over. Otherwise, get a replacement and tell them it's acting weird and slow haha.
Sent from my SCH-I605 using xda app-developers app
Same here!!
spydersilk said:
Anyone with other ideas on this? I was frequently flashing back and forth between TW and AOSP. The other day I tried to flash AOSP again and get a failed message in TWRP. Already using latest version of TWRP. I then restore a backup of TW. Download again, verify md5, get failed message again. And yes, I wiped everything...same thing I do everytime. Now I have tried to DL and flash multiple different AOSP roms and I get failed everytime. Decided to try CWM recovery and that just aborts. I have NO problems flashing TW roms though
Click to expand...
Click to collapse
I currently have a Tmobile Note 2. And i recently ran into the same issue. I think it started after installing a certain paranoid andrroid rom, which wrote OS folders differently from what i am normally used to seeing. The folders were 0, legacy, and obb. I also notice that it changed my device id to an SGH-i317, which is an ATT Note 2. The rom was a port from an ATT rom of course, but if it was for ATT, it wouldn't work on my device right? I installed GOOmanager, and flashed the OPEN INSTALL SCRIPT. Which it flashed the ATT version. Everything still worked. I flashed back to stock, and updated OTA. Still nothing. I've also noticed that, if i can open the zip file on my pc, it will work on my phone. For some reason, The AOSP files read invalid. While the Touchwiz roms open like a regular zip file.
Any help is appreciated. Hope some of this info helps.
Just realized i posted in the Verizon section. But i think you and I are the only two people with this issue...lol
slinky42 said:
I think it started after installing a certain paranoid andrroid rom, which wrote OS folders differently from what i am normally used to seeing. The folders were 0, legacy, and obb.
Just realized i posted in the Verizon section. But i think you and I are the only two people with this issue...lol
Click to expand...
Click to collapse
This is standard on 4.2.2 ROMs. It is related to the multi-user implementation.
slinky42 said:
I currently have a Tmobile Note 2. And i recently ran into the same issue. I think it started after installing a certain paranoid andrroid rom, which wrote OS folders differently from what i am normally used to seeing. The folders were 0, legacy, and obb. I also notice that it changed my device id to an SGH-i317, which is an ATT Note 2. The rom was a port from an ATT rom of course, but if it was for ATT, it wouldn't work on my device right? I installed GOOmanager, and flashed the OPEN INSTALL SCRIPT. Which it flashed the ATT version. Everything still worked. I flashed back to stock, and updated OTA. Still nothing. I've also noticed that, if i can open the zip file on my pc, it will work on my phone. For some reason, The AOSP files read invalid. While the Touchwiz roms open like a regular zip file.
Any help is appreciated. Hope some of this info helps.
Just realized i posted in the Verizon section. But i think you and I are the only two people with this issue...lol
Click to expand...
Click to collapse
Did you ever get your phone to install the AOSP Roms? Mine worked when l just let the phone sit. Now it works fine all the time.
Sent from my SCH-I605 using xda app-developers app
as the title says.. my droid dna has a triangle above the signal strength.. says I am roaming.. I flashed cm10.2 but it wouldnt boot up so I wiped it and then installed viper rom on it.. still there. any suggestions.. please..thanks
Is it overlaying the signal bars or above the bars, like the data indicator in AOSP?
Sent from my CarbonROM 4.3'd HTC DNA
jlinn75 said:
as the title says.. my droid dna has a triangle above the signal strength.. says I am roaming.. I flashed cm10.2 but it wouldnt boot up so I wiped it and then installed viper rom on it.. still there. any suggestions.. please..thanks
Click to expand...
Click to collapse
I had to reset mine to stock, relock it and return it on warranty, apparently there is a known issue with the sim card slot or tray or something. On my third now, debating whether to unlock and try again. No matter what I flashed on it, RUU, stock roms, anything, I couldn't get it back working right. Always had the roaming. New sim card didn't work either.
So your gonna have to do some work to get it back to stock and proper relocked, and then request a new phone from verizon.
I'm screwed I bought it from a friend
Sent from my Nexus 7 using Tapatalk 4
jlinn75 said:
I'm screwed I bought it from a friend
Sent from my Nexus 7 using Tapatalk 4
Click to expand...
Click to collapse
This happen to me also. Luckily I had an upgrade available.
So reverting back to stock and then getting a new sim won't work.?
Sent from my Nexus 7 using Tapatalk 4
Harvey Dent said:
This happen to me also. Luckily I had an upgrade available.
Click to expand...
Click to collapse
what phone did you end up getting?
jlinn75 said:
what phone did you end up getting?
Click to expand...
Click to collapse
I ended up getting the S4. Wanted the One but figured I would give the S4 a go.
I just ****ing got this phone and having the same exact issue.. Got it off swappa so now looks like I'm ****ed
Sent from my Nexus 7 using xda premium
I to have the triangle
Are their any current threads on how to ruu back to stock?
I also have the triangle and was told flashing back to stock would fix it I guess we'll see lol
The thing is I get the triangle but I got it back today by messing around with the sim card.. IMO this seems like an issue with the sim slot.. If u go back to stock let me know how that goes.. As of now I have 3g but no 4g and honestly I haven't had 4g on this phone since I got it 3 days ago
Edit... Just replaced my sim .. Good to go now make sure u try that b4 giving up
Sent from my HTC6435LVW using XDA Premium 4 mobile app
Kevin3328 said:
The thing is I get the triangle but I got it back today by messing around with the sim card.. IMO this seems like an issue with the sim slot.. If u go back to stock let me know how that goes.. As of now I have 3g but no 4g and honestly I haven't had 4g on this phone since I got it 3 days ago
Edit... Just replaced my sim .. Good to go now make sure u try that b4 giving up
Sent from my HTC6435LVW using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I've tried replacing my sim with no luck. Is there a step by step guide to return to s-on with the moonshine method?
Ruu back to stock, I had the same issue and had to do this to get it working again. You do NOT need to go back to s-on to run the ruu, but you do need to be running the stock hboot, so if you are on eng hboot make sure you flash back. .torrented has links in his signature for the ruu and the hboot
Sent from my DNA using Tapatalk 2
jamiethemorris said:
Ruu back to stock, I had the same issue and had to do this to get it working again. You do NOT need to go back to s-on to run the ruu, but you do need to be running the stock hboot, so if you are on eng hboot make sure you flash back. .torrented has links in his signature for the ruu and the hboot
Sent from my DNA using Tapatalk 2
Click to expand...
Click to collapse
I did that and it did not work I had to warranty replace it
Nothing will fix it sorry guys
Sent from my HTC6435LVW using xda app-developers app
How exactly is this an issue? Seems more like a cosmetic thing. Plus, your carrier could be renting towers from another carrier causing the phone to think it is roaming while it actually is not.
Sent from my GT-I9300 using xda app-developers app
eyegor said:
How exactly is this an issue? Seems more like a cosmetic thing. Plus, your carrier could be renting towers from another carrier causing the phone to think it is roaming while it actually is not.
Sent from my GT-I9300 using xda app-developers app
Click to expand...
Click to collapse
I don't think this has anything to do with renting towers. The same thing happened to me while I was flashing the GPE rom for the DNA. I spent two days trying to revert back to s-on and stock out of the box. Finally figured out how to do it. Next I took the ota and the triangle disappeared and showed 4G LTE.
It means your are stuck in roaming. You'll have to adb install stock hboot. Run the RUU. Let it boot. Once that's installed, you'll have to go into hboot and do a factory reset. After that, get the two OTA's. Then install custom recovery and your back in business. I've done it three times that I remember, maybe more, with success. If the first time factory reset don't work, so it again. Promise it will work. You don't have to lock or relock...
Sent from my HTC6435LVW using Tapatalk 4
planedoc said:
It means your are stuck in roaming. You'll have to adb install stock hboot. Run the RUU. Let it boot. Once that's installed, you'll have to go into hboot and do a factory reset. After that, get the two OTA's. Then install custom recovery and your back in business. I've done it three times that I remember, maybe more, with success. If the first time factory reset don't work, so it again. Promise it will work. You don't have to lock or relock...
I have the 'triangle' problem on a moonshine s-off DNA, but ADB doesn't recognize the phone, I only get "list of devices attached" and blank. It will connect in fastboot, but I've tried 3 computers, multiple usb ports, installing and updating drivers, etc. The device shows up in windows attached by usb and I can drag and drop files- any ideas? I am NOT a programmer by the way, so have been trying to rely on step by steps. Is there a way to fix it without adb? I guess even if I have to go back to box stock that will be better than no phone!
Also, the other things I've read do say you have to lock the bootloader in order to flash the stock hboot and run the RUU.
Thanks in advance-
Click to expand...
Click to collapse
Try these drivers for adb
https://db.tt/GMMd9IFX
Sent from my HTC6435LVW using Tapatalk 4
planedoc said:
Try these drivers for adb
Sent from my HTC6435LVW using Tapatalk 4
Click to expand...
Click to collapse
Planedoc, thanks for that, nogo however...when I tried to manually install those I got a Windows (7) error message saying "The folder you specified doesn't contain a compatible software driver for your device. If the folder contains a driver, make sure it is designed to work with Windows for x64 based systems."
I did try to install Koush's universal drivers as well via the exe he provided, and it still didn't recognize the phone in ADB, and then every time I plug the phone in it tries to install it's own drivers again, currently the DNA is showing up in device manager with device name: HTC6435LVW, Device type ortable devices, Location: Port_#0004.Hub_#0005, and driver files \Windows\system32\DRIVERS\WinUSB.sys and \Windows\system32\DRIVERS\WUDFRd.sys
Maybe I'll try my wifes macbook tonight and see if it shows up there.
So the problem started when I flashed a 4.3 rom last friday. I formatted my internal memory in recovery mode because for some reason I only had 4 gigs of space and had moved everything over to the sd card. Once that was done phone said like 8 gigs available and thought everything was fixed. Well now if I turn off my phone it gets stuck in some kind of bootloop but it's not looping. It's just sits at the Samsung unlock symbol and custom screen. Doesn't loop just sits there. So one day I decided to format the internal memory again and the phone boots up like normal, but I can't power off the phone without going into recovery and formatting the internal memory every time. Any ideas on what is causing it or how I can make the Samsung custom boot stock instead so I can send it out.
I also have tried flashing another 4.3 rom and it doesn't seem to go away either.
I'm not an expert on how they have to make this stuff work with the mdk bootloader but I'm sure it's not hardware related. Have you tried flashing back to a 4.2 rom?
Sent from my SCH-I545 using Tapatalk 2
Downloading one now hopefully it will fix it.
Which recovery are you using? Make sure to wipe data, cache, and dalvik 3x each, then flash your rom
Sent from my SCH-I545 using Tapatalk 2
TWRP and I flashed hyperdrive still no luck still freezing in the same spot and have to actually format to get past it.
Anyone else have any idea on what else I can try?
BlackDynomitr said:
Anyone else have any idea on what else I can try?
Click to expand...
Click to collapse
What version of TWRP are you using?
Sent from my SCH-I545 using Tapatalk
I believe 2.5 I'm guessing only way to check is to go into recovery again.
BlackDynomitr said:
I believe 2.5 I'm guessing only way to check is to go into recovery again.
Click to expand...
Click to collapse
Yep that's the only one I've never had any issues with. TWRP 2.5.0.2
Edit: If your still having issues you could always Odin back with Stock firmware and get a clean start. I know its a pain lol
Sent from my SCH-I545 using Tapatalk
heath2805 said:
Yep that's the only one I've never had any issues with. TWRP 2.5.0.2
Edit: If your still having issues you could always Odin back with Stock firmware and get a clean start. I know its a pain lol
Sent from my SCH-I545 using Tapatalk
Click to expand...
Click to collapse
Well I think that might work only thing I'm afraid is what if it doesn't turn on.
BlackDynomitr said:
Well I think that might work only thing I'm afraid is what if it doesn't turn on.
Click to expand...
Click to collapse
Well if it doesn't turn on after flashing stock firmware via Odin, you'll know its a hardware issue with it and your warranty should cover a new replacement.
Sent from my SCH-I545 using Tapatalk
I had this issue when I first got my phone. I bought it off Swappa, it was already running TWRP 2.5.0.2, giving me nothing but problems. I switch to Philz Touch and no longer have the issue.