Related
I've been dealing with SOD (Sleep Of Death) problem since official OTA ICS update. On HC everything (except calendar) was fine, but after official ICS update I was having SOD almost every sleep longer then few minutes.
Tried WiFi/sync tricks etc.
What helped ? Well..
1. hardware reset (Vol+ / Pwr / RotateLock)
2. factory reset (from Settings Menu)
3. full update via sd card (Vol- / Pwr)
OFFICIAL ROM: 7.014.16 - 041.213.01 - COM_GEN1 (ICS)
(Acer_A500_7.014.16_041.213.01_COM_GEN1_1336732099520_45282ff4.zip)
and once again:
4. hardware reset (Vol+ / Pwr / RotateLock)
5. factory reset (from Settings Menu)
...I know that hardware & facory reset are pretty much the same, but...It helped...
mayekk said:
I've been dealing with SOD (Sleep Of Death) problem since official OTA ICS update. On HC everything (except calendar) was fine, but after official ICS update I was having SOD almost every sleep longer then few minutes.
Tried WiFi/sync tricks etc.
What helped ? Well..
1. hardware reset (Vol+ / Pwr / RotateLock)
2. factory reset (from Settings Menu)
3. full update via sd card (Vol- / Pwr)
OFFICIAL ROM: 7.014.16 - 041.213.01 - COM_GEN1 (ICS)
(Acer_A500_7.014.16_041.213.01_COM_GEN1_1336732099520_45282ff4.zip)
and once again:
4. hardware reset (Vol+ / Pwr / RotateLock)
5. factory reset (from Settings Menu)
...I know that hardware & facory reset are pretty much the same, but...It helped...
Click to expand...
Click to collapse
Does t means I have to re-install all applications?
cscs3 said:
Does t means I have to re-install all applications?
Click to expand...
Click to collapse
yes, but you can use titanium backup or similar app to do it for you...
I have a A501 and want to get rid of this sod problem. so i took the last "Ice Cream Sandwich 4.0.3 (LEAK)" Rom from http://forum.xda-developers.com/showthread.php?t=1816560 and tried to install the update.zip file from the sd card. When i get to the recovery it starts but crashes after a few seconds. Do i habe to install a different recovery or unlock my bootloader? I'm a little bit confused...can somebody give me a short hint? Thx.
captainn said:
I have a A501 and want to get rid of this sod problem. so i took the last "Ice Cream Sandwich 4.0.3 (LEAK)" Rom from http://forum.xda-developers.com/showthread.php?t=1816560 and tried to install the update.zip file from the sd card. When i get to the recovery it starts but crashes after a few seconds. Do i habe to install a different recovery or unlock my bootloader? I'm a little bit confused...can somebody give me a short hint? Thx.
Click to expand...
Click to collapse
This is probably because of a couple of reasons.
1. You didn't do the incremental update. The available update files are incremental patch files, which means you have to have the others installed before you install the latest. Or at least part 1 and 2 of the original leak.
2. You didn't decrypt the file and remove the "update.zip". Generally, you can't just rename these update files to "update.zip". So the latest OTA you took, you should decrypt it "if it needs it", open in 7zip or Winzip and pull the update.zip file and copy that to your EXT SD card.
The final Official release build, was build .021. So if you still get SOD on .021, then chances are you have one of the later revision tablets, and may have to wait a long time until Acer releases another update, as the later revisions only account for a very small percentage.
Or, you can install the unlocked bootloader, and try one of the newer kernels we have.
MD
Moscow Desire said:
This is probably because of a couple of reasons.
1. You didn't do the incremental update. The available update files are incremental patch files, which means you have to have the others installed before you install the latest. Or at least part 1 and 2 of the original leak.
2. You didn't decrypt the file and remove the "update.zip". Generally, you can't just rename these update files to "update.zip". So the latest OTA you took, you should decrypt it "if it needs it", open in 7zip or Winzip and pull the update.zip file and copy that to your EXT SD card.
The final Official release build, was build .021. So if you still get SOD on .021, then chances are you have one of the later revision tablets, and may have to wait a long time until Acer releases another update, as the later revisions only account for a very small percentage.
Or, you can install the unlocked bootloader, and try one of the newer kernels we have.
MD
Click to expand...
Click to collapse
Thanks for your replay. So what i did was to install all available OTA updates. Then i downloaded the full package Ice Cream Sandwich 4.0.3 (LEAK) from the site above, extracted the update.zip from this archive and put it on the external sd card. i think that is all i have to do. And my current build number is Acer_AV041_A501_1.021.00_EMEA_DE...so don't know exactly if "[LEAK]Acer A501 ICS (COM_GEN1). Build number 041.126.01" is the same version.
And i tried to unlock my bootloader but the next funny thing is that i tried that Afterota-Tool, but it stucks at 3/4 "Flashing recovery...".
I don't want to loose my 3G-Feature and i saw that nearly all roms are only for A500. Which kernel and rom would you recommend for me?
Looking forward for your replay. Thx a lot!
captainn said:
Thanks for your replay. So what i did was to install all available OTA updates. Then i downloaded the full package Ice Cream Sandwich 4.0.3 (LEAK) from the site above, extracted the update.zip from this archive and put it on the external sd card. i think that is all i have to do. And my current build number is Acer_AV041_A501_1.021.00_EMEA_DE...so don't know exactly if "[LEAK]Acer A501 ICS (COM_GEN1). Build number 041.126.01" is the same version.
And i tried to unlock my bootloader but the next funny thing is that i tried that Afterota-Tool, but it stucks at 3/4 "Flashing recovery...".
I don't want to loose my 3G-Feature and i saw that nearly all roms are only for A500. Which kernel and rom would you recommend for me?
Looking forward for your replay. Thx a lot!
Click to expand...
Click to collapse
You current build is cooked my friend. Unless you want Acer repair.
Most of all OTA ICS Updates are Com Gen 1 now. Not sure what acer had in mind. But I believe it has duetch or danish language.
You have to use a 501 update if you want to use 3g and GPS.
My question, were you successful in booting to your system after installing the updates correctly? That is my primary question. If so, make sure you have USB debugging turned on.
But I need to know exactly what your tablet is in now before going further. Does it boot into the OS after running the updates?
MD
Moscow Desire said:
You current build is cooked my friend. Unless you want Acer repair.
Most of all OTA ICS Updates are Com Gen 1 now. Not sure what acer had in mind. But I believe it has duetch or danish language.
You have to use a 501 update if you want to use 3g and GPS.
My question, were you successful in booting to your system after installing the updates correctly? That is my primary question. If so, make sure you have USB debugging turned on.
But I need to know exactly what your tablet is in now before going further. Does it boot into the OS after running the updates?
MD
Click to expand...
Click to collapse
I don't know exactly which updates you are talking about. I installed all the available ota updates and the tablet booted correctly after this. If you mean any other update via sd-card i can only tell you that i was not able to install one of them. what do you mean with "cooked"? sorry for stupid questions
My USB debugging ist turned on, firewall and uac off.
Thx.
captainn said:
I don't know exactly which updates you are talking about. I installed all the available ota updates and the tablet booted correctly after this. If you mean any other update via sd-card i can only tell you that i was not able to install one of them. what do you mean with "cooked"? sorry for stupid questions
My USB debugging ist turned on, firewall and uac off.
Thx.
Click to expand...
Click to collapse
The only stupid question, is the one that doesn't get asked
What is the current version you are on? (settings/about tablet) The current build should be .021
MD
Moscow Desire said:
The only stupid question, is the one that doesn't get asked
What is the current version you are on? (settings/about tablet) The current build should be .021
MD
Click to expand...
Click to collapse
Android 4.0.3
Kernel 2.6.39.4+
Image Acer_AV041_A501_RV20RC05_EMEA
Build Acer_AV041_A501_1.021.00_EMEA_DE
P/N FM.S14A0.02A
Is it all you need?
captainn said:
Android 4.0.3
Kernel 2.6.39.4+
Image Acer_AV041_A501_RV20RC05_EMEA
Build Acer_AV041_A501_1.021.00_EMEA_DE
P/N FM.S14A0.02A
Is it all you need?
Click to expand...
Click to collapse
Yes, you have build .021 But I am surprised it's not WW_Com_Gen_1
This is the latest Acer build. So stay with it.
Ok, info for you, I am currently working with kernel dev's to maybe get something better as far as kernels, that may help with your SOD if you still have it.
For right now, let us work on things. This may take a few days.
As with Unlocked Bootloader and CWM recovery.
Here is what you should do.
GET YOUR UID NUMBER and write it down.
1. Make sure your Acer drivers are installed.
2. Using After OTA, only install the Patched Bootloader.
3. If you already have the patched bootloader installed (you see Skirlax_CZ bootloader text when you boot),
Did it install the patched bootloader?
MD
Moscow Desire said:
Yes, you have build .021 But I am surprised it's not WW_Com_Gen_1
This is the latest Acer build. So stay with it.
Ok, info for you, I am currently working with kernel dev's to maybe get something better as far as kernels, that may help with your SOD if you still have it.
For right now, let us work on things. This may take a few days.
As with Unlocked Bootloader and CWM recovery.
Here is what you should do.
GET YOUR UID NUMBER and write it down.
1. Make sure your Acer drivers are installed.
2. Using After OTA, only install the Patched Bootloader.
3. If you already have the patched bootloader installed (you see Skirlax_CZ bootloader text when you boot),
Did it install the patched bootloader?
MD
Click to expand...
Click to collapse
So in Afterota i open the tab advanced and there i can choose "browse for custom bootloader" and i can choose between different binary files. I think "bl_ics_ac_v8.bin" or "bl_ics_pb_v8.bin" should be right. What's the difference, what's the right one?
captainn said:
So in Afterota i open the tab advanced and there i can choose "browse for custom bootloader" and i can choose between different binary files. I think "bl_ics_ac_v8.bin" or "bl_ics_pb_v8.bin" should be right. What's the difference, what's the right one?
Click to expand...
Click to collapse
Well, I did things the old fashioned way.
If I am to guess. the first one is CWM recovery included, and the second is Public Recovery included. I never used this tool
I would choose door number 1
BTW, there are other methods to install these things. But let's see what happens. Personally, I don't use these all in 1 tools. Got too many of them in the forums. But, let's see what happens.
If not successful, we'll use My method. And you will learn something in the process.
MD
Moscow Desire said:
Well, I did things the old fashioned way.
If I am to guess. the first one is CWM recovery included, and the second is Public Recovery included. I never used this tool
I would choose door number 1
BTW, there are other methods to install these things. But let's see what happens. Personally, I don't use these all in 1 tools. Got too many of them in the forums. But, let's see what happens.
If not successful, we'll use My method. And you will learn something in the process.
MD
Click to expand...
Click to collapse
*LOL* Tool doesn't work at all...so i will do it by using another method...can you recommend one that really works= :fingers-crossed:
captainn said:
*LOL* Tool doesn't work at all...so i will do it by using another method...can you recommend one that really works= :fingers-crossed:
Click to expand...
Click to collapse
Ehhhh,,, we're gonna do it my way now.
Ok, keep in mind, it's late in Moscow, and I have a baby that will need bath (long process) and other family duties.
Let's get your computer prepared the way it should always be when dealing with the dark side of android.
Your tab is running now, and that's good. You have a .021 build. Ok. But let;s see if we can make it better.
First thing, and I hope you have Windows XP or Windows 7.
Download and install the Android SDK.
http://developer.android.com/sdk/index.html
Now, next, is the Oracle Java Platform (JDK)
http://www.oracle.com/technetwork/java/javase/downloads/index.html
After you do these 2 things, well, we can move over to the dark side.
Now, after everything is installed, I want you to do something.
Connect your tab with USB debugging on. (Never turn this off)
Open Windows explorer, go to C:\program file (x86)\Android\Android-sdk\platform tools . Open a command window here (SHIFT & Right mouse click)
Then type adb devices in the CMD window. Should show device connected and some numbers.
This tells me the drivers are installed.
If not, You have to install Acer USB drivers from the website.
Then try again.
And that, is as far as I go tonight, too late.
Tomorrow, I will give you a lesson in NVFlash and fastboot.
Rule number 1. Drivers, Drivers, Drivers. This was just to prepare your system.
To save some time, for tomorrow, shut down your tab.
Using a paper clip, or needle or something. Press and hold the pin hole button near the USB port. Hold it. Then, press and hold PWR button. Wait 4 seconds, release PWR only. 1 second later, release the pin hole.
Tab should be black. PWR button white. You may get vibrate.
This is what we call APX mode.
When you connect your tab to your PC, after a few seconds, the PC should recognize this as (Recovery Mode, APX Mode, or Download Mode)
Will need to know what it says. If it says nothing, but gives you an error in Windows device manager, then Houston, we have a problem. And the problem is the drivers. And you need to fix it. You may have to manually select from a list or tell it where the drivers are.
And that is all for tonight Mate. Baby needs bath.
MD
Thank you very much. I installed the bootloader, the recovery and the tegraowner ics rom for the A501. It looks great and it seems that SOD is now part of the history 3G is also working. Great success :laugh:
Thanks for your help and to all developers!
captainn said:
Thank you very much. I installed the bootloader, the recovery and the tegraowner ics rom for the A501. It looks great and it seems that SOD is now part of the history 3G is also working. Great success :laugh:
Thanks for your help and to all developers!
Click to expand...
Click to collapse
Great! Was waiting to hear!
Not that I demand it, but, it's customary to hit the "thanks" button for those that help
Always remember, you have a "fastboot" bootloader, so if something happens, you can boot to the Fastboot, and do things like install boot.img's (kernels), Custom Recoveries, and some other things. That's why you installed Android SDK. Also, you have ADB capability as well.
Rock On!
MD
Moscow Desire said:
Great! Was waiting to hear!
Not that I demand it, but, it's customary to hit the "thanks" button for those that help
Always remember, you have a "fastboot" bootloader, so if something happens, you can boot to the Fastboot, and do things like install boot.img's (kernels), Custom Recoveries, and some other things. That's why you installed Android SDK. Also, you have ADB capability as well.
Rock On!
MD
Click to expand...
Click to collapse
In addition: Now i am using "ICS Evil Alex Unleashed Ver 2". I switched because gps is not working when using tegraowners rom. Now it seems, that all important features are working! Thanks a lot for your rom!
I have the official A500 ICS, didn't do anything other than the OTA upgrade, and it worked fine until I installed some additional apps, it started to do the SOD. Then I uninstalled the latest apps I added, more likely instagram, and the SOD went away, till now at least. So, if you can't get it to work, maybe a factory reset to clear out all the apps might help, then, add apps slowly to see find out which one actually act bad.
Moscow Desire said:
Ehhhh,,, we're gonna do it my way now.
Ok, keep in mind, it's late in Moscow, and I have a baby that will need bath (long process) and other family duties.
Let's get your computer prepared the way it should always be when dealing with the dark side of android.
Your tab is running now, and that's good. You have a .021 build. Ok. But let;s see if we can make it better.
First thing, and I hope you have Windows XP or Windows 7.
Download and install the Android SDK.
http://developer.android.com/sdk/index.html
Now, next, is the Oracle Java Platform (JDK)
http://www.oracle.com/technetwork/java/javase/downloads/index.html
After you do these 2 things, well, we can move over to the dark side.
Now, after everything is installed, I want you to do something.
Connect your tab with USB debugging on. (Never turn this off)
Open Windows explorer, go to C:\program file (x86)\Android\Android-sdk\platform tools . Open a command window here (SHIFT & Right mouse click)
Then type adb devices in the CMD window. Should show device connected and some numbers.
This tells me the drivers are installed.
If not, You have to install Acer USB drivers from the website.
Then try again.
And that, is as far as I go tonight, too late.
Tomorrow, I will give you a lesson in NVFlash and fastboot.
Rule number 1. Drivers, Drivers, Drivers. This was just to prepare your system.
To save some time, for tomorrow, shut down your tab.
Using a paper clip, or needle or something. Press and hold the pin hole button near the USB port. Hold it. Then, press and hold PWR button. Wait 4 seconds, release PWR only. 1 second later, release the pin hole.
Tab should be black. PWR button white. You may get vibrate.
This is what we call APX mode.
When you connect your tab to your PC, after a few seconds, the PC should recognize this as (Recovery Mode, APX Mode, or Download Mode)
Will need to know what it says. If it says nothing, but gives you an error in Windows device manager, then Houston, we have a problem. And the problem is the drivers. And you need to fix it. You may have to manually select from a list or tell it where the drivers are.
And that is all for tonight Mate. Baby needs bath.
MD
Click to expand...
Click to collapse
Great tutorial!
I have a500 with ota ICS. Rooted. Locked bootloader. And working fine, but I think it could be better..
I am used to flashing rom and kernel on my android phone, but it looks like it is a bit more difficult on this device..
If I want to try another rom, should I follow your tutorial first? Or what do I do?
Oh, and what rom do you recommend? - I need fast, reliable and everything working.. Nothing fancy is required
Sent from my A500 using xda app-developers app
Due to the fact that the N6/9 cannot oem unlock until after initial setup (which also means a forced ota), it may be impossible to dump the initial rom on it, info: PSA: OEM Unlock On The Nexus 6 And 9 Requires Checking A Box In Developer Options
What can be done however is finding a little information, specifically the bootloader/baseband (for devices that have them) and initial rom version.
How to check:
Enter fastboot mode
Make note of baseband and bootloader versions
Enter Recovery mode
Press and hold Volume up, and then press power until the UI appears
Make note of rom build in title
I would like to request someone that has not done first setup to make note of what build is preinstalled.
Is it not possible to go through initial setup without Internet connectivity?
dualityim said:
Is it not possible to go through initial setup without Internet connectivity?
Click to expand...
Click to collapse
It depends on the device, most recent ones now simply cannot finish setup without first checking in with gservices. They force you to connect to wifi to continue, and if you connect to a wifi point that cannot reach the internet, it will simply sit there waiting to connect.
This is what happened with my NP at least, and it was roughly the same with the 2013 N7.
I think all the quick hands on unboxing videos show people skipping all the setup steps, including adding wifi and logging in. There may be cell connection, but the OTA doesn't install itself, it just starts downloading and tells you when it's done, right? That's what my Moto X 2013 did when I cracked it open.
All nexii in recent history have forced otas during setup, there is no way to bypass it short of doing something that would normally break the ota check.
Most reviews have devices from before the ota, or had no ota available at all.
reminder: now that the N6 is starting to ship out, please make note of what the initial rom is.
Update: the N6 does not seem to have a forced update at least.
If you have a N6 and are willing to hold off on updating for a few days/weeks (until CWM or the like is ported), I would like to request a dump of the initial rom.
Due to the fact the N6 is likely a secure /system device, the only usable dumps require DD, nandroids or manually pulling the files are of minimal help.
YOU MUST DO THIS FROM A RECOVERY, IF YOU ROOT YOUR ROM YOU WILL NO LONGER BE ABLE TO RECIEVE OTAS/THE DUMP WILL BE NO GOOD
Here's how to do it:
boot into a custom recovery
open an adb shell
mount data: mount /data
dump bootloader:
dd if=/dev/block/platform/msm_sdcc.1/by-name/aboot of=/data/local/aboot.mbn
dd if=/dev/block/platform/msm_sdcc.1/by-name/rpm of=/data/local/rpm.mbn
dd if=/dev/block/platform/msm_sdcc.1/by-name/sbl1 of=/data/local/sbl1.mbn
dd if=/dev/block/platform/msm_sdcc.1/by-name/sdi of=/data/local/sdi.mbn
dd if=/dev/block/platform/msm_sdcc.1/by-name/tz of=/data/local/tz.mbn
dump baseband: dd if=/dev/block/platform/msm_sdcc.1/by-name/modem of=/data/local/radio.img
dump boot: dd if=/dev/block/platform/msm_sdcc.1/by-name/boot of=/data/local/boot.img
dump recovery: dd if=/dev/block/platform/msm_sdcc.1/by-name/recovery of=/data/local/recovery.img
dump system: dd if=/dev/block/platform/msm_sdcc.1/by-name/system of=/data/local/system.img
dump logo: dd if=dev/block/platform/msm_sdcc.1/by-name/logo of=/data/local/logo.bin
dump versions: dd if=/dev/block/platform/msm_sdcc.1/by-name/versions of=/data/local/versions.bin
What about dumping Att OEM? Since it is memblck0p39, does it matter? For the people that nuked the OEM partition and have to send it in for warrenty, it might make a big difference.
Well,I didn't take the ota,but I rooted it. what you trying to get done?
TheManii said:
All nexii in recent history have forced otas during setup, there is no way to bypass it short of doing something that would normally break the ota check.
Most reviews have devices from before the ota, or had no ota available at all.
reminder: now that the N6 is starting to ship out, please make note of what the initial rom is.
Click to expand...
Click to collapse
not true.
i got my ota a day after i got my n6, i didnt take the ota. the option hung for another day, but it was my choice not to ota. instead, i flashed the most recent aosp. otas are never forced upon anyone who owns a nexus.
edit.. ok, i read your next post.
This thread has been a lifesaver, I have a friend with a pre-order Att Nexus 6 that I was able to get the OEM partition from. I deleted something and I still do not have any sensors, and my logcat shows a ton of errors trying to get the sensors to work. I tried to fix-permissions with TWRP but it always fails. Anyone have any suggestions?
simms22 said:
not true.
i got my ota a day after i got my n6, i didnt take the ota. the option hung for another day, but it was my choice not to ota. instead, i flashed the most recent aosp. otas are never forced upon anyone who owns a nexus.
edit.. ok, i read your next post.
Click to expand...
Click to collapse
same here, I got my ota update probably 3 or 4 hours after setting my device up, but I just hit remind me later and never accepted it and wasn't forced to accept anything
Greetings XDA Members,
I am seeing alot of people repeating this same question again and again like "Hey, I have messed up I flashed this and this and now I want to get all setup to take the official Lollipop OTA of MOTO X, Please help" the same question over and over again in several other threads so I thought it might be a good idea to sum up everything in one thread and make this easier for other members to point any person having issue like these to this thread. Now keep in mind that I am not a professional developer, Im just here to tell the basics of flashing a stock firmware, IF I make any mistake please let me know and also this thread will be a long briefly explained one so please read carefully and consider everything before applying anything.
To start off, the point of this thread is to help our new members of XDA to have an idea of what to do and how to do, Now the main topic of this thread is to point our newbie fellows on how to flash a stock firmware on a messed up MOTO X (Any Model), By messed up I mean: Either the user corrupted or damaged or somehow got stuck between anything like bootloops,not getting signals,phone not working properly and all sorts of basic software problems. If you are having such problems with your phone and want to get back to the newly fresh Moto X like when you bought it, it was shiny and all the software was fresh etc And also you want to get all setup to receive the Lollipop OTA.. you are at the right place mate. Keep reading.
Have a look at this thread also for more useful information about getting ready to take the OTA its for the kitkat ota but still its all the same so this could be very useful! by @KidJoe http://forum.xda-developers.com/moto-x/general/faq-kit-kat-how-to-prepare-carriers-t2536735
or If you have an unlocked bootloader and are rooted, and the only change you did to your phone was replacing recovery to root.. Here is another option to flash Stock Recovery back on your phone to get ready to install the latest OTA -> http://forum.xda-developers.com/moto...ooted-t3027079 credits goes to @KidJoe .
PRECAUTIONS (A MUST READ BEFORE PROCEEDING ANY FURTHER)
I am not responsible if anything happens to your device during this process because I am just explaining here what to do I wont be the one who is applying the instructions on any phone so in no matter or aspect I am the responsible for damage caused to your device. So again do this on your own risk. I wont be responsible for any damage to your phone.
1: NEVER DOWNGRAED FIRMWARE/BOOTLOADER VERSION!
Okay so you want to downgrade to get the advantages of the previous android version of your phone. THE ANSWER IS A BIG NO! if you try to downgrade your phone and mess up with motoboot.img or gpt.bin you will get a hard brick! Never try to downgrade! Refer to this thread http://forum.xda-developers.com/moto-x/general/info-warning-risks-downgrading-impacts-t3058202 by @KidJoe to know all the facts about downgrading.
2: Downlaod the exact and correct firmrware, before flashing
Flashing another carriers rom on your phone would be a stupidity. MAKE yourself 100% sure that you have downloaded the correct/exact firmware of your phone, never flash some random firmware on your particular moto x. Flashing another carriers rom would give you a hard brick probably.. Never play with different firmwares. (I will be mentioning further in the thread, how to make sure to download the correct firmware.)
3:You must consider of having an Unlocked Bootloader before proceeding any further, Or if you have a locked bootloader this method might work on the locked bootloaders also but, again flashing different carriers firmware on a locked bootloader device will get you more screwed up
This method should also work for the locked bootloaders but be 100% sure that you are flashing the correct signed firmware of your specific carrier. As for the Bootloader Unlock, There are not much of options for now, You can unlock your bootloader either from the motorola official site or use sunshine unlocker to unlock your bootloader. Refer to this thread : http://forum.xda-developers.com/moto-x/general/request-help-exploit-moto-x-bl-t2828471 by @samwathegreat to have an idea about the sunshine unlocking method.
Also refer to this also for info about gaining root and unlocking bootloader http://forum.xda-developers.com/moto-x/general/one-stop-shop-how-root-moto-x-confusion-t2826159 by @KidJoe.
4:You messed up your stock rom and freezed some apps
If you have rooted, put xposed etc. Dont plan to revert back by restoring the freezed apps and Instead just flash the stock firmware from RSD. Restoring back freezed apps etc will cause more problems. But make sure you uninstall all of the frameworks of xposed before proceeding to flash stock firmware.
5:This method will wipe your data completely
As the Title says this method will obviously wipe every single piece of your personal data stored on this phone such as pictures,contacts,videos and pretty much everything. So be sure to backup your data on your pc or anywhere.
Grab Your Phones Its time to start the process. Make sure its charged more than 60%.
Okay enough theory, lets get this over with.
Download and install motorola drivers : https://motorola-global-portal.custhelp.com/app/answers/detail/a_id/88481 and restart you computer and proceed.
STEP 1: Identifying the correct name or model number of your Moto X
1: If the original motorola back cover is on the phone, there is some very fine/small print at the bottom of the back. It will have the FCC ID, Model number, etc. It could be hard to see, So you might have to tilt/twist the phone so the light shines off it just right and the model no appears. The Model No of your MOTO X should start with XT. Make a note of that. (credits goes to @KidJoe for explaining this in detail.)
2:Another way to find the model is by checking the Settings>About Phone of your X.
3:More ways to find out your model no, Connect the phone with the pc and see what does it shows on the pc when connected on USB MASS STORAGE. It should mention the XT10xx (Model name) of your phone on pc
NOTE:BEFORE you flash away from Stock, on the phone you first go App Drawer -> Settings -> About Phone... Make note of what is listed under System Version, Android Version, and build number. Then visit one (or all) of the sites until that host the leaked SBF files until you find the SBF that matches and down load the file to your PC for use later.. The file name will usually contain parts or all of that info listed under settings, and possibly the carrier name, or acronym for the carrier name (Verizon might be VZW, Rogers Canada might be RCI, etc).
So for example: If your phone model is XT1058 and under about phone it reports...
android version is 4.4.4
system version is 212.44.26. ghost_row.RCI.en.ca
build nunber is KXA21.12-L1.26
That tells me you have a Rogers Canada (RCI) XT1058 with 4.4.4 ROM on it. When you look at the file factory site for your SBF, you want to look for a file that contains some/all of that info, like... XT1058_RCI-CA_4.4.4_KXA21.12-L1.26_59_cid14_CFC_1FF.xml.zip
(notice the parts of the "about phone" info and file name which are highlighted in Bold to help illustrate the example)
IF you are already running a CUSTOM or 3Rd party rom, like CM, system version and build number will not match STOCK Moto SBF files. credits goes to @KidJoe for adding this additional info about figuring out what ROM is on your phone.
STEP 2: Identifying and downloading the correct firmware for your model of X
1:So now that you have identified, your Moto X is XT10xx, Now you will be downloading the correct firmware of your phone which should match the System/Build Version of your phone.
For Example: If your phone is from Rogers,ATT,Sprint,T-Mobile,US-CELLULAR,Europe etc. IT should be mentioned in the Settings>About Phone section below build version. Make a note of the whole build version/system version on a piece of paper or anything you like. Because the system/build version is the main key to have the proper knowledge about your phone before flashing any firmware.
Additional Info about bootloaders according to android version(This will give an idea about bootloaders, read it carefully and match the version of you bootloader in order with this dont downgrade):
(Android Version: Bootloader)
4.2.2: 30.70
4.2.2/camera patch OTA: 30.71
4.4: 30.B2
4.4.2: 30.B4
4.4.4: 30.B7
2:Now this part must get hard for the newbie guys but I will try my best to keep everything clear and easy. All The firmwares you need for your X is available at this site: http://www.filefactory.com/folder/dd05c058d3ff8dbe/?sort=created&order=DESC&show=100&page=1
Now start by searching the model no and system version of your moto x. For example: if your phone is from Rogers Canada it must have "XT1058 RCI_CA " in it.. XT1058:Model Name Rci: Rogers CA: Canada. You get this right? on the firmware there should be mentioned a little bit hint or info you need to identify your firmware. Go ahead and download it. Again for the newbie guys I cant explain much easier than i've explained above, Still if you cannot find the correct firmware let me know I will try to find it out. But please first try your best from your own side first, I cant spoonfeed you [emoji14] . ATTENTION: Please download the 4.4.4 Version of your carrier because it will be easy to receive the 5.1 OTA on a 4.4.4 rom.
STEP 3: Getting ready to flash through RSD LITENote: I wont be explaining a method to flash through fastboot as from my opinion I dont like fastboot it can cause you a serious problem if you type anything wrong. If you want to try the fastboot method there is also another similar guide on how to flash through fastboot refer to this thread http://forum.xda-developers.com/moto-x/general/guide-moto-x-return-to-100-stock-using-t2446515 by @TechSavvy2
1: Download RSD LITE 6.1.5 (RSD LITE SETUP IS ATTACHED download from there) and install it in your PC Windows. (I dont have a mac dont know anything about mac.)
2:Make a new folder and unzip the firmware zip file in that new folder
3: Open the XML FILE and edit the .XML file and remove any lines with "getvar" written in them, Remove that whole line which has "getvar" in it, and (CTRL+S) save that edited file.
3: RUN RSD LITE IN ADMINISTRATIVE RIGHTS on rsd lite right click and run as administrator, IF you dont run as administrator rsd lite wont flash anything.
4: Now on rsd lite press the three dotted "..." button and select the XML File from the "new folder" you made moments ago.
STEP 4: Getting your phone in fastboot mode
If you are totally fine and running your software normally: Power off your phone, wait for 5 seconds then press and hold the power/lock button and volume down button simultaneously for 5 seconds, then release those buttons after 5 seconds. You will be in the fastboot mode of your phone now plugin your phone on usb cable of your computer make sure the bootloader says "USB CONNECTED." If it doesnt shows usb connected sign, Change the usb cable or try another usb slot.
For the people who have damaged and corrupted the software and having black screens stuck and nothing else or either they did something naive and somehow cant get in the fastboot mode: Hook up your phone to an A/C Charger and wait for about 30mins to atleast recharge it. Then remove your phone from charger and dont press the power button! Do this: Press and hold the power/lock button and volume down button simultaneously for 5 seconds, then release those buttons after 5 seconds,If you are not properly bricked you will be on the fastboot now probably, now plugin your phone on usb cable of your computer make sure the bootloader says "USB CONNECTED." If it doesnt shows usb connected sign, Change the usb cable or try another usb slot.
For the people stuck on bootloop after flashing a 3rd party custom rom or stuck on the motorola logo etc. Do this: Press and hold the Power/lock button, Volume Up Button and Volume Down button, all the three buttons simultaneously for about 15 seconds, when the screen turns off, Quickly press the Power button and volume down button repeatedly (this time dont press and hold! Press both buttons repeatedly!) You will be on the fastboot mode of your phone plugin the phone on usb port and your bootloader should say "USB CONNECTED" AFAIK. If you are not bricked!
STEP 5:Flashing the firmware
On Rsd lite, make sure that your device is showing "Connected" Now, Press the start button on the rsd lite and wait for about maximum 30-40Mins to get your firmware flashed in the phone successfully. ATTENSION: Dont touch or power off your phone or computer during the flashing process untill or unless your device reboots and comes to its homescreen on the factory settings, make sure the usb cable is connected properly not loose. If you mess up anything during flashing process you are risking your whole phone so do this when you are calm enough.
Flashing Process Done Now You Are All Set Up To Receive The Latest OTA OF 5.1!
For the people who have flashed the 5.1 soak test/leak and are stuck at some certain point
So you couldn't wait and flashed the LEAKED test/soak versions of 5.02 and 5.1 and your bootloader is upgraded to 30.BC or 30.BD you are stuck on a bootloop and cant get your phone to work ----> There is nothing you could really do to save your self till now only one thing you can do is wait! DO NOT DOWNGRADE YOUR BOOTLOADER/FIRMWARE as that will risk bricking, but rather WAIT and hope a 5.1 SBF for their model/carrier leaks in the coming weeks/months, then fully flash it to return to stock. credits goes to @KidJoe for adding this info.
Good luck mates!
Thats all I can sum up in one thread, I hope this helps the new people. Peace Out.
whizinc said:
Greetings XDA Members,
I am seeing alot of people repeating this same question again and again like "Hey, I have messed up I flashed this and this and now I want to get all setup to take the official Lollipop OTA of MOTO X, Please help" the same question over and over again in several other threads so I though it might be a good idea to sum up everything in one thread and make this easier for other members to point any person having issue like these to this thread. Now keep in mind that I am not a professional developer, Im just here to tell the basics of flashing a stock firmware, IF I make any mistake please let me know and also this thread will be a long briefly explained one so please read carefully and consider everything before applying anything.
To start off, the point of this thread is to help our new members of XDA to have an idea of what to do and how to do, Now the main topic of this thread is to point our newbie fellows on how to flash a stock firmware on a messed up MOTO X (Any Model), By messed up I mean: Either the user corrupted or damaged or somehow got stuck between anything like bootloops,not getting signals,phone not working properly and all sorts of basic software problems. If you are having such problems with your phone and want to get back to the newly fresh Moto X like when you bought it, it was shiny and all the software was fresh etc And also you want to get all setup to receive the Lollipop OTA.. you are at the right place mate. Keep reading.
Have a look at this thread also for more useful information about getting ready to take the OTA its for the kitkat ota but still its all the same so this could be very useful! by @KidJoe http://forum.xda-developers.com/moto-x/general/faq-kit-kat-how-to-prepare-carriers-t2536735
PRECAUTIONS (A MUST READ BEFORE PROCEEDING ANY FURTHER)
I am not responsible if anything happens to your device during this process because I am just explaining here what to do I wont be the one who is applying the instructions on any phone so in no matter or aspect I am the responsible for damage caused to your device. So again do this on your own risk. I wont be responsible for any damage to your phone.
1: NEVER DOWNGRAED FIRMWARE/BOOTLOADER VERSION!
Okay so you want to downgrade to get the advantages of the previous android version of your phone. THE ANSWER IS A BIG NO! if you try to downgrade your phone and mess up with motoboot.img or gpt.bin you will get a hard brick! Never try to downgrade! Refer to this thread http://forum.xda-developers.com/moto-x/general/info-warning-risks-downgrading-impacts-t3058202 by @KidJoe to know all the facts about downgrading.
2: Downlaod the exact and correct firmrware, before flashing
Flashing another carriers rom on your phone would be a stupidity. MAKE yourself 100% sure that you have downloaded the correct/exact firmware of your phone, never flash some random firmware on your particular moto x. Flashing another carriers rom would give you a hard brick probably.. Never play with different firmwares. (I will be mentioning further in the thread, how to make sure to download the correct firmware.)
3:You must consider of having an Unlocked Bootloader before proceeding any further
There are not much of options for now, You can unlock your bootloader either from the motorola official site or use sunshine unlocker to unlock your bootloader. Refer to this thread : http://forum.xda-developers.com/moto-x/general/request-help-exploit-moto-x-bl-t2828471 by @samwathegreat to have an idea about the sunshine unlocking method.
Also refer to this also for info about gaining root and unlocking bootloader http://forum.xda-developers.com/moto-x/general/one-stop-shop-how-root-moto-x-confusion-t2826159 by @KidJoe.
3:You messed up your stock rom and freezed some apps
If you have rooted, put xposed etc. Dont plan to revert back by restoring the freezed apps and Instead just flash the stock firmware from RSD. Restoring back apps freezed etc will cause more problems. But make sure you uninstall all of the frameworks of xposed before proceeding to flash stock firmware.
Grab Your Phones Its time to start the process. Make sure its charged more than 60%.
Okay enough theory, lets get this over with.
Download and install motorola drivers : https://motorola-global-portal.custhelp.com/app/answers/detail/a_id/88481 and restart you computer and proceed.
STEP 1: Identifying the correct name or model number of your Moto X
1: If the original motorola back cover is on the phone, there is some very fine/small print at the bottom of the back. It will have the FCC ID, Model number, etc. It could be hard to see, So you might have to tilt/twist the phone so the light shines off it just right and the model no appears. The Model No of your MOTO X should start with XT. Make a note of that. (credits goes to @KidJoe for explaining this in detail.)
2:Another way to find the model is by checking the Settings>About Phone of your X.
3:More ways to find out your model no, Connect the phone with the pc and see what does it shows on the pc when connected on USB MASS STORAGE. It should mention the XT10xx (Model name) of your phone on pc
STEP 2: Identifying and downloading the correct firmware for your model of X
1:So now that you have identified, your Moto X is XT10xx, Now you will be downloading the correct firmware of your phone which should match the System/Build Version of your phone.
For Example: If your phone is from Rogers,ATT,Sprint,T-Mobile,US-CELLULAR,Europe etc. IT should be mentioned in the Settings>About Phone section below build version. Make a note of the whole build version/system version on a piece of paper or anything you like. Because the system/build version is the main key to have the proper knowledge about your phone before flashing any firmware.
Additional Info about bootloaders according to android version(This will give an idea about bootloaders, read it carefully and match the version of you bootloader in order with this dont downgrade):
(Android Version: Bootloader)
4.2.2: 30.70
4.2.2/camera patch OTA: 30.71
4.4: 30.B2
4.4.2: 30.B4
4.4.4: 30.B7
2:Now this part must get hard for the newbie guys but I will try my best to keep everything clear and easy. All The firmwares you need for your X is available at this site: http://www.filefactory.com/folder/dd05c058d3ff8dbe/?sort=created&order=DESC&show=100&page=1
Now start by searching the model no and system version of your moto x. For example: if your phone is from Rogers Canada it must have "XT1058 RCI_CA " in it.. XT1058:Model Name Rci: Rogers CA: Canada. You get this right? on the firmware there should be mentioned a little bit hint or info you need to identify your firmware. Go ahead and download it. Again for the newbie guys I cant explain much easier than i've explained above, Still if you cannot find the correct firmware let me know I will try to find it out. But please first try your best from your own side first, I cant spoonfeed you [emoji14] . ATTENTION: Please download the 4.4.4 Version of your carrier because it will be easy to receive the 5.1 OTA on a 4.4.4 rom.
STEP 3: Getting ready to flash through RSD LITENote: I wont be explaining a method to flash through fastboot as from my opinion I dont like fastboot it can cause you a serious problem if you type anything wrong. If you want to try the fastboot method there is also another similar guide on how to flash through fastboot refer to this thread http://forum.xda-developers.com/moto-x/general/guide-moto-x-return-to-100-stock-using-t2446515 by @TechSavvy2
1: Download RSD LITE 6.1.5 (RSD LITE SETUP IS ATTACHED download from there) and install it in your PC Windows. (I dont have a mac dont know anything about mac.)
2:Make a new folder and unzip the firmware zip file in that new folder
3: Open the XML FILE and edit the .XML file and remove any lines with "getvar" written in them, Remove that whole line which has "getvar" in it, and (CTRL+S) save that edited file.
3: RUN RSD LITE IN ADMINISTRATIVE RIGHTS on rsd lite right click and run as administrator, IF you dont run as administrator rsd lite wont flash anything.
4: Now on rsd lite press the three dotted "..." button and select the XML File from the "new folder" you made moments ago.
STEP 4: Getting your phone in fastboot mode
If you are totally fine and running your software normally: Power off your phone, wait for 5 seconds then press and hold the power/lock button and volume down button simultaneously for 5 seconds, then release those buttons after 5 seconds. You will be in the fastboot mode of your phone now plugin your phone on usb cable of your computer make sure the bootloader says "USB CONNECTED." If it doesnt shows usb connected sign, Change the usb cable or try another usb slot.
For the people who have damaged and corrupted the software and having black screens stuck and nothing else or either they did something naive and somehow cant get in the fastboot mode: Hook up your phone to an A/C Charger and wait for about 30mins to atleast recharge it. Then remove your phone from charger and dont press the power button! Do this: Press and hold the power/lock button and volume down button simultaneously for 5 seconds, then release those buttons after 5 seconds,If you are not properly bricked you will be on the fastboot now probably, now plugin your phone on usb cable of your computer make sure the bootloader says "USB CONNECTED." If it doesnt shows usb connected sign, Change the usb cable or try another usb slot.
For the people stuck on bootloop after flashing a 3rd party custom rom or stuck on the motorola logo etc. Do this: Press and hold the Power/lock button, Volume Up Button and Volume Down button, all the three buttons simultaneously for about 15 seconds, when the screen turns off, Quickly press the Power button and volume down button repeatedly (this time dont press and hold! Press both buttons repeatedly!) You will be on the fastboot mode of your phone plugin the phone on usb port and your bootloader should say "USB CONNECTED" AFAIK. If you are not bricked!
STEP 5:Flashing the firmware
On Rsd lite, make sure that your device is showing "Connected" Now, Press the start button on the rsd lite and wait for about maximum 30-40Mins to get your firmware flashed in the phone successfully. ATTENSION: Dont touch or power off your phone or computer during the flashing process untill or unless your device reboots and comes to its homescreen on the factory settings, make sure the usb cable is connected properly not loose. If you mess up anything during flashing process you are risking your whole phone so do this when you are calm enough.
Flashing Process Done Now You Are All Set Up To Receive The Latest OTA OF 5.1!
Note: Currently please dont and I repeat DONT flash any soak test or any 5.1 leaked release of stock rom. All you will be getting by doing this would be A messed up bootloader,motoboot,gpt etc. Dont be so impatient just wait for the ota to show up on your phone!
Good luck mates!
Thats all I can sum up in one thread, I hope this helps the new people. Peace Out.
Click to expand...
Click to collapse
That's exactly what I did last night to make sure that I can get the OTA of Lollipop 5.1 when it finally comes out. I have a feeling that it will be rolling out here pretty soon.
Mod Edit : HIDE tags added by @Darth ... No need to quote long Opening posts, or use hide tags if you must. Thanks!
cindylike24 said:
That's exactly what I did last night to make sure that I can get the OTA of Lollipop 5.1 when it finally comes out. I have a feeling that it will be rolling out here pretty soon.
Click to expand...
Click to collapse
Yeah its already rolling out in some areas of US.. Good luck
Sent from my ghost using Tapatalk
whizinc said:
Yeah its already rolling out in some areas of US.. Good luck
Sent from my ghost using Tapatalk
Click to expand...
Click to collapse
Not in my area yet.
Cindy
cindylike24 said:
Not in my area yet.
Cindy
Click to expand...
Click to collapse
Not across the river, either! *Waves from Illinois*
hbar98 said:
Not across the river, either! *Waves from Illinois*
Click to expand...
Click to collapse
Where are you from? I'm from Vincennes, Indiana.
Sent from my Samsung Galaxy Tab 4 8" model using Tapatalk
cindylike24 said:
Where are you from? I'm from Vincennes, Indiana.
Sent from my Samsung Galaxy Tab 4 8" model using Tapatalk
Click to expand...
Click to collapse
Now I live around Fairfiled, IL, but I grew up in Keensburg and Mt. Carmel.
hbar98 said:
Now I live around Fairfiled, IL, but I grew up in Keensburg and Mt. Carmel.
Click to expand...
Click to collapse
Cool! Small world, isn't it?!
Sent from my Samsung Galaxy Tab 4 8" model using Tapatalk
cindylike24 said:
Cool! Small world, isn't it?!
Sent from my Samsung Galaxy Tab 4 8" model using Tapatalk
Click to expand...
Click to collapse
Yep! I don't think that 5.1 is rolling out in the states yet... you'd think that whichever carrier rolled it out first would make some noise about it. I'll be ready, though! I really like 5.1.1 on my 2013 Nexus 7.
If you have an unlocked bootloader and are rooted, and the only change you did to your phone was replacing recovery to root.. Here is another option to flash Stock Recovery back on your phone -> http://forum.xda-developers.com/moto-x/general/ref-return-to-stock-recovery-rooted-t3027079
----
@whizinc , Something else to add to the OP on figuring out what ROM is on your phone...
Normally I would suggest BEFORE you flash away from Stock, on the phone you first go App Drawer -> Settings -> About Phone... Make note of what is listed under System Version, Android Version, and build number. Then visit one (or all) of the sites until that host the leaked SBF files until you find the SBF that matches and down load the file to your PC for use later.. The file name will usually contain parts or all of that info listed under settings, and possibly the carrier name, or acronym for the carrier name (Verizon might be VZW, Rogers Canada might be RCI, etc).
So for example: If your phone model is XT1058 and under about phone it reports...
android version is 4.4.4
system version is 212.44.26. ghost_row.RCI.en.ca
build nunber is KXA21.12-L1.26
That tells me you have a Rogers Canada (RCI) XT1058 with 4.4.4 ROM on it. When you look at the file factory site for your SBF, you want to look for a file that contains some/all of that info, like... XT1058_RCI-CA_4.4.4_KXA21.12-L1.26_59_cid14_CFC_1FF.xml.zip
(notice the parts of the "about phone" info and file name which are highlighted in Bold to help illustrate the example)
IF you are already running a CUSTOM or 3Rd party rom, like CM, system version and build number will not match STOCK Moto SBF files.
-------
You also might want to add info for those who couldn't wait, and flashed the LEAKED test/soak versions of 5.02 and 5.1 that now have bootloader 30.BC or 30.BD... as they will NOT want to downgrade to 4.4.4 as that will risk bricking, but rather WAIT and hope a 5.1 SBF for their model/carrier leaks in the coming weeks/months, then fully flash it to return to stock.
KidJoe said:
If you have an unlocked bootloader and are rooted, and the only change you did to your phone was replacing recovery to root.. Here is another option to flash Stock Recovery back on your phone -> http://forum.xda-developers.com/moto-x/general/ref-return-to-stock-recovery-rooted-t3027079
----
@whizinc , Something else to add to the OP on figuring out what ROM is on your phone...
Normally I would suggest BEFORE you flash away from Stock, on the phone you first go App Drawer -> Settings -> About Phone... Make note of what is listed under System Version, Android Version, and build number. Then visit one (or all) of the sites until that host the leaked SBF files until you find the SBF that matches and down load the file to your PC for use later.. The file name will usually contain parts or all of that info listed under settings, and possibly the carrier name, or acronym for the carrier name (Verizon might be VZW, Rogers Canada might be RCI, etc).
So for example: If your phone model is XT1058 and under about phone it reports...
android version is 4.4.4
system version is 212.44.26. ghost_row.RCI.en.ca
build nunber is KXA21.12-L1.26
That tells me you have a Rogers Canada (RCI) XT1058 with 4.4.4 ROM on it. When you look at the file factory site for your SBF, you want to look for a file that contains some/all of that info, like... XT1058_RCI-CA_4.4.4_KXA21.12-L1.26_59_cid14_CFC_1FF.xml.zip
(notice the parts of the "about phone" info and file name which are highlighted in Bold to help illustrate the example)
IF you are already running a CUSTOM or 3Rd party rom, like CM, system version and build number will not match STOCK Moto SBF files.
-------
You also might want to add info for those who couldn't wait, and flashed the LEAKED test/soak versions of 5.02 and 5.1 that now have bootloader 30.BC or 30.BD... as they will NOT want to downgrade to 4.4.4 as that will risk bricking, but rather WAIT and hope a 5.1 SBF for their model/carrier leaks in the coming weeks/months, then fully flash it to return to stock.
Click to expand...
Click to collapse
All the information that you suggested has been added to the OP. Thank you! :good:
https://docs.google.com/open?id=0B5XNxZ2OcfKtdDROTk5kb21ObU0 for asia retail only XT1052_RETAIL-ASIA_4.4.4_KXA21.12-L1.26_18_cid7_CFC_1FF.xml.zip
miju12 said:
https://docs.google.com/open?id=0B5XNxZ2OcfKtdDROTk5kb21ObU0 for asia retail only XT1052_RETAIL-ASIA_4.4.4_KXA21.12-L1.26_18_cid7_CFC_1FF.xml.zip
Click to expand...
Click to collapse
what do you mean by this?
Sent from my ghost using Tapatalk
whizinc said:
what do you mean by this?
Sent from my ghost using Tapatalk
Click to expand...
Click to collapse
factory image for XT1052. if you download from the file factory site it takes a lot of time.
miju12 said:
factory image for XT1052. if you download from the file factory site it takes a lot of time.
Click to expand...
Click to collapse
file factory is the only site present and online for now which has all the firmwares in it... So that's why i preferred it, ignoring the problem of the download speeds...
Sent from my ghost using Tapatalk
whizinc said:
file factory is the only site present and online for now which has all the firmwares in it... So that's why i preferred it, ignoring the problem of the download speeds...
Sent from my ghost using Tapatalk
Click to expand...
Click to collapse
yeah i know. if someone uploads the file to some other cloud like drive, won't it be easy to others to download? i have posted the link because if someone needs the asia retail factory image, it would be easy and fast to download from this link. and for others the file factory website is there. and the problem from downloading file from file factory is it can't be resume so if there is a network error you have to download the file from begining.
miju12 said:
yeah i know. if someone uploads the file to some other cloud like drive, won't it be easy to others to download? i have posted the link because if someone needs the asia retail factory image, it would be easy and fast to download from this link. and for others the file factory website is there. and the problem from downloading file from file factory is it can't be resume so if there is a network error you have to download the file from begining.
Click to expand...
Click to collapse
I agree with you, But i dont think someone will do that because its not easy to upload such big files on a private drive like clouds etc...
Sent from my ghost using Tapatalk
Do you know the file name for the Verizon Dev Edition?
whizinc said:
I agree with you, But i dont think someone will do that because its not easy to upload such big files on a private drive like clouds etc...
Sent from my ghost using Tapatalk
Click to expand...
Click to collapse
yeah its a pain to upload such big file. but the link i posted someone have uploaded file so its easy for XT1052 asia retail users to download
---------- Post added at 05:24 PM ---------- Previous post was at 05:16 PM ----------
mbush78 said:
Do you know the file name for the Verizon Dev Edition?
Click to expand...
Click to collapse
check this link for the file as it was uploaded in google drive. before flashing confirm it is for your model with the dev http://forum.xda-developers.com/moto-x/development/vzw-4-4-kitkat-fastboot-factory-image-t2537398
check this page of motorola https://motorola-global-portal.custhelp.com/app/standalone/bootloader/recovery-images
mbush78 said:
Do you know the file name for the Verizon Dev Edition?
Click to expand...
Click to collapse
Follow the link @miju12 suggested that would be the firmware for verizon dev edition... and dont execute the oem lock command... It will relock your bootloader if you have it unlocked.
Sent from my ghost using Tapatalk
< include generic disclaimer here >
TL;DR
Since update 3.1, Nvidia can force updates (such as the one that bricks your tablet) to be downloaded and installed silently. No guarantees, but:
If you're on stock, delete TegraOTA (/system/app/TegraOTA or /system/priv-app/TegraOTA if you're on 5.0 or newer, or /system/app/TegraOTA.apk if you're still on 4.4) before booting into Android (the attached ZIP file does this for you, but please check with the file manager in recovery before rebooting and let me know if it didn't work), then reboot
Note: you also will need to delete TegraOTA again if you ever install an OTA from Nvidia or a recovery image
If you're not on stock, you're probably safe
EDIT: The urgent OTA is currently not getting sent out to any devices anymore, not even to those who have been getting it before.
EDIT 2: The urgent OTA is now being delivered again, this time named "ST - yy"!
What if my tablet is already deactivated?
Unless you can still boot into fastboot mode (in which case your tablet isn't really deactivated yet), your tablet is probably gone for good. The only way to fix this would be through nvflash, and using it requires the SBK that is unique to each device and that only Nvidia knows, so it's pretty unlikely that we'll ever be able to fix these deactivated tablets.
What/why/how?
In the last OTA (Update 3.1), Nvidia has made some changes to their TegraOTA application. The most important/interesting/suspicious of which is the ability for them to mark OTAs as "urgent". What this means is that these updates will be downloaded without ever notifying the user, and they will be installed without asking the user for permission first. If this is how the kill switch is delivered, all users will see is the tablet randomly rebooting and installing an update, then the tablet would never boot again. As some of you might notice, this would match what has been happening to a few users already, both here and on reddit.
But that's not all. I've been connecting to the OTA servers using various serial numbers (both found and provided to me by a few people) in hopes of actually finding the update that bricks the device. The first serial number I've tried that wasn't mine was the serial number from the screenshot on the recall page. It revealed an interesting "urgent" OTA, named "SHIELD Tablet xx - LTE", which does nothing but flash a blob (which, among other things, contains the bootloader). Many more questions appear now, but the main one is: if this is nothing but a routine bootloader update, why is it marked urgent? And why is it not attached to any Android update? But this by itself is not enough to prove anything, as I could only obtain it with one serial number, so as far as I could have known, it might had just been an internal update or something similar. (update is linked and analysed in the second post below)
Today, however, one of the serial numbers I've been given by some of the people here (thanks for the help guys!) turned out to have the same update waiting for it the next time it connected to the Internet. This rules out the possibility of an internal update, so the next somewhat obvious possibility is that this is the kill switch. Mind you, I still have no direct way of proving this without flashing the ZIP to see what happens (which I'm not planning to do myself), but I will keep checking on the other serial numbers I've gotten to see if this update turns up for them too.
The same person who has given me this serial number has also tested running the old tablet on the latest stock Android version but with TegraOTA removed, and, as expected, the tablet is still working perfectly fine now. Your mileage may vary.
How can I know if the kill switch has been triggered for my tablet?
Go to http://shield.bogdacutu.me/ and enter the full serial number of your old tablet. If the next OTA returned is "SHIELD Tablet xx" "ST - yy", the kill switch has been triggered for your tablet.
Warning: the serial number from the box of the tablet and the one etched on the side of the tablet are not complete, as they only contain the first 13 characters of the full (20 characters) serial number. You can get the full serial number from Android (Settings -> About -> Status), from the bootloader (it will be on the screen when you boot into bootloader mode), or from your computer if the tablet is or (in some cases) if it was previously connected, using various tools such as USBDeview. Example: 0413714803249000a4cf (you can try this on the page and it will return that the kill switch is activated).
Why would I want to also do the fix on my new tablet too?
The update is signed by Nvidia, and communication with the OTA server does not use HTTPS, so, for example, a malicious WiFi network could MITM your connection and cause this update (as well as any other signed update) to be flashed to your new tablet without your permission, thus permanently disabling it too. If you have the stock recovery, only updates signed by Nvidia can run. The story might be slightly different if your recovery doesn't enforce signature verification (such as TWRP and CWM by default).
Can I still get updates from Nvidia after doing this?
Not directly, but people will post OTA download links here on xda when new updates get released. I'd personally recommend that you wait before flashing though until someone here checks the new update to confirm that there's no new way for Nvidia to kill your tablet.
Many hours of work have gone into investigating this. Even if it doesn't help your specific scenario, consider hitting that Thanks button, so that I can at least know it wasn't for nothing.
I'd also like to thank the people who have given me their serial numbers to use for testing again, this wouldn't have been possible without their help: @Beauenheim, @Jackill, and @runandhide05 (who has even volunteered to test removing TegraOTA with the latest update on his old tablet :highfive
Fragments of code from TegraOTA.apk
< screenshots temporarily removed >
Also, from what I've seen so far, the update isn't delivered instantly after activating the new tablet. I don't know exactly what the rule is, but out of the 4 serial numbers that I have, only 2 have this update waiting for them.
EDIT: One more serial number from the ones I have has gotten the xx update. Only one left...
EDIT 2: All the serial numbers I have have the urgent OTA waiting for them now.
"SHIELD Tablet xx" - Update Analysis
OTA URL: http://ota.nvidia.com/ota/data/post...wf-full_ota-32256_554.0168.20150624152335.zip
yy OTA URL: http://ota.nvidia.com/ota/data/posted-roms/uploaded/st---yy--092704233775---7294.20150819152732.zip (if you don't know what you're doing, DO NOT DOWNLOAD THIS, it's very likely that this will permanently brick your device upon flashing it!!!) - also attached to this post in case this link becomes invalid
updater-script is the first file we check:
Code:
getprop("ro.product.device") == "shieldtablet" || abort("This package is for \"shieldtablet\" devices; this is a \"" + getprop("ro.product.device") + "\".");
nv_copy_blob_file("blob", "/staging");
reboot_now("/dev/block/platform/sdhci-tegra.3/by-name/MSC", "");
Suspiciously enough, this only flashes a blob to the staging partition. But what exactly does this blob do, you might ask? Well, the blob actually contains data for 9 partitions, which are automatically replaced during the next boot (before the bootloader does anything else at all, so once you've rebooted, there's no going back) with the contents present in this blob. The 9 partitions are as follows (also detailing comparison with files from update 3.1):
BCT (Boot Configuration Table) - stores some information that is needed for the device to find the bootloader stored on the other partitions, initialize the RAM and some other stuff
Status after update: probably corrupted - the previous OTAs have binary BCTs, but this update replaces it with a text file (which, while it does contain somewhat relevant information, is likely not a valid format). If this is corrupted, it's enough for the device not to be able to boot anymore.
BMP (boot logo) - intact
DTB - intact
EBT (part of the bootloader) - has a zeroed out region
NVC (part of the bootloader) - intact
RBL (part of the bootloader) - has a zeroed out region
RP4 (landscape boot logo) - intact
TOS (Trusted OS - probably part of the bootloader too) - has a zeroed out region
WB0 (related to the boot process, source file is named "nvbootwb0.bin") - has a zeroed out region
The update also contains a few other files, but those are not used at all (probably leftovers from the 5.1 AOSP update template that they are using).
DO NOT DOWNLOAD THE ATTACHMENT IF YOU DON'T KNOW WHAT YOU'RE DOING. THIS IS THE XX OTA, NOT THE ZIP THAT REMOVES TEGRAOTA!
Just as I suspected!!
Thanks a lot this is great. So the silent updater can force updating even with a custom recovery like cwm?
How to install the provided zip?
Thanks again.
tecnoworld said:
Thanks a lot this is great. So the silent updater can force updating even with a custom recovery like cwm?
How to install the provided zip?
Thanks again.
Click to expand...
Click to collapse
CWM and TWRP are both compatible with OTAs, so yes, it can. If you completely erase the recovery (fastboot erase recovery), the update can't get flashed, but the tablet will still reboot (which is at least annoying).
You can flash the provided ZIP through CWM or TWRP (but please check through the file manager if /system/app/TegraOTA still exists after installing it, the ZIP hasn't gone through a lot of testing so it might not work properly in all cases)
tecnoworld said:
Thanks a lot this is great. So the silent updater can force updating even with a custom recovery like cwm?
How to install the provided zip?
Thanks again.
Click to expand...
Click to collapse
This was to be my question too... Normal ota updates will not flash if you have a custom recovery, so how would this silent ota update?
bluegizmo83 said:
This was to be my question too... Normal ota updates will not flash if you have a custom recovery, so how would this silent ota update?
Click to expand...
Click to collapse
Normal OTAs don't work through custom recoveries because they do various checks that usually fail when you have a custom recovery (such as if the system partition is modified, by rooting for example), this urgent OTA has none of those checks
Bogdacutu said:
Normal OTAs don't work through custom recoveries because they do various checks that usually fail when you have a custom recovery (such as if the system partition is modified, by rooting for example), this urgent OTA has none of those checks
Click to expand...
Click to collapse
Oh ok! Great explaination. Thanks for all your hard work on this! I'm flashing the zip now, i'll report back if it removes the file
Edit: Ok I flashed the zip, and TegraOTA is gone. Now I will finally turn on my new tablet and set it up!
So out of interest, what do you think the chances are that thisll work?
How did you find out if the update is waiting? FYI I flashed the ZIP... All is good and it booted fine on LTE 32Gb...
Plus the deleting of the TegraOTA File has gone through... So you really think the TegraOTA removal has stopped it?
How do i check if i have downloaded randomly that update?
Great post. Hopefully that's as far as Nvidia is going to go. I flashed a custom rom on my old tablet. I'm keeping my new one stock but deleting the system app per your post. Just in case Nvidia is spiteful when I don't return the old tablet. I don't want to leave them any option of nuking the new one.
fkofilee said:
So out of interest, what do you think the chances are that thisll work?
How did you find out if the update is waiting? FYI I flashed the ZIP... All is good and it booted fine on LTE 32Gb...
Click to expand...
Click to collapse
Decompiled the OTA application. Using information from there I can connect to the OTA server directly from my PC, and request updates for any given serial number and Android version combination.
I wouldn't have posted this if I weren't relatively confident in my findings
Bogdacutu said:
Decompiled the OTA application. Using information from there I can connect to the OTA server directly from my PC, and request updates for any given serial number and Android version combination.
I wouldn't have posted this if I weren't relatively confident in my findings
Click to expand...
Click to collapse
I know fella I appreciate it. Could you check my second point? 2 x Nvidia Shields would be awesome! One for Work, One For Home
fkofilee said:
Plus the deleting of the TegraOTA File has gone through... So you really think the TegraOTA removal has stopped it?
How do i check if i have downloaded randomly that update?
Click to expand...
Click to collapse
Yes, I think it did. If that update was downloaded on your device, it would have been too late (as it reboots instantly after the update is downloaded), so I wouldn't worry about that.
Bogdacutu said:
Yes, I think it did. If that update was downloaded on your device, it would have been too late (as it reboots instantly after the update is downloaded), so I wouldn't worry about that.
Click to expand...
Click to collapse
So heres an interesting one for you, using a logical mindset, if you receive your new tablet, activate it, the next time that the old one connects to the network, it downloads this update and bricks it? But it wont technically do this until the new tablet is turned on?
fkofilee said:
So heres an interesting one for you, using a logical mindset, if you receive your new tablet, activate it, the next time that the old one connects to the network, it downloads this update and bricks it? But it wont technically do this until the new tablet is turned on?
Click to expand...
Click to collapse
As mentioned in the OP, the update doesn't get delivered immediately after you activate the new tablet. But yes, the old tablet shouldn't get the update before the new one is activated.
Bogdacutu said:
As mentioned in the first post, the update doesn't get delivered immediately after you activate the new tablet. But yes, the old tablet shouldn't get the update before the new one is activated.
Click to expand...
Click to collapse
Sorry fella missed that part, I will be donating some funds when i get paid later this month Mucho Gracias!
Totally not related to this thread, but I just went to setup my new tablet and it's not letting me restore apps & settings from my old Shield Tablet... It doesn't show my old tablet as a restore option. I doubt checked and the old tablet is setup to backup all settings and apps though. Anyone else have this issue when setting up they're new tablet?
bluegizmo83 said:
Totally not related to this thread, but I just went to setup my new tablet and it's not letting me restore apps & settings from my old Shield Tablet... It doesn't show my old tablet as a restore option. I doubt checked and the old tablet is setup to backup all settings and apps though. Anyone else have this issue when setting up they're new tablet?
Click to expand...
Click to collapse
Upgrade to 5.1 on the new tablet without restoring any data, then do a factory reset and you should get the option to restore
Bogdacutu said:
Upgrade to 5.1 on the new tablet without restoring any data, then do a factory reset and you should get the option to restore
Click to expand...
Click to collapse
AWESOME man, thank you!!
Hey XDA,
I think google may have just created a way to save any nonbootable bricked nexus with recovery access. Due to some N OTA failures, they just released a side-loadable OTA through recovery. This OTA is actually a full system image and from what I am reading it can be used to saved any bricked device that won't accept another sideloadable OTA. Here is the reddit post and the AP article on it.
https://www.reddit.com/r/Android/comments/4a0ox6/marshmallow_ota_hose_your_nexus_device_just_flash/
http://www.androidpolice.com/2016/0...t-bricking-some-devices-but-google-has-a-fix/
Good luck guys. I would love to see some success stories here if it works for you and if so, spread the word!
That explains why the OTA for the N preview was the same size as the image, and why after upgrading to March security release I didn't have to download a different OTA to get to N
So is this usable in all situations? If yes then should download it & store it safely
Interesting thing, can this update bypass factory reset protection?
iluvatrix said:
So is this usable in all situations? If yes then should download it & store it safely
Click to expand...
Click to collapse
I would assume this could be used in any situation where you have a paper wait. So say you're on marshmallow build and somehow things go wrong ,bootloader locked USB debugging not check ,with this ota you can still sideload but it will be an N build which is fine at least you'll have a working device that now you can revert back to your original build. So I'm keeping this as well. I really don't need to but its nice to have just in case. I normally keep my bootloader unlocked at all times anyways just in case things go haywire... Someone correct me if I'm not correct please. Have a nice weekend all?
---------- Post added at 11:01 AM ---------- Previous post was at 10:58 AM ----------
Displax said:
Interesting thing, can this update bypass factory reset protection?
Click to expand...
Click to collapse
Good question..
Displax said:
Interesting thing, can this update bypass factory reset protection?
Click to expand...
Click to collapse
Most likely not, because normally when receiving an OTA all of that remains intact but, I think it's worth a test.
This will NOT bypass factory reset protection. This is just an update.zip that is a signed "FULL" image rather than a "DIFFERENCE" image. That means that it just doesn't need to perform the verification step before proceeding to install the update.
There is also another "problem" with relying on these as the ultimate unbrick files, which is that if you happen to install some official build that is NEWER than N-pre1, then the recovery will refuse to "downgrade". So while it may be useful for now while nobody is running anything newer than N-pre1, it isn't a permanent solution.
This is a ligit Fix. Confirmed by me.
Only thing I did different was to use an app called "Nexus Root Toolkit v2.1.4"
Upon launching the app (and there was plenty of prep to get it going on my Windows Vista laptop-my Mini Mac had problems loading in VMWare as WIndows XP so it did not work for me on a Mac)
I clicked on the "Advanced Utilities" section and clicked the "Launch" Tab.
The Advanced Utilities has a section called "Sideload OTA Update", I then clicked on "Sideload Update" and followed the instructions.
It pretty much asked me to select the file location of the Google Patched Image file called "shamu-ota-2659757-073c33ae.zip" (which stays zipped-do not extract it).
Then I followed the instructions on the screen. It did take me several attempts to get right, but in the end it worked as stated... I was so tired of trying to get this work for the last 7 days that I got lazy and despirate and did not take the time to read the instructions on the Nexus Root Toolkit. I had already filled an insurance claim for this because I was sure I could not get this phone back from this problem.
The trickiest issue I had was getting to boot the device into "Recovery" "ADB Sideload" because when I switched it to ADB Sideload, it would stop seeing the device. This is obtained by Power Down, Press Power and Volume Down at the same time, this brings up the Boot menu. You have to use the volume keys up or down to select "Recovery" and press Power again to select it. After about 3 or 4 seconds you see the Dead android with the Red Exclamation Point. That is what you want. Next Press Power and Volume Up, quickly release both and Press the Volume up again. You will finally see the Recovery screen where you will find the "ADB Sideload" option. This missing tidbit I was able to find at the Motorola Nexus Support page.
So, Yes. this worked for me! ...and I am going to cancel that insurance claim after all. :good:
Thanks again to whoever posted this and Google for being man enough to make things right for all the people that got in too deep with this "N Preview" gone wrong.
flash4yish
Displax said:
Interesting thing, can this update bypass factory reset protection?
Click to expand...
Click to collapse
doitright said:
This will NOT bypass factory reset protection.
Click to expand...
Click to collapse
The first N preview apparently has a bug that will allow a user to bypass FRP (if they are on the first N preview)
http://www.androidpolice.com/2016/0...ory-reset-protection-workaround-on-android-n/
flash4yish said:
This is a ligit Fix. Confirmed by me.
Only thing I did different was to use an app called "Nexus Root Toolkit v2.1.4"
Upon launching the app (and there was plenty of prep to get it going on my Windows Vista laptop-my Mini Mac had problems loading in VMWare as WIndows XP so it did not work for me on a Mac)
I clicked on the "Advanced Utilities" section and clicked the "Launch" Tab.
The Advanced Utilities has a section called "Sideload OTA Update", I then clicked on "Sideload Update" and followed the instructions.
It pretty much asked me to select the file location of the Google Patched Image file called "shamu-ota-2659757-073c33ae.zip" (which stays zipped-do not extract it).
Then I followed the instructions on the screen. It did take me several attempts to get right, but in the end it worked as stated... I was so tired of trying to get this work for the last 7 days that I got lazy and despirate and did not take the time to read the instructions on the Nexus Root Toolkit. I had already filled an insurance claim for this because I was sure I could not get this phone back from this problem.
The trickiest issue I had was getting to boot the device into "Recovery" "ADB Sideload" because when I switched it to ADB Sideload, it would stop seeing the device. This is obtained by Power Down, Press Power and Volume Down at the same time, this brings up the Boot menu. You have to use the volume keys up or down to select "Recovery" and press Power again to select it. After about 3 or 4 seconds you see the Dead android with the Red Exclamation Point. That is what you want. Next Press Power and Volume Up, quickly release both and Press the Volume up again. You will finally see the Recovery screen where you will find the "ADB Sideload" option. This missing tidbit I was able to find at the Motorola Nexus Support page.
So, Yes. this worked for me! ...and I am going to cancel that insurance claim after all. :good:
Thanks again to whoever posted this and Google for being man enough to make things right for all the people that got in too deep with this "N Preview" gone wrong.
flash4yish
Click to expand...
Click to collapse
I'm glad to hear it worked for you
Works for me boss
Thanks for finding this one - one of my 6's was soft bricked ( could only get to fastboot or recovery etc. could not complete reg. boot after signing up for android beta program OTA ).
I was able to ADB sideload the system OTA as described without a hitch. All data / set-up on phone was intact and functional.
Just for the record this Nx6 was only bootloader unlocked - no other mods/changes prior to original Beta OTA.
:good::good:
mowgli762 said:
Thanks for finding this one - one of my 6's was soft bricked ( could only get to fastboot or recovery etc. could not complete reg. boot after signing up for android beta program OTA ).
I was able to ADB sideload the system OTA as described without a hitch. All data / set-up on phone was intact and functional.
Just for the record this Nx6 was only bootloader unlocked - no other mods/changes prior to original Beta OTA.
:good::good:
Click to expand...
Click to collapse
Why didn't you just flash the system.IMG if the bootloader was unlocked?
holeindalip said:
Why didn't you just flash the system.IMG if the bootloader was unlocked?
Click to expand...
Click to collapse
I could have but I don't have any experience with flashing system images and retaining my settings and data (removing the wipe command in the batch file if I remember correctly).
I was pleased just to be able to handle it as an OTA instead. When I'm working at/near my experience limits I try to take smaller chances. I know working with a alpha release is risky and I'll face the consequences at need. Must have been a considerable number of folks in the same boat as me for Google to have come up with a lower skill level solution (for the likes of me).
mowgli762 said:
I could have but I don't have any experience with flashing system images and retaining my settings and data (removing the wipe command in the batch file if I remember correctly).
I was pleased just to be able to handle it as an OTA instead. When I'm working at/near my experience limits I try to take smaller chances. I know working with a alpha release is risky and I'll face the consequences at need. Must have been a considerable number of folks in the same boat as me for Google to have come up with a lower skill level solution (for the likes of me).
Click to expand...
Click to collapse
Download the system image
Extract system.img
Fastboot flash system system.img
This will retain all data on phone
Your boot loader is unlocked so...
A. You used a toolkit and don't know the commands that the toolkit uses
B. You bought the phone used with an unlocked bootloader
Toolkits are for just ease of use if you already know the commands , because if you unlocked your bootloader manually this is a simple 5 minute fix if the factory image is already downloaded. sorry for the rant not trying to be rude, just enlightenment.
holeindalip said:
Download the system image
Extract system.img
Fastboot flash system system.img
This will retain all data on phone
Your boot loader is unlocked so...
A. You used a toolkit and don't know the commands that the toolkit uses
B. You bought the phone used with an unlocked bootloader
Toolkits are for just ease of use if you already know the commands , because if you unlocked your bootloader manually this is a simple 5 minute fix if the factory image is already downloaded. sorry for the rant not trying to be rude, just enlightenment.
Click to expand...
Click to collapse
Good - case specific information needs no apology - Diplomacy has never been alluded to as being in my skill set (too much glass in my house to throw stones).
Thanks for your interest and info.
TriguyRN said:
Hey XDA,
I think google may have just created a way to save any nonbootable bricked nexus with recovery access. Due to some N OTA failures, they just released a side-loadable OTA through recovery. This OTA is actually a full system image and from what I am reading it can be used to saved any bricked device that won't accept another sideloadable OTA. Here is the reddit post and the AP article on it.
https://www.reddit.com/r/Android/comments/4a0ox6/marshmallow_ota_hose_your_nexus_device_just_flash/
http://www.androidpolice.com/2016/0...t-bricking-some-devices-but-google-has-a-fix/
Good luck guys. I would love to see some success stories here if it works for you and if so, spread the word!
Click to expand...
Click to collapse
Man you are life saver i donno how to thank you
you saved my nexus 6p with this post , i sent my problem about 2 months ago in nexus 6p question and answer about my device which bricked while installing the ota update with looked bootloader and have tried everything to save it but noway you are the hero who saved it XD
(btw my device is nexus 6p and it worked )
i really appreciate your help and sharing your information
thanks
---------- Post added at 01:52 AM ---------- Previous post was at 01:46 AM ----------
flash4yish said:
This is a ligit Fix. Confirmed by me.
Only thing I did different was to use an app called "Nexus Root Toolkit v2.1.4"
Upon launching the app (and there was plenty of prep to get it going on my Windows Vista laptop-my Mini Mac had problems loading in VMWare as WIndows XP so it did not work for me on a Mac)
I clicked on the "Advanced Utilities" section and clicked the "Launch" Tab.
The Advanced Utilities has a section called "Sideload OTA Update", I then clicked on "Sideload Update" and followed the instructions.
It pretty much asked me to select the file location of the Google Patched Image file called "shamu-ota-2659757-073c33ae.zip" (which stays zipped-do not extract it).
Then I followed the instructions on the screen. It did take me several attempts to get right, but in the end it worked as stated... I was so tired of trying to get this work for the last 7 days that I got lazy and despirate and did not take the time to read the instructions on the Nexus Root Toolkit. I had already filled an insurance claim for this because I was sure I could not get this phone back from this problem.
The trickiest issue I had was getting to boot the device into "Recovery" "ADB Sideload" because when I switched it to ADB Sideload, it would stop seeing the device. This is obtained by Power Down, Press Power and Volume Down at the same time, this brings up the Boot menu. You have to use the volume keys up or down to select "Recovery" and press Power again to select it. After about 3 or 4 seconds you see the Dead android with the Red Exclamation Point. That is what you want. Next Press Power and Volume Up, quickly release both and Press the Volume up again. You will finally see the Recovery screen where you will find the "ADB Sideload" option. This missing tidbit I was able to find at the Motorola Nexus Support page.
So, Yes. this worked for me! ...and I am going to cancel that insurance claim after all. :good:
Thanks again to whoever posted this and Google for being man enough to make things right for all the people that got in too deep with this "N Preview" gone wrong.
flash4yish
Click to expand...
Click to collapse
thanks buddy for sharing your experience
i tried to sideload the ota file by sdk from stock recovery and apply ota from adb manually by command adb sideload (filename)
but it stopped at 89% , so i give shot to your way and it works fine by the toolkit so i have to thank you too .
atef79 said:
Man you are life saver i donno how to thank you
you saved my nexus 6p with this post , i sent my problem about 2 months ago in nexus 6p question and answer about my device which bricked while installing the ota update with looked bootloader and have tried everything to save it but noway you are the hero who saved it XD
(btw my device is nexus 6p and it worked )
i really appreciate your help and sharing your information
thanks
---------- Post added at 01:52 AM ---------- Previous post was at 01:46 AM ----------
thanks buddy for sharing your experience
i tried to sideload the ota file by sdk from stock recovery and apply ota from adb manually by command adb sideload (filename)
but it stopped at 89% , so i give shot to your way and it works fine by the toolkit so i have to thank you too .
Click to expand...
Click to collapse
The best way to thank me is sharing your experience and this thread to help people in need. Already put a smile on my face
TriguyRN said:
The best way to thank me is sharing your experience and this thread to help people in need. Already put a smile on my face
Click to expand...
Click to collapse
I already shared your post in my topic that I made in the Nexus 6p section to help all who bricked there devices with locked bootloader, and thx again .
This is my topic link
http://forum.xda-developers.com/nexus-6p/help/command-t3308390/post66086939#post66086939
just want to ask would this method work if the phone has not been authorized to a specific PC ?
iluvatrix said:
just want to ask would this method work if the phone has not been authorized to a specific PC ?
Click to expand...
Click to collapse
I'm not sure what you mean by "if the phone has not been authorized to a specific PC". As far as I am aware Android phones are not authorized to a PC, that is an Apple thing...