Develop Bugs

Anything special needed for flashing the Google factory restore images?

After initially trying the Android Revolution HD rom after rooting few days ago, I realized I wanted to go back to stock. I downloaded "https://dl.google.com/dl/android/aosp/mysid-icl53f-factory-65895fa8.tgz" off of http://groups.google.com/group/android-building/msg/2cd2b16ed56a7e84 for my Verizon LTE GN variant...
I extracted "image-mysid-icl53f.zip" and flashed it the usually way with CWM, ended up going into a boot loop. Luckily I had a Nandroid backup of my phone just after rooting so I was able to use that to restore back to stock...
Was there any reason that "image-mysid-icl53f.zip" didn't work? I read another unrelated (if I remember correctly) post on here about flashing the image with a modified script from Google, do I need to use the flash-all.sh or something when flashing this zip? Do I need the other files (bootloader-toro..., radio-cdma..., and radio-toro...)? Or did I just get unlucky and a reflash probably would have fixed it?
Thanks

You don't flash the zip with cwm. You need to do fastboot -w update blah.,ip command with it.
Search for the "convert yawuwhatever to yawublah" thread for the directions
Sent from my Galaxy Nexus

s1977 said:
Resetting the phone by taking out the battery shouldn't be a problem if you havent started flashing the new rom. I would try again after confirming that the fastboot and usb drivers can see the device before proceeding any further.
You can use fastboot devices to list attached devices. Only progress further once you can see your phone using the above command.
I did the same today a few hours ago and in my case, I started the phone in bootloader mode via Volume up + down + power button or via adb reboot bootloader. Then with fastboot, issue the fastboot oem unlock command to unlock the bootloader first. Once done, then you can flash the stock image (bootloader, radio and rom) with the following commands.
fastboot flash bootloader <bootloader image>
fastboot reboot-bootloader
fastboot flash radio <radio image>
fastboot reboot-bootloader
fastboot -w update <rom image>
Don't forget to lock the bootloader once done using fastboot oem lock
Just to clarify, depending on the version of the OS on your client PC/Mac/Linux, there are variants of fastboot. I use fastboot-mac from my mac.
Click to expand...
Click to collapse
Also try checking out this thread: How to? Change from yakjuxw to yakju

[Q] Very hard bricked. Please help!

