Related
Hey guys,
apart from my Un-Bricking-Thread I wanted to start a Thread dealing with how to prevent a brick in the first place.
--- Already bricked your Prime? Read on here, maybe you can recover it ---
In the last days I learned quite a few things about the TFP, its CWM and how to work with it. I also hard bricked my Prime so I certainly know what I am talking about
Unfortunately ASUS didn't fully unlock our Bootloader. We still can't use NVFLASH for low level flashs.
This also means that we can't recover some things we could with NVFLASH access (like a broken bootloader).
So lets start with the things you better not do:
DON'T
Once you unlocked the prime and installed CWM, do NOT try to install a super blob from ASUS (that is a blob file from one of the 'full' updates from their site)
It seems that doing so totally bricks your Prime with no chance of recovery... (happened at least twice so far)
Don't flash kernels like you used to flash (with write_raw_image to /boot). This does not work on the Prime. More on how to do it later.
Don't rely on your newly created ROM to work, ALWAYS have a backup of a working ROM on your sdcard (or a zip of a working ROM)
Currently we can't mount the USB-Storage from inside CWM, so transferring files to the Prime while being in recovery is not as easy for many not so advanced users.
Always make sure you have all files you need before rebooting to recovery.
DO
Kernel flashing: There seem to be two methods on how to flash a new kernel. One is safer but needs a bit more work, and the other is rather unsafe but okay when you (or the ROM dev) know what needs to be done.
Flash your boot.img via fastboot. This is usually rather safe (as safe as fastboot can be) but needs you to have a working fastboot environment. Update: It seems kernel flashing via fastboot does not work at all. Fastboot doesn't give you an error but it doesn't update the kernel either...
Flash your kernel via the /staging partition. In order to use this method you first need to pack your boot.img into a blob file.
Then you need put the data from the blob file to the /staging partition.
Once you reboot the kernel gets automatically installed.
Please be aware that you can flash almost everything like this, even the bootloader.
So if you screw up packing the blob file, you could easily brick your Prime.
The advantage of this method is that the user doesn't need to do anything, but you really need to take care of what you are doing.
Also make sure that the /staging partition is ALWAYS unmounted before flashing anything to it. Otherwise this will result in a Brick 3.
Always make a backup of your current ROM before flashing anything else. As stated earlier, we currently have no access to the sdcard in recovery, so transferring files to Prime is not as easy in recovery mode.
So I hope I can find some more topics in the future, but for now that's it
Diamondback said:
DON'T
Once you unlocked the prime and installed CWM, do NOT try to install a super blob from ASUS (that is a blob file from one of the 'full' updates from their site) It seems that doing so totally bricks your Prime with no chance of recovery... (happened at least twice so far)
Click to expand...
Click to collapse
But but but how can I has update?! I want Update! RWAR!
Thanks, thanks, bump, and thanks again! Due to the current state of our device's development (especially with an early build of CWM), misinformation floating around, etc. this is invaluable! Now I know what "staging" is and what its use is. Well done - keep up the great work
Sent from my Transformer Prime TF201 using xda premium
mtotho said:
But but but how can I has update?! I want Update!
Click to expand...
Click to collapse
Use custom ROMs. We currently don't really know if it ALWAYS bricks your Prime. We just know that two updates bricked two primes
I think nobody wants to try
Diamondback said:
Use custom ROMs. We currently don't really know if it ALWAYS bricks your Prime. We just know that two updated bricked two primes
I think nobody wants to try
Click to expand...
Click to collapse
Yea I am just kidding. I knoweth better plus I like custom roms (and I am very flash happy)
I won't be happy until we get some sort of nightly rom that I can flash daily
thanks diamondback this prob saved me lots of time and the almost $700 i have in my device+dock
Sent from my Transformer Prime TF201 using xda premium
Will be possible to use NVFLASH anytime? Have we to look for a dev or is Asus that must upgrade its apk?
Thanks Diamondback for making this. This needs to become a sticky immediately. To many people are blindly unlocking then get mad when they find out they can't do OTA updates. Or people installing CMW without even unlocking and blaming others issues on that when they found out device should've been unlocked first..lmfao
Unlock tool release=operation sabotage for those who don't know any better or ignorant or lazy to research first. QnA section had several people with semi or hard bricked primes. Primes are dying off left n right..lol
Diamondback said:
Unfortunately ASUS didn't fully unlock our Bootloader.
Click to expand...
Click to collapse
So you download their software, run it to completely void your warranty (they've already denied support on one unrelated hardware issues that I know of), and you STILL don't have full access?
WTF!?!?!!?
Not being able to use NVFlash has completely put me off, for me NVFlash was the ultimate aim for unlocking the bootloader ... pretty **** !
(unhappy smiley)
Diamondback, I'm so sorry to hear that you bricked your Prime! Any luck getting unbricked yet?
Thank you so much for posting this invaluable guide. You are generous beyond words, to go to this effort to save other users from the lessons you had to learn the hard way. There aren't enough thanks in the world.
If we can at least ATM use fastboot that's a good thing. A good thing for fastboot is you can first do-
fastboot boot boot.img and it will boot the kernel the first time, basically so you can test it before it writes the .img
then you can fastboot flash boot.img to write the image. It'll work for now, sucks that any non-dev who just wants to flash a kernel has to set up fastboot
Edit- girluvsdroid- just saw you were in wilmington- me too.
This was very helpful.
BUMP!
Reading is fundamental! Lol I don't know how many times I've just glanced over post, just to get the newest firmware, and kernals, just to end up on the verg of a bricked device. Thanks.
What ?
So If I UnlockBootLoader
I cant OTA Anymore ? Seriously
AndyMclamb said:
What ?
So If I UnlockBootLoader
I cant OTA Anymore ? Seriously
Click to expand...
Click to collapse
But why would you unlock if you were not going to install custom roms (that have the latest OTA built in) anyway?
Diamondback said:
Flash your boot.img via fastboot. This is usually rather safe (as safe as fastboot can be) but needs you to have a working fastboot environment.
Click to expand...
Click to collapse
Hmm.. Does not seem to work for me. Built a kernel, switched in fastboot mode. Then:
Code:
$ sudo ./fastboot -i 0x0b05 boot zImage blob.LNX-ramdisk.cpio.gz
creating boot image...
creating boot image - 4214784 bytes
downloading 'boot.img'...
OKAY [ 0.748s]
booting...
FAILED (remote: ()
finished. total time: 0.749s
Prime displays: Failed to process command boot error(0x120000)
Any advice?
saturn_de said:
Hmm.. Does not seem to work for me. Built a kernel, switched in fastboot mode. Then:
Code:
$ sudo ./fastboot -i 0x0b05 boot zImage blob.LNX-ramdisk.cpio.gz
creating boot image...
creating boot image - 4214784 bytes
downloading 'boot.img'...
OKAY [ 0.748s]
booting...
FAILED (remote: ()
finished. total time: 0.749s
Prime displays: Failed to process command boot error(0x120000)
Any advice?
Click to expand...
Click to collapse
Yes. fastboot boot does not work at all.And we also found out that kernel flashing via fastboot does not work either.
You have to flash your kernels via a custom made blob ;-)
Gesendet von meinem Desire HD mit Tapatalk
Prime Stuck in CWM boot loop hell.
I have a Prime that is stuck in a CWM Recovery boot loop.
Brick 1a
All thanks (sincerely) to Viperboy and his ViperMOD PrimeTime 4.5, I had my Prime rooted, boot loader unlocked and loaded with ClockworkMOD Recovery 5.5.0.4.
I used CWM to create a backup, wipe the data/factory, cache partition and Dalvik cache, rebooted the system (from CWM menu) just to verify that the unit was really wiped back to setup, powered down the unit, rebooted into CWM Recovery (using Power while holding Vol.Down, wait for small/white text, Vol.Up) and Restored using the previously created Backup.
I rebooted Android from CWM menu and my Prime was restored.
Everything was great, but not for long.
The next time that I booted into CWM recovery I selected “Reboot System Now”.
It went dark, displayed the ASUS splash screen, went dark and went back into CWM.
I am stuck in that loop.
I have tried all the suggested fixes I can find but all methods are useless because:
1. I can’t acquire an ADB connection because Windows doesn’t identify the bricked Prime correctly and won’t install the USB drivers. Device Manager sees “Full Android as Emulator”.
2. I can’t boot into the boot loader to use Fastboot because I never see the option to choose it. It boots or reboots directly into CWM after “Booting Recovery Kernel Image”, ever while holding the Vol.Down button.
I have repeatedly tried installing and uninstalling the drivers by installing and uninstalling the Asus Sync and Asus Android USB Drivers. I have repeatedly tried to install the drivers via the Device Manager. No good. I’ve installed and uninstalled Android SDK Tools repeatedly.
Is there a way out of this? I hope I'm not efed.
Thank you in advance for any help.
Temporalmind said:
I have a Prime that is stuck in a CWM Recovery boot loop.
Brick 1a
[..]
I apologize for the length of this post. I hope I’m not efed.
Click to expand...
Click to collapse
Please try to manually installing these drivers here
http://forum.xda-developers.com/showthread.php?t=1426502
Adb should be working afterwards
Universal Naked Driver works great!
Ok, you saved me and my precious.
Your drivers were exactly what I needed.
After installing them in Device manager I was able to achieve a “ASUS Android Composite ADB Interface” connection.
Following the “How to Unbrick your Transformer Prime (or not)”, Option 1a and restoring I’m up and running.
Thank you!
Then, I deliberately caused the boot looping condition again to see if I could figure out how I got there.
There is an app that I think comes preinstalled on the Prime called ”Transformer Recovery Boot”. The icon is labeled "Recovery". This is the app that took me into the Brick 1a the first time and I duplicated it the next time I used it.
Then I was able to ADB my way back to civilization, again.
Thought I’d pass that on incase it helps to determine why the unlocked Prime seems to be so susceptible to bricking.
Again, Thank You!
Did my best to avoid having to ask for help, but looks like I've run out of ideas. I've got a 7840 that currently refuses to boot past the recovery screen, thanks (probably) to my own incompetence. Here's what happened along the way to this point:
First, probably important to note: my tablet is a Chinese-released 7840 running 5.0.2 Lollipop. The hardware is identical from what I can tell, but the software was definitely a bit tweaked as there were no Google services installed. (And sideloading any of the Google services always failed no matter how I went about it.) This is basically why I decided to start messing around with things.
Attempted to load the developer firmware. Wound up in the dreaded "Intel Inside" bootloop, but thanks to @xBIGREDDx and his unbrick.zip (http://forum.xda-developers.com/showpost.php?p=60663442&postcount=2) I was able to return to normal booting. No matter how many times I attempted to flash the open source firmware, I always got stuck in the bootloop and had to flash the unbrick.zip to be able to do anything. No ability to exit the bootloop in order to reach the bootloader meant this was a big impasse.
I then decided to use the tethered CWM method to root the device for the purposes of giving sideloading the Play Store another try. That worked just fine and I was able to root my 7840 without a hitch. I then created a nandroid backup (which suspiciously didn't generate an MD5 file) in case I managed to really screw things up trying to sideload the Google Services.
That's when I thought wiping and recovering the 4.4.4 Kit Kat nandroid backup might be a good idea. This of course didn't work, so I wiped and restored my own 5.0.2 backup. However, at this point things wouldn't boot no matter what I did. I would see the boot screen with the Dell logo and the Lollipop-style ANDROID text, but after a couple of minutes everything would reboot and after a couple of tries the device would boot to recovery and just sit.
After fiddling around with trying different restore methods, I decided to see if I could flash the developer firmware to no avail. (Unable to write to OSIP, security error, etc.) Then I gave @anggusss's 5.0.1 OTA update.zip a try. (http://forum.xda-developers.com/showpost.php?p=60632439&postcount=21) That gave me a different error:
"Can't install this package (Fri Apr 24 13:29:34 CST 2015) over newer build (Fri Apr 24 13:58:18 CST 2015)."
Frustrating to see that a build a half hour newer might be all I need. So, if any of you happen to have captured the 5.0.2 OTA build (or can help me tweak the 5.0.1 build to report itself as newer), would you mind giving me a hand? Would be most appreciative. I've written to Dell open-source support but don't expect to hear back for another week or so. It'd be nice to not be using the Venue as a paperweight for a week.
wirebook said:
No matter how many times I attempted to flash the open source firmware, I always got stuck in the bootloop and had to flash the unbrick.zip to be able to do anything. No ability to exit the bootloop in order to reach the bootloader meant this was a big impasse.
Click to expand...
Click to collapse
Out of interest, how was the tablet booted when you flashed the unbrick.zip (did you volup + power or just regular boot?) ?
Going back to the open-source firmware won't help, because they 4.x to 5.x transition included a re-partitioning, and the bootloader in the 4.x firmware doesn't understand the new partition scheme.
If you boot with the vol. down key held, do you get into fastboot mode? If you can, then you should be able to flash a system image and boot image. I have those pulled from my device; I can post them for you to try later tonight.
anggusss said:
Out of interest, how was the tablet booted when you flashed the unbrick.zip (did you volup + power or just regular boot?) ?
Click to expand...
Click to collapse
I've never gotten vol. up + power to do anything, is that normal? Only vol. down + power, and that'll get me into fastboot mode.
xBIGREDDx said:
Going back to the open-source firmware won't help, because they 4.x to 5.x transition included a re-partitioning, and the bootloader in the 4.x firmware doesn't understand the new partition scheme.
If you boot with the vol. down key held, do you get into fastboot mode? If you can, then you should be able to flash a system image and boot image. I have those pulled from my device; I can post them for you to try later tonight.
Click to expand...
Click to collapse
Ah, well this sounds like it's my problem, then. If you can get those images to me to try I'd be most appreciative! Should be able to give it a shot as I'm still able to get into fastboot.
wirebook said:
Ah, well this sounds like it's my problem, then. If you can get those images to me to try I'd be most appreciative! Should be able to give it a shot as I'm still able to get into fastboot.
Click to expand...
Click to collapse
system.img
This is inside a .zip file because I don't know how to get only the important bits, so I got the whole /system partition. Just unzip then 'fastboot flash system system.img'
boot.img
This is straight from the OTA zip.
You will be pre-rooted. Let me know if this goes well. :good:
xBIGREDDx said:
system.img
This is inside a .zip file because I don't know how to get only the important bits, so I got the whole /system partition. Just unzip then 'fastboot flash system system.img'
boot.img
This is straight from the OTA zip.
You will be pre-rooted. Let me know if this goes well. :good:
Click to expand...
Click to collapse
Thanks a lot for those! Flashed both boot and system, though the system gave me some sort of error on my machine ("Invalid sparse file format at header magi") and then continued to flash something ("sending sparse 'system'"). I saw the red text of some sort of error on the tablet but wasn't able to read it fast enough. The system flash did seem a bit suspiciously fast, though...
Anyway, now waiting to see if anything boots. Been sitting on the Dell/Powered By Android screen for a couple of minutes, though, so if nothing else it looks like I've at least found myself in a new place. Will try reflashing if no improvement and then get back with results!
Sorry if this is considered spamming my own thread, but didn't seem right to just edit my earlier post.
Couldn't get the system image to flash. First got the error about needing to flash as a sparse system, which seemed to be fine. But when the device tried to write the sparse chunk to the partition, it threw an error. ("remote: flash_cmds error!") Thought this might've been a bug of my particular version of adb/fastboot, but updating or trying a different version didn't work any better. In fact, things got worse as I can't even run fastboot on my machine (Windows) anymore without the program crashing on me.
Jumped over onto my Mac and things seemed to be going better, but no progress was made. Still threw that error whenever it came time to write that first sparse chunk. Might my partition table be totally out of whack? (If so, how do I go about fixing it without easy access to an adb shell?)
In other news, I realized the back of the tab has "Venue 8 784001" engraved on it, so there might be hardware / bootloader changes that I can't beat...
Well, I'm not 100% sure it's going to be able to flash the system.img correctly, I thought I could just pull it from my device and it would flash fine, but apparently not. It would be interesting to see what your partition table looks like, but I don't know of a way to get that without having a root shell.
If you have a hex editor or know how to use dd, try chopping off like 200 MB from the end of the image (I think it's all zeroes for at least that much) and see if it flashes then.
If you don't know how to do that, I could upload a modified image for you.
xBIGREDDx said:
Well, I'm not 100% sure it's going to be able to flash the system.img correctly, I thought I could just pull it from my device and it would flash fine, but apparently not. It would be interesting to see what your partition table looks like, but I don't know of a way to get that without having a root shell.
If you have a hex editor or know how to use dd, try chopping off like 200 MB from the end of the image (I think it's all zeroes for at least that much) and see if it flashes then.
If you don't know how to do that, I could upload a modified image for you.
Click to expand...
Click to collapse
wirebook said:
Sorry if this is considered spamming my own thread, but didn't seem right to just edit my earlier post.
Couldn't get the system image to flash. First got the error about needing to flash as a sparse system, which seemed to be fine. But when the device tried to write the sparse chunk to the partition, it threw an error. ("remote: flash_cmds error!") Thought this might've been a bug of my particular version of adb/fastboot, but updating or trying a different version didn't work any better. In fact, things got worse as I can't even run fastboot on my machine (Windows) anymore without the program crashing on me.
Jumped over onto my Mac and things seemed to be going better, but no progress was made. Still threw that error whenever it came time to write that first sparse chunk. Might my partition table be totally out of whack? (If so, how do I go about fixing it without easy access to an adb shell?)
In other news, I realized the back of the tab has "Venue 8 784001" engraved on it, so there might be hardware / bootloader changes that I can't beat...
Click to expand...
Click to collapse
When you dump an image is raw.ext4 it has to be converted to sparse image format for android 5.0.2
social-design-concepts said:
When you dump an image is raw.ext4 it has to be converted to sparse image format for android 5.0.2
Click to expand...
Click to collapse
Well I found the source for img2simg but it won't do me much good... you wouldn't happen to have a pre-built tool handy would you?
xBIGREDDx said:
Well I found the source for img2simg but it won't do me much good... you wouldn't happen to have a pre-built tool handy would you?
Click to expand...
Click to collapse
I think the image you passed me already employed some kind of compression on it, as I was getting errors about an invalid sparse data header or something like that. (The size on the disk was also less than the reported image size.) Unfortunately I'm unable to mount or convert it on any of my machines so I'm a bit useless.
Thanks everyone for all the help you've been, by the way!
wirebook said:
I think the image you passed me already employed some kind of compression on it, as I was getting errors about an invalid sparse data header or something like that. (The size on the disk was also less than the reported image size.) Unfortunately I'm unable to mount or convert it on any of my machines so I'm a bit useless.
Thanks everyone for all the help you've been, by the way!
Click to expand...
Click to collapse
It's just a dump straight from my system partition. I don't have my tablet with me so I'm not certain on file paths but essentially I did:
dd if=/dev/block/by-name/system of=/storage/sdcard1/system.img
So it's a raw dump of the system partition, whatever happened to be in there.
I think the fastboot command tries to sparse things on its own, but fails?
If you want to try re-partitioning (could be dangerous, could be harmless), try these commands with the partition file from the OTA package:
EDIT: For anyone else coming along, don't do this, it didn't work out well for wirebrook. /EDIT
Code:
fastboot oem start_partitioning
fastboot flash /tmp/partition.tbl kk2lp_partition.tbl
fastboot oem partition /tmp/partition.tbl
fastboot erase system
fastboot erase cache
fastboot oem stop_partitioning
You may also want to erase data while you're in there.
xBIGREDDx said:
It's just a dump straight from my system partition. I don't have my tablet with me so I'm not certain on file paths but essentially I did:
dd if=/dev/block/by-name/system of=/storage/sdcard1/system.img
So it's a raw dump of the system partition, whatever happened to be in there.
I think the fastboot command tries to sparse things on its own, but fails?
Click to expand...
Click to collapse
That must be what's happening. I'll fiddle with things a bit more later on. It's a bummer there aren't any custom ROMs I could simply flash as an alternative to getting stock up and running...
xBIGREDDx said:
Well I found the source for img2simg but it won't do me much good... you wouldn't happen to have a pre-built tool handy would you?
Click to expand...
Click to collapse
xBIGREDDx said:
It's just a dump straight from my system partition. I don't have my tablet with me so I'm not certain on file paths but essentially I did:
dd if=/dev/block/by-name/system of=/storage/sdcard1/system.img
So it's a raw dump of the system partition, whatever happened to be in there.
I think the fastboot command tries to sparse things on its own, but fails?
Click to expand...
Click to collapse
It's looking for the sparse magic header that's not there I can when I get home you could also try to use 7zip to compress it to a .gz but I believe Intel stopped support for that format in 4.4.4.
I'm at work I have it at home if your on Linux and want to convert it.
social-design-concepts said:
It's looking for the sparse magic header that's not there I can when I get home you could also try to use 7zip to compress it to a .gz but I believe Intel stopped support for that format in 4.4.4.
I'm at work I have it at home if your on Linux and want to convert it.
Click to expand...
Click to collapse
Not sure this'll be useful for me any more because... (see below)
xBIGREDDx said:
If you want to try re-partitioning (could be dangerous, could be harmless), try these commands with the partition file from the OTA package:
Code:
fastboot oem start_partitioning
fastboot flash /tmp/partition.tbl kk2lp_partition.tbl
fastboot oem partition /tmp/partition.tbl
fastboot erase system
fastboot erase cache
fastboot oem stop_partitioning
You may also want to erase data while you're in there.
Click to expand...
Click to collapse
Gave this a shot and partitioning seemed to work just fine. Flashing the OTA boot.img worked just fine, and attempting to flash your system.img once again threw an error at me. Thought I'd perform a reboot at this point (bad idea!) to see what I was working with and then I found myself with @anggusss' USB screen. (http://forum.xda-developers.com/showpost.php?p=60675581&postcount=5) Probably should've tried flashing a something else just to see if that did anything.
Guessing I've now got a brick, because I'm no longer able to get it to register with Fastboot. I can, however, flash the open-source firmware and the unbrick.zip firmware, which reacts exactly like when @anggusss did it. We'll have to see if Dell ever gets back to my original query for help, otherwise might have to look into contacting Dell for a replacement.
You might have better luck, just using one of the tethered TWRP recoveries, If someone with a working system backups up system via TWRP recovery and shares it you could use the TWRP recovery to restore it.
I have Linux version tethered TWRP up and SDC has Windows version of tethered TWRP up.
Linux version
http://forum.xda-developers.com/android/development/linux-version-twrp-2-8-6-0-tethered-t3123075
Windows Version
http://forum.xda-developers.com/android/development/intel-android-devices-root-temp-cwm-t2975096
vampirefo said:
You might have better luck, just using one of the tethered TWRP recoveries, If someone with a working system backups up system via TWRP recovery and shares it you could use the TWRP recovery to restore it.
I have Linux version tethered TWRP up and SDC has Windows version of tethered TWRP up.
Linux version
http://forum.xda-developers.com/android/development/linux-version-twrp-2-8-6-0-tethered-t3123075
Windows Version
http://forum.xda-developers.com/android/development/intel-android-devices-root-temp-cwm-t2975096
Click to expand...
Click to collapse
Thanks for the thought, but if I can't get into Fastboot mode (or get the computer to recognize the device as being in Fastboot mode)... kinda unable to use it.
wirebook said:
Gave this a shot and partitioning seemed to work just fine. Flashing the OTA boot.img worked just fine, and attempting to flash your system.img once again threw an error at me. Thought I'd perform a reboot at this point (bad idea!) to see what I was working with and then I found myself with @anggusss' USB screen. (http://forum.xda-developers.com/showpost.php?p=60675581&postcount=5) Probably should've tried flashing a something else just to see if that did anything.
Guessing I've now got a brick, because I'm no longer able to get it to register with Fastboot. I can, however, flash the open-source firmware and the unbrick.zip firmware, which reacts exactly like when @anggusss did it. We'll have to see if Dell ever gets back to my original query for help, otherwise might have to look into contacting Dell for a replacement.
Click to expand...
Click to collapse
Oh man, sad to hear, I've done that successfully in the past, they must have changed something in the process. I check just about every day for an update to the dev. firmware. Last time around it took them just over two months from release, so maybe, end of June?
xBIGREDDx said:
Oh man, sad to hear, I've done that successfully in the past, they must have changed something in the process. I check just about every day for an update to the dev. firmware. Last time around it took them just over two months from release, so maybe, end of June?
Click to expand...
Click to collapse
Fingers shall stay crossed till the end of the month, then! Contacted Dell Support and- just as I predicted- they don't want to help out. Something about being unable to do anything at all for Dell products purchased outside of their support areas (US and Canada). What a joy of a phone call that was...
An internet search landed me on guides for unbricking the Asus Zenfone displaying a similar USB symbol. They used the xFSTK Downloader to flash a set of files which then gave them renewed access to the bootloader (and thus fastboot). Played around with the xFSTK-Downloader and Manufacturing Flash Tool apps and can see the 7840 and even flash the (open-source and unbrick.zip) firmware, however I'm at a loss for what I might use for the Operating System flash files. Anybody have any thoughts?
Feel like I'm so close to getting this thing unbricked. If I could just figure out where to find the .bin "OS Image" that the tool wants...
Edit: Would also need the droidboot binary. FIngers crossed for Dell to release all of this soon...
Hello everyone this is my fist guide so be kind with the formatting, i will get better as I post more. I am writing this guide, because like you, the reader, I had installed lineageOS 14.1 and set up the phone and realized there was encryption on it, and with that tried to wipe it in twrp just to find out that it only wiped the encryption key, but not the encryption itself. Don't panic, it isn't all your fault, XD. Stay calm, the last thing you need is to be freaking out, flashing random zips in hopes of fixing it. I will give credit to all of the developers whose tools i am linking at the bottom.
Now that the introductions are out of the way, time for the complimentary dose of warning.
WARNING: Doing this won't guarantee that this will fix it, as every situation can vary. I am not responsible for any bricked devices, thermal reactors coming from your phone after this, or modding before it was cool.
Assuming you can still get into fastboot first you need to gather these files if you don't have them yet.
- Minimal adb and fastboot on windows after installing just drag to desktop to add files to it
- Qualcomm fastboot drivers for axon7tool.exe and for fastboot and adb
- TWRP 3.0.4-1 official for Axon 7
- B29 rollback modded zip on the second tab
- Nougat modem and bootstack
- Tenfar's axon7root.exe (just in case you can't use fastboot. that's what i used because i don't know how to use axon7tool.exe)
- Fastboot image to get fastboot working again flash it in twrp after getting twrp installed again through axon7root.exe
- Some time because this will likely take an hour of your time, assuming you have the drivers and files already downloaded, longer if not and slow internet.
- LineageOS 14.1
- GAPPS 7.1.1 ARM 64
- almost forgot, you also need a microsd card to store the files because we will be wiping your entire internal with this, so back up your lovely dank memes or forever hold the loss.
Step 0.5. if you don't have fastboot working flash the bootloader unlock file by drakenfx to get it working again. if you don't have twrp for whatever reason go to the guide for axon7root.exe linked above and reboot to edl mode by holding all buttons down and have your phone connected to computer to know you are there. there won't be a vibration to let you know, just your computer telling you it has a connected device. now flash twrp, by first renaming the recovery to recovery.img and putting it in the adb folder along with the the root exe and do 'axon7root.exe -p (insert your com number listed in device manager) -r' (without the ' obviously) and it should send the recovery. if it doesn't see your device. make sure you have the drivers installed and make sure you have put down your com number where i left the () at
Step 1. assuming your device boots to this beautiful screen. you need to go back to twrp and drag the B29 zip from your computer to your external sd card from mtp and go to mount and mount system read-only this is very important.
Step 2. flash the B29 modded and let it go through. this will take a few minutes. if the progress bar automatically jumps to the end, you didn't go read only.
Step 3. after it finishes reboot into system and let it set up your system, you can skip through because we will be resetting again anyhow.
Step 4. reboot back to recovery. you can do this by using that pesky bl unlocked message by pressing up on volume as soon as it shows and selecting recovery. there you can see you have stock recovery, don't panic this is what we need. select wipe data factory reset and let it do it
Step 5. go back and skip set up again and reboot to bootloader where you can now 'fastboot flash recovery recovery.img' to get back twrp.
Step 6. flash the nougat bootstack and modem i had you download. after flashing that, go to wipe: Advanced wipe. Select Dalvik, system, data, cache and swipe to wipe. this will format it as ext4 which is what is required to get to lineageOS
Step 7. flash lineageos 14.1 and your gapps category and wait to let it finish. Note, you don't have to flash the modem more than once after flashing lineageos, even for updating. just after leaving B29
Step 8. reboot to make sure your encryption problem is not there
Step 9. set up phone and profit.
If you have done everything right, you shouldn't have bricked and should be back to lineageos 14.1 with no further problems. If you skipped around and got yourself bricked, congratulations because i am not the best at fixing problems, and i can try to help, but you will be at the mercy of the Best devs this community has to offer.
Now to the part where I thank all the Devs who, without their tireless time and effort, would not have made this guide possible and development into this phone in the first place. @Unjustified Dev for the lineageOS build i use as my daily driver for now; you rock dude. ^^
@DrakenFX oh god where do i begin. for the bl unlock zip, B29 modded ota, inspiration to the rest of the community, etc.
@tenfar for the axon7root.exe tool used
@sixohtew for his constant help and advice with not only this guide, but with teaching me to build android. if you are interest in learning how to compile android for any device, he can probably help. he has a very fair deal and is amazing at what he does.
Thank you all for your copious hours of time spent in the building of each great tool and to the community as a whole. Everyone, these guys are amazing, even if i have only talked to one of them. Be sure to stop by and donate.
If i have left anyone's name out, please hit me up and i will add you to the credits, and to that i apologize.
Happy flashing!
I read through your guide several times. I'm missing the point here. At which step does the decryption get removed?
gpz1100 said:
I read through your guide several times. I'm missing the point here. At which step does the decryption get removed?
Click to expand...
Click to collapse
Sorry for delayed response, it gets removed when you do the factory reset in stock recovery. For some reason TWRP can't remove it from /data in nougat but stock recovery can in B29.
Wipe->Format Data in TWRP removes all encryption from /data and /sdcard. Did you try that before reinstalling the stock recovery? I've had weird experiences in the past with stuck encryption.
QuantumFluxx said:
Wipe->Format Data in TWRP removes all encryption from /data and /sdcard. Did you try that before reinstalling the stock recovery? I've had weird experiences in the past with stuck encryption.
Click to expand...
Click to collapse
I did try it. It doesn't wipe it because there is a bug with TWRP for our phone. I would wipe and even format data and it wouldn't work. If you go to the official TWRP thread it even warns you that if you have encryption to not wipe. We had a dev who wiped and it got rid of the encryption key and not the encryption, like what happened to me. I tried to wipe so many times and had to revert. Long process but I got my phone to work again
Rip me
So I was bricked to the point where I was able to access TWRP and if I flashed any ROM, even after formatting data, I would reach a Decryption unsuccessful screen on my A2017U. I followed the guide from step 0.5, since fastboot was not working. After flashing the bootloader unlock file via TWRP, I was not able to access anything, further bricking the device. It boots within a second to a black screen, and reboots to it if I hold the power button or any combination for recovery.etc. I can not go to EDL mode; Axon7tool detects it though when it is in this state, and is able to send files successfully. However, it still stays in this black screen. Is there any way to get back to a functioning phone at this point?
Edit: It is apparently always in EDL? It shows up and is identified by my PC as QUSB_BULK...
navsterama said:
So I was bricked to the point where I was able to access TWRP and if I flashed any ROM, even after formatting data, I would reach a Decryption unsuccessful screen on my A2017U. I followed the guide from step 0.5, since fastboot was not working. After flashing the bootloader unlock file via TWRP, I was not able to access anything, further bricking the device. It boots within a second to a black screen, and reboots to it if I hold the power button or any combination for recovery.etc. I can not go to EDL mode; Axon7tool detects it though when it is in this state, and is able to send files successfully. However, it still stays in this black screen. Is there any way to get back to a functioning phone at this point?
Edit: It is apparently always in EDL? It shows up and is identified by my PC as QUSB_BULK...
Click to expand...
Click to collapse
Can you still get into recovery with power & vol+? and what happened as soon as you flashed the zip?
twilighttony said:
Can you still get into recovery with power & vol+? and what happened as soon as you flashed the zip?
Click to expand...
Click to collapse
Nope :crying:. The EDL combo and the recovery combo result in the same screen and duration of boot. After flashing the bootloader unlock file, I remember reading the script to see that it was successful and yielded a result of 1 before resulting in this screen.
navsterama said:
Nope :crying:. The EDL combo and the recovery combo result in the same screen and duration of boot. After flashing the bootloader unlock file, I remember reading the script to see that it was successful and yielded a result of 1 before resulting in this screen.
Click to expand...
Click to collapse
I am not sure what happened to that, were you originally on B15? i was simply on the modem/bootstack which allowed me to succeed in flashing that file. that could be a variable. i will be sure to look into a tool ive heard of called miflash which works through edl mode to unbrick.
navsterama said:
Nope :crying:. The EDL combo and the recovery combo result in the same screen and duration of boot. After flashing the bootloader unlock file, I remember reading the script to see that it was successful and yielded a result of 1 before resulting in this screen.
Click to expand...
Click to collapse
try this.
twilighttony said:
I am not sure what happened to that, were you originally on B15? i was simply on the modem/bootstack which allowed me to succeed in flashing that file. that could be a variable. i will be sure to look into a tool ive heard of called miflash which works through edl mode to unbrick.
Click to expand...
Click to collapse
Yea, I was on B15. Trying miFlash right now though. I'll update you when its done...:good:
navsterama said:
Yea, I was on B15. Trying miFlash right now though. I'll update you when its done...:good:
Click to expand...
Click to collapse
ok that does make sense as to why it failed. i was on the modded modem file that allowed me to install los
twilighttony said:
ok that does make sense as to why it failed. i was on the modded modem file that allowed me to install los
Click to expand...
Click to collapse
Wait...in terms of the bootstack I was also on the modded one for LOS 14.1. However, it was when the last unofficial build came out (Feb 3rd???). I tried to clean flash LOS Weekly today and thats when I ran into the dilemma of the decryption. Idk why I said yes for being on B15, for some reason that translated to generally Nougat bootstack in my head. My bad, OP.
---------- Post added at 10:47 PM ---------- Previous post was at 10:30 PM ----------
navsterama said:
Yea, I was on B15. Trying miFlash right now though. I'll update you when its done...:good:
Click to expand...
Click to collapse
Unbricked, booted up, now its on the "beautiful" screen. Thanks!
twilighttony said:
try this.
Click to expand...
Click to collapse
This is posted in the dev section. No need for external linkage.
navsterama said:
Wait...in terms of the bootstack I was also on the modded one for LOS 14.1. However, it was when the last unofficial build came out (Feb 3rd???). I tried to clean flash LOS Weekly today and thats when I ran into the dilemma of the decryption. Idk why I said yes for being on B15, for some reason that translated to generally Nougat bootstack in my head. My bad, OP.
---------- Post added at 10:47 PM ---------- Previous post was at 10:30 PM ----------
Unbricked, booted up, now its on the "beautiful" screen. Thanks!
Click to expand...
Click to collapse
glad that worked. perhaps i will edit the guide to where fastboot is added at the end as an extra. seems that if we at least have twrp we can go from there. do you still have an unlocked bl?
lafester said:
This is posted in the dev section. No need for external linkage.
Click to expand...
Click to collapse
will remember for future reference. thanks
lafester said:
This is posted in the dev section. No need for external linkage.
Click to expand...
Click to collapse
At least the poster of the blog gives credit to the original author and thread.
The method referenced at the blog is confusing though. If one is in a bricked state (edl only), they can't access developer options or even boot into android.
gpz1100 said:
At least the poster of the blog gives credit to the original author and thread.
The method referenced at the blog is confusing though. If one is in a bricked state (edl only), they can't access developer options or even boot into android.
Click to expand...
Click to collapse
If you are in edl only with an unlocked bootloader than the part of enabling bl unlock won't apply.
twilighttony said:
If you are in edl only with an unlocked bootloader than the part of enabling bl unlock won't apply.
Click to expand...
Click to collapse
Right, I understand that, but the person reading your blog won't, and thus the confusion.
This guide really needs to be stickied or higher up. Restarted my phone yesterday and it randomly got encrypted upon booting. Was locked out of everything and no keyboard was popping up to be able to put in a PIN or Password. This guide saved me. Thank you.
Bricked your M5? Post here. I am one of three posters who have posted threads requesting assistance - we might as well create one thread where we can try and help each other.
My model? SHT-AL09 (C636). My story? I apparently made a bad change to my build.prop file, and had USB debugging disabled. I then probably dug myself a deeper hole trying to recover. I don't even get boot animation anymore. I'd happily pay someone to unbrick me.
The only potential progress I have made, is that I was able to install and successfully boot TWRP - although TWRP detects that I have no operating system installed and I am unable to mount any partitions except for my external SD card. Using TWRP's file manager, I can see that the system partition, for example, has not been entirely wiped, but many files seem to be missing. At the very least, TWRP allows me to turn the screen off without seeking to contantly reboot thereafter.
To install TWRP, I followed these instructions intended for Mate 9 owners:
duraaraa said:
This is TWRP to Mate 9/Android O, brought to you by FunkyHuawei.
It's just a preliminary build so I can't promise anything/everything will work! Keep that in mind. I'm not responsible if you brick your device.
EDIT: Does not work with Mate 10 series.
DOWNLOAD LINK:
https://drive.google.com/open?id=0B45NCsO2AL_1NEh2aDFLM3JlYkU
It works on the Android O build here:
https://www.reddit.com/r/FunkyHuawei/comments/75uwkd/october_12_first_official_android_o_beta_for/
and the official European beta.
To install:
First, have Android O running. Unlock the bootloader. Download the twrp image.
Then, run in fastboot mode:
fastboot flash recovery_ramdisk twrp_android_o_mate9_a1.img
Then, reboot holding volume up, and you've got TWRP!
Note: With the Android O update, it is no longer possible to flash the recovery2 partition. Furthermore, the names of the partitions have changed. Please keep that in mind, and don't mess around too much with TWRP, to be sure you don't brick your system!
Click to expand...
Click to collapse
Hmm ... I wanted to ask you whether you have the full OTA package for your device? So you should be able to extract all the partition images from there and to fastboot flash them. But I checked on HFF and I do not see a full OTA package matching your device yet.
AndDiSa said:
Hmm ... I wanted to ask you whether you have the full OTA package for your device? So you should be able to extract all the partition images from there and to fastboot flash them. But I checked on HFF and I do not see a full OTA package matching your device yet.
Click to expand...
Click to collapse
I've tried flashing system.img/ramdisk.img from the c00 package. Maybe I have to wait for c636 firmware, or maybe I have to flash additional .imgs. I am pretty sure that the specs and hardware I have are the same as the c00.
I've tried flashing the entire update.zip file in TWRP...but as noted TWRP is unable to mount internal storage. I'm not sure if I need to wipe and reformat first. I also have no clue whether the TWRP build I installed is properly compatible with the device. I had nothing to lose by giving it a shot.
thref23 said:
I've tried flashing system.img/ramdisk.img from the c00 package. Maybe I have to wait for c636 firmware, or maybe I have to flash additional .imgs. I am pretty sure that the specs and hardware I have are the same as the c00.
Click to expand...
Click to collapse
This will not work as the boot chain will be broken due to mismatching checksums. You need to have the correct images. To flash a OTA image you also need to have the standard recovery image installed ...
So...will someone correct please correct me if this is wrong?
If I were to flash a c00 oeminfo file, I could then install a c00 update.zip via dload folder?
Would c432 work as well (with a flashed oeminfo), even though the Euro hardware has different bands than my hardware?
There is now a full OTA on FF for C635.....still nothing for c636...
Finally, a full OTA is available for c636.
But the 'dload' method (update.app on an sd card) failed at 5%. And flashing ramdisk/recovery/erecovery/system images also failed.
Is this possibly because the OTA is B153, whereas my M5 was shipped B121?
(I hate to be that guy bumping his own thread, sorry)
I'm unbricked!
For those in a similar spot, looking to rebrand, or otherwise interested...
I finally e-mailed Funky Huawei for assistance. Their unbrick tool did not work. However, their e-recovery method worked perfectly (basically, you point your router's DNS to Funky Huawei, enter stock recovery and connect to wi-fi, and Funky Huawei's servers mimic Huawei's servers. If they do not have your firmware on their server, they will add it by request (provided it exists on the internet).
I paid $65 for a 30 day pass - a little steep, but I was impatient. I'm not sure if I could have gotten away with paying less. If you want to try and use my FH account over the next 30 days PM me (although I don't want to get carried away with that).
For those looking to rebrand, if you can flash an OEMinfo file successfully (FH has a rebrand tool and I have no clue how well it works), you should be able to use FH's erecovery method to flash firmware (don't blame me if something goes wrong).
One reason for the trouble I was having, if because I bootlooped after making a change to the vendor/build.prop file. This file was on the vendor partition, not the system partition, and for whatever reason the vendor partition cannot be flashed via fastboot (in theory it can be flashed, in reality it returns an error that doesn't have to do with the size of the partition).
Before reverting to FH, I finally got TWRP installled and functioning, and after all the attempts I made to recover my device, the same build.prop file which initially caused a bootloop was still in the /vendor folder. And TWRP wouldn't mount the system and vendor partitions as read/writeable - that was frustrating.
Now off to experiment with AOSP GSIs while I feel like I have little to lose...
Please help me
hello everyone,
i tried to rebrand my m5pro with help of ministryofsolutions. Something went wrong and my tablet (CMR-AL19) is stucked in the recovery mode. how can i fix it? Someone who ca help me? I will pay
Greeztings
Luigi
thref23 said:
Bricked your M5? Post here. I am one of three posters who have posted threads requesting assistance - we might as well create one thread where we can try and help each other.
My model? SHT-AL09 (C636). My story? I apparently made a bad change to my build.prop file, and had USB debugging disabled. I then probably dug myself a deeper hole trying to recover. I don't even get boot animation anymore. I'd happily pay someone to unbrick me.
The only potential progress I have made, is that I was able to install and successfully boot TWRP - although TWRP detects that I have no operating system installed and I am unable to mount any partitions except for my external SD card. Using TWRP's file manager, I can see that the system partition, for example, has not been entirely wiped, but many files seem to be missing. At the very least, TWRP allows me to turn the screen off without seeking to contantly reboot thereafter.
To install TWRP, I followed these instructions intended for Mate 9 owners:
Click to expand...
Click to collapse
I have been through hell and high water today with this Nord N200 5G today. Soft Brick after Soft Brick. iI only flashed TWRP and try to boot into OS after exiting TWRP but i get No OS you sure you want to reboot?. I also can't figure out how to get my internal storage viewed in TWRP. I've read multiple guides and still can't figure it out. I"m pretty new to this so . and they try to flash Magisk for root as well as super su during on adventure fiasco after fiasco today. The Bootloader and OEM unlock was simple straight forward. Most Guides though are not in LAMENS terms and have abbreviations that new people do not understand. i have had to reflash my phone 20+ today with factory due to the NO OS problem with TWRP and can't get it so i can view my internal data from twrp even though i've followed several guides and the ones that says to do the wipe thing i always get the error about it can't mount the data or it has encountered and error 255 and by got try looking things up for those and you you get sent all over the place. So If there is Anyone Out There That would like to help an old geezer out to be able to get a stable TWRP and a Stable root going on please Respond. Sorry Had to Vent......
Oh yea and not to mention Unable to install 3.6.2
TWRP is not officially launched for this phone. In my opinion lineage is the best option for this phone as of now. It has a custom recovery and is easily rooted as well. https://forum.xda-developers.com/t/rom-official-dre-12l-lineageos-19.4473129/
weirdfate said:
TWRP is not officially launched for this phone. In my opinion lineage is the best option for this phone as of now. It has a custom recovery and is easily rooted as well. https://forum.xda-developers.com/t/rom-official-dre-12l-lineageos-19.4473129/
Click to expand...
Click to collapse
A couple of questions before I jump into that.
How are updates handled? Does the OS do auto-updates?
How is the camera?
I don't know a lot about this phone, but previous phones I've owned had proprietary camera/software, and any custom ROM not based on the stock OS lost camera quality because it couldn't use the proprietary software..
jova33 said:
A couple of questions before I jump into that.
How are updates handled? Does the OS do auto-updates?
How is the camera?
I don't know a lot about this phone, but previous phones I've owned had proprietary camera/software, and any custom ROM not based on the stock OS lost camera quality because it couldn't use the proprietary software..
Click to expand...
Click to collapse
Obviously not who you were asking but I just updated to Lineage and it was fairly straightforward following the directions, just make sure you're on Android 11. Updates can be done through settings menu, I just actually applied an update and it worked fine. It can check for updates every day, week, month if you choose I don't know if it will automatically update it though. Camera I have not tried as I don't use it as an everyday phone but generally from what I've seen it's common to have quality go down using software other than stock but I could be wrong.
I can't speak on the difference in camera quality because I dont use it much. There is some loss of function between the stock camera app and the aftermarket rom camera app
This phone has no official twrp so it has tons of decrypting issues which explains almost all of your problems.
What worked for me is to avoid touching the phone if at all possible while in TWRP. It's very unstable and if you click something it will try to mount partitions and somehow brick you in the process. While booted into TWRP I did almost everything via ADB command from my computer instead of through the TWRP menus, including reboot.
I Pushed my magisk package to /tmp instead which worked. I'm just going to go the lineage route later though. I don't think it's worth messing with TWRP on this device.
Update: Phone Complete Bricked. Says something like The Image(boot/recovery) has been destroyed please flash the correct image or call customer service to fix it. on top of this....Unable to flash anything. everything no matter what it is, i even tried to follow a guide to get back to factory and it say that no such partition or volume full. Oh and it's an A/B partition phone
swee08315 said:
What worked for me is to avoid touching the phone if at all possible while in TWRP. It's very unstable and if you click something it will try to mount partitions and somehow brick you in the process. While booted into TWRP I did almost everything via ADB command from my computer instead of through the TWRP menus, including reboot.
I Pushed my magisk package to /tmp instead which worked. I'm just going to go the lineage route later though. I don't think it's worth messing with TWRP on this device.
Click to expand...
Click to collapse
how do you push? ive tried the adb push and to no avail... it just keeps saying it's unable to. oh and when i did have twrp installed it wouldn't boot into the os unless i fastboot boot twrp.img then it would reset and finally boot into regular os
MiniNinja2024 said:
how do you push? ive tried the adb push and to no avail... it just keeps saying it's unable to. oh and when i did have twrp installed it wouldn't boot into the os unless i fastboot boot twrp.img then it would reset and finally boot into regular os
Click to expand...
Click to collapse
I believe it was just "adb push boot.img /tmp/boot.img"
And then in TWRP when selecting a file to flash you have to click on the top level option to go up a directory and find /tmp while not clicking anything else. I pushed to tmp to avoid mounting any partitions since the phone bricked everytime that happened.
swee08315 said:
I believe it was just "adb push boot.img /tmp/boot.img"
And then in TWRP when selecting a file to flash you have to click on the top level option to go up a directory and find /tmp while not clicking anything else. I pushed to tmp to avoid mounting any partitions since the phone bricked everytime that happened.
Click to expand...
Click to collapse
how do i get the phone completely unbricked cause it's saying something like The Image[boot,recovery] has been destroyed please flash correct image or contact customer service to fix it
I forgot to mention that I can no long get into recovery it won't even flash a recovery anymore. it will say it completed successfully but i got to boot recovery and it just boot right back into bootloadre/fastboot mode. i even tried to do fastboot --set-active=a and fastboot --set-active=b tried booting into each of them and nothing. when i do fastboot getvar all it says that boot_a and boot_b are unbootable. any idea how to fix this?
Will be trying again in a week when i get my new unlock token. just took the phone to the store, said that the bricking of the phone happend during an update. They didn't have any Nord N200's in stock so they ordered one and said they would have it in the store in a day or two. onto the next phone til then. any ideas on a TCL A509DL Trac Phone?
MiniNinja2024 said:
I forgot to mention that I can no long get into recovery it won't even flash a recovery anymore. it will say it completed successfully but i got to boot recovery and it just boot right back into bootloadre/fastboot mode. i even tried to do fastboot --set-active=a and fastboot --set-active=b tried booting into each of them and nothing. when i do fastboot getvar all it says that boot_a and boot_b are unbootable. any idea how to fix this?
Click to expand...
Click to collapse
You need to use MSM tools to unbrick. It'll restore your device to stock and relock your bootloader.
swee08315 said:
You need to use MSM tools to unbrick. It'll restore your device to stock and relock your bootloader.
Click to expand...
Click to collapse
Having problems getting msm running on deb linux. Have the firmware and files needed but can't get msm to run on MX linux And can't get VMware to run either to try it through that on windows 10
MiniNinja2024 said:
Having problems getting msm running on deb linux. Have the firmware and files needed but can't get msm to run on MX linux And can't get VMware to run either to try it through that on windows 10
Click to expand...
Click to collapse
i'm not sure if you can even get the devices to connect to the unbrick tools in a virtual machine. to save some time, use a physical computer running windows 10+ and use a virtual machine as a last resort or if you don't have another computer.
by the way, make sure you have the drivers.
justauserthatusesaphone said:
i'm not sure if you can even get the devices to connect to the unbrick tools in a virtual machine. to save some time, use a physical computer running windows 10+ and use a virtual machine as a last resort or if you don't have another computer.
by the way, make sure you have the drivers.
Click to expand...
Click to collapse
i don't have another machine only the one i'm using running MX linux. and with all the Distro's of linux i have installed and used there is no need to install drivers for phones for every phone, 3 that i have connected to my computer it' has recognized all 3 phones and runs adb and fastboot commands fine on them. Lol, Took me a minute to read your name but Love the Name.
Haha, don't flash it. Boot it. I ended up stop using it and am now using the Lineage OS Recovery. SUPER stable. I am in the works making a new TWRP as well... This unofficial variant just isn't working for me either. So, I figured since im making it doe myself, might as well release it
justauserthatusesaphone said:
i'm not sure if you can even get the devices to connect to the unbrick tools in a virtual machine. to save some time, use a physical computer running windows 10+ and use a virtual machine as a last resort or if you don't have another computer.
by the way, make sure you have the drivers.
Click to expand...
Click to collapse
You can. Use virtualbox. I wouldn't bother with qemu.
swee08315 said:
You need to use MSM tools to unbrick. It'll restore your device to stock and relock your bootloader.
Click to expand...
Click to collapse
There is a command line alternative for Linux. It is originally made for flashing android boards, but works with phones as well.
Springles2 said:
You can. Use virtualbox. I wouldn't bother with qemu.
Click to expand...
Click to collapse
Interesting, that's actually useful to know. Thanks.
MiniNinja2024 said:
Update: Phone Complete Bricked. Says something like The Image(boot/recovery) has been destroyed please flash the correct image or call customer service to fix it. on top of this....Unable to flash anything. everything no matter what it is, i even tried to follow a guide to get back to factory and it say that no such partition or volume full. Oh and it's an A/B partition phone
how do you push? ive tried the adb push and to no avail... it just keeps saying it's unable to. oh and when i did have twrp installed it wouldn't boot into the os unless i fastboot boot twrp.img then it would reset and finally boot into regular os
Click to expand...
Click to collapse
I do adb push (File) partition