Hey folks, yesterday i made a serious mistake trying to root my nokia, that resulted in my phone not being able to boot android.
I tried several guides trying to install trwp, but everytime i tried to flash using fastboot like this:
fastboot flash recovery twrp.img
Click to expand...
Click to collapse
It kept complaining that twrp file was to large. So i did some random searches and ended up using the following command from a random noob, which i never shouldn't have done because after it my phone hangs on splash screen
This is the command i did use:
fastboot flash system twrp.img
Click to expand...
Click to collapse
Using this command my phone seemed to flash, but it wont boot anymore.
Does anyone know how to repair my nokia and flash twrp without complaining that twrp.img file is to large? Is there a way to recover my phone from the mistake i have made? Any tips, hints or help is highly appreciated.
Greets,
Autonomus
Autonomus said:
Hey folks, yesterday i made a serious mistake trying to root my nokia, that resulted in my phone not being able to boot android.
I tried several guides trying to install trwp, but everytime i tried to flash using fastboot like this:
It kept complaining that twrp file was to large. So i did some random searches and ended up using the following command from a random noob, which i never shouldn't have done because after it my phone hangs on splash screen
This is the command i did use:
Using this command my phone seemed to flash, but it wont boot anymore.
Does anyone know how to repair my nokia and flash twrp without complaining that twrp.img file is to large? Is there a way to recover my phone from the mistake i have made? Any tips, hints or help is highly appreciated.
Greets,
Autonomus
Click to expand...
Click to collapse
Ouch! I think you flashed your system partition. Can you still enter fastboot mode? If so should be able recover. your phone using OST. Get instructions here:
https://forum.xda-developers.com/nokia-3/development/nokia-3-official-firmware-india-uae-t3674320
i've followed the instruction, ost launched as it should and it did recognise phone. That ost tried to reboot bootloader, and then it stopped working completly. It now only has a black screen and vibrates every now and then.
Also ost doesn't recognise the phone anymore ... :cry
Related
So... Anyone have any experience getting sticky bit turned off on fastboot? My phone boots to it anytime I try to reboot or do a regular boot up.
fallnSaint said:
So... Anyone have any experience getting sticky bit turned off on fastboot? My phone boots to it anytime I try to reboot or do a regular boot up.
Click to expand...
Click to collapse
Mine did that for a short while after I screwed up a flash, I reflashed boot and while running tossed the adb command to get into fastboot and then left it properly. Haven't seen it since.
KitsunePaws said:
Mine did that for a short while after I screwed up a flash, I reflashed boot and while running tossed the adb command to get into fastboot and then left it properly. Haven't seen it since.
Click to expand...
Click to collapse
To clarify... Flash boot from recovery, while that is running adb reboot bootloader? If that is the case I have a different set of problems to "boot", I can't get my pc to recognize the phone while in recovery. Everything else is recognized, even reinstalled drivers to be certain, pc doesn't even try to install a driver for recovery. Tried both TWRP & CWM.
fallnSaint said:
To clarify... Flash boot from recovery, while that is running adb reboot bootloader? If that is the case I have a different set of problems to "boot", I can't get my pc to recognize the phone while in recovery. Everything else is recognized, even reinstalled drivers to be certain, pc doesn't even try to install a driver for recovery. Tried both TWRP & CWM.
Click to expand...
Click to collapse
Memory is fuzzy but I'm pretty sure I did it from fastboot, this happened to me about the time shabby was trying to fastboot boot boot.img and I ended up flashing it instead.
KitsunePaws said:
Memory is fuzzy but I'm pretty sure I did it from fastboot, this happened to me about the time shabby was trying to fastboot boot boot.img and I ended up flashing it instead.
Click to expand...
Click to collapse
I had this same issue when porting TWRP ^^^.
I can't seem to find my posts on it right now, but someone just said do a clean flash. No problems since
how did you do this please!
fallnSaint said:
So... Anyone have any experience getting sticky bit turned off on fastboot? My phone boots to it anytime I try to reboot or do a regular boot up.
Click to expand...
Click to collapse
Okay, this will probably help you...while your device is in Sticky Bit Factory Fastboot, open up a command prompt and connect to your device (given you know how to do so in your folder containing your fastboot app and drivers). Then type "fastboot oem fb_mode_clear" This command will allow your device to boot into system normally. Problem is (I think) when a failed flash occurs sometimes it sets your device in that mode and the above command clears it. Another way to manually place a device in the same state you described is to enter this command using fastboot: fastboot oem fb_mode_set. I believe that is how RSD Lite automatically reboots your device into factory fastboot mode after flashing partitions (.mbn) on your system so that it may resume flashing the boot, recovery, and system images, etc. Let me know if it helps.....
Sent from my XT897 using xda premium
so, i recently updated my oneplus one from cm11 to cm12.1 and when cm12 loaded in, i got a repeated message that com.android.phone has stopped and the quick settings bar displayed that i had no sim card in. so i tried reflashing, and the same problem. i redownloaded and reflashed... same problem.
so, i went into twrp and performed a full wipe, thinking that i'd push a new zip using twrp's mount function. the problem is, when i went to mount, no drive appeared on my computer. and when i went to fastboot to flash it manually, fastboot said that 'Image is not a boot image' . the same thing happens whenever i try to re-flash recovery as well. so how can i get an os back on the system if fastboot won't cooperate and twrp is essentially useless?
tldr; no os on oneplus one, fastboot wont flash boot image, twrp mount and twrp adb wont do anything. What do?
ItsDeadEnd said:
so, i recently updated my oneplus one from cm11 to cm12.1 and when cm12 loaded in, i got a repeated message that com.android.phone has stopped and the quick settings bar displayed that i had no sim card in. so i tried reflashing, and the same problem. i redownloaded and reflashed... same problem.
so, i went into twrp and performed a full wipe, thinking that i'd push a new zip using twrp's mount function. the problem is, when i went to mount, no drive appeared on my computer. and when i went to fastboot to flash it manually, fastboot said that 'Image is not a boot image' . the same thing happens whenever i try to re-flash recovery as well. so how can i get an os back on the system if fastboot won't cooperate and twrp is essentially useless?
tldr; no os on oneplus one, fastboot wont flash boot image, twrp mount and twrp adb wont do anything. What do?
Click to expand...
Click to collapse
What's the exact command you're using with fastboot? Are you only attempting to flash the boot.img? If so, why only that?
Heisenberg said:
What's the exact command you're using with fastboot? Are you only attempting to flash the boot.img? If so, why only that?
Click to expand...
Click to collapse
I am using "fastboot flash boot [zip]" i also tried "fastboot update [zip]", neither of which worked
ItsDeadEnd said:
I am using "fastboot flash boot [zip]" i also tried "fastboot update [zip]", neither of which worked
Click to expand...
Click to collapse
You didn't answer my question, why are you giving that command? There are a dozen or so commands that you're meant to give when flashing with fastboot. The only time you use that command is when you're just trying to flash a kernel.
Heisenberg said:
You didn't answer my question, why are you giving that command? There are a dozen or so commands that you're meant to give when flashing with fastboot. The only time you use that command is when you're just trying to flash a kernel.
Click to expand...
Click to collapse
what commands would you suggest i do then? because those are the only things i used other than the wipe command
ItsDeadEnd said:
what commands would you suggest i do then? because those are the only things i used other than the wipe command
Click to expand...
Click to collapse
Well it depends on what you're trying to do. As I said, the "fastboot flash boot boot.img" command will only flash a kernel. You really shouldn't be messing around with fastboot if you don't actually know what you're doing, that's how phones get bricked. Go to my guide and follow the instructions in section 8:
http://forum.xda-developers.com/showthread.php?t=2839471
[SOLVED]
apparently sometime between me instlling cm11 and installing cm12, my oem got re-locked. which prevented me from flashing anything new.
i ran:
fastboot oem unlock
and fastboot flash boot boot.img
and voila
help thread for those with the same problem
http://forum.xda-developers.com/show....php?t=2839471
thank you for the help!
So I bought my shield tablet back in March, used it until about may I think. Was browsing the internet then it suddenly crashed and got stuck on the Nvidia boot screen. tried to reboot several times. Nothing. So I forgot about it and thought I would just google the reset option later when I had time. Now since June I have tried everything! From factory reset to fast boot and adb my pc won't even recognize my tablet. Also I never turned on usb dbugging cause I didn't even know what that was. I even gave it to the IT guys at work and they couldn't fix it. Now after reading everything there is to read on this problem and trying to fix it myself I'm stuck on the no command screen with the dead android robot. And now I hear there is a recall do to the battery, I can't even check what type I have. So if someone can please help me I would be much appreciative. Also this happened after updating to the latest OS.
okay so i was able to unlock the bootloader and start flashing but from fastboot flash recovery.img and beyond it says failed to write. any ideas of why?
Ace0169 said:
okay so i was able to unlock the bootloader and start flashing but from fastboot flash recovery.img and beyond it says failed to write. any ideas of why?
Click to expand...
Click to collapse
Can you flash twrp and boot to it?
Ace0169 said:
okay so i was able to unlock the bootloader and start flashing but from fastboot flash recovery.img and beyond it says failed to write. any ideas of why?
Click to expand...
Click to collapse
Hello,
Did you use "Fastboot flash recovery.img" as your command line??
I believe it is "Fastboot flash recovery recovery.img"
If you were able to unlock bootloader you're on the right track.
Sent from a Locked Bootloader
Yes I used "fastboot flash recovery recovery.img" but every command after that keeps telling me "failed to write file"
danjull said:
Can you flash twrp and boot to it?
Click to expand...
Click to collapse
I'm a complete noob when it comes to this stuff, what is twrp? Haha
Ace0169 said:
I'm a complete noob when it comes to this stuff, what is twrp? Haha
Click to expand...
Click to collapse
TWRP (Team Win Recovery Project) is a custom recovery that you can flash on your device. You can flash it like the stock recovery over fastboot. With TWRP you can make full system backups, installing roms or other stuff, wipe partitions and more. Keep trying to install the drivers on your pc. Try to use another usb slot or boot your pc into test mode to install the driver. If you can still access the bootloader, you have really good chances to rescue your device.
Okay will try that. Thanks man.
Ace0169 said:
Okay will try that. Thanks man.
Click to expand...
Click to collapse
I see what your doing wrong. You probably don't even have the recovery img to flash. That's why it's giving you a write error.
There is a tutorial in the general section, that should have all the files and links, etc etc that you'll need to flash TWRP/CWM recovery and root the device if you want
Here is the link:
http://forum.xda-developers.com/shi...k-recovery-images-ota-library-guides-t2988881
Sent from my Nexus 5
Mojar7070 said:
I see what your doing wrong. You probably don't even have the recovery img to flash. That's why it's giving you a write error.
There is a tutorial in the general section, that should have all the files and links, etc etc that you'll need to flash TWRP/CWM recovery and root the device if you want
Here is the link:
http://forum.xda-developers.com/shi...k-recovery-images-ota-library-guides-t2988881
Sent from my Nexus 5
Click to expand...
Click to collapse
If your referring to the recovery images from Nvidia website I have dowloaded that, also the correct drivers. Maybe there is something else I'm missing?
Ace0169 said:
If your referring to the recovery images from Nvidia website I have dowloaded that, also the correct drivers. Maybe there is something else I'm missing?
Click to expand...
Click to collapse
First off, let me ask, what is your end result for the tablet?? Are you trying to just go a Complete stock tablet or are you trying to do anything custom (ex. Custom rom, recovery etc etc)
I'm assuming that since you unlocked your Bootloader, your trying to do something custom.
Sent from a Locked Bootloader
Ace0169 said:
If your referring to the recovery images from Nvidia website I have dowloaded that, also the correct drivers. Maybe there is something else I'm missing?
Click to expand...
Click to collapse
Those official nVidia recovery images come with smaller .img files such as recovery.img, system.img, etc. You'll need to flash those one by one ("fastboot flash recovery recovery.img", then run "fastboot flash system system.img", etc. etc.) or you can just run the flashall script that I think is included in the nVidia images.
Otherwise, if you want to flash TWRP, you'll need to download the TWRP recovery (you can rename it to "twrp-recovery.zip"). Then you'll need to "fastboot flash twrp-recovery.zip" in order to flash the twrp recovery to your tablet.
Mojar7070 said:
First off, let me ask, what is your end result for the tablet?? Are you trying to just go a Complete stock tablet or are you trying to do anything custom (ex. Custom rom, recovery etc etc)
I'm assuming that since you unlocked your Bootloader, your trying to do something custom.
Sent from a Locked Bootloader
Click to expand...
Click to collapse
I want my tablet to boot again, it's completely unusable in its condition I've heard re flashing will fix it.
Ace0169 said:
I want my tablet to boot again, it's completely unusable in its condition I've heard re flashing will fix it.
Click to expand...
Click to collapse
OK. Then the link I gave earlier should help flash stock software onto your tablet.
However, that guide is only to go back to factory "state" Operating System wise. It may not help with hardware. Once your flash everything correctly but device still doesn't boot, its probably not software related.
Sent from my Nexus 5
Mojar7070 said:
OK. Then the link I gave earlier should help flash stock software onto your tablet.
However, that guide is only to go back to factory "state" Operating System wise. It may not help with hardware. Once your flash everything correctly but device still doesn't boot, its probably not software related.
Sent from my Nexus 5
Click to expand...
Click to collapse
so ive followed the steps in the link, and ive executed all the commands but when i get to fasboot flash system system.img it says write failed. also all the commands beyond that one. ive got to be missing something. i have the image from nvidia developer, all the drivers, and my fastboot recognizes my device. has anyone encountered this before?
Ace0169 said:
so ive followed the steps in the link, and ive executed all the commands but when i get to fasboot flash system system.img it says write failed. also all the commands beyond that one. ive got to be missing something. i have the image from nvidia developer, all the drivers, and my fastboot recognizes my device. has anyone encountered this before?
Click to expand...
Click to collapse
After you unlocked the device but before trying to flash anything else on the device, try putting the shield into Fastboot mode. At the bootloader, select fastboot using the volume buttons.
koop1955 said:
After you unlocked the device but before trying to flash anything else on the device, try putting the shield into Fastboot mode. At the bootloader, select fastboot using the volume buttons.
Click to expand...
Click to collapse
Select "fastboot protocol"? Is that correct?
Ace0169 said:
Select "fastboot protocol"? Is that correct?
Click to expand...
Click to collapse
So i selected "fastboot protocol" it blipped for a second then brought me back to the bootloader. tried flashing again and once i reached the fastboot flash system system.img it said write failed again. did it not engage the "fastboot protocol"?
Bringing you back to the bootloader was expected behavior. The "write fail" is a mystery to me. Sorry, that is all that I can offer.
koop1955 said:
Bringing you back to the bootloader was expected behavior. The "write fail" is a mystery to me. Sorry, that is all that I can offer.
Click to expand...
Click to collapse
@Ace0169 Same, not sure what else to tell you. Sorry sir.
Sent from a Locked Bootloader
Hello all,
I'm new to the whole rooting scene with my Pixel 3 and found myself stuck in fastboot as a result of this Guide: https://forum.xda-developers.com/pixel-3/how-to/guide-patching-boot-img-magisk-canary-t3964359. I realize that's because the firmware was old.
I then followed this video to reset everything: https://www.youtube.com/watch?v=zQmK5KwN5dk.
However, I am still stuck in the loop. I can now at least get to recovery mode but it just brings me right back to fastboot. I could really use some help getting my phone working again
update
averagejoe13579 said:
Hello all,
I'm new to the whole rooting scene with my Pixel 3 and found myself stuck in fastboot as a result of this Guide: https://forum.xda-developers.com/pixel-3/how-to/guide-patching-boot-img-magisk-canary-t3964359. I realize that's because the firmware was old.
I then followed this video to reset everything: https://www.youtube.com/watch?v=zQmK5KwN5dk.
However, I am still stuck in the loop. I can now at least get to recovery mode but it just brings me right back to fastboot. I could really use some help getting my phone working again
Click to expand...
Click to collapse
I was able to get it to move further by putting in the boot.img but now I get stuck on what I belive is the rescue screen. It says at the bottom of my screen "waiting for rescue commands...". I found online that it will now take adb commands but when I reboot or anything of the sort it just takes me back to the beginning
Put it into fastboot mode. Flash the full factory image with the flash-all bat file. But first edit the flash all bat file and remove the -w near the end. That will save your data.
TonikJDK said:
Put it into fastboot mode. Flash the full factory image with the flash-all bat file. But first edit the flash all bat file and remove the -w near the end. That will save your data.
Click to expand...
Click to collapse
When I downloaded the files from the google site all I found was flash-all.sh. Is that the same?
When I do fastboot flash flash-all.sh, I get the error "cannot determine image file name"
averagejoe13579 said:
When I downloaded the files from the google site all I found was flash-all.sh. Is that the same?
When I do fastboot flash flash-all.sh, I get the error "cannot determine image file name"
Click to expand...
Click to collapse
So I re-extracted everything and found it. Kept getting stuck but now the reason it is saying I'm in fastboot is no valid slot to boot. Any advice?
averagejoe13579 said:
So I re-extracted everything and found it. Kept getting stuck but now the reason it is saying I'm in fastboot is no valid slot to boot. Any advice?
Click to expand...
Click to collapse
Make sure you have the latest platform tools.
Long story short I messed up and now I don't have recovery. Only fastboot. Was bricked too before the no recovery thing.
How do I try to sort this? I don't have a pc either.
Using my old OnePlus 8T I was able to unlock, root and install a custom kernel.
Any ideas?
shadowofdeth said:
Long story short I messed up and now I don't have recovery. Only fastboot. Was bricked too before the no recovery thing.
How do I try to sort this? I don't have a pc either.
the good news is your phone can very likely be fixed. however in my experience you will need a computer. Folks here would love to help but knowing what device you are having an issue with would probably help with response to your situation. from fastboot you can boot a recovery image for your device and go from there. from fastboot you can also likely flash stock firmware to your device and start over fresh. It's also common to have to perform a factory reset after flashing the device to get it to properly boot.
Click to expand...
Click to collapse
OnePlus 9.
I tried searching but there are so many dead ends for finding the stock recovery. Even with that I'd still be bricked.
Where would one find the stock recovery, kernel and fastboot ready update.zip?
You do realize the boot.img is both recovery and kernel. Just extract it from payload.bin
MrSteelX said:
You do realize the boot.img is both recovery and kernel. Just extract it from payload.bin
Click to expand...
Click to collapse
If only I thought of that. It's not like I've been trying all day without success extracting what I need from the payload.bin. Definitely no dead ends there. Thanks for the massive help.
shadowofdeth said:
If only I thought of that. It's not like I've been trying all day without success extracting what I need from the payload.bin. Definitely no dead ends there. Thanks for the massive help.
Click to expand...
Click to collapse
borrow a laptop from someone , use the msm tool
taintsx said:
borrow a laptop from someone , use the msm tool
Click to expand...
Click to collapse
Im so close I can smell it now. Managed to get Python installed (had to deep dive into the comments on articles and tutorials) and have everything extracted in the last hour.
Now, for flashing these images I have to use Termux and it's working for the most part. My issue is now that I can flash one batch of images but not the other as per the xda guide linked now:
Restore OnePlus 9 to Stock via Fastboot Commands
This guide assumes you have the SDK Platform Tools installed and working, along with USB drivers for your device (if needed), and have your full update zip which you've already extracted the payload.bin from, and then dumped the images using...
forum.xda-developers.com
I keep getting errors about the partition being locked or something.
So close man. So close.
Locked partitions can only be flashed in fastbootd (fastboot reboot fastboot to get there).
First of all... Hold the both volume and power button for around 2 minutes. It'll take you to the bootloader mode. Then from the bootloader mode turn off your device then boot into edl then flash with msm.
Lesson learned