Hello,
Guys i have got Moto X XT1052 from a friend for few days. To mainly fix it. Actually, whenever i turn phone on. It keeps on crashing all apps, like Unfortunately, Launcher has stopped, calender and so on. It's not allowing me to touch anywhere else. So i would like to restore it. I checked all threads and found fine solution for flashing. I can do it. But those who uploaded ROMs on filefactory, it's kinda old. And downloading speed is really slow. Even when my net speed is double of it. I should get 300 KB/s some. But i am getting 50KB/s from their site. So i need help on this. If anyone can upload that ROM(XT1052_RETAIL-ASIA_4.4.4_KXA21.12-L1.26_18_cid7_CFC_1FF.xml.zip) on any other site like mediafire, Google files or torrent. I will really appreciate it. Please i urgently need it. Let me know if anything else to be done too. Because on current bootloader showing Device is Lock. And i saw youtube videos, most of them had Device is unlock. I am using this method, please take a look and let me know. Thanks. http://forum.gsmhosting.com/vbb/f78...to-x-2nd-gen-firmware-flashing-guide-1877668/
You can try to look here:
https://cloud.mail.ru/public/a083d0bb5e97/Motorola/XT1052/
https://cloud.mail.ru/public/64a43f0fcc1e/Moto_X/XT1052/
+
4.4.4 Retail GB (XT1052_RETAIL-GB_4.4.4_KXA21.12-L1.26_56_cid7_CFC_1FF.xml.zip)
4.4.4 Retail DE (XT1052_RETAIL-DE_4.4.4_KXA21.12-L1.26_54_cid7_CFC_1FF.xml.zip)
4.4.4 Retail EU (XT1052_RETAIL-EU_4.4.4_KXA21.12-L1.26_54_cid7_CFC_1FF.xml.zip)
http://forum.xda-developers.com/showthread.php?t=2976596
Here you go - https://mega.co.nz/#!U8NkgQqA!2yUsrJlNp0j_8ttzjJmHS4C4hh9cQ__vXtNKfmlm8cg
Sent from my Moto X using XDA Free mobile app
Guys, stuck in mid. Can you tell me, that do i need to unlock device first to get back to stock ROM? I tried manual flashing and RSD method too. But both failed to do anything. All apps still crashing. :l Please help me on this? New for Moto X. :l Thanks.
DarKrypton said:
Guys, stuck in mid. Can you tell me, that do i need to unlock device first to get back to stock ROM? I tried manual flashing and RSD method too. But both failed to do anything. All apps still crashing. :l Please help me on this? New for Moto X. :l Thanks.
Click to expand...
Click to collapse
First you dont need to unlock or lock your bootloader. Have you already tried to just go into recovery mode and factory reset the phone? How did the error start? What did your friend try to do, when he got the error first? What is the EXACT error message you get, while flashing?
Sent from my XT1052 using XDA Free mobile app
N00BY0815 said:
First you dont need to unlock or lock your bootloader. Have you already tried to just go into recovery mode and factory reset the phone? How did the error start? What did your friend try to do, when he got the error first? What is the EXACT error message you get, while flashing?
Sent from my XT1052 using XDA Free mobile app
Click to expand...
Click to collapse
When i do factory option in recovery mode, it just boot up phone normally. And then it shows "Unfortunately, the process com.google.process.gapps has stopped". Then it keeps poping up with more crashes, like launcher, google play services. It hardly let me touch somewhere else. And if i tap "Ok" quickly, phone just shut down. Even in recovery mode, i tried selecting "Recovery" option, and it shown me "Boot up failed". And actually my friend don't know much about phones and all this. He said it just started happening. :l Maybe he installed some weird app. And i don't get any error while flashing. Everything went fine. But when i check phone it doesn't change anything else. Same as old. Even when i erased all user data. Will just erasing data will fix it? Then after that i can do full stock ROM flashing.
Why i am not getting back to stock guys. Everything going fine. Just i checked a thread, where a guy said he is getting that "Variable not supported" something. I am getting same thing. So what can i do? :l Please help me to get back to stock ROM. I really need to fix it. Thanks.
Try motofirmware.center to try and see if they have the ROM you're looking for. I went to this site for the stock ROM for my XT1060 Developer Edition and was able to find it there. It saved me when I messed up my phone earlier this week. When you flash the stock ROM using the RSDLite program, it will do a wipe on your phone as it flashes it to your phone. When you boot up the phone after flashing the stock ROM, your programs should reinstall just fine on the phone once you log on to your Google Play account.
Cindy
DarKrypton said:
So.. i am confused with all this. Maybe you can help me with this. Thanks. I hope you don't mind.
Click to expand...
Click to collapse
We don't know what your doing, what you tried, or why it didn't work, because we can't see you or what your doing.
You need to post in a coherent straight forward manor.
I would use the manual version, so you can see what errors occur more easily.
Make sure you have the right files for your version, and understand this:
http://forum.xda-developers.com/moto-x/general/info-warning-risks-downgrading-impacts-t3058202
copy and paste the terminal output here using code tags.
Click to expand...
Click to collapse
You have been asked multiple times for the exact error messages. We don't know why your computer wont work... But your computer pretty much tells you each time with a specific message. You need to give us those messages.
Consider the fact that there MAY be someone here who doesn't care about you or your phone, but knows the answer. If you make it easy that person MAY help you. If you post paragraph after paragraph of text describing the error message, rather then the 1 line error message they probably wont read. Be as direct as possible, show us what you have done (I didn't really flow many of you links, why should we have to chase down this information to give you free tech support?)
Like this:
I am trying to fix a phone for a friend. Upon boot I get continuous force closes from a variety of different apps. I am left with a crashed an unusable system.
I have tried to flash _____ rom using _____ tool, but recivied the following error message
Code:
word for word error message
I found this thread: http://forum.xda-developers.com/moto-x/general/guide-moto-x-return-to-100-stock-using-t2446515 on returning to stock using RDS light, and used
RETAIL-US_4.4.4_KXA21.12-L1.29.1_2_cid9_CFC_1FF.xml.zip from http://motofirmware.center/files/category/9-ghost/
There was an error durring fasboot, and there seem to be no changes to the phone.
Code:
130 [email protected] ~ % fastboot oem fb_mode_set :(
< waiting for device >
^C
130 [email protected] ~ %
Click to expand...
Click to collapse
Someone can drop in, and with out much work tell what I have done, and see that it is not working because fastboot cannot find the device.
scryan said:
We don't know what your doing, what you tried, or why it didn't work, because we can't see you or what your doing.
You need to post in a coherent straight forward manor.
I am not sure why you follow other peoples tutorials, then ask US about them. For help with your tutorial, ask the people who wrote that tutorial. If you want help here, try first with OUR tutorials. I don't say this to be mean, but we are unfamiliar with other tutorials and can only really support ours.... It gives us a standard to reference back to.
From the first page, "Returning to 100% stock with RDS or manual"
http://forum.xda-developers.com/moto-x/general/guide-moto-x-return-to-100-stock-using-t2446515
I would use the manual version, so you can see what errors occur more easily.
Make sure you have the right files for your version, and understand this:
http://forum.xda-developers.com/moto-x/general/info-warning-risks-downgrading-impacts-t3058202 about downgrading, shouldn't be an issue but not a bad idea to double check what bootloader you have.
Also make SURE you have the right firmware.
Read those threads, and if you still have an issue copy and paste the terminal output here using code tags.
Rather then downloading it from random websites, you know Moto hosts the official firmwares, at least for DE phones on their website so you can get the most recent, verified version direct from the official source rather then going through random unofficial mirrors...
Click to expand...
Click to collapse
Actually mate, i have been using that link only. But when that didn't worked. I tried others. :l But they failed too. This link shown perfect method. But i have no idea why it's keep happening. This seems more confusing that flashing ROMs on my Canvas HD. It was easy. But this is getting crazy. Please help me with this. I tried from fresh. But it's still same. Maybe you could help me with team viewer or something? Plus one thing i would like to tell you. On most tutorials they said, delete a line "<step operation="getvar" var="max-download-size" />" even it's written in that link too, which you posted. But thing is that, i extracted my firmware, and it's already not in XML file. So.. i am confused with all this. Maybe you can help me with this. Thanks. I hope you don't mind.
You have a locked bootloader, your not just flashing a rom, you need to use fastboot, a standard android tool, to restore your phone.
Your not going to flash a rom, you will be downloading that SBF you have been linked to, unzipping it and flashing each partition, AS STATED IN THE RSD THREAD.
DarKrypton said:
So.. i am confused with all this. Maybe you can help me with this. Thanks. I hope you don't mind.
Click to expand...
Click to collapse
We don't know what your doing, what you tried, or why it didn't work, because we can't see you or what your doing.
You need to post in a coherent straight forward manor.
I would use the manual version, so you can see what errors occur more easily.
Make sure you have the right files for your version, and understand this:
http://forum.xda-developers.com/moto-x/general/info-warning-risks-downgrading-impacts-t3058202
copy and paste the terminal output here using code tags.
Click to expand...
Click to collapse
You have been asked multiple times for the exact error messages. We don't know why your computer wont work... But your computer pretty much tells you each time with a specific message. You need to give us those messages.
Consider the fact that there MAY be someone here who doesn't care about you or your phone, but knows the answer. If you make it easy that person MAY help you. If you post paragraph after paragraph of text describing the error message, rather then the 1 line error message they probably wont read. Be as direct as possible, show us what you have done (I didn't really flow many of you links, why should we have to chase down this information to give you free tech support?)
Like this:
I am trying to fix a phone for a friend. Upon boot I get continuous force closes from a variety of different apps. I am left with a crashed an unusable system.
I have tried to flash _____ rom using _____ tool, but recivied the following error message
Code:
word for word error message
I found this thread: http://forum.xda-developers.com/moto-x/general/guide-moto-x-return-to-100-stock-using-t2446515 on returning to stock using RDS light, and used
RETAIL-US_4.4.4_KXA21.12-L1.29.1_2_cid9_CFC_1FF.xml.zip from http://motofirmware.center/files/category/9-ghost/
There was an error durring fasboot, and there seem to be no changes to the phone.
Code:
130 [email protected] ~ % fastboot oem fb_mode_set :(
< waiting for device >
^C
130 [email protected] ~ %
Click to expand...
Click to collapse
Someone can drop in, and with out much work tell what I have done, and see that it is not working because fastboot cannot find the device.
Ok, let me clear everything to you.
I am trying to fix a phone for a friend. Upon boot I get continuous force closes from a variety of different apps. I am left with a crashed an unusable system.
I have tried to flash Moto X XT1052 (XT1052_RETAIL-ASIA_4.4.4_KXA21.12-L1.26_18_cid7_CFC_1FF.xml) rom posted above by "athulele" using "fastboot" tool, but recivied the following error message. This is first error, with fresh installing. Trying with first command. "fastboot oem fb_mode_set"
Code:
"fastboot" is not recognized as an internal or external command, operable program or batch file.
It's obviously because "fastboot" and ADB are not present in ROM folder. So i guess i need to copy all files from a software i installed "Minimal ADB and Fastboot" as per other tutorials. Which made me more confused. So i want to go with your tutorial.
Second thing, if i make copy of files in ROM folder. It starts taking commands, but with another error. Which is :
Code:
C:\Users\(Username)\Desktop\XT1052_RETAIL-ASIA_4.4.4_KXA21.12-L1.26_18_cid7_CFC_1FF.x
ml>fastboot flash partition fpt.bin
(bootloader) Variable not supported!
target reported max download size of 805306368 bytes
error: cannot load 'fpt.bin': No error
After that, i think i should not continue. After this maybe please take a look. Let me know where i am doing wrong. Must be totally wrong where i copied those files in ROM folder. I couldn't continue without them. Because of that error. Let me know if i am missing any driver. Because as fasr i know i installed all latest drivers. Let me know. Thanks.
Click to expand...
Click to collapse
DarKrypton said:
Ok, let me clear everything to you.
Click to expand...
Click to collapse
Try the commands without "fastboot OEM mode set". Also if your friend had completely stock system, you can try flashing only system.img, boot.img, recovery.IMG
After you flash this, erase data by " fastboot erase userdata" this will erase everything including sdcard .
After that "fastboot erase modemst1" and "fastboot erase modemst2" to clear modem cache. Then try rebooting into system.
Also, you had typed fpt instead of gpt. That's why you got the error
Sent from my Moto X using XDA Free mobile app
athulele said:
Try the commands without "fastboot OEM mode set". Also if your friend had completely stock system, you can try flashing only system.img, boot.img, recovery.IMG
After you flash this, erase data by " fastboot erase userdata" this will erase everything including sdcard .
After that "fastboot erase modemst1" and "fastboot erase modemst2" to clear modem cache. Then try rebooting into system.
Also, you had typed fpt instead of gpt. That's why you got the error
Sent from my Moto X using XDA Free mobile app
Click to expand...
Click to collapse
No no, sorry my bad. Typing mistake here. I did gpt.bin. This time i did mistake, that's why got "error: cannot load 'fpt.bin'". Otherwise it's only "(bootloader) Variable not supported!" And status at end "OKAY" then next command. And i can't take risk for flashing few files only. Because my friend have no idea on this. It's all on me, what can be done. I need to flash full ROM to match up future OTA updates. It's somewhere wrong in copying files in ROM folder. I tried those commands, as per tutorial. So it didn't worked. :l
DarKrypton said:
No no, sorry my bad. Typing mistake here. I did gpt.bin. This time i did mistake, that's why got "error: cannot load 'fpt.bin'". Otherwise it's only "(bootloader) Variable not supported!" And status at end "OKAY" then next command. And i can't take risk for flashing few files only. Because my friend have no idea on this. It's all on me, what can be done. I need to flash full ROM to match up future OTA updates. It's somewhere wrong in copying files in ROM folder. I tried those commands, as per tutorial. So it didn't worked. :l
Click to expand...
Click to collapse
I don't exactly know whether you need an unlocked bootloader to flash via fastboot. But if you don't want to, then you can try factory reset from stock recovery or from the bootloader. There's plenty of guides all around for stock recovery.
Sent from my Moto X using XDA Free mobile app
athulele said:
I don't exactly know whether you need an unlocked bootloader to flash via fastboot. But if you don't want to, then you can try factory reset from stock recovery or from the bootloader. There's plenty of guides all around for stock recovery.
Sent from my Moto X using XDA Free mobile app
Click to expand...
Click to collapse
Naw, fastboot works with locked boot loader. It should be able to reflash on locked as long as the files are signed.
athulele, I think he said he tried factory reset...
Dark, your correct that you need to be in the same directory as that fastboot command (note there is also a mfastboot command. Motorola modified the stock android fastboot tool so it could flash larger partitions, at least from my understanding). If your not in the directory that executable is your OS will not be able to find it (unless you add it to your systems path, but if you don't know how or what that is easier to just make sure the EXE is in the folder your working out of)
The second time you tried to run it it looked like it worked perfectly right? but the correct command is
Code:
fastboot flash partition gpt.bin
Note the syntax is
fastboot [operation] [partition name] [file], so when you gave it the wrong file it correctly said it can't do it. Everything fine here.
again MAKE SURE your flashing the right files, double check your typing the command correctly (Copy and paste is good, but make sure you don't copy any extra characters at the begining or end of the line before you press enter to run the command)
About the worry over only flashing some paritions: You right to worry, you don't want to do this. HOWEVER, if you have the right files they should work. Go through that list of commands one by one. Figure out why any one command fails and get it to work before moving on... But if your flashing the same thing as is already on the phone, your not going to miss match partitions because your flashing the same version of each partition back over itself just trying to fix what ever one is messed up...
But yeah, make sure you got those files, run through those fastboot commands and post the output here. Copying too much of the console output is probably better then too little.
scryan said:
Naw, fastboot works with locked boot loader. It should be able to reflash on locked as long as the files are signed.
athulele, I think he said he tried factory reset...
Dark, your correct that you need to be in the same directory as that fastboot command (note there is also a mfastboot command. Motorola modified the stock android fastboot tool so it could flash larger partitions, at least from my understanding). If your not in the directory that executable is your OS will not be able to find it (unless you add it to your systems path, but if you don't know how or what that is easier to just make sure the EXE is in the folder your working out of)
The second time you tried to run it it looked like it worked perfectly right? but the correct command is
Code:
fastboot flash partition gpt.bin
Note the syntax is
fastboot [operation] [partition name] [file], so when you gave it the wrong file it correctly said it can't do it. Everything fine here.
again MAKE SURE your flashing the right files, double check your typing the command correctly (Copy and paste is good, but make sure you don't copy any extra characters at the begining or end of the line before you press enter to run the command)
About the worry over only flashing some paritions: You right to worry, you don't want to do this. HOWEVER, if you have the right files they should work. Go through that list of commands one by one. Figure out why any one command fails and get it to work before moving on... But if your flashing the same thing as is already on the phone, your not going to miss match partitions because your flashing the same version of each partition back over itself just trying to fix what ever one is messed up...
But yeah, make sure you got those files, run through those fastboot commands and post the output here. Copying too much of the console output is probably better then too little.
Click to expand...
Click to collapse
One thing i would like to ask mate. I am gonna start fresh installation. From laptop now. I noticed one thing, that on
Code:
"fastboot erase modemst1" and
"fastboot erase modemst2"
commands. On boot screen, it just keep showing
Code:
"erasing modemst1..."
for a long time. Does it take that long, or it gets "done" text in a sec? Let me know. I am starting now. Thanks.
Not sure how long it should take tbh. I would let it run, and give it a good while before worrying about it. Maybe open up some kind of system resource monitor on the side (on your computer) so you can see that things are still happening?
There are definitely times that these types of tools will look like its just sitting there though... It should go through eventually, give 10+ minutes before assuming it is not working.
scryan said:
Not sure how long it should take tbh. I would let it run, and give it a good while before worrying about it. Maybe open up some kind of system resource monitor on the side (on your computer) so you can see that things are still happening?
There are definitely times that these types of tools will look like its just sitting there though... It should go through eventually, give 10+ minutes before assuming it is not working.
Click to expand...
Click to collapse
Alright, i am on that command. I am gonna paste whole console commands. Because i think this time it won't work too. :l After every command it's showing
Code:
<bootloader> Variable not supported!
then "OKAY" like it went correct. Plus can you tell me what exactly my variant name is? I can't figure out, as for that OP, it was VZW. But for me, it must be different. I need it for second last command. Thanks.
EDIT : 25 minutes passed. Still same.
Related
I'm a relatively new user to root, with my htc hero cdma rooted since Feburary 2010, but I've been having some problems as of late with my custom recovery image.
When I try to load the Image from fastboot, I get the error "Wrong or no image," (Among others of the same nature), as fastboot tries to load the image several times, it fails with the same general error. It happens very quickly, so I can't post many details, but if a picture or two is needed for more information, I can provide a few for refrence. I am running Darchdroid 2.6.2, great rom, and I would love to update to the newest image(And Rom). I've tried booting into recovery several times, but it bootloops at the HTC logo. I've tried booting from fastboot and DS updater, but the same bootloop occurs, probably because the error is ongoing at fastboot. I've tried flashing multiple images and from using flashrec, I get a command line error. I've flashed many through command line, and the same error occurs.
Can Anyone help me out, or knows what's going on?
PS: If it helps, I have all of the fastboot device stock, EX: radio is the stock 1.0.4 and the touch panel is the stock touchpanel, etc.
put a new recovery image on your Sdcard.
Code:
adb remount
adb shell
flash_image recovery /sdcard/recovery.img
See what that does for ya.
Broken Root???????
Kcarpenter said:
put a new recovery image on your Sdcard.
Code:
adb remount
adb shell
flash_image recovery /sdcard/recovery.img
See what that does for ya.
Click to expand...
Click to collapse
I tried it, but unfortunately, it didn't work. Instead, the same error came up again several times, and I tried with many different images, even with my last two working images.
Can you ask or message anyone who you know who might know whats going on, and can help me???
Ryoma Echizen said:
Can you ask or message anyone who you know who might know whats going on, and can help me???
Click to expand...
Click to collapse
What error message is it giving when you try to flash a new image?
I would also try a different SD card.
EDIT:
NVM I assume that you are getting the run via adb error.
Try a different card. Your current ROM should have absolutely no effect on nandroids.
Broken Root???????
Kcarpenter said:
What error message is it giving when you try to flash a new image?
I would also try a different SD card.
EDIT:
NVM I assume that you are getting the run via adb error.
Try a different card. Your current ROM should have absolutely no effect on nandroids.
Click to expand...
Click to collapse
Ok I will try it, thanks. That could be the problem, since I switched sd cards recently. I am not getting the run via adb error, I am getting an error on fastboot that says; wrong or no image. My image started to freeze when I tried to flash when I switched sd cards to an 8gb. I will try this, and thanks a lot. I probably wouldn't have thought of this way of solving the problem!
Broken Root???????
Welllll.......
I still can't get the image to work...
Can you give me any help, like direct message anyone who you know who might know how to solve this problem??? The error is as follows: "finding name of image, some element in the said image,"
"Wrong or no image!"
Can you message zenulator or anyone who you know who might be experienced in this problem.
Kcarpenter said:
put a new recovery image on your Sdcard.
Code:
adb remount
adb shell
flash_image recovery /sdcard/recovery.img
See what that does for ya.
Click to expand...
Click to collapse
Do this:
Code:
adb remount
adb shell
cd \sdcard\
flash_image recovery recovery.img
Thats actually what I always have to do for some reason the other does not work.
Broken Root???????
For some reason, I get the same error.
Here are some more specific details (my approximate translation because it went by so fast, and not even the full 15 or so lines, but the gist of it...) :
Checking sdcard...
Opening HCTDIAG.zip...
No image!
checking HCTDIAG.nhb...
Wrong or no image!
If you think the log would help, I can email or message it to you. I have been trying all kinds of commands for the last three hours, and no luck...
If anyone knows any solution to my problem, it would be a great help...
ADB works fine, anyway, so I don't think that's the problem.
Broken Root???????
Anyways, if it helps, I'm just trying to get back to the damagecontrol 2.1 stock sprint leaked rom. I might be able to get away with a wipe and then leaving the only data on my sdcard as the backup from the stock sprint leaked. I don't mind any method, as long as I can get back to default and sense, I'll even take the official update with the low ram of 40 mb, rather then 80.
Best advice right now is to start over. Run the ruu, then reroot. It only takes fifteen minutes at most. I know you probably don't want to but sometimes you gotta instead of wasting hours
Broken Root???????
There may be one error though...
When I try to install apks (I have a mac), I get the error as follows, ex: can't find Browser.apk to install.
Maybe has to be in the operating system area, not sdcard?
Anyways, forget about this. I just need to get a working recovery image. Any advice on how to access recovery via adb, like maybe, "reboot recovery" though I doubt this will work, considering that it is just another way to boot into my broken recovery mode w/out an image, or the apparent, "wrong image!"
Broken Root???????
How do I do this, since I am running a rom that doesn't have htc sync??? Should I factory data reset and place a backup folder w/stock sprint 2.1 leaked on the sdcard so the boot will retrieve that and boot that data, since the whole operating system is extracted onto that backup? I don't really know how to run ruu's, and I don't want to run the risk of bricking my phone.
(Running darchdroid 2.6.2, and I do not blame darch for my current situation, just trying to avoid any misunderstandings there.) (O.O)
Broken Root???????
Sorry about the situation I'm in. Definitely the worst possible situation, and I really, really appriciate any help that anyone is willing to provide me.I'm clearly in a sticky situation...
go here and download the sprint hero 2.27.651.5 ruu. You need htc sync get that from sprint site in support and downloads. First run the sync then run the ruu exe with your phone plugged in and usb debugging turned on. Actually just follow the root guide from regaw
I found another way, it worked for me:
http://forum.xda-developers.com/showpost.php?p=6879703&postcount=953
Just realized you were on MAC I don't know much bout that but I have heard you can dualboot it with windows. Definitely something you want to do if you can and plan on messing with android
-------------------------------------
Sent via the XDA Tapatalk App
Broken Root???????
Well, I do have a windows vista laptop.
However, the sprint support section of the site is down for repairs, (TT.TT) so I can't download htc sync for the moment...
Broken Root???????
YESSSSSSS
The clockwork recovery option worked!!!
Special thanks to davec1234 for providing a working solution!!!
Thanks to thatguydid for providing another solution, and thanks to everyone who has replied to my problem that I created this thread to solve.
Just in case anyone else has this problem, then try clockwork recovery, and I think that Rom Manager is a great app from the market that helped me fix my problem, as well as improve my device speed and fixed my permissions to slow down force closes.
THANKS TO EVERYONE ON XDA WHO PARTICIPATES AND MAKES THIS FORUM GREAT!!!
I couldn't ever have fixed my problem without everyone's help!!!
STAY AWAY from GOD SPEED
i thought it was cool but it wouldnt let me flash new recoverys and froze phone after nandroideds on cm6... i also think it wouldnt let me flash the newest zen exp but im testing the above posts method
Okay, so now we have 3 Atrix HD's in the house and except for the unremoveable battery thing, and the short "battery life" when actively using it, I'd say we pretty much love them. However, I decided to remove some apps, etc. and managed to get my messages, camera and gallery to the "not working" and basically non-existent point. Now on startup I'm getting the Android is Updating message with the never-ending swirl of Starting Apps... I'm positive I've waited long enough as I set it down and went back to bed just to wake up and still see it.
Info - phone IS rooted
running the "jellybean" update
Unfortuanately a couple weeks ago, I UNCHECKED the sync photots for both facebook and gmail, so there are pictures I really don't want to lose.....
I'm definitely not a "pro" like lots of them up here, but am capable of following directions. I'm pretty sure I have to "unroot" my phone via USB/SD card through my laptop....Any help would be greatly appreciated... and the more specific the directions the better!! :cyclops: LOL... Thanks so much.
/COLOR]
Sounds like you deleted a critical OS file. You need to flash back to stock again. Is your boot loader locked or unlocked?
Don't remeber...
ai6908 said:
Sounds like you deleted a critical OS file. You need to flash back to stock again. Is your boot loader locked or unlocked?
Click to expand...
Click to collapse
I Don't rememer if I unlocked the bootloader. Is there a way to check? Thanks.
Follow what's in the website to reload your stock image...
http://www.andromods.com/tips-trick...-qinara-stock-original-firmware-fastboot.html
ai6908 said:
Follow what's in the website to reload your stock image...
http://www.andromods.com/tips-trick...-qinara-stock-original-firmware-fastboot.html
Click to expand...
Click to collapse
I've been trying and I've fallowed everything to the T but everytime it says it falls.
I'm not sure...I have used it before and was able to restore...are you sure it's not a hardware issue?
Sent from my HTC_Flyer_P512_NA using xda app-developers app
Okay, here's where we're at.... it is no longer frozen on that screen and goes thru the setup w/ my gmail, etc.... but then I have a black screen (except for the top row icons...). I can pull down the settings menu and see everything there, but I have no "homescreen"....It's black. It seems like we're in the right direction and I know it's not dead. Anything??
Also wanted to thank you for the help. This place is ALWAYS amazing....
Hey, my son and I are wondering since it's already running 4.1.1 and we can't downgrade, what about flashing a custom rom? Will that flash a totally complete, full home page and everything?? Just a thought.
While trying to search for answers I came across a "xoom forums??" post with a tablet that was doing exactly the same thing....multiple people had that problem, but doesn't seem to have been answered...... not sure if I'm suppose to post links to that or not, but at least I know I'm not alone.....
If you're rooted, than I'm assuming ADB debugging is on. You should be able to unlock your boot loader and load CWM recovery. From there you can wipe cache and dalvik cache. If that doesn't help, you can reflash a stock ROM zip from Skeevys thread. Flashing a zip won't touch your SD card
There is official 4.1.1 available...you can try flashing that...you dont need to downgrade.
Okay, my son installed safetystrap (whatever that is...lol) and when you click Operating system, it says "there is no operating system installed are you sure you want to reboot????
Is this fixable?
Note: We have two other identical Atrix HD's in the house if that helps for any reason.....
Well that's what we are trying to figure out is how to install OS...Lol..
Try install system using fastboot... Look for skeevedudes guide...its in this forum somewhere...
Sent from my MB886 using xda premium
LOL....okay, so do yoiu see why my son says I'm not "ALLOWED" to have a rooted phone if this happens again..... Guess I was just glad to SEE it written out, so that it's a little more def what's going on - but I'm sure everyone up here (except me) already knew that!!!
He's not around today, so my phone is just "sitting" saying "creating rom slot" but never gets off that screen. The good thing is that we can see it's actually charging and we weren't sure before....... Does this sound like something that will eventually be repairable??
You have a soft brick...yes it is fixable...
Okay, thought I had already posted this before but I guess I never hit the submit ....
Before safety strap was installed, we could get the phone (minus the homescreen and os) to come on....the settings, wifi etc.....No we can't seem to get to that point with the safetystrap on. It just goes completely blank and won't let safestrap connect to the computer via usb.
Apparently there is also no way to remove SS without an opperating system. This doesn't sound promising.....ugggg..... I so want my phone back.
Any help would be greatly appreciated.
OK dude. Follow my instructions.
Hold down power and both volume buttons all at once until the phone screen turns black, then continue holding the volume buttons. You will get a menu. Go to AP fastboot mode using the volume down button, select it with the volume up button. Plug your phone into your computer with a data cable. Download RSD lite and the MOTOROLA drivers from the MOTOROLA website. Install both. Download the 4.1.1 sbf file for your phone, there is a thread for it here in the AHD forum. Its a zip file, extract it to your desktop. Open RSD lite, click the browse for file button, select the XML file inside the folder you just unzipped. Hit flash. If you get any errors, let me know I'll send you a different XML file with the getvar lines removed.
Okay, will get it started..... Thanks so much. My son has been working on this for hours and hours. You have no idea how much I appreciate this place and everyone who helps out!! You guys rock! Will let you know what we get.
Here is the website for what youngunn mentioned...
http://www.andromods.com/tips-trick...-qinara-stock-original-firmware-fastboot.html
[FONT="Comic [SIZE="3"]Okay, my son (BlackestPain) is too new here to post the picture links, so I copied and pasted. They're just downloads from his camera pictures. This is where we are right now after following suggestions....[/SIZE]MS"][/FONT]
Okay, here is what I've (chixwithkidz5' son) tried.... Please cut me some slack because I haven't been doing this stuff long....
Getvar file
Getvar removed
RSD Lite connected
RSD Lite failed
\
***** this is what the phone reads after everything
What am I missing ? Thanks - I can use all the decent help I can get.
I have a Verizon DE moto x that has twrp recovery. My active display keeps getting stuck when I get a notification, so I think I need to flash (or however it must be done) a fresh rooted stock copy. Where can I find info on how to do this?
Sent from my XT1060
Since you aren't downgrading or anything, you won't have to worry about the bootloader, so just grab the Verizon 4.4 SBF and follow the instructions
mastarifla said:
Since you aren't downgrading or anything, you won't have to worry about the bootloader, so just grab the Verizon 4.4 SBF and follow the instructions
Click to expand...
Click to collapse
What is the difference between flashing firmware and flashing factory images?
Cozume said:
What is the difference between flashing firmware and flashing factory images?
Click to expand...
Click to collapse
As far as I know, the only verifiable "factory images" are the Developer Edition ones that Moto hosts on their personal website.
The SBF may/may not be official factory images. However, they are essentially accepted by the community as the next best thing, mainly because the zips follow the rules set by RSD Lite (Insider Moto Tool) and help prevent bad flashes/user error.
Flashing the SBF firmware manually (via fastboot commands) can raise a few problems of its own, if you don't know what you are doing you can cause serious damage to your device, which is why it is safer to use something like RSD Lite. If you are manually flashing, there is no "check" to verify that you installed them in the correct order or that you flashed all the files without missing anything. Therefore, it is much more risky, please know what you are doing if you plan on flashing this way.
mastarifla said:
As far as I know, the only verifiable "factory images" are the Developer Edition ones that Moto hosts on their personal website.
The SBF may/may not be official factory images. However, they are essentially accepted by the community as the next best thing, mainly because the zips follow the rules set by RSD Lite (Insider Moto Tool) and help prevent bad flashes/user error.
Flashing the SBF firmware manually (via fastboot commands) can raise a few problems of its own, if you don't know what you are doing you can cause serious damage to your device, which is why it is safer to use something like RSD Lite. If you are manually flashing, there is no "check" to verify that you installed them in the correct order or that you flashed all the files without missing anything. Therefore, it is much more risky, please know what you are doing if you plan on flashing this way.
Click to expand...
Click to collapse
Just to clarify. Using the rsd lite method will not mess with the boot loader nor the /media folder correct?
Sent from my XT1060
Swimboy46163 said:
Just to clarify. Using the rsd lite method will not mess with the boot loader nor the /media folder correct?
Sent from my XT1060
Click to expand...
Click to collapse
Depends on if you edit the xml file or not. The bootloader will be flashed by default and data will be wiped by default. It's been a while since I've used RSD but I think when it wipes /data it wipes everything (i.e. including /media). That being said, you could always take those steps out of the xml file.
piccit said:
Depends on if you edit the xml file or not. The bootloader will be flashed by default and data will be wiped by default. It's been a while since I've used RSD but I think when it wipes /data it wipes everything (i.e. including /media). That being said, you could always take those steps out of the xml file.
Click to expand...
Click to collapse
Will this work? http://www.youtube.com/watch?v=gDJvZe7_s0E
While yes it will work I would suggest learning HOW it works, take a look at the steps it goes through and see what is happening, don't rely on these kinds of tools, because they become useless if something bad happens. However, if you look at and modify the XML, it is literally only taking out a few lines of code, but if you want an automated version, then use the tool.
mastarifla said:
While yes it will work I would suggest learning HOW it works, take a look at the steps it goes through and see what is happening, don't rely on these kinds of tools, because they become useless if something bad happens. However, if you look at and modify the XML, it is literally only taking out a few lines of code, but if you want an automated version, then use the tool.
Click to expand...
Click to collapse
I can never get adb to run in command prompt. Mostly because windows is different from Mac.
Sent from my XT1060
Swimboy46163 said:
I can never get adb to run in command prompt. Mostly because windows is different from Mac.
Click to expand...
Click to collapse
I have a Windows 7 machine and I can never get adb to run in a command prompt, either. I have a driver problem.
I can only use mfastboot to do anything unless I can fix my driver problem.
Swimboy46163 said:
I can never get adb to run in command prompt. Mostly because windows is different from Mac.
Sent from my XT1060
Click to expand...
Click to collapse
There are a few tutorials for setting it up correctly, I'm not sure that you need the full SDK in order to do this, but I guess it's nice to have anyways. Try reading up a bit about it, I'm sure you can get it running in no time , after that you'll be much more familiar with these kinds of things.
OP, are you on 4.4? if so, then you don't have to worry about the bootloader. Just download the most current factory image from Motorola. The instructions for flashing the factory images are on their website. Go to www.motorola.com, go to the bottom of the page and click on "Developers". Its the same page you went to in order to get the bootloader unlock code. You have to request the factory image, and Motorola will email you a link, or there's several links to it floating around here.
The factory image will have the same bootlaoder version as you have installed as long as your are flashing the same OS version. It won't relock your bootloader, but you will lose root until you flash TWRP recovery. as far as the media partition, just back up your sdcard partition to your computer before flashing the factory image.
Here's the steps:
1. Plug your MX into the computer and back up all files you want to keep (photos, music, videos, downloads, etc...)
2. Download the 4.4 factory image from the source of your choice (If you don't get it from Motorola, make 100% sure you are downloading the correct file)
3. Make sure you have ADB and fastboot set up properly (and make sure you use the motorola fastboot (mfastboot.exe), bot the Google version)
4. Unzip the factory image and place all the files into the same folder as your adb and fastboot files.
5. Boot your MX into fastboot mode (power off, then hold all three buttons for approx 5 seconds and release)
6. Flash the files using mfastboot, and following the order provided in the included xml file.
7. Reboot.
8. Set your phone up and then restore the files you backed up to your computer
9. If you want root, then you will have to go back to fastboot and flash the TWRP recovery and let it install SuperSU.
10. Finally, PLEASE, make a nandroid back up once you have everything set up and before you make any alterations to it.
Thanks guys! The toolkit actually did the trick for me I was being lazy today lol
Sent from my XT1060 using Tapatalk
Swimboy46163 said:
Thanks guys! The toolkit actually did the trick for me I was being lazy today lol
Sent from my XT1060 using Tapatalk
Click to expand...
Click to collapse
Thanks buddy for ruining it for everybody. If you would stop being on your rag and complaining like a girl none if this would have happened. Look at what you did little girl.
MOTO X Slapped
Some background...Rooted and unlocked. I removed encryption right after I bought it.
I attempted to flash 5.1 the update. I flashed the bootloader and radio first, and rebooted the bootloader. Everything went fine until I tried to flash the system image. I got a lot of "sparse" errors.
When it rebooted it re-encrypted the device. But now nothing works. Phone, NFC ect shows errors. I can get into the bootoader, and I can flash stuff, but the recovery menu is gone,. It's just an error icon with "no connection" now.
Any ideas on how I can salvage this? I already backed everything up before I started. Is there a way I can just wipe everything and go back to stock? Even if it is 5.01?
EDIT - My bootloader is still showing as unlocked. I did not re-lock it.
JeffDenver said:
Some background...Rooted and unlocked. I removed encryption right after I bought it.
I attempted to flash 5.1 the update. I flashed the bootloader and radio first, and rebooted the bootloader. Everything went fine until I tried to flash the system image. I got a lot of "sparse" errors.
When it rebooted it re-encrypted the device. But now nothing works. Phone, NFC ect shows errors. I can get into the bootoader, and I can flash stuff, but the recovery menu is gone,. It's just an error icon with "no connection" now.
Any ideas on how I can salvage this? I already backed everything up before I started. Is there a way I can just wipe everything and go back to stock? Even if it is 5.01?
EDIT - My bootloader is still showing as unlocked. I did not re-lock it.
Click to expand...
Click to collapse
Install factory images using fastboot
https://developers.google.com/android/nexus/images
You might have "soft bricked" it, but if you still have bootloader access you are fine
I actually tried that, but it will not recognize it from ADB...I can flash stuff via fastboot, but ADB does not see it.
I did fully update the android SDK before I started. Should'nt that have updated all the drivers needed for ADB?
JeffDenver said:
I actually tried that, but it will not recognize it from ADB...I can flash stuff via fastboot, but ADB does not see it.
I did fully update the android SDK before I started. Should'nt that have updated all the drivers needed for ADB?
Click to expand...
Click to collapse
you update via fastboot, while youre in the bootloader. adb has nothing to do with it.
When I go to the platform tools folder, and use "adb devices", it tells me nothing after "list of devices attached". As if it does not see the phone.
When I attempt to "fastboot -w update image-shamu-lmy47d.zip", a window comes up and scrolls 3 or 4 lines too fast to see, and then exits. Nothing happens.
JeffDenver said:
When I go to the platform tools folder, and use "adb devices", it tells me nothing after "list of devices attached". As if it does not see the phone.
Click to expand...
Click to collapse
Have you updated the SDK? Drivers installed? Also, read up on how to use fastboot. Fastboot only works from bootloader, not when booted into Android.
I'm all for adb, but save yourself a headache and get wugs toolkit and use force flash.
Sent from my Nexus 6 using XDA Free mobile app
Better to learn some basics first then you shall fear no soft brick ever!
http://forum.xda-developers.com/showthread.php?t=2277112
Evolution_Freak said:
Have you updated the SDK? Drivers installed? Also, read up on how to use fastboot. Fastboot only works from bootloader, not when booted into Android.
Click to expand...
Click to collapse
SDK is updated. I assumed it updated drivers as well. If not, where do I get those?
I do understand that fastboot only works while in the bootloader. I have not attempted to use it while in Android.
JeffDenver said:
When I attempt to "fastboot -w update image-shamu-lmy47d.zip", a window comes up and scrolls 3 or 4 lines too fast to see, and then exits. Nothing happens.
Click to expand...
Click to collapse
Just extract the .zip and flash the things inside separately using fastboot. You can skip user data I believe (or not if you don't care about erasing your device). Using the -w switch would have erased it anyway. The commands are easy, just "fastboot flash system system.img" and the like. Change "system" and "system.img" for the file you're flashing.
Evolution_Freak said:
Have you updated the SDK? Drivers installed? Also, read up on how to use fastboot. Fastboot only works from bootloader, not when booted into Android.
Click to expand...
Click to collapse
Konfuzion said:
I'm all for adb, but save yourself a headache and get wugs toolkit and use force flash.
Sent from my Nexus 6 using XDA Free mobile app
Click to expand...
Click to collapse
Where do I get that from?
JeffDenver said:
Where do I get that from?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?p=56913254
Sent from my Nexus 6 using XDA Free mobile app
---------- Post added at 12:56 PM ---------- Previous post was at 12:55 PM ----------
Evolution_Freak said:
Better to learn some basics first then you shall fear no soft brick ever!
http://forum.xda-developers.com/showthread.php?t=2277112
Click to expand...
Click to collapse
Better fear the bootloader downgrade soft brick
Sent from my Nexus 6 using XDA Free mobile app
Konfuzion said:
I'm all for adb, but save yourself a headache and get wugs toolkit and use force flash.
Sent from my Nexus 6 using XDA Free mobile app
Click to expand...
Click to collapse
Are you sure you know what adb is?
:/
rootSU said:
Are you sure you know what adb is?
:/
Click to expand...
Click to collapse
What's it to you? Yeah I'm fine with adb thanks. If you want to discuss something other than helping the OP go ahead and pm me.
Sent from my Nexus 6 using XDA Free mobile app
mwalt2 said:
Just extract the .zip and flash the things inside separately using fastboot. You can skip user data I believe (or not if you don't care about erasing your device). Using the -w switch would have erased it anyway. The commands are easy, just "fastboot flash system system.img" and the like. Change "system" and "system.img" for the file you're flashing.
Click to expand...
Click to collapse
Ok, I did this. It appeared to work correctly, but...
My phone looks like it did before. In "about" I see it shows 5.1 as the version. I have lost root. Shouldn't I be reset to factory appearance since I overwrote the entire system? Everything looks intact, including nova launcher.
Phone appears to be working normally. I am on the phone on hold as I type this. I am just worried about problems down the road. Do I need to flash anything else? Can I assume the bootloader and radio installed correctly?
Konfuzion said:
What's it to you? Yeah I'm fine with adb thanks. If you want to discuss something other than helping the OP go ahead and pm me.
Sent from my Nexus 6 using XDA Free mobile app
Click to expand...
Click to collapse
Its just you mentioned a toolkit as an alternative to adb but adb has nothing to do with any of this so if you're going to be helping the OP, I thought I'd better check that you know what you're talking about. ...which I don't think you do... So back to the point, how I'm helping the OP is by telling him to ignore everything you say. THAT'S "what's it" to me. Cheeky chops
@JeffDenver, ignore this guy. Use fastboot. Read general > all in one guide > question 28 for any info you may need, including drivers.
to repeat again, you use fastboot to flash the factory img, while youre in the bootloader. it should take you just several minutes to do, or a little bit longer if you are being very carefull. adb has nothing to do with it.
JeffDenver said:
Ok, I did this. It appeared to work correctly, but...
My phone looks like it did before. In "about" I see it shows 5.1 as the version. I have lost root. Shouldn't I be reset to factory appearance since I overwrote the entire system? Everything looks intact, including nova launcher.
Phone appears to be working normally. I am on the phone on hold as I type this. I am just worried about problems down the road. Do I need to flash anything else? Can I assume the bootloader and radio installed correctly?
Click to expand...
Click to collapse
its probably a good idea to factory reset since you're going up a major version and have already had problems.
rootSU said:
Its just you mentioned a toolkit as an alternative to adb but adb has nothing to do with any of this so if you're going to be helping the OP, I thought I'd better check that you know what you're talking about. ...which I don't think you do... So back to the point, how I'm helping the OP is by telling him to ignore everything you say. THAT'S "what's it" to me. Cheeky chops
@JeffDenver, ignore this guy. Use fastboot. Read general > all in one guide > question 28 for any info you may need, including drivers.
Click to expand...
Click to collapse
The reason I suggested wugs, is the first thing it has you do after installation is walks you through removing old drivers and installing the correct drivers and making sure that the phone is recognized. Then it will download the needed files and check the md5's which would help to avoid further problems.
Sent from my Nexus 6 using XDA Free mobile app
Full stock LVY48H on Fi . I've been wanting to go Marshmallow, but Google hasn't gotten around to sending me the OTA. I found this thread in the General forum and downloaded the appropriate .ZIP, but the contents don't look a bit like the ROM downloads, so fastboot doesn't appear to be an option. How do I put it on?
Download factory image, extract, flash each img file separately except for userdata.
Mostlyhrmlss said:
Full stock LVY48H on Fi . I've been wanting to go Marshmallow, but Google hasn't gotten around to sending me the OTA. I found this thread in the General forum and downloaded the appropriate .ZIP, but the contents don't look a bit like the ROM downloads, so fastboot doesn't appear to be an option. How do I put it on?
Click to expand...
Click to collapse
If your bootloader is unlocked, you can flash it manually in ABD or use that toolkit (for factory image). I did that but it it also wiped my phone, which was fine by me, it needed a good cleaning after flashing updates to another custom 5.1.1 rom over and over again!
@nhizzat: I was thinking that, but I'd only done a factory load that way and wasn't sure if I could do a full version jump without cats and dogs living together and mass hysteria (i.e. having to reload all the personals), so I was happy to find that OTA thread. Shame they didn't bother with practical matters such as what to do with that information.
@Tower1972: Attached is a screenshot of the contents of the ZIP. How would I go about flashing that with ADB?
Mostlyhrmlss said:
@nhizzat: I was thinking that, but I'd only done a factory load that way and wasn't sure if I could do a full version jump without cats and dogs living together and mass hysteria (i.e. having to reload all the personals), so I was happy to find that OTA thread. Shame they didn't bother with practical matters such as what to do with that information.
Click to expand...
Click to collapse
RTFM
Tower1972 said:
If your bootloader is unlocked, you can flash it manually in ABD or use that toolkit (for factory image). I did that but it it also wiped my phone, which was fine by me, it needed a good cleaning after flashing updates to another custom 5.1.1 rom over and over again!
Click to expand...
Click to collapse
when youre giving advice to someone, make sure that its correct. you dont flash anything with adb, you use fastboot. fastboot is different than adb.
@boomerbubba: FTFY: Here's a guide on how to do that. I prefer civility when applicable; my sympathies for whatever is going on in your life to make you want to answer in such a way.
@simms22: Turns out the advice was correct: "adb sideload [OTA file].zip" is the appropriate command to accomplish what I'm after here.
Some strategic Googling found me the answer while I was awaiting responses, here it is for the benefit of anyone who should have the same question. Prollyshooda done that first.
Mostlyhrmlss said:
@boomerbubba: FTFY: Here's a guide on how to do that. I prefer civility when applicable; my sympathies for whatever is going on in your life to make you want to answer in such a way.
@simms22: Turns out the advice was correct: "adb sideload [OTA file].zip" is the appropriate command to accomplish what I'm after here.
Some strategic Googling found me the answer while I was awaiting responses, here it is for the benefit of anyone who should have the same question. Prollyshooda done that first.
Click to expand...
Click to collapse
actually, you were incorrect. you said use adb to manually flash. now you said adb for adb sideload. those are two completely different things. all adb sideload does is move a file from your computer to your phone.
edit.. now you are right, i read your response wrong :angel:
Contrition on the Internet? Whodathunkit! We should get together for a beer, I like your kind of folk.
Mostlyhrmlss said:
Contrition on the Internet? Whodathunkit! We should get together for a beer, I like your kind of folk.
Click to expand...
Click to collapse
contrition is one of the things that pull me down. but its honesty, and the truth. so i stay with it
Mostlyhrmlss said:
@nhizzat: I was thinking that, but I'd only done a factory load that way and wasn't sure if I could do a full version jump without cats and dogs living together and mass hysteria (i.e. having to reload all the personals), so I was happy to find that OTA thread. Shame they didn't bother with practical matters such as what to do with that information.
@Tower1972: Attached is a screenshot of the contents of the ZIP. How would I go about flashing that with ADB?
Click to expand...
Click to collapse
I don't know what zip file that is, but it's not a factory image from Google. If you download a factory image from Google, you extract every img file and flash using fastboot.
What is everyone's fascination with adb sideload?
nhizzat said:
What is everyone's fascination with adb sideload?
Click to expand...
Click to collapse
It doesn't require an unlocked bootloader. Which for the people that haven't done that, it wipes your phone as part of the unlock process.
Also, it is a smaller download if you are on an ISP with limited bandwidth.
Google says....
http://https://developers.google.com/android/nexus/images
That will get you going, but since the included script won't work, you have to unzip the zip package, what you will find inside the parent folder. Happy flashing
nhizzat said:
I don't know what zip file that is, but it's not a factory image from Google. If you download a factory image from Google, you extract every img file and flash using fastboot.
What is everyone's fascination with adb sideload?
Click to expand...
Click to collapse
That ZIP is an OTA downloaded from the thread referenced in my original post. My fascination with adb sideload (now that I know what it is) is that I can accomplish an upgrade with a single command, which suits my advanced case of laziness very well . Seems much easier than unzipping a file, then unzipping a file from that file (more than doubling the storage requirement, I have a rather small SSD) and issuing several fastboot commands with slightly different syntaxes and hoping I didn't miss (or mistype) something.
I already know how to do a full flash, I unlocked the bootloader and did so first thing when I bought it used to make sure it was cleared of the previous owner's data and completely up-to-date. What I wasn't sure of is if it would be safe to do so for a full version jump. I'm much more comfortable with OTAs since I've applied several and it stands to reason that a carrier would never issue one if it might cause an undue number of problems for their support staff to address.
Martend said:
That will get you going, but since the included script won't work...
Click to expand...
Click to collapse
That script just burns my biscuits. Why in the name of all that is neat and groovy can't Google fix such a basic problem?
Mostlyhrmlss said:
That script just burns my biscuits. Why in the name of all that is neat and groovy can't Google fix such a basic problem?
Click to expand...
Click to collapse
because its fixed in the latest version of fastboot, that no one seems to be using..
simms22 said:
because its fixed in the latest version of fastboot, that no one seems to be using..
Click to expand...
Click to collapse
Why break it in the first place? lol It's the first thing you learn here, debug & test before releasing it to the masses
So, I got the latest ADB and FASTBOOT from here, put the device in ADB update mode through recovery mode (already OEM unlocked and USB debugging enabled), ran 'adb sideload <filename>' as instructed onscreen, and got "error: device (null) not found" from the command. The device shows up in the Windows device manager when in bootloader mode, but disappears when I go to recovery mode. What am I doing wrong?
Mostlyhrmlss said:
So, I got the latest ADB and FASTBOOT from here, put the device in ADB update mode through recovery mode (already OEM unlocked and USB debugging enabled), ran 'adb sideload <filename>' as instructed onscreen, and got "error: device (null) not found" from the command. What am I doing wrong?
Click to expand...
Click to collapse
do you have the drivers installed? fastboot wont see your device until then.
I installed the drivers as part of the ADB/FASTBOOT package referenced above, but that's not the problem: the device is not shown at all in the Windows device manager, as if it wasn't plugged in.