Can someone please with ATT android Q build 30E send me both A and B boot.img
nikothebarber said:
Can someone please with ATT android Q build 30E send me both A and B boot.img
Click to expand...
Click to collapse
Niko, yer asking everywhere for this, but u already have it right? Your phone is att updated to 30e right?
So, just like anyone else would have to do, use qfil and get it? I mean, if you're going to root and get twrp on the device, you're going to have to install and learn to use, qfil.
As I mentioned in another thread, if you post your boot_a image, I'll twrp patch it for u and post it back.
Do you need help using / installing qfil?
No I believe im mismatched I accidentally flashed a and b boot ing ive got it working but boot imgg is older then 30e, I get the error on start up saying current version is not available for user can't find match carrier NT code FFFFFF: 84
nikothebarber said:
No I believe im mismatched I accidentally flashed a and b boot ing ive got it working but boot imgg is older then 30e, I get the error on start up saying current version is not available for user can't find match carrier NT code FFFFFF: 84
Click to expand...
Click to collapse
Okay, since you did an OTA update (right?) then the other boot image would be the previous version OS for att. Maybe to get the newest one u can do the update again? (I don't know, I"m asking, I don't have a carrier specific phone so no way to test that).
Also, that NT error code is usually only going to occur when u 'cross flash'. Which makes me wonder... what boot partition are u really using? It sounds like it **may** not even be an att one?
I better understand your situation now, sure does make it obvious why you want to do a backup before any modifications right? sorry, I'm sure you've learned that lesson now, but maybe others can benefit from your tough lesson.
Here's the first thing I'd do if u; Make A COPY OF EA boot partition, as they are now. At least you'll have a backup of ea one from here (whatever they happen to be).
One of the easiest ways to do that would be (assuming you have twrp injected), would be to boot recovery, connect to pc with usb cable, and type in 'adb shell'.
Then use the following dd commands (modify for your directory structure on sd card);
dd if=/dev/block/bootdevice/by-name/boot_b of=/external_sd/backup/current_att_boot_b.img
this assumes you have a directory on your sd card called 'backup'. Replace it with whichever you may have. Do the same for boot_a also (change boot_b to boot_a), and change the output name to reflect what you're backing up.
So with these backups, you **could** decide to copy your boot_b backup tot he boot_a partition and see what happens? I mean it sounds like you're not sure what is on either one of your boot partitions, so trying that may be the only way to have some idea of what's there.
*If** it turns out that the device boots okay with boot_b copied over, then at least you'll have a boot partition that could be twrp injected and not have the nt_error code?
good luck
I mixed up the active side and replaced one with the other already . I never did OTA and unfortunately it does not work. I have back ups now of boot a and b with qfil, my firmware is 30e and boot img is 30b. I need boot.img 30E
I've got 30e boot.bin can.you add twrp to it
nikothebarber said:
I've got 30e boot.bin can.you add twrp to it
Click to expand...
Click to collapse
Well I have no way of knowing which one is 30e and which is att prior version. But I can tell you the 30e_a u posted here is identical to the 30e_a posted in this thread.
cheers
Related
I think it's possible because the amazon fifth Gen, it has a locked bootloader but we were still able to boot into a custom recovery by using the original kernel of the device somehow. I know it's not the same thing but if we have access to do commands we can flash a custom recovery that way. I'll be asking the guy who made the custom recovery on how he did it. Then maybe we can modify the android 6.0 update zip and inject root into it??
I have that device. It requires fastboot i believe.
Not holding my breath
danweb66 said:
I have that device. It requires fastboot i believe.
Click to expand...
Click to collapse
It is possible to nuke the laf and gain access to fastboot. You could then flash your needed commands and restore laf.
tabp0le said:
It is possible to nuke the laf and gain access to fastboot. You could then flash your needed commands and restore laf.
Click to expand...
Click to collapse
I was about to say exactly that. A fun little trick I picked up with my G2 when I bricked it really damn bad and basically had zero options for getting it to boot again without access to fastboot, which was so wonderfully omitted by LG despite the G2 and the Nexus 5 being almost the same phone under the hood, so I was a bit reckless thinking they wouldn't have made the software so drastically different when they're almost identical hardware.
I have a feeling nuking laf and using a kindle method really could work, but unfortunately I don't have a backup phone to move my number over to while I try until I get a replacement Moto X under warranty (that one literally bricked itself within six months running stock)
I don't think the 5th gen fire has 6.0...I may be mistaken tho.
No I'm not saying use fastboot I'm saying flash the recovery using dd commands instead. You can back up the recovery just incase something happensAL and flash that back. Meaning nuking only the recovery partition and flashing a modified boot.img
Interesting, sounds possible but you would think that someone more advanced than us would of considered this.
Awesomeslayerg said:
No I'm not saying use fastboot I'm saying flash the recovery using dd commands instead. You can back up the recovery just incase something happensAL and flash that back. Meaning nuking only the recovery partition and flashing a modified boot.img
Click to expand...
Click to collapse
base_ten said:
Interesting, sounds possible but you would think that someone more advanced than us would of considered this.
Click to expand...
Click to collapse
I'm pretty sure that's what I did for the tmoble version...was side load the recovery with dd commands..I think the twrp recovery needs to made for sprint tho
Edit: http://forum.xda-developers.com/tmo...recovery-twrp-2-8-7-0-touch-recovery-t3164874 there was 2 ways 2 do it one with flashify an the other with dd commands...not sure if it will work for us but who knows...
Hate to resurrect a perfectly dead thread, but I'm guessing no one has tried this with any success?
Ive been looking into things like i know g2 had lokinexploit att g3 images and recoverys are bumped both had lock bls but i dont know yet i just got this g4 last night and ill be stuck with it for at least a year or so so im in for testing i aint worried bout waranty and i got insuarance have in my opinion better tech skills than a lot of people i know so im all game
So my computer bit the dust about two months ago so i found myself in a situation where yes, I had a PC back when i unlocked the bootloader, ran ADB fastboot commands and flashed the twrp recovery.img . But now, I have no access to computers whatsoever. So heres what I did:
Downloaded - Str8upx's TWRP backup found here - http://forum.xda-developers.com/showpost.php?p=67914526&postcount=43
Nightbreed813s flashable MM rom for Sprint Phones found here - http://forum.xda-developers.com/des...m-flashable-stock-htc-626s-debloated-t3293602
After downloading the files, I extracted the TWRP backup from the .zip file, navigate with a file explorer past the folder with a Serial Number on it, copied the backup folder that comes next, moved it to my external sd cards TWRP backup folder .
Then I booted into TWRP, after backing up my current ROM, wiped everything and then flashed the sprint ROM
after that, I restored ONLY the System portion of Str8upx's backup. (this means i didn't flash the system image either, ONLY SYSTEM)
Rebooted phone and I was done. Still had SuperSU, but had to install busybox.
I'd like to note that from this point on everything works without any problems and I'm on the official Metro MM. The red letters show up every time I boot the phone now, instead of only when i boot into TWRP like it used to so please be aware of that. Also, my baseband and kernel appear to be different than the ones in Metro MM. I do intend on updating once somebody makes a TWRP flashable version of MM. But until then, i'll stay on this as my daily driver as again, everything does work. I figured I'd share what I learned and maybe we will see less threads about " i tried to install MM on my rooted 626s and it failed " feel free to ask any questions if there are any. All thanks goes to Nightbreed813 and Str8upx for uploading the files. If you have a second and you use these files, Click thanks on the linked posts to thank them.
I need to make all aware that wifi isn't going to work with this method. So if you plan on using wifi, you're gonna have to flash the ruu. Full disclosure I no longer stand behind this due to lack of wifi. I went ahead and flashed with the RUU and fastboot flashed twrp back. This solution was only a temporary fix for me. As it should be for anybody if its used at all
You reckon this'll work with Boost Mobile?
TeamLiquid.koyo said:
You reckon this'll work with Boost Mobile?
Click to expand...
Click to collapse
There's already a flashable MM ROM for the boost 626s, http://forum.xda-developers.com/des...m-flashable-stock-htc-626s-debloated-t3293602
Yeah. On boost that's all you need
Genius... Simply Genius
talksickisil said:
So my computer bit the dust about two months ago so i found myself in a situation where yes, I had a PC back when i unlocked the bootloader, ran ADB fastboot commands and flashed the twrp recovery.img . But now, I have no access to computers whatsoever. So heres what I did:
Downloaded - Str8upx's TWRP backup found here - http://forum.xda-developers.com/showpost.php?p=67914526&postcount=43
Nightbreed813s flashable MM rom for Sprint Phones found here - http://forum.xda-developers.com/des...m-flashable-stock-htc-626s-debloated-t3293602
After downloading the files, I extracted the TWRP backup from the .zip file, navigate with a file explorer past the folder with a Serial Number on it, copied the backup folder that comes next, moved it to my external sd cards TWRP backup folder .
Then I booted into TWRP, after backing up my current ROM, wiped everything and then flashed the sprint ROM
after that, I restored ONLY the System portion of Str8upx's backup. (this means i didn't flash the system image either, ONLY SYSTEM)
Rebooted phone and I was done. Still had SuperSU, but had to install busybox.
I'd like to note that from this point on everything works without any problems and I'm on the official Metro MM. The red letters show up every time I boot the phone now, instead of only when i boot into TWRP like it used to so please be aware of that. Also, my baseband and kernel appear to be different than the ones in Metro MM. I do intend on updating once somebody makes a TWRP flashable version of MM. But until then, i'll stay on this as my daily driver as again, everything does work. I figured I'd share what I learned and maybe we will see less threads about " i tried to install MM on my rooted 626s and it failed " feel free to ask any questions if there are any. All thanks goes to Nightbreed813 and Str8upx for uploading the files. If you have a second and you use these files, Click thanks on the linked posts to thank them.
Click to expand...
Click to collapse
I downloaded the Metro pcs RUU onto a PC to install the update, then fast boot flashed twrp. (At this moment it didn't show the red warning letters In the bottom of the boot screen) I suspect it happened when I flashed the SuperSU.zip
i2andog said:
Genius... Simply Genius
Click to expand...
Click to collapse
Thanks man. Lol....
Did you try? If so, any issues?
IsaacGuti said:
I downloaded the Metro pcs RUU onto a PC to install the update, then fast boot flashed twrp. (At this moment it didn't show the red warning letters In the bottom of the boot screen) I suspect it happened when I flashed the SuperSU.zip
Click to expand...
Click to collapse
I really don't know what causes the red letters. Personally speaking, I can still manage with or without them.
talksickisil said:
Thanks man. Lol....
Did you try? If so, any issues?
Click to expand...
Click to collapse
No I have a working PC... I just really admired your use of magiver like resources
Gotcha. . Yeah, it's not the first time. And not just phones. I Jimmy rig my way thru a lot of life haha. To be honest I'd probably still do this even if I had my PC. I'm just not a fan of fastboot and adb commands. And I don't want to lock my bootloader again
Yes.. those mother f'in boot loaders would burn in hell if I had any say ... in uh.. boot loaders souls or whatever... ... *crickets*.... hey check that out
Sent from my HTC Desire 626s using Tapatalk
talksickisil said:
So my computer bit the dust about two months ago so i found myself in a situation where yes, I had a PC back when i unlocked the bootloader, ran ADB fastboot commands and flashed the twrp recovery.img . But now, I have no access to computers whatsoever. So heres what I did:
Downloaded - Str8upx's TWRP backup found here - http://forum.xda-developers.com/showpost.php?p=67914526&postcount=43
Nightbreed813s flashable MM rom for Sprint Phones found here - http://forum.xda-developers.com/des...m-flashable-stock-htc-626s-debloated-t3293602
After downloading the files, I extracted the TWRP backup from the .zip file, navigate with a file explorer past the folder with a Serial Number on it, copied the backup folder that comes next, moved it to my external sd cards TWRP backup folder .
Then I booted into TWRP, after backing up my current ROM, wiped everything and then flashed the sprint ROM
after that, I restored ONLY the System portion of Str8upx's backup. (this means i didn't flash the system image either, ONLY SYSTEM)
Rebooted phone and I was done. Still had SuperSU, but had to install busybox.
I'd like to note that from this point on everything works without any problems and I'm on the official Metro MM. The red letters show up every time I boot the phone now, instead of only when i boot into TWRP like it used to so please be aware of that. Also, my baseband and kernel appear to be different than the ones in Metro MM. I do intend on updating once somebody makes a TWRP flashable version of MM. But until then, i'll stay on this as my daily driver as again, everything does work. I figured I'd share what I learned and maybe we will see less threads about " i tried to install MM on my rooted 626s and it failed " feel free to ask any questions if there are any. All thanks goes to Nightbreed813 and Str8upx for uploading the files. If you have a second and you use these files, Click thanks on the linked posts to thank them.
Click to expand...
Click to collapse
But what i'm wanting to know is, did you flash the standard or the De -Bloated rom? I'm not clear on that. Also are there any differences in the UI or OS that you noticed in this mm update?
s3llz said:
But what i'm wanting to know is, did you flash the standard or the De -Bloated rom? I'm not clear on that. Also are there any differences in the UI or OS that you noticed in this mm update?
Click to expand...
Click to collapse
As far as which sprint ROM you flash debloated version or regular it doesn't really matter, since once you restore the twrp backup you're going to be on the standard non debloated metro official MM. As far as UI differences, there's a few things here and there. Nothing mind blowing. What was advantageous for me is the expanded internal storage. I love it.
I tried installing with the RUU and always got error 155 all the time some I am trying this method out. I would like to know will this method still work on a phone with exposed binary, and for those with MetroPCS, does the service still work as well.
Hello I tried doing everything as followed installed the sprint now after every call or just randomly i get "SIM card has been inserted" "Select a carrier" which T-mobile is the only one to work. Then after a call and again randomly i get this message again and have to repeat the process. Does anyone know why and how can I fix this?
bnawolf said:
Hello I tried doing everything as followed installed the sprint now after every call or just randomly i get "SIM card has been inserted" "Select a carrier" which T-mobile is the only one to work. Then after a call and again randomly i get this message again and have to repeat the process. Does anyone know why and how can I fix this?
Click to expand...
Click to collapse
In my instructions you don't stay on the sprint rom. You're supposed to restore the backup after installing that rom. But I need to make all aware that wifi isn't going to work with this method. So if you plan on using wifi, you're gonna have to re lock your bootloader and flash the ruu
Hey everybody,
I was on CM14.1, no issues, but decided to flash back to 6 and made the stupid mistake of trying to go straight with the standard motorola image. Now I am able to load the bootloader mode but cant do much after that. None of the partitions work, nor I can get data from bootloader info (tried retreieving flashing info to no avail). I am trying to find something I can use. Anyone has a suggestion?
Would you mind detailing which steps you took to flash? I think I know what your problem is, but I want to be sure first.
zstricky said:
Would you mind detailing which steps you took to flash? I think I know what your problem is, but I want to be sure first.
Click to expand...
Click to collapse
Sure!
- Got unlocked bootloader and installed cm14.1
- Decided to revert back to stock so downloaded 6.0 system image.
- instead of deleting the got.bin line from flashfile.xml I went to rsd and tried flashing it. It errored out and this took me where I am.
There is a flashable stock rom zip, but assuming you want to just use the official image that you already have you'll need to flash with fastboot. I saw that you posted on the thread 'return to stock etc'. Follow those fastboot steps, but be aware that there is a major omission: the instructions only go to system.img_sparsechunk.8, but there are 9 of those files and the phone will not boot if you only flash 8. As you go through fastboot flashing I think there will be a couple files that will give errors. Do an internet search on the error output line, but if I remember correctly the files that won't flash are no big deal and didn't affect my phone when I went ahead and ignored the errors.
I did man... The problem is... Something trully god messed up here. I am now getting hard stops related to aboot failures. I saw something similar on the xt1033 forums but we miss those same files.
Just got a new in the box unit. It was made in 7/2019 and it arrived with Pie installed even though these originally came with Oreo. Is there any way to downgrade mine and, if so, how to do it and were to get a firmware file? Thanks for your help.
Unless I'm mistaken, this thread will tell you how: https://forum.xda-developers.com/lg-v40/how-to/guide-lgup-root-t3967858
and this thread contains the links to the KDZs (LG speak for stock ROMs): https://forum.xda-developers.com/lg-v40/development/v40-firmware-links-ainzooalgown-t3940600
[NG]Owner
NGOwner said:
Unless I'm mistaken, this thread will tell you how: https://forum.xda-developers.com/lg-v40/how-to/guide-lgup-root-t3967858
and this thread contains the links to the KDZs (LG speak for stock ROMs): https://forum.xda-developers.com/lg-v40/development/v40-firmware-links-ainzooalgown-t3940600
[NG]Owner
Click to expand...
Click to collapse
Thanks. I do see those threads and those definitely help. But I am still not clear if I can downgrade. Perhaps it is because I am new to LG phones from Samsung and I know that on some Samsung devices, once you go forward you may not be able to go back. So I am just wondering about all that (along with if I can unlock the bootloader, install TWRP, and root on the model 405QA that I have). Cheers!
Using LGUP 1.14 on DEV mode will let you downgrade, matter is flashing cause phones themselves seem not have any issues by downgrading. Personally I've downgraded both my v40 and my older g7 a couple of times, no probs.
smariob said:
Using LGUP 1.14 on DEV mode will let you downgrade, matter is flashing cause phones themselves seem not have any issues by downgrading. Personally I've downgraded both my v40 and my older g7 a couple of times, no probs.
Click to expand...
Click to collapse
Thanks so much for your time and help. I have downloaded LGUP and installed according to this thread <https://forum.xda-developers.com/lg-v40/how-to/guide-lgup-root-t3967858>. When I try to run it, Win10 asks if it is ok, I say yes, and then nothing else happens. Hmmm. I believe this is LGUP 1.16.0.3. No idea what's up. I have the phone attached and in download mode as described here <https://droidrecovery.com/lg-v40-thinq-recovery-mode/>. Grrr.
Try this LG UP version https://forum.xda-developers.com/showpost.php?p=76995781&postcount=26 set the DLL on DEV mode.
As for unlock bootloader question on your other thread, yep so far it's the easiest method to do it. ADVICE: If you haven't touched anything yet I suggest take a bakup of your partitions via QFIL. So if you mess up something (most likely not but you never know) you will be able to restore everything as it was when you got the phone.
smariob said:
Try this LG UP version https://forum.xda-developers.com/showpost.php?p=76995781&postcount=26 set the DLL on DEV mode.
As for unlock bootloader question on your other thread, yep so far it's the easiest method to do it. ADVICE: If you haven't touched anything yet I suggest take a bakup of your partitions via QFIL. So if you mess up something (most likely not but you never know) you will be able to restore everything as it was when you got the phone.
Click to expand...
Click to collapse
Oh thanks so much! That version of LGUP seems to work (after I manually did some file copying that had permission problems from the scripts). I presume that to downgrade - assuming I have a compatible .KDZ - is to use the FOTA upgrade option?
I will look into the backup as you suggest. As a newbie on these devices, there is alot to learn. Cheers
smariob said:
Try this LG UP version https://forum.xda-developers.com/showpost.php?p=76995781&postcount=26 set the DLL on DEV mode.
As for unlock bootloader question on your other thread, yep so far it's the easiest method to do it. ADVICE: If you haven't touched anything yet I suggest take a bakup of your partitions via QFIL. So if you mess up something (most likely not but you never know) you will be able to restore everything as it was when you got the phone.
Click to expand...
Click to collapse
Ok, I see the phone in QFIL. Under the tools menu, I see QCN Backup/Restore. Is this the backup to which you refer? I don't see anything else that looks promising. Sorry for all of my newbie questions.
So, if you are going to do the back up use this guide: https://forum.xda-developers.com/lg-g7-thinq/how-to/how-to-partitions-flash-abl-t-mo-t4051249
Follow steps 1 to 10, Backing up _a partitions will do the job _b patitions will be mirrored from those when restore. Data is not mandatory to back up as it will take much time to read the whole partition. Another tip, rename your backed up files so you can identify them properly later.
Then when you are ready you can play with LG UP most of the time you will like to use Partition DL. Use refurbish only to go stock. FOTA is for updating between versions without losing data (nice if you crossflash/loss the ability to OTA on the phone)
smariob said:
So, if you are going to do the back up use this guide: https://forum.xda-developers.com/lg-g7-thinq/how-to/how-to-partitions-flash-abl-t-mo-t4051249
Follow steps 1 to 10, Backing up _a partitions will do the job _b patitions will be mirrored from those when restore. Data is not mandatory to back up as it will take much time to read the whole partition. Another tip, rename your backed up files so you can identify them properly later.
Then when you are ready you can play with LG UP most of the time you will like to use Partition DL. Use refurbish only to go stock. FOTA is for updating between versions without losing data (nice if you crossflash/loss the ability to OTA on the phone)
Click to expand...
Click to collapse
I cannot thank you enough for your time and help. I will read up on all this and continue tomorrow morning. Cheers.
smariob said:
So, if you are going to do the back up use this guide: https://forum.xda-developers.com/lg-g7-thinq/how-to/how-to-partitions-flash-abl-t-mo-t4051249
Follow steps 1 to 10, Backing up _a partitions will do the job _b patitions will be mirrored from those when restore. Data is not mandatory to back up as it will take much time to read the whole partition. Another tip, rename your backed up files so you can identify them properly later.
Then when you are ready you can play with LG UP most of the time you will like to use Partition DL. Use refurbish only to go stock. FOTA is for updating between versions without losing data (nice if you crossflash/loss the ability to OTA on the phone)
Click to expand...
Click to collapse
Wow! That is alot of partitions and a lengthy backup chore - even without including the _b partitions. You were 100% correct that renaming each file as you go makes this easier. I used the LUN#_the partition-label.bin as I discovered that some labels were re-used in different LUN.
I never would have figured this out without your help. Thanks.
After a brief rest I will move on and try to unlock the bootloader as described here <https://forum.xda-developers.com/lg-v40/development/unlock-lg-v40-via-9008-root-t-mobile-t4042207>.
It's great to know that, once you've done that UL BL would be a piece of a cake.
smariob said:
It's great to know that, once you've done that UL BL would be a piece of a cake.
Click to expand...
Click to collapse
Thanks so much! You might note I have posted in the other thread about troubles getting unlocked. I seem to have successfully sent the v35 bootloader to the phone. I have the QFIL log showing that. But when I go to fastboot mode and try the unlock command, it fails with unknown command. After restoring/sending the backup of the original partition, I tried issuing the same unlock command (not expecting it to work since I should have been back to the original pie bootloader) and I get the exact same error. This makes me wonder if the v35 bootloader is actually getting installed properly. The phone is on the most recent Pie (QA20e) and seems to boot and run fine - even right after I send the v35 bootloader. There were comments that using this bootloader with Pie might have problems and I have never had any so far. So again, I am wondering if the v35 is actually getting into place. A real mystery to me. Thanks!
whitedavidp said:
Wow! That is alot of partitions and a lengthy backup chore - even without including the _b partitions. You were 100% correct that renaming each file as you go makes this easier. I used the LUN#_the partition-label.bin as I discovered that some labels were re-used in different LUN.
I never would have figured this out without your help. Thanks.
After a brief rest I will move on and try to unlock the bootloader as described here <https://forum.xda-developers.com/lg-v40/development/unlock-lg-v40-via-9008-root-t-mobile-t4042207>.
Click to expand...
Click to collapse
In my case, it turned out that the phone was active on the B slot. So I took backups of those partitions as well, flashed the V35 bootloader into B, performed the unlock, re-flashed the Pie bootloader. When I reboot into normal mode, I now see an unlocked warning and it took a very long time for the phone to get started and prompt me to start all over with my Android install. Before I do that I am trying to restore the backup I made of the userdata partition to see if that spares me the whole setup thing. Thanks to all.
Yeah you've made it at least. Good one on figure out B slot was active. Now you're able to go custom roms or just go root.
smariob said:
Yeah you've made it at least. Good one on figure out B slot was active. Now you're able to go custom roms or just go root.
Click to expand...
Click to collapse
Again, thanks so much for all of you help and encouragement. From my pre-purchase research I had anticipated that I could do a dev unlock of the bootloader quite easily. I have rooted with Magisk now and am moving on to see what I can do. Cheers.
smariob said:
Using LGUP 1.14 on DEV mode will let you downgrade, matter is flashing cause phones themselves seem not have any issues by downgrading. Personally I've downgraded both my v40 and my older g7 a couple of times, no probs.
Click to expand...
Click to collapse
Thanks for all of your help and sorry for all the questions.
I am just wondering if you are able to use TWRP/Magisk root on the downgraded v40? In the TWRP thread it indicates that it requires Pie firmware be installed. If I cannot use TWRP/Magisk root on Oreo, then I will not bother trying to downgrade.
Again, thanks so much!
Now that you mention it. V40 TWRP is meant to use with pie... Will not boot on Oreo. I think there are workarounds for that if it's mandatory for you to be in Oreo, but not personally tested'em.
smariob said:
Now that you mention it. V40 TWRP is meant to use with pie... Will not boot on Oreo. I think there are workarounds for that if it's mandatory for you to be in Oreo, but not personally tested'em.
Click to expand...
Click to collapse
Thanks. Certainly not mandatory. So will stick with Pie for now anyway. Again, thanks so much.
need mmcblk0 for XT1925-3
or blank flash working
mmcblk0.img
Ambrosio71 said:
need mmcblk0 for XT1925-3
or blank flash working
Click to expand...
Click to collapse
Nobody?
Ambrosio71 said:
Nobody?
Click to expand...
Click to collapse
Well, to be honest you're kind of asking for a lot. An entire copy of someone's phone, every partition and all data.
I've seen it posted for a few devices in these threads before somewhere, but I've never understood why someone would need such a thing, so I didn't really pay too much attention.
nate1975 said:
Well, to be honest you're kind of asking for a lot. An entire copy of someone's phone, every partition and all data.
I've seen it posted for a few devices in these threads before somewhere, but I've never understood why someone would need such a thing, so I didn't really pay too much attention.
Click to expand...
Click to collapse
recover from a hard brick
Ambrosio71 said:
recover from a hard brick
Click to expand...
Click to collapse
Well, I don't have that particular variant, but if someone does want to create such a backup, they should be able to do the following:
1) Boot into twrp, plug into a computer.
2) adb pull /dev/block/mmcblk0 mmcblk0.img
Compressing that giant image should shrink it down considerably, so you won't have to actually post a 32G file or whatever.
And also just a note here, if you can boot into the bootloader and run fastboot commands, then you shouldn't need this anyway.
nate1975 said:
Well, I don't have that particular variant, but if someone does want to create such a backup, they should be able to do the following:
1) Boot into twrp, plug into a computer.
2) adb pull /dev/block/mmcblk0 mmcblk0.img
Compressing that giant image should shrink it down considerably, so you won't have to actually post a 32G file or whatever.
And also just a note here, if you can boot into the bootloader and run fastboot commands, then you shouldn't need this anyway.
Click to expand...
Click to collapse
in my case only the led flashes
there is still no blank flash file for XT1925-3
Ambrosio71 said:
in my case only the led flashes
there is still no blank flash file for XT1925-3
Click to expand...
Click to collapse
I'm curious how you ended up in this situation? How do you know that the OS is even the problem and it isn't a bad battery or something?
nate1975 said:
I'm curious how you ended up in this situation? How do you know that the OS is even the problem and it isn't a bad battery or something?
Click to expand...
Click to collapse
my version of Android was 8.0
I downloaded version 9.0 in .zip and put it in the internal memory, the system identifies the package and installs it normally as if it were an available update.
I had done this type of update before and never thought it would cause this type of problem.
This time, everything happened normally, but at the end of the update, the device needs to restart, but mine turned off and did not start, I put it on the charger and it was in the state it is in, with a flashing LED.
NOTE: this version of Android 9.0 for this device is official, however, it is a beta version, so it is only installed via .zip in the internal memory.
Ambrosio71 said:
my version of Android was 8.0
I downloaded version 9.0 in .zip and put it in the internal memory, the system identifies the package and installs it normally as if it were an available update.
I had done this type of update before and never thought it would cause this type of problem.
This time, everything happened normally, but at the end of the update, the device needs to restart, but mine turned off and did not start, I put it on the charger and it was in the state it is in, with a flashing LED.
NOTE: this version of Android 9.0 for this device is official, however, it is a beta version, so it is only installed via .zip in the internal memory.
Click to expand...
Click to collapse
Huh. Ok, so someone gave you an official beta, but won't supply you with the file you need to recover? Very strange. Hopefully someone else has that same device and can create a backup that you can use.