Database Users

can't flash any ROM's - SD card problem

Can anyone extend some help to a TF300T n00b?
I flashed the unofficial CM10 Jellybean ROM to my tf300t, and since the storage isn't working I can't move another ROM or even the stock firmware file to my SD card to flash. So, basically I'm stuck on the unofficial CM10 for now...
posted here because I can't post in the actual developement thread

just connect the tablet to a pc and copy the rom to the tablet. I dont rember if windows sees the internal storage. If it dosent linux should or you can install adb and push the file to /sdcard from your computer.

go here and dl the prog:
http://www.google.de/url?sa=t&rct=j...sg=AFQjCNG5sMnAkUGOfTZHgHJLFBARtdiyPg&cad=rja
extract it
boot into tecovery.
open the prog
choose the rom you like and push it to your tablet.
It is not possible to do it when you are in system, cause you cant write anything to the internal space.

mikaole said:
go here and dl the prog:
http://www.google.de/url?sa=t&rct=j...sg=AFQjCNG5sMnAkUGOfTZHgHJLFBARtdiyPg&cad=rja
extract it
boot into tecovery.
open the prog
choose the rom you like and push it to your tablet.
It is not possible to do it when you are in system, cause you cant write anything to the internal space.
Click to expand...
Click to collapse
I couldn't get the fast ADB pusher to work, nor the actual ADB. Fast pusher said it succeeded a few times but I couldn't find the new ROM on my SD card in CWM.

http://forum.xda-developers.com/showthread.php?t=1680570
Check here it has instructions on how to setup and use adb

MegaNoob said:
http://forum.xda-developers.com/showthread.php?t=1680570
Check here it has instructions on how to setup and use adb
Click to expand...
Click to collapse
looks promising. I hadn't been attempting to push the files while the tablet was in recovery because adb wouldnt recognize the tab when it was in recovery. I don't have my tablet cable, but I will try tomorrow morning. Thanks again.

ljungberg3 said:
looks promising. I hadn't been attempting to push the files while the tablet was in recovery because adb wouldn't recognize the tab when it was in recovery. I don't have my tablet cable, but I will try tomorrow morning. Thanks again.
Click to expand...
Click to collapse
if adb doesn't recognize the pad when it's in recovery, the drivers may not be installed correctly

paedz718 said:
if adb doesn't recognize the pad when it's in recovery, the drivers may not be installed correctly
Click to expand...
Click to collapse
I installed the drivers exactly as the guide directed, then tried using regular ADB, which didnt work. So I tried to use the ADB fast push and it didn't work either, under the "information" tab on the fast adb program it says
"Failed to mount as R/W"
is this a problem?

I got files to push via ADB, installation was aborted on the stock rom
I will try to find another stock rom to flash and update you guys. thanks for all the help so far

Can you still get to fastboot mode?
---------- Post added at 10:53 PM ---------- Previous post was at 10:44 PM ----------
If yes, dl the latest. Asus. STOCK, extract the blob, put it in the Fastboot Folder and. Open cmd
cd to the fastboot directory and write
fastboot -i 0x0B05 flash system blob
This will flash stock.
Don't give up, when it's not working. Just rewrite and try again and again.
A, user in the German Forum needed 20 times till it finally run through.

mikaole said:
Can you still get to fastboot mode?
---------- Post added at 10:53 PM ---------- Previous post was at 10:44 PM ----------
If yes, dl the latest. Asus. STOCK, extract the blob, put it in the Fastboot Folder and. Open cmd
cd to the fastboot directory and write
fastboot -i 0x0B05 flash system blob
This will flash stock.
Don't give up, when it's not working. Just rewrite and try again and again.
A, user in the German Forum needed 20 times till it finally run through.
Click to expand...
Click to collapse
I was able to push and flash a stock firmware! thank god! haha, and thank you guys for all the help!

ljungberg3 said:
I was able to push and flash a stock firmware! thank god! haha, and thank you guys for all the help!
Click to expand...
Click to collapse
Np

So, much of the stuff in this and other threads has been a tremendous help. I did pretty much exactly what OP did in this thread http://forum.xda-developers.com/showthread.php?t=1779080.
That thread lead me to this one, as I was having trouble getting my computer to recognize the usb drivers. I was able to finally get ADB to see the tablet, however, when I go to push the stock rom, I get an error message of "Protocol Failure" in cmd.
Any ideas?
http://s12.postimage.org/unt8ag1vh/adbcmd.jpg
Created new thread as OP solved his problem.

[Q] How to flash a ROM through twrp adb sideload?

I flashed 1.2.5 Malladus on 12B OTA rooted for Verizon using twrp 2.6.3.3. When I booted the LG logo appears for a second and the screen turns black. Reading from a previous post Malladus wont boot if you're on 12B OTA. I can't boot my phone flashing this rom. I would like to adb sideload through twrp. I don't want to mess phone up to brick I'm a noob I don't have adb tools on my computer I wouldn't know where to place them.
Please help me with a step by step.
Thank you

