Related
So I completely bricked my tablet, cant even get my PC to recognize the tablet, and the only screen i have up is the Google and the unlock padlock. and if i try a hard reset, all i get is android on his back and the red triangle. I have decided to buy a used motherboard, I see from ifixit.com that they are easy to repair, will this solve my dilema? I found used mobo's on ebay, made sure to get the correct one, is this the answer to not buying a new tablet?
My nexus 7 lte is in the exact same state(that's why I've posted here instead of starting new thread)...by using nrt to try updating to marshmellow as per site's instructions...wondering if anyone can offer a solution???
(bought at google play almost 2 years ago and they already sent me a free refurb replacement...but I still wanna try getting the old one going before sending it back if possible...worth a try before buying a replacement mobo)
here some details of my situation:
ran this on my nexus 7 2013 lte...failed on the first try...tried again..it wiped everything and then failed on install...now I have bootloader (accessible by volume down and power button simultaneously) only and no functional recovery(get the android with red triangle and asterisk when I select Recovery)...the only Android device listed in Device manager is Android Bootloader Interface.
If I start from fastboot mode:
gives a driver failed to load error from windows" and also, now in Device Manager my Android Device Listed changed from "Android Bootloader Interface" to "Android Composite ADB Interface", as well, there is now a Portable Device listed also but it's the driver that failed to load I guess "MTP USB Device" with a yellow asterisk.
If I run the flash-all.bat in the image download that the NRT got on the first attempt, everything goes fine until I get to "sending system"...this fails with unknown data transfer error...
when I download the latest image from developers google.com and extract it I get just one big file with no extension...shouldn't there be a bunch of files including a flashhall.bat file?
^Yes, inside the main image zip is the bootloader (+ radio in your case) and another zip of the actual partition images.
Run fastboot devices from the bootloader just to be sure it's detected. If not uninstall all traces from your pc and start fresh.
Flash the new bootloader, reboot bootloader, flash the radio, reboot bootloader then flash each .img individually with fastboot. Don't use any toolkits.
You should get the "OKAY" after flashing each image. Is it only system that fails? Do you get the okay with boot and recovery? If system only I don't know.
ronf1011 said:
So I completely bricked my tablet, cant even get my PC to recognize the tablet, and the only screen i have up is the Google and the unlock padlock. and if i try a hard reset, all i get is android on his back and the red triangle. I have decided to buy a used motherboard, I see from ifixit.com that they are easy to repair, will this solve my dilema? I found used mobo's on ebay, made sure to get the correct one, is this the answer to not buying a new tablet?
Click to expand...
Click to collapse
The android with the red triangle with exclamation is what happens with stock recovery, you need to press power, volume up and down quickly all at the same time to get in. Usually takes a few tries. If you can get into recovery you could factory reset. It could be another problem though. You have to describe what you previously did to it if you really wan't help.
rma
Thanks for the reply...was never able to get the system image to load...google play is supposed to reemburse me once they receive my original nexus 7 (already got a pristine refurb from them..updated to marshmellow..will be staying away from NRT with this one...)
Thanks again for the reply and suggestions!
system image can't be written
Exactly the same happened to me. After a successful update to MM with Wugfresh's NRT 2.0.5 (with no root) I tried to root my device with 2.0.6 which was released in the meantime.
But that failed because NRT thinks my bootloader is locked, while in fastboot mode I can see that it is unlocked. With fastboot commands I can relock and re-unlock but for NRT it makes no difference.
It seemed to me that a manual reflash of bootloader (FLO-04.05), kernel, cache, system and data should solve this, but no way. The flashall. bat reports a write error of the system.img. A direct fastboot flash system system.img command leads to FAILED (remote: unknown chunk type).
I couldn't find any information about chunk types. I am afraid that somewhere in the process the partitioning was affected. Is that a possibility and can anything be done to fix this? Or are there other solutions for the chunk type error?
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
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
Recently I had some trouble with my pixel 2 as my magisk root had magically disappeared, because of this I decided to fix it and re-flash magisk using fastboot to flash the modified boot.img. Since then my Pixel 2 XL wont turn on, I attempted to also flash twrp as well but was met with only a frozen splash screen. Since then I've tried to re-flash the entire OS that was downloaded from the google database and yes for the right version (taimen). I've auto tried to restore it using the android flash tool available through google online as well with limited success.
So here's my current situation. Right now turning on the phone takes me straight to the bootloader screen, attempting to hold volume up or anything other button combinations does nothing but take me to the bootloader screen. Attempting to use the android flash tool now turns the phone off the instant the pc detects it, trying to flash manually with fastboot (the latest version yes) does not work and even a simply "fastboot devices" returns "???????????? fastboot" which then reboots the phone. I'm kinda at a loss of what to do here, i've had softbricks on other phones before but have always managed to fix it one way or another but this one has sadly beaten me
p.s. I've already tried 3 different cables
tcxufatime said:
Recently I had some trouble with my pixel 2 as my magisk root had magically disappeared, because of this I decided to fix it and re-flash magisk using fastboot to flash the modified boot.img. Since then my Pixel 2 XL wont turn on, I attempted to also flash twrp as well but was met with only a frozen splash screen. Since then I've tried to re-flash the entire OS that was downloaded from the google database and yes for the right version (taimen). I've auto tried to restore it using the android flash tool available through google online as well with limited success.
So here's my current situation. Right now turning on the phone takes me straight to the bootloader screen, attempting to hold volume up or anything other button combinations does nothing but take me to the bootloader screen. Attempting to use the android flash tool now turns the phone off the instant the pc detects it, trying to flash manually with fastboot (the latest version yes) does not work and even a simply "fastboot devices" returns "???????????? fastboot" which then reboots the phone. I'm kinda at a loss of what to do here, i've had softbricks on other phones before but have always managed to fix it one way or another but this one has sadly beaten me
p.s. I've already tried 3 different cables
Click to expand...
Click to collapse
https://forum.xda-developers.com/pixel-2-xl/help/pixel-2-bricked-t3889296 on the last page there are possible solutions to try. Have you tried a different port?
Also, as you can use fastboot in the bootmenu, download the twrp.img (link) to your adb.exe directory and use the adb shell to type 'fastboot boot twrp.img'.
If that works you could go to the reboot option and change the A/B slot to the other version used.
Through twrp - tools, you can also select adb mode to allow your PC adb shell to use 'adb sideload ota.zip'.
Use the ota.zip version of your current version which you download here.