my tablet (asus me170c) was hard bricked for a long time and only usb logo showed up. using this amazing guide and using xftk tools I managed to make droidboot available but I can't boot into recovery or system. fastboot detects the device but adb doesn't. I read all similar xda treaths and downloaded about 5 or 6 roms (including raw rom) and started trying the following(but none worked:crying: ):
1-first i tried to boot into recovery and flash latest rom but sadly the tablet won't boot into recovey and SD update is not available in droidboot.
2-then i downloaded ASUS flash tool to flash raw rom but even though all drivers are installed and i can see my tablet in device manager phone flash tool doesn't detect the device :crying:
3-since there is no custom recovery for this specific model, i tried flashing me176cx unofficial twrp by fastboot: fastboot flash recovery twrp.img but it didn't flash recovey with sign_key ROS error (but boot.img and fastboot.img were flashed successfully. and i also tried flashing the raw frameware's system.img with fastboot and it was flashed successfully but nothing changed and the device is still stuck on intel logo.
4-as my last chance, I tried booting into temporary tethered twrp and it booted! but the touch screen didn't work. then I booted temporary cwm but it can't flash any of frameware zip files on external sd card even though it detects them! with erorr closed:0. and It can't load internal storage. there was also an adb sideload option in cwm and after enabling it adb finally detected device but adb sideload zip file failded with the same closed:0 error
5-I also tried Intel flash tool and it detects the device but says the firmware xml file is invalid both stock rom and raw rom have the same error.
I thought making it into fastboot will make reviving my tablet easy but it didn't.
please help, I don't know what else to do i need this tablet for reading books.
Related
Hi
I have a HTC one m7 which went in Boot loop just like that. It was working perfectly some time back., just rebooted and won.t me back now. I had the latest stock OS 4.4 with sense 6 developer edition on it with no tamperig.
I tried many time wipe cache and factory reset. Nothing helped. Finally someone here suggested i do a unlock bootloader -> custom recovery -> custom rom -> s-off -> Load my Stock RUU.
Problem with above is i have done the unlock boot loader and install twrp recovery. But to do a s-off i need my device to read adb commands. As its in boot loop i cannot. Can i flash a custom binary which can run on S-on just to run those commands of firewater to make s-off.
I am stuck here. Please help to revive my device and reach me back to stock 4.4 sense 6 .
Also i came to know as i was on latest version if i flash a older RUU with S-On it can brick my device. True ?
And something else i noticed , i read some 4-5 thread in last two days complaining of HTC going in boot loop just like that.
HTC to blame ? Is this some issue with htc ???
Thanks
anirudhgargi said:
Hi
I have a HTC one m7 which went in Boot loop just like that. It was working perfectly some time back., just rebooted and won.t me back now. I had the latest stock OS 4.4 with sense 6 developer edition on it with no tamperig.
I tried many time wipe cache and factory reset. Nothing helped. Finally someone here suggested i do a unlock bootloader -> custom recovery -> custom rom -> s-off -> Load my Stock RUU.
Problem with above is i have done the unlock boot loader and install twrp recovery. But to do a s-off i need my device to read adb commands. As its in boot loop i cannot. Can i flash a custom binary which can run on S-on just to run those commands of firewater to make s-off.
I am stuck here. Please help to revive my device and reach me back to stock 4.4 sense 6 .
Also i came to know as i was on latest version if i flash a older RUU with S-On it can brick my device. True ?
And something else i noticed , i read some 4-5 thread in last two days complaining of HTC going in boot loop just like that.
HTC to blame ? Is this some issue with htc ???
Thanks
Click to expand...
Click to collapse
as mentioned in the previous post you made, you need to install a custom ROM first in order to boot back into your phone. You have unlocked the bootloader and installed TWRP recovery. Now you need to sideload the ROM by adb sideload commands in order to boot the phone up again
Do not run an earlier RUU.zip as you will brick your phone. Firewater needs a working ROM, there are no ways to bypass this
Flash ARHD 81 or Insert Coin or Team Venom Rom
Step 1. Unlock Bootloader and Install TWRP 2.7.x.x recovery. Don't install Twrp v2.8.x.x, wont work with any roms.
Step 2. Boot to Recovery.
Step 3. Mount the system using twrp. I am assuming that you don't have custom rom on your phone storage.
Note that TWRP v2.7.x.x wont mount the phone storage. v2.7 and above always had issues. My recommendation is to install TWRP v2.8 for temporary purposes. Now mount the phone storage copy any rom you downloaded to the system.
Step 4. Assuming that you install TWRP v2.8 to copy rom files to phone storage. Boot to bootloader again and Install TWRP using fastboot. Command: "Fastboot flash recovery openrecovery-twrp-2.7.1.1-m7.img"
Step 5. Reboot to recovery. WIPE DATA, CACHE, DALVIK CACHE, SYSTEM > Install Rom.
Note do not wipe "internal storage." Otherwise you have to go back and start again with installing twrp v2.8, then copy rom...
Step 6: follow the steps.
IMO ARHD 81 is a stable rom, provides better battery life. If you like Sense then stick with this Rom, if you want Stock Android aka AOSP then try aospa legacy, CM, SlimKAT, AOSB and many more.
Moreover, i haven't found RUU for Sense 6 KK4.4.3, if you do please provide me a link as well.
As of yet there are no links for 4.4.3 RUU's. Haven't been released anywhere. He just needs a working ROM to get s off again. Nice step by step guide tho
Not able to copy my custom rom in phone.
stovie_steve said:
As of yet there are no links for 4.4.3 RUU's. Haven't been released anywhere. He just needs a working ROM to get s off again. Nice step by step guide tho
Click to expand...
Click to collapse
Hi , i got stuck with a minor issue. I am with 2.8 TWRP was trying to mount the phone . i am using a mac os with the Android Revolution Rom downloaded in place. .
m7 gets mount i could see the phone in android fie transfer ( MTP utility for mac) . I selected the System and data and cache back in the twrp mount page. I can write and create some folders etc.
Issue is when i start to copy the Custom ROM file to the phone ( any folder) it says 'filexxx.zip not copy'. However i copied a small file (1mb). It was copied ok.
Any idea what is the issue with the file size restrictions?
I tried the adb sideload that also fails with saying device not found. Wanna avoid sideload, as sideload will execute also the zip after copying . I Want to change the recovery file as the recovery file need to changed to a twrp 2.7xx before installation starts. I hear that V2.8 is not compatible with lot of roms.
anirudhgargi said:
Hi , i got stuck with a minor issue. I am with 2.8 TWRP was trying to mount the phone . i am using a mac os with the Android Revolution Rom downloaded in place. .
m7 gets mount i could see the phone in android fie transfer ( MTP utility for mac) . I selected the System and data and cache back in the twrp mount page. I can write and create some folders etc.
Issue is when i start to copy the Custom ROM file to the phone ( any folder) it says 'filexxx.zip not copy'. However i copied a small file (1mb). It was copied ok.
Any idea what is the issue with the file size restrictions?
I tried the adb sideload that also fails with saying device not found. Wanna avoid sideload, as sideload will execute also the zip after copying . I Want to change the recovery file as the recovery file need to changed to a twrp 2.7xx before installation starts. I hear that V2.8 is not compatible with lot of roms.
Click to expand...
Click to collapse
You are better using the 2.7.xx version of TWRP. Sounds like you could also be using out of date adb drivers. You can download the most up to date ones by downloading the latest Google sdk
Try fixing the above and sideloading again
No luck ! Fastboot mode also not getting detected now.
stovie_steve said:
You are better using the 2.7.xx version of TWRP. Sounds like you could also be using out of date adb drivers. You can download the most up to date ones by downloading the latest Google sdk
Try fixing the above and sideloading again
Click to expand...
Click to collapse
Hello i tried updating the drivers from the sdk itself. No luck . The device won't just get detect as adb device. Tried cache clear. factory reset , reboot pc and phone. And Loaded other twrp recovery images ( 2.8 and 2.7).
Today tried with a window machine also. I thought some issue with Mac + adb drivers. But with window also No luck.
Also one more issue, my phone fastboot has stopped detecting om pc and mac. Tried everything almost.
It was like just working some time back, i loaded twrp 2.7.x and booted to recovery for adb sideload.
Adb Sideload failed as mentioned above on this window machine also ... so i was like this adb is not working at all.
But then i thought of loading 2.8 twrp and see if mount (mtp) works, i can send the ROM to device this way. But for that when i booted to fastboot. Fastboot just stopped detecting in PC (window and mac)
I wonder can the Fastboot mode ( within Hboot bootloader) can go corrupt ?
I am sure drivers are there, usb cable is fine, usb port in HTC one is fine. It just show "fastboot ac" not "fastboot usb" . No activity in the device manager when i plug surprisingly !! (can't see Android phone there " . Afterall it was working ok when i loaded the recovery image of 2.7.1.
Also , can the recovery mess up with the fastboot mode ? i am still s-on and in boot loop.
-Thanks,
anirudhgargi said:
Hello i tried updating the drivers from the sdk itself. No luck . The device won't just get detect as adb device. Tried cache clear. factory reset , reboot pc and phone. And Loaded other twrp recovery images ( 2.8 and 2.7).
Today tried with a window machine also. I thought some issue with Mac + adb drivers. But with window also No luck.
Also one more issue, my phone fastboot has stopped detecting om pc and mac. Tried everything almost.
It was like just working some time back, i loaded twrp 2.7.x and booted to recovery for adb sideload.
Adb Sideload failed as mentioned above on this window machine also ... so i was like this adb is not working at all.
But then i thought of loading 2.8 twrp and see if mount (mtp) works, i can send the ROM to device this way. But for that when i booted to fastboot. Fastboot just stopped detecting in PC (window and mac)
I wonder can the Fastboot mode ( within Hboot bootloader) can go corrupt ?
I am sure drivers are there, usb cable is fine, usb port in HTC one is fine. It just show "fastboot ac" not "fastboot usb" . No activity in the device manager when i plug surprisingly !! (can't see Android phone there " . Afterall it was working ok when i loaded the recovery image of 2.7.1.
Also , can the recovery mess up with the fastboot mode ? i am still s-on and in boot loop.
-Thanks,
Click to expand...
Click to collapse
Sounds also like a driver issue
Try instling HTC sync to get the up to date HTC drivers and retry. Use different usb ports (2.0 preferably) and different cables. If it's saying fastboot ac then the phone is not being detected correctly, so it's a driver issue
You can also try manually installing the driver by searching for I think the Google naked driver
I have rooted my phone using supersu by cwm
and after that the phone rooted and was working perfectly and yeterday i got an update from asus and a started dwonloading it but it not installed so i downloaded firmware from asus site and it not installed also so i started working using cwm and try to install using install update from zip and it not works also after that the phone didnt works the main problem that i just executed this command fastboot flash recovery 4.3.6_ww_recovery.img and 450cg doent have recovery mode and later i know that i have to disable/uninstall super su and thier require 1 gb space now i need to boot into cmw i think the recovery makes the problem after running fastboot flash update updateCWM_6.0.2.8_fix_wipe.zip this the phone restars and shows asus logo and nothing happens what will i do now after ruuing this command it not even loads droidboot
fastboot flash recovery droidboot.img
the img file is from the new firmware i have downloaded
Myn 2 stuck at asus logo ,,whats showing in ur device manager
myn is MTP USB DEVICE
got any solution
Try this : https://forum.xda-developers.com/android/development/hard-bricked-zenfone-unbrick-method-to-t3131911
is there any reason why flashing twrps via ADB would send z5 pro gt into boot loop into bootloader unable to access the custom recovry or phone needing to do emergency flashing via qfil to stock firmware i did previously use trwps on device to flash files and to sign boot to always boot twrps recovery when trying to access recovery mode . (before bootlooping)
affter bootlooping and fixing via qfil i have been unable to successful install trwps if i do it bootloop to bootloader.
whats the difference between "meta" / "flat" options in qfil
tried locked and unlocked bootloader on both 10.5.304 and 11.1.021 also tried to go straight to recovery mode affter twrps flashing on both firmware same thing lead me bootloop needing to qfill to 10.5.30
another question can i qfil flash to 11.1.021 straight away without having having to qfil 10.5.30 then ota updating to 11.1.021..
thanks in advance
leerh said:
is there any reason why flashing twrps via ADB would send z5 pro gt into boot loop into bootloader unable to access the custom recovry or phone needing to do emergency flashing via qfil to stock firmware i did previously use trwps on device to flash files and to sign boot to always boot twrps recovery when trying to access recovery mode . (before bootlooping)
affter bootlooping and fixing via qfil i have been unable to successful install trwps if i do it bootloop to bootloader.
whats the difference between "meta" / "flat" options in qfil
tried locked and unlocked bootloader on both 10.5.304 and 11.1.021 also tried to go straight to recovery mode affter twrps flashing on both firmware same thing lead me bootloop needing to qfill to 10.5.30
another question can i qfil flash to 11.1.021 straight away without having having to qfil 10.5.30 then ota updating to 11.1.021..
thanks in advance
Click to expand...
Click to collapse
Okay ?
The point is ? I must unlock , install twrp and flashing via ota ?
Flash via qfil done and isn't working
My touchscreen still have thats issue
IamRdw said:
Okay
The point is ? I must unlock , install twrp and flashing via ota ?
Flash via qfil done and isn't working
My touchscreen still have thats issue
Click to expand...
Click to collapse
if you want OTA(over the air) updates you need to lock bootloader. otherwise the updater will say something like phone has been rooted and they cant provide you an update
https://forum.xda-developers.com/z5-pro-gt/how-to/installing-ota-update-11-5-141-via-twrp-t4050027
http://anago.2ch.sc/test/read.cgi/sm...ne/1577014188/ theres a lot of information on this link here are some highlights for me
_____________________________________
>> Crash dump loop of 113 ROM burnt Z5PROGT can be restored by burning CNROM for the time being,
Even if I tried it again, it was useless, so if I look at the syntax at the time of batch execution, it seems that vbmeta.img is not burned.
It says unrecognised option `--disable-verification '.
This time, the boot loader loop only started, and TWRP couldn't start.
This time it may be packed
__________________________________________
>> 117
I'm sorry I want to confirm.
Where did you use the fastboot command?
①fastboot --disable-verification flash vbmeta vbmeta.img
②fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
It is ① that I instructed, but it looks like there are two kinds when I check it on the net.
He seemed to have hit it without knowing it.
Excuse me, can you hit both again?
________________________________________
>> 150
>> I burned 113 ZUI11 version Gro ROM.
I re-added TWRP, but when I started it, it was usable normally, so I could add Magisk,
After that, it only seems to be unavoidable that it only starts up in normal recovery mode.
It is troublesome to do it every time you want to use TWRP, but it can't be helped.
__________________________________________________ _______
this helped Solved
G'day folks,
I've been reading through the forums the past several days to fix an issue I have with my Moto G7 Plus.
I have successfully unlocked bootloader, have had various Roms installed and have also had OrangeFox Recovery.
What I forgot to do was flash 'copy-partions' before installing Roms. Have flashed this file now, but i think this is too late.
Current working OS: LineageOS 18.1
Recovery: Lineage 18.1
All I am needing to do is change to TWRP recovery and install Magisk. However, I am unable to flash BL or recovery. The process just hangs with 'sending.....' [twrp-xxxx.lake.img]
I have tried using 'Rescue and Smart Assistant' which successfully downloads the match firmware 'LAKE_QPWS30.61_21_18_7_subsidy_DEFAULT-regulatory_XT195-3_JANZ-CFC.xml.zip'
however fails and throws and error: Fastboot Flash Single Partition.
I have tried using the 'Latest ADB Launcher' and trying various commands. It seems that the A/B partitioning system is not properly working.
When I load into Lineage Recovery it reports that Slot A is active.
Just to reiterate, the phone is booting into LinageOS 18.1, everything seems to be working, just not able to flash TWRP so i can then root the phone with Magisk.
Your help will be appreciated.
Thank you.
I had a similar issue when trying to flash using fastboot on a machine with USB 3 ports, I had to find a old machine with USB2.
Then on the USB2 machine I couldn't boot recovery after flashing the linageos recovery or twrp recovery, but I was able to boot twrp using 'fastboot boot twrp-3.5.2_9-0-lake.img' and then I was able to sideload from there.
MozzerW said:
I had a similar issue when trying to flash using fastboot on a machine with USB 3 ports, I had to find a old machine with USB2.
Then on the USB2 machine I couldn't boot recovery after flashing the linageos recovery or twrp recovery, but I was able to boot twrp using 'fastboot boot twrp-3.5.2_9-0-lake.img' and then I was able to sideload from there.
Click to expand...
Click to collapse
Hi, I've tried USB 2 ports, still yield same result.
Phone screen while in BL mode
'Flashing_unlocked'
Transfer Mode: USB Connected
Have tried multiple twrp.*.img files, but still no success.
I think there is an issue with Slot A/B because I didn't flash the copy-partitions.zip.
From all the posts I have read, people have bricked their phone and recovered it using various methods, but my phone is not bricked, just will not allow flashing of BL and Recovery. It is messed up.
Thank you.
I'm having the same issue. Can't load any TRWP image and I DID flash the copy partition.
WhiskyDrink said:
I'm having the same issue. Can't load any TRWP image and I DID flash the copy partition.
Click to expand...
Click to collapse
Just solved it by grabbing a USB hub.
SOLUTION: connect the phone using a USB hub
I try like @WhiskyDrink said :
When plugin the G7 Plus, MTP and ADB working, but fastboot “Sending 'boot.img'” dont worked at all...
The HUB worked for me
Regards
Hello, I wanted to free my pixel 5 (android12) from google and install the e.foundation os. I managed to unlock the bootloader. At further step something must have gone wrong and I came only in the recovery mode. Then I flashed TWRP and wanted to install android 11 from there. I did not know which version for my phone is the right one. TWRP has any errors displayed. I have a few years ago on another phone made a custom rom flash on it and thought I know what I'm doing but thought wrong. I selected all the check marks in the wipe data menu and formatted everything. Then nothing worked and the phone went into bootloop. Now I managed to get into the recovery mode. But I can not flash TWRP or rom. Can someone maybe give me a tip? or do I now have a 500 euro expensive stone here.
I am grateful for any advice. this flashing is very complicated for me a I had it somehow easier in memory.
I speak german and the text was created with deepl
there is a photo of the screen
Okay you can try this
Download ADB AND MINIMAL FASTBOOT
Download TWRP
1. Open ADB AND MINIMAL FASTBOOT
2. Type fastboot flash recovery /path/to/twrp.img
3. Try reboot to recovery mode.
4. If you can reboot to recovery mode (TWRP) - Copy stock rom to device and flash it.
I have also tried this with TWRP but i always get the error message:
FAILED (remote: Not allowed to flash (recovery))
i have also tried several roms to flash after unpacking.
fastboot flash bootloader runs through
fastboot flash radio runs through successfully
fastboot update image but not
and ends with the message:
FAILED (remote: Partition should be flashed in fastbootd).