atticustcx said:
I flashed 1.2.5 Malladus on 12B OTA rooted for Verizon using twrp 2.6.3.3. When I booted the LG logo appears for a second and the screen turns black. Reading from a previous post Malladus wont boot if you're on 12B OTA. I can't boot my phone flashing this rom. I would like to adb sideload through twrp. I don't want to mess phone up to brick I'm a noob I don't have adb tools on my computer I wouldn't know where to place them.
Please help me with a step by step.
Thank you
Click to expand...
Click to collapse
Hey man here's a link;
http://teamw.in/ADBSideload
If you need more help let me know..
.make sure that your enviromentals are set too so your PC can understand commands

RubbleTea said:
Hey man here's a link;
http://teamw.in/ADBSideload
If you need more help let me know..
.make sure that your enviromentals are set too so your PC can understand commands
Click to expand...
Click to collapse
I'm having trouble installing adb i'm following this guy I installed adb but when I open device manager I don't see adb.exe or fastboot in C:\Windows

atticustcx said:
I'm having trouble installing adb i'm following this guy I installed adb but when I open device manager I don't see adb.exe or fastboot in C:\Windows
Click to expand...
Click to collapse
OK hey so you have adb all set up and set in enviromentals right? And you have a ROM ready? And drivers installed? For ease of doing things rename the ROM "ROM" so it should be ROM.zip
---------- Post added at 12:10 PM ---------- Previous post was at 12:00 PM ----------
Once you have that done place the rom into the same folder as your adb.exe is.......now plug in your phone to PC a and have recovery open.....then go to advanced the click sideload ROM....then swipe....
..now open a command prompt...then type adb devices to heck if your device is shown....if it is go ahead and type" adb sideload ROM.zip" ...then wait til it finishes...then unplug from PC and flash the ROM.......if your driver won't show your device try koush universal drivers....sorry man I'm at work now

I had a similar issue and I was able to flash clean rom but I still reboot to twrp. Do I need to flash a boot image or something.?
from my Note Thrizzle

RubbleTea said:
OK hey so you have adb all set up and set in enviromentals right? And you have a ROM ready? And drivers installed? For ease of doing things rename the ROM "ROM" so it should be ROM.zip
---------- Post added at 12:10 PM ---------- Previous post was at 12:00 PM ----------
Once you have that done place the rom into the same folder as your adb.exe is.......now plug in your phone to PC a and have recovery open.....then go to advanced the click sideload ROM....then swipe....
..now open a command prompt...then type adb devices to heck if your device is shown....if it is go ahead and type" adb sideload ROM.zip" ...then wait til it finishes...then unplug from PC and flash the ROM.......if your driver won't show your device try koush universal drivers....sorry man I'm at work now
Click to expand...
Click to collapse
I don't have adb installed and environmentals. I don't have a ROM ready because I'm not sure which one is safe to flash over 12B OTA.
I only have LG drivers 2.11.1.0 installed. Every time I connect my phone it says to install drivers but it can't find VS980 drivers and says unsuccessful install

