Hello guys,
I had my phone rooted with latest twrp. I flashed stock+ rom with Franco Kernel 25r and the A.R.I.S.E file for better sound. I've done the same set up minus the ARISE file and never had an issue.
well to my luck it kept bootlooping and I wasn't able to get back into my custom recovery. When I got home and got my hands on a pc I did a factory reset by manually flashing stock google img . I even used a couple tools since I ran out of ideas and still no luck.
I'm able to do anything through fastboot but I can't seem to get into my recovery at all.
Any ideas or tips of where I should go next?
Not a Hardbrick
As long as you can get to the bootloader mode, you haven't hard bricked your device. Hardbricking is a point where you cant boot your device and in to bootloader so there is no way to flash your device to a useable state.
Now as you can boot to the bootloader, just fastboot boot twrp.img and if you have a factory image zip, copy it in your device internal storage and flash it. Its that simple, provided you are already using an unencrypted boot.img in your current setup. Or else the next step is to flash an decrypted boot.img(you will loose all your userdata and internal storage data.). There are ways to mount the the encrypted filesystem if you are using a pin or password combo with your fingerprint. But without it its a bit more trickier so just for ease and if you dont have any inseparable data in your device now just flash a decrypted boot.img and then you can easily mount your internal storage to your pc and copy the factory image and the rest you already know..
At this point, I'd recommend a full reset.
Flash all the images in the latest Android M factory image (don't flash DP5 or similar N based ROMs): Recovery, Boot, System, Bootloader, Radio, everything.
Once you get stabilized and back into a working phone, then start rooting and messing around with kernels and what not.
To be completely honest, I've flashed nearly every ROM for the 6p, as well as my other Nexus devices, Galaxy phones, Sony phones, and no-name brands and none of those ultra modified kernels did any noticeable change. I tried the F2FS, NTFS, etc file system changes, tweaks to the governors and IO's, all of that, and found the stock kernel was the best. If a kernel with a different IO Scheduler worked even 10% better than the current implementation, and was just as stable, don't you think the Google/Android Engineers would've pushed that to live?
Currently running Pure Nexus July 23rd Update, everything stock that comes with it, Systemless Root/XPosed, and Viper4Android and have never had a performance or stability issue. I'd recommend you do the same.
leninmon said:
As long as you can get to the bootloader mode, you haven't hard bricked your device. Hardbricking is a point where you cant boot your device and in to bootloader so there is no way to flash your device to a useable state.
Now as you can boot to the bootloader, just fastboot boot twrp.img and if you have a factory image zip, copy it in your device internal storage and flash it. Its that simple, provided you are already using an unencrypted boot.img in your current setup. Or else the next step is to flash an decrypted boot.img(you will loose all your userdata and internal storage data.). There are ways to mount the the encrypted filesystem if you are using a pin or password combo with your fingerprint. But without it its a bit more trickier so just for ease and if you dont have any inseparable data in your device now just flash a decrypted boot.img and then you can easily mount your internal storage to your pc and copy the factory image and the rest you already know..
Click to expand...
Click to collapse
First of all thank you for the response.
I've tried flashing the most current twrp and it seems to go through fine on fast boot but when I actually try to get into recovery from the device it will boot loop and just keep doing that.
How can I get into the phones storage through fastboot?
Where can I get the factory zip?
it feels as if everything seems to go good through fastboot but when I actually try to boot the phone nothing seems to work.
Wiltron said:
At this point, I'd recommend a full reset.
Flash all the images in the latest Android M factory image (don't flash DP5 or similar N based ROMs): Recovery, Boot, System, Bootloader, Radio, everything.
Once you get stabilized and back into a working phone, then start rooting and messing around with kernels and what not.
To be completely honest, I've flashed nearly every ROM for the 6p, as well as my other Nexus devices, Galaxy phones, Sony phones, and no-name brands and none of those ultra modified kernels did any noticeable change. I tried the F2FS, NTFS, etc file system changes, tweaks to the governors and IO's, all of that, and found the stock kernel was the best. If a kernel with a different IO Scheduler worked even 10% better than the current implementation, and was just as stable, don't you think the Google/Android Engineers would've pushed that to live?
Currently running Pure Nexus July 23rd Update, everything stock that comes with it, Systemless Root/XPosed, and Viper4Android and have never had a performance or stability issue. I'd recommend you do the same.
Click to expand...
Click to collapse
Thanks for the reply.
I've done the manual flashing already and flashed everything single item the most current factory image. Everything seemed to have gone through okay but when I rebooted the phone it was back to 0.
I'm actually considering getting rid of the phone now since it is my daily =/
Format each partition before flashing.
fastboot format <partition>
wait until it's done, then
fastboot flash <partition> <image>
Some partitions can't be formatted, which there are ways around, but try this first.
Just get to bootloader mode and try booting the twrp.img
fastboot boot twrp.img
From the twrp ui, go to advanced wipe and format your storage.
To mount the internal storage on your PC, enable mtp from twrp screen.
If U are using a decrypted boot.img, it will easily mount ur internal storage. Or try flashing a decrypted boot.img
fastboot flash boot boot.img
Then try the above again..
leninmon said:
Just get to bootloader mode and try booting the twrp.img
fastboot boot twrp.img
From the twrp ui, go to advanced wipe and format your storage.
To mount the internal storage on your PC, enable mtp from twrp screen.
If U are using a decrypted boot.img, it will easily mount ur internal storage. Or try flashing a decrypted boot.img
fastboot flash boot boot.img
Then try the above again..
Click to expand...
Click to collapse
I flashed the twrp.img and it went through successfully at least on the computer it did but when the phone actually tries to get into recovery (twrp) it will start to boot loop and keep on doing that. I tried both an encrypted and decrypted boot img but it still made no difference.
I'm really going crazy over this
Wiltron said:
Format each partition before flashing.
fastboot format <partition>
wait until it's done, then
fastboot flash <partition> <image>
Some partitions can't be formatted, which there are ways around, but try this first.
Click to expand...
Click to collapse
I just tried this and had no luck =/....the phone wont get past the google boot screen
You need to explain more on what you actually tried here.
Just download the latest factory image and try to flash the latest bootloader using fastboot.
Then boot to the bootloader and try formating the device. Not wiping
Then you have to
fastboot boot twrp.img
I believe you have only tried wiping not formating. I faced similar issue before. But once I flashed a decrypted boot.img, it cleared the user data and then I was able to get to twrp.
Maybe your twrp img is corrupted if this didn't work.
leninmon said:
You need to explain more on what you actually tried here.
Just download the latest factory image and try to flash the latest bootloader using fastboot.
Then boot to the bootloader and try formating the device. Not wiping
Then you have to
fastboot boot twrp.img
I believe you have only tried wiping not formating. I faced similar issue before. But once I flashed a decrypted boot.img, it cleared the user data and then I was able to get to twrp.
Maybe your twrp img is corrupted if this didn't work.
Click to expand...
Click to collapse
i just flashed the latest bootloader from the most recent factory image and i did the command format user data and then tried the fastboot boot twrp and the phone will then try to get into recovery, the google logo comes up lasts a couple seconds and boot loops all over to where is says my phone cant be check for corruption
By now i should have been able to get into recovery and it wont go through
edgarted said:
i just flashed the latest bootloader from the most recent factory image and i did the command format user data and then tried the fastboot boot twrp and the phone will then try to get into recovery, the google logo comes up lasts a couple seconds and boot loops all over to where is says my phone cant be check for corruption
By now i should have been able to get into recovery and it wont go through
Click to expand...
Click to collapse
download a factory image and run the flash all file...... it should reboot your phone after 5 minutes and the issue should be resolved.. a hard brick would be a device that does nothing.... in this case i believe that you just didnt do something right.
Then download the latest factory image and extract it
fastboot flash radio.img
fastboot flash bootloader.img
& do a fastboot update the rest archive file as it is
This will flash the rom via fastboot& U don't have to rely on TWRP or CWM
i42o said:
download a factory image and run the flash all file...... it should reboot your phone after 5 minutes and the issue should be resolved.. a hard brick would be a device that does nothing.... in this case i believe that you just didnt do something right.
Click to expand...
Click to collapse
I was really really hoping this would help. I erase/formated everything before flashing anything. I then ran the flash-all file and it took a couple of minutes and it said finished on the command box and my phone restarted and went into the white google logo and rebooted again with a bootloop. I waited around 15 minutes hoping it would start but it didn't.
It honestly feels as if the phone is not processing the full commands but on the pc it seems to go through successfully
is there a way to force an install of a rom and see if maybe a dirty flash over the stock one will allow it to start up?
leninmon said:
Then download the latest factory image and extract it
fastboot flash radio.img
fastboot flash bootloader.img
& do a fastboot update the rest archive file as it is
This will flash the rom via fastboot& U don't have to rely on TWRP or CWM
Click to expand...
Click to collapse
i know how to flash the radio and bootloader but how do i do a fastboot update?
edgarted said:
i know how to flash the radio and bootloader but how do i do a fastboot update?
Click to expand...
Click to collapse
Just unzip the factory image and there U can see the flash shell script files too. Open them in a text editor & U could see the exact command. In a factory img, they also do the same thing via script files. Flashing the radio & bootloader & updating the rest archive
so this is what I've done
I've manually flashed every file needed for the factory image from google.
I also tried wugfresh tool kit which is great but didn't help me much. I flashed stock recovery and treid to boot into to and nothing. I flashed a customer recovery and nothing.
It always does the same thing
the screen that says my phone can't be checked for corruption and then the google sign comes up stays on for a couple seconds and then it bootloops to the can't be checked for corruption.
I try to get into recovery using fastboot commands and the phone does the same exact thing.
I was even able to lock and relock the bootloader and I was able to successfully flash everything at least that is what it showed on the computer
so ive read almost every thread that had to do with bricking and I feel like an expert now but im starting to think it is done =/
edgarted said:
so this is what I've done
I've manually flashed every file needed for the factory image from google.
I also tried wugfresh tool kit which is great but didn't help me much. I flashed stock recovery and treid to boot into to and nothing. I flashed a customer recovery and nothing.
It always does the same thing
the screen that says my phone can't be checked for corruption and then the google sign comes up stays on for a couple seconds and then it bootloops to the can't be checked for corruption.
I try to get into recovery using fastboot commands and the phone does the same exact thing.
I was even able to lock and relock the bootloader and I was able to successfully flash everything at least that is what it showed on the computer
so ive read almost every thread that had to do with bricking and I feel like an expert now but im starting to think it is done =/
Click to expand...
Click to collapse
Hey there. First off make sure to unlock again your bootloader. Then you may follow post # 10 of @Heisenberg 's flashing guide for our device.
First images to flash would be bootloader and radio. First flash bootloader, then make sure to issue the command adb reboot-bootloader. Then afterwards once the phone has rebooted back to bootloader, flash radio, then again do the adb reboot-bootloader again.
Once the phone is again back to bootloader flash the rest of the images except userdata. For the boot.img and recovery.img, flash the stock ones-don't use the decrypted boot.img and don't flash the twrp.img yet. Once all necessary images have been flashed issue the reboot-booloater command one more time, then on the bootloader screen choose the reboot option. Wait anywhere from 3-10 minutes for the phone to load. Let us know how it goes for you.
blitzkriegger said:
Hey there. First off make sure to unlock again your bootloader. Then you may follow post # 10 of @Heisenberg 's flashing guide for our device.
First images to flash would be bootloader and radio. First flash bootloader, then make sure to issue the command adb reboot-bootloader. Then afterwards once the phone has rebooted back to bootloader, flash radio, then again do the adb reboot-bootloader again.
Once the phone is again back to bootloader flash the rest of the images except userdata. For the boot.img and recovery.img, flash the stock ones-don't use the decrypted boot.img and don't flash the twrp.img yet. Once all necessary images have been flashed issue the reboot-booloater command one more time, then on the bootloader screen choose the reboot option. Wait anywhere from 3-10 minutes for the phone to load. Let us know how it goes for you.
Click to expand...
Click to collapse
Hello and thank you for helping.
I tried this method a couple of minutes ago. I flashed them this same way
fastboot flash bootloader C:\angler\images\bootloader-angler-angler-xx.xx.img
fastboot reboot-bootloader
fastboot flash radio C:\angler\images\radio-angler-angler-xx.xx.img
fastboot reboot-bootloader
fastboot flash boot C:\angler\images\boot.img
fastboot erase cache
fastboot flash cache C:\angler\images\cache.img
fastboot flash recovery C:\angler\images\recovery.img
fastboot flash system C:\angler\images\system.img
fastboot flash vendor C:\angler\images\vendor.img
It does the same exact thing it will try and restart the phone, the message that says it can't be checked for corruption the google logo comes up and it repeats it self non stop.
This is what doesn't make sense to me.
This is the file that I had flashed through twrp when it was working fine
Leviticus 1.3 - http://forum.xda-developers.com/android/software/r-s-e-sound-systems-auditory-research-t3379709
edgarted said:
Hello and thank you for helping.
I tried this method a couple of minutes ago. I flashed them this same way
fastboot flash bootloader C:\angler\images\bootloader-angler-angler-xx.xx.img
fastboot reboot-bootloader
fastboot flash radio C:\angler\images\radio-angler-angler-xx.xx.img
fastboot reboot-bootloader
fastboot flash boot C:\angler\images\boot.img
fastboot erase cache
fastboot flash cache C:\angler\images\cache.img
fastboot flash recovery C:\angler\images\recovery.img
fastboot flash system C:\angler\images\system.img
fastboot flash vendor C:\angler\images\vendor.img
It does the same exact thing it will try and restart the phone, the message that says it can't be checked for corruption the google logo comes up and it repeats it self non stop.
This is what doesn't make sense to me.
This is the file that I had flashed through twrp when it was working fine
Leviticus 1.3 - http://forum.xda-developers.com/android/software/r-s-e-sound-systems-auditory-research-t3379709
Click to expand...
Click to collapse
This is weird. What version of the stock factory images did you flash? I've been using leviticus 1.3 since it came out and when i was still on stock rom. I switched over to cm builds and have been flashing every nightly since the 7/24th build, and in the process repeatesly reflashing the aound mod along, and i've had zero issues with the phone booting afterwards.
Note:
This is not bootanimation, this is the splash screen (the Mi' boot logo which is displayed when device is switched ON)
This is for Redmi 4A/4 Only..
For other devices, please send me your splash.img so that I can create a tool for you too.
Requirements:
1. Rooted Redmi 4A/4 (any ROM)
2. Terminal Emulator app
STEPS to create & flash splash.img:
Same procedure as in here:
[GUIDE] How to Create Custom Splash Screen (Boot Logo) for Redmi 2/3
Hit the Thanks :good: button if it worked for you
You're welcome to post the splash images that you created..
Thanks to @karantamboli who provided stock splash.img of Redmi 4A..
Hi. If I converte a splashscreen image via gimp, what would be the image settings?
Custom Bootloader image and Splash Logo..
Flashable zip : https://drive.google.com/file/d/0BxPVo9bN1AVAUHNEU3J1STh3cTA/view?usp=sharing
Splash Image Flash Through Bootloader ( CMD: fastboot flash splash spalsh.img) For Reboot (fastboot reboot) :
https://drive.google.com/file/d/0BxPVo9bN1AVANGY2cVh2dEN4UTg/view?usp=sharing
I was looking for this since last week. Please upload more flashable files with screnshot plz
Unable to flash it through twrp
i tried to flash it but my logo comes only for a second and then it gets replaced by the stock logo (note i have a custom ROM and have different boot video ) fastboot logo is fine it works
I tried too and had the same result, only fastboot works.
I also tried to flash a custom logo, but I didn't use the .bat file because I'm using a linux OS. I searched to find a linux version of the script but I found only a request in another device' s thread with no answer from the creator of the tool. So I tried to use the commands from .bat file. I used "cat" command to join the files which I found that is equivalent to "copy /b" and the "720x1280_header.img" which provided, but it didn't work. I get only af small penguin icon for both fastboot and splash which I suppose is the linux kernel' s default splash. For fastboot I used the "fastboot.img" which also provided, so doesn't seems that is the image I made problem.
Doesn't Work! Atleast must update the thread.
[email protected] said:
i tried to flash it but my logo comes only for a second and then it gets replaced by the stock logo (note i have a custom ROM and have different boot video ) fastboot logo is fine it works
Click to expand...
Click to collapse
smurfisrael03 said:
Doesn't Work! Atleast must update the thread.
Click to expand...
Click to collapse
If boot logo gets instantly replaced by the stock one, use this modified version by PG:
https://forum.xda-developers.com/showpost.php?p=75994298&postcount=9
Worked perfectly on my (updated) 4A.
nice
Does someone know how to change the boot logo/splash screen on Zenfone 3 Z017D?
Thanks
Sorry for my bad English
Are you talking about the splash screen or the boot animation? The boot animation is the file "bootanimation.zip" located in /system/media.
The splash partition for the ze552kl is mmcblk0p48, but using fastboot you can flash it with just the "splash" designation, "fastboot flash splash splash.img".
I would be very careful with what you flash, I soft-bricked my phone using an incorrect file, lol.
wang1chung said:
Are you talking about the splash screen or the boot animation? The boot animation is the file "bootanimation.zip" located in /system/media.
The splash partition for the ze552kl is mmcblk0p48, but using freeboot you can flash it with just the "splash" designation, "freeboot flash splash splash.img".
I would be very careful with what you flash, I soft-bricked my phone using an incorrect file, lol.
Click to expand...
Click to collapse
Thanks, I'll give it a try
BTW, for ZE520KL, where is the splash screen located?
Chances are it'll be flashable with the same command "fastboot flash splash image.bin".
If you want to double check, install parted and run "parted /dev/block/mmcblk0", then type "p" and enter. Verify your partition is named "splash".
Once you run that command, you can figure out exactly which partition it is (eg. mmcblk0p48) and then can back it up with "dd if=/dev/block/mmcblk0p48 of=/sdcard/splash-backup.bin" to flash in the event of a soft brick via the fastboot flash command.
Might as well post the entire output of the parted command for other people to reference.
hi,
this forum provided me with a ton of useful info but i still couldn't manage to root my phone (F5321), let alone implement custom recovery. after flashing TWRP i always end up either with a bootloop or the screen stuck on displaying 'sony' (waited +20min). i tried the following procedure (at first just 1 + 3):
1) flash via flashtool/xperifirm [flashmode, stock 34.4.A.2.118, wipe userdata // wipe everything]
2) fastboot flash boot boot.img [genesis kernel 1.09 // modded img from this thread // patched img with rootkernel]
3) fastboot flash recovery twrp.img [TWRP 3.3.1 // 3.3.2]
4) directly start into TWRP, format data (to get rid of encryption), wipe cache and reboot to system
=> every time: boot loop until sony screen or it gets stuck on the sony screen
=> i can still start into TWRP
=> flashing stock without TWRP works just fine
edit: it even bootloops when starting TWRP via fastboot boot twrp.img (no matter if before or after first start of flashed stock)
edit2: system boot works if i use TWRP in read-only mode ... but then i can't root or do anything fun ...
any ideas what i can try next?
shikaji said:
hi,
this forum provided me with a ton of useful info but i still couldn't manage to root my phone (F5321), let alone implement custom recovery. after flashing TWRP i always end up either with a bootloop or the screen stuck on displaying 'sony' (waited +20min). i tried the following procedure (at first just 1 + 3):
1) flash via flashtool/xperifirm [flashmode, stock 34.4.A.2.118, wipe userdata // wipe everything]
2) fastboot flash boot boot.img [genesis kernel 1.09 // modded img from this thread // patched img with rootkernel]
3) fastboot flash recovery twrp.img [TWRP 3.3.1 // 3.3.2]
4) directly start into TWRP, format data (to get rid of encryption), wipe cache and reboot to system
=> every time: boot loop until sony screen or it gets stuck on the sony screen
=> i can still start into TWRP
=> flashing stock without TWRP works just fine
edit: it even bootloops when starting TWRP via fastboot boot twrp.img (no matter if before or after first start of flashed stock)
edit2: system boot works if i use TWRP in read-only mode ... but then i can't root or do anything fun ...
any ideas what i can try next?
Click to expand...
Click to collapse
I had a very difficult time rooting my Xperia X Compact (F5321) using the method you describe above. I had exactly the same problem with bootloop and sticking on the Sony screen. My problem was that I did not rename the boot118.img (Modded boot img for 34.4.A.2.118)to boot.img before I flashed it over ADB which resulted in the issues you mentioned. So I'm assuming it's an issue with your boot.img file. Maybe try the original boot118.img?
So I opened up ADB and flashed the renamed boot.img file, followed by Twrp. Then I booted into TWRP recovery (power button + volume down) and installed the supersu (or magisk if you prefer) and drmfix.
Then I rebooted to system and after a few minutes it booted normally into the Xperia homescreen.
Regards,
Dave
funkoot said:
My problem was that I did not rename the boot118.img (Modded boot img for 34.4.A.2.118)to boot.img before I flashed it over ADB which resulted in the issues you mentioned. So I'm assuming it's an issue with your boot.img file. Maybe try the original boot118.img?
Click to expand...
Click to collapse
does the file name of the boot image matter even if i of course change the command accordingly to "fastboot flash boot boot118.img"? i feel like that can't really be but i'll give it a try anyway, thanks!
shikaji said:
does the file name of the boot image matter even if i of course change the command accordingly to "fastboot flash boot boot118.img"? i feel like that can't really be but i'll give it a try anyway, thanks!
Click to expand...
Click to collapse
nope, that wasn't it either.
i also tried now having the boot118.img patched with magsik but same problem occurs. just can't get it to work and i don't know why.
shikaji said:
nope, that wasn't it either.
i also tried now having the boot118.img patched with magsik but same problem occurs. just can't get it to work and i don't know why.
Click to expand...
Click to collapse
I also had lot of problems with thjis root procedure.
The info i found
in twrp the question if the twrp app should be installed choose do not install
After this i was able to boot correctly and install omni, gaaps, magisk
Everytime in TWRP choose ---do not install twrp app
Bluestar01 said:
I also had lot of problems with thjis root procedure.
The info i found
in twrp the question if the twrp app should be installed choose do not install
After this i was able to boot correctly and install omni, gaaps, magisk
Everytime in TWRP choose ---do not install twrp app
Click to expand...
Click to collapse
unfortunately i've tried that as well already. same thing - stuck at sony screen or bootloop.
Hello, any updates ? I have the same problem, after flashing my F5321 with Flashtool to update from android 6 to 8...
I see the splash screen with NOTHING logo and "Powered by Android" at the bottom. After 15 seconds or so, the phone reboots.
This started happening after I erased the persist partition using fastboot.
A few things I tried which didn't work:
Sideloading a full 1.1.4 hotfix zip file using adb.
Factory resetting from the recovery and fastboot.
Format persist partition as ext4, "fastboot format:ext4 persist".
I don't see persist.img included in the firmware release. Can anyone extract the persist partition from their Nothing Phone (1)? I can flash persist.img and hopefully get the phone to boot properly.
Or if it's possible to enable diag mode from the recovery image. I don't know if it's possible to set sys.usb.config to diag,adb on recovery. I took a qcn backup beforehand. I can just restore that.
Thanks to @ayed78 providing persist.img from their device, I was able to boot into Android. I restored the qcn backup to restore the IMEIs and therefore restore cellular network connectivity.
arinc9 said:
I see the splash screen with NOTHING logo and "Powered by Android" at the bottom. After 15 seconds or so, the phone reboots.
This started happening after I erased the persist partition using fastboot.
A few things I tried which didn't work:
Sideloading a full 1.1.4 hotfix zip file using adb.
Factory resetting from the recovery and fastboot.
Format persist partition as ext4, "fastboot format:ext4 persist".
I don't see persist.img included in the firmware release. Can anyone extract the persist partition from their Nothing Phone (1)? I can flash persist.img and hopefully get the phone to boot properly.
Or if it's possible to enable diag mode from the recovery image. I don't know if it's possible to set sys.usb.config to diag,adb on recovery. I took a qcn backup beforehand. I can just restore that.
Click to expand...
Click to collapse
I will make a tutorial about brick fix tonight wich worked for me. Hope it'll work for yours
AntoXik72 said:
I will make a tutorial about brick fix tonight wich worked for me. Hope it'll work for yours
Click to expand...
Click to collapse
Great! Keep me posted.
Posting a short version of my reply here, from https://forum.xda-developers.com/t/how-to-unbrick-nothing-phone-1-fastboot-bootloop.4501439/
I've tried this on my Nothing Phone (1) EEA version which bootloops. It doesn't work. Whilst booting from the A slot, there's the 15 seconds of splash screen, then it reboots, same as before.
Flashing to A slot was completed without any errors. I don't think this super image includes the persist partition. My phone started bootlooping after I erased the persist partition. Can anyone upload their persist partition for the global or EEA version?