So, I got my new phone today, and immediately rooted it. This was the first time I'd ever done something like this to any phone, so I was really in the dark on the whole matter. I managed to root it successfully, and proceeded to install Cyanogen, which took ages to install, and I remembered that I'd forgotten to wipe the phone, so I restarted, went into recovery mode and ACCIDENTALLY WIPED ALL OF MY FILES with TWRP. Once I realised what I'd done, I panicked, restarting the phone, which landed me, stuck, on the 'WARNING, BOOTLOADER UNLOCKED' screen. I panicked again, and went to this thread:
http://forum.xda-developers.com/showthread.php?t=2542219
And tried to follow everything, but I didn't really understand what I was doing and was in a state of panic. I can go into details of what I did if needs be, but long story short, whenever I boot up my phone I get the bootloader unlocked screen and do not boot into the OS. I cannot also access the Recovery window, and it has the android mascot lying on its back with a red triangle.
All I want to do is fix my phone, if anyone could guide me through this, I'd be forever grateful.
tl;dr: F**ked up, possible bricked my phone and don't know what to do.
Many thanks for any response.
Phaydze said:
So, I got my new phone today, and immediately rooted it. This was the first time I'd ever done something like this to any phone, so I was really in the dark on the whole matter. I managed to root it successfully, and proceeded to install Cyanogen, which took ages to install, and I remembered that I'd forgotten to wipe the phone, so I restarted, went into recovery mode and ACCIDENTALLY WIPED ALL OF MY FILES with TWRP. Once I realised what I'd done, I panicked, restarting the phone, which landed me, stuck, on the 'WARNING, BOOTLOADER UNLOCKED' screen. I panicked again, and went to this thread:
http://forum.xda-developers.com/showthread.php?t=2542219
And tried to follow everything, but I didn't really understand what I was doing and was in a state of panic. I can go into details of what I did if needs be, but long story short, whenever I boot up my phone I get the bootloader unlocked screen and do not boot into the OS. I cannot also access the Recovery window, and it has the android mascot lying on its back with a red triangle.
All I want to do is fix my phone, if anyone could guide me through this, I'd be forever grateful.
tl;dr: F**ked up, possible bricked my phone and don't know what to do.
Many thanks for any response.
Click to expand...
Click to collapse
Recovery has been deleted by u accidentally
Go to bootlander (power + volume down) try to install TWRP recovery again through adb n install cm11 directly through adb sideload
Phaydze said:
So, I got my new phone today, and immediately rooted it. This was the first time I'd ever done something like this to any phone, so I was really in the dark on the whole matter. I managed to root it successfully, and proceeded to install Cyanogen, which took ages to install, and I remembered that I'd forgotten to wipe the phone, so I restarted, went into recovery mode and ACCIDENTALLY WIPED ALL OF MY FILES with TWRP. Once I realised what I'd done, I panicked, restarting the phone, which landed me, stuck, on the 'WARNING, BOOTLOADER UNLOCKED' screen. I panicked again, and went to this thread:
http://forum.xda-developers.com/showthread.php?t=2542219
And tried to follow everything, but I didn't really understand what I was doing and was in a state of panic. I can go into details of what I did if needs be, but long story short, whenever I boot up my phone I get the bootloader unlocked screen and do not boot into the OS. I cannot also access the Recovery window, and it has the android mascot lying on its back with a red triangle.
All I want to do is fix my phone, if anyone could guide me through this, I'd be forever grateful.
tl;dr: F**ked up, possible bricked my phone and don't know what to do.
Many thanks for any response.
Click to expand...
Click to collapse
Since you managed to root, im assuming you have ADB and Fastboot on your PC?
Download a recovery.img file from XDA. I recommend this one ----> http://forum.xda-developers.com/showthread.php?t=2639583
Place the recovery.img file in the same file folder/location as your fastboot and ADB files.
Open a command window from the same location as the adb/fastboot/recover.img files.
In the command window type "fastboot device" and make sure some type of serial number shows up in the window.
Once you know your device is connected via fastboot, type: "fastboot flash recovery __________.img"
Where the ______.img is, you would put the name of the recovery.img file.
For example, the file that gets downloaded if you download philz touch (the link i gave you), is called "recovery.img"
So in fastboot you would type "fastboot flash recovery recovery.img"
Once thats been flashed, you should be able to boot into recovery, sideload a rom, and flash it to your device.
Good Luck!
Phaydze said:
So, I got my new phone today, and immediately rooted it. This was the first time I'd ever done something like this to any phone, so I was really in the dark on the whole matter. I managed to root it successfully, and proceeded to install Cyanogen, which took ages to install, and I remembered that I'd forgotten to wipe the phone, so I restarted, went into recovery mode and ACCIDENTALLY WIPED ALL OF MY FILES with TWRP. Once I realised what I'd done, I panicked, restarting the phone, which landed me, stuck, on the 'WARNING, BOOTLOADER UNLOCKED' screen. I panicked again, and went to this thread:
http://forum.xda-developers.com/showthread.php?t=2542219
And tried to follow everything, but I didn't really understand what I was doing and was in a state of panic. I can go into details of what I did if needs be, but long story short, whenever I boot up my phone I get the bootloader unlocked screen and do not boot into the OS. I cannot also access the Recovery window, and it has the android mascot lying on its back with a red triangle.
All I want to do is fix my phone, if anyone could guide me through this, I'd be forever grateful.
tl;dr: F**ked up, possible bricked my phone and don't kn.
go to this link for any response.
http://forum.xda-developers.com/showthread.php?t=2744058
Click to expand...
Click to collapse
Related
Hi, hope Im not double posting or anything, but I havent found a solution to my problems yet.
I recently purchased Nexus S 4G, thinking it was working, but it is not. It powers up, but doesn't get to the main system. It sticks on the Nexus colorful flashing things and wont get past that. Sometimes it sticks on the Google logo. Is there anything I can check, or somehow restore it or something to get it to boot up? I can also get to the fast boot menu, but when I get there, and try recovery, it just gives me the sad dead Android with his tummy open with a red triangle.
aaps59 said:
Hi, hope Im not double posting or anything, but I havent found a solution to my problems yet.
I recently purchased Nexus S 4G, thinking it was working, but it is not. It powers up, but doesn't get to the main system. It sticks on the Nexus colorful flashing things and wont get past that. Sometimes it sticks on the Google logo. Is there anything I can check, or somehow restore it or something to get it to boot up? I can also get to the fast boot menu, but when I get there, and try recovery, it just gives me the sad dead Android with his tummy open with a red triangle.
Click to expand...
Click to collapse
If you can get into fastboot just flash CWM http://www.clockworkmod.com/rommanager and SU http://androidsu.com/superuser/
Put SU on phone SD card
Reboot phone into bootloader mode
Open a command prompt and go to the folder in where CWM is
Now execute this fastboot command to flash the CWM recovery. Change the filename to the file you have downloaded.
fastboot flash recovery recovery-clockwork-touch-6.0.1.0-crespo4g.img
Now go to recovery.
There, using the options, navigate to the install the superuser zip file
Reboot.
So guys, i've done it. I bring my first device.
Yesterday i tried to downgrade via fastboot with this recovery images https://developer.nvidia.com/gameworksdownload (yes is choose the right ones)
flash boot, check
flash recovery, check
flash system, failes (insufficient memory)
erase sytem, check
flash system, failed (insufficient memory)
flash twrp, check, but no usb mouse so
flash cwm, check
factory reset, check
rom.zip and gapps on sd card, check
reboot, boot into bootloader, no chance
It boots everytime normal, so i cant enter the recovery.
Connect it to charger, check
charging led lights up, check
Go sleeping, check
doenst boot into bootloader :/
Back to charger
Now I wanted to try it again and i wont even boot.
Anyone has an Idea? Or is it really bricked?
Can you still see the device listed using fast boot?
No, because I can't enter the bootloader or the recovery. But it boots again
...
The same thing just happened to me. Unfortunately, I am still trying to figure it out. I flashed a "stock" recovery that I had found in order to be able to take the OTAs. Now when I boot, I just stay stuck on the NVIDIA splash screen.....been there for hours.
rafaelvelasquez2 said:
The same thing just happened to me. Unfortunately, I am still trying to figure it out. I flashed a "stock" recovery that I had found in order to be able to take the OTAs. Now when I boot, I just stay stuck on the NVIDIA splash screen.....been there for hours.
Click to expand...
Click to collapse
Same here.....
Mine is working again. Booting in the bootloader is a little bit tricky.
Have you tried to flash all? Boot.img, recovery.img and system.img?
...
I had the same issue. But after trying to get into the bootloader using POWER + VOLUME DOWN for about 15 minutes it finally went to the bootloader and I was able to re-flash it. I have a feeling it's the cludgy power button.
You do not need to flash the stock recovery to take the ota. I have taken 2 otas now on custom recovery without any issue and without loosing root. Just an FYI.
Sent from my SHIELD Tablet using XDA Free mobile app
I just did a factory reset under lollipop, locked boot-loader rooted and it rebooted to the green android screen then dropped into CWM and asked to fix root. I said no, then it went to the nvidia boot logo and it is stuck. Any suggestions? Thanks.
Edit: nevermind, I just powered it off after about 20 minuets and it hung again. When I plugged it into my pc, it finally poped into the setup/welcome screen. Pretty weird. Heart attack averted
I have a nexus 5 16 GB and i downloaded the recent software update android 6.0.1 and then I decided to root and I used 'Nexus root toolkit v2.06' and first unlocked the bootloader and then rooted. Everything worked fine but after the process was complete it was rebooting and the booting animation went on and on for many hours and the device did not root. I really don't know what's going on. My purpose is to install a custom rom: cyanogenmod 12. Now what should I do ???? PLEASE HELP. When i try to enter recovery mode it shows a picture of the android mascot with opened back and exclamation and cannot enter command as well. and after some time the booting animation begins and goes on and on...
please help...
nexus_5_ said:
I have a nexus 5 16 GB and i downloaded the recent software update android 6.0.1 and then I decided to root and I used 'Nexus root toolkit v2.06' and first unlocked the bootloader and then rooted. Everything worked fine but after the process was complete it was rebooting and the booting animation went on and on for many hours and the device did not root. I really don't know what's going on. My purpose is to install a custom rom: cyanogenmod 12. Now what should I do ???? PLEASE HELP. When i try to enter recovery mode it shows a picture of the android mascot with opened back and exclamation and cannot enter command as well. and after some time the booting animation begins and goes on and on...
please help...
Click to expand...
Click to collapse
Unless something has changed, version 6. requires that you flash a special kernel before you can root your phone otherwise you are as you are now, stuck in a boot loop. You should probably download the factory image from Google, and then flash the system image to get rid of what you have done.. Perhaps then your phone will start normally
funnel71 said:
Unless something has changed, version 6. requires that you flash a special kernel before you can root your phone otherwise you are as you are now, stuck in a boot loop. You should probably download the factory image from Google, and then flash the system image to get rid of what you have done.. Perhaps then your phone will start normally
Click to expand...
Click to collapse
Thank you very much for the reply, I really do have no idea as to how to flash the factory image because i am very new in this area. Could you please recommend software and which factory image i should download, please ?? thanks very much.
:good:
funnel71 said:
Unless something has changed, version 6. requires that you flash a special kernel before you can root your phone otherwise you are as you are now, stuck in a boot loop. You should probably download the factory image from Google, and then flash the system image to get rid of what you have done.. Perhaps then your phone will start normally
Click to expand...
Click to collapse
Also, you mentioned a 'special kernel' what does that mean. All i want to do to my device is install cyanogenmod 12 and for that i believe it needs to be rooted, so i am really confused. What should I do know
I'm having this same problem, and unfortunately, when I start the phone on fastboot, I can not access the recovery mode in order to upload a factory image of nexus 5.
I used the new tool available her for quick flash, and now, I don't have a phone.
First, don't panic. Your phone is still very easy to recover. Unfortunately I can't get you a complete walkthrough here (for now at least), so I'll give you the main idea and you'll have to do your homework (as maybe you should have done before).
1. You need to get fastboot working on your computer. It's included in the Android sdk package, but there might be some easier way to get it. Google it. You might need drivers for your pc too. Google it as well.
2. Then you need to get into fastboot mode on your phone. To do it, hold down power button AND volume down button until it gets into fastboot mode. You will see an android on his back with the cover open. At this point, connect your phone to your pc, open a terminal on your pc and type "fastboot devices" without the quotes "". It should find your phone if fastboot is working. If it doesn't work go back to step 1.
3. Download TWRP recovery on your pc and place the img file in the same folder as your fastboot executable (not mandatory but easier). It can be found here https://dl.twrp.me/hammerhead/
4. Always in fastboot mode, type "fastboot flash recovery twrp-2.8.7.1-hammerhead.img" assuming you downloaded that file, which you should have by the way. It should install fine. If you haven't placed the file in the same directory as your fastboot executable, you will need to provide the path to your img file as well.
5. Then use the volume rocker to switch between modes and choose reboot recovery.
6. You should now be in TWRP recovery. At this point, download a custom kernel (anyone found on xda for hammerhead should do) and push it to your phone. It should be fairly simple with TWRP. Then flash your new kernel using install. It should help you get your phone booting normally. Alternatively, you can download a custom ROM like cm12.1 and flash it altogether. It will install everything needed for your phone to boot up too. Beware if flashing a ROM though, I strongly advice you to do a factory reset before flashing it. You will find that option in the wipe menu.
Hope it helps, let me know if you need further assistance.
Yesterday, I have tried everything to have my computer to recognize the "fastboot" command, and I installed like 2 or 3 different programs for that. With my old Windows 7, I have been able to push a flashed image to fix this issue, using the fastboot command, but with Windows 10, it's always telling me it's not a valid command. I'll keep trying it, otherwise, i'll have to "resurrect" my old Windows XP computer.
Also, I noticed now that, while trying to install the fastboot, as per some files that I could download, but no file has been copied into my computer, not even if I run it as admin.
fixed. but no RECOVERY mode options....
Hi Guys,
Thank you very much for the help, I have finally recovered the phone and running android 6.0 MRA58N but it is not rooted. Now if you don't mind could you teach me how to root because i have checked lots of videos and tuts but none worked for me...
IMPORTANT:
when i am in recovery mode why cannot I access options even when i press volume up + power button and release them at the same time...????
Thanks in advance.
Just flash a custom recovery via fastboot. Just make sure your bootloader is unlocked. Can't link though.
hi guys i have used nexus 5 mobile with cyanogenmod 14.1 .It worked properly in 1 year. after that suddenly switched off and it not properly boot up .i try to switch on my mobile , first it show google with unlock logo properly and when it show cyanogenmod logo it stuck and again show google with unlock logo....i try recovery mode to wipe and flash the same rom ....the process is interrupt at middle stage and again show the google..i try lots of time . after few try that process finished completely without interrupt. then use my mobile 1 day same as i used first time root. after that same problem occur on my mobile ..so help me guys
@[email protected], possible power button problem?
Hello,
I apologise for any mistakes as this is my first time posting here.
I recently changed the screen on my brothers OnePlus One. The installation went really smoothly and the phone displayed on startup.:good:
But for some reason now when ever it it starts up you get a 1+ logo and then it has the android man with the red triangle. It then puts you into recovery . My brother has never tried custom roms on his opo, so he has the stock recovery. I try to install some zips using the ADB sideload method but it gets about 80% done and then says that the signature verification failed even on roms downloaded from the official site. I think the phone would work if I could get TWRP installed and install the rom through there, but I can't get into fastboot mode. My brother has never been in fastboot so I don't know if you had to enable it in the OS first or something like that. If I press reboot bootloader in advance settings in the recovery it just restarts the phone back into recovery. I am not sure whether to try some type of brick fix method however it isn't hard bricked because it turns on and in soft bricked you have to use fastboot for every method that I've seen.
Any help would be brilliant.
Thanks!
So over the past day I had rooted my oneplus 7 pro and all was going well until I decided to delete the netflix stock application. Then I restarted my phone from holding the power button and pressing restart and then I booted into fastboot. Everytime I pressed start it would send me back to fastboot but I was able go to twrp recovery. Stupidly, I wiped the whole phone thinking I had no other options. Then after that, I found a setting in advanced that allowed me to leave recovery mode I think? Whatever it was, I was booted back into the oneplus start screen and reset up my phone. Then I tried to re-root my phone and couldn't get it to work because it said the magisk zip file was corrupt. Then I just decided to give up and go back to stock.
Little did I no, you are NOT supposed to relock the bootloader, because that is exactly what I did. After doing that, I got a message saying my phone was corrupt and I looked up quick solution and it said to press my volume buttons and power buttons. Now my phone won't even turn on. I am freaking out right now, knowing that my phone is probably bricked and I am going to have to pay probably a third of what I even paid for this phone to get it fixed. When I plug my phone into my pc the device is shown as "QUSB_BULK_CID:0404_SN:3BB285D7". If any of you guys can help, I'm all ears.
edit: I meant I locked oem/bootloader. Also, I got the phone to power on. It is in a bootloop where the oneplus logo shows up and then it gives me the message "Your device is corrupt. it can't be trusted and will not boot"
edit 2: After two hours, I finally fixed it. I downloaded the MSM tool and found the qualcomm drivers and after a few trial and errors, I finally got it to work
gotdiamonds99 said:
So over the past day I had rooted my oneplus 7 pro and all was going well until I decided to delete the netflix stock application. Then I restarted my phone from holding the power button and pressing restart and then I booted into fastboot. Everytime I pressed start it would send me back to fastboot but I was able go to twrp recovery. Stupidly, I wiped the whole phone thinking I had no other options. Then after that, I found a setting in advanced that allowed me to leave recovery mode I think? Whatever it was, I was booted back into the oneplus start screen and reset up my phone. Then I tried to re-root my phone and couldn't get it to work because it said the magisk zip file was corrupt. Then I just decided to give up and go back to stock.
Little did I no, you are NOT supposed to relock the bootloader, because that is exactly what I did. After doing that, I got a message saying my phone was corrupt and I looked up quick solution and it said to press my volume buttons and power buttons. Now my phone won't even turn on. I am freaking out right now, knowing that my phone is probably bricked and I am going to have to pay probably a third of what I even paid for this phone to get it fixed. When I plug my phone into my pc the device is shown as "QUSB_BULK_CID:0404_SN:3BB285D7". If any of you guys can help, I'm all ears.
edit: I meant I locked oem/bootloader. Also, I got the phone to power on. It is in a bootloop where the oneplus logo shows up and then it gives me the message "Your device is corrupt. it can't be trusted and will not boot"
edit 2: After two hours, I finally fixed it. I downloaded the MSM tool and found the qualcomm drivers and after a few trial and errors, I finally got it to work
Click to expand...
Click to collapse
U probably should have flashed stock firmware before relocking the bootloader
As long as you can boot into fastboot you should be good. Make sure you have correct drivers etc etc. Boot into fastboot and just boot into twrp, don't flash. Wipe data, system, vendor, dalv, cache. Recheck on what to delete and what order because it has to be the correct things and I might be mixed up off the top of my head, delete them in twrp. Then boot back into twrp after all that and reflash your custom rom. Take note if your ****s bricked you wont be able to install the zip via regular twrp swipe, you will have to use twrp sideload feature with adb and install from pc and install it that way. If that doesn't work at all just do a complete reflash of stock firmware via fastboot. Reflashing custom should work though I got mine out of a brick this way. As long as fastboots working you can get out of anything. Also Linux is 100x better than other OSs for this stuff.
cuNezzar said:
As long as you can boot into fastboot you should be good. Make sure you have correct drivers etc etc. Boot into fastboot and just boot into twrp, don't flash. Wipe data, system, vendor, dalv, cache. Recheck on what to delete and what order because it has to be the correct things and I might be mixed up off the top of my head, delete them in twrp. Then boot back into twrp after all that and reflash your custom rom. Take note if your ****s bricked you wont be able to install the zip via regular twrp swipe, you will have to use twrp sideload feature with adb and install from pc and install it that way. If that doesn't work at all just do a complete reflash of stock firmware via fastboot. Reflashing custom should work though I got mine out of a brick this way. As long as fastboots working you can get out of anything. Also Linux is 100x better than other OSs for this stuff.
Click to expand...
Click to collapse
OK here's the order. Boot into twrp, don't flash.
Wipe -> ADVANCED -- select system + vendor -> SWIPE TO WIPE
reboot bootloader
fastboot boot back into twrp
-- then --
Format data, Wipe cache & dalvik-cache
Flash ROM.
Then reboot system. Boom.
Remember you will most likely have to flash the ROM via sideload. As transferring will not work in a bricked phone.
cuNezzar said:
As long as you can boot into fastboot you should be good. Make sure you have correct drivers etc etc. Boot into fastboot and just boot into twrp, don't flash. Wipe data, system, vendor, dalv, cache. Recheck on what to delete and what order because it has to be the correct things and I might be mixed up off the top of my head, delete them in twrp. Then boot back into twrp after all that and reflash your custom rom. Take note if your ****s bricked you wont be able to install the zip via regular twrp swipe, you will have to use twrp sideload feature with adb and install from pc and install it that way. If that doesn't work at all just do a complete reflash of stock firmware via fastboot. Reflashing custom should work though I got mine out of a brick this way. As long as fastboots working you can get out of anything. Also Linux is 100x better than other OSs for this stuff.
Click to expand...
Click to collapse
I don't know if u realize this but he said that he relocked the bootloader after installing twrp and root
Austinredstoner said:
I don't know if u realize this but he said that he relocked the bootloader after installing twrp and root
Click to expand...
Click to collapse
Austinredstoner said:
I don't know if u realize this but he said that he relocked the bootloader after installing twrp and root
Click to expand...
Click to collapse
Damn forgot about that. Yeah In that case its most likely bricked to hell OP with no method of recovery as far as I know.