Related
So I went from the UCKK4 leak to the newest CatyROM. I was having a lot of issues with the gallery and the music player so I decided to head back to stock for now to put a leak or a different ROM back on. I started up Odin with the pre-installed root+3e return to stock, but it got stuck so I pulled it. Then I went to full on rainbows, no DL mode, nothing. Then I used GTG's unbrick and it got stuck so I pulled again. Now I've got DL mode (regular) But Odin keeps getting stuck on factoryfs.rfs. I rebooted my computer, tried a different port, all that. I can't use another computer since I don't have a second one. I'm definitely at a loss on this one. Anyone got anything?
Redownload or try Adam's Hemidall.
Try a different cord. I had the same problem on a different rom
Sent from my SGH-I997 using xda premium
The phone won't even detect in Heimdall. I can't figure out how to use Adam's either since I've never used Heimdall. The phone does go into DL mode and the PC and Odin detect it, but that's about it
EDIT: I should asp add that when I get up to factoryfs.rfs the DL mode progress bar does show about 1/16 worth of progress.
Seriously guys... nothing else?
Kevinr678 said:
Seriously guys... nothing else?
Click to expand...
Click to collapse
Kev,
If I understood heimdall correctly, according to description, it is different from odin. it installs a different usb drivers.
I think you should give heimdall a try again.
I don't know if odin does anything to prevent heimdall from recognizing your phone or not.
UN-install all usb drivers for the phone.
assign 1 usb port just for heimdall
DL Adam's heimdall uckj4 1click
update to newest java.
put your phone in DL mode.
run 1 click.
zadig should allow you to install it's own usb driver.
if heimdall does not recognize your phone or show connected,
try rebooting windows
and try 1 click again.
if the first flash doesn't work, flash 2nd time with boatloader checked.
good luck
btw, next time you get FC's on gallery or music, it may because there were left over files from the previous rom such as thumbnails and data. you can try to manually locate theses files and delete them and their folders or flush them or even use Tibu to flush or delete the apps and then reboot and reinstall.
qkster said:
Kev,
If I understood heimdall correctly, according to description, it is different from odin. it installs a different usb drivers.
I think you should give heimdall a try again.
I don't know if odin does anything to prevent heimdall from recognizing your phone or not.
UN-install all usb drivers for the phone.
assign 1 usb port just for heimdall
DL Adam's heimdall uckj4 1click
update to newest java.
put your phone in DL mode.
run 1 click.
zadig should allow you to install it's own usb driver.
if heimdall does not recognize your phone or show connected,
try rebooting windows
and try 1 click again.
if the first flash doesn't work, flash 2nd time with boatloader checked.
good luck
Click to expand...
Click to collapse
That's the problem. I've tried all of that. I have to say, I'm very saddened by this issue. I tried Adam's one-click as well, but for some reason, my java won't allow it to open, and I do have the latest. Man, I'm really at a loss on this one... Ireally appreciate the response though. Hmm.... I'm really not sure what to do at this point.
Kevinr678 said:
That's the problem. I've tried all of that. I have to say, I'm very saddened by this issue. I tried Adam's one-click as well, but for some reason, my java won't allow it to open, and I do have the latest. Man, I'm really at a loss on this one... Ireally appreciate the response though. Hmm.... I'm really not sure what to do at this point.
Click to expand...
Click to collapse
it may be your windows. disable firewall? and anti-virus programs?
it may be helpful to borrow someone else's pc - (I had good luck with winXp), install java and try it again.
you're best bet is heimdall from what I read about it.
edit: you may have a corrupt partition at the location, i think heimdall will correct this.
qkster said:
it may be your windows. disable firewall? and anti-virus programs?
it may be helpful to borrow someone else's pc - (I had good luck with winXp), install java and try it again.
you're best bet is heimdall from what I read about it.
edit: you may have a corrupt partition at the location, i think heimdall will correct this.
Click to expand...
Click to collapse
Yeah, I disabled all that. I don't have another personally, but I may be able to borrow my sister's at some point if I can find the cable for the monitor. My brother in-law has a Mac, maybe I could use that if I could figure out how to use newer Mac softwares.
Kevinr678 said:
Yeah, I disabled all that. I don't have another personally, but I may be able to borrow my sister's at some point if I can find the cable for the monitor. My brother in-law has a Mac, maybe I could use that if I could figure out how to use newer Mac softwares.
Click to expand...
Click to collapse
You're almost there, man. If you can get heimdall to run, it will restore your phone.
qkster said:
You're almost there, man. If you can get heimdall to run, it will restore your phone.
Click to expand...
Click to collapse
I sure hope so, haha. I'm quite sad that I can't look at this gorgeous screen
Kevinr678 said:
I sure hope so, haha. I'm quite sad that I can't look at this gorgeous screen
Click to expand...
Click to collapse
try reading this thread..
http://forum.xda-developers.com/showthread.php?t=1367099
qkster said:
try reading this thread..
http://forum.xda-developers.com/showthread.php?t=1367099
Click to expand...
Click to collapse
Sorry man, had to run off and take care of a few things. Trying this now.
Having some issues getting Heimdall to recognize my phone in DL mode. I'll try a few more things before I head off to bed.
make sure you go through the device options and choose the correct device drivers
qkster said:
make sure you go through the device options and choose the correct device drivers
Click to expand...
Click to collapse
I've done that with the Samsungcomposite drivers or whatever with zadig. I'm just having no luck getting it to connect :/
Kevinr678 said:
I've done that with the Samsungcomposite drivers or whatever with zadig. I'm just having no luck getting it to connect :/
Click to expand...
Click to collapse
hmm...i remembered similar problems when i had tried odin first after all the kies and sammy drivers etc - i think it may have borked my usb to recognize heimdall
almost gave up until i tried heimdall first on a different PC...worked immediately.
i guessing your window version and usb drivers may be corrupt...
If you don't have another pc, un-install generic usb drivers and then re-install or try a new usb adapter or hub may fix it.
Maybe reinstall windows?
I may even give it a shot with a virtual box running XP if that'll work.
I have to get up early tomorrow morning, so I'm gonna pick this back up later tomorrow. Thanks a lot for all the help qkster. Hopefully I can get this baby up and running again.
no prob..good luck
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.
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 bricked my Photon Q while customizing with font apks and soft key customization.. I cannot access recovery, as it just attempts to normally boot. When it normally boots, it gets to the final frame in the boot animation and does not do anything else. I do not have boot loader unlocked and this is a last resort for me. :crying:
I will answer any necessary questions to getting my phone unbricked!
Thanks!
Have you tried flashing stock firmware via RSDlite?
rabinhood said:
Have you tried flashing stock firmware via RSDlite?
Click to expand...
Click to collapse
I have not, trying to boot in any mode except Fastboot will go through the normal boot, also I am running a Linux OS and do not know if I can run RSDLite through Wine or not.
MotoLegacy said:
I have not, trying to boot in any mode except Fastboot will go through the normal boot, also I am running a Linux OS and do not know if I can run RSDLite through Wine or not.
Click to expand...
Click to collapse
Do NOT run RSDLite thru Wine (or a VM for that matter).
Borrow a Windows machine if you have to.
RSDlite runs with no problems on VirtualBox (closed source binary version - with USB pass through) running XP. At least it worked well with Motorola Droid 2.
[edit]
I know flashing bootloader may be more risky, but for many (countless) times I flashed Droid 2 and 3 under linux running a VirtualBox VM with XP installed, and never had any problems. I haven't done it with PQ, since I had no need to flash it.
rabinhood said:
RSDlite runs with no problems on VirtualBox (closed source binary version - with USB pass through) running XP. At least it worked well with Motorola Droid 2.
[edit]
I know flashing bootloader may be more risky, but for many (countless) times I flashed Droid 2 and 3 under linux running a VirtualBox VM with XP installed, and never had any problems. I haven't done it with PQ, since I had no need to flash it.
Click to expand...
Click to collapse
I'm not saying that it is impossible - certainly with USB passthru it *should* work.
But why risk it? I can't recommend using that method - again, may work... but may turn your device into a permanent paperweight if something flakes during the flashing process.
arrrghhh said:
I'm not saying that it is impossible - certainly with USB passthru it *should* work.
But why risk it? I can't recommend using that method - again, may work... but may turn your device into a permanent paperweight if something flakes during the flashing process.
Click to expand...
Click to collapse
I will borrow a Windows machine and try RSDLite, I will post results in a day or two..
I'm still wondering why I was bricked by installing simple customization applications. Maybe it was just a coincidence though.
Kb2005 international version just purchased. Rooted but lost wifi access tried to fix and bricked stuck in fastboot repeat and red boot loop
Hi,
You may try to boot to safe mode. Just a thought. If you choose to do it, I am not responsible if it would not work or if something else wrong happens.
Good luck!
Have you MSM'd back to stock? https://androidfilehost.com/?fid=2188818919693750637
craznazn said:
Have you MSM'd back to stock? https://androidfilehost.com/?fid=2188818919693750637
Click to expand...
Click to collapse
Mam isnt working this should work on a vm too right ive installed all usb drivers too
amplatfus said:
Hi,
You may try to boot to safe mode. Just a thought. If you choose to do it, I am not responsible if it would not work or if something else wrong happens.
Good luck!
Click to expand...
Click to collapse
Thanks for the reply thats fine im ok i just want to try and get it back its a brand new phone
Method 1. Download Full ROM, and Payload Dumper. Extract payload.bin and put it to payload_input folder and all *.img files will be in payload_output folder. Use fastboot flash boot boot.img command and reboot. Device should work after reboot. If you need root, either flash a patched boot.img or use flashboot to flash TWRP and then install Magisk from TWRP.
Method 2. Manually flash *.img files. Reference: [GUIDE] Unbrick or restore to OOS using only fastboot
Method 3. Use MSMtool to wipe and restore your phone.
Note: If you lost WiFi AFTER your device is rooted, and if you ever installed a custom kernel, it's probably the RAMDISK (can't remember where I saw it before) causing the issue. Easy solution, flash same custom kernel again. Or try different kernels.
So these unbricktools here don't work for you?
Index of /list/Unbrick_Tools/OnePlus_8T
Millyrocker said:
Mam isnt working this should work on a vm too right ive installed all usb drivers too
Click to expand...
Click to collapse
EDL mode will disconnect/reconnect several times and change connection protocol. Your virtual machine may lost device due to this process.
So better on Windows PC.
ULTRAJC said:
EDL mode will disconnect/reconnect several times and change connection protocol. Your virtual machine may lost device due to this process.
So better on Windows PC.
Click to expand...
Click to collapse
Im on linux right now im trying to find a way to install windows but even thats not working smh
Millyrocker said:
Im on linux right now im trying to find a way to install windows but even thats not working smh
Click to expand...
Click to collapse
I applaud your use of linux! Unfortunately, I've not found a good solution under linux to do what the windows MSM tool can do. I had to book in to a full Win install in order to use it on my phone as well.
On a positive note, it's nearly impossible to truely brick these phones. The negative is the MSM tool needs windows. Unless someone can point to a linux solution (which I'd love) you may need to find a friend with Windows and borrow their computer...
The fact you are in fastboot loop makes me think you should be able to just fastboot flash everything manually. MSM is the nuclear option. I'd try getting the stock full ROM and manually flashing everything in fastboot.
What fastboot are you using? I've found that the one in many linux distributions are old. Download the latest from Android https://dl.google.com/android/repository/platform-tools-latest-linux.zip and use this.
Millyrocker said:
Im on linux right now im trying to find a way to install windows but even thats not working smh
Click to expand...
Click to collapse
EDL mode will reboot itself if there was no command sent to the phone. So you need to run MSM tool first and once you see the phone is recognized, just execute.
A real Windows should make whole process a lot more easier. If you use a VM, as long as Windows can recognize Qualcomm Modem driver, it should work too.