Related
I just took my good ol' Streak 7 to update it as I see some nice JB action here. But as I understand any manipulation to be made needs TWRP to be present on device. As GooManager wasn't instaling recovery the simple way, I decided to download image and flash it via Fastboot. Yet every single time it failed to do so.
Code:
fastboot flash recovery twrps.img
sending 'recovery' (4822 KB)...
FAILED (command write failed (Invalid argument))
finished. total time: 0.000s
I was flashing the latest (2.6.x) version. Also my device is empty atm (had 3.2, now has nothing). Custom Recovery is CWR 5.
Need help to flash the TWRP and begin using JB roms.
YOu need to use the NVflash pack, which write the recovery.img to the correct partition at a lower level than fastboot.
The error you are seeing is due to Dell screwing things up and resulting in fastboot being able to read the partitions name value.
giveen said:
YOu need to use the NVflash pack, which write the recovery.img to the correct partition at a lower level than fastboot.
The error you are seeing is due to Dell screwing things up and resulting in fastboot being able to read the partitions name value.
Click to expand...
Click to collapse
Seems that all download links for nvflash pack for DS7 are now dead both on xda and google.
Hi, I'm writing this to guide those who faced - and will face similar situation in the future - the problem of being stuck on the fastboot screen, where the recovery or booting in EDL is not available.
So, after failing to get root after upgrading to android 10 I was fiddling with TWRP to try to get it to recognize my storage so I can reflash it and flash Magisk, but I couldn't get it to mount the storage, so my stupid brain decided to go to the wipe page and wiped everything in the hope it might magically work!! well.. it didn't!! and I got stuck in the fastboot screen and I thought that I bricked my phone for good.
after hours of searching online and trying everything nothing helped... but finally I managed to fix it.
and btw when I tried to flash TWRP by (fasboot boot twrp.img) I got the following message:
"remote: Failed to load/authenticate boot image: Load Error"
So here is what I did to get my phone working again:
Download and install Tool All in One
Download Fastboot ROM for your phone from here
In the Tool All in One app click on the Flash Factory Images button.
Select the ROM and let it do its work,
hopefully this will work and your device will reboot into a fresh android.
Also it's good to know that the official TWRP of twrp.me does not support Android Q at the moment, that's why you couldn't decrypt and mount the storage. TWRP in Oneplus 7 Pro thread here on XDA does support Q, you just have to remember to boot into the inactive/upgraded slot before booting back to TWRP to flash Magisk as it only installs to the active slot and not the upgraded slot.
Skickat från min GM1913 via Tapatalk
vegatr0n said:
Hi, I'm writing this to guide those who faced - and will face similar situation in the future - the problem of being stuck on the fastboot screen, where the recovery or booting in EDL is not available.
So, after failing to get root after upgrading to android 10 I was fiddling with TWRP to try to get it to recognize my storage so I can reflash it and flash Magisk, but I couldn't get it to mount the storage, so my stupid brain decided to go to the wipe page and wiped everything in the hope it might magically work!! well.. it didn't!! and I got stuck in the fastboot screen and I thought that I bricked my phone for good.
after hours of searching online and trying everything nothing helped... but finally I managed to fix it.
and btw when I tried to flash TWRP by (fasboot boot twrp.img) I got the following message:
"remote: Failed to load/authenticate boot image: Load Error"
So here is what I did to get my phone working again:
Download and install Tool All in One
Download Fastboot ROM for your phone from here
In the Tool All in One app click on the Flash Factory Images button.
Select the ROM and let it do its work,
hopefully this will work and your device will reboot into a fresh android.
Click to expand...
Click to collapse
Or just use the MSM tool. Job done
All with varying levels of interpretation, steps, descriptions, and the solution. Not all are useful.
I had the same issue and this worked perfectly to get my device up and running again. Thanks again!!
Hi all!
Here is plan B!
First of all - BEFORE you do some upgrade - make OPSwitch backup and copy to PC !!!!!
If you stuck - it's mean that something is badly damaged and wrong. Some of the files reside in the areas where upgrade tools (including Fastboot!) can't change and repair them.
We don't have time, knowledge to sort out WHAT was damaged.
We make all straight from beginning:
1. MSM tools - make your phone like from the Factory with "clean" install (ver 9 for now)
2. "FlashAll" то ver 10E
3. If you need - install "global"
4. If you need - install TWRP and Magisk
5. Restore your backup from PC
At the end you will have "clean" phone with all programs working
EASY!!!
Same as OP, I wanted to flash twrp.img.
I had my OP7Pro stuck in 'fastboot mode', I thought. It wouldn't respond to any commands from console (device not found) and I couldn't turn it off with the power button any more.
For noobs, just like me, I learned that I just had to press the powerbutton + volume up button. My phone rebooted after this.
Now making a backup before rooting and such, phew.
vegatr0n
I was stuck in Fastboot after switching slots. Excelent stuf! 2,3 clicks , done! Thank you!
vegatr0n said:
Hi, I'm writing this to guide those who faced - and will face similar situation in the future - the problem of being stuck on the fastboot screen, where the recovery or booting in EDL is not available.
So, after failing to get root after upgrading to android 10 I was fiddling with TWRP to try to get it to recognize my storage so I can reflash it and flash Magisk, but I couldn't get it to mount the storage, so my stupid brain decided to go to the wipe page and wiped everything in the hope it might magically work!! well.. it didn't!! and I got stuck in the fastboot screen and I thought that I bricked my phone for good.
after hours of searching online and trying everything nothing helped... but finally I managed to fix it.
and btw when I tried to flash TWRP by (fasboot boot twrp.img) I got the following message:
"remote: Failed to load/authenticate boot image: Load Error"
So here is what I did to get my phone working again:
Download and install Tool All in One
Download Fastboot ROM for your phone from here
In the Tool All in One app click on the Flash Factory Images button.
Select the ROM and let it do its work,
hopefully this will work and your device will reboot into a fresh android.
Click to expand...
Click to collapse
Many people have found this problem. Thank you, I am working again.
i am not even able to flash the twrp in android 10 always getting stuck at fastbootlogo after flashing the recovery cmd
nitinvaid said:
i am not even able to flash the twrp in android 10 always getting stuck at fastbootlogo after flashing the recovery cmd
Click to expand...
Click to collapse
Then you have to use the MSM unbrick tool:
https://forum.xda-developers.com/oneplus-7-pro/how-to/op7pro-collection-unbrick-tools-t3956595/amp/
vegatr0n said:
Then you have to use the MSM unbrick tool:
https://forum.xda-developers.com/oneplus-7-pro/how-to/op7pro-collection-unbrick-tools-t3956595/amp/
Click to expand...
Click to collapse
Nope...
I was able to reboot holding both vol+ and - and power
I bricked my tmobile oneplus 7 pro and dont know which file is safe to try can anyone please point me in the right direction?
I already tried the steps using the tool and downloading the FASTBOOK os file and I get this error
"CreateProcess failed: %1 is not a valid Win32 application. (193)
fastboot: error: Cannot generate image for userdata"
Tried booting the device but boots to OOS recovery always.
---------- Post added at 11:54 PM ---------- Previous post was at 11:21 PM ----------
vegatr0n said:
Hi, I'm writing this to guide those who faced - and will face similar situation in the future - the problem of being stuck on the fastboot screen, where the recovery or booting in EDL is not available.
So, after failing to get root after upgrading to android 10 I was fiddling with TWRP to try to get it to recognize my storage so I can reflash it and flash Magisk, but I couldn't get it to mount the storage, so my stupid brain decided to go to the wipe page and wiped everything in the hope it might magically work!! well.. it didn't!! and I got stuck in the fastboot screen and I thought that I bricked my phone for good.
after hours of searching online and trying everything nothing helped... but finally I managed to fix it.
and btw when I tried to flash TWRP by (fasboot boot twrp.img) I got the following message:
"remote: Failed to load/authenticate boot image: Load Error"
So here is what I did to get my phone working again:
Download and install Tool All in One
Download Fastboot ROM for your phone from here
In the Tool All in One app click on the Flash Factory Images button.
Select the ROM and let it do its work,
hopefully this will work and your device will reboot into a fresh android.
Click to expand...
Click to collapse
I am getting the error
"Erasing 'userdata' OKAY [ 0.243s]
CreateProcess failed: %1 is not a valid Win32 application. (193)
fastboot: error: Cannot generate image for userdata"
I dont know how to proceed with this :crying:
moonbosques said:
I already tried the steps using the tool and downloading the FASTBOOK os file and I get this error
"CreateProcess failed: %1 is not a valid Win32 application. (193)
fastboot: error: Cannot generate image for userdata"
Tried booting the device but boots to OOS recovery always.
---------- Post added at 11:54 PM ---------- Previous post was at 11:21 PM ----------
I am getting the error
"Erasing 'userdata' OKAY [ 0.243s]
CreateProcess failed: %1 is not a valid Win32 application. (193)
fastboot: error: Cannot generate image for userdata"
I dont know how to proceed with this :crying:
Click to expand...
Click to collapse
Sounds like you're having problems with Windows Defender. I also got the same error messages suddenly once week ago. I did sfc /scannow and all that but all files were intact. After rebooting the PC two times the problem was gone, really strange.
Skickat från min GM1913 via Tapatalk
Anyone here know what fastboot rom i can use to fix my bricked tmobile oneplus 7 pro?
Can you explain this strange effect, please
pitrus- said:
Also it's good to know that the official TWRP of twrp.me does not support Android Q at the moment, that's why you couldn't decrypt and mount the storage. TWRP in Oneplus 7 Pro thread here on XDA does support Q, you just have to remember to boot into the inactive/upgraded slot before booting back to TWRP to flash Magisk as it only installs to the active slot and not the upgraded slot.
Skickat från min GM1913 via Tapatalk
Click to expand...
Click to collapse
After an update to Android Q twrp an root was lost.
I was going the normal way like this:
1. In fastboot boot twrp.img
2. In twrp install twrp.zip
3. Reboot to twrp
4. In twrp install magisk.zip
After this the phone stuck a while on this orange splash screen and then reboot to bootloader.
Reboot --> the same effect
Then:
1. Boot into twrp
2. install twrp.zip
3. Reboot system
Everything ok, but no root
Just one method is working for me:
1. Download the full package of OOS 10.x.x
2. Extract the boot.img
3. Patch boot.img with Magisk
4. Flash on fastboot boot magisk_patched.img
5. reboot
My phone is rooted now but without twrp.
Why can twrp an Magisk not work together?
And why I can´t find any information for this problem on the internet?
Well, since TWRP lives in the boot partition on this phone, you will have to boot TWRP using fastboot boot TWRP. Then you flash the unofficial TWRP build 74 installer zip downloaded from the link below (the one from twrp.me only works on OOS 9 and not 10). Reboot phone back into Magisk to switch slot, flash Magisk installer zip which will then install Magisk to both boot slot a and boot slot b. Reboot phone and you should have both Magisk root and working TWRP.
https://r.tapatalk.com/shareLink/to...2&share_fid=3793&share_type=t&link_source=app
Skickat från min GM1913 via Tapatalk
Fails anyway
Bricked my OnePlus and now I'm left with bootloader (no os, no twrp). Everything leads back to bootloader. Any attempts to apply fastboot boot lead to "Load Error". Now I tried with that tool and ended up with this:
Sending 'odm' (102400 KB) OKAY [ 2.576s]
Writing 'odm' FAILED (remote: '(odb_b) No such partition')
fastboot: error: Command failed
Press any key to exit...
P.S. Full log:
--------------------------------------------
Bootloader Version...:
Baseband Version.....:
Serial Number........: e434a4c8
--------------------------------------------
extracting android-info.txt (0 MB) to RAM...
android-info.txt syntax error: я╗┐require product=msmnile
Setting current slot to 'b' OKAY [ 0.002s]
extracting boot.img (96 MB) to disk... took 0.776s
archive does not contain 'boot.sig'
Sending 'boot_b' (98304 KB) OKAY [ 2.389s]
Writing 'boot_b' OKAY [ 0.406s]
extracting dtbo.img (16 MB) to disk... took 0.151s
archive does not contain 'dtbo.sig'
Sending 'dtbo' (16384 KB) OKAY [ 0.393s]
Writing 'dtbo' OKAY [ 0.047s]
archive does not contain 'dt.img'
archive does not contain 'recovery.img'
extracting vbmeta.img (0 MB) to disk... took 0.001s
archive does not contain 'vbmeta.sig'
Sending 'vbmeta' (8 KB) OKAY [ 0.008s]
Writing 'vbmeta' OKAY [ 0.002s]
archive does not contain 'vbmeta_system.img'
archive does not contain 'super_empty.img'
archive does not contain 'boot_other.img'
extracting odm.img (100 MB) to disk... took 0.395s
archive does not contain 'odm.sig'
Sending 'odm' (102400 KB) OKAY [ 2.576s]
Writing 'odm' FAILED (remote: '(odm_b) No such partition')
fastboot: error: Command failed
Press any key to exit...
I am getting this error, any ideas what is going wrong? (please see attachment)
vegatr0n said:
Hi, I'm writing this to guide those who faced - and will face similar situation in the future - the problem of being stuck on the fastboot screen, where the recovery or booting in EDL is not available.
So, after failing to get root after upgrading to android 10 I was fiddling with TWRP to try to get it to recognize my storage so I can reflash it and flash Magisk, but I couldn't get it to mount the storage, so my stupid brain decided to go to the wipe page and wiped everything in the hope it might magically work!! well.. it didn't!! and I got stuck in the fastboot screen and I thought that I bricked my phone for good.
after hours of searching online and trying everything nothing helped... but finally I managed to fix it.
and btw when I tried to flash TWRP by (fasboot boot twrp.img) I got the following message:
"remote: Failed to load/authenticate boot image: Load Error"
So here is what I did to get my phone working again:
Download and install Tool All in One
Download Fastboot ROM for your phone from here
In the Tool All in One app click on the Flash Factory Images button.
Select the ROM and let it do its work,
hopefully this will work and your device will reboot into a fresh android.
Click to expand...
Click to collapse
Hi,
When I download I cant find it on my downloads. I have to go into my files app then I can find the zip there. And when I try patch it, it says "unknown image format". Therefore the installation fails.
How can I fix this. I also haven't been able to install TWRP.
thanks
What zip file? Do you mean the Magisk installation zip? You can't use that unless you're already rooted (and then you need to install it from the modules section of the Manager) or through TWRP. But if you're already rooted it's easier to just do a direct install from the Manager anyway.
The patch file option in the Manager is for a boot or recovery image (depending on what device you have, see the installation instructions).
twrp
thanks for your reply.
Im also having trouble with installing twrp. I have unlocked the bootloader on my huawei p8 lite 2017 and have downloaded all the tools and flash img needed to flash it. However when use command " fastboot flash recovery twrp-3.4.0-0-prague.img" it says:
Sending 'recovery' (13458 KB) OKAY [ 0.532s]
Writing 'recovery' OKAY [ 0.340s]
Finished. Total time: 0.909s
then when I use " fastboot boot twrp-3.4.0-0-prague.img" it says
Sending 'boot.img' (13458 KB) OKAY [ 0.500s]
Booting FAILED (remote: 'Command not allowed')
fastboot: error: Command failed
How can i fix this. Thanks in advance.
The recovery seems to have installed correctly, so instead of running the command to boot the image, try just using the option directly in the bootloader (usually navigated to by using the volume keys) to boot into recovery.
Didgeridoohan said:
The recovery seems to have installed correctly, so instead of running the command to boot the image, try just using the option directly in the bootloader (usually navigated to by using the volume keys) to boot into recovery.
Click to expand...
Click to collapse
Hi,
When i boot into recover I get another error which is as follows:
ERROR MODE
ATTENTION!
PLEASE UPDATE SYSTEM AGAIN
(Green android bot image)
ERROR!
Func NO : 11 (recovery image)
Error NO : 2(load failed!)
Thanks
You need to take this to your device's forum. That's the best way to get help with stuff like this...
Judging by this thread, you're using the wrong command:
https://forum.xda-developers.com/p8...nt/recovery-twrp-huawei-p8-lite-2017-t4113153
Hi, my tablet was crashed when i updated firmware to one of the latest version in Lolipop.(i don't remember what was the version number of it). Started freezing bootlops, weird crashes and after some time it's stucked at UEFI bios menu. i've searched a lot of possible solutions and made some progress, but it's annoyingly persistent failing to flash ROM. Some ROMs caused freezing on installation progress bar as it's mentioned below( thread ***5.0 Brick Solution*** Asus Memo Pad 7 ME176CX) waiting 20 minutes, but couldn't get response from the device.
Can you please help me what's wrong i'm doing and do you have any solution for this ?
Followed guides:
UNBRICK ASUS MemoPad 7 ME176C/CX
Enter recovery and sideload CN ROM http://dlcdnet.asus.com/pub/ASUS/EeePAD/ME176C/ME176C-CN-3_2_23_182.zip To return to WW rom its a litle complicated becouse when you try to sideloade ww version it gives error for not having inough space. So...
forum.xda-developers.com
UNBRICK ASUS MemoPad 7 ME176C/CX
Enter recovery and sideload CN ROM http://dlcdnet.asus.com/pub/ASUS/EeePAD/ME176C/ME176C-CN-3_2_23_182.zip To return to WW rom its a litle complicated becouse when you try to sideloade ww version it gives error for not having inough space. So...
forum.xda-developers.com
***5.0 Brick Solution*** Asus Memo Pad 7 ME176CX
For the people out there who for some reason had there devices bricked when updating to lollipop. Whenever I was going to flash the WW_5.0_ME176C/X update I would get this error. "This package is for "K013" devices; this is a "K013_1"." I was...
forum.xda-developers.com
Intel Android Devices Root / Temp Recovery Session
Intel Android Devices Root / Temp Recovery Session Disclaimer: Before you proceed to the rooting instructions below, please read this disclaimer: XDA-DEVELOPERS.COM and I are not responsible for what you are doing to your device. You...
forum.xda-developers.com
UEFI bios
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Droidboot
TWRP session, flashing update.zip
Failed but why ?
Tried to unlock bootloader on Android 5.0, seems successfully finished.
Tried to install permanent TWRP with this guide. Command is flashed ok, but when select recovery mode on Droidboot screen, it drops back to UEFI bios menu again:
[RECOVERY][2019-06-09] UNOFFICIAL TWRP 3.3.1 for ASUS MeMO Pad 7 (ME176C(X))
/* * Your warranty is now void. * * I am not responsible for bricked devices, dead SD cards, * thermonuclear war, or you getting fired because the alarm app failed. Please * do some research if you have any concerns about features...
forum.xda-developers.com
Tried to restore with TWRP backup WW 12.10.1.36 8 GB version. It's failed due to unable to mount partitions. Only Factory partition is mounted.
Tried rollback from Android 5 to 4.4 Kitkat.
Code:
OSLOADER: efilinux-userdebug.efi
sending 'osloader' (2023 KB)...
OKAY [ 0.103s]
writing 'osloader'...
OKAY [ 0.007s]
finished. total time: 0.113s
downloading 'boot.img'...
OKAY [ 0.536s]
booting...
OKAY [ 0.001s]
finished. total time: 0.541s
Waiting for 0 seconds, press a key to continue ...
< waiting for device >
...
(bootloader) Start partitioning
OKAY [ 0.047s]
finished. total time: 0.048s
target reported max download size of 536870912 bytes
sending '/tmp/partition.tbl' (1 KB)...
OKAY [ 0.035s]
writing '/tmp/partition.tbl'...
OKAY [ 0.044s]
finished. total time: 0.081s
...
FAILED (remote: GPT command failed
)
finished. total time: 0.287s
"partition /tmp/partition.tbl FAILED, EXIT!"
Press any key to continue . . .
Fastboot commands:
Code:
fastboot oem start_partitioning
fastboot oem partition /system/etc/partition.tbl
Code:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash osloader efilinux
.efi
target didn't report max-download-size
sending 'osloader' (2009 KB)...
OKAY [ 0.104s]
writing 'osloader'...
OKAY [ 0.045s]
finished. total time: 0.153s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot boot droidboot.img
downloading 'boot.img'...
OKAY [ 0.537s]
booting...
OKAY [ 0.002s]
finished. total time: 0.540s
C:\Program Files (x86)\Minimal ADB and Fastboot>
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot oem start_partitioning
...
(bootloader) Start partitioning
OKAY [ 0.046s]
finished. total time: 0.048s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot oem partition /system/e
tc/partition.tbl
...
FAILED (remote: GPT command failed
)
finished. total time: 0.103s
C:\Program Files (x86)\Minimal ADB and Fastboot>
Patch Micro SD, trying to run OS on it.
Power Y USB Hub connected. Have access to UEFI settings.
RaiKov said:
Hi, my tablet was crashed when i updated firmware to one of the latest version in Lolipop.(i don't remember what was the version number of it). Started freezing bootlops, weird crashes and after some time it's stucked at UEFI bios menu. i've searched a lot of possible solutions and made some progress, but it's annoyingly persistent failing to flash ROM. Some ROMs caused freezing on installation progress bar as it's mentioned below( thread ***5.0 Brick Solution*** Asus Memo Pad 7 ME176CX) waiting 20 minutes, but couldn't get response from the device.
Can you please help me what's wrong i'm doing and do you have any solution for this ?
Followed guides:
UNBRICK ASUS MemoPad 7 ME176C/CX
Enter recovery and sideload CN ROM http://dlcdnet.asus.com/pub/ASUS/EeePAD/ME176C/ME176C-CN-3_2_23_182.zip To return to WW rom its a litle complicated becouse when you try to sideloade ww version it gives error for not having inough space. So...
forum.xda-developers.com
UNBRICK ASUS MemoPad 7 ME176C/CX
Enter recovery and sideload CN ROM http://dlcdnet.asus.com/pub/ASUS/EeePAD/ME176C/ME176C-CN-3_2_23_182.zip To return to WW rom its a litle complicated becouse when you try to sideloade ww version it gives error for not having inough space. So...
forum.xda-developers.com
***5.0 Brick Solution*** Asus Memo Pad 7 ME176CX
For the people out there who for some reason had there devices bricked when updating to lollipop. Whenever I was going to flash the WW_5.0_ME176C/X update I would get this error. "This package is for "K013" devices; this is a "K013_1"." I was...
forum.xda-developers.com
Intel Android Devices Root / Temp Recovery Session
Intel Android Devices Root / Temp Recovery Session Disclaimer: Before you proceed to the rooting instructions below, please read this disclaimer: XDA-DEVELOPERS.COM and I are not responsible for what you are doing to your device. You...
forum.xda-developers.com
UEFI bios
View attachment 5150261
Droidboot
View attachment 5150263
TWRP session, flashing update.zip
View attachment 5150265
Failed but why ?
Click to expand...
Click to collapse
If im not wrong its due to bad partition table, you should try to format everything first, before flashing, on after new year I can give more detailed help, I dont have access to the device at the moment.
Ruben Craveiro said:
If im not wrong its due to bad partition table, you should try to format everything first, before flashing, on after new year I can give more detailed help, I dont have access to the device at the moment.
Click to expand...
Click to collapse
Hi, i appreciate if you can help me further. Yes, the main problem is Internal memory is somehow disappeared after i tried to format all memory on WIPE menu in TWRP. Now Tablet went into read-only mode, no access to flash something. Only MicroSD storage is visible on MTP device on Windows PC. It was both visible(Internal storage and MicroSD) before formatting data in TWRP. Looks like all partitions are erased, unable to mount data due to Internal Storage(0 MB) problem. I guess i may need a full memory dump of any of working 176CX 8GB tablet to restore my tablet. Looking forward to your reply. Merry Christmas and happy holidays.
Raiko.
RaiKov said:
Hi, i appreciate if you can help me further. Yes, the main problem is Internal memory is somehow disappeared after i tried to format all memory on WIPE menu in TWRP. Now Tablet went into read-only mode, no access to flash something. Only MicroSD storage is visible on MTP device on Windows PC. It was both visible(Internal storage and MicroSD) before formatting data in TWRP. Looks like all partitions are erased, unable to mount data due to Internal Storage(0 MB) problem. I guess i may need a full memory dump of any of working 176CX 8GB tablet to restore my tablet. Looking forward to your reply. Merry Christmas and happy holidays.
Raiko.
Click to expand...
Click to collapse
The partition table looks pretty good in this screenshot:
Spoiler
The sizes seem to mostly match mine (I have the 16 GB variant though).
In general, as long as you can still access the UEFI setup or even boot (temporary?) TWRP your tablet seems in pretty good shape.
I would try flashing e.g. me176c-boot from the "FASTBOOT MODE" (Droidboot) screen (see https://forum.xda-developers.com/t/...6c-boot-for-asus-memo-pad-7-me176c-x.3780225/) and then check if it shows the boot menu if you keep "Volume Down" pressed while turning the tablet on.
lambdadroid said:
The partition table looks pretty good in this screenshot:
Spoiler
The sizes seem to mostly match mine (I have the 16 GB variant though).
In general, as long as you can still access the UEFI setup or even boot (temporary?) TWRP your tablet seems in pretty good shape.
I would try flashing e.g. me176c-boot from the "FASTBOOT MODE" (Droidboot) screen (see https://forum.xda-developers.com/t/...6c-boot-for-asus-memo-pad-7-me176c-x.3780225/) and then check if it shows the boot menu if you keep "Volume Down" pressed while turning the tablet on.
Click to expand...
Click to collapse
Hi, yes i have access to Fastboot mode and then TWRP, but not directly(first i need to flash efilinux from DNX mode Fastboot starting...#1#2#3 https://forum.xda-developers.com/t/unbrick-asus-memopad-7-me176c-cx.2970049/post-72963836) I flashed ESP.img successfully. When i press Volume down button. These options are available:
*Recovery mode
*Restart bootloader
*Normal boot
*Power off
(This is an old image for e.g., there was no error in this session.)
Code:
C:\Users\RaiKo\Desktop\asus recovery project\rollback\WW_ME176C_V12.10.1.17-user
debug-201505051557-rawdata>fastboot flash osloader efilinux-userdebug.efi
sending 'osloader' (2023 KB)...
OKAY [ 0.105s]
writing 'osloader'...
OKAY [ 0.007s]
finished. total time: 0.115s
C:\Users\RaiKo\Desktop\asus recovery project\rollback\WW_ME176C_V12.10.1.17-user
debug-201505051557-rawdata>fastboot boot droidboot.img
downloading 'boot.img'...
OKAY [ 0.536s]
booting...
OKAY [ 0.002s]
finished. total time: 0.541s
C:\Users\RaiKo\Desktop\asus recovery project\rollback\WW_ME176C_V12.10.1.17-user
debug-201505051557-rawdata>fastboot flash ESP esp.img
target reported max download size of 536870912 bytes
sending 'ESP' (33792 KB)...
OKAY [ 1.169s]
writing 'ESP'...
OKAY [ 0.616s]
finished. total time: 1.788s
C:\Users\RaiKo\Desktop\asus recovery project\rollback\WW_ME176C_V12.10.1.17-user
debug-201505051557-rawdata>
When i select boot or recovery it directly goes into UEFI bios screen. Is there any solution to format or recover Internal Storage(0 Mb) of the tablet?
RaiKov said:
Hi, yes i have access to Fastboot mode and then TWRP, but not directly(first i need to flash efilinux from DNX mode Fastboot starting...#1#2#3 https://forum.xda-developers.com/t/unbrick-asus-memopad-7-me176c-cx.2970049/post-72963836) I flashed ESP.img successfully. When i press Volume down button. These options are available:
*Recovery mode
*Restart bootloader
*Normal boot
*Power off
Code:
C:\Users\RaiKo\Desktop\asus recovery project\rollback\WW_ME176C_V12.10.1.17-user
debug-201505051557-rawdata>fastboot flash osloader efilinux-userdebug.efi
sending 'osloader' (2023 KB)...
OKAY [ 0.105s]
writing 'osloader'...
OKAY [ 0.007s]
finished. total time: 0.115s
C:\Users\RaiKo\Desktop\asus recovery project\rollback\WW_ME176C_V12.10.1.17-user
debug-201505051557-rawdata>fastboot boot droidboot.img
downloading 'boot.img'...
OKAY [ 0.536s]
booting...
OKAY [ 0.002s]
finished. total time: 0.541s
C:\Users\RaiKo\Desktop\asus recovery project\rollback\WW_ME176C_V12.10.1.17-user
debug-201505051557-rawdata>fastboot flash ESP esp.img
target reported max download size of 536870912 bytes
sending 'ESP' (33792 KB)...
OKAY [ 1.169s]
writing 'ESP'...
OKAY [ 0.616s]
finished. total time: 1.788s
C:\Users\RaiKo\Desktop\asus recovery project\rollback\WW_ME176C_V12.10.1.17-user
debug-201505051557-rawdata>
When i select boot or recovery it directly goes into UEFI bios screen. Is there any solution to format or recover Internal Storage(0 Mb) of the tablet?
Click to expand...
Click to collapse
That does not sound like it really flashed it successfully. If you install me176c-boot, the boot menu should look like
It does kind of sound like your eMMC has magically become read-only, although I don't know how this is possible.
lambdadroid said:
That does not sound like it really flashed it successfully. If you install me176c-boot, the boot menu should look like
View attachment 5185301
It does kind of sound like your eMMC has magically become read-only, although I don't know how this is possible.
Click to expand...
Click to collapse
Exactly yes! This read-only memory mode what i'm facing now. As i said above, i didn't change too many things. When i was trying to solve "unable to mount" error, once i tried to format internal memory on TWRP wipe menu. I saw this advice in main topic, it was explaining in guide how to solve Internal Memory(0 Mb) problem with TWRP formatting, wipe, repairing partitions, change type of format from ext4 to ext2 and rechange it to ext4 etc. I'm very sure Internal memory was visible both TWRP and MTP device on Windows PC before formatting.
Maybe i need to give permissions or enter password(seen it in many Youtube tutorials for Asus Phone) to unlock Internal Memory, but i don't know how to solve this problem without running Android.
Do you have any suggestion to me, what i supposed to do?
RaiKov said:
Do you have any suggestion to me, what i supposed to do?
Click to expand...
Click to collapse
It's a very strange problem and to be honest I don't really know what to do either.
I guess in your situation I would put some Linux distribution on a USB flash drive (e.g. Arch Linux), boot it through the UEFI menu (use the "Boot Override" option). And then try to investigate from there using some proper Linux command line tools or by looking at the kernel log. But I can't give you exact steps because I don't know how the eMMC could magically become read-only or how to get it out of this mode.
lambdadroid said:
It's a very strange problem and to be honest I don't really know what to do either.
I guess in your situation I would put some Linux distribution on a USB flash drive (e.g. Arch Linux), boot it through the UEFI menu (use the "Boot Override" option). And then try to investigate from there using some proper Linux command line tools or by looking at the kernel log. But I can't give you exact steps because I don't know how the eMMC could magically become read-only or how to get it out of this mode.
Click to expand...
Click to collapse
Thanks for the answer. Not sure we are talking about similar things. I downloaded gparted live on Linux OS.(My dev specialist friend had advised me). Created a bootable disk by rufus, but if i knew it i could tell you the result.
And then do you know any person in the forum who can help me in this case? i believe this eMMC issue is weird, but not magical imho, it must have happened and affected to more users.
RaiKov said:
Thanks for the answer. Not sure we are talking about similar things. I downloaded gparted live on Linux OS.(My dev specialist friend had advised me). Created a bootable disk by rufus, but if i knew it i could tell you the result.
Click to expand...
Click to collapse
So, did you find anything interesting?
RaiKov said:
And then do you know any person in the forum who can help me in this case? i believe this eMMC issue is weird, but not magical imho, it must have happened and affected to more users.
Click to expand...
Click to collapse
I don't really know any other person who has worked on this device in the last few years so I'm afraid I don't know anyone either.
lambdadroid said:
So, did you find anything interesting?
Click to expand...
Click to collapse
No, actually i haven't tried it yet. Because i dunno how to recognise it.(not familiar with Linux) Another reason i know this is one of the last thing i can try to bring the tablet back life. I was searching other possible solutions before this step.
What do you think about if i got a full memory dump.img.gz(including all 15 partitions) of a working 176CX 8GB tablet? Would that help me in some way?
RaiKov said:
What do you think about if i got a full memory dump.img.gz(including all 15 partitions) of a working 176CX 8GB tablet? Would that help me in some way?
Click to expand...
Click to collapse
This will probably be helpful at some point, but I would recommend against randomly overwriting all partitions from some memory dump. This might do more harm than good. From what I could tell, your partition table for example seems fine.
You can try booting the following image. This is me176c-boot packaged for USB. It also contains a bootable version of my TWRP build (https://forum.xda-developers.com/t/...p-3-3-1-for-asus-memo-pad-7-me176c-x.3745190/).
Flash it to an USB flash drive using Rufus.
Boot it on your tablet. A menu like I showed above should show up.
You can try the other boot options but I added a special "Recovery (USB)" one. This should boot TWRP from the USB flash drive. (Note: use ↓ to switch options, ↑ or Enter to select an option)
When the TWRP splash screen shows up you can disconnect USB.
Post the output of "dmesg" in the terminal emulator here. You can get it via adb shell (tablet connected via USB to your PC) or write to to an external SD card e.g. with "dmesg > /external_sd/dmesg.txt".
Perhaps that (dmesg = kernel log) contains something useful.
lambdadroid said:
This will probably be helpful at some point, but I would recommend against randomly overwriting all partitions from some memory dump. This might do more harm than good. From what I could tell, your partition table for example seems fine.
You can try booting the following image. This is me176c-boot packaged for USB. It also contains a bootable version of my TWRP build (https://forum.xda-developers.com/t/...p-3-3-1-for-asus-memo-pad-7-me176c-x.3745190/).
Flash it to an USB flash drive using Rufus.
Boot it on your tablet. A menu like I showed above should show up.
You can try the other boot options but I added a special "Recovery (USB)" one. This should boot TWRP from the USB flash drive. (Note: use ↓ to switch options, ↑ or Enter to select an option)
When the TWRP splash screen shows up you can disconnect USB.
Post the output of "dmesg" in the terminal emulator here. You can get it via adb shell (tablet connected via USB to your PC) or write to to an external SD card e.g. with "dmesg > /external_sd/dmesg.txt".
Perhaps that (dmesg = kernel log) contains something useful.
Click to expand...
Click to collapse
Thank you for taking your time! i will try it asap.
lambdadroid said:
This will probably be helpful at some point, but I would recommend against randomly overwriting all partitions from some memory dump. This might do more harm than good. From what I could tell, your partition table for example seems fine.
You can try booting the following image. This is me176c-boot packaged for USB. It also contains a bootable version of my TWRP build (https://forum.xda-developers.com/t/...p-3-3-1-for-asus-memo-pad-7-me176c-x.3745190/).
Flash it to an USB flash drive using Rufus.
Boot it on your tablet. A menu like I showed above should show up.
You can try the other boot options but I added a special "Recovery (USB)" one. This should boot TWRP from the USB flash drive. (Note: use ↓ to switch options, ↑ or Enter to select an option)
When the TWRP splash screen shows up you can disconnect USB.
Post the output of "dmesg" in the terminal emulator here. You can get it via adb shell (tablet connected via USB to your PC) or write to to an external SD card e.g. with "dmesg > /external_sd/dmesg.txt".
Perhaps that (dmesg = kernel log) contains something useful.
Click to expand...
Click to collapse
Here's the result. i hope it will be helpful.
Also, is there a solution to charge the tablet properly? After the battery capacity goes under 50%(only i can monitor it in TWRP) and then try to connect a power source (AC charger, PC USB cable or USB HUB), Tablet screen is immediately opened in UEFI bios menu by itself. No matter of using power off button. During a cable is connected, tablet goes on again(with release of power off button). Only way i find is opening back cover of tablet and disconnecting power supply terminal of battery for a while. Tablet is charging well via AC charger while screen is completely off(No backlight.) i hope you understand it.
RaiKov said:
Here's the result. i hope it will be helpful.
Click to expand...
Click to collapse
Hmm. There are lots of I/O errors that shouldn't be there.
Code:
[ 8.008459] print_req_error: I/O error, dev mmcblk2, sector 589864
[ 8.008492] Buffer I/O error on dev mmcblk2p9, logical block 0, lost sync page write
[ 8.008641] EXT4-fs (mmcblk2p9): I/O error while writing superblock
[ 8.008692] EXT4-fs (mmcblk2p9): mount failed
[ 8.030538] print_req_error: I/O error, dev mmcblk2, sector 589864
[ 8.030571] Buffer I/O error on dev mmcblk2p9, logical block 0, lost sync page write
[ 8.030868] EXT4-fs (mmcblk2p9): I/O error while writing superblock
[ 8.030919] EXT4-fs (mmcblk2p9): mount failed
This could be caused by this "eMMC has magically become read-only" problem. But I have absolutely no idea how this could happen, it seems almost impossible.
Sadly, another possible explanation for those I/O errors would be that your eMMC is just broken.
Can you try flashing me176c-boot to the internal storage from that TWRP build? Download https://github.com/me176c-dev/me176c-boot/releases/download/0.3.0/esp-0.3.0.zip and unpack it to external SD card.
From TWRP terminal do dd if=/external_sd/esp.img of=/dev/block/by-name/ESP (make sure to type it correctly). Before rebooting, copy the dmesg again to see if there are new I/O errors. (You can post it here if you are not sure how to read it...)
Hi All,
After several years (since 2006) of playing with flashing and rooting the hardware, the day has finally come (I still hope not ...) - I broke my smartphone.
Don't ask me why it happened - I think I was rocking in the clouds by turning off USB debugging while I was still getting my stuff back from backups... Maybe I clicked this option by accident. But one by one:
1. I have downgraded the LineageOS for microG 18.1 ROM to the April 11 version (the newer one had huge connectivity problems :[).
2. Everything worked fine again, unfortunately I have restored too many files (some system files) using my root backup and after rebooting I have bootloop.
The above would not be a problem, but:
* USB debugging is disabled (I don't know if there is a hack method on Pixel 5 to enable it from PC (I'm using Linux)). Flashing recovery seems unavailable (Writing 'recovery' FAILED (remote: 'No such file or directory')), the same with adb sideload commands.
* adb shell is unavailable (I tried to send a ROM image file to the device) due to lack of any trusted device on Pixel 5.
(db: error: failed to get feature set: device unauthorized.
This adb server's $ADB_VENDOR_KEYS is not set
Try 'adb kill-server' if that seems wrong.
Otherwise check for a confirmation dialog on your device.)
adb kill-server/start-server and deleting my Linux adbkey doesn't work of course.
I can only add that I have root access and an unlocked bootloader, but I don't know if I can do anything on this basis.
Is there any magician on the forum who has an idea for my brick with bootlooping screen?
Maybe this can work for you? >> Deuces Flashing Script
It should work with any google factory image as stated in the post, don't download the wrong factory image tho.
Goodluck.
XDHx86 said:
Maybe this can work for you? >> Deuces Flashing Script
It should work with any google factory image as stated in the post, don't download the wrong factory image tho.
Goodluck.
Click to expand...
Click to collapse
Thank you very much! I have only recently been with Pixel and did not know about the existence of this script.
Interestingly, on my first try on Pixel 5 the script crashed, it requires fastbootd instead of the fastboot standard:
system
Sending 'system_b' (23660 KB) OKAY [ 0.700s]
Writing 'system_b' FAILED (remote: 'Partition should be flashed in fastbootd')
as a result, the system did not rise.
Quickly switched to recovery and then fastbootd on the second attempt was successful.
Michu_z said:
Thank you very much! I have only recently been with Pixel and did not know about the existence of this script.
Interestingly, on my first try on Pixel 5 the script crashed, it requires fastbootd instead of the fastboot standard:
system
Sending 'system_b' (23660 KB) OKAY [ 0.700s]
Writing 'system_b' FAILED (remote: 'Partition should be flashed in fastbootd')
as a result, the system did not rise.
Quickly switched to recovery and then fastbootd on the second attempt was successful.
Click to expand...
Click to collapse
No need for a magician then I guess, haha.
Glad it worked out mate, don't brick your phone again. I think pixel phones are one of the hardest to fix.