I've gotten myself into a bit of a pickle. I just got my Nothing Phone yesterday, and I've already managed to get it stuck in a boot loop. I am still able to access fastboot and my computer still recognises it, so i hope it is still salvageable.
It all started when I stumbled upon this guide, which promised that unlocking and rooting it would be done in minutes. I know next to nothing about rooting phones, but the guide made it seem fairly straightforward. So I gave it a go. Big mistake.
Here's exactly what's happened:
I followed the guide step by step.
At step 2.2 I downloaded the full 1.1.7 (EEA) package from here. Then I extracted the boot image from the downloaded zip by following this guide (still following the main guide).
Flashing it went fine, no errors, but after trying to start it, it just shows the logo for a few seconds and then restarts.
A bunch of googling later, I stumbled upon an xda thread where someone had linked to a website with pre-built images. I tried flashing some of those too, no luck.
Last thing I tried was flashing the "v1.5.3 Fastboot ROM" from that site, but I didn't get far with that at all. It contains a .bat file, but i'm on mac, so tried running the commands one by one. First step was "fastboot set_active b" and that succeeded, but after that it fails with the flashing; "Flashing is not allowed for Critical Partitions". I'm afraid to continue at this point.
If possible I would still like to continue with rooting it, but if it is easier to go back to factory without root I am ok with that too at this point. Can someone please help?
Did you try this? https://forum.xda-developers.com/t/how-to-unbrick-nothing-phone-1-fastboot-bootloop.4501439/
@itsTarec oh god, i think that might just have worked! It does boot now, and i'm going through the setup process. BUT, a few things failed during the flash process:
Code:
(not in order)
Resizing 'system_a' FAILED (remote: 'Not enough space to resize partition')
Writing 'odm_b' FAILED (remote: 'No such file or directory')
Writing 'product_b' FAILED (remote: 'No such file or directory')
Writing 'system_b' FAILED (remote: 'No such file or directory')
Writing 'system_ext_b' FAILED (remote: 'No such file or directory')
Writing 'vendor_b' FAILED (remote: 'No such file or directory')
Should i be worried?
nike1 said:
@itsTarec oh god, i think that might just have worked! It does boot now, and i'm going through the setup process. BUT, a few things failed during the flash process:
Code:
(not in order)
Resizing 'system_a' FAILED (remote: 'Not enough space to resize partition')
Writing 'odm_b' FAILED (remote: 'No such file or directory')
Writing 'product_b' FAILED (remote: 'No such file or directory')
Writing 'system_b' FAILED (remote: 'No such file or directory')
Writing 'system_ext_b' FAILED (remote: 'No such file or directory')
Writing 'vendor_b' FAILED (remote: 'No such file or directory')
Should i be worried?
Click to expand...
Click to collapse
Sorry mate, I have no idea. Keep looking for a solution... I was thinking about rooting my NP1 either but after seeing your thread I'm reluctant
itsTarec said:
Sorry mate, I have no idea. Keep looking for a solution... I was thinking about rooting my NP1 either but after seeing your thread I'm reluctant
Click to expand...
Click to collapse
Yeah, can't recommend it unless you really know what you're doing. It seems to be alright now though, thankfully
nike1 said:
Yeah, can't recommend it unless you really know what you're doing. It seems to be alright now though, thankfully
Click to expand...
Click to collapse
Is your device rooted now? Or did you just fixed the issue?
nike1 said:
I've gotten myself into a bit of a pickle. I just got my Nothing Phone yesterday, and I've already managed to get it stuck in a boot loop. I am still able to access fastboot and my computer still recognises it, so i hope it is still salvageable.
It all started when I stumbled upon this guide, which promised that unlocking and rooting it would be done in minutes. I know next to nothing about rooting phones, but the guide made it seem fairly straightforward. So I gave it a go. Big mistake.
Here's exactly what's happened:
I followed the guide step by step.
At step 2.2 I downloaded the full 1.1.7 (EEA) package from here. Then I extracted the boot image from the downloaded zip by following this guide (still following the main guide).
Flashing it went fine, no errors, but after trying to start it, it just shows the logo for a few seconds and then restarts.
A bunch of googling later, I stumbled upon an xda thread where someone had linked to a website with pre-built images. I tried flashing some of those too, no luck.
Last thing I tried was flashing the "v1.5.3 Fastboot ROM" from that site, but I didn't get far with that at all. It contains a .bat file, but i'm on mac, so tried running the commands one by one. First step was "fastboot set_active b" and that succeeded, but after that it fails with the flashing; "Flashing is not allowed for Critical Partitions". I'm afraid to continue at this point.
If possible I would still like to continue with rooting it, but if it is easier to go back to factory without root I am ok with that too at this point. Can someone please help?
Click to expand...
Click to collapse
When you want to root it is fairly simple, but you need to patch the EXACT boot.img file that your current firmware has. For example, you cannot patch the 1.1.7 boot.img and flash it when you have installed the 1.5.3 firmware.
And for root you need to patch the boot.img with the Magisk app, not just flash it.
lucy1983 said:
When you want to root it is fairly simple, but you need to patch the EXACT boot.img file that your current firmware has. For example, you cannot patch the 1.1.7 boot.img and flash it when you have installed the 1.5.3 firmware.
And for root you need to patch the boot.img with the Magisk app, not just flash it.
Click to expand...
Click to collapse
Aha, I see. That wasn't clear to me. I thought i needed a full package and not just an incremental one, that's why I went for 1.1.7. I did patch it with Magisk though, just the wrong version i guess. But all is well now, the phone's fully working afaict. Thank you for clarifying what went wrong!
Related
EDIT: Its amazing how typing everything help when asking for help can give you an idea on how to fix it. I downloaded the recovery image manually, unpacked it once, loaded it up in RapidCRC to figure out its MD5, restarted the factory reset program, and bam all working. Guess I was just being dumb and overlooking the obvious. Thanks anyhow all. Sorry for the trouble.
Hello all, I am in quite the pickle and I hope someone here can help me.
Not long ago I unlocked my Nexus 10's boot loader and installed TWRP recovery and a rooted copy of 4.2.2. I did all of this using the latest Nexus root toolkit, and I had zero issues. However recently I decided to revert back to stock completely. This brings me to the problem I am having.
So this morning these were my exact steps. Again, the current state of my Nexus 10 before I did anything was Unlocked Bootloader, TWRP Recovery, and 4.2.2 rooted installed. Nothing else.
I loaded up the Nexus Root Toolkit and connected my tablet to my computer making sure to use a USB port that worked last time. Made sure USB Debugging was enabled and clicked the "Flash Stock + Unroot" button. I followed all the steps and selected the latest (4.2.2) recovery image. Everything appeared to be going ok. I will now post exactly what I saw on the flashstock.bat window below.
sending 'bootloader' <1280 KB>...
OKAY [ 0.141s]
writing 'bootloader'...
OKAY [ 0.124S]
finished. total time: 0.270s
rebooting into bootloader....
OKAY [ 0.004s]
finished. total time: 0.006s
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
failed to allocate 535248732 bytes
error: update package missing system.img
It then closed and showed the completion message in the console window and said something along the lines of "press any key to close". In the bootloader it said " fastboot status fail signature verification".
At this point I thought "well, maybe it did not send the reboot single" so I selected the reboot option from the bootloader and all it did was hang at the google logo. Nothing happened. Next I tried rebooting into the bootloader and selecting recovery. Here is where I got very worried as nothing happened except a black screen. Nothing at all. Its like it does not have a recovery system at all.
I tried redoing the whole process and the same thing happened. I hope someone can help me as I really have no idea what to do and am quite frightened I broke it. The only thing I can think that leads me to believe me I can salvage this is that I can still get into the bootloader and as a result I assume I can get into fastboot.
Any help would be greatly appreciated.
Thanks very much,
-S
Glad you got it solved.
I've been trying to follow the instructions listed in a reddit thread I found called "Because kit kat botched update, nexus is hanging on boot animation. trying to un [email protected]#$ my phone but need help." , however, I'm stuck at the very last step. When I typed in "flash-all.bat" I got told the archive does not contain boot.sig, recovery.sig or system.sig. It then checks everything and says it's okay but when writing boot it fails saying <remote: not supported in locked devices> What can I do?
Darewaves said:
I've been trying to follow the instructions listed in a reddit thread I found called "Because kit kat botched update, nexus is hanging on boot animation. trying to un [email protected]#$ my phone but need help." , however, I'm stuck at the very last step. When I typed in "flash-all.bat" I got told the archive does not contain boot.sig, recovery.sig or system.sig. It then checks everything and says it's okay but when writing boot it fails saying <remote: not supported in locked devices> What can I do?
Click to expand...
Click to collapse
Did you by any chance forgot to unlock your bootloader? This here is a good guide by efrant. Always refer here. http://forum.xda-developers.com/nexus-4/general/how-to-how-to-flash-factory-image-t2010312
Wugfresh is a very handy tool too.
http://www.wugfresh.com/nrt/
I'm new to XDA and flashing my Nexus, I had a buddy of mine unlock and flash a custom ROM on my device. I'm working on getting my system to stock and upgrading to Android 'N'. I followed the guide http://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928 I had success in flashing all the images one time and rebooted the device. Only to find that it will not start so I loaded up the bootloader once again, checking recovery, still nothing. Now I'm rerunning the flash process everything runs fine all the way up to flashing vender.img
Code:
C:\SDK\platform-tools>fastboot flash vender C:\Angler\Images\vendor.img
target reported max download size of 494927872 bytes
sending 'vender' (185129 KB)...
OKAY [ 4.528s]
writing 'vender'...
FAILED (remote: Permission denied!)
finished. total time: 4.544s
This is where I'm stuck. Thanks for any help on this matter.
Hey, no problem bro! It's called vendor, not vender, and the command is: fastboot flash vendor etc. This should solve your problem (Sorry for my english)
NHagney said:
I'm new to XDA and flashing my Nexus, I had a buddy of mine unlock and flash a custom ROM on my device. I'm working on getting my system to stock and upgrading to Android 'N'. I followed the guide http://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928 I had success in flashing all the images one time and rebooted the device. Only to find that it will not start so I loaded up the bootloader once again, checking recovery, still nothing. Now I'm rerunning the flash process everything runs fine all the way up to flashing vender.img
Code:
C:\SDK\platform-tools>fastboot flash vender C:\Angler\Images\vendor.img
target reported max download size of 494927872 bytes
sending 'vender' (185129 KB)...
OKAY [ 4.528s]
writing 'vender'...
FAILED (remote: Permission denied!)
finished. total time: 4.544s
This is where I'm stuck. Thanks for any help on this matter.
Click to expand...
Click to collapse
I'm a Linux guy so you may wish to take this with a grain of salt. I have a vague memory of the same error and it was a case of a misspelled and/or miscapitalized command. I am assuming 2 things -
1) everything has worked up to this point
2)the code presented is exactly what you typed on your computer
Your error may simply be that your misspelled vendor after "fastboot flash"
Thats what i get for being hung over. I'm over here trying to run this as admin all kinds of nonsense. Wondering why this went so smooth last night now running into this. I still don't have a working device. After restarting the device I don't get the OS only the initial google screen. Edit: nevermind. It just posted. TY guys. On to Android 'N' maybe Nuttybar?
If there is a thread that solves a problem like mine, please point me to it, thanks.
Basically, I had updated my phone to Nougat which resulted in the infamous test-keys build number, instead of the right one (my device is VNS-L31 and it was single-SIM, supposedly.) I was fine with it, but at some point SuperSU auto-updated through the play store and I lost root. So I tried rooting it, but couldn't boot into recovery. Even when I managed to, SuperSU would not flash properly. So I thought I should roll back and do it properly.
I tried the rollback packages through dload from the rollback to MM thread, they wouldn't work. I found another thread that seemed to be describing the 'good way' so I did as it said. Flashed the OEMinfo provided, but then it told me the data partition was damaged. I turned it off and updated through dload, which went to 100%, turned off. And that's that. Screen is not turning on, no tactile feeling from the power button. The only thing that I seem to access is fastboot and only on the pc, the phone shows nothing.
Now I have tried flashing the extracted system, boot and recovery.img from the update zip and even though it says okay, nothing happens. The bootlocker seems to be unlocked still, thankfully I kept the pass!
fastboot oem get-build-number gives 'VNS-C432B120'
Any help would be appreciated.
EDIT: Since flashing the separate images does not seem to work, and fastboot erase system -w results in:
Erase successful, but not automatically formatting.
Can't determine partition type.
FAILED (remote: Command not allowed)
Erase successful, but not automatically formatting.
Can't determine partition type.
FAILED (remote: Command not allowed)
erasing 'system'...
FAILED (remote: Command not allowed)
I think that perhaps the partition table is messed up? Even though as I said the separate images seem to flash fine, without any errors... I tried to flash the whole update.zip or even a couple of ROMs, but it says that there is no android-info.txt. Is there any ROM which includes the android-info.txt or android-product.txt? Or does anyone perhaps know what the .txt should say inside? I have found some threads about HTC phones where they know the content of the .txt file, which is 4 tiny lines mentioning the model ID, main version and such information.
I wanted to get on the latest developer preview release, downloaded the system image, and flashed it to my phone, when done i tried to reboot it, but it stayed on the white google logo screen infinitely. Eventually rebooted, and now won't even attempt to boot. It just goes back to fastboot.
Any attempt to go to recovery, boot the system, or anything - gives an error "Your device is corrupt. It can't be trusted and may not work properly". It offers a link to g.co/ABH then an option to press the power to continue, when I do, it briefly flashes the google logo, then back to the bootloader. Where it has a reason shown as "error booting boot.img"
It doesn't respond to any adb or fastboot commands, but does show in the device manager as LeMobile Android Device (Android Bootloader Interface). And that's about it.
I seem to be stuck in a loop here, and would appreciate if anyone has any advice to offer.
I've managed to get it responding to fastboot commands, but it fails while flashing the system image, it seems to fail at exactly the same point each time though, and I just can't seem to get it to finish the install, and therefore can't boot up.
It flashes the radio, and recovery without any problem, goes through a large portion of the system flash process before failing.
Below is the text from where it fails, does anyone know a way around this?
Sending sparse 'vendor_b' 1/3 (262140 KB) FAILED (Error reading sparse file)
fastboot: error: Command failed
Ohiostyle said:
I've managed to get it responding to fastboot commands, but it fails while flashing the system image, it seems to fail at exactly the same point each time though, and I just can't seem to get it to finish the install, and therefore can't boot up.
It flashes the radio, and recovery without any problem, goes through a large portion of the system flash process before failing.
Below is the text from where it fails, does anyone know a way around this?
Sending sparse 'vendor_b' 1/3 (262140 KB) FAILED (Error reading sparse file)
fastboot: error: Command failed
Click to expand...
Click to collapse
Is it going from fastboot to fastbootd?
Yeah it was, it completed a lot of other read/write actions after moving over to fastbootd, before failing.
I was able to get it working by sideloading the ota file. Any system image (always factory images) that I would try to flash would fail at the same point. I have no idea why.
Ohiostyle said:
I've managed to get it responding to fastboot commands, but it fails while flashing the system image, it seems to fail at exactly the same point each time though, and I just can't seem to get it to finish the install, and therefore can't boot up.
It flashes the radio, and recovery without any problem, goes through a large portion of the system flash process before failing.
Below is the text from where it fails, does anyone know a way around this?
Sending sparse 'vendor_b' 1/3 (262140 KB) FAILED (Error reading sparse file)
fastboot: error: Command failed
Click to expand...
Click to collapse
you need to extract the other zip within the image and make sure you extract it where your adb tools are
tmoore3496 said:
you need to extract the other zip within the image and make sure you extract it where your adb tools are
Click to expand...
Click to collapse
Yes, I had that problem time ago (I think with the OG Pixel).
Doing what you described fixed it, now I always do it just in case.
Also updating to the latest platform tools.
Can you go into recovery? If so try sideloading an OTA file.