Related
I am having the same problem with Contacts and with process com.motorola.contacts force closing that many others are having. I had rooted as well as uninstalled bloatware (instead of freezing, yes, I know!). Tried unrooting, reinstalling Yahoo and AT&T apps as suggested, factory resets, everything. Contacts still acts the same; that is, I can get to it but can't edit individual contacts nor get to Contacts Storage. I think it must have something to do with AT&T Address Book, which won't reinstall (says not supported but was there before).
At this point I just want to return Atrix 2 to its stock, 2.3.6 configuration and start all over. Can anyone help me, or is that not "out" yet?
Follow the instructions on flashing the 2.3.5 FXZ listed here (the beginner's guide) and then use the OTA update to get to 2.3.6. Next time make a CWM backup before you try any ROMs! It is inevitable that you'll eventually get stuck in some sort of boot loop.
bmbanker said:
Follow the instructions on flashing the 2.3.5 FXZ listed here (the beginner's guide) and then use the OTA update to get to 2.3.6. Next time make a CWM backup before you try any ROMs! It is inevitable that you'll eventually get stuck in some sort of boot loop.
Click to expand...
Click to collapse
I will try that. It looks pretty complicated...I'll be studying for awhile!
It's not hard at all! Just follow the instructions listed EXACTLY and make sure that your battery is well charged before you do this -- if it dies during the middle of something like this, you could run into a tricky problem.
motocyndi said:
I will try that. It looks pretty complicated...I'll be studying for awhile!
Click to expand...
Click to collapse
It's alot easier than it sounds....and im no pro. I was able to successfully flash 2.3.5 to mine that way the first time around following the instructions in the noob thread.
Atrix 2//RebelROM//Tapatalk 2
so let me get this straight....
I had 2.3.5 rooted. I accepted the OTA update to 2.3.6, so naturally, it un-rooted me, although the superuser is still there. I tried the one click method for 2.3.6 after it came out, as I am a total NOOB and was afraid to try it and screw things up. That doesn't work. I tried to unroot it using the same method. Also didn't work. The superuser is still there and denying permissions.
Soooooooo, I have decided to do the FXZ method in the in the noob/general forum. I'm still unclear and afraid about how to do it. Am I supposed to go through the first 11 steps, then do the "replace" step that is added as a note? Speaking of the added note. It says to "move all the the items in it to the stock fxz". The "stock FXZ" is what i downloaded and did in step 1-11, right? I have searched the forums and this was the best place I could see to ask. Sorry for my extreme NOOBness.
Thanks in advance for helping, or just taking the timpe to read my post!
psdroid said:
I had 2.3.5 rooted. I accepted the OTA update to 2.3.6, so naturally, it un-rooted me, although the superuser is still there. I tried the one click method for 2.3.6 after it came out, as I am a total NOOB and was afraid to try it and screw things up. That doesn't work. I tried to unroot it using the same method. Also didn't work. The superuser is still there and denying permissions.
Soooooooo, I have decided to do the FXZ method in the in the noob/general forum. I'm still unclear and afraid about how to do it. Am I supposed to go through the first 11 steps, then do the "replace" step that is added as a note? Speaking of the added note. It says to "move all the the items in it to the stock fxz". The "stock FXZ" is what i downloaded and did in step 1-11, right? I have searched the forums and this was the best place I could see to ask. Sorry for my extreme NOOBness.
Thanks in advance for helping, or just taking the timpe to read my post!
Click to expand...
Click to collapse
Unzip the stock fxz and copy the extra files into it. Accept any error it may give you. The open rsd and click the "..." Button and find the fxc that you modified and then hook your phone up in Detroit and hit the start button. Should be golden after
Running AtrixBlaze 3 on my Atrix 2.
bmbanker said:
It's not hard at all! Just follow the instructions listed EXACTLY and make sure that your battery is well charged before you do this -- if it dies during the middle of something like this, you could run into a tricky problem.
Click to expand...
Click to collapse
Everything did work like a charm finally; thank you so much for being so helpful, everyone! I feel a little less nooby now.
Thanks!!!
DarkJatrix said:
Unzip the stock fxz and copy the extra files into it. Accept any error it may give you. The open rsd and click the "..." Button and find the fxc that you modified and then hook your phone up in Detroit and hit the start button. Should be golden after
Running AtrixBlaze 3 on my Atrix 2.
Click to expand...
Click to collapse
Downloading FXZ as we speak. i will give an update as soon as I try it out! Thanks again.
IT WORKED!!!!
As the title states, it worked. I downloaded the fxz, replaced the files, ran it, the re-rooted after everything came back up. Then I did the OTA rootkeeper procedure and now I am about to takt the ota. Will let you know if anything goes wrong after that. Thanks again for all the help and encouragement.
psdroid said:
As the title states, it worked. I downloaded the fxz, replaced the files, ran it, the re-rooted after everything came back up. Then I did the OTA rootkeeper procedure and now I am about to takt the ota. Will let you know if anything goes wrong after that. Thanks again for all the help and encouragement.
Click to expand...
Click to collapse
Why not just take the ota then root it with motto fail one click?
Sent from my MB865 using Tapatalk 2 Beta-4
DarkJatrix said:
Why not just take the ota then root it with motto fail one click?
Sent from my MB865 using Tapatalk 2 Beta-4
Click to expand...
Click to collapse
I just wanted to be sure that I wouldn't lose root again if I ever get another ota. If the motto fail incorporates that, I wasn't aware.
I'm just starting to learn how to do all this...
I have CWM 5.8.4.0 installed, UCLD2 and Superuser 3.0.7
I've lost root access and can't figure out how to get it back. I've been searching the forum but can't quite seem to find what I need. I went through the process for rooting and no good result. I thought maybe I should just do a recovery back to 2.3.6 in CWM and it says the MD5 mismatch. I thought I had a solid backup for my original phone all this time. I restored it once through ROM manager and it worked great. I did a factory reset and went through the rooting process again and still nothing.
What my goal is, is to flash to a ROM that people are liking and that performs well. Was going to try SKYICS 4.2E, but I don't think I should attempt anything until I figure out how to go to a backup consistently. I could back up what I have now, which gives me a working phone, but I don't really like it. Most of my apps don't work correctly on it. What I really don't want to do is go forward again and really have it jacked up and not be able to go to a previous backup.
Where should I start? I'm guessing getting root access again. I'm assuming I won't be able to flash another ROM until I get this.
Thanks for the help!
I was having that problem too, I used this script "su_ics_v3.1_updated_wraithdu_installer" also install and run busybox if you haven't already or just flash an insecure kernel (make sure its right for your rom)
jordan9812 said:
Just go read the faxes then after hours of that restore to stock and read the rooting guide good luck
Sent from my SAMSUNG-SGH-I727 using XDA
Click to expand...
Click to collapse
Okay funny guy... What was my first line again??? lol
I don't even know how to get back to stock. I can do that even if I don't have root access? I'm just trying to learn the mechanics of all this. Learn what does what... CWM is a means to write to the phone from boot. Can install different ROMs and parts of ROMS, ie. lock screens... Then there's kernels that operate the hardware that have to be compatible with the ROM. People talk about way more than I can comprehend at this point; it's one step at a time for learning.
So---first step is what? Read for hours? I don't understand what I'm reading. haha
32dave said:
I was having that problem too, I used this script "su_ics_v3.1_updated_wraithdu_installer" also install and run busybox if you haven't already or just flash an insecure kernel (make sure its right for your rom)
Click to expand...
Click to collapse
What was the very first line in my post? lol
I'm not a programmer, but have taken some Java classes.
I don't know how to use scripts at all. In my mind, I can't do anything until I get root access. I'm not sure what the MD5 mismatch means either. I'm definitely reading things, but it seems that either I'm not understanding or that it's a tangent and not really related to what I'm trying to do...
You don't need root access. All you need is cwm to flash roms, kernels and radios
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
I'm starting to figure that out. This stuff isn't very simple. It seems like it is, but for some reason it's just not. It's like a tractor pull. The more I learn the harder it gets to learn more because the crap gets too deep!
CodeRedDewd said:
I'm starting to figure that out. This stuff isn't very simple. It seems like it is, but for some reason it's just not. It's like a tractor pull. The more I learn the harder it gets to learn more because the crap gets too deep!
Click to expand...
Click to collapse
read the n00b posts and stickies, its really not that hard, all roms r rooted..meaning u dont have to root, u can do root ur self for stock firmware, the hard part(not really hard) is flashing cwm(clockworkmod recovery) via odin, once u do that flash a rom according to the rom u want to use, read this on howto root and flash cwm using odin http://forum.xda-developers.com/showthread.php?t=1340526
to go back to stock is very easy also via odin, read this link on howto http://forum.xda-developers.com/showthread.php?t=1652398
once u find a rom read all about that rom on how to flash it and any trouble shooting
clockworkmod recovery replaces the stock recovery so u can do wonderful things to our phones, it's this application that installs(flashes) the roms
Thanks for the info... I installed another ROM that I liked better, SKYICS without the root. I wanted to tweek something else and I cannot do it unless I get root access. Using Odin is pretty easy like you said and CW recovery. The first link you posted is the one I originally followed and it was rooted. I went through the process again and no root. Titanium just says sorry I don't have permission. I did a factory reset and tried to root again and nothing. I'm not sure where to go from here to get the root back....
If you flash a custom ROM they are already rooted
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
I don't have root access. I did have it, but lost it when I installed ICS 4.0.4.
Titanium is saying it can't do anything... I just checked and now it's working. I didn't change anything. That's weird. It asked me for permission and is now in the superuser list. I couldn't get anything to do that for a few days. I'll just have to say Okay and move on. lol
CodeRedDewd said:
I don't have root access. I did have it, but lost it when I installed ICS 4.0.4.
Titanium is saying it can't do anything... I just checked and now it's working. I didn't change anything. That's weird. It asked me for permission and is now in the superuser list. I couldn't get anything to do that for a few days. I'll just have to say Okay and move on. lol
Click to expand...
Click to collapse
thats why i said when u use a rom "once u find a rom read all about that rom on how to flash it and any trouble shooting", its usually a bad flash, if reflashing doesnt work then redownload the rom and again and flash
u could of flashed superuser, but the problem was the rom didnt install properly......good u got it solved
32dave said:
I was having that problem too, I used this script "su_ics_v3.1_updated_wraithdu_installer" also install and run busybox if you haven't already or just flash an insecure kernel (make sure its right for your rom)
Click to expand...
Click to collapse
Can you be more specific on rooting 4.0.4? I didn't like SKY ICS and installed Embryo. It's much faster than the other, but now I don't have root again. I don't know how I got root access to SKY ICS, because when I asked I didn't have root, but 2 days later I suddenly had the access and did nothing.
I'm browsing around trying to find how people root 4.0.4...
CodeRedDewd said:
I'm browsing around trying to find how people root 4.0.4...
Click to expand...
Click to collapse
I used the 1st 3 steps for my ULCE2 [GUIDE]{ROOT}How To Root The ICS Leak
pc103 said:
I used the 1st 3 steps for my ULCE2 [GUIDE]{ROOT}How To Root The ICS Leak
Click to expand...
Click to collapse
That's exactly what I did and it's not working. I'm using CWM touch and tried 2 different superuser files I've found and nothing. BusyBox won't install because it says it doesn't have permission and I can't mount the drive in the phone with a file explorer because it's not rooted.
I read somewhere that I may need to install an "insecure kernel", or maybe a ROM that is already rooted? I can't figure those things out....
I've even started all over and flashed the UCLE2 again, cleared all data. then installed Embryo, CWM then superuser. No luck. I'm at a loss here.
Update: I have tried these superuser files.
Superuser, Superuser-3.0.7-d-signed and Superuser-3.0.7-efghi-signed. The last one gave me root access for 4.0.4. I'll attach the file for others.
CodeRedDewd said:
That's exactly what I did and it's not working. I'm using CWM touch and tried 2 different superuser files I've found and nothing. BusyBox won't install because it says it doesn't have permission and I can't mount the drive in the phone with a file explorer because it's not rooted.
I read somewhere that I may need to install an "insecure kernel", or maybe a ROM that is already rooted? I can't figure those things out....
I've even started all over and flashed the UCLE2 again, cleared all data. then installed Embryo, CWM then superuser. No luck. I'm at a loss here.
Update: I have tried these superuser files.
Superuser, Superuser-3.0.7-d-signed and Superuser-3.0.7-efghi-signed. The last one gave me root access for 4.0.4. I'll attach the file for others.
Click to expand...
Click to collapse
This superuser zip gave root access where other versions did not for 4.0.4.
CodeRedDewd said:
That's exactly what I did and it's not working. ...
I read somewhere that I may need to install an "insecure kernel", or maybe a ROM that is already rooted?....
I've even started all over and ...I'm at a loss here..
Click to expand...
Click to collapse
(See below)
CodeRedDewd said:
This superuser zip gave root access where other versions did not for 4.0.4.
Click to expand...
Click to collapse
...which is why we're focused on the one method with its 3 or 4 steps we linked. [Confession] My bad, I forgot to mention as is often covered in the threads - CWM flashing the zip took me a few (4) retries. I only backed up as far as 'select update from sdcard' for each retry, all within the same recovery session. Maybe this will help?
pc103 said:
(See below)
...which is why we're focused on the one method with its 3 or 4 steps we linked. [Confession] My bad, I forgot to mention as is often covered in the threads - CWM flashing the zip took me a few (4) retries. I only backed up as far as 'select update from sdcard' for each retry, all within the same recovery session. Maybe this will help?
Click to expand...
Click to collapse
It wasn't the steps ther were wrong. It was superuser that was wrong. I tried and tried with 2 different ones and nothing. Then I found another version that worked on the first attempt. The versions I tried first worked on 2.3.5, but not on 4.0.4.
I'm attaching the one I found that worked the first time. I tried the others about 20 times each and nothing, but they worked before. I haven't read anywhere that there are different versions of superuser that only root certain builds. I found it out the hard way.
If i can remember "SOME" superuser zips need to be flashed a few times before they flash successfully.
Sent from my SAMSUNG-SGH-I727 using XDA
jyazzie110 said:
If i can remember "SOME" superuser zips need to be flashed a few times before they flash successfully.
Sent from my SAMSUNG-SGH-I727 using XDA
Click to expand...
Click to collapse
Thanks. I have read that, and that it works sometimes when it says it fails. The problem was that there are a few versions of superuser. I had two that worked on previous versions of android, like 2.3.6, but they won't work on 4.0.4. I found a different one named. "Superuser-3.0.7-efghi-signed" that worked first time. I tried the others more than enough. They don't work on 4.0.4. It's funny no one has mentioned this before.
Let's be clear.
I am glad you reached this goal CodeRed. Enjoy!
CodeRedDewd said:
...It wasn't the steps that were wrong....The problem was that there are a few versions of superuser.
Click to expand...
Click to collapse
Yes, but there was only one version in the [GUIDE]{ROOT}How To Root The ICS Leak.
CodeRedDewd said:
I had two that worked on previous versions of android, like 2.3.6, but they won't work on 4.0.4. I found a different one named. "Superuser-3.0.7-efghi-signed" that worked first time. I tried the others more than enough. They don't work on 4.0.4. It's funny no one has mentioned this before.
Click to expand...
Click to collapse
I had the older zip too, but it was all properly instructed in our [Dev] thread. Copperhed posted 'This will root 2.3.5 or 2.3.6' for an earlier Superuser.zip last November, linked in InSaiyanone's excellent all-in-one guide.
Needing to root 4.0.4 would lead us to the next stickie, where projeqht linked
Starskyrob's 'Step 2: Flash Attached zip from recovery.' in his [GUIDE]{ROOT}How To Root The ICS Leak, posted March 28th, referring to the zip you and I succeeded with. I think anyone reading the stickies should find the same guidance.
This is a method to root Atrix 2 running on Android GB(2.3.6) / ICS(4.0.4).
EDIT: Last updated on 26th July 2012
WHAT WORKS: Everything including the setting inside superuser which was not working in superuser 3.1
If you use this MOD, then please click on thanks button below.
I have updated this method to latest version of superuser 3.1.3 and su binary 3.1.1 for better compatibility with various Apps.
By following the below instructions you will be rooted in no time. If you have any questions feel free to ask.
Features added in superuser 3.1.3:
1.Temp unroot
2. Ota survival
3. Outdated binary Notification
Method:
1. Enable "USB debugging" in your phone settings
2. Download the attachment Named "Motofail Root (superuser 3.1.3, su binary 3.1.1).zip" to root Android GB(2.3.6)
or Attachment named "ICS_root(superuser 3.1.3 and su binary 3.1.1) .zip" to root Android ICS (4.0.4).
3. Uninstall your old Motorola drivers from PC and install these new drivers.
4. Connect your phone with original USB cable that came with your phone.
5. To root Android GB(2.3.6) click on "Click-To-Root.bat" in the attachment folder or
To root Android ICS(4.0.4) click on "Root.bat" in the attachment folder
6.Your phone will reboot 2-3 times don't remove the USB cable during this process
NOTE: If you are unable to Root even after following the above MOD then perform a Factory restore after OTA update and retry.
Can i root the ics with this?
And my phone is rooted,but can i re-root it?
atrix2 said:
Can i root the ics with this?
And my phone is rooted,but can i re-root it?
Click to expand...
Click to collapse
YES
Thanks for the new update.......
Sent from my GT-S6102 using Tapatalk 2
Please be aware that other A2 users have had issues with Superuser versions higher than 3.0.3.
Sent from my SAMSUNG-SGH-I747 using xda premium
jimbridgman said:
Please be aware that other A2 users have had issues with Superuser versions higher than 3.0.3.
Sent from my SAMSUNG-SGH-I747 using xda premium
Click to expand...
Click to collapse
I haven't been having problems, but I always have been using the older motofail exploit then updating the binary from within the app.
lkrasner said:
I haven't been having problems, but I always have been using the older motofail exploit then updating the binary from within the app.
Click to expand...
Click to collapse
I had the issue the other day, on stock 2.3.6, I also saw that alterdlikeness had a similar issue as well. It was updating past the 3.03 on both su and Superuser.
I had issues on my A2 with 3.1 only, and it would just FC and not work. I had to remove and basically re-root, and leave it at 3.0.1.
jimbridgman said:
I had the issue the other day, on stock 2.3.6, I also saw that alterdlikeness had a similar issue as well. It was updating past the 3.03 on both su and Superuser.
I had issues on my A2 with 3.1 only, and it would just FC and not work. I had to remove and basically re-root, and leave it at 3.0.1.
Click to expand...
Click to collapse
hmm. good to know in case it ever happens to me. I guess I will know I am not alone.
I don't know about other variants but it is working on ATT ROM and I have also assisted the same method to one user in India on androidcentral who was on MEART ROM and it even worked for him.
prasannapmv said:
I don't know about other variants but it is working on ATT ROM and I have also assisted the same method to one user in India on androidcentral who was on MEART ROM and it even worked for him.
Click to expand...
Click to collapse
You missed the point I was trying to make to those wanting to update thier binaries for su and superuser.... not new root exploits.
I just want everyone to know there are issues with 3.1... however today an update to 3.1.2 today has been proven to work for those having the issues that both alteredlikness and I have seen with FCs.
Sent from my MB865 using xda premium
On Stock 2.3.6 rooted. The new updates to the Superuser app allow you to update the binary and use the settings now.
Updating thread for superuser 3.1.2 now..
This method works as stated today I was trying to update my su binary but update was not getting successful so I unrooted and rooted back using this method now everything is updated and running smoothly.
About to root my girlfriends phone to eventually install Lithium.
Coming from a AT&T Galaxy S2 so things are a bit different here.
Should I use this method or Jimmy's from this thread? http://forum.xda-developers.com/showthread.php?t=1327741
After that what steps do I need to take to get CWM installed so I can backup and install a new ROM?
Thanks thanks!
seanpr123 said:
About to root my girlfriends phone to eventually install Lithium.
Coming from a AT&T Galaxy S2 so things are a bit different here.
Should I use this method or Jimmy's from this thread? http://forum.xda-developers.com/showthread.php?t=1327741
After that what steps do I need to take to get CWM installed so I can backup and install a new ROM?
Thanks thanks!
Click to expand...
Click to collapse
I think they are the same, except this one has a more updated version of superuser - I think (someone correct me if I'm wrong).
I personally have always used the one in Jimmy's thread and just update the superuser app and binary (and, thanks for reminding me about that post - I never thanked him until today - and due credit to p3droid & JRW 28 of course).
As for CWM recovery, just install the A2 Bootstrap app after being rooted. Use the bootstrap app - top button, OK, bottom button to boot into recovery.
Good luck to you and your girl!
alteredlikeness said:
I think they are the same, except this one has a more updated version of superuser - I think (someone correct me if I'm wrong).
I personally have always used the one in Jimmy's thread and just update the superuser app and binary (and, thanks for reminding me about that post - I never thanked him until today - and due credit to p3droid & JRW 28 of course).
As for CWM recovery, just install the A2 Bootstrap app after being rooted. Use the bootstrap app - top button, OK, bottom button to boot into recovery.
Good luck to you and your girl!
Click to expand...
Click to collapse
Boom, was one setup ahead of you and just finished all that. Currently backing up in CWM and waiting for a painfully slow download of Lithium and we should be jammin. Can't believe how easy it all was actually.
So I assume since this CWM is loaded from an app there's no way to boot into recovery should a bootloop or rom failure happen? Is that something people worry about?
Thanks for your response bud.
seanpr123 said:
Boom, was one setup ahead of you and just finished all that. Currently backing up in CWM and waiting for a painfully slow download of Lithium and we should be jammin. Can't believe how easy it all was actually.
So I assume since this CWM is loaded from an app there's no way to boot into recovery should a bootloop or rom failure happen? Is that something people worry about?
Thanks for your response bud.
Click to expand...
Click to collapse
The cwm on boot feature may already be included in Lithium (edit: yes, it it included - just checked)... if not, you can set that up rather painlessly. And, yes, some of us do worry about that very much so..
Great thanks! worked perfectly for me on the ICS leak (non AT&T A2)
So I am on Atrix Xperia 4 rom and i was wondering if there is any way to re-root my phone to ICS and then flash the ics rom? I really havent seen anyone ask this yet but sorry if I am repeating anyones question.
matt_12tall said:
So I am on Atrix Xperia 4 rom and i was wondering if there is any way to re-root my phone to ICS and then flash the ics rom? I really havent seen anyone ask this yet but sorry if I am repeating anyones question.
Click to expand...
Click to collapse
Are you on the ICS leak already? Are you on AT&T? If you are on the ICS leak and on AT&T there is a way to root it in the leak thread in the General section. I put the files back up today.
If not, I really am not sure, one of the guys on the other leaks might be able to help there.
So we know that the ics ota is is coming soon. In on stock rooted 2.3.6. I know you don't have to uproot to do it, but I did (for some reason) install bootstrap and bootstrapped my recovery. Is there anything I need to do with that before the ota or is that good to leave as well since it's not actually flashed? If so could you tell me or link me to a guide? (Sorry if this has been asked couldn't find anything on it)
okachowwa said:
So we know that the ics ota is is coming soon. In on stock rooted 2.3.6. I know you don't have to uproot to do it, but I did (for some reason) install bootstrap and bootstrapped my recovery. Is there anything I need to do with that before the ota or is that good to leave as well since it's not actually flashed? If so could you tell me or link me to a guide? (Sorry if this has been asked couldn't find anything on it)
Click to expand...
Click to collapse
Your best bet is to fxz to a full 100% stock load before any OTA. We already have root so losing root is only for during the update, I know it does not check for root, but it is safer to just be 100% stock off of the fxz.
If you are on the ICS leak, I have several people testing the fix I have made and I am hopeful to have it released to everyone in the next couple of days.
jimbridgman said:
Your best bet is to fxz to a full 100% stock load before any OTA. We already have root so losing root is only for during the update, I know it does not check for root, but it is safer to just be 100% stock off of the fxz.
If you are on the ICS leak, I have several people testing the fix I have made and I am hopeful to have it released to everyone in the next couple of days.
Click to expand...
Click to collapse
I'm not worried about root, but man last time I attempted an fxz I got extremely confused and ended up just exchanging my phone... Well shoot. I believe most phones can do OTA's with root, just not sure about that whole bootstrap and I still have all the stock (non-uninstallable) at&crap apps.
okachowwa said:
I'm not worried about root, but man last time I attempted an fxz I got extremely confused and ended up just exchanging my phone... Well shoot. I believe most phones can do OTA's with root, just not sure about that whole bootstrap and I still have all the stock (non-uninstallable) at&crap apps.
Click to expand...
Click to collapse
You HAVE to remove bootstrap, the log wrapper link in /system/bin and also remove the hijack file in /system/bin and move logwrapper.bin to logwrapper also in /system/bin. All of this can be done from root explorer. Then reboot. If not done correctly you will bootloop. The fxz is way easier and I have a scripted version that does not require rsdlite.
Sent from my SAMSUNG-SGH-I747 using xda premium
jimbridgman said:
You HAVE to remove bootstrap, the log wrapper link in /system/bin and also remove the hijack file in /system/bin and move logwrapper.bin to logwrapper also in /system/bin. All of this can be done from root explorer. Then reboot. If not done correctly you will bootloop. The fxz is way easier and I have a scripted version that does not require rsdlite.
Sent from my SAMSUNG-SGH-I747 using xda premium
Click to expand...
Click to collapse
Will the scripted version work from 2.3.6 ti 2.3.5? Also will I run into all those CG errors and whatnot with it? So so sorry for my annoyance and ignorance but I guess that will help me learn.
okachowwa said:
Will the scripted version work from 2.3.6 ti 2.3.5? Also will I run into all those CG errors and whatnot with it? So so sorry for my annoyance and ignorance but I guess that will help me learn.
Click to expand...
Click to collapse
You have no ignorance, no worries... questions are what this place is for and so you can learn.
Yes I have script for both 2.3.6 and another for ICS.
Not sure if you will have the cg error or not. Usually you get that from flashing the incorrect fxz. If you tell me which version of the phone you have and your correct location, I might be able to put a "special" one together for.
Or if you bought an att phone but live in India then you might have to flash the att fxz and then give cogeary's international rom a try.
Sent from my SAMSUNG-SGH-I747 using xda premium
jimbridgman said:
You have no ignorance, no worries... questions are what this place is for and so you can learn.
Yes I have script for both 2.3.6 and another for ICS.
Not sure if you will have the cg error or not. Usually you get that from flashing the incorrect fxz. If you tell me which version of the phone you have and your correct location, I might be able to put a "special" one together for.
Or if you bought an att phone but live in India then you might have to flash the att fxz and then give cogeary's international rom a try.
Sent from my SAMSUNG-SGH-I747 using xda premium
Click to expand...
Click to collapse
You're definitely a great guy for doing this stuff. I have the AT&T USA a2 running the stock 2.3.6 rom.
jimbridgman said:
You have no ignorance, no worries... questions are what this place is for and so you can learn.
Yes I have script for both 2.3.6 and another for ICS.
Not sure if you will have the cg error or not. Usually you get that from flashing the incorrect fxz. If you tell me which version of the phone you have and your correct location, I might be able to put a "special" one together for.
Or if you bought an att phone but live in India then you might have to flash the att fxz and then give cogeary's international rom a try.
Sent from my SAMSUNG-SGH-I747 using xda premium
Click to expand...
Click to collapse
Are you using that one-click script from the dev section because that one says for 2.3.5
okachowwa said:
Are you using that one-click script from the dev section because that one says for 2.3.5
Click to expand...
Click to collapse
Are you looking for a root or fxz script?
jimbridgman said:
Are you looking for a root or fxz script?
Click to expand...
Click to collapse
The FXZ to go from 2.3.6 to 2.3.5 so I can get rid of bootstrap.
please help! I do NOT care about my root, I do NOT care about my data I just really want this to be fixed, I'm almost crying, I have no idea what to do, all i wanted was a custom battery so i downloaded one, loaded it into some app called metamorph and it said it was all good but when i restarted my phone the notification bar was gone. I cannot pull it down and this is my first android device, I have had it for 3 days and it cost me a lot of money! please help I will do anything whatsoever, I'm so worried, I'm only 16. I tried restoring my phone to factory settings, wiping my memory card as if that would do anything. please help it's all I ask!
Hi there, I have had this problem before. I am no dev so I can't explain the technical issue, but this usually happens when you flash a mod that's not compatible with your ROM... if its compatible and your ROM has updated, the mod sometimes needs to be updated to be compatible with the latest version of your ROM.
Reflashing your ROM will completely fix the issue. I hate to say it, but ALWAYS do backups before flashing anything through recovery!!!
Sent from my One X using xda premium
Sorry
franki_667 said:
Hi there, I have had this problem before. I am no dev so I can't explain the technical issue, but this usually happens when you flash a mod that's not compatible with your ROM... if its compatible and your ROM has updated, the mod sometimes needs to be updated to be compatible with the latest version of your ROM.
Reflashing your ROM will completely fix the issue. I hate to say it, but ALWAYS do backups before flashing anything through recovery!!!
Sent from my One X using xda premium
Click to expand...
Click to collapse
Sorry I'm such a noob, I have no idea what I am doing, I don't know what flashing is or anything could you please tell me how to flash a ROM? please??? I will love you forever man I have no idea what to do, im so desperate right now
franki_667 said:
Hi there, I have had this problem before. I am no dev so I can't explain the technical issue, but this usually happens when you flash a mod that's not compatible with your ROM... if its compatible and your ROM has updated, the mod sometimes needs to be updated to be compatible with the latest version of your ROM.
Reflashing your ROM will completely fix the issue. I hate to say it, but ALWAYS do backups before flashing anything through recovery!!!
Sent from my One X using xda premium
Click to expand...
Click to collapse
He's not rooted it seems. You first need to calm down. Then, go to settings -> About phone and see what build you have. If it's 2.20 then go here. If it's 1.73 or 1.82 go here. If it's 1.85 then go here. Once rooted, if you have anything but 2.20 you won't need to flash the boot.img seperately. In order to flash the boot.img go here.
Mister J said:
He's not rooted it seems. You first need to calm down. Then, go to settings -> About phone and see what build you have. If it's 2.20 then go here. If it's 1.73 or 1.82 go here. If it's 1.85 then go here. Once rooted, if you have anything but 2.20 you won't need to flash the boot.img seperately. In order to flash the boot.img go here.
Click to expand...
Click to collapse
i am rooted on software 1.85 please help me get this stupid notification bar back, it happened when I used Metamorph to change my battery
Is there possibly a way to revert to the original through "metamorph"? Most tweaks or apps like this only work on certain devices, so check the reviews or description more thoroughly if it doesn't say your device.
Sent from my HTC One X using Tapatalk 2
sorry
tyessen said:
Is there possibly a way to revert to the original through "metamorph"? Most tweaks or apps like this only work on certain devices, so check the reviews or description more thoroughly if it doesn't say your device.
Sent from my HTC One X using Tapatalk 2
Click to expand...
Click to collapse
no there is no way to revert in metamorph and i already wiped my device and the notification bar is still not there, I have no idea what to do.
HtcOneXProblem said:
no there is no way to revert in metamorph and i already wiped my device and the notification bar is still not there, I have no idea what to do.
Click to expand...
Click to collapse
That happened to me on my old LG G2X. I tried to do something similar with a different program. It was messing with SystemUI.apk. I had created a backup before it did its work so I just replaced it, rebooted and it was fine. Might not be the same problem just because the symptoms are similar. If you had an unmodified SystemUI.apk file you could probably just overwrite it. Worst case, just flash a new ROM.
But yeah, in the future always take backups before you do anything like that. I learned that the hard way a few times.
HtcOneXProblem said:
i am rooted on software 1.85 please help me get this stupid notification bar back, it happened when I used Metamorph to change my battery
Click to expand...
Click to collapse
In that case just back everything up and reinstall the rom.
Thanks
Mister J said:
In that case just back everything up and reinstall the rom.
Click to expand...
Click to collapse
thanks for everyone's help, i figured out that I did not have bootloader installed so I got that (it was a ***** because I had to fake the CID which took forever) and I installed a new ROM, thanks for the help guys, really means a lot to me