Database Info

[Q] Update Nexus S from 2.3.6 to 4.0.3 manually with a broken power button

Hello everyone
I own a Nexus s I9020 T-mobile. and I'm using it on Vodafone.
My power button stopped working a month back and I'm using widgetlocker lockscreen to unlock.
I did not receive the OTA for ICS last month and i would like to have it on my phone by doing the update manually.
Is there a way to do the update manually with a broken power button ?
Thanks

There is a clockwork recovery with touchscreen interface I can't remember where I saw it though. So you could use that to flash the ota. Or you could flash the boot and system images directly through adb if they have been posted somewhere. You will have to root your phone before you can use these methods
Sent from my Nexus S using Tapatalk

timhl7 said:
There is a clockwork recovery with touchscreen interface I can't remember where I saw it though. So you could use that to flash the ota. Or you could flash the boot and system images directly through adb if they have been posted somewhere. You will have to root your phone before you can use these methods
Sent from my Nexus S using Tapatalk
Click to expand...
Click to collapse
thanks .. but I think the touch based clockwork recovery is only avilable for Galaxy Nexus and more over I dont want to root my phone unless it is absolutely necessary .. because i'll have to re-install all my apps
is there any possible way to do it without rooting ?

The Clockwork Recovery you are looking for is named TWRP (latest is Version 2.0.0). Look at the offical site - http://teamw.in/project/twrp2 - choose your device (NS or NS4G) and install via adb
Good luck

Rallyharry said:
The Clockwork Recovery you are looking for is named TWRP (latest is Version 2.0.0). Look at the offical site - http://teamw.in/project/twrp2 - choose your device (NS or NS4G) and install via adb
Good luck
Click to expand...
Click to collapse
Thanks mate
should my device be rooted for this ?
and after installing clockwork recovery how do I flash the update.zip file via clockwork, any guide ?

I have a new posted guide which should be useful for you, but you have to have it rooted first.

mingkee said:
I have a new posted guide which should be useful for you, but you have to have it rooted first.
Click to expand...
Click to collapse
Thanks mingkee
will try it out .. just hope I don't brick my phone 'coz im going to root my phone for the first time
looks like you have gone back to CM7 from ICS
should I overlook ICS too, coz im pretty happy with GB right now.

You don't need to flash TWRP. In clockwork mod recovery back is back, menu is down, search is select, home is up.
Sent from my SNES

even to flash ClockworkMod or TWRP, first you will need to unlock the bootloader right ?
for this again the need for power button arises..

Keep root with JB update?

As we wait for the JB update in US, I was wondering if there's a proven method to keep root on note 10.1?

grimloktt said:
As we wait for the JB update in US, I was wondering if there's a proven method to keep root on note 10.1?
Click to expand...
Click to collapse
I always use voodoo root keeper just to be safe
Sent from my EVO using xda premium

Install the update through mobile ODIN....

Install root without odin?
ultramag69 said:
Install the update through mobile ODIN....
Click to expand...
Click to collapse
I updated via Keis (bad mistake!) and lost my root. Even worse, I lost the ability to boot into cmd -- every time I do the Control + power routine I get booted into Android Recovery. Without the ability to get my tablet into download mode, I can't connect with Odin.
Please help --
Either........ is there another way to boot into download mode?
Or........... is there a way to install cmd on my tablet without using odin?
Please....... I am not new to rooting but I need a bit of detailed description. I'm very afraid of bricking my lovely tablet.
thanks,
Barb

Volume down+power button will get you into download mode volume up+power will get you into recovery
Sent from my EVO using xda premium