atticustcx said:
I don't have adb installed and environmentals. I don't have a ROM ready because I'm not sure which one is safe to flash over 12B OTA.
I only have LG drivers 2.11.1.0 installed. Every time I connect my phone it says to install drivers but it can't find VS980 drivers and says unsuccessful install
Click to expand...
Click to collapse
Try downloading a stock ROM with the ota should be one, and download koush universal drivers anyway.....for adb android SDK will have it and have instructions to setup....Google will help.....environment settings will make it so your computer understands adb commands...
---------- Post added at 01:39 PM ---------- Previous post was at 01:37 PM ----------
rawb123456 said:
I had a similar issue and I was able to flash clean rom but I still reboot to twrp. Do I need to flash a boot image or something.?
from my Note Thrizzle
Click to expand...
Click to collapse
So you flash a ROM and it goes to twrp, did you accept the ota with a custom recovery? For you might have to flash to stock image(there's a thread in general forum) but first try another rom

RubbleTea said:
Try downloading a stock ROM with the ota should be one, and download koush universal drivers anyway.....for adb android SDK will have it and have instructions to setup....Google will help.....environment settings will make it so your computer understands adb commands...
---------- Post added at 01:39 PM ---------- Previous post was at 01:37 PM ----------
So you flash a ROM and it goes to twrp, did you accept the ota with a custom recovery? For you might have to flash to stock image(there's a thread in general forum) but first try another rom
Click to expand...
Click to collapse
After trying for hours to get my drivers installed so my phone can be read by computer I gave up. I followed this http://forum.xda-developers.com/showthread.php?t=2448960 took my phone back to stock on 11A.

Error updating via OTA

Hi everyone,
I was trying to update via OTA to the latest version, but after downloading the update the tablet started updating itself and returned the Android dead droid error. It is important to highlight that I was rooted with KingRoot and removed it to apply OTA update. Any help would be appreciated

regular_ said:
Hi everyone,
I was trying to update via OTA to the latest version, but after downloading the update the tablet started updating itself and returned the Android dead droid error. It is important to highlight that I was rooted with KingRoot and removed it to apply OTA update. Any help would be appreciated
Click to expand...
Click to collapse
Am in the same situation. Waiting to hear back from Cameron Yan.

Looks like you might need to flash the 1.5 version via fastboot and go through each update iteration.

Yeah u might have to flash 1.5
Your Jide Ambassador is here!!!
---------- Post added at 12:45 PM ---------- Previous post was at 12:35 PM ----------
U can't just remove the rooting and think the update will be applied. Each updated is like a layered cake placed on its foundation. When you rooted you messed with pliers of stability for future layered updates and the updates check where they are suppose to be place. If something is missing or out of place you are going to get an error.
Your Jide Ambassador is here!!!

regular_ said:
Hi everyone,
I was trying to update via OTA to the latest version, but after downloading the update the tablet started updating itself and returned the Android dead droid error. It is important to highlight that I was rooted with KingRoot and removed it to apply OTA update. Any help would be appreciated
Click to expand...
Click to collapse
I had the same experience and ended up flashing 1.5 and then going through the automatic updates. Took a little while, but the update installed and I am back to stock for the time being.

regular_ said:
Hi everyone,
I was trying to update via OTA to the latest version, but after downloading the update the tablet started updating itself and returned the Android dead droid error. It is important to highlight that I was rooted with KingRoot and removed it to apply OTA update. Any help would be appreciated
Click to expand...
Click to collapse
Same issue for me I am scared about the root by King root : not the cleaner tool ...

iceheart3131 said:
Same issue for me I am scared about the root by King root : not the cleaner tool ...
Click to expand...
Click to collapse
If you have rooted, the only way to get OTA that I have found is to reflash version 1.5 and then have the normal updates be applied.
I have done this and then rerooted after I have applied the current update.

tomlogan1 said:
If you have rooted, the only way to get OTA that I have found is to reflash version 1.5 and then have the normal updates be applied.
I have done this and then rerooted after I have applied the current update.
Click to expand...
Click to collapse
Ok , but where can I found this 1.5 version please ? there is no Download section on Jide webpage ...
Ok 1.5 version and toutos available on JIDE webpage

I have an issue with fastboot : adb devices found the tablet but fastboot devices found nothing ... My fastboot is functionnal with my edge 7, nexus 5x and android TV ... So it must be something specific to do on Utra Tablet ... But I don't know what

iceheart3131 said:
I have an issue with fastboot : adb devices found the tablet but fastboot devices found nothing ... My fastboot is functionnal with my edge 7, nexus 5x and android TV ... So it must be something specific to do on Utra Tablet ... But I don't know what
Click to expand...
Click to collapse
Probably obvious, but to you have USB debugging enabled?

tomlogan1 said:
Probably obvious, but to you have USB debugging enabled?
Click to expand...
Click to collapse
Yes i have... I have try to connecter other Devices to be sure but the issue is only with Ultra Tablet

iceheart3131 said:
Yes i have... I have try to connecter other Devices to be sure but the issue is only with Ultra Tablet
Click to expand...
Click to collapse
Try connecting via USB and then run a command like adb devices and then unplug the tablet and plug it back in. I remember a security (RSA?) prompt that you have to accept in order for this to work. Worth a try.

tomlogan1 said:
Probably obvious, but to you have USB debugging enabled?
Click to expand...
Click to collapse
Sorry for the long delay (Holydays !!)... Yes USB debug is enabled .
---------- Post added at 05:15 PM ---------- Previous post was at 05:02 PM ----------
tomlogan1 said:
Try connecting via USB and then run a command like adb devices and then unplug the tablet and plug it back in. I remember a security (RSA?) prompt that you have to accept in
Still not available with fastboot
Click to expand...
Click to collapse

iceheart3131 said:
Sorry for the long delay (Holydays !!)... Yes USB debug is enabled .
---------- Post added at 05:15 PM ---------- Previous post was at 05:02 PM ----------
tomlogan1 said:
Try connecting via USB and then run a command like adb devices and then unplug the tablet and plug it back in. I remember a security (RSA?) prompt that you have to accept in
Still not available with fastboot
Click to expand...
Click to collapse
When I use adb I get the device SN. When I use fastboot devices I get nothing. If I then adb reboot bootloader I get the attached response.
Click to expand...
Click to collapse

I follow this tuto (How to flash Remix OS 1.5 from Jide) :
To flash the ROM, please download the file from the following link and follow the below instructions.
https://drive.google.com/open?id=0B...1FVVR3RkRya29sakQ3SEdVbXU5cUg0YTIzUnNfUTRWMTA
Installing image files using fastboot
1. Make sure your Remix has working fastboot (http://wiki.cyanogenmod.org/w/Fastboot) and adb (http://wiki.cyanogenmod.org/w/Adb).
2. Download images
The information of the image zip file:
Images Zip File Name: SK1WG.zip
md5: f993e49ff5f0bfac169dcb62b2e820e8
sha1: 6f9b364f46680ff1294ff2eb9e3fe9aba6592d5a
3. Unzip the downloaded zip file ( SK1WG.zip ) and go to the folder
4. Connect the Remix to the computer via USB.
5. Make sure the fastboot binary is in your PATH (http://wiki.cyanogenmod.org/w/Doc:_paths) or that you place the recovery image in the same directory as fastboot.
6. Open a terminal on your PC and reboot the device into fastboot mode by typing adb reboot bootloader or by using the hardware key combination for your device while it is powered off.
7. Once the device is in fastboot mode, verify your PC sees the device by typing fastboot devices
-If you don't see your device serial number, and instead see "", fastboot is not configured properly on your machine. See fastboot (http://wiki.cyanogenmod.org/w/Doc:_fastboot_intro) documentation for more info.
-If you see "no permissions fastboot", make sure your UDEV (http://wiki.cyanogenmod.org/w/UDEV) rules are setup correctly.
8. Clean the existing data by entering the following command: fastboot -w
9. Flash images onto your device by entering the following three commands:
-fastboot flash system system.img
-fastboot flash recovery recovery.img
-fastboot flash boot boot.img
10. Once the flash completes successfully, run the following command to reboot the device into recovery to verify the installation.
-fastboot reboot
Click to expand...
Click to collapse
I can reboot with adb command
Code:
adb reboot bootloader
my tablet reboot and this menu is available :
but fasboot command seems still without effect , i have try to launch fastboot protocol in the menu : no effect . fastboot devices doens't return any ID . I have try to install complete suite android studio to have ALL tools ( and fastboot ) but it seems the same isssue .

iceheart3131 said:
I follow this tuto (How to flash Remix OS 1.5 from Jide) :
I can reboot with adb command
Code:
adb reboot bootloader
my tablet reboot and this menu is available :
but fasboot command seems still without effect , i have try to launch fastboot protocol in the menu : no effect . fastboot devices doens't return any ID . I have try to install complete suite android studio to have ALL tools ( and fastboot ) but it seems the same isssue .
Click to expand...
Click to collapse
Maybe a driver from previous devices? I'm using the Android naked drivers and they work with the tablet as well as my Android phone.

Victory !!!! until now i have tried with Windows 10 and it doesn't works . With a friend we have follow the sme process on Ubuntu and it works perfectly ! Thanks tomlogan1 for your patience and your support , I appreciate

iceheart3131 said:
Victory !!!! until now i have tried with Windows 10 and it doesn't works . With a friend we have follow the sme process on Ubuntu and it works perfectly ! Thanks tomlogan1 for your patience and your support , I appreciate
Click to expand...
Click to collapse
Congratulations! Now you can be ready when custom ROMs become available. Your presistance paid off.

Any new update about new BlankFlash?

as you guys know June update killed a lot of athenes and same thing happened with my athene. and the BlankFlash is also not working after this update. so is there any update for blankFlash, post a link here.

no updated blankflash ... we should wait la
:crying::crying::crying::crying::crying::crying::crying::crying::crying::crying::crying::crying::crying::crying::crying::crying::crying::crying::crying:
siddhesh9146 said:
as you guys know June update killed a lot of athenes and same thing happened with my athene. and the BlankFlash is also not working after this update. so is there any update for blankFlash, post a link here.
Click to expand...
Click to collapse
sad..... my athne toooooo dead .... we should hope get updated soon... most of moto g4 plus athene dead ...... i dont who gonna make new updated blankflash to recover....... thanks in advance who make new one..... or any other solution... already a post is here but it didnot work out at allll..... pls someone geeks solve this
...... ISSUES LOTS OF MOTO G4 PLUS DEADDD..... EVERYTHING TRIED NO LUCK[ATHENE]XT1643]:crying::crying::crying::crying::crying::crying::crying::crying::crying::crying::crying:

tamil2692 said:
:crying::crying::crying::crying::crying::crying::crying::crying::crying::crying::crying::crying::crying::crying::crying::crying::crying::crying::crying:
sad..... my athne toooooo dead .... we should hope get updated soon... most of moto g4 plus athene dead ...... i dont who gonna make new updated blankflash to recover....... thanks in advance who make new one..... or any other solution... already a post is here but it didnot work out at allll..... pls someone geeks solve this
...... ISSUES LOTS OF MOTO G4 PLUS DEADDD..... EVERYTHING TRIED NO LUCK[ATHENE]XT1643]:crying::crying::crying::crying::crying::crying::crying::crying::crying::crying::crying:
Click to expand...
Click to collapse
Nothin

new blankflash HERE : https://forum.xda-developers.com/moto-g4-plus/how-to/moto-g4-plus-hardbrick-solved-guide-t3657761

Does not enter recovery or boot up system
as soon as the blankflash file is updated i flashed it and worked
then i flashed updated gpt and bootloader
then i tried to enter recovery mode but its not entering
and also when i unplug usb cable it is turning off
then i flashed stock rom
but still recovery and system booting are not working,enters only to fastboot that too on charging.
guyss please help me it means a lot to me.Thanks in advance

Geek_manoj said:
as soon as the blankflash file is updated i flashed it and worked
then i flashed updated gpt and bootloader
then i tried to enter recovery mode but its not entering
and also when i unplug usb cable it is turning off
then i flashed stock rom
but still recovery and system booting are not working,enters only to fastboot that too on charging.
guyss please help me it means a lot to me.Thanks in advance
Click to expand...
Click to collapse
Are you mentioning that your device only boots to fastboot now? If you press 'start', does that boot to system or not?
Which stock ROM did you flash, and can you confirm if the flash worked? How did your device brick in the first place?

echo92 said:
Are you mentioning that your device only boots to fastboot now? If you press 'start', does that boot to system or not?
Which stock ROM did you flash, and can you confirm if the flash worked? How did your device brick in the first place?
Click to expand...
Click to collapse
he didn't flashed stock rom yet, he is only trying to flash custom roms zips from recovery. someone please him that this won't work in this case:cyclops:

Blank Flash Files Moto G4 Plus
Yes I have the correct blank flash files for Moto G4 Plus. I was used it on my device XT1643 and it is working.

echo92 said:
Are you mentioning that your device only boots to fastboot now? If you press 'start', does that boot to system or not?
Which stock ROM did you flash, and can you confirm if the flash worked? How did your device brick in the first place?
Click to expand...
Click to collapse
yes,the device boots only to fastboot that too only when charged.if i press start that doesn't boot to system.I flashed "ATHENE_NPJS25.93-14-8_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip".I bricked by doing softare update after reflashing stock rom.it also doesnt enter recovery
---------- Post added at 02:09 AM ---------- Previous post was at 02:05 AM ----------
siddhesh9146 said:
he didn't flashed stock rom yet, he is only trying to flash custom roms zips from recovery. someone please him that this won't work in this case:cyclops:
Click to expand...
Click to collapse
sorry if you dont understand.but i flash stock rom "ATHENE_NPJS25.93-14-8_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip" in stock recovery.if u could help me please let me know.thanks in advance

Geek_manoj said:
yes,the device boots only to fastboot that too only when charged.if i press start that doesn't boot to system.I flashed "ATHENE_NPJS25.93-14-8_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip".I bricked by doing softare update after reflashing stock rom.it also doesnt enter recovery
---------- Post added at 02:09 AM ---------- Previous post was at 02:05 AM ----------
sorry if you dont understand.but i flash stock rom "ATHENE_NPJS25.93-14-8_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip" in stock recovery.if u could help me please let me know.thanks in advance
Click to expand...
Click to collapse
I knew that, that file was for flashing in fastboot mode
but you flashed in recovery

Geek_manoj said:
yes,the device boots only to fastboot that too only when charged.if i press start that doesn't boot to system.I flashed "ATHENE_NPJS25.93-14-8_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip".I bricked by doing softare update after reflashing stock rom.it also doesnt enter recovery
---------- Post added at 02:09 AM ---------- Previous post was at 02:05 AM ----------
sorry if you dont understand.but i flash stock rom "ATHENE_NPJS25.93-14-8_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip" in stock recovery.if u could help me please let me know.thanks in advance
Click to expand...
Click to collapse
As siddhesh9146 had mentioned, the Athene stock ROM cannot be flashed in stock recovery, it is not a flashable zip file. You need a computer and ADB set up, extract the zip on your computer and use the flashing commands in the fastboot ROM thread to flash a stock ROM.
Until you've flashed the stock ROM, I'm not even sure if you have stock recovery, or a stock system on your device. The supplied blank flash does not appear to have a functioning recovery included with it.

echo92 said:
As siddhesh9146 had mentioned, the Athene stock ROM cannot be flashed in stock recovery, it is not a flashable zip file. You need a computer and ADB set up, extract the zip on your computer and use the flashing commands in the fastboot ROM thread to flash a stock ROM.
Until you've flashed the stock ROM, I'm not even sure if you have stock recovery, or a stock system on your device. The supplied blank flash does not appear to have a functioning recovery included with it.
Click to expand...
Click to collapse
I m sorry.I must have described in a better way.I actually mean that i used computer extracted the firmware and then i ran oem_flash,which is the actual way i suppouse in fastboot mode(i ommited for fastboot as stock recovery in previous post,sorry).but i dont know why it still doesnt enter recovery or enter into system or work without plug.i even tried flashing updated gpt.bin and bootloader files again followed by the rom,but noting happened
---------- Post added at 04:24 PM ---------- Previous post was at 04:19 PM ----------
echo92 said:
As siddhesh9146 had mentioned, the Athene stock ROM cannot be flashed in stock recovery, it is not a flashable zip file. You need a computer and ADB set up, extract the zip on your computer and use the flashing commands in the fastboot ROM thread to flash a stock ROM.
Until you've flashed the stock ROM, I'm not even sure if you have stock recovery, or a stock system on your device. The supplied blank flash does not appear to have a functioning recovery included with it.
Click to expand...
Click to collapse
siddhesh9146 said:
I knew that, that file was for flashing in fastboot mode
but you flashed in recovery
Click to expand...
Click to collapse
hey,i ommited in the post telling that i did it in recovery(sorry for that)actually it doesnt enter recovery,which i already mentioned.thanks for being concerned

Geek_manoj said:
I m sorry.I must have described in a better way.I actually mean that i used computer extracted the firmware and then i ran oem_flash,which is the actual way i suppouse in fastboot mode(i ommited for fastboot as stock recovery in previous post,sorry).but i dont know why it still doesnt enter recovery or enter into system or work without plug.i even tried flashing updated gpt.bin and bootloader files again followed by the rom,but noting happened
---------- Post added at 04:24 PM ---------- Previous post was at 04:19 PM ----------
hey,i ommited in the post telling that i did it in recovery(sorry for that)actually it doesnt enter recovery,which i already mentioned.thanks for being concerned
Click to expand...
Click to collapse
So, you booted your device to the bootloader screen (not to recovery), connected your device to your computer, and you've flashed using the OEM_flash script, and yet you're unable to reboot to recovery?
Sounds like your stock ROM flash did not work the first time, leaving you without a recovery or a system. Try the following just to confirm:
1) Ensure your adb folder contains the extracted NPJS25.93-14-8 stock ROM (all the files), should be about 2 GB for the stock ROM. Also confirm that the OEM flash script is in the same location (so your adb folder should have the stock ROM, the flash script and the adb and fastboot.exe and adb.dlls)
2)Reboot your device to the bootloader (power down, then press the power and volume down keys to boot to bootloader) and connect your device to your computer.
3)In the adb terminal, type 'fastboot devices', without the quotes. If communicating, you should see your device respond with its serial number.
4)If communicating, run the OEM flash script again.
5)If your device does not boot properly, then reboot to bootloader.
5a)Copy each of the commands from the script (you can open the script in a text editor) and paste them in the adb terminal window and run each one by pressing Enter on your keyboard. You should see the command report [OKAY] if it's flashed. Any errors, let us know, that might point more accurately to what might be going on.
As an aside, this is one of the reasons why downgrading isn't a good idea....

