Phone: Motorola Atrix 2
Gingerbread 2.3.5 running 1-Click Rooted, Supercharged V4 ROM
Issue: Phone no longer has superuser permissions, cannot restore
Background: I recently decided to update via the OTA update to 2.3.6. My first issue was that the phone could not be updated due to the bloatware I removed (namely Social Location, AKA Richlocation.apk and RichLocation.odex).
My end goal was to run Supercharged V4 and 2.3.6 rooted, however I could not use RSD Lite because it will not recognize my phone (64 Bit windows, latest drivers, etc.)
So I tried finding RichLocation.odex to replace the one deleted (since titanium backup could not restore it), and found it for another phone. The upgrade still kept hanging up on that file (saying unexpected results this time).
I downloaded ATrix 2 Bootstrapper and loaded the Supercharged V4. I noticed it reinstalled Social Location, so I decided to give it another try. This time I found that all the other system/apps didn't work. So my plan was to pull the original versions from the backup I had run prior to going Supercharged and put them in the system/apps directory.
It was here that I noticed I no longer had write capability through RootExplorer. I then opened SetCPU and a few other Rooted Apps to find that I no longer had root permissions.
I tried doing a restore in RomManager, but it just hangs up. Atrix 2 Bootstrapper cannot go to Reboot Recovery.
I also tried a factory reset/wipe. No luck (although it did reinstall Social Location and the appropriate Odex file)
So without being able to use RSD Lite, and access through ROM Manager or Bootstrapper, how do I fix this? It seems Supercharged V4 has completely killed my permissions, so I can't re-root the phone or write to any of the system directories.
Help!
Thanks in Advance.
Mover
Moverf16 said:
I recently decided to update via the OTA update to 2.3.6. My first issue was that the phone could not be updated due to the bloatware I removed (namely Social Location, AKA Richlocation.apk and RichLocation.odex).
Click to expand...
Click to collapse
A little research would have saved you a lot of headache by reading this first http://forum.xda-developers.com/showthread.php?t=1396650
Moverf16 said:
My end goal was to run Supercharged V4 and 2.3.6 rooted, however I could not use RSD Lite because it will not recognize my phone (64 Bit windows, latest drivers, etc.)
Click to expand...
Click to collapse
Again by doing some reading you would have seen that this combo isn't available and unless I'm mistaking this is the only ROM running 2.3.6 currently
http://forum.xda-developers.com/showthread.php?t=1420980
Now to your problem with RSD, do you have adb installed or SDK, is your phone in fastboot mode, what OS are you running on your computer, etc. Not trying to come across as rude but generally all your problems been covered and searching will usually reveal them to you. Everything you need is in the beginners thread along with a detailed write up of what you need and how to flash the fastboot files using RSD.
JRW 28 said:
A little research would have saved you a lot of headache by reading this first http://forum.xda-developers.com/showthread.php?t=1396650
Click to expand...
Click to collapse
Copy, but that doesn't help me now. When I rooted my phone, I knew nothing about this site or the above. I only rooted for the sole reason of getting rid of social location.
Again by doing some reading you would have seen that this combo isn't available and unless I'm mistaking this is the only ROM running 2.3.6 currently
http://forum.xda-developers.com/showthread.php?t=1420980
Click to expand...
Click to collapse
My understanding from the reading I have done is that if you're rooted and then upgrade to 2.3.6, you will still be rooted, correct? And that pre-rooting at 2.3.5 is the only way to root 2.3.6?
Also, I thought I had seen a few people post that once they were past 2.3.6, they went to supercharged v4.
Regardless, that is not my current issue. My current issue is that Supercharged V4 has locked me out of my superuser permissions. I cannot use this function anymore, and I'm looking for help to restore back to my previous settings.
Now to your problem with RSD, do you have adb installed or SDK, is your phone in fastboot mode, what OS are you running on your computer, etc. Not trying to come across as rude but generally all your problems been covered and searching will usually reveal them to you. Everything you need is in the beginners thread along with a detailed write up of what you need and how to flash the fastboot files using RSD.
Click to expand...
Click to collapse
Phone is in fastboot mode. I have adb installed.
Windows 7 64-Bit
Believe me, I have searched. None of the proposed solutions have resolved my problem, and I'm currently looking for a way to do this without RSD.
Thanks.
Moverf16 said:
Copy, but that doesn't help me now. When I rooted my phone, I knew nothing about this site or the above. I only rooted for the sole reason of getting rid of social location.
My understanding from the reading I have done is that if you're rooted and then upgrade to 2.3.6, you will still be rooted, correct? And that pre-rooting at 2.3.5 is the only way to root 2.3.6?
Also, I thought I had seen a few people post that once they were past 2.3.6, they went to supercharged v4.
Regardless, that is not my current issue. My current issue is that Supercharged V4 has locked me out of my superuser permissions. I cannot use this function anymore, and I'm looking for help to restore back to my previous settings.
Phone is in fastboot mode. I have adb installed.
Windows 7 64-Bit
Believe me, I have searched. None of the proposed solutions have resolved my problem, and I'm currently looking for a way to do this without RSD.
Thanks.
Click to expand...
Click to collapse
Just download the motorola drivers from the beginners thread. I also have Windows 7 64 bit, and I have flashed the fkz's countless times. Just remember to pull the files required from 2.3.6 and edit the XML and you should be all set. And you CANNOT use Supercharged with 2.3.6 as it is based on 2.3.5, if you do flash it you will loose all the benefits on 2.3.6 because SC v4 flashes the entire /system/app therefore replacing all apps from 2.3.5.
OK. First off, why do you say RSD Lite is giving an error? What error message is it giving?
Secondly, you do NOT preserve root through an OTA. The su binary/Superuser.apk do not get deleted but their permissions are set to 0. Read the noob thread on how to preserve root through an OTA.
The only way you can fix the problem you're having is by flashing the fxz. Preferably do it through RSD Lite. It only takes 5 minutes.
Now... if you have to not use RSD Lite... you can use the fastboot command that comes in the Android sdk. In 30 mins I'll be home and will post a fastboot binary/what to do.
The latest version of Supercharged is based on 2.3.6, so once you get this worked out you can flash that instead of installing the OTA and not have to worry about losing root/failure due to removed bloatware. EDIT- 2.3.6 was having some problems with hardware buttons, among other things. It looks like 2.3.6 Supercharged has been removed, however there's still a deodexed 2.3.6.
Sent from my MB865 using Tapatalk
cogeary said:
OK. First off, why do you say RSD Lite? What error message is it giving?
Click to expand...
Click to collapse
RSD Lite 5.6 is the name of the program.
It gives no error message. When I click "Show Device" it does nothing, and when I select the file, it only gives me the option to uncompress, not flash.
Secondly, you do NOT preserve root through an OTA. The su binary/Superuser.apk do not get deleted but their permissions are set to 0. Read the noob thread on how to preserve root through an OTA.
Click to expand...
Click to collapse
Will do. I thought I had understood in my readings that the process was 1 Click root 2.3.5, OTA, then restore the previous files. I'll reread.
The only way you can fix the problem you're having is by flashing the fxz. Preferably do it through RSS Lite. It only takes 5 minutes.
Click to expand...
Click to collapse
What is RSS Lite?
Now... if you have to not use RSD Lite... you can use the fastboot command that comes in the Android sdk. In 30 mins I'll be home and will post a fastboot binary/what to do.
Click to expand...
Click to collapse
Thank you! This will help huge.
The latest version of Supercharged is based on 2.3.6, so once you get this worked out you can flash that instead of installing the OTA and not have to worry about losing root/failure due to removed bloatware.
Sent from my MB865 using Tapatalk
Click to expand...
Click to collapse
Ok, now there's conflicting data in this very thread.
Moverf16 said:
RSD Lite 5.6 is the name of the program.
It gives no error message. When I click "Show Device" it does nothing, and when I select the file, it only gives me the option to uncompress, not flash.
Will do. I thought I had understood in my readings that the process was 1 Click root 2.3.5, OTA, then restore the previous files. I'll reread.
What is RSS Lite?
Thank you! This will help huge.
Ok, now there's conflicting data in this very thread.
Click to expand...
Click to collapse
@Cogeary/@moverf16 Supercharged v4 is based off of 2.3.5 I am 100% sure of that. Also I think he meant RSD Lite, he was typing on his phone so it was probably a typo.
farshad525hou said:
Just download the motorola drivers from the beginners thread. I also have Windows 7 64 bit, and I have flashed the fkz's countless times. Just remember to pull the files required from 2.3.6 and edit the XML and you should be all set. And you CANNOT use Supercharged with 2.3.6 as it is based on 2.3.5, if you do flash it you will loose all the benefits on 2.3.6 because SC v4 flashes the entire /system/app therefore replacing all apps from 2.3.5.
Click to expand...
Click to collapse
I've tried both the ones in the beginners thread, and the latest ones (that include Moto helper).. Neither seem to work.
I've now tried this on two laptops - Windows 7 and a Vista 32 Bit. Same results.
Moverf16 said:
I've tried both the ones in the beginners thread, and the latest ones (that include Moto helper).. Neither seem to work.
I've now tried this on two laptops - Windows 7 and a Vista 32 Bit. Same results.
Click to expand...
Click to collapse
That is very weird indeed. Is your phone recognized for usb mass storage? You might have a faulty USB cable maybe one that has problems with data transfer.
farshad525hou said:
That is very weird indeed. Is your phone recognized for usb mass storage? You might have a faulty USB cable maybe one that has problems with data transfer.
Click to expand...
Click to collapse
I've tried two of those as well.
If I could have just replaced the bloatware files when this all started, I'd be happily using my phone right now.
Just to confirm, though. Once I finally figure out RSD Lite or how to reflash my phone out of Supercharged V4, my steps will be:
-Flash the Edison stock 2.3.5 Motorola firmware from the Noob thread
- 1 click root the phone
- Change the lines of code per the OTA thread:
If you want to have your device rooted with 2.3.6 and you're currently on 2.3.5 (rooted), follow these instructions:
With a root explorer, navigate to /system/bin/ and edit the mount_ext3.sh file. If you used a 1-click root method, then add the following lines to the end of the file (if you manually rooted then you might want to omit the 1st/2nd line):
Click to expand...
Click to collapse
- OTA update (which I actually currently have sitting on my SD card, since I moved it from the cache to the SD card earlier in the process, my plan is to do a boot loader install update from SD device).
- Wait for supercharged V5.
Now, if I can just figure out how to restore my phone back to 2.3.5.
Is there anyway to get back the Super User Permissions that V4 has somehow taken from me?
Also, if anyone has the 2.3.5 system/apps/ files (the .odex's), that would be greatly appreciated, in case I am able to just return to my restore point (somehow regain control of my superuser status).
If your still on 2.3.5 I don't see why the one click way wouldn't work.
farshad525hou said:
If your still on 2.3.5 I don't see why the one click way wouldn't work.
Click to expand...
Click to collapse
Right now one click doesn't work because Supercharger V4 is locking out permissions. It says it's missing some of the directories and that some of the files it's trying to access are read only.
farshad525hou said:
If your still on 2.3.5 I don't see why the one click way wouldn't work.
Click to expand...
Click to collapse
He can't he did the 2.3.6 update.
Look You have to restore the FXZ, you need to figure out why windows does not see your phone. Have you gone into device manager after connecting the phone to see if it even shows there at all?
The ONLY way you are getting root back is to restore the fxz. I am telling you that many others have done exactly what you have, and it has been resolved, please search.
There is no way to get root back or use something other than RSD lite.... You can try using fastboot, to restore the fxz files individually, but considering that you are having the troubles that you are, I would not advise it. That is more complex, and easier to mess your phone up permanently.
OK First off sorry for the typos! Corrected my post.
First let's make 100% sure that you have the correct drivers. Download THESE DRIVERS. Install them. Boot up your phone normally and make sure that you can connect properly in USB Mass Storage, Windows Media Sync, etc.
Now let's check to see that your phone is connecting to your PC correctly. Boot into fastboot mode (Hold power + volume buttons, scroll down to "AP Fastboot," press volum up) and connect your phone to your computer. The bottom text on your phone should now change to: "Transfer Mode: USB Connected". If something else happens then you have a faulty connection.
Now let's make sure RSD Lite is detecting your phone properly. First uninstall/reinstall RSD (reboot in between). Then boot back into fastboot mode and connect the USB Cable, and make sure that it still says "Transfer Mode: USB Connected" at the bottom. Open RSD Lite and wait a couple seconds. It should look like this:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
If everything has worked so far then you're good to go. If not then post back.
P.S- Once this gets worked out you don't have to install the OTA. If you want to install SC v5 when it's released you don't need to be on the ota.
jimbridgman said:
He can't he did the 2.3.6 update.
Click to expand...
Click to collapse
No, I have not done the 2.3.6 update. I could not originally because of the missing RichLocation.odex
Look You have to restore the FXZ, you need to figure out why windows does not see your phone. Have you gone into device manager after connecting the phone to see if it even shows there at all?
Click to expand...
Click to collapse
Windows does see my phone. RSD Lite does not. PDA Net works fine. It installs fine each time I connect.
The ONLY way you are getting root back is to restore the fxz. I am telling you that many others have done exactly what you have, and it has been resolved, please search.
Click to expand...
Click to collapse
I have searched plenty. I haven't found anyone who has been locked out of their root by Supercharged V4 and been unable to flash via RSD Lite. BTW, the search function would be a lot more user friendly if it didn't have a convoluted captcha process each time.
There is no way to get root back or use something other than RSD lite.... You can try using fastboot, to restore the fxz files individually, but considering that you are having the troubles that you are, I would not advise it. That is more complex, and easier to mess your phone up permanently.
Click to expand...
Click to collapse
Again, the update did not happen. Supercharge V4 (2.3.5) took away my root permissions.
cogeary said:
OK First off sorry for the typos! Corrected my post.
First let's make 100% sure that you have the correct drivers. Download THESE DRIVERS. Install them. Boot up your phone normally and make sure that you can connect properly in USB Mass Storage, Windows Media Sync, etc.
Click to expand...
Click to collapse
Done. USB mass storage, windows media sync and portal all work as advertised.
Now let's check to see that your phone is connecting to your PC correctly. Boot into fastboot mode (Hold power + volume buttons, scroll down to "AP Fastboot," press volum up) and connect your phone to your computer. The bottom text on your phone should now change to: "Transfer Mode: USB Connected". If something else happens then you have a faulty connection.
Click to expand...
Click to collapse
USB Connected, Battery OK.
Now let's make sure RSD Lite is detecting your phone properly. First uninstall/reinstall RSD (reboot in between). Then boot back into fastboot mode and connect the USB Cable, and make sure that it still says "Transfer Mode: USB Connected" at the bottom. Open RSD Lite and wait a couple seconds. It should look like this:
If everything has worked so far then you're good to go. If not then post back.
P.S- Once this gets worked out you don't have to install the OTA. If you want to install SC v5 when it's released you don't need to be on the ota.
Click to expand...
Click to collapse
I reinstalled RSD Lite and it still shows nothing under device. I have also tried running as administrator and both Windows 7 and Windows XP SP 2 (from the Readfile included that says it was designed for SP2).
Moverf16 said:
Done. USB mass storage, windows media sync and portal all work as advertised.
USB Connected, Battery OK.
I reinstalled RSD Lite and it still shows nothing under device. I have also tried running as administrator and both Windows 7 and Windows XP SP 2 (from the Readfile included that says it was designed for SP2).
Click to expand...
Click to collapse
:S
OK...
as jim said RSD Lite is really the only way to go.. unless you're willing to try something relatively untested for the A2 that can have complications and is more complicated, and read on.
First let's see if the more complicated method will even work (if RSD Lite doesn't detect your phone then it may not...). Download THIS ZIP: View attachment fastboot.zip. Unzip it to your desktop.
Now open a command prompt (start -> search box -> "cmd" -> <enter>). Type in the following command:
Code:
cd C:\Users\[COLOR="Red"]username[/COLOR]\Desktop
change "username" for whatever your Windows username is.
Now boot your phone into fastboot mode and wait for it to say "USB Connected." Now type this command:
Code:
fastboot devices
this scans for devices connected in fastboot mode and lists them. If the list is empty then that means your computer just isn't going to work. If it lists something then post back.
EDIT oh by they way! Make sure that the port you connected your phone to has enough power. Try all the USB ports on your computer and wiggle the cable around a bit and see if RSD Lite detects your phone.
EDIT EDIT jim is correct. Are you sure you flashed the Stock Rooted Deodexed ROM before you flashed Supercharged?
Moverf16 said:
No, I have not done the 2.3.6 update. I could not originally because of the missing RichLocation.odex
Windows does see my phone. RSD Lite does not. PDA Net works fine. It installs fine each time I connect.
I have searched plenty. I haven't found anyone who has been locked out of their root by Supercharged V4 and been unable to flash via RSD Lite. BTW, the search function would be a lot more user friendly if it didn't have a convoluted captcha process each time.
Again, the update did not happen. Supercharge V4 (2.3.5) took away my root permissions.
Click to expand...
Click to collapse
Actually that was quite common for people that did not follow the directions properly, and it was not just V4, it was on ALL versions.
Wow, you really have not looked very well then, it took me less than a min. find it.... post 36 in the supercharged rom thread is where it is first seen.
http://forum.xda-developers.com/showthread.php?t=1441397
Post #36:
http://forum.xda-developers.com/showpost.php?p=21347598&postcount=36
Here is how to fix the issue with the superchared loosing root issue, it is post #42:
http://forum.xda-developers.com/showpost.php?p=21355316&postcount=42
As for your issues with RSD.
1) uninstall RSD
2) reboot
3) uninstall the moto drivers.
4) reboot
5) go redownload RSD:
http://forum.xda-developers.com/attachment.php?attachmentid=784077&d=1321414457
6) go redownload the drivers:
http://www.motorola.com/consumers/v...59431210VgnVCM1000008406b00aRCRD&pubid=987654
7) reinstall the drivers, connect your phone, and make sure it sees it.
8) reinstall RSD
9) REBOOT!!!!! this is important.
10) try to flash the FXZ file with RSD
jimbridgman said:
Actually that was quite common for people that did not follow the directions properly, and it was not just V4, it was on ALL versions.
Wow, you really have not looked very well then, it took me less than a min. find it.... post 36 in the supercharged rom thread is where it is first seen.
http://forum.xda-developers.com/showthread.php?t=1441397
Post #36:
http://forum.xda-developers.com/showpost.php?p=21347598&postcount=36
Here is how to fix the issue with the superchared loosing root issue, it is post #42:
http://forum.xda-developers.com/showpost.php?p=21355316&postcount=42
Click to expand...
Click to collapse
Thanks, however, I posted this because I was looking for a way to get back root permissions without having to use RSD.. Since RSD does not currently work for me.
I understand your insistence on the search function, but I sincerely could not find it.
I've done some more looking at the android SDK stuff. Could I shell into it and change the directory permissions from read only to read/write, then reroot using 1-click and regain superuser permissions? The issue seems to be the SC4 made all of the system files read only again.
As for your issues with RSD.
1) uninstall RSD
2) uninstall the moto drivers.
3) go redownload RSD:
http://forum.xda-developers.com/attachment.php?attachmentid=784077&d=1321414457
4) go redownload the drivers:
http://www.motorola.com/consumers/v...59431210VgnVCM1000008406b00aRCRD&pubid=987654
5) reinstall the drivers, connect your phone, and make sure it sees it.
6) reinstall RSD
7) REBOOT!!!!! this is important.
8) try to flash the FXZ file with RSD
Click to expand...
Click to collapse
[/quote]
I did this above.
Related
Seeing as there isn't a section for the LG P870/LG Escape I'm going to try and get as much info condensed into one thread for now.
Not even sure how popular this phone is but, hopefully this will be of some use to someone.
KDZ:
I know this isn't posted anywhere so here is the v10f KDZ from LG. It is the latest firmware as of 11/6/2012:
http://csmg.lgmobile.com:9002/swdata/WEBSW/LGP870/AATTBK/P87010f_00/P87010f_00.kdz
If you don't know how to flash a KDZ I will make a guide here soon. V10f is rootable using the method below as is v10c
Download Mode:
To get into download mode turn off your phone, press and hold the vol+ and vol- keys, with those held down insert the USB cable while continuing to hold down the keys. After a few seconds phone will enter download mode automatically.
Rooting:
I was able to root my phone that has v10c on it using this tool:
http://forum.xda-developers.com/showpost.php?p=31963526&postcount=532
I used 1.6 of the root script but some say that 1.2 works better for them. I would try 1.6 if that doesn't work try 1.2 if it fails the first time run it a second time and it should work.
Thanks! My wife just got this. I was able to root and update and retain root with OTA rootkeeper. Was looking for a kdz just in case. If there's enough interest i will see if i can port TWRP so we can cook up some custom roms.
I am definitely interested in custom roms, I have this device. Its not bad considering the price and what you get. 1494 on geekbench too! Pretty decent!
---------- Post added at 07:49 PM ---------- Previous post was at 07:44 PM ----------
Thanks for the effort
Aye guys I'm new into rooting and android in general, but I don't really understand how to root this phone. Kinda been looking around for a while and I was wondering if you can write some sort of guide. As of now I'm pretty lost the other threads aren't giving me any general information on exactly how to root the LG P870 or androids in general.
-Thanks
Btw I understand what exactly what rooting does to your device and the purpose of rooting, its just exactly how to root the device.
Well first things first do you have the android SDK installed on your computer
cyclejim said:
Well first things first do you have the android SDK installed on your computer
Click to expand...
Click to collapse
Alright now what lol.
As of now I have Eclipse with android sdk installed on it and the newest version of java. Whats next, and spefically whats a KDZ and what is he talking about here:
Urabewe said:
Rooting:
I was able to root my phone that has v10c on it using this tool:
http://forum.xda-developers.com/showpost.php?p=31963526&postcount=532
I used 1.6 of the root script but some say that 1.2 works better for them. I would try 1.6 if that doesn't work try 1.2 if it fails the first time run it a second time and it should work.
Click to expand...
Click to collapse
He
GHazard said:
Alright now what lol.
As of now I have Eclipse with android sdk installed on it and the newest version of java. Whats next, and spefically whats a KDZ and what is he talking about here:
Click to expand...
Click to collapse
Download the zip and unzip it to your desktop. Go into your phone's settings and go to developers options. Turn on USB debugging. Go back to settings and go to security. Turn on unknown sources. Now plug your phone in and run the .bat file that you just unzipped. Follow the commands on the and that should be it. Good luck!
Thanks for the effort
GHazard said:
Alright now what lol.
As of now I have Eclipse with android sdk installed on it and the newest version of java. Whats next, and spefically whats a KDZ and what is he talking about here:
Click to expand...
Click to collapse
KDZ is the LG format for ROMs which is the built in read only memory that hold the instructions for the phone to run the hardware and features.
But I just rooted my phone with a combination of the above files, and it didnt go exactly as I hoped. First I ran the v1.2 batch file linked above, (the 1.6 batch file archive is invalid and doesnt extract properly. It seemed like it ran properly, i did the restore (no data destructive you shouldnt lost any data) but I didnt have root when completed. Then I tried the v17 of the original thread which can be found here http://forum.xda-developers.com/showthread.php?t=1886460
That one also ran but failed at the end saying something about me not having root on the phone.
I than ran the v1.2 batch file not once, but twice in a row. The second time I found my phone operating in "emulator mode" in other words, it was running laggy as hell and very slow. I then ran the V17 batch file from the link above, and boom it worked. So as you can see it wasnt typical, but I think if you dont have success with the 1.2 the first time, run it again, if it still didnt work, try running v17 like i did. I now have root and my phone is working fine.
Basically, I got the Escape then got the Nexus7 and have been involved in that. Really haven't been doing much with the Escape. I will be looking into more for everyone and hopefully get a custom recovery at the very least. Then at that point we can start thinking about rom. Until then we are stuck with what we have. I will get more info for everyone , till then this is what we have. If you think you can help go for it. If not sorry but this is the best info there is for our phone . I will positively without a doubt post any new info here so if that's what you are looking for this is the right place until then, thank you and you are welcome.
Sent from my Nexus 7 using xda premium
Markyzz said:
He
Download the zip and unzip it to your desktop. Go into your phone's settings and go to developers options. Turn on USB debugging. Go back to settings and go to security. Turn on unknown sources. Now plug your phone in and run the .bat file that you just unzipped. Follow the commands on the and that should be it. Good luck!
Click to expand...
Click to collapse
So when I run the .bat file do I just run it in cmd? I'm kinda knew at this lol.
Also does my phone have to be in download mode?
Sorry for the inconvenience but where exactly do I run the .bat file?
-Thanks
One more thing I never downloaded a .zip or .rar file.. Could you please leave me a link?
Rooted
Thanks people I guess I just needed time to figure it out lol. I ran it in cmd twice(1.2v) but not right after each other and the second time it worked thanks guys.
Well. I tried to install beats audio but now it won't even load up just boot loops when it gets to at&t...
Bricked
Great the first bricked lg p870 lol, anyone know how to fix this. Or is it just a brick?
Sorry for the repititive posts, but so far I have gotten my device to read by my computer. The only thing is I can see it in the Device manager but it never shows up in my computer. It also picks the phone up in cmd, is there sometype of command I can run to flash the device and put it back to normal?
GHazard said:
Sorry for the repititive posts, but so far I have gotten my device to read by my computer. The only thing is I can see it in the Device manager but it never shows up in my computer. It also picks the phone up in cmd, is there sometype of command I can run to flash the device and put it back to normal?
Click to expand...
Click to collapse
No command. You need to flash the kdz using lg flash tool.
Sent from my MB886 using xda premium
Markyzz said:
No command. You need to flash the kdz using lg flash tool.
Sent from my MB886 using xda premium
Click to expand...
Click to collapse
Is their a guide on how to flash the device using the kdz flash tool? I mean my phone won't turn on though. It goes into the lg logo then just goes black (the back light is still on).
K I have all the tools but
I downloaded every tool from this thread
But in the PDF guides it says to put the phone in Upgrade mode by removing the SIM, battery and SDC(Micro sd card?) so I did that. Then insert the usb while holding the Volume Up button. All that happens on my phone is the home keys on the bottom just flash. And my phone doesn't connect to my computer either.
My Notes on LG P870
Ok I have fixed my device, well twice now. It seems whenever you try to change any file within the root it restarts, then boot loops. I tried too change a font using Rom Toolbox, it restarted then boot looped. I rooted the device using the 1.2v script once, but this time I'll try 1.7v and see if I can change fonts etc.
Are any of you guys having any problem with this?
If you do, and you are soft bricked just:
Download UPK 3.7.1
Then open up LG /mobile Update
Click Install Drivers(Make sure your phone is not connected) Choose your phone and carrier
Let that finish(Gonna take awhile you have to install all of them)
Then click Install updates...Done
Worked
Posting confirmation for an LG Escape (p870). 10f rooted using the tools linked in first post. Used version 1.2 to start and had to use the version 17 of the other rooting kit to finalize like another user encountered as well. Thanks will be given if they haven't been yet.
Hi,
I was trying to root and install a custom rom on a friends phone. She has T-Mobile Galaxy S 4G. I was rushing through the whole project cause I had work and accidentally installed T-Mobile Vibrant Stock 2.1 using Heimdall. It was my fault. I did a google search for SGH-T959, but failed to realize that SGH-t959U is Vibrant and SGH-T959V is Samsung Galaxy S 4G...
After flashing the wrong ROM, I could not get it back into Download mode. I removed the SIM, SD card, Battery, and then tried putting it back into download mode (without the SIM or SD card) and that worked. I was able to get it into download mode at that point, but it would still not turn on or boot into recovery.
After realizing it was the wrong Flash, I searched online and found this http://forum.xda-developers.com/showthread.php?t=1358498 , after searching for users who bricked their phone previously and this was listed as a solution... the phone doesn't boot now however. It loads into Samsung Recovery (3e) and gives the error:
--Applying Multi-CSC...
Installing Multi-CSC
Can't access to '/system/csc/TMB/system/'
Successfully applied multi-CSC
Each time i try to 'reboot system now' it just loops back to recovery with the same error. On that link i listed above, it says to install bootloaders if that CSC issue exists. Problem is, each time i try, it says PIT failed and then it just disconnects and wont reboot, requiring me to reflash the package all-together.
This phone was originally on 2.3.6 and the problem is I tried rooting using Vibrant instructions which was to go back to 2.1, then flash root, then CWM, then custom ROM.
How do i get this phone working again. I can pick up where i left off as far as rooting and installing a custom ROM. I have experience with it... But I have no idea how to get this phone out of this soft-brick. Can anyone please assist me. I feel terrible for messing up my friends phone.
Thanks a bunch!
TL;DR - Soft bricked SGS4G by flashing Vibrant ROM, tried to correct using SuperOneClick heimdall, doesnt work. please help. Originally was completely stock.
Read the second link in my signature and see if it helps you with Heimdal.
lumin30 said:
Read the second link in my signature and see if it helps you with Heimdal.
Click to expand...
Click to collapse
Yeah, I've read that when I was searching for a fix on my lunch break. My laptop is a MAC however. Which is why I didn't ODIN. I lost my Windows partition a while ago, along with my Windows CD.... Is there anyway I can get some MAC instructions?
JGonzo1299 said:
Yeah, I've read that when I was searching for a fix on my lunch break. My laptop is a MAC however. Which is why I didn't ODIN. I lost my Windows partition a while ago, along with my Windows CD.... Is there anyway I can get some MAC instructions?
Click to expand...
Click to collapse
Get heimdall 1.3.1 for mac os x here. There is 1.3.2 and 1.4.0-rc1, but don't use them, just use 1.3.1 for now!
Read the install instructions here.
After that, you should be able to do the oneclick on your mac.
Just replying to the OP... Still follow the instructions in my previous post.
JGonzo1299 said:
the phone doesn't boot now however. It loads into Samsung Recovery (3e) and gives the error:
--Applying Multi-CSC...
Installing Multi-CSC
Can't access to '/system/csc/TMB/system/'
Successfully applied multi-CSC
Each time i try to 'reboot system now' it just loops back to recovery with the same error. On that link i listed above, it says to install bootloaders if that CSC issue exists. Problem is, each time i try, it says PIT failed and then it just disconnects and wont reboot, requiring me to reflash the package all-together.
Click to expand...
Click to collapse
The CSC error is just a red herring. Don't worry about that error. The one to worry about is not being able to flash the PIT!
JGonzo1299 said:
This phone was originally on 2.3.6 and the problem is I tried rooting using Vibrant instructions which was to go back to 2.1, then flash root, then CWM, then custom ROM.
Click to expand...
Click to collapse
Yea... Don't do that. Follow only instructions for the SGH-T959V, Galaxy S 4G. Do not ever, EVER, follow instructions for any other phone, unless you know exactly what you are doing.
JGonzo1299 said:
How do i get this phone working again. I can pick up where i left off as far as rooting and installing a custom ROM. I have experience with it... But I have no idea how to get this phone out of this soft-brick. Can anyone please assist me. I feel terrible for messing up my friends phone.
Thanks a bunch!
TL;DR - Soft bricked SGS4G by flashing Vibrant ROM, tried to correct using SuperOneClick heimdall, doesnt work. please help. Originally was completely stock.
Click to expand...
Click to collapse
Make sure you only follow instructions for the SGH-T959V, Galaxy S 4G! As I said above.
Either follow the instructions in my oneclick sticky thread, or follow lumin30's guide.
Make sure you try different usb cables. Make sure the ports on the computer and phone are clear of obstructions. Check in the cable connectors too. If all that still doesn't work, try a different computer. You could have bad usb ports. This has happened to me before, but it was a double whammy. I had bad usb ports on my computer and a bad usb cable.
bhundven said:
Get heimdall 1.3.1 for mac os x here. There is 1.3.2 and 1.4.0-rc1, but don't use them, just use 1.3.1 for now!
Read the install instructions here.
After that, you should be able to do the oneclick on your mac.
Click to expand...
Click to collapse
With that in mind, does anyone have a link to the most up to date Stock ROM not rooted. The Sticky Page has a dead link and the workaround link takes me to the OneClick ROM install that gave me the problem to begin with. I'd rather use the instructions to flash it myself and choose the file instead of doing the OneClick option. Does that make sense?
bhundven said:
Just replying to the OP... Still follow the instructions in my previous post.
The CSC error is just a red herring. Don't worry about that error. The one to worry about is not being able to flash the PIT!
Yea... Don't do that. Follow only instructions for the SGH-T959V, Galaxy S 4G. Do not ever, EVER, follow instructions for any other phone, unless you know exactly what you are doing.
Make sure you only follow instructions for the SGH-T959V, Galaxy S 4G! As I said above.
Either follow the instructions in my oneclick sticky thread, or follow lumin30's guide.
Make sure you try different usb cables. Make sure the ports on the computer and phone are clear of obstructions. Check in the cable connectors too. If all that still doesn't work, try a different computer. You could have bad usb ports. This has happened to me before, but it was a double whammy. I had bad usb ports on my computer and a bad usb cable.
Click to expand...
Click to collapse
Yeah i followed Vibrant instructions on accident. It was a careless mistake. Ill ignore the CSC error then and Ill try using a different USB port. My usb cable is brand new from my SIII. I don't think its a problem. But my mac USB ports are pretty old.
JGonzo1299 said:
With that in mind, does anyone have a link to the most up to date Stock ROM not rooted. The Sticky Page has a dead link and the workaround link takes me to the OneClick ROM install that gave me the problem to begin with. I'd rather use the instructions to flash it myself and choose the file instead of doing the OneClick option. Does that make sense?
Click to expand...
Click to collapse
Uhm, In the very first post of this thread, is this link. This is the totally back to stock oneclick.
I just downloaded it. Link works fine.
Yes, I realize you'd like to just run "heimdall" to flash everything, but it is so error prone.
The oneclick works for me on mac, linux, and windows. Again, if you have problems, list out each step you made and the results and we'll help
Just open a terminal, type:
Code:
java -jar T959VUVKJ6_STOCK-UVKJ6-One-Click.jar
and go...
bhundven said:
Uhm, In the very first post of this thread, is this link. This is the totally back to stock oneclick.
I just downloaded it. Link works fine.
Yes, I realize you'd like to just run "heimdall" to flash everything, but it is so error prone.
The oneclick works for me on mac, linux, and windows. Again, if you have problems, list out each step you made and the results and we'll help
Just open a terminal, type:
Code:
java -jar T959VUVKJ6_STOCK-UVKJ6-One-Click.jar
and go...
Click to expand...
Click to collapse
OK. I followed this. It DIDNT work. Ill list the steps i did.:
1) Redownloaded the one click listed above to ensure its not a corrupted download and verified
2)Placed file in my user folder (MAC Terminal defaults to this folder which is why i chose it)
3) Checked my Java version using Software update on MAC. Java was already up to date.
4)Opened Terminal
5) typed ls to confirm i was in the correct directory.
6) typed 'java -jar T959VUVKJ6_STOCK-UVKJ6-One-Click.jar'
7) Terminal began doing its thing.
8) I already have the Samsung Drivers. I've had Samsung Facinate and i currently have SIII so thats all up to date. Once i verified, i skipped the samsung drivers step.
9)I skipped the x86 step cause i know MAC has its own version of it already installed. My MAC version is 10.6.8
10) Connected phone to USB port, put in download mode.
11) Waited til phone was recognized with OneClick AND my MAC,
12) Ready to Flash
13) Clicked Flash
14) Flash successful, phone automatically powers down, reboots
15) Phone automatically loads into Android Recovery (3e) and gives error CSC mumbo jumbo i quoted in my first post
16) I needed bootloaders since I accidentally put Vibrant ROM. (per instructions from http://forum.xda-developers.com/showpost.php?p=21953878&postcount=2 )
17) Removed Battery, Reconnected to MAC and placed in Download Mode
18) Clicked Flash Bootloaders, bypassed the warning, clicked Flash.
19) Uploading PIT, PIT upload failed!, Ending Session..., Rebooting Device...
20) Phone shuts off and never reboots, stays as a black screen, cant turn it on, load into recovery. I can ONLY load it into Download mode.
I followed these instructions as directed http://forum.xda-developers.com/showpost.php?p=21953878&postcount=2 . Tried different USB cables and also tried BOTH USB ports. Please help. Thanks in advance.
JGonzo1299 said:
OK. I followed this. It DIDNT work. Ill list the steps i did.:
1) Redownloaded the one click listed above to ensure its not a corrupted download and verified
2)Placed file in my user folder (MAC Terminal defaults to this folder which is why i chose it)
3) Checked my Java version using Software update on MAC. Java was already up to date.
4)Opened Terminal
5) typed ls to confirm i was in the correct directory.
6) typed 'java -jar T959VUVKJ6_STOCK-UVKJ6-One-Click.jar'
7) Terminal began doing its thing.
8) I already have the Samsung Drivers. I've had Samsung Facinate and i currently have SIII so thats all up to date. Once i verified, i skipped the samsung drivers step.
9)I skipped the x86 step cause i know MAC has its own version of it already installed. My MAC version is 10.6.8
10) Connected phone to USB port, put in download mode.
11) Waited til phone was recognized with OneClick AND my MAC,
12) Ready to Flash
13) Clicked Flash
14) Flash successful, phone automatically powers down, reboots
15) Phone automatically loads into Android Recovery (3e) and gives error CSC mumbo jumbo i quoted in my first post
16) I needed bootloaders since I accidentally put Vibrant ROM. (per instructions from http://forum.xda-developers.com/showpost.php?p=21953878&postcount=2 )
17) Removed Battery, Reconnected to MAC and placed in Download Mode
18) Clicked Flash Bootloaders, bypassed the warning, clicked Flash.
19) Uploading PIT, PIT upload failed!, Ending Session..., Rebooting Device...
20) Phone shuts off and never reboots, stays as a black screen, cant turn it on, load into recovery. I can ONLY load it into Download mode.
I followed these instructions as directed http://forum.xda-developers.com/showpost.php?p=21953878&postcount=2 . Tried different USB cables and also tried BOTH USB ports. Please help. Thanks in advance.
Click to expand...
Click to collapse
Just double checking, This is t959v, not t959w... right? T959W has some issues with heimdall and odin that are still being worked out.
When i originally encountered the problem. I downloaded the 'back to Factory stock rom' for vibrant. It was an ODIN file so it was .tar, I downloaded its associated PIT file.
I loaded the PIT file into heimdall under the 'flash' tab
i extracted the .tar file and found 6 files. i took each file and loaded them individually to heimdall 1.3.1 under the 'flash' tab.
I had 6 files in there: cache, dbdata, factoryfs, modem, param, zImage.
Once I flashed those it wouldnt boot and was just black. could only go into download mode.
Then I realized i messed up and used the wrong ROM.
Came into this thread for SGS4G
Found the right files.
Phones been broken since and ive been following the instructions listed above. hope that makes sense. im at my work desk. sorry. Ill try to find the link of the go back to factory stock file i found on the vibrant forums but it was whatever vibrant came with out of the box. and it was a verified stock ROM. I just followed the instructions to the T until I encountered problems.....
bhundven said:
Just double checking, This is t959v, not t959w... right? T959W has some issues with heimdall and odin that are still being worked out.
Click to expand...
Click to collapse
Yes. I popped the battery out and im looking at the label in the back of the phone and it says SGH-959V.
JGonzo1299 said:
Yes. I popped the battery out and im looking at the label in the back of the phone and it says SGH-959V.
Click to expand...
Click to collapse
Ok, so it sounds like you need to try a different computer.
I know this is a pita, and I'm not trying to make things more difficult then they are, but as I said before. I've had this issue and had to buy a new computer. :crying:
Just thinking aloud, could try the kc1/kd1(froyo) firmware? Then move to gingerbread.
bhundven said:
Ok, so it sounds like you need to try a different computer.
I know this is a pita, and I'm not trying to make things more difficult then they are, but as I said before. I've had this issue and had to buy a new computer. :crying:
Click to expand...
Click to collapse
I'm going to try my friends PC. I'll try ODIN if I can find ODIN files, if not ill try heimdall instructions on a PC.
champ1919 said:
Just thinking aloud, could try the kc1/kd1(froyo) firmware? Then move to gingerbread.
Click to expand...
Click to collapse
Where do I find these? Can you post the link? I can probably try to flash this while im still at work for the next 2 hours lol
JGonzo1299 said:
I'm going to try my friends PC. I'll try ODIN if I can find ODIN files, if not ill try heimdall instructions on a PC.
Where do I find these? Can you post the link? I can probably try to flash this while im still at work for the next 2 hours lol
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?p=27374477
I think it's still a good link in that thread... I'm on my phone, I did try and something started.
JGonzo1299 said:
I had 6 files in there: cache, dbdata, factoryfs, modem, param, zImage.
Click to expand...
Click to collapse
So out of curiosity I just unpacked this Ravers KJ6 for Odin which was harder to find than I thought because Raver likes to spell offical instead of official. But I digress. The kicker here is that there are only 5 files.
cache.rfs
factoryfs.rfs
modem.bin
Sbl.bin
zImage
If I where the OP I'd DL that then unpack it. Reverse engineer what you did the first time by using the proper .tar through heimdall. If it worked once to totally hose you it just might work again to save you. Or it might not. Either way it's worth a shot. Good luck man.
hechoen said:
So out of curiosity I just unpacked this Ravers KJ6 for Odin which was harder to find than I thought because Raver likes to spell offical instead of official. But I digress. The kicker here is that there are only 5 files.
cache.rfs
factoryfs.rfs
modem.bin
Sbl.bin
zImage
If I where the OP I'd DL that then unpack it. Reverse engineer what you did the first time by using the proper .tar through heimdall. If it worked once to totally hose you it just might work again to save you. Or it might not. Either way it's worth a shot. Good luck man.
Click to expand...
Click to collapse
So you mean Download this and do exactly what I did that bricked the phone in the first place. but use these files instead. Cause these are for SGS4G. Correct?
I'll try that now. But dbdata is missing. Is that an issue? What is dbdata for anyway?
champ1919 said:
http://forum.xda-developers.com/showthread.php?p=27374477
I think it's still a good link in that thread... I'm on my phone, I did try and something started.
Click to expand...
Click to collapse
Thank you. I'm going to try this after I try what i just posted above first. Will post results later tonight around 11 EST. Work computer wont let me download any links.
JGonzo1299 said:
So you mean Download this and do exactly what I did that bricked the phone in the first place. but use these files instead. Cause these are for SGS4G. Correct?
I'll try that now. But dbdata is missing. Is that an issue? What is dbdata for anyway?
Click to expand...
Click to collapse
Yes that is what I mean.
I don't own a vibrant so I have know idea what dbdata is for. Maybe someone will chime in with a better answer. Doing it this way you should be able to get the phone back to where it was. Again this is my best guess at how to try to fix it. Plus it's really hard to brick a brick(bad joke I know but i had too).
I semi-bricked my Optimus One earlier today, but fixed it via KDZ and the India rom fix..
Re-rooted..
and used Root Uninstaller to remove the Bollywood bloatware like I did before..
only this time, all the apps I uninstalled, are still showing in my installed list, but with the "SD card" icon..
they're NOT on the card, I made sure of that..
but idk where to find them in the filesystem..
they're taking up space that I don't really have, y'know.
how would I go about remedying this?
(I'll post a screenshot later, when the site will let me.)
Deathpunkin said:
I semi-bricked my Optimus One earlier today, but fixed it via KDZ and the India rom fix..
Re-rooted..
and used Root Uninstaller to remove the Bollywood bloatware like I did before..
only this time, all the apps I uninstalled, are still showing in my installed list, but with the "SD card" icon..
they're NOT on the card, I made sure of that..
but idk where to find them in the filesystem..
they're taking up space that I don't really have, y'know.
how would I go about remedying this?
(I'll post a screenshot later, when the site will let me.)
Click to expand...
Click to collapse
It's possible that your root didn't take or the system partition didn't get remounted RW. System Apps reside in /system/app . User apps reside in /data/app .
The root did take, I confirmed that.
and the files are not in those locations..
heres the screenshot of what one looks like in app list..
Deathpunkin said:
The root did take, I confirmed that.
and the files are not in those locations..
heres the screenshot of what one looks like in app list..
Click to expand...
Click to collapse
I'm at a loss then. I've never experienced the issue you are facing. You rebooted after removing those apps? Are you using some kind of *2SD script?
Yup, I rebooted.
no, I'm not using any scripts or anything..
The only thing I have my phone doing that it "shouldn't" is the root.
am I going to have to re-flash it, and try to remove them again?
Also, the apps in question are not in the list when I go through Root Uninstaller again.
I'm guessing there's something better than RU, but I just don't know what it is yet xD
Deathpunkin said:
Yup, I rebooted.
no, I'm not using any scripts or anything..
The only thing I have my phone doing that it "shouldn't" is the root.
am I going to have to re-flash it, and try to remove them again?
Click to expand...
Click to collapse
Possibly as a last resort. Do you have a custom recovery installed? If so, try wiping cache and Dalvik cache and then reboot. The reboot will take a few minutes as Android will need to rebuild the caches.
shinobisoft said:
Possibly as a last resort. Do you have a custom recovery installed? If so, try wiping cache and Dalvik cache and then reboot. The reboot will take a few minutes as Android will need to rebuild the caches.
Click to expand...
Click to collapse
Trying to put CWM recovery on is what got me in this mess..
I'm not going to try to do any modding outside of Root untill I get a new phone..
this is the second time I've tried.
Deathpunkin said:
Trying to put CWM recovery on is what got me in this mess..
I'm not going to try to do any modding outside of Root untill I get a new phone..
this is the second time I've tried.
Click to expand...
Click to collapse
I can understand that. Did you use ROM Manager to try and install recovery? I've written a tool for Windows that can flash recoveries via fastboot and fastboot mode. If you're interested, it's called Android Flash Recovery and a link to it's thread can be found in my signature.
shinobisoft said:
I can understand that. Did you use ROM Manager to try and install recovery? I've written a tool for Windows that can flash recoveries via fastboot and fastboot mode. If you're interested, it's called Android Flash Recovery and a link to it's thread can be found in my signature.
Click to expand...
Click to collapse
Yea, I tried to use ROM Manager...
I have no clue what/how to get to 'fastboot' mode..
and I don't know what BB I'm using.
I've tried to find out but nothing showing in my About Phone helps.
Deathpunkin said:
Yea, I tried to use ROM Manager...
I have no clue what/how to get to 'fastboot' mode..
and I don't know what BB I'm using.
I've tried to find out but nothing showing in my About Phone helps.
Click to expand...
Click to collapse
What version of Android is on your device? 2.2 is Froyo which is old baseband. 2.3 is GingerBread which is new baseband.
Download my tool. Make sure USB Debugging is enabled on the device. Complete instructions are in the download archive. It's up to you tho.
I have used Root Uninstaller for 11/2 years on my Optimus V. The Uninstaller doesn't work that well.
I just use it because it auto saves all downloaded apk's, every version. I have to manually delete any saved versions.
Great when an update to an app is borked, or too slow of a data connection to re-install Titanium Backup after a ROM flash (I go to folder on SD card and move TB apk to root of SD card, then install).
Try using Link2SD
It has worked flawlessly to delete any unwanted pre-installed apps from ROM developers and Google Apps.
Sent from my LG-VM670 using xda premium
shinobisoft said:
What version of Android is on your device? 2.2 is Froyo which is old baseband. 2.3 is GingerBread which is new baseband.
Download my tool. Make sure USB Debugging is enabled on the device. Complete instructions are in the download archive. It's up to you tho.
Click to expand...
Click to collapse
Android 2.3.3
is it 100% that it's new Baseband?
and, I might give it a try later today..
I'll update you when I get a chance.
Deathpunkin said:
Android 2.3.3
is it 100% that it's new Baseband?
and, I might give it a try later today..
I'll update you when I get a chance.
Click to expand...
Click to collapse
Yes. Positive. You can optionally use the method just mentioned by AndieOpie150, or ES File Explorer has and uninstall/backup feature too.
shinobisoft said:
Download my tool. Make sure USB Debugging is enabled on the device. Complete instructions are in the download archive. It's up to you tho.
Click to expand...
Click to collapse
Booted in 'fastboot mode' and it just sits at
"
Fastboot mode started
udc_start()
-- suspend --
"
not detected after fastboot by AFR
it detected before the boot, but "Flash Recovery" was greyed out.
still is greyed out.
Deathpunkin said:
Booted in 'fastboot mode' and it just sits at
"
Fastboot mode started
udc_start()
-- suspend --
"
not detected after fastboot by AFR
it detected before the boot, but "Flash Recovery" was greyed out.
still is greyed out.
Click to expand...
Click to collapse
fastboot is a little weird. Boot device into fastboot mode, but not connected to PC. Then connect to PC after getting into fastboot mode.
I think I've seen something like that before. I think it's when the APK is gone but the cache, dalvik etc for the app is still there.
If you haven't yet done anything hardcore to your phone. EG: Reflashing.
And can still boot into your ROM then you might wanna give Clean Master a go.
It's here:
https://play.google.com/store/apps/details?id=com.cleanmaster.mguard&feature=nav_result#?t=W251bGwsMSwyLDNd
It's got a Residual Files cleaner which might get rid of the files that are causing your problems
shinobisoft said:
fastboot is a little weird. Boot device into fastboot mode, but not connected to PC. Then connect to PC after getting into fastboot mode.
Click to expand...
Click to collapse
So, Fastboot before hooking up the phone, gives me a driver searching Windows update for "Android"... I'm guessing that something is missing, yes?
WidowCranky said:
I think I've seen something like that before. I think it's when the APK is gone but the cache, dalvik etc for the app is still there.
If you haven't yet done anything hardcore to your phone. EG: Reflashing.
And can still boot into your ROM then you might wanna give Clean Master a go.
Click to expand...
Click to collapse
if I've got the room, I'll give that a try.
Deathpunkin said:
if I've got the room, I'll give that a try.
Click to expand...
Click to collapse
Clean Master didn't help at all, "Residual Files" only searched the SD card, even though the apps in question are taking up system space.
Thanks anyway Cranky...
might use that later for future uninstalls though.
Deathpunkin said:
So, Fastboot before hooking up the phone, gives me a driver searching Windows update for "Android"... I'm guessing that something is missing, yes?
Click to expand...
Click to collapse
Yeah, the driver from LG.
Go Here.
Scroll down to Manuals & Download, Software Update tab and then "Install the USB DRIVER"
Just get the driver, don't worry about the LG Mobile Support Tool. That's for updating the stock ROM.
Officially but there are no official updates since GB.
WidowCranky said:
Yeah, the driver from LG.
Go Here.
Scroll down to Manuals & Download, Software Update tab and then "Install the USB DRIVER"
Just get the driver, don't worry about the LG Mobile Support Tool. That's for updating the stock ROM.
Officially but there are no official updates since GB.
Click to expand...
Click to collapse
I have the drivers though..
I put that one in, then the United drivers.. which updated the ones from LG...
when I unplug the phone, Windows gave an error about unable to install ADB Modem or something like that..
Okay, so I have used RSD Lite before with no problem. I need to flash my entire device back to stock before tomorrow, but the program is not reading my phone. Motorola Device Manager is installed, same setup I had last time I had to flash after soft bricking...I can't figure it out. Any help would be very appreciated. Thank you.
Moto Q stock with Arrrghhh's kernel v.0.10
Have you entered AP Fastboot mode? Hold both volume button and power. You'll see bootmenu. And navigate using volume down and select AP Fastboot using volume up.
Sent from my XT897 using Tapatalk 2
No Go in Fastboot AP
huatz84 said:
Have you entered AP Fastboot mode? Hold both volume button and power. You'll see bootmenu. And navigate using volume down and select AP Fastboot using volume up.
Sent from my XT897 using Tapatalk 2
Click to expand...
Click to collapse
Yeah, totally know what to do, and what order to do it in, only RSD Lite will not acknowledge my device! Crazy, cause I just flashed stock image ASA 14 about 3 weeks ago, no problems.
Nevermind... hehe
---------- Post added at 09:25 PM ---------- Previous post was at 09:10 PM ----------
Are you in Windows? I find Windows pretty annoying when it comes to certain drivers. You might have a look in Device Manager while your phone is plugged in(maybe check with the phone is fastboot mode too), and see if there are any Moto related drivers that have a yellow exclamation point. If so, perhaps reinstalling Device Manager will fix it? Good luck
yogi2010 said:
Nevermind... hehe
---------- Post added at 09:25 PM ---------- Previous post was at 09:10 PM ----------
Are you in Windows? I find Windows pretty annoying when it comes to certain drivers. You might have a look in Device Manager while your phone is plugged in(maybe check with the phone is fastboot mode too), and see if there are any Moto related drivers that have a yellow exclamation point. If so, perhaps reinstalling Device Manager will fix it? Good luck
Click to expand...
Click to collapse
Tried uninstalling and reinstalling Moto Device Manager 3 times...no. Tried RSD Lite versions 5.7 through 6.1...nothing. Is there an actual driver pack I can install that would have the appropriate drivers?
(I have a dual boot laptop, Ubuntu and Win 7, using Windows)
Moto Q stock with Arrrghhh's kernel v.0.10
galacticservant said:
Tried uninstalling and reinstalling Moto Device Manager 3 times...no. Tried RSD Lite versions 5.7 through 6.1...nothing. Is there an actual driver pack I can install that would have the appropriate drivers?
(I have a dual boot laptop, Ubuntu and Win 7, using Windows)
Moto Q stock with Arrrghhh's kernel v.0.10
Click to expand...
Click to collapse
I do have a driver installer downloaded on my computer, but I don't know if it would help you. I will attach it here just in case.
I had this issue a month back, but Moto Device Manager ended up being the solution for me. I have RSD Lite 6.1.5, and it sill recognizes my device in fastboot mode.
edit: the site wouldn't let upload the files for some reason, so I used Dropbox. here is the driver installer I have, but i'm not sure, it might not have solved the issue for me. also, here is RSD Lite 6.1.5 in case you don't have it and wanna try it:
https://dl.dropboxusercontent.com/u/18474790/USB_Drivers_64_bit_4.6.5.zip
https://dl.dropboxusercontent.com/u/18474790/RSDLite6.1.5.zip
hope you get it working,,, i'm sure you will somehow..
yogi2010 said:
I do have a driver installer downloaded on my computer, but I don't know if it would help you. I will attach it here just in case.
I had this issue a month back, but Moto Device Manager ended up being the solution for me. I have RSD Lite 6.1.5, and it sill recognizes my device in fastboot mode.
edit: the site wouldn't let upload the files for some reason, so I used Dropbox. here is the driver installer I have, but i'm not sure, it might not have solved the issue for me. also, here is RSD Lite 6.1.5 in case you don't have it and wanna try it:
https://dl.dropboxusercontent.com/u/18474790/USB_Drivers_64_bit_4.6.5.zip
https://dl.dropboxusercontent.com/u/18474790/RSDLite6.1.5.zip
hope you get it working,,, i'm sure you will somehow..
Click to expand...
Click to collapse
Yeah, I'm sure somehow that I will...thanks for the files, I'll try that now. Oh, by the way, you should check out the Dev Host site (google it), they provide free file uploading and sharing for, well, developers (or anyone for that matter). Only 500 MBs worth of storage is provided for free, but that really is all I need. Anyway, I'll try your advice and let ya know.
***by the way, I need drivers for 32 bit, not 64***
Moto Q stock with Arrrghhh's kernel v.0.10
yogi2010 said:
I do have a driver installer downloaded on my computer, but I don't know if it would help you. I will attach it here just in case.
I had this issue a month back, but Moto Device Manager ended up being the solution for me. I have RSD Lite 6.1.5, and it sill recognizes my device in fastboot mode.
edit: the site wouldn't let upload the files for some reason, so I used Dropbox. here is the driver installer I have, but i'm not sure, it might not have solved the issue for me. also, here is RSD Lite 6.1.5 in case you don't have it and wanna try it:
https://dl.dropboxusercontent.com/u/18474790/USB_Drivers_64_bit_4.6.5.zip
https://dl.dropboxusercontent.com/u/18474790/RSDLite6.1.5.zip
hope you get it working,,, i'm sure you will somehow..
Click to expand...
Click to collapse
No dice, RSD still not reading device...no freaking clue
galacticservant said:
No dice, RSD still not reading device...no freaking clue
Click to expand...
Click to collapse
damn, that sucks! did you ever check Device Manager in the Control Panel. i remember seeing a missing Moto driver there, but then again, that led me on a driver search, which led me to Moto Device Manager. did you completely uninstall it first before reinstalling it?
i dunno, just throwing out ideas here lol. otherwise, you might be able to just fastboot flash the necessary components from the FXZ file to get your setup back to stock. or else use a stock TWRP backup, then reflash stock recovery. hope you get it
yogi2010 said:
damn, that sucks! did you ever check Device Manager in the Control Panel. i remember seeing a missing Moto driver there, but then again, that led me on a driver search, which led me to Moto Device Manager. did you completely uninstall it first before reinstalling it?
i dunno, just throwing out ideas here lol. otherwise, you might be able to just fastboot flash the necessary components from the FXZ file to get your setup back to stock. or else use a stock TWRP backup, then reflash stock recovery. hope you get it
Click to expand...
Click to collapse
Yup, used moto-fastboot.exe to push files FZB fles to device. All was okay until trying to flash system.img.ext4. Had error message. My battery was okay though, but said there was problem with multiflash...any ideas
Sent from my SPH-M930 using xda app-developers app
Try another SD-Card, I had problems with my 32GB Samsung SD-Card.
Loader009 said:
Try another SD-Card, I had problems with my 32GB Samsung SD-Card.
Click to expand...
Click to collapse
RSD Lite will have a hard time reading device due to a SD card?
Sent from my SPH-M930 using xda app-developers app
Sorry, I was thinking about nandroid and TWRP, not of RSD Lite...
My mistake.
Entering AP Fastboot
huatz84 said:
Have you entered AP Fastboot mode? Hold both volume button and power. You'll see bootmenu. And navigate using volume down and select AP Fastboot using volume up.
Sent from my XT897 using Tapatalk 2
Click to expand...
Click to collapse
You can also hold power and the camera button to enter bootloader, then choose AP Fastboot (just saying for users who may not know).
Loader009 said:
Sorry, I was thinking about nandroid and TWRP, not of RSD Lite...
My mistake.
Click to expand...
Click to collapse
Yeah, I have no problem using TWRP or flashing stuff from Internal or External SD
yogi2010 said:
damn, that sucks! did you ever check Device Manager in the Control Panel. i remember seeing a missing Moto driver there, but then again, that led me on a driver search, which led me to Moto Device Manager. did you completely uninstall it first before reinstalling it?
i dunno, just throwing out ideas here lol. otherwise, you might be able to just fastboot flash the necessary components from the FXZ file to get your setup back to stock. or else use a stock TWRP backup, then reflash stock recovery. hope you get it
Click to expand...
Click to collapse
Okay, now this is weird! I have my system back up and running, but I can only load it by starting the bootloader and choosing "normal startup"; otherwise my device boots into fastboot automatically every time I power down. Seems like I can't utilize stock recovery either when I flash it (otherwise I am using TWRP). My entire purpose behind unrooting and going back to stock was to update to JB as I participated in Moto's soak test. I am still stumped...?
System Up, Stock Recovery Down
Guess I'll try re-flashing the bootloader? or a version from a different/newer image?
galacticservant said:
Okay, now this is weird! I have my system back up and running, but I can only load it by starting the bootloader and choosing "normal startup"; otherwise my device boots into fastboot automatically every time I power down. Seems like I can't utilize stock recovery either when I flash it (otherwise I am using TWRP). My entire purpose behind unrooting and going back to stock was to update to JB as I participated in Moto's soak test. I am still stumped...?
System Up, Stock Recovery Down
Guess I'll try re-flashing the bootloader? or a version from a different/newer image?
Click to expand...
Click to collapse
hmm ok, that's good you made some progress, not sure what's up there. which file did you restore with RSD? i tried restoring the asa14 one last night and got an error immediately, but i'm not sure if i edited the xml properly.
so what i ended up doing was restoring this one: http://forum.xda-developers.com/showpost.php?p=33942232&postcount=12. it will restore everything to the original factory firmware that came with the phone.... except for the system. but i had already restored the stock system with a TWRP backup posted by rangerbry, so it was ok. then i had to run the 2 OTA updates on the phone to get up to the most recent official release. it's a bit convoluted, but it's an option, hehe.
yogi2010 said:
hmm ok, that's good you made some progress, not sure what's up there. which file did you restore with RSD? i tried restoring the asa14 one last night and got an error immediately, but i'm not sure if i edited the xml properly.
so what i ended up doing was restoring this one: http://forum.xda-developers.com/showpost.php?p=33942232&postcount=12. it will restore everything to the original factory firmware that came with the phone.... except for the system. but i had already restored the stock system with a TWRP backup posted by rangerbry, so it was ok. then i had to run the 2 OTA updates on the phone to get up to the most recent official release. it's a bit convoluted, but it's an option, hehe.
Click to expand...
Click to collapse
I think the problem is with the cdrom...my phone keeps booting into AP fastboot automatically like I said...and I was never able to get RSD Lite to recognize my device, so I only used fastboot and TWRP. RSD Lite is sadly not an option for me at this point...
Oh, the image that I previously restored with RSD was odexed and purely stock, ASA 14-15 Sprint. Now it wont read in RSD...
Sent from my XT897 using xda app-developers app
yogi2010 said:
hmm ok, that's good you made some progress, not sure what's up there. which file did you restore with RSD? i tried restoring the asa14 one last night and got an error immediately, but i'm not sure if i edited the xml properly.
so what i ended up doing was restoring this one: http://forum.xda-developers.com/showpost.php?p=33942232&postcount=12. it will restore everything to the original factory firmware that came with the phone.... except for the system. but i had already restored the stock system with a TWRP backup posted by rangerbry, so it was ok. then i had to run the 2 OTA updates on the phone to get up to the most recent official release. it's a bit convoluted, but it's an option, hehe.
Click to expand...
Click to collapse
Something else that I totally overlooked...the red Motorola ripple boot animation doesn't even play anymore! It goes right to the sprint_bootanimation...something's not quite right in Moto Land!
Sent from my XT897 using xda app-developers app
galacticservant said:
Okay, now this is weird! I have my system back up and running, but I can only load it by starting the bootloader and choosing "normal startup"; otherwise my device boots into fastboot automatically every time I power down. Seems like I can't utilize stock recovery either when I flash it (otherwise I am using TWRP). My entire purpose behind unrooting and going back to stock was to update to JB as I participated in Moto's soak test. I am still stumped...?
System Up, Stock Recovery Down
Guess I'll try re-flashing the bootloader? or a version from a different/newer image?
Click to expand...
Click to collapse
Stock recovery still not functioning, but phone doesn't auto load fastboot anymore. Still can only load system from bootloader. But also TWRP doesn't disappear after reboot. I flashed cdrom, but is what is the extension? Is it a .img, or is it supposed to be? In details it just said "file".
Sent from my XT897 using xda app-developers app
I'm new to Motorola in the smartphone world, but just upgraded to a Droid Maxx Developer Edition. The bootloader is unlocked and it has root, but with the stock ROM. Well since yesterday it has been VERY annoyingly insisting on installing an OTA device update every few hours. After postponing it and postponing it I accidentally selected install. Now it's constantly rebooting into recovery (I assume) to install the update, but TWRP loads instead of the stock recovery so nothing happens. Then when I reboot into Android (4.2 19.5.3), within 2 minutes it reboots again to attempt installing the update.
Now, I'm ready to get away from stock (played with it stock for about a month, ready to move on), so I downloaded CM for it. But it won't stay booted into Android long enough for me to copy the .zip over to the phone to flash in TWRP. Also, I've never done anything in adb or fastboot. However, I did install adb (Windows 7 64-bit) and have been playing with that. When my phone is in android, I can usually see it listed as "TA4310BUAV unauthorized" when I run adb devices. After googling, this is because I've not authorized my computer on my phone. However, even after selecting 'revoke all authorizations' or whatever in developer settings, I still get no notification to authorize. And then when I'm booted into TWRP I can't see the phone at all.
Basically, I'm stuck in a bootloop and just want to copy the CM zip file to the phone so I can flash it in TWRP, but I'm at a loss as to how to do this. Can anyone provide me with some advice on how to proceed? It would be greatly appreciated!!
carmike692000 said:
I'm new to Motorola in the smartphone world, but just upgraded to a Droid Maxx Developer Edition. The bootloader is unlocked and it has root, but with the stock ROM. Well since yesterday it has been VERY annoyingly insisting on installing an OTA device update every few hours. After postponing it and postponing it I accidentally selected install. Now it's constantly rebooting into recovery (I assume) to install the update, but TWRP loads instead of the stock recovery so nothing happens. Then when I reboot into Android (4.2 19.5.3), within 2 minutes it reboots again to attempt installing the update.
Now, I'm ready to get away from stock (played with it stock for about a month, ready to move on), so I downloaded CM for it. But it won't stay booted into Android long enough for me to copy the .zip over to the phone to flash in TWRP. Also, I've never done anything in adb or fastboot. However, I did install adb (Windows 7 64-bit) and have been playing with that. When my phone is in android, I can usually see it listed as "TA4310BUAV unauthorized" when I run adb devices. After googling, this is because I've not authorized my computer on my phone. However, even after selecting 'revoke all authorizations' or whatever in developer settings, I still get no notification to authorize. And then when I'm booted into TWRP I can't see the phone at all.
Basically, I'm stuck in a bootloop and just want to copy the CM zip file to the phone so I can flash it in TWRP, but I'm at a loss as to how to do this. Can anyone provide me with some advice on how to proceed? It would be greatly appreciated!!
Click to expand...
Click to collapse
In TWRP try wiping your cache. That should delete the OTA. Then when you boot back into the OS use titanium backup to freeze the app "MotorolaOTA." That should do it.
Sent From Droid Ultra
Caseyk621 said:
In TWRP try wiping your cache. That should delete the OTA. Then when you boot back into the OS use titanium backup to freeze the app "MotorolaOTA." That should do it.
Sent From Droid Ultra
Click to expand...
Click to collapse
Thank you so much! I will try this immediately. I just figured out how to get into fastbook, and my computer recognizes the phone in that mode. Is that a good method for pushing the CM.zip to the phone (just for future reference if the above doesn't work)?
carmike692000 said:
Thank you so much! I will try this immediately. I just figured out how to get into fastbook, and my computer recognizes the phone in that mode. Is that a good method for pushing the CM.zip to the phone (just for future reference if the above doesn't work)?
Click to expand...
Click to collapse
May be wrong but I don't think you can push files in that way via fastboot. If my first method didn't work let me know. There are a few other things to try.
Sent From Droid Ultra
Caseyk621 said:
May be wrong but I don't think you can push files in that way via fastboot. If my first method didn't work let me know. There are a few other things to try.
Sent From Droid Ultra
Click to expand...
Click to collapse
I erased the cache like you said (though I did it through fastboot since I already had it up and it's 'new and exciting' and all), and rebooted. Seems to have worked so far. I could go ahead and d/l TiB and freeze that service like you said, but since I'm going to flash CM anyways, I don't see as that's necessary at the moment. However, I can't get W7 to see the phone to be able to transfer the .zip to the phone, whether by Windows Explorer or adb, because I still don't have the option on the phone to authorize my laptop.
EDIT - I'm sure one problem with the computer not listing the phone as a device is it cannot find the device driver to install for it, and I've not been successful googling for it. So in the Windows Device Manager list, my XT1080 has a yellow exclamation mark by it. Also, just installed TiB and froze "Motorola OTA" since I had to wait five minutes to post this edit anyways.
carmike692000 said:
I erased the cache like you said (though I did it through fastboot since I already had it up and it's 'new and exciting' and all), and rebooted. Seems to have worked so far. I could go ahead and d/l TiB and freeze that service like you said, but since I'm going to flash CM anyways, I don't see as that's necessary at the moment. However, I can't get W7 to see the phone to be able to transfer the .zip to the phone, whether by Windows Explorer or adb, because I still don't have the option on the phone to authorize my laptop.
Click to expand...
Click to collapse
Ok i just like to disable the OTA app to avoid accidentally upgrading and bootlooping. Plus I'm assuming that you'll be making a back up of your stock system to go back to should you not care for CM. Do you have USB debugging enabled on your phone?
Sent From Droid Ultra
Caseyk621 said:
Ok i just like to disable the OTA app to avoid accidentally upgrading and bootlooping. Plus I'm assuming that you'll be making a back up of your stock system to go back to should you not care for CM. Do you have USB debugging enabled on your phone?
Sent From Droid Ultra
Click to expand...
Click to collapse
As per my edit above, I have now frozen "Motorola OTA". That is a great point regarding the backup.
Yes, I do have USB debugging enabled on my phone. Also, per my edit above, not having the proper driver installed for my phone may be the limiting factor here. Though having never used adb before, maybe it's a slew of other things, I'm not sure.
carmike692000 said:
As per my edit above, I have now frozen "Motorola OTA". That is a great point regarding the backup.
Yes, I do have USB debugging enabled on my phone. Also, per my edit above, not having the proper driver installed for my phone may be the limiting factor here. Though having never used adb before, maybe it's a slew of other things, I'm not sure.
Click to expand...
Click to collapse
Maybe here
https://motorola-global-portal.custhelp.com/app/answers/detail/a_id/88481
Sent From Droid Ultra
Caseyk621 said:
Maybe here
https://motorola-global-portal.custhelp.com/app/answers/detail/a_id/88481
Sent From Droid Ultra
Click to expand...
Click to collapse
Finally we're getting somewhere. I had installed that earlier, but never had any success with it. However, after just aimlessly disabling and reenabling things (USB debugging, PTP media sharing, revoking authorizations), and unplugging/replugging, it finally installed the driver. And now adb recognizes it, I was able to authorize my laptop, and I just copy and pasted the cm .zip to my phone.
It seems everything is going to work out just fine! I'm going to back up a few things with TiB and then flash CM.
Thank you so much for your input! I'd still be dead in the water if it weren't for your help!
carmike692000 said:
Finally we're getting somewhere. I had installed that earlier, but never had any success with it. However, after just aimlessly disabling and reenabling things (USB debugging, PTP media sharing, revoking authorizations), and unplugging/replugging, it finally installed the driver. And now adb recognizes it, I was able to authorize my laptop, and I just copy and pasted the cm .zip to my phone.
It seems everything is going to work out just fine! I'm going to back up a few things with TiB and then flash CM.
Thank you so much for your input! I'd still be dead in the water if it weren't for your help!
Click to expand...
Click to collapse
Glad I could help! Don't forget to make a backup in TWRP! You may find yourself wanting to go back to stock sooner than you think! I keep trying ROMs but always end up missing active notifications and touch less as well as some others!
Sent From Droid Ultra
I am wanting to take and install the latest Ota update. I'm rooted and unlocked (via Chinese method). My question is how do I actually install the downloaded update considering that I have twrp for a recovery?.... Thank you in advance
nubia11 said:
I am wanting to take and install the latest Ota update. I'm rooted and unlocked (via Chinese method). My question is how do I actually install the downloaded update considering that I have twrp for a recovery?.... Thank you in advance
Click to expand...
Click to collapse
Flash the stock recovery with fastboot. I forget if you need to also unroot or not. Also make sure you have any apps that were disabled or frozen enabled/defrosted