Database Develop

[Q] Really basic help needed updating to 5.7.906

Hi guys, total noob in your midst but need about 2 minutes of help :fingers-crossed:
(Firstly i should say that my phone was bought on Verizon, unlocked, and is now running on 3 in Ireland)
My droid 3 is running 5.6.890.xt862.Verizon.en.US, i tried to get the 5.7.906 OTA update, it will download perfectly, it starts to install but then it just reboots and says "Update Failed"
So i downloaded the file here http://forum.xda-developers.com/showthread.php?t=1643521
I don't understand bootstrap, have no interest in rooting my phone,
if I just put that on my SD card, can I install it in recovery mode?
My main problem is that the 3g keeps dropping, and won't reconnect once its dropped, so really hoping this update will fix/help this

Youll probably have to root.
Sent from my xt862 using xda app-developers app

You can try to flash it with the phone recovery.
- put the update-zip-file on your external (!) sd-card (not the internal phone memory)
- switch your phone off
- press and hold the key "x" on your phone-keyboard
- power on the device
- when you see the android: stop pressing x, pess both volume keys at the same time
- you now navigate up/down with the volume keys and you choose with the powerbutton
- use "apply update from sdcard", choose your file, yes, done

g747m said:
Hi guys, total noob in your midst but need about 2 minutes of help :fingers-crossed:
(Firstly i should say that my phone was bought on Verizon, unlocked, and is now running on 3 in Ireland)
My droid 3 is running 5.6.890.xt862.Verizon.en.US, i tried to get the 5.7.906 OTA update, it will download perfectly, it starts to install but then it just reboots and says "Update Failed"
So i downloaded the file here http://forum.xda-developers.com/showthread.php?t=1643521
I don't understand bootstrap, have no interest in rooting my phone,
if I just put that on my SD card, can I install it in recovery mode?
My main problem is that the 3g keeps dropping, and won't reconnect once its dropped, so really hoping this update will fix/help this
Click to expand...
Click to collapse
That update must be installed through your stock recovery not a custom recovery..
1.download the update to your phone
2.move it to your external sdcard..most file managers will do it
3.boot into your stock recovery..power off phone then power it up holding the pwr + x
4.install .zip

SGH-i957 LTE (Rogers) - OTA update FAIL, only CWM works

Hello fellow XDA'ers!
I have come into possession of a tablet that has the following problem:
When applying the OTA update to the SGH-i957 LTE tablet from Rogers, the previous owner plugged in the tablet into a mains power supply.
Because of this, I was told that the OTA update did not "complete." Specifically, at device reboot, the tablet was not accessing the newly updated ROM. At this point, the owner went into a bit of a panic:
- They hooked up the device to ODIN3 v1.85, with no response;
- They wiped all data & performed a factory reset;
- They wiped the cache partition;
- They formatted /cache;
- They formatted /data;
- They formatted /system
- They also made sure all settings were clear.
I tried to restore via Nandroid, but I get the following output via CWM-based Recovery (v5.5.0.4):
Code:
restoring boot image...
restoring system...
restoring data...
".android_secure.img not found. Skipping restore of /sdcard/.androidsecure."
restoring cache...
Restore complete!
Obviously, this isn't good. But wait, there's more! When I am trying to activate the option to "mount USB storage," I get the following error:
Code:
E: Unable to open ums lunfile (No such file or directory)
I opened the CWM recovery log, and like the Stanley Kubrick movie "The Shining," the log printed following 10 to 12 times:
Code:
failed to open /sys/class/android_usb/android0/state: No such file or directory.
I have yet to connect the device to my computer, as I don't want to mess it up any further. The tablet is currently plugged in to a mains power supply, awaiting resurrection.
I have experience in successfully restocking & flashing my Samsung Galaxy Tab (GT-P1000) via ODIN with Overcome/CM9, so I am more than happy to troubleshoot and thoroughly document anything that is happening with the tablet.
I have searched this specific forum for threads that relate to OTA failed updates, but I have not seen a similar thread or post.
I fully promise to document this problem in this thread if other people have issues in the future relating to this problem.
Therefore, how do I bring this tablet back to its former glory of sweet LTE-goodness?
Thanks,
willing_to_cooperate

Download the file here: http://www.sammobile.com/firmware/?page=3&model=SGH-I957R&pcode=RWC&os=1&type=1#firmware
Get into download mode, Use Odin to apply it. That should get your tab running again.
I went through something like this a little while ago.
Sent from my SAMSUNG-SGH-I957 using XDA Premium HD app