echo92 said:
So, you booted your device to the bootloader screen (not to recovery), connected your device to your computer, and you've flashed using the OEM_flash script, and yet you're unable to reboot to recovery?
Sounds like your stock ROM flash did not work the first time, leaving you without a recovery or a system. Try the following just to confirm:
1) Ensure your adb folder contains the extracted NPJS25.93-14-8 stock ROM (all the files), should be about 2 GB for the stock ROM. Also confirm that the OEM flash script is in the same location (so your adb folder should have the stock ROM, the flash script and the adb and fastboot.exe and adb.dlls)
2)Reboot your device to the bootloader (power down, then press the power and volume down keys to boot to bootloader) and connect your device to your computer.
3)In the adb terminal, type 'fastboot devices', without the quotes. If communicating, you should see your device respond with its serial number.
4)If communicating, run the OEM flash script again.
5)If your device does not boot properly, then reboot to bootloader.
5a)Copy each of the commands from the script (you can open the script in a text editor) and paste them in the adb terminal window and run each one by pressing Enter on your keyboard. You should see the command report [OKAY] if it's flashed. Any errors, let us know, that might point more accurately to what might be going on.
As an aside, this is one of the reasons why downgrading isn't a good idea....
Click to expand...
Click to collapse
Hey,thanks for bothering.But,it didnt work.i have got no error.But still mobile enters only fastboot that too when charging( only fastboot again).

