Related
I recently got xperia P and wanted to flash @Abhinav2[/user]'s Carbon ROM. Here is what I did step wise:
Unlocked the device from Developer World without any errors from Fastboot.
Downloaded and saved the zips to my SDCARD
Backed up my data (Text Messages, Call Logs using Super Backup)
Rebooted to bootloader with blue LED on and stable.
Flashed the Carbon Rom's boot image with
Code:
fastboot flash boot boot.img
Fastboot returned no errors and then I powered on my device.
While the bootsplash showed up, I was pressing all side buttons simultaneously.
The problem is that all I can see is a blank screen and nothing else after the bootsplash ends. The device does not enter recovery. I tried several other boot images like one from @percy_g2's CM. Everything fails. Even tried unlocking again which shows status aborted
Code:
device already unlocked
. Only Kernel that works is @Abhinav2's Dual recovery Kernel.
I'd like to know a way out of it because Carbon ROM is as slow as snail on AJ's Dual recovery Kernel.
Regards,
@danishsajjad
The fact that only you have this problem in the entire forum means there's something wrong with you or your device.
Flash aj kernel, use its recovery to flash carbon rom. Boot it up. Then flash the kernel included in the rom zip.
Problem solved.
@danishsajjad
Hey everyone!
I own a BluBoo X6 (MT6732) and have been having some difficulty installing a custom recovery on my device. As the title explains, after I flash a custom recovery onto the device I am presented with a blank black screen for about 10-20 seconds and the the phone will boot like normal to the Android lock screen. This phone seems to have little to no support at all that I could find online, so I've only been working off the stock ROM. My attempts to have been as follows:
Using MTKDroidTools with the stock Boot.img to create a CWM recovery (Flashed from that application) - Blank screen then boots
Using MTKDroidTools with the stock Boot.img to create a CWM recovery (Flashed via SP Flash Tools) - Blank screen then boots
Using MTKDroidTools with the stock Boot.img to create a CWM recovery (Flashed via Android app) - Blank screen then boots
Using TWRP Setup with to create a TWRP recovery (Flashed from that application) - Doesn't install anything and stock recovery works perfectly
I haven't found any other one-click form of applications so my next step will likely be to try and port a recovery from a different phone but I thought I'd post my current issue incase it's something craz obvious that I don't know about as I'm 100% noob and trying to learn.
Thanks in advance!
Hello!
Thanks for reading this thread, there's a lot that I'm about to say based on what has happened for the past 8 hours of troubleshooting.
I hope you'll be able to help me regarding my issue.
Everything was going well as I on my way to unlock my bootloader (done) and root my device.
After rooting via TWRP, I'm stuck on the white XPERIA logo screen.
Proceeded to wipe my phone, and thanks to my stupidity, loss of OS.
Downloaded an GLOBAL OS online, tried to flash into my device with FlashTool.
Error came to me as I needed flash script.
Search online, to no avail, I went to my final option
I saw a tutorial of creating a pre-rooted ROM : https://forum.xda-developers.com/crossdevice-dev/sony/tool-prfcreator-easily-create-pre-t2859904
I attached my OS I previously downloaded which i tried to flash with FlashTool, attached SuperSu into the application and a flashablezip (as instructed).
Flashed this pre-rooted ROM into my device using TWRP, rebooted.
New problem: Stuck at white Sony logo, couldn't enter TWRP.
Flashed in via cmd.exe a working boot.img & recovery.img.
TWRP now works, but I'm back to square one : stuck at the white XPERIA logo screen.
If you've read all of that, I thank you so much for doing so.
I hope that you'll be able to help me after these gruesome 8-hours of researching, trial & error session.
It's about time I requested help from professionals.
Thank you!
Edit : I can boot up my phone now, however that's achievable by removing SuperSu via TWRP.
This is no longer an urgent need for help, but it will be nice if I could get an idea why would I be stuck at the XPERIA logo screen when SuperSu is installed.
Mercuryus said:
Hello!
Thanks for reading this thread, there's a lot that I'm about to say based on what has happened for the past 8 hours of troubleshooting.
I hope you'll be able to help me regarding my issue.
Everything was going well as I on my way to unlock my bootloader (done) and root my device.
After rooting via TWRP, I'm stuck on the white XPERIA logo screen.
Proceeded to wipe my phone, and thanks to my stupidity, loss of OS.
Downloaded an GLOBAL OS online, tried to flash into my device with FlashTool.
Error came to me as I needed flash script.
Search online, to no avail, I went to my final option
I saw a tutorial of creating a pre-rooted ROM : https://forum.xda-developers.com/crossdevice-dev/sony/tool-prfcreator-easily-create-pre-t2859904
I attached my OS I previously downloaded which i tried to flash with FlashTool, attached SuperSu into the application and a flashablezip (as instructed).
Flashed this pre-rooted ROM into my device using TWRP, rebooted.
New problem: Stuck at white Sony logo, couldn't enter TWRP.
Flashed in via cmd.exe a working boot.img & recovery.img.
TWRP now works, but I'm back to square one : stuck at the white XPERIA logo screen.
If you've read all of that, I thank you so much for doing so.
I hope that you'll be able to help me after these gruesome 8-hours of researching, trial & error session.
It's about time I requested help from professionals.
Thank you!
Edit : I can boot up my phone now, however that's achievable by removing SuperSu via TWRP.
This is no longer an urgent need for help, but it will be nice if I could get an idea why would I be stuck at the XPERIA logo screen when SuperSu is installed.
Click to expand...
Click to collapse
Hi, without any logcat it will be very hard to help you
I was in MIUI Eu rom, I think the 7.11.23 update change the boot logo/image. Now I'm in RR 5.8.5 I flashed many zip intended for changing boot image but still the Boot image doesn't change.
I have same issue here, after install 7.12.8 firmware. And i'm install pixel splash.img and bootanimation. Bootanimation changed successfully, but boot logo does't change.. Btw, there is " unlocked " text, below the boot logo
dev.azra said:
I have same issue here, after install 7.12.8 firmware. And i'm install pixel splash.img and bootanimation. Bootanimation changed successfully, but boot logo does't change.. Btw, there is " unlocked " text, below the boot logo
Click to expand...
Click to collapse
i posted it also to miui eu community, hope someone will help us
it's a new feature from xiaomi actually. if you want to have custom splash image, flash older firmware
Custom boot logo upgrade problem.
My boot logo used to change after I flashed another boot logo but I recently can't change it after flashing to another ROM called 'Alpha Centauri'. I flashed the logo 10 times but all in hell. Can anyone help me out.
Thanks in advance
primarina said:
I was in MIUI Eu rom, I think the 7.11.23 update change the boot logo/image. Now I'm in RR 5.8.5 I flashed many zip intended for changing boot image but still the Boot image doesn't change.
Click to expand...
Click to collapse
Alright, make a clean wipe of your phone,everything. Now flash this firmware: https://sourceforge.net/projects/xi..._V9.6.2.0.NCFMIFD_88bb9b1f76_7.0.zip/download (all credits go to this site which is updated with the latest firmware :https://forum.xda-developers.com/re...lopment/firmware-xiaomi-redmi-note-4-t3760917)
Then flash the file below and tell me if it has changed which it should. If it worked keep the same firmware and go to this site(which i got the logo from,credits to them actually) https://forum.xda-developers.com/re...ow-to-change-boot-logo-splash-t3572441/page17
Search for something like this: name_new_firmware and download it or request one icon of your choice for your new firmware
Flash this via fastboot. Working for me on fw 9.6.2.0
I have this device rooted with magisk BUT cant find way to properly port a qualcomm twrp from similar devices i just need help to get started with custom recovery if i can get one to boot i might be able to fiqure out the rest if any "Bugs" are found thru out the custom recovery. any help would be appericated.
below is a stock image of recovery and boot if needed
both images were from a " .Tar " file. I then extracted the file and got the recovery and boot in " .img.lz4 " format and then i converted them to " .img " only for easy access to edit ETC.
Android Version : 10
Current Firmware Version : A115MUBU1ATC2
Chipset : msm8953
Encryption State : encrypted
#System as Root
Uses an A/B operating System
https://drive.google.com/drive/folders/1mYYqvNgAXAxmiBH8ZDmbnoKMma4CUR12?usp=sharing
Why not compile a matching TWRP by yourself?
Look inside here.
@ jwoegerbauer i can give a try but have no experiences when it comes to makin a custom recovery.
ᐯerified Developer said:
I have this device rooted with magisk BUT cant find way to properly port a qualcomm twrp from similar devices i just need help to get started with custom recovery if i can get one to boot i might be able to fiqure out the rest if any "Bugs" are found thru out the custom recovery. any help would be appericated.
below is a stock image of recovery and boot if needed
both images were from a " .Tar " file. I then extracted the file and got the recovery and boot in " .img.lz4 " format and then i converted them to " .img " only for easy access to edit ETC.
Android Version : 10
Current Firmware Version : A115MUBU1ATC2
Chipset : msm8953
Encryption State : encrypted
#System as Root
Uses an A/B operating System
https://drive.google.com/drive/folders/1mYYqvNgAXAxmiBH8ZDmbnoKMma4CUR12?usp=sharing
Click to expand...
Click to collapse
Yea, im also looking for a way to get some sort of custom recovery on the exact same device. My advice is (if you cant build your own version of twrp) to just wait for some devs to release something for it. The galaxy a11 is a very new device so we'll just have to wait it out.
Edit: So I followed a tutorial here (https://www.youtube.com/watch?time_continue=40&v=MyxGZbCuxDQ&feature=emb_logo) and i created this (https://filebin.net/u3yww2cyajktm043). IT MAY OR MAY NOT WORK!!! USE IT AT YOUR OWN RISK!!!!
what model number is yours? i have the one from boost its the sm-a115u and it seems the toggle for oem unlock is not in my dev settings on my phone
ninjakira said:
what model number is yours? i have the one from boost its the sm-a115u and it seems the toggle for oem unlock is not in my dev settings on my phone
Click to expand...
Click to collapse
You can put the device into download mode and unlock the bootloader from there...
I'm currently stuck on this device trying to get it to unlock the boot loader. I've ticked OEM unlock but when I get into download mode (adb reboot download) I'm not getting any option to unlock the boot loader there. I'm also not able to get into download mode with any key commands. Any ideas here?
I've heard you power off, then hold volume up and down when you plug in a data cable. Haven't tried it yet, I'm on the a115u t-mobile variant. I can get to what it calls download mode, which looks to be fastboot and NOT the standard samsung blue screen download mode. Just boot to recovery and select reboot to bootloader. I do not have oem unlock in my dev settings, but I'll see if I can fastboot oem unlock when I get back to my laptop.
flash sm-a115u1 version firmware first. gives you oem unlock option. obviously toggle on and adb debugging. power off the phone. hold both volume buttons and insert usb cable. it will look like the normal blue download warning screen but read it carefully. it says long press volume up to unlock bootloader. it works. it will go black. release volume up and next it will ask you to confirm. choose yes. it will reboot and erase. after skipping thru set up enable dev options again and you will see oem toggle greyed out with a caption "bootloader already unlocked". thats as far as ive gotten. because now im like "what now?" i need a custom recovery file to flash to the device. any help with that out there? so now that the bootloader is unlocked can i install magisk to root and if so after that how can i network unlock? any help would be greatly appreciated. also looking for any custom roms that are available for this a11(2020). seems like a decent phone.thanks.
Situation:
You can build your TWRP it's very easy. Or get compiled version from A10 and patch your system.
As result you'll get a bootloop.
Why?
Samsung had f****d you up and give you a SECURE BOOT that's not possible to remove by bootloader unlock. If you're install wrong signed recovery loader will said to you:
1st something is going wrong and signatures are mismatched, lete wipe your phone!
Ok. You jad solved that and not wiped your phone.
2nd hmm, signatures still mismatched I'll not boot and go in ***!
Result:
Untill someone will not break this Qualcomm Secure Boot you'll not able to install custom OS or TWRP or any other good stuff.
Is there any updates that can be flashed with stock recovery
griha41 said:
Situation:
You can build your TWRP it's very easy. Or get compiled version from A10 and patch your system.
As result you'll get a bootloop.
Why?
Samsung had f****d you up and give you a SECURE BOOT that's not possible to remove by bootloader unlock. If you're install wrong signed recovery loader will said to you:
1st something is going wrong and signatures are mismatched, lete wipe your phone!
Ok. You jad solved that and not wiped your phone.
2nd hmm, signatures still mismatched I'll not boot and go in ***!
Result:
Untill someone will not break this Qualcomm Secure Boot you'll not able to install custom OS or TWRP or any other good stuff.
Click to expand...
Click to collapse
my a115u is stuck on load screen ,,after flash root trying to get bit un stuck ?????
ugg frustrating
sdell said:
my a115u is stuck on load screen ,,after flash root trying to get bit un stuck ?????
ugg frustrating
Click to expand...
Click to collapse
What's a point? Unpack firmware's AP_ file, extract boot.img, patch it through magisk, and flash through odin. But where in that thread header did you found the install root?
I want to remind you that recovery is bot a root part. That's why root thread and TWRP threads are separated.
griha41 said:
What's a point? Unpack firmware's AP_ file, extract boot.img, patch it through magisk, and flash through odin. But where in that thread header did you found the install root?
I want to remind you that recovery is bot a root part. That's why root thread and TWRP threads are separated.
Click to expand...
Click to collapse
cause i was new ..lol didnt know ..and still trying to understand it all but thqnk you for reply
sdell said:
cause i was new ..lol didnt know ..and still trying to understand it all but thqnk you for reply
Click to expand...
Click to collapse
Ahh I see. Sorry then.
You shall do that way. Find current fiware for your device, download it through fine software.
A result you will get 5 files with .zip extension.
You need to unpack file with AP_ prefix, i suggest you to use 7zip for that stuff. From file you need took off the boot.img.
Then boot.img you shall pack into archive.tar,
When you've done, down load the Magisk apk from github and install on your phone. Move your jew archive to phone memory/diwnload folder and start the Magisk, make patching of kenel, as result you'll receive the magisk_patched.tar, copy that file to your pc and start the Odin, place that archive in AP slot and flash it.
PROFIT!
But I want to warn you in android 10 and up there root and kernel system are different, now system is booting from super.img, and partition /,/system and etc are RO, so through the root you'll not able to change anything in system it would be wiped on next system restart.