It works! It came back from the dead!
Eun-Hjzjined said:
Download the file here: http://www.sammobile.com/firmware/?page=3&model=SGH-I957R&pcode=RWC&os=1&type=1#firmware
Get into download mode, Use Odin to apply it. That should get your tab running again.
I went through something like this a little while ago.
Sent from my SAMSUNG-SGH-I957 using XDA Premium HD app
Click to expand...
Click to collapse
It worked!
For anyone that may have the same problem:
1) Put SGH-i957 into download mode (turn off, then hold power and volume up-down keys):
2) When you see a warning, make sure to press the volume up key (therefore, if you're looking at the tablet screen with the power cord outlet on the left hand side, it would be the bottom rocker button, furthest away from the power button).
3) Connect to ODIN v1.85.
4) Load the firmware into the PDA slot.
5) Make sure that Re-Partition and Flash Lock are NOT checked.
6) Make sure that Auto Reboot and F. Reset Time are checked.
7) Press start.
The tablet will go through its process, and may reboot 1-2 times. It will build a cache (you will see the Android figure with a geometric ball rotating in its stomach).
After that, it should boot into your carrier's logo screen, with setup of the device.
Thanks again, Eun-Hjzjined!
willing_to_cooperate
---------------------------EDIT:
This process also removes root from the tablet. However, no hiccups when re-installing root.

Hi thanks for all your help!
I have an i957 on ATT in the US, and previously had rooted with DaG v2 Kernel, worked great.
Yesterday I used the stock i957M (Bell) Update to get on ICS. Failed on Modem (known issue mo XDA), but rebooted and works fine.
It removed the root (as yours did above) - when I tried to re-root with same kernel on ODIN, everything locked up. Had to re-do the firmware with ODIN as in your entry above - now back in action.
Question: If there was some way you re-did your root so it was compatible with your build, can you point me to it?
Did some searching around, and only found dated sources that talked to how I did original root.
Maybe you have some magic.
Sure would be nice to get SU and CWM again, rather than stock.

Nevermind - Got it working - used "Method 1" - Stock Kernel from http://forum.xda-developers.com/showthread.php?t=1401100

Dumb, Dumber and me