I tried to clear cache memory by booting my g4 plus in recovery mode. the phone hanged up and switched off now unable to boot. tried the blank flash file to update but the same is not working. Can any one help !!

Software update cannot be assigned and TWRP cannot be installed!

Hey, When trying to update software with stock rom and recovery, I cannot update with "installation failed" error. So I wanted to do other things with fastboot, but with fastboot only the bootloader can be unlocked. Errors I get while installing TWRP:
FAILED (remote: Requested download size is more than max allowed)
or
stuck on "sending recovery.img"
Officially I'm stuck in the Oreo 8.1 version. No matter how much research I did on this issue, I could not reach a solution. What I tried are the following
- All resets that can be done on the phone.
- Delete and reinstall ADB
- Refreshing rom and recovery files
- adb sideload
Please help.

Try this command..
fastboot erase recovery
fastboot erase cache
fastboot flash recovery (file name).img
fastboot reboot bootloader
Their select recovery and boot to recovery mod..
If this not helps you... Please use toolkit..
---------- Post added at 02:59 AM ---------- Previous post was at 02:39 AM ----------
gokhanhaskilit said:
Hey, When trying to update software with stock rom and recovery, I cannot update with "installation failed" error. So I wanted to do other things with fastboot, but with fastboot only the bootloader can be unlocked. Errors I get while installing TWRP:
FAILED (remote: Requested download size is more than max allowed)
or
stuck on "sending recovery.img"
Officially I'm stuck in the Oreo 8.1 version. No matter how much research I did on this issue, I could not reach a solution. What I tried are the following
- All resets that can be done on the phone.
- Delete and reinstall ADB
- Refreshing rom and recovery files
- adb sideload
Please help.
Click to expand...
Click to collapse
Fastboot boot (filename).img.
It will boot into recovery flash recovery from the recovery.
1)Try to use another usb port in your Pc ,
2)If you still getting those errors reinstall the adb driver may help,
3)Try to clear cache from the existing stock recovery
And execute the command
4)Try renaming the file name (smaller) it's a myth:laugh:
I hope it will fix your problem:good:

