I am not a noob when it comes to android dev, but this has stomped me and I am asking for expert's help. I have a GSM version SGN that I flashed the official yakju ICL53F on it via fastboot. It has been working great for a month now. Suddenly today I felt it was vibrating in my pocket, took it out and discover it was stuck in boot loop--the google sign with the unlocked icon. I waited til I get home to put clockworkmod on it, but when I try to nandroid it first it gave me an error. Then I figure I would just fastboot the stock rom on it again, using fastboot mode like I did before. I even flashed the bootloader, radio, and system image. Still stuck on google icon with screen went blank, vibrate and repeat. Is there anything else I should try? odin mode is also available, but I am not seeing any instructions on it at the developer section so I am reluctuant to try it. I can still adb and fastboot to access my phone...help please?
well I am no noob but I am no expert either. Apparently you cannot
fastboot flash system XXXXstock_image.img, you have to use
fastboot update -w XXXstock_image.img instead.
still I am baffled by why this happened in the first place. I was ready to lock the bootloader back up and send it in for warranty...glad I didn't have to resort to that.
lettcco said:
well I am no noob but I am no expert either. Apparently you cannot
fastboot flash system XXXXstock_image.img, you have to use
fastboot update -w XXXstock_image.img instead.
still I am baffled by why this happened in the first place. I was ready to lock the bootloader back up and send it in for warranty...glad I didn't have to resort to that.
Click to expand...
Click to collapse
I think you are mixing some things up.
The "update" parameter of fastboot is used to flash a group of images inside a zip file to you device.
The "flash" parameter is used to flash a single image to your device.
The following two groups of commands do the same thing:
fastboot update -w image-yakju-icl513f.zip
or
fastboot flash system system.img
fastboot flash boot boot.img
fastboot flash userdata userdata.img
fastboot flash recovery recovery.img
fastboot erase cache
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.
Last night i bricked my phone and accidently deleted system partitions i think from slot A and slot B when i was trying to install twrp. I always try to figure out how to fix it from reading helpful guides and without asking questions. I flashed full image a couple of times because i was getting bootloops everytime. In the last try, i flashed full image then gave me a bootloop again. So what i did, i adb sideload ota and it booted fine. Now im rooted and it seems i installed twrp correctly, i currently have nde63v build. At the moment i have supposedly used 22.71gb of 29.70gb.
So can someone let me know what i did wrong or point me out how to get those gbs back please.
ls2power said:
Last night i bricked my phone and accidently deleted system partitions i think from slot A and slot B when i was trying to install twrp. I always try to figure out how to fix it from reading helpful guides and without asking questions. I flashed full image a couple of times because i was getting bootloops everytime. In the last try, i flashed full image then gave me a bootloop again. So what i did, i adb sideload ota and it booted fine. Now im rooted and it seems i installed twrp correctly, i currently have nde63v build. At the moment i have supposedly used 22.71gb of 29.70gb.
So can someone let me know what i did wrong or point me out how to get those gbs back please.
Click to expand...
Click to collapse
I just did a factory reset and it fixed it. I also was stock without twrp though.
seshaz said:
I just did a factory reset and it fixed it. I also was stock without twrp though.
Click to expand...
Click to collapse
I tried factory reset already but still shows system using 19.9gbs.
Have you tried doing a complete full flash of nde63v without installing TWRP or root to see if it goes back to normal?
cambunch said:
Have you tried doing a complete full flash of nde63v without installing TWRP or root to see if it goes back to normal?
Click to expand...
Click to collapse
yes i did a few times, it would just bootloop. Until i sideloaded ota nde63v on top of full system img then it booted fine
ls2power said:
I tried factory reset already but still shows system using 19.9gbs.
Click to expand...
Click to collapse
Mine shows system using 19.9 gigs also. I posted this on another thread as I thought it seemed high but no one said weather it was high or was not so I assumed it was normal to use 19.9 gigs of space on my verizon pixel xl. I"am rooted on the x software but I couldnt get twrp working and I figured what good was TWRP if there was no supersu that was working with it and I decided to wait for TWRP to get out of beta to try again.
ls2power said:
yes i did a few times, it would just bootloop. Until i sideloaded ota nde63v on top of full system img then it booted fine
Click to expand...
Click to collapse
If you are getting a bootloop after flashing a factory image, I would assume it isn't flashing correctly. Can you post the output of what happens when you run the flashall.bat?
cambunch said:
If you are getting a bootloop after factory a factory image, I would assume it isn't flashing correctly. Can you post the output of what happens when you run the flashall.bat?
Click to expand...
Click to collapse
im able to flash every single img, but when i try to flash flashall.bat it doesnt seem to work. I will give it a try once i get home from work. The only thing bugging me is that the system shows using 19.9gb of space.
Mine is only using 6.79GB. Something is definitely off with yours.
Sent from my Pixel XL using XDA-Developers mobile app
Neomage84 said:
Mine is only using 6.79GB. Something is definitely off with yours.
Click to expand...
Click to collapse
yes there is. When you reboot your phone, which slot does it have? And do you have twrp installed and root?
M9guy said:
Mine shows system using 19.9 gigs also. I posted this on another thread as I thought it seemed high but no one said weather it was high or was not so I assumed it was normal to use 19.9 gigs of space on my verizon pixel xl. I"am rooted on the x software but I couldnt get twrp working and I figured what good was TWRP if there was no supersu that was working with it and I decided to wait for TWRP to get out of beta to try again.
Click to expand...
Click to collapse
I fixed it, i flashed full system image while i was on slot A. Now system is using 5.39gb, im on V build.
i have the same problem with a 128GB version not sure whats up but to fix it i just flashed over and over and one of them just worked would be nice to know the cause so i dont have to flash many times to get it to show full space again.
How do you select slot a while stock? I can select it in twrp but need to know how to get stock images to flash to a
theycallmerayj said:
How do you select slot a while stock? I can select it in twrp but need to know how to get stock images to flash to a
Click to expand...
Click to collapse
I figured out how to fix it by selecting slot a through twrp, booting into fastboot and flashing stock images. However, I am curious how it even ended up on slot b when I went from stock to unlocked and simply flashed the factory images. I never intended to switched from a to b.
theycallmerayj said:
How do you select slot a while stock? I can select it in twrp but need to know how to get stock images to flash to a
Click to expand...
Click to collapse
theycallmerayj said:
I figured out how to fix it by selecting slot a through twrp, booting into fastboot and flashing stock images. However, I am curious how it even ended up on slot b when I went from stock to unlocked and simply flashed the factory images. I never intended to switched from a to b.
Click to expand...
Click to collapse
whenever you flash a factory img or an OTA, or any firmware, the slots will switch unless told not to, i believe this is to keep them in sync aka the seamless updates. here is some info on that - http://www.androidpolice.com/2016/1...-partition-changes-and-new-fastboot-commands/
Quick Tip - while in cmdlne for ADB and Fastboot, and fully updated, just type
Code:
adb
to get all the ADB commands available, and likewise for fastboot, just type
Code:
fastboot
And to switch active slots type
Code:
fastboot set_active -a
or
Code:
fastboot set_active -b
. Then to activate slot
Code:
fastboot reboot bootloader
I believe with TWRP installed you have to switch slots in TWRP.
Click to expand...
Click to collapse
Moving on, I found this to be pretty helpful, it's not the exact answer you are looking for, but i think it will come in handy.
All dual-booting credit in this thread goes to hucqym, this wasn't my idea, im just a messenger.
hucqym said:
so I successfully have the dual boot running on my pixel (verizon edition) with the same configuration you are trying (one is NDE63X image rooted and one is NDE63X image stock/unrooted). Here were my steps:
-> dePixel8 to unlock bootloader (because verizon edition pixel)
-> download NDE63X image from google and modified flash_all.sh to flash stock images to both slots manually
using the --slot _a/_b and --skip-secondary flags. Modified scripts below. At this point I confirmed that I could boot to both slots. I also verified bootloader lock/unlock again to make sure it was stock image on both slots
-> TWRP alpha2 to get recovery on both slots
-> with slot _b selected as active in TWRP, i installed the SuperSU v2.78 SR4 zip
-> with slot _a as active in TWRP, installed ElementalX-P-1.00 zip for the kernel patch to pass SafetyNet
voila, I now have non-rooted on slot _a and rooted on slot _b
Note that TWRP is not really a requirement for doing this. I had the same dual boot configuration working with SuperSU v2.78 SR3 rooting one slot directly. The only reason I needed TWRP is so that I can switch slots easily on the device and don't need a cable and a laptop just to switch the bootloader flag
Although, I got this to work it still falls short of what I really wanted to do. For my use-case I would really want an isolated userdata for the two slots so I can use the rooted slot as a complete sandbox. and then perhaps have a shared folder mechanism between the two. ...so if somebody has an idea on this, I'm all ears.
[UPDATE]: Note that the unrooted slot is still limited in the sense that safetynet checks fail and so AndroidPay etc.. that use that API will still not work. This, however, has little to do with the dual boot setup and more because SafetyNet now fails on just unlocked bootloader and we do need it unlocked. On Conchors' suggestion, I installed ElementalX kernel on slotA from TWRP and now my 'otherwise-stock' non-rooted image on slotA passes SafetyNet while slotB is successfully rooted
flash_all_slot-a.sh
Code:
fastboot flash --slot _a bootloader bootloader-sailfish-8996-012001-1608281716.img
fastboot reboot-bootloader
sleep 5
fastboot flash --slot _a radio radio-sailfish-8996-012511-1609191801.img
fastboot reboot-bootloader
sleep 5
#fastboot -w update image-sailfish-nde63x.zip
fastboot update --slot _a --skip-secondary image-sailfish-nde63x.zip
flash_all_slot-b.sh
Code:
fastboot flash --slot _b bootloader bootloader-sailfish-8996-012001-1608281716.img
fastboot reboot-bootloader
sleep 5
fastboot flash --slot _b radio radio-sailfish-8996-012511-1609191801.img
fastboot reboot-bootloader
sleep 5
#fastboot -w update image-sailfish-nde63x.zip
fastboot update --slot _b --skip-secondary image-sailfish-nde63x.zip
Click to expand...
Click to collapse
I switched it up a bit, and to be perfectly honest, the script is easier, this is just an alternate way of doing it
I did this for both slot_a and slot_b (not sure if it is needed for the flrst one, but that is what i did), both ways are correct, this way is much longer, but it gives some control, plus it's a nice learning process as it is pretty easy going.
If you are going to erase, erase first before you start anything, because you know...science.
Code:
fastboot erase boot
fastboot erase cache
fastboot erase system
fastboot erase vendor
the cache partition, i dont remember if this worked or not, I'm too tired to verify
Code:
fastboot flash --slot _b --skip-secondary bootloader "name-of-bootloader.img"
fastboot reboot-bootloader
fastboot flash --slot _b --skip-secondary radio "name-of-radio.img"
fastboot reboot-bootloader
fastboot flash --slot _b --skip-secondary system system.img
fastboot flash --slot _b --skip-secondary boot boot.img
fastboot flash --slot _b --skip-secondary vendor vendor.img
If you want to wipe everything, use the following commands next:
Code:
fastboot erase userdata
fastboot flash userdata userdata.img
fastboot reboot
system.img and userdata.img take time to flash— the command prompt appears to stop. Let it do it's thing, when it's done the cursor will begin blinking again.
All dual-booting credit goes to hucqym; again, not my idea.
Slightly Off Topic -
Has anyone tried this on a specific slot, does it make any difference?) I haven't actually even thought of this till now
something like:
Code:
fastboot erase --slot _(a/b) --skip-secondary userdata
fastboot flash --slot _(a/b) --skip-secondary userdata userdata.img[/B]
theycallmerayj said:
I figured out how to fix it by selecting slot a through twrp, booting into fastboot and flashing stock images. However, I am curious how it even ended up on slot b when I went from stock to unlocked and simply flashed the factory images. I never intended to switched from a to b.
Click to expand...
Click to collapse
ls2power said:
Last night i bricked my phone and accidently deleted system partitions i think from slot A and slot B when i was trying to install twrp. I always try to figure out how to fix it from reading helpful guides and without asking questions. I flashed full image a couple of times because i was getting bootloops everytime. In the last try, i flashed full image then gave me a bootloop again. So what i did, i adb sideload ota and it booted fine. Now im rooted and it seems i installed twrp correctly, i currently have nde63v build. At the moment i have supposedly used 22.71gb of 29.70gb.
So can someone let me know what i did wrong or point me out how to get those gbs back please.
Click to expand...
Click to collapse
I was noticing quite a bit of space missing as well. what i did was boot into the slot I wanted as secondary (do this in TWRP), and i wiped just the system (which includes cache) and reflashed the system.img directly pulled from factory.zip. I noticed twice as much space had been gained then what was actually said to be there. I was a little surprised...it was over 5 gb I had gained while the system only said 2.5ish gb. (perhaps there was a second other_system.img wrapped up in it, I don't know. Then i went back to the primary slot and booted back up.
It's possible I got off course, I'm tired.
Hello, I am currently rooted and on stock on pixel xl. I am trying to flash the pure nexus rom. I downloaded through the link in the op, factory reset and flashed through twrp (3.0.2rc1). When I went to reboot, it said OS not installed. Can anyone offer any assistance with this? Needless to say, I didn't reboot with that. I did however do a backup (of stock) prior to this. I decided to restore my backup but when it rebooted it said something about the vender image is not right with this system and to flash the correct image. This is exactly what its saying : Your vendor image does not match the system. Please flash the NOF27C vendor image for your device. I have managed to move the correct image file to the internal storage but from what i read, can only install through twrp.
And when it finished rebooting, now 90% of my apps are crashing, no fingerprint hardware, developer options are not available and I had to reboot back into recovery but its like twrp is gone, it looks like the stock recovery. Somehow it appears there are parts of my stock rom and pure nexus rom combined which is understandbly causing my issues. Right now I am trying to get back to having twrp but am stuck.
I have since tried to reinstall twrp but when I plug my xl into my pc, the pc recognizes it but no storage. I cant move a file from pc to xl because its saying disconnected or not responding. Tried to get a command prompt and when I shift/right click, there is no option. I don't know what else to do.
If anyone has any suggestions, please help. I am freaking over this. Can't use my phone in the state its in.
Sounds far from bricked.
Just entirely screwed up.
FASTboot the latest factory image and then refrain from tinkering for the weekend.
These are the steps i use.
I think a new ADB/FastBoot package was released yesterday you might want to install that.
Execute fastboot commands (assuming the bin is on your PATH)
fastboot flash bootloader c:\_PIXEL_XL_\bootloader.img
fastboot reboot-bootloader
fastboot flash radio c:\_PIXEL_XL_\radio.img
fastboot reboot-bootloader
fastboot flash boot_a c:\_PIXEL_XL_\boot.img
fastboot flash boot_b c:\_PIXEL_XL_\boot.img
fastboot flash system c:\_PIXEL_XL_\system.img
fastboot flash system_b c:\_PIXEL_XL_\system_other.img
fastboot flash vendor c:\_PIXEL_XL_\vendor.img
fastboot flash modem c:\_PIXEL_XL_\modem.img
fastboot reboot
To add TWRP and Root:
fastboot boot c:\_PIXEL_XL_\twrp.img
In TWRP, install twrp.zip
Reboot into the installed recovery
In TWRP, install supersu.zip
I've been following this guide:
https://forum.xda-developers.com/pi...p-flashable-monthly-update-zip-pixel-t3375591
to try and root my Pixel C. I was initially following a different guide, but I believe I now have:
bootloader-dragon-google_smaug.7900.50.0.img and TWRP_dragon_3.1.0-2.img, loaded through fastboot
I was then able to push
Update.ZIP_PixelC_Ryu_system-vendor-boot_OPP1.zip and SuperSU-v2.79-201612051815.zip to /sdcard/ via adb in TWRP. I then tried to install both, as per the guide.
I was a bit confused when the "flashing system.img... this will take some time" part took no time at all, but it had taken a while to get to that point so I figured maybe the messages were in the wrong order or something. Both said they were successful.
Tried booting to system - just came back to TWRP.
So I thought I'd try to flash the system image back on. But I can't push any files now. Everytime I try, it creates the files then fails and I start getting read-only file system errors
If I try to install update.zip again (the one above), I now get "failed to mount '/data-full' (Device or resource busy)"
So I'm quite stuck at this point. Can't revert to stock image, can't install the new image... any help would be much appreciated!
I would do the following:
Download the full factory image from here. If you want to keep all of your data extract the zip and remove "-w" from flash_all.bat or flash_all.sh (depending on your OS).
If you keep -w it wipes your settings.
Boot into fastboot and run flash_all.
It will write all data from the factory image to your device and it should boot into android again.
If your tablet is up and running you can download twrp and flash it again on your tablet.
I always flash twrp like this:
fastboot flash recovery twrp.img
fastboot boot twrp.img
if i boot into twrp it asks for a decryption-pass. I skip this and go directly to reboot and reboot into recovery. Now i will not be asked for a password and can go on flashing the latest supersu.
peter73 said:
I would do the following:
Download the full factory image from here. If you want to keep all of your data extract the zip and remove "-w" from flash_all.bat or flash_all.sh (depending on your OS).
If you keep -w it wipes your settings.
Boot into fastboot and run flash_all.
It will write all data from the factory image to your device and it should boot into android again.
If your tablet is up and running you can download twrp and flash it again on your tablet.
I always flash twrp like this:
fastboot flash recovery twrp.img
fastboot boot twrp.img
if i boot into twrp it asks for a decryption-pass. I skip this and go directly to reboot and reboot into recovery. Now i will not be asked for a password and can go on flashing the latest supersu.
Click to expand...
Click to collapse
I second this ^ except for the fastboot boot twrp.img part. Why do you do that? The first line should be enough.