Related
Hi Guys,
I have a rooted HTC Hero so am familiar with rooting Android etc.
I said I'd help a colleague out with a problem on her newly purchased Nexus One but I'm struggling. When you turn it on, it doesn't actually boot up - the static X (not the animated one) just sits there indefinitely. We've left it for ages and it doesn't do anything at all.
The only progress I have managed to make so far is to unlock the bootloader through "fastboot oem unlock". I've since tried copying some stock N1 ROMs onto the SD Card and tried getting them to install through the Bootloader/Hboot screen as passimg.zips. They're recognised and the blue progress bar runs but it always fails.
I also don't seem to be able to get adb access to the device. "adb devices" returns no results and "adb shell" obviously says "device not found".
I've also tried writing amon_ra's recovery to the device via fastboot and while it sends it fine, it fails to write (remote: image update error).
I'm assuming the last two points are because usb debugging isn't enabled (can't boot it to do so) and it isn't rooted.
Is there some way I can get a ROM flashed onto this that will boot to allow me to root it and then install the custom recovery and a ROM of my choice?
If it makes any difference, the model should be a UK Vodafone one. One of the passimg.zips I've tried has been PASSIMG_Passion_Google_WWE_1.01.1700.1_ERD79_release_signed.zip, which I read is the one to downgrade Vodafone N1's to but it failed.
Any help at all will be gratefully received.
Thanks in advance.
Just a quick update about the passimg.zip failures...the error message is "main version is older"
Have also just tried a "fastboot boot recovery.img" (where recovery.img is a renamed amon_ra)...it downloaded fine and kicked off a reboot but it didn't actually boot into the recovery image at all...it remains at the static X screen (with unlocked padlock).
Have now tried a stock FRF91 as passimg.zip and this time it didn't error at the end. Instead it just returned to the menu after checking the passimg and didn't prompt me to apply etc...
Look here and download the PASSIMG.zip from the second post. put in root of sd .This will pass the "Older rom version" But it will downgrade you to EPE76.
If everything works out good. You would have EPE76 and a working N1. but you will need to download FRF85B. http://www.mediafire.com/?j5zejudgngm. rename that to update.zip. put into root of sd. boot into stock recovery. once you see triangle and android hold power and hit volume up. You will then see the recovery menu. Select apply update.zip. if its an success you will have FRF85B. Then just go to settings>system updates and search for FRF91 update.
Thanks for the reply. EPE76 is one of the ones I recently tried but even though it passes the check, it doesn't seem to apply. I don't get an option to apply and rebooting results in the static X again.
Earlier I managed to successfully apply amon_ra's recovery through fastboot. Apparently. The text in my command prompt said it was successful but attempting to boot into recovery from the bootloader menu presents me with the same static X.
I really don't understand what's going on with this thing.
I've now downloaded EPE76 in its original img component format from modaco and flashed boot, system, and userdata onto the three partitions separately using fastboot. System took three attempts but succeeded eventually.
Despite now having what should be EPE76 forced onto it, it still refuses to boot, giving me only the static X again.
I'm running out of ideas here. Does anyone have any suggestions at all?
Anybody? (bump)
I'm assuming she bought it used (because if it's new you would have took it back). From what I know, it sounds like a radio flash gone bad
I hope I'm wrong though.
I was dumb enough to root my phone and try using some custom roms just to get a black notification bar and a couple other things. Thats literally all I wanted. Used Cyan, couldnt get notification bar to change color so went back to original. Anyways thought I'd try flashing the black desire bar or w/e, and failed.
Tries booting up and gets half stuck on the nexus 'X' animation loop. It gets really laggy and studders, never fully completing the loop. So I say eff it after fifteen or so minutes and reboot to recovery. Only it's the stock android recovery, not that clockwork one? So I'm lost, can't flash back to original, and decide i'll just try the factory reset. I have no time for this stuff at this point, and just want my phone so I can talk to people.
Did factory reset/wipe option, and still nothing, stuck on boot. Don't know what to do and I would greatly appreciate some help or advice. Honestly would be so sad if this $500 phone is a paperweight.
Dude relax,
1.First boot to superboot
2.Flash your clockwork (Or any other recovery). DONT REBOOT.
3.Go straight to recovery,
4.Restore your nandroid back up,
--- If you dont have back up then you have to download rom what you want (Stock froyo can be found some where in htc site)
--- Select mass storage option in the recovery and copy there the zip file, then flash it.
Tadaa everything is working again
Read my signature, "unroot / restore your Nexus", and execute. If you have ever updated to FRG83, you might be out of luck and no PASSIMG.ZIP will flash. In this case, you'll need to connect using ADB and run flash_image to flash recovery (most probably you'll get adb shell even if your phone isn't finishing boot - just make sure you run adb shell early enough in the boot). Once you've flashed the recovery, get into it and proceed with a custom ROM. If you flash stock again, your recovery will be lost again. If you didn't set up ADB (enable "USB Debugging" option on your phone) - then you're seriously out of luck. If you have it, but don't know how to use it - spend time reading and understanding "flashing Recovery" guide in the same place from my signature (Wiki), and if you have any further questions along the way - ask here.
You're not booting up because you've screwed up framework-res.apk and possibly some other system files - so you're stuck in boot loop. Need to read and understand what you're doing before you're doing it. It's really not that hard, and not willing to spend enough time understanding things "pays off" if mishaps happen - and they happen.
elkyur said:
Dude relax,
1.First boot to superboot
Tadaa everything is working again
Click to expand...
Click to collapse
He can't boot! Do you read what I read? He's stuck in a bootloop! What boot are you talking about?!
Take your time reading before you rush answering with wrong and incomplete instructions that won't get the OP anywhere. A good portion of mishaps happens because of instructions like these.
This is alot for me to take learn in such quick time to be honest.
I can't even get adb to recognize my phone and i've followed all the steps. My computer makes the noise that something has been plugged in through USB, but nothing else. Under that program to uninstall drivers, I try uninstalling them, but they just stay there, nothing changes.
As for the USB debugging and me being ****ed, I'm pretty sure I left that on.
Maybe it would help me if I told you more about what I know and what I've done.
Literally just followed the step by step instructions from this site theunlockr.com/ to root my phone and use a custom rom.
In the process it made me install PDANet (again probably means nothing, but I don't know).
If adb isn't recognizing my phone, I can't flash using it. Again thank you for the help, as I really am clueless about most stuff like this.
Most of the time when doing anything that could possibly do any harm to a device, I am very cautious. I have hacked several PSP's and didn't think this would be much different...
I read all about the rooting, and knew full well all i wanted to do was get a new notification bar, I didn't really read into the rest as I had no desire or use for that information. Then everything went well, and I learnt how easy it was to go back if I screwed up or didn't like what I had flashed. Not to mention people saying it's near impossible to brick your phone unless your really trying to. Maybe that was just me being ignorant, this could not have happened at a worse time. And I cannot thank you enough for your help thus far.
Thank you for the help. Your guides were very helpful. But unfortunately every step of the way I have run into some sort of problem.
When trying to install the sdk drivers, it won't let me install the amd64 or the i386, but only both of them together. As in it selecting usb_drivers installs (where both of the seperate drivers can be found). I don't know if this is right or not.
When typing in "fastboot devices", "HT036P901361 decives" shows up, but when viewed in USBDeview, 2 of the 3 HT036P901361 drivers show as not connected. The only one that shows as connected is the "vendor specific" one.
Also adb devices, shows nothing.
So again, I'm asking for advice or help.
Edit: So I can reboot fastboot through my computer, but cannot flash anything,
typing in "flashboot flash recovery recovery.img" I get a "cannot load recovery.img".
My recovery.img file is saved on the root of the SD card which is in the phone. Is this the correct way to do it? If so I assume it's still because of the issue stated at the beginning of this post (before edit).
Edit 2: Okay decided to try this
fastboot flash recovery C:\CWrecovery.img (where its located on my hdd), and it starts then says failed infoSignature.
volsey said:
Thank you for the help. Your guides were very helpful. But unfortunately every step of the way I have run into some sort of problem.
1. When trying to install the sdk drivers, it won't let me install the amd64 or the i386, but only both of them together. As in it selecting usb_drivers installs (where both of the seperate drivers can be found). I don't know if this is right or not.
2. When typing in "fastboot devices", "HT036P901361 decives" shows up, but when viewed in USBDeview, 2 of the 3 HT036P901361 drivers show as not connected. The only one that shows as connected is the "vendor specific" one.
3. Also adb devices, shows nothing.
So again, I'm asking for advice or help.
4. Edit: So I can reboot fastboot through my computer, but cannot flash anything,
typing in "flashboot flash recovery recovery.img" I get a "cannot load recovery.img".
My recovery.img file is saved on the root of the SD card which is in the phone. Is this the correct way to do it? If so I assume it's still because of the issue stated at the beginning of this post (before edit).
Edit 2: Okay decided to try this
fastboot flash recovery C:\CWrecovery.img (where its located on my hdd), and it starts then says failed infoSignature.
Click to expand...
Click to collapse
Let's get one thing straight. You need to read more, I guess, because you still don't know the basics - and with the lack of knowledge, it's going to be hard to help you.
Fastboot commands and driver only work when you're booted into bootloader - which is, 3 droids on skateboards on white screen and text menu, get there by booting with trackball or volumedown button pressed.
adb works only when you're booting the OS - which means, you don't touch anything and let the phone boot. Right when boot animation starts, adb should also start.
1. That's correct.
2. Are you booting into bootloader? There should be no other way to view fastboot driver. In that case, DON'T boot to bootloader, just reboot your phone and let it loop, and only then try "adb devices". If it works - use the "flash_image" method to flash recovery.
3. Read (2) above.
4. If your bootloader isn't unlocked (does it show a padlock below Nexus logo when you boot?), you won't be able to flash non-standard recovery through fastboot. You might be able to flash a complete system image through fastboot, though. Download a factory image, FRF91 for example, unzip it, then do "fastboot flash system system.img", "fastboot flash boot boot.img", and reboot.
When you flash something, you should open the Command prompt in the same directory as the file you're trying to flash! Or use full path for the image you're flashing. And it should be on the computer, not on SD card.
If everything fails - just unlock your bootloader and fastboot flash anything you want.
I am using bootloader.
C:\android-sdk-windows\tools>fastboot flash system system.img
sending 'system' (58570 KB)... OKAY [ 8.293s]
writing 'system'... INFOsignature checking...
FAILED (remote: signature verify fail)
finished. total time: 15.014s
That's the error I'm getting everytime.
I got the system.img from hXXp://developer.htc.com/adp.html, I tried looking for FRF91 but could only find megaupload links, and I had exceeded my limit somehow.
As for adb, still getting no devices when I leave it to boot by itself even though I've:
Uninstalled the 3 drivers, unplugged/rebooted, plugged back in/turned back on, and it automatically installs the wrong drivers again too quickly to do anything about it. I've gone into advanced system settings and checked it to never install system drivers automatically. Tried updating drivers, all say they're up to date.
1)So is bootloader not an option for me? Or is there something else I haven't tried? Why am I getting the signature errors?
2)Is it the drivers that are keeping adb from recognizing my phone? How do I fix this?
Any suggestions?
Ok, looks like USB debugging isn't on. In that case, there are exactly 2 options:
1) from here:
http://developer.htc.com/
Download FRG83 image for Nexus, rename to PASSIMG.ZIP, put on the root of your SD card (you can't use the phone for it, so use SD card reader), reboot into bootloader, it'll ask you to flash system image, answer "yes", wait for it to flash. Keep the phone powered. WAIT.
2) if it doesn't work - you're out of luck. "fastboot oem unlock" it is. Then you can flash whatever you want with fastboot.
Is it just me or is not possible to flash a recovery, like TWRP from fastboot? I've been reading a bunch of guides online and tried at least a dozen different ways to install a recovery from fastboot all to no avail.
That said, I CAN successfully flash a recovery from Hasoon's all in one toolkit and from a app like twrp/cwm/flashify after installing a rooted rom. So the fact that I can't get it to work from fastboot, yet it works perfectly fine with this pre-made program has been bugging the living **** out of me. I'll list the two processes I use below so please tell me either they are incorrect or perhaps it's just simply not possible to install TWRP or other recoveries from fastboot.
I have tried each of these processes with versions ranging from TWRP 2.5-2.7 and none of them will work, each time I flash them and attempt to access the recovery it will say in pink lettering above "entering recovery..." then it just reboots the phone, occasionally the teamwin loading screen will pop up but then it simply disappears and reboots.
Anyways here's the processes I've tried
1. in the cmd prompt I do 'fastboot flash recovery TWRP.img' then reboot the bootloader and go to the recovery.
2. in the cmd prompt I do 'fastboot flash recovery TWRP.img' then do 'fastboot erase cache' and restart the bootloader then attempt to enter recovery.
These are the two slightly different processes I've tried, each time it appears as though it's working in the cmd prompt but then when I go to start the recovery it just reboots the phone. Also incase you're wondering, I did rename each of the recoveries to TWRP all uppercase before attempting the flash them).
If you have any ideas please let me know, although this isn't too big of a deal this has been bugging me a lot!
I was trying to fix an issue with my phone the other day, and saw that re-locking the bootloader might fix it. Nobody mentioned anything about it completely wiping the phone, including the internal SD card. I set most of the stuff back up again but realized that it was suffering from the bug on the old radio version that causes it to lose LTE randomly.
I went and rebooted into TWRP to try and flash it, and TWRP showed a completely empty sdcard partition and said it could not mount '/data'. I enabled "require pattern to boot," thinking it may not have known to decrypt the partition without that, and now I can't get into TWRP at all. I tried disabling the "require pattern to boot" option again but no luck. It shows the "Google" logo for about 5 seconds, then the blue "TEAMWIN" logo for about 3 seconds, then reboots to the "Google" logo and proceeds to boot normally. I should note that I have CM12.1 installed, and the latest TWRP. I've tried reflashing TWRP and that didn't help; I also did "fastboot format cache" and then "fastboot flash cache cache.img" using the stock factory cache.img. I got the radio flashed using fastboot, but I'd really like to have a working recovery.
briman0094 said:
I was trying to fix an issue with my phone the other day, and saw that re-locking the bootloader might fix it. Nobody mentioned anything about it completely wiping the phone, including the internal SD card. I set most of the stuff back up again but realized that it was suffering from the bug on the old radio version that causes it to lose LTE randomly.
I went and rebooted into TWRP to try and flash it, and TWRP showed a completely empty sdcard partition and said it could not mount '/data'. I enabled "require pattern to boot," thinking it may not have known to decrypt the partition without that, and now I can't get into TWRP at all. I tried disabling the "require pattern to boot" option again but no luck. It shows the "Google" logo for about 5 seconds, then the blue "TEAMWIN" logo for about 3 seconds, then reboots to the "Google" logo and proceeds to boot normally. I should note that I have CM12.1 installed, and the latest TWRP. I've tried reflashing TWRP and that didn't help; I also did "fastboot format cache" and then "fastboot flash cache cache.img" using the stock factory cache.img. I got the radio flashed using fastboot, but I'd really like to have a working recovery.
Click to expand...
Click to collapse
no working recovery with a locked bootloader, sorry. if the bootloader is locked, you cant flash anything. its locked. to flash things, you need an unlocked bootloader. its like locking a door, but expecting it to open magically when you walk up to it.
simms22 said:
no working recovery with a locked bootloader, sorry. if the bootloader is locked, you cant flash anything. its locked. to flash things, you need an unlocked bootloader. its like locking a door, but expecting it to open magically when you walk up to it.
Click to expand...
Click to collapse
I forgot to mention that I re-unlocked the bootloader. I can also boot the OS so I'd be able to enable OEM unlock again if needed.
briman0094 said:
I forgot to mention that I re-unlocked the bootloader. I can also boot the OS so I'd be able to enable OEM unlock again if needed.
Click to expand...
Click to collapse
important thing to forget to mention
So what happened when you reflashed the lasted version of twrp for your device after verifying the downloads md5?
simms22 said:
important thing to forget to mention
Click to expand...
Click to collapse
I guess I assumed that when I said "continues to boot normally" people would assume I could re-enable "OEM Unlock" if needed
scryan said:
So what happened when you reflashed the lasted version of twrp for your device after verifying the downloads md5?
Click to expand...
Click to collapse
All the console output indicates success, and it boots to the initial "TEAMWIN" logo for a few seconds and reboots.
No Recovery Similiar issue
briman0094 said:
I was trying to fix an issue with my phone the other day, and saw that re-locking the bootloader might fix it. Nobody mentioned anything about it completely wiping the phone, including the internal SD card. I set most of the stuff back up again but realized that it was suffering from the bug on the old radio version that causes it to lose LTE randomly.
I went and rebooted into TWRP to try and flash it, and TWRP showed a completely empty sdcard partition and said it could not mount '/data'. I enabled "require pattern to boot," thinking it may not have known to decrypt the partition without that, and now I can't get into TWRP at all. I tried disabling the "require pattern to boot" option again but no luck. It shows the "Google" logo for about 5 seconds, then the blue "TEAMWIN" logo for about 3 seconds, then reboots to the "Google" logo and proceeds to boot normally. I should note that I have CM12.1 installed, and the latest TWRP. I've tried reflashing TWRP and that didn't help; I also did "fastboot format cache" and then "fastboot flash cache cache.img" using the stock factory cache.img. I got the radio flashed using fastboot, but I'd really like to have a working recovery.
Click to expand...
Click to collapse
Briman, I seem to have a similar issue on my and wife's Google Nexus 6s. I unlocked and rooted using Wug Tool Kit I used in years past with seamless success. To confirm root CM 12.1 I can get into bootloader, Teamwin. From there I am to flash the Superuser, Busybox and TWRP zips under SD\iReady to Flash\Rootfiles..... Only I am not given an option on the menu? I am struggling with using the command prompt and proper paths from SDK Tools so that is not an option at this moment. I see a File Manager that shows this path but am hesitant to use it as I have READ this could cause damage ( brick) to the system. Watching your thread for answers or possibilities. I know the senior members as Simm22 dislike tool kits and so do I. I am simply trying to grow and learn.
ray6279 said:
Briman, I seem to have a similar issue on my and wife's Google Nexus 6s. I unlocked and rooted using Wug Tool Kit I used in years past with seamless success. To confirm root CM 12.1 I can get into bootloader, Teamwin. From there I am to flash the Superuser, Busybox and TWRP zips under SD\iReady to Flash\Rootfiles..... Only I am not given an option on the menu? I am struggling with using the command prompt and proper paths from SDK Tools so that is not an option at this moment. I see a File Manager that shows this path but am hesitant to use it as I have READ this could cause damage ( brick) to the system. Watching your thread for answers or possibilities. I know the senior members as Simm22 dislike tool kits and so do I. I am simply trying to grow and learn.
Click to expand...
Click to collapse
na, toolkits work fine. sure, they occasionally do mess up, but its not very ofver. i generally like ut when noobies do the rooting the correct way the first time, that way they can learn some basic things about how everything works. then, they can yse toolkits all they
btw, teamwin isnt your bootloader, its your recovery. team win = twrp. now all you need to do is download the latest supersu and flash it via your recovery, and the you can install a busybox app from tbe play store, and use it to unstall .
briman0094 said:
I was trying to fix an issue with my phone the other day, and saw that re-locking the bootloader might fix it.
Click to expand...
Click to collapse
Saw that bit of advice where? I can't think of a single thing re-locking the bootloader would fix.
nhizzat said:
Saw that bit of advice where? I can't think of a single thing re-locking the bootloader would fix.
Click to expand...
Click to collapse
A screenshot of an e-mail from a Google employee regarding Android Pay and SafetyNet.
50% JOY No Fastboot?
simms22 said:
na, toolkits work fine. sure, they occasionally do mess up, but its not very ofver. i generally like ut when noobies do the rooting the correct way the first time, that way they can learn some basic things about how everything works. then, they can yse toolkits all they
btw, teamwin isnt your bootloader, its your recovery. team win = twrp. now all you need to do is download the latest supersu and flash it via your recovery, and the you can install a busybox app from tbe play store, and use it to unstall .
Click to expand...
Click to collapse
I followed your directions while working on my Nexus6 phone. Was able to access bootloader then install iReady files. Worked perfectly and phone loaded SUPERUSER, BUSYBOX & PERM RECOVERY. Not so much on wife's Nexus 6. I get thru UNLOCK & ROOT w/custom recovery on the Wug Fresh Tool Kit. At RECOVERY menu pulls up SD - Up one level. No option is allowed to continue on and load the three mentioned packages. I then able to reboot to system. Does it appear I am bootloading but not fastbooting? Will try and insert images.
ray6279 said:
I followed your directions while working on my Nexus6 phone. Was able to access bootloader then install iReady files. Worked perfectly and phone loaded SUPERUSER, BUSYBOX & PERM RECOVERY. Not so much on wife's Nexus 6. I get thru UNLOCK & ROOT w/custom recovery on the Wug Fresh Tool Kit. At RECOVERY menu pulls up SD - Up one level. No option is allowed to continue on and load the three mentioned packages. I then able to reboot to system. Does it appear I am bootloading but not fastbooting? Will try and insert images.
Click to expand...
Click to collapse
one question.. what is perm recovery?? the only recovery that works on the n6 is twrp recovery.
and when you are in her recovery, is it showing you the right location where the files should be? if nit, you csn change the lication.
Simm & Others. Thank you for your good words and suggestions. It would be easier for me to list what I did not attempt rather than what I did try. . I tried nearly most functions in the Wug Fresh ( by Harold) v2.0.5 after failing to find the correct command prompt to use ADB. What happened is an odditity. Mind you, I've been on these two Nexus 6 phones for 4-6hours a day for about ten days! Day later, Happened to be waiting for wife in parking lot and picked up phone and pressed SuperUser. Viola! It went into TWRP and gave me an RECOVERY option. On impluse, I flashed TWRP and Superuser zips. It took and processed. however, the best part of this is the hands on learning experience of booting, flashing, wiping, language, terms, SDK, Android and more. Once I figure out my path problem on my windows based PC to loading ABD commands I am continuing my self study of Android and App development. How do I get the packages out of the SDK Tool Kit to folders in PC? Thanks all.
ray6279 said:
Simm & Others. Thank you for your good words and suggestions. It would be easier for me to list what I did not attempt rather than what I did try. . I tried nearly most functions in the Wug Fresh ( by Harold) v2.0.5 after failing to find the correct command prompt to use ADB. What happened is an odditity. Mind you, I've been on these two Nexus 6 phones for 4-6hours a day for about ten days! Day later, Happened to be waiting for wife in parking lot and picked up phone and pressed SuperUser. Viola! It went into TWRP and gave me an RECOVERY option. On impluse, I flashed TWRP and Superuser zips. It took and processed. however, the best part of this is the hands on learning experience of booting, flashing, wiping, language, terms, SDK, Android and more. Once I figure out my path problem on my windows based PC to loading ABD commands I am continuing my self study of Android and App development. How do I get the packages out of the SDK Tool Kit to folders in PC? Thanks all.
Click to expand...
Click to collapse
your welcome, but you are still off in one bit of fact. you use fastboot, not adb, to flash a recovery(and system.img)
edit.. you can use apps like flashify to flash recovery, if you have root already.
So BOOTLOADER is the USB connection between the device and PC. FASTBOOT is the process via we make changes in the device via the PC. ADB is the device language via which we communicate. So do I still need to flash a system recovery image? Flashify App? I already went thru install>iready to flash> superuser (version)>busybox>flash>reboot>system. I'm going cross eyed from reading. The wiping part worries me as I fear formatting or deleting essential data.
ray6279 said:
So BOOTLOADER is the USB connection between the device and PC. FASTBOOT is the process via we make changes in the device via the PC. ADB is the device language via which we communicate. So do I still need to flash a system recovery image? Flashify App? I already went thru install>iready to flash> superuser (version)>busybox>flash>reboot>system. I'm going cross eyed from reading. The wiping part worries me as I fear formatting or deleting essential data.
Click to expand...
Click to collapse
ok, when wiping, dont do the first option wipe, itll wipe your whole phone clean. you need to select the advanced options and pick what you want wiped. fastboot is the way to unlock your bootloader, or flash a recovery. also, you use it to flash a system.img or any part of it.
adb is a general linux that can be used with android, anywhere but in the bootloader(only fastboot in the bootloader).
bootloader isnt the usb connection between the device and the pc, its part of the phone that boots it and decides if the rom is safe to run. thats why we unlock it. so we can flash roms eithout googles key.
fastboot is the tool that you use to do whatever needs to be fone in the bootloader, adb everywhere else.
a recovery you need if you want to flash custom roms, kernels, supersu, or other mods. you can also wipe different partitions with the recovery, or make a "nandroid' backup. thats a bavkup of everything. its like a complete snapshot of everything during the time you made it. if you ever mess up your phone, you can restore it, and you will be at the exact same place when you made the backup.
anything else?
So, I ****ed up.
Earlier this night i hard bricked my device while trying to uninstall Magisk. Used a guide that worked and was back on stock OOS 3.5.0.
In the old Oxygen OS I installed TWRP. But the thing with the recovery was that you needed to boot recovery from the command line with the command
Code:
fastboot boot twrp.img
. If I booted into recovery in any other way the screen is just black and never boots.
When I tried to install OOS 4.0.1 I got error code 7. Googled it and it just told me to relock the bootloader and install the OTA instead.
I relocked it, and when it was done I got the prompt to fill in the password to start Android. But the thing was I did not use any security options, no fingerprint or pin code. So zero luck there. And now I can't boot into recovery because I didn't flash the stock recovery because I'm a retard, so when I'm trying to boot recovery it's just black. So I have no chance to come back. Please help...
So this is not a hard brick. It's a brick for sure, but a Hard Brick is where you cannot boot up your phone whatsoever.
Now, assuming from the vague details you've provided, you can boot into the normal boot logo screen? You should be able to get into fastboot, but if you can't since you've not mentioned it, there are still ways of getting your device back into OOS.
If you can get your device into Fastboot;
1. Boot into FB
2. Unlock your bootloader
3. Reflash TWRP
4. Boot into TWRP
5. Flash ROM of your choice.
If you can't get into Fastboot;
Use this thread ( https://forum.xda-developers.com/oneplus-3t/how-to/unbrick-unbrick-tutorial-oneplus-3t-t3515306)
OR use this one if you want the updated tools and follow the instructions on the above Thread (https://forum.xda-developers.com/oneplus-3t/help/ultra-brick-oreo-firmware-ob16-nougat-t3689356)
What you need to know;
Never lock your bootloader when you have a Third Party recovery or ROM installed.
Never interrupt the unbrick process.
Please do a search here on XDA before you post a new thread. There have been similar issues solved multiple times on this Forum.
Good luck!
thes3usa said:
So this is not a hard brick. It's a brick for sure, but a Hard Brick is where you cannot boot up your phone whatsoever.
Now, assuming from the vague details you've provided, you can boot into the normal boot logo screen? You should be able to get into fastboot, but if you can't since you've not mentioned it, there are still ways of getting your device back into OOS.
If you can get your device into Fastboot;
1. Boot into FB
2. Unlock your bootloader
3. Reflash TWRP
4. Boot into TWRP
5. Flash ROM of your choice.
If you can't get into Fastboot;
Use this thread ( https://forum.xda-developers.com/oneplus-3t/how-to/unbrick-unbrick-tutorial-oneplus-3t-t3515306)
OR use this one if you want the updated tools and follow the instructions on the above Thread (https://forum.xda-developers.com/oneplus-3t/help/ultra-brick-oreo-firmware-ob16-nougat-t3689356)
What you need to know;
Never lock your bootloader when you have a Third Party recovery or ROM installed.
Never interrupt the unbrick process.
Please do a search here on XDA before you post a new thread. There have been similar issues solved multiple times on this Forum.
Good luck!
Click to expand...
Click to collapse
Thank you for your reply, I tried to do the method with the MSMDownload thing yesterday, but the computer did not recognize the device. It was late in the night (5am) so I went to bed. This morning I took my other computer and plugged my phone in, it recognized it and I was able to fully recover the phone!
avveawesome said:
When I tried to install OOS 4.0.1 I got error code 7. Googled it and it just told me to relock the bootloader and install the OTA instead.
Click to expand...
Click to collapse
This isn't good idea. As already noted, never relock the bootloader on this device with TWRP, root, etc. It should only be relocked after returning to full stock condition.
Also, never install an incremental OTA when you have TWRP (root, etc.), only the full update zips should be used in that case.
Try to stick to these forums for advice. Maybe the guidance your found above is not specific to this device?