[Q] Atrix 2 soft bricked after root + cyanogen install - Motorola Atrix 2

Atrix 2 with stock ROM on 2.3.6.
I used this guide to root my phone: http://forum.xda-developers.com/showthread.php?t=1327741
Then I used this guide to try to install cyanogen: http://www.theandroidsoul.com/cyanogenmod-10-for-motorola-atrix-2-cm10/
After installing the ROM which went successfully, I selected " reboot system now" and got stuck on the Dual Core Technology screen. It sits there indefintiely now.
I am able to get into the recovery mode thing by pressing Power+VolUp+VolDown -- this gives me the options
"Normal Powerup" (doesn't work, stuck on the Dual Core Technology)
"Recovery" (doesn't work stuck on a screen with an android logo and an exclamation mark)
"AP FastBoot" (allows me to connect a USB cable)
"BP Tools" (dosen't work, stuck on the Dual Core Technology)
I've tried everything I can think of, tried moto-fastboot -w and that didn't work. I tried to install romracer's CWM recovery but I got this:
Code:
E:\System\Desktop\moto-fastboot-win32>moto-fastboot.exe devices
XXXXXXXXXXXXXXXXX fastboot
E:\System\Desktop\moto-fastboot-win32>moto-fastboot.exe erase recovery
erasing 'recovery'... INFOCommand restricted
FAILED (remote: )
E:\System\Desktop\moto-fastboot-win32>moto-fastboot.exe flash recovery recovery.img
sending 'recovery' (4708 KB)... OKAY [ 0.432s]
writing 'recovery'... INFOPreflash validation failure
FAILED (remote: )
How to fix this??

Your first issue was that you were on 2.3.6 when you tried to flash CM10... YOU MUST BE ON ICS BEFORE FLASHING CM10!
So now you need to apply the fxz. Go look at the noob thread:
http://forum.xda-developers.com/showthread.php?t=1396650
That will tell you how ^^
now go get the correct fxz file from here:
http://sbf.droid-developers.org/edison/list.php
And since you will want to use the ICS fxz, make sure you grab the 6.0 version of RSD lite from here:
https://hotfile.com/dl/174582400/60ad26d/RSDLite_6.0.rar.html
Now you need to do some more reading on this forum, we have all the info you need. It is important to read, read, and read some more before doing anything.

Hi Jim,
Thanks for that, I am back up and running now on 2.3.6 via the zip file on the site you linked!
Is there a thread on how to upgrade to 4 ICS? I understand this handset is supported.
Or, perhaps a definitve guide on how to go to from my current version up to Cyanogen?
Thanks again in advance, you've been very helpful!

breakaway said:
Hi Jim,
Thanks for that, I am back up and running now on 2.3.6 via the zip file on the site you linked!
Is there a thread on how to upgrade to 4 ICS? I understand this handset is supported.
Or, perhaps a definitve guide on how to go to from my current version up to Cyanogen?
Thanks again in advance, you've been very helpful!
Click to expand...
Click to collapse
I think everyone would agree with me when they tell you to stick with the leak 1 for a atrix2 2 that Jim posted in the general section it's the only version of ice cream that lets you return to Gingerbread safely. Once you have installed and follow the guidelines in Jim's thread you should be able to install any ROM based on ICS. I would recommend magic mod, it seems to be the fastest.
From my locked down superchargedV6 1.425ghz A "What tha duce?"

I was gonna to follow the instructions in this thread to do that http://forum.xda-developers.com/showthread.php?t=1779968
I just tried this but I when it tries to install it says
Code:
E: failed to verify whole-file signature
E: signature verification failed
And won't let me install it!
Also just to clarify this rom is for AT&T the US carrier -- but I"m in NZ -- trust this doesn't have any bearing on why its failing.

breakaway said:
I was gonna to follow the instructions in this thread to do that http://forum.xda-developers.com/showthread.php?t=1779968
I just tried this but I when it tries to install it says
Code:
E: failed to verify whole-file signature
E: signature verification failed
And won't let me install it!
Also just to clarify this rom is for AT&T the US carrier -- but I"m in NZ -- trust this doesn't have any bearing on why its failing.
Click to expand...
Click to collapse
Once you fxz back to 2.3.6, you're not supposed to set up any accounts or anything before flashing ICS leak. Just follow Jim's instructions and it will work like a charm.
Sent from yours truly..
ΧΔΑ Fraternity's Rush Chairman
{
"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"
}

Ok I swear this time I put the phone in AP-FastBoot mode, flashed the 2.3.6 ROM using RSD Lite v6.1.4, then when it was done sitting on the "Tap the droid to begin" screen, I shut it down, entered the recovery mode, and told it to flash the update from SD card, and I got the same thing!
Code:
E: failed to verify whole-file signature
E: signature verification failed
Any ideas?

breakaway said:
Ok I swear this time I put the phone in AP-FastBoot mode, flashed the 2.3.6 ROM using RSD Lite v6.1.4, then when it was done sitting on the "Tap the droid to begin" screen, I shut it down, entered the recovery mode, and told it to flash the update from SD card, and I got the same thing!
Code:
E: failed to verify whole-file signature
E: signature verification failed
Any ideas?
Click to expand...
Click to collapse
Well you should probably check to make sure USB debugging and unknown sources are enabled in the settings menu, just in case. I only meant don't sign in to any email accounts or sync with AT&T or anything like that. If this doesn't help, then try it all over again because there shouldn't be any problems if your completely stock.
Sent from yours truly..
ΧΔΑ Fraternity's Rush Chairman

breakaway said:
Ok I swear this time I put the phone in AP-FastBoot mode, flashed the 2.3.6 ROM using RSD Lite v6.1.4, then when it was done sitting on the "Tap the droid to begin" screen, I shut it down, entered the recovery mode, and told it to flash the update from SD card, and I got the same thing!
Code:
E: failed to verify whole-file signature
E: signature verification failed
Any ideas?
Click to expand...
Click to collapse
You have a bad/corrupt file. Re-download the Blur file and use the MD5 to make sure it passes the checksum, that is what the installer will also try and do first, and why you are getting that error.

Axis_Drummer -- I noticed that USB Debugging was off, so I turned it on and tried again but no dice!
Jim - I Just used MD5sum to compare the hash of the file Blur_Version.55.13.25.MB865.ATT.en.US.zip on the file on the SD card
and got this
Code:
5bd615584406ba726ad7d49a225dd6f1
the link in your thread says its supposed to be this
Code:
5bd615584406ba726ad7d49a225dd6f1
Any ideas what else it cold be if it isn't the MD5?

breakaway said:
Axis_Drummer -- I noticed that USB Debugging was off, so I turned it on and tried again but no dice!
Jim - I Just used MD5sum to compare the hash of the file Blur_Version.55.13.25.MB865.ATT.en.US.zip on the file on the SD card
and got this
Code:
5bd615584406ba726ad7d49a225dd6f1
the link in your thread says its supposed to be this
Code:
5bd615584406ba726ad7d49a225dd6f1
Any ideas what else it cold be if it isn't the MD5?
Click to expand...
Click to collapse
I'm wondering if you know u have to run the leak update twice right? Could be a dumb response but I thought I would ask....
Sent from my MB865 using xda app-developers app

Bump, anyone? :crying:

daavvis said:
I'm wondering if you know u have to run the leak update twice right? Could be a dumb response but I thought I would ask....
Sent from my MB865 using xda app-developers app
Click to expand...
Click to collapse
Hi,
I can't even get it to 'take' the first time. When I flash it it's supposed to come up with a 'dead droid' logo and then you flash it again, but mine just sits there permanently with 'invalid signature'. I think this has to do with how my phone isn't from AT&T...
Here's what I get after attempting to flash twice:

breakaway said:
Hi,
I can't even get it to 'take' the first time. When I flash it it's supposed to come up with a 'dead droid' logo and then you flash it again, but mine just sits there permanently with 'invalid signature'. I think this has to do with how my phone isn't from AT&T...
Here's what I get after attempting to flash twice:
Click to expand...
Click to collapse
If your phone is not an ATT phone, leak one from my thread, will not install on your phone.

Right, that must be what it is then.
Are there other ways to get CM10 (or any other ICS ROM) on here?

cant get my pc to recognize my device
jimbridgman said:
Your first issue was that you were on 2.3.6 when you tried to flash CM10... YOU MUST BE ON ICS BEFORE FLASHING CM10!
So now you need to apply the fxz. Go look at the noob thread:
http://forum.xda-developers.com/showthread.php?t=1396650
That will tell you how ^^
now go get the correct fxz file from here:
http://sbf.droid-developers.org/edison/list.php
And since you will want to use the ICS fxz, make sure you grab the 6.0 version of RSD lite from here:
https://hotfile.com/dl/174582400/60ad26d/RSDLite_6.0.rar.html
Now you need to do some more reading on this forum, we have all the info you need. It is important to read, read, and read some more before doing anything.
Click to expand...
Click to collapse
i have everything setup and ready to go but when i connect the usb my pc will not recognize my dvice ther for i cant start rsd lite. i have installed and reinstalled the drivers from motorola but to no avail. what to do, i am lost with out my phone.

jimbridgman said:
Your first issue was that you were on 2.3.6 when you tried to flash CM10... YOU MUST BE ON ICS BEFORE FLASHING CM10!
So now you need to apply the fxz. Go look at the noob thread:
http://forum.xda-developers.com/showthread.php?t=1396650
That will tell you how ^^
now go get the correct fxz file from here:
http://sbf.droid-developers.org/edison/list.php
And since you will want to use the ICS fxz, make sure you grab the 6.0 version of RSD lite from here:
https://hotfile.com/dl/174582400/60ad26d/RSDLite_6.0.rar.html
Now you need to do some more reading on this forum, we have all the info you need. It is important to read, read, and read some more before doing anything.
Click to expand...
Click to collapse
Damn we need to bump that noob thread often Ive never even seen it
Its real resourceful solves almost all problems ....:good:
---------- Post added at 03:57 PM ---------- Previous post was at 03:55 PM ----------
Imabitslow said:
i have everything setup and ready to go but when i connect the usb my pc will not recognize my dvice ther for i cant start rsd lite. i have installed and reinstalled the drivers from motorola but to no avail. what to do, i am lost with out my phone.
Click to expand...
Click to collapse
Read this thread and goto the one about FXZ....
http://forum.xda-developers.com/showthread.php?t=2472331:D

atrix 2 soft brick boot loop. pc will not reason recognize my device to fastboot
darth_nihar said:
Damn we need to bump that noob thread often Ive never even seen it
Its real resourceful solves almost all problems ....:good:
---------- Post added at 03:57 PM ---------- Previous post was at 03:55 PM ----------
Read this thread and goto the one about FXZ....
http://forum.xda-developers.com/showthread.php?t=2472331:D
Click to expand...
Click to collapse
I have a motorola atrix 2 mb 865. i was on gb 2.3.6 and not knowing what i was doing i updated it to jelly bean using cwm from recovery menu. i got a message saying every thing was successful but when it went to boot it got stuck in a boot loop. i have tried rsd lite fxz fastboot but my computer will not recognize the phone i have uninstalled and reinstalled the correct drivers but still the pc will not recognize. i am able to update with sdcard going into stock recovery on android but every blur_version i have tried either says assert failed or veryfing signature failed. im at a complete loss here please can some one help me. i have looked all over the web but to no avail.

were good
ok so i dont knw if this is only on my device but heres what i did to get out of the soft brick boot loop. upon powering on whe the first motorola icon shows up i hit the volume down key. the logo disappears. after the logo disappears i hit the menu button on my phone while simotaneously pressing the middle of the screen. (my atrix 2 was rooted unlocked and i installed clock work mod) so as i pressed the menu and middle of the screen simotaneously it took me to the cwm recovery. here i was able to go back to stock rom via sdcard update blur version 55.13.25 http://*******/ChEMK and now my phone is back to its old self. i am at ease now. hope this helps some one who was in the same jam i was in

Related

[Q] Atrix 2.3.5 with Supercharged ROM Unrooted?

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.

Generic Cyanogenmod 10 help/discussion thread

Post in this thread if you need help getting CM to work, or if you have a problem and need help.
This thread is about:
- Discussing Cyanogenmod on the Optimus 3D/ 4G thrill/... phones
- Asking questions about Cyanogenmod
- Answering questions posted here
- Ask for help, because you can't get it to work
- Help people who can't figure something out
This thread is made with the intent to solve these problems:
1. Not have (duplicate) threads spamming this subforum asking for help
2. Create a nice environment for the developer of CM, Arcee, to work with. He has already said that the previous solution was a mess.
Arcee is a great guy, but messy forums can be very frustrating.
I'll make a posting guide.
[highlight]WHERE TO POST[/highlight]
{
"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"
}
[highlight]Get the latest nightlies here![/highlight]
http://www.get.cm/?device=p920
My Problem:
No IMEI so .. no singnal!!
Flashed bernys files but didn't help!
Cm10 is so nice!
PLZ help me!
Sent from my LG-P920 using xda app-developers app
History? current version?
I'm coming Form 21e and flashed cm10 via cwm and everythimg works feine except Form im ei and little Problem... while listening Tod an sound i can't change loudness
Sent from my LG-P920 using xda app-developers app
Before moving from lg to cm10, you did not downgrade to 21d or similar? This, atm, seems to fix problems like the imei not showing based on input from the other users. Give it a try, make sure you do all the wipes etc. and it should work, it does here.
philivm said:
My Problem:
No IMEI so .. no singnal!!
Flashed bernys files but didn't help!
Cm10 is so nice!
PLZ help me!
Sent from my LG-P920 using xda app-developers app
Click to expand...
Click to collapse
This is being worked on. I have it too, the logs are already posted in the other thread. Be patient!
philivm said:
I'm coming Form 21e and flashed cm10 via cwm and everythimg works feine except Form im ei and little Problem... while listening Tod an sound i can't change loudness
Sent from my LG-P920 using xda app-developers app
Click to expand...
Click to collapse
Sound problem and IMEI problem are being worked on.
Nanax said:
Before moving from lg to cm10, you did not downgrade to 21d or similar? This, atm, seems to fix problems like the imei not showing based on input from the other users. Give it a try, make sure you do all the wipes etc. and it should work, it does here.
Click to expand...
Click to collapse
For some people this works, for others it doesn't. I haven't tried myself, but Arcee said the baseband shouldn't matter. With that knowledge I'll be patient for a bit before I try this.
Thanks for using this thread!
True, but most succes stories i've seen have been on v21d or lower, so if he/she is dying to get it working, this might be worth the 20 min ey
Think this thread is a good idea. I'm afraid there could be the time when arcee get totally ****ed up about the "It's not working, what should I do" posts from 1000 users in the thread in which he just wanted error logs. So let's whine here: it's not working for me either lol
To let this be a little useful can you please always post the newest version and maybe changelog/bugfixes und probably working combinations in post 1? The link http://download.cyanogenmod.org/?type=nightly&device=p920 is useful as well there. This thread is btw kinda the same: http://forum.xda-developers.com/showthread.php?t=1540163
This graph thing is cool, maybe we should make something similar:
Did you flash ICS before? - Yes - Downgrade and replace the u-boot & loader - etc - etc
- No - Did wipes? (Try again) - Fixed permissions? - Did you try flashing a clean KDZ? (try again) - Did you search the thread? - Still no solution? Post a q!
------------
If i may add a question/suggestion:
With all the new nightlies comming out, what would be the best way to upgrade, is it ok to flash it over the old one for sure? Since i guess more people will want to upgrade it every once in a while we might also want to add that to the TS/FP?
Today i want downgrade form Xbsall 4.0.4 to install CM10.
So first i wipe my Rom, do a Factory Reset and flash the "BOOTV21E_AP" via Smartflash from the Resurrection Guide
I only do it with Smartflash because the Lg Flashtool no longer works for me....
Now I'm on Stock Gingerbread 2.3.5 but i can't root the phone via Megatrone....
I get an error that says "failed inufficented storage"
I have the same problem when i try to download something from the google playstore, in the store i get this error
"there is insufficient space on the device"
Anyone can help
Elil60 said:
Today i want downgrade form Xbsall 4.0.4 to install CM10.
So first i wipe my Rom, do a Factory Reset and flash the "BOOTV21E_AP" via Smartflash from the Resurrection Guide
I only do it with Smartflash because the Lg Flashtool no longer works for me....
Now I'm on Stock Gingerbread 2.3.5 but i can't root the phone via Megatrone....
I get an error that says "failed inufficented storage"
I have the same problem when i try to download something from the google playstore, in the store i get this error
"there is insufficient space on the device"
Anyone can help
Click to expand...
Click to collapse
Random attempt to be helpfull but: did you try formatting the internal storage? or a factory reset?
Nanax said:
Random attempt to be helpfull but: did you try formatting the internal storage? or a factory reset?
Click to expand...
Click to collapse
Before i downgrade i do a factory Reset and i erase the internal store in the System Settings from the Stock Rom.
But the phone says everytime "not enough space free, clean up your data and try it again"
Elil60 said:
Before i downgrade i do a factory Reset and i erase the internal store in the System Settings from the Stock Rom.
But the phone says everytime "not enough space free, clean up your data and try it again"
Click to expand...
Click to collapse
I always get this after restoring stock. The trick is to factory reset the device again after restoring stock Rom. Just restart into recovery (shutdown, hold volume down + 3D button, start phone) and do a factory reset.
Sent from my GT-N8013 using xda app-developers app
Elil60 said:
Before i downgrade i do a factory Reset and i erase the internal store in the System Settings from the Stock Rom.
But the phone says everytime "not enough space free, clean up your data and try it again"
Click to expand...
Click to collapse
See FP's reply, and while you are at it: http://forum.xda-developers.com/showthread.php?t=2037287
Just this part of the 5th step:
"
type fastboot flash u-boot u-boot.img
fastboot flash x-loader x-loader.img
..
fastboot reboot
"
This ensures some other remainders from your ICS flash are removed aswell (this is not directly related to your space problem, but does enhance the chance of runnig CM 10 in the end)
FPtje said:
I always get this after restoring stock. The trick is to factory reset the device again after restoring stock Rom. Just restart into recovery (shutdown, hold volume down + 3D button, start phone) and do a factory reset.
Sent from my GT-N8013 using xda app-developers app
Click to expand...
Click to collapse
I get to the Cwm but there i also get some errors
E:Can't open /cache/recovery/log
E:Cant't mount /cache/recovery/last_log
E:Can't open /cache/recovery/last_log
I can't even reboot the system via CWM....
Nanax said:
See FP's reply, and while you are at it: http://forum.xda-developers.com/showthread.php?t=2037287
Just this part of the 5th step:
"
type fastboot flash u-boot u-boot.img
fastboot flash x-loader x-loader.img
..
fastboot reboot
"
This ensures some other remainders from your ICS flash are removed aswell (this is not directly related to your space problem, but does enhance the chance of runnig CM 10 in the end)
Click to expand...
Click to collapse
The Problem is i can't get into the fastboot mode, the computer don't show Omap up....
Nanax said:
With all the new nightlies comming out, what would be the best way to upgrade, is it ok to flash it over the old one for sure? Since i guess more people will want to upgrade it every once in a while we might also want to add that to the TS/FP?
Click to expand...
Click to collapse
If you already have cm installed, you won't need to factory reset again when you want to flash a new version.
The best way to update cyanogenmod is to go to settings, about phone, cyanogenmod updates. Set the update types to include nighties. The updater will do all the work for you.
Sent from my GT-N8013 using xda app-developers app
Elil60 said:
Today i want downgrade form Xbsall 4.0.4 to install CM10.
So first i wipe my Rom, do a Factory Reset and flash the "BOOTV21E_AP" via Smartflash from the Resurrection Guide
I only do it with Smartflash because the Lg Flashtool no longer works for me....
Now I'm on Stock Gingerbread 2.3.5 but i can't root the phone via Megatrone....
I get an error that says "failed inufficented storage"
I have the same problem when i try to download something from the google playstore, in the store i get this error
"there is insufficient space on the device"
Anyone can help
Click to expand...
Click to collapse
Your apps present? can you get into settings?
Nanax said:
This graph thing is cool, maybe we should make something similar:
Did you flash ICS before? - Yes - Downgrade and replace the u-boot & loader - etc - etc
- No - Did wipes? (Try again) - Fixed permissions? - Did you try flashing a clean KDZ? (try again) - Did you search the thread? - Still no solution? Post a q!
------------
If i may add a question/suggestion:
With all the new nightlies comming out, what would be the best way to upgrade, is it ok to flash it over the old one for sure? Since i guess more people will want to upgrade it every once in a while we might also want to add that to the TS/FP?
Click to expand...
Click to collapse
did this all came from v21e no imei no signal...
wiped all twice and nothing... what do you suggest to do?
pthacker85 said:
did this all came from v21e no imei no signal...
wiped all twice and nothing... what do you suggest to do?
Click to expand...
Click to collapse
Some people are reporting that V21e did not work for them myself included have you tried another baseband?
no. i don't know how to flash baseband...

[Q] htc one S red exclaimation during update or recovery

OK i got a ONE S last night and its on android 4.0.3, there was an OTA update available so i downloaded it and installed it but during installation suddenly the green logo changes to a red triangle with exclamation. I have tried factory resetting and again installing but the problem persists. i can get in that boot-locker page and also when i click on recovery i get the same green logo which changes to red triangle. Phone is working fine, but i need to update to jelly bean. On the boot locker page, on the top its written locked, Hboot-1.13. I think the phone is not rooted everything is stock.
Sorry for my vocabulary.
Any help would be greatly appreciated, this is giving me a serious headache.
Rana747 said:
OK i got a ONE S last night and its on android 4.0.3, there was an OTA update available so i downloaded it and installed it but during installation suddenly the green logo changes to a red triangle with exclamation. I have tried factory resetting and again installing but the problem persists. i can get in that boot-locker page and also when i click on recovery i get the same green logo which changes to red triangle. Phone is working fine, but i need to update to jelly bean. On the boot locker page, on the top its written locked, Hboot-1.13. I think the phone is not rooted everything is stock.
Sorry for my vocabulary.
Any help would be greatly appreciated, this is giving me a serious headache.
Click to expand...
Click to collapse
I'm assuming you are in the US and on TMobile.
http://www.htc.com/us/support/news.aspx?p_id=463&p_name=htc-one-s-t-mobile
Scroll down to:
Manual system update instructions:
Follow the instructions to download HTC Sync Manager to your pc.
download the file at the bottom of the page. (download, in green font)
that is the Ruu.exe that you will run on your pc and will walk you through the update process.
It will delete all information from the device. (bye bye pictures, videos, music) save those to your pc before hand if your are able.
tivofool said:
I'm assuming you are in the US and on TMobile.
Scroll down to:
Manual system update instructions:
Follow the instructions to download HTC Sync Manager to your pc.
download the file at the bottom of the page. (download, in green font)
that is the Ruu.exe that you will run on your pc and will walk you through the update process.
It will delete all information from the device. (bye bye pictures, videos, music) save those to your pc before hand if your are able.
Click to expand...
Click to collapse
Sorry i should have mentioned that am not from US and i have the international version of one S.. now please dont tell me there is no hope for this version.. plus does ruu requires a rooted device?
Rana747 said:
Sorry i should have mentioned that am not from US and i have the international version of one S.. now please dont tell me there is no hope for this version.. plus does ruu requires a rooted device?
Click to expand...
Click to collapse
No, it doesn't require a rooted device.
If you go to HTC website does it offer you a similar manual update solution for you?
Since your phone is new, I am directing you to HTC website because that way you will not void your warrantee.
If you bought the phone from a local store I would go back there and show them what is happening. They will be able to correct the phone and if something goes wrong it is on them and not you.
If you bought it online, I would call support and have them try and help. Again that way you are able to return it if something is wrong.
Otherwise
http://www.androidruu.com/
you would need to know which version of the HTC One S you have (ville/ville C2)
And be able to match your CID to the correct RUU.exe
But I would not recommend that since your phone is brand new.
tivofool said:
No, it doesn't require a rooted device.
If you go to HTC website does it offer you a similar manual update solution for you?
Since your phone is new, I am directing you to HTC website because that way you will not void your warrantee.
If you bought the phone from a local store I would go back there and show them what is happening. They will be able to correct the phone and if something goes wrong it is on them and not you.
If you bought it online, I would call support and have them try and help. Again that way you are able to return it if something is wrong.
Otherwise
you would need to know which version of the HTC One S you have (ville/ville C2)
And be able to match your CID to the correct RUU.exe
But I would not recommend that since your phone is brand new.
Click to expand...
Click to collapse
I dont have any sort of warranty, purchased from a guy who does not even know what is android.
I just need jellybean. If u could explain this ruu method to me, am not a tech genious.
One more this, for instance i update the device by this ruu method, can i factory reset the device??
Thanks u have been helpful, i thought no one would even reply to this thread
Rana747 said:
I dont have any sort of warranty, purchased from a guy who does not even know what is android.
I just need jellybean. If u could explain this ruu method to me, am not a tech genious.
One more this, for instance i update the device by this ruu method, can i factory reset the device??
Thanks u have been helpful, i thought no one would even reply to this thread
Click to expand...
Click to collapse
Ok,
Like you did before, go to bootloader and tell me what you have there.
What CID is your phone?
I'm thinking you have a S4 version of this phone as you stated your hboot was 1.13
for example mine is different, but looks 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"
}
And yes, you will be able to factory reset it after running a ruu.exe
crocodiles riammiu
tivofool said:
Ok,
Like you did before, go to bootloader and tell me what you have there.
What CID is your phone?
I'm thinking you have a S4 version of this phone as you stated your hboot was 1.13
for example mine is different, but looks like this:
And yes, you will be able to factory reset it after running a ruu.exe
Click to expand...
Click to collapse
How to find cid? Yes my model is z520e.
Rana747 said:
How to find cid? Yes my model is z520e.
Click to expand...
Click to collapse
Holy Crap!
Where did you get that phone?
That phone is S-Off (security off)
SuperCid
People would pay extra $ for that.
So basically you can flash any RUU you want. Your phone isn't going to care.
What country are you in?
tivofool said:
Holy Crap!
Where did you get that phone?
That phone is S-Off (security off)
SuperCid
People would pay extra $ for that.
So basically you can flash any RUU you want. Your phone isn't going to care.
What country are you in?
Click to expand...
Click to collapse
I dont even know what is soff neiher did the seller. He probably has 2 more in stock
Am from Pakistan, got it for 230$.
Soo where to download this ruu program? And could u recommend a ruu file which updates me to jelly bean? And what about people saying flash .img file at the end, somethomg like this.
Rana747 said:
How to find cid? Yes my model is z520e.
Click to expand...
Click to collapse
Holy Crap!
Where did you get that phone?
That phone is S-Off (security off)
SuperCid
People would pay extra $ for that.
So basically you can flash any RUU you want. Your phone isn't going to care.
What country are you in?
http://www.androidruu.com/?developer=Ville
RUU_Ville_U_JB_45_S_HTC_Europe_3.16.401.8_Radio_1.11.50.05.28_10.27.50.08L_release_301814_signed_2_4.exe
Something like that one is a Jelly Bean and should have the languages for Europe
Basically you are wanting to download the file that end in EXE and not ZIP
where it start off with ruu ville u jb that will be a jellybean
ruu ville u ICS is a ice cream sandwich
So, to run the RUU, you need the drivers for your phone on your computer.
If you install HTC sync Manager from the HTC website it will install the drivers.
or
http://forum.xda-developers.com/showthread.php?t=2217396&highlight=htc+driver
if you only want to install the driver
from there once you have downloaded a RUU.exe
have your phone in bootloader mode
plug your phone into PC
it should say fastboot USB (see in my picture it says HBOOT if you press power button it will enter into fastboot mode)
On your PC, double click the RUU.exe file and it will open up a installation dialogue to walk you through the rest.
Easy Peasy
---------- Post added at 10:58 PM ---------- Previous post was at 10:50 PM ----------
Rana747 said:
I dont even know what is soff neiher did the seller. He probably has 2 more in stock
Am from Pakistan, got it for 230$.
Soo where to download this ruu program? And could u recommend a ruu file which updates me to jelly bean? And what about people saying flash .img file at the end, somethomg like this.
Click to expand...
Click to collapse
Yeah, if you are all about running the various Custom ROMs that people have developed here you will be using boot.img and recovery.img to install particular ROMs.
But you don't need to worry about that right now.
By the way, I am so impressed with all of the people who come to this site who speak more than one language. I realize that most people in the world do speak more than one language. But still, it is very impressive to me.
Hopefully that Europe ruu has a suitable language for you.
tivofool said:
Holy Crap!
Where did you get that phone?
That phone is S-Off (security off)
SuperCid
People would pay extra $ for that.
So basically you can flash any RUU you want. Your phone isn't going to care.
What country are you in?
RUU_Ville_U_JB_45_S_HTC_Europe_3.16.401.8_Radio_1.11.50.05.28_10.27.50.08L_release_301814_signed_2_4.exe
Something like that one is a Jelly Bean and should have the languages for Europe
Basically you are wanting to download the file that end in EXE and not ZIP
where it start off with ruu ville u jb that will be a jellybean
ruu ville u ICS is a ice cream sandwich
So, to run the RUU, you need the drivers for your phone on your computer.
If you install HTC sync Manager from the HTC website it will install the drivers.
or
if you only want to install the driver
from there once you have downloaded a RUU.exe
have your phone in bootloader mode
plug your phone into PC
it should say fastboot USB (see in my picture it says HBOOT if you press power button it will enter into fastboot mode)
On your PC, double click the RUU.exe file and it will open up a installation dialogue to walk you through the rest.
Easy Peasy
Click to expand...
Click to collapse
ok i downloaded the ruu file exactly the same one that u mentioned above, downloading took about 40min. I got into fastboot USB mode.
Then i clicked the ruu setup exe file, error shows up (i knew it will not be easy peasy for me). error says "please make sure you have finished any previous setup and closed other applications. If error still persists contact your vendor,
error details
Error Code: -5001 : 0x80070002
Error Information:
>SetupNew\setup.cpp (142)
PAPP:
PVENDOR:
PGUID:
$
 @Windows 7 / Server 2008 R2 Service Pack 0 (9200)
IE Version: 9.10.9200.16721
btw am running windows 8
Rana747 said:
ok i downloaded the ruu file exactly the same one that u mentioned above, downloading took about 40min. I got into fastboot USB mode.
Then i clicked the ruu setup exe file, error shows up (i knew it will not be easy peasy for me). error says "please make sure you have finished any previous setup and closed other applications. If error still persists contact your vendor,
error details
Error Code: -5001 : 0x80070002
Error Information:
>SetupNew\setup.cpp (142)
PAPP:
PVENDOR:
PGUID:
$
@Windows 7 / Server 2008 R2 Service Pack 0 (9200)
IE Version: 9.10.9200.16721
btw am running windows 8
Click to expand...
Click to collapse
Yes, "Murphy's Law: if anything can go wrong, it will"
A quick google of that error code on windows 8 does show a lot of frustrated people.
I'm kind of out of ideas, maybe someone else can help.
tivofool said:
Yes, "Murphy's Law: if anything can go wrong, it will"
A quick google of that error code on windows 8 does show a lot of frustrated people.
I'm kind of out of ideas, maybe someone else can help.
Click to expand...
Click to collapse
sorry am dragging u, i downloaded the file again and got it working everything was going perfect and at the end when it was updating, error came that "this is not the correct rom utilty, select the correct ruu for your device and try again" error was something like this.
help, pleasee
Rana747 said:
sorry am dragging u, i downloaded the file again and got it working everything was going perfect and at the end when it was updating, error came that "this is not the correct rom utilty, select the correct ruu for your device and try again" error was something like this.
help, pleasee
Click to expand...
Click to collapse
Well a lot of people have read this and I suspect someone smarter than me will read this and have an answer. I honestly don't know why this isn't working.
Have patience someone will help.
going from image 1.78.401.2 to 3.16.401.8. This error comes.
anyone??
Rana747 said:
going from image 1.78.401.2 to 3.16.401.8. This error comes.
anyone??
Click to expand...
Click to collapse
Hey, I know it's been a few weeks and I don't know if you gave up or solved the problem.
I was mistaken about S-off devices easily will run any RUU.
You need to match the CID to the RUU you are going to flash. Which is easy to do when you are S-off
Here is a guide
http://forum.xda-developers.com/showthread.php?t=2501542
tivofool said:
Hey, I know it's been a few weeks and I don't know if you gave up or solved the problem.
I was mistaken about S-off devices easily will run any RUU.
You need to match the CID to the RUU you are going to flash. Which is easy to do when you are S-off
Here is a guide
http://forum.xda-developers.com/showthread.php?t=2501542
Click to expand...
Click to collapse
Yea i solved it by matching the cid then restoring through RUU. Then everything was working fine, so i updated through OTA and now am on 4.1.1.
Thanks for ur help
ps
i sold one S , now using note 3

xt926 stuck at Motorola Dual Core logo

I've not dealt with Moto's before, All my previous phone's have typically been Samsung, Nexus, and currently my LG G3.
My mom has a Verizon XT926 that from what it sounds like started an OTA update and is now stuck at the red circle, white M logo screen, that says "Dual Core"
I would call myself pretty android savvy, and have tried everything I've found so far without any luck.
Here is the current situation:
I can get into recovery, and fastboot
I have tried using RSD Lite to flash multiple versions of the stock ROM without any success
I have tried using HouseOfMoto method, also without any success
I read through SamuriHL's thread here and at droidrzr.com and tried every possible suggestion without any success
Here is a screenshot of RSD Lite
{
"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"
}
Also, after attempting an RSD Lite flash, the error message on the phone is:
failed to read signature for partition aboot
downgraded security version
update gpt_main version failed
preflash validation failed for GPT
I thought the above error meant that I was trying to downgrade, but I have even attempted to flash the latest image of VZW_XT926_4.4.2-KDA20.62-10.1_CFC_1FF.xml and it still fails.
From a few of SamuriHL's posts, i get the feeling this phone has a "corrupt partition table" issue that I don't believe anyone has been able to find a solution for.
Any help would be appreciated, thanks guys!
.10 is not the most current OTA, that's why you're getting the downgrade error. Look in the general section for the thread with the .15 update.
Sent from my HTC6525LVW using Tapatalk
RikRong said:
.10 is not the most current OTA, that's why you're getting the downgrade error. Look in the general section for the thread with the .15 update.
Sent from my HTC6525LVW using Tapatalk
Click to expand...
Click to collapse
Same deal, phone returns "fail"
This time it doesn't specify that its a downgraded security version, it just flat out fails. Pretty sure the OTA fried this thing. Oh well.....
Namtaru said:
Same deal, phone returns "fail"
This time it doesn't specify that its a downgraded security version, it just flat out fails. Pretty sure the OTA fried this thing. Oh well.....
Click to expand...
Click to collapse
you apparently missed some key points in your research, obvious just by looking at your screenshot.
you need to completely remove the "tz" and "gpt" lines from the xml file, then flash again.
your having a pretty basic issue, thats fairly easily fixed.
.... and yes, if it comes to it, i can easily guide you to fixing the partition table, but that doesnt appear necessary at this point.
bweN diorD said:
you apparently missed some key points in your research, obvious just by looking at your screenshot.
you need to completely remove the "tz" and "gpt" lines from the xml file, then flash again.
your having a pretty basic issue, thats fairly easily fixed.
.... and yes, if it comes to it, i can easily guide you to fixing the partition table, but that doesnt appear necessary at this point.
Click to expand...
Click to collapse
Would you be able to point me to the thread where this is talked about?
I found many references to removing the lines that have getvar in them, which I have also tried, but none referencing your suggestion.
Thanks!
Namtaru said:
Would you be able to point me to the thread where this is talked about?
I found many references to removing the lines that have getvar in them, which I have also tried, but none referencing your suggestion.
Thanks!
Click to expand...
Click to collapse
it has been said by myself and others easily a hundred times, i would rather not dig through threads looking for it.
when we post certain tools and firmwares, we just remove those lines before you get them to avoid this issue. but firmwares posted more for general use will still have those lines, as they are sometimes needed.
if you were to type "gpt error rsd android" into google, im sure there would be many post in threads suggesting the removal of certain lines from the xml as i have suggested.
hope that helps..
edit, added some search terms, just gpt error was too vague.
bweN diorD said:
it has been said by myself and others easily a hundred times, i would rather not dig through threads looking for it.
when we post certain tools and firmwares, we just remove those lines before you get them to avoid this issue. but firmwares posted more for general use will still have those lines, as they are sometimes needed.
if you were to type "gpt error rsd android" into google, im sure there would be many post in threads suggesting the removal of certain lines from the xml as i have suggested.
hope that helps..
edit, added some search terms, just gpt error was too vague.
Click to expand...
Click to collapse
Still doesn't matter, fails again.
The phone doesn't report anything on screen, the last line is still just "usb connected"
edit: when i try to flash .10 instead of .15, it still fails, but the phone returns a single line of: "failed to read signature for partition aboot"
Namtaru said:
Still doesn't matter, fails again.
The phone doesn't report anything on screen, the last line is still just "usb connected"
edit: when i try to flash .10 instead of .15, it still fails, but the phone returns a single line of: "failed to read signature for partition aboot"
Click to expand...
Click to collapse
rsd really blows some times.
run this in fastboot.
-extract the rar
-run the windows batch file and follow the directions
-profit!!
bweN diorD said:
rsd really blows some times.
run this in fastboot.
-extract the rar
-run the windows batch file and follow the directions
-profit!!
Click to expand...
Click to collapse
Already tried that, and DROID_RAZR_HD_Utility_1.4gpt KK, and DROID_RAZR_HD_Utility_1.3.gpt fix.
I'm pretty sure the phone is beyond repair. It just crazy to me because I've been using android since just after the Dream, and of all the horrible things I've done to them, I've never bricked one. Yet a simple OTA from Verizon on a bone stock Rzr HD bricks it, lol.
Namtaru said:
Already tried that, and DROID_RAZR_HD_Utility_1.4gpt KK, and DROID_RAZR_HD_Utility_1.3.gpt fix.
I'm pretty sure the phone is beyond repair. It just crazy to me because I've been using android since just after the Dream, and of all the horrible things I've done to them, I've never bricked one. Yet a simple OTA from Verizon on a bone stock Rzr HD bricks it, lol.
Click to expand...
Click to collapse
unless you grabbed that one from a thread, then you havent tried it. its not the same as either of those you mentioned, its newer.
it may be bricked, you will know after you flash that file. there is nothing else im aware of to try.
if everything says it failed when using the utility, then its toast.
bweN diorD said:
unless you grabbed that one from a thread, then you havent tried it. its not the same as either of those you mentioned, its newer.
it may be bricked, you will know after you flash that file. there is nothing else im aware of to try.
if everything says it failed when using the utility, then its toast.
Click to expand...
Click to collapse
Sorry I wasn't clear. I already tried the one you posted. Literally the exact same link you posted. I ALSO tried the two older versions of the fix you posted.
Namtaru said:
Sorry I wasn't clear. I already tried the one you posted. Literally the exact same link you posted. I ALSO tried the two older versions of the fix you posted.
Click to expand...
Click to collapse
that sux, its done then.
i have seen this a few times before, but its pretty rare.
bweN diorD said:
that sux, its done then.
i have seen this a few times before, but its pretty rare.
Click to expand...
Click to collapse
Thanks for the suggestions. Anyone want a bricked razr hd? Lol
I can help u contact me
zainbintariq12345 said:
I can help u contact me
Click to expand...
Click to collapse
Why not just post it here so everyone can benefit?
Your either f.o.s. or charging money, otherwise there is no reason for a private fix.
Sent from my G3 Rockin Cyanogen
same thing here
I have an xt926 doing the same thing. I dont care if i recover the phone or not, but i was wondering if there was a way to make the computer recognize the memory so i can pull the pictures off it? even better, pull the contacts off it, if thats possible? thanks in advance!
me pasa igual amigo tengo un xt926 y el progrma no me reconoce el cel alguien sabe como hacer
Namtaru said:
Thanks for the suggestions. Anyone want a bricked razr hd? Lol
Click to expand...
Click to collapse
What is it doing can you get to the red motorola logo. If you can then try and plug in charger and while connected to charger, when it gets to the red M logo hold power and volume up and volume down at the same time. when screen goes off release right away and then as quick as you can hold the same three buttons untill you get to fastboot mode and then let go. if it gets to fastboot mode then it might just be a bad battery. If it does not then it is bricked and you would need a fastboot cable to get into fatboot mode and flash stock firmware and bring back the device to life.
xt926 Stuck at Droid Logo
ive tried a hard reset and same thing just stuck at boot when i turn it on it makes noise and starts to fired up and then it just sits at the droid sign until battery dies or i hold volume up or down and it powers off ??? i cant get to the recovery menu and some other menu the on where you select recovery but thats it ??? somone please help thanks
Namtaru said:
I've not dealt with Moto's before, All my previous phone's have typically been Samsung, Nexus, and currently my LG G3.
My mom has a Verizon XT926 that from what it sounds like started an OTA update and is now stuck at the red circle, white M logo screen, that says "Dual Core"
I would call myself pretty android savvy, and have tried everything I've found so far without any luck.
Here is the current situation:
I can get into recovery, and fastboot
I have tried using RSD Lite to flash multiple versions of the stock ROM without any success
I have tried using HouseOfMoto method, also without any success
I read through SamuriHL's thread here and at droidrzr.com and tried every possible suggestion without any success
Here is a screenshot of RSD Lite
Also, after attempting an RSD Lite flash, the error message on the phone is:
failed to read signature for partition aboot
downgraded security version
update gpt_main version failed
preflash validation failed for GPT
I thought the above error meant that I was trying to downgrade, but I have even attempted to flash the latest image of VZW_XT926_4.4.2-KDA20.62-10.1_CFC_1FF.xml and it still fails.
From a few of SamuriHL's posts, i get the feeling this phone has a "corrupt partition table" issue that I don't believe anyone has been able to find a solution for.
Any help would be appreciated, thanks guys!
Click to expand...
Click to collapse
As long as you can to fastboot you can get his device working here are t correct drivers for your device. Install these drivers
http://forum.xda-developers.com/attachment.php?attachmentid=3187938&d=1425146663
and here is the correct firmware https://www.androidfilehost.com/?fid=24269982087011676
Install the drivers for your device then try flashing the correct firmware i gave you drivers for 64 bit windows system if you have 32 instead let me know and ill give you link to those drivers
---------- Post added at 02:04 AM ---------- Previous post was at 02:00 AM ----------
sdwyz74 said:
ive tried a hard reset and same thing just stuck at boot when i turn it on it makes noise and starts to fired up and then it just sits at the droid sign until battery dies or i hold volume up or down and it powers off ??? i cant get to the recovery menu and some other menu the on where you select recovery but thats it ??? somone please help thanks
Click to expand...
Click to collapse
You might have a bad battery.

6.0.1 OTA for stock rooted system

Hi, sorry if this is a stupid question, but I just noticed Sprint pushed an OTA for 6.0.1 to my stock rooted device (S-on) and I'm just trying to figure out what the best way to get this OTA is going to be. I'm assuming I shouldn't download and install the OTA as-is due to the TWRP recovery and root.
After looking around a bit, it seems like the only option available is to use a stock 6.0.0 RUU file in the bootloader and basically reset the entire device back to factory settings (losing all apps and data in the process presumably), installing the OTA, then re-flashing TWRP and re-rooting.
I guess what I'm asking is - 1. is this the correct way to go about doing this? and 2. is there any better alternative perhaps that doesn't involve losing my data?
Thanks in advance guys.
Been googling around for the last few days and scouring this board for just as long and still haven't come to a definitive conclusion. From what little I've seen the documentation on this seems kind of spotty and I'm just wondering which direction to head in. Any help on this would be much appreciated.
Safest way.. ruu back to stock everything take ota and re root/download apps etc...
Thanks for the reply, man.. Thats kind of what I had gathered pouring over all these articles and board posts. I went ahead and RUU'd back to 1.10.651.1 for sprint.. Literally just moments ago though I downloaded the OTA and hit install and got presented with an error screen during the update. Phone rebooted back into the system normally, and I went to check the version # only to see it unchanged, along with a prompt to install the OTA for 1.57.651.1 again.
Any idea why this might've happened or how to remedy it?
{
"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"
}
Wonders_Never_Cease said:
Safest way.. ruu back to stock everything take ota and re root/download apps etc...
Click to expand...
Click to collapse
What was the error? You may have to relock bootloader to accept the ota...unsure of how they are with their device,GSM device I have doesnt need relocked...(S-Off as well so)
---------- Post added at 12:50 AM ---------- Previous post was at 12:47 AM ----------
Also the 1.57.651.1 RUU is available... Why not use it?
http://dl3.htc.com/application/RUU_HIA_AERO_WHL_M60_SENSE7GP_SPCS_MR_Sprint_WWE_1.57.651.1_R2.exe
Thats the weird part, it didnt give an error message, just that icon in the image I added to my last post. forelock the bootloader would be kind of surprising... Might give that a try in the morning after I find out if it can be re-unlocked.
EDIT: Ohhh I just saw your last edit, i didnt see that before, i'll use that then. Thank you!!!
Wonders_Never_Cease said:
What was the error? You may have to relock bootloader to accept the ota...unsure of how they are with their device,GSM device I have doesnt need relocked...(S-Off as well so)
---------- Post added at 12:50 AM ---------- Previous post was at 12:47 AM ----------
Also the 1.57.651.1 RUU is available... Why not use it?
http://dl3.htc.com/application/RUU_HIA_AERO_WHL_M60_SENSE7GP_SPCS_MR_Sprint_WWE_1.57.651.1_R2.exe
Click to expand...
Click to collapse
Download the .651 ruu,reboot phone into download mode and run it... Should be up to date after that for a bit id think
---------- Post added at 12:58 AM ---------- Previous post was at 12:53 AM ----------
How did you unlock it to begin with? HTC Dev site? If so then should be able to use the same unlocktoken.bin from before... Or can resubmit and get another one...
txag2011 said:
Thats the weird part, it didnt give an error message, just that icon in the image I added to my last post. forelock the bootloader would be kind of surprising... Might give that a try in the morning after I find out if it can be re-unlocked.
EDIT: Ohhh I just saw your last edit, i didnt see that before, i'll use that then. Thank you!!!
Click to expand...
Click to collapse
Thats precisely what I did. Unlocked it with the HTC Dev Token. I gotta admit, I was pretty surprised that I had an OTA so soon after getting the phone and unlocking / rooting it. Just when I had everything set up how I liked it
I just finished flashing the 651 RUU and its just optimizing the apps now, but looks like it should do it!
Wonders_Never_Cease said:
Download the .651 ruu,reboot phone into download mode and run it... Should be up to date after that for a bit id think
---------- Post added at 12:58 AM ---------- Previous post was at 12:53 AM ----------
How did you unlock it to begin with? HTC Dev site? If so then should be able to use the same unlocktoken.bin from before... Or can resubmit and get another one...
Click to expand...
Click to collapse
Cool glad got it sorted...
txag2011 said:
Thats precisely what I did. Unlocked it with the HTC Dev Token. I gotta admit, I was pretty surprised that I had an OTA so soon after getting the phone and unlocking / rooting it. Just when I had everything set up how I liked it
I just finished flashing the 651 RUU and its just optimizing the apps now, but looks like it should do it!
Click to expand...
Click to collapse
Actually.. I've hit another wall now tryign to achieve root with this. I've got TWRP back on the device, and I'm using WinDroid Toolkit to flash SuperSU to it. It'll show that it's pushing it, then drop into recovery and naturally ask for me to wipe the /data partition since it's encrypted, before proceeding to install the supersu.zip package.
The only problem is, there doesn't appear to be any supersu.zip anywhere on the device once it gets into recovery, either before or after the data wipe. Any idea where it's going?
Wonders_Never_Cease said:
Cool glad got it sorted...
Click to expand...
Click to collapse
First thing ya need to do is read how to install adb and fastboot and get away from toolkits... Download 2.67 from this thread...copy to device flash through twrp...
http://forum.xda-developers.com/showpost.php?p=64161125&postcount=3
txag2011 said:
Actually.. I've hit another wall now tryign to achieve root with this. I've got TWRP back on the device, and I'm using WinDroid Toolkit to flash SuperSU to it. It'll show that it's pushing it, then drop into recovery and naturally ask for me to wipe the /data partition since it's encrypted, before proceeding to install the supersu.zip package.
The only problem is, there doesn't appear to be any supersu.zip anywhere on the device once it gets into recovery, either before or after the data wipe. Any idea where it's going?
Click to expand...
Click to collapse
And didnt mean that in a snotty,sarcastic way... Those tools sometimes cause issues that could be avoided is all I was getting at...
I want to join this conversation.
The A9 of my mom got is a Vodaphone UK version (cid: vodap001) and got the update message to version 1.62.161.2
I've rooted the device and installed TWRP.
So now i relocked the bootloader, installed the firmware.zip that was inside the OTA Download which i've copied from Update-App Path.
If i now want to manualy update the OTA-zip with fastboot in download-mode, i got Error 7.
If i want to update with original OTA updater Up, it stops at 25% with the red cross.
So what should i do now?
There is noch previous RUU-file for this firmware-version thats why i've already updated to the recovery from this OTA-update.
I hope someone can help with it.
Thanks,
Bond
txag2011 said:
Actually.. I've hit another wall now tryign to achieve root with this. I've got TWRP back on the device, and I'm using WinDroid Toolkit to flash SuperSU to it. It'll show that it's pushing it, then drop into recovery and naturally ask for me to wipe the /data partition since it's encrypted, before proceeding to install the supersu.zip package.
The only problem is, there doesn't appear to be any supersu.zip anywhere on the device once it gets into recovery, either before or after the data wipe. Any idea where it's going?
Click to expand...
Click to collapse
I have to agree with Wonders_never_cease about the toolkits. I have used many different ones and they are great from a few things but not all things go right using them unlike adb/fastboot. You should have better results from using adb/fastboot here.
That being said.....it would be easier to achieve root by simply going to full stock using RUU or system/boot.img in fastboot, flashing TWRP, format data, reboot into TWRP, flash supersu 2.74 from your SD card either by itself to obtain normal root or follow steps here http://forum.xda-developers.com/showpost.php?p=63197935&postcount=2 for systemless root. it's that simple...or at least was for me. I never could get pushing supersu through adb right or to work really.
---------- Post added at 10:12 AM ---------- Previous post was at 09:59 AM ----------
Bond246 said:
I want to join this conversation.
The A9 of my mom got is a Vodaphone UK version (cid: vodap001) and got the update message to version 1.62.161.2
I've rooted the device and installed TWRP.
So now i relocked the bootloader, installed the firmware.zip that was inside the OTA Download which i've copied from Update-App Path.
If i now want to manualy update the OTA-zip with fastboot in download-mode, i got Error 7.
If i want to update with original OTA updater Up, it stops at 25% with the red cross.
So what should i do now?
There is noch previous RUU-file for this firmware-version thats why i've already updated to the recovery from this OTA-update.
I hope someone can help with it.
Thanks,
Bond
Click to expand...
Click to collapse
You will not be able to apply the OTA update if you are not completely stock including being with stock recovery. Having your bootloader unlocked will not be an issue so no need to relock it like you did. Use a system/boot/recovery.img to restore stock completely, or whatever RUU need. Then accept the OTA or flash it manually, then reroot. Thats really the only way you will be able to get that to work.....
mcbright80 said:
You will not be able to apply the OTA update if you are not completely stock including being with stock recovery. Having your bootloader unlocked will not be an issue so no need to relock it like you did. Use a system/boot/recovery.img to restore stock completely, or whatever RUU need. Then accept the OTA or flash it manually, then reroot. Thats really the only way you will be able to get that to work.....
Click to expand...
Click to collapse
Thanks for your answer.
But how to get complete stock without nandroid or RUU?
The Firmware.zip of the 1.62.161.2 OTA Update was installed without Errors. But as i already mentioned i Need stock System/boot-files of my last Version (1.62.161.1) to get this partitions to stock. And they are not available anywhere.
Bond246 said:
Thanks for your answer.
But how to get complete stock without nandroid or RUU?
The Firmware.zip of the 1.62.161.2 OTA Update was installed without Errors. But as i already mentioned i Need stock System/boot-files of my last Version (1.62.161.1) to get this partitions to stock. And they are not available anywhere.
Click to expand...
Click to collapse
Ah so sorry, it was 4 am when i was replying so i missed that part on it installing correct, or confused it with the other question i was replying to at that same time haha......anyhoo....i looked for you as well and nothing was found on my end as well so I think you may be in the exact situation i was in when i bought the sprint variant of the A9. HTC has faults like all companies but the one that really pisses me off is their lack of proper support on ALL variants especially concerning firmware. The phone was released and i found NO RUU on their site or anywhere online and of course not many people had my specific variant which meant no one on here or anywhere had the means to get me the stock firmware i too needed to restore my phone.
The ONLY reason anyone here, who has SPRINT US VERSION, is able to then and NOW get the RUU on the HTC website is directly due to my incessant badgering and yelling at HTC damn near daily about having a handset on the market for sale but no firmware for it in case of tech service needs. You may have to do the same thing sadly.
I assume you have checked htc UK site for the rom downloads......contact their tech support and see whats up. Till then, like i had to when the sprint version came out....you'll have to just keep checking back on here and anywhere online for someone else who may post what you need or some other kind of solution.
Thanks mcbright80,
as you already said, HTC resists and says RUUs are only available in the US. I'm excited on their reaction that there are still lower RUU-versions of my UK-edition.
It is an annoying mess with all these different versions for tons of carriers, countrys and so on.

Categories

Resources