Related
For starters, I have an AT&T HTC M9. I unlocked the bootloader, and after a while, got TWRP 3.0.2.0 installed as the custom recovery. I decided to flash ARHD, since that's my personal favorite that I've used on my M7 and M8. After flashing and clearing cache, the phone optimizes apps, reboots, and then stays at the HTC screen for a bit. Finally, the screen will turn off as if it's booted in. I could then wake the device and adjust volume and such, but I still had the HTC logo covering what would be the UI. After a bit more time, the setup menu finally came up. I couldn't set up wifi, as it got stuck on the "connecting" screen. Wiped, re-flashed ARHD. Same thing. Finally got through the setup, and I had no service. What am I doing wrong? Do I need to install a corresponding firmware or something? This happens to me every time. Also the M9 had Android 6.0 with Sense 7.0, for the record.
Have you made sure that the rom is compatible with your phones firmware?.
Beamed in by telepathy.
shivadow said:
Have you made sure that the rom is compatible with your phones firmware?.
Beamed in by telepathy.
Click to expand...
Click to collapse
The thread says it's built off of 3.35.401.12, and my phone is running 3.38.502.12. The thread goes on to say "- If your current firmware version doesn't match ROM firmware version, wiping data inside AROMA is highly recommended!" so I figured if I wiped the data inside AROMA it would still work. Am I just dumb?
manlavi95 said:
The thread says it's built off of 3.35.401.12, and my phone is running 3.38.502.12. The thread goes on to say "- If your current firmware version doesn't match ROM firmware version, wiping data inside AROMA is highly recommended!" so I figured if I wiped the data inside AROMA it would still work. Am I just dumb?
Click to expand...
Click to collapse
Please read the FAQ section of the Readme thread which is pinned above the normal questions here in the Q&A section. There you'll find the reason and the solution for the no service problem.
Sent from my HTC One M9 using XDA Labs
Flippy498 said:
Please read the FAQ section of the Readme thread which is pinned above the normal questions here in the Q&A section. There you'll find the reason and the solution for the no service problem.
Sent from my HTC One M9 using XDA Labs
Click to expand...
Click to collapse
"For Sense-based roms you just need to re-flash the stock boot image of your current firmware version." I'm now at a loss. I am in way over my head right now. So technically speaking, I'd be able to get ARHD to run on my ATT M9? That quoted sentence gave me an anxiety attack.
Edit: I've got an RUU that I was thinking of using and then just rooting the stock ROM and then going about my day. I'd be ok with that if I knew for a fact that it wouldn't remove TWRP. That and I was looking forward to the ARHD battery life.
manlavi95 said:
"For Sense-based roms you just need to re-flash the stock boot image of your current firmware version." I'm now at a loss. I am in way over my head right now. So technically speaking, I'd be able to get ARHD to run on my ATT M9? That quoted sentence gave me an anxiety attack.
Click to expand...
Click to collapse
Keep calm. All you need to do is downloading the RUU for your current firmware and the decryption tool that is linked in my thread. Drag'n'drop the RUU onto the *.exe file of the tool and wait some minutes. When it's finished it will give you an output folder. Inside you'll find a firmware folder and inside that one you'll find the needed boot image. All you need to do then is booting your phone to download mode and connecting it via USB with your pc. Copy the boot.img into your adb/fastboot folder and use
Code:
fastboot flash boot <enter name of the boot image - including its file extension - here and delete the less/greater symbols>
E.g. if the file is named boot_signed.img the command would be
Code:
fastboot flash boot boot_signed.img
The next time you boot your rom everything should be working, fine.
Edit: Your edit didn't exist when I wrote this post... The RUU will remove TWRP if you flash it. RUUs always reflash the whole phone (in other words: the system and the firmware).
Flippy498 said:
Keep calm. All you need to do is downloading the RUU for your current firmware and the decryption tool that is linked in my thread. Drag'n'drop the RUU onto the *.exe file of the tool and wait some minutes. When it's finished it will give you an output folder. Inside you'll find a firmware folder and inside that one you'll find the needed boot image. All you need to do then is booting your phone to download mode and connecting it via USB with your pc. Copy the boot.img into your adb/fastboot folder and use
Code:
fastboot flash boot <enter name of the boot image - including its file extension - here and delete the less/greater symbols>
E.g. if the file is named boot_signed.img the command would be
Code:
fastboot flash boot boot_signed.img
The next time you boot your rom everything should be working, fine.
Edit: Your edit didn't exist when I wrote this post... The RUU will remove TWRP if you flash it. RUUs always reflash the whole phone (in other words: the system and the firmware).
Click to expand...
Click to collapse
It appears that I may have given some misinformation. Looking in the ROM that I had flashed (Official Build ATT 3.38.502.12 ROM 7-12-2016), the firmware appears as (obviously) 3.38.502.12. However, looking in download mode, OS appears to actually be 3.38.502.41. Are the instructions you gave me still pertinent, or do I need to try something else?
manlavi95 said:
It appears that I may have given some misinformation. Looking in the ROM that I had flashed (Official Build ATT 3.38.502.12 ROM 7-12-2016), the firmware appears as (obviously) 3.38.502.12. However, looking in download mode, OS appears to actually be 3.38.502.41. Are the instructions you gave me still pertinent, or do I need to try something else?
Click to expand...
Click to collapse
In that case you will need the boot image of firmware 3.38.502.41. The correct firmware version of your phone is stated in the download mode. You're lucky since HTC released a RUU for that firmware, as well.
There are two main problems with HTCs website:
a) They only provide RUUs for their US customers. So be happy that you bought a US varaint of the M9.
b) They don't update their website that regularly although the files are already available. Since the URL isn't that complicated you can simply guess the correct one for newer RUUs.
Flippy498 said:
In that case you will need the boot image of firmware 3.38.502.41. The correct firmware version of your phone is stated in the download mode. You're lucky since HTC released a RUU for that firmware, as well.
There are two main problems with HTCs website:
a) They only provide RUUs for their US customers. So be happy that you bought a US varaint of the M9.
b) They don't update their website that regularly although the files are already available. Since the URL isn't that complicated you can simply guess the correct one for newer RUUs.
Click to expand...
Click to collapse
Done deal. So after flashing ARHD and then re-flashing the boot image, I can happily go on my way with a nifty AT&T M9 with ARHD?
manlavi95 said:
Done deal. So after flashing ARHD and then re-flashing the boot image, I can happily go on my way with a nifty AT&T M9 with ARHD?
Click to expand...
Click to collapse
Based on my previous experiences with the M9 I'd say yes.
Flippy498 said:
Based on my previous experiences with the M9 I'd say yes.
Click to expand...
Click to collapse
Thank you for preventing me from dying today. I'll see what I can do. Also, I was sitting here, looking at the HTC site, and I found all the ROMs, but for the life of me could not find the right one. That was when I noticed you had linked it to me. Now I'm actually wondering where you're finding these.
manlavi95 said:
Thank you for preventing me from dying today. I'll see what I can do. Also, I was sitting here, looking at the HTC site, and I found all the ROMs, but for the life of me could not find the right one. That was when I noticed you had linked it to me. Now I'm actually wondering where you're finding these.
Click to expand...
Click to collapse
On their website. Take a look at the URL of the download for the older 3.38.502.12 RUU you can find there, then take a look at your current firmware. If you now look at the link for the latest RUU I posted you'll understand how I guessed the correct link. It's no magic.
Flippy498 said:
On their website. Take a look at the URL of the download for the older 3.38.502.12 RUU you can find there, then take a look at your current firmware. If you now look at the link for the latest RUU I posted you'll understand how I guessed the correct link. It's no magic.
Click to expand...
Click to collapse
Ok, so I flashed the ROM, (ARHD 20.0, 6.0, Sense 7.0) and then flashed the boot. Phone boots up fine, I now have signal and data, but there is one issue. I have no wifi. Is this...radio-related?
Another edit: I also don't see SuperSU anywhere, and that's confusing me just a bit.
manlavi95 said:
Ok, so I flashed the ROM, (ARHD 20.0, 6.0, Sense 7.0) and then flashed the boot. Phone boots up fine, I now have signal and data, but there is one issue. I have no wifi. Is this...radio-related?
Click to expand...
Click to collapse
No, the radio/baseband doesn't deal with the WIFI reception. There are other parts of the firmware like the wcnss that are responsible for that. You may want to ask in the dedicated rom thread for further help. I haven't heard of such wifi problems before.
In regard to your edit: I never flashed ARHD. I can't even tell you whether it's using SuperSU or any other superuser app.
Flippy498 said:
No, the radio/baseband doesn't deal with the WIFI reception. There are other parts of the firmware like the wcnss that are responsible for that. You may want to ask in the dedicated rom thread for further help. I haven't heard of such wifi problems before.
In regard to your edit: I never flashed ARHD. I can't even tell you whether it's using SuperSU or any other superuser app.
Click to expand...
Click to collapse
Alrighty, so it appears support has ended for ARHD. I'll go ahead and ask in the thread anyway, but out of curiosity, I checked out Viper. Looks like that won't work with AT&T. I'll try out ICE maybe. I need more practice.
manlavi95 said:
Alrighty, so it appears support has ended for ARHD. I'll go ahead and ask in the thread anyway, but out of curiosity, I checked out Viper. Looks like that won't work with AT&T. I'll try out ICE maybe. I need more practice.
Click to expand...
Click to collapse
Well, you could use viper. You just need to choose default in the aroma installer. But I don't know whether your reception is supported out of the box or not. And since viper 5 is based on a HTC 10 port the boot image trick might not work, either. Viper 4 on the other hand should be working fine in case you need to reflash the boot image since it's based on the latest wwe M9 firmware.
Flippy498 said:
Well, you could use viper. You just need to choose default in the aroma installer. But I don't know whether your reception is supported out of the box or not. And since viper 5 is based on a HTC 10 port the boot image trick might not work, either. Viper 4 on the other hand should be working fine in case you need to reflash the boot image since it's based on the latest wwe M9 firmware.
Click to expand...
Click to collapse
Would you... recommend Viper by chance? I'm trying to weigh my options at this point.
manlavi95 said:
Would you... recommend Viper by chance? I'm trying to weigh my options at this point.
Click to expand...
Click to collapse
I guess my signature should be sufficent for answering that question.
(And yes, I do know that my firmware and the TWRP version I'm using are outdated. I didn't have the time nor the motiviation that would be needed for updating them. I'll probably just wait until HTC distributes android 7 for my SKU.)
Flippy498 said:
I guess my signature should be sufficent for answering that question.
(And yes, I do know that my firmware and the TWRP version I'm using are outdated. I didn't have the time nor the motiviation that would be needed for updating them. I'll probably just wait until HTC distributes android 7 for my SKU.)
Click to expand...
Click to collapse
I hope I'm not taking up too much of your personal time from asking such questions, as the thread's original question has been answered. I'm currently looking at how to install 5.3, because it looks like a wonderful ROM to have.
manlavi95 said:
I hope I'm not taking up too much of your personal time from asking such questions, as the thread's original question has been answered. I'm currently looking at how to install 5.3, because it looks like a wonderful ROM to have.
Click to expand...
Click to collapse
Flash it like any other rom. The aroma installer is actually pretty straight forward. Choose default since there is nor AT&T specific installation.
Just make sure that you read what it wants you to do. Sometimes it asks which apps you want to install and sometimes which you want to uninstall.
Here was a Guide. Someone said people don't care about Me or My Work so...
does it need unlock bl and will it break the drm？
lenchan139 said:
does it need unlock bl and will it break the drm？
Click to expand...
Click to collapse
Like i said on other Places before. DRMs will get lost after unlocking but only the Ones for the Display Colors, Xperia Services and Netflix 4K. They will get restored after locking and flashing a Firmware again and it's already handled Like that from SONY since the Xperia 1 & 5.
And Sure, You need to be unlocked to modify anything on a Android Device persistently.
Br
Would anyone please make a patched boot.img for XQ-AT52?
Attach the file link.
https://mega.nz/file/sVgj3IjT#bkWnWs8TQhwI-dp9mtXC5FLcNVxXD613qzTmblX_tnk
I installed Magisk Manager on a non-rooted Xperia 1 Ii and did the following, but the patched boot.img is not created.
Magisk Install-Install-Select and Patch a File
Select XQ-AT52 boot.img
got this message
-Device platform: arm64-v8a
-Processing tar file
--Writing: ./xbl_config_43.mbn
--Writing: ./tzxflattest_43.mbn
--Writing: ./xbl_43.mbn
--Writing: ./xfl_43.mbn
--Writing: ./qupfw_43.mbn
--Writing: ./aop_43.mbn
--Writing: ./cmnlib_43.mbn
--Writing: ./devcfg_43.mbn
--Writing: ./abl_43.mbn
--Writing: ./uefisecapp_43.mbn
--Writing: ./keymaster_43.mbn
--Writing: ./hyp_43.mbn
--Writing: ./tz_43.mbn
--Writing: ./cmnlib64_43.mbn
--Writing: ./tzxfl_43.mbn
! No boot image found
!Process error
!Installation failed
alphonsezero said:
Would anyone please make a patched boot.img for XQ-AT52?
Attach the file link.
https://mega.nz/file/sVgj3IjT#bkWnWs8TQhwI-dp9mtXC5FLcNVxXD613qzTmblX_tnk
I installed Magisk Manager on a non-rooted Xperia 1 Ii and did the following, but the patched boot.img is not created.
Magisk Install-Install-Select and Patch a File
Select XQ-AT52 boot.img
got this message
-Device platform: arm64-v8a
-Processing tar file
--Writing: ./xbl_config_43.mbn
--Writing: ./tzxflattest_43.mbn
--Writing: ./xbl_43.mbn
--Writing: ./xfl_43.mbn
--Writing: ./qupfw_43.mbn
--Writing: ./aop_43.mbn
--Writing: ./cmnlib_43.mbn
--Writing: ./devcfg_43.mbn
--Writing: ./abl_43.mbn
--Writing: ./uefisecapp_43.mbn
--Writing: ./keymaster_43.mbn
--Writing: ./hyp_43.mbn
--Writing: ./tz_43.mbn
--Writing: ./cmnlib64_43.mbn
--Writing: ./tzxfl_43.mbn
! No boot image found
!Process error
!Installation failed
Click to expand...
Click to collapse
You can use this Old version of Canary Magisk to make a patched boot.img straight from the boot.sin file:
https://drive.google.com/file/d/10xY6I2tmeq0TXy7Oe0FRxEOkBZ1ASB3y/view?usp=drivesdk
Then use this Canary Magisk to update the boot.img to the latest version :
https://drive.google.com/file/d/116Nk7xgUl1Idz0JYLfmGxRnnJHbRFdo5/view?usp=drivesdk
Need any help with anything or if you keep failing just upload and send us your boot.sin file ??
Edit: I just noticed your link, your using the wrong file you need the boot one (boot_X-FLASH-ALL-2389) it's not inside the boot folder it's in the root directory, I would've downloaded it for you but I'm not sure which region you need.
Thanks to you, we were able to root the XQ-AT52.
Question, is it possible to modify the system files?
please tell me.
Miustone said:
Like i said on other Places before. DRMs will get lost after unlocking but only the Ones for the Display Colors, Xperia Services and Netflix 4K. They will get restored after locking and flashing a Firmware again and it's already handled Like that from SONY since the Xperia 1 & 5.
And Sure, You need to be unlocked to modify anything on a Android Device persistently.
Br
Click to expand...
Click to collapse
Are you sure that it is possible to relock the bootloader? This ia not possible for Xperia 10.
tobos said:
Thanks to you, we were able to root the XQ-AT52.
Question, is it possible to modify the system files?
please tell me.
Click to expand...
Click to collapse
The Xperias are using System-as-root so no TWRP but You can do it with Magisk like i do with My MARS_SOM Systemlessly. OR You can make own GSIs based on Stock or AOSP...
chortya said:
Are you sure that it is possible to relock the bootloader? This ia not possible for Xperia 10.
Click to expand...
Click to collapse
YES, I also heard even the Xperia 10 and 10 Plus can do that but they are no Flagships and May don't even have Special DRMs. I never touched the Firmwares of them but possible that they got that Option with Android 10 Updates...
system mont
Sorry for the repeated occurrences.
When I run the adb command, everything is disabled.
Can you give me the detailed steps to mount the system?
wrong magisk image xperia 1 II
Miustone said:
This Guide includes the Kernel for the EU Models of the XPERIA 1, 5 and 1 MARK 2. If You have another Model, please get Your own Kernel like explained on the bottom of this Post.
-Turn Off Your Device
-Hold Volume Up (Louder) while connecting to USB
-Do You see the Blue LED on Your Device? If Yes are You in Fastboot Mode!
-Download the Boot Image for Your Device from HERE and place it into Your fastboot Folder
-Use fastboot with this commands:
Code:
fastboot flash boot_a magisk_patched.img
fastboot flash boot_b magisk_patched.img
fastboot reboot
DIY - How to get Your own Kernel / Boot Image:
Download XperiFirm from XDA
Download UnSin from XDA
Download a Firmware with XperiFirm
Extract the File boot_X-FLASH-ALL*** with Unsin (By drag and drop)
You will get a .img File which You can patch with Magisk Manager
If i helped You, leave a Thanks <3
Click to expand...
Click to collapse
Man , your file corupted my phone....shame to you..
daphix said:
Man , your file corupted my phone....shame to you..
Click to expand...
Click to collapse
Thanks for the additional Infos like what Model You have. Is it the Single SIM one (EU?)? An Xperia Z or a Galaxy S2? What have You done? Which Firmware are You on? Don't blame Me for My Work, blame You for not giving even a Single info, No one can Help You Like this....
Miustone said:
Thanks for the additional Infos like what Model You have. Is it the Single SIM one (EU?)? An Xperia Z or a Galaxy S2? What have You done? Which Firmware are You on? Don't blame Me for My Work, blame You for not giving even a Single info, No one can Help You Like this....
Click to expand...
Click to collapse
i think in this general root topic you provided wrong files from another image, for your rom, marsom, who is in another section;
that's why was bricked, sorry for telling you all of this; here you have to tell clearly what image you used as source for magisk;
your work is good, but the details in this post are limited for simple users like me;
my version is single sim EU; XQ-AT51; 58.0.A.3.39; customized EU 1321-7706 R13A;
i suceed to repair, after digging on more sites, but i have to recognize that one of your instructions from other post also helped me ; by extracting the File boot_X-FLASH-ALL-2389.sin from ftf image (downloaded previously with flashtool) with Unsin and converting into img and flashing back;
Have attentions, your magisk boot image (link to drive) from this topic are wrong, even as file size.
Also your refference to the command of flashing 2 partitions is wrong, is not applicable (simple rooting of Xperia 1 II EU single Sim version, in my case); you need only one:
fastboot flash boot magisk_patched.img
I reacted because this lack of information and confusion is spread all over the topics, and even a little mistake conduct to risk of bricking the phones;
the people who post solutions, images, should be aware - here is not instagram, is not beauty contest.
daphix said:
i think in this general root topic you provided wrong files from another image, for your rom, marsom, who is in another section;
that's why was bricked, sorry for telling you all of this; here you have to tell clearly what image you used as source for magisk;
your work is good, but the details in this post are limited for simple users like me;
my version is single sim EU; XQ-AT51; 58.0.A.3.39; customized EU 1321-7706 R13A;
Click to expand...
Click to collapse
Don't flash things randomly if you don't know how they work. The DIY section also describes pretty well the simple steps you need to do. Which would've saved you from this entire situation.
daphix said:
Have attentions, your magisk boot image (link to drive) from this topic are wrong, even as file size.
Also your refference to the command of flashing 2 partitions is wrong, is not applicable (simple rooting of Xperia 1 II EU single Sim version, in my case); you need only one:
fastboot flash boot magisk_patched.img
Click to expand...
Click to collapse
Learn how A/B partitions work to realize why you need to flash both partitions.
daphix said:
I reacted because this lack of information and confusion is spread all over the topics, and even a little mistake conduct to risk of bricking the phones;
the people who post solutions, images, should be aware - here is not instagram, is not beauty contest.
Click to expand...
Click to collapse
Again, don't mod your phone if you don't have the knowledge of basic workings of Android. Flashing a bad boot image won't brick your phone, and as you have discovered is recoverable. There is no reason to overreact. You merely flashed a boot image for a different firmware.
Winrahr said:
Don't flash things randomly if you don't know how they work. The DIY section also describes pretty well the simple steps you need to do. Which would've saved you from this entire situation.
Learn how A/B partitions work to realize why you need to flash both partitions.
Again, don't mod your phone if you don't have the knowledge of basic workings of Android. Flashing a bad boot image won't brick your phone, and as you have discovered is recoverable. There is no reason to overreact. You merely flashed a boot image for a different firmware.
Click to expand...
Click to collapse
Thanks for Your Reply! Couldn't say it any better... :highfive:
To be honest: "This Guide includes the Kernel for the EU Models of the XPERIA 1, 5 and 1 MARK 2. If You have another Model, please get Your own Kernel like explained on the bottom of this Post."
This is the first Sentence of this Thread. What People can blame Me for is that i don't tell the Model Numbers i got the Images from, but if You take a look on XperiFirm... There is only one EU Model of each Xperia (Except the 2019 Xperias but that would be EU3 in this case instead of EU and is still Dual SIM). Besides that are all Images just fine. The Image Sizes are based on Magisk and is different (smaller) as the OG Image, totally normal so far...
"Don't flash things randomly" Is the smartest Thing to say. I would clearly ask on the Thread if I'm not sure what i do. I just have made many Threads this Year and i need to maintain all of them besides doing Overlays, My Website, MARS, Images and all that. Sorry if not everything is always that good described, but at the End is the Work important, not the Threads with Cool Pics/Banners and fancy Words. We are not on Instagram nor on a Beauty Contest (already said). But i'm always open for critics if it is constructive... In this case, i will just add Model Numbers to the Threads to avoid confusion of People who never touched XperiFirm before.
Thanks again and best Regards!
Winrahr said:
Don't flash things randomly if you don't know how they work. The DIY section also describes pretty well the simple steps you need to do. Which would've saved you from this entire situation.
Click to expand...
Click to collapse
@Winrahr: look at the title of topic: Xperia 1 II root guide; not flashed randomly, i falshed for XQ-AT51, as the author named in his post; but his image is wrong;
You try now to escuse your friend saying that is general topic; it is not, it is reffering dedicated models;
if he post a rooting guide, should be clear, indicating the source of image; or better without reffering any image, if he want only to stay on general flashing instructions.
Winrahr said:
Learn how A/B partitions work to realize why you need to flash both partitions.
Click to expand...
Click to collapse
@Winrahr: Really? so this topic is a school, how to root any phone? Even In this case beign general instructions, as you try to escuse him now, are a totally mess; moreover he are indicating: "flash this images, from this drive location"; they are clearly named by author in written : xperia 1 mark 2, XQ-AT51; it was my mistake to download them thinking that i have to do with professionals;
Winrahr said:
Again, don't mod your phone if you don't have the knowledge of basic workings of Android. Flashing a bad boot image won't brick your phone, and as you have discovered is recoverable. There is no reason to overreact. You merely flashed a boot image for a different firmware.
Click to expand...
Click to collapse
@Winrahr: I repaired myself the phone after bricking due his instructions; The errors belong to author, who indicated: "flash there from this drive image, is for xperia 1 mark 2", XQ-AT51; but the boot image source is wrong; he linked to another moded image, this i discovered later; he posted in this general topic the firmware for another modded rom, marsom, who is in another section;
What he posted here is far ayaw of the basics, is kindergarden; better avoid to post; when adress a topic, should be clear & complete; not by posting wrong file image and wrong flashing instructions.
Not try to escuse him by weak argumention as he wanted to present generalities, even those are incomplete.
Contrary of what is expected from a advanced user, he provided only wrong information and confusion;
---------- Post added at 07:31 AM ---------- Previous post was at 07:09 AM ----------
Miustone said:
Thanks for Your Reply! Couldn't say it any better... :highfive:
To be honest: "This Guide includes the Kernel for the EU Models of the XPERIA 1, 5 and 1 MARK 2. If You have another Model, please get Your own Kernel like explained on the bottom of this Post."
This is the first Sentence of this Thread. What People can blame Me for is that i don't tell the Model Numbers i got the Images from, but if You take a look on XperiFirm... There is only one EU Model of each Xperia (Except the 2019 Xperias but that would be EU3 in this case instead of EU and is still Dual SIM). Besides that are all Images just fine. The Image Sizes are based on Magisk and is different (smaller) as the OG Image, totally normal so far...
"Don't flash things randomly" Is the smartest Thing to say. I would clearly ask on the Thread if I'm not sure what i do. I just have made many Threads this Year and i need to maintain all of them besides doing Overlays, My Website, MARS, Images and all that. Sorry if not everything is always that good described, but at the End is the Work important, not the Threads with Cool Pics/Banners and fancy Words. We are not on Instagram nor on a Beauty Contest (already said). But i'm always open for critics if it is constructive... In this case, i will just add Model Numbers to the Threads to avoid confusion of People who never touched XperiFirm before.
Thanks again and best Regards!
Click to expand...
Click to collapse
@Miustone: I don't blame you, but for you would be better not to justify, you should recognize and be a Man. You have another topic , when you present your moded rom; this topic is a general one, and you simply pasted the wrong link to your moded rom, this i discovered after bricking the phone.
Another mistake you did is that you posted wrong instructions, of flashing two boot partitions, instead of one.
Now you try to be escused by weak arguments of that you wanted to present generalities, even those beign inclomplete. Maybe you had good intentions but (possible due speed), you pasted wrong link to modded image, not to the rooted one; or you not have own rooted image of XQ- AT51; aslo you continue errors by posting wrong instructions of flashing two partitions instead one;
You try now to justify yourself, but what's your point? What are the meaning of your post, of "general instructions" if is incomplete, non-aplicable to this topic and generating problems?
When you adress a topic, you should be clear & complete; not by posting wrong file image and wrong flashing instructions, in a specific , named phone thread.
Don't continue to defend yourself, maybe you have knowledge, but you posted in hurry, with lack of informations, full of confusions.
Sorry for others readers, i written too much just to highlight this lesson learned: pay attentions to those called "experts" who try to use this forum as a place for beauty contest.
---------- Post added at 08:07 AM ---------- Previous post was at 07:31 AM ----------
Miustone said:
This Guide includes the Kernel for the EU Models of the XPERIA 1, 5 and 1 MARK 2. If You have another Model, please get Your own Kernel like explained on the bottom of this Post.
-Turn Off Your Device or reboot to fastboot from ADB
-Hold Volume Up (Louder) while connecting to USB if Your Device is Off
-Do You see the Blue LED on Your Device? If so, are You in Fastboot Mode!
-Download the Boot Image for Your Device from HERE and place it into Your fastboot Folder
-Use fastboot with this commands for Treble A/B Devices:
Code:
fastboot flash boot_a magisk_patched.img
fastboot flash boot_b magisk_patched.img
fastboot continue
Done. You will be rooted now, just install the Magisk Manager and enjoy! The Provided Images are from the J9110, J9210 and XQ-AT51...
DIY - How to get Your own Kernel / Boot Image:
Download XperiFirm from XDA
Download UnSin from XDA
Download a Firmware with XperiFirm
Extract the File boot_X-FLASH-ALL*** with Unsin (By drag and drop)
You will get a .img File which You can patch with Magisk Manager
If i helped You, leave a Thanks <3
Click to expand...
Click to collapse
Sorry to tell this, advice for another readers: the provided image is wrong, is not for XQ-AT51, have different size, better build your own using Magisk - check other posts to learn how to do this; also not need to flash two boot partitions, is enough one: fastboot flash boot magisk_patched.img
I still don't get what your big rant about beauty contests is about but I have to reply because you are giving incorrect information.
daphix said:
look at the title of topic: Xperia 1 II root guide; not flashed randomly, i falshed for XQ-AT51, as the author named in his post; but his image is wrong;
You try now to escuse your friend saying that is general topic; it is not, it is reffering dedicated models;
if he post a rooting guide, should be clear, indicating the source of image; or better without reffering any image, if he want only to stay on general flashing instructions.
Click to expand...
Click to collapse
I don't know the guy. I can't comment on whether his image was correct or not because I never used the image.
daphix said:
Really? so this topic is a school, how to root any phone? Even In this case beign general instructions, as you try to escuse him now, are a totally mess; moreover he are indicating: "flash this images, from this drive location"; they are clearly named by author in written : xperia 1 mark 2, XQ-AT51; it was my mistake to download them thinking that i have to do with professionals;
Click to expand...
Click to collapse
I don't know what you're trying to say here. I was telling you to go read up on it to realize why your statement was wrong. On an A/B device such as the Xperia 1 II, you should flash both _a and _b partitions to save yourself the hassle of wondering why your phone wont boot when it switches to slot B and you only flashed slot A, and you'll come back crying about how the instructions are wrong and we aren't professionals and this isn't a beauty contest. Which by the way, we aren't professionals, we are hobbyists. So your assumption led to your own demise.
daphix said:
I repaired myself the phone after bricking due his instructions; The errors belong to author, who indicated: "flash there from this drive image, is for xperia 1 mark 2", XQ-AT51; but the boot image source is wrong; he linked to another moded image, this i discovered later; he posted in this general topic the firmware for another modded rom, marsom, who is in another section;
What he posted here is far ayaw of the basics, is kindergarden; better avoid to post; when adress a topic, should be clear & complete; not by posting wrong file image and wrong flashing instructions.
Not try to escuse him by weak argumention as he wanted to present generalities, even those are incomplete.
Contrary of what is expected from a advanced user, he provided only wrong information and confusion;
Click to expand...
Click to collapse
I laughed at this part because I had no idea what it meant but it was funny.
daphix said:
[rant removed for brevity]
Now you try to be escused by weak arguments of that you wanted to present generalities, even those beign inclomplete. Maybe you had good intentions but (possible due speed), you pasted wrong link to modded image, not to the rooted one; or you not have own rooted image of XQ- AT51; aslo you continue errors by posting wrong instructions of flashing two partitions instead one;
Click to expand...
Click to collapse
I don't have an issue with you ranting with all of this. But I have to stop you here because you are complaining about wrong info that could cause damage to other users, when you yourself are posting wrong and dangerous information. Your anecdotal evidence is not enough to claim someone's instructions wrong.
daphix said:
Sorry for others readers, i written too much just to highlight this lesson learned: pay attentions to those called "experts" who try to use this forum as a place for beauty contest.
Click to expand...
Click to collapse
Yes you have written too much. This is not a beauty contest. You are not an expert. Please stop.
daphix said:
Sorry to tell this, advice for another readers: the provided image is wrong, is not for XQ-AT51, have different size, better build your own using Magisk - check other posts to learn how to do this; also not need to flash two boot partitions, is enough one: fastboot flash boot magisk_patched.img
Click to expand...
Click to collapse
I don't have comments on if the provided image is correct or not, but the instructions to building your own is literally in the post that you have just quoted, you don't need to check other posts. But the issue I have with you is your adamant claim that you only need to flash the active partition.
Yes, you can get away by just flashing the active boot partition. But there is no reason to not flash both A and B partitions at the same time when you flash anything to guarantee that the partitions always match. Again, please learn how A/B partitions work to know why your advice can be dangerous.
Winrahr said:
I still don't get what your big rant about beauty contests is about but I have to reply because you are giving incorrect information.
I don't know the guy. I can't comment on whether his image was correct or not because I never used the image.
I don't know what you're trying to say here. I was telling you to go read up on it to realize why your statement was wrong. On an A/B device such as the Xperia 1 II, you should flash both _a and _b partitions to save yourself the hassle of wondering why your phone wont boot when it switches to slot B and you only flashed slot A, and you'll come back crying about how the instructions are wrong and we aren't professionals and this isn't a beauty contest. Which by the way, we aren't professionals, we are hobbyists. So your assumption led to your own demise.
I laughed at this part because I had no idea what it meant but it was funny.
I don't have an issue with you ranting with all of this. But I have to stop you here because you are complaining about wrong info that could cause damage to other users, when you yourself are posting wrong and dangerous information. Your anecdotal evidence is not enough to claim someone's instructions wrong.
Yes you have written too much. This is not a beauty contest. You are not an expert. Please stop.
I don't have comments on if the provided image is correct or not, but the instructions to building your own is literally in the post that you have just quoted, you don't need to check other posts. But the issue I have with you is your adamant claim that you only need to flash the active partition.
Yes, you can get away by just flashing the active boot partition. But there is no reason to not flash both A and B partitions at the same time when you flash anything to guarantee that the partitions always match. Again, please learn how A/B partitions work to know why your advice can be dangerous.
Click to expand...
Click to collapse
@Winrahr:
Thx for replying; my reply was not for you; you not have to reply in the name of author;
By other hand, in few lines you written more clear and complete than him; this prove my point, you are more experienced member than him. all my statements remains;
He not provided correct image and his instructions are incomplete; following his instructions help nobody to build a boot image, here you are wrong - he pointed out only how to upload a file, not how to generate one. This can be found on other threads.
You drop too many accuses against victim, stop laughing of regular users, otherwise you prove that you understand nothing. i just highlighted the risk of flashing images from so called experts;
Instead of fighting with me and defending so much in others name, better you provide a link to a good thread;
I pointed in my last reply that is enough to flash only one partition, if you know when is applicable.
You pointed well the differences of flashing 2 partitions, he misses even this. I bet that he did only a copy & paste from other sources.
Actual thread Is a simple one with few & incomplete instructions, my point is to avoid "fake experts"- well known people who only try to be first, by posting copy& paste from other sources, whitout understaning well what they do and the risk for others; for them only image it counts, quality of information being the last;
This people are called "cloners". Avoid them and reply when you find such cases.
If you give me advices, please allow me one for you: try yourself to be promoter of correct way to do the job, by structured & clear information and highlight the risk of posting wrong images & inaccurate info;
You should assume also to reply to such types of people and improve their posts, otherwise you are wrong if you post only against regular users.
daphix said:
-snip-
Click to expand...
Click to collapse
I don't care. Just don't tell people to only flash the active boot partition because that's wrong. Instructions in OP are fine. This will be my last reply.
Winrahr said:
I don't care. Just don't tell people to only flash the active boot partition because that's wrong. Instructions in OP are fine. This will be my last reply.
Click to expand...
Click to collapse
Check this, carefully;
"https://www.xda-developers.com/how-a-b-partitions-and-seamless-updates-affect-custom-development-on-xda/"
"https://www.droidwin.com/flash-roms-magisk-twrp-kernels-a-b-partition-devices/"
I never sayd to flash Active; i said that is not good to flash both partitions and author's instructions in first post are wrong;
Flashing one partition is less risky; A & B partion are existing for more reasons; one of them is to remain always a back-up in one partition for recovery; when you flash one partition and at restart OS found eventualy an error, Android will try to restore from other partition;
If you flash both partitions with a corupted boog image, you almost sure brick the phone, because will enter in bootloop, without chance to start the good image from back-up partition.
This was the case who generated all debate. And people who pose in experts by "hearing things" have to be avoided;
If you flash one partition, it remains the existing flashed to be used for recovery.
You not need to point out A or B when flash only one, will be written corectly because Android know what partition is active and what not, at the moment of flashing and it will flash corectly;
Check the articles.
Otherwise I almost thought that we'll become friends, you replied me more often than to your girlfriend
Cheers mate!
I also think that it is better to refresh only one partition, so that the fault tolerance rate will provide no direct bricking of the phone. I would like to ask friends, can this phone be used for third-party recovery? Do I need to backup TA before unlocking
I understand I can convert to EU.... However, I don't wish to do that. I just want to root my stock TMOBILE ROM.
My sim is unlocked and I have the unlock.bin from OnePlus for my phone. For anyone who has rooted TMOBILE stock ROM, which boot.img did you patch? I've read that AA boot image can work, but no firsthand accounts confirming this.
Ideally, I'd like to use my own boot.img but I can't find a tutorial or guide anywhere advising how to obtain my boot.img without root.
Thanks!
use AA boot img, but recommend unlocking Bootloader and backing up your tmo modem a/b imgs
How to guide
[TMO] 9 PRO MODEM RETENTION/DATA FIX
----- With the release of OOS13, the modem issue no longer exist. Thank you all for the support & help with this unfortunate issue, we had to endure.... ----- EXPLICITLY FOR TMOBILE 9 PRO (I'm not responsible for your failure to read or...
forum.xda-developers.com
Use partitions backup (app) to backup the existing TMO Firmware first and copy your files to a pc before you do anything. As with any flashing you run the risk of wiping your info and stored files..
galaxyuser88 said:
Use partition magic to backup the existing TMO Firmware first and copy your files to a pc before you do anything. As with any flashing you run the risk of wiping your info and stored files..
Click to expand...
Click to collapse
What is partition magic? An app? Software?
Pain-N-Panic said:
What is partition magic? An app? Software?
Click to expand...
Click to collapse
Sorry meant to say partitions backup. Which is an app.
Partitions Backup & Restore - Apps on Google Play
Backup your important partitions to avoid any data or IMEI corruption
play.google.com
Thank you... unfortunately partition backup requires root. So I can't back anything up until I unlock and root....which using the AA boot image to root kinda freaks me out
Pain-N-Panic said:
Thank you... unfortunately partition backup requires root. So I can't back anything up until I unlock and root....which using the AA boot image to root kinda freaks me out
Click to expand...
Click to collapse
It is understandable to be freaked out,. But if you follow the direction letter for letter then you should be fine.
Also good rule of thumb is make sure you have all the drivers and software loaded on your pc, then make sure your pc and phone can talk in adb and fastboot before you start to flash your phone.
I have rooted my stock tmo rom with aa and all good. Of course I went even further and installed the EU version on my tmo bought 9Pro..
galaxyuser88 said:
It is understandable to be freaked out,. But if you follow the direction letter for letter then you should be fine.
Also good rule of thumb is make sure you have all the drivers and software loaded on your pc, then make sure your pc and phone can talk in adb and fastboot before you start to flash your phone.
I have rooted my stock tmo rom with aa and all good. Of course I went even further and installed the EU version on my tmo bought 9Pro..
Click to expand...
Click to collapse
Yep, confirmed, 9pro and my computer can talk. The whole MSM thing is what is worrying me. In the MSM tool, it says it is the TMO -EU MSM. So, once it does it's thing and flashes it all, it should wipe the phone, it would be on the EU rom?
From there, I would need to follow the steps, unlock BL, flash modems, and then download oxygen updater to be able to locally download updates and install?
I think I understand the idea behind the device-specific Treble system, and the device-agnostic GIS images, which can work on any phone that has Treble. The app "Treble Check" says that the Sony Xperia 10 III is fully supported.
Here's my questions / educated guesses, please tell me if they're wrong or right:
1. This phone already comes with a Treble-compliant hardware layer (kernel+drivers) and GSI-compliant user-facing ROM, directly from Sony.
2. I can install any other GSI ROM (or from XDA) as long as it's an A/B arm64 ROM, and the hardware should work perfectly.
3. Can the phone still get OTA vendor updates for the hardware stuff after I unlock bootloader/install 3rd party GIS, or do I have to get the new images and flash them manually? Or do I get cut off from them altogether?
4. The original bootloader can take commands from the standard fastboot util in the Android SDK Platform Tools.
5. I understand I need to unlock the bootloader in order to be able to flash anything, but why is it necessary to overwrite the vbmeta partition?
6. Is the procedure to get Magisk working still patching the bootloader, regardless what GSI ROM I install?
7. Did anybody pass Safety Net with Magisk and a 3rd-party GIS ROM? Can it be passed anymore after unlocking bootloader?
8. I see there's no TWRP recovery for this device. Does it matter? Are there alternatives? In theory, if I have Magisk->root I can do pretty much anything so it doesn't sound like a big deal.
wirespot said:
1. This phone already comes with a Treble-compliant hardware layer (kernel+drivers) and GSI-compliant user-facing ROM, directly from Sony.
Click to expand...
Click to collapse
Yes.
wirespot said:
2. I can install any other GSI ROM (or from XDA) as long as it's an A/B arm64 ROM, and the hardware should work perfectly.
Click to expand...
Click to collapse
In theory. In practice it still depends on how the GSI ROM was implemented, there can still be issues.
wirespot said:
3. Can the phone still get OTA vendor updates for the hardware stuff after I unlock bootloader/install 3rd party GIS, or do I have to get the new images and flash them manually? Or do I get cut off from them altogether?
Click to expand...
Click to collapse
Not totally sure about this one. I think you don't get to install OTA updates anymore. You can probably download a new firmware with XperiFirm and flash pieces of it but no idea how that would work or what would happen.
wirespot said:
4. The original bootloader can take commands from the standard fastboot util in the Android SDK Platform Tools.
Click to expand...
Click to collapse
Yes. Sony did a great job going for standard things.
wirespot said:
5. I understand I need to unlock the bootloader in order to be able to flash anything, but why is it necessary to overwrite the vbmeta partition?
Click to expand...
Click to collapse
The original vbmeta partition contains a mechanism that checks for the other partitions to not be modified. The image downloaded from Google disables that mechanism, so you can put whatever you want on any partition.
wirespot said:
6. Is the procedure to get Magisk working still patching the bootloader, regardless what GSI ROM I install?
Click to expand...
Click to collapse
Yes, it's for the best. A large amount of what Magisk does is based on it being "hidden" from the regular system. Not just for hiding from SafetyNet, since you may not care about that with a 3rd party GSI ROM, but because keeping system modifications separate and keeping the original ROM is a very, very good practice.
wirespot said:
7. Did anybody pass Safety Net with Magisk and a 3rd-party GIS ROM? Can it be passed anymore after unlocking bootloader?
Click to expand...
Click to collapse
You can pass SafetyNet on the stock ROM, with unlocked bootloader and boot image patched to load Magisk. See my how to guide. I don't know about 3rd party GIS ROMs.
wirespot said:
8. I see there's no TWRP recovery for this device. Does it matter? Are there alternatives? In theory, if I have Magisk->root I can do pretty much anything so it doesn't sound like a big deal.
Click to expand...
Click to collapse
I've looked into this some more. The biggest downsides seem to be inability to restore backups of the userdata, and inability to disable problematic Magisk modules. There are modules such as Magisk Bootloop Protector which will disable all modules if it detects a bootloop, but if the problem is not a bootloop and still prevents your access you're out of luck...
Please feel free to add more info.
Hello community, I need some explanation first if my approach is incorrect. I am trying to downgrade to Android 10, but i was soul-crashed after reading some information about the bit/binary value that samsung uses on its firmware(basically you cant downgrade if this value is not equal to your targeted frimware). However even though i feel scammed by Samsung, i would like to ask you the community as my final resort to guide me.
Is there some way i can trick SW REV checker or delete this partition containing this binary file?. Does "deleting" it affect my ability to boot into the download mode?
{Temp_User} said:
Hello community, I need some explanation first if my approach is incorrect. I am trying to downgrade to Android 10, but i was soul-crashed after reading some information about the bit/binary value that samsung uses on its firmware(basically you cant downgrade if this value is not equal to your targeted frimware). However even though i feel scammed by Samsung, i would like to ask you the community as my final resort to guide me.
Is there some way i can trick SW REV checker or delete this partition containing this binary file?. Does "deleting" it affect my ability to boot into the download mode?
Click to expand...
Click to collapse
you can downgrade by simply flashing system,kernel and vendor from android 10 on twrp
JuanTamqd21 said:
you can downgrade by simply flashing system,kernel and vendor from android 10 on twrp
Click to expand...
Click to collapse
Hi, thank you for the reply.
Sorry for the late reply. I will try this today
JuanTamqd21 said:
you can downgrade by simply flashing system,kernel and vendor from android 10 on twrp
Click to expand...
Click to collapse
Okay. I am may be misunderstanding something because this way did not work for me. Do I have to manually extract files from the lz4 files?
{Temp_User} said:
Okay. I am may be misunderstanding something because this way did not work for me. Do I have to manually extract files from the lz4 files?
Click to expand...
Click to collapse
well, I can provide vendor and kernel in telegram. You can also get them by extracting lz4 files
make sure its from Android 10/Q/one ui 2.x firmware
I have with me the latest (previous) android 10 . I have extracted correctly ( used 7-zip zstd ) the lz4 files and flashed the vendor, system and kernel in that order.
upon reboot, I can not get past the splash screen. However i do see that an error appears on top left of my screen as CHECK FAIL binary 7(BOOT). The words are not clear though.
What did i do wrong?
JuanTamqd21 said:
well, I can provide vendor and kernel in telegram. You can also get them by extracting lz4 files
make sure its from Android 10/Q/one ui 2.x firmware
Click to expand...
Click to collapse
please provide an in-depth process?
Okay, so after a number of attempts i finally have android 10/Q on my phone. Keep in mind that i am not tech savvy, as all this was a guessing game(well not all of it)
I will share my story and hope it may be useful to others who intend to downgrade their android version.
SW REV ERRORSYou cannot and you should not change the bit version. If you see this error, it means you tried to flash a firmware or maybe just a boot file that is outdated or incompatible with the current secure boot loader.
With my limited knowledge, I went with what was easier for me at the time of writing this,
Flash latest firmware for model A505F,(yours may differ) using Odin.(SUCCESS)Boot into system normally.(make sure the OEM unlock is greyed out.Flash the latest custom recovery(TWRP or 'sky hawk recovery project', I chose the latter. )Boot into your recovery and Format data., also make advanced wipes. System kernel vendor Dalvik Cache Data.Pay attention to what exactly you are wiping.With your targeted firmware (A10) somewhere nearby, I recommend to use a reliable tool to extract the lz4 compressed file. I used this to get 'system.img' 'vendor.img' 'boot.img' . If you are on windows, look at the type column in your file explorer or enable 'view filename extension'.Flash/Install the image files in your recovery. Be patient.
Here is the tricky part for me. the boot loader wont accept this older kernel.(thus the boot loops).
A faster way to work around this, is installing a custom kernel that supports android 10. e.g. quantum kernel.
You may have to reboot a number of times before you can get past the splash screen. Be patient.Success, you now have a weird but working system. (I call it weird because the kernel you will use will carry along with its bugs e.g. camera fails, random reboots.)You can not update the system. this may be due to the different AP/CP/CSC/ match. This is not a step by step guide, i am only sharing with the public what i did to get my final point.
Of course this goes without saying that you are attempting a risky route and you the user shall carry all responsibility.
{Temp_User} said:
Okay, so after a number of attempts i finally have android 10/Q on my phone. Keep in mind that i am not tech savvy, as all this was a guessing game(well not all of it)
I will share my story and hope it may be useful to others who intend to downgrade their android version.
SW REV ERRORSYou cannot and you should not change the bit version. If you see this error, it means you tried to flash a firmware or maybe just a boot file that is outdated or incompatible with the current secure boot loader.
With my limited knowledge, I went with what was easier for me at the time of writing this,
Flash latest firmware for model A505F,(yours may differ) using Odin.(SUCCESS)Boot into system normally.(make sure the OEM unlock is greyed out.Flash the latest custom recovery(TWRP or 'sky hawk recovery project', I chose the latter. )Boot into your recovery and Format data., also make advanced wipes. System kernel vendor Dalvik Cache Data.Pay attention to what exactly you are wiping.With your targeted firmware (A10) somewhere nearby, I recommend to use a reliable tool to extract the lz4 compressed file. I used this to get 'system.img' 'vendor.img' 'boot.img' . If you are on windows, look at the type column in your file explorer or enable 'view filename extension'.Flash/Install the image files in your recovery. Be patient.
Here is the tricky part for me. the boot loader wont accept this older kernel.(thus the boot loops).
A faster way to work around this, is installing a custom kernel that supports android 10. e.g. quantum kernel.
You may have to reboot a number of times before you can get past the splash screen. Be patient.Success, you now have a weird but working system. (I call it weird because the kernel you will use will carry along with its bugs e.g. camera fails, random reboots.)You can not update the system. this may be due to the different AP/CP/CSC/ match. This is not a step by step guide, i am only sharing with the public what i did to get my final point.
Of course this goes without saying that you are attempting a risky route and you the user shall carry all responsibility.
Click to expand...
Click to collapse
Hello, you will not be able to downgrade your phone to Android 11, if it is not on theese firmware updates:
Of course, the reason is, that the binaries of newer updates are higher, than 7 (A505FNPUU7CUC2).
vmirrimv said:
Of course, the reason is, that the binaries of newer updates are higher, than 7 (A505FNPUU7CUC2).
Click to expand...
Click to collapse
So long as we both happy and got what we wanted. I finally have a working android 10 on my device(coming from a11)
vmirrimv said:
Hello, you will not be able to downgrade your phone to Android 11, if it is not on theese firmware updates:
Click to expand...
Click to collapse
You are correct. I gave up on changing the binaries after seeing it was impossible.
Camera should still work on custom android 10 one ui roms and GSI. I think I tested them before.