All I get is this screen:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Please help its been like that for awhile after the update is done downloading and I try to install it!
Sent from my HTC Sensation 4G using XDA App
it seem you have some mods in /system or /webtop partition
Did you ever unlock your bootloader?
ATT right?
mramirezusa said:
it seem you have some mods in /system or /webtop partition
Did you ever unlock your bootloader?
ATT right?
Click to expand...
Click to collapse
if you Answer are NO
and YES
this is the way to do it follow this link and you need a PC and your phone attached to it by USB:
"http://direct.motorola.com/hellomoto/motosupport/source/SoftwareUpdateSummary.asp?country=USA&language=ENS&web_page_name=SUPPORT&strCarrierId=ATT&strPhone=Motorola%20ATRIX%28TM%29%204G&strCable=Micro%20USB%20Data%20Cable&strURL=https://rsddownload.motorola.com/download/SoftwareUpdateforATTATRIX4Gversion.4.5.91.pdf"
I believe i just rooted it with gingerbreak but then i followed this tutorial: http://atrix4ghacks.com/atrix-4g-hacks/how-to-enable-webtop-without-laptopusb-dock/
it edited my webtop stuff so how do i fix it so i can update
lol don't panic! (....I have a towel =D)
You just entered the recovery menu. To see the error message, you need to un-hide it by touching the screen on the bottom right corner (right above the search button). This will show you what error you encountered.
If you're OTAing up, then you probably had Titanium or something that removed bloatware or modded the system with a theme or custom files. If that's the case, any OTA will fail because you will not have passed the pre-install check. You have three options:
1.) Go here and get the Automated Upgrade for PC Users. That will allow you to upgrade and bypass the test, while also keeping your data. This doesn't require any mods or unlocked bootloaders. (BE WARNED THAT IF YOU USE THIS, YOUR BOOTLOADER WILL BE BLOWN. DON'T DOWNGRADE WITH SBFs AND STICK TO EATING YOUR FRUITCAKE! However, Radio and Bootloader SBFs are still considered safe. As any wise man would do, proceed with caution.)
OR
2.) Unlock your bootloader, install CWM from Tenfar, and then get KP's 2.3.4 ROM Beta 4 and put it in your SD card. Boot up CWM and install it. That easy. =] (BE WARNED SOME PEOPLE BRICKED THIS WAY.)
ORRRRRR
3.) Using the fastboot from Motorola and unlocking your bootloader, just flash the images here. (Currently the best method and seems to produce the best results, but if you don't know how to do it, then don't do it.)
If you need instructions on how to do any of the above, use this noob bible. And lastly, if you want to root, use the preinstall method (also in bible.)
Happy upgrading!
~jojojohnson7410~
I had the same problem and also had only used gingerbreak and webtop mod. I tried using pc update software but it thought I was on orange france (mine is AT&T) so I didn't proceed. Decided to flash the gingerbread plus pudding sbf in pudding thread, worked perfect and kept all data, you don't need to unlock bootloader before updating
Same problem
I'm having the exact same problem.
Except my bootloader is unlocked.
Any help would be greatly appreciated.
Thanks!
Related
Is it possible? And, yes, it's Android 2.3.5 STOCK on International version of the Atrix.
The history behind that:
He was having issues with a rooted/modded atrix (battery wise) and he knew someone that work at motorola here in Brazil. He sent the Atrix to his friend and got back the same atrix back but with a stock 2.3.5 android installed. Now he is asking what to do to root it since all programs won't work (gingerbreak, for example) nor he is willing to install the AT&T SBF from here: http://forum.xda-developers.com/showthread.php?t=1182871 (specially cuz it can brick his device since it's a different device).
Image:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Your best bet would probably either pete's root tool or the thread that says "How to root any phone after SBF" located in the dev section. Use your search feature. The preinstall method involves basic ADB commands via a cmd line. Pete's is a 1 click option, some people are saying it works for any moto phone...
He will test it when he can.. I'll let you know.
Nop.. It didn't work.. It seems that 2.3.5 is different..
Any other ideas??
Does gingerbreak work? Just a thought.
sent from my Atrix via XDA premium
marko! said:
Does gingerbreak work? Just a thought.
sent from my Atrix via XDA premium
Click to expand...
Click to collapse
Read OP again. He already said it doesn't work!
Assimilated via WinBorg 4G
No root method tested work..
- One Click
- GingerBreak
- SBF File (fastboot) from here: http://forum.xda-developers.com/showpost.php?p=15023022&postcount=2 (fastboot errors out)
So far, no method works for root..
Uhuhu said:
No root method tested work..
- One Click
- GingerBreak
- SBF File (fastboot) from here: http://forum.xda-developers.com/showpost.php?p=15023022&postcount=2 (fastboot errors out)
So far, no method works for root..
Click to expand...
Click to collapse
what do you mean sbf file from the preinstall method? you're supposed to flash the preinstall.img in the second post, which can be downloaded by this link here: http://forum.xda-developers.com/attachment.php?attachmentid=652327&d=1310460219
then do 'fastboot flash preinstall preinstall.img' and then run the whole /preinstall/dosu commands in either adb shell or terminal emulator on your phone
Well, I've written it wrong.. Sorry 'bout that.
- Fastboot fails to install... Can't even install the preinstall.img file.. That's what I've meant.
As known by most of you, removing any "bloatware" by means of deletion, such as Bell bloatware, will make it so that you are not capable of updating to gingerbread.
I did not know this prior to deleting my .odex files and rooting, sadly.
I had a simple question, what am I to do in this kind of situation? I've read here to flash a stock SBF and update it from there, however, I'm a bit weary of flashing my device for risk of bricking it. (Bought off Craigslist...rooted = no warranty)\
Any ideas xdaders?
Oh and I just finished a factory reset.
are you on 2.3.x or 2.2?
2.2, froyo.
Motoblur.
(2.3 backwards sbf flashing would = a brick )
Flash a fruitcake?
You should just flash the newest sbf. And flash a new rom such as cm7 that would perform even better. After unlocking the bootloader just flash cwm and if you really wanted you could flash a stock carrier rom.
Sent from my MB860 using xda premium
turl1 said:
Flash a fruitcake?
Click to expand...
Click to collapse
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Nevermind, I get it.
Thank you freshlycutlawn, I'll look into flashing the newest sbf. This is relatively safe if all the procedures are followed, correct?
Yes, since you are on froyo pretty much all of the unlock sbf's will be newer and wont brick your phone, you only have to watch out for an older version. Other than that you should be good to go, let me know if you have any other questions especially since im on bell too. It was a bit more tricky to find all of the correct downloads and follow the right steps, but now i have done it and im sure the same way i did it would work for you. Best of luck.
freshlycutlawn said:
Yes, since you are on froyo pretty much all of the unlock sbf's will be newer and wont brick your phone, you only have to watch out for an older version. Other than that you should be good to go, let me know if you have any other questions especially since im on bell too. It was a bit more tricky to find all of the correct downloads and follow the right steps, but now i have done it and im sure the same way i did it would work for you. Best of luck.
Click to expand...
Click to collapse
That would be appreciated. I have been trying to find Bell files and other related information using the search function, but if you've already done that and are offering to help, might as well.
If you can private message me it, that'd be greatly appreciated.
Ok so this may have been posted before but I've been searching and can't find anything.
So I got my note 2 when they released and I did the first "root" method available which I think was odin. Not really root with a custom recovery however I don't think. See the following screenshot to see what I'm currently running. Its been fine until now so I never re flashed anything or install twrp or anything.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Lately its been running slow so I want to fully root and install something along the lines of the latest Clean Rom. I had cleanrom on my Rezound and I love his roms.
Only reason I'm making this thread is because I'm not sure where to start because I don't think I'm stock yet I'm not "really" rooted.
Dont want to mess up my device.
Thanks!!
ufvj217 said:
Ok so this may have been posted before but I've been searching and can't find anything.
So I got my note 2 when they released and I did the first "root" method available which I think was odin. Not really root with a custom recovery however I don't think. See the following screenshot to see what I'm currently running. Its been fine until now so I never re flashed anything or install twrp or anything.
Lately its been running slow so I want to fully root and install something along the lines of the latest Clean Rom. I had cleanrom on my Rezound and I love his roms.
Only reason I'm making this thread is because I'm not sure where to start because I don't think I'm stock yet I'm not "really" rooted.
Dont want to mess up my device.
Thanks!!
Click to expand...
Click to collapse
Sounds like you are rooted, but your bootloader is still locked. In order to flash ROMs on Verizon you will need to unlock the bootloader (unless you did that via Odin the first time around). From those screenshots you won't be able to tell if you have unlocked the bootloader...as far as I know the only want to check is to boot into recovery. If you see TWRP or CWM you are set...if you get the stock recovery you need to follow Adam Outler's original unlock method as you are on baseband VRALJB. To access recovery power off the device and then press volume up + power button + home button simultaneously. Whatever boots up will tell you what you need to know.
stary by reading the stickies.
Yea I believe I'm still on the stock recovery.
Hello there, I won't lie, I ask for help, you answer me.
I don't understand enought your method, because it's not well described.
But.. Therefore...
I'm able to root my device.
I'm able to backup my ta partition or my drm keys.
I'm able to unlock my bootloader.
I'm able to restore my bootloader to lock it back.
i'm able to unbrick my phone when it couldn't boot via flashtool.
Click to expand...
Click to collapse
But I'm unable to install a custom recovery and or even launch the stock on it there was one.
I tried this method: http://forum.xda-developers.com/showthread.php?t=2647492 (normal boot and no pink led).
I tried this method: http://forum.xda-developers.com/showthread.php?t=2799388 via flashtool and my phone couldn't boot, even to the SONY logo, but it were vibrating when pushing on the power button.
Anyway, I flashed via flashtool the 14.4.A.0.108 back, now I'm still rooted and the bootloader is still unlocked.
Click to expand...
Click to collapse
What can I do to install a custom recovery via the 14.4.A.0.108 ?
Or this operation is impossible and I have to downgrade ?
(I read about downgrade and I'm affraid to lose my IMEI)
Click to expand...
Click to collapse
Thank you for your glorious complete explanations.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I'm pretty sure the problem here is that there is a stock firmware development aka the custom ROMs can't just start "taking over from where the devs left off" like it happened with Samsung Devices that get stuck at v4.1.2 unless someone else does something about it.
I guess most things here just are not stable. I hope the stock works out for you. Did you get the rooting done? I found a video tutorial for that here http://forum.xda-developers.com/xpe...de-root-android-4-4-4-ver-14-4-0-108-t2801587
Zhuinden said:
I'm pretty sure the problem here is that there is a stock firmware development aka the custom ROMs can't just start "taking over from where the devs left off" like it happened with Samsung Devices that get stuck at v4.1.2 unless someone else does something about it.
I guess most things here just are not stable. I hope the stock works out for you. Did you get the rooting done? I found a video tutorial for that here http://forum.xda-developers.com/xpe...de-root-android-4-4-4-ver-14-4-0-108-t2801587
Click to expand...
Click to collapse
Hello, of course I have done rooting, now I'm back in full stock, nk rooting, just pure sony beauty. And everything works better without root, or it doesn't matter, but the navigation and the use of the device is much smoother without lags
Hi I am getting an error when trying to relock the bootloader, I reboot into bootloader put in the command to lock "Fastboot flashing lock" get the error below in the image. Any idea why?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Have you restored the full stock firmware? If not then do that first using: https://pixelrepair.withgoogle.com/carrier_selection
foobar66 said:
Have you restored the full stock firmware? If not then do that first using: https://pixelrepair.withgoogle.com/carrier_selection
Click to expand...
Click to collapse
I don't recommend using the Pixel Repair Tool unless absolutely necessary.
If you are trying to return your device to absolute stock, I recommend using the Android Flash Tool. You can choose which factory build to flash, whether to wipe the device, and whether to relock the bootloader.
aymuhamm said:
Hi I am getting an error when trying to relock the bootloader, I reboot into bootloader put in the command to lock "Fastboot flashing lock" get the error below in the image. Any idea why?
View attachment 5475895
Click to expand...
Click to collapse
It is likely that you rooted your phone at one point, or perhaps flashed an alternative operating system which does not support verified boot.
Traditionally but not in all cases, re-locking your bootloader requires you to be unequivocally 100% stock. If you plan on being on stock and you are not (which I am assuming), you can either follow the # Flashing Instructions steps on the Nexus/Pixel Factory Images page. If you find that a bit tedious, there is always the flash-all.sh/flash-all.bat which will do this all for you.
After this, your device will be set straight back to factory, and you can follow the steps to re-lock your bootloader.
VozerCozer said:
It is likely that you rooted your phone at one point, or perhaps flashed an alternative operating system which does not support verified boot.
Traditionally but not in all cases, re-locking your bootloader requires you to be unequivocally 100% stock. If you plan on being on stock and you are not (which I am assuming), you can either follow the # Flashing Instructions steps on the Nexus/Pixel Factory Images page. If you find that a bit tedious, there is always the flash-all.sh/flash-all.bat which will do this all for you.
After this, your device will be set straight back to factory, and you can follow the steps to re-lock your bootloader
Click to expand...
Click to collapse
This is why I like to recommend the Android Flash Tool - simply from a perspective of ease of use, and the fact it's practically impossible to get wrong; additionally, the user can elect to lock the bootloader during the process when choosing the flash options. This removes the need to do anything else manually; the tool takes care of the entire process.
It's also very useful for updates.