Related
Hi guys. Was just trying to install a 4.4 custom rom on my HTC One using CWM. I got into rrecovery mode and started trying to install the rom but it came up with an error saying it had aborted. I realised I hadn't made a backup so I thought I best do it in case anything goes wrong. I tried doing that and rebooting the phone. Now the HTC logo flashes on screen before flashing off and then the phone puts me back in recovery. Have I bricked this phone? If anyone can help me I can answer any more necessary questions.
krisdeaco said:
Hi guys. Was just trying to install a 4.4 custom rom on my HTC One using CWM. I got into rrecovery mode and started trying to install the rom but it came up with an error saying it had aborted. I realised I hadn't made a backup so I thought I best do it in case anything goes wrong. I tried doing that and rebooting the phone. Now the HTC logo flashes on screen before flashing off and then the phone puts me back in recovery. Have I bricked this phone? If anyone can help me I can answer any more necessary questions.
Click to expand...
Click to collapse
You need TWRP 2.6.3.3 (or later) for 4.4 roms, also if you are using a GPE rom, then you need to be s-off.
Download from here: http://techerrata.com/browse/twrp2/m7 don't use a download manager, it will fail; download normally and check MD5 to make sure file is not corrupt,
go to bootloader/FASTBOOT USB, and flash it:
fastboot flash openrecovery-twrp-2.6.3.3-m7.img
fastboot erase cache
fastboot reboot-bootloader
and install the ROM again.
nkk71 said:
You need TWRP 2.6.3.3 (or later) for 4.4 roms, also if you are using a GPE rom, then you need to be s-off.
Download from here: don't use a download manager, it will fail; download normally and check MD5 to make sure file is not corrupt,
go to bootloader/FASTBOOT USB, and flash it:
fastboot flash openrecovery-twrp-2.6.3.3-m7.img
fastboot erase cache
fastboot reboot-bootloader
and install the ROM again.
Click to expand...
Click to collapse
Sorrry if I seem like a complete fool but how to I flash the recovery image. I'm in the fastboot usb menu now but there doesn't appear to be any option to flash.
krisdeaco said:
Sorrry if I seem like a complete fool but how to I flash the recovery image. I'm in the fastboot usb menu now but there doesn't appear to be any option to flash.
Click to expand...
Click to collapse
from you PC
open a command prompt, go to the folder where adb is (also put the downloaded recovery there), then on your PC, type commands in bold above.
nkk71 said:
from you PC
open a command prompt, go to the folder where adb is (also put the downloaded recovery there), then on your PC, type commands in bold above.
Click to expand...
Click to collapse
Again, rreally sorry. Where will I find ADB? Where would it typically be?
EDIT: I've downloaded minimal ADB and Fastboot and out the recovery image in there. I've tried typing in the top command but had no luck. A little more help, please? Thank you for your help so far by the way
krisdeaco said:
Again, rreally sorry. Where will I find ADB? Where would it typically be?
Click to expand...
Click to collapse
wherever you put it, didnt you unlock your phone using "fastboot flash unlocktoken Unlock_code.bin"? that would be the folder (often referred to the adb sdk)
nkk71 said:
wherever you put it, didnt you unlock your phone using "fastboot flash unlocktoken Unlock_code.bin"? that would be the folder (often referred to the adb sdk)
Click to expand...
Click to collapse
Ah yes thanks. I've found it all and put it where you said. I've tried to flashing it but I'm getting the message:
"unknown partition 'fastboot flash openrecovery-twrp-2.6.3.3-m7.img'
error:cannot deterrmine image filename for 'fastboot flash openrecovery-twrp-2.6.3.3-m7.img'
krisdeaco said:
Ah yes thanks. I've found it all and put it where you said. I've tried to flashing it but I'm getting the message:
"unknown partition 'fastboot flash openrecovery-twrp-2.6.3.3-m7.img'
error:cannot deterrmine image filename for 'fastboot flash openrecovery-twrp-2.6.3.3-m7.img'
Click to expand...
Click to collapse
fastboot flash recovery openrecovery-twrp-2.6.3.3-m7.img
fastboot erase cache
please be careful with things like these, you don't want to mess up your phone, reading and staying calm, not rushing things, IS A MUST!!
nkk71 said:
wherever you put it, didnt you unlock your phone using "fastboot flash unlocktoken Unlock_code.bin"? that would be the folder (often referred to the adb sdk)
Click to expand...
Click to collapse
nkk71 said:
fastboot flash recovery openrecovery-twrp-2.6.3.3-m7.img
fastboot erase cache
please be careful with things like these, you don't want to mess up your phone, reading and staying calm, not rushing things, IS A MUST!!
Click to expand...
Click to collapse
Sorry I'm just panicking an awful lot. I'm a bit calmer now though so I'll crack on. I've got TWRP back up and I've tried to install the ROM but it keeps saying failed. Is therre any way to make my phone available to transfer to so I can try a different ROM?
EDIT: It seems I did make a backup with TWRP, I'm assuming that wouldn't show up on CWM? That seems to be working so I'll count myself lucky. I would very much like to get stock android 4.4 though so do you know of any detailed guides for getting that with TWRP on HTC one?
By the way THANK YOU SO MUCH for everything. I completely panicked and I would never have figured any of this out without your help. Thank you.
krisdeaco said:
Sorry I'm just panicking an awful lot. I'm a bit calmer now though so I'll crack on. I've got TWRP back up and I've tried to install the ROM but it keeps saying failed. Is therre any way to make my phone available to transfer to so I can try a different ROM?
Click to expand...
Click to collapse
yes plenty, now please go get a glass of water and I'll post back in a minute, you need to relax, we'll have your phone up and running soon.
Which ROM would you like to have? post, then get that water/coffee/beer/scotch whatever makes you calm down :laugh:
krisdeaco said:
EDIT: It seems I did make a backup with TWRP, I'm assuming that wouldn't show up on CWM? That seems to be working so I'll count myself lucky. I would very much like to get stock android 4.4 though so do you know of any detailed guides for getting that with TWRP on HTC one?
Click to expand...
Click to collapse
Unfortunately, TWRP and CWM backups aren't interchangeable but you can always flash back the proper recovery for the backup, and restore.
krisdeaco said:
I would very much like to get stock android 4.4 though so do you know of any detailed guides for getting that with TWRP on HTC one?
Click to expand...
Click to collapse
Details please , GPE or Sense, any one in particular, best post a link to the one you'd like to have.
krisdeaco said:
By the way THANK YOU SO MUCH for everything. I completely panicked and I would never have figured any of this out without your help. Thank you.
Click to expand...
Click to collapse
Feel free to hit the thanks button
Hi, Gang... Please be patient as I'm not normally playing at this level...
I recently had a kid kill my TF700 so I bought at TF701 as a replacement. I immediately unlocked it, forgetting to take the latest Asus update OTA beforehand. Anyways, I manually downloaded v11.4..1.17 and put it on a blank microSD and stuck it into the tablet where the update was recognized as available and I set the update in motion... Something went sideways after I walked away to let the update run and now I can't get back into the system and I can't get into recovery.
I have the bootloader up (1.00e as released by 10.14.1.47) and I can communicate with the device via fastboot. Can someone help me wipe and get a recovery.img and/or a full stock image onto this thing. Right now it just keeps rebooting unless I manually force it to the bootloader.
I'm hoping someone more knowledgeable can chastise me for being a moron an point me in the right direction. Ultimately, I was tying to get to the latest ASUS ROM to the the bootloader that goes with it and then move onto a custom ROM.
Many thanx.
Im no help. Dont listen to me. Try using fastboot to run a recovery. "fastboot boot recovery.img" from the bootloader. Maybe with that old bootloader you should be using an old recovery maybe.
---------- Post added at 08:27 PM ---------- Previous post was at 08:19 PM ----------
I wouldnt flash a recovery/bootloader especially the new ones til you can verify an older recovery works. Try booting this one https://www.dropbox.com/s/il2m4rtxlmzjfz9/recovery.img but dont flash til someone else takes a look at this. This is an old philz touch without touch.
Still nothing...
YayYouFixedIt said:
Im no help. Dont listen to me. Try using fastboot to run a recovery. "fastboot boot recovery.img" from the bootloader. Maybe with that old bootloader you should be using an old recovery maybe.
I'm really starting to get frustrated... (understatement)
I've got a copy of the 4.4.2 OTA image (zip and recovery.img). Should I not be able to use ADB to copy the image to the device and then boot the recovery.img? I can get the tablet to respond to fastboot but I can't get it to be recognized by ADB.
I've never had issues with custom ROMs before. This time I'm wading into unfamiliar waters. I'm note even sure how the initial update failed. Is there a way for me to update the bootloader, then add a CWM recovery, then load the ROM?
Again sorry to have to ask but any help would greatly be appreciated.
Click to expand...
Click to collapse
kartman_canada said:
YayYouFixedIt said:
Im no help. Dont listen to me. Try using fastboot to run a recovery. "fastboot boot recovery.img" from the bootloader. Maybe with that old bootloader you should be using an old recovery maybe.
I'm really starting to get frustrated... (understatement)
I've got a copy of the 4.4.2 OTA image (zip and recovery.img). Should I not be able to use ADB to copy the image to the device and then boot the recovery.img? I can get the tablet to respond to fastboot but I can't get it to be recognized by ADB.
I've never had issues with custom ROMs before. This time I'm wading into unfamiliar waters. I'm note even sure how the initial update failed. Is there a way for me to update the bootloader, then add a CWM recovery, then load the ROM?
Again sorry to have to ask but any help would greatly be appreciated.
Click to expand...
Click to collapse
Where did you get the full firmware update you tried to flash?
I can't find a recovery that is compatible with that old bootloader, so your best bet would be to update via Asus firmware.
What happens if you choose RCK in the bootloader menu? Is the stock recovery still working?
What's your SKU?
If the manual stock update doesn't work you may have to flash the system blob in fastboot, but answer above questions first and then we'll see.
If you're getting frustrated, stop and come back to it later. Don't do anything desperate! No reason for it yet.
Click to expand...
Click to collapse
kartman_canada said:
YayYouFixedIt said:
Im no help. Dont listen to me. Try using fastboot to run a recovery. "fastboot boot recovery.img" from the bootloader. Maybe with that old bootloader you should be using an old recovery maybe.
I'm really starting to get frustrated... (understatement)
I've got a copy of the 4.4.2 OTA image (zip and recovery.img). Should I not be able to use ADB to copy the image to the device and then boot the recovery.img? I can get the tablet to respond to fastboot but I can't get it to be recognized by ADB.
I've never had issues with custom ROMs before. This time I'm wading into unfamiliar waters. I'm note even sure how the initial update failed. Is there a way for me to update the bootloader, then add a CWM recovery, then load the ROM?
Again sorry to have to ask but any help would greatly be appreciated.
Click to expand...
Click to collapse
https://www.dropbox.com/s/il2m4rtxlmzjfz9/recovery.img
download this recovery(which is an older one compatable with that bootloader and try fastboot boot recovery.img from your older bootloader.
It should work. If you can determine that it works and all your partitions are intact. The command is" fastboot flash recovery recovery.img" I would think if you can simply get this one to boot it will be ok to flash and you should be able to flash whatever you want. Namely you will want to flash the new bootloader and recovery from the flashable zip that sbdags provides from his optimized asus stock.
If you have to adb sideload a rom from within the recovery. Then download just use the cm11 rom for now because the asus stock is over a gig and and might not sideload. the asus stock sbdags provides in this forum.
Otherwise you might be able to flash things from the microsd card.
Than if you decide to go the cm11 route. just download the asus stock from this forum from inside the rom. Be careful.
Click to expand...
Click to collapse
Fixed!
YayYouFixedIt said:
kartman_canada said:
download this recovery(which is an older one compatable with that bootloader and try fastboot boot recovery.img from your older bootloader.
It should work. If you can determine that it works and all your partitions are intact. The command is" fastboot flash recovery recovery.img" I would think if you can simply get this one to boot it will be ok to flash and you should be able to flash whatever you want. Namely you will want to flash the new bootloader and recovery from the flashable zip that sbdags provides from his optimized asus stock.
If you have to adb sideload a rom from within the recovery. Then download just use the cm11 rom for now because the asus stock is over a gig and and might not sideload. the asus stock sbdags provides in this forum.
Otherwise you might be able to flash things from the microsd card.
Than if you decide to go the cm11 route. just download the asus stock from this forum from inside the rom. Be careful.
Click to expand...
Click to collapse
Managed to fastboot to the older recovery.img. As per instructions, I then flashed the latest bootloader and recovery from sbdags. I'm now good to go with whatever ROM I want. Many thanx! I'd still like to know how the upgrade to the latest Asus update screwed up. I wasn't watching it after setting the update in motion so it's a mystery. All I know is that the unit was plugged in so it wouldn't run out of juice and when I came back to check it, it wouldn't boot to Android, I couldn't get to recovery, and it would just keep rebooting in a loop.
Lucky for me it was unlocked and I had fastboot access to the (albeit out-of-date) bootloader.
All good now. Cheers.
Click to expand...
Click to collapse
kartman_canada said:
YayYouFixedIt said:
Managed to fastboot to the older recovery.img. As per instructions, I then flashed the latest bootloader and recovery from sbdags. I'm now good to go with whatever ROM I want. Many thanx! I'd still like to know how the upgrade to the latest Asus update screwed up. I wasn't watching it after setting the update in motion so it's a mystery. All I know is that the unit was plugged in so it wouldn't run out of juice and when I came back to check it, it wouldn't boot to Android, I couldn't get to recovery, and it would just keep rebooting in a loop.
Lucky for me it was unlocked and I had fastboot access to the (albeit out-of-date) bootloader.
All good now. Cheers.
Click to expand...
Click to collapse
Good to hear. For the Asus updates you just put them in /sdcard and reboot dont you? Its fairly automatic wasnt it? Then unlock after being updated? What went wrong in your case, Hard for me to say i guess because I and others unlocked at or before 4.3.
Click to expand...
Click to collapse
My apologies if this has already been posted. I've been looking all morning but haven't seen anyone with the same issue.
Unlock bootloader: no problem.
Flash TWRP: I downloaded from http://teamw.in/project/twrp2/275, and I got an error about partition size mismatch, but that's ok, right?
But when I try to enter recovery, all I get is the warning screen that my phone is unlocked. The drivers are certainly installed correctly, and fastboot is working fine. I just can't get into recovery to flash a ROM!
Restoring to 4.4.4 stock worked like a charm.
http://forum.xda-developers.com/mot...dows-tool-moto-g-2014-xt1064-restore-t2957167
I've re-enabled USB debugging. Do I dare try to flash a custom recovery again?
Pandae said:
Do I dare try to flash a custom recovery again?
Click to expand...
Click to collapse
You can use Flashify to make a backup of your current recovery and to flash TWRP.img. should work like a charm.
But Flashify requires root, I see? The reason I'm trying to flash a custom recovery is so I can root in the first place.
Pandae said:
But Flashify requires root, I see? The reason I'm trying to flash a custom recovery is so I can root in the first place.
Click to expand...
Click to collapse
You're right. Latest motorola driver and [TOOL]Minimal ADB and Fastboot will do the trick.
Sorry, I should have clarified that when flashing TWRP, I've already been using fastboot.exe from a command line (and administrator level), with the drivers correctly installed. That's how I was able to unlock in the first place.
I did try it with the version of Fastboot you linked to (what I have works peachy for my Nexus 7), still the same thing. I can't boot into recovery and only get stuck at the Motorola unlocked warning.
Pandae said:
I can't boot into recovery and only get stuck at the Motorola unlocked warning.
Click to expand...
Click to collapse
Oh. Sorry. Can you post the output (terminal & device) of
Code:
fastboot devices
fastboot flash recovery NAME_OF_RECOVERY.img
I'd done "fastboot devices" already to verify, and it returns the serial number, though as I said it's clearly working since I was able to unlock as well as flash recovery. I'm flashing "TWRP2801-titan-motog-2014.img" that I downloaded from the TWRP site, and fastboot gives the standard messages about size and success (and my phone gives the size mismatch error).
It's so strange to me. I've flashed a custom recovery dozens of times on both generations of my Nexus 7s, but I've never seen this.
Pandae said:
It's so strange to me.
Click to expand...
Click to collapse
Yeah......have to meditate about that problem....... is your battery low? Fastboot mode of the device gives me all sorts of problems if it detects low battery
I had been using fastboot at 100% (literally finished a full charge) and 84%, but thanks for the continued attempts at explanation.
Oh, did you check the md5 checksum of your download?
Ah, good thought! I rarely do, but I did just now...and they're the same. It's crazy, isn't it?
Pandae said:
Ah, good thought! I rarely do, but I did just now...and they're the same. It's crazy, isn't it?
Click to expand...
Click to collapse
If you are willing to risk it, try a fresh download and try again. I've flashed TWRP more than 20 times by now and never recieved an error whatsoever. It basically the easiest thing to do.
Incase you are stuck again, don't reflash the entire stock rom. Just flash the recovery.img from the stock rom files.
OR
Try this:
HOW TO ROOT MOTO G 2014 with Temporary Custom Recovery
Cheers
I've flashed a custom recovery many a time and have helped people through it, though on Nexus 7s.
Now shall I compound the mystery? I didn't think yet to use ADB to make my phone reboot to recovery. I had assumed recovery wasn't working. So here we go, after booting into Android:
adb reboot devices: my phone's there.
adb reboot recovery: TWRP's working?! And now root is complete!
It doesn't make sense to me why I can't get into recovery from the bootloader, but I can get into it with the simple ADB command. But I appreciate all the help, thanks!
Pandae said:
It doesn't make sense to me why I can't get into recovery from the bootloader
Click to expand...
Click to collapse
A little workaround:
Install Android Terminal Emulator
Add "Term shortcut" widget.
In "Arguments" enter
Code:
su -c reboot recovery
So i tried flashing the factory image onto my rooted nexus 6 device manually , but while doing so i couldnt get the system.img to load as it kept saying "unable to allocate byte 1176........bytes" something like that. So i read about this error on some forums and they suggested to erase system , cache , userdata and then try flashing the stock image. Upon doing so it gave the same error and unable to load sys.img file.
Now , im stuck at the splash screen with stock recovery and bootloader working fine.
Im aware that my phone is bricked please advise what can i do to fix this issue.???
Thank you
I take it you placed the system.img in the platform-tools folder an you typed fastboot flash system system.img in cmd.
Sent from my Nexus 10 using XDA Free mobile app
faraz90 said:
So i tried flashing the factory image onto my rooted nexus 6 device manually , but while doing so i couldnt get the system.img to load as it kept saying "unable to allocate byte 1176........bytes" something like that. So i read about this error on some forums and they suggested to erase system , cache , userdata and then try flashing the stock image. Upon doing so it gave the same error and unable to load sys.img file.
Now , im stuck at the splash screen with stock recovery and bootloader working fine.
Im aware that my phone is bricked please advise what can i do to fix this issue.???
Thank you
Click to expand...
Click to collapse
First thing, do NOT lock your bootloader. Are you trying to use flash all? If so, do not. Flash the images separately.
Evolution_Tech said:
First thing, do NOT lock your bootloader. Are you trying to use flash all? If so, do not. Flash the images separately.
Click to expand...
Click to collapse
gee2012 said:
I take it you placed the system.img in the platform-tools folder an you typed fastboot flash system system.img in cmd.
Sent from my Nexus 10 using XDA Free mobile app
Click to expand...
Click to collapse
Thanks for the quick reply.
Yes i did place is it under the platform tools folder and tried flashing separately as per the instructions given to flash manually.
I know that i should not lock the bootloader.
Im currently trying to flash using the toolkit "flash stock + unroot" and chose the current status "Softbricked/ bootloop in the bootloader mode.
Is this the right option or should i stop it ?
Thanks again for assistance.
faraz90 said:
Thanks for the quick reply.
Yes i did place is it under the platform tools folder and tried flashing separately as per the instructions given to flash manually.
I know that i should not lock the bootloader.
Im currently trying to flash using the toolkit "flash stock + unroot" and chose the current status "Softbricked/ bootloop in the bootloader mode.
Is this the right option or should i stop it ?
Thanks again for assistance.
Click to expand...
Click to collapse
the right option would be to flash the factory image the right way, via fastboot, and while in your bootloader.
simms22 said:
the right option would be to flash the factory image the right way, via fastboot, and while in your bootloader.
Click to expand...
Click to collapse
you mean it flashing it manually by placing the factory image in the platform tools folder ?
I tried that multiple times but it gave me the "could not allocate 721539744 bytes error: cannot load 'system.img" error :/
faraz90 said:
you mean it flashing it manually by placing the factory image in the platform tools folder ?
I tried that multiple times but it gave me the "could not allocate 721539744 bytes error: cannot load 'system.img" error :/
Click to expand...
Click to collapse
If your Android SDK is more than 6 months old, you may need to update it. Google updated fastboot to allow flashing these very large files.
faraz90 said:
you mean it flashing it manually by placing the factory image in the platform tools folder ?
Click to expand...
Click to collapse
No, by using fastboot commands.. The location of the images you flash is irrelevant.
faraz90 said:
I tried that multiple times but it gave me the "could not allocate 721539744 bytes error: cannot load 'system.img" error :/
Click to expand...
Click to collapse
Either there is a problem with the system.img (redownload) or there is a problem with the flash memory on your device.
You could flash a custom recovery and use that to flash a zipped ROM to see.if that makes any difference.
faraz90 said:
you mean it flashing it manually by placing the factory image in the platform tools folder ?
I tried that multiple times but it gave me the "could not allocate 721539744 bytes error: cannot load 'system.img" error :/
Click to expand...
Click to collapse
if you are using the flash-all, dont, as that gives many people problems as of lately. instead, you want to unzip and flash each partition separately.
Here is a detailled guide http://forum.xda-developers.com/google-nexus-5/general/tutorial-how-to-flash-factory-image-t2513701 for how to flash a image, use method 2. Its the same for the N6 as for the N5.
simms22 said:
if you are using the flash-all, dont, as that gives many people problems as of lately. instead, you want to unzip and flash each partition separately.
Click to expand...
Click to collapse
gee2012 said:
Here is a detailled guide http://forum.xda-developers.com/google-nexus-5/general/tutorial-how-to-flash-factory-image-t2513701 for how to flash a image, use method 2. Its the same for the N6 as for the N5.
Click to expand...
Click to collapse
I think he has already used fast boot to flash the system.img
rootSU said:
I think he has already used fast boot to flash the system.img
Click to expand...
Click to collapse
Maybe he used the wrong command like: fastboot flash system.img or something similar. If the img`s are in the correct folder and the commands are good it shouldn`t be a problem
I agree with @rootSU flash TWRP, flash factory zip from here:
http://forum.xda-developers.com/showthread.php?t=3066052
gee2012 said:
Maybe he used the wrong command like: fastboot flash system.img or something similar. If the img`s are in the correct folder and the commands are good it shouldn`t be a problem
Click to expand...
Click to collapse
Nope. He used the correct commands. There is no correct folder.
Evolution_Tech said:
I agree with @rootSU flash TWRP, flash factory zip from here:
http://forum.xda-developers.com/showthread.php?t=3066052
Click to expand...
Click to collapse
thanks a bunch. I have a few questions which could be noobish yet i would like to know.
- how can i flash the custom recovery when i cant place the files under the internal storage as my phone doesn't show when i connect it to the PC ?
- just like that im downloading the zip file but i would like to first access the internal storage to place the files under the root or is there a way around to do this ?
Thanks
faraz90 said:
thanks a bunch. I have a few questions which could be noobish yet i would like to know.
- how can i flash the custom recovery when i cant place the files under the internal storage as my phone doesn't show when i connect it to the PC ?
- just like that im downloading the zip file but i would like to first access the internal storage to place the files under the root or is there a way around to do this ?
Thanks
Click to expand...
Click to collapse
Flash TWRP, reboot to bootloader, select recovery mode, enter TWRP, mount MTP.
Evolution_Tech said:
Flash TWRP, reboot to bootloader, select recovery mode, enter TWRP, mount MTP.
Click to expand...
Click to collapse
You Sir, are a lifesaver. It worked!
Although for the sake of better understanding why do you think I wasn't able to flash the system image manually via fastboot ? having tried multiple times with correct fastboot commands :S
Thanks all for the help!
faraz90 said:
You Sir, are a lifesaver. It worked!
Although for the sake of better understanding why do you think I wasn't able to flash the system image manually via fastboot ? having tried multiple times with correct fastboot commands :S
Thanks all for the help!
Click to expand...
Click to collapse
*ahem*
rootSU said:
*ahem*
Click to expand...
Click to collapse
haha ofcourse thanks alot to you for suggesting that idea
faraz90 said:
Although for the sake of better understanding why do you think I wasn't able to flash the system image manually via fastboot ? having tried multiple times with correct fastboot commands :S
!
Click to expand...
Click to collapse
Possibly because your Android SDK tools are out of date(specifically fastboot).
Hi everyone.
I was trying to flash Nitrogen OS. First I flashed the latest firmware, then the actual rom and then GAPPS. After that my mobile got stuck in Oneplus logo without being able to go into recovery mode.
I tried using fastboot to flash the files in this thread(https://forum.xda-developers.com/oneplus-3t/how-to/unbrick-unbrick-tutorial-oneplus-3t-t3515306) which worked once, but even after that I can't surpass the logo screen.
I've been trying to look for information but I can't find anything.
To clarify:
- I already tried erasing userdata and cache from fastboot
-I already tried flashing recovery images from twrp, stock and bluspark
Thanks in advance guys.
Pavononer23 said:
Hi everyone.
I was trying to flash Nitrogen OS. First I flashed the latest firmware, then the actual rom and then GAPPS. After that my mobile got stuck in Oneplus logo without being able to go into recovery mode.
I tried using fastboot to flash the files in this thread(https://forum.xda-developers.com/oneplus-3t/how-to/unbrick-unbrick-tutorial-oneplus-3t-t3515306) which worked once, but even after that I can't surpass the logo screen.
I've been trying to look for information but I can't find anything.
Thanks in advance guys.
Click to expand...
Click to collapse
Which TWRP are you using? Which firmware are you flashing? You can't access recovery at all? I've run into plenty of bricks like this and I'm usually able to get back to recovery by forcing the device off (vol up + power hold) and rebooting back to recovery. and if that doesn't work I can at least get to the bootloader and re-flash a recovery file.
rykanator said:
Which TWRP are you using? Which firmware are you flashing? You can't access recovery at all? I've run into plenty of bricks like this and I'm usually able to get back to recovery by forcing the device off (vol up + power hold) and rebooting back to recovery. and if that doesn't work I can at least get to the bootloader and re-flash a recovery file.
Click to expand...
Click to collapse
I was using last bluspark recovery. I was flashing OB21 when everything happened.
There is no way I can access to recovery. I tried reflashing the stock recovery from that unbricking thread with all the other things through fastboot and I can't boot into recovery at all. It is the first time I face this error so I am lost.
Pavononer23 said:
I was using last bluspark recovery. I was flashing OB21 when everything happened.
There is no way I can access to recovery. I tried reflashing the stock recovery from that unbricking thread with all the other things through fastboot and I can't boot into recovery at all. It is the first time I face this error so I am lost.
Click to expand...
Click to collapse
can you boot into the bootloader/fastboot?
rykanator said:
can you boot into the bootloader/fastboot?
Click to expand...
Click to collapse
Yes I can
Pavononer23 said:
Yes I can
Click to expand...
Click to collapse
okay, well what I would do is boot into the bootloader, and then reflash the blu_spark recovery via adb so you can boot into it. then wipe everything and restart. but this time I would try the OB 20 firmware and not the 21. when I was on NOS I used that one and it worked just fine. I'm not sure if it made a difference, but I flashed the firmware both right before and right after flashing NOS
rykanator said:
okay, well what I would do is boot into the bootloader, and then reflash the blu_spark recovery via adb so you can boot into it. then wipe everything and restart. but this time I would try the OB 20 firmware and not the 21. when I was on NOS I used that one and it worked just fine. I'm not sure if it made a difference, but I flashed the firmware both right before and right after flashing NOS
Click to expand...
Click to collapse
It doesnt recognize my device through adb and I don't know why. If that worked I would have tried to sideload some firmware, but when I do adb devices it doesn't appear
Pavononer23 said:
It doesnt recognize my device through adb and I don't know why. If that worked I would have tried to sideload some firmware, but when I do adb devices it doesn't appear
Click to expand...
Click to collapse
idk if it'll recognize as an adb device if it's in the bootloader. maybe try fastboot devices? sorry, I'm just spitballin here
rykanator said:
idk if it'll recognize as an adb device if it's in the bootloader. maybe try fastboot devices? sorry, I'm just spitballin here
Click to expand...
Click to collapse
Somehow fastboot devices does send me that my device is there but adb devices no, I will try looking into that to see if that works. Thanks for the help anyway
Pavononer23 said:
Somehow fastboot devices does send me that my device is there but adb devices no, I will try looking into that to see if that works. Thanks for the help anyway
Click to expand...
Click to collapse
yeah! try fastboot flash recovery "recovery file name".img
make sure that recovery img file is in the platform-tools file (or wherever your adb files are) and see if that works!
rykanator said:
yeah! try fastboot flash recovery "recovery file name".img
make sure that recovery img file is in the platform-tools file (or wherever your adb files are) and see if that works!
Click to expand...
Click to collapse
It is not working, I think I lost my Oneplus 3t...
Pavononer23 said:
It is not working, I think I lost my Oneplus 3t...
Click to expand...
Click to collapse
I mean idk if you wanna do this, but you could always try to "format userdata", then flash the stock recovery, and then sideload OOS. but you would lose all of your data in your internal storage, and it's still not a guarantee. there are some posts about doing a full wipe and starting from scratch. I'd look into those. Best of luck reviving your OP3T
Pavononer23 said:
It is not working, I think I lost my Oneplus 3t...
Click to expand...
Click to collapse
just a tip, try posting the output instead of "it's not working",
so the devs here might be able to analyze the problem..
nicknacknuke said:
just a tip, try posting the output instead of "it's not working",
so the devs here might be able to analyze the problem..
Click to expand...
Click to collapse
I already post a lot of information on the first post:
Mobile not passing the first time Oneplus logo appears.
Only fastboot is working, not adb, not recovery.
I already tried flashing other recoveries and the stock one->Can't pass Oneplus logo anyway
Tried formatting userdata through fastboot and flashing the .img files from my first post->Not working
Then just do the Qualcomm restore and unlock, boot to fastboot and flash the latest TWRP. Then boot into TWRP and format cache partitions, system and data and then adb sideload using this option under TWRP advanced to flash firmware zip, NitrogenOS zip and then 8.1 Gapps and try booting to see if same thing happens again. You are using the NitrogenOS stock kernel and not some other?
pitrus- said:
Then just do the Qualcomm restore and unlock, boot to fastboot and flash the latest TWRP. Then boot into TWRP and format cache partitions, system and data and then adb sideload using this option under TWRP advanced to flash firmware zip, NitrogenOS zip and then 8.1 Gapps and try booting to see if same thing happens again. You are using the NitrogenOS stock kernel and not some other?
Click to expand...
Click to collapse
What do you mean by the Qualcomm restor and unlock? I already tried the flashing of latest TWRP and it did not work.
I was coming from Validus last beta but did a previous factory reset and that stuff.
Thank you for the answer
Pavononer23 said:
What do you mean by the Qualcomm restor and unlock? I already tried the flashing of latest TWRP and it did not work.
I was coming from Validus last beta but did a previous factory reset and that stuff.
Thank you for the answer
Click to expand...
Click to collapse
What he meant is probably unbrick tool - https://forum.xda-developers.com/oneplus-3t/how-to/unbrick-unbrick-tutorial-oneplus-3t-t3515306
Try flashing official firmware with it and then try again by flashing TWRP and flashing Nitrogen.
przemcio510 said:
What he meant is probably unbrick tool - https://forum.xda-developers.com/oneplus-3t/how-to/unbrick-unbrick-tutorial-oneplus-3t-t3515306
Try flashing official firmware with it and then try again by flashing TWRP and flashing Nitrogen.
Click to expand...
Click to collapse
I can't install the drivers:
-First, stupid Windows policy saying that its driver is the best one available.
-Second, choosing from a disk to avoid one saying that the driver is not a x64 one.
Pavononer23 said:
I already post a lot of information on the first post:
Mobile not passing the first time Oneplus logo appears.
Only fastboot is working, not adb, not recovery.
I already tried flashing other recoveries and the stock one->Can't pass Oneplus logo anyway
Tried formatting userdata through fastboot and flashing the .img files from my first post->Not working
Click to expand...
Click to collapse
None of that answer what he actually asked, which is: what was the output (error message, result, etc.) when you tried to flash TWRP?
Did it flash successfully, but still can't boot to TWRP? Or else, what was the exact error message?
In general, when asking for help and giving status, be specific as possible, and give as many details as possible. Saying you "tried xxx" or "it did not work" is not specific enough.
Seems silly, but I've seen a lot of times where it's as simple as the user not using the correct command or entering the right file name.
redpoint73 said:
None of that answer what he actually asked, which is: what was the output (error message, result, etc.) when you tried to flash TWRP?
Did it flash successfully, but still can't boot to TWRP? Or else, what was the exact error message?
In general, when asking for help and giving status, be specific as possible, and give as many details as possible. Saying you "tried xxx" or "it did not work" is not specific enough.
Seems silly, but I've seen a lot of times where it's as simple as the user not using the correct command or entering the right file name.
Click to expand...
Click to collapse
There were no errors when flashing TWRP. When I tried rebooting using fastboot(fastboot boot recovery.img) it got stuck in the message saying booting up... and the only thing that changed was that my phone left the bootloader screen to a screen with the Oneplus logo and a fastboot mode message under it.
The command I used was fastboot flash recovery recovery.img(Name of the actual recovery file)