[email protected] said:
Try this command..
fastboot erase recovery
fastboot erase cache
fastboot flash recovery (file name).img
fastboot reboot bootloader
Their select recovery and boot to recovery mod..
If this not helps you... Please use toolkit..
---------- Post added at 02:59 AM ---------- Previous post was at 02:39 AM ----------
Fastboot boot (filename).img.
It will boot into recovery flash recovery from the recovery.
1)Try to use another usb port in your Pc ,
2)If you still getting those errors reinstall the adb driver may help,
3)Try to clear cache from the existing stock recovery
And execute the command
4)Try renaming the file name (smaller) it's a myth:laugh:
I hope it will fix your problem:good:
Click to expand...
Click to collapse
fastboot erase recovery
fastboot erase cache
When you enter the commands above, it starts but doesn't finish. So it is not Finished. No results were obtained in other operations.
What else can you suggest about this?

gokhanhaskilit said:
fastboot erase recovery
fastboot erase cache
When you enter the commands above, it starts but doesn't finish. So it is not Finished. No results were obtained in other operations.
What else can you suggest about this?
Click to expand...
Click to collapse
Have you tried fastboot boot recovery.img

[email protected] said:
Have you tried fastboot boot recovery.img
Click to expand...
Click to collapse
I tried but failed. Can we talk on Telegram?

