Related
I've been going through quite an ordeal with my Tab over the past few days.
It started with my Tab boot looping for no apparent reason, then I couldn't get fastboot to work, but now I solved my fastboot problems. I followed some instructions (here: http://forum.xda-developers.com/showpost.php?p=14600617&postcount=111) on how to use fastboot to get it working again, and i flashed that system image linked to in that post. And it worked, I had my Tab up and running again, but I noticed that my storage space total is now at 13GB; I remember it having 32GB total storage before this whole ordeal. I'm guessing I flashed the wrong system image to my device, so does anyone have the correct system image for the I/O Tab 10.1?
I tried this one: http://forum.xda-developers.com/showthread.php?t=1075993 and my device gets stuck in the boot screen (not even looping, it just stays on the "Samsung Galaxy Tab 10.1" screen)
Any help would really be appreciated.
use this to recover:
http://forum.xda-developers.com/showpost.php?p=14684694&postcount=77
read the whole thing (quoted and unquoted).
you can get images here:
http://droidbasement.com/galaxy/sys-backup/hc_31
if you have media (/data/media (internal sdcard)), back it up prior (you will lose it).
that droidbasement link returned a 404 not found error.
fixed.
refresh.
let me upload raw fastbootable images also, for the first part.
check back in one hr.
done uploading.
Ok, I've got it all sorted out. Thanks for the quick response, Pershoot.
Here's a breakdown of how I got it working again...
First, I installed PDAnet as a shortcut to get the fastboot drivers, as soon as I installed it, fastboot started working.
Then I downloaded the files linked here: http://forum.xda-developers.com/show...&postcount=111
Then I followed the first half of Pershoot's instructions (http://forum.xda-developers.com/showpost.php?p=14684694&postcount=77) using the files provided by novicejeep. I did all the fastboot stuff, booted into recovery, factory reset, reboot, but instead of getting a boot loop, my device booted up just fine. I had previously flashed these same files to get it working but those times my storage showed as 13GB for some reason, but now it's showing as 27GB. I'm guessing the factory reset corrected that issue (or maybe it was erasing before flashing each thing?).
The only downside now is that I'm back on 3.0.1, so what's the safest way to get up to 3.1 for a root user? I suppose I'll take my chances with System Update in the Settings.
Thanks Pershoot, novicejeep, kdietze3 and everyone else here on the forums
if you are on 3.0, then just use the restore method to 3.1.
you would have been on 3.1, if you would have used all 3.1 images, as outlined in my instructions from the sys-backup/hc_31 folder.
I ran system update and now I'm on 3.1 again
Even though I had fastboot working, I couldn't get ADB to work so I couldn't push the backup file to the device so I could restore it. Without that, I just kept bootlooping.
When I used the 3.0 files, I didn't even get that far in your instructions. At the part where you expect it to boot loop, it just booted up with no problems. Whereas when I flashed the hc31 files you posted, I bootlooped at that step.
dracoaffectus said:
I ran system update and now I'm on 3.1 again
Even though I had fastboot working, I couldn't get ADB to work so I couldn't push the backup file to the device so I could restore it. Without that, I just kept bootlooping.
When I used the 3.0 files, I didn't even get that far in your instructions. At the part where you expect it to boot loop, it just booted up with no problems. Whereas when I flashed the hc31 files you posted, I bootlooped at that step.
Click to expand...
Click to collapse
yea as outlined. then prceed on with the instructions, and when done, you will be sorted.
The new kernel did not like my tab. It crashed pretty hard when I plugged it in to charge. Now when I try to boot, it loops at the "glowing SAMSUNG" screen. I tried to restore with ODIN and it's still looping. Going to try this method.
I'm trying to update my wife's N7 to 4.3. She used a toolkit to root and has TWRP recovery. Everything else is stock. So first I downloaded the 4.3 update and attempted to flash, but immediately after choosing "install" I received a message the the flash failed. I thought maybe I got a bad download, so I rebooted the device and forced an OTA. The device downloaded the OTA, but then rebooted to TWRP and didn't install. Then I thought maybe I need to have stock recovery... So I unrooted, and installed stock recovery. I then forced the OTA again, downloaded, and began to install in stock recovery, and approximately halfway through it stopped and gave an error message. Then the device rebooted on it's own. I'm not sure what to do at this point. I was able to update to 4.3 on my N4 without any issues. Does anyone have a solution for me? Please let me know if there is some detail I left out. Thanks!
You can use fastboot to erase your current partitions then manually flash the 4.3 stock images.
I've never used fastboot before. Plus another problem now... I tried to flash the stock image via toolkit, now the device is stuck on the bootloader.
chrisbo4 said:
I've never used fastboot before. Plus another problem now... I tried to flash the stock image via toolkit, now the device is stuck on the bootloader.
Click to expand...
Click to collapse
On the bootloader or the boot animation? Big difference.
There was a recent change in fastboot that makes flashing the 4.3 images a little dicey if you're not using the latest fastboot executable, which I imagine could cause problems with various toolkits that bundle the executable.
Rirere said:
On the bootloader or the boot animation? Big difference.
There was a recent change in fastboot that makes flashing the 4.3 images a little dicey if you're not using the latest fastboot executable, which I imagine could cause problems with various toolkits that bundle the executable.
Click to expand...
Click to collapse
On the bootloader. I can't get past the google splash screen, but it overlays the bootloader screen. I just want to get back to stock, then upgrade to 4.3. I've tried to install adb on my computer, but couldn't get the computer to recognize the device.
chrisbo4 said:
On the bootloader. I can't get past the google splash screen, but it overlays the bootloader screen. I just want to get back to stock, then upgrade to 4.3. I've tried to install adb on my computer, but couldn't get the computer to recognize the device.
Click to expand...
Click to collapse
Install this through device manager.
http://d-h.st/kDu
Username invalid said:
Install this through device manager.
http://d-h.st/kDu
Click to expand...
Click to collapse
Okay, it's installed. I'm not sure what I should unzip though?
chrisbo4 said:
Okay, it's installed. I'm not sure what I should unzip though?
Click to expand...
Click to collapse
You can either flash stock images with fastboot or install TWRP then flash stock zip file.
chrisbo4 said:
I'm trying to update my wife's N7 to 4.3. She used a toolkit to root and has TWRP recovery. Everything else is stock. So first I downloaded the 4.3 update and attempted to flash, but immediately after choosing "install" I received a message the the flash failed. I thought maybe I got a bad download, so I rebooted the device and forced an OTA. The device downloaded the OTA, but then rebooted to TWRP and didn't install. Then I thought maybe I need to have stock recovery... So I unrooted, and installed stock recovery. I then forced the OTA again, downloaded, and began to install in stock recovery, and approximately halfway through it stopped and gave an error message. Then the device rebooted on it's own. I'm not sure what to do at this point. I was able to update to 4.3 on my N4 without any issues. Does anyone have a solution for me? Please let me know if there is some detail I left out. Thanks!
Click to expand...
Click to collapse
First of all I do not intend to offend you. I am not lecturing. I just want to give you my opinion in order to try to help you.
In general to install an update the safest way is to have or re-install stock recovery prior to the installation of the update. There is no need to unroot for the stock recovery installation.
In your household you have Nexus products. It means that you will probably continue to acquire Nexus equipment. In this case, in the long run, you will be better off installing, learning, and using adb and fastboot methods. Toolkits are mostly a quick fix which works ...............or not. I am thinking that toolkits are useless in the sense that they do not bring knowledge and experience (in my area trash collection are Monday and Thursday:laugh.
The XDA forum is full of resources. It does not leave a stone unturned. Its a matter of reading, asking, and learning.
In your case, facing your problem, I would install adb through a program called "android-sdk- windows". Then I will take advantage of the experience and the knowledge of our forum members to install the JB 4.3 factory image.
here are two references among several:
http://forum.xda-developers.com/showthread.php?t=1907796
http://forum.xda-developers.com/showthread.php?t=1781250
But it is a long way for a beginner - which I was 2-3 years ago - to go this route. But what a reward!
gunner1937 said:
First of all I do not intend to offend you. I am not lecturing. I just want to give you my opinion in order to try to help you.
In general to install an update the safest way is to have or re-install stock recovery prior to the installation of the update. There is no need to unroot for the stock recovery installation.
In your household you have Nexus products. It means that you will probably continue to acquire Nexus equipment. In this case, in the long run, you will be better off installing, learning, and using adb and fastboot methods. Toolkits are mostly a quick fix which works ...............or not. I am thinking that toolkits are useless in the sense that they do not bring knowledge and experience (in my area trash collection are Monday and Thursday:laugh.
The XDA forum is full of resources. It does not leave a stone unturned. Its a matter of reading, asking, and learning.
In your case, facing your problem, I would install adb through a program called "android-sdk- windows". Then I will take advantage of the experience and the knowledge of our forum members to install the JB 4.3 factory image.
here are two references among several:
http://forum.xda-developers.com/showthread.php?t=1907796
http://forum.xda-developers.com/showthread.php?t=1781250
But it is a long way for a beginner - which I was 2-3 years ago - to go this route. But what a reward!
Click to expand...
Click to collapse
Thank you for the information, and I'm not offended at all. I spent most of last night reading, and attempting to get adb running on my computer. I experienced issues getting drivers installed, and the computer recognizing the device. Also, trying to find the directories... I'll keep searching to see if I can get this figured out. Thank you again!
Thanks to everyone for helping me through this problem. After a lot of searching, research, reading, and video tutorials, I flashed stock images to the N7 via fastboot. I always thought that adb and fastboot was way too advanced for me (and it probably still is), but at least I got the basics down. Thank you all again.
Backstory I'm running PureNexus rom with Experimental kernel. Yesterday out of nowhere the phone started bootlooping, usually this is fine and i'll just restart the phone. Well after trying this the bootloop stayed for 15mins. I cleared cache and dalvik and still the same results. I ended up trying to restore a previous nandroid and nothing changed. Frustrated I backuped my titanium backups to my PC and cleared everything, factory reset and data format from twrp. I tried flashing the PureNexus rom clean and still bootloops. It just hangs on the white Google screen with the black background.
I'm following Heisenberg's tutorial (section 10) and after using fastboot and following the directions, i'm getting stuck on flashing the system. I'll get, "load_file: could not allocate 2014388768 bytes
error: cannot load 'C:\angler\images\system.img'
I read restarting the computer might help and i tried that and nothing has changed. It seems this is not rom related, since I downloaded a couple different ones and pushed it to my phone/flashed and it still bootloops. Any suggestions or help? Thanks!
Subiegsr said:
Backstory I'm running PureNexus rom with Experimental kernel. Yesterday out of nowhere the phone started bootlooping, usually this is fine and i'll just restart the phone. Well after trying this the bootloop stayed for 15mins. I cleared cache and dalvik and still the same results. I ended up trying to restore a previous nandroid and nothing changed. Frustrated I backuped my titanium backups to my PC and cleared everything, factory reset and data format from twrp. I tried flashing the PureNexus rom clean and still bootloops. It just hangs on the white Google screen with the black background.
I'm following Heisenberg's tutorial (section 10) and after using fastboot and following the directions, i'm getting stuck on flashing the system. I'll get, "load_file: could not allocate 2014388768 bytes
error: cannot load 'C:\angler\images\system.img'
I read restarting the computer might help and i tried that and nothing has changed. It seems this is not rom related, since I downloaded a couple different ones and pushed it to my phone/flashed and it still bootloops. Any suggestions or help? Thanks!
Click to expand...
Click to collapse
Just download NexusRoot Toolkit to flash back to stock or boot into recovery TWRP and flash PN rom again. It should work fine after that.
luckyfate said:
Just download NexusRoot Toolkit to flash back to stock or boot into recovery TWRP and flash PN rom again. It should work fine after that.
Click to expand...
Click to collapse
Just updated the SDK tool and it actually did let me install the system.img file now after it allocated some. But phone still boot looped.
Downloading the NexusRoot Toolkit now! Thank you for the suggestion, I'll update with the results.
So I installed the toolkit and did the flash stock + Unroot and checked soft-bricket/bootloop and phone is still bootlooping 30 mins later. It's doing the same bootloop as before. Just the black and white Google logo and then the orange pause boot screen. Although, as I type this the Google is not just there and it doesn't flash back to the orange screen..
Not sure if this helps but the live log said:
"Nexus Root Toolkit v2.1.6
Masterlists:
- LatestToolkitFiles.ini 3124
- AndroidDeviceListFull.ini 3124
- AndroidDeviceListFlash.ini 3124
ANGLER-ANGLER: Android 6.0.0 - Any Build
Live log initiated [2016-07-31]:
Further extracting contents of factory image package for use in 'Force Flash Mode'...
Checking ADB/FASTBOOT Connectivity
adb devices
fastboot devices
5VT7N15A25003518 fastboot
Connectivity Status: Fastboot Device Connected
+ Confirmed: Bootloader Unlocked.
fastboot getvar product
product: angler
finished. total time: 0.012s
Launching flashstock.bat"
Subiegsr said:
So I installed the toolkit and did the flash stock + Unroot and checked soft-bricket/bootloop and phone is still bootlooping 30 mins later. It's doing the same bootloop as before. Just the black and white Google logo and then the orange pause boot screen. Although, as I type this the Google is not just there and it doesn't flash back to the orange screen..
Not sure if this helps but the live log said:
"Nexus Root Toolkit v2.1.6
Masterlists:
- LatestToolkitFiles.ini 3124
- AndroidDeviceListFull.ini 3124
- AndroidDeviceListFlash.ini 3124
ANGLER-ANGLER: Android 6.0.0 - Any Build
Live log initiated [2016-07-31]:
Further extracting contents of factory image package for use in 'Force Flash Mode'...
Checking ADB/FASTBOOT Connectivity
adb devices
fastboot devices
5VT7N15A25003518 fastboot
Connectivity Status: Fastboot Device Connected
+ Confirmed: Bootloader Unlocked.
fastboot getvar product
product: angler
finished. total time: 0.012s
Launching flashstock.bat"
Click to expand...
Click to collapse
Have you tried just downloading the nexus6p IMG and using the flash-all command? I've always been able to recover that way. It restores everything to stock and wipes everything. If it still doesn't work then I would assume a hardware issue. Unless your PC drivers are messing with the process. Some USB hardware can have issues.
Gizmoe said:
Have you tried just downloading the nexus6p IMG and using the flash-all command? I've always been able to recover that way. It restores everything to stock and wipes everything. If it still doesn't work then I would assume a hardware issue. Unless your PC drivers are messing with the process. Some USB hardware can have issues.
Click to expand...
Click to collapse
Could you tell me where I could find the nexus6p img file at and how to flash all command? Seems like most are files I come across are zip files.
*edit: I downloaded the latest version from https://developers.google.com/android/nexus/images did the flash all command and it still hangs on the white Google screen. Although, it did say it couldn't flash boot.sig, recovery.sig, vendor.sig, and etc.. but still completed the flash? I did have all the files unzipped in the same folder of the platform-tools. I just held shift + right clicked the folder and opened the run command window. Am I missing something?
duplicate*
Subiegsr said:
Could you tell me where I could find the nexus6p img file at and how to flash all command? Seems like most are files I come across are zip files.
Click to expand...
Click to collapse
You should try to flash by choosing different stock rom N
Except any stock rom. I will try to flash any android N stock rom by checking Device is normal or no soft brick. If phone boots up fine, u can flash back any to different stock rom like 19X....
luckyfate said:
You should try to flash by choosing different stock rom N
Except any stock rom. I will try to flash any android N stock rom by checking Device is normal or no soft brick. If phone boots up fine, u can flash back any to different stock rom like 19X....
Click to expand...
Click to collapse
doesn't seem any rom is working when booting clean from twrp.
Subiegsr said:
Could you tell me where I could find the nexus6p img file at and how to flash all command? Seems like most are files I come across are zip files.
*edit: I downloaded the latest version from https://developers.google.com/android/nexus/images did the flash all command and it still hangs on the white Google screen. Although, it did say it couldn't flash boot.sig, recovery.sig, vendor.sig, and etc.. but still completed the flash? I did have all the files unzipped in the same folder of the platform-tools. I just held shift + right clicked the folder and opened the run command window. Am I missing something?
Click to expand...
Click to collapse
Usually you would want to run it from an elevated command prompt and navigate to folder and just type flash-all.bat, as long as adb tools are in environment variables it will work. But if it made it all the way to flashing vendor, wiping data and then rebooting it should have worked. This seems like the symptoms of a bad chip. Bad luck I'm guessing. You could try another PC just to be sure but I would trade it in if it was me.
Gizmoe said:
Usually you would want to run it from an elevated command prompt and navigate to folder and just type flash-all.bat, as long as adb tools are in environment variables it will work. But if it made it all the way to flashing vendor, wiping data and then rebooting it should have worked. This seems like the symptoms of a bad chip. Bad luck I'm guessing. I would try another PC just to be sure but I would trade it in if it was me.
Click to expand...
Click to collapse
Yeah, the command prompt installed everything successfully. The only other computer I have is a MacPro that I could try to use, but honestly I spent 7 hours today trying to fix the phone and 4 last night.. i think my eyes are done lol. Good call on the bad chip, probably was too hot over the weekend for it. I did talk to Google and they're sending me a replacement. Sucks though, I took care of my battery life crazy to preserve the life, hopefully the refurb one is just as good. Thanks for the help anyways. :good:
Subiegsr said:
Yeah, the command prompt installed everything successfully. The only other computer I have is a MacPro that I could try to use, but honestly I spent 7 hours today trying to fix the phone and 4 last night.. i think my eyes are done lol. Good call on the bad chip, probably was too hot over the weekend for it. I did talk to Google and they're sending me a replacement. Sucks though, I took care of my battery life crazy to preserve the life, hopefully the refurb one is just as good. Thanks for the help anyways. :good:
Click to expand...
Click to collapse
The exact same thing happened to me over the weekend, and I've tried all the steps you did. I'm now at the same conclusion of hardware failure, so will be calling google today for an RMA.
zamula said:
The exact same thing happened to me over the weekend, and I've tried all the steps you did. I'm now at the same conclusion of hardware failure, so will be calling google today for an RMA.
Click to expand...
Click to collapse
That's crazy it happened to you too. Good luck with the replacement. I hope the replacement doesn't have scratches/scuffs. Mine is seriously immaculate.
I cannot get my phone to accept ADB commands while in the Bootloader. The phone has been doing some strange stuff so I decided to start from scratch and reinstall everything. I tried to use the "Restore to Stock Tool" but once it reboots to the bootloader, I get "device not found" until it gets to the erase commands, phone restarts and is wiped but still on the 6.0 update. I tried "adb devices" and the device shows up but if I try "adb reboot bootloader" it reboots to the bootloader but "adb devices" doesn't see the device anymore. The only thing I can think that could cause this is a corrupt bootloader but how can you correct the problem if you can't flash anything? If someone can suggest anything I can try, I would appreciate it.
6.0 is the current update...
Flash twrp then try flashing a custom ROM. Honestly it sounds like you might be doing something wrong, or maybe a bad USB cable? Keep trying I don't think you're screwed
Steeleio said:
I cannot get my phone to accept ADB commands while in the Bootloader. The phone has been doing some strange stuff so I decided to start from scratch and reinstall everything. I tried to use the "Restore to Stock Tool" but once it reboots to the bootloader, I get "device not found" until it gets to the erase commands, phone restarts and is wiped but still on the 6.0 update. I tried "adb devices" and the device shows up but if I try "adb reboot bootloader" it reboots to the bootloader but "adb devices" doesn't see the device anymore. The only thing I can think that could cause this is a corrupt bootloader but how can you correct the problem if you can't flash anything? If someone can suggest anything I can try, I would appreciate it.
Click to expand...
Click to collapse
Do you still have an custom recovery installed? TWRP?
Steeleio said:
I cannot get my phone to accept ADB commands while in the Bootloader. The phone has been doing some strange stuff so I decided to start from scratch and reinstall everything. I tried to use the "Restore to Stock Tool" but once it reboots to the bootloader, I get "device not found" until it gets to the erase commands, phone restarts and is wiped but still on the 6.0 update. I tried "adb devices" and the device shows up but if I try "adb reboot bootloader" it reboots to the bootloader but "adb devices" doesn't see the device anymore. The only thing I can think that could cause this is a corrupt bootloader but how can you correct the problem if you can't flash anything? If someone can suggest anything I can try, I would appreciate it.
Click to expand...
Click to collapse
Frankly, I would be surprised if your "SCREWED"... it sounds more like your misinformed.
ADB will NEVER work in the bootloader, it isn't intended to, that is what fastboot is for. ADB stands for Android Debugging Bridge because it is the computer's "bridge" to Android, you can think of it as the connection to the operating system, meaning the phone must be booted and running Android for it to work or there is nothing to "bridge" to.
Fastboot is a more limited tool designed to talk to the bootloader and get the phone so that operating system can boot or it can be returned to it's factory state, fastboot cannot talk or "bridge" to Android. They are different and unique tools with different purposes that are used at different times.
This is another case of why one-click or scripting tools are not recommended... even if they work 90% of the time or more, there is still failure due to automation.
I would suggest grabbing the full factory firmware package and install it MANUALLY with the fastboot commands and you will likely be fine. Remember to give it time on the first boot, it can be 20 minutes or more before things look like they are progressing initially.
acejavelin said:
Frankly, I would be surprised if your "SCREWED"... it sounds more like your misinformed.
ADB will NEVER work in the bootloader, it isn't intended to, that is what fastboot is for. ADB stands for Android Debugging Bridge because it is the computer's "bridge" to Android, you can think of it as the connection to the operating system, meaning the phone must be booted and running Android for it to work or there is nothing to "bridge" to.
Fastboot is a more limited tool designed to talk to the bootloader and get the phone so that operating system can boot or it can be returned to it's factory state, fastboot cannot talk or "bridge" to Android. They are different and unique tools with different purposes that are used at different times.
This is another case of why one-click or scripting tools are not recommended... even if they work 90% of the time or more, there is still failure due to automation.
I would suggest grabbing the full factory firmware package and install it MANUALLY with the fastboot commands and you will likely be fine. Remember to give it time on the first boot, it can be 20 minutes or more before things look like they are progressing initially.
Click to expand...
Click to collapse
So I got the computer to recognize the phone. I reset everything back to stock 5.1.1. Once I had it reset, the Bluetooth would not turn on (which was one of my original problems). So I took all the OTAs to get back to 6.0. For some reason when It got to about the 3rd update, it wouldn't complete. It failed but didn't specify a reason. I tried this 2 times without any luck. I left it at the update it was on and used it for a day. The Bluetooth still would not turn on and I was experiencing random data drops which required a reboot. I finally gave up because I was so frustrated. I figured something must be going wrong some hardware inside the phone.
Steeleio said:
So I got the computer to recognize the phone. I reset everything back to stock 5.1.1. Once I had it reset, the Bluetooth would not turn on (which was one of my original problems). So I took all the OTAs to get back to 6.0. For some reason when It got to about the 3rd update, it wouldn't complete. It failed but didn't specify a reason. I tried this 2 times without any luck. I left it at the update it was on and used it for a day. The Bluetooth still would not turn on and I was experiencing random data drops which required a reboot. I finally gave up because I was so frustrated. I figured something must be going wrong some hardware inside the phone.
Click to expand...
Click to collapse
Style or Pure? And why flash 5.1.1 when 6.0 images are available? http://forum.xda-developers.com/moto-x-style/development/pure-firmware-tuff-wip-t3224833
Also, I see many guides don't show flashing the Bluetooth firmware for some reason, so depending on the guide you used might be wrong, always look at the XML file in the image.
fastboot flash bluetooth BTFM.bin
Sent from my XT1575 using Tapatalk
acejavelin said:
Style or Pure? And why flash 5.1.1 when 6.0 images are available? http://forum.xda-developers.com/moto-x-style/development/pure-firmware-tuff-wip-t3224833
Also, I see many guides don't show flashing the Bluetooth firmware for some reason, so depending on the guide you used might be wrong, always look at the XML file in the image.
fastboot flash bluetooth BTFM.bin
Sent from my XT1575 using Tapatalk
Click to expand...
Click to collapse
Pure. I figured if I start all the way over from the beginning it would work out. Like I said, even one of the OTA's failed. I tried flashing the BTFM.bin file but that didn't work either. I will try some other stuff when I get off work today.
So I tried starting from scratch again. I get a "validation failed" when I try to flash the gpt.bin file. Everything else worked. Bluetooth and data are working now. Could I have a corrupt partition that is causing the validation to fail? Does anyone know the partition sizes for the Pure?
Steeleio said:
So I tried starting from scratch again. I get a "validation failed" when I try to flash the gpt.bin file. Everything else worked. Bluetooth and data are working now. Could I have a corrupt partition that is causing the validation to fail? Does anyone know the partition sizes for the Pure?
Click to expand...
Click to collapse
No, in fact it is quite common to get that message with the partition information... Ignore it, if everything else went fine and you having no more problems, your good to go.
So guys,
I got my nothing phone 1 three days ago and I absolutely love it. Then yesterday I tried to root it. I thought it would be easy since I´ve rooted three phones already (older ones like oneplus 2)
I unlocked the Bootloader and it worked fine. Then I researched how to root with magisk and found out that you dont get the boot.img anymore just like that and have to "payload-dump" i tried this for around two hours with every method i could find but it just wouldnt work.
Then I found an already patched boot file and flashed directly out of joy. Then the bootloop hits the Phone.
I forgot to check the versions and the boot.img was version 1.5.3 and my phone was already running newest 1.5.4
fastboot is still totally fine and I can use every command
I cant access the recovery. When I do fastboot reboot recovery it just gets back into bootloop
I thought okay it shouldnt be that hard to flash the stock image but I was so wrong.
Everytime I try to flash something it says "fastboot: error: cannot load '.\images\boot.img': No such file or directory"
and I really dont know how to correct that.
Read something about fastbootd but when I do "fastboot reboot fastboot" it gets back into a bootloop"
I would really appreciate help, since I need this phone for work in some time and of course would reward i anyone can help me.
ps yeah I know it was stupid to do this on my future work phone but I really thought I knew what I was doing
the complete output I get from the phone 1 tool by sh4tteredd is in the screenshots since I dont know how to extract it as a text
but I think the main problem is that it always says "No such file or directory"
also!: it also says "No such file or directory" when I try to manually flash command by command or a "Flash_all.bat"
Try to Flash the stock 1.5.4 stock boot image.... from fastboot... and let me know what happened.. this link might be help you https://forum.xda-developers.com/t/nothing-phone-1-rom-ota-nothing-os-repo-of-nothing-os.4464039/
Make sure use Android Platforms 33.0.3 since the latest verson is riddled with bugs.
soltion:
honestly idk, but i tried flashing an very old stock rom (from when roms were still split and i think I even used the wrong one) but that seemed to brake the system so hard that i eventually was able to just flash the newest stock rom and even root it with a patched file I found online (this time the right verion of course haha)