Related
My device is European L04, currently running North Africa release (the earliest Marshmallow build uploaded) - L04_2016_0316_0900 (B820)
I'd like to unlock the bootloader and root my Honor 6. I've never done it (on this particular device), because I've read enough here to know it's slightly more risky than on other devices, especially when you plan to update the stock rom soon, so I preferred to wait until I have the last important update the device is likely to receive - Android 6.0.
What I want to know (some of the answers are in the topics which I listed below):
MultiTool - I've seen reports of bricks when using MultiTool with EMUI4/Marshmallow - why does it happen? My understanding is that MultiTool is a bundle of adb/fastboot and some recovery images for older Android versions, so my theory is that instead of using MultiTool, I should simply get the proper recovery for Marshmallow and flash it manually with fastboot, right?
unlocking bootloader, rooting, flashing recovery - I think I understand the process; in a nutshell: 'fastboot oem unlock X', 'fastboot flash recovery imagename.img', then flash the proper SU.zip in recovery. Where do I find the code, the Marshmallow recovery image, the SU.zip file?
will recovery backup in TWRP work without any problems?
what is the procedure to go back to stock completely after rooting? Unroot, (then wipe if it's needed?) so I am able to safely flash stock firmware again (since, from what I know, flashing stock on a rooted phone makes itself brick permanently, right? or is it just a soft-brick and it can be fixed?)
is there anything else I should know before proceeding?
What I found so far:
http://forum.xda-developers.com/showpost.php?p=66615082&postcount=502 - two recovery images, TWRP and another one (stock?) for the Marshmallow release
http://forum.xda-developers.com/honor-6/general/honor6-multi-tool-t2963060/page50 some rooting instructions for the L02 beta, see posts 494 and 498; no idea whether this is applicable to final Marshmallow or L04 at all
http://forum.xda-developers.com/honor-6/general/huawei-honor-6-plus-unlock-bootloader-id-t3357259 an app to get the unlock code, seems a bit shady to me though on the first glance
http://forum.xda-developers.com/honor-6/development/honor-6-rooting-method-t2962795 alternate methods for bootloader (through a website or by email), in case the app won't work; also, detailed instructions on unlocking and rooting
Basically, I need to know whether my procedure is more or less right before I proceed. I think the information is quite hard to find and the risks are quite high, so I'd like to make a promise - when I'm done rooting it and I know the correct process, I'm going to make a "Update to Marshmallow, unlock, root" how-to thread for all the people that will need it in the future.
Another two questions...
1. Where do I get proper SuperSU for Marshmallow? I get a boot loop (yeah, I know I have to wait and I did, but it's a pretty obvious bootloop from watching the logcat content, and nothing new happens...) after flashing http://download.chainfire.eu/supersu-stable (2.65).
2. I have unlocked my bootloader and installed TWRP, so recovery and fastboot are functional. I didn't make a backup before flashing the zip and now I'm in a bootloop. How do I restore working Marshmallow? I assume I can either beg somebody to upload a TWRP backup for my H60-L04, or somehow flash the stock over what I have now. Can I simply use manual update from SD? Can I somehow flash Marshmallow again with fastboot? I'm too scared of bricking my device right now so I guess I'll brace myself for a few days without a phone until somebody helps me :/
I just flashed the Marshmallow release I had before the bootloop (I used Huawei Update Extractor and flashed boot, cust, system and recovery with fastboot; then open up Huawei recovery and factory reset for good measure, I'm not sure it was even needed) and the device is working. I'll restore my stuff, install TWRP, make a backup then try out your ZIP. Thanks
edit: thanks again - your zip works indeed. So after the initial hurdles, now I've got working root and a reasonable way of restoring in case I screw something up along the way.
Before making a new topic with the tutorial I have a few more questions.
First of all, why exactly we weren't supposed to update the rooted devices? I'm not currently interested in OTAs (it's pretty obvious that it needs a functional Huawei recovery, and you need to unroot cause an update can make a mess in a rooted system, making it bootloop for example), but can we flash extracted images with fastboot on rooted devices? Logically, we should be able to... How about sdcard update method?
Can we flash Marshmallow on Kitkat? (fastboot, sdcard, local update methods?) Or do we need to update to Lollipop along the way?
Can I flash stock roms in general (evenbetween different Android versions) by using fastboot with {boot, cust, recovery, system} images only? There's a lot of images that you can extract with Huawei Update Extractor - why there's so many if they're not needed?
So i was thinking that we dont have any thread to this device so i made this.
Can someone help me to unlock bootloader to this beatiful device. i cant get it open.
when im trying to unlock it with the code(adb or flashtool) it gives me error saying "command not allowed" i have tried many times and re installing the drivers and tried different os and nothing helps.
tried to make some research from google etc like stackflow but just cant find nothing. i have the imei right and everything. and tried to unlock with the sonys dev site. and i did out the device as e4g or e4. nothing
command not allowed
to my device xperia e5 f3311 but it also writes in the service menu * # * # 7378423 # * # * service info\configuration is line "rooring status:" bootloader unlock alloved: yes
I'm now looking for a custom recovery for my xperia e5 f3311 and install an supersu.zip and rooting proces is complete but
GameboyZA said:
to my device xperia e5 f3311 but it also writes in the service menu * # * # 7378423 # * # * service info\configuration is line "rooring status:" bootloader unlock alloved: yes
I'm now looking for a custom recovery for my xperia e5 f3311 and install an supersu.zip and rooting proces is complete but
Click to expand...
Click to collapse
Solved the command not allowed proplem . just go in your phone top the developer settings and enable the oem thing. and make sure that usb debugging is on. thats it! hope it helps you out
pottu221 said:
Solved the command not allowed proplem . just go in your phone top the developer settings and enable the oem thing. and make sure that usb debugging is on. thats it! hope it helps you out
Click to expand...
Click to collapse
pottu221 thanks....
Hey, does the root works with your method?
If this work how do you proceed for that (Install CWM and install super su ?)?
Thanks
toinedu27 said:
Hey, does the root works with your method?
If this work how do you proceed for that (Install CWM and install super su ?)?
Thanks
Click to expand...
Click to collapse
aint gonna happen. none of the tools doesnt support mtk 6735 with android 6.0. so we should have rooted phone to get recovery.img so i think that our only hope is to wait that kingroot or something will work on our device
You don't need to wait for the Kingroot as it is not possible to root locked bootloader with drm-verify enabled.
What You need is to create recovery.img to flash on /recovery partition (it should exist, as Sony started to adding them before E5).
There are autotools for MTK devices (they create recovery for specific SoC/CPU not model), but I'm not sure if it is safe to flash on Sony firmware as it is different than generic firmware used on standard (Chinese) devices.
Than using it should be possible to root it by flashing SuperSU zip.
ch3mn3y said:
You don't need to wait for the Kingroot as it is not possible to root locked bootloader with drm-verify enabled.
What You need is to create recovery.img to flash on /recovery partition (it should exist, as Sony started to adding them before E5).
There are autotools for MTK devices (they create recovery for specific SoC/CPU not model), but I'm not sure if it is safe to flash on Sony firmware as it is different than generic firmware used on standard (Chinese) devices.
Than using it should be possible to root it by flashing SuperSU zip.
Click to expand...
Click to collapse
The proplem is that cant get the recovery.img out from anywhere :/
So there's still no way to root this phone ? I really need to install Viper4Android on it ^^
Hey,
I saw the "Dirty Cow" fault on the Linux systems.
I also saw that fault should works on Android, I will see if I can root my device with that
I will be back soon
toinedu27 said:
Hey,
I saw the "Dirty Cow" fault on the Linux systems.
I also saw that fault should works on Android, I will see if I can root my device with that
I will be back soon
Click to expand...
Click to collapse
Have you managed to root your device?
I've been trying to make a working cwm or twrp recovery, but I need to extract the stock recovery.img to do so.
And that requires root.
Can you send me a dm if you managed to root it with the dirty cow exploit? Thanks.
Hey,
I didn't find time to try this exploit but the thing I should do is just install the package dirty cow for android (released on github) and after use the "run-as" command for install super su...
I'm not certain that can work but it should if Sony didn't correct this fault, else I will always can recover via FlashTool to a factory version.
toinedu27 said:
Hey,
I didn't find time to try this exploit but the thing I should do is just install the package dirty cow for android (released on github) and after use the "run-as" command for install super su...
I'm not certain that can work but it should if Sony didn't correct this fault, else I will always can recover via FlashTool to a factory version.
Click to expand...
Click to collapse
Can you check if it works?
I just need a confirmation that you got your phone rooted safely with that fault, then I'll start working on twrp and hopefully we'll have our first rom on this device soon.
But since I recently bought this phone and I can't get my pc to work (for flashtool, in case anything goes wrong), I need someone to test if the dirty cow fault still works on our devices.
If you have time, please check it out.
Hey,
I try but I need to install a tool called "NDK" for the "NDK-Build" command
I'm progressing
I am waiting for a miracle. I also installed Kingroot and in it I found that in 1497 people have applied for root so that we are not alone. ?
Hey there,
I've managed to set up fastboot and finding alternative drivers to work on our device.
Finally, I can now use adb with full fastboot access.
I've also managed to unlock my bootloader, so now I will have to find a recovery that will work on our mediatek 6735 chipset, build based on API 23 (marshmallow).
If necessary, I can try to port cwm from some different device.
When we have a working recovery, we can most likely flash anything, so I might make a prerooted version of the stock firmware.
Expect the first development for this device any soon.
Edit1: Due to health reasons, I might have to delay this for a week, my appologies.
I'm sorry I don't have the time to exploit the Dirty Cow fault (lot of Home Work) and I don't have the knowledges that I need :/
I hope @mrmarvin_16 will got the root access (Thanks a lot )
Hello. Excuse me for my English writing through translayte google. I am writing with Russian Forum 4PDA. We were able to unlock bootloader is a link to my post on this forum 4pda.ru/forum/index.php?showtopic=753685&st=160#entry54277601 . And TWP recovery we also gathered, the download link yadi.sk/d/Vq0jgohxymPCG . Problem Only here we do not know how to sew it into the phone itself.
I flash recovery but i dont have boot to recovery menu
And as you flashed? I just have all the time an error in piercing through ADB.
[Guide] XT1575 Update To NPH25.200-22 Nougat After Modifying Your System & Re-Root
THIS GUIDE IS NOW DEPRECATED. THERE IS NO NEED ANYMORE TO GO THROUGH THE UPDATING PROCESS AS THERE IS A FULL NOUGAT FACTORY IMAGE AVAILABLE (Build NPH25.200-22). FIRMWARE AVAILABLE HERE: https://forum.xda-developers.com/moto-x-style/general/xt1575-moto-x-pure-edition-factory-t3704142 BE SURE TO THANK @acejavelin FOR TRACKING DOWN THE FIRMWARE PACKAGE FOR US.
Notes:
-YOU ATTEMPT THIS AT YOUR OWN RISK IF YOU FLASHED ANY FIRMWARE PREVIOUSLY NOT FOR THE XT1575 US VERSION
-This guide will have 2 parts. 1 for those that kept their systems read only/systemless, and 1 for those that did not.
-Whether you live booted TWRP or Installed TWRP, if you chose to allow system modifications your OTA will likely fail (you'll need part 2).
-Restoring a TWRP backup will not work and will cause an OTA to fail due to having to allow system write access in TWRP - You Need Part 2.
-This guide assumes you have basic ADB knowledge and already know what fastboot is and how it works.
-Thanks to @gokart2 for the OTA and @acejavelin for the return to stock guides
Part 1: Those That Tweaked Systemlessly Currently On 24.49-18-16 (Will only work if you kept TWRP read only/used systemless root):
1: Disable & Remove systemless Xposed within Magisk Manager and all other Magisk modules. Reboot and wait for Art cache to rebuild.
2: Remove any adblock hosts within your adblock app if installed, or any other root level system altering apps like Greenify (don't worry, you'll get them back).
3: Remove Magisk by booting into TWRP and flashing the current Magisk Removal zip. Reboot.
4: For systemless SuperSu you need to consult their thread as I do not use it. (I'll update this if someone knows the correct process).
5: ADB reboot bootloader and fastboot flash the stock recovery. Latest MM recovery links at the bottom of this post. (rename file to recovery.img).
6: Move the OTA Blur_Version.24.231.16.clark_retus.retus.en.US.zip to the root of your internal sd card (NOT in a folder). File links at the bottom of the post. Thanks @gokart2
7: ADB reboot recovery, when "no command" is listed, hold power + tap volume up then release to access recovery options. Choose "apply update from phone storage". Choose the file and wait for the flash. It's a large update so be patient (about 10-20min). Choose reboot manually in recovery after flash succeeds. Enjoy Nougat!
8: For root you can go ahead and flash TWRP again or live boot TWRP (fastboot boot twrp.img) and then flash Magisk 14.0 from TWRP. Works perfectly.
Part 2: Those That Have Done Everything - TWRP Write Access, Custom Roms, On Older Firmware, Etc (XT1572 Build Flashers Do This At Their Own Risk):
1: Flash the latest full factory image available (24.49-18-8) available here: https://forum.xda-developers.com/mo...de-return-to-stock-relock-bootloader-t3489110. Thank @acejavelin for the thread while your at it. Follow the directions in that guide, it's well detailed and accurate - however read my notes just below first:
NOTES:
-Omit the "fastboot oem lock begin" & "fastboot oem lock" commands to remain bootloader unlocked.
-Omit the "fastboot erase userdata" command if you want to dirty flash and keep all of your data. I recommend clean, you can always root & restore each apps data with Titanium after the Playstore installs everything.
-The "fastboot oem fb_mode_set" instead of "fastboot oem lock begin" & "fastboot oem fb_mode_clear" instead of "fastboot oem lock" I've found to be unnecessary if staying unlocked. Your choice.
-The "fastboot flash partition gpt.bin" & "fastboot flash bootloader bootloader.img" commands will likely fail due to version mismatches. This is ok.
-The "fastboot flash modem NON-HLOS.bin" tends to fail too. For this, just run the command again until it succeeds.
2: After flashing 24.49-18-8 take the OTA to 24.49-18-16. Reboot. OTA zip provided below if you prefer to sideload.
3: Either install the 7.0 OTA the normal way via the update center or just side load it using the directions above. I recommend side loading due to the file size being very close to 1GB.
4: For root you can go ahead and flash TWRP again or live boot TWRP (fastboot boot twrp.img) and then flash Magisk 14.0 from TWRP. Works perfectly!
For Xposed, See My Guide Here: https://forum.xda-developers.com/showpost.php?p=74014516&postcount=96
Stock MM 24.49-18-16 Recovery: https://mega.nz/#!aZpC2RzQ!Fy3GTo_XYPjB1lwuHffCUUERuvnsyvON3kS8kMJ9Cm8
Stock MM 24.49-18-16 Recovery Mirror: https://drive.google.com/file/d/0BxxRfNko9QDKNS1NdnAyZVp6dVU/view?usp=sharing
24.49-18-8 OTA to 24.49-18-16: https://mega.nz/#!yZx2FLzR!cWfKIAYe5VyuadLI55UNHJvwWU98CXUi1g0DO1pDoKg
NPH25.200-22 OTA: https://mega.nz/#!HVhWWLxK!h-8G3vO3Sye_YwypyIJyWb2_79Ow34vNiDnMl2Q8uJg
NPH25.200-22 OTA Mirror: https://drive.google.com/file/d/0B3gPYUZ4nRLwOHJKQnNYczNEMHc/view?usp=sharing
MD5 for NPH25.200-22 OTA: 74d1a4b135200661cc4efd248f99ce33
Stock 7.0 NPH25.200-22 Recovery: https://mega.nz/#!TNoHQAjI!5U2w4p_G7pHlW6Mak7LqFR_PeWUDpSLc7S3OiUs_Qf8
Alrighty. I got back to stock 6.0 with the 18-16 update. I couldn't get the OTA via the system update, so I tried doing it via ADB. That threw up a "status 7 error". I then copied the file to my internal storage and selected update via SD Card in recovery. It hung on "Patching System Files" for a while, but in the end it moved on and worked fine. Thanks for the awesome guide!
Thread updated with downloads for the 24.49-18-8 OTA to 24.49-18-16 zip.
I exctracted the 7.0 Stock recovery to replace if you decide to flash TWRP and want to go back to the stock recovery for future updates (HAHAHA yeah right!). Download link in OP. The 7.0 Recovery is different than the MM recovery. They are not interchangeable. Don't flash the 7.0 recovery on MM.
Question... can those of us who are rooted, custom roms, with TWRP, not just flash a stock unrooted TWRP backup from here: https://forum.xda-developers.com/moto-x-style/development/pure-firmware-tuff-wip-t3224833
Then, flash the stock recovery like it says... and take the update? Isn't that easier than this method?
Bwangster12 said:
Question... can those of us who are rooted, custom roms, with TWRP, not just flash a stock unrooted TWRP backup from here: https://forum.xda-developers.com/moto-x-style/development/pure-firmware-tuff-wip-t3224833
Then, flash the stock recovery like it says... and take the update? Isn't that easier than this method?
Click to expand...
Click to collapse
It probably won't work. Once TWRP is given write access to your system (which is required to flash a full rom or restore a backup) any OTA's will fail. Plus any modem/bluetooth mismatches will cause a failure too. Fastboot flashing a stock image is really very easy & pretty much a guarantee that everything will work properly. However, if your able to get it to work, please let us know...though I don't think it will.
annoyingduck said:
It probably won't work. Once TWRP is given write access to your system (which is required to flash a full rom or restore a backup) any OTA's will fail. Plus any modem/bluetooth mismatches will cause a failure too. Fastboot flashing a stock image is really very easy & pretty much a guarantee that everything will work properly. However, if your able to get it to work, please let us know...though I don't think it will.
Click to expand...
Click to collapse
Once I do this, I can just reinstall TWRP and Magisk, backup the stock 7.0 and if I ever decided, just flash a custom rom later on?
hey thanks for the help on this one. I was so worried because I got stuck on th May security update OTA-wise.
question: I messed with the LatAm version of Nougat, so when I tried to re-lock the bootloader, it game the preflash error.
After this proper update flash, is there a way to run the bootloader CMD to just re-lock the bootloader?
Here's the recovery before the 7.0 one, just incase.. Was bored. Ok, I won't lie....didn't see u posted the 7.0 recovery....lol.:good::highfive:
Bwangster12 said:
Once I do this, I can just reinstall TWRP and Magisk, backup the stock 7.0 and if I ever decided, just flash a custom rom later on?
Click to expand...
Click to collapse
Yup. TWRP flashes and works, magisk v14 works, and so far systemless xposed api24 is working.
EsteBandido4444 said:
hey thanks for the help on this one. I was so worried because I got stuck on th May security update OTA-wise.
question: I messed with the LatAm version of Nougat, so when I tried to re-lock the bootloader, it game the preflash error.
After this proper update flash, is there a way to run the bootloader CMD to just re-lock the bootloader?
Click to expand...
Click to collapse
What is everyone's fascination with relocking the bootloader? You do not need to relock your bootloader. You cannot relock the bootloader unless all your system partitions match. Use my part 2 section. Read the notes, skip the bootloader lock commands. Leave your bootloader unlocked, get up and running on nougat, then you can issue the lock commands if you really want a locked bootloader.
How exactly do you flash the 24.49-18-16 OTA? I'm stuck at this part
EDIT nevermind didn't read lol
Amp699435 said:
How exactly do you flash the 24.49-18-16 OTA? I'm stuck at this part
Click to expand...
Click to collapse
Copy the file to the root of your internal storage. Reboot into recovery. Hold power = volume up & release to access menu options. Choose apply update from storage. Select the OTA.zip package and let it install. (Directions are clearly written in OP.)
Does it matter which version you're on? I'm currently on MPSH24.49-18-4 with the May 2016 security update.
GrandAdmiral said:
Does it matter which version you're on? I'm currently on MPSH24.49-18-4 with the May 2016 security update.
Click to expand...
Click to collapse
Part 1 implies that you are on MPSH24.49-18-16 (dec), for part 2 - no it doesn't matter. Go ahead and start with the full firmware available MPSH24.49-18-8 and follow the steps from there.
annoyingduck said:
Part 1 implies that you are on MPSH24.49-18-16 (dec), for part 2 - no it doesn't matter. Go ahead and start with the full firmware available MPSH24.49-18-8 and follow the steps from there.
Click to expand...
Click to collapse
Ok. Was going to have to follow option two anyway because of how I rooted...
Now I also take it that flashing Magisk is recommended, but optional?
GrandAdmiral said:
Ok. Was going to have to follow option two anyway because of how I rooted...
Now I also take it that flashing Magisk is recommended, but optional?
Click to expand...
Click to collapse
Root is completely up to you. It's noted so users know that TWRP/Root are working. My logic with any XDA thread is that your bootloader is unlocked and you want root, but that's me...
annoyingduck said:
Root is completely up to you. It's noted so users know that TWRP/Root are working. My logic with any XDA thread is that your bootloader is unlocked and you want root, but that's me...
Click to expand...
Click to collapse
Gotcha. I know I'm going to root again, but I've never used Magisk before so I wasn't sure of that piece.
annoyingduck said:
Part 1 implies that you are on MPSH24.49-18-16 (dec), for part 2 - no it doesn't matter. Go ahead and start with the full firmware available MPSH24.49-18-8 and follow the steps from there.
Click to expand...
Click to collapse
I am running Dirty Unicorns right now and when i looked up what I'm on in fastboot, it showed MPSH24.49-18-16. Would I just follow part 2 and use MPSH24.49-18-8 or something? I thought I had to use at least the version I'm on or newer.
GrandAdmiral said:
Does it matter which version you're on? I'm currently on MPSH24.49-18-4 with the May 2016 security update.[/QUOTE
Your issue is that TWRP has modified your
System, any restoring of the stock rom will fail to update. So yes, you'll need to go through part 2 and downgrade and work your way back up.
Click to expand...
Click to collapse
I downloaded the zip (it took a while).
Restored to stock like 3 different ways but still hit a road block. I went the adb sideload route but got status error 7 because my build fingerprint wasn't correct. I tried searching for the right build I need, but I'm not an expert and couldn't find the right set of files that I was sure I knew how to restore. I ended up restoring my AICP backup.
If somebody could PM me and give me a hand (messaging through Hangouts or something) that would be AWESOME!
I'm planning trying to snag an XL 2 pre-order next week, but until then the less headache the better! Plus stock Nougat looks better on a Swappa listing
Trying to sideload via recovery 24.49-18-16 but I keep getting "("unexpected contents:EMMC:/dev/block/bootdevice/by-name/boot...". I've also tried installing from the phone but the same error appears in recovery. Any ideas?
How to root Xperia XZs G8232 Oreo. Please provide necessary steps for root xperia xzs dual sim oreo.
the only way in unlock bootloader, flash twrp then flash supersu or magisk su, done
squall_20042001 said:
the only way in unlock bootloader, flash twrp then flash supersu or magisk su, done
Click to expand...
Click to collapse
I spent the entire day today trying to get to fastboot but it won't. When I do adb devices, it lists my device. I ran adb reboot bootloader. It would show the blue notification light, but when I do fastboot devices it won't show anything.
I have all the necessary drivers installed. But it just won't go into fastboot mode. Can you please help?
https://forum.xda-developers.com/xzs/how-to/tutorial-step-step-guide-to-gain-root-t3612624
https://forum.xda-developers.com/xzs/development/root-xperia-xzs-t3726911
3mozz said:
both dont work on stock kernal. need a custom kernal which i cannot find
Click to expand...
Click to collapse
Theres no Kernel Posted here for the latest Oreo Build . I suggest You downgrade to 7.1.1 so that you can download Xposed Modules and Also performance in NOugat is better than Oreo and theres alot of rootable kernel here with DRM Fix .
Farsiris said:
Theres no Kernel Posted here for the latest Oreo Build . I suggest You downgrade to 7.1.1 so https://forum.xda-developers.com/xzs/development/root-xperia-xzs-t3726911
Click to expand...
Click to collapse
Yes, Existenz is the best ROM for XZs now. But I prefer to use 7.1.1 because of Xposed Modules compatibility and theres many to install from xposed Forum. As for now Oreo is not yet supported by Xposed.
Rooted yrs ago, but having trbl now
Guys, I've rooted devices, but it's been a few years. I don't remember it being this complicated.
Here's what I think I understand:
Fastboot mode allows me to the ability to flash(overwrite) image files, which are what loads when my device powers up.
ADB is an interface that allows my PC to talk to my Android device at a command level.
My ROM (is that what some are calling Kernal?) is what I see as a user on the device.
>writing a new ROM gives me different Android functionality and user interface experience.
Root is an access level and is what allows me to overwrite the ROM, and uninstall bloatware (my goal)
Bootloader must be unlocked, and USB Debugging enabled
all being true and I don't necessarily dislike the XZs Dual G8232 interface (I just want to remove some garbage):
1. What does the Recovery.img do, and why do I need to overwrite it?
2. What's the best way to go about this?
>> I have watched a few videos and read several step by step guides, none of them seem to work as written/recorded for me.
Am I not getting this concept correct?
1. Must have drivers installed, a new boot.img (the new ROM) and recovery.img, and a means of communicating (adb)
2. Unlock bootloader, enable Debugging
3. get phone into Fastboot Mode (struggling here, key combo into fastboot mode has the phone off; adb into Fastboot reboots the phone , but the LED turns orange and no further commands execute.)
4. Overwrite the Boot.img
5. Overwrite the Recovery.img
6. reboot normally, done
thanks
IT changes so much and so fast, if you're into it now, don't ever get out!!!!
Hello all,
I hope someone can help since at the moment I can't do anything with my phone. I wanted to give a new live to my Sony XZP since I am tired of the phone, so I decied to unlock the bootloader and install twrp/root so I could test some of the available Android 10 roms here in XDA.
The unlock bootloader part was ok (once I realised that windows 10 wasn't installing the drivers properly and I sorted that), the problems started when I installed twrp twrp-3.3.1-0-maple, when I restarted into recovery twrp I couldn't see any of my files and there was actually an error saying can't mount /data and when I tried to do select storage everything said 0 MB.
I did what is mentioned on this post: https://forum.xda-developers.com/android/general/how-to-fix-unable-to-mount-data-t3830897
After this when I rebooted my phone was stuck on the Xperia screen, from there I just have been tried to restore anything there, however I am not an advanced users I tried a few things:
1- Used XperiFirm embeeded in Flashtool to download the Europe CE1 image for my device G8142 dual and tried to flash it using Flashtool but it seems the phone doesn't do anything after getvar-max-download-size or something similar
2 - Tried to use newflasher to flash the same image, but it also fails in the same step
AFter this I realised I could push files to the phone using ADB, so I tried the following:
3 - Pushed the SuperSU to the phone and flashed it
4 - Pushed a few roms (LineageOS 17.1 for XZP, eXistenZ Pie v10.0.0 47.2.A.10.107 )
5 - I tried to flash eXistenZ Pie v10.0.0 47.2.A.10.107 but the phone entered in a restart loop that was going always to the TWRP recovery
6 - I tried to flash LineageOS 17.1 for XZP but aftert reboot the phone doesn't do nothing, I can't power one, not fastboot, no flashmode nothing, now it seems that I really bricked.
Any help will be much appreciated.
Thanks in advance.
Hello,
This can be closed, I was able to restore my phone, I noticed flashmode still worked, once I found a tutorial explaining how to prepare the firmware downloaded by XperiFirm so it could be used with newflasher I was able to flash the most current CE1 firmware and the phone is working. I wanted to leave it here for someone else's reference.
However it would be nice to have a single article explaining how to unlock the booloader, install twrp and root and use that to flash a custom rom. If anyone knows about such article can you please share?
I searched the forum but I can only find bits and pieces nothing really explaining it in a simple way that someone that doesn't know much about this can use.
fattheman said:
Hello,
This can be closed, I was able to restore my phone, I noticed flashmode still worked, once I found a tutorial explaining how to prepare the firmware downloaded by XperiFirm so it could be used with newflasher I was able to flash the most current CE1 firmware and the phone is working. I wanted to leave it here for someone else's reference.
However it would be nice to have a single article explaining how to unlock the booloader, install twrp and root and use that to flash a custom rom. If anyone knows about such article can you please share?
I searched the forum but I can only find bits and pieces nothing really explaining it in a simple way that someone that doesn't know much about this can use.
Click to expand...
Click to collapse
Try using the twrp linked below, its an older version (3.2.1) but works flawlessly. Install it in fastboot mode, using the same command as the other recovery (fastboot flash recovery TWRPA10.img).
Twrp: https://drive.google.com/file/d/109obOcD_FVMg7rLP5g5wlxgpM9OsxZOG/view?usp=drivesdk
Also find magisk 20.4 attached below