Flashed vendor image while updating PureNexus but forgot to do it for both slots. Rebooted into system but it kept throwing "System has crashed" dialogs.
Rebooted into recovery to find TWRP gone. Went into Stock Recovery and did a Full Wipe in an attempt to fix things (I was traveling without a laptop and didn't have many options.
I can now get back into the OS, but receive a vendor mismatch error and have lost functionalities like wireless data.
I'm back with my computer but it's no longer seeing the phone (or vice versa) when I plug in. As such I can't sideload.
I also can't load through Stock Recovery because I had encrypted my phone and it can't install off SD.
At this point I just wanna go back to square one but with neither the ability to sideload nor recovery-load, I'm not sure what I can do to try to fix things.
Am I screwed? Is there a potential solution I'm overlooking? Any insight would be greatly appreciated.
Thanks!
Boot into recovery and run the flashall bat file for the full age and remove the-w to save data.
TonikJDK said:
Boot into recovery and run the flashall bat file for the full age and remove the-w to save data.
Click to expand...
Click to collapse
He no longer has TWRP. His device reverted back to stock recovery. He also can't flash a custom recovery due to his computer not recognizing the device.
I've never experienced this issue on any of my devices. These dual slots really make tinkering much more risky from all the crazy issues I've been reading on XDA.
Can you get into fastboot? If you use the "fastboot devices" command in the cmd menu where your fastboot file is located, does it show your device's serial number (I assume probably not, but it should be attempted)?
Pain-N-Panic said:
Can you get into fastboot? If you use the "fastboot devices" command in the cmd menu where your fastboot file is located, does it show your device's serial number (I assume probably not, but it should be attempted)?
Click to expand...
Click to collapse
That is where I was going, and flash the factory image. The computer not seeing the phone is a computer or cable issue he should be able to overcome.
TonikJDK said:
That is where I was going, and flash the factory image. The computer not seeing the phone is a computer or cable issue he should be able to overcome.
Click to expand...
Click to collapse
Or maybe a driver issue? If you can't get the device to be recognized via fastboot, I would try driver troubleshooting.
Pain-N-Panic said:
Or maybe a driver issue? If you can't get the device to be recognized via fastboot, I would try driver troubleshooting.
Click to expand...
Click to collapse
Yep, in stock recovery there is nothing that can cause this other than drivers, cable or computer.
Well, I suppose a bad usb port on the phone could too.
Mismatched Vendor images (so long as they are from the same version (oreo/nougat/etc)) Should not cause any of these problems.
In your specific situation, i wouldnt even bother trying any recovery process through any recovery, stock or twrp.
The best thing for you to do is back up your data, boot your phone into the bootloader, and flash a factory image.
That's the thing, 'fastboot devices' doesn't list anything (nor does 'adb devices' when I'm in system). I never had this problem before and could always see my phone via fb/adb in the past. Nothing has changed on my laptop side (same drivers, same cable, same everything). The only thing that's changed is whatever happened to the phone itself.
Is there no way to undo the nuke the phone so that it undoes the encryption? That's what I thought stock recovery full wipe would do, but the fact that I still can't mount/access the SD card must mean that it's still encrypted.
BTW as far as the vendor image goes, I flashed the NJH47D one, though I must have NOF26W in the other slot because that's what shows up under "Vendor version" in Settings/About Phone.
Troubleshooting update:
• it's not the port, because the phone can see/use a usb-c thumb drive
• it's not the drivers or cable, because I'm able to see my old Nexus 5X when I plug it in
• also, the Pixel charges when it's plugged into the computer, it just doesn't do anything else
The more I poke around, the more hopeless this situation seems. I have no idea how to get around it.
Hello OP,
Understand the urgency your want to your phone fixed but we can only allow one thread for the same content.
Here I close this one and users who are willing to help can go to this thread below:
https://forum.xda-developers.com/general/help/lost-twrp-adb-fastboot-phone-to-sideload-t3694745/
Regards
Jerry
Related
hi all,
i've managed to get my g-nex (vz lte) pretty badly bricked and am hoping that someone here will be able to help. here's what i did initially on the phone:
1. ran 4.0.2 update from carrier
2. installed adb sdk etc on win 7, verified connectivity and function
3. oem unlock
4. rooted phone
5. installed apps, etc.
6. used phone for a few days, rebooted at will, all working as expected, no issues
7. fully charged phone and in the settings kicked off the encryption process, entered PIN, everything looked good.
8. this morning i woke up to a failed encryption (unfortunately i didn't catch the error message) which needed to be rebooted to move on.
9. after choosing reboot, the screen went very strange - it had grainy horizontal lines that shifted in color somewhat and got dim
10. after waiting for a bit without anything happening, pulled the power and battery
11. the phone rebooted into fastboot, couldn't get into recovery to restore cwm backup, couldn't really do anything
phone shows the following:
fastboot mode - no boot or recovery img
product name - tuna
variant - toro
hw version - 9
bootloader version - primekkk15
baseband version - i515.ek02 cdma - i515.ek05
carrier info - none
serial number - XX_redacted_XX
signing - production
lock state - unlocked
here's what i've tried:
adb commands - doesn't show as there from adb devices
fastboot commands - shows up with fastboot devices, flash commands seem to start but never stop
ODIN mode - connects but writes fail to complete
different usb ports/cables, doesn't seem to make a difference
what i've found to somewhat work - but not really do much - is to oem lock and unlock the phone, once there i can fastboot flash boot boot.img, etc. but if i do a recovery and try and boot into it, it just hangs at the google screen (with the lock unlocked).
i would like maybe reformat the phone completely and reinstall, i've tried the fastboot -w and erase boot / recovery thinking that i could write a clean image to them once they had been cleared, no dice.
if anyone has some suggestions, i'd really appreciate it.
take care,
philo
Have you tried a clean install of the factory image found here? http://code.google.com/android/nexus/images.html#mysidicl53f
i have tried going back to factory, unfortunately that set of images didn't work either. i was able (after an oem lock/unlock) to flash the img files, but it errored on the fastboot reboot-bootloader command with the oddly lined screen. i've attached a picture of the screen for reference.
philo_enyce said:
i have tried going back to factory, unfortunately that set of images didn't work either. i was able (after an oem lock/unlock) to flash the img files, but it errored on the fastboot reboot-bootloader command with the oddly lined screen. i've attached a picture of the screen for reference.
Click to expand...
Click to collapse
I hope you flashed the LTE version and not the GSM
You need this one https://dl.google.com/dl/android/aosp/mysid-icl53f-factory-65895fa8.tgz and you must first flash bootloader then radio and then the update img
i have been using the lte, same as your link. i can get the bootloader on, but a reboot-bootloader gives that weird screen, if i try and flash the radio without rebooting i get:
unknown partition 'radio'
philo_enyce said:
i have been using the lte, same as your link. i can get the bootloader on, but a reboot-bootloader gives that weird screen, if i try and flash the radio without rebooting i get:
unknown partition 'radio'
Click to expand...
Click to collapse
Check here http://forum.xda-developers.com/showthread.php?t=1392336
Its the cwm for cdma edition.Check if you can flash it and in this way have access to cwm recovery
i've tried that as well, same lines even if i use the menu to go to recovery after flashing rather than reboot to bootloader first.
So long as it's back to stock, and you've locked the bootloader, it's off for a replacement you go if it was me
EddyOS said:
So long as it's back to stock, and you've locked the bootloader, it's off for a replacement you go if it was me
Click to expand...
Click to collapse
+1 to this
interestingly, i can't get the fastboot oem lock to take either. it reverts back to unlocked after the reboot fails and i have to pop the battery.
does anyone know how to straight up repartition/reformat the flash? i'm assuming that the failed encryption of the flash has put it into an unusable state and would be happy enough just wiping the damn thing clean...
It looks the encryption screwed up because of the different recovery partition which might of also messed up the partition table.
Best bet is to plead ignorance and get a replacement phone.
problem "solved"
i called samsung and pleaded for the pit + factory image with no luck, so i went over to my local vzw and had them replace the phone for me.
i'm not going to try and encrypt this one, hopefully this was just a fluke and won't affect anyone else...
nice work... let them try to fix that shiz!
Darn, I was hoping for a solution...
I am having a similar issue with a Nexus 5. Phone was working fine, started the encryption process and went to bed and woke up with a bricked phone. I can get into the Bootloader and had figured no problem, I'll just do a factory wipe. Whether trying to boot the phone or get it to do the factory restore it sits there and bootloops with the Google logo. Wish programmers would put in status messages the way we did in the 'old days.'
I was able to get a little further was able to reflash, format the partitions etc. but no luck. I am wondering if perhaps the user data may have an indicator or flag that states it is encrypted even though it isnt at this point encrypted. Figured the factory restore would have been more than enough. WUG makes a nice Root Toolkit that automates a lot of the process but even letting do what I already didnt help.
philo_enyce said:
i called samsung and pleaded for the pit + factory image with no luck, so i went over to my local vzw and had them replace the phone for me.
i'm not going to try and encrypt this one, hopefully this was just a fluke and won't affect anyone else...
Click to expand...
Click to collapse
philo_enyce said:
interestingly, i can't get the fastboot oem lock to take either. it reverts back to unlocked after the reboot fails and i have to pop the battery.
does anyone know how to straight up repartition/reformat the flash? i'm assuming that the failed encryption of the flash has put it into an unusable state and would be happy enough just wiping the damn thing clean...
Click to expand...
Click to collapse
Yep , if you can get into recovery , you can adb shell , then list the partitions with "cat proc/mounts" , from there you'll have a list of your partitions and you can use the ext4 tools to manually repartition . I believe the command is makefs_ext4 <whatever partition you wanna do > I'll try to find the exact command but you can do it .
Also if you simply type "fastboot " when at the bootloader it'll give you the help text and it should tell you how to wipe partitions from fastboot
Hack The Tuna
The same issue here ! memory locked
I ve got the same scenario on a phone i just got , brand new but with the same issue , this one boots up but its impossible to factory reset it , odin , cyanogenmod , fastboot adb flashes .... everything fails somehow .... once you reboot the phone everything comes back ! stock software with the applications and old data .... theres no way to erase it ... it seems the previous owner of the phone encrypted it and then used clockworkmod or something like that ..... the nand on the device is like hardlocked .... doesnt let you do anything !
I accidently erased everything from the KF2, all I have on it now is the recovery.
How can I get a rom back on the device?
When I plugged it in the computer under Device Manager it says Portable Devices >> F:/
When I go to my computer to try to enter f:/ its inaccessible.
How can I fix this?
Thanks!
Same issue here. Understood the instruction to wipe everything before installing ROM to mean "System" and "Internal Storage" as well. Now the downloaded ROM and "gapps" zip files are gone...
Found something called "ADB Sideload" in TWRP, could that help?
Like the OP, would appreciate some help. Kindle is a brick for now...
chipsndukes
Back Up & Running
First You need a Fastboot Cable.
Run The Recovery Tool. (Options 1 then 2)
When its completed unplug the Fastboot Cable and press and hold the power button until the KF2 turns off.
Turn it back on and you are all set to Root it!
Rooting
[ONE-CLICK] Automated Freedom-Boot and TWRP installer
OK, thanks LEGEND94, that helped !
Only difference to above: did not use a Fastboot cable to get into fastboot mode, rather fmkilo's technique here: http://forum.xda-developers.com/showthread.php?t=2117224
Held off button to shut down and restarted without having to do anything else, did not have to type any command to get out of fastboot mode.
Am restarting root and ROM flashing, hopefully will work this time.
Thanks again,
chipsndukes
chipsndukes said:
OK, thanks LEGEND94, that helped !
Only difference to above: did not use a Fastboot cable to get into fastboot mode, rather fmkilo's technique here: http://forum.xda-developers.com/showthread.php?t=2117224
Held off button to shut down and restarted without having to do anything else, did not have to type any command to get out of fastboot mode.
Am restarting root and ROM flashing, hopefully will work this time.
Thanks again,
chipsndukes
Click to expand...
Click to collapse
even though legend was OP, his method was a bit overkill, but totally fine.
Once you have recovery, or even the bootloader, you should NEVER need to restore. From the bootloader you can get into fastboot now, and from fastboot you can get the recovery.
As for putting files on, I'm not sure. I could look it up but you both got your issues solved. If someone coming here does need the help, PM me and I can look it up, but from what i remember on other android devices, usually the recovery somewhere has an option to mount USB like a storage device (probably bad wording there) but basically just like when you "turn on usb storage" in the android OS.
I am ASSUMING TWRP has something similar, and if I'm wrong, I'm sure you can always ADB to push the files onto the device from your PC in fastboot mode.
iytrix said:
even though legend was OP, his method was a bit overkill, but totally fine.
Once you have recovery, or even the bootloader, you should NEVER need to restore. From the bootloader you can get into fastboot now, and from fastboot you can get the recovery.
As for putting files on, I'm not sure. I could look it up but you both got your issues solved. If someone coming here does need the help, PM me and I can look it up, but from what i remember on other android devices, usually the recovery somewhere has an option to mount USB like a storage device (probably bad wording there) but basically just like when you "turn on usb storage" in the android OS.
I am ASSUMING TWRP has something similar, and if I'm wrong, I'm sure you can always ADB to push the files onto the device from your PC in fastboot mode.
Click to expand...
Click to collapse
Unfortunately usb Mount doesn't work in the kf2 twrp. I would love the option.
You CAN adb sideload from twrp though.
--
Sent from my Kindle Fire 2, CM 10.1
What I did above is the easiest way, the sideload didn't even work!
chipsndukes said:
Held off button to shut down and restarted without having to do anything else, did not have to type any command to get out of fastboot mode.
Click to expand...
Click to collapse
One change to the above statement. I did have to get out of fastboot mode, but it was confusing how because the terminal emulator was now gone.
I did this instead via a command window with the Fire plugged into the computer. I sent the "fastboot -i0x1949 oem idme bootmode 1" command while in the root directory for the KF2_SRT_10.2.3 restore package, there is a fastboot.exe file there.
Hope that helps.
chipsndukes
fastboot devices shows the Pixel C, but any fastboot flash commands (or fastboot flashall) fail due to unsupported command errors. Any ideas what's going on? I tried reinstalling drivers and rebooting Windows 10. Those didn't help. What's wrong? Is there a fix I can make?
This device used to have a rooted copy of Marshmallow from xceed along with a TWRP installation. But those are gone. The system partition is now blank (probably along with the user and data partitions).
I had a similar issue as the device being not detected. I used Nexus Root Toolkit v2.1.8 to flash TWRP and push supersu so I could flash them.
could the partitions just be unmounted which would show as empty
Mother_Teresa said:
I had a similar issue as the device being not detected. I used Nexus Root Toolkit v2.1.8 to flash TWRP and push supersu so I could flash them.
Click to expand...
Click to collapse
My problem is different from yours. fastboot detects the device and can perform thinks like locking and unlocking. What it can't do is flash. I did try NRT. But it can't flash either as it appears to use the same driver and fastboot that I was using--just buried.
dkryder said:
could the partitions just be unmounted which would show as empty
Click to expand...
Click to collapse
Not sure who you were replying to. But the partitions (except for bootloader and recovery) are empty as they've been wiped. I wiped the system partition myself with TWRP once. Turning on and off the bootloader lock seems to have done the rest. Besides, what would that have to do with the unsupported command I got?
I misread.
Will Pittenger said:
My problem is different from yours. fastboot detects the device and can perform thinks like locking and unlocking. What it can't do is flash. I did try NRT. But it can't flash either as it appears to use the same driver and fastboot that I was using--just buried.
Click to expand...
Click to collapse
If I recall correctly--but it's been a number of months, I had a sort of similar problem with my Pixel C trying to flash a system image after unlocking the bootloader. This thread http://forum.xda-developers.com/pixel-c/help/fastboot-pixel-c-t3328635 was helpful. Selecting some generic Google driver in Win 10 did the trick, but I do not recall which driver.
tbcpn said:
If I recall correctly--but it's been a number of months, I had a sort of similar problem with my Pixel C trying to flash a system image after unlocking the bootloader. This thread http://forum.xda-developers.com/pixel-c/help/fastboot-pixel-c-t3328635 was helpful. Selecting some generic Google driver in Win 10 did the trick, but I do not recall which driver.
Click to expand...
Click to collapse
Their drivers didn't help either.
Well, I'm getting a different error. I moved the USB cable to a different port on the PC. The first port was on a hub as the 3.0 ones built into the computer were in use. I only have one on the PC itself that's on the front. The others I have to crawl under the desk and behind the computer for--and those are in use to. The new error is that it didn't like the raw file size of the img files I tried. Seems i need something that's a multiple of the block size which is 4096.
I finally have Nougat on my device.
I've been trying to install TWRP and Magisk to the Razer phone for upwards of 3 days now. I cannot get anything to flash through fastboot to the phone no matter what I try. At one point I even said screw it and tried flashing the stock boot image back over to re-lock my bootloader, but no luck, still won't flash.
I was originally following this tutorial here but during the flashing of the boot image it kept failing. Then I tried following the "foolproof" guide found here
I either ended up with the error of "no such file or directory" or "too many links" or "unable to identify current slot". Did a ton of Googling but ultimately came up with no solutions.
I have Android SDK and development studio installed. I have the google drivers installed. I have the Razer phone drivers installed and I have ADB and Fastboot installed.
I have all the files I need on the SD card, and when I'm flashing everything I have the files I need placed in the same folder as the ADB\Fastboot files.
I have my bootloader unlocked, developer mode on and USB debugging enabled. I am using a USB Type A to Type C cable as recommended (made by Anker if it matters). I've tried all 3 USB ports on my laptop. I've even disabled Antivirus.
I have flashed many Android devices in the past and none have given me such a headache as this one. I'm even more ticked off that I can't even get the factory boot image back over to re-lock the bootloader after now realizing that I can't install Netflix anymore because they wen't and blocked installations for Rooted android users (for whatever ridiculous reason).
I will say that for whatever reason that when I go to open command prompt by using the shift+right click I only get the option to use Windows Powershell, not Command Prompt. I also have to put a .\ in front of every command I send. I'm unsure why, but I found no work around for it.
I'd like to try to get the TWRP and Magisk installed. I'm sure I can force Netflix to install over to the phone using another method.
Open to any suggestions!
FireGuy0723 said:
I've been trying to install TWRP and Magisk to the Razer phone for upwards of 3 days now.
Click to expand...
Click to collapse
I feel for you as when things don't work, like someone says they do, it's frustrating. I personally wouldn't be doing everything through power shell but would instead press Windows Key+R to bring up the "Run" dialog box then type "cmd" for command prompt. Trying to restore "command prompt here" to Windows 10 seems stupidly hidden. I'm just not sure if using powershell is messing with your progress.
Second thought is that your Razer phone drivers may not be installed correctly. For me I spent days/hours with my main PC, I then tried another PC and got my phone flashed in minutes. What would happen is that I could send "adb" commands without issue but some of the "fastboot" commands were not working. So at the critical times when it's trying to flash the different portions of our phone, some of them were successful while the others were giving little errors here and there.
I spent a lot of time updating my adb and fastboot commands to newer ones because it seems every time you download someones resources you get a different version. Also the more phones you have owned the more times you have installed specific USB drivers for those phones and they are now hanging around messing things up. There are programs such as USBDeview that will allow you to uninstall those old drivers. For me I had HP drivers from an old tablet, OnePlus drivers, LG drivers, etc.
Munk0 said:
I feel for you as when things don't work, like someone says they do, it's frustrating. I personally wouldn't be doing everything through power shell but would instead press Windows Key+R to bring up the "Run" dialog box then type "cmd" for command prompt. Trying to restore "command prompt here" to Windows 10 seems stupidly hidden. I'm just not sure if using powershell is messing with your progress.
Second thought is that your Razer phone drivers may not be installed correctly. For me I spent days/hours with my main PC, I then tried another PC and got my phone flashed in minutes. What would happen is that I could send "adb" commands without issue but some of the "fastboot" commands were not working. So at the critical times when it's trying to flash the different portions of our phone, some of them were successful while the others were giving little errors here and there.
I spent a lot of time updating my adb and fastboot commands to newer ones because it seems every time you download someones resources you get a different version. Also the more phones you have owned the more times you have installed specific USB drivers for those phones and they are now hanging around messing things up. There are programs such as USBDeview that will allow you to uninstall those old drivers. For me I had HP drivers from an old tablet, OnePlus drivers, LG drivers, etc.
Click to expand...
Click to collapse
I've been messing with it today a bunch. I am back to following the "foolproof" guide and this time I have completely uninstalled all my old drivers for anything android or USB or ADB related and reinstalled everything.
All commands work, I am using command prompt now.
What I am getting hung up on now is even after pushing all three files to the SD card, I run the command "fastboot flash boot twrp-3.2.1-0-cheryl.img && fastboot reboot" and it bounces back with " Failed: Write to device failed (no such file or directory)"
I've double checked the file names numerous times. I have no idea what I am doing wrong now. I have tried the command "fastboot boot twrp-3.2.1-0-cheryl.img" as stated in the other tutorial and it bounces back with "failed to identify current slot".
So I'm making progress at least. I'm trying to follow the first set of instructions listed in the fool proof guide but still no luck. I also tried the "clean method" listed below on that guide and that one doesn't work either. Apparently the Fool Proof guide thinks I'm a fool!
FireGuy0723 said:
What I am getting hung up on now is even after pushing all three files to the SD card, I run the command "fastboot flash boot twrp-3.2.1-0-cheryl.img && fastboot reboot" and it bounces back with " Failed: Write to device failed (no such file or directory)"
Click to expand...
Click to collapse
I believe that when you run "fastboot flash boot twrp-3.2.1-0-cheryl.img" you are pushing the file called "twrp-3.2.1-0-cheryl.img" that is sitting on your PC's C: or whichever drive you are currently sitting in to the Razer Phone. So make sure the file is in the same directory as where you are running that command. This will then transfer it to the Razer and will reboot into TWRP.
But after you reboot into TWRP you will want to flash the version you have sitting within your SD card to the "recovery" partition. That way it is permanent.
Munk0 said:
I believe that when you run "fastboot flash boot twrp-3.2.1-0-cheryl.img" you are pushing the file called "twrp-3.2.1-0-cheryl.img" that is sitting on your PC's C: or whichever drive you are currently sitting in to the Razer Phone. So make sure the file is in the same directory as where you are running that command. This will then transfer it to the Razer and will reboot into TWRP.
But after you reboot into TWRP you will want to flash the version you have sitting within your SD card to the "recovery" partition. That way it is permanent.
Click to expand...
Click to collapse
I was finally able to get the phone to accept a flash! I ended up saying screw it and dug a old laptop out, fresh install of windows and installed all the proper drivers onto it.
It worked almost flawlessly. It was able to correctly send the twrp.img file and the phone was able to boot into twrp which is about as far as I got. As it was attempting to load twrp it would "crash" the screen would flash twice and try rebooting back to TWRP.
What ended up happening was it got stuck in a boot loop trying to boot into TWRP. (I haven't even installed TWRP.zip yet, just tried booting the .img file).
I couldn't get the phone to boot to the system anymore. I thought I had a nice $600 paperweight on my hands.
I finally got the phone to go back into the boot loader and flashed all the factory stuff back on and relocked the bootloader. So right now I'm 100% back to stock.
I'm not sure what went wrong in the boot up of the twrp.img file. I'd like to try again but I'm kinda getting sick of wiping the phone Everytime something goes wrong.
Sent from my Phone using Tapatalk
I'm wanting to get TWRP / Magisk on my Razer too, but see too many bootloop stories after attempting to flash TWRP.... making me nervous ha ha.
Sorry, not much help, but hope you get it sorted...
Peace
chris5s said:
I'm wanting to get TWRP / Magisk on my Razer too, but see too many bootloop stories after attempting to flash TWRP.... making me nervous ha ha.
Sorry, not much help, but hope you get it sorted...
Peace
Click to expand...
Click to collapse
I had mine in boot loop, I was able to get it out pretty easily. If your able to get the phone into the bootloader (I did using a fastboot command while it was in a boot loop) you can just execute the script provided by Razer and it does the rest. Took about 10 minutes and I had factory everything back on the phone. Relocked the bootloader after and done, phone fixed.
Sent from my Phone using Tapatalk
FireGuy0723 said:
I had mine in boot loop, I was able to get it out pretty easily. If your able to get the phone into the bootloader (I did using a fastboot command while it was in a boot loop) you can just execute the script provided by Razer and it does the rest. Took about 10 minutes and I had factory everything back on the phone. Relocked the bootloader after and done, phone fixed.
Sent from my Phone using Tapatalk
Click to expand...
Click to collapse
In my case I actually had to flash the stock boot.img from the May 2018 stock OS. Then I was able to use Razers guide to flash stock again. I haven't locked my bootloader since I still want to give it a try again. But I want to find a reliable way of rooting and then unrooting in case I want to do so in the feature.
So far I haven't found said documentation.
Installed Magisk v17.1 via TWRP loaded in fastboot boot (not fastboot flash boot ie not permanently installed) and so far all seems well. No boot loops when restarting...
Peace
Below are the things I had done before the phone when completely bricked (Cant access bootloader/recovery). The phone just stuck on razer logo with powered by android. Is my mistake to set the active slot B after flashing the stock factory image which cause the phone unable to boot into bootloader/recovery. Plug into pc and device manager does not show Android device anymore. Is there anyway to set the active slot to A?:silly:
lloyd1006 said:
Below are the things I had done before the phone when completely bricked (Cant access bootloader/recovery). The phone just stuck on razer logo with powered by android. Is my mistake to set the active slot B after flashing the stock factory image which cause the phone unable to boot into bootloader/recovery. Plug into pc and device manager does not show Android device anymore. Is there anyway to set the active slot to A?:silly:
Click to expand...
Click to collapse
Is your boot-loader fully unlocked and is your computer setup to use fastboot and adb with all drivers installed?
Assuming yes
Make sure you download the factory image
https://developer.razerzone.com/raze...actory-images/
Download the latest TWRP image https://dl.twrp.me/cheryl
Take ONLY the boot.img file from the factory image
I guess you can put the whole thing but you only need the boot.img
anyway put the boot.img file on an external SD card and put it on your phone
now boot into fastboot mode, this is how, make sure your phone is turned completly off
Plug in your original USB C cable into your computer BUT NOT INTO YOUR PHONE (not yet)
Hold the volume down button (ONLY) and while your holding volume down plug in your USB-C cable
type fastboot devices and make sure you can see the device
If not it means your Adb/Fastboot is not installed correctly, I reccomend getting the latest version from https://developer.android.com/studio/releases/platform-tools
Ive tried older versions that do not work.
Anyway assuming you can get to fastboot mode
type in
fastboot flash boot twrp-3.2.1-0-cheryl.img && fastboot reboot
If successful, you should now be in a TEMP version of TWRP this did not actully flash twrp and thats not the goal here im just trying to help you out of your brick
so in TWRP go to install, install image, then select the boot.img you put on your sdcard (you might need to change storage to sdcard first)
now click reboot and STOP dont reboot, look and youll see your slots, youll probably be in slot B, change to slot A then select bootloader and once again type: fastboot flash boot twrp-3.2.1-0-cheryl.img && fastboot reboot click reboot and make sure you are in slot A, assuming yes once again go to install, install image, and install boot.img to slot A.
Now from here it shouldn't matter the slot your in, in theory you should now be able to boot back your device in any slot.
is there an easier way to do this? Probably...but that's how i know.
Now look...I don't know what lead to this event i'm going on the assumption that the only thing that you did was switch to slot B but if it was other factors like formatting or flashing things my instructions may not work for you.
majicmazo said:
Is your boot-loader fully unlocked and is your computer setup to use fastboot and adb with all drivers installed?
Assuming yes
Make sure you download the factory image
https://developer.razerzone.com/raze...actory-images/
now boot into fastboot mode, this is how, make sure your phone is turned completly off
Plug in your original USB C cable into your computer BUT NOT INTO YOUR PHONE (not yet)
Hold the volume down button (ONLY) and while your holding volume down plug in your USB-C cable
type fastboot devices and make sure you can see the device
If not it means your Adb/Fastboot is not installed correctly, I reccomend getting the latest version from https://developer.android.com/studio/releases/platform-tools
Ive tried older versions that do not work.
Anyway assuming you can get to fastboot mode
.
Click to expand...
Click to collapse
try the flash all.bat in the factory image from razer if you did mess with the partitions or want a stock device
42o247 said:
try the flash all.bat in the factory image from razer if you did mess with the partitions or want a stock device
Click to expand...
Click to collapse
You responded to the wrong post lol I think that was meant for op not me
Also...I could be wrong but I assumed he tried that first when he said he flashed the stock image...hence why I made a different suggestion.
majicmazo said:
You responded to the wrong post lol I think that was meant for op not me
Also...I could be wrong but I assumed he tried that first when he said he flashed the stock image...hence why I made a different suggestion.
Click to expand...
Click to collapse
it was less of a response and more of a reference to what you had typed.
42o247 said:
it was less of a response and more of a reference to what you had typed.
Click to expand...
Click to collapse
Got you
No worries...
I'd still try my way first only because flashall.bat will erase everything there is a chance the phone can be restored without loosing data...Just a chance but worth a try.
Edit:
Although I see now he said he was trying to flash the stock factory image anyway so I guess data probably doesn't matter lol
majicmazo said:
Got you
No worries...
I'd still try my way first only because flashall.bat will erase everything there is a chance the phone can be restored without loosing data...Just a chance but worth a try.
Edit:
Although I see now he said he was trying to flash the stock factory image anyway so I guess data probably doesn't matter lol
Click to expand...
Click to collapse
you can edit the .bat file in notepad and throw a '#' in front of the erase userdata command to stop it.
42o247 said:
you can edit the .bat file in notepad and throw a '#' in front of the erase userdata command to stop it.
Click to expand...
Click to collapse
true enough I actually separately ran all the batch commands without the batch all file personally because the file was giving me error for some reason I actually still don't know why but everything succeeded when I ran each command separate but that's a whole another story
Any news on this? on the same boat. only shows qualcomm HS-USB QDLoader 9008
qualcomm HS-USB QDLoader 9008 on mine too.nobody can help send to razer probably only option.no methods anywhere on the net