Related
Hi Sorry if this does not belong in this tread.
I have a Droid HD XT926 i´ve Changed the bootanimation from the original to the one from the moto x but know it just run the bootanimation but it doesn´t go on. Please Help Me I´m Desperate
i have tried everything i can think of.
Sorry for my poor English
Regards,Rich.
Had this same problem months ago when I tried to flash that boot animation. I still don't know why it happens.
Can you get into recovery or anything?
Happened to mee too (see this post & thread in general: http://forum.xda-developers.com/showthread.php?t=2393012&page=4). The bootanimation you flashed is just too big for the phone to handle and it eventually freezes. Your best luck is to have a recovery with a file manager installed to delete bootanimation.zip and restore your original one.
I think there is another location you can place the bootanimation.zip i.e. another location that is read on boot to display the boot animation. IIRC it's /data/local (default and most commonly used is /system/media). Maybe you can push a file quickly there using adb and hope it will be used for boot, therefore bypassing the faulty one.
CoinCoin88 said:
Happened to mee too (see this post & thread in general: http://forum.xda-developers.com/showthread.php?t=2393012&page=4). The bootanimation you flashed is just too big for the phone to handle and it eventually freezes. Your best luck is to have a recovery with a file manager installed to delete bootanimation.zip and restore your original one.
I think there is another location you can place the bootanimation.zip i.e. another location that is read on boot to display the boot animation. IIRC it's /data/local (default and most commonly used is /system/media). Maybe you can push a file quickly there using adb and hope it will be used for boot, therefore bypassing the faulty one.
Click to expand...
Click to collapse
thanks for your answer, by any change does anyone have the original bootanimation but flashable?
Don't ave a flashable zip, if that's what you meant (and I actually have no clue how to create one, or whether it's even possible).
IIRC I had the same idea back when this happened to me, and I was told here (again, it's what I remember, but I could be wrong) that flashign a single file from recovery was not possible.
The only thing that could have eventually led to sth correct was that adb was available for a very short time when booting the phone in "AP Fastboot mode". I was able to adb inside but could not achieve a su prompt.
Don't wanna take your hopes down, but i ended up reflashing to stock rom... Sorry I can't be of any more help. But you should really dig in that thread I mentioned yesterday, maybe there are some more answers than at the time I posted there.
CoinCoin88 said:
Don't ave a flashable zip, if that's what you meant (and I actually have no clue how to create one, or whether it's even possible).
IIRC I had the same idea back when this happened to me, and I was told here (again, it's what I remember, but I could be wrong) that flashign a single file from recovery was not possible.
The only thing that could have eventually led to sth correct was that adb was available for a very short time when booting the phone in "AP Fastboot mode". I was able to adb inside but could not achieve a su prompt.
Don't wanna take your hopes down, but i ended up reflashing to stock rom... Sorry I can't be of any more help. But you should really dig in that thread I mentioned yesterday, maybe there are some more answers than at the time I posted there.
Click to expand...
Click to collapse
I flashed the stock firmware with Droid HD Utility but stiil tries to boot and nothing... The problem Started when i changed the bootanimation from stock to Moto X´s.
Does somebody have a probable fix? Thanks in Advance...
rbernabe83 said:
I flashed the stock firmware with Droid HD Utility but stiil tries to boot and nothing... The problem Started when i changed the bootanimation from stock to Moto X´s.
Does somebody have a probable fix? Thanks in Advance...
Click to expand...
Click to collapse
I dont feel like looking but IIRC the HD Utility doesnt flash the bootlogo. you will need to do it by hand while in fastboot mode.....
fastboot flash logo whatever_the_new_filename_is
cmh714 said:
I dont feel like looking but IIRC the HD Utility doesnt flash the bootlogo. you will need to do it by hand while in fastboot mode.....
fastboot flash logo whatever_the_new_filename_is
Click to expand...
Click to collapse
Fixed the issue i´ve found a solution in Q&A. i´ve flashed stock rom with rsd lite.
Thanks All for your help.:good:
cmh714 said:
I dont feel like looking but IIRC the HD Utility doesnt flash the bootlogo. you will need to do it by hand while in fastboot mode.....
fastboot flash logo whatever_the_new_filename_is
Click to expand...
Click to collapse
Well ****, had I known that a couple months ago it would have saved me a full reflash. have my thank sir!
Hi, decided to make this thread since I'm not getting help from the Ask questions thread. Friend of mine had me look into a N5 she got used and it's not working and wants me to see if I can get it to work. Thing is when you boot it up, it takes you to to the startup welcome screen no problem right to the 1st step which is choose a language, as soon as I select any language the screen stutters and the coloring goes all weird and goes to a black screen and sometimes reboots and back to the same welcome select language screen. I already tried wipiing everything, unlocking bootloader and wiping so I can get it back to stock as if it were new, I have no idea what they did to the phone but after doing that thought it would fix it but still having the same issue, any clues on what else to do? should i give up?
daLareid said:
Hi, decided to make this thread since I'm not getting help from the Ask questions thread. Friend of mine had me look into a N5 she got used and it's not working and wants me to see if I can get it to work. Thing is when you boot it up, it takes you to to the startup welcome screen no problem right to the 1st step which is choose a language, as soon as I select any language the screen stutters and the coloring goes all weird and goes to a black screen and sometimes reboots and back to the same welcome select language screen. I already tried wipiing everything, unlocking bootloader and wiping so I can get it back to stock as if it were new, I have no idea what they did to the phone but after doing that thought it would fix it but still having the same issue, any clues on what else to do? should i give up?
Click to expand...
Click to collapse
Have you tried flashing the factory image with fastboot? That's the first thing I would do.
_MetalHead_ said:
Have you tried flashing the factory image with fastboot? That's the first thing I would do.
Click to expand...
Click to collapse
You mean doing this, right?
http://forum.xda-developers.com/google-nexus-5/general/tutorial-how-to-flash-factory-image-t2513701/
Cause I tried that with no luck.
daLareid said:
You mean doing this, right?
http://forum.xda-developers.com/google-nexus-5/general/tutorial-how-to-flash-factory-image-t2513701/
Cause I tried that with no luck.
Click to expand...
Click to collapse
What do you mean no luck? Did you get an error message when you flashed it? Are you sure you did it correctly?
_MetalHead_ said:
What do you mean no luck? Did you get an error message when you flashed it? Are you sure you did it correctly?
Click to expand...
Click to collapse
I was able to go through with the whole process but after the reboot, I started up the phone but I'm still stuck on the Welcome screen, as soon as I choose a language the screen stutters and goes black.
daLareid said:
I was able to go through with the whole process but after the reboot, I started up the phone but I'm still stuck on the Welcome screen, as soon as I choose a language the screen stutters and goes black.
Click to expand...
Click to collapse
That's so strange. It seems like it would be a software issue but if you're 100% sure you were able to successfully flash a factory image then I really don't know what's going on. What software version did you flash? I would try to flash a factory image for a different software version. If you're on KitKat then flash a different KitKat image, if on Lollipop then flash a different lollipop image. Make sure to either run the flash-all.bat or to flash EVERYTHING in the image file that gets flashed in the script. That way you know 100% that the phone is back at factory conditions. If you're going to do it manually just open the flash-all.bat with a text editor and follow all the steps that are in the script and in that order. Take a screenshot of the terminal screen for me when it's done flashing.
_MetalHead_ said:
That's so strange. It seems like it would be a software issue but if you're 100% sure you were able to successfully flash a factory image then I really don't know what's going on. What software version did you flash? I would try to flash a factory image for a different software version. If you're on KitKat then flash a different KitKat image, if on Lollipop then flash a different lollipop image. Make sure to either run the flash-all.bat or to flash EVERYTHING in the image file that gets flashed in the script. That way you know 100% that the phone is back at factory conditions. If you're going to do it manually just open the flash-all.bat with a text editor and follow all the steps that are in the script and in that order. Take a screenshot of the terminal screen for me when it's done flashing.
Click to expand...
Click to collapse
Phone was on kitkat so I did it with kit kat, I just flashed 5.0.1 on it and it did go through because it did boot to the Lollipop Welcome screen but same thing happened as soon as I selected a language screen stuttered and stopped working.
daLareid said:
Phone was on kitkat so I did it with kit kat, I just flashed 5.0.1 on it and it did go through because it did boot to the Lollipop Welcome screen but same thing happened as soon as I selected a language screen stuttered and stopped working.
Click to expand...
Click to collapse
So this happened on KitKat as well as Lollipop? I don't know what to tell you then, it seems like it's a software glitch but that's pretty much ruled out. I wonder if it has something to do with data... like it's freaking out when it gets to the point that it has to transmit/receive data. Try doing it with WiFi on and off, SIM card in and out, and try flashing a different radio. If it still does it every time then I guess I'd RMA it.
_MetalHead_ said:
So this happened on KitKat as well as Lollipop? I don't know what to tell you then, it seems like it's a software glitch but that's pretty much ruled out. I wonder if it has something to do with data... like it's freaking out when it gets to the point that it has to transmit/receive data. Try doing it with WiFi on and off, SIM card in and out, and try flashing a different radio. If it still does it every time then I guess I'd RMA it.
Click to expand...
Click to collapse
Unfortunately I can't set any of the setting such as WiFi on or off because as soon as I tap on something the screen goes off, I guess it might be hardware (screen) related, thanks for your help.
daLareid said:
Hi, decided to make this thread since I'm not getting help from the Ask questions thread. Friend of mine had me look into a N5 she got used and it's not working and wants me to see if I can get it to work. Thing is when you boot it up, it takes you to to the startup welcome screen no problem right to the 1st step which is choose a language, as soon as I select any language the screen stutters and the coloring goes all weird and goes to a black screen and sometimes reboots and back to the same welcome select language screen. I already tried wipiing everything, unlocking bootloader and wiping so I can get it back to stock as if it were new, I have no idea what they did to the phone but after doing that thought it would fix it but still having the same issue, any clues on what else to do? should i give up?
Click to expand...
Click to collapse
Did you ever find a fix for this ?
qzcgd said:
Did you ever find a fix for this ?
Click to expand...
Click to collapse
No, I later found that some of the hardware inside (motherboard maybe? not sure which part) but that it was most likely from some irreparable damage to it, and it seemed worthless looking for a piece of an old phone to repair.
Does anybody know how to install Ubuntu or Kali Linux on moto g Turbo edition?
Or anybody know how to change the offline charging animation or how to port it from another phone?
Thanks in advance
umanggoel24 said:
Does anybody know how to install Ubuntu or Kali Linux on moto g Turbo edition?
Or anybody know how to change the offline charging animation or how to port it from another phone?
Thanks in advance
Click to expand...
Click to collapse
The "offline charging animation"? As in the battery icon you see when the device is off? Nope, not possible that I know of, it's part of the bootloader and can't be changed even if you found a way I stall Kali or Ubuntu, they still have to use the devices bootloader.
acejavelin said:
The "offline charging animation"? As in the battery icon you see when the device is off? Nope, not possible that I know of, it's part of the bootloader and can't be changed even if you found a way I stall Kali or Ubuntu, they still have to use the devices bootloader.
Click to expand...
Click to collapse
Does installing a custom rom changes bootloader too?
umanggoel24 said:
Does installing a custom rom changes bootloader too?
Click to expand...
Click to collapse
No, the bootloader is fixed from the original stock firmware, it cannot be changed, actually more correctly it cannot be downgraded and an unsigned or 3rd party bootloader cannot be flashed. The bootloader can only be upgraded with a signed, factory image.
The bootloader is an important piece of software, not only does it initiate the startup process and hand that off to the boot image, it also has tools for restoring original firmware images and some maintenance (fastboot), start a handful of factory and diagnostic tools, and start the recovery image. One if it's other jobs is to manage charging the battery in a "powered off" state after it has sufficient charge from the inbuilt electronics that can slow charge the battery until the bootloader can take over.
acejavelin said:
No, the bootloader is fixed from the original stock firmware, it cannot be changed, actually more correctly it cannot be downgraded and an unsigned or 3rd party bootloader cannot be flashed. The bootloader can only be upgraded with a signed, factory image.
The bootloader is an important piece of software, not only does it initiate the startup process and hand that off to the boot image, it also has tools for restoring original firmware images and some maintenance (fastboot), start a handful of factory and diagnostic tools, and start the recovery image. One if it's other jobs is to manage charging the battery in a "powered off" state after it has sufficient charge from the inbuilt electronics that can slow charge the battery until the bootloader can take over.
Click to expand...
Click to collapse
So how is it possible that custom roms changes offline charging animation too?
umanggoel24 said:
So how is it possible that custom roms changes offline charging animation too?
Click to expand...
Click to collapse
I don't think I have ever seen that... can you give me an example?
We are talking the same thing here, right? By "offline charging" you mean when the device is actually powered off, correct?
EDIT: I may be wrong, it appears in some devices the bootloader doesn't handle it by itself, but calls another process according to this answer on Stack Overflow... I am investigating more, I may have been wrong about this for a very long time. :/
When i was using stock rom on my phone the battery logo is different but when i use AOSP rom so its different and its also different when i used lineage os rom
Yes i mean when phone is switched off and connected to charger
Guys please help me. Can anyone who have an account at 4pda request the thermal.zip file fix for our phone and post it on xda please. Whenever I try to download it it says 404 not found. The screenshots shows much better performance from the phone after flashing the file. https: //4pda.ru/forum/index.php?showtopic=895159&st=1240#entry74738420. This is the link. Please help me thanks.
Special thanks to Asa Bay for providing another link to the requested file. Here it is http://www.mediafire.com/file/m9wqa9...patch.zip/file
Monster 00 said:
Special thanks to Asa Bay for providing another link to the requested file. Here it is http://www.mediafire.com/file/m9wqa9...patch.zip/file
Click to expand...
Click to collapse
Does it remove the Thermal Throttling, what is the AnTuTu score with it? By the way the mediafire link doesn't work. Since it's a small file could you please re-upload?
chemeng said:
Does it remove the Thermal Throttling, what is the AnTuTu score with it? By the way the mediafire link doesn't work. Since it's a small file could you please re-upload?
Click to expand...
Click to collapse
There are two files inside the zip. I flashed only the first one idk if I should flash the second one. I sent him a message but he hasn't replied yet. I ran CPU throttling test and it was always green. I never ran it before. On 4pda the screenshots of before and after show that it goes red before the flash and green after. So I guess it worked but antutu score is 95k. I got 106k on 28s. There is a performance over time graph and it showed that the CPU never got under 80% I also noticed that the 2 high performance cores never got to 2.3ghz. the maximum they got was 1.8ghz. Here is the link https://mega.nz/#!T0YGVKxa!R9R2f81CBxU40h-x2WeH5HmaU96X4KXWLeJdtxm8jjo
My phone is the x23 version 4/32gb
Monster 00 said:
There are two files inside the zip. I flashed only the first one idk if I should flash the second one. I sent him a message but he hasn't replied yet. I ran CPU throttling test and it was always green. I never ran it before. On 4pda the screenshots of before and after show that it goes red before the flash and green after. So I guess it worked but antutu score is 95k. I got 106k on 28s. There is a performance over time graph and it showed that the CPU never got under 80% I also noticed that the 2 high performance cores never got to 2.3ghz. the maximum they got was 1.8ghz. Here is the link https://mega.nz/#!T0YGVKxa!R9R2f81CBxU40h-x2WeH5HmaU96X4KXWLeJdtxm8jjo
My phone is the x23 version 4/32gb
Click to expand...
Click to collapse
hi!,
how am i going to flash this zip file? do i need to boot into twrp? im sorry i dont know what to do.
ag0ny1 said:
hi!,
how am i going to flash this zip file? do i need to boot into twrp? im sorry i dont know what to do.
Click to expand...
Click to collapse
Yes I used old twrp. I think 3.0.3 something like that
Monster 00 said:
Yes I used old twrp. I think 3.0.3 something like that
Click to expand...
Click to collapse
Can you tell me the process? because the last time I try to boot my phone into twrp, my phone bootloop.
ag0ny1 said:
Can you tell me the process? because the last time I try to boot my phone into twrp, my phone bootloop.
Click to expand...
Click to collapse
Sorry for late response. I was at work. I did get bootloop also. I didn't flash the twrp but I booted from my PC. I think it is an issue with the ROM. I installed back my modded ROM that I got from 4pda. It's EUI 6.0.30s mod that allows u to alter system partition but that doesn't mean that you can root it. I did the same thing again, that is, boot TWRP from my PC but before that make sure to save the zip file in a card reader that has USB-C .
Then reboot bootloader.
Fastboot boot recoveryname.img .
Unplug your phone from PC then plug in your card reader as you won't be able to read from the phone's memory since it's encrypted.
Go to Mount and select USB OTG
Go to install and navigate to usbotg and flash the file.
Note: u need to extract the 2zips inside the zip. U will get zip 1 and zip 2. Idk but I think zip1 removes the throttling and zip 2 restores it. I flashed only the first one and ran CPU throttling test and it was always green.
If u need the modded EUI6 tell me. Thanks
Monster 00 said:
Sorry for late response. I was at work. I did get bootloop also. I didn't flash the twrp but I booted from my PC. I think it is an issue with the ROM. I installed back my modded ROM that I got from 4pda. It's EUI 6.0.30s mod that allows u to alter system partition but that doesn't mean that you can root it. I did the same thing again, that is, boot TWRP from my PC but before that make sure to save the zip file in a card reader that has USB-C .
Then reboot bootloader.
Fastboot boot recoveryname.img .
Unplug your phone from PC then plug in your card reader as you won't be able to read from the phone's memory since it's encrypted.
Go to Mount and select USB OTG
Go to install and navigate to usbotg and flash the file.
Note: u need to extract the 2zips inside the zip. U will get zip 1 and zip 2. Idk but I think zip1 removes the throttling and zip 2 restores it. I flashed only the first one and ran CPU throttling test and it was always green.
If u need the modded EUI6 tell me. Thanks
Click to expand...
Click to collapse
hi man,
i already have the moded rom. yeah and i saw that throttling thing at the 4pda too.
thanks for your response. im gonna try this and give some feedback after. thanks again
PS:
how am i going to boot into default recovery again after the flashing? or is it going to boot into system without problem after the flashing?
ag0ny1 said:
hi man,
i already have the moded rom. yeah and i saw that throttling thing at the 4pda too.
thanks for your response. im gonna try this and give some feedback after. thanks again
PS:
how am i going to boot into default recovery again after the flashing? or is it going to boot into system without problem after the flashing?
Click to expand...
Click to collapse
Please do not flash it.
Just boot from it. That is,
"Fastboot boot twrp.img"
Monster 00 said:
Please do not flash it.
Just boot from it. That is,
"Fastboot boot twrp.img"
Click to expand...
Click to collapse
i mean yeah! i'm just going to boot into twrp. but what about after flashing the thermal? how am i going to boot into default recovery. because the last time i boot into recovery and boot into system directly in twrp, i got bootlooped. so how am i going to boot into system without problem?
ag0ny1 said:
i mean yeah! i'm just going to boot into twrp. but what about after flashing the thermal? how am i going to boot into default recovery. because the last time i boot into recovery and boot into system directly in twrp, i got bootlooped. so how am i going to boot into system without problem?
Click to expand...
Click to collapse
Actually I got bootlooped also but it happened only with the newer twrp. I stopped using it and I use the older one 3.03 i think. Also I stopped using the official EUI6 ROM. I use this one https://drive.google.com/file/d/1h0VsqO-V9jsxf1Pyv3muR1qoKuvSHunu/view.
It allows u to modify system partition but that doesn't mean that you can root it.
Install this one because you won't have any problem starting the device after installing the patch.
Now I have to tell u all something. On Google play store where I downloaded the CPU throttle app, I saw a review of someone saying that you need to delete a file to stop the throttling. I was using the modded ROM v1 with the patch but now that there is a newer one(v3) I installed it yesterday and I tried to do what that person said on Google play and guess what it worked. I deleted a file I think called thermal.conf. Before that I ran the test and performance was very bad that it even dropped under 40%. It became red like the screenshot at 4pda and even stopped responding but after deleting the file the performance was much better and it stayed green and never dropped under 80%. I haven't played any game right now so IDK if it really makes a difference.
I think you should just delete the file to make things simpler. It's located at system/etc/.tp
Because there is actually two files inside the zip and IDK which one to flash but I think the first zip was it.
Guys I need your help again. There is a boot.img at 4pda that can help us boot with root rights temporarily, that is, until we reboot the phone. This file also is unavailable so could anyone please help us get that file https://4pda.ru/forum/index.php?showtopic=895159&st=580#entry73892896. Thanks
I just ran AnTuTu and the performance was deceiving to me. I got only 92k. CPU:40k GPU:19k UX:26.9k MEM:5.7k. I don't like it at all because I got 106k on 28s without the patch or anything but when I entered the app it said high performance mode entered. I did not see it this time. On 28s I got 50k for CPU and 30k for UX and 6k+ for MEM
I played PUBG on low power without any overheat. I did so by accessing engineer mode. I think the 2 high performance cores are useless since they are not optimized. PPM: Low power GPU: Performance. The phone surely got warm but it did not heat like crazy and also not too much battery drain was observed.
I am a very experienced ROM enthusiast and owned plenty of Xiaomi/Oneplus devices.. This is my first pixel device. I loved the phone, more than the other mentioned companies. My pixel 7 Pro was my prized possession.. I've came close a couple of times botching a ROM flash, even once with my p7p (installing evo with February firmware instead of Jan, phone would boot to bootloader for a total of 2 seconds before dying again, had to spam flash phone in pixel flasher app until it recognized and luckily it did) but this time, trying to go from latest feb build to jan before flashing evo, my ****ing cable did something in the middle of flashing the second partition (b partition) and was almost to system, the partition it flashes before booting.. it was flashing the product partition.. literally already flashed every other partition except partition and system on the b slot. A slot was fully flashed.. phone literally wont respond to plugging into computer, into charger, holding down every combination of buttons... doesn't matter. I'm stumped how flashing a factory rom could have gone this horribly.. especially so late into the flashing process..
Beware guys; Make sure the cable you're using to flash is stable!
attached in this post is the logs I have pulled from the pixel flasher app.. if someone could bounce some ideas off of me or somehow make this make sense to me, it would be gladly appreciated.
Holding down the down volume button when starting doesn't enter bootloader? If it does, use Google's online Android Flash tool to go back to stock.
Try a different cable.
Try a different USB port.
Try another computer as well.
If any of these prompt some response, I think there's hope. Also try booting into fastboot from bootloader as well as recovery.
Prob hard brick.
im wondering, since i am just flashing the feb factory image on my rooted pixel and read this thread here: if my laptop (from which i operate the flashing procedure) were to malfunction like it did last night (bsod) - would i hard brick my phone, too? isnt that, where the other slot comes into play?
does this mean, every time i flash, my pc/laptop should never run into any issues whilst flashing or otherwise my phone will be effed?
xflowy said:
im wondering, since i am just flashing the feb factory image on my rooted pixel and read this thread here: if my laptop (from which i operate the flashing procedure) were to malfunction like it did last night (bsod) - would i hard brick my phone, too? isnt that, where the other slot comes into play?
does this mean, every time i flash, my pc/laptop should never run into any issues whilst flashing or otherwise my phone will be effed?
Click to expand...
Click to collapse
If you device is flashing something like the bootloader, and connection breaks for any reason at all, or the problem closes, etc, it will be a hard brick. You may get lucky, and it may be something unessential.
Arealhooman said:
If you device is flashing something like the bootloader, and connection breaks for any reason at all, or the problem closes, etc, it will be a hard brick. You may get lucky, and it may be something unessential.
Click to expand...
Click to collapse
uff ok. is there any way to avoid this? i mean, even my desktop pc (which is stable) could suffer from a power shortage in the house for example.
xflowy said:
uff ok. is there any way to avoid this? i mean, even my desktop pc (which is stable) could suffer from a power shortage in the house for example.
Click to expand...
Click to collapse
Nope. Get a battery. If a flash fails, 75 percent chance ur ****ed (and yes, I am pulling these statistics out off my ass, but I doubt I’m too much off)
Arealhooman said:
Nope. Get a battery. If a flash fails, 75 percent chance ur ****ed (and yes, I am pulling these statistics out off my ass, but I doubt I’m too much off)
Click to expand...
Click to collapse
A battery for my desktop PC?
xflowy said:
A battery for my desktop PC?
Click to expand...
Click to collapse
Google for "uninterruptible power supply" ...
xflowy said:
A battery for my desktop PC?
Click to expand...
Click to collapse
Yeah, no idea.
Maybe I'm wrong, but although the whole flashing process can fail if communication with device breaks, it's hard to actually fail while flashing a partition? Because the system first pushes the whole file and only then does it begin actual flashing. So whatever partition you are pushing at any given moment, if it fails to push it in its entirety, then it won't flash it... Unless data is corrupted during transfer?
xflowy said:
im wondering, since i am just flashing the feb factory image on my rooted pixel and read this thread here: if my laptop (from which i operate the flashing procedure) were to malfunction like it did last night (bsod) - would i hard brick my phone, too? isnt that, where the other slot comes into play?
does this mean, every time i flash, my pc/laptop should never run into any issues whilst flashing or otherwise my phone will be effed?
Click to expand...
Click to collapse
Arealhooman said:
If you device is flashing something like the bootloader, and connection breaks for any reason at all, or the problem closes, etc, it will be a hard brick. You may get lucky, and it may be something unessential.
Click to expand...
Click to collapse
The real answer to this is why google and the android community as a whole is pushing away from having a supporting third party recovery menu (implementing new partitions like init_boot and vendor_boot for recovery, also no working twrp). Why do you think Evolution ROM pushes so hard to be different and when flashing their newest build you do it not through the usual scary tedious bootloader way (THE SAME WAY WE ARE SUPPOSED TO FLASH OUR FACTORY ROMS) to making their own recovery, which obviously means only flashing one partition, and adb sideloading the rom. its like google wants you to break your phone and they are making it more convenient for third party roms to package theirs the same way. i should have never left evo.. haha.
Oh, and sorry for the late reply. I thought I would leave my phone alone for a little to see if it would help; I'm accident prone and lose things constantly, and what do ya know I just lost my phone that I can't even call to find lmao. Ill keep updated on everyones opinions on what i should try whenever i find it
krakout said:
Maybe I'm wrong, but although the whole flashing process can fail if communication with device breaks, it's hard to actually fail while flashing a partition? Because the system first pushes the whole file and only then does it begin actual flashing. So whatever partition you are pushing at any given moment, if it fails to push it in its entirety, then it won't flash it... Unless data is corrupted during transfer?
Click to expand...
Click to collapse
Google uses sparse images... I think they're maxed at like 262MB? So like you'll see the flashing process go Product 1, Product 2, etc... It flashes after the full sparse image is transferred but if you don't have the full image when something goes wrong, you can still brick.
EtherealRemnant said:
Google uses sparse images... I think they're maxed at like 262MB? So like you'll see the flashing process go Product 1, Product 2, etc... It flashes after the full sparse image is transferred but if you don't have the full image when something goes wrong, you can still brick.
Click to expand...
Click to collapse
Ah I see, makes sense.
xflowy said:
uff ok. is there any way to avoid this? i mean, even my desktop pc (which is stable) could suffer from a power shortage in the house for example.
Click to expand...
Click to collapse
Oh brother, how often does that actually even happen?
HipKat said:
Oh brother, how often does that actually even happen?
Click to expand...
Click to collapse
Sure, not really often. But when it does..
Arealhooman said:
If you device is flashing something like the bootloader, and connection breaks for any reason at all, or the problem closes, etc, it will be a hard brick. You may get lucky, and it may be something unessential.
Click to expand...
Click to collapse
This is incorrect. The image is sent to the device memory (RAM) prior to actually being written. It won't write it to flash storage until AFTER the entire image is received.
zacattackkc said:
trying to go from latest feb build to jan before flashing....
Click to expand...
Click to collapse
It sounds like you may have tripped some anti-downgrade code.
EDIT: I can confirm that the bootloader version was changed in the FEB image as compared to the JAN image.
96carboard said:
This is incorrect. The image is sent to the device memory (RAM) prior to actually being written. It won't write it to flash storage until AFTER the entire image is received.
Click to expand...
Click to collapse
Well, I use Samsung, so I am assuming fastboot is similar…