Database Users

[Q] Unzip official update and flash contents ok to do? Can't OTA from 4.2.1 to 4.2.2

Hello all,
I did not see this in any of the other numerous threads and was wondering if this would work. I downloaded the official 4.2.2 update being I can not OTA it. The update always fails when CWM comes up. I am rooted and used the Nexus 4.0 root kit to root the tablet originally. I have upgraded the bootloader to 4.18 by pushing the image file and fastboot and was wondering if I could do the same for the system and user data file images as well to upgrade. I have Voodoo OTA root keeper as well.
From what I can see in the flash-all.bat file that comes with the update this is its contents:
PATH=%PATH%;"%SYSTEMROOT%\System32"
fastboot oem unlock
fastboot erase boot
fastboot erase cache
fastboot erase recovery
fastboot erase system
fastboot erase userdata
fastboot flash bootloader bootloader-grouper-4.18.img
fastboot reboot-bootloader
ping -n 10 127.0.0.1 >nul
fastboot -w update image-nakasi-jdq39.zip
echo Press any key to exit...
pause >nul
exit
From what I can tell this script is just to do all the standard wipes but take it a step further to basically format the tablet to allow the install of the update.
From inside the image-nakasi-jdq39.zip I find the following files:
android-info.txt which only has one line of text in it which is:
require board=grouper require version-bootloader=4.18
boot.img << I am assuming this is the upgraded bootloader
recovery.img << Stock recovery instead of TWRP or CWM
system.img << The meat and potatos of 4.2.2
userdata.img << no clue but i'm assuming its important being it is 104 meg file.
If I temp unroot with Voodoo OTA root keeper then push system.img and userdata.img through fastboot should it:
1) overwrite anything causing the OTA to fail originally?
2) cause any damage?
3) allow me to keep CWM without losing all my data?
4) work?
Thanks for any help ahead of time :good:

[Q] Kitkat big mess, bootloop only! Any help?

Hi there,
I think I screwed in such a fashioned manner that I did not spot any spot to better expose my issue.
I run a Nexus 4 root which used to run fine with 4.3.
I did ota to Nexus 4.4 failure.
Then I did Efrant guide (without step 10) to go 4.4, it worked.
fastboot devices
fastboot reboot-bootloader
fastboot flash bootloader bootloader-mako-makoz20i.img
fastboot reboot-bootloader
fastboot flash radio radio-mako-m9615a-cefwmazm-2.0.1700.84.img
fastboot reboot-bootloader
fastboot flash system system44.img
fastboot flash boot boot44.img
fastboot flash recovery recovery44.img
fastboot format cache
fastboot reboot
I had really bad experience with kitkat. No notification, sms history gone, home virtual button not working (only blipping), same for the top right notification menu.
Well I thought going to 4.3 would be best.
I did 4.3 through the same steps with different archives and boot loop at the X.
Then I tried a 4.2.2 but I did a huge mistake, I did it with Nexus 7 files. After sweating a bit I got it back in fastboot mode.
Then I tried 4.3 occam and 4.4 occam. Bootloop, old style and new one.
Now I can try 4.2.2 or 4.4 with fastboot flash userdata userdata.img
Any clue?
Edit: From Efrants:
Note that some users indicate that they can't get past the X on boot. If this happens to you, reboot into the bootloader and select recovery. Then, when you see the Android with the red exclamation mark, hold power and press volume up to take you to the menu. Wipe cache. If that still doesn't work, boot back into recovery and do a factory reset (this will obviously delete all your data & files in /sdcard...).
I can go to the red exclamation mark.
Than all the combinations I do just reboot me. What is the trick? Power on then volume up? Power on and volume up at the same time? How long should I press?

Try this
Get proper files for let's say 4.3 mako
fastboot erase system -w
fastboot erase boot
fastboot erase recovery
fastboot flash radio radio.img
fastboot flash bootloader bootloader.img
fastboot flash recovery recovery.img
The bootloader and radio being from stock ota from Google, recovery stable custom one
fastboot reboot-bootloader
Make sure all matches
Boot to recovery
Flash ROM of choice, use a 4.3, maybe slimbean
May need to sideload the ROM though
Sent from my Nexus 4 using XDA Premium 4 mobile app

