Related
Hello folks! I achieved root on my unlocked AT&T sgs2 using DooMLoRD's method but it didn't have CWM on it so I tried using Mobile Odin to get CWM on it. Odin didn't recognize my device and I waited for the dumping process to complete but it was taking too long and so I tried using PC Odin to flash a CWM kernel but failed. Afterwards the device started showing red blue green dots on a black background and then on a white background. I can't boot into recovery or download mode and I guess I'm bricked. Any advice or suggestions?
Hey remember that time you posted in the wrong forums? It just happened. Considering this is the i777 forums.
Sent from my MB860 using Tapatalk 2
Phalanx7621 said:
Hey remember that time you posted in the wrong forums? It just happened. Considering this is the i777 forums.
Sent from my MB860 using Tapatalk 2
Click to expand...
Click to collapse
He must have the never before seen by human eyes, cross between i777 and i9100....or based on his other posts he's in the wrong damn forum considering all his other posts involve the note.
Sent from my Nexus 7 using Tapatalk 2
Pirateghost said:
He must have the never before seen by human eyes, cross between i777 and i9100....or based on his other posts he's in the wrong damn forum considering all his other posts involve the note.
Sent from my Nexus 7 using Tapatalk 2
Click to expand...
Click to collapse
Guy, chill. Ain't the end of the world here. Yes it's my bad, it's the i777. Happy? Good.
usmanold said:
Guy, chill. Ain't the end of the world here. Yes it's my bad, it's the i777. Happy? Good.
Click to expand...
Click to collapse
How did you attempt to get cwm on? The only way you will have cwm on this phone is to flash a custom kernel.
Sent from my Nexus 7 using Tapatalk 2
Pirateghost said:
How did you attempt to get cwm on? The only way you will have cwm on this phone is to flash a custom kernel.
Sent from my Nexus 7 using Tapatalk 2
Click to expand...
Click to collapse
He probably used ROM manager. We all know how well that works haha
Sent from my Nexus 7 using Tapatalk 2
usmanold said:
Hello folks! I achieved root on my unlocked AT&T sgs2 using DooMLoRD's method but it didn't have CWM on it so I tried using Mobile Odin to get CWM on it. Odin didn't recognize my device and I waited for the dumping process to complete but it was taking too long and so I tried using PC Odin to flash a CWM kernel but failed. Afterwards the device started showing red blue green dots on a black background and then on a white background. I can't boot into recovery or download mode and I guess I'm bricked. Any advice or suggestions?
Click to expand...
Click to collapse
try using a JIG it would help ur phone to get into download mode if its not bricked.or remove battery for few seconds and put it back with the usb connected to ur phone and pc and try the download mode combination(VOL UP+VOL DOWN+POWER) if it goes into download mode just check with creepyncrawly or entropy's guides to restore ur device
Hey guys, I sent my Note 2 into Samsung in Texas to repair it since the wifi was not connecting. Prior to sending it in, I had it rooted and unlocked based on the instructions on this site, but I put it back to stock (using those same directions) to limit the chance that sammy would screw me on my warranty.
I checked the status of my repairs today and it says they replaced the mainboard, so now I am wondering what I will have to do to get it back to its rooted and unlocked state the way it was before sending in. I am guessing that all I will have to do is boot into recovery and flash a rom, but maybe the stock process did more than that.
If anyone could walk me through the steps it takes to get from where it is to where it was, that would be great. Again, it was rooted and unlocked, then I used Odin to go back to stock (which I think means rooted stock, so simply the stock software while still being rooted and unlocked), and now I want to send it back to rooted/unlocked. Also, remember that the mainboard was replaced, and I am not sure if that matters to the whole process.
Thanks!
Head in over to the development section and check out Adam Outlers thread. Very detailed and great way to root and unlock.
Sent from my SCH-I605 using Tapatalk 2
Mandroidified said:
Head in over to the development section and check out Adam Outlers thread. Very detailed and great way to root and unlock.
Sent from my SCH-I605 using Tapatalk 2
Click to expand...
Click to collapse
But do I need to reroot it? I guess I assumed that putting it back to stock meant rooted/unlocked stock, or stock software. No big deal, I can just reroot/unlock it like I did the first time, but I assumed it was something different.
I'd use triangle away too. I did that before sending it to vzw. Oddly, my counter was at 0
kimdoocheol said:
I'd use triangle away too. I did that before sending it to vzw. Oddly, my counter was at 0
Click to expand...
Click to collapse
Can you explain triangle away? Is that short for odin and what not?
Mindstar1 said:
Can you explain triangle away? Is that short for odin and what not?
Click to expand...
Click to collapse
No it's not. Triangle away is an app that resets your flash counter to 0. You needed to use it before using odin to stock so it's to late right now.
To get back to where you were you will need to repeat the unlock process by Adam. When you used odin you unrooted and relocked your phone. Think of it being just like the day you got it now.
Sent from my SGH-T889 using xda app-developers app
kintwofan said:
No it's not. Triangle away is an app that resets your flash counter to 0. You needed to use it before using odin to stock so it's to late right now.
To get back to where you were you will need to repeat the unlock process by Adam. When you used odin you unrooted and relocked your phone. Think of it being just like the day you got it now.
Sent from my SGH-T889 using xda app-developers app
Click to expand...
Click to collapse
You sure about this? I thought the only way TriangleAway works is if you flash back stock ROM/kernel. I never used it before and my flash counter was at 0.
Anyways, also I would reset factory defaults if your firmware shows Modified, as well.
There was something on the lock/unlock thread about going back to stock and keeping the phone unlocked. It said if you were using the ota that made the phone so hard to unlock that you should flash a different tar file (an alternate one) to stay unlocked. I will track it down and post it here, but it made it seem like it would keep the phone unlocked.
Sent from my Nexus 7 using Tapatalk 2
kimdoocheol said:
You sure about this? I thought the only way TriangleAway works is if you flash back stock ROM/kernel. I never used it before and my flash counter was at 0.
Anyways, also I would reset factory defaults if your firmware shows Modified, as well.
Click to expand...
Click to collapse
Yes I'm sure. The bootloader had to be unlocked for triangle away to work (see screen shot from triangle away OP). So when he uses odin and re locks it's to late. Also, flashing stock firmware doesn't trip the flash counter.
Sent from my SGH-T889 using xda app-developers app
Mindstar1 said:
There was something on the lock/unlock thread about going back to stock and keeping the phone unlocked. It said if you were using the ota that made the phone so hard to unlock that you should flash a different tar file (an alternate one) to stay unlocked. I will track it down and post it here, but it made it seem like it would keep the phone unlocked.
Sent from my Nexus 7 using Tapatalk 2
Click to expand...
Click to collapse
There is an "alternate restore" file that does not flash a boot loader. If that's what you flashed then your boot loader is still unlocked. In the op you didn't specify you just said you restored to stock which would suggest full stock with a lock bootloader.
Sent from my SGH-T889 using xda app-developers app
kintwofan said:
There is an "alternate restore" file that does not flash a boot loader. If that's what you flashed then your boot loader is still unlocked. In the op you didn't specify you just said you restored to stock which would suggest full stock with a lock bootloader.
Sent from my SGH-T889 using xda app-developers app
Click to expand...
Click to collapse
I did flash the alternate file, sorry for not specifying. The directions were pretty clear that I had to do the alternate file. Anyways, assuming I did that, do I just have to reroot or just flash a rom?
Sent from my Nexus 7 using Tapatalk 2
Mindstar1 said:
I did flash the alternate file, sorry for not specifying. The directions were pretty clear that I had to do the alternate file. Anyways, assuming I did that, do I just have to reroot or just flash a rom?
Sent from my Nexus 7 using Tapatalk 2
Click to expand...
Click to collapse
Im not sure if it's rooted already or not. If it is then install a recovery and flash a ROM. If not then reroot with root 66 odin install a recovery and flash
Sent from my SGH-T889 using xda app-developers app
My solution
OK, so I got the phone back and ran into a few hiccups but got it worked out.
Basically I got the phone and re-rooted it and when I tried to install a new recovery I got an error telling me that I am using bad software and I should take the phone to VZW (yeah right).
I then hopped back on ODIN and went back to stock, same way I did before sending it in to Sammy. Once I did that, I went back to the thread about rooting/unlocking and found that there was an update since I last visited. Now, there was a one click method so I decided to give that a shot. I plugged her in, had some issues with drivers but got it worked out, then ran the process. Once it was finished, all was well.
I am not sure if the phone was still rooted/unlocked or not, but either way the one click method appeared to straighten it out.
I have build ME7 (rooted) and I thought I'd see what happens if I installed a recovery using ROM Toolbox. What happened is that I now cannot boot my phone. I get a large green Andy with "Downloading" and "Do not turn off target!!" below it and the screen is stuck there. I tried a battery pull, but still I'm stuck there. These lines appear at the top left of the screen:
Could not do normal boot.
ODIN MODE
Product Name: SCH-I535
Current binary: Samsung official
System Status: Custom
CSB_CONFIG_LSB: 0x30
Write Protection: Enable
Can anyone please get me booting my phone again? Thanks so much. I tried rebooting into recovery (vol up + home + power), but the phone still does into Downloading mode.
UPDATE - Figured it out. Pressed vol down + power, waited a minute, released power button. Warning screen came up asking me to press vol up to continue into download mode or vol down to cancel. I pressed vol down and voila, I was able to boot my phone. Phew !
I have the same problem.
On boot, I get a screen that says:
Samsung
Unlock
Then it goes to that stupid Downloading Do Not Turn Off Target screen!
How the hell do I get TWRP to load? I can get back into the stock ROM by canceling the update, but I would really like to be able to install Eclipse on this phone!
Thanks guys!
From off - Power, vol up, and I think home button. Once it vibrates once, let go of power. Once it says booting recovery, let go of the other buttons.
Sent from my SCH-I545 using Tapatalk 4 Beta
jova33 said:
From off - Power, vol up, and I think home button. Once it vibrates once, let go of power. Once it says booting recovery, let go of the other buttons.
Sent from my SCH-I545 using Tapatalk 4 Beta
Click to expand...
Click to collapse
That just takes me to the same screens as described above.
This is a brand new phone. Just bought it today. Could they have changed something?
I rooted with SuperSU and installed TWRP with GooManager.
If your on the me7 ota you cant load a custom recovery. Me7 patched the exploit that facilitated the use of a custom recovery. If your on mdk still I would try reinstalling it.
Sent from my SCH-I545 using Tapatalk 2
hexitnow said:
If your on the me7 ota you cant load a custom recovery. Me7 patched the exploit that faciliated the use of a custom recovery. If your on mdk still I would try reinstalling it.
Sent from my SCH-I545 using Tapatalk 2
Click to expand...
Click to collapse
I am on ME7. I tried flashing back to MD2 and MDK and not having any luck. Is this completely impossible and I have just wasted 4 hours of my life? lol
Pretty much sorry to say. Once on it you cant flash back to mdk.
Sent from my SCH-I545 using Tapatalk 2
Can you Odin back to stock ME7?
Sent from my SCH-I545 using Tapatalk 4 Beta
jova33 said:
Can you Odin back to stock ME7?
Sent from my SCH-I545 using Tapatalk 4 Beta
Click to expand...
Click to collapse
Nope. For now you are stuck on the ME7 you have (assuming you got ME7 from the OTA or it was installed when you bought the phone from VZW) which does not (cannot) have a custom recovery nor an unlocked bootloader. All that is possible as of this writing is to be able to root ME7. I have not seen anything documented where the root exploit in ME7 can be undone.
UPDATE - Apparently I was wrong. You can go back to stock ME7. From another thread:
Plug your phone into a Mac or PC, install the VZW utility, select repair device. It will download and flash the official firmware and change your status to official and your splash screen back to the normal samsung logo, not the open lock with custom. It will be ME7 and bone stock. Have done it and rerooted myself. Hope it helps.
And I also found this: http://forum.xda-developers.com/showthread.php?t=2301259
And this: http://droidviews.com/2013/how-to-unroot-samsung-galaxy-s4-gt-i9500-and-reclaim-warranty/
thornev said:
Nope. For now you are stuck on the ME7 you have (assuming you got ME7 from the OTA or it was installed when you bought the phone from VZW) which does not (cannot) have a custom recovery nor an unlocked bootloader. All that is possible as of this writing is to be able to root ME7. I have not seen anything documented where the root exploit in ME7 can be undone.
UPDATE - Apparently I was wrong. You can go back to stock ME7. From another thread:
Plug your phone into a Mac or PC, install the VZW utility, select repair device. It will download and flash the official firmware and change your status to official and your splash screen back to the normal samsung logo, not the open lock with custom. It will be ME7 and bone stock. Have done it and rerooted myself. Hope it helps.
And I also found this: http://forum.xda-developers.com/showthread.php?t=2301259
And this: http://droidviews.com/2013/how-to-unroot-samsung-galaxy-s4-gt-i9500-and-reclaim-warranty/
Click to expand...
Click to collapse
What Verizon utility are you referring to. I had all these issues. Got it back but I just want to go back to stock till all this is resolved. Thanks
jbeezybaby said:
What Verizon utility are you referring to. I had all these issues. Got it back but I just want to go back to stock till all this is resolved. Thanks
Click to expand...
Click to collapse
Sorry, I don't know. I was quoting someone else's post (post 132): http://forum.xda-developers.com/showthread.php?p=44132772
thornev said:
Sorry, I don't know. I was quoting someone else's post (post 132): http://forum.xda-developers.com/showthread.php?p=44132772
Click to expand...
Click to collapse
Ok, Thanks
Back to stock...thanks for the link below. The no-wipe version did not work for me. However, My Samsung Boot Screen still says custom.
I've been running Beans rom all day without issue. I've never updated to ME7. Tonight, I enabled autocorrect in my stock keyboard and read I needed to reboot for it to take effect. Upon reboot, it hangs at the Samsung Screen and Custom at the bottom. I downloaded the no-wipe odin as I can't find a full stock odin tar anywhere, and I've attempted to install it twice but after installation, it reboots, a little green android comes on the screen, and then it goes back to the Samsung Custom screen. I can't access recovery at all. Thoughts?
edpete97 said:
I've been running Beans rom all day without issue. I've never updated to ME7. Tonight, I enabled autocorrect in my stock keyboard and read I needed to reboot for it to take effect. Upon reboot, it hangs at the Samsung Screen and Custom at the bottom. I downloaded the no-wipe odin as I can't find a full stock odin tar anywhere, and I've attempted to install it twice but after installation, it reboots, a little green android comes on the screen, and then it goes back to the Samsung Custom screen. I can't access recovery at all. Thoughts?
Click to expand...
Click to collapse
Any chance someone has a link to a recovery .tar?
Theres a "full stock odin tar" in the dev section. I believe there is also a recovery tar at the link provided in the same thread.
Sent from my SCH-I545 using Tapatalk 2
Just looked there and searched. No luck. Do you have a link to it?
edpete97 said:
Just looked there and searched. No luck. Do you have a link to it?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?p=41680619
It says mkd in the title but its a typo. Its the mdk file.
Sent from my SCH-I545 using Tapatalk 2
hexitnow said:
http://forum.xda-developers.com/showthread.php?p=41680619
It says mkd in the title but its a typo. Its the mdk file.
Sent from my SCH-I545 using Tapatalk 2
Click to expand...
Click to collapse
Thanks. Flashing now. I hope it works. For the life of me I can't figure out what happened. I edited features.xml to change disableautocorrect from true to false. I rebooted, and got stuck at Samsung Custom. I couldn't access recovery. Volume Up + Power did nothing. I got 'Loading Recovery" in blue at the top, but it just flashed and went away. I was running TWRP. Any thoughts on what might have happened?
edpete97 said:
Thanks. Flashing now. I hope it works. For the life of me I can't figure out what happened. I edited features.xml to change disableautocorrect from true to false. I rebooted, and got stuck at Samsung Custom. I couldn't access recovery. Volume Up + Power did nothing. I got 'Loading Recovery" in blue at the top, but it just flashed and went away. I was running TWRP. Any thoughts on what might have happened?
Click to expand...
Click to collapse
This one did the trick, however, it still says Samsung Custom. How do we get rid of that?
If youre unrooted I would boot into stock recovery and factory data reset then reboot a couple of times to see if it registers that its a stock phone. Triangle away supposedly gets rid of it, never used it so I cant confirm. TA needs root tho. The custom boot screen has never bothered me so I havent done much research on it. I have seen a few threads posted about it tho so I know theres an answer somewhere on the forums.
Sent from my SCH-I545 using Tapatalk 2
edpete97 said:
Thanks. Flashing now. I hope it works. For the life of me I can't figure out what happened. I edited features.xml to change disableautocorrect from true to false. I rebooted, and got stuck at Samsung Custom. I couldn't access recovery. Volume Up + Power did nothing. I got 'Loading Recovery" in blue at the top, but it just flashed and went away. I was running TWRP. Any thoughts on what might have happened?
Click to expand...
Click to collapse
here is a video that might help.
Back to stock no custom screen. Thank you. I'm going to try CWM recovery and see if my stability issues go away.
Sent from my SCH-I545 using xda premium
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.