Related
I've got a nexus one with a broken power button and a corrupt OS. It rarely successfully manages to boot. Since this is the case, I'm not able to turn on USB debugging to follow some of the tutorials here..
My next try was fastboot.. I downloaded these two files:
recovery-clockwork-5.0.2.0-passion.img
update-cm-7.1.0-N1-signed.zip
But it seems like I wont be able to flash a recovery file if I have "s-on" displayed on my hboot or fastboot screen..
How do I gain "s-off"? And is it possible to flash a stock rom via fastboot?
And yes, my phone's got stock gingerbread 2.3.4 rom.
HBOOT 0.35.0017
MICROP 0b15
Touch panel SYNT0103
Radio 5.08.00.04
Please help me with this matter as I have been trying to accomplish this task for over three months now..
Read Nexus One wiki, section "root", and section "recovery".
You don't need S-OFF to flash anything, if you unlock your bootloader. This is Nexus.
Boot into fastboot, plug into your PC, open command prompt wherever you have the fastboot command in Windows, most likely in android sdk under platform-tools, run "fastboot oem unlock" from command prompt, your bootloader is now unlocked. Attempt to flash your recovery now."
Sent from my Nexus One using XDA App
troby86 said:
Boot into fastboot, plug into your PC, open command prompt wherever you have the fastboot command in Windows, most likely in android sdk under platform-tools, run "fastboot oem unlock" from command prompt, your bootloader is now unlocked. Attempt to flash your recovery now."
Sent from my Nexus One using XDA App
Click to expand...
Click to collapse
My phone's power button is broken so I'm not able to select the recovery option
Jack_R1 said:
Read Nexus One wiki, section "root", and section "recovery".
You don't need S-OFF to flash anything, if you unlock your bootloader. This is Nexus.
Click to expand...
Click to collapse
It's already unlocked, as there is a small open lock displayed at the bottom of the boot screen.. and fastboot displayed it as already unlocked as well.. still.. i need a way to go to recovery without the power button
If you're in the bootloader - "fastboot reboot recovery".
If you're in the OS or while the OS is booting and ADB daemon is already running - "adb reboot recovery".
Jack_R1 said:
If you're in the bootloader - "fastboot reboot recovery".
If you're in the OS or while the OS is booting and ADB daemon is already running - "adb reboot recovery".
Click to expand...
Click to collapse
fastboot reboot recovery doesnt seem to boot the phone to recovery..
should the OS be completely booted up if I want to use the adb command? because it displays the error "error: device not found" when I try to "adb reboot recovery"
Might this be a problem with my computer? I checked and confirmed that the drivers for the phone are successfully installed...
knaphih said:
fastboot reboot recovery doesnt seem to boot the phone to recovery..
should the OS be completely booted up if I want to use the adb command? because it displays the error "error: device not found" when I try to "adb reboot recovery"
Might this be a problem with my computer? I checked and confirmed that the drivers for the phone are successfully installed...
Click to expand...
Click to collapse
Do you have the fastboot command on your computer?
troby86 said:
Do you have the fastboot command on your computer?
Click to expand...
Click to collapse
Yes, I can fastboot works ok because I can flash recovery image and reboot phone through fastboot. But since my power button is broken, I need to reboot to recovery through the computer...
knaphih said:
Yes, I can fastboot works ok because I can flash recovery image and reboot phone through fastboot. But since my power button is broken, I need to reboot to recovery through the computer...
Click to expand...
Click to collapse
First try: "adb reboot recovery" or "fastboot reboot-recovery"
If that doesn't work, give this a good read to see if it will help you:
http://wiki.cyanogenmod.com/index.php?title=Fastboot
If you are able to flash the recovery via fastboot, then I see no reason why you should not be able to reboot into recovery via fastboot or adb.
---------- Post added at 06:18 AM ---------- Previous post was at 06:11 AM ----------
knaphih said:
Yes, I can fastboot works ok because I can flash recovery image and reboot phone through fastboot. But since my power button is broken, I need to reboot to recovery through the computer...
Click to expand...
Click to collapse
And if none of that seems to work:
http://www.androidguys.com/2010/09/08/manage-nexus-broken-power-button/
OR
http://www.yamihoshi.nl/tech/tutorial-google-nexus-one-power-button-soft-fix
Both are the same, the second one is easier to follow.
OR
Put your recovery .img file into the same folder as your fastboot command, and run this: "fastboot boot recovery-clockwork-2.5.1.4-passion.img"
^^^^^USE YOUR RECOVERY NAME...NOT THE EXACT ONE ABOVE^^^^^
First try: "adb reboot recovery" or "fastboot reboot-recovery"
If that doesn't work, give this a good read to see if it will help you:
http://wiki.cyanogenmod.com/index.php?title=Fastboot
If you are able to flash the recovery via fastboot, then I see no reason why you should not be able to reboot into recovery via fastboot or adb.
Click to expand...
Click to collapse
I've attached an image showing proof that I've tried your method but still kept on failing to reboot to recovery..
When i try the command "fastboot boot recovery-clockwork-5.0.2.0-passion.img", the phone simply restarts and goes back to the 'X' boot screen and gets stuck there.
Could anyone please find me an genuine unedited gingerbread 2.3.4 ROM so I can PASSIMG it? ... I've downloaded several rooted ones.. but all seem to need the "android-info" file
fastboot reboot recovery
No "reboot-recovery".
And if you still get stuck on "X" when you reboot to recovery - it means that your recovery is corrupted/unusable too, and you need to PASSIMG everything.
Generally, booting the recovery through "fastboot boot" should have done enough - if your phone can't boot, it might probably be a HW problem preventing it from booting, and in that case - nothing will help.
fastboot reboot recovery
No "reboot-recovery".
And if you still get stuck on "X" when you reboot to recovery - it means that your recovery is corrupted/unusable too, and you need to PASSIMG everything.
Generally, booting the recovery through "fastboot boot" should have done enough - if your phone can't boot, it might probably be a HW problem preventing it from booting, and in that case - nothing will help.
Click to expand...
Click to collapse
I've attached an image trying out "fastboot reboot recovery" fastboot doesnt even seem to send that command to the phone..
Could anyone please provide me with a genuine stock gingerbread 2.3.4 or higher PASSIMG file? i've searched a lot but all i see are modded or rooted ones.
Yes, you're right. Fastboot can't reboot to recovery, only adb.
Oh well, in that case you're out of luck. You can't PASSIMG without power button, so if "fastboot boot some_boot_image" doesn't help - there's not much left to do.
You could always disassemble the phone and fix the power button...
knaphih said:
I've attached an image trying out "fastboot reboot recovery" fastboot doesnt even seem to send that command to the phone..
Could anyone please provide me with a genuine stock gingerbread 2.3.4 or higher PASSIMG file? i've searched a lot but all i see are modded or rooted ones.
Click to expand...
Click to collapse
Here's the 2.3.6 PASSIMG zip file link. Follow the directions. If you can get into BootLoader, your phone should automatically boot this if you have it named to PASSIMG.zip, and on the ROOT of your SD card:
http://forum.xda-developers.com/showthread.php?t=1312540
You guys are life savers troby86 and Jack_R1..
Yes, you're right. Fastboot can't reboot to recovery, only adb.
Oh well, in that case you're out of luck. You can't PASSIMG without power button, so if "fastboot boot some_boot_image" doesn't help - there's not much left to do.
You could always disassemble the phone and fix the power button...
Click to expand...
Click to collapse
I've seen an in depth video tutorial on youtube and attempted to repair the power button on my own.. however I failed since I cannot do such tiny soldering..
Here's the 2.3.6 PASSIMG zip file link. Follow the directions. If you can get into BootLoader, your phone should automatically boot this if you have it named to PASSIMG.zip, and on the ROOT of your SD card:
http://forum.xda-developers.com/show....php?t=1312540
Click to expand...
Click to collapse
Thankyou so much . This is what I've been searching for.. I'll let you guys know the outcome after I download and fix my phone (hopefully I will)
knaphih said:
You guys are life savers troby86 and Jack_R1..
I've seen an in depth video tutorial on youtube and attempted to repair the power button on my own.. however I failed since I cannot do such tiny soldering..
Thankyou so much . This is what I've been searching for.. I'll let you guys know the outcome after I download and fix my phone (hopefully I will)
Click to expand...
Click to collapse
Did the link I provided work? If not here is the actual file:
http://www.multiupload.com/KVY1MG1HGH
troby86 said:
Did the link I provided work? If not here is the actual file:
http://www.multiupload.com/KVY1MG1HGH
Click to expand...
Click to collapse
wow troby86
your still here
http://forum.xda-developers.com/showthread.php?t=1350288
atleast have the decency to refund my money you jackass
mally2 said:
wow troby86
your still here
http://forum.xda-developers.com/showthread.php?t=1350288
atleast have the decency to refund my money you jackass
Click to expand...
Click to collapse
I realize the situation you are in sucks, but please don't let your frustration carry over into these threads. We are here to help the original poster, not to try and get claims resolved and to sling mud. Try to keep this thread a helpful thread
Thanks
bassmadrigal said:
I realize the situation you are in sucks, but please don't let your frustration carry over into these threads. We are here to help the original poster, not to try and get claims resolved and to sling mud. Try to keep this thread a helpful thread
Thanks
Click to expand...
Click to collapse
well what do you know, he may just ask the OP to send him his nexus to get it fixed and you will never hear from him again.... just warning y'all thats all....
ok been dealing with this for the past hour no results.. i recently flashed the twrp recovery just to check it out and wanted to flash a rom on it went to do so and now that i reboot phone it stays on the htc start up screen turns off than back on.. only thing working on it is the hboot, no recovery. although occasionally ill see the twrp start up screen than it turns off and goes white htc... any help is appreciated.. thinking i may have to relock and find the stock at&t ruu??:crying:
gabriel1946 said:
ok been dealing with this for the past hour no results.. i recently flashed the twrp recovery just to check it out and wanted to flash a rom on it went to do so and now that i reboot phone it stays on the htc start up screen turns off than back on.. only thing working on it is the hboot, no recovery. although occasionally ill see the twrp start up screen than it turns off and goes white htc... any help is appreciated.. thinking i may have to relock and find the stock at&t ruu??:crying:
Click to expand...
Click to collapse
So you flashed the rom and it wont boot up now? or you flashed the recovery and it wont boot up now.
camo_flage said:
So you flashed the rom and it wont boot up now? or you flashed the recovery and it wont boot up now.
Click to expand...
Click to collapse
the recovery was working i was using jb pacman rom than flashed to i think it was element rom by shadow slayer but once i did that it keeps turning on and off if i try to choose recovery from the hboot it shows the recovery screen for a second than goes to htc screen and turns off and back on
gabriel1946 said:
ok been dealing with this for the past hour no results.. i recently flashed the twrp recovery just to check it out and wanted to flash a rom on it went to do so and now that i reboot phone it stays on the htc start up screen turns off than back on.. only thing working on it is the hboot, no recovery. although occasionally ill see the twrp start up screen than it turns off and goes white htc... any help is appreciated.. thinking i may have to relock and find the stock at&t ruu??:crying:
Click to expand...
Click to collapse
Fastboot erase cache command will fix this problem. Boot to your bootloader select fastboot usb and run that command.
haha im not too good with computers more of a mobile only tech haha can u explain that please?
gabriel1946 said:
haha im not too good with computers more of a mobile only tech haha can u explain that please?
Click to expand...
Click to collapse
I assume you are using windows...? Do you have adb installed/working? If the answer to both of these is yes. Reboot your phone to the bootloader (hboot) select fastboot usb in hboot. Open a cmd Window cd to the dir where adb is located. Then run the command in the above post.
---------- Post added at 06:07 PM ---------- Previous post was at 05:54 PM ----------
gabriel1946 said:
the recovery was working i was using jb pacman rom than flashed to i think it was element rom by shadow slayer but once i did that it keeps turning on and off if i try to choose recovery from the hboot it shows the recovery screen for a second than goes to htc screen and turns off and back on
Click to expand...
Click to collapse
Last time this happened there was a script that was running that corrupted the cache partition. That is why erasing cache fixes it.
esloan said:
I assume you are using windows...? Do you have adb installed/working? If the answer to both of these is yes. Reboot your phone to the bootloader (hboot) select fastboot usb in hboot. Open a cmd Window cd to the dir where adb is located. Then run the command in the above post.
Click to expand...
Click to collapse
adb u mean adbfastbootrecovery? i installed in not sure how to get it working, the command imputing is where im getting lost sorry for my noobness lol appreciate ur help i have my phone on hboot fastboot now connected to my computer ive seen that command imput is shift and right click but i dont get any command window i get normal options.. ive only use command in the run app under start
gabriel1946 said:
adb u mean adbfastbootrecovery? i installed in not sure how to get it working, the command imputing is where im getting lost sorry for my noobness lol appreciate ur help i have my phone on hboot fastboot now connected to my computer ive seen that command imput is shift and right click but i dont get any command window i get normal options.. ive only use command in the run app under start
Click to expand...
Click to collapse
Okay where is your adb file? Ex mine is in a C:/Android. By default if you installed the android SDK the adb files would be in the SDK folders. Any way if you were fast boot flashing a recovery your going to do the same thing just use fastboot erase cache as the command instead of the recovery command. If none of this makes since PM me.
Resolved via PM
Hello,
I have trouble with my nexus 6. I tried to flash the latest factory image for 5.1. But my system.img did not flash... after hours, I did not found any solution, so tried to lock and relock the bootloader again. Locking worked as espected... but unlocking returns the following message:
Code:
(bootloader) Check 'Allow OEM Unlock' in Developer Options.
FAILED (remote failure)
finished. total time: 0.004s
Now I sit here, no booting device because of missing android version and I can not unlock the bootloader anymore... Somebody can help?
Thanks
Andy
Sorry - it's not good news:
http://forum.xda-developers.com/nexus-6/general/relock-bootloader-time-updating-to-5-1-t3053497
**** that's really bad!!! But thanks for your reply!!!
ANDYx1975 said:
**** that's really bad!!! But thanks for your reply!!!
Click to expand...
Click to collapse
I did have same problem with system.img, i rebooted my phone and it was on a bunch of fc phone, nfc Bluetooth, etc.. So i went back to recovery tried again, same results. So i decided to flash a lower firmware i think 5.01.. Radio, bootloader and then system.. Damn it... System got a error... Then i did a - w , and flashed 5.1 again.. This time system was successful .. Everything went good.. Reboot my phone.. Went to recovery mode, factory reset.. And rebooted system.. Went good.. Then on Settings developers OEM unlock was uncheck..? Anyway.. Im glad everything works fine..
Sent from my Nexus 6 using Tapatalk
narezese said:
I did have same problem with system.img, i rebooted my phone and it was on a bunch of fc phone, nfc Bluetooth, etc.. So i went back to recovery tried again, same results. So i decided to flash a lower firmware i think 5.01.. Radio, bootloader and then system.. Damn it... System got a error... Then i did a - w , and flashed 5.1 again.. This time system was successful .. Everything went good.. Reboot my phone.. Went to recovery mode, factory reset.. And rebooted system.. Went good.. Then on Settings developers OEM unlock was uncheck..? Anyway.. Im glad everything works fine..
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
I do not know if it was unchecked... I can not reunlock bootloader anymore.... that's my main problem!!!
ANDYx1975 said:
I do not know if it was unchecked... I can not reunlock bootloader anymore.... that's my main problem!!!
Click to expand...
Click to collapse
Im talking about mine.. Before flashing 5.1 the option was checked..
Sent from my Nexus 6 using Tapatalk
You sir have a brick. Your only option as of right now is to try to get Motorola to replace the device for you.
Sent from my Nexus 6 using XDA Free mobile app
ok... tkanks I have to try this... even if I think my chances are almost zero!!! Thanks anyway!!!
Have you tried to adb sideload the ota .zip?
yeah I only have access to fastboot... and he does not find the device
From fastboot can you get to stock recovery? After selecting recovery in fastboot, you'll get the Android dude ... But you have to hit the power and volume up/down as well (forget the exact combo) to get into recovery. From there you select install install via adb (forget the exact verbiage, but it's the second option from the top). From there you run adb, not fastboot
---------- Post added at 04:00 AM ---------- Previous post was at 03:58 AM ----------
http://www.droid-life.com/2015/03/1...1-ota-updates-for-nexus-devices-4-5-6-7-9-10/
^ d/l link with a link to (better) flashing directions
to be honest I do not know it's already out home to the repair service... ****... I should be more patient!!!
Gotcha ... Don't feel bad, you're not alone. I, and many others, did the same/similar and ended up in the same situation.
I been rooting/tinkering for 6+ years across 10 or so devices and it turns out a friggin NEXUS is the first device that I brick! ?
(I'm fully aware of the risks we take with unlocking amd rooting, but IMO Google screwed the pooch with this OEM Unlock "feature" in developer options! Why make unlocking dependent on a setting WITHIN the OS??!)
So hey... I managed to get it back from my post office... when I go into fastboot, I can choose "Recovery Mode" and it seems to boot into it:
But when I try to sideload... I get the following message:
Code:
adb sideload nexus.zip
error: device not found
ANDYx1975 said:
So hey... I managed to get it back from my post office... when I go into fastboot, I can choose "Recovery Mode" and it seems to boot into it:
But when I try to sideload... I get the following message:
Code:
adb sideload nexus.zip
error: device not found
Click to expand...
Click to collapse
You need to boot into stock recovery. From the screen you are in press volume up and power.
What ^ he said ... Then once in stock recovery select the second option (install update from adb (or something like that))
ok... I can not go into recovery... the google logo appears and nothing happens... ****!!! But hey thanks anyways!!!
That sucks! Sorry man!
@rootSU
At that screen in his pic, isn't he supposed to hit power+volume + or something to get to a different screen?
I might've wrong, but I did read somewhere when you get the dead Droid guy, you hit that combo and it takes you to a different screen.
Sent from my Nexus 6
Casper34 said:
@rootSU
At that screen in his pic, isn't he supposed to hit power+volume + or something to get to a different screen?
I might've wrong, but I did read somewhere when you get the dead Droid guy, you hit that combo and it takes you to a different screen.
Sent from my Nexus 6
Click to expand...
Click to collapse
Yes, thats what I said.
Okay...
So i bricked my device n so to unbrick am flashing stock image through nexus root toolkit but my phone doesn't enter into fast boot mode no matter wat buttons i press it just stays on google logo...
Anyone has a solution ???
Pls help
umair shaikh said:
Okay...
So i bricked my device n so to unbrick am flashing stock image through nexus root toolkit but my phone doesn't enter into fast boot mode no matter wat buttons i press it just stays on google logo...
Anyone has a solution ???
Pls help
Click to expand...
Click to collapse
Have you tried it from your PC?
fastboot reboot-bootloader
How can you run fastboot commands if your not in fastbbot-bootloader?
"my phone doesn't enter into fast boot mode"
(General message - see what I did there? No need to repeat the entire post. Just the part I'm responding to.)
Does this mean that you can't get to bootloader? Is your bootloader unlocked? When you reboot do you see the open padlock symbol?
So what did you do to brick your device?
dahawthorne said:
"my phone doesn't enter into fast boot mode"
(General message - see what I did there? No need to repeat the entire post. Just the part I'm responding to.)
Does this mean that you can't get to bootloader? Is your bootloader unlocked? When you reboot do you see the open padlock symbol?
So what did you do to brick your device?
Click to expand...
Click to collapse
Yep my bootloader is unlocked i used to run custom rom it just stays on google logo thats it
holeindalip said:
How can you run fastboot commands if your not in fastbbot-bootloader?
Click to expand...
Click to collapse
With USB connected, from a cmd prompt I do:
adb devices (to load the drivers and make sure my phone is recognized)
adb reboot bootloader (this should put you in bootloader mode)
fastboot devices (just to be sure my phone is still recognized)
fastboot flash radio radio.img (or whatever image you want to flash)
fastboot reboot-bootloader (in between flashes, just to be safe)
I do so hate it when people don't bother to read my posts properly. It takes away my incentive to try to help them...
"No need to repeat the entire post. Just the part I'm responding to."
"So what did you do to brick your device?" Install the custom ROM you mention?
And a new question. You say "no matter wat buttons i press". Does that include the bootloader power & volume down simultaneous press for maybe 30 seconds?
So there are 3 items in this post. Can I have 3 responses please? The first will be not copying this entire post all over again, the other two will be answers to my questions.
umair shaikh said:
Okay...
So i bricked my device n so to unbrick am flashing stock image through nexus root toolkit but my phone doesn't enter into fast boot mode no matter wat buttons i press it just stays on google logo...
Anyone has a solution ???
Pls help
Click to expand...
Click to collapse
Do you have a working recovery you can access?
And stay away from toolkits. Learn to flash manually. It's easy and you know what part goes wrong. Tool kits are nice in automation, but when something happens ya don't have a decent idea where to start.
Sent from my Nexus 6 using XDA Free mobile app
@dahawthorne
1.lol fine i get it my bad ..
2.i was actually trying to install n preview. Actually i read somewhere we can flash adb file type by new twrp so i tried doing that n this happened..
3.i tried it a couple of times..but if i press them for longer time it just turns off n turn on again n gets stuck on logo
31ken31 said:
Do you have a working recovery you can access?
And stay away from toolkits. Learn to flash manually. It's easy and you know what part goes wrong. Tool kits are nice in automation, but when something happens ya don't have a decent idea where to start.
Sent from my Nexus 6 using XDA Free mobile app
Click to expand...
Click to collapse
Nope...nothing
I have been blundering my way though the internet to get my ROG Phone 2 rooted. I have unlocked the bootloader, I have a modified boot image from magisk, I have the ADB connection set up through USB and it works fantastically. I honestly don't know how I got it work, it involved many different driver update attempts and then figuring out I hadn't put the phone into USB debugging, but now fastboot doesn't work.
ADB will list the device, but fastboot cannot see it. I have tried rebooting the phone into the bootloader, but there is no connection on either. Not sure why I thought that would work, but I tried. I really don't understand enough about fastboot to get any farther on my own.
I have the tencent version and I was pretty certain I have the CN android 9.0 on it, but I am no longer certain of that. I am running windows 10.
This is my build number: PKQ1.190414.001.WW_Phone-16.0622.1906.19-0
I honestly don't know, but does that WW mean my tencent phone is running the WW firmware?
RichDoe252 said:
I have been blundering my way though the internet to get my ROG Phone 2 rooted. I have unlocked the bootloader, I have a modified boot image from magisk, I have the ADB connection set up through USB and it works fantastically. I honestly don't know how I got it work, it involved many different driver update attempts and then figuring out I hadn't put the phone into USB debugging, but now fastboot doesn't work.
ADB will list the device, but fastboot cannot see it. I have tried rebooting the phone into the bootloader, but there is no connection on either. Not sure why I thought that would work, but I tried. I really don't understand enough about fastboot to get any farther on my own.
I have the tencent version and I was pretty certain I have the CN android 9.0 on it, but I am no longer certain of that. I am running windows 10.
This is my build number: PKQ1.190414.001.WW_Phone-16.0622.1906.19-0
I honestly don't know, but does that WW mean my tencent phone is running the WW firmware?
Click to expand...
Click to collapse
Fun fact, I just got Fastboot access from my computer by using the side USB port and rebooting into the bootloader from ADB. Still not to sure about the version bit. I think I'm just going to give it whirl and brick my device, maybe.
RichDoe252 said:
I have been blundering my way though the internet to get my ROG Phone 2 rooted. I have unlocked the bootloader, I have a modified boot image from magisk, I have the ADB connection set up through USB and it works fantastically. I honestly don't know how I got it work, it involved many different driver update attempts and then figuring out I hadn't put the phone into USB debugging, but now fastboot doesn't work.
ADB will list the device, but fastboot cannot see it. I have tried rebooting the phone into the bootloader, but there is no connection on either. Not sure why I thought that would work, but I tried. I really don't understand enough about fastboot to get any farther on my own.
I have the tencent version and I was pretty certain I have the CN android 9.0 on it, but I am no longer certain of that. I am running windows 10.
This is my build number: PKQ1.190414.001.WW_Phone-16.0622.1906.19-0
I honestly don't know, but does that WW mean my tencent phone is running the WW firmware?
Click to expand...
Click to collapse
1. You are running a WW rom, but that doesn't necessarily mean your fingerprint is matched. To update you need to have both WW rom and WW fingerprint. You can check if your fingerprint is CN or WW using device info hw from playstore under 'system'
2. In order to root you need to have a matching root boot img for your current rom ie root img for 1906.19, just checking that your know this?
3. Have you managed to get the phone recognised using the cmd 'fastboot devices'? Also are you using the side port?
4.when you say bootloader, have you definitely got the phone in fastboot mode - hold vol up and power button until you see the screen with some options. That screen is fastboot mode, you don't need to select any further options. Once in that mode, connect to pc, open adb and run the fastboot devices cmd. Once your device is recognised, report back here for further steps
superbrick.
reg66 said:
1. You are running a WW rom, but that doesn't necessarily mean your fingerprint is matched. To update you need to have both WW rom and WW fingerprint. You can check if your fingerprint is CN or WW using device info hw from playstore under 'system'
2. In order to root you need to have a matching root boot img for your current rom ie root img for 1906.19, just checking that your know this?
3. Have you managed to get the phone recognised using the cmd 'fastboot devices'? Also are you using the side port?
4.when you say bootloader, have you definitely got the phone in fastboot mode - hold vol up and power button until you see the screen with some options. That screen is fastboot mode, you don't need to select any further options. Once in that mode, connect to pc, open adb and run the fastboot devices cmd. Once your device is recognised, report back here for further steps
Click to expand...
Click to collapse
Thanks for the reply! I did indeed get fastboot to work over USB. Fastboot devices reported back the serial number and everything. I did not know that the build need to match on both the boot and the rom, but that does make sense and I probably should have realized that before I went ahead and copied the rooted boot.img I had over. Then my phone couldn't boot up proper, and got stuck in fastboot. Then I went ahead and copied all of the contents of the same rom over and now it is literally just a black screen. Won't turn on any more. I think I super bricked it.
Sorry I didn't see your post earlier and I know I am not father into the deep end, but is there a way out from where I am.
RichDoe252 said:
Thanks for the reply! I did indeed get fastboot to work over USB. Fastboot devices reported back the serial number and everything. I did not know that the build need to match on both the boot and the rom, but that does make sense and I probably should have realized that before I went ahead and copied the rooted boot.img I had over. Then my phone couldn't boot up proper, and got stuck in fastboot. Then I went ahead and copied all of the contents of the same rom over and now it is literally just a black screen. Won't turn on any more. I think I super bricked it.
Sorry I didn't see your post earlier and I know I am not father into the deep end, but is there a way out from where I am.
Click to expand...
Click to collapse
Oh jeepers dude. So just a black screen... Can you at least boot into fastboot?
reg66 said:
Oh jeepers dude. So just a black screen... Can you at least boot into fastboot?
Click to expand...
Click to collapse
Nope. The only response I can get out of it now is when I plug it into the fastboot port, the computer recognizes that something was plugged in. I don't even get a device on a device manager.
RichDoe252 said:
Nope. The only response I can get out of it now is when I plug it into the fastboot port, the computer recognizes that something was plugged in. I don't even get a device on a device manager.
Click to expand...
Click to collapse
Try holding the power button for around 20 secs until it shuts down. Then try vol up and power together and see if you get back to fastboot. If that doesn't work try vol up vol down and power buttons all together. Then try again to put it in fastboot mode using vol up and power. Let us know what happens /if you can reach fastboot mode
reg66 said:
Try holding the power button for around 20 secs until it shuts down. Then try vol up and power together and see if you get back to fastboot. If that doesn't work try vol up vol down and power buttons all together. Then try again to put it in fastboot mode using vol up and power. Let us know what happens /if you can reach fastboot mode
Click to expand...
Click to collapse
Unfortunately, nothing. Holding power for 20 seconds showed nothing, and like wise for volume up and power. Battery was fully charged too. Had it plugged in for most of today while I was trying to get fastboot to work.
RichDoe252 said:
Unfortunately, nothing. Holding power for 20 seconds showed nothing, and like wise for volume up and power. Battery was fully charged too. Had it plugged in for most of today while I was trying to get fastboot to work.
Click to expand...
Click to collapse
Is there any sort of illumination to the black screen ie do you think the phone is on but the screen is black or do think the phone is completely off?
Holding power button for a while should switch it off after a while. Try holding for longer than 20 secs, then try booting into fastboot mode
---------- Post added at 04:00 AM ---------- Previous post was at 03:44 AM ----------
Well dude, it's 4 am here. Gotta get some sleep dude. Will check here when I wake. Good luck in the mean time
Still trying to get to sleep. How ya getting on? What about vol down and power buttons for 30+secs, can you try that and let us know the results
reg66 said:
Still trying to get to sleep. How ya getting on? What about vol down and power buttons for 30+secs, can you try that and let us know the results
Click to expand...
Click to collapse
Bro get to sleep! Such a good Samaritan
TikiThePug said:
Bro get to sleep! Such a good Samaritan
Click to expand...
Click to collapse
LOL! I would if I could, just can't sleep yet. Hopefully soon tho!
RichDoe252 said:
Unfortunately, nothing. Holding power for 20 seconds showed nothing, and like wise for volume up and power. Battery was fully charged too. Had it plugged in for most of today while I was trying to get fastboot to work.
Click to expand...
Click to collapse
Try a USB 2.0 port? Surprisingly this works for some phones even though it's compatible with 3.0.
reg66 said:
Still trying to get to sleep. How ya getting on? What about vol down and power buttons for 30+secs, can you try that and let us know the results
Click to expand...
Click to collapse
Well, It's been untouched for a day now, and it still will not react to input. No response from long hold on the power button. I will try again in the morning. Is it possible that I somehow wrote into the BIOS of the phone? Android does use a BIOS, right?
RichDoe252 said:
Well, It's been untouched for a day now, and it still will not react to input. No response from long hold on the power button. I will try again in the morning. Is it possible that I somehow wrote into the BIOS of the phone? Android does use a BIOS, right?
Click to expand...
Click to collapse
Android itself does not have a BIOS, since Android is an OS and BIOS is more similar to firmware. But yes, the phone does have firmware, and it could be that the mismatch in firmware versions (from which you tried to flash), has caused the bootloader to "not know what to do now" when trying to start the phone up.
One thing which comes with all phones with a Qualcomm chipset is something called Qualcomm Crashdump Mode. You can try to see if you can get your phone in EDL (emergency download) mode and restore the correct firmware in that way:
https://www.the***********.com/rog-phone-2-unbrick-guide (URL gets censored for some reason; it should be "the custom droid" with no spaces)
Also, if you continue to have driver issues with connecting the phone to your PC, are you able to test another PC or even a Mac if you have access to one? I find Windows can be a giant pain for getting ADB and fastboot to work properly at times.
Good luck and let us know how it goes.
reg66 said:
Still trying to get to sleep. How ya getting on? What about vol down and power buttons for 30+secs, can you try that and let us know the results
Click to expand...
Click to collapse
Ok, so here's where I am: I have left the phone unplugged for a long time now. Really had no effect. I just downloaded QPST and I can actually get my computer to see the phone. However, I am still not quite sure how to USE QPST and not make things worse. So this is my plan: I am going to look through the forums here for info on how to use QPST to get my phone working again. Not really sure what that will look like, but fastboot would be a good start. From there, it sounds like I have to get the original firmware back on it, and then go about the process of rooting once again.
Still leaves me with the issue that started me down the path of rooting this phone, but at least it will not longer be bricked.
RichDoe252 said:
Ok, so here's where I am: I have left the phone unplugged for a long time now. Really had no effect. I just downloaded QPST and I can actually get my computer to see the phone. However, I am still not quite sure how to USE QPST and not make things worse. So this is my plan: I am going to look through the forums here for info on how to use QPST to get my phone working again. Not really sure what that will look like, but fastboot would be a good start. From there, it sounds like I have to get the original firmware back on it, and then go about the process of rooting once again.
Still leaves me with the issue that started me down the path of rooting this phone, but at least it will not longer be bricked.
Click to expand...
Click to collapse
You may not HAVE to flash complete firmware, it is quite likely that the boot.img is causing the problem as you flashed an incompatible version. Below you'll flash the correct version which HOPEFULLY will fix your phone, provided you can get into fastboot mode now.
Haven't read back through all the thread so i can't recall all the details of where you're at. As far as i can tell you're still running WW 16.0622.1906.19-0, correct? Can you get the device to now boot into fastboot mode? (from a powered off state, press and hold vol up and power at the same time. You should then be presented with some options, DON'T select any option. With that menu screen open is fastboot mode.
1. Download and install ADB Fastboot from here to C: drive of your pc/laptop.
2. With your phone in fastboot mode (as detailed above) connect it to pc/laptop using the side port of the phone.
3. Navigate to C:\Program Files (x86)\Minimal ADB and Fastboot folder and double click the cmd-here.exe, this will open a cmd window.
4. Type 'fastboot devices' to check that it's recognised, there should be a serial/key shown after entering that cmd.
5. Provided the serial/key is shown in fastboot mode, download the following boot.img (which is for WW 1906.19) from here.
6. Copy that boot img to the same folder you have open for ADB (C:\Program Files (x86)\Minimal ADB and Fastboot)
7. In the cmd window type 'fastboot flash boot boot.img'.
Now, that boot img is the STOCK boot img for your rom version. Don't worry about rooting for now (if i recall correctly, your phone won't boot to system), let's just try to get the phone booting first. Providing there are no errors when flashing the boot img, on the phone fastboot menu, scroll through and choose 'restart'.
Let me know if the device boots to system now... Good luck
I'll pm you my email address so you'll be able to get hold of me if you get stuck at any stage...
EDIT: was forgetting you tried so many times to get into fastboot mode, without success.
---------- Post added at 08:59 PM ---------- Previous post was at 08:17 PM ----------
Dude, is your phone screen still black but switched on? When you tap the screen does it vibrate. I'm thinking you might already be in edl mode (which could be a good thing). Let us know
Check your pm's dude for further info. I can't post links to the site required so have sent via pm
TikiThePug said:
Android itself does not have a BIOS, since Android is an OS and BIOS is more similar to firmware. But yes, the phone does have firmware, and it could be that the mismatch in firmware versions (from which you tried to flash), has caused the bootloader to "not know what to do now" when trying to start the phone up.
One thing which comes with all phones with a Qualcomm chipset is something called Qualcomm Crashdump Mode. You can try to see if you can get your phone in EDL (emergency download) mode and restore the correct firmware in that way:
https://www.the***********.com/rog-phone-2-unbrick-guide (URL gets censored for some reason; it should be "the custom droid" with no spaces)
Also, if you continue to have driver issues with connecting the phone to your PC, are you able to test another PC or even a Mac if you have access to one? I find Windows can be a giant pain for getting ADB and fastboot to work properly at times.
Good luck and let us know how it goes.
Click to expand...
Click to collapse
Just dropping you a quick note to say thanks for thanks! LOL. Yeah, your post earlier seems like the best place to go. Have used Miflash Tool a few times on Xiaomi devices, it's pretty good and straight forward. Should be a LOT easier than using QPST and having to change EMMC to UFS.
Can't remember where i saw it now, but i'm sure i read that if the phone screen is black (but switched on) and vibrates, then it's likely to be in EDL mode already. Which will hopefully be good news for @RichDoe252. Before that (having never been in that situation), i wasn't aware that an all black screen could mean EDL mode is active. Fingers crossed for Rich it'll all work out just fine.
@RichDoe252 If all goes successfully using the QPST file download (and using the Miflash Tool the guide mentions in the pm i sent you) and flashing, DON'T ROOT JUST YET!!!! LOL. Let us know how it goes and then we can look into, and point you in the right direction, for getting you rooted and up to date on latest A9 or A10 whichever you'd prefer
Well I must say Rich, I'm surprised you haven't been back here yet to give any updates on progress!! Sent you a couple of emails through pm... Man, if it was my fairly expensive phone that was in the poo pan, I'd be all over trying to fix it lol
reg66 said:
Well I must say Rich, I'm surprised you haven't been back here yet to give any updates on progress!! Sent you a couple of emails through pm... Man, if it was my fairly expensive phone that was in the poo pan, I'd be all over trying to fix it lol
Click to expand...
Click to collapse
First off, you are a freaking saint. I really do appreciate all the help you have been offering up, and I am sorry I have not been very quick with a response. As my phone currently stands, I get 0% response from anything I do to it. No vibrate, nothing. No indication it even is plugged in. I had it connected to my PC with QPST installed, and it was able to pick up that the phone was there, and then immediately tried to download something to it. Not sure what, not sure why, but that kinda typifiies my interaction with this whole process so far. If you haven't guessed, I'm kinda in over my head.
Back to the problem: QPST started some opperation to download something to it. Wouldn't let me do anything else, said the phone was in "download mode". Either way it stopped at 30% and didn't progress for 30 minutes, so I tried to unplug it and plug it back in. Same interaction. Unable to do anything to the phone, no reaction from the phone what so ever. This was, by the way, plugged into the fastboot side port.
I saw that you PM'ed me, and now I can't find the email notification or the PMs on the site. Forgive me for being unfortunately new at this. I will get back to you bud, and thank you again.