Robert542 said:
Volume down+power button will get you into download mode volume up+power will get you into recovery
Sent from my EVO using xda premium
Click to expand...
Click to collapse
Thanks for the response -- however the process you describe does not work after this Kies upgrade. Volume down + power does not get me into download mode -- instead I get stuck in the Android system recovery (3e). (Same with the volume up+power.)
My only options in this Android sytem recovery are to:
reboot
apply update from external storage
wipe data/factory reset
wipe cache partition
apply update from cache
I am wondering -- what if I were to place the clockword mod recovery zip file on my sd card and then use "apply update from external storage", or simply reboot.
Any thoughts or suggestions? I was also told I might be able to get into download mode through adb.
Thanks again for dialogue.
Barbara

No chance... Stock recovery needs the zip files to have samsung approval, not only that but it won't allow a different region rom to be flashed either.... Looks like you screwed the pooch on this little puppy...

nabour said:
I updated via Keis (bad mistake!) and lost my root.
Click to expand...
Click to collapse
Did you update to JB?

Just clarify, please
ultramag69 said:
No chance... Stock recovery needs the zip files to have samsung approval, not only that but it won't allow a different region rom to be flashed either.... Looks like you screwed the pooch on this little puppy...
Click to expand...
Click to collapse
So just to clarify, you are saying that it doesn't matter whether I can get into download mode or not (which I was able to do, with ADB), because ANY clockwork mod recovery file that I find will be unloadable (because it won't "play" with stock recovery)? Is that correct?
Don't want to sound argumentative, but does that mean that anyone who upgrades their firmware via "official Samsung" will be unable to root in the future? That's not too cool.
But if so, I can live with it.
Again, I appreciate your time.
Barb

I know with the S3 there is a root tool that allows rooting via ADB but I don't believe this has been developed for the Note 10.1 as yet. Everything is done via ODIN... Unless you wish to try the 1st method from this thread to get root access - http://forum.xda-developers.com/showthread.php?t=1831152 - then install a version of CWM manually...
Stock root is very picky about what it will or wont flash.... Even if you have a stock rom, if the CSC oodes, region, doesn't match it will error out...

grimloktt said:
Did you update to JB?
Click to expand...
Click to collapse
No........ that's the goofy part of it. I had an upgrade waiting for me (under "settings, upgrade" and so I stupidly assumed it was the official jellybean. Wrong, wrong! I was simply upgraded to 4.0.4. I can't see any noticeable changes, except for the Android Recovery system having booted out my Clockwork recovery (and the root, of course.)
I've decided to wait a week or so until I get the official jellybean and then decide what to do.

It will also have given you a new template in s-notes - landscape and the scroll bar... It will also have given you the ability to use an exFAT formatted sd card... There were a few other tweaks but not too much...

Problem with huawei vision

Hi!I have a problem with my huawei vision.I wanted to install android 4.2.1 jelly bean from another phone and now my phone start and stuck at huawei logo....PC dont recognized him......No recovery No fastboot No nothing.....What should i do?:|

Someone help me?please?

