Hello Everyone,
I was using lineage os 15.0 and found some bugs so wanted to change the rom... So i wiped everything except internal storage and flashed viper os final version but it did not complete its flashing process, it was stuck on 100% for a very long time so i rebooted to recovery and tried again, faced the same issue again and again, then i planned to try some other roms and i noticed that i cant flash any of the roms via twrp nor 7.0 nougat nor 8.0 oreo roms.
I tried flashing stock rom via both toolkit and via adb both gave me error: command write failed (unknown error) or else command write failed(no error). I erased my data partition and tried again but still no use.. I restored a twrp backup from the forum but it does not boot whenever i click on reboot to system it boots to bootloader..
Guys please help!!! :crying::crying::crying::crying:
Try to reformat your file system and try the flash again. Worst case, you can fastboot back to the stock images
Karlinski said:
Try to reformat your file system and try the flash again. Worst case, you can fastboot back to the stock images
Click to expand...
Click to collapse
if you can get to twrp you can plug it into your computer and it should read it as storage *(if you have drivers installed) if you have sd card. Put rom you want on sd card boot twrp wipe and profit hope this helps if not let me know. Ill do what I can
* if not install this on your computer, after you install it uninstall it and the moto drivers will stay
https://motorola-global-portal.custhelp.com/app/answers/prod_detail/a_id/79106/p/30,75,27, <---- CLICK HERE
Karlinski said:
Try to reformat your file system and try the flash again. Worst case, you can fastboot back to the stock images
Click to expand...
Click to collapse
tried that but it did not work
orvon.freeman said:
if you can get to twrp you can plug it into your computer and it should read it as storage *(if you have drivers installed) if you have sd card. Put rom you want on sd card boot twrp wipe and profit hope this helps if not let me know. Ill do what I can
* if not install this on your computer, after you install it uninstall it and the moto drivers will stay
https://motorola-global-portal.custhelp.com/app/answers/prod_detail/a_id/79106/p/30,75,27, <---- CLICK HERE
Click to expand...
Click to collapse
i can access the twrp but i cant successfully flash any rom it gets stuck at 100% and does not get ahead
this happens when i flash a stock rom
it gives me this error whenever i try to flash anything
Fastboot devices. See if you get anything there
If not
1) you are not on the bootloader screen (NOT TWRP)
OR
2)You do not have drivers installed/bad port/bad cable etc.
Karlinski said:
Fastboot devices. See if you get anything there
If not
1) you are not on the bootloader screen (NOT TWRP)
OR
2)You do not have drivers installed/bad port/bad cable etc.
Click to expand...
Click to collapse
If it shows up in device manager and you have installed the moto drivers update driver browse then pick from a list and look for anything adb or moto
Related
I wanted to flash PSX Pure Speed Experiment 4.4 rom but I got the " Failed. E:Error executing updated binary in zip '/sdcard/psx_mako_kk_v1..." message mentioned in the OP. I tried the solution posted there, which was to download a patched multirom version of TWRP recovery using the flashify app from the play store. This all seemed to work out fine, and I booted into recovery to flash the rom. Now, this could just be due to my ignorance because the version of TWRP I flashed is 2.6.3.2 (I originally had 2.3.0.1 I believe), but when I wiped my phone, then went to install, there wasnt anything listed in the root of my sd card folder. I tried rebooting TWRP and when I tried again it listed a folder named TWRP there but nothing else. Subsequent reboots yielded nothing. At this point I dont even want to flash the 4.4 rom, I just want to reflash my old CM10.1 rom and be done with it. Any help is greatly appreciated
sropedia said:
I wanted to flash PSX Pure Speed Experiment 4.4 rom but I got the " Failed. E:Error executing updated binary in zip '/sdcard/psx_mako_kk_v1..." message mentioned in the OP. I tried the solution posted there, which was to download a patched multirom version of TWRP recovery using the flashify app from the play store. This all seemed to work out fine, and I booted into recovery to flash the rom. Now, this could just be due to my ignorance because the version of TWRP I flashed is 2.6.3.2 (I originally had 2.3.0.1 I believe), but when I wiped my phone, then went to install, there wasnt anything listed in the root of my sd card folder. I tried rebooting TWRP and when I tried again it listed a folder named TWRP there but nothing else. Subsequent reboots yielded nothing. At this point I dont even want to flash the 4.4 rom, I just want to reflash my old CM10.1 rom and be done with it. Any help is greatly appreciated
Click to expand...
Click to collapse
Reboot the phone and then connect it to your PC and check to see if the PSX ROM file is there. If not, redownload the file and save it in the root of the SDcard. As for the TWRP folder that has nothing in it, delete it. Then try to boot into recovery and flash the PSX ROM, also just making sure that the checkbox for "System" in mount section is unchecked. BTW, is your a multiROM patch for TWRP?
taodan said:
Reboot the phone and then connect it to your PC and check to see if the PSX ROM file is there. If not, redownload the file and save it in the root of the SDcard. As for the TWRP folder that has nothing in it, delete it. Then try to boot into recovery and flash the PSX ROM, also just making sure that the checkbox for "System" in mount section is unchecked. BTW, is your a multiROM patch for TWRP?
Click to expand...
Click to collapse
Thanks for the reply, but when I try to mount my phone, my computer acknowledges that I've connected a device with a sound, but it doesnt show up as a storage device. when I go into devices and printers I can find my phone but it only shows up as an ADB device
And yes to answer your question it is a multiROM patch for TWRP
sropedia said:
Thanks for the reply, but when I try to mount my phone, my computer acknowledges that I've connected a device with a sound, but it doesnt show up as a storage device. when I go into devices and printers I can find my phone but it only shows up as an ADB device
Click to expand...
Click to collapse
Do you have "USB debugging" checkbox, in Developer Options, checked? Also, try reboot your PC and reconect your phone to see whether it shows up as a storage device.
sropedia said:
I wanted to flash PSX Pure Speed Experiment 4.4 rom but I got the " Failed. E:Error executing updated binary in zip '/sdcard/psx_mako_kk_v1..." message mentioned in the OP. I tried the solution posted there, which was to download a patched multirom version of TWRP recovery using the flashify app from the play store. This all seemed to work out fine, and I booted into recovery to flash the rom. Now, this could just be due to my ignorance because the version of TWRP I flashed is 2.6.3.2 (I originally had 2.3.0.1 I believe), but when I wiped my phone, then went to install, there wasnt anything listed in the root of my sd card folder. I tried rebooting TWRP and when I tried again it listed a folder named TWRP there but nothing else. Subsequent reboots yielded nothing. At this point I dont even want to flash the 4.4 rom, I just want to reflash my old CM10.1 rom and be done with it. Any help is greatly appreciated
Click to expand...
Click to collapse
ok when you wiped your rom did you just do a factory reset or a internal sd wipe as well. Also you should try and use 2.6.3.3. Also you have to remember where it is you save your stuff or place everything in 1 specific folder. May I suggest you start over with downloading rom and putting it in a folder created by you like !Flash... using "!" will ensure its the first folder you see.
Also your error also can be fixed by simply rebooting your recovery as its been what I used to fix that error
playya said:
ok when you wiped your rom did you just do a factory reset or a internal sd wipe as well. Also you should try and use 2.6.3.3. Also you have to remember where it is you save your stuff or place everything in 1 specific folder. May I suggest you start over with downloading rom and putting it in a folder created by you like !Flash... using "!" will ensure its the first folder you see.
Also your error also can be fixed by simply rebooting your recovery as its been what I used to fix that error
Click to expand...
Click to collapse
I did a full wipe like I usually do. I would use a different version of TWRP if I knew how to change it from within TWRP. I have a follder titled ROOT that I keep all my ROMs and whatnot in, but the problem is that literally none of the folders in my internal storage are showing up from within TWRP. I can't check to see if USB debugging is enabled because theres no operating system on my phone; like I said, I did a full wipe. The fact that no folders show up also means that it doesnt recognize the backup I had. My computer still won't recognize my phone as a storage device after mounting in TWRP. Maybe I'm doing something in the wrong order? Restarting my computer didn't help.I really need to get my phone working on ANY ROM, and I appreciate all the help so far
This isn't my phone. It was just running the stock OS with root. I think what happened is that an update from tmobile was released, and got installed, which corrupted the ROM/OS. The only backup it has is a couple of months old. I've tried wiping data/system/caches and factory resets which did not work. I've also tried restoring from the backup; just system, then both data and system, and no results.
Currently it has no ROM on it that I can install.
No matter what I do it always reboots back to TWRP. It has TWRP 2.6.3.2
I've tried to mount the SD card from the Mount menu so I can push a ROM to it, which doesn't work.
I've tried using ADB sideload but it doesn't seem to start, and I'm not able to see the device from command line with 'adb devices'
I've tried using the LG PC Suite, but it also cannot detect the device.
Please help, thanks!
brickwall99 said:
This isn't my phone. It was just running the stock OS with root. I think what happened is that an update from tmobile was released, and got installed, which corrupted the ROM/OS. The only backup it has is a couple of months old. I've tried wiping data/system/caches and factory resets which did not work. I've also tried restoring from the backup; just system, then both data and system, and no results.
Currently it has no ROM on it that I can install.
No matter what I do it always reboots back to TWRP. It has TWRP 2.6.3.2
I've tried to mount the SD card from the Mount menu so I can push a ROM to it, which doesn't work.
I've tried using ADB sideload but it doesn't seem to start, and I'm not able to see the device from command line with 'adb devices'
I've tried using the LG PC Suite, but it also cannot detect the device.
Please help, thanks!
Click to expand...
Click to collapse
sounds like you dont have lg drivers installed. can get them from the lg g2 official website.
freebee269 said:
sounds like you dont have lg drivers installed. can get them from the lg g2 official website.
Click to expand...
Click to collapse
Is that what would prevent side load from working?
I've installed the drivers previously, and can use adb/USB storage with my LG G2.
brickwall99 said:
Is that what would prevent side load from working?
I've installed the drivers previously, and can use adb/USB storage with my LG G2.
Click to expand...
Click to collapse
you said you see no adb devices, this usually means the adb drivers are not installed. no adb drivers = no sideload. also make sure you are in twrp when you are trying to use adb. also i'd recommend updating to twrp 2.6.3.3 from the official twrp site, it's much better than 2.6.3.2. also if you are using an outdated adb.exe that will give you adb problems. can get the latest from android website.
freebee269 said:
you said you see no adb devices, this usually means the adb drivers are not installed. no adb drivers = no sideload. also make sure you are in twrp when you are trying to use adb. also i'd recommend updating to twrp 2.6.3.3 from the official twrp site, it's much better than 2.6.3.2. also if you are using an outdated adb.exe that will give you adb problems. can get the latest from android website.
Click to expand...
Click to collapse
Well, I have no way to transfer any files to the phone, so I can't install the new recovery. All I need to do is be able to push a ROM file to the phone, I think, so I can install it.
I am using adb sideload from recovery. I'm not aware of another location to do so. It just sits at the prompt saying starting sideload...
brickwall99 said:
Well, I have no way to transfer any files to the phone, so I can't install the new recovery. All I need to do is be able to push a ROM file to the phone, I think, so I can install it.
I am using adb sideload from recovery. I'm not aware of another location to do so. It just sits at the prompt saying starting sideload...
Click to expand...
Click to collapse
that's because you have no adb connection. no connection = no pushing files. that's why i said you need to get adb working first.
I installed the universal adb driver and now 'adb devices' does show the device, and I'm transferring the ROM with adb sideload 'filename', so hopefully this will work.
Thanks!
brickwall99 said:
I installed the universal adb driver and now 'adb devices' does show the device, and I'm transferring the ROM with adb sideload 'filename', so hopefully this will work.
Thanks!
Click to expand...
Click to collapse
good news. hope you get up and running now. still update your twrp.
freebee269 said:
good news. hope you get up and running now. still update your twrp.
Click to expand...
Click to collapse
Okay I got the ROM transferred and I have installed it successfully.
Using this one: http://forum.xda-developers.com/showthread.php?t=2598361
But when I reboot it goes straight to recovery.
A factory reset fails. I'm only able to advanced wipe of system/data, also it fails when I wipe cache or dalvik.
So I've tried wiping system/data, then installing the ROM again, and it just reboots straight back to recovery.
I sideloaded TWRP 2.6.3.5 for tmobile. Verified it shows 2.6.3.5 TWRP now. I'll try to sideload/install the ROM again.
Edit: When trying to factory reset it says failed to mount cache.
Okay so I have successfully installed the ROM with TWRP 2.6.3.5 and when I reboot it still goes straight into recovery.
What next?
Thanks
Edit: Is there perhaps something wrong with the bootloader, or what? I'm thinking part of the issue is because I can't mount or wipe cache/dalvik?
I'm in the exact same position with the d800. Stuck in twrp. I think we need to sideload a working boot.img. Idk. I was working on it all night reading everything I could about adb because although I had the lg drivers and my PC recognized my phone was connected it would give me a driver error. Thus I couldn't use the flash tool. Can you get to download mode?
from my Note Thrizzle
rawb123456 said:
I'm in the exact same position with the d800. Stuck in twrp. I think we need to sideload a working boot.img. Idk. I was working on it all night reading everything I could about adb because although I had the lg drivers and my PC recognized my phone was connected it would give me a driver error. Thus I couldn't use the flash tool. Can you get to download mode?
from my Note Thrizzle
Click to expand...
Click to collapse
How do you start download mode?
I was able to mount cache now, after unchecking format setting (use rm instead of -rf), but after doing factory reset and advanced wipe (everything except internal storage), then installing ROM, it still reboots straight back into recovery. Damn.
Any luck? I tried flashing CM11 on TWRP 2.6.3.2 (per XDA instructions) and it failed. Now I am stuck in recovery and can't ADB new recovery
brickwall99 said:
How do you start download mode?
I was able to mount cache now, after unchecking format setting (use rm instead of -rf), but after doing factory reset and advanced wipe (everything except internal storage), then installing ROM, it still reboots straight back into recovery. Damn.
Click to expand...
Click to collapse
I accidentally wiped the OS from advanced wipe option. How do I get my phone to work again. I tried to operate adb sideload from recovery but it failed. I have downloaded the stock rom but I do not know how to install it.
Please help.
Thanks.
Kalaxy said:
I accidentally wiped the OS from advanced wipe option. How do I get my phone to work again. I tried to operate adb sideload from recovery but it failed. I have downloaded the stock rom but I do not know how to install it.
Please help.
Thanks.
Click to expand...
Click to collapse
Just flash it from custom recovery, so download it into ur phone go to recovery and simply flash it and all should be good.
Sent from my Nexus 6P using Tapatalk
Exiwolfman said:
Just flash it from custom recovery, so download it into ur phone go to recovery and simply flash it and all should be good.
Sent from my Nexus 6P using Tapatalk
Click to expand...
Click to collapse
How do I download it to my phone if I cannot boot into it. Is there any way I can copy a zip file (rom) onto the phone's internal memory.?
Your phone should boot into recovery, so as long as it goes on and boots all u do u is use ur pc to move file over and flash it...
Sent from my Nexus 6P using Tapatalk
Kalaxy said:
How do I download it to my phone if I cannot boot into it. Is there any way I can copy a zip file (rom) onto the phone's internal memory.?
Click to expand...
Click to collapse
Boot into bootloader (hold power and system on), flash the though recovery through adb, mount your .zip,, flash your .zip through recovery. Sorry if that doesn't make sense, I've been drinking with the roommates, lol.
Edit: if that doesn't work, send me an IM and I will help you in the morning
Sent from my Huawei Nexus 6P using XDA Labs
Which state is your phone in right now? Is it bootlooping or in recovery?
Sent from my HTC 10 using Tapatalk
The same thing happened to me also! The whole /data (incl. sdcard) partition went corrupt (showed up in TWRP as eemc instead of ext4) & the /vendor failed to mount.
First I had to repair the /data partition (unfortunately the data was lost, as it repaired to a blank partition). I ended up having to go home (was at work at the time) & hook the phone up to the PC & download the ROM & transfer it onto the sdcard. I'm not entirely sure why/how this happened, but I believe it was because a corrupt vendor IMG. Although that theory doesnt include why the /data partition corrupted, it only explains why the /vendor partition failed to mount.
Fastboot flash system system.img
?
removed
I have the same issue. The problem is, that my computer will not recognize the phone in bootloader mode or in recovery mode(MTP enabled). How can install usb drivers without being able to boot into phone OS???? I've tried Nexus Toolkit with no success. Please help?
Have a look here how to load in bootloader, flash, etc.
http://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928
So I did the same thing. I'm sitting in TWRP right now but have nothing on the phone. Will I be able to reboot from TWRP into the bootloader and just use the flash-all command to get my phone to boot back up, then just go through the process of custom recovery again?
Basically I'm worried about leaving twrp without an OS. I didn't wipe bootloader did I? Also, I tried to download a ROM and just drag it to internal memory, but I can't seem to add anything to the internal memory.
dbroer91884 said:
So I did the same thing. I'm sitting in TWRP right now but have nothing on the phone. Will I be able to reboot from TWRP into the bootloader and just use the flash-all command to get my phone to boot back up, then just go through the process of custom recovery again?
Basically I'm worried about leaving twrp without an OS. I didn't wipe bootloader did I? Also, I tried to download a ROM and just drag it to internal memory, but I can't seem to add anything to the internal memory.
Click to expand...
Click to collapse
Hi... Just boot into recovery and reflash system.img from the factory image of your choice in bootloader with fastboot. Also flash the vendor image from the same factory image. Done...
Or reflash the whole package with flash all (manually is better imho). But you'll waisted time... Let your phone reboot into Android and you'll have your internal storage back.
5.1 said:
Hi... Just boot into recovery and reflash system.img from the factory image of your choice in bootloader with fastboot. Also flash the vendor image from the same factory image. Done...
Or reflash the whole package with flash all (manually is better imho). But you'll waisted time... Let your phone reboot into Android and you'll have your internal storage back.
Click to expand...
Click to collapse
Thats what I thought. JUst wanted to make sure I could get into bootloader still
dbroer91884 said:
So I did the same thing. I'm sitting in TWRP right now but have nothing on the phone. Will I be able to reboot from TWRP into the bootloader and just use the flash-all command to get my phone to boot back up, then just go through the process of custom recovery again?
Basically I'm worried about leaving twrp without an OS. I didn't wipe bootloader did I? Also, I tried to download a ROM and just drag it to internal memory, but I can't seem to add anything to the internal memory.
Click to expand...
Click to collapse
Yes TWRP has a reboot to bootloader option available. So you can access fastboot via bootloader to flash the necessary images. Just don't forget to re flash TWRP image again in case the stock recovery image was flashed beforehand.
The odd thing was that I did choose that option to boot to bootloader in twrp and it didn't work. I ended up having to reboot to bootloader manually. Not a big deal. All is working now, but thought that was interesting.
Kalaxy said:
I accidentally wiped the OS from advanced wipe option. How do I get my phone to work again. I tried to operate adb sideload from recovery but it failed. I have downloaded the stock rom but I do not know how to install it.
Click to expand...
Click to collapse
Exactly which partitions did you wipe? system? data? Internal Storage (userdata)? all of the above? Hopefully you did not wipe userdata (all your stuff). Were you on a stock ROM? You should be able to d/l the Google image from the same build you were on, extract system and data and fastboot flash those. Don't flash userdata. All your stuff should be there. Follow the tutorial on how to set up fastboot and selectively flash partitions.
---------- Post added at 06:49 AM ---------- Previous post was at 06:44 AM ----------
This thread got hijacked at least 3 times. Let's hope OP can find his way back.
pocholo36 said:
I have the same issue. The problem is, that my computer will not recognize the phone in bootloader mode or in recovery mode(MTP enabled). How can install usb drivers without being able to boot into phone OS???? I've tried Nexus Toolkit with no success. Please help?
Click to expand...
Click to collapse
Try this Hope you get solution to your problem of installing adb and fastboot tools in the correct manner.
I just by mistake deleted my internal storage.
I have TWRP, how do i put the ROM on there and flash it? Someone please help.
Thanks
Ok I am sure I did this before without any problem, but this time, through TWRP on the NRTK, I installed Magisk, no problems, and then went back to install the SU with the zip file in TWRP again and then on the reboot it freezes on the Google startup screen.
I didnt even want to install the SU zip, but when I ran SU after Magisk installed after reboot, SU gave an error, so I decided to install SU from TWRP.
Did I do something wrong there, so I dont repeat the same error next time?
And how do I get out of this locked state?
I've tried wiping all cache to factory reset without deleting internal storage data... I am hoping I dont have to delete and wipe everything and start all over. I did not have a chance to eve install TiB yet.
Dathaeus said:
Ok I am sure I did this before without any problem, but this time, through TWRP on the NRTK, I installed Magisk, no problems, and then went back to install the SU with the zip file in TWRP again and then on the reboot it freezes on the Google startup screen.
I didnt even want to install the SU zip, but when I ran SU after Magisk installed after reboot, SU gave an error, so I decided to install SU from TWRP.
Did I do something wrong there, so I dont repeat the same error next time?
And how do I get out of this locked state?
I've tried wiping all cache to factory reset without deleting internal storage data... I am hoping I dont have to delete and wipe everything and start all over. I did not have a chance to eve install TiB yet.
Click to expand...
Click to collapse
Flash the stock boot.img from the image/rom you were using before this and reboot. You will have to re-root (properly) afterwards, but your phone should boot up. If you use Magisk, you don't need SU, and vice versa. Use only one method to root.
v12xke said:
Flash the stock boot.img from the image/rom you were using before this and reboot. You will have to re-root (properly) afterwards, but your phone should boot up. If you use Magisk, you don't need SU, and vice versa. Use only one method to root.
Click to expand...
Click to collapse
Hmmm ya I prob should have posted that SU error message instead of what I did, douche move.
But how do I flash the boot.img... I have an original copy of it on my PC... can I somehow while in TWRP on the phone connect to my PC via cable and run commands from my PC in CMD and execute that old boot.img flash? Or is there a location in the stock Nexus already I can use? Because there is no file in the root drive after I did the soft wipe.
P.S. Everything I have done so far has not deleted my whole storage, yet.... not sure if that is necessary at this point bec it seems reflashing the boot.img wipes absolutely everything again? If I have to it is what it is... just painful when this happens before I could get TiB running... unless my Nandroid backup file I have will restore and work after I do this?
Dathaeus said:
Hmmm ya I prob should have posted that SU error message instead of what I did, douche move.
But how do I flash the boot.img... I have an original copy of it on my PC... can I somehow while in TWRP on the phone connect to my PC via cable and run commands from my PC in CMD and execute that old boot.img flash? Or is there a location in the stock Nexus already I can use? Because there is no file in the root drive after I did the soft wipe.
Click to expand...
Click to collapse
While in TWRP you have MTP (file transfer) so you can add files to your device. Transfer the boot.img over to your device via MTP and then use TWRP to flash. Just be sure to select flash IMAGE rather than ZIP. Lesson here is when you get back up and running, install fastboot/adb and make sure it is working well and communicating with your PC. Then you can learn how to use it. This would take literally 5 seconds to flash via fastboot (device in bootloader mode).
---------- Post added at 01:29 PM ---------- Previous post was at 01:26 PM ----------
Dathaeus said:
P.S. Everything I have done so far has not deleted my whole storage, yet.... not sure if that is necessary at this point bec it seems reflashing the boot.img wipes absolutely everything again? If I have to it is what it is... just painful when this happens before I could get TiB running... unless my Nandroid backup file I have will restore and work after I do this?
Click to expand...
Click to collapse
NO, flashing boot.img will not delete any of your files. It will only write to the boot partition. If using fastboot the command is fastboot flash boot boot.img
v12xke said:
While in TWRP you have MTP (file transfer) so you can add files to your device. Transfer the boot.img over to your device via MTP and then use TWRP to flash. Just be sure to select flash IMAGE rather than ZIP. Lesson here is when you get back up and running, install fastboot/adb and make sure it is working well and communicating with your PC. Then you can learn how to use it. This would take literally 5 seconds to flash via fastboot (device in bootloader mode).
NO, flashing boot.img will not delete any of your files. It will only write to the boot partition. If using fastboot the command is fastboot flash boot boot.img
Click to expand...
Click to collapse
Yep I actually had those platform files already, and yes the MTP was active there, I just never tried that before so didnt know it was even a possibility or the right way.
So I tried via flashing my very old boot.img and also the one from
https://forum.xda-developers.com/nexus-6p/general/stock-modified-boot-img-regular-root-t3306684
via TWRP "Install" via image install (not zip) and to the "boot partition"
and no change, same stuck on Google logo screen.
I tried the fastboot command from CMD and it says
< waiting for any device >
and doesnt do anything. I had it on the default TWRP menu screen.... I waited over 20 min although I know it shouldnt take near that long, just in case.
My bootloader is unlocked BTW, I dont want to assume anything here.
You need help getting the latest fastboot/adb binaries working on your PC. So many tutorials on how to do this. Ugh.
Dathaeus said:
Yep I actually had those platform files already, and yes the MTP was active there, I just never tried that before so didnt know it was even a possibility or the right way.
So I tried via flashing my very old boot.img and also the one from
https://forum.xda-developers.com/nexus-6p/general/stock-modified-boot-img-regular-root-t3306684
via TWRP "Install" via image install (not zip) and to the "boot partition"
and no change, same stuck on Google logo screen.
I tried the fastboot command from CMD and it says
< waiting for any device >
and doesnt do anything. I had it on the default TWRP menu screen.... I waited over 20 min although I know it shouldnt take near that long, just in case.
My bootloader is unlocked BTW, I dont want to assume anything here.
Click to expand...
Click to collapse
Which OS security patch were you running? Flash the system (to the system partition in TWRP) and boot images (again) from the 6P factory image of the same name:
https://developers.google.com/android/images?hl=en
See if this helps.
Sent from my Nexus 5X using Tapatalk
v12xke said:
You need help getting the latest fastboot/adb binaries working on your PC. So many tutorials on how to do this. Ugh.
Click to expand...
Click to collapse
Not sure what you mean... I JUST did all that when I redid my phone completely back to factory etc etc.... just few weeks ago and then again on my new replacement. But just to be sure, I downloaded all those files again today and it didnt make any difference.
Still stuck on the
< waiting for any device >
I have to be missing some other step or something else is wrong here.
FYI not sure if this matters but when phone boots to recovery there's a red error message
"Unable to mount storage"
but it loads to TWRP fine anyways.
SlimSnoopOS said:
Which OS security patch were you running? Flash the system (to the system partition in TWRP) and boot images (again) from the 6P factory image of the same name:
https://developers.google.com/android/images?hl=en
Click to expand...
Click to collapse
Yep thats what I been doing.....
So the CMD command still doesnt work, which I think is weird in itself... and when I try to install from recovery, it goes through the whole process, both boot.img and system.img, but then it freezes on the Google logo again, so no change.
Sorry I am not sure what security patch, I just got this used from eBay, and one thing, not sure if this means anything, it says its a beta version or something and that message came up all the time when I rebooted when the phone was working.
Do I need to suck it up and redo the whole phone again........ :/
Unlocked Mediapad M3 wifi 713, damaged file system showing 0 storage, managed to get TWRP installed via fastboot, but TWRP is unable to change/repair any partition. I've tried to use "fastboot format:ext4 userdata" but I get the "remote: command not allowed" error.
Is there some way to use fastboot commands? Or some terminal command from TWRP?
thanks, jf
Bro have you unlocked the bootloader and it would be very helpfull to know how you corrupted the data partion,it could be solved maybe if you enter the second recovery (erecovery) and click on download lastest firmware install or so , then after its done with the installition it will probably not boot click power and volume down wait, do it some times until you get to the bootloader and unlock it, after factory reset it should boot but first explain a little more about your issue we dont want to srew your device up
qlue4e said:
Bro have you unlocked the bootloader and it would be very helpfull to know how you corrupted the data partion,it could be solved maybe if you enter the second recovery (erecovery) and click on download lastest firmware install or so , then after its done with the installition it will probably not boot click power and volume down wait, do it some times until you get to the bootloader and unlock it, after factory reset it should boot but first explain a little more about your issue we dont want to srew your device up
Click to expand...
Click to collapse
Not sure how things got corrupted, had installed Linage on it, but was not able to download files from any installed program. Reinstalled Linage and it blew up. Erecovery fails to download anything, don't know why. I followed the instructions here https://forum.xda-developers.com/xperia-sp/help/format-data-using-twrp-3-0-2-t3371137 to format all partitions, and still TWRP only sees 0 space, can't do anything with it..
In short - can't see how anything could screw it up more!
which version of twrp is currently installed and normally for format matters only data partition is used, have you formated the system partition too,
maybe we can try to force install the update zip / you were on nougat then lineage oreo and then in the current state right?
qlue4e said:
which version of twrp is currently installed and normally for format matters only data partition is used, have you formated the system partition too,
maybe we can try to force install the update zip / you were on nougat then lineage oreo and then in the current state right?
Click to expand...
Click to collapse
TWRP is 3.0.3-0 It is failing to mount /data (Invalid argument) nor can it mount any other partition.
Yes, was on stock nougat, then Linage oreo, then reinstalled Linage and got current state.
When I try to install zip from PC, it appears to be successful - but apparently is not.
can you intall the twrp 3.3.1-0 which is at the lineage oreo thread and then try to install los zip https://forum.xda-developers.com/mediapad-m3/development/rom-t4085115
qlue4e said:
can you intall the twrp 3.3.1-0 which is at the lineage oreo thread and then try to install los zip https://forum.xda-developers.com/mediapad-m3/development/rom-t4085115
Click to expand...
Click to collapse
The good news is... I did that, got in unbricked, installed ROM, GAPPS... installed apps - and I'm back to the same problem I had before. I can install apps, I can download from Google Drive, but programs such as Gmail cannot download attachments. even though permission to access storage is turned on. This is all to internal storage - no external chip at this time.
thoughts?
thanks, jf
For gmail you must install the micro version of the gapps not the pico one after that it should work
qlue4e said:
For gmail you must install the micro version of the gapps not the pico one after that it should work
Click to expand...
Click to collapse
It's not working for Aquamail either. Also, can't download from the web, using Brave browser.
friedsonjm said:
The good news is... I did that, got in unbricked, installed ROM, GAPPS... installed apps - and I'm back to the same problem I had before. I can install apps, I can download from Google Drive, but programs such as Gmail cannot download attachments. even though permission to access storage is turned on. This is all to internal storage - no external chip at this time.
thoughts?
thanks, jf
Click to expand...
Click to collapse
I'm having the same issue basically storage is off limits to my apps.
The developer of the Linux 15 ROM is aware of the issue, it's on the list to be fixed.