Related
I have a mimax hydrogen that had Nigel's lineage is 7.1.2 installed and working perfectly. I then made a full TWRP backup and installed another rom which also worked fine. However, I didn't quite like the rom and decided to restore back to the old rom, so I wiped cache, data and system in TWRP and restored the full backup of Nigel's rom. After booting up, the baseband is unknown. No wifi, BT or sim card showed up. Tried installing the other lineage Rom but nothing. Did full reset and restore of the radio from backup but still nothing. I need urgent help guys. What else can I try? Thanks
seti007 said:
I have a mimax hydrogen that had Nigel's lineage is 7.1.2 installed and working perfectly. I then made a full TWRP backup and installed another rom which also worked fine. However, I didn't quite like the rom and decided to restore back to the old rom, so I wiped cache, data and system in TWRP and restored the full backup of Nigel's rom. After booting up, the baseband is unknown. No wifi, BT or sim card showed up. Tried installing the other lineage Rom but nothing. Did full reset and restore of the radio from backup but still nothing. I need urgent help guys. What else can I try? Thanks
Click to expand...
Click to collapse
A clean installation of MIUI
Enviado desde mi MI MAX mediante Tapatalk
Do you think I can download a global rom and flash using TWRP? Will it relock my baseband? Thanks for the response
seti007 said:
Do you think I can download a global rom and flash using TWRP? Will it relock my baseband? Thanks for the response
Click to expand...
Click to collapse
I'm not sure if using TWRP it works you can try formating everything,if it doesn't then Fastboot is 100% sure.
Enviado desde mi MI MAX mediante Tapatalk
Thank you again for your help. While I was downloading the MIUI ROM, I tried installing lineage ROM one more time. I erased everything on the internal memory and then install the ROM and it worked. My IMEI as well as Wi-Fi and everything is back to normal. I then did a restore through TWRP how to backup I had and now I am up and running 100%. Thanks again.
You need to fill in your ID MIUI, otherwise you'll write about it on the factory manufacturer.
MCT_ said:
You need to fill in your ID MIUI, otherwise you'll write about it on the factory manufacturer.
Click to expand...
Click to collapse
Sorry can you please elaborate? I was able to get my phone back and running. Are you suggesting something additional I should do?
seti007 said:
Sorry can you please elaborate? I was able to get my phone back and running. Are you suggesting something additional I should do?
Click to expand...
Click to collapse
Yes (addition need to know), what in some cases, the server is unable to obtain reliable information about your device.
And before making any manipulation with the Rom, you need to register in bases MIUI, as the sole owner of the device.
If you flashed some other Rom and do not get the imei or the unique number of the Bluetooth (on some devices no), you need to check your account MIUI.
And if you do not remember your ID or password, the unlock will go through factory manufacturer.
Because the situation about which you say, very similar to the problem of reliability of information on the device.
Especially dangerous in such cases, the purchase of devices with owner, when originally ID registered was someone else.
Change of account, may occur only with the former owner of the device.
And you can imagine how it looks this situatio with any other custom Rom (which can not provide security).
When your unique IMEI code is threatened (with your consent) or no longer have rights of authorship on the part of the manufacturer and he refuses to bear any liability.
Your device turns into a piece of iron and glass, when you cross that line.
It is a General principle for all IMEI and equipment manufacturers (International Mobile Equipment Identifier).
The solution to the problem of which you speak may be actual until the first FC, is received on your device.
Not the fact that you solved your problem.
Thanks for the detailed answer. I get it now.
MCT_ said:
You need to fill in your ID MIUI, otherwise you'll write about it on the factory manufacturer.
Click to expand...
Click to collapse
MCT_ said:
Yes (addition need to know), what in some cases, the server is unable to obtain reliable information about your device.
And before making any manipulation with the Rom, you need to register in bases MIUI, as the sole owner of the device.
If you flashed some other Rom and do not get the imei or the unique number of the Bluetooth (on some devices no), you need to check your account MIUI.
And if you do not remember your ID or password, the unlock will go through factory manufacturer.
Because the situation about which you say, very similar to the problem of reliability of information on the device.
Especially dangerous in such cases, the purchase of devices with owner, when originally ID registered was someone else.
Change of account, may occur only with the former owner of the device.
And you can imagine how it looks this situatio with any other custom Rom (which can not provide security).
When your unique IMEI code is threatened (with your consent) or no longer have rights of authorship on the part of the manufacturer and he refuses to bear any liability.
Your device turns into a piece of iron and glass, when you cross that line.
It is a General principle for all IMEI and equipment manufacturers (International Mobile Equipment Identifier).
The solution to the problem of which you speak may be actual until the first FC, is received on your device.
Not the fact that you solved your problem.
Click to expand...
Click to collapse
seti007 said:
Thanks for the detailed answer. I get it now.
Click to expand...
Click to collapse
Very well, if you understand... because sometimes it is very difficult to formulate the message with lots of words.
This is the only reason.
Dear Community,
I just searched the past 2 days for a solution but I've not been lucky
Therefore I'd like to ask for help in this forum and hope there is some additional hint or hack I could try...:
So here's the situation:
OnePlus 5T (8/128) with a non booting or not "useful" OS (see last point what I've tried)
No TWRP or CWM
Stock Recovery present
Bootloader Locked
Allow Bootloader to be unlocked = FALSE
What I've already tried yet:
Flashing TWRP --> Not possible Bootloader Locked
Flashing regarding any other kinds like "update" or "flash all" as provided with TOOL_ALL_IN_ONE
ADB Sideload any available ROMS (Original "full" OP5T / FreedomOS / Omni8) --> ADB stops at 47% in Stock Recovery regardless of size of the ZIP file
Tried different versions of ADB (32 & 64 Bit / older & new / also with the LargeAddressAware approach / and on multiple PC's) --> Always same error (47%)
Stumbled upon the possibility to EmergencyDownload a factory flash due to Qualcomm chipset using the MSM-Download-Tool --> Only OnePlus 5 ROM available (no "T")
Mentioned EDL procedure works and OS is booting BUT neither Touchscreen nor USB OTG (for external mouse support) is working --> So I can't navigate and allow Bootloader to be unlocked again
Unfortunately I'm now stuck and have no more idea how to unbrick my phone again
What would help:
Any source to MSM-Download-Tool packed with a correct ROM for the OnePlus 5T
A Workaround to just flash TWRP via MSM-Download-Tool or Qualcomm's QFIL application in EDL mode
Some "hack" to bypass the locked Bootloader situation
Every appreciated Input you might have that I'm currently not aware of...
So PLEASE let me know of any approach that I could try or if you might have found a link or something else to a solution that might help me out of this disaster...
Many thanks in advance!
Tryouts due to your feedback:
@dreinulldrei - "fastboot boot recovery.img" tried with the original 5T Recovery.img also with blu_spark TWRP --> no luck...
SOLVED SOLUTION:
As the EDL factory flash ROM is currently not (or will never officially be) available public getting in contact with the OnePlus support team is required.
They have such a recovery tool (MSM-Download-Tool) with an appropriate ROM and are able to flash the device during a remote support session conducted via chat.
So by starting a chat on the OnePlus Support page and describing your situation will lead to scheduled time slot where a Level-2 technician will do all required steps remotely.
(All files are password protected and the technician ensures they are deleted at the end of the session so I'm unfortunately not able to provide the sources for DIY purposes...)
Following. I would think there would be some way to flash some sort of signed image via fastboot...
U flashed a 5 os to it, using the msmtool try to extract those files from 5t os, I will do it when I get home and so u can try it, i can't guarantee anything though, would u like me to do that for u
Bradl79 said:
U flashed a 5 os to it, using the msmtool try to extract those files from 5t os, I will do it when I get home and so u can try it, i can't guarantee anything though, would u like me to do that for u
Click to expand...
Click to collapse
Thanks for your input - I'm really not aware of how to generate such *.ops ROM files as this is what the MSM Tool expects...
But if there is a way and you are able to extract and produce a MSM flashable file I would be very happy to try!
I would recommend trying to boot a OP5T recovery, you might have flashed some OP5 rom including OP5 recovery. Just go into fastboot (power on with volume up pressed down), then via cmd:
fastboot boot recovery.img
Since OP does not offer the recovery to be downloaded, it will need to be downloaded from a working device. Lacking the cable right where I am, but I am sure someone else can help out.
crakerjac said:
Following. I would think there would be some way to flash some sort of signed image via fastboot...
Click to expand...
Click to collapse
Thanks for the input - I forgot to mention I also tried the 2 original available OP5T "full" ZIP ROM's (think they should be signed...)
Will add this to the initial Post but I assume also no chance here...
dreinulldrei said:
I would recommend trying to boot a OP5T recovery, you might have flashed some OP5 rom including OP5 recovery. Just go into fastboot (power on with volume up pressed down), then via cmd:
fastboot boot recovery.img
Since OP does not offer the recovery to be downloaded, it will need to be downloaded from a working device. Lacking the cable right where I am, but I am sure someone else can help out.
Click to expand...
Click to collapse
Ohhh good point - I also think there is the "wrong" recovery (from 5) currently on my phone (because also there the touchscreen behaves unexpectedly...)
But unfortunately with your command I get the "Your device is corrupted. It can't be trusted and will not boot" message.
Tried this with the original 5T Recovery.img I managed to obtain and also with the blu_spark TWRP - no luck...
Edit: Ignore, misread previous post.
U may have to make a call to oneplus so they can restore for u
Submit a ticket to One Plus
You are going to have to submit a ticket, they will arrange a time to help you by unbricking the phone remotely.
I just had to do this myself this week, and it got done today.
I do have the 5t unbricking files but I cannot access the archive because it's password protected.
One important this you didn't mention is how this happened.
OnePlus may be able to help with this one, but all root guides explicitly include the phrase "at your own risk."
blackknightavalon said:
OnePlus may be able to help with this one, but all root guides explicitly include the phrase "at your own risk."
Click to expand...
Click to collapse
Bradl79 said:
U may have to make a call to oneplus so they can restore for u
Click to expand...
Click to collapse
WMerkens said:
You are going to have to submit a ticket, they will arrange a time to help you by unbricking the phone remotely.
I just had to do this myself this week, and it got done today.
I do have the 5t unbricking files but I cannot access the archive because it's password protected.
Click to expand...
Click to collapse
Thanks for all your advice - so I will arrange a support chat/ticket as soon as possible and inform about the result in this thread.
Didn't thought that OnePlus Support Team would even care about such bricks (no warranty / own risk / "playing" with root / etc...)
But as indeed they seem to help like @WMerkens experienced I would be very happy to have a working device again
CodeXter said:
Thanks for all your advice - so I will arrange a support chat/ticket as soon as possible and inform about the result in this thread.
Didn't thought that OnePlus Support Team would even care about such bricks (no warranty / own risk / "playing" with root / etc...)
But as indeed they seem to help like @WMerkens experienced I would be very happy to have a working device again
Click to expand...
Click to collapse
don't know why you would think that OP wouldn't help...they have said from day one that unlocking/rooting does not void your warranty. Heck they encourage it. I assume you are the same person on the OP forum w/ this problem. Hopefully after you get this resolved you will have learned to NEVER EVER RELOCK your phone unless you do the whole factory image qualcomm recovery tool bit. and experienced OP folks on this forum know any claims of a "hardbricked" OP phone is ALWAYS not true.
Yeah oneplus used to be good about and does a remote session to restore, this was back in the one plus one days though, but I think they still do it
---------- Post added at 03:25 AM ---------- Previous post was at 02:54 AM ----------
WMerkens said:
You are going to have to submit a ticket, they will arrange a time to help you by unbricking the phone remotely.
I just had to do this myself this week, and it got done today.
I do have the 5t unbricking files but I cannot access the archive because it's password protected.
Click to expand...
Click to collapse
Awwww I wish we could get them, do they use the msmtool too?
How I bricked a 5t
I got the phone and I had installed twrp, that went fine. I was looking at magick systemless rooter when the phone then kicked in with a OTA update, I chose to ignore it the first time. It occurred again a few minutes and in my haste I let it do it's job but it did not complete correctly. I rebooted and the phone complained about corruption to the OS, I got in again but made the dumb mistake of re enabling the OEM lock and because I thought that might be causing the problem. I rebooted again but now I could not boot any more into the OS, it complained I was corrupted and go to google to see what to do.
So I was left with a bricked phone.
I could do bootloader but not recovery and I could not unlock the bootloader.
I could not get in via adb usb debug, So after much research I download the OnePlus 5 unbricking pack and learned a whole lot about qualicom and EDL mode, plus I learned a lot about the QFIL tools and restoring a phone. I did the 5 unbrick but my screen ended up upside down but the touch was right side up, which resulted in a very hard to use phone.
I tried the QFIL method but I was missing a mdb file to be able to talk to the phone.
So I gave up submitted a ticket and after much bad co-ordination on their part got a level 2 tech to debrick the phone remotely.
They do a reverse VPN and connect to your computer, they tell you to have 2 files archive ready in a folder on your desktop (they supply the links). They install the EDL driver and unpack the debrick archive. The archives are password protected, they run the tool and restore the phone
back to factory.
They erase the unpacked archives after they are done.
jerrywmilton said:
don't know why you would think that OP wouldn't help...they have said from day one that unlocking/rooting does not void your warranty. Heck they encourage it. I assume you are the same person on the OP forum w/ this problem. Hopefully after you get this resolved you will have learned to NEVER EVER RELOCK your phone unless you do the whole factory image qualcomm recovery tool bit. and experienced OP folks on this forum know any claims of a "hardbricked" OP phone is ALWAYS not true.
Click to expand...
Click to collapse
Oh yes I've learned my lesson on this :angel: --> Never ever set OEM to be unlocked to NO again
Obviously I do not exactly know what wrong procedure made me stuck in this situation but I just wanted to revert every single step back one by one to see which element brings me back to a valid SafetyNet situation...
I've been with the OnePlus "family" since the OP1 but never needed any direct support from the vendor - so every time there's a first time and so for me now...
Thus I really didn't know OP staff is actively doing remote support for their devices - but thumbs up for that! :good:
(BTW: I'm not the guy from the OP forum)
Bradl79 said:
Yeah oneplus used to be good about and does a remote session to restore, this was back in the one plus one days though, but I think they still do it
---------- Post added at 03:25 AM ---------- Previous post was at 02:54 AM ----------
Awwww I wish we could get them, do they use the msmtool too?
Click to expand...
Click to collapse
Yes basically it's the same archive as the 5 unbrick pack but it's for 5t, OnePlus 5T OxygenOS 4.7.2-171116.zip is the archive and you can look in it and you see the ops file is for dumpling not cheesburger, which is the code name for 5t. I saw the MsmDownloadTool is 4.0.8
Bradl79 said:
Yeah oneplus used to be good about and does a remote session to restore, this was back in the one plus one days though, but I think they still do it
---------- Post added at 03:25 AM ---------- Previous post was at 02:54 AM ----------
Awwww I wish we could get them, do they use the msmtool too?
Click to expand...
Click to collapse
I just had a chat with them before and got mailed a link to the MSMTool incl. ROM for the OP5T (dumpling)
But unfortunatley support files from OnePlus are password protected Nevertheless here the original vendor link:
https://onepluscn-my.sharepoint.com/personal/sheva_liu_oneplus_net/_layouts/15/guestaccess.aspx?docid=0fde9596c72744b4fb9c073ca5d87edbe&authkey=AQPXKRi7pdIzZX-5WH_pwWg&e=1030aa0046da4d1aa9189020027d9c93
So I have to wait for my remote support schedule on Saturday to have the L2 technician entering the password and do the rest.
Would be able to do this myself but OnePlus obviously wants to protect their sources what I have to accept, respect and be patient for...
So, never turn off the OEM Unlocking?
I've been trying to unlock the bootloader of Realme X2, the CN version but I'm facing a problem.
The Problem is that whenever I try to install the bootloader unlocking app (In Depth Test), a message appears (see the attachment) saying "An app with the same signature has already been installed" although I've not installed it yet, and I can't find it anywhere on my phone assuming that it's pre-installed.
what should I do to install the app?
or is there any other method to unlock the bootloader that avoids installing the app as long as I can't install it?
N.B: a photo of the message is attached.
{Mod edit: Quoted post deleted}
Thanks for the advice.
I only want to unlock the bootloader to change the launcher because it's so annoying and I can't get used to it.
is there a way to do it? because I tried to uninstall it using adb uninstall command and it's not working.
louai rabia said:
The Problem is that whenever I try to install the bootloader unlocking app (In Depth Test), a message appears (see the attachment) saying "An app with the same signature has already been installed" although I've not installed it yet, and I can't find it anywhere on my phone assuming that it's pre-installed.
Click to expand...
Click to collapse
You tried to install a wrong version of the app. Use this one
---------- Post added at 05:17 PM ---------- Previous post was at 05:12 PM ----------
badreddine uday said:
look dear friend i tried before i bricked my phone i spent two months without so i flashed it a week ago online by egyptian guy its cost me 14 dollars so i wanna advice you di not unlock it u can have premium themes with trick and enjoy there is no different between cn and global
Click to expand...
Click to collapse
Most likely you bricked your device by LOCKING BACK it, not by UNLOCKING bootloader.
yakovpol said:
You tried to install a wrong version of the app. Use this one
---------- Post added at 05:17 PM ---------- Previous post was at 05:12 PM ----------
Most likely you bricked your device by LOCKING BACK it, not by UNLOCKING bootloader.
Click to expand...
Click to collapse
Does this mean, if someone tries to relocking the bootloader after unlocking it, it will brick?
louai rabia said:
Does this mean, if someone tries to relocking the bootloader after unlocking it, it will brick?
Click to expand...
Click to collapse
Not at all!
I made it about 5 times without any problems. The reason for bricking is non-stock contents of the partitions. Follow closely the Back to stock ROM howto guide to avoid this.
yakovpol said:
Not at all!
I made it about 5 times without any problems. The reason for bricking is non-stock contents of the partitions. Follow closely the Back to stock ROM howto guide to avoid this.
Click to expand...
Click to collapse
First, may you post the links of the right way to unlock the bootloader and rooting the device?
Second, does unlocking the bootloader or rooting harm the device in anyway? As some say the fingerprint won't work anymore, some say the gestures won't work and some say other things.
Moderator Announcement: I've cleaned the thread from the "discussion" how to circumvent license checks. Please do not commence such a discussion, provide information in this respect just do not become involved in the bypass or circumvention of license checks. If you required to pay for a theme, an app or whatever, then pay for it!
XDA Forum Rules (excerpt):
...
6. Do not post or request warez.
If a piece of software requires you to pay to use it, then pay for it. We do not accept warez nor do we permit members to request, post, promote or describe ways in which warez, cracks, serial codes or other means of avoiding payment, can be obtained or used. This is a site of developers, i.e. the sort of people who create such software. When you cheat a software developer, you cheat us as a community.
...
Click to expand...
Click to collapse
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
Hello.
I want to install a custom ROM on my phone.
I have a Xiaomi Redmi Note 8 Pro, and I would like to move away from the stock firmware do to privacy concerns.
I have never seen a phone where you have to accept a licence agreement for a calendar app.
Anyway, I have never installed a custom ROM on my phone, and would like to start. The only thing that is stopping me is the fact that I have no idea where to start or what to do...
So, here I am.
Can you people link me to some good tutorials?
I want to backup the current firmware I have (including recovery) to return it when selling the phone or giving it to someone...
And I would like to know how to flash different roms and recoveries.
Thanks in advance.
LOL
Have you searched that forum before asking?
parkourz said:
LOL
Have you searched that forum before asking?
Click to expand...
Click to collapse
No, I’m asking for good tutorials. read the whole thing before you go “LOL”…
electric fish said:
Hello.
I want to install a custom ROM on my phone.
I have a Xiaomi Redmi Note 8 Pro, and I would like to move away from the stock firmware do to privacy concerns.
I have never seen a phone where you have to accept a licence agreement for a calendar app.
Anyway, I have never installed a custom ROM on my phone, and would like to start. The only thing that is stopping me is the fact that I have no idea where to start or what to do...
So, here I am.
Can you people link me to some good tutorials?
I want to backup the current firmware I have (including recovery) to return it when selling the phone or giving it to someone...
And I would like to know how to flash different roms and recoveries.
Thanks in advance.
Click to expand...
Click to collapse
1/You dont need to backup your firmware, when you want to sell, just flash any firmware and lock bootloader if you want. But you need to remember your Mi Account Password.
2/Some you need:
-Unlock bootloader
-Flash correct firmware of custom rom you want
-Custom recovery
-Flash rom in Twrp with Guide (Read in rom post)
You can collect some information in Xda group. You can also join Telegram Group which have enough guide (some can lead you here and some not) and new roms.
Kirasu2080 said:
1/You dont need to backup your firmware, when you want to sell, just flash any firmware and lock bootloader if you want. But you need to remember your Mi Account Password.
2/Some you need:
-Unlock bootloader
-Flash correct firmware of custom rom you want
-Custom recovery
-Flash rom in Twrp with Guide (Read in rom post)
You can collect some information in Xda group. You can also join Telegram Group which have enough guide (some can lead you here and some not) and new roms.
Click to expand...
Click to collapse
Thank you. Let's hope I won't brick my device hehe. By the way, I'm running Linux on my PC, does Xiaomi have an unlock tool for Linux?
electric fish said:
Thank you. Let's hope I won't brick my device hehe. By the way, I'm running Linux on my PC, does Xiaomi have an unlock tool for Linux?
Click to expand...
Click to collapse
Unlock official tool maybe doesn't work with Linux and you will need to wait 168h for unlock.
Unlock unofficial tool (mtkclient) can work with Linux and instant but sometimes increase more bug chance (which can fix as i know). And mess with it if you dont know anything can make terrible thing. Just check unlock part, dont mess with other
And we have unbrick hardbrick method. If you don't do crazy thing, then you will be fine.
After unlock and flash twrp, backup your Imei first. That will help you if you make some unknown mistake later.
Kirasu2080 said:
Unlock official tool maybe doesn't work with Linux and you will need to wait 168h for unlock.
Unlock unofficial tool (mtkclient) can work with Linux and instant but sometimes increase more bug chance (which can fix as i know). And mess with it if you dont know anything can make terrible thing. Just check unlock part, dont mess with other
And we have unbrick hardbrick method. If you don't do crazy thing, then you will be fine.
After unlock and flash twrp, backup your Imei first. That will help you if you make some unknown mistake later.
Click to expand...
Click to collapse
About the IMEI backup, is that only the number, or a file I need to back up?
I also want to make a backup of my original stock recovery and ROM, is it possible?
electric fish said:
No, I’m asking for good tutorials. read the whole thing before you go “LOL”…
Click to expand...
Click to collapse
LOL
Maybe better leave your phone alone if you consider tutorials on that forum "not good"...
parkourz said:
LOL
Maybe better leave your phone alone if you consider tutorials on that forum "not good"...
Click to expand...
Click to collapse
What forum is "that forum" and where did I ever say that they're "not good"?