N900A (AT&T so no custom recovery).
Rom de la Vega worked fine, got root. Loaded some apps, some needing root, some not. Didn't trigger the 0x1, it''s still 0x0.
Everything worked fine until ... well, I don't remember exactly what I did, but it wasn't anything close to "stupidest move ever made". Phone now boots to the Samsung logo with the circles orbiting each other, then goes to the AT&T symbol with a few (about 4) bars of music, and stops. No soft keys (they do flash on for about half a second) and the home key does nothing.
If I wait a few seconds, it reboots, back to the unlocked lock, the "Custom", the Samsung orbits, etc. I assume that's a boot loop.
ADB doesn't see a device. I can boot into recovery (standard AT&T thing), download or standard boot, but ADB doesn't see any device. (The computer is set up correctly - plug my wife's N900A into the same cable and Kies reads it immediately.)
I've tried N900AUCUBMI1_OneClickBin and it seems to run properly, running Odin 3.09 after about 5 minutes. Press Start and the files start downloading. (Port 22, but I''ve learned not to argue with Win7 serial port assignments.) It finishes with all files listed and a green "passed". The pnone boots into the little green guy, then into the boot loop. This is with the original 16GB microSD, a clean 2GB microSD or none at all. I've cleared cache/system or not - same results.
I can't finish the rest of the procedure, because I can't put anything into internal storage - because the computer doesn't see the phone.
I'm at the end of my knowledge. I don't know how things are laid out in Android, so I don't know what to flash or if there's anything I can flash to fix anything.,
Oh - nothing shows on the computer - no Phone and no Card. If USB debug got turned off, I don't know of any way to turn it on from outside. I can't run any Android apps, of course. It I have to, I can install Linux on a partition on this laptop, but is there something I can do to just get back a plain working (preferably rooted) Note 3?
If not, I'm going to have to go back to the big blue and yellow place and feign stupidity, and hope all the boot looping articles will convince them that this is just another one.

You didn't update to the latest MJ 5 firmware, did you? ,accidentally and then try the one click to mi 1?
Sent from my SAMSUNG-SM-N900A using Tapatalk

tdamocles said:
You didn't update to the latest MJ 5 firmware, did you? ,accidentally and then try the one click to mi 1?
Click to expand...
Click to collapse
That's possible. I''ve been looking for links to MI5 and MI9 but with all the deleted links, I haven't been able to find any. All I have is MI1 and the MI9 file with the .tar.md5 files, which I'm reluctant to use, in case I cause a hard brick.

Failed downgrade from Nougat to MM bricked my EVA-L09

Recently I tried out the Nougat preview on my EVA-L09C636. It was ok but seeing as there was a problem with fonts and I'd lost root access, I began thinking about going back to MM.
To prepare for downgrade I tried using srktool to bring TWRP back (and I think this is my big mistake as srktool uses a TWRP made for MM, not N, is that right?). After I tried to restore TWRP I noticed "not recognised" errors when I connected my phone to PC again.
System recovery using hajuuk's Firmware Updater and HiSuite looked like it would complete but near the end of the process (the restoring system part) HiSuite aborted itself saying my device wasn't supported. This has left my P9 is in an unusable state where the only thing I can access is fastboot. Also I can't turn off my phone - holding down power simply makes it reboot then get stuck at the "Your device ... can't be trusted / Your device is booting now" screen.
Reading around a bit I attempted to unbrick it without any luck:
1. downloaded EVA-L09C636B152 update.zip from http://forum.xda-developers.com/p9/development/rom-stock-rom-eva-l19c636b168-t3419586 and installed Snoop05's 15 seconds ADB Installer.
2. extracted images from update.zip using Huawei Update Extractor and did
Code:
fastboot flash system system.img
fastboot flash recovery recovery.img
fastboot flash boot boot.img
fastboot flash cust cust.img
then tried rebooting holding volume up + power several times (but never got past untrusted device boot screen).
3. extracted contents of update.zip to folder 'dload' on a blank sd card, trying to force update several times by rebooting and holding down power + volume up + volume down (still never get past the screen saying my device is booting).
At this point I'd be happy to get anything happening on my phone - Marshmallow, Nougat or even some other ROM so I can use my device again.
Any ideas? I'm on EVA-L09 C636.

i2ectcf said:
Recently I tried out the Nougat preview on my EVA-L09C636. It was ok but seeing as there was a problem with fonts and I'd lost root access, I began thinking about going back to MM.
To prepare for downgrade I tried using srktool to bring TWRP back (and I think this is my big mistake as srktool uses a TWRP made for MM, not N, is that right?). After I tried to restore TWRP I noticed "not recognised" errors when I connected my phone to PC again.
System recovery using hajuuk's Firmware Updater and HiSuite looked like it would complete but near the end of the process (the restoring system part) HiSuite aborted itself saying my device wasn't supported. This has left my P9 is in an unusable state where the only thing I can access is fastboot. Also I can't turn off my phone - holding down power simply makes it reboot then get stuck at the "Your device ... can't be trusted / Your device is booting now" screen.
Reading around a bit I attempted to unbrick it without any luck:
1. downloaded EVA-L09C636B152 update.zip from http://forum.xda-developers.com/p9/development/rom-stock-rom-eva-l19c636b168-t3419586 and installed Snoop05's 15 seconds ADB Installer.
2. extracted images from update.zip using Huawei Update Extractor and did then tried rebooting holding volume up + power several times (but never got past untrusted device boot screen).
3. extracted contents of update.zip to folder 'dload' on a blank sd card, trying to force update several times by rebooting and holding down power + volume up + volume down (still never get past the screen saying my device is booting).
At this point I'd be happy to get anything happening on my phone - Marshmallow, Nougat or even some other ROM so I can use my device again.
Any ideas? I'm on EVA-L09 C636.
Click to expand...
Click to collapse
did you wiped data, cache, dalvik?

snapdesign said:
did you wiped data, cache, dalvik?
Click to expand...
Click to collapse
Hi! I'm not sure how to wipe data, cache or dalvik, because when I upgraded to Nougat this apparently removed TWRP.
Also I'm wondering if trying to use srktool to reinstall TWRP for 6.0 might have corrupted my 7.0 phone?
Is there any way to wipe data, cache, and/or dalvik now? Or are there other things I could try to unbrick?

Although my phone was in a pretty bizarre state - it would get hot and sit on the booting now screen until battery died - I was able to use DC Phoenix to make it boot up again. At that point it had no themes and only KitKat-esque icons. A reset and upgrade later icons and themes work and I'm back on stock Marshmallow. Here's an outline:
1. Google "Huawei Bricked phone repair guide with DC Phoenix", go to the first result and look at the instructions (I can't post URLs yet).
I used Method 1. But note! The newer versions of DC Phoenix are missing a feature that the instructions make clear you have to use. To get the original version used in their guide, you have to download the latest version of DC Phoenix, open it on your PC, then click "Enter Support Area" which logs you in to a download section. Find "DC Unlocker Softwares", "DC_Phoenix", then download DC_Phoenix_v14.rar and run that instead. Whether it's Method 1 or 2 make sure you complete it - i.e. the fastboot flash step AND a step they call "flashing in upgrade mode."
(Also note that for DC Phoenix you want to feed it the oldest version of firmware available for your phone, in my case b152. This is because themes and icons won't be fixed until it receives the next version of firmware as an update.)
2. Once I did the fastboot and upgrade flash, I did a system reset from the Settings app trying to get themes and current icons again. (This didn't work but doesn't do any harm or might have helped somehow further down the line).
3. I used hajuuk's Firmware Updater and HiSuite to upgrade to the next version of firmware available (in my case b168).
3. All fine and your phone is back to stock - icons look nice again and local themes are back. To get the original icons layout, go to Recents, hold down on the Trash Icon, show system apps, and Clear Data for Huawei Home.

i2ectcf said:
Although my phone was in a pretty bizarre state - it would get hot and sit on the booting now screen until battery died - I was able to use DC Phoenix to make it boot up again. At that point it had no themes and only KitKat-esque icons. A reset and upgrade later icons and themes work and I'm back on stock Marshmallow.
Click to expand...
Click to collapse
Thanks for sharing! You saved me!

Nexus 6 stuck on boot-up color splash scrn - after flash Mar17 Marsh +root+xposed

I am currently stuck for 45+ minutes at the google reboot splashscreen (4 colorful spinning dots that eventually should turn into the word android once reboot is complete).
I followed an update procedure that I have used many times (last done November 16), although some of the files involved are somewhat old.
Starting from November 16 update for Marshmallow:
1 - Fastboot-Flashed that March 2017 factory image for Marshmallow (yes, there is still a Marshmallow... I dont' want Nougat yet). Flashed all partitions except data and recovery.
2 - Reboot directly into TWRP (I believe it is TWRP 3.0.2... I haven'te changed it recently)
3 - In TWRP: Flash superuser BETA-SuperSU-v2.65-20151226141550 i
4 - In TWRP: Clear space from app/system by deleting foreign language directories (to make room for xposed)
5 - IN TWRP: Flash xposed xposed-v79-sdk23-arm
6 - In TWRP - initiate reboot to system.
7 - As system rebooted, I entered my PIN.
That's where I am now. Note I never saw a screen for "optimizing apps" that was expected. I
Note I never rebooted to android system, so I'm not sure which step caused the problem (it was a method I developed to update quicker although in retrospect rebooting each step to check would be smarter).
I have some ideas of what to do eventually: (retry my flash one step at a time)
BUT, I don't know how to do anything with a phone that is stuck on the splashscreen:
* It does not respond to key combination on/volume-down (which normally goes to fastboot)
* When plugged into pc, it does not respond to fastboot devices
* There is no battery pull option on this phone.
What to do next to get control of my phone... let the battery run out on the splash screen?

Hmmm. Weird. Just held power-on and vol-down and it took me briefly to a different screen (android?) and then promprted for PIN, then back to splashscreen.

I kept pressing that combo and eventually did get into fastboot.
Now I'll flash again.

electricpete1 said:
I kept pressing that combo and eventually did get into fastboot.
Now I'll flash again.
Click to expand...
Click to collapse
Hello. Not sure what caused your problem. Also, i don't use Xposed...
Just a heads up... Your SuperSU is really really old. Just use this one:
https://download.chainfire.eu/1021/SuperSU/SR3-SuperSU-v2.79-SR3-20170114223742.zip
Good luck...

The version of SuperSU he used likely was the cause of the bootloop.

5.1 said:
Hello. Not sure what caused your problem. Also, i don't use Xposed...
Just a heads up... Your SuperSU is really really old. Just use this one:
https://download.chainfire.eu/1021/SuperSU/SR3-SuperSU-v2.79-SR3-20170114223742.zip
Good luck...
Click to expand...
Click to collapse
I reflashed the system and then flashed newer files:
SR3-SuperSU-v2.79-SR3-20170114223742.zip
xposed-v87-sdk23-arm
(with a reboot between flashing SU and flashing xposed).
Everything booted up fine.
Problem solved.
Thanks for the help!

Aren't you supposed to fastboot boot, not flash the su with marshmallow?