Related
I'm sorry to do this, but I don't know where to start. Here's what I did to get to where I'm at:
- previously running SlimBean flashed using TWRP
- Downloaded ROM Manager and it recommended installing CWM Recovery
- Followed prompts
- It installed CWM 6.0.4.8
- Booted back into ROM and used ROM Manager to attempt to flash SlimKat 4.4.2 build 6
- CWM wiped dalvik but then got hung up
- Now it keeps saying Can't mount /cache/recovery/command
I'm completely stuck. Can't figure out what to do next. Please help!!!
Have you tryed reflashing the recovery to rule out a faulty install of cwm?
I should say, have you tried reflashing cwm *through Fastboot* to rule out a faulty cwm install?
Use TWRP recovery, preferred is 2.6.3.3 although there are newer versions, enter recovery, wipe - format data, basically for some reason, fastboot erase cache wipes the cache into an un-readable format.
note: this will also erase your internal storage too, so if theres anything important you want on there, make sure you back it up first using the adb pull command.
dougeedug said:
Have you tryed reflashing the recovery to rule out a faulty install of cwm?
I should say, have you tried reflashing cwm *through Fastboot* to rule out a faulty cwm install?
Click to expand...
Click to collapse
I can't get it to recognize my devices in order to use ADB. When connected, I type ADB Devices and I don't see anything listed. Is there a way to check I'm doing this ok?
EDIT: Ok, I got it to recongize my device. I'm going to try flashing TWRP thru ADB....will report back shortly...
Seanie280672 said:
Use TWRP recovery, preferred is 2.6.3.3 although there are newer versions, enter recovery, wipe - format data, basically for some reason, fastboot erase cache wipes the cache into an un-readable format.
note: this will also erase your internal storage too, so if theres anything important you want on there, make sure you back it up first using the adb pull command.
Click to expand...
Click to collapse
I can't quite risk doing this yet. Only as a last, last resort...
cartisdm said:
I can't get it to recognize my devices in order to use ADB. When connected, I type ADB Devices and I don't see anything listed. Is there a way to check I'm doing this ok?
EDIT: Ok, I got it to recongize my device. I'm going to try flashing TWRP thru ADB....will report back shortly...
I can't quite risk doing this yet. Only as a last, last resort...
Click to expand...
Click to collapse
whilst your phone is in recovery and plugged into your computer, open device manager, is there a yellow ! where its says android devices or myHTC ?
IGNORE THIS, You got it working whilst I was typing this.
cartisdm said:
I can't get it to recognize my devices in order to use ADB. When connected, I type ADB Devices and I don't see anything listed.
Click to expand...
Click to collapse
Use the command "fastboot devices" from the bootloader with "fastbootUSB" highlighted. You can't use adb commands in the bootloader because adb is to interact with android, which is not running while in bootloader. Let me know if you get output with the "fastboot devices" command.
EDIT: I should specify, if you are trying to flash recovery from anywhere but the bootloader using fastboot commands (it sounds like you may be trying to flash recovery with adb commands), you are just doing it wrong. so lets get that sorted first.
cartisdm said:
I can't get it to recognize my devices in order to use ADB. When connected, I type ADB Devices and I don't see anything listed. Is there a way to check I'm doing this ok?
EDIT: Ok, I got it to recongize my device. I'm going to try flashing TWRP thru ADB....will report back shortly...
Click to expand...
Click to collapse
you flash a custom recovery with fastboot commands not adb commands.
Got it!!! Thank you everyone for taking the time. I have a flight in a few hours and I was panicking!!!!
I grabbed universal drivers from here: download.clockworkmod.[com]/test/UniversalAdbDriverSetup6.msi (remove the brackets around .com)
Then my computer picked up the device and I was able to install TWRP. Clockworkmod recovery still doesn't work, no matter which version I tried. I'll stick with TWRP for now.
Thanks again!
EDIT: Well eff me, it wiped my internal storage. It must have done it after I flashed because that's where I grabbed the zip in the first place. That sucks...
cartisdm said:
Got it!!! Thank you everyone for taking the time. I have a flight in a few hours and I was panicking!!!!
I grabbed universal drivers from here: download.clockworkmod.[com]/test/UniversalAdbDriverSetup6.msi (remove the brackets around .com)
Then my computer picked up the device and I was able to install TWRP. Clockworkmod recovery still doesn't work, no matter which version I tried. I'll stick with TWRP for now.
Thanks again!
EDIT: Well eff me, it wiped my internal storage. It must have done it after I flashed because that's where I grabbed the zip in the first place. That sucks...
Click to expand...
Click to collapse
did you format data inside twrp recovery, like I said above, that will erase your internal storage too, you will need to push a rom over to your internal storage now using adb and then flash it.
Seanie280672 said:
did you format data inside twrp recovery, like I said above, that will erase your internal storage too, you will need to push a rom over to your internal storage now using adb and then flash it.
Click to expand...
Click to collapse
I didn't do so intentionally, but it's possible I did it without paying attention. I'm back to my system now so I'll just live with the loss. I flashed an existing ROM that I had in my Downloads folder once I was able to get into TWRP. It's just weird that folder is empty now.
So this is a bit of a comedy of errors on my part...
I took the OTA update to lollipop and (foolishly) followed the same method as on KK to get root, putting myself in a bootloop. I got myself out of it by clearing the userdata and the cache.
I went about sorting everything and achieved root using the chainfire method, that was fine and I then went about reinstalling the xposed modules I had before. Foolishly, I didn't double check the status of xposed on Lollipop and consequently put myself back in a bootloop (idiot). I redid what had worked earlier, clearing the userdata and the cache to no avail.
Obviously, the problem was not the same as before and I needed to disable xposed, but in clearing the userdata I not only removed the xposed_disable.zip file to do this and also turned off adb so I can't push it.
The bootloader is fine and I can use fastboot, but can't push anything across. I hadn't replaced the recovery but can boot into twrp. However, I cannot flash it because I cannot push it over using adb.
I can't work out exactly how far I need to go back/what exactly I need to flash in order to put this all back together again.
I would be very grateful for any help that people can give on this.
Oh man.... This post made me giggle.
Right first of all what device do you have?
Anyway to connect a flash drive to the USB or a Micro SD and flash a new ROM in recovery?
Sent From N5
All you need is ability to enter fastboot. Using Multitool or manual fastboot flash commands, you should be able to go back to stock KK. From there on you can flash stock L. Root it.
Do not have access to Multitool runme.cmd file at the moment to confirm that all you need is ability to issue fastboot command. adb is not needed. But am almost certain that this is the case.
LiamAtkins90 said:
Oh man.... This post made me giggle.
Right first of all what device do you have?
Anyway to connect a flash drive to the USB or a Micro SD and flash a new ROM in recovery?
Sent From N5
Click to expand...
Click to collapse
It's a 2014 Moto X, the XT1092 (bought straight from Motorola - I think that makes it the pure edition).
prasad.adam said:
All you need is ability to enter fastboot. Using Multitool or manual fastboot flash commands, you should be able to go back to stock KK. From there on you can flash stock L. Root it.
Do not have access to Multitool runme.cmd file at the moment to confirm that all you need is ability to issue fastboot command. adb is not needed. But am almost certain that this is the case.
Click to expand...
Click to collapse
I have tried the Multitool (as in here) but it would always throw me errors and never showed up anything on the fastboot console. I expect I probably need to get the stock image from Motorola (I've requested access to this which is the top option from here) and issue the fastboot commands by hand which seems to work. I'm mostly just unsure about what exact commands I need to give to make sure I don't forget to flash a particular part. I haven't gone this far on other phones and have normally worked from CWM but I can't even flash that/TWRP at the moment.
Thanks for your help guys!
HamRack said:
It's a 2014 Moto X, the XT1092 (bought straight from Motorola - I think that makes it the pure edition).
I have tried the Multitool (as in here) but it would always throw me errors and never showed up anything on the fastboot console. I expect I probably need to get the stock image from Motorola (I've requested access to this which is the top option from here) and issue the fastboot commands by hand which seems to work. I'm mostly just unsure about what exact commands I need to give to make sure I don't forget to flash a particular part. I haven't gone this far on other phones and have normally worked from CWM but I can't even flash that/TWRP at the moment.
Thanks for your help guys!
Click to expand...
Click to collapse
1.Download the latest TWRP recovery. 2.Prepare a SD card with a card reader and format it to ext4,then put Xposed-Disabler-Recovery.zip in it.
3.Boot your phone to ap fastboot mode,then open a cmd prompt and issue: fastboot boot TWRPimgfilename
3.link your phone to the card reader with otg cable and mount the SD card via TWRP advanced menu.
4.Flash the Xposed-Disabler-Recovery.zip via TWRP.
purejoy said:
1.Download the latest TWRP recovery. 2.Prepare a SD card with a card reader and format it to ext4,then put Xposed-Disabler-Recovery.zip in it.
3.Boot your phone to ap fastboot mode,then open a cmd prompt and issue: fastboot boot TWRPimgfilename
3.link your phone to the card reader with otg cable and mount the SD card via TWRP advanced menu.
4.Flash the Xposed-Disabler-Recovery.zip via TWRP.
Click to expand...
Click to collapse
Would it need to be an SD card or just a usb stick formatted correctly?
This sounds the best idea yet, now just to track down a USB OTG cable...
HamRack said:
Would it need to be an SD card or just a usb stick formatted correctly?
This sounds the best idea yet, now just to track down a USB OTG cable...
Click to expand...
Click to collapse
SD card is OK. As USB disk,haven't give a try.
Ok, cheers. I'll get a usb otg cable and give it a go.
HamRack said:
Ok, cheers. I'll get a usb otg cable and give it a go.
Click to expand...
Click to collapse
Normally Xposed installer would put a copy of Xposed-Disabler-recovery.zip under directory /sdcard after being installed. You should check the directory first, moreover, that file was released for those KK users. I have no idea whether it would take effect on lollipop or destroy your system. Take your own risk.
purejoy said:
Normally Xposed installer would put a copy of Xposed-Disabler-recovery.zip under directory /sdcard after being installed.
Click to expand...
Click to collapse
So I found, but because my first reaction to the second bootloop was to erase userdata (as had fixed the earlier one) I lost that.
purejoy said:
1.Download the latest TWRP recovery. 2.Prepare a SD card with a card reader and format it to ext4,then put Xposed-Disabler-Recovery.zip in it.
3.Boot your phone to ap fastboot mode,then open a cmd prompt and issue: fastboot boot TWRPimgfilename
3.link your phone to the card reader with otg cable and mount the SD card via TWRP advanced menu.
4.Flash the Xposed-Disabler-Recovery.zip via TWRP.
Click to expand...
Click to collapse
Hi,
Tracked down a usbotg cable and have booted into TWRP. When I plug in the sd card using the cable, I don't find anything to mount the sd card in the advanced menu of TWRP, but I do find a 'mount' option on the main menu
(as you can see here). Under there is a tick box for 'USB-OTG' which I have ticked, but I can't find where it actually is in the filemanager/when I select 'install'...
Any suggestions?
Realised what I had done, managed to flash the xposed_disabler zip, but it didn't work.
However, I was pointed in the direction of this where I downgraded to KK 4.4.4. That seems to have done the trick at getting me back to a working device. Out of curiosity, does anyone know a reason why I shouldn't get have the Lollipop OTA come through again in due course? When I check for updates it says I am up to date - is the only way I will get L by way of sideloading?
Finally, thanks for all your help, you've been very patient with my dangerous level of knowledge - enough to do plenty of damage but not enough to fix it!
HamRack said:
Hi,
Tracked down a usbotg cable and have booted into TWRP. When I plug in the sd card using the cable, I don't find anything to mount the sd card in the advanced menu of TWRP, but I do find a 'mount' option on the main menu
(as you can see here). Under there is a tick box for 'USB-OTG' which I have ticked, but I can't find where it actually is in the filemanager/when I select 'install'...
Any suggestions?
Click to expand...
Click to collapse
You were expected to use the latest TWRP which is 2.8+,at least 2.7. Anyway,that's not important.
Did you get an error after issuing "fastboot flash motoboot motoboot.IMG"?
Cuz you succeeded in updating, the OTA has upgraded your bootloader. Although you have downgraded your system, the BL can't be,hence when you try to accept another OTA, there will be a verification error.
Now You need flash a custom OTA pack via a 3rd party recovery. Some verifications must be removed from the official OTA zip.
You can also wait for someone to backup and share the images of the new system.
---------- Post added at 01:29 AM ---------- Previous post was at 01:07 AM ----------
HamRack said:
Realised what I had done, managed to flash the xposed_disabler zip, but it didn't work.
However, I was pointed in the direction of this where I downgraded to KK 4.4.4. That seems to have done the trick at getting me back to a working device. Out of curiosity, does anyone know a reason why I shouldn't get have the Lollipop OTA come through again in due course? When I check for updates it says I am up to date - is the only way I will get L by way of sideloading?
Finally, thanks for all your help, you've been very patient with my dangerous level of knowledge - enough to do plenty of damage but not enough to fix it!
Click to expand...
Click to collapse
I think you can have a try to download the .19 OTA zip and put it under /sdcard, then reboot into stock recovery to apply update from SD card or adb sideload. If there's no errors while verifying, you would get lollipop again.
Sorry for not reading all the reply's in this thread before posting (i'm in a bit of a rush)
I got a bootloop while applying the OTA on a brand new XT 1092 right after taking out of the box. After some digging around the forums (you can tell i'm new by the post count) i managed to get an OTA zip for my DE version and pushed it via ADB using stock recovery, with a few hickups:
- had to manually install the driver in windows
- first time the install via ADB push failed with some assert failure on something related to moto.odex
- the second try went ok and got the bootloop sorted.
So definitely give ADB a shot
Good luck!
First, try to recover as much as of your data stored on the device .
Then reflash the old ROM. You'll need a specific program for that - and a PC Surely! ☺
After that to get easier Back-Ups - i recommend unblocking the bootloader.
All the best☻.
purejoy said:
You were expected to use the latest TWRP which is 2.8+,at least 2.7. Anyway,that's not important.
Click to expand...
Click to collapse
I used TWRP 2.8.1.0, I downloaded it that day. Not sure what else it could have been...
Did you get an error after issuing "fastboot flash motoboot motoboot.IMG"?
Click to expand...
Click to collapse
Not sure when I was supposed to do that, couldn't see that in your directions...? Not a really a problem either way as its now sorted.
Cuz you succeeded in updating, the OTA has upgraded your bootloader. Although you have downgraded your system, the BL can't be,hence when you try to accept another OTA, there will be a verification error.
Now You need flash a custom OTA pack via a 3rd party recovery. Some verifications must be removed from the official OTA zip.
You can also wait for someone to backup and share the images of the new system.
I think you can have a try to download the .19 OTA zip and put it under /sdcard, then reboot into stock recovery to apply update from SD card or adb sideload. If there's no errors while verifying, you would get lollipop again.
Click to expand...
Click to collapse
Ok, thanks for the info. Any idea how to remove those verifications? Would this do the required thing?
Also, what exactly do you mean by the .19 OTA zip? You mean the OTA zip with the new bootloader in with it? If it has an error while trying this, would it give problems or just stop and return as before?
Thanks
Sorry, i have stayed up too late last night. You know there is time difference.
i dunno the differences between GB version and EU version, since you have a system of EU, maybe you should refer to this thread http://forum.xda-developers.com/moto-x-2014/general/ota-zip-moto-x-2014-xt1092-5-0-t2970818
Hmm,there is a better choice. Seems that moto has released the stock 5.0 firmware for GB xt1092. http://forum.xda-developers.com/showpost.php?p=57591807&postcount=36
Download it and make a full recovery.
BTW: Please backup your data first.
purejoy said:
Sorry, i have stayed up too late last night. You know there is time difference.
i dunno the differences between GB version and EU version, since you have a system of EU, maybe you should refer to this thread http://forum.xda-developers.com/moto-x-2014/general/ota-zip-moto-x-2014-xt1092-5-0-t2970818
Hmm,there is a better choice. Seems that moto has released the stock 5.0 firmware for GB xt1092. http://forum.xda-developers.com/showpost.php?p=57591807&postcount=36
Download it and make a full recovery.
BTW: Please backup your data first.
Click to expand...
Click to collapse
I'm not sure of the differences either...
So I'm wanting to make sure I do this correctly this time. I know a couple of ways of backing up but after all the faff recently I want to have an ironclad backup before I piss around with anything else (foolish me for not doing so before). Can you clarify the best way to back up my device and how I would do that? I have a feeling I haven't been doing it correctly/the most ideal way before and it would be good to know.
Also, how would I go about putting that backup you've pointed too (thank you for finding that, I don't think I'd been searching for quite the right thing) on to my device? Would I go through a similar series of steps to how I recovered my phone before (ie here)?
I'm going away for xmas/NY and will probably do this when I get back so I don't risk borking my phone when I need it most. Nonetheless, it would be good to have things ready to roll when I get back.
Thanks for your help, you've been great.
It depends on what you plan to backup and i don't konw what app your are using. If you use Google service, Contacts and some app data are normally synced to Google Cloud Servers. You can get them back in lollipop 5.0 via your Google account. As your pictures and videos,you can also directly copy them on your PC. What you need to backup are private app data and private messages. You can use some 3rd party backup apps like TitaniumBakcup to solve this. If there are not so much user data, you can backup like this.
You can also backup and restore your userdata via TWRP. If you get so many data, you can try this.
As the full stock recovery,you can restore your phone via fastboot utility or RSD lite.
1.Download and Unzip the image.
2.Put your phone in AP Fastboot Mode.
3. $ fastboot flash partition gpt.bin
$ fastboot flash motoboot motoboot.img
$ fastboot reboot-bootloader
$ fastboot flash logo logo.bin
$ fastboot flash boot boot.img
$ fastboot flash recovery recovery.img
$ fastboot flash system system.img
$ fastboot erase modemst1
$ fastboot erase modemst2
$ fastboot flash fsg fsg.mbn
$ fastboot -w (Erase userdata. Optional,maybe unnecessary)
$ fastboot reboot
I would advise you to put off erasing data. If you get any issues while rebooting into new system, then you can erase your data.
Hope these help. Good Luck!
Great, thanks for the tip.
I tend to have minimal important data on my phone that isn't covered by either google or evolvesms/whatsapp. Nonetheless, thanks for the tips. I've been using titanium for a long while and have that backed up to dropbox too.
I tried flashing TWRP after I fixed the clusterbadger that was the last few days, but had no luck. I still don't seem to be able to push the image over using adb nor use adb to issue commands while booted into TWRP through fastboot. Have you experienced that? I guess worst case is that I copy the zip to an sdcard and flash it from usbotg by issuing commands in the TWRP shell they give you...?
Thanks for the tip on the userdata too.
Hey guys
So I just bought a new Z3C and I'm planning on rooting it and installing CM12.1 on it. But before that I wanna make sure I perfectly understood the entire process. So if anyone could help by answering/confirming some of the things below, I would really appreciate that.
First, Sony devices don't come with a default recovery? Did I get that part right? That's why I need to flash a custom one, right? I suppose this is also the reason why I need a custom recovery in order to flash CM12.1 on my phone. Since I don't know if CM can run without one.
Second of all, kingroot. Ok, so this is an app for PC or phone that will root your phone in one click. Still without needing to unlock the bootloader (thus compromising that TA partition), right? It's in Chinese but I guess I don't need to know Chinese to click the only button on the screen. ) So that won't be a problem.
Third, I need root access for the backup part, right? So after running kingroot, I need to make a backup of my DRM stuff, right? It won't be of any use in CM, I suppose. So I just keep it somewhere safe.
Another thing, since I don't already have a custom recovery, I need the "installer" version of that xzdrecovery recovery, right? Cause there is also a flashable zip version of it, and I was wondering how the hell do I install that with no default recovery.
Can CM12 run on a locked bootloader? Probably stupid question. But this forum seems to pack some really interesting tricks I never thought were possible. So...I'm asking.
One thing I didn't quite understand: why do I need to flash part of CM12.1 to have a working recovery? Is the recovery not usable after installing it? Does it need a "simulated" ROM in order to be accessible/visible? I mean, on my SGS4, I just had to have a custom recovery (in my case it was CWM, but I'm not sure there is such a thing for the Z3C) and then just boot into it and flash CyanogenMod ROM or any other custom ROM for that matter. I didn't have to "split" the installation. First the boot.img, and then the rest (which will basically rewrite the boot.img anyway). So this part is still a bit confusing to me. Can anyone explain?
Thank you very much.
arsradu said:
First, Sony devices don't come with a default recovery? Did I get that part right? That's why I need to flash a custom one, right? I suppose this is also the reason why I need a custom recovery in order to flash CM12.1 on my phone. Since I don't know if CM can run without one.
Click to expand...
Click to collapse
As far as I know there really isn't a default recovery for Sony devices so to install CM you will need a recovery.
arsradu said:
Second of all, kingroot. Ok, so this is an app for PC or phone that will root your phone in one click. Still without needing to unlock the bootloader (thus compromising that TA partition), right? It's in Chinese but I guess I don't need to know Chinese to click the only button on the screen. ) So that won't be a problem.
Click to expand...
Click to collapse
I do not recommend kingroot but you can try it if you trust it. I used the xda guide on doing it and it worked fine for me: http://forum.xda-developers.com/z3-compact/general/how-to-root-backup-drm-keys-t3013343 (takes some time but its worth it if you ever want to go back to factory). As long as the bootloader stays locked the TA partition wont be touched thats right but once you unlock it you will lose all DRM keys and they wont restore if you flash a factory frimware again.
arsradu said:
Third, I need root access for the backup part, right? So after running kingroot, I need to make a backup of my DRM stuff, right? It won't be of any use in CM, I suppose. So I just keep it somewhere safe.
Click to expand...
Click to collapse
Yes you need root to backup the TA parition and yes only Sony roms use the DRM keys, CM doesn't touch them.
arsradu said:
Another thing, since I don't already have a custom recovery, I need the "installer" version of that xzdrecovery recovery, right? Cause there is also a flashable zip version of it, and I was wondering how the hell do I install that with no default recovery.
Click to expand...
Click to collapse
You install it over fastboot pretty much or with locked bootloader you use the Sony flash tool. More here: http://forum.xda-developers.com/z3-compact/general/how-to-root-backup-drm-keys-t3013343
Also keep in mind that custom Kernels like "M5 Kernel" come with a pre-installed recovery.
arsradu said:
Can CM12 run on a locked bootloader? Probably stupid question. But this forum seems to pack some really interesting tricks I never thought were possible. So...I'm asking.
Click to expand...
Click to collapse
Im pretty sure its not possible. For not sony kernels you need a unlocked bootloader, otherwise it wont even boot up.
arsradu said:
One thing I didn't quite understand: why do I need to flash part of CM12.1 to have a working recovery? Is the recovery not usable after installing it? Does it need a "simulated" ROM in order to be accessible/visible? I mean, on my SGS4, I just had to have a custom recovery (in my case it was CWM, but I'm not sure there is such a thing for the Z3C) and then just boot into it and flash CyanogenMod ROM or any other custom ROM for that matter. I didn't have to "split" the installation. First the boot.img, and then the rest (which will basically rewrite the boot.img anyway). So this part is still a bit confusing to me. Can anyone explain?
Click to expand...
Click to collapse
Unlike Samsung... Sony devices have no recovery (maybe at a later time?) so you cant just replace the stock recovery with a custom one. You have to take out boot.img because fastboot cant flash entire zips like a recovery, so you flash the boot.img over fastboot which installs the recovery for you.
After that you execute "fastboot reboot" and spam your volume up key till you enter the recovery and from there you can install cyanogenmod and other.
MyPictures said:
As far as I know there really isn't a default recovery for Sony devices so to install CM you will need a recovery.
I do not recommend kingroot but you can try it if you trust it. I used the xda guide on doing it and it worked fine for me: http://forum.xda-developers.com/z3-compact/general/how-to-root-backup-drm-keys-t3013343 (takes some time but its worth it if you ever want to go back to factory). As long as the bootloader stays locked the TA partition wont be touched thats right but once you unlock it you will lose all DRM keys and they wont restore if you flash a factory frimware again.
Yes you need root to backup the TA parition and yes only Sony roms use the DRM keys, CM doesn't touch them.
You install it over fastboot pretty much or with locked bootloader you use the Sony flash tool. More here: http://forum.xda-developers.com/z3-compact/general/how-to-root-backup-drm-keys-t3013343
Also keep in mind that custom Kernels like "M5 Kernel" come with a pre-installed recovery.
Im pretty sure its not possible. For not sony kernels you need a unlocked bootloader, otherwise it wont even boot up.
Unlike Samsung... Sony devices have no recovery (maybe at a later time?) so you cant just replace the stock recovery with a custom one. You have to take out boot.img because fastboot cant flash entire zips like a recovery, so you flash the boot.img over fastboot which installs the recovery for you.
After that you execute "fastboot reboot" and spam your volume up key till you enter the recovery and from there you can install cyanogenmod and other.
Click to expand...
Click to collapse
Alright. Thank you a lot for your answers.
So, to sum up:
First, I need to root my device. You said you would not recommend Kingroot. Ok. But I'm on stock Lollipop right now. And for as far as I understood, in order to get root on it without using Kingroot method, I need to downgrade to KitKat using FlashTool. Did I get it right?
Second, I need to backup my TA partition stuff.
Third, I need to flash the boot.img from CM12.1 flashable zip and then the recovery (flashable zip version of it, right?). In this order. Am I right?
And for the recovery part, I think I'm gonna go with that FlashTool (since I already got it for downgrading to KitKat) or via fastboot (command line), for which I need the Android SDK installed, I suppose?
Forth, unlock the bootloader. I guess I'm gonna have to Google that part. I saw some videos explaining how to do that, so I guess I'm gonna be ok.
Fifth, boot into recovery and flash CM12.1 (finally).
Please, let me know if I got the flow right or if you would make any suggestions/adjustments/corrections to it.
Also, one other thing, I heard people not being able to flash back stock and booting with it, after having a custom ROM installed, even after re-adding the content of the TA partition back and re-locking the bootloader. Any idea how to get this right from the first time, in case I need to revert to stock?
Again, big thank you for your help.
arsradu said:
Alright. Thank you a lot for your answers.
So, to sum up:
First, I need to root my device. You said you would not recommend Kingroot. Ok. But I'm on stock Lollipop right now. And for as far as I understood, in order to get root on it without using Kingroot method, I need to downgrade to KitKat using FlashTool. Did I get it right?
Second, I need to backup my TA partition stuff.
Third, I need to flash the boot.img from CM12.1 flashable zip and then the recovery (flashable zip version of it, right?). In this order. Am I right?
And for the recovery part, I think I'm gonna go with that FlashTool (since I already got it for downgrading to KitKat) or via fastboot (command line), for which I need the Android SDK installed, I suppose?
Forth, unlock the bootloader. I guess I'm gonna have to Google that part. I saw some videos explaining how to do that, so I guess I'm gonna be ok.
Fifth, boot into recovery and flash CM12.1 (finally).
Please, let me know if I got the flow right or if you would make any suggestions/adjustments/corrections to it.
Also, one other thing, I heard people not being able to flash back stock and booting with it, after having a custom ROM installed, even after re-adding the content of the TA partition back and re-locking the bootloader. Any idea how to get this right from the first time, in case I need to revert to stock?
Again, big thank you for your help.
Click to expand...
Click to collapse
- Yes you need to downgrade to a version where that root exploit isn't patched and root that way
- Yea then when you got root and all, you use that tool to backup your TA partition
- Yea after that you unlock your bootloader: http://developer.sonymobile.com/unlockbootloader/unlock-yourboot-loader/ and then you flash boot.img from CM (or a custom Kernel that implements a recovery). After flashing the boot.img you reboot into your recovery and flash the whole Cyanogenmod.zip there (Apply update). I just installed my recovery over fastboot, never actually tried the FashTool way. fastboot.exe is in the Android SDK yeah but you can also just get the small ADB installer which has it too: http://forum.xda-developers.com/showthread.php?t=2588979 (For Linux you need to install it over your package manager I think).
- No. You need to unlock the bootloader before, otherwhise it wont allow you to flash a custom boot.img
Not sure about the restoring process, I kinda don't think that I will move back from CM anyways.
However if I would go back then I would try this:
- Relock bootloader
- Factory reset
- Flash back old sony rom with root exploit over flashtool
- Gain root over that exploit and use the TA Backup tool to restore TA partition
- Install latest Sony ROM and that should work? (Not sure)
Can you post one of those theards where they get issues with restoring? How do they do it?
MyPictures said:
- Yes you need to downgrade to a version where that root exploit isn't patched and root that way
- Yea then when you got root and all, you use that tool to backup your TA partition
- Yea after that you unlock your bootloader: http://developer.sonymobile.com/unlockbootloader/unlock-yourboot-loader/ and then you flash boot.img from CM (or a custom Kernel that implements a recovery). After flashing the boot.img you reboot into your recovery and flash the whole Cyanogenmod.zip there (Apply update). I just installed my recovery over fastboot, never actually tried the FashTool way. fastboot.exe is in the Android SDK yeah but you can also just get the small ADB installer which has it too: http://forum.xda-developers.com/showthread.php?t=2588979 (For Linux you need to install it over your package manager I think).
- No. You need to unlock the bootloader before, otherwhise it wont allow you to flash a custom boot.img
Not sure about the restoring process, I kinda don't think that I will move back from CM anyways.
However if I would go back then I would try this:
- Relock bootloader
- Factory reset
- Flash back old sony rom with root exploit over flashtool
- Gain root over that exploit and use the TA Backup tool to restore TA partition
- Install latest Sony ROM and that should work? (Not sure)
Can you post one of those theards where they get issues with restoring? How do they do it?
Click to expand...
Click to collapse
It was a post in a long thread. I'm not sure I can find it right now.
Anyway, I got stuck at flashing back KitKat. FlashTool says "waiting for flashmode", whike asking me to disconnect my phone, press the back button (I got it that this is for older phones that do have a physical button), and plugging back. Which I did. The result being a very nice animation for charging. The USB debugging is ON. What am I missing here?
Sent from my D5803 using Tapatalk
arsradu said:
It was a post in a long thread. I'm not sure I can find it right now.
Anyway, I got stuck at flashing back KitKat. FlashTool says "waiting for flashmode", whike asking me to disconnect my phone, press the back button (I got it that this is for older phones that do have a physical button), and plugging back. Which I did. The result being a very nice animation for charging. The USB debugging is ON. What am I missing here?
Sent from my D5803 using Tapatalk
Click to expand...
Click to collapse
Did you install the drivers properly and on which Operating system are you flashing it?
MyPictures said:
Did you install the drivers properly and on which Operating system are you flashing it?
Click to expand...
Click to collapse
I would say yes. I mean...after googling a bit, I saw that I actually don't need to just "ignore" that message asking to press the Back button, but to actually press Volume Down instead. Which I did. And I was able to go into Flash Mode. (Flash Tool says "device connected in Flash Mode"). The device was properly recognized in MTP mode. Still, I had to manually install the Flash-tool drivers to get it recognized in flash mode, as well. Not sure why...
I mean, if the phone was properly recognized without manually installing anything (Windows downloaded and installed its own drivers), why the hell do I need to install custom drivers to get it recognized in flash mode? By the way, this "flash mode" is similar to Samsung's "Download Mode", for as far as I could see. And, just like on Samsung's devices, the access is made by pressing the Volume Down upon booting up.
Anyway, even though the device is now recognized in flash mode, I still get an error trying to flash stock 4.4.4.
I get this:
Code:
14/014/2015 21:14:34 - INFO - Please connect your device into flashmode.
14/016/2015 21:16:28 - INFO - Device disconnected
14/017/2015 21:17:03 - INFO - Device connected in flash mode
14/017/2015 21:17:03 - INFO - Opening device for R/W
14/017/2015 21:17:03 - INFO - Reading device information
14/017/2015 21:17:03 - INFO - Unable to read from phone after having opened it.
14/017/2015 21:17:03 - INFO - trying to continue anyway
14/017/2015 21:17:03 - INFO - Start Flashing
14/017/2015 21:17:03 - INFO - Processing loader.sin
14/017/2015 21:17:03 - INFO - Checking header
14/017/2015 21:17:03 - ERROR - Processing of loader.sin finished with errors.
14/017/2015 21:17:03 - INFO - Ending flash session
14/017/2015 21:17:03 - ERROR - Error in processHeader : 1 : Incorrect function.
14/017/2015 21:17:03 - ERROR - Error flashing. Aborted
14/017/2015 21:17:03 - INFO - Device connected in flash mode
And after a while, it automatically reboots in normal mode.
Windows version is Windows 10. But I'm not sure that's the problem here since, as I said, the device does get recognized both in MTP and flash modes. Also, for as far as I could see, other people are having the same issues on other versions of Windows.
Hmm not exactly sure but for Windows 8 and 8.1 (also Vista 64 bit and 7 64 Bit) You sometimes need to disable enforced driver signature.
Are you running the correct executable for your OS?:
FlashTool64.exe for 64 Bit OS and
FlashTool.exe for 32 Bit OS.
Is the device properly recognized in your device manager. Maybe re-downloading the frimware might help.
MyPictures said:
Hmm not exactly sure but for Windows 8 and 8.1 (also Vista 64 bit and 7 64 Bit) You sometimes need to disable enforced driver signature.
Are you running the correct executable for your OS?:
FlashTool64.exe for 64 Bit OS and
FlashTool.exe for 32 Bit OS.
Is the device properly recognized in your device manager. Maybe re-downloading the frimware might help.
Click to expand...
Click to collapse
Yes, I'm running FlashTool64.exe since I'm running a 64-bit version of Windows.
The device is correctly recognized in flash mode (after manually selecting the driver installed with flash-tool). See the attached image for more info.
But indeed maybe I got the wrong firmware. Problem is that I'm not really sure which one should I choose.
I got one called D5803_23.0.1.A.5.77_Customized_FR.ftf. I don't mind it that it's in French. All of them have English anyway.
Also, I saw one for UK here called D5803_23.0.A.2.105_UK.ftf. Seems to be different.... I will try with that as well.
Update: same error with that UK firmware, as well.
Update2: Well I'm half way there. Got 4.4.4 installed and got it rooted. YAY. Still trying to figure out why adb is not correctly running when trying to backup TA.
Update3: ok, backup done too!
Update4: the boot.img that comes with CM12.1 doesn't seem to have a recovery.... Or if it does, I couldn't boot in it so I can flash CM12.1.
I tried the one from Doomlord (Z3c_DooMLoRD_AdvStkKernel_v01_FW-105.img) and that seems to be based on CWM v6.0.4.7.
Problem with that is that, even though I can boot into recovery, I can't flash CM12.1. It says error status 7. Any idea why or how to fix this?
I belive error 7 indicates a outdated recovery (CM 12.1 needs a up to date one).
MyPictures said:
I belive error 7 indicates a outdated recovery (CM 12.1 needs a up to date one).
Click to expand...
Click to collapse
Might be. The problem is the device is not correctly recognized upon flashing (it says the device is "Aries" but the ROM is for D5803, D5833, z3c LOL), due to the check made within the updater-script (first line). For as far as I could see, this is a known issue... Not sure why it hasn't been fixed by now.
Anyway, removing that line will get the ROM installed successfully (at least with THAT recovery).
So I'm on CM12.1 , been for a few days now (thank you for your help), and I was wondering if there are any "permanent" recoveries (compatible with CM12.1, of course) that I can flash, something that can give me the ability to boot into recovery (and not Cyanogen Recovery, since that one sucks) and do things like nandroid backup (I know TWRP and CWM can do that, but I couldn't find any permanent version of those (or maybe I just didn't dig deep enough), and I'm not sure they are compatible with CM12.1) and formatting /system. The last one is really important for a clean installation of the ROM, especially since it doesn't look like it's done by the ROM itself.
Hey guys,
I'll be honest...I'm a noob at all of this. I thought I would experiment with putting a custom ROM on an old Android phone I had (the SP), so googled around to find some guides on how to do it and tried to follow them. I successfully got the phone into fastboot (after using the Windows 8 driver workaround on Windows 10), and all seemed good. However, from then the issues (or what looked like them) started:
1. When entering into the bootloader (correct me if I'm wrong, but that's when you hold down the up volume as you connect it to the PC), the blue light would come on, but nothing would show on the screen. The guides I was looking at would suggest that the bootloader would load onto the screen. Was I just not loading into the bootloader?
However, I was still able to interact with the phone through the Cmd.exe, so something right was happening, so I pressed on (probably a mistake!) to attempt to install TWRP, as this was the next step in the guide I was following. This was where I ran into my next problem:
2. When trying to flash the TWRP.img to the recovery partition, I would get an error back saying the recovery partition could not be found. As far as I was concerned, there was also no way to verify whether the recovery partition was there or not, as I couldn't seem to load the bootloader either
Having googled around, I found an article that suggested I'd flash it to the boot partition instead, which I did. From that point, the device would no longer boot at all. It would enter fastboot/bootloader with the blue light, but unplugging the device and holding down the power button did nothing. At this point I decided "screw it" and decided to push on and see if I could install a ROM (I'd settled on LineageOS), so started following the steps, and flashed the Boot.img to the boot partition. The other instruction was to "flash the LineageOS zip from recovery", which I did not know how to do, and presumed was not possible, seeing as I thought I'd somehow broken that partition. At this point, the phone would turn on, the bar would flash green then red, and the Sony splashscreen would show. However, that is that would happen - it would stay frozen at that point. That is the point I'm at now
I appreciate that I've probably royally messed up this phone, and that's okay with me if that's the case - it was a learning experience. However, if this is recoverable, I'd really appreciate some help! I may be new to this, and not know much at all, but I want to try it, so if there is a way to get to a position where I can install TWRP and then flash a ROM to the phone, then please share your knowledge! I'm open to anything
Thanks in advance,
Meeb
MrMeeb said:
Hey guys,
I'll be honest...I'm a noob at all of this. I thought I would experiment with putting a custom ROM on an old Android phone I had (the SP), so googled around to find some guides on how to do it and tried to follow them. I successfully got the phone into fastboot (after using the Windows 8 driver workaround on Windows 10), and all seemed good. However, from then the issues (or what looked like them) started:
1. When entering into the bootloader (correct me if I'm wrong, but that's when you hold down the up volume as you connect it to the PC), the blue light would come on, but nothing would show on the screen. The guides I was looking at would suggest that the bootloader would load onto the screen. Was I just not loading into the bootloader?
However, I was still able to interact with the phone through the Cmd.exe, so something right was happening, so I pressed on (probably a mistake!) to attempt to install TWRP, as this was the next step in the guide I was following. This was where I ran into my next problem:
2. When trying to flash the TWRP.img to the recovery partition, I would get an error back saying the recovery partition could not be found. As far as I was concerned, there was also no way to verify whether the recovery partition was there or not, as I couldn't seem to load the bootloader either
Having googled around, I found an article that suggested I'd flash it to the boot partition instead, which I did. From that point, the device would no longer boot at all. It would enter fastboot/bootloader with the blue light, but unplugging the device and holding down the power button did nothing. At this point I decided "screw it" and decided to push on and see if I could install a ROM (I'd settled on LineageOS), so started following the steps, and flashed the Boot.img to the boot partition. The other instruction was to "flash the LineageOS zip from recovery", which I did not know how to do, and presumed was not possible, seeing as I thought I'd somehow broken that partition. At this point, the phone would turn on, the bar would flash green then red, and the Sony splashscreen would show. However, that is that would happen - it would stay frozen at that point. That is the point I'm at now
I appreciate that I've probably royally messed up this phone, and that's okay with me if that's the case - it was a learning experience. However, if this is recoverable, I'd really appreciate some help! I may be new to this, and not know much at all, but I want to try it, so if there is a way to get to a position where I can install TWRP and then flash a ROM to the phone, then please share your knowledge! I'm open to anything
Thanks in advance,
Meeb
Click to expand...
Click to collapse
First of all don't worry, Sony's phone doesn't brick that easy ?
All you need to do first is to repair your phone using official Xperia companion (Google how to repair your phone using Xperia companion).. After that you'll need to root your phone and unlock the bootloader to be able to install custom recovery like TWRP and use it to install any custom ROM.
Sent from my Xperia SP using Tapatalk
OsGhaly said:
First of all don't worry, Sony's phone doesn't brick that easy
All you need to do first is to repair your phone using official Xperia companion (Google how to repair your phone using Xperia companion).. After that you'll need to root your phone and unlock the bootloader to be able to install custom recovery like TWRP and use it to install any custom ROM.
Sent from my Xperia SP using Tapatalk
Click to expand...
Click to collapse
Thanks for the advice! I successfully got it to the point of being rooted (using towelroot) and the bootloader unlocked, using flashtool. All seemed good. I then downloaded TWRP Manager, and tried to install TWRP, but it failed, which was an issue I faced before. To confirm my theory, I tried doing it using the CMD fastboot, and, using "fastboot flash recovery twrp.img", and was met with the same error as before - recovery partition not found. How am I supposed to install TWRP to the recovery partition if I don't have a recovery partition?
MrMeeb said:
Thanks for the advice! I successfully got it to the point of being rooted (using towelroot) and the bootloader unlocked, using flashtool. All seemed good. I then downloaded TWRP Manager, and tried to install TWRP, but it failed, which was an issue I faced before. To confirm my theory, I tried doing it using the CMD fastboot, and, using "fastboot flash recovery twrp.img", and was met with the same error as before - recovery partition not found. How am I supposed to install TWRP to the recovery partition if I don't have a recovery partition?
Click to expand...
Click to collapse
You're more than welcome dear, glad to hear you've successfully did it :good:
Concerning TWRP flash, you can try one of these:
1- Use rasher tool to flash the TWRP img (the easiest way).
2- Adb Sideload:
AdrianDC said:
HOW TO INSTALL MANUALLY TO FOTA :
* Bootimage : Download the TWRP bootimage you want to flash
* File storage : Adapt the path and push the file to the device this way :
Code:
adb root
adb wait-for-device
adb push FullPathToTheRecovery.img /tmp/twrp.img
* Flash : Extract the TWRP image to the FOTA partition
Code:
adb shell dd if=/tmp/twrp.img of=/dev/block/platform/msm_sdcc.1/by-name/FOTAKernel
* Reboot to recovery : adb reboot recovery
Click to expand...
Click to collapse
3- Using terminal emulator app such as $cripter:
Place twrp.img in the root of your /sdcard folder then run the following commands using $cripter app:
Code:
su
dd if=/sdcard/twrp.img of=/dev/block/platform/msm_sdcc.1/by-name/FOTAKernel
P.S. You can download the latest TWRP from here
OsGhaly said:
You're more than welcome dear, glad to hear you've successfully did it :good:
(Rest cut as I'm not allowed to post external links)
[/CODE]
Click to expand...
Click to collapse
Hmm, Rashr does not seem to work - I select it to flash recovery, select my twrp.img, it says flashing then nothing happens. When booting to recovery, nothing shows, and it goes through to a normal boot. When trying to flash TWRP using the official TWRP app, it says it has flashed successfully, but again, no luck when booting into recovery mode. I don't really want to try either of the other two techniques, for fear of breaking things again. I've seen talk elsewhere that this isn't possible on the stock Kernel, which I'm on. Is that correct?
MrMeeb said:
Hmm, Rashr does not seem to work - I select it to flash recovery, select my twrp.img, it says flashing then nothing happens. When booting to recovery, nothing shows, and it goes through to a normal boot. When trying to flash TWRP using the official TWRP app, it says it has flashed successfully, but again, no luck when booting into recovery mode. I don't really want to try either of the other two techniques, for fear of breaking things again. I've seen talk elsewhere that this isn't possible on the stock Kernel, which I'm on. Is that correct?
Click to expand...
Click to collapse
Ok then, you can't use custom recovery with the stock kernel ofc. but we don't want that!.. you will install the TWRP recovery then reboot to it and install the new ROM without booting to the stock ROM at all.
1- Download TWRP and the ROM you want to flash for example Lineage OS.
2- Use the second method mentioned in my previous post by Adrian DC to install TWRP then boot into recovery -> wipe all then install LineageOS ROM + GApps.
-----
Another workaround is to install XZDualRecovery to have Philz touch and TWRP recoveries working alongside with the stock kernel and use it to install LineageOS ROM.
Hi bro
neva mind wat happened to u ,do as wat i say
First search n find the proper (stock .tft) file as per your country and version.
Download FLASHTOOL
now paste ur stock.tft file (around 1-2 gb) in flash folder
open flashtool and connect ur sick brick SP-Xepria in fastboot
install ur stock onces it done successfullly u wil get ur phone as stock .
i too bricked now im on andriod 7
no worries bro
---------- Post added at 09:31 AM ---------- Previous post was at 09:24 AM ----------
Hi everybody welcome to my tutorial about Flashing with Flashtool. This thread is for those who want to reflash their device back to Sony Stock. See below for last details about this thread and the last build by Sony.
Note: I DO NOT OWN THIS DEVICE ANYMORE. PICTURES ARE REMOVED FROM MY DROPBOX AND THUS NOT VISEBLE. FOR NOW JUST RELY ON THE EXPLANATION PLEASE. ANY QUESTION CAN BE ASKED HERE. I DO NOT RESPOND TO TECHMAIL!
Created: 23-02-2014
Updated: 05-07-2014
Latest Android build released by Sony: 12.1.A.1.205
Let's begin shall we.. We shall!
First you need to download the correct ftf file for your device/operator or needs. This can be done here: http://forum.xda-developers.com/show....php?t=2311964 In there you can share and download firmware files in .ftf format..
You alsol need a program called Flashtool. You can download this here: http://forum.xda-developers.com/showthread.php?t=920746
For Windows 8 and 8.1 users I also recommend you to read this thread: http://forum.xda-developers.com/show....php?t=2095087 Microsoft has enhanced the security in Windows 8/8.1 and Windows won't install proper signed drivers.
When you are done with that you need to move your downloaded firmware file to the proper location for flashtool to be found:
C:\Flashtool\Firmwares
After that you are good to go, just remember the following:
Bootloader locked? If not you wont have BE2/OTA/PCC etc (for unlocking and relocking: http://forum.xda-developers.com/show....php?t=2354721 )
I've made backups of my important files that are stored on my phone?
Battery at atleast 50%?
I have patience?
I got something to do meanwhile?
The last two things are very important
Let's get started:
1: Open Flashtool:
Flashtool(.exe) for 32Bits systems and Flashtool64(.exe) for 64Bits systems
2: Press the Lightningbolt picture and select Flashmode
This will give another screen.
3: Select the downloaded ftf. (In this case 2.254)
Make sure that all the wipes are checked and the others are unchecked. This is to prevent any bootloops or other problems after downgrading.
4: Press Flash and the next two lines will be added to the flashtool log
The files are being prepared and checked. Have a bit of patience please.
5: Turn off your phone and turn it back on into Flashmode
After this the process will start.
After flashing you can disconnect your phone and boot it up.
Via Flashtool you can also reset your system after. For example:
You are running the latest ExistenZe ROM from our beloved Niaboc79 and you want to go back to stock for a reason WITHOUT losing data! Just flash the last Stock ROM and untick the following boxes:
Untick DATA and APPSLOG!! But keep CACHE to wipe the /cache (is the same as a wipe cache via CWM).
FAQ
- My Phone wont stay into flashmode
> Turn it off, wait a few minutes and turn it back into flashmode
- Flashtool wont recognise my phone
> Make sure you have the proper drivers installed. See C://Flashtool/Drivers
- Flashing failed
> Problem depends on the error code given by Flashtool. Post the problem here and perhaps we can help
- Got a bootloop
> Reflash again
- Even after reflash I got into a bootloop
> Turn off your phone via the small button behind the batterycover and wait a few minutes. Then try again. If that doesnt work you need to flash again.
- Booting takes ages
> This is normal. The entire cache needs to be rebuild. Patience my dear..
- After flashing and booting my phone is laggy.
> Reboot device and wait a bit. The phone needs to fully reset and boot itself. Have some patience dear.
- Do I need to unlock my bootloader to use flashtool
> NO!
- Can I unlock my bootloader with flashtool?
> NO!
- Can I relock my bootloader with flashtool?
> Yes
You too have Sony.yt procedure with s1boot in the last case...
OsGhaly said:
Ok then, you can't use custom recovery with the stock kernel ofc. but we don't want that!.. you will install the TWRP recovery then reboot to it and install the new ROM without booting to the stock ROM at all.
1- Download TWRP and the ROM you want to flash for example Lineage OS.
2- Use the second method mentioned in my previous post by Adrian DC to install TWRP then boot into recovery -> wipe all then install LineageOS ROM + GApps.
Click to expand...
Click to collapse
Oh, okay! I'm trying to do the command as stated, but (while rooted with SuperSU installed) I get the error about adb not being able to run root in production builds. So, I enter the shell with adb shell type su, but then when i type exit and then adb root I get an error saying device not found, even though it shows up when typing adb devices before entering into SU (suggesting I have the correct drivers installed). However, when looking in Device Manager there's a yellow triangle next to the device, with an option to update drivers. Any advice? If I need to update the drivers, what drivers are they and were do I find them?
Edit: Picture as described -
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
MrMeeb said:
Oh, okay! I'm trying to do the command as stated, but (while rooted with SuperSU installed) I get the error about adb not being able to run root in production builds. So, I enter the shell with adb shell type su, but then when i type exit and then adb root I get an error saying device not found, even though it shows up when typing adb devices before entering into SU (suggesting I have the correct drivers installed). However, when looking in Device Manager there's a yellow triangle next to the device, with an option to update drivers. Any advice? If I need to update the drivers, what drivers are they and were do I find them?
Edit: Picture as described -
Click to expand...
Click to collapse
Uninstall any driver installed + Xperia companion then install ADB drivers from here:
http://adbdriver.com/downloads/
Here you can find a guide how to install ADB drivers on Windows 8 or 10:
http://adbdriver.com/documentation/how-to-install-adb-driver-on-windows-8-10-x64.html
Also make sure you have enabled USB Debugging from Developer options menu on your phone before connecting it to PC.
OsGhaly said:
Uninstall any driver installed + Xperia companion then install ADB drivers from here:
http://adbdriver.com/downloads/
Here you can find a guide how to install ADB drivers on Windows 8 or 10:
http://adbdriver.com/documentation/how-to-install-adb-driver-on-windows-8-10-x64.html
Also make sure you have enabled USB Debugging from Developer options menu on your phone before connecting it to PC.
Click to expand...
Click to collapse
Thank you! We've done it! I initially managed to install LineageOS using the developer TWRP that could be flashed to boot partition, but after that wanted to have TWRP with LineageOS. Thanks to your advice I just managed to install TWRP using FOTA, so now I have TWRP and LineageOS. Hallelujah! I've given you all the thanks I can on this thread
MrMeeb said:
Thank you! We've done it! I initially managed to install LineageOS using the developer TWRP that could be flashed to boot partition, but after that wanted to have TWRP with LineageOS. Thanks to your advice I just managed to install TWRP using FOTA, so now I have TWRP and LineageOS. Hallelujah! I've given you all the thanks I can on this thread
Click to expand...
Click to collapse
You're welcome dear, glad to hear that you finally got lineage os and TWRP on your phone.. Well done
Sent from my Xperia SP using Tapatalk
Have my Mi 8 about a week, loving it BUT as the bootloader is unlocked I couldn't use Google Pay so I decided to install TWRP and get the Xiaomi.eu ROM.
I just installed TWRP and tried backing up the phone, but I got an error saying it Can not create the folder. I reinstalled TWRP, thinking maybe there was an issue with the first install but now it's stuck in a recovery boot loop. It loads to the MI screen with the unlocked icon but doesn't get to the powered by android, it goes straight into recovery.
The Rom is not on the device and I thought maybe could install it through the recovery but if I have the phone plugged into the laptop (Windows 10) and go into recovery, the touch screen on the phone doesn't work and the phone keeps rebooting itself.
I can also get into Fastboot and the device is detected by miFlash.
What should I do next, I don't trust my instincts. Any advice would be much appreciated. I'm currently downloading the Global Rom off Xiaomi (going to take a while on my 3mb broadband) and hoping I can flash that with miFlash tool, good or bad idea??
U can use otg usb and put the rom on it.
Boot to twrp and wipe data (the one that ask you to say yes? Than install the rom(choose one for recovery flashing not fastboot)
gm007 said:
U can use otg usb and put the rom on it.
Boot to twrp and wipe data (the one that ask you to say yes? Than install the rom(choose one for recovery flashing not fastboot)
Click to expand...
Click to collapse
Cheers for the reply! Unfortunately I don't have an adapter to put the rom on the phone. I'll order one now, always good to have for situations like this.
Any other way of getting the phone up and running sooner? If not, no problem, I'll just have to wait for the adapter.
cherbe.3 said:
Cheers for the reply! Unfortunately I don't have an adapter to put the rom on the phone. I'll order one now, always good to have for situations like this.
Any other way of getting the phone up and running sooner? If not, no problem, I'll just have to wait for the adapter.
Click to expand...
Click to collapse
Sure there must be a fastboot method but didn't tried it yet, i had this phone 3 days ago
Not sure if after formatting data and reboot to twrp you can copy the rom from pc to phone.
One more thing if you use fastboot method be sure not to relock the bootloader cause you may brick ur phone.
If you want to install xiaomi.eu rom dont just wipe data but you have to format data then type yes. Reboot to twrp again. And at twrp recopy the xiaomi.eu rom.
Sent from my MI 8 using Tapatalk
Flash last MIUI global dev. Flash twrp. Wipe only data. Transfer Rom to phone. Flash Xiaomi eu Rom. Done
ariekumbang said:
If you want to install xiaomi.eu rom dont just wipe data but you have to format data then type yes. Reboot to twrp again. And at twrp recopy the xiaomi.eu rom.
Sent from my MI 8 using Tapatalk
Click to expand...
Click to collapse
the only right answer, all other are more or less useless.
you need to wipe data, then format data (confirm with yes)
after that, hold power+up to reboot in twrp again
(or go to mainmenu and choose reboot to recovery),
connect your Mi8 with Usb cable to PC and copy the xiaomi.eu rom to your mi8
and then flash it.
gm007 said:
One more thing if you use fastboot method be sure not to relock the bootloader cause you may brick ur phone.
Click to expand...
Click to collapse
Oh yes, thank you for the reminder, that slipped my mind with this whole mess.
ariekumbang said:
If you want to install xiaomi.eu rom dont just wipe data but you have to format data then type yes. Reboot to twrp again. And at twrp recopy the xiaomi.eu rom.
Click to expand...
Click to collapse
Cheers for the advice, I'll make sure to format before installing. Only issue now is that I can't get the rom onto the phone to install it. Do you reckon if I format the data through TWRP it will then allow me to copy over the rom onto the device? Currently, unless in fastboot, the laptop doesn't recognise the device - constantly reboots the phone causing it to connect and disconnect.
SPOCK_VULKAN said:
Flash last MIUI global dev. Flash twrp. Wipe only data. Transfer Rom to phone. Flash Xiaomi eu Rom. Done
Click to expand...
Click to collapse
I like the sound of this solution but I have a few questions/need clarification as this mess has made me doubt myself (no issue flashing my previous phone mi5)
I downloaded the Global rom from here: http://en.miui.com/download-346.html#523 (just want clarification this is the official rom) I have the latest version of the miFlash. Am I right in thinking, put phone into fastboot, launch tool, locate unzipped rom folder, select 'Clean all' (and not save user data / clean all and lock (presume this means bootloader)) and click Flash??
And then do I start again, flash TWRP and hope it works?
deepblue2000 said:
the only right answer, all other are more or less useless.
you need to wipe data, then format data (confirm with yes)
after that, hold power+up to reboot in twrp again
(or go to mainmenu and choose reboot to recovery),
connect your Mi8 with Usb cable to PC and copy the xiaomi.eu rom to your mi8
and then flash it.
Click to expand...
Click to collapse
If I do this (wipe data and format) will the laptop detect the device to allow me to move the rom onto the phone, currently it doesn't (well it loops between connecting and disconnecting when in TWRP, no issue detecting in fastboot)
normally if twrp is launched, you can copy files as usual from pc to your Mi8
should be a stable connection.. (Win7/10 or any other Win)
if it keeps connecting/disconnecting you can try an other usb port.
do you use the right twrp ?
https://forum.xda-developers.com/mi-8/development/recovery-twrp-3-2-3-0-mi-8-t3837745
and you enabled usb debugging in settings before you flashed twrp ?
(I think without it will not work, even to flash twrp it is needed, so you did it)
deepblue2000 said:
the only right answer, all other are more or less useless.
you need to wipe data, then format data (confirm with yes)
after that, hold power+up to reboot in twrp again
(or go to mainmenu and choose reboot to recovery),
connect your Mi8 with Usb cable to PC and copy the xiaomi.eu rom to your mi8
and then flash it.
Click to expand...
Click to collapse
deepblue2000 said:
normally if twrp is launched, you can copy files as usual from pc to your Mi8
should be a stable connection.. (Win7/10 or any other Win)
if it keeps connecting/disconnecting you can try an other usb port.
do you use the right twrp ?
https://forum.xda-developers.com/mi-8/development/recovery-twrp-3-2-3-0-mi-8-t3837745
and you enabled usb debugging in settings before you flashed twrp ?
(I think without it will not work, even to flash twrp it is needed, so you did it)
Click to expand...
Click to collapse
I've tried several USB ports and different cables, no luck getting it to connect.
No the TWRP installed is 3.2.1-0611-XIAOMI8, yours uses the code name and seems to be a newer version and more legit, I'm going to flash that onto the phone. I presume do it the way I did it before - fastboot, shift right click to get to cmd line...etc.
I did indeed enable usb debugging when I installed it originally.
By the way, thanks so much for your help, I'm lost without my phone - it was love at first sight
Fastboot Flashing Code
Code:
Fastboot boot Twrp.img
Flash the recovery img again inside twrp and reboot to recovery again and it will stay.
If u are new to twrp, format data in twrp and reboot to recovery again and flash this file https://androidfilehost.com/?fid=3700668719832238534 after that u can flash the rom.
If u have already twrp installed, just flash the img in twrp
Click to expand...
Click to collapse
Actually I'm confused now, is this probably where I went wrong in the first place.
Boot the TWRP img and then flash it through TWRP, I've never done it this way before (have I been doing this worng all along?)
and whats the other file about? Disable_Dm-Verity_FEC_v1.1.zip
Sorry about all the questions
you can flash/update twrp inside twrp itself, but you dont need it.
I never used any tools or bat files, just normally installed adb,
and put the twrp.img in the same folder.
then open cmd:
fastboot flash recovery twrp.img
to boot into twrp again:
fastboot boot twrp.img
never heard from this fec1.1 zip, so ignore it.
you should go to the xiaomi.eu forum for help,
https://xiaomi.eu/community/threads...ing-xiaomi-eu-8-8-30.46378/page-2#post-444327
there are the steps posted what to do
deepblue2000 said:
you can flash/update twrp inside twrp itself, but you dont need it.
I never used any tools or bat files, just normally installed adb,
and put the twrp.img in the same folder.
then open cmd:
fastboot flash recovery twrp.img
to boot into twrp again:
fastboot boot twrp.img
never heard from this fec1.1 zip, so ignore it.
you should go to the xiaomi.eu forum for help,
https://xiaomi.eu/community/threads...ing-xiaomi-eu-8-8-30.46378/page-2#post-444327
there are the steps posted what to do
Click to expand...
Click to collapse
Right, so I got TWRP 3.2.3 installed and seems to be working (not disconnecting and reconnecting) BUT the phone is still not recognsed - It says unspecified in the devices . I ran through the ADB set up, all installed including drivers but still no phone showing up. I hate windows 10 and drivers, can't get them to play nice (or it's me)
I had never any problems with Win10 x64,
I dnever installed any driver for my Mi5/6 and now 8,
win10 detects everything automatically, if you have installed any driver, maybe just
uninstall them and restart win10
deepblue2000 said:
I had never any problems with Win10 x64,
I dnever installed any driver for my Mi5/6 and now 8,
win10 detects everything automatically, if you have installed any driver, maybe just
uninstall them and restart win10
Click to expand...
Click to collapse
AND WE'RE IN!!! THANK YOU, THANK YOU!! If you were here I'd hug you and get you a drink.
Forget my above nonsense and babble, PC wasn't happy with whatever was going on, once I got brave enough and actually followed your instructions in all fell into place!!
So conclusion -
I had the wrong TWRP (3.2.3 is needed)
PC didn't like whatever was happening without the OS
Wiped and formatted through TWRP - Phone was recognised
Dragged Xiaomi.eu rom over - copied perfectly
Flashed rom - successful and the wiped cache again to be safe
Rebooted and my smile came back the moment I saw the 'powered by android' icon
Went through set up and I'm back in.
Mi 8 - bootloop and locked device, no system, help?
Hi guys,
I did a pretty much bad thing on my phone, I've just bought it 2 weeks ago and I was loving the phone, my phone is unlocked but today I was rooting to install google camera with night sight and I don't know why my twpr was really weird, when pressing install all the folder that was showing was very different from youtube videos about mi 8 root and even compared to my old devices, it was showing folders like licence and others, but the weirdest was inside the sdcard folder that was showing a lot of unnamed folders(like this: 54u3hu6ijj4!ji5), the thing got worse when I've flashed magisk and the phone got stuck on bootloop, after that tried to flash a stock global rom from official Mi website on fastboot mode using Mi Flash Toll, what I did wrong is that I didn't see that the Lock option was ticked and than I pressed to flash, everything was going good when my device showed a message saying that the Miui wasn't compatible with my phone. After that I've tried to install TWPR again but my phone was locked by the Mi flash toll and know my device is without system and unlocked. I've also tried to unlock but is saying that my account is not bound to my device, so I have no idea what to do, I'm gonna never root any phone ever, worse thing I did.
Can Anybody know what I can do to unlock the phone?
Sorry about my English, that's not my native language.