Related
Hi, Grateful for advice on approach to re-root. I have already researched this.
An early root-able L9 p769 10e which I purchased new and successfully rooted before putting it up for storage worked flawlessly for six months beginning this April when I finally put it in service with ATT with very light use voice and text. No mods or tinkering on the oem 10e ROM. Almost nothing downloaded and very little web browsing.
A few days ago 4.1.2 20h, kernel 3.0.31, build JZO54K was pushed through. Did this perma-lock the B-L?
TMO unlocked this when new. I had rooted on stock ICS 10e ROM and verified the binary then installed these from G-Play prior to dry storage: Root Checker, Super SU Pro, Titanum Pro, SuperUserPro, Script Writer, nothing else.
It functioned flawlessly for six months with very light use primarily text , SMS and rare web browsing. Virtually no other mods, downloads or tinkering. No tunes or photos.
Several days ago I started getting low memory warning. Using only the stock software I attempted to free up space so should not have damaged anything. After removing a few tmo bloatware items it started to freeze on boot the other day. I removed the battery but could not get it to boot past the tmo jingle and oval logo. It would enter the S/W mode with yellow./black screen so I attempted to use the LG update tool. The phone was recognized. After "analyzizing" it reported "downloading" but the clock would stop at 37 seconds. I could get no other diagnostic screens on the phone itself and suspected that it was not in correct USB mode for update. ATT had me do an emergency restore which was successful but of course wiped the root.
It appears that Titanium has saved bu to the SD but I do not know if this will be useful. I believe this early L9 had the unencrypted boot loader. IIRC the b-l was unlocked when rooted..
File manager shows what I believe are titanium bu.:
folder with black box "external_SD" and one called "sdcard 0"
"external" fldr has these sub folders: "backup 7/5/2015" , data, DCIM, LOST.DIR
the sdcard0 fldr has another dcim plus many more sub folders
Can this be re-rooted? I'd like to at least recover phone data such as SMS texts.
Grateful if someone will advise if BL is now perm locked and point me in the right direction.
BL unlock, NAM. unlock & root are mutually exclusive.
BL unlocked = install custom firmware. I doubt you have this. It will indicate on s/w update screen if it's unlocked.
NAM unlocked = use SIM from another carrier. Sounds like you have this, c/o Tmo.
Root = administrative access via 'su' binary.
When you say low memory warning, do you mean "free up some storage" warning? Memory & storage are not the same thing. External_SD is just that. Sdcard0 is internal, virtual storage, which is what was full.
Since you have a working ROM, I'd suggest rooting with Cydia Impactor (Google it), installing Titanium Backup, and restoring from the backup. Likely just that simple.
Darren
Sent from my Bell Mobility Samsung Galaxy S6 SM-G920W8 using Tapatalk
@DarryDoo
Darren, Your reply is very much appreciated. Yes, I meant storage. There are 1.8GB available at best. I had only a handful of pics, no music. The warning seems a common complaint with this phone.
I located this: http://www.cydiawater.com/cydia-impactor-can-root-android-devices/
Are there any pros or cons of this method compared to the others described here?
I'd like to strip the tmo branding and bloatware but it seems others have gotten in over their heads trying to run CWM. Understood that BL unlock is required for recovery in to custom KDZ, ROM and such but being able to load apps like Titanium will likely suffice.
The Bin4ry rooting was all there was back when I purchased the P769 which fortunately was the early model. Thought that I had unlocked the BL but perhaps I'm mistaken. I remain unclear as to the persistence of the advantage that this early P769 has/had once the update to 20h is pushed through. Is my BL now encrypted?
For the purpose of learning and future reference it would be good to know what alternatives were available to me when the rooted 10e phone locked up. All the apps mentioned are gone but SuperSU which is reporting no binary of course. I wonder why it didn't get wiped. I'm uncertain as to whether this was a "restore" hard or soft reset that I did.
>>Is it necessary to remove SuperSU prior to the Cydia process ?
Thanks again for your help Darren and to any who might have something to add.
Creeks
creeks said:
@DarryDoo
Darren, Your reply is very much appreciated. Yes, I meant storage. There are 1.8GB available at best. I had only a handful of pics, no music. The warning seems a common complaint with this phone.
I located this: http://www.cydiawater.com/cydia-impactor-can-root-android-devices/
Are there any pros or cons of this method compared to the others described here?
I'd like to strip the tmo branding and bloatware but it seems others have gotten in over their heads trying to run CWM. Understood that BL unlock is required for recovery in to custom KDZ, ROM and such but being able to load apps like Titanium will likely suffice.
The Bin4ry rooting was all there was back when I purchased the P769 which fortunately was the early model. Thought that I had unlocked the BL but perhaps I'm mistaken. I remain unclear as to the persistence of the advantage that this early P769 has/had once the update to 20h is pushed through. Is my BL now encrypted?
For the purpose of learning and future reference it would be good to know what alternatives were available to me when the rooted 10e phone locked up. All the apps mentioned are gone but SuperSU which is reporting no binary of course. I wonder why it didn't get wiped. I'm uncertain as to whether this was a "restore" hard or soft reset that I did.
>>Is it necessary to remove SuperSU prior to the Cydia process ?
Thanks again for your help Darren and to any who might have something to add.
Creeks
Click to expand...
Click to collapse
Try this: http://www.cydiaimpactor.com
More info: http://forum.xda-developers.com/showthread.php?t=2511695
The big pros: super simple rooting. Very safe.
You can likely leave SuperSU installed, read the 2nd link above to be certain. (edit: checked the link, you can leave it installed.)
I don't know enough about your particular phone to comment on the BL status, but you weren't installing custom ROMs anyway, so it's an academic question. (edit: you can check BL status in s/w update mode, as I stated earlier.)
You can still install customized, de-bloated stock ROMs on a locked BL, there are a number in these forums, eg. Kumakan & UltraROM. They rely on a 2nd-init recovery, which is permitted on a locked BL.
You can also verify your BL status, and unlock your BL if you want to use CM. I've successfully unlocked both my P769's, and run CM11, using a 910k cable.
My best guess is that during your de-bloating process, you uninstalled something critical. Installing a 2nd-init recovery, and making nandroid backups in recovery prior to making changes, is a good practice, and makes rolling back changes if something goes wrong, possible.
Sent from my Bell Mobility Samsung Galaxy S6 SM-G920W8 using Tapatalk
Hey XDA, I haven't been on here since my Samsung S2 years ago. I picked up a new moto Z for daydream, (amazon 499 special, 64 gb luna grey unlocked, retus software, 650-03). I bought it from the american amazon, and I am in canada. I popped in my Sasktel sim card and it works perfectly.
My questions are:
How do I manually flash nougat?
If I flash to the rogers 45 firmware, will I still be able to use my Sasktel sim?
How long until nougat comes out regardless? Should I just wait?
If I do flash to this "rogers 45 nougat", can I go back to my "vanilla" stock later? ( i just want daydream now, i bought the headset already. then when my area gets nougat, ill flash back to my phones nougat.. or does it make a difference?)
Sorry for the really random questions. I couldn't find the answers to these on the forums or on google. (reddit has been saying just wait, and don't flash)
You can try this thread here: http://forum.xda-developers.com/moto-z/how-to/easy-flash-to-nougat-tutorial-unlocked-t3514245 - I had success flashing the Rogers 45 firmware (am on retca software channel) but for the life of me couldn't get the Nougat update to install. I'm on Telus and had no issues with my SIM card working after I flashed to the Rogers 45. Flashed back to the retca official firmware (http://forum.xda-developers.com/moto-z/development/moto-z-official-firmware-downloads-t3449837) this morning with no problems.
Another issue I'm running into is that I unlocked it and for the life of me I can't seem to get the phone locked again. Minor issue but that "your phone is unlocked/untrustworthy" message when you boot up is annoying
pixelens said:
...
Another issue I'm running into is that I unlocked it and for the life of me I can't seem to get the phone locked again. Minor issue but that "your phone is unlocked/untrustworthy" message when you boot up is annoying
Click to expand...
Click to collapse
Just flash the patched bootlogo you can find here... (or, better, make one as I liked more and asked for... )
enetec said:
Just flash the patched bootlogo you can find here... (or, better, make one as I liked more and asked for... )
Click to expand...
Click to collapse
Going to start a new thread so as not to hijack this one
I'll try to give you some "sparse" answers...
- Rogers is a "not carrier locked" software so, no problem with any sim... to be honest it hasn't any special at all!
It's preferred only because between the "leaked" software versions it is the only leaked in .45 and not in .17 subversion... and a .45 is needed for Nougat OTA to apply.
If you are already on a .45 I don't think you really need to flash Roger to have the sideload OTA to apply...
- if you have your full software version on pc to flash in case, yes, you can come back from rogers BUT *only* until you are still on MM.
On this phone Nougat OTA updates a LOT of things (bootloader, baseband, perhaps something on GPT too...) and is *NOT* reversible. Or, at least, not in an easy (as safe...) way... Some have poked with it and.... we have had first bricks... (quite hard ones...).
So?
So I would eventually try in another way.
DISCLAIMER: this isn't tested first hand by me. Some other ( @erfanoabdi) in chat with me reported that it worked for him, but I've to warn that as ALL hacking & tweaking operations something could go wrong (read: bootloop & eventually soft bricks... I don't think hard bricks anyway, BUT this only my-own-opinion, ok? )
Said that... my idea is making things simpler. More... many people are reporting issues with some of the upgraded parts on Nougat (wifi, Bluetooth, etc...) AND upgraded bootloader (and GPT?) are main problems if we want to return to MM, so... let's limit the upgrade to only what's really needed...
Steps should be:
- unlock bootloader
- Flash TWRP in fastboot/fastload mode
- take a *FULL* backup of *ALL* partitions by TWRP (yes, system image too!!) and put it in a safe place (no, your phone or microSD is *not* a safe place...)
- download full Nougat retmx firmware (the only N available at moment...)
- go in fastboot/fastload mode and flash *only* boot.img and system.img using mfastload commands
- enter directly in TWRP (don't boot!) and flash patch for unencrypted kernel
- wipe cache, dalvik and *format* data (yes, format, not only wipe it...). WARNING: this will erase all the contents of your internal storage memory, so take a backup before...
- Reboot...
It should boot fine on Nougat... :fingers-crossed:
(and mantaining your ret channel, not changing it to retmx probably...)
After eventually we'll talk about root...
This way it should be ready to return to MM if needed using the same procedure (changing only boot.img and system.img with MM ones...).
Obviously this is a raw description of procedures... it is written considering that you have good knowledge of the matter and you know how to install and use drivers, adb & fastboot commands, TWRP and so on...
For more info or doubts... ask @erfanoabdi :laugh:
enetec said:
I'll try to give you some "sparse" answers...
- Rogers is a "not carrier locked" software so, no problem with any sim... to be honest it hasn't any special at all!
It's preferred only because between the "leaked" software versions it is the only leaked in .45 and not in .17 subversion... and a .45 is needed for Nougat OTA to apply.
If you are already on a .45 I don't think you really need to flash Roger to have the sideload OTA to apply...
- if you have your full software version on pc to flash in case, yes, you can come back from rogers BUT *only* until you are still on MM.
On this phone Nougat OTA updates a LOT of things (bootloader, baseband, perhaps something on GPT too...) and is *NOT* reversible. Or, at least, not in an easy (as safe...) way... Some have poked with it and.... we have had first bricks... (quite hard ones...).
So?
So I would eventually try in another way.
DISCLAIMER: this isn't tested first hand by me. Some other @erfanoabdi) in chat with me reported that it worked for him, but I've to warn that as ALL hacking & tweaking operations something could go wrong (read: bootloop & eventually soft bricks... I don't think hard bricks anyway, BUT this only my-own - opinion, ok? )
Said that... my idea is making things simpler. More... many people are reporting issues with some of the upgraded parts on Nougat (wifi, Bluetooth, etc...) AND upgraded bootloader (and GPT?) are main problems if we want to return to MM, so... limit the upgrade to only what's really needed...
Steps should be:
- unlock bootloader
- Flash TWRP in fastboot/fastload mode
- take a *FULL* backup of *ALL* partitions by TWRP (yes, system image too!!) and put it in a safe place (no, your phone or microSD is *not* a safe place...)
- download full Nougat retmx firmware (the only N available at moment...)
- go in fastboot/fastload mode and flash *only* boot.img and system.img using mfastload commands
- enter directly in TWRP (don't boot!) and flash patch for unencrypted kernel
- wipe cache, dalvik and *format* data (yes, format, not only wipe it...). WARNING: this will erase all the contents of your internal storage memory, so take a backup before...
- Reboot...
It should boot fine on Nougat... :fingers-crossed:
(and mantaining your ret channel, not changing it to retmx probably...)
After eventually we'll talk about root...
This way it should be ready to return to MM if needed using the same procedure (changing only boot.img and system.img with MM ones...).
Obviously this is a raw description of procedures... it is written considering that you have good knowledge of the matter and you know how to install and use drivers, adb & fastboot commands, TWRP and so on...
For more info or doubts... ask @erfanoabdi :laugh:
Click to expand...
Click to collapse
Yes very good tutorial, I really likes to write something like this but I'm not good in English
Thanks again
erfanoabdi said:
...
Thanks again
Click to expand...
Click to collapse
Ahahahaha, this is only "chatting" in not-so-good-English ... :laugh:
Thanx for you *great* development here instead! :highfive:
enetec said:
I'll try to give you some "sparse" answers...
- Rogers is a "not carrier locked" software so, no problem with any sim... to be honest it hasn't any special at all!
It's preferred only because between the "leaked" software versions it is the only leaked in .45 and not in .17 subversion... and a .45 is needed for Nougat OTA to apply.
If you are already on a .45 I don't think you really need to flash Roger to have the sideload OTA to apply...
- if you have your full software version on pc to flash in case, yes, you can come back from rogers BUT *only* until you are still on MM.
On this phone Nougat OTA updates a LOT of things (bootloader, baseband, perhaps something on GPT too...) and is *NOT* reversible. Or, at least, not in an easy (as safe...) way... Some have poked with it and.... we have had first bricks... (quite hard ones...).
So?
So I would eventually try in another way.
DISCLAIMER: this isn't tested first hand by me. Some other ( @erfanoabdi) in chat with me reported that it worked for him, but I've to warn that as ALL hacking & tweaking operations something could go wrong (read: bootloop & eventually soft bricks... I don't think hard bricks anyway, BUT this only my-own-opinion, ok? )
Said that... my idea is making things simpler. More... many people are reporting issues with some of the upgraded parts on Nougat (wifi, Bluetooth, etc...) AND upgraded bootloader (and GPT?) are main problems if we want to return to MM, so... let's limit the upgrade to only what's really needed...
Steps should be:
- unlock bootloader
- Flash TWRP in fastboot/fastload mode
- take a *FULL* backup of *ALL* partitions by TWRP (yes, system image too!!) and put it in a safe place (no, your phone or microSD is *not* a safe place...)
- download full Nougat retmx firmware (the only N available at moment...)
- go in fastboot/fastload mode and flash *only* boot.img and system.img using mfastload commands
- enter directly in TWRP (don't boot!) and flash patch for unencrypted kernel
- wipe cache, dalvik and *format* data (yes, format, not only wipe it...). WARNING: this will erase all the contents of your internal storage memory, so take a backup before...
- Reboot...
It should boot fine on Nougat... :fingers-crossed:
(and mantaining your ret channel, not changing it to retmx probably...)
After eventually we'll talk about root...
This way it should be ready to return to MM if needed using the same procedure (changing only boot.img and system.img with MM ones...).
Obviously this is a raw description of procedures... it is written considering that you have good knowledge of the matter and you know how to install and use drivers, adb & fastboot commands, TWRP and so on...
For more info or doubts... ask @erfanoabdi :laugh:
Click to expand...
Click to collapse
Wow! Thank you for the response! This answered pretty much all of my questions, but also sparked a few more. The Moto Z was a pretty big purchase for me so I am in no hurry to lose functionality. A lot of people are using translators on here, so I'll be simple (sorry if it comes off as blunt or rude, typing with translators in mind)
I want to stay on android 7. Downgrading to 6.0 is not a worry for me.
I want to get future updates from my carrier. (official android/moto updates and security patches. I want to be able to use the "Google Tango" mod, if it comes out)
I want to be able to use the projector mod and daydream.
I do not plan on rooting my phone (maybe later), and I do not want to unlock my bootloader.
Will the retmx nougat be different then the copy of nougat I would get from retus?
Finally, is there any benefit to waiting for the OTA? Or am I getting the exact same copy of nougat on XDA, that I would in three weeks from OTA? I already bought the daydream headset, am I waiting for nothing?
*two more questions I guess*
Do I need a SD card?
do I need to unlock my bootloader to do this upgrade?
( http://forum.xda-developers.com/moto-z/how-to/update-to-7-0-nougat-xt1650-03-retus-t3513095)
(http://forum.xda-developers.com/moto-z/how-to/easy-flash-to-nougat-tutorial-unlocked-t3514245)
Sorry for all the questions. I have looked all over XDA and haven't been able to find an answer (reddit, and google too :/). I am hoping that other people will be able to read this, and have their questions answered as well.
Again, thank you. You guys are really smart.
pixelens said:
You can try this thread here: http://forum.xda-developers.com/moto-z/how-to/easy-flash-to-nougat-tutorial-unlocked-t3514245 - I had success flashing the Rogers 45 firmware (am on retca software channel) but for the life of me couldn't get the Nougat update to install. I'm on Telus and had no issues with my SIM card working after I flashed to the Rogers 45. Flashed back to the retca official firmware (http://forum.xda-developers.com/moto-z/development/moto-z-official-firmware-downloads-t3449837) this morning with no problems.
Another issue I'm running into is that I unlocked it and for the life of me I can't seem to get the phone locked again. Minor issue but that "your phone is unlocked/untrustworthy" message when you boot up is annoying
Click to expand...
Click to collapse
Awesome, so I would probably want to take note of my retus (not retca, because I bought mine from the american amazon, right?). Do I need to unlock my bootloader to get regular android 7? or did you root as well as upgrade?
Thank you for the response.
Porcelainfog said:
Awesome, so I would probably want to take note of my retus (not retca, because I bought mine from the american amazon, right?). Do I need to unlock my bootloader to get regular android 7? or did you root as well as upgrade?
Thank you for the response.
Click to expand...
Click to collapse
Yup, you'll want the retus firmware I would think. I'm not sure if you have to unlock your bootloader, I did only because I was having issues with the Nougat update and thought that might be why but it didn't make a difference. I did get the Nougat update to install this morning though, tried it on another computer (stupid ADB). I did not root though, just unocked my bootloader and did the Rogers flash then the Noughat sideload.
I'd try it without unlocking the bootloader, if you get an error saying "can't read file <###>" when trying to adb sideload the Nougat update, try different ADB drivers or a different computer first before unlocking it. The couple people I know that have chimed in say they're unlocked as well but haven't indicated whether you need to be or not.
Based on your expressed needs... I'll just wait your OTA. Nothing more. It's only a matter of weeks anyway...
Sorry for being a newb and asking here but I'm finding it difficult to get my head around this.
I was originally on MM and upgraded to Nougat on unlocked I international Moto Z.
I then decided to install TWRP, root and try a new ROM. If I want to go back to stock Nougat can't it just be a case of flashing the Nougat update I have download on my computer through ODIN or is it going to be a little more complex than that?
Thanks for any help
pixelens said:
Yup, you'll want the retus firmware I would think. I'm not sure if you have to unlock your bootloader, I did only because I was having issues with the Nougat update and thought that might be why but it didn't make a difference. I did get the Nougat update to install this morning though, tried it on another computer (stupid ADB). I did not root though, just unocked my bootloader and did the Rogers flash then the Noughat sideload.
I'd try it without unlocking the bootloader, if you get an error saying "can't read file <###>" when trying to adb sideload the Nougat update, try different ADB drivers or a different computer first before unlocking it. The couple people I know that have chimed in say they're unlocked as well but haven't indicated whether you need to be or not.
Click to expand...
Click to collapse
Ok, I'll try it without unlocking the bootloader and let you know what happens. Is your new version of nougat working properly (unrooted?)? Is there a difference between the nougat I am going to flash, and the OTA i'll get in a few weeks? (If you say there is no difference, I'll flash it ASAP without unlocking boot loader and let you know. Working daydream, playstore, and moto mods right?)
Again, thank you for helping a noob like me out.
Porcelainfog said:
Ok, I'll try it without unlocking the bootloader and let you know what happens. Is your new version of nougat working properly (unrooted?)? Is there a difference between the nougat I am going to flash, and the OTA i'll get in a few weeks? (If you say there is no difference, I'll flash it ASAP without unlocking boot loader and let you know. Working daydream, playstore, and moto mods right?)
Again, thank you for helping a noob like me out.
Click to expand...
Click to collapse
Seems to be working properly, at least from what I remember of Nougat on my 6P. I've had not force closes or other issues. I haven't tried Daydream apps out yet, but they did install fine (which they wouldn't under Marshmallow - got the "not compatible with your device" message). Play Store works fine, Incipio Battery Moto Mod works fine, haven't tested the others yet.
As far as what's different between this version and the OTA in a few weeks, I have no clue - but from what I gather this is a stock Nougat pulled from a device that got the OTA (don't quote me on that though hah). As for a few weeks, where are you hearing that? Can't get an answer out of Telus at all here and am wondering if maybe they're working on pushing it out as 7.1.x instead of 7.0. Who knows...
Let me know how it goes without unlocking the boot loader, having a ***** of a time trying to get it relocked lol (not the end of the world though).
pixelens said:
Seems to be working properly, at least from what I remember of Nougat on my 6P. I've had not force closes or other issues. I haven't tried Daydream apps out yet, but they did install fine (which they wouldn't under Marshmallow - got the "not compatible with your device" message). Play Store works fine, Incipio Battery Moto Mod works fine, haven't tested the others yet.
As far as what's different between this version and the OTA in a few weeks, I have no clue - but from what I gather this is a stock Nougat pulled from a device that got the OTA (don't quote me on that though hah). As for a few weeks, where are you hearing that? Can't get an answer out of Telus at all here and am wondering if maybe they're working on pushing it out as 7.1.x instead of 7.0. Who knows...
Let me know how it goes without unlocking the boot loader, having a ***** of a time trying to get it relocked lol (not the end of the world though).
Click to expand...
Click to collapse
Hey so I got it onto 7.0 finally. I ended up unlocking my bootloader. I didn't try without it, I read somewhere that it could cause a soft brick. Just wanted to say thanks to you guys that helped and Prfndhatrdofman (if he reads this) for his guide.
PS
holy ****ing ****. **** adb. **** android studio. **** drivers. And ****ing .zip extentions (took me like 30 minutes to put .zip on the end of Blur_Version...zip. Yes, I am an idiot).
Telus appears to have finally updated their update page for moto z nougat. Tentative date of December 19.
Forum post - Telus
Dawnhawk said:
Telus appears to have finally updated their update page for moto z nougat. Tentative date of December 19.
Forum post - Telus
Click to expand...
Click to collapse
LOL, of course they did!
---------- Post added at 04:26 PM ---------- Previous post was at 04:25 PM ----------
Porcelainfog said:
Hey so I got it onto 7.0 finally. I ended up unlocking my bootloader. I didn't try without it, I read somewhere that it could cause a soft brick. Just wanted to say thanks to you guys that helped and Prfndhatrdofman (if he reads this) for his guide.
PS
holy ****ing ****. **** adb. **** android studio. **** drivers. And ****ing .zip extentions (took me like 30 minutes to put .zip on the end of Blur_Version...zip. Yes, I am an idiot).
Click to expand...
Click to collapse
Cool. And ya re ADB haha
I have this canadian version of Huawei honor 5x, and I've been scouring to find answers to whether if am i able to flash a custom rom such as cyanogenmod or not. Can anyone please help me out with this; I've already made several post and it get unanswered. Sofar I've managed to unlock the bootloader, flashed twrp, and rooted it. When I tried installing CM 13 from a thread on this site, I always get the "error 7" and I tried deleting the 2nd line in the meta-inf and rezipping the rom and reflashing; results remain the same.
Here's more info on my phone:
Build#: KII-L05C654B330
EMUI 4.0
Hopefully this will answer your question.
You have a slight typo in your thread title, the Canadian version is the GR5.
I have the same phone as you, and am currently running Lineage OS which is the only one so far that the developers have stated they support all variants (except firmware with VOLTE). Even though they support all variants, thus far the zips they provide still have a line where they assert, so you need to edit out those lines in the updater script. But everything works including fingerprint.
Now, I am currently on chatr, so I do not know if LTE is enabled or not as chatr doesn't use LTE, just 3G. But I do have a backup of my ROM in case you need it. My Backup is from the Zoom Mobile version (Rogers subsidiary/MVNO) which means it doesn't have all the Rogers bloatware apps. But same firmware. Also, I did read here that you need to be running recent firmware so your firmware etc is up to date. I trust you ran all the Huawei updates prior?
Have a look at Lineage OS. It's awesome.
Chaos Storm said:
Hopefully this will answer your question.
You have a slight typo in your thread title, the Canadian version is the GR5.
I have the same phone as you, and am currently running Lineage OS which is the only one so far that the developers have stated they support all variants (except firmware with VOLTE). Even though they support all variants, thus far the zips they provide still have a line where they assert, so you need to edit out those lines in the updater script. But everything works including fingerprint.
Now, I am currently on chatr, so I do not know if LTE is enabled or not as chatr doesn't use LTE, just 3G. But I do have a backup of my ROM in case you need it. My Backup is from the Zoom Mobile version (Rogers subsidiary/MVNO) which means it doesn't have all the Rogers bloatware apps. But same firmware. Also, I did read here that you need to be running recent firmware so your firmware etc is up to date. I trust you ran all the Huawei updates prior?
Have a look at Lineage OS. It's awesome.
Click to expand...
Click to collapse
Hai bud , he mentioned that he is on emui 4 . So we have necessary proof that he is on marshmallow which we require to flash a rom on 5x:highfive:
And after thinking for a while , the last version (latest updates) have modem issues so custom roms may have stopped working for u due to this. I have solutions for u .
Hi Chaos Storm!
I'm fellow Canadian and just got GR5 on kijiji for my daughter.
Just couple quick questions: what ROM do you have now? (i.e. which one you recommend?)
Are there any tricks to flash? I'm having issue now - unlocked bootloader, flashed TWRP, SU. But when I try to boot into TWRP I get stock recovery. Can boot into TWRP only from TWRP app or ADB command...
Then I tried to flash LinOS 14 but got Error 7...
Thanks in advance!!!
Chaos Storm said:
Hopefully this will answer your question.
You have a slight typo in your thread title, the Canadian version is the GR5.
I have the same phone as you, and am currently running Lineage OS which is the only one so far that the developers have stated they support all variants (except firmware with VOLTE). Even though they support all variants, thus far the zips they provide still have a line where they assert, so you need to edit out those lines in the updater script. But everything works including fingerprint.
Now, I am currently on chatr, so I do not know if LTE is enabled or not as chatr doesn't use LTE, just 3G. But I do have a backup of my ROM in case you need it. My Backup is from the Zoom Mobile version (Rogers subsidiary/MVNO) which means it doesn't have all the Rogers bloatware apps. But same firmware. Also, I did read here that you need to be running recent firmware so your firmware etc is up to date. I trust you ran all the Huawei updates prior?
Have a look at Lineage OS. It's awesome.
Click to expand...
Click to collapse
Goldenmeadow said:
Hi Chaos Storm!
I'm fellow Canadian and just got GR5 on kijiji for my daughter.
Just couple quick questions: what ROM do you have now? (i.e. which one you recommend?)
Are there any tricks to flash? I'm having issue now - unlocked bootloader, flashed TWRP, SU. But when I try to boot into TWRP I get stock recovery. Can boot into TWRP only from TWRP app or ADB command...
Then I tried to flash LinOS 14 but got Error 7...
Thanks in advance!!!
Click to expand...
Click to collapse
Not sure what happened there. When you unlocked the bootloader did you reboot at least once to allow it to reset all data? I've had issues before if I unlock a bootloader then immediately flash something.
I know TWRP should ask you if you want to prevent stock recovery from being restored when you exit, always say yes. (It should only ask once)
Did you edit the updater-script in the Lineage install zip? You need to remove the first line or two where it says: "assert device" or something like that.
If all else fails, boot the phone into fastboot, flash twrp again, and make sure you "fastboot reboot recovery" so the unit doesn't have a chance to try and restore the factory recovery. Then try flashing your rom again.
Thanks for reply! With the help of fellow members I figured it out - I was holding POWER button TOO LONG And if that happens, phone goes into built in recovery... You suppose to let button go once you see first splash screen.
So it's all good!
Thanks!!!
Chaos Storm said:
Not sure what happened there. When you unlocked the bootloader did you reboot at least once to allow it to reset all data? I've had issues before if I unlock a bootloader then immediately flash something.
I know TWRP should ask you if you want to prevent stock recovery from being restored when you exit, always say yes. (It should only ask once)
Did you edit the updater-script in the Lineage install zip? You need to remove the first line or two where it says: "assert device" or something like that.
If all else fails, boot the phone into fastboot, flash twrp again, and make sure you "fastboot reboot recovery" so the unit doesn't have a chance to try and restore the factory recovery. Then try flashing your rom again.
Click to expand...
Click to collapse
Chaos Storm said:
Hopefully this will answer your question.
You have a slight typo in your thread title, the Canadian version is the GR5.
I have the same phone as you, and am currently running Lineage OS which is the only one so far that the developers have stated they support all variants (except firmware with VOLTE). Even though they support all variants, thus far the zips they provide still have a line where they assert, so you need to edit out those lines in the updater script. But everything works including fingerprint.
Now, I am currently on chatr, so I do not know if LTE is enabled or not as chatr doesn't use LTE, just 3G. But I do have a backup of my ROM in case you need it. My Backup is from the Zoom Mobile version (Rogers subsidiary/MVNO) which means it doesn't have all the Rogers bloatware apps. But same firmware. Also, I did read here that you need to be running recent firmware so your firmware etc is up to date. I trust you ran all the Huawei updates prior?
Have a look at Lineage OS. It's awesome.
Click to expand...
Click to collapse
Would I be able to get a copy of your ROM? I am with Cityfone (Rogers subsidiary), and am looking to network unlock, I can't seem to find my backup from when I started flashing custom ROMs
kenneth_82614 said:
Would I be able to get a copy of your ROM? I am with Cityfone (Rogers subsidiary), and am looking to network unlock, I can't seem to find my backup from when I started flashing custom ROMs
Click to expand...
Click to collapse
I will have a look. As things would be, I also need to restore my GR5 so I'll find it for both of us.
'Morning all,
I would really appreciate some advice on a couple of things about my MATE 10 Standard.
I bought this phone online from an online shop in Manchester around April last year. I got the Mate 10 ALP-AL00 which was rebranded by the shop to ALP-L29. Its currently on 8.0.0.136(C636).
My aim is to unlock and root my device with Magisk and of course get TWRP working as well. From what I have read, there seems to be quite a high level of success but there are still things i'm not sure about. Huawei phones are a bit fragile, software wise and can easily brick. Plus, the fact that the phone itself is the Chinese variant, I don't expect any kind of help from Huawei Customer services if it does get bricked. Hence i'm being very cautious. (Past bad experience with a Honor 9 STF-AL10).
1. my phone is on ALP-L29 8.0.0.136(c636) 1 June security patch. Bootloader Version: Chipset-boston8.0.0.001(02M8)_FASTBOOT
I've refused all attempts to upgrade via OTA as I've read about the 01 and 02 bootloaders fiasco.
2. I've got an unlock code from DC-Unlocker, but I've not tried it yet. I never was able to get a code from Huawei's official site due to the fact that it was rebranded, which lead me to believe the online shop I bought it from used Funky to rebrand. (Apparently, FunkyH messes up something on the bootloader thus preventing unlocking with official unlockcode. AFIK). BUT, the info displayed by phone is exactly the same as what is on the box, imei 1&2, S/N, device Id code, etc...
Basically my questions are:
With the current firmware version I'm on, can I unlock my bootloader, install the unofficial TWRP then root with Magisk? AFIK its on xloader 01.
Is there anything to look out for when doing the above?
and, If I do a full backup immediately after installing TWRP, can this be used to recover the phone if it fails to boot up for any reason.?
I'm not really interested in being on the latest EMUI version etc, just wan't a phone with full root and an easy method to unbrick it.
thank you all,
ums1405 said:
'Morning all,
I would really appreciate some advice on a couple of things about my MATE 10 Standard.
I bought this phone online from an online shop in Manchester around April last year. I got the Mate 10 ALP-AL00 which was rebranded by the shop to ALP-L29. Its currently on 8.0.0.136(C636).
My aim is to unlock and root my device with Magisk and of course get TWRP working as well. From what I have read, there seems to be quite a high level of success but there are still things i'm not sure about. Huawei phones are a bit fragile, software wise and can easily brick. Plus, the fact that the phone itself is the Chinese variant, I don't expect any kind of help from Huawei Customer services if it does get bricked. Hence i'm being very cautious. (Past bad experience with a Honor 9 STF-AL10).
1. my phone is on ALP-L29 8.0.0.136(c636) 1 June security patch. Bootloader Version: Chipset-boston8.0.0.001(02M8)_FASTBOOT
I've refused all attempts to upgrade via OTA as I've read about the 01 and 02 bootloaders fiasco.
2. I've got an unlock code from DC-Unlocker, but I've not tried it yet. I never was able to get a code from Huawei's official site due to the fact that it was rebranded, which lead me to believe the online shop I bought it from used Funky to rebrand. (Apparently, FunkyH messes up something on the bootloader thus preventing unlocking with official unlockcode. AFIK). BUT, the info displayed by phone is exactly the same as what is on the box, imei 1&2, S/N, device Id code, etc...
Basically my questions are:
With the current firmware version I'm on, can I unlock my bootloader, install the unofficial TWRP then root with Magisk? AFIK its on xloader 01.
Is there anything to look out for when doing the above?
and, If I do a full backup immediately after installing TWRP, can this be used to recover the phone if it fails to boot up for any reason.?
I'm not really interested in being on the latest EMUI version etc, just wan't a phone with full root and an easy method to unbrick it.
thank you all,
Click to expand...
Click to collapse
You could just test the code in fastboot: fastboot oem unlock UNLOCKCODE
If the code is incorrect, for some reason, it will say Password incorrect. Else it will bring you to the yes/no unlock screen on phone. DCs unlock code should always work as it doesn't need the correct imei/imei2/sn/product combo when generating unlock code.
There's no real point in staying on xloader 01 anymore, every update (except a few unapproved firmware) after 02 started appearing has been 02.
Downside is that you can't downgrade, but you could replace fastboot in latest fw with the one from may/June and you'd have DC working again. But there's also service firmware available for free on androidhost.ru which can be used if phone should brick. There's also testpoint (only one person has tested this) which can be used to downgrade to any firmware (even xloader 02 to 01).
Before unlocking, backup everything as unlocking will wipe data.
ums1405 said:
'Morning all,
I would really appreciate some advice on a couple of things about my MATE 10 Standard.
I bought this phone online from an online shop in Manchester around April last year. I got the Mate 10 ALP-AL00 which was rebranded by the shop to ALP-L29. Its currently on 8.0.0.136(C636).
My aim is to unlock and root my device with Magisk and of course get TWRP working as well. From what I have read, there seems to be quite a high level of success but there are still things i'm not sure about. Huawei phones are a bit fragile, software wise and can easily brick. Plus, the fact that the phone itself is the Chinese variant, I don't expect any kind of help from Huawei Customer services if it does get bricked. Hence i'm being very cautious. (Past bad experience with a Honor 9 STF-AL10).
1. my phone is on ALP-L29 8.0.0.136(c636) 1 June security patch. Bootloader Version: Chipset-boston8.0.0.001(02M8)_FASTBOOT
I've refused all attempts to upgrade via OTA as I've read about the 01 and 02 bootloaders fiasco.
2. I've got an unlock code from DC-Unlocker, but I've not tried it yet. I never was able to get a code from Huawei's official site due to the fact that it was rebranded, which lead me to believe the online shop I bought it from used Funky to rebrand. (Apparently, FunkyH messes up something on the bootloader thus preventing unlocking with official unlockcode. AFIK). BUT, the info displayed by phone is exactly the same as what is on the box, imei 1&2, S/N, device Id code, etc...
Basically my questions are:
With the current firmware version I'm on, can I unlock my bootloader, install the unofficial TWRP then root with Magisk? AFIK its on xloader 01.
Is there anything to look out for when doing the above?
and, If I do a full backup immediately after installing TWRP, can this be used to recover the phone if it fails to boot up for any reason.?
I'm not really interested in being on the latest EMUI version etc, just wan't a phone with full root and an easy method to unbrick it.
thank you all,
Click to expand...
Click to collapse
U can check unlock code by dialing *#*#2846579#*#* and goto veneer informations>Verify key> Input boot unlock code. If it is correct it will show Success in toast notification.
Hi all,
Appologies for late reply as I've been lumbered with bored kids on their midterms plus a backlog of work.
I've verified the key I go from DC, and success it got verified OK.
Now to prepare and read through again all the important bits for TWRP nstallatuon and magisk.
Quick question, is there a way or method that is 100% foolproof to recover your device via unofficial TWRP.
Noobish questions, I know but please bear with me.
Thanks for your time and patience and best regards....
ums1405 said:
Hi all,
Appologies for late reply as I've been lumbered with bored kids on their midterms plus a backlog of work.
I've verified the key I go from DC, and success it got verified OK.
Now to prepare and read through again all the important bits for TWRP nstallatuon and magisk.
Quick question, is there a way or method that is 100% foolproof to recover your device via unofficial TWRP.
Noobish questions, I know but please bear with me.
Thanks for your time and patience and best regards....
Click to expand...
Click to collapse
There are a few methods to recover your device from an eventual soft-brick, i wouldn't call them foolproof, not because are hard to follow/use, but only because it seem that no matter how easy a guid, a method or a tool is, there are still some people that fail to do it properly.
If your only goal is to install TWRP and Magisk, my advice is to read a bit on these forums and you shoul be fine.
Another advice, that people seem to ignore completely after they acquire root, is to backup your partitions. I recommend Partitions Backup (by Wanam) from Playstore. Backup all partitions beside system, vendor and userdata then transfer the backup on PC, Cloud, etc.
Good luck!
debbuger said:
U can check unlock code by dialing *#*#2846579#*#* and goto veneer informations>Verify key> Input boot unlock code. If it is correct it will show Success in toast notification.
Click to expand...
Click to collapse
Thanks, that's worth the entrance fee alone as they say.
Pretoriano80 said:
There are a few methods to recover your device from an eventual soft-brick, i wouldn't call them foolproof, not because are hard to follow/use, but only because it seem that no matter how easy a guid, a method or a tool is, there are still some people that fail to do it properly.
If your only goal is to install TWRP and Magisk, my advice is to read a bit on these forums and you shoul be fine.
Another advice, that people seem to ignore completely after they acquire root, is to backup your partitions. I recommend Partitions Backup (by Wanam) from Playstore. Backup all partitions beside system, vendor and userdata then transfer the backup on PC, Cloud, etc.
Good luck!
Click to expand...
Click to collapse
Thank you for taking the time to put me right.
I'll go back to your Unofficial TWRP post and go through it A to Z.
Hi all,
thanks for the all the help with my issues.
I've unlocked the bootloader and even got the unofficial TWRP working.
I've also backup my partitions and kept them on my PC and Cloud.
Now the problem I'm having is with Magisk. I can't seem to get it installed.
When I flashed it in TWRP I got an error that /system and /Vendor are not mounted. Mounted them manually and retried the instalation and it worked. When I check the APP, it shows as not installed.
I've tried magisk 16.0 and 17.1 both failed to install. Tried the one in the HWOTA zip and it failed too.
Anyone please advise...
ums1405 said:
Hi all,
thanks for the all the help with my issues.
I've unlocked the bootloader and even got the unofficial TWRP working.
I've also backup my partitions and kept them on my PC and Cloud.
Now the problem I'm having is with Magisk. I can't seem to get it installed.
When I flashed it in TWRP I got an error that /system and /Vendor are not mounted. Mounted them manually and retried the instalation and it worked. When I check the APP, it shows as not installed.
I've tried magisk 16.0 and 17.1 both failed to install. Tried the one in the HWOTA zip and it failed too.
Anyone please advise...
Click to expand...
Click to collapse
Which device and build do you have? First uninstall Magisk with Magisk Uninstaller, by flashing it with TWRP. Then try again to install latest Magisk.
And btw, your partitions backup is not completely done, not untill you install Magisk and use that app, Partitions Backup!
Solved!
I ran the magisk_uninstall twice then ran the magisk.bat again.
Got 16.0 to work, now updated to 17.1 via the app and all is good.
worked like a CHARM.
full root & TWRP + Magisk 17.1 installed
Christmas has come early for me!
Now to way the pros and cons of updating to xloader2 (infact anything above B136)
Much respect to all and best regards.....
:good:
ums1405 said:
Solved!
I ran the magisk_uninstall twice then ran the magisk.bat again.
Got 16.0 to work, now updated to 17.1 via the app and all is good.
worked like a CHARM.
full root & TWRP + Magisk 17.1 installed
Christmas has come early for me!
Now to way the pros and cons of updating to xloader2 (infact anything above B136)
Much respect to all and best regards.....
:good:
Click to expand...
Click to collapse
Well, you can't stay on xloader01 forever, at least not if you want to update your device.
The cons is that once on xloader02, you can't go back to xloader01.
Pretoriano80 said:
Which device and build do you have? First uninstall Magisk with Magisk Uninstaller, by flashing it with TWRP. Then try again to install latest Magisk.
And btw, your partitions backup is not completely done, not untill you install Magisk and use that app, Partitions Backup!
Click to expand...
Click to collapse
All sorted now boss......I'm about to do the backups now.
I'm presented with heaps of partions, anyone in particular or just back the whole lot?
ums1405 said:
All sorted now boss......I'm about to do the backups now.
I'm presented with heaps of partions, anyone in particular or just back the whole lot?
Click to expand...
Click to collapse
All except userdata, system and vendor (these are large and can be found on stock firmwares, so can be skipped).
all done.
just restoring apps and data now.
if I was going to update to x2loader FW how would i do that?
Thanks again pal.
ums1405 said:
all done.
just restoring apps and data now.
if I was going to update to x2loader FW how would i do that?
Thanks again pal.
Click to expand...
Click to collapse
You can use HWOTA8 or HuRUpdater! Beware that if you update to a firmware with patch 01, simply flashing Magisk won't work anymore and you will have to patch the stock ramdisk with Magisk Manage (keep encryption and preserve dm_verity must be enabled) , then flash the patched image with fastboot.
Hey everyone,
So! I bought a Sony Xperia 1 (J8110-2019) phone from someone on Facebook Marketplace at a very solid price of £250 (RRP is still £850 in the UK) due to the seller describing it as 'in retail demo mode' so they lowered the price. I jumped the gun thinking I was getting a solid deal and just stupidly assumed it to be a feature I could just disable with *#*#73556673*#*#- me believing I was some insane developer with mad coding skills where in realityI had once flashed and rooted my Xperia XZ back in 2016. [Insert 'Hackerman' meme]
Yes... I am fully aware I'm a complete idiot for not doing a full assessment on the phone and am now having to learn a very important lesson from this situation!!
It seems to have a Store Front firmware installed and unsure what firmware to download and flash? I've tried some of the official stock ROMs from XperiFirm and it just continues to boot into constant 10-second cycles of demo videos making general functionality like phone calls pretty much impossible. without interruption. I've tried Customized and UK Service Provider Firmware such as EE and O2 but it always goes back into Store mode.
I was hoping if anyone would have or could elaborate on how to make an executable system flash zip for a 2019 Xperia 1? When I extract files from XperiaFirm ROMS (FTF,ZIP,SIN etc), I don't seem to get any META-INF files and thus cant make the proper .zip that TWRP needs to successfully flash a new repacked stock ROM? It always ends in a boot loop."
Here are some key points to hopefully give you some background:
I've installed TWRP successfully and have attempted to use 3 official firmware to flash whilst in recovery but have been unsuccessful each time with 'Invalid .ZIP format'. I've only a few times got booted whilst bundling together FTF files via Flashtool and doing it that way round but only ever seems to solve half the problem
I can't use the SinExtract feature in Flashtools as the SIN file errors as not being supported yet to use different file versions.
I can't use PRFCreator as it errors as the FTF file being unsupported (Due to it being new I assume)
I attempted to create my own META-INF>Updater-script but am unable to identify what partition my phone would use for mounting on "/dev/block". I only ever seem to get MANIFEST.MF from the files and nothing else. On my XZ I think I used something like:
(package_extract_file("boot.img", "/dev/block/mmcblk0");
package_extract_file("system.sin","/dev/block/platform/msm_sdcc.1/by-name/system");
Click to expand...
Click to collapse
I have been able to install Magisk for rooting and verified.
I have used Minimal ADB and Fastboot to install programs like TWRP, SuperSu, Magisk but have never attempted, nor would I even know how to wipe my phone completely and install a clean stock ROM - is this possible?
All drivers, software, and systems are correct and up to date (as far as I am aware)
Would installing the' Service Exchange Firmware' be recommended (if I ever make it that far!) due to it being StoreFront?
I checked the IMEI number to see if it was blacklisted/blocked and it's all good. Not lost or stolen.
Thank you for your time to read and wallow in my woes with me my lovelies! Any help would be GREATLY appreciated you magnificent beasts! x
Bump x
...
the last chance... :good: