Related
Hello folks!
I got my new Vivo XL less than 24 hours ago and messing around with it (as I do with all my Android devices) I tried rooting it as some people mentioned with rootking first and then remove it with something called sume-something, can't recall but I did it right lol. Right after this I restarted the device and to my surprise it was stuck in the blu logo at the startup (the one with the colors). I aint that stupid though so I went ahead and accessed the phone's original recovery to wipe cache and factory reset it as well with no success, I tried up to 5 times doing still with no success. Now concerned I tried reflashing the unit and again to my surprise since it is too new (perhaps) I haven't been able to find just 1 guide in which I could've just downloaded certain files and push them through fastboot or something, the only thing I found was installing TWRP or CMW through SP Flash Tool which I definitely tried and now the device won't even show me a colored screen. I was able to install the MDTK drivers so the unit gets recognized by my windows 10 computer and while trying to flash through SPFT the unit gets detected but right now the device just wont boot up and I can't find the way of somehow installing the stock rom (which I couldn't find) back to the device. I didn't touch the bootloader nor anything related to it just tried to root the goddamn thing -_-.
I'd really appreciate any help you guys could offer me, right now I'm downloading the VIVO XL backup someone left available at the following link but if I knew at least what to do with it :/
https://www.dropbox.com/s/x4lgfv27jtgirkh/Blu_VivoXL_backup-2016-03-05.zip?dl=0
Keep in mind that my device right now is completely dead, I know I can flash it because when I connect it to the computer it gets recognized but nothing shows up in the screen , not even if I press the volume rockers or hold the power button.,
I'm even willing to issue a donation for the hero that could help me out because the unit was sent to my freight forwarder's locker and having it returned would technically be more expensive than getting the phone itself brand new, help a brother out and I'll do my best to help YOU out with at least a beer
Well after seeing so many views and realizing I could be taking advantage of the time I went ahead and downloaded the ROM for the geenios ?? S plus, formatted the device without the bootloader, downloaded the ROM and surprise surprise, it came back to life :0)
It however got stuck in the logo screen for 5 minutes but then android showed up. Just for anyone who goes through what I have and needs help, cheers!! (0:
Learning everday
MamoriNoTenshi said:
Well after seeing so many views and realizing I could be taking advantage of the time I went ahead and downloaded the ROM for the geenios ?? S plus, formatted the device without the bootloader, downloaded the ROM and surprise surprise, it came back to life :0)
It however got stuck in the logo screen for 5 minutes but then android showed up. Just for anyone who goes through what I have and needs help, cheers!! (0:
Learning everday
Click to expand...
Click to collapse
what you 're saying is that this BLU VIVO XL device can be recovered with the phone rom stock Gionee Elife S Plus and if there is no risk of doing so ?
andymartinez96 said:
what you 're saying is that this BLU VIVO XL device can be recovered with the phone rom stock Gionee Elife S Plus and if there is no risk of doing so ?
Click to expand...
Click to collapse
Sorry My English.
If you have a dead phone you can get to life but without modem, d´nt recognize the sim
This is with the rom Gionee S Plus in my vivo XL, all the applications works good, you d´not have calls or messages.
Saludos
El Eduar said:
Sorry My English.
If you have a dead phone you can get to life but without modem, d´nt recognize the sim
This is with the rom Gionee S Plus in my vivo XL, all the applications works good, you d´not have calls or messages.
Saludos
Click to expand...
Click to collapse
You can actually flash the Gionee rom and once installed use either the engineer mode or MTK droid tools to bring back the IMEI, the modem works but there's no IMEI and without it the carrier will not provide you signal, with the IMEI set (which is on the box and inside the phone below the battery) you will start receiving signal again. What happens is that when you reflash the VIvo XL with the GIonee flash it just removes the IMEI, but here's the thing. I didn't know about the IMei thingy after reflashing the phone, I was just trying to use my SIM certainly with no success. Once I was able to work out the Imei thing (I'm pretty sure I used uncle's app on android for the engineer mode) it started taking signal but it would just work for a few seconds (minutes if lucky) and then it would no longer have signal. After working this SEVERAL times I just thought to myself.. what if I just get a SIM from a different carrier. I **** YOU NOT, it worked. I didn't have to return my phone internationally (which would've been easier I guess but I liked the challenge) and ended up not only with a fixed phone, but rooted as well. Can't be happier right now, the phone, after a few weeks of testing this baby I can't complain, is definitely what I was looking for in a cellphone. Along with a few kernel tweaks it actually runs snappier than my girl's Iphone 5s, although I know spec-wise it's quite obvious.
Hope this gives you light, I know nothing about developing roms or such, just read for days without sleeping and worked the magic on this baby, embrace the challange!
MamoriNoTenshi said:
You can actually flash the Gionee and once installed use either the engineer mode or MTK droid tools to bring back the IMEI, the modem works but there's no IMEI and without it the carrier will not provide you signal, with the IMEI set (which is on the box and inside the below the battery) you will start receiving signal again. What happens is that when you reflash the VIvo XL with the GIonee flash it just removes the IMEI, but here's the thing. I didn't know about the IMei thingy after reflashing the , I was just trying to use my SIM certainly with no success. Once I was able to work out the Imei thing (I'm pretty sure I used uncle's app on for the engineer mode) it started taking signal but it would just work for a few seconds (minutes if lucky) and then it would no longer have signal. After working this SEVERAL times I just thought to myself.. what if I just get a SIM from a different carrier. I **** YOU NOT, it worked. I didn't have to return my internationally (which would've been easier I guess but I liked the challenge) and ended up not only with a fixed , but rooted as well. Can't be happier right now, the , after a few weeks of testing this baby I can't complain, is definitely what I was looking for in a cellphone. Along with a few kernel tweaks it actually runs snappier than my girl's Iphone 5s, although I know spec-wise it's quite obvious.
Hope this gives you light, I know nothing about developing roms or such, just read for days without sleeping and worked the magic on this baby, embrace the challange!
Click to expand...
Click to collapse
Thanks
I can´t write the imei (codes o aplications such as mtk tools, mtk engineering mode)
Saludos
ROM Stock BLU vivo XL
mediafire.com/folder/61m7ikt8k97j9/Vivo_XL_V0030UU_(TWRP)
Flash Tool (Mediatek)
mtk2000.ucoz.ru/load/soft/soft_mtk/sp_flash_tool/5-1-0-14
Kernel Source
FTP= 162.252.123.103/Vivo%20XL%20V0030UU/
Material:
plus.google.com/communities/117846429749085694805
Alguna idea para portar Cyanogenmod 13 a este modelo?
MamoriNoTenshi said:
You can actually flash the Gionee rom and once installed use either the engineer mode or MTK droid tools to bring back the IMEI, the modem works but there's no IMEI and without it the carrier will not provide you signal, with the IMEI set (which is on the box and inside the phone below the battery) you will start receiving signal again. What happens is that when you reflash the VIvo XL with the GIonee flash it just removes the IMEI, but here's the thing. I didn't know about the IMei thingy after reflashing the phone, I was just trying to use my SIM certainly with no success. Once I was able to work out the Imei thing (I'm pretty sure I used uncle's app on android for the engineer mode) it started taking signal but it would just work for a few seconds (minutes if lucky) and then it would no longer have signal. After working this SEVERAL times I just thought to myself.. what if I just get a SIM from a different carrier. I **** YOU NOT, it worked. I didn't have to return my phone internationally (which would've been easier I guess but I liked the challenge) and ended up not only with a fixed phone, but rooted as well. Can't be happier right now, the phone, after a few weeks of testing this baby I can't complain, is definitely what I was looking for in a cellphone. Along with a few kernel tweaks it actually runs snappier than my girl's Iphone 5s, although I know spec-wise it's quite obvious.
Hope this gives you light, I know nothing about developing roms or such, just read for days without sleeping and worked the magic on this baby, embrace the challange!
Click to expand...
Click to collapse
Glad you got it working. What kernel tweaks are you talking about ? I'd love to flash a kernel on my phone
Sent from my VIVO XL using XDA-Developers mobile app
D'not use Gionee, there is the Vivo XL posted.
You can't write the Imei with thats apk.
Flash the Vivo XL rom with SP Flash Tools.
Saludos
BLU One Plus con Tapatalk 6.0.5
Hello giuys
Here I am again, getting every day more and more dissapointed in this phone
Two weeks ago (or when the update was released) I updated to 32.2.A.0.224 hoping to get a better batterylife because previous build was giving me 2h SoT and a lot of bugs like random reboots and overheat all the time
I downloaded an algerian version from XPerifirm (one of the first to was released) and everything was fine (actually there was no much improvement of wich I was looking for, but it was a little better) but one day I can't connect to home wifi, cheking some things neither bluethoot, I had to reboot several times to make it work. Last weekend I downloaded another version from xperifirm (an SA version) and flashed again w/o problem, but the issue persist (started today), actually is worst because today I can't connect at all nor wifi or bluethoot .... I tried Hotspot but can't turn it on too... The screenshots below shows what happens when try to turn on wifi, bt and hotspot
Any ideas how to fix this? I was thinking on simply root and get a custom rom, but almost every custom rom is rooted and there are some games I play a lot and can't be played with root (and root cloack and every tool doesn't work), so is not an option, I'm so frustrated with this phone, hope one of u guys can help me
thanks in advance
I guess you got the wrong modem on that rom, may be you wasn't supposed to flash it.
So, you are frustated with this phone because you flashed a version that was not supposed to be installed on your phone? You mixed up your phone, not the phone itself. You are complaining about SOT and overheating without mentioning how you use your phone. Well, i guess, if you can flass another version rom in your phone, i think you have done more than this..!
Anyway, i hope someone expert can help you. But you have to admit that maybe it is your fault and not accuse the phone
It just was an expression, but as a note, the phone is unusable since the beginning, every update mess one more thing, is the crapiest phone I ever had xD, two months later I bought a real flagship phone, but need this phone working for a not advanced user (that doesn't know or have the time to flash and install all apps over and over again), and every rom installed brings problems that make the phone useless as your post[\s], sometimes battery of 5h in standby, sometimes overheat all the time, sometimes random reboots...
Also genius, actually this phone came with the first customization I flashed, but if u didn't know, all customizations are the same, just came with some apps and market restrictions (plus carrier apps/ settings in carrier specifics) so there's no "version that was not supposed to be installed in your phone" (u can even flash between variants in the same model as long as is a single-sim variant), go home and learn something before u comment so useless things, I understand why there are so low population lately in xda, remember when ppl actually came to help QQ
Anyways, this issue was there since before in some devices (Z3+ obviously) in old updates, I was trying to get some info with that ppl to see if there's a way to solve it, but due limitations at not rooted phones I think there's no way...
Another thing, in the second last update, there's a thread about some issues bootloader/security-related if u updated via OTA, there's a problem if I try to flash am older version after that OTA was installed? because I think the phone was a little more stable before that
Sent from my SM-G935F using XDA-Developers mobile app
Hi, I recently bought this phone and found out the cell reception has some issue and due to that phone keeps on searching network and draining my battery.
I didn't start cursing sony or this phone because I knew there is some issue with the radio and it needs to be replaced and I went to service center and they told me that motherboard needs to be changed.
It's been 1 week still I am waiting but with the new motherboard I think things will be fine.
So why don't you visit sony service center and try to fix things instead of blaming them.
mohitgalaxy3 said:
Hi, I recently bought this phone and found out the cell reception has some issue and due to that phone keeps on searching network and draining my battery.
I didn't start cursing sony or this phone because I knew there is some issue with the radio and it needs to be replaced and I went to service center and they told me that motherboard needs to be changed.
It's been 1 week still I am waiting but with the new motherboard I think things will be fine.
So why don't you visit sony service center and try to fix things instead of blaming them.
Click to expand...
Click to collapse
Don't misunderstand me, I love Sony phones and used it since W300-SE years, this phone have issues, sad is, service center actually doesn't give service if u don't buy the phone with the carrier they are (it seems the carrier pay to have service of almost all brands), and they sell phones (specially flagships) overpriced (like 150usd more) so I don't buy with them, neither use that carrier, so is a little hard
Sent from my SM-G935F using XDA-Developers mobile app
Hi!,
I'm a long-time reader of this forum, but this is my first post. In the last few days, something happened (I wish I could pinpoint exactly what) where I ended up restarting my phone and it entered a continuous boot loop. The phone was receiving updates per normal and may have received an update not that long ago that required some kind of restart, but I'm not confident about that. Either way, the phone was restarted and it entered into a permanent boot loop.
Before restarting, I'm confident the "ear sensor" that turns the screen off when I'm on a call as functioning. I'm also confident the auto-rotate functionality of the phone was working perfectly.
After I tried to factory reset the phone from the power-volume reset options, I actually ran into a TON of trouble trying to get the phone to properly reset. It tooks me countless tries to eventually get the phone to start after resetting it over and over again. I was stuck trying to get the phone to actually move through the setup steps. SUPER frustrating. I actually went to sleep while the phone was somewhere in the middle of setting up and when I woke up the phone somehow eventually made it through some setup steps.
I'm now using the phone as I normally would, but it's very odd. The phone is a LOT more unstable. At least 3 of the sensors I had working have just completely stopped working.
The phone is in otherwise perfect condition. I'm genuinely confused about how I should go about trying to resetting this thing to a pure stock configuration and slowly installing apps again to make the experience what I'd want.
And no, I'm not a super power user. I am a strong engineer happy to do crazy things like flashing bootloaders and whatnot, but I'm honestly confused about where to start. I understand other versions of this device may have had corrupted persist partitions during updates -- those problems seem like my problems -- but I don't know how I should go about simply flashing my phone at the lowest level into something stock that I can try to build back from.
And obviously when talking to google support their suggsetion is that I mail them the device and wait 10 days without a phone. I'm confused about how that could EVER be a reasonable way to get a phone repaired, sigh -- phones are not toys, they're pretty critical to the day-to-day work of so many people including myself. I'm pretty disappointing with that approach from Google and I had always considered them much better than that before this experience.
Anyway, I'm really lost and I'd love to understand how to repair the software on my phone.
(You all kick ass!)
aliljet said:
Hi!,
I'm a long-time reader of this forum, but this is my first post. In the last few days, something happened (I wish I could pinpoint exactly what) where I ended up restarting my phone and it entered a continuous boot loop. The phone was receiving updates per normal and may have received an update not that long ago that required some kind of restart, but I'm not confident about that. Either way, the phone was restarted and it entered into a permanent boot loop.
Before restarting, I'm confident the "ear sensor" that turns the screen off when I'm on a call as functioning. I'm also confident the auto-rotate functionality of the phone was working perfectly.
After I tried to factory reset the phone from the power-volume reset options, I actually ran into a TON of trouble trying to get the phone to properly reset. It tooks me countless tries to eventually get the phone to start after resetting it over and over again. I was stuck trying to get the phone to actually move through the setup steps. SUPER frustrating. I actually went to sleep while the phone was somewhere in the middle of setting up and when I woke up the phone somehow eventually made it through some setup steps.
I'm now using the phone as I normally would, but it's very odd. The phone is a LOT more unstable. At least 3 of the sensors I had working have just completely stopped working.
The phone is in otherwise perfect condition. I'm genuinely confused about how I should go about trying to resetting this thing to a pure stock configuration and slowly installing apps again to make the experience what I'd want.
And no, I'm not a super power user. I am a strong engineer happy to do crazy things like flashing bootloaders and whatnot, but I'm honestly confused about where to start. I understand other versions of this device may have had corrupted persist partitions during updates -- those problems seem like my problems -- but I don't know how I should go about simply flashing my phone at the lowest level into something stock that I can try to build back from.
And obviously when talking to google support their suggsetion is that I mail them the device and wait 10 days without a phone. I'm confused about how that could EVER be a reasonable way to get a phone repaired, sigh -- phones are not toys, they're pretty critical to the day-to-day work of so many people including myself. I'm pretty disappointing with that approach from Google and I had always considered them much better than that before this experience.
Anyway, I'm really lost and I'd love to understand how to repair the software on my phone.
(You all kick ass!)
Click to expand...
Click to collapse
I would try flashing the latest factory image via fastboot.
[Guide] Root Pixel 4 XL with Magisk Android 13
[Guide] Root Pixel 4 XL With Magisk Android 13 Android Security Bulletin—Feburary 2023 Pixel Update Bulletin—Feburary 2023 Introduction This Guide is for Pixel 4 XL owners that want to Root their phone, and enjoy the benefits of rooting it. The...
forum.xda-developers.com
https://forum.xda-developers.com/t/guide-unlock-flash-root-for-the-pixel-2-xl-taimen.3702418/ (This is for a Pixel 2 XL but the process is the same. It's basically a condensed version of the one above.)
aliljet said:
Hi!,
I'm a long-time reader of this forum, but this is my first post. In the last few days, something happened (I wish I could pinpoint exactly what) where I ended up restarting my phone and it entered a continuous boot loop. The phone was receiving updates per normal and may have received an update not that long ago that required some kind of restart, but I'm not confident about that. Either way, the phone was restarted and it entered into a permanent boot loop.
Click to expand...
Click to collapse
You did not provide the most important information we need- whether your phone is bootloader unlocked. Probably not, otherwise you would have already flashed it with a full Google image, which returns the phone to "out of the box" condition. You need to determine whether you can unlock your bootloader. If you cannot unlock (allow oem unlock is off and or greyed out in Dev options) then you will not be able to fastboot flash ANYTHING. If that is your case, the next best thing is flashing a full OTA image (sometimes called a rescue OTA) from recovery mode using the OTA via ADB option. This means you need fastboot/adb installed and working on your PC. Instructions on how are on the same Google dev page for OTA's.
So, my phone's bootloader is not unlocked. But I have an update for the crowd that may one day find this. I know your frustration and I can report that my phone is once again fixed.
A day (or two) after I sent this, a set of updates came down to my phone. And WebView was updated. That restored all of my sensors and also restored most of my crashing applications. It was an incredibly odd experience.
My phone once again functions. And the nightmare of owning a Google phone and talking to Google support has ended.
Ive actually been following the advice of many on this site for, ****, a couple few years now. i have a super unorthodox way of doing things, like how i figured out how to succesfully bypass frp on most samsung devices without a computer, last one i did was a couple weeks ago. because i dont have "class time" or training in coding or development besides what ive learned from you guys, i try alot of **** alot of pros wouldnt based on it shouldnt work that way, but, if i think i can weasel my way through anyway i usually prevail, and its usually by the application of a bunch of stupid little tiny actions. long story short i have to do things the hard way, guy could just grab a zte, install twrp app, flash recovery then in twrp recovery flash magisk, done. nope, too fricken easy. i gotta always get a lg, motorola or an iphone, before Uncover 8.0.2 was out, well before it was out i had my iphone 12 pro max jailbroken on 14.8. and i hope yall enjoy this as much as i did. i turned my ish app which i got from the app store jjst to make Apples butt hurt just a little more, i manipulated some filed and configs and basically turned it into Kali-Alpine lol, i then installed the checkrain debian, and yes jailbroke it from within, apples mdm is like neck and neck wiht you i learned while doing this, but when i did my ish filesystem editing, i didnt mount it until i was ready, and when i mounted thatfilesystem, you should ahve seen that realtime log light up, anyway, they said tell a story or something, and this will always be one of my favorite moments in triumph, because i took everything they use to keep a handle, as the very tools to take over the device lol.
in closing, i hope to give back for the advice and knowledge ive recieved in my time around. i will soon share my samsung debloat batch file, and a cople combination firmwares i have, and a magisk patched SM-A530W AP file whixh i also loaded the no verity/force encrypt kernel and twrp recovery image into, /system is mounted rw, props edited wiht all security disabled, and yes, kgclient removable, like totally uninstallable and everything is fine after, currently working on how to successfully boot and operate Samsung devices with 0x030c, bootloader code
theprimalconcretesinister said:
Ive actually been following the advice of many on this site for, ****, a couple few years now. i have a super unorthodox way of doing things, like how i figured out how to succesfully bypass frp on most samsung devices without a computer, last one i did was a couple weeks ago. because i dont have "class time" or training in coding or development besides what ive learned from you guys, i try alot of **** alot of pros wouldnt based on it shouldnt work that way, but, if i think i can weasel my way through anyway i usually prevail, and its usually by the application of a bunch of stupid little tiny actions. long story short i have to do things the hard way, guy could just grab a zte, install twrp app, flash recovery then in twrp recovery flash magisk, done. nope, too fricken easy. i gotta always get a lg, motorola or an iphone, before Uncover 8.0.2 was out, well before it was out i had my iphone 12 pro max jailbroken on 14.8. and i hope yall enjoy this as much as i did. i turned my ish app which i got from the app store jjst to make Apples butt hurt just a little more, i manipulated some filed and configs and basically turned it into Kali-Alpine lol, i then installed the checkrain debian, and yes jailbroke it from within, apples mdm is like neck and neck wiht you i learned while doing this, but when i did my ish filesystem editing, i didnt mount it until i was ready, and when i mounted thatfilesystem, you should ahve seen that realtime log light up, anyway, they said tell a story or something, and this will always be one of my favorite moments in triumph, because i took everything they use to keep a handle, as the very tools to take over the device lol.
in closing, i hope to give back for the advice and knowledge ive recieved in my time around. i will soon share my samsung debloat batch file, and a cople combination firmwares i have, and a magisk patched SM-A530W AP file whixh i also loaded the no verity/force encrypt kernel and twrp recovery image into, /system is mounted rw, props edited wiht all security disabled, and yes, kgclient removable, like totally uninstallable and everything is fine after, currently working on how to successfully boot and operate Samsung devices with 0x030c, bootloader code
Click to expand...
Click to collapse
Nice intro!, Welcome to XDA
theprimalconcretesinister said:
Ive actually been following the advice of many on this site for, ****, a couple few years now. i have a super unorthodox way of doing things, like how i figured out how to succesfully bypass frp on most samsung devices without a computer, last one i did was a couple weeks ago. because i dont have "class time" or training in coding or development besides what ive learned from you guys, i try alot of **** alot of pros wouldnt based on it shouldnt work that way, but, if i think i can weasel my way through anyway i usually prevail, and its usually by the application of a bunch of stupid little tiny actions. long story short i have to do things the hard way, guy could just grab a zte, install twrp app, flash recovery then in twrp recovery flash magisk, done. nope, too fricken easy. i gotta always get a lg, motorola or an iphone, before Uncover 8.0.2 was out, well before it was out i had my iphone 12 pro max jailbroken on 14.8. and i hope yall enjoy this as much as i did. i turned my ish app which i got from the app store jjst to make Apples butt hurt just a little more, i manipulated some filed and configs and basically turned it into Kali-Alpine lol, i then installed the checkrain debian, and yes jailbroke it from within, apples mdm is like neck and neck wiht you i learned while doing this, but when i did my ish filesystem editing, i didnt mount it until i was ready, and when i mounted thatfilesystem, you should ahve seen that realtime log light up, anyway, they said tell a story or something, and this will always be one of my favorite moments in triumph, because i took everything they use to keep a handle, as the very tools to take over the device lol.
in closing, i hope to give back for the advice and knowledge ive recieved in my time around. i will soon share my samsung debloat batch file, and a cople combination firmwares i have, and a magisk patched SM-A530W AP file whixh i also loaded the no verity/force encrypt kernel and twrp recovery image into, /system is mounted rw, props edited wiht all security disabled, and yes, kgclient removable, like totally uninstallable and everything is fine after, currently working on how to successfully boot and operate Samsung devices with 0x030c, bootloader code
Click to expand...
Click to collapse
How did your jail-breaking experience go? I've been thinking of jail-breaking my iPad Mini 4. (Look at my profile banner)
First of all: no, not from Hans Zimmer, but you may hear the beautiful Inception song as well while reading this... or don't...
Secondly: no I don't need help - so in case you don't have time / don't want to read my story, just don't. You won't be richer afterwards anyway. :')
And thirdly: God, this post won't be easy to write as I'm already sure, that it is going to be longer than imagined, to short because I have missed so much and also forgot to mention a few names, because there are too many names out there from people, who I do admire, are inspirations at&to the core and are really geniuses in their area. And I decided not to use any tags, because it would be just too many... and also to few... And I decided as well not to search for exact names, I'm sorry if I misspelled yours / remembered it incorrectly, I'll try my best.
- I have already said / mentioned it a couple of times that I'm going to stop rooting my next device, which has now arrived and is waiting in its box until the next days... it was real fun with my beloved stolen HTC Desire HD, where the world was still in its shape, XDA was less commercial and you could simply root your phone by using Chainfire's SuperSU - god I miss those days, I really do. Thank you also mike1986.
- After that came my horrible and second more intense endeavor with the LG Optimus 2X, which hurt my relationship with nVidia (yes, it was written like that years ago when I liked it and I still refuse to adapt to the new name) so so much and caused a couple of explosions from myself and as well my girlfriend's, because my phone refuse to ring when being called due to an incompatible RIL. Thank you pengus77 and also Ricardo Cerqueira for the glorious CyanogenMod.
- Things were quite smooth with all of my Xperia phones (Z1 Compact, Z5 Compact and X Performance), because if you knew them you could a) really use them rooted, were b) quite compact and c) you could also restore them fully to stock after they were rooted. So the situation was still ok, but you needed to unlock them after you saved the internal TA image partition, because Sony decided to permanently wipe it once you unlock the bootloader causing a crippled phone, because of missing drm keys. Thanks j4nn, doomlord, devshaft, IgorEisberg, tobias waldvogel, serajr, osm0sis, munjeni, Androxyde (in no particular order) for the experience. And I hate(d) Sony for that, i.e. that you need to a) find a security hole in the OS to be able to store your drm keys, b) they crippled all media on the phone (yes, this includes the camera as well, sadly). Sadly it became impossible to find a new competitive phone from the brand with an already known security hole.
- This story leads now down to the rabbit hole and my current phone: Samsung Galaxy S10. I _never ever_ thought that I'd buy a Samsung device as I usually am more of an underdog brand guy... but as it was more and more difficult to find a device with a) a good camera and b) a micro sd card I decided to expose myself to the Samsung world (side note: I never had a Nokia back then for example as well). That you also (permanently) cripple your phone due to Knox and cause bluetooth connections to be lost on reboot, wearables not to work, broken secure folder, etc. I didn't know, which made me sad - but at least they don't cripple the experience too much like Sony does... i.e. no deal-breaker... still it was a) on one hand a more pleasant experience than expected (god I even tried to stay with Samsung on the next phone), b) my first non-compact phone (with the intention to kill this criteria as well with the next phone) and c) still a phone with a micro sd card. Boy... (or / and girl...) d) rooted.
I needed root because d1) I always used an adblocker (thanks PerfectSlayer for AdAway), d2) used vpn since the x performance (not critical for d2 so far), and always used d3) betterbatterystats (thanks chamonix) + greenify (thanks oasisfeng) + (EdX|LS|X)posed (thanks rovo89, mlgmxyysd, whole LSposed team) which was one big reason to root (and finally became obsolete since Android 10+, because of Google's better deep sleep implementation), d4) backups (thanks to both the whole CWM, TWRP and TitaniumBackup teams) and d5) (also since the x performance) XPrivacy(Lua) (thanks M66B).
Finally we're on point when needed to migrate from SuperSU with SudoHide (or similar) to Magisk (thanks so much to topjohnwu for his efforts: 1) for the idea of Magisk... Google started to cause so much troubles, 2) for the Galaxy S10 procedures specifically -> what a horrible phone this is to root... due to no initramfs in the boot partition you need to either root the phone's (i.e. put Magisk into) kernel (never did that personally) or the recovery. I also wanted to spice up the security a bit, which led to the usage of an encrypted data partition by giving up twrp - bad bad decision, because that's when I had my only bootloop with an encrypted data partition and no way to recover from it, because I accidentally flashed an incomplete image, which shrank my data partition and every attempt to restore from that failed... I didnt bother too much, because I had set up TitaniumBackup and set my phone's camera to the external sd card. That's also exactly when I've realized that Titanium Backup is mostly broken on newer Android versions and my other backups were 3 months old... additionally I had lost the photos of a very cool holiday, because I borrowed my sd card to a friend and as I put it back in so that my girlfriend could take some photos during this trip, she didn't know to set the storage to the external card... I wasn't close by and she forgot to tell. That's how it is with backups: I needed them once all those years (obviously I also flashed, restored apps, etc., but that was all planned) and that's exactly when they don't work. Long story short: now we need people like (topjohnwu, osm0sis, ) byxiaorun, displax, huskydg, the whole Riru team (thanks Rikka and also all the other guys I have missed), didgeridoohan, BostonDan and also summarizers (like pndwal or zgfg to be able to keep up with everything, no disrespect intended [for calling you summarizers]!) to still have a working phone. Specific to the S10: thanks to 3arthur6, pickles, Ianmacd, dr.ketan.
And to be honest: I'm tired of having to write debloat scripts by my own just because I don't want to unencrypt the data partition. Change hex patches with every new major one ui update. copy images back and forth to phone to be able to root them, copy them back to the pc to finally flash them. crossing my fingers for every operation that works when I know that my backup was already long overdue since the last time. Oh I forgot: create my own riru and magisk forks for better hiding purposes when I'm a father of two children with a wife at home. Srsly... enough is enough... so I decided already approx. a year ago to stop rooting phones (screw google for the upcoming TEE enforcement!) and combined d1 and d2 to a vpn solution with ad blocking, stopped d3 alltogether, d4 wasn't working when I needed it most and d5 had to be sacrified... still unsure if my road continues now with Netguard (again: thank you M66B), AdAway or a different VPN solution - we'll see about that as well (and screw google a second time for not being able to use two VPNs at the same time). And screw (most of) all the manufacturers as well for giving up the microsd card slot... it shouldn't be that hard to get a phone with a microsd card slot and a very good camera. Sure there is Huawei (without Google Services, no thanks) or Xiaomi (at least some phones... without root I'm not sure if I would put my trust into this company with their stock firmware as a non-chinese resident) or Sony... where you can't use the camera / make videos for more than a couple of minutes, because they overheat... and that on a ~1400 USD phone. My ass... (sorry for the language). And to sacrifice the microsd slot was once again a tough decision, let's see if it's the right one - only time will tell. But to be able to do that, I wanted a phone with 512GB internal memory. This leaves you now with basically a couple of choices only: S22 Ultra (as being mentioned: would have loved it, but I don't want to spend so much on phones), Asus ROG Phone 6(d), Oppo Find X5 Pro or One+ 10 Pro. Let's see how the story continues... yes, you'll still see me around, but I'm not intending to use the XDA app on the phone anymore and won't stop by / react so frequently anymore. It was fun... (also to see pndwal and / or 73sidney joking around)... oh and I forgot to throw a few ponkles to you guys as well), but time to move on... And as everyone sees / hears, I took a different decision than Hippoman with his new Pixel 5 phone (have fun with that!).
Have a nice day / night everybody! And merry christmas + a happy 2023 as well, over and out (in the next couple of days at least)!
dr4go
p.s.: Sorry if I have ofended you / caused you any harm / not mentioned you. Sadly I'm not the youngest anymore and time is more precious than ever these days.
Noice fone!...
To get you started:
https://forum.xda-developers.com/t/oneplus-10-pro-ne2215-rooted.4431585/
A ponkle for you:
Maitre D: And finally, monsieur, a wafer-thin mint.
Mr Creosote: No.
Maitre D: Oh sir! It's only a tiny little thin one.
Mr Creosote: No... - I'm full...
Maitre D: Oh sir... it's only wafer thin.
Mr Creosote: Look - I couldn't eat another thing. I'm absolutely stuffed...
Maitre D: Oh sir, just... just one...
Mr Creosote: Oh all right. Just one.
Maitre D: Just the one, sir... voila... bon appetit...
....
Maitre D: Thank you, sir, and now the check....
- The Last Straw...