I recently got my replacement EVO3D, rooted it, and flashed SteelRom 1.04. I noticed that my phone randomly "crashed" (for lack of a better word) and, while trying to reboot, became trapped in a never-ending boot loop cycle. Only temp solution was to do a battery pull, which allowed me to boot back into the ROM.
Assuming that it was a problem with the ROM, I tried flashing CleanROM 1.3. The same problem occurred (esp. when I was browsing the web). Worse, even, because even a battery pull didn't fix it.
I nandroided back to Stock rooted to see if the problem remains.
So, besides the simple sharing of my problem, I'd like to know if
Can I reroot after "Complete Stock and S-ON"?
Is this problem stemming from ROM bugs, or maybe is it a hardware defect?
I am still within the 30 days, but I have already had it exchanged once. What should I do?
Thanks will be given to those who help
EDIT: I went back to Stock/S-ON and rerooted. Problem fixed for now
Did you notice this problem before you rooted? If not, then something probably went wrong during the ROM flashing process.
I doubt its the ROM itself otherwise I'm sure there would be plenty of folks posting the issue in the ROM's thread. Likewise, if you didn't have the problem before you rooted, its not a hardware issue either.
A couple of questions:
1. Did you wipe your caches before flashing the ROM?
2. Did you try performing a factory reset after you flashed the ROM and started
having this issue?
mvansomeren said:
Did you notice this problem before you rooted? If not, then something probably went wrong during the ROM flashing process.
I doubt its the ROM itself otherwise I'm sure there would be plenty of folks posting the issue in the ROM's thread. Likewise, if you didn't have the problem before you rooted, its not a hardware issue either.
A couple of questions:
1. Did you wipe your caches before flashing the ROM?
2. Did you try performing a factory reset after you flashed the ROM and started
having this issue?
Click to expand...
Click to collapse
Hi, and thanks for your reply.
I rooted the phone as soon as I got it (maybe stock for 15 minutes) so I didnt have a chance to observe this problem then.
I rooted using Revolutionary 0.4a I flashed SteelRom and CleanROM, both of which showed this problem. I finally flashed ShooterRewind 3D, which hadn't shown this problem until I tried to reply to this thread, ironically.
and to answer your questions:
I do. Actually I always use t3_superwipe_1.3.zip before flashing.
I also tried to "Wipe Data/Factory Reset" after I experienced the problem. No change.
Finally, can you tell me if I can go back to stock using one of the guides and reroot using Revolutionary?
Yes you can go back to stock and back to S-ON. There is a thread in the dev section that will guide you.
http://forum.xda-developers.com/showthread.php?t=1194053
nevermind, did not read OP fully.
mvansomeren said:
Did you notice this problem before you rooted? If not, then something probably went wrong during the ROM flashing process.
I doubt its the ROM itself otherwise I'm sure there would be plenty of folks posting the issue in the ROM's thread. Likewise, if you didn't have the problem before you rooted, its not a hardware issue either.
A couple of questions:
1. Did you wipe your caches before flashing the ROM?
2. Did you try performing a factory reset after you flashed the ROM and started
having this issue?
Click to expand...
Click to collapse
mvansomeren said:
Yes you can go back to stock and back to S-ON. There is a thread in the dev section that will guide you.
http://forum.xda-developers.com/showthread.php?t=1194053
Click to expand...
Click to collapse
tatnai said:
nevermind, did not read OP fully.
Click to expand...
Click to collapse
Thanks Everyone for you're replies. I went back to Stock S-ON, talked with Sprint, they did a ##786# Reset, and then I rerooted with Revolutionary. No problems so far, although Revolutionary did an odd root sequence:
Code:
Rebooting to fastboot
Rebooting to fastboot (again)
Rebooting to fastbook (yet again)
Communications with the device were interrupted, try again
Anyway, I am all set now, so thank you all. Appreciate it.
I apologize in advance if this has been posted elsewhere. I've been looking everywhere I can possibly imagine for the past 3 hours trying to find a solution to no avail.
I'll get right to it. Whenever I try to turn on WI-FI or 4G, I get "Error". No description as to why, or what could be causing it, but heres what I've done.
I'm no noob when it comes to rooting. I had my original Evo rooted most of the time I had it with little to no problems. I've had the 3D since the day it came out, and I haven't felt the need to root. But I got to talking with my buddy earlier and decided I'm going to do it for the OC (and I gotta admit, Synergy looks pretty legit). I'm at hboot 1.5, so I went through the HTC unlock process, and the TWRP recovery process. Then I flashed Synergy, and I set it up, and I get this error.
So I try reflashing it, and that doesnt work. I'm thinking it could be the kernal. So i try 2-3 different kernals (listed on the Synergy thread), and I get the same error. I try a combination of different things for what seems like the next 10 hours (reality, it was about 2) and no matter what I try, I can not seem to get rid of this message. I clear all the cache/dalvik. Wipe back to factory. Hell, I even tried loading the stock ROM and this problem will not go away.
I have the PC86IMG ready to go about to flash back to stock and be done with this root process. The damage is done as far as warranties go, but I would really like to have something to show for it. Does anyone know a way to resolve this without reverting back to locked?
Did you flash the kernel via fastboot? If not the kernels don't flash with the 1.50 hboot, you need to grab the boot.img out of the rom zip and flash via fastboot. Check post 2 in the Synergy thread I believe there are detailed instructions there.
EDIT: Instructions are actually on post 2 of the Eternity thread.
Transformer Sent
Is it not possible to just flash using TWRP?
Edit: I did read that you would need to flash via Fastboot, but I thought that was just initially. So everytime I flash a ROM, I need to adb through fastboot?
That did it. Thanks so much! That was driving me crazy!
(made sure to click "thanks" too)
So I'm posting this here because I don't have enough posts to post in the thread for the Rom its self.
I updated my firmware and flashed this rom exactly like it said to in the thread, and I wiped everything before i flashed the rom its self, then flashed the rom, then the kernel install because I am s-on. This is where my problem lies, I did some searching and maybe I'm missing knowledge to do what posts relating to this said to do but when it went to flash the kernel in hboot, it gave me the Main Version is Older alert and the option to reboot. Now I'm stuck either going back to hboot just to have it try to reflash the kernel and bring back the error message or stuck at the sweet bootscreen |||bored||| put in this rom. If anyone can help me get past this this flash this kernel successfully it would be a big help and a big thank you from me.
I have the .zip that you can flash to write the main version in order for it to get over this problem but I have no idea how to get into recovery from where I'm at, it cant get passed the failed flashing in hboot and adb commands wont load recovery for me.
Burkejt1 said:
So I'm posting this here because I don't have enough posts to post in the thread for the Rom its self.
I updated my firmware and flashed this rom exactly like it said to in the thread, and I wiped everything before i flashed the rom its self, then flashed the rom, then the kernel install because I am s-on. This is where my problem lies, I did some searching and maybe I'm missing knowledge to do what posts relating to this said to do but when it went to flash the kernel in hboot, it gave me the Main Version is Older alert and the option to reboot. Now I'm stuck either going back to hboot just to have it try to reflash the kernel and bring back the error message or stuck at the sweet bootscreen |||bored||| put in this rom. If anyone can help me get past this this flash this kernel successfully it would be a big help and a big thank you from me.
I have the .zip that you can flash to write the main version in order for it to get over this problem but I have no idea how to get into recovery from where I'm at, it cant get passed the failed flashing in hboot and adb commands wont load recovery for me.
Click to expand...
Click to collapse
The fix is listed in boreds rezrom thread in one of his first couple posts. It even says mainver fix...
Sorry didn't read all the way. Lol my bad. Been awake 30+ hours now.
So two things you can do. Put the micro SD card into another phone or computer and temp remove the ph98img.zip file.
Two is pull the micro SD card out about halfway and put the battery in so it touched the contacts and turns on but don't put pressure on the micro SD card. Boot into hboot then lift the battery while pushing it against the contacts and push the microsd in and then volume down to recovery and power to chose and your in the recovery.
Sent from my ADR6425LVW using XDA
Got it, thanks a ton!
I like the SD card halfway in trick because I don't have a micro sd to computer adapter that did the trick for me
Mirror for that mainver file...
Burkejt1 said:
So I'm posting this here because I don't have enough posts to post in the thread for the Rom its self.
I updated my firmware and flashed this rom exactly like it said to in the thread, and I wiped everything before i flashed the rom its self, then flashed the rom, then the kernel install because I am s-on. This is where my problem lies, I did some searching and maybe I'm missing knowledge to do what posts relating to this said to do but when it went to flash the kernel in hboot, it gave me the Main Version is Older alert and the option to reboot. Now I'm stuck either going back to hboot just to have it try to reflash the kernel and bring back the error message or stuck at the sweet bootscreen |||bored||| put in this rom. If anyone can help me get past this this flash this kernel successfully it would be a big help and a big thank you from me.
I have the .zip that you can flash to write the main version in order for it to get over this problem but I have no idea how to get into recovery from where I'm at, it cant get passed the failed flashing in hboot and adb commands wont load recovery for me.
Click to expand...
Click to collapse
Hey bud same issue here do you happen to have a link to that file...the op's link in that thread is 404 ...thx in advance
OK, guys, we have a TON of information here, and MAYBE I am not following things, so can we set a chronological order to how we go about GETTING to installing ROMs?
Specifically: Root first, then UNLOCK, then Flash? Seriously, the WEALTH of information is getting hard to follow, and I haven't been able to find a DECENT guide as to what steps to do first. I HAVE found Lokifish Mars' post witht he root-unlock-relock files but ARE they in the "order to be performed on his post located here: http://forum.xda-developers.com/showpost.php?p=20331623&postcount=6
Now, my problem is: Flashed Th3Bill's CM10_2012-1114 and CM10_2012_1117 and ran into some major errors. SOOOOOO......
....Trying to .sbf back to stock 198_7 and keep bootlooping (?) and get stuck at the infernal "Now" screen...... Not sure what to do at this point. I have tried going back through and reflashing the .sbf's, going into fastboot to erase/install recovery and get errors "failing to communicate" "flash failed" etc. Someone, HELP!!!
When you sbf back to stock, you have to go into stock recovery and wipe data
Yes there is a lot of information, and that can be very confusing. Qbking77's vids help out tremendously with getting to know the flashing process.
Sent from my MB855 using xda premium
As stated, make sure after you sbf back to stock, go into recovery mode( when you boot into recovery you have to press both volume up and down at the same time to see the recovery menu), then wipe data. That will get you booted up to a stock phone. Then follow the instructions in the thread you linked to. Root first, then unlock and flash your recovery of choice. As a side note, once you unlock for the first time, if you decide to re-lock or you have to go back to stock for any reason you no longer have to input your unique I.D. when you unlock again. Good luck
Fixed it!
Thanks for all the help guys.
Yes, I DID find that I needed to go back and wipe /data, /cache, etc., etc., However, my CM10 CWMR (Th3Bill's V1) got wiped when I sbf'd. So then had to figure out how to re-root, re-unlock, and reinstall Jokers CWM Recovery V3, but I DID finally get it to go! SOOOOO, Now that I have made myself a cheat sheet, since I try not to sbf/wipe often, I am also going to work on a script in Windows that will do the requisite work for me to bring me back to absolute stock if I ever need to do so in the future. Now, time to go play with some of the newer Aroma-Based ROMS the all these AWESOME Devs are working on!!!!! :good:
Hello first time rooting this phone. Its a SGH-I777. I used the guide from galaxys2root.com/. At first it didnt work because my computer didnt recongnize my phone. I tried a different computer and it seemed successful until it rebooted. When the phone rebooted it did nothing but stay on the first screen. I still have the ability to get into Odin mode(download mode), but that is it. When i put the phone in download mode and use Odin it allows me to download the "zimage" but after rebooting it is the same exact thing. I have tried the one click root, one click factory restore. Tried restoring it on Kies. and nothing work took it to a store and the guy said he tried but it would stop in the middle of the download the only option i had with him was purchasing a new mother board for $80. Does anyone have a solution that can help me fix my phone.
Before i attempted to root it, it had OS 2.3.6 with kernal 2.6.35.7.
Go to the development section and read the stickies. There you will find stock rooted packages you can flash with Odin.
Sent from my SGH-I777 using xda premium
@jmula,
Enter recovery and perform a wipe data/factory reset. That may clear the failure to boot. If not you'll need to flash back to stock and start over.
The yellow trangle is a result of flashing a custom kernel using Odin or Heimdall, and is expected. You are not the first person having problems with the tools provided by GalaxyS2Root. In the future, I would recommend you avoid his site.
And... as suggested, read and study till you understand the basics. Then if you have questions, feel free to ask.
creepyncrawly said:
@jmula,
Enter recovery and perform a wipe data/factory reset. That may clear the failure to boot. If not you'll need to flash back to stock and start over.
The yellow trangle is a result of flashing a custom kernel using Odin or Heimdall, and is expected. You are not the first person having problems with the tools provided by GalaxyS2Root. In the future, I would recommend you avoid his site.
And... as suggested, read and study till you understand the basics. Then if you have questions, feel free to ask.
Click to expand...
Click to collapse
the only option that i have is to put the phone in download mode. when i try to download any kernel it reboots and does not go past the booting screen with the triangle.
jmula said:
the only option that i have is to put the phone in download mode. when i try to download any kernel it reboots and does not go past the booting screen with the triangle.
Click to expand...
Click to collapse
You should be able to enter recovery. Hold down all three buttons, vol+ vol- and pwr, continuously until the phone boots into recovery. It could take 10 or 15 seconds or more. If that is unsuccessful, then since you can enter download mode, you will need to flash back to stock, or stock plus root. That is not just a kernel, but the entire package. Please see the links in my sig for instructions.
The dropbox links in the download repository are temporarily suspended until probably Monday night or Tuesday as someone abused and over-downloaded. But the hotfile links still work.
creepyncrawly said:
You should be able to enter recovery. Hold down all three buttons, vol+ vol- and pwr, continuously until the phone boots into recovery. It could take 10 or 15 seconds or more. If that is unsuccessful, then since you can enter download mode, you will need to flash back to stock, or stock plus root. That is not just a kernel, but the entire package. Please see the links in my sig for instructions.
The dropbox links in the download repository are temporarily suspended until probably Monday night or Tuesday as someone abused and over-downloaded. But the hotfile links still work.
Click to expand...
Click to collapse
i Downloaded ''UCLE5 Stock ICS plus Root'' . i placed the phone in download mode started Odin and placed file in PDA. It starts but gets stuck at cache.img
jmula said:
i Downloaded ''UCLE5 Stock ICS plus Root'' . i placed the phone in download mode started Odin and placed file in PDA. It starts but gets stuck at cache.img
Click to expand...
Click to collapse
The next thing I would suggest is to try and flash the UCKH7 full stock package with bootloaders. However, as the dropbox links in the download repository are currently suspended, you will have to download it from SamFirmware. To be able to download, you will need to register for free if you havn't already. Search sgh-i777 in the upper right hand corner of the page, then download the I777UCKH7 version. Let us know if that will flash.
Ok it finally wokred after countless times of changing usb ports. I used the one click recovery. It restroed my phone to 2.3.4 i had 2.3.6. I tried to update by kies to 4.01 and it didnt work. Kies froze. The queestion is how do i safltey root the phone?
jmula said:
Ok it finally wokred after countless times of changing usb ports. I used the one click recovery. It restroed my phone to 2.3.4 i had 2.3.6. I tried to update by kies to 4.01 and it didnt work. Kies froze. The queestion is how do i safltey root the phone?
Click to expand...
Click to collapse
Flash a .tar version of a custom kernel with Odin. I always use an old siyah.tar, but that's just me. There are other methods floating around but that's the quickest and easiest for me. I think there's an old entropy dd.tar around somewhere too. But just flash it through Odin and you're good to go, assuming you flashed one for your version of android. If you just want to get into recovery to flash something this works as well.
There may be links to tar versions of the kernels in creepy's sig I don't remember offhand.
Ok since i do not want to brick my phone again where it is just stuck at the boot loop. I tried looking for ways to root and when i tried some of them my phone went back to the problem it had it the beginning. Should i just call it quits or do you guys have a guide?
jmula said:
Ok since i do not want to brick my phone again where it is just stuck at the boot loop. I tried looking for ways to root and when i tried some of them my phone went back to the problem it had it the beginning. Should i just call it quits or do you guys have a guide?
Click to expand...
Click to collapse
Give up???
I personally don't think flashing a kernel with odin is the best way to root. It increments the flash counter, for one thing, though I'm not sure how many people care about that anymore. I would suggest that you use the stock plus root package to root the phone with odin. See the links in my sig.
Guide... did someone say guide?
Feeling the pain....
creepyncrawly said:
@jmula,
Enter recovery and perform a wipe data/factory reset. That may clear the failure to boot. If not you'll need to flash back to stock and start over.
The yellow trangle is a result of flashing a custom kernel using Odin or Heimdall, and is expected. You are not the first person having problems with the tools provided by GalaxyS2Root. In the future, I would recommend you avoid his site.
And... as suggested, read and study till you understand the basics. Then if you have questions, feel free to ask.
Click to expand...
Click to collapse
First, to Creepy....you've been a great resource here and I read a lot of what you post and you got me out of the very jam being discussed here. I made the mistake of trying to root via the galaxys2root.com site (actually, I thought it was a different site...was redirected), got the i9100 screen and a boot loop...couldn't go anywhere. I came back here and found resources eventually unrooting my phone all the way back to 2.3.4, then moved to 2.3.6, then the stock android 4.0.3 which updated to 4.0.4.
But I still want to root (4.0.4 shuts itself down A LOT...more than 4.0.3) and I have a Galaxy note 10.1 with JB 4.1.2 and I LOVE IT! I feel on a mission to get rooted and try out some of the JB roms I see talked about here, but can't seem to find the best way to root. I've heard exynosabuse referenced here (no links to it though) and I don't want to use the wrong one and mess up my phone. I've been reading for weeks here and there's obviously a lot of great material, but I'm not sure which material is critical to understand, and which is "nice to know" but might not even apply, and which material isn't even right. Very frustrating.
Judi
judib said:
First, to Creepy....you've been a great resource here and I read a lot of what you post and you got me out of the very jam being discussed here. I made the mistake of trying to root via the galaxys2root.com site (actually, I thought it was a different site...was redirected), got the i9100 screen and a boot loop...couldn't go anywhere. I came back here and found resources eventually unrooting my phone all the way back to 2.3.4, then moved to 2.3.6, then the stock android 4.0.3 which updated to 4.0.4.
But I still want to root (4.0.4 shuts itself down A LOT...more than 4.0.3) and I have a Galaxy note 10.1 with JB 4.1.2 and I LOVE IT! I feel on a mission to get rooted and try out some of the JB roms I see talked about here, but can't seem to find the best way to root. I've heard exynosabuse referenced here (no links to it though) and I don't want to use the wrong one and mess up my phone. I've been reading for weeks here and there's obviously a lot of great material, but I'm not sure which material is critical to understand, and which is "nice to know" but might not even apply, and which material isn't even right. Very frustrating.
Judi
Click to expand...
Click to collapse
The ExynosAbuse application is the only practical way to root 4.0.4 without changing base. You can download it as an attachment in the OP of the developer's thread, but read through the thread first to understand its limitations and risks.
Alternatively, you could flash 4.0.3 plus root from the development forum. If you choose that route, please read the thread to understand how to install a custom kernel, which is recommended whether you plan to install a custom firmware or not. The custom kernel will contain ClockworkMod Recovery so you can flash the firmware of your choice if you wish.
There are really several routes you could choose. All of them work. Another would be to flash back to stock Gingerbread plus root. For that see my guide How to Flash Custom Binaries Without Ever Incrementing the Flash counter!! (link in sig)
Hmmmmm..
Well, I see that their are many, more experienced than me following this thread and my following comment is not meant to jump on the knowledge train here, but............... I had the same event happen as the orig poster earlier today. I had installed an app,I then rebooted and it got a bit stuck on the Galaxy SII, What I did was go into recovery ,cleared the Dalvik cache and that is all I cleared. Then I re-installed the RR Rom .rar, which I keep on my SD, over everything and rebooted, it came back as it was 4 mins before . All I did after, was do a system restore(only) using Titanium BU. So when I see all the "clear and restore this and that" I started to doubt some of the more experienced than I. My 2 cents is, that, if one does not know EXACTLY ,how to correct an issue,leave it for our more knowledgeable brothers and sisters.
If I am wrong ,please except my appology.
b0bb said:
Well, I see that their are many, more experienced than me following this thread and my following comment is not meant to jump on the knowledge train here, but............... I had the same event happen as the orig poster earlier today. I had installed an app,I then rebooted and it got a bit stuck on the Galaxy SII, What I did was go into recovery ,cleared the Dalvik cache and that is all I cleared. Then I re-installed the RR Rom .rar, which I keep on my SD, over everything and rebooted, it came back as it was 4 mins before . All I did after, was do a system restore(only) using Titanium BU. So when I see all the "clear and restore this and that" I started to doubt some of the more experienced than I. My 2 cents is, that, if one does not know EXACTLY ,how to correct an issue,leave it for our more knowledgeable brothers and sisters.
If I am wrong ,please except my appology.
Click to expand...
Click to collapse
I don't know what you're trying to get across here. Yes, restoring a backup nandroid works. Yes, you can try wiping cache and dalvik to see if it fixes an issue. Yes you can restore apps via titanium backup. All these things are indeed true.
Phalanx7621 said:
I don't know what you're trying to get across here. Yes, restoring a backup nandroid works. Yes, you can try wiping cache and dalvik to see if it fixes an issue. Yes you can restore apps via titanium backup. All these things are indeed true.
Click to expand...
Click to collapse
Well if you did not fully grasp what I was trying to get across,you seemed to get it correct with your statement.
b0bb said:
Well if you did not fully grasp what I was trying to get across,you seemed to get it correct with your statement.
Click to expand...
Click to collapse
And yet you say, "All I did after, was do a system restore(only) using Titanium BU." This may have worked for you, but this is an absolute recipe for disaster, and should not be given as a recommendation.
And further, from what you say, you did not have the "same event happen as the orig poster." Instead you "had installed an app,I then rebooted and it got a bit stuck on the Galaxy SII." This is by far not the same as trying to root with a tool from GalaxyS2Root.
creepyncrawly said:
And yet you say, "All I did after, was do a system restore(only) using Titanium BU." This may have worked for you, but this is an absolute recipe for disaster, and should not be given as a recommendation.
And further, from what you say, you did not have the "same event happen as the orig poster." Instead you "had installed an app,I then rebooted and it got a bit stuck on the Galaxy SII." This is by far not the same as trying to root with a tool from GalaxyS2Root.
Click to expand...
Click to collapse
Hey Bro, I think you think that I am challenging you, trust me I am not and I thank you for correcting me and putting me in my place, which is a bit phone techie challenged, I'll stick to building submarines. Thanks for what you do here.
b0bb said:
Hey Bro, I think you think that I am challenging you, trust me I am not and I thank you for correcting me and putting me in my place, which is a bit phone techie challenged, I'll stick to building submarines. Thanks for what you do here.
Click to expand...
Click to collapse
Not at all. I want people to help others here. I want you to help other here as well. But it is important to post only accurate information. Inaccurate information can cause someone to do the wrong action. So I always correct misinformation.