Device the .img was made from is as follows:
ROM: Slim-7.1.2.build.2.0-UNOFFICIAL-20180310-1717
Model: Moto E4 XT1765
Carrier: MetroPCS
Bootloader: Unlocked
Color: Gold
debrick.img created with unlocked bootloader in TWRP on XT1765
Code:
dd if=/dev/block/mmcblk0 of=/sdcard/debrick.img bs=1024 count=2621244
I haven't used the file just yet or had the chance. Pleases let me know if it works for you. Thank you.
Download:
Code:
https://www.androidfilehost.com/?fid=1322778262904007534
MD5:
Code:
7c2de3d12af51a264b9d3c86bb902d32
how to burn in in SD, i tried in XT1765 and not work! always QS-LOAD Quallcomm
write with diskimager 1.0 in sd 16GB but no work no fastboot .
I am very confused about what to do with this .img file.
wait, why an sdcard...?
Why are yall trying to use an sd card, don't you flash .img files with a pc and fastboot?
Wolf_Link115 said:
Why are yall trying to use an sd card, don't you flash .img files with a pc and fastboot?
Click to expand...
Click to collapse
It's a debrick image. You boot those from SD card. Not saying this one works, I don't know. But the theory is sound.
after write imge set alive but when remove sd set not booting
Related
Hello everyone!
I have run into problems with my hero since I flashed Drizzy's hero rom.
My sd card reader is no longer functioning and hence I am locked into drizzy's rom without any possibility of any kind of sd card use.
The sd card can't be read from cyanogens recovery even.
Is there any way to put a new rom on the phone without access to the sd card?
(I have root if that helps)
Thanks in advance,
Hampan
Can I use the fastboot update command without an sd-card available to the phone?
you can push (=upload) with adb (command is: adb push [local] [remote]) a file to the sdcard (just connect your phone via usb to computer)
example:
update.zip is here: C:\update.zip
then do:
adb push C:\update.zip /sdcard/update.zip
then it will upload the file (about 5-10 minutes).. ready to flash
Thank you for your reply , no I can't make adb connect to the phone.
Only fastboot works, and even if adb was working I couldn't possibly make it push the update to the sdcard since the phone can't see the sd card at all.
and you are even not able to access the sdcard via cyanogen recovery AND adb shell??
No exactly, the sd card can't be reached from ANYTHING , adb shell won't connect although fastboot does, and i can use fastboot commands.
I tried using the "fastboot update update.zip" with modacos rom but got the message:
archive does not contain 'android-info.txt'
archive does not contain 'android-product.txt'
error: update package has no android-info.txt or android-product.txt
I'm thinking maybe one can flash the device without putting anything on sd via "fastboot update" .. can anyone confirm?
simply restore your nandroid backup that im sure you did.
./fastboot flash system system.img
./fastboot flash userdata data.img
./fastboot flash boot boot.img
./fastboot reboot
Thanks for your reply, yes I did make a nandroid backup and copied it to my pc
However, as it stands now I can only reach the phone from the computer with fastboot, usb is not recognized in windows and sd card is not functioning (even in cyanogen fastboot).
So, if I use my old stock nandroid backup and somehow the sd and usb is still not functioning, would there be a possibility that I would be stuck with the old slow rom forever?
Thanks for any help!
keatonreckard said:
simply restore your nandroid backup that im sure you did.
./fastboot flash system system.img
./fastboot flash userdata data.img
./fastboot flash boot boot.img
./fastboot reboot
Click to expand...
Click to collapse
Yup, now I tried .. doesn't work
C:\android-sdk-windows-1.5_r3\tools>fastboot flash boot boot.img
sending 'boot' (2560 KB)... OKAY
writing 'boot'... INFOsignature checking...
FAILED (remote: signature verify fail)
I'm sh*t out of luck aren't I?
maybe the remaining option is to send it to htc... :-( but that will cost money cuz you lost the garanty
Yup, that, sadly -Is my conclusion as well.
Anyway, the phone works as usual , just no SD and no updates.
Since I have no warranty I might just wait until a new android version is released for Hero.
Thank you all for replying and trying to help me.
stupid question, but did you check to see if it is the micro sd that went bad, not the reader? you don't need to embarrass yourself by responding, I just hope it helps if that is what it was.
I have the same problems and follow these threads:
http://forum.xda-developers.com/showthread.php?t=556335
http://forum.xda-developers.com/showthread.php?t=559106
Can't you try to 'update' (restore) it with the htc RUU .exe
?
not totally sure since i dont have a hero myself, but i think this might work...
I installed the paranoid android rom yesterday and i have problem with my sd card when i go to gallery or something it says No external storage and when i go to storage only my internal shows up...when i mount the sd card in my laptop it works perfectly...i searched for answers on google and i found that my sd card might be bricked so i searched for solution i found http://tasriri.blogspot.com/2011/01/htc-desire-usb-brick-fix.html
everything went perfect but in the end when i use the codes in terminal it says:
cant create /data/: Is a directory
help me pls :crying:
Not seen that method. Don't know if that works.
You can try to install 4ext recovery (requires s-off), it has a usb unbrick option which I've heard to be good
That recovery is also very good at partitioning your sdcard for more app space
eddiehk6 said:
Not seen that method. Don't know if that works.
You can try to install 4ext recovery (requires s-off), it has a usb unbrick option which I've heard to be good
That recovery is also very good at partitioning your sdcard for more app space
Click to expand...
Click to collapse
how to flash the reovery? and where do i download it?
Go to 4ext.net. download the apk, install it. Then from within the app u can install the recovery.
Sent from my HTC Desire using xda app-developers app
chromium96 said:
Go to 4ext.net. download the apk, install it. Then from within the app u can install the recovery.
Sent from my HTC Desire using xda app-developers app
Click to expand...
Click to collapse
i cant download the app from my phone cuz my phone says u need to put external storage i tried also to put it on my sd card but the file manager on my phone says no external storage...
EpicSmurf22 said:
i cant download the app from my phone cuz my phone says u need to put external storage i tried also to put it on my sd card but the file manager on my phone says no external storage...
Click to expand...
Click to collapse
go to the 4ext thread in my sig
download the recovery.img directly, it's in the first post
flash it through fastboot (read the fastboot bit here)
backup your sd card, then reboot into recovery from bootloader, try usb unbrick. also partition your sd card from there, and copy your backup back to sd
eddiehk6 said:
go to the 4ext thread in my sig
download the recovery.img directly, it's in the first post
flash it through fastboot (read the fastboot bit here)
backup your sd card, then reboot into recovery from bootloader, try usb unbrick. also partition your sd card from there, and copy your backup back to sd
Click to expand...
Click to collapse
Microsoft Windows [Version 6.2.9200]
(c) 2012 Microsoft Corporation. All rights reserved.
c:\platform-tools>fastboot flash recovery recovery.img
sending 'recovery' (6912 KB)...
OKAY [ 1.020s]
writing 'recovery'...
FAILED (remote: image update error)
finished. total time: 1.042s
c:\platform-tools>
didnt work... i tried with Android Flasher it says completed and everything but i still have the clockwork...
EpicSmurf22 said:
Microsoft Windows [Version 6.2.9200]
(c) 2012 Microsoft Corporation. All rights reserved.
c:\platform-tools>fastboot flash recovery recovery.img
sending 'recovery' (6912 KB)...
OKAY [ 1.020s]
writing 'recovery'...
FAILED (remote: image update error)
finished. total time: 1.042s
c:\platform-tools>
didnt work... i tried with Android Flasher it says completed and everything but i still have the clockwork...
Click to expand...
Click to collapse
eddiehk6 said:
You can try to install 4ext recovery (requires s-off)
Click to expand...
Click to collapse
you need to be s-off to flash recovery. search revolutionary and follow guide.
eddiehk6 said:
you need to be s-off to flash recovery. search revolutionary and follow guide.
Click to expand...
Click to collapse
im already s-off
hmm not absolutely sure then
you sure you installed all drivers properly? you may also need to enable usb debugging (not sure)
if that doesn't work, try renaming the recovery img to 'PB99IMG.zip', place it on sd card, and reboot into bootloader. it should find the file and ask if you want to flash it.
eddiehk6 said:
hmm not absolutely sure then
you sure you installed all drivers properly? you may also need to enable usb debugging (not sure)
if that doesn't work, try renaming the recovery img to 'PB99IMG.zip', place it on sd card, and reboot into bootloader. it should find the file and ask if you want to flash it.
Click to expand...
Click to collapse
It's not that simple to make a PB99IMG.zip. You need to do more stuff. Jmcclue had a zip version of 4ext recovery.
it is actually very easy, all u need is "recovery.img" & "android-info.txt" files (u can get the android-info.txt file from one of the Alpharev PB99IMG hboots) then simply zip the 2 files naming it PB99IMG. Anyway 4ext recovery PB99IMG in my sig.
abaaaabbbb63 said:
It's not that simple to make a PB99IMG.zip. You need to do more stuff. Jmcclue had a zip version of 4ext recovery.
Click to expand...
Click to collapse
jmcclue said:
it is actually very easy, all u need is "recovery.img" & "android-info.txt" files (u can get the android-info.txt file from one of the Alpharev PB99IMG hboots) then simply zip the 2 files naming it PB99IMG. Anyway 4ext recovery PB99IMG in my sig.
Click to expand...
Click to collapse
hah thought one or both of you might come along if i made a mistake
anyway either of you know why EpicSmurf22 is getting a "FAILED (remote: image update error)" ? i've never seen that while using fastboot..
i'm just hoping after all of this, recovery can be flashed and solve the original sd card mount problem..
dunno really, try the PB99IMG works most of the time. if not then extract the zip file and try flash recovery.img via fastboot (the recovery.img u have could be corrupt), if still not then try a different sdcard or could be ur phones memory is screwed up. got corrupt some how.
Hey guys and girls,
This is a bit of copy and paste for from my guide for the HTC U12+. I thought it might be helpful to people here too.
If you find mentions of the HTC U12+ please notify me and I will correct them.
I couldn´t find any guide on how to root the Asus Zenfone 6 without twrp yet, so I thought maybe it´s good to have one. It´s also useful for people who don´t like to boot/flash the recovery but want root access.
I also decided now to do a little write up about the A/B slot partition system.
General Information about the A/B slot partition system and seamless updates
Google firstly introduced seamless updates on the Pixel Phones and with it the A/B partition system.
So this means, contrary to non A/B devices, there are two copys of most partitions except userdata.
We have two system (system_a and system_b), two boot (boot_a and boot_b) and two vendor (vendor_a and vendor_b) partitions, amongst others (can be found further down in the partition list but let´s concentrate on these).
When booted in the OS, one slot is actively used and the other is "inactive".
The main advantage that emerges now is, that in case an OTA arrives the "inactive" partitions get updated, while the OS is running. That means while the actual OTA is happening you can use your phone just like you always do.
The following reboot will boot into the former "inactive" slot and use the seamless updated partitions. This happens seamless and just with a reboot. So OTAs are much faster!
If you are interested further here are some links:
https://www.xda-developers.com/list-android-devices-seamless-updates/
https://source.android.com/devices/tech/ota/ab/
https://source.android.com/devices/tech/ota/ab/ab_faqs
Here’s another writeup from the XDA portal!
https://www.xda-developers.com/how-...ess-updates-affect-custom-development-on-xda/
But here are a few tips and tricks:
How to reboot to bootloader to be able to use fastboot:
From booted OS with buttons: Press and hold power down until the screen goes black, then press and hold power and vol up to enter bootloader
non responding and the phone isn´t booting: press and hold power plus volume up to enter bootloader
From the OS or recovery via ADB (requires USB Debugging enabled in dev options):
Code:
adb reboot bootloader
How to get the active slot:
Code:
fastboot getvar current-slot
How to set the active slot:
A word of advice. If you don´t know what you´re doing you should probably not change slots. Because my U12+ only has a working A Slot. The B slot is without the first OTA or flashing a RUU unbootable.
Set active slot to a:
Code:
fastboot --set-active=a
Set active slot to b:
Code:
fastboot --set-active=b
How to extract the boot.img from a firmware.zip
1. Download the firmware zip from here : https://www.asus.com/Phone/ZenFone-6-ZS630KL/HelpDesk_Download/
2. Follow the steps described here: https://forum.xda-developers.com/nokia-7-plus/how-to/guide-how-to-extract-payload-bin-ota-t3830962
3. Obtain your boot.img
How to root your phone without TWRP
Prerequisites:
- unlocked bootloader
- USB-Debugging in developer options enabled
- latest adb and fastboot binaries (can always be found here
- working adb and fastboot environment
- magisk-patched boot.img
How to:
1. Download the latest magisk manager from here and install it on your phone: https://github.com/topjohnwu/MagiskManager/releases
2. Get a boot.img that fits your current firmware. Look at the point above, how to extract it from an Asus firmware zip.
Important: if you decide to use a pre-patched boot.img (available below), download it and place it in your fastboot folder, then skip to step 11!
3. Copy the extracted boot.img to your phone
4. Open the magisk manager app and tap two times on install
5. Now choose patch boot.img file and select the previously extracted boot.img you copied to your phone in the upcoming file chooser
6. Wait for the boot.img to be patched
7. Now connect your phone to your pc and make sure usb debugging is enabled in developer options
8. Open up a terminal in your fastboot folder and make sure adb is working by typing
Code:
adb devices
into terminal which should return your serial number
9. Pull the patches boot.img to your fastboot folder via:
Code:
adb pull /sdcard/Download/magisk_patched.img
10. Reboot to bootloader:
Code:
adb reboot bootloader
11. Flash the magisk patched boot.img:
Code:
fastboot flash boot magisk_patched.img
12. Congratulations you´re now rooted.
Pre-Magisk-Patched boot.imgs
Important: Make sure to download the correct version, that matches your firmware.
Downloads: https://www.androidfilehost.com/?w=files&flid=295609
Is it possible to do this and still get OTA updates from ASUS?
sidamos77 said:
Is it possible to do this and still get OTA updates from ASUS?
Click to expand...
Click to collapse
You need to unlock the bootloader for this which will prevent you from getting ota updates automatically from asus. But you can install updates manually.
Ok, great, thank you.
Remember, this will void your warranty (as per Asus' own definition). Sad, but true.
I would root it in an instant, but am hesitant due to warranty being void.
Any way to unofficially unlock the Bootloader?
vasra said:
Remember, this will void your warranty (as per Asus' own definition). Sad, but true.
I would root it in an instant, but am hesitant due to warranty being void.
Click to expand...
Click to collapse
In Europe unlocking the bootloader and rooting doesn't legally void warranty. It was ruled this way a few years ago.
Freak07 said:
[...]
Pre-Magisk-Patched boot.imgs
Important: Make sure to download the correct version, that matches your firmware.
Downloads: https://www.androidfilehost.com/?w=files&flid=295609
Click to expand...
Click to collapse
The folder WW_PHONE-16.1210.1904.75-0 which is the firmware my device has, is empty. Do you still have the prepatched boot.img of that version ? ASUS doesn't have that version for download anymore.
Thanks in advance.
If not: how can I update manually since I do not get any OTA Updates with a locked Bootloader ?
GRöder said:
how can I update manually since I do not get any OTA Updates with a locked Bootloader ?
Click to expand...
Click to collapse
https://swedroid.se/forum/threads/snabba-fragor-snabba-svar-zenfone-6.165775/page-26#post-2433773
https://swedroid.se/forum/threads/snabba-fragor-snabba-svar-zenfone-6.165775/page-37#post-2442236
Use Translator.
I managed to update my device using the stock recovery. (There is a option like "apply update from sdcard") Now it is on the -133 Firmware, so I should've been able to use the existing, pre-patched boot of that firmware. When I tried to flash it, I got the following error:
Code:
fastboot flash boot magisk_patched.img
target reported max download size of 805306368 bytes
sending 'bootb' (47064 KB)...
OKAY [ 1.094s]
writing 'bootb'...
FAILED (remote: (bootb_b) No such partition)
finished. total time: 1.106s
the getvar command returns the following output:
Code:
fastboot getvar current-slot
current-slot: b
finished. total time: 0.009s
Do you have any advice for me ?
Edit:
After being curious and trying
Code:
fastboot flash boot_a magisk_patched.img
which worked, I tried to flash it at the active slot b explicitly:
Code:
fastboot flash boot_b magisk_patched.img
which worked, too. I'm having root, now.
The point is, to specify the partition precisely (e.g. with _a or _b).
Thank you for the guide, maybe you could add my findings to make it easier for others to root their devices, @Freak07 .
GRöder said:
I managed to update my device using the stock recovery. (There is a option like "apply update from sdcard") Now it is on the -133 Firmware, so I should've been able to use the existing, pre-patched boot of that firmware. When I tried to flash it, I got the following error:
the getvar command returns the following output:
Do you have any advice for me ?
Edit:
After being curious and trying which worked, I tried to flash it at the active slot b explicitly: which worked, too. I'm having root, now.
The point is, to specify the partition precisely (e.g. with _a or _b).
Thank you for the guide, maybe you could add my findings to make it easier for others to root their devices, @Freak07 .
Click to expand...
Click to collapse
Did you download the latest adb and fastboot binaries from the link I provided in the OP?
Or did you use already existing ones or from a toolkit/easy installer etc. from somewhere on xda?
To me it sounds you were using outdated binaries.
Fastboot flash boot boot.img detects the active slot automatically if you’re on the latest binaries. Did it like this on the zenfone like on all other A/B devices I’ve owned so far and it works just fine.
Freak07 said:
Did you download the latest adb and fastboot binaries from the link I provided in the OP?
Or did you use already existing ones or from a toolkit/easy installer etc. from somewhere on xda?
To me it sounds you were using outdated binaries.
Fastboot flash boot boot.img detects the active slot automatically if you’re on the latest binaries. Did it like this on the zenfone like on all other A/B devices I’ve owned so far and it works just fine.
Click to expand...
Click to collapse
That might have been the the point. In fact, I did download them, but I used (definately outdated, because on my pc since literally years) a minimal adb and fastboot installation.
I didn't think about it, as this is my first A/B device.
I won't try it now with the latest ones, because it worked and I don't want to destroy something (since we still dont have a working TWRP for backup & recovery) but I guess you're right, and the problem were the outdated binaries.
Thank you.
GRöder said:
If not: how can I update manually since I do not get any OTA Updates with a locked Bootloader ?
Click to expand...
Click to collapse
Download the new Firmware from Asus and copy it to the root of sdcard. Unplug the usb cable or reboot or search for update in settings. It will find the update file and display a notification.
isthisadagger said:
Download the new Firmware from Asus and copy it to the root of sdcard. Unplug the usb cable or reboot or search for update in settings. It will find the update file and display a notification.
Click to expand...
Click to collapse
In fact, I tried that before I tried the stock-recovery-method (found it at the ASUS FAQ-pages), but it didn't work, even after a reboot, no notification showed up.
GRöder said:
I managed to update my device using the stock recovery. (There is a option like "apply update from sdcard") Now it is on the -133 Firmware, so I should've been able to use the existing, pre-patched boot of that firmware. When I tried to flash it, I got the following error:
Code:
fastboot flash boot magisk_patched.img
target reported max download size of 805306368 bytes
sending 'bootb' (47064 KB)...
OKAY [ 1.094s]
writing 'bootb'...
FAILED (remote: (bootb_b) No such partition)
finished. total time: 1.106s
the getvar command returns the following output:
Code:
fastboot getvar current-slot
current-slot: b
finished. total time: 0.009s
Do you have any advice for me ?
Edit:
After being curious and trying
Code:
fastboot flash boot_a magisk_patched.img
which worked, I tried to flash it at the active slot b explicitly:
Code:
fastboot flash boot_b magisk_patched.img
which worked, too. I'm having root, now.
The point is, to specify the partition precisely (e.g. with _a or _b).
Thank you for the guide, maybe you could add my findings to make it easier for others to root their devices, @Freak07 .
Click to expand...
Click to collapse
sorry guy,
how you unlocked the bootloader ? for me official tool asus doens't work. error due to internet connection is the message.
please can you explain every step ? thanks
Ya how do we unlock the bootloader without asus knowing it
MirkoMirko9 said:
sorry guy,
how you unlocked the bootloader ? for me official tool asus doens't work. error due to internet connection is the message.
please can you explain every step ? thanks
Click to expand...
Click to collapse
nikhil18 said:
Ya how do we unlock the bootloader without asus knowing it
Click to expand...
Click to collapse
I used the official app, while the device was connected to the internet. So yes, ASUS knows that I unlocked the device.
The device was still at the -75 firmware, when I did it.
@MirkoMirko9 If you can live with asus knowing that you unlocked the device, try it again with active internet connection.
As far as I know, there is no other method yet.
unable to unlock bootloader with the official unlock device tool, it is showing network error although my network is alright. Any workaround?
QuazIqbal said:
unable to unlock bootloader with the official unlock device tool, it is showing network error although my network is alright. Any workaround?
Click to expand...
Click to collapse
https://forum.xda-developers.com/showpost.php?p=79817571&postcount=31
magisk_patched boot.img for .156 firmware is uploaded to the patched boot.imgs folder
I hard bricked my device few days back with custom rom installed somehow I recovered using blank flash but the problem is that now the bootloader is locked with custom rom i cannot boot into the system neither i can flash stock rom.(preflash validation failed)
I think i can get through this if i flash unlocked bootloader ie. aboot partition from another device.
So i request if some one can provide me with the dump to resolve this issue. I need oreo bootloader C1.81 version or above
Just run this command on terminal emulator or adb shell
dd if=/dev/block/bootdevice/by-name/aboot of=/sdcard/aboot.img
dd if=/dev/block/bootdevice/by-name/abootbak of=/sdcard/abootbak.img
ronyroy said:
I hard bricked my device few days back with custom rom installed somehow I recovered using blank flash but the problem is that now the bootloader is locked with custom rom i cannot boot into the system neither i can flash stock rom.(preflash validation failed)
I think i can get through this if i flash unlocked bootloader ie. aboot partition from another device.
So i request if some one can provide me with the dump to resolve this issue. I need oreo bootloader C1.81 version or above
Just run this command on terminal emulator or adb shell
dd if=/dev/block/bootdevice/by-name/aboot of=/sdcard/aboot.img
dd if=/dev/block/bootdevice/by-name/abootbak of=/sdcard/abootbak.img
Click to expand...
Click to collapse
What is your model no of device
Bootloader version is MBm-2.1-albus_retail-b625135-190911
Someone said that «The recovery image is only to be used for SAR A-only devices. That's not the case for your device so you have to find the boot image somehow.» (because I had dowloaded some images from the internet, github, that is the following:
stock_recovery_Z00ED_WW_Phone_13.10.7.1.img (32 mb)
twrp-3.0.2-0-ze500kl.img (15 mb)
So my question is: how can I get the boot image of my smartphone, an Asus Zenfone 2 Z00ED?
I tried with adb:
Code:
adb shell dd if=/dev/block/bootdevice/by-name/boot of=boot.img
, but I got an error message
Code:
permission denied
I need this image to root my device with Magisk: don't I?
Thank you
You could try use fastboot mode to tell the phone to do a "tethered" boot into twrp recovery you downloaded (a. To see if that's the recovery to use on the phone b. To extract the boot.img to sdcard and mtp over to pc) but I don't have that specific model so I can't promise success, it's just an idea to ponder ? also you may need to unlock your bootloader before dumping an image of it