Related
yesterday i bought the motorola defy +, first thing i noticed is Wi-Fi problems when creating a motoblur account. i read that it's an incompatibility with some new routers or something, this morning went outside to find unsecure Wi-Fis and create that motoblur account, created it on the 3rd wifi i found and was finally able to access my phone.
but again when i came home, it showed i was connected but it couldn't actually use the internet (Market, Youtube, Browser).
it's a thing i'm concerned about but i think is fixable at the store or fixable when putting a new android version.
i want to upgrade my Defy+ to Android 4
questions:
1)how dangerous is this process?
2)i've read that if you change it from stock ROM, Motoblur bans your account, if so what are the consequences of it.
3) what is Motoblur good for besides the widgets and the social network updates on your home screen?
4)if motoblur doesn't ban the account when upgrading say to android 4. will it be problematic in that version and can i get rid of it?
5)from the store, i got the Defy+ on android 2.3.6, i've read somewhere that the android version you get when you buy it is 2.3.4, was the phone rooted or something? the phone is also set for my countries languages (English, Russian, Hebrew, Arabic) (btw, i'm still very confused about rooting and what it is)
6)i don't wanna ruin the warranty when i upgrade to android 4. I've read that you can just set to the original 2.3.4 and everything will be fine, thing is for me it's 2.3.6 and with different languages than some other places. will i still be fine?
7)if i upgrade to android 4, will i be able to download paid apps for free?
if so, is there anything i need to do extra? are there consequences?
if not, how do i do so? and again, what are the consequences?
8) what is cyanogenmod(CM x (x being a number))
9) is there anything else necessary for a person like me to know?
if i missed some detail please let me know, i tend to miss details or words for some reason.
Thanks a Head a Lot for the time and and answers!
Regards, Confidential.
Cm (cyanogenmod) is an after market customer support rom. It's build by developers in there spare time. It replaces your current rom. No blur, extra functions, fixes for bugs by Motorola...
There is no upgrade to ics (at least not by Motorola). Cm9 (ics) us not yet that stable.
If you want to improve your telephone experience you can look into cm7 (gb, they skipped 8 -> honeycomb) or miui(other look). They don't have blur. There are other apps in the market that do the same. And backup of your contacts is done best with Google.
Verstuurd van mijn MB525 met Tapatalk
yesterday i bought the motorola defy +, first thing i noticed is Wi-Fi problems when creating a motoblur account. i read that it's an incompatibility with some new routers or something, this morning went outside to find unsecure Wi-Fis and create that motoblur account, created it on the 3rd wifi i found and was finally able to access my phone.<br />
but again when i came home, it showed i was connected but it couldn't actually use the internet (Market, Youtube, Browser).<br />
it's a thing i'm concerned about but i think is fixable at the store or fixable when putting a new android version.<br />
<br />
<br />
<br />
i want to upgrade my Defy+ to Android 4<br />
questions:<br />
<br />
1)how dangerous is this process?<br />
<br />
2)i've read that if you change it from stock ROM, Motoblur bans your account, if so what are the consequences of it.<br />
<br />
3) what is Motoblur good for besides the widgets and the social network updates on your home screen?<br />
<br />
4)if motoblur doesn't ban the account when upgrading say to android 4. will it be problematic in that version and can i get rid of it?<br />
<br />
5)from the store, i got the Defy+ on android 2.3.6, i've read somewhere that the android version you get when you buy it is 2.3.4, was the phone rooted or something? the phone is also set for my countries languages (English, Russian, Hebrew, Arabic) (btw, i'm still very confused about rooting and what it is)<br />
<br />
6)i don't wanna ruin the warranty when i upgrade to android 4. I've read that you can just set to the original 2.3.4 and everything will be fine, thing is for me it's 2.3.6 and with different languages than some other places. will i still be fine? <br />
<br />
7)if i upgrade to android 4, will i be able to download paid apps for free?<br />
if so, is there anything i need to do extra? are there consequences?<br />
if not, how do i do so? and again, what are the consequences?<br />
<br />
8) what is cyanogenmod(CM x (x being a number)) <br />
<br />
9) is there anything else necessary for a person like me to know?<br />
<br />
<br />
if i missed some detail please let me know, i tend to miss details or words for some reason.<br />
<br />
Thanks a Head a Lot for the time and and answers!<br />
Regards, Confidential.
Click to expand...
Click to collapse
1) Before you do anything read up on flashing sbfs. These are how motorola updates the phone. If you ever mess up or get stuck you can always flash an sbf and you'll be like new. So there is no real danger.
2)3)4) Most people hate motoblur, so I wouldn't worry about it, if you flash cm there will be no trace of it.
5)6) Sounds like your'e in Israel, they obviously installed their own version of the software to support their languages. Try searching for Israeli sbf.
7) If you mean apps you paid for yes you can redownload them.
9) look through the forums for tutorial and read everything first.
Enjoy youre phone.
Sent from my MB526 using XDA
It is not dangerous, the only dangerous part is flashing sbfs, because if u flash a newer version you can't be able to flash your previous sbf (downgrade). Just flash only the same sbf you have now. Your phone is not rooted, you have to root it. When you root it you will be able to use apps that require root, and to install a custom recovery (u need it to install custom roms). Obviously if it's a paid app you have to pay for it, even on ics. CM7 (gingerbread) is stable, and CM9 (ics) is not stable yet, it has some bugs, but it works really well. The only consequence is flashing a newer bootloader version, defy is hard to brick.
I've been reading a few threads here on XDA... still completely confused about everything...
I'm going to post the process i assume i need to do to get my phone to a nicer version.
and a question before that: will upgrading to a new version fix my Wi-FI problem?
1) rooting:
Get SuperOneClickRoot (can't download it from here: ht tp:// short fuse.org/?p=80 ) (will superoneclick 2.3.3 do the job?)
Get and Install Motorola Drivers [32bits] [64bits]
Reboot your PC
Turn USB Debugging ON (Settings -> Applications -> Development on your Defy)
Connect your Defy to the PC
Wait for the PC to install any missing Drivers
Click on Root
Let it work, then it will ask if you want to install BusyBox, hit YES
After it finished it will ask to make a test, click cancel and just Reboot your Defy
Done, Defy rooted
2) Flashing:
Get the SBF you want to flash
(cyanogenmod 7 or 9 or ICS (i don't mind some of the bugs since i don't use the apps related to them)
Get and Install RSD Lite v4.9 (do i install on PC or phone)
Open RSD Lite: Click on [ … ] Button and select your .SBF (Remember to rename to a short name and put it on root of your PC) and click Open.
Boot your phone into Bootloader Mode (check last section if you don’t know how to do it).
Now connect your Defy to your PC
The START button on RSD Lite should be available now, click and wait.
and to comeback to stock ROM i have no idea how to. something to do with CG versions and i have no idea what it means, do i have to find an ICS/cyanogenmod with the same CG?
again thank you for your replies and future replies!
WIUI
I Tried CM9 and WIUI i Think WIUI is much more stable and offer better perfomance, with a easier UI
On witch android version are you now? (In settings>about). Different defy+ sbf's need different methods. Read the defy beginners guide for info on sbf's etc...
Verstuurd van mijn MB525 met Tapatalk
i have android 2.3.6. i have read that guide and it confused me even more.... about CG. which 1 do i need? (if it makes a difference i have languages that appear most in my country; israel) again, many thanks!
Cyanogenmod is not a sbf. First you have to flash your sbf, and then root your phone. The sbf will be your stock rom, and cm your custom rom (it comes in a .zip flashable with recovery).
You're with 2.3.6.. Most probably CG version 7(Bootloader 7). Don't worry you're already on ' what I should say' Top of the tower right now.There's no jumping back.
For more info about rooting, flashing and SBF etc. go through the guides in the forum..
Doesn't matter from where I send it, what matters is written above
wow i just can't comprehend this process...
if i manage to do this process and some time later i might need the warranty, is there a way to unroot uneverything i've done in my phone assuming i can't get my hands on the sbf that i have on my phone? (or can i somehow save the 1 on my phone)
3 more unrelated questions:
1)i have some sort of scratch or erased part on my Defy+ (which is supposed to withstand almost all). it's on the left side of the screen and if u blow hot air on it (on the whole screen) then you can see borders of the screen and that scratched part, if u move ur finger from the right to the left u feel a bit of roughness on the bordered area.
this is weird, because i haven't even put my phone on the table on the screen, always on it's back. and i'm very paranoid about my phone even though it's supposed to withstand a lot. i have only once lost my phone out of sight through the 3 days i have it, i gave it to a tech guy in the store i bought it in for 5 minutes.
now, how the **** can something like that happen? isn't that gorilla glass? (it's not an even line/border if it matters) and i know it's not dirt because I've rubbed, I've sprayed some LCD cleaner spray, some Window Cleaner, Some alcohol (95%).
2) i heard of 2 ways to download paid apps for free, 4shared.com appplanet (or something) now the questions are: will i get banned on motoblur or android or something like that? will i be still able to use it (4shared/applanet) once i flash my Defy+?
what are the consequences of this?
3)my phone constantly opens apps for no reason! every 5 minutes i have to go into app killer or task killer (forgot the name) to kill all the running apps. if i don't do it every few minutes i will come to find a butt load of apps!!! is this a bug? will this be fixed if i flash my Defy+?
again, many thanks ahead.
Confidential said:
wow i just can't comprehend this process...
if i manage to do this process and some time later i might need the warranty, is there a way to unroot uneverything i've done in my phone assuming i can't get my hands on the sbf that i have on my phone? (or can i somehow save the 1 on my phone)
3 more unrelated questions:
1)i have some sort of scratch or erased part on my Defy+ (which is supposed to withstand almost all). it's on the left side of the screen and if u blow hot air on it (on the whole screen) then you can see borders of the screen and that scratched part, if u move ur finger from the right to the left u feel a bit of roughness on the bordered area.
this is weird, because i haven't even put my phone on the table on the screen, always on it's back. and i'm very paranoid about my phone even though it's supposed to withstand a lot. i have only once lost my phone out of sight through the 3 days i have it, i gave it to a tech guy in the store i bought it in for 5 minutes.
now, how the **** can something like that happen? isn't that gorilla glass? (it's not an even line/border if it matters) and i know it's not dirt because I've rubbed, I've sprayed some LCD cleaner spray, some Window Cleaner, Some alcohol (95%).
2) i heard of 2 ways to download paid apps for free, 4shared.com appplanet (or something) now the questions are: will i get banned on motoblur or android or something like that? will i be still able to use it (4shared/applanet) once i flash my Defy+?
what are the consequences of this?
3)my phone constantly opens apps for no reason! every 5 minutes i have to go into app killer or task killer (forgot the name) to kill all the running apps. if i don't do it every few minutes i will come to find a butt load of apps!!! is this a bug? will this be fixed if i flash my Defy+?
again, many thanks ahead.
Click to expand...
Click to collapse
1. To unroot it you'll need your stock SBF.Look for it, most probably you'll find in the SBF's thread.
2. Gorilla glass is scratch resistant not scratch proof so some minor scratches may appear, better find a good screen-guard.
3.When a developer ask users to pay for the apps, it is because he would've worked real hard for that and the app is worth paying for.I feel its not only illegal bt unethical as well to run pirated apps.
Still if you run any pirated apps, Google or Android or anything else won't block anything.
At most the app may stop wrking if it fails to verify the license.
4.There's a lot of stuff running in the background that invoke the apps you see running.
If you feel some of those are useless and killing those won't affect system working, use Auto-kill from your task manager..
Doesn't matter from where I send it, what matters is written above
about that rough area in the phone.
that screen is supposed to survive keys but can't survive my hand, pocket and shirt (only things the screen came in touch with)?(empty pocket)
and this morning i wake up after last night seeing the rough area one more time before bed. and see a New Rough area, it's a very thin line in the middle right of the screen. (i blew hot air to look at the rough area and saw this) and at night, NOBODY touched it! it's like the screen coating (not sure if it is coating, dunno what it is.) is degrading.
i will buy a screen guard but the thing is that untill then i'm afraid the screen won't be fully intact anymore. (not that it is now...)
Confidential said:
about that rough area in the phone.
that screen is supposed to survive keys but can't survive my hand, pocket and shirt (only things the screen came in touch with)?(empty pocket)
and this morning i wake up after last night seeing the rough area one more time before bed. and see a New Rough area, it's a very thin line in the middle right of the screen. (i blew hot air to look at the rough area and saw this) and at night, NOBODY touched it! it's like the screen coating (not sure if it is coating, dunno what it is.) is degrading.
i will buy a screen guard but the thing is that untill then i'm afraid the screen won't be fully intact anymore. (not that it is now...)
Click to expand...
Click to collapse
The environment around you..Is it quite dusty or does the phone gets in contact with sand particles??
Coz it can survive keys but not sand..
Doesn't matter from where I send it, what matters is written above
i live in the city and i don't recall living in a very dusty house or going to one.
and isn't it dust resistant as well as waterproof?
EDIT:
back on topic of upgrading: i have some apps i cannot uninstall (they came with the phone) will i be able to uninstall them if i install WIUI?
Confidential said:
i live in the city and i don't recall living in a very dusty house or going to one.
and isn't it dust resistant as well as waterproof?
EDIT:
back on topic of upgrading: i have some apps i cannot uninstall (they came with the phone) will i be able to uninstall them if i install WIUI?
Click to expand...
Click to collapse
Sand particles may cause scratches on the glass..however if you feel its serious, get it to the service center..
Some apps are the part of the ROM. If you flash another ROM, those apps won't be present unless they're included in the one you flash.
Doesn't matter from where I send it, what matters is written above
i have a question about DLNA.
i opened up DLNA while on wi-fi saw 2 computers (mine and bros)
i tried connecting to mine (every 1 of the 3 options failed) (share media is enabled)
so i googled how to my computer accesible to DLNA and followed a guide.
(basically enable media sharing...) once i've done that, i checked my Defy+ and my computer was gone from the list, i restored the setting so i will be able to see it again, but i can't! and i can't find anything anywhere about how to make it work.
is there a normal guide for this? has anyone encountered this issue?
Confidential said:
i have a question about DLNA.
i opened up DLNA while on wi-fi saw 2 computers (mine and bros)
i tried connecting to mine (every 1 of the 3 options failed) (share media is enabled)
so i googled how to my computer accesible to DLNA and followed a guide.
(basically enable media sharing...) once i've done that, i checked my Defy+ and my computer was gone from the list, i restored the setting so i will be able to see it again, but i can't! and i can't find anything anywhere about how to make it work.
is there a normal guide for this? has anyone encountered this issue?
Click to expand...
Click to collapse
Can't help you much with that.DLNA is stock rom feat and I've been using custom roms for quite a long now..
Though I'd suggest to clear app data from settings.
Sent from my Defy+ using Tapatalk 2
if i do a nandroid backup, will i be able to use that back up (i have no idea what nandroid back up does so...) to unroot, and return to original SBF? original Flash original everything? and have no warranty issues?
is this the process i need to go through to get WIUI?
Flashing:
1) Put the ROM i want in the SC card (zipped or unzipped?)
2)download and install motorola drivers
3) download and install RSDLite (4.9 if i'm not mistaken?)
4)open RSDLite
5)Enter Bootloader Mode on you phone (Power+VolUp)
6)Connect phone to you PC (USB)
7)Open RSD - Lite
8) Flash new SBF.
(where and when and how do i backup?)
rooting:
1.Download SuperOneClick (2.1.1-shortfuse)
2.Turn On usb debugging mode in your phone.Don't put phone USB mass storage mode.
3.Connect your phone to your pc.
4.Open SuperOneClick as Administrator.
5.Click ROOT and wait. If it asks whether you wish to install Busybox etc, give yes or ok.
6.Once root is complete you will get a pop up asking whether you wish to donate. Make a choice.
7.At last you will find a line on the right side pane saying to reboot. Reboot your phone.
Installing the rom:
1. Download 2ndinit 1.4.2
2. install 2ndinit (Important!:following the instructions)
3. Boot into bootmenu by pressing volume down when device flashes a blue led at bootup. Set default boot mode to 2nd init.
4. Select Recovery/Stable Recovery. Choose "Wipe Data/Cache" option. Let finish.
5. Choose Install zip from SD Card, select WajkIUI_multilang .zip and let it finish.
6. select "Wipe Cache" then go to Advanced and select "Wipe Dalvik Cache". Reboot Now!
7. After boot, set your prefered language in Settings menu
7. Done! Recommend: use Battery Calibration for maximum battery
questions:
1) where does the nandroid backup come in mind?
2) what about that CG stuff? and how do i know my CG and the WIUI CG and how do i know that if i need to unroot it's unrootable./return to stock SBF.
3) i've read somewhere that you need to change some file name to a very short one otherwise it will be brick, also it needs to be in a certain location on the pc/phone?
what file is that?
4) where does the clockwork Manager come in play?
unrelated:
Should i overclock my CPU? (i play games a lot, not sure if every game i plan on downloading will be able to run fluidly with 1 GHZ...)
Many thanks Ahead.
EDIT: i may have found the stock SBF that i need, but i am Very unsure, the download might be broken, it might not be it...
i rather have a few ways to go back than just one.
if i do a nandroid backup, will i be able to use that back up (i have no idea what nandroid back up does so...) to unroot, and return to original SBF? original Flash original everything? and have no warranty issues?
is this the process i need to go through to get WIUI?
Flashing:
1) Put the ROM i want in the SC card (zipped or unzipped?)
2)download and install motorola drivers
3) download and install RSDLite (4.9 if i'm not mistaken?)
4)open RSDLite
5)Enter Bootloader Mode on you phone (Power+VolUp)
6)Connect phone to you PC (USB)
7)Open RSD - Lite
8) Flash new SBF.
(where and when and how do i backup?)
Click to expand...
Click to collapse
Nandroid backup is done when you're flashing a New Custom ROM to your phone through Custom Recovery(Clockwork Mod is A custom Recovery).
The above steps are for flashing A New SBF..
What are SBF's? You'll find the answer here.
Also Read the risks involved with flashing A new SBF.
Installing the rom:
1. Download 2ndinit 1.4.2
2. install 2ndinit (Important!:following the instructions)
3. Boot into bootmenu by pressing volume down when device flashes a blue led at bootup. Set default boot mode to 2nd init.
4. Select Recovery/Stable Recovery. Choose "Wipe Data/Cache" option. Let finish.
5. Choose Install zip from SD Card, select WajkIUI_multilang .zip and let it finish.
6. select "Wipe Cache" then go to Advanced and select "Wipe Dalvik Cache". Reboot Now!
7. After boot, set your prefered language in Settings menu
7. Done! Recommend: use Battery Calibration for maximum battery
Click to expand...
Click to collapse
This is how you flash a Custom ROM, which is a flashable *.zip file
Only thing to add is when you enter stable Recovery(CWM), choose Backup/Restore> Full Backup before step 5.
This is your Nandroid backup
Now get the difference between two methods.
Code:
1.)Flashing A SBF
Flashing A SBF is done through RSDLite using your PC. This is where the CG versions are important.The file is with extension *.sbf placed on your pc at any location.
Code:
2.)Flashing A Custom ROM
Flashing A Custom ROM is done through your Recovery on the device itself. The ROM is a flashable zip placed on you SDcard.Custom ROM's DO NOT ALTER the CG version.
3) i've read somewhere that you need to change some file name to a very short one otherwise it will be brick, also it needs to be in a certain location on the pc/phone?
what file is that?
4) where does the clockwork Manager come in play?
Should i overclock my CPU? (i play games a lot, not sure if every game i plan on downloading will be able to run fluidly with 1 GHZ...)
Click to expand...
Click to collapse
Its the SBF file when flashing through RSDLite.
Its ClockworkMod And it is your Custom/Stable Recovery.
I don't see a need to do so,unless you feel some lags using your phone. 1Ghz is quite high for a device, trust me.
i may have found the stock SBF that i need, but i am Very unsure, the download might be broken, it might not be it...
i rather have a few ways to go back than just one.
Click to expand...
Click to collapse
The only way to unroot it is to flash you stock SBF through RSDLite. Thats the only way. nothing else.
PS: you should read the faq threads etc. Most of the stuff is already answered in detail.
I flashed the Eclipse ROM via safestrap and then restored the Eclipse ROM onto the stock ROM slot. For some stupid reason, instead of restoring the stock ROM slot before resetting the phone back to stock, I opted to use RSD Lite 6.1.4 and tried to flash the JB firmware (yes, I got into fastboot). When I tried to do this, the phone reboots past the Motorola M insignia, to the droid startup screen (with the flashing red light/circle), but does not get past the startup screen (yes, I gave it 30+ minutes to no avail). I also tried to reflash the JB firmware, but no matter what, I ended up stuck at the bootup screen.
For this reason, I tried to flash the ICS firmware instead (per instructions on XDA and other websites, I removed the lines in the XML file that had the word var, getvar, and oem). This did work! However, after RSD flashed the firmware, rather than restarting into the OS, the phone reboots into a black screen w/ the phrase "Fastboot Reason: Sticky bit factory_fastboot" at the very bottom. Anytime I try to restart the phone, it automatically boots into this screen. If I hold the volume up and down buttons, together w/ the power button, I am able to get back to the option to start normally.
When I tried to do the OTA JB update, the phone downloads the necessary files, but when the phone tries to reboot to install the OS update, it goes back into that black screen and does not install the update. Also, when I finally do get back into the OS, the phone then constantly reboots as if it were trying to install the OTA JB update.
Does anyone know what "Fastboot Reason: Sticky bit factory_fastboot" means? Also, if anyone knows how to "fix" this issue, I'd greatly appreciate it. If the fix requires command line work (like in this thread), I'd greatly appreciate if someone could walk me through it step-by-step, as I am not familiar w/ the command line process.
Thanks!
Edit 1: The next step I will try is to get root back on my phone, install Safestrap, and see whether I can flash a backup that I previously had.
Edit 2: In some threads for other Moto phones, there is some discussion regarding using ADB to fastboot/flash the stock ROM. Anyone know how this is different from using RSD? Also, can anyone walk me through HOW to ADB? I have zero knowledge in this regard.
Have you tried holding the buttons down to enter fast boot again and reflash? Worth a shot if you haven't. You could also attempt a factory reset from the boot menu. Maybe the corrupt file would correct itself.
You should definitely take the time to learn some ADB; at least a working understanding. It helps down the road.
Here's a good tutorial on ADB commands. http://mobile.tutsplus.com/tutorials/android/android-adb-quick-guide/
And to install ADB without Android SDK (app production software) http://mobilecon.info/install-adb-in-windows.html
Sent from my Nexus 7 using xda app-developers app
skippid said:
Have you tried holding the buttons down to enter fast boot again and reflash? Worth a shot if you haven't. You could also attempt a factory reset from the boot menu. Maybe the corrupt file would correct itself.
You should definitely take the time to learn some ADB; at least a working understanding. It helps down the road.
Here's a good tutorial on ADB commands. http://mobile.tutsplus.com/tutorials/android/android-adb-quick-guide/
And to install ADB without Android SDK (app production software) http://mobilecon.info/install-adb-in-windows.html
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
Yes, I attempted to reflash on multiple occasions, both using the stock ICS and the stock JB roms. I must have reflashed close to 10x at this point. In any case, no matter how often I have reflahsed (including after doing a factory reset from within the OS as well as from within recovery), I still get the error. The good news is that I was successfully able to flash the JB ROM and have the phone OS actually start up, whereas, a few days ago, it would be stuck at the red circle/eye thing.
Furthermore, I attempted the command fastboot flash system [system.img], and I got the error:
(bootloader) Variable not supported!
target reported max download size of 31457280 bytes
error: cannot load '[system.img]': no error
I saved the system.img in both c:\android, as well as the internal SD card of the phone.
The other good news is that I am still able to use the phone if I get into the boot menu and ask the phone to boot normally. However, I am now unable to get root, and anytime I need to restart the phone, it gives me that error message.
I have also tried the command fastboot reboot bootloader but continue to get the same error message.
OK. Find a JB leak zip or current stock JB zip, access the screen where it asks for AP Fast boot and recovery, choose recovery, then volume up I believe when the phone shows the android with the red exclamation point.. Then choose update with zip. Search your SD card and install. It's worth a try in this manner in case you haven't already.
That's odd that your phone didn't respond well with RSD.
Sent from my XT907 using xda app-developers app
You need to use an updated fastboot binary for the new larger images in these devices.
http://db.tt/AveMC40y
skippid said:
OK. Find a JB leak zip or current stock JB zip, access the screen where it asks for AP Fast boot and recovery, choose recovery, then volume up I believe when the phone shows the android with the red exclamation point.. Then choose update with zip. Search your SD card and install. It's worth a try in this manner in case you haven't already.
That's odd that your phone didn't respond well with RSD.
Sent from my XT907 using xda app-developers app
Click to expand...
Click to collapse
Skippid, thanks for the suggestions. I tried your method as well. Went into recovery, selected to update from external SD (or something to that effect), selected the JB zip file, and let it flash that way. Unfortunately, I still received the same error message regarding the sticky bit factory_fastboot.
cellzealot said:
You need to use an updated fastboot binary for the new larger images in these devices.
http://db.tt/AveMC40y
Click to expand...
Click to collapse
cellzealot, thank you for the link. I've downloaded the file that you linked to. Could you be so kind as to now give me a step-by-step on how to re-attempt the flashing process?
Quick update - I was able to get root back, installed safestrap, and flashed the nandroid that I had made back when I first flashed Eclipse. However, I am still having the same issue:
Whenever I restart the phone, I get the sticky bit factory_fastboot error. If I use the command fastboot continue, the phone boots up as normal; however, it would be great to not have to do this each and every time I reboot the phone. Any help would be greatly appreciated. Thanks!
More updates (still not fixed):
After getting root, I reflashed my nandroid, factory reset (both within the OS and in recovery), and then tried flashing both the ICS and JB stock ROMs. I tried flashing both using mfastboot, as well RSD Lite. The files flash successfully; however, whenever I restart the phone, I continue to get the stick bit factory_fastboot error.
Also, when I get into recovery, I try to flash via "update from external SD". When I do so, recovery simply restarts without flashing the stock ROM.
Here's my last update as to this issue:
After trying all of the methods that I could think of (RSD Lite, flashing via fastboot and mfastboot, flashing from external), the problem did not correct itself.
I brought my phone into a Verizon store, where they told me that they had never seen that problem before. They agreed to replace my phone pursuant to the one-year warranty (I received my phone in December), which I received today. I've again rooted my phone, but have opted to not screw around w/ safestrap and custom ROMs this time around, as I find the stock JB experience to actually be quite good.
Found the soultion!!!!!!
Ok guys so after serching a while I found out similar moto phones have the same issue. I found in a latin forum and in a Droid forum people ponting to the same issue. So the solution that worked for my Razr HD xt925 was:
1) Enter fastboot mode in your phone (very easy since every time you restart the phone you end there anyways)
2) Write this command on the computer: fastboot oem fb_mode_clear
there will be a dialogue with the time take and OK
You are done!
Thought someone might find it useful
Thank you!
cerafio said:
Ok guys so after serching a while I found out similar moto phones have the same issue. I found in a latin forum and in a Droid forum people ponting to the same issue. So the solution that worked for my Razr HD xt925 was:
1) Enter fastboot mode in your phone (very easy since every time you restart the phone you end there anyways)
2) Write this command on the computer: fastboot oem fb_mode_clear
there will be a dialogue with the time take and OK
You are done!
Thought someone might find it useful
Click to expand...
Click to collapse
Thank you! This was the answer I needed after searching and searching trying all the different things for over 3 hours, this 2 second fix worked!
Namanati said:
Thank you! This was the answer I needed after searching and searching trying all the different things for over 3 hours, this 2 second fix worked!
Click to expand...
Click to collapse
#8 > http://forum.xda-developers.com/droid-razr-m/general/guide-faq-how-to-root-boot-unlock-t2869432
ATTACK said:
#8 > http://forum.xda-developers.com/droid-razr-m/general/guide-faq-how-to-root-boot-unlock-t2869432
Click to expand...
Click to collapse
Thanks, but that didn't come up when I googled AP Fastboot: flash failed, and since I didn't get it from rooting or unlocking my phone I didn't think to look for that.
cerafio said:
Ok guys so after serching a while I found out similar moto phones have the same issue. I found in a latin forum and in a Droid forum people ponting to the same issue. So the solution that worked for my Razr HD xt925 was:
1) Enter fastboot mode in your phone (very easy since every time you restart the phone you end there anyways)
2) Write this command on the computer: fastboot oem fb_mode_clear
there will be a dialogue with the time take and OK
You are done!
Thought someone might find it useful
Click to expand...
Click to collapse
Oh my god dude thank you so much. That fixed my bootloader issue that was plaguing me for weeks
Thanks again!!!
cerafio said:
Ok guys so after serching a while I found out similar moto phones have the same issue. I found in a latin forum and in a Droid forum people ponting to the same issue. So the solution that worked for my Razr HD xt925 was:
1) Enter fastboot mode in your phone (very easy since every time you restart the phone you end there anyways)
2) Write this command on the computer: fastboot oem fb_mode_clear
there will be a dialogue with the time take and OK
You are done!
Thought someone might find it useful
Click to expand...
Click to collapse
Thanks Man You really saved my razr.:good:
Edit : Sorry I asked stupid question!
Pierro29 said:
Edit : Sorry I asked stupid question!
Click to expand...
Click to collapse
there are no stupid questions if you question its because you dont know something and would like to fulfill the empty space where a reasonable answer could go. and s thanks for the solution to this error.
Okay, I have a "stupid"/newbie question. I flashed an image and I am getting the sticky boot thing. How to a get to a window to type the lines in?
Thanks!
cerafio said:
Ok guys so after serching a while I found out similar moto phones have the same issue. I found in a latin forum and in a Droid forum people ponting to the same issue. So the solution that worked for my Razr HD xt925 was:
1) Enter fastboot mode in your phone (very easy since every time you restart the phone you end there anyways)
2) Write this command on the computer: fastboot oem fb_mode_clear
there will be a dialogue with the time take and OK
You are done!
Thought someone might find it useful
Click to expand...
Click to collapse
Hey dude ! You save my life
Awesome trick
I have had my Maxx HD since launch and unlocked very soon after it became available,
Recently I downgraded from the last OTA with matgroffs 1.21 utility and enjoyed a wonderful clean slate experience but after a while (today) I went for the OTA to get prepared for KK coming soon hopefully, the install failed entirely and my bootloader is now back in a locked state the phone is stuck in fastboot and will not take a flash from any utility on here, 1.21, 1.3x 2.0 ext including rsd lite.(RSD will not even detect the phone)
Ive tried the utilities on Mac and Windows 7, nothing has worked so I broke down and called verizon and ordered a recertified razr HD for a discounted price.
So just a warning there is a way the bootloader can get relocked. will take a picture and load soon to show the screen of the phone incase someone can help. Just a side note my vibrate motor failed and I have been having 4g radio problems before I went back on matgroffs utility.
You tried house of moto to fastboot flash 98.30.1? Sux they found a way to relock them...
Sent from my XT907 using Tapatalk
This only shows up when you get the GPT error. It will still be unlocked once you get this restored. This came up when the OTA was released. A few people with unlocked BL had this GPT error. There's a fix somewhere around here, just search for the error.
RikRong said:
This only shows up when you get the GPT error. It will still be unlocked once you get this restored. This came up when the OTA was released. A few people with unlocked BL had this GPT error. There's a fix somewhere around here, just search for the error.
Click to expand...
Click to collapse
@AndroidGreg
There's a line in the fastboot xml file with gpt_main0.bin (somithing really similar to that, been a while since I flashed it...) and all that's necessary is removing that line and flashing the fastboot with rsd, or just manually flash the fastboot skipping that partition, either or will work and fix the problem. Even though the bootloader is unlocked, that particular partition IS still controlled by securtiy and is blocked from downgrading -- luckily for us the partition table never changed between rom versions so it's perfectly safe to flash or not to flash it.
I've never flashed with RSD, but IIRC, there's also two more lines in the fastboot's xml that need to be removed for it to properly flash. I've only flashed my phone with moto-fastboot from linux and used MythTools from windows -- MythTools is an interactive script for the Atrix HD to flash stock fastboots, root, unlock the bootloader, flash a custom recovery, boot logos, and soon different radios -- Similar to Mattlgroff's tool.
The Atrix HD has the exact same issue with that partition.
download the sbf file from http://sbf.droid-developers.org/phone.php?device=5
install these drivers https://motorola-global-portal.custhelp.com/app/answers/detail/a_id/88481/action/auth
connect the phone in fastboot mode.
now extract the "fastboot_rsd.zip " to a folder.
extract the contents of the downloaded sbf/xml file into the fastboot_rsd.zip folder
execute "flash_fastboot_erase_userdata"
worth a shot.
always works for me..
good luck.
RSD does not detect the phone at all, only the quick utilities did and they failed. Verizon overnighted my new phone and its here already, not unlockable im just gona root and keep it for a while till I switch to strait talk with the nexus 5, I cant afford $100 a month anymore anyway.
First off, thanks to the OP for posting this. This was exactly my thought on getting the KK update when it arrived then building phone back up with the mods and apps I have currently - flash back using 1.21, update, use TiBu to reinstall everything. Sux to see that didn't work, but thank you for posting the warning to others.
Not that I'm hoping to see others attempt this and fail or somewhat ruin their phone, but has anyone else had this experience? Anyone verify this method isn't possible to keep unlocked bootloader and a fully working device?
If not possible, hopefully someone will build a flashable version of the OTA KK update when it FINALLY arrives. I'm way too unstock for the update to work OTA, that's a fact.
LifeAsADroid said:
First off, thanks to the OP for posting this. This was exactly my thought on getting the KK update when it arrived then building phone back up with the mods and apps I have currently - flash back using 1.21, update, use TiBu to reinstall everything. Sux to see that didn't work, but thank you for posting the warning to others.
Not that I'm hoping to see others attempt this and fail or somewhat ruin their phone, but has anyone else had this experience? Anyone verify this method isn't possible to keep unlocked bootloader and a fully working device?
If not possible, hopefully someone will build a flashable version of the OTA KK update when it FINALLY arrives. I'm way too unstock for the update to work OTA, that's a fact.
Click to expand...
Click to collapse
It only shows that his BL is locked because of the GPT error. I can assure you it is still unlocked. Many, many people updated and we still have unlocked BLs. Heck, I've flashed the latest OTA on my M and HD with RSD and am still good. He just needs to fix the error, but he have up and got another phone.
RikRong said:
It only shows that his BL is locked because of the GPT error. I can assure you it is still unlocked. Many, many people updated and we still have unlocked BLs. Heck, I've flashed the latest OTA on my M and HD with RSD and am still good. He just needs to fix the error, but he have up and got another phone.
Click to expand...
Click to collapse
Exactly. The Atrix HD gives us this error if we flashed the stock Mexican firmware (our latest) and try to flash anything below it, or the Bell firmware (2nd newest) and anything below that, and so on and so forth. All that's necessary is to remove the gpt flashing line and go again....just like we have to remove the oem lines from the fastboot xml.
First time I had that error, I went WTF (the first flash after unlocking my bootloader if ya'll's curious), knew that GPT is a partition table from grub experience, figured that the partition table has never changed since stock ICS roms, removed the GPT line, flashed ICS, and I was happy.
I'd love to be able to combine all the data, system, cache, and any other partition that don't need a fixed place (like modem, etc) and be able to use ZFS or BTRFS volumes to maximize the amount of storage we can have -- I've always wondered why they don't do something like that already...
Ok 3 computers 1 xp and 2 windows 7, nothing, mac nothing, even made a factory cable because the battery just got to low, nothing, no computer will detect it, using any of the 3 motorola branded usb cables plugged directly into the laptops. Now the utilities from matgroff and the other guy (cant think of his name but he made the 2.0 utility) will not even try to flash the phone they say please plug a phone in that is in fastboot mode, I
Serious question, but have you tried Linux? My old Bravo wasn't detected by Windows (XP or 7, been 2 years now) after a bad RSD flash, but I was able to manually flash it from Linux (either Manjaro or Debian Testing). After that, to this day it'll flash with RSD, but it isn't detected properly. I still flash it, and almost everything else, from Linux because I don't trust flashing from Windows anymore. I made an exception recently to help with a tool and because my Linux partition was down for a month.
LifeAsADroid said:
First off, thanks to the OP for posting this. This was exactly my thought on getting the KK update when it arrived then building phone back up with the mods and apps I have currently - flash back using 1.21, update, use TiBu to reinstall everything. Sux to see that didn't work, but thank you for posting the warning to others.
Not that I'm hoping to see others attempt this and fail or somewhat ruin their phone, but has anyone else had this experience? Anyone verify this method isn't possible to keep unlocked bootloader and a fully working device?
Click to expand...
Click to collapse
I tried doing the exact same thing as the OP - factory reset to "stock" and then flash back up in preparation for KK, after using TiBu to save everything and using SafeStrap to make a Nandroid (very thankful I did). I ended up with the identical screen that the OP had, even stating that my previously unlocked BL had been apparently "relocked." For me, RSD Lite did recognize my phone (I updated RSD to the latest version beforehand), however it would not flash anything for me (the flashing process would start and then immediately say "failed").
See my post for the details and the solution I used: http://forum.xda-developers.com/showthread.php?t=2674431.
I was completely freaked out for a couple of hours until I stumbled upon bweN diorD's GPT partition fix. And then everything was fine for me.
Hope this helps anyone who falls into the same trap.
AndroidGreg said:
I have had my Maxx HD since launch and unlocked very soon after it became available,
Recently I downgraded from the last OTA with matgroffs 1.21 utility and enjoyed a wonderful clean slate experience but after a while (today) I went for the OTA to get prepared for KK coming soon hopefully, the install failed entirely and my bootloader is now back in a locked state the phone is stuck in fastboot and will not take a flash from any utility on here, 1.21, 1.3x 2.0 ext including rsd lite.(RSD will not even detect the phone)
Ive tried the utilities on Mac and Windows 7, nothing has worked so I broke down and called verizon and ordered a recertified razr HD for a discounted price.
So just a warning there is a way the bootloader can get relocked. will take a picture and load soon to show the screen of the phone incase someone can help. Just a side note my vibrate motor failed and I have been having 4g radio problems before I went back on matgroffs utility.
Click to expand...
Click to collapse
I had this same problem when i tried to go back to stock a while back. You need to flash the gpt_main0.bin file to fix it. Here are the steps I used to fix the problem: http://forum.xda-developers.com/showpost.php?p=47716278&postcount=57
Another user took my steps and edited a script so give this a shot if you want to run something thats automatic: http://forum.xda-developers.com/showpost.php?p=48587194&postcount=89
scoobaspeaz said:
I had this same problem when i tried to go back to stock a while back. You need to flash the gpt_main0.bin file to fix it. Here are the steps I used to fix the problem: http://forum.xda-developers.com/showpost.php?p=47716278&postcount=57
Another user took my steps and edited a script so give this a shot if you want to run something thats automatic: http://forum.xda-developers.com/showpost.php?p=48587194&postcount=89
Click to expand...
Click to collapse
@AndroidGreg, do you still have the phone?
Sent from my DROID RAZR HD using Xparent BlueTapatalk 2
So for the last few days I have been trying to get the bootloader unlocked, with no progress. <br />
What ever drivers fir adb and fastboot I use it doesn't install it. There is always a "other device" icon with an android sub-icon. If I force install android fastboot or any other adb driver be it of Asus , nexus or any other it doesn't work.<br />
Is there a issue in windows 7? <br />
I cannot switch to win 8 so is there a working way to get this done?<br/>
Bro this is development section :banghead::what:
Oops sorry will delete thread
dont post untill u dont know its place,cant u see Q&A section
but u got blind and posted under dev threads,whats wrong with you.
Get the thread deleted.
Hi. I'm just gonna say this first: I didn't know entirely what I was doing when beginning this operation. I was just trying to do something fun and new, and it didn't pan out. I fully acknowledge that I am an idiot.
Now, the story. I was attempting to root my LGV20 with this guide: https://forum.xda-developers.com/v20/how-to/root-h910-v10m-t3664500 .
I have read over this thread more times than countable and thought I was doing everything correctly. I got to the "STEP3.BAT" portion of the guide and long story short, my phone crashed during it and somehow got foobarred.
It *kinda* works (as in it will boot for around a minute) and then blue/black screen into a reboot.
Is there any way I can save this phone? Hard resets, going into software, more dumb computer stuff, anything. I don't *need* to get this phone working again but it would be really preferable.
Simultaneously I fully accept the responsibility in failing the operations. I know that somewhere I must have messed up. If no-one wants/ can help me, tell me so. Just means new phone time.
If any more detail on what happened is needed, tell me.
First off: that guide is ONLY for the H910 (AT&T) variant, so make sure with your model
and also, when you said a "blue or black screen" it also has very small writings too, right? If so, then you may have faced a kernel/bootloader panic
Technically your phone is *still* alive, and your best method is to start over again, assuming if you read the whole guide carefully then you have backed up your firmware and can still access download mode.
Flash your stock firmware back (or use the H915 firmware provided by the guide), wipe and setup your phone again, then root the phone again.
I also suggest replacing the TWRP recovery inside the provided Dirtysanta folder cuz that's what i did when i faced the kernel panic
MEMO#22 said:
First off: that guide is ONLY for the H910 (AT&T) variant, so make sure with your model
and also, when you said a "blue or black screen" it also has very small writings too, right? If so, then you may have faced a kernel/bootloader panic
Technically your phone is *still* alive, and your best method is to start over again, assuming if you read the whole guide carefully then you have backed up your firmware and can still access download mode.
Flash your stock firmware back (or use the H915 firmware provided by the guide), wipe and setup your phone again, then root the phone again.
I also suggest replacing the TWRP recovery inside the provided Dirtysanta folder cuz that's what i did when i faced the kernel panic
Click to expand...
Click to collapse
Thanks so much. Freaked out over this for a good bit. Came back, did what you said and we're back at that step fully working. Life saver.
Now my first guess as to why step3 failed is that i didn't have the latest version of TWRP. How can I set that up?
Inside the root package folder you can see an .img file named twrp 3.0.2-1- us996.img
What i did was downloaded a later version
(not latest cuz my phone won't boot at the latest version for some reason), copied the name of the original twrp and renamed it, paste it to the folder, overwrite the old one, and try to root it again
MEMO#22 said:
Inside the root package folder you can see an .img file named twrp 3.0.2-1- us996.img
What i did was downloaded a later version
(not latest cuz my phone won't boot at the latest version for some reason), copied the name of the original twrp and renamed it, paste it to the folder, overwrite the old one, and try to root it again
Click to expand...
Click to collapse
Alright, i've done that now too. Thanks. Is there anything else i should/need to keep in mind to ensure failure is not going to happen? I want to make 100% sure I get everything right this time.
reptarien said:
Alright, i've done that now too. Thanks. Is there anything else i should/need to keep in mind to ensure failure is not going to happen? I want to make 100% sure I get everything right this time.
Click to expand...
Click to collapse
No i don't think there is more things to do, the guide you're following is pretty much straightforward already.
100% guarantee is always a stretch here in XDA. But if you're still facing problems you can ask for help on that guide's thread.
MEMO#22 said:
No i don't think there is more things to do, the guide you're following is pretty much straightforward already.
100% guarantee is always a stretch here in XDA. But if you're still facing problems you can ask for help on that guide's thread.
Click to expand...
Click to collapse
I really want to give up on this. This time I successfully made it through all Step 3, but I also noticed that my screen was kind of glitched and not rendering properly at that stage. After it rebooted, I unplugged my micro usb cable and it gave me an angry green warning message I will attach here.
If you/someone can tell me what to do with this message from here or instruct me on how to flash stock H910 10 q back onto the phone without doing TWRP (since i'm evidently incapable of installing it) I would be most appreciative.
Slightly better picture without anything cut off.
reptarien said:
I really want to give up on this. This time I successfully made it through all Step 3, but I also noticed that my screen was kind of glitched and not rendering properly at that stage. After it rebooted, I unplugged my micro usb cable and it gave me an angry green warning message I will attach here.
If you/someone can tell me what to do with this message from here or instruct me on how to flash stock H910 10 q back onto the phone without doing TWRP (since i'm evidently incapable of installing it) I would be most appreciative.
Click to expand...
Click to collapse
The screen glitching is normal, the green text after boot however is somehow not.
Sad to hear that it still didn't work, there something seems to be interrupting the process of rooting your phone. I dunno if it has something to do with ARB (anti rollback) preventing you to root
If you want to go back to your stock firmware that you backed up, you can:
-Carefully flash each file of your backed up firmware through adb and fastboot mode
-build a zip file of your firmware and flash through TWRP (since it didn't succeed tho)
MEMO#22 said:
The screen glitching is normal, the green text after boot however is somehow not.
Sad to hear that it still didn't work, there something seems to be interrupting the process of rooting your phone. I dunno if it has something to do with ARB (anti rollback) preventing you to root
If you want to go back to your stock firmware that you backed up, you can:
-Carefully flash each file of your backed up firmware through adb and fastboot mode
-build a zip file of your firmware and flash through TWRP (since it didn't succeed tho)
Click to expand...
Click to collapse
Could you reply with any links with a tutorial on how to do the first thing? Or describe it. Sorry for being so dumb i'm a total newbie lol
reptarien said:
Could you reply with any links with a tutorial on how to do the first thing? Or describe it. Sorry for being so dumb i'm a total newbie lol
Click to expand...
Click to collapse
Unfortunately i can't find any guides when it comes to flashing the back up.
I did read something back then on turning it into a zip file, but even if you can build one you still need TWRP, in which case you haven't successfully installed, so that's no option
Flashing the backup files requires specific commands, especially to the part on what partition should it be flashed to
When LGUP backs up your phone's firmware, you can see a vast number of files(i can't remember how were they named, I'll look up a reddit post about it)
The files where named based on what partition it came fom (H910_modemxx_COM12, H910_system_COM12 or something like that)
These are image files, what i did as far as i can remember was rename these files by adding an IMG extension for ADB to recognize
Flash them according to it's partition name:
"Fastboot flash system H910_system_COM12.img"
"Fastboot flash recovery H910_recovery_COM12.img'
Etc.
To go to fastboot, turn off your phone and hold the volume down button , then plug your phone to the PC.
But i really cannot guarantee this, because for all i know, in order to flash this you need fastboot, and to get fastboot you need to root your phone, because only the engineering bootloader has it (i'm sorry if it's wrong tho), and flashing these files to fastboot might be a bit dangerous because it will not verify the files, there may be chances that you might flash a corrupted file. so flashing via LGUP is the safest option so far if you don't know what you're doing