demkantor said:
Try this
Get proper files for let's say 4.3 mako
fastboot erase system -w
fastboot erase boot
fastboot erase recovery
fastboot flash radio radio.img
fastboot flash bootloader bootloader.img
fastboot flash recovery recovery.img
The bootloader and radio being from stock ota from Google, recovery stable custom one
fastboot reboot-bootloader
Make sure all matches
Boot to recovery
Flash ROM of choice, use a 4.3, maybe slimbean
May need to sideload the ROM though
Sent from my Nexus 4 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
OK I get the idea. By flashing the ROM of your choice what do you mean, flashing an OTA zip? I know how tosideload, just trying to understand what to flash.
I am about to try to flash a recovery (twrp) to wipe cache.
I tried and added system and boot.
/!\ fastboot erase system -w Erase all userdata I wanted to do that as a last option... Well now it is done...
The phone is now properly booting a 4.2.2 I will see tonight if I can get it to 4.3 or 4.4

ROM of choice is ROM of your choice, hence the recommendation for slimbean but only a recommendation
The fastboot erase system -w will cover wiping cache, but yeh still download and install the twrp image
Sent from my Nexus 7 using Tapatalk 2

demkantor said:
ROM of choice is ROM of your choice, hence the recommendation for slimbean but only a recommendation
The fastboot erase system -w will cover wiping cache, but yeh still download and install the twrp image
Sent from my Nexus 7 using Tapatalk 2
Click to expand...
Click to collapse
Well thanks for your help.
I think that my first install of 4.4 was messy. I really suspect that I installed bad radio and or bootloader. Thank you google for giving same name to different versions. Or may be I got some corrupted stuff on userdata?
When I went back to 4.3 I dont know what went wrong, maybe only that cache issue?
Then messing with the nakasi img (call me stupid) could not do any good.
I took too much confidence in messing the previous upgrades and recovering without loosing personnal data...
Now I have a fresh start to think about it...

I've got one question and one question only: how do I install 4.3 again on my nexus 4 again. I have NEVER rooted or flashed my phone. Would really really appreciate all the help I can get.

omairanwar said:
I've got one question and one question only: how do I install 4.3 again on my nexus 4 again. I have NEVER rooted or flashed my phone. Would really really appreciate all the help I can get.
Click to expand...
Click to collapse
fastboot oem unlock
fastboot flash recovery recovery.img
reboot to recovery
flash rom of choice
There are many guides on rooting and fastboot, i would suggest staying away from any toolkit
as if you would like to learn, you wont from a toolkit.
the above take minuets and is far from a difficult task, its a nexus, its meant to be easy.
peek your nose around the forum a bit, you have any issues or are unsure just ask and id be glad to help

[Q] Nexus Player is dead?

I just try to root my new nexus player and I don't know what happened there.
After success installation tried to install SuperSu and rebooted it. And device still loading I don't know why?
I did it in MAC OSX Yosemite
I have this screen already 4 hours
What should I do here

Not dead, it just bootloops (softbrick)
Get familiar with fastboot and bootloader mode
google or youtube on how to start the nex player in bootloader mode.
Download the latest image from Google here https://developers.google.com/android/nexus/images#fugu
Untar and unzip the .img files. You should be able to flash the system via fastboot
Command is:
fastboot flash system "path/to/system.img"

I tried Chainfires root method and the same thing happened to me, I don't think he's updated root for 5.1.1 yet. Using ADB
Download the image from above and follow the commands in terminal. They all start with ./
fastboot flash bootloader <drag bootloader image from finder to here>
fastboot reboot-bootloader
sleep 5
fastboot -w update <drag image zip from finder here>

tomalak007 said:
fastboot -w update <drag image zip from finder here>
Click to expand...
Click to collapse
You can do this command without the -w flag and it'll leave your /data/ partition intact. That usually fixes things. Then you can boot chainfire's root image to get root back. But updating the binaries will get you stuck at the boot screen. I actually had to go through this myself when I flashed the 5.1.1 factory image.

Right after booting from the root image, i had a similar problem. I turned it off and turned it back on and it worked. Chances are you either flashed boot.img or system.img so i don't think you should have a problem reflashing if you still can't boot after restarting. Also you may need to wipe in recovery.

i am having same problem also please tell us how to fix this .