gokhanhaskilit said:
I tried but failed. Can we talk on Telegram?
Click to expand...
Click to collapse
Hey. You can't flash anything via fastboot on locked bootloader.
The reason you can't update is that your phone doesn't have vendor partition. Recovery can't find it. That's why it stops. You have to flash Pie stock first (preferably the release that introduced vendor partition (treble), then you can upgrade to Android Q.

gokhanhaskilit said:
I tried but failed. Can we talk on Telegram?
Click to expand...
Click to collapse
I'm quite sure it is the problem with your pc
Is it a desktop or laptop?
Windows version?
Did you know how to differentiate between USB 2.0 and 3.0?
I too didn't have any idea about what you are dealing with
After I made a lot of research on Google
This problem is happening because of the usb 3.0
The adb driver can't deal with USB 3.0 so you need to use usb 2.0 or else buy a USB Hub 2.0
Or use a different system, I mean use your friend pc(high success rate:fingers-crossed
And our conversation must be continued here because in future if someone with the same issue can't read our personal telegraph chat
I'm also looking for a solution for your problem
---------- Post added at 04:35 PM ---------- Previous post was at 04:26 PM ----------
gokhanhaskilit said:
I tried but failed. Can we talk on Telegram?
Click to expand...
Click to collapse
optimumpro said:
Hey. You can't flash anything via fastboot on locked bootloader.
The reason you can't update is that your phone doesn't have vendor partition. Recovery can't find it. That's why it stops. You have to flash Pie stock first (preferably the release that introduced vendor partition (treble), then you can upgrade to Android Q.
Click to expand...
Click to collapse
He already unlocked the bootloader

[email protected] said:
I'm quite sure it is the problem with your pc
Is it a desktop or laptop?
Windows version?
Did you know how to differentiate between USB 2.0 and 3.0?
I too didn't have any idea about what you are dealing with
After I made a lot of research on Google
This problem is happening because of the usb 3.0
The adb driver can't deal with USB 3.0 so you need to use usb 2.0 or else buy a USB Hub 2.0
Or use a different system, I mean use your friend pc(high success rate:fingers-crossed
And our conversation must be continued here because in future if someone with the same issue can't read our personal telegraph chat
I'm also looking for a solution for your problem
---------- Post added at 04:35 PM ---------- Previous post was at 04:26 PM ----------
He already unlocked the bootloader
Click to expand...
Click to collapse
Yes, I guess the problem is in the relationship between ADB and USB 3.0 connectivity.
Desktop PC
Windows 10 Pro 1909
I don't know much about the differences between USB 2.0 and 3.0 but I know the blue ones in the USB port are 3.0 and the black ones are 2.0. Although I have tried all USB ports on the computer, the result does not change. (The problem with USB 2.0 and USB 3.0 is different)
- Minimal ADB and several drivers have been downloaded to this PC for Xioami device. (QUALCOMM, XIOAMI, GOOGLE AND MORE) Is it because they conflict? I tried yesterday on another computer but I am getting the same issue. So I guess the problem isn't just with the PC.
You are right about Telegram. I've tried most operations with my lock on and off. The result does not change.

[email protected] said:
I'm quite sure it is the problem with your pc
Is it a desktop or laptop?
Windows version?
Did you know how to differentiate between USB 2.0 and 3.0?
I too didn't have any idea about what you are dealing with
After I made a lot of research on Google
This problem is happening because of the usb 3.0
The adb driver can't deal with USB 3.0 so you need to use usb 2.0 or else buy a USB Hub 2.0
Or use a different system, I mean use your friend pc(high success rate:fingers-crossed
And our conversation must be continued here because in future if someone with the same issue can't read our personal telegraph chat
I'm also looking for a solution for your problem
---------- Post added at 04:35 PM ---------- Previous post was at 04:26 PM ----------
He already unlocked the bootloader
Click to expand...
Click to collapse
gokhanhaskilit said:
Yes, I guess the problem is in the relationship between ADB and USB 3.0 connectivity.
Desktop PC
Windows 10 Pro 1909
I don't know much about the differences between USB 2.0 and 3.0 but I know the blue ones in the USB port are 3.0 and the black ones are 2.0. Although I have tried all USB ports on the computer, the result does not change. (The problem with USB 2.0 and USB 3.0 is different)
- Minimal ADB and several drivers have been downloaded to this PC for Xioami device. (QUALCOMM, XIOAMI, GOOGLE AND MORE) Is it because they conflict? I tried yesterday on another computer but I am getting the same issue. So I guess the problem isn't just with the PC.
You are right about Telegram. I've tried most operations with my lock on and off. The result does not change.
Click to expand...
Click to collapse
Also fastboot screen says "PRODUCT NAME: qc referance phone". It used to write my device serial number. So I guess I might have messed up something while installing the final ROM. or Drivers ...

gokhanhaskilit said:
Also fastboot screen says "PRODUCT NAME: qc referance phone". It used to write my device serial number. So I guess I might have messed up something while installing the final ROM. or Drivers ...
Click to expand...
Click to collapse
If you want to update your phone use a unbrick tool
(Android pie unbrick tool is available)
https://forum.xda-developers.com/oneplus-5t/how-to/op5t-collection-unbrick-tools-t3898890
This may help to replace your old Oxygen os bootloader with latest one so this may help to fix your issue ,we must hope this one will fix
( Do it at your own risk I am not responsible if anything goes wrong)

[email protected] said:
If you want to update your phone use a unbrick tool
(Android pie unbrick tool is available)
https://forum.xda-developers.com/oneplus-5t/how-to/op5t-collection-unbrick-tools-t3898890
This may help to replace your old Oxygen os bootloader with latest one so this may help to fix your issue ,we must hope this one will fix
( Do it at your own risk I am not responsible if anything goes wrong)
Click to expand...
Click to collapse
OK. I will process 9.0.11 version firmware with OREO 8.1 version installed now, with cache removal tool. Isn't that a problem?

gokhanhaskilit said:
OK. I will process 9.0.11 version firmware with OREO 8.1 version installed now, with cache removal tool. Isn't that a problem?
Click to expand...
Click to collapse
What do you mean cache removal tool?

[email protected] said:
What do you mean cache removal tool?
Click to expand...
Click to collapse
Never mind. A translation error has occurred. My OnePlus 5 device is not recognized by the MSM Download Tool (Unbrick Tool). What should I do?

gokhanhaskilit said:
Never mind. A translation error has occurred. My OnePlus 5 device is not recognized by the MSM Download Tool (Unbrick Tool). What should I do?
Click to expand...
Click to collapse
I switched the device to the PIE version. I tried to flash Nougat rom to try it out right away. However, like in Oreo, the loading screen stops for a while and throws it back to the main screen. Presumably the problem with ADB persists.
I guess our problem is more than unbrick tool ..

gokhanhaskilit said:
I switched the device to the PIE version. I tried to flash Nougat rom to try it out right away. However, like in Oreo, the loading screen stops for a while and throws it back to the main screen. Presumably the problem with ADB persists.
I guess our problem is more than unbrick tool ..
Click to expand...
Click to collapse
I did TWRP with Fastboot. Stable. But I am unable to flash any OxygenOS software with Stock Recovery...

gokhanhaskilit said:
OK. I will process 9.0.11 version firmware with OREO 8.1 version installed now, with cache removal tool. Isn't that a problem?
Click to expand...
Click to collapse
gokhanhaskilit said:
I did TWRP with Fastboot. Stable. But I am unable to flash any OxygenOS software with Stock Recovery...
Click to expand...
Click to collapse
I don't understand what you talking about
Did you mean you have successfully installed TWRP?.
Did you installed oos9.11 using the unbrick tool successfully?
---------- Post added at 03:41 PM ---------- Previous post was at 03:37 PM ----------
gokhanhaskilit said:
I did TWRP with Fastboot. Stable. But I am unable to flash any OxygenOS software with Stock Recovery...
Click to expand...
Click to collapse
Try using the new adb driver
Uninstall older driver and install this:
http://www.mediafire.com/file/a4d0p5uvebc0xwp/file