You should never install ROMs or flash kernels which are made for another phone to your own phone. Each ROM is made specificaly for one device making it hardly possible to work properly on others.
If you have an unlocked bootloader then you could simply flash a kernel with CWM recovery and flash another supported ROM.
If you have a locked bootloader (also if you don't know what that is, then this is probably what you have) and if you haven't flashed any custom kernels (if you don't know what those are then you probably haven't) then your only hope is to find and flash the stock ROM back on it.
EDIT: If you're phone is the Huawei U8850 aka Vision then this is a stock ROM you can use:
https://mega.co.nz/#!hxIEDTrZ!ejEk1AC5f6S4aJ0iLx2rIkB0gMJIUMY5-_8iPDIZcfI

Probaly i have locked bootloader ....but how i unlock bootloader because my pc don recognized my phone nothing....

Download the U8850 Upgrade package from here. Unpack it and install SUT L3 and the USB drivers from the unpacked files. With SUT L3 you will flash this firmware which will enable CWM recovery on your device which you can access by pressing Vol- and Power button at the same time when you turn your phone on (you don't have to enter it after flashing this firmware I gave you because it should work fine).
First boot will take a while, but if it takes more than aprox. 15 minutes than something's wrong again.
EDIT: If everything goes fine and you want an ICS ROM than you can hop to this thread/tutorial. BUT DO THIS ONLY IF AND AFTER YOU HAVE SUCCESSFULLY INSTALLED AND BOOTED THE ABOVE FIRMWARE!

Dont work....Pc dont recognized him......

If SUT L3 is not detecting your phone when you connect it, neither turned off nor turned on, then I'm afraid you just bricked your phone.

Thank you! I finish problem:*!

Now ...i have a problem...when i want to install firmware .....error : task 2 of 2 ,download image fail error=device_not_configure

Glad to hear that! Just remember to never use ROMs which are not made specifically for your device!
Sent from my Xperia X10 using xda app-developers app

But ....with error?.....i cant install android:|.....error appear in sut l3..

Did you install the required USB drivers from the upgrade tools I gave you?
Sent from my Xperia X10 using xda app-developers app

Yes i install.....now boot recovery .....but i cant select anything..

Use the volume hard keys.
Sent from my Xperia X10 using xda app-developers app

i use.....but when i click on "install zip from sdcard" nothing

How?

U must first transfer a ROM in zip format to your SD card and then select it via recovery.
But I lost you there a little. Was the recovery there before or did you successfully install the firmware via SUT L3? Because if you have, than you should be able to boot the Gingerbread ROM from the firmware.
Sent from my Xperia X10 using xda app-developers app

CCVader13 said:
First boot will take a while, but if it takes more than aprox. 15 minutes than something's wrong again.
Click to expand...
Click to collapse
Hi CCVader,
I've got a similar problem with my Huawei Vision that I bought/bricked yesterday. I managed to download an image file to my phone that was rooted and allowed me to boot to cwm. From the CWM Recovery screen I installed jellybean.zip, but after restart the phone hangs on the red Huawei screen. Every minute or so the screen goes black then comes right back to the red logo. Is this the 'first boot' you are describing above? Shall I just leave it doing this for 15 mins?
Thanks.
James.

jamesprocha said:
Hi CCVader,
I've got a similar problem with my Huawei Vision that I bought/bricked yesterday. I managed to download an image file to my phone that was rooted and allowed me to boot to cwm. From the CWM Recovery screen I installed jellybean.zip, but after restart the phone hangs on the red Huawei screen. Every minute or so the screen goes black then comes right back to the red logo. Is this the 'first boot' you are describing above? Shall I just leave it doing this for 15 mins?
Thanks.
James.
Click to expand...
Click to collapse
You can't just flash ROMs without the appropriate kernel istalled. U8850 comes with Gingerbread and with the GB kernel.
Flash this.

CCVader13 said:
You can't just flash ROMs without the appropriate kernel istalled. U8850 comes with Gingerbread and with the GB kernel.
Flash this
Click to expand...
Click to collapse
OK, I'll give that a go when I get home. The firmware you've linked me to - is this GB?
One thing that concerns me - the Software Update Tool detects my phone if I attach it while it is on CWM, but if I try to install the original image it keeps failing. Equally, trying to install a tested nb0 file from the stock recovery tool also now fails.
The little bit of home I have is that I can still get to CWM Recovery - as long as I can do this, does that mean there is a chance I can unbrick my phone?
Many thanks for the quick response.

[5.0] Nexus 5 Refuses To Flash OTA or Different ROM's

Hello,
So I just discovered this while trying to flash the 5.0.1 OTA from 5.0. I'm rooted on LRX21O via the Nexus Root Toolkit 1.9.9 (which is what I've always used in the past with no issues).
1 Tried flashing the OTA via Google notification push. It reboot, and no changes occur.
2 Fine - I try to use the Root Toolkit again. Boots into bootloader, appears to flash the radio and other necessary components. Reboots - no changes occur.
3 I then tried to just download the 5.0.1 package and flash everything manually via adb. Everything appears to go smoothly, and upon bootup Android updates all of its apps - still nothing. I appear to be completely stuck on LRX21O without any way to reflash stock or OTA's.
Anyone have any clue why this is occurring or have heard of such an issue before?
Thanks all.

Just flash factory images. With fastboot/flash-all script.
https://developers.google.com/android/nexus/images

You flash these in fastboot not adb
Sent from my Nexus 5 using Tapatalk

Did you not understand? I did flash in boot loader USING adb on my computer. All that bat script does is just automate the flashing of each image for you (system, radio, etc) so this is not helpful. I know how to flash, but flashing seems to have no effect despite successfully flashing via manually installing or just using the script

Sane116 said:
Did you not understand? I did flash in boot loader USING adb on my computer.
Click to expand...
Click to collapse
You use fastboot in bootloader, not adb.

I'm not the one asking for help. Anyways, carry on.

Your device's /system partition is tampered (you say you rooted it) and thus the OTA fails. Flash the 5.0 factory image (LRX21O) WITHOUT rooting/flashing kernels/whatever and then use the OTA zip to do adb sideload in the stock recovery to update to 5.0.1 LRX22C.

Manually use fastboot commands to flash system.img and boot.img of the full 5.0.1 factory image (not script). post the output please

I'm not the one asking for help. Anyways, carry on.
Click to expand...
Click to collapse
Sorry about that - didn't mean to come across snippy
It worked this time with fastboot. For future reference can this be done the same way with the OTA update zip instead of reflashing the entire image?

Sane116 said:
Sorry about that - didn't mean to come across snippy
It worked this time with fastboot. For future reference can this be done the same way with the OTA update zip instead of reflashing the entire image?
Click to expand...
Click to collapse
No, but if your phone is setup correctly you can sideload the ota zip in the stock recovery
Sent from my Nexus 9 using XDA Free mobile app

jd1639 said:
No, but if your phone is setup correctly you can sideload the ota zip in the stock recovery
Sent from my Nexus 9 using XDA Free mobile app
Click to expand...
Click to collapse
Would you mind explaining this? I've used sideload in cwm and twrp before but I'm unsure of how to operate anything within stock recovery. adb won't even connect while in recovery. I would like to just remain on unrooted stock until xposed eventually get's developed for ART and flash zips that way.

Sane116 said:
Would you mind explaining this? I've used sideload in cwm and twrp before but I'm unsure of how to operate anything within stock recovery. adb won't even connect while in recovery. I would like to just remain on unrooted stock until xposed eventually get's developed for ART and flash zips that way.
Click to expand...
Click to collapse
Sideloading in the stock recovery works much the same as in a custom recovery. Boot into the stock recovery and there is an option to sideload. Then on your pc in a command window you type adb sideload update.zip. or whatever the file name is that you're trying to sideload. Obviously, if you can't get adb to recognize your device that's a problem. But that's a separate driver issue.
Sent from my Nexus 9 using XDA Free mobile app

jd1639 said:
Sideloading in the stock recovery works much the same as in a custom recovery. Boot into the stock recovery and there is an option to sideload. Then on your pc in a command window you type adb sideload update.zip. or whatever the file name is that you're trying to sideload. Obviously, if you can't get adb to recognize your device that's a problem. But that's a separate driver issue.
Sent from my Nexus 9 using XDA Free mobile app
Click to expand...
Click to collapse
How can this be possible though without a custom recovery with the sideload feature? Stock recovery is essentially unusable as it just displays a picture of a dead android on a black screen.
Perhaps we're on different pages, or am I just confused still?

sideloading an OTA update from stock recovery
Hello, to make it work you will need to use the Google USB drivers you downloaded when you go into stock recovery then press the power button and volume up once then you will see a menu option with the "install update from adb option select this and plug in your phone to the computer. After this is done you will need to go to device manager and install the USB drivers from the Google USB drivers you downloaded. at this point after that is done you then go into the folder that has ADB installed and use adb sideload filename.zip
at this point your phone will accept the ota update package and you wont lose any data, I hope this helps..
-cs

Sane116 said:
How can this be possible though without a custom recovery with the sideload feature? Stock recovery is essentially unusable as it just displays a picture of a dead android on a black screen.
Perhaps we're on different pages, or am I just confused still?
Click to expand...
Click to collapse
When you get the dead android you need to press vol up and then press and release power. That'll get you into the stock recovery. It's stupid and I don't know why they made it that way
Sent from my Nexus 9 using XDA Free mobile app

thanks all, can't believe i never knew that volumeup+power got me into stock recovery options.
new issue: sideload works all well and perfect, but how can I bypass the "signature verification failed" flag that kicks me from the zip install every time?

Sane116 said:
thanks all, can't believe i never knew that volumeup+power got me into stock recovery options.
new issue: sideload works all well and perfect, but how can I bypass the "signature verification failed" flag that kicks me from the zip install every time?
Click to expand...
Click to collapse
Well you can't. The limitation of the stock recovery is you can only flash files signed by Google. That's why you need a custom recovery to flash most files
Sent from my Nexus 9 using XDA Free mobile app

jd1639 said:
Well you can't. The limitation of the stock recovery is you can only flash files signed by Google. That's why you need a custom recovery to flash most files
Sent from my Nexus 9 using XDA Free mobile app
Click to expand...
Click to collapse
So can I just flash twrp with fastboot and go about that method? I believe it can bypass the signature. I am unlocked without root currently.

Sane116 said:
So can I just flash twrp with fastboot and go about that method? I believe it can bypass the signature. I am unlocked without root currently.
Click to expand...
Click to collapse
If you're trying to flash the update.zip to 5.0.1 you need to do that in the stock recovery. It will not work in twrp or cwm. I'm not sure what you're trying to do right now
Sent from my Nexus 9 using XDA Free mobile app

my apologies.
so originally i wanted to just flash the OTA. ended up performing a fresh install and un-rooted. but there's a few unsigned zips i like to have installed.
So I think I'm going to re-root, flash twrp, install my zips, and leave it at that. i'll just flash stock recovery whenever I need the OTA which should be quick now that I know what to do.
hope that sounds correct. thanks for all the help!

Moto G XT1033 (India) problems updating to Lollipop

Hello everyone, I have a Moto G (2013) aka first generation Moto G & I live in India. I had unlocked my bootloader. I even flashed cwm touch via fastboot but it doesn't go to recovery mode at all. I get a black screen. I tried flashing the official TWRP 2.8.4.0 today, but I get a message that reads, "Partition size mismatch" & I'm stuck. The phone is usable & it boots up normally & I use it daily. But it is the recovery that is messed up. I tried updating to lollipop by ota but the device got stuck on a black screen once the ota was downloaded. I tried downloading the KitKat factory image, but the link is dead. Please, somebody help!! Thanks in advance!
Sent from my XT1033 using xda premium

The partition size mismatch error can be ignored, You get that error because the TWRP 2.8.4.0 is for the XT1032 and not the XT1033. To flash the OTA, you have to use the stock recovery only. Your system should not be modified (eg. It shouldn't be rooted, and if it had been rooted previously, you will have to unroot it.) To flash the stock recovery again, download the Asian XT1033 4.4.4 firmware and just flash the "recovery.img" from it. The flash the OTA. The numerous guides regarding this in the general section should help you.

I have a similar question.
I have unlocked bootloader & rooted moto g.
I received official OTA update today but its not installing. Do I need to lock bootloader or do something else to install the official OTA update?

Facing a similar issue. Updated the moto g and was successful. It was used for a couple of days before the error cropped up.
Now, it boots up but goes to a black screen after the boot animation. However, it still connects to the computer and I'm able to see the phone and its files in explorer. Beyond that, I can't interact with the phone because the screen is totally black.
Additionally, I can access the bootloader, but selecting 'factory' or 'recovery' isn't doing anything - just black screens everywhere.
The phone was perfectly fine for a few days after the update. (The phone is unrooted and unmodded and was running stock at lolipop update.)
Another thread suggests that I should
Code:
fastboot erase cache
fastboot erase userdata
Is that a viable course of action? Has anybody been able to recover from this issue?

pr.itdude said:
I have a similar question.
I have unlocked bootloader & rooted moto g.
I received official OTA update today but its not installing. Do I need to lock bootloader or do something else to install the official OTA update?
Click to expand...
Click to collapse
No need to lock. Unroot, reflash stock signed recovery and you should be good to go. Also undo any modifications you made to the filesystem and wiping /cache should help prevent errors.
---------- Post added at 02:42 AM ---------- Previous post was at 02:40 AM ----------
SoberDogs said:
Facing a similar issue. Updated the moto g and was successful. It was used for a couple of days before the error cropped up.
Now, it boots up but goes to a black screen after the boot animation. However, it still connects to the computer and I'm able to see the phone and its files in explorer. Beyond that, I can't interact with the phone because the screen is totally black.
Additionally, I can access the bootloader, but selecting 'factory' or 'recovery' isn't doing anything - just black screens everywhere.
The phone was perfectly fine for a few days after the update. (The phone is unrooted and unmodded and was running stock at lolipop update.)
Another thread suggests that I should
Code:
fastboot erase cache
fastboot erase userdata
Is that a viable course of action? Has anybody been able to recover from this issue?
Click to expand...
Click to collapse
Try fastboot erase cache, it shouldn't delete any of your data and it might be enough to get the device working again. You might want to wipe the dalvik-cache as well. If all else fails, since you can access you filesystem, backup all important files and do a factory reset.

skyguy126 said:
No need to lock. Unroot, reflash stock signed recovery and you should be good to go. Also undo any modifications you made to the filesystem and wiping /cache should help prevent errors.
Click to expand...
Click to collapse
Ok. Few more Q pls:
1. Reflashing stock recovery wipes system data & apps? After this my phone will be rooted or not? Any links where i can read more about it?
2. I have stock ROM but yes I installed xposed framework & few modules. Is it a filesystem modification?
3. Any other alternative to this?

pr.itdude said:
Ok. Few more Q pls:
1. Reflashing stock recovery wipes system data & apps? After this my phone will be rooted or not? Any links where i can read more about it?
2. I have stock ROM but yes I installed xposed framework & few modules. Is it a filesystem modification?
3. Any other alternative to this?
Click to expand...
Click to collapse
1. No it should not. If you had root before you will still have it. Search in the forum for more info.
2. Yes but you can easily uninstall xposed with the click of a button.
3. This is by far the easiest and safest method. I know of one alternative is to flash the ota update zip through custom recovery but you are on your own there.

skyguy126 said:
1. No it should not. If you had root before you will still have it. Search in the forum for more info.
2. Yes but you can easily uninstall xposed with the click of a button.
3. This is by far the easiest and safest method. I know of one alternative is to flash the ota update zip through custom recovery but you are on your own there.
Click to expand...
Click to collapse
ok so Here what i am planning:
1. Uninstall all modules & xposed framework
2. Unroot using supersu
3. Restore/reflash stock recovery (just recovery not whole firmware as I already have stock rom)
4. Install the update either manually via recovery or using auto install.
Am i on right path? Pls help me on step 3, any link or step-t-step guide? I couldn't find one, every post is abt restoring whole firmware.
TIA. Cheers !!

pr.itdude said:
ok so Here what i am planning:
1. Uninstall all modules & xposed framework
2. Unroot using supersu
3. Restore/reflash stock recovery (just recovery not whole firmware as I already have stock rom)
4. Install the update either manually via recovery or using auto install.
Am i on right path? Pls help me on step 3, any link or step-t-step guide? I couldn't find one, every post is abt restoring whole firmware.
TIA. Cheers !!
Click to expand...
Click to collapse
Yep you should be good good luck!!!