Not dead. Which guide did you follow?

MX4 bootloop brick after trying to update I firmware on A phone

SOLVED:
Hi,
I just bricked my MX4 after trying to update system image from 4.5.6 to 4.5.7 using this guide:
Extract I version update.zip
use sdat2img to create system image
dd system image to system partition on live phone and reboot.
I used the same procedure successfully before, x-updating 4.5.4A ti I then updating to 4.5.6I.
After updating to 4.5.7, the phone goes into an infinite loop of Meizu splash screen, Flyme balloon, reboot.
I can enter fastboot and official recovery, but can't flash any partition from fastboot.
The bootloader is still locked.
Does anyone have any advice for unbricking?
Update:
The bootloop suddenly froze up for long enough for me to use adb to push an update.zip to the "sdcard" root. Have now flashed 4.2.8A from recovery and booted the phone.
As I had to clear all data I will unlock bootloader before trying anything else.

Try do flash 4.2.8.2 with uboot.img modded (to reunlock bootloader) and reboot fastboot and tell me

bobslesbricoleurs said:
Try do flash 4.2.8.2 with uboot.img modded (to reunlock bootloader) and reboot fastboot and tell me
Click to expand...
Click to collapse
Hi,
I managed to push 4.2.8.2 to sdcard then do a normal recovery reflash.
Have now successfully unlocked using the .apk method.
Now I need to find out if I can use that unlocked bootloader to flash recent "I" firmwares, or if I can only flash the unfinished cyanogen (would like to wait 'til that's a bit more polished before using it.
Anyway. Happy to have my phone back!

Maybe that newest 4.5.7I need a new kernel so you'll need to update to 4.5.7A before flashing system.img or you can flash directly 4.5.7I but you'll need to use fastboot flash boot boot.img
If a rom/firmware needs a specific kernel it'll bootloop if you don't flash it

Can I flash 4.5.7 I now that I have unlocked bootloader and custom recovery? If I understand the unlock threads correctly, I think I will relock the bootloader, or even brick if I try to flash the complete update.zip. Can I flash system and boot partitions using fastboot?

Fully BRICKED.
Now I FULLY bricked it (no more recovery).
Had successfully upgraded to 4.5.7 "I" and was installing super su for full root, before disabling update, but had forgotten that I still had official 4.2.8 rom as update.zip on "sdcard" root.
rebooted to TWRP recovery for full su install and recovery found the update.zip and flashed it.
Result: Bootloop, No recovery, locked fastboot, no possibility to flash anything.
Aaargh!

Where do I find a 4.2.8 recovery.img for this phone?
Maybe there's a possibility doing a fastboot boot recovery.img ???
NOPE:
[email protected]:/home/marius/Downloads# fastboot boot recovery.img
downloading 'boot.img'...
OKAY [ 0.662s]
booting...
FAILED (remote: unknown command)

Fixed with large hammer! Goodbye Meizu!
Learnincurve said:
Where do I find a 4.2.8 recovery.img for this phone?
Maybe there's a possibility doing a fastboot boot recovery.img ???
NOPE:
[email protected]:/home/marius/Downloads# fastboot boot recovery.img
downloading 'boot.img'...
OKAY [ 0.662s]
booting...
FAILED (remote: unknown command)
Click to expand...
Click to collapse
Fixed with large hammer! Goodbye Meizu!

fastboot boot recovery.img isn't a command at all... It's fastboot flash recovery C:/path/to/recovery.img

System delete..

Hello! I have an P8Lite ALE-L21 unlocked and by mistake I delete the system.. Now I don't have OS to boot
What can I do now to have back?

Download the rom for your phone then install the rom using the recovery system op the phone.
If that doesn't work try flashing the rom through fastboot.

EpicBas said:
Download the rom for your phone then install the rom using the recovery system op the phone.
If that doesn't work try flashing the rom through fastboot.
Click to expand...
Click to collapse
I tried both but it dosen't work
I don't find source with system.img

Use this http://forum.xda-developers.com/showthread.php?t=2433454&page=31 to extract the system.img
- Fastboot flash boot boot.img
- Fastboot flash recovery recovery.img
- Fastboot flash cust cust.img
- Fastboot flash system system.img
- Fastboot reboot
Use those commands and I hope it will be fixed.