So a couple nights ago everything was working just fine. Locked my Nexus 7 and went to sleep. The next morning I try to unlock it, but I just have a completely black screen. No backlight or anything. I force shut it off and try turning it back on. It gives me the TWRP loading screen and freezes there (I'm rooted with custom recovery but no custom rom). It does this twice, then booting gives me nothing. No Google logo, no boot animation, nothing. I boot into the bootloader and figure I'll re-flash my recovery and see if I can get to that. No commands will send via fastboot. I'm able to execute "fastboot reboot-bootloader", but nothing else works.
Now I'm familiar with switching USB ports and USB cables, but even after using two different cables (Nexus 7 2013 and Nexus 4) and about 6 different USB ports (both USB 3, and USB 2), nothing. I can't send a new recovery, new bootloader or anything.
So I figure I'll try re-locking the bootloader and then unlocking so it'll hopefully do a factory reset and might help. Well locking worked fine, however when I run "fastboot oem unlock" it brings me to the confirmation screen. I'm able to press the up volume button and press the power button to confirm, but after this it freezes and I have to do another force restart. I've reinstalled the USB drivers, reinstalled the Android SDK, and tried it on a different computer with no Android drivers at all. I've installed the offical Google USB drivers, used the Nexus Root Toolkit to install them, and used PDAnet to install drivers.
It's driving me crazy. It was literally working perfectly the night before, and the next morning it's like there's some catastrophic damage to the device.
Does anyone have any experience with this sort of extreme scenario?
Any help at all would be appreciated! Thank you!

Have you downloaded the factory Google image, then boot to the bootloader, and use fastboot commands to completely erase and reflash the stock image?
- Sent from my Galaxy S3

RMarkwald said:
Have you downloaded the factory Google image, then boot to the bootloader, and use fastboot commands to completely erase and reflash the stock image?
- Sent from my Galaxy S3
Click to expand...
Click to collapse
I was able to erase the boot image, recovery, user data, ect.. because I read to do that if you have intentions to reflash the factory images. However, this was still after my problem of not being able to unlock the bootloader. I think I may be able to flash the factory images if it weren't for the fact that every time I try to unlock the bootloader it freezes completely.

Did you let the tablet reboot after running "fastboot oem lock"?
---------- Post added at 02:46 PM ---------- Previous post was at 02:38 PM ----------
Did you flash the factory images after erasing them? After you run "fastboot oem lock", the device will reboot, but if you erased everything and didn't flash the images, nothing is there to boot to.
Download the Nexus 7 JSS15R OEM image.
Extract the compressed file to the folder where your fastboot.exe lives. Typically this is the platform-tools directory in the SDK.
Open a command prompt window where your fastboot.exe lives.
Type in the following commands and press enter after each one.
Code:
fastboot erase boot
fastboot erase cache
fastboot erase recovery
fastboot erase system
fastboot erase userdata
fastboot flash bootloader razor-jss15r/bootloader-flo-flo-03.14.img
fastboot reboot-bootloader
fastboot -w update razor-jss15r/image-razor-jss15r.zip
Wait for the image to flash. The tablet will automatically reboot, let it do so. Once done, rush through initial device setup, don't worry about Google credentials right now or anything. Once to the homescreen, reboot back into fastboot to run:
Code:
fastboot oem unlock
Then let the tablet reboot.
THESE INSTRUCTIONS ARE ASSUMING THIS IS THE WIFI VERSION ONLY. THEY'LL WORK FOR THE LTE, JUST REPLACE FOLDER AND FILE NAMES AS NEEDED.

[Q] Htc one Bricked Need help

I tried doing a manual ota update, only getting to flashing the firmware.So when I tried to flash the ota I was unable to due do it relocking my phone and wiping everything.I still have s-off but I cant do anything in fastboot since its not unlocked and my custom recovery was deleted leaving me with stock.Is my htc bricked? If so is there any way to get it to boot? Thanks

RubberThunder said:
I tried doing a manual ota update, only getting to flashing the firmware.So when I tried to flash the ota I was unable to due do it relocking my phone and wiping everything.I still have s-off but I cant do anything in fastboot since its not unlocked and my custom recovery was deleted leaving me with stock.Is my htc bricked? If so is there any way to get it to boot? Thanks
Click to expand...
Click to collapse
Not at all, you are fine. Since you are s-off, you can flash a stock RUU and start fresh.
Download this RUU - http://goo.gl/JEkyCk
Then follow this instruction -
Place the zip in your fastboot/adb directory on your computer.
Put the device in fastboot mode
(Volume down and power until menu appears, select fastboot using power button)
Connect the device to the computer
Enter the following commands from terminal/command prompt in the fastboot directory, one at a time:
fastboot oem rebootRUU (this puts the device in RUU mode)
fastboot flash zip rom.zip (rename file to rom.zip)
It will say that the update did not finish, to flush again, so repeat the above step:
fastboot flash zip rom.zip
That will leave you in stock 4.3 android, then you can just use a command line to unlock bootloader since you are s-off.
Hope I helped!

[Q] [HELP] Bricked Galaxy Nexus (maguro)

Hello guys, a friend of mine has a galaxy nexus with some problems.
When I turn on the phone, it starts booting normally, but a few seconds after getting into "desktop" it starts popping up errors saying that the process as stopped.
I've already tried a few things, but without success. I'm running out of ideas and here I'm asking for your help.
Things I've tried:
-Boot into recovery mode and wipe all data.
The phone says that the operation completed successfully, but after rebooting the phone remains the same. All apps, wallpaper, lock screen, etc. It seems that nothing was changed by this process.
-Flash a original google ROM
Following the tutorials, the first step is to unlock the bootloader with fastboot oem unlock. The phone shows a confirmation asking if I want to unlock it, I say yes, and it shows "status: unlocked". But after rebooting the phone it is locked again!!!
I tried to flash the room without rebooting the phone after unlocking it,
Code:
fastboot flash bootloader bootloader-maguro-primela03.img
fastboot reboot-bootloader
sleep 5
fastboot flash radio radio-maguro-i9250xxla02.img
fastboot reboot-bootloader
sleep 5
fastboot -w update image-takju-imm76i.zip
The first command to flash the bootloader also says that completes successfully, but when I'm flashing the radio it will complain saying that the phone has the wrong bootloader version installed.
-Flashing via Odin
It fails when is flashing system.img to the phone
-Flash custom recovery - fastboot flash recovery recovery.img
The process completes "successfully" but when I boot into recovery mode, there is the original one and not the one I just flashed.
-emmc brickbug - partition scanner
I found this thread http://forum.xda-developers.com/showthread.php?t=1823918 and tried to run the partition scanner. As I can't have the phone on enough time to use adb shell, I tried to use this scanner via adb sideload but the phones returns an error when running it. (probably because it doesn't have busybox installed, not sure)
After trying all of steps above, the phone is still the same... nothing changed. Once, I managed to connect it to the pc as an usb storage device, and was able to copy some photos from the phone and deleted them. But after rebooting they were all there again. It seems that all write changes are not persistent.
I'm out of ideas now... Do you have any idea of what is the problem? Or any suggestion for me to try?
Thanks in advance

I believe that there is a script in the android SDK tools called flashall.bat which will reflash the kernel, bootloader, recovery, ROM ect. I'm not sure how to use it, but you could potentially try that

Hi, thanks for you suggestion, but unfortunately it didn't work.
I had a look at the flashall.bat script and it runs the same commands I run manually.
I think that the phone might have some hardware problem... Normally I would buy a new phone, but I'm trying to fix it because it is important for my friend and for me because it is challenging.
I guess that the next thing I will try, will be trying to run emmc_find_brick script by @hg42 via sideload

Try formatting /system and reinstall android. Power your device into bootloader mode. Make sure your device is unlocked. Also, make sure you have the factory image downloaded. After your device is plugged in into your computer, use this fastboot command: fastboot erase system. This will delete everything from /system. Also format /data and /cache: fastboot erase data and fastboot erase cache. After that, try installing the factory image again.

Nexus 7 - 2nd gen: update failed to Lollipop 5.1

HI everyone,
I updated "successfully" from Kitkat to 5.0.2 on my rooted (stock ROM) Nexus 7 second gen.
Unfortunately, when I tried to upgrade to 5.1 everything seem to be normal until the device rebooted and it went through the "update process". 3/4 the way through, the green droid went on his back and the "ERROR" message appeared.
I wiped the cache partition but that doesn't help. I tried to download the update in safe mode, but no success. I also find it odd that each time I reboot my device, I get a message from Android that it is "updating my apps".
If I didn't have any apps and a lot of data on my Nexus, I would wipe the device clean but I'd rather avoid this, if at all possible.
Is there a way to upgrade to 5.1 or reinstall 5.0.2 without losing everything?
Thanks

Michael Carleone said:
Is there a way to upgrade to 5.1 or reinstall 5.0.2 without losing everything?
Click to expand...
Click to collapse
No problem. As you rooted it before then presumably it is unlocked and equipped with custom recovery, so all you have to do is:
boot TWRP
connect PC
transfer data and APKs to PC
flash OS
If you don't have TWRP installed, then boot it like this fastboot boot twrp-3.0.2-0-flo.img

k23m said:
No problem. As you rooted it before then presumably it is unlocked and equipped with custom recovery, so all you have to do is:
boot TWRP
connect PC
transfer data and APKs to PC
flash OS
If you don't have TWRP installed, then boot it like this fastboot boot twrp-3.0.2-0-flo.img
Click to expand...
Click to collapse
Hi,
Thanks for the reply. I rooted with Kingroot. I don't believe I have a custom recovery. The bootloader is locked as shown when I boot into recovery mode.
I want to avoid transferring my data and APK files to my PC.
Should I assume there is no way of reinstalling the OS without wiping out the device?Also, there is no link in the above quote: fastboot boot twrp-3.0.2-0-flo.img

Since I got no other replies, I went and restored to factory image. I do have another question. I hope I get a better response there: http://forum.xda-developers.com/nex...a/nexus-7-2013-wifi-root-marshmallow-t3515072

Thanks for the reply.
Can we compare using fastboot flashing TWRP vs Nexus Root Tool Kit: http://www.wugfresh.com/nrt/? I ended up using this utility instead because it was pretty much one click and it didn't require command lines and for whatever reason, I found instructions using fastboot a bit confusing. Which method is better or has more advantages? I left my bootloader unlocked.
Incidentally, I think there was something wrong with my Nexus image. As a result, I did use Google's instructions on how to flash etc. the OEM image. Instructions weren't ideal but I managed to figure things out: https://developers.google.com/android/images
The instructions are here which I assume would be similar if I wanted to fastboot TWRP?
To flash a system image:
Download the appropriate system image for your device below, then unzip it to a safe directory.
Connect your device to your computer over USB.
Start the device in fastboot mode with one of the following methods:
Using the adb tool: With the device powered on, execute:
adb reboot bootloader
Using a key combo: Turn the device off, then turn it on and immediately hold down the relevant key combination for your device. For example, to put a Nexus 5 ("hammerhead") into fastboot mode, press and hold Volume Up + Volume Down + Power as the device begins booting up.
If necessary, unlock the device's bootloader by running:
fastboot flashing unlock
or, for older devices, run:
fastboot oem unlock
The target device will show you a confirmation screen. (This erases all data on the target device.)
Open a terminal and navigate to the unzipped system image directory.
Execute the flash-all script. This script installs the necessary bootloader, baseband firmware(s), and operating system.
Once the script finishes, your device reboots. You should now lock the bootloader for security:
Start the device in fastboot mode again, as described above.
Execute:
fastboot flashing lock
or, for older devices, run:
fastboot oem lock
Locking bootloader will wipe the data on some devices. After locking the bootloader, if you want to flash the device again, you must run fastboot oem unlock again, which will wipe the data.
Click to expand...
Click to collapse
Also, I could've sworn that when I rooted KitKat on my Nexus, my data wasn't wiped out. I don't recall doing anything to the bootloader. I can't recall which method I used, but I know for certain I didn't use the Nexus Root Toolkit. I should've recorded my steps when I rooted.

i rooted my nexus 7 using towel root on kitkat .. i unrooted using supersu... and ota untill marhsmallow with out a problem never use kingroot as its so un stable.