I tried to flash the team spain 5.8 recovery but it does not work , flash seem to go well but still only boots into stock recovery.
Rom is 15s
zsajak said:
I tried to flash the team spain 5.8 recovery but it does not work , flash seem to go well but still only boots into stock recovery.
Rom is 15s
Click to expand...
Click to collapse
http://forum.xda-developers.com/showpost.php?p=68462069&postcount=2
sanke1 said:
http://forum.xda-developers.com/showpost.php?p=68462069&postcount=2
Click to expand...
Click to collapse
How can I follow your guide If I cannot flash the recovery?
zsajak said:
How can I follow your guide If I cannot flash the recovery?
Click to expand...
Click to collapse
Are you having correct adb drivers installed? On my PC Windows 10 X64, they get installed from Windows Update and show up as "London Marshal adb interface."
It wouldn't hurt to try a different USB port.
Also try fully resetting your phone to factory default from the settings.
I am using X821 and only the TWRP recovery posted in my guide works. Other recoveries do not work for our device.
BTW I have updated my guide. Check it out again.
sanke1 said:
Are you having correct adb drivers installed? On my PC Windows 10 X64, they get installed from Windows Update and show up as "London Marshal adb interface."
It wouldn't hurt to try a different USB port.
Also try fully resetting your phone to factory default from the settings.
I am using X821 and only the TWRP recovery posted in my guide works. Other recoveries do not work for our device.
BTW I have updated my guide. Check it out again.
Click to expand...
Click to collapse
For some reason it was not working, it is now.
I still get a bootloop when I try to flash the resurrection remix rom.
cm13 by teamspain worked fine though
sanke1 said:
Are you having correct adb drivers installed? On my PC Windows 10 X64, they get installed from Windows Update and show up as "London Marshal adb interface."
It wouldn't hurt to try a different USB port.
Also try fully resetting your phone to factory default from the settings.
I am using X821 and only the TWRP recovery posted in my guide works. Other recoveries do not work for our device.
BTW I have updated my guide. Check it out again.
Click to expand...
Click to collapse
I followed your guide and installed twrp correctly and it worked.
I cannot install any rom besides cm13 unofficial though, i always get a bootloop if I install resurrection remix for example.
Its really very annoying, I wiped everything including data and system, only the official 16s roms works and cm13 unofficial, all other roms result in a bootloop.
something is not right here.
twrp not mounting storage data
sanke1 said:
Are you having correct adb drivers installed? On my PC Windows 10 X64, they get installed from Windows Update and show up as "London Marshal adb interface."
It wouldn't hurt to try a different USB port.
Also try fully resetting your phone to factory default from the settings.
I am using X821 and only the TWRP recovery posted in my guide works. Other recoveries do not work for our device.
BTW I have updated my guide. Check it out again.
Click to expand...
Click to collapse
twrp flased but its not mounting storage data, also sideload command to install supersu.zip didnt worked tried several times
its just stopping exactly at 73% everytime
Related
Right now my phone is stuck in recovery with no ROM installed, so I tried to adb sideload one.
Whenever I try to do anything with adb, my phone does not register at all with my computer under adb devices.
Is there any way someone could help?
cortem said:
Right now my phone is stuck in recovery with no ROM installed, so I tried to adb sideload one.
Whenever I try to do anything with adb, my phone does not register at all with my computer under adb devices.
Is there any way someone could help?
Click to expand...
Click to collapse
What is your recovery?
cortem said:
Right now my phone is stuck in recovery with no ROM installed, so I tried to adb sideload one.
Whenever I try to do anything with adb, my phone does not register at all with my computer under adb devices.
Is there any way someone could help?
Click to expand...
Click to collapse
Make sure u have installed the drivers on ur PC.....
If u havent installed Try HTC Sync that will automatically install the necessary drivers...........
Gud luck
Danny Samuel said:
Make sure u have installed the drivers on ur PC.....
If u havent installed Try HTC Sync that will automatically install the necessary drivers...........
Gud luck
Click to expand...
Click to collapse
Also, let us know the OS you are using.. Win 8 x64 is a tricky BS.. sometimes the drivers work, some times they don't...
for my recovery, I have TWRP 2.5.0.0
I'll check my drivers just in case.
For my computer OS, I have windows 7 x64
I'm on Windows 7 and had the same problem the other night when I needed to sideload a rom, it just would not find my device. Even though I had previously flashed kernels without any issues.
I ended up removing the drivers, re-installing them using Hassoons toolkit and rebooting both PC and phone. It will work, just can be a bit finnicky. I used his toolkit to sideload a rom through twrp.
cortem said:
for my recovery, I have TWRP 2.5.0.0
I'll check my drivers just in case.
For my computer OS, I have windows 7 x64
Click to expand...
Click to collapse
I hope you are giving enough time for the device to be recognized.
BTW TWRP has been updated to 2.6
Sent from my GT-I9300 using xda premium
OK, so I flashed TWRP and now I have sort of a halfway bricked x829- I can load TWRP and Fastboot, that's it. I can't adb sideload anything because I get a "cannot read" error. I also can't Fastboot flash anything because all the ROMs I can find are zip files, and not .img files. What am I doing wrong?
Wagmans said:
OK, so I flashed TWRP and now I have sort of a halfway bricked x829- I can load TWRP and Fastboot, that's it. I can't adb sideload anything because I get a "cannot read" error. I also can't Fastboot flash anything because all the ROMs I can find are zip files, and not .img files. What am I doing wrong?
Click to expand...
Click to collapse
ok why do you even want to flash the rom with adb/fastboot?
even if you forgot to cp the rom onto the sdcard - just flash with twrp from a stick - OTG works fine
Horsebeatsbishop said:
ok why do you even want to flash the rom with adb/fastboot?
even if you forgot to cp the rom onto the sdcard - just flash with twrp from a stick - OTG works fine
Click to expand...
Click to collapse
OTG not working for me either. I have a USB C to standard USB adapter and it doesn't see any flash drives (I can see the drive being accessed- the light flashes, but doesn't mount). Do I need a USB OTG C Y adapter? I'm a bit lost why I can't just adb sideload.
Someone explain it to me like I'm a child. Obviously I'm doing something wrong and I'm missing something.
Wagmans said:
OTG not working for me either. I have a USB C to standard USB adapter and it doesn't see any flash drives. Do I need a USB OTG C Y adapter? I'm a bit lost why I can't just adb sideload.
Someone explain it to me like I'm a child. Obviously I'm doing something wrong and I'm missing something.
Click to expand...
Click to collapse
ok sounds like a toughie - never had a problem with OTG (neither with fat32 nor ntfs both works (twpr 3.0.2.1 myself) )
since i'm just a beginner myself i can only give you ideas where i would look:
-do you even see your device in adb service?
-enabled usb-debug?
-current usb driver?
-current adb version?
-correct adb version (32/64b)?
Horsebeatsbishop said:
ok sounds like a toughie - never had a problem with OTG (neither with fat32 nor ntfs both works (twpr 3.0.2.1 myself) )
since i'm just a beginner myself i can only give you ideas where i would look:
-do you even see your device in adb service?
-enabled usb-debug?
-current usb driver?
-current adb version?
-correct adb version (32/64b)?
Click to expand...
Click to collapse
I flashed TWRP properly- but when I put it into recovery I get half a corrupted screen- after the screen goes off if I press the power button I can access TWRP.
I tried flashing multiple flash drives in different formats- yes, I can see the drive LEDs flash after I insert it, but when I try to mount it says "0" space for all drives.
So, I assume everything is working properly because adb can see the device in sideload mode (Win 10 device mgr shows it as a USB device, when in TWRP (no sideload mode) it sees it as ADB device- but when I try to run ADB it doesn't show any devices):
List of devices attached
17963e29 sideload
No devices listed when sideload in TWRP is off.
I should be able to sideload something, but I get:
loading: 'le_x2_x820-5.9.020S.zip'
* cannot read 'le_x2_x820-5.9.020S.zip' *
Every time- every file.
Bricked?
are you using the official twrp ?
you should... https://twrp.me/devices/leecolemax2.html
or use multirom.
you can also transfer the rom first using mtp (in twrp).and flash afterwards.
Gesendet von meinem LEX820 mit Tapatalk
A.N.Droid said:
are you using the official twrp ?
you should... https://twrp.me/devices/leecolemax2.html
or use multirom.
you can also transfer the rom first using mtp (in twrp).and flash afterwards.
Gesendet von meinem LEX820 mit Tapatalk
Click to expand...
Click to collapse
FlashTools64_20161125.zip
I figured it out. I had to download FlashTools64 from Asus in order to sideload the file without the "cannot read" error. Well, that took me all morning.
This should be posted in the TWRP sticky.
I'm sideloading a rom right now. Let's see what happens...
Wagmans said:
FlashTools64_20161125.zip
I figured it out. I had to download FlashTools64 from Asus in order to sideload the file without the "cannot read" error. Well, that took me all morning.
This should be posted in the TWRP sticky.
I'm sideloading a rom right now. Let's see what happens...
Click to expand...
Click to collapse
looks like the standard 15 sec adb installer to me... seems u had the wrong version
Horsebeatsbishop said:
looks like the standard 15 sec adb installer to me... seems u had the wrong version
Click to expand...
Click to collapse
I don't know- I dowloaded it right from the link in the TWRP thread.
Anyways. now when I'm sideloading a ROM it times out at 46% every time (TWRP stops sideload mode). Any ideas?
Wagmans said:
I don't know- I dowloaded it right from the link in the TWRP thread.
Anyways. now when I'm sideloading a ROM it times out at 46% every time (TWRP stops sideload mode). Any ideas?
Click to expand...
Click to collapse
I had sort of the same problem, your not encrypted are you?
Supertacomonkeyexplosion said:
I had sort of the same problem, your not encrypted are you?
Click to expand...
Click to collapse
Nope. Unless I can sideload a ROM I'm stuck because TWRP won't mount a flash drive for me.
why dont you transfer the zip first with mtp?
Gesendet von meinem LEX820 mit Tapatalk
Wagmans said:
Nope. Unless I can sideload a ROM I'm stuck because TWRP won't mount a flash drive for me.
Click to expand...
Click to collapse
You can't boot the OS at all ?
I flashed twrp, couldn't backup,side load or read any OTG. I ended up booting back into my stock OS, loosing twrp, putting teamspain cm13 on, reflashing twrp from fastboot then immediately booting into twrp and flashing CM zip.
Mine was encryption problem though, cm let me decrypt and twrp started working right
Supertacomonkeyexplosion said:
You can't boot the OS at all ?
I flashed twrp, couldn't backup,side load or read any OTG. I ended up booting back into my stock OS, loosing twrp, putting teamspain cm13 on, reflashing twrp from fastboot then immediately booting into twrp and flashing CM zip.
Mine was encryption problem though, cm let me decrypt and twrp started working right
Click to expand...
Click to collapse
Nope. Just TWRP, that's it. As for MTP it doesn't even show up- just as a Android ADB Device in the drivers when in TWRP, and as a USB Device in TWRP Sideload mode. Remember, I'm stuck in either TWRP or Fastboot mode.
Wagmans said:
Nope. Just TWRP, that's it. As for MTP it doesn't even show up- just as a Android ADB Device in the drivers when in TWRP, and as a USB Device in TWRP Sideload mode. Remember, I'm stuck in either TWRP or Fastboot mode.
Click to expand...
Click to collapse
you have strange issues. are you sure you installed the right twrp version for your device? a link would help.
about adb:
i'm using universal ADB drivers and it just works.
http://adbdriver.com
Gesendet von meinem LEX820 mit Tapatalk
Wagmans said:
Nope. Just TWRP, that's it. As for MTP it doesn't even show up- just as a Android ADB Device in the drivers when in TWRP, and as a USB Device in TWRP Sideload mode. Remember, I'm stuck in either TWRP or Fastboot mode.
Click to expand...
Click to collapse
Strange that you lost your OS just flashing a recovery image, I've never seen that before. My last suggestion would be to fastboot flash a earlier version of TWRP.
Not sure of you seen this..... Last resort if you can't figure it out
https://forum.xda-developers.com/le-max-2/how-to/guide-hard-brick-fix-qualcomm-hs-usb-t3492949
Getting closer- I gave up on sideloading and I was finally able to push a ROM to the phone.
Thanks for all the help guys. Now running Chinese .20s ROM. Took long enough.lol
Wagmans said:
Getting closer- I gave up on sideloading and I was finally able to push a ROM to the phone.
Thanks for all the help guys. Now running Chinese .20s ROM. Took long enough.lol
Click to expand...
Click to collapse
Glad you figured it out.
Your running Chinese 20s on x829?
Lots of people will be interested to know how it runs..... Fingerprint? Language? Band 20? VoLTE?
Supertacomonkeyexplosion said:
Glad you figured it out.
Your running Chinese 20s on x829?
Lots of people will be interested to know how it runs..... Fingerprint? Language? Band 20? VoLTE?
Click to expand...
Click to collapse
Been playing with it a bit:
Shows as X820 with 64GB
Fingerprint still doesn't work for me
Google Voice doesn't work- at least I haven't figured it out (Doesn't recognize "OK Google"- I have to go into the app by hand).
Same problem- no VoLTE on AT&T here in US (didn't think it would work- unsupported phone). On Band 2 with LTE (cycled it- was on band 17 before). Haven't checked the other bands yet.
Lots of bloatware. That I can deal with. If I can't get Google voice recognition working properly I'll probably go to a custom ROM.
Wagmans said:
Getting closer- I gave up on sideloading and I was finally able to push a ROM to the phone.
Thanks for all the help guys. Now running Chinese .20s ROM. Took long enough.lol
Click to expand...
Click to collapse
You should share how did u fix it for helping other people in the future
Enviado desde mi ASUS_Z00TD mediante Tapatalk
My p9000 is currently on 20160810 and I'm unable to do the OTA update to 20170112, every time it downloads and starts to install it just stays on "rebooting" but does nothing.
On top of that I've tried to connect it up to a PC to flash it instead (was looking to try Nougart), I've managed to succesfully install the drivers but whatever PC I plug it into when powered off the PC recognises it for a few seconds and then disconnect again. So I have no device in device manager to try to play with the drivers, although as I mentioned I have already installed them sucessfully.
Should also mention I can't hard reset it with the power and voulume+ option either, as unable to enter recovery.
I've tried with Windows 7/8.1/10 all with the same result. The only difference is on the windows 7 machine it recognises it as the mtx65preloader device for a split second.
But to confuse things now more, on my windows 8.1 device the elephone is no longer recognised as a storage device, it shows as a connected device but there is no access to the drive.
The only way to go to the newer 2017 versions of the stock roms (nougat or marshmallow) is to use spflashtools. It is because elephone broke the recovery in 2016810. So when you try to update it will fail because the stock recovery is broken.
Have you disabled the driver signature in windows 10/ 8/ 7 before installing the mtk drivers? Else the installation will fail and you won't have the drivers installed at all.
I used this tutorial and it works for me on windows 10.
https://forum.xda-developers.com/elephone-m2/help/windows-10-mtk-vcom-usb-drivers-32-64-t3267033
Hexyl said:
The only way to go to the newer 2017 versions of the stock roms (nougat or marshmallow) is to use spflashtools. It is because elephone broke the recovery in 2016810. So when you try to update it will fail because the stock recovery is broken.
Have you disabled the driver signature in windows 10/ 8/ 7 before installing the mtk drivers? Else the installation will fail and you won't have the drivers installed at all.
I used this tutorial and it works for me on windows 10.
https://forum.xda-developers.com/elephone-m2/help/windows-10-mtk-vcom-usb-drivers-32-64-t3267033
Click to expand...
Click to collapse
Drivers were all installed fine, but the strangness continued today but for the good. On the Windows 7 machine I managed to flash the Nougart rom and now all is working great. So after days of nothing working it just suddenly decide to co-operate.
with a "broken" recovery, isn't dangerous to do any update operations? if something get corrupted how can you resolve?
Hexyl said:
The only way to go to the newer 2017 versions of the stock roms (nougat or marshmallow) is to use spflashtools. It is because elephone broke the recovery in 2016810. So when you try to update it will fail because the stock recovery is broken.
Have you disabled the driver signature in windows 10/ 8/ 7 before installing the mtk drivers? Else the installation will fail and you won't have the drivers installed at all.
I used this tutorial and it works for me on windows 10.
https://forum.xda-developers.com/elephone-m2/help/windows-10-mtk-vcom-usb-drivers-32-64-t3267033
Click to expand...
Click to collapse
Fabioamd87 said:
with a "broken" recovery, isn't dangerous to do any update operations? if something get corrupted how can you resolve?
Click to expand...
Click to collapse
You simply can't do an ota update if the phone has a broken recovery. It won't install because it fails booting in the recovery. So nothing goes corrupted.
no I mean if the flash fails how you can recover without a working recovery mode?
Well mines been working without a problem for the past week, quite impressed with it.
Fabioamd87 said:
no I mean if the flash fails how you can recover without a working recovery mode?
Click to expand...
Click to collapse
Then try to Flash again. As far as I know the stock recovery can't restore backups. It is for installing ota updates and etc, I think. If you want to backup your ROM then flash a custom recovery with sp flashtools.
Can I flash again if the first flash fails? from where I do it , there is some kind of "download mode/fastboot"? Do I need to root the phone to flash a custom recovery?
thanks
Fabioamd87 said:
Can I flash again if the first flash fails? from where I do it , there is some kind of "download mode/fastboot"? Do I need to root the phone to flash a custom recovery?
thanks
Click to expand...
Click to collapse
I assume you have never installed a ROM/recovery before on your phone (with a mediatek soc). In that case, you flash your phone with a PC. You flash the phone with a program called "sp flashtools".
So the very first time you want to install a CUSTOM ROM/recovery. ---> use sp flashtools.
If you already have a custom recovery installed ----> boot the phone up in recovery (holding power button and volume +. If elephone logo appears, release power button but keep pressing volume +) and install custom ROM from there.
If you want to flash a STOCK rom ( nougat or marshmallow) -----> use sp flashtools.
You do not need a rooted phone for flashing a custom recovery.
For sp flashtools tutorials etc, look it up on XDA or just Google some spflashtool tutorials. The steps are the same for most mtk phones.
I have tried installing through ADB and used the one provided by KingOfMezi. Have also tried the automated installation of CATUVA21. It always brings me to the Huawei eRecovery. I have unlocked bootloader, USB Debugging is on too.
First indicate which version are you in, Noughat or Oreo ??? I say so bcoz there are separate recoveries for
the 2 versions of Android available here @ XDA
Also indicate what happens when you try to flash the TWRP after fastboot command, does it say
FAILED or any error or it installs properly ? Send screenshot of your fastboot command and its result
themagicalmage22 said:
I have tried installing through ADB and used the one provided by KingOfMezi. Have also tried the automated installation of CATUVA21. It always brings me to the Huawei eRecovery. I have unlocked bootloader, USB Debugging is on too.
Click to expand...
Click to collapse
If i were you dont install twrp now. On huawei nova 2i because the device is new. Developers of twrp have some issue to backup all of the system data. So it is useless and remember you cant update OTA. I rooted and install twrp now i regret. Because stock roms and software update are hard to find. And you cant flash it so easy. Im just giving you an idea.
Hello,
A long time ago my brother has done something more stupid – had made root in Sony Xperia Z2 with TWRP, using the latest version of Sirius. As he has bought his new mobile phone, he has given me his old mobile phone, but he was not interested in formatting, de-rooting or fixing the bug of AudioFX, then I decided to work on my own. I made a lot of researches about how to fix the bug of AudioFX, so no luck.
As I wanted to de-root, I had to use my friend and sister's computers with Windows, using Kingo Root, because I am a Linux user, but no luck.
Then I downloaded the original and de-rooted image from TWRP, booted into TWRP mode, and flashed that image into Recovery. After, I could not boot any more. I tried to press power and Volume - and Volume +, but I could not boot either. I plugged the mobile phone into my laptop with Linux, but it was not recognised.
I read the following topics of XDA Developers, trying to train myself, but no luck:
1. Problem with TWRP 3.0.2 and encryption to solve boot loop
2.. [Q] Flashtool tool failed after amss_fsg.sin, can't flash phone
3. Downgrade to KitKat?
4. Unknown firmware, no boot, I can't flash
5. I can not flash!
6. Boot loop after flashing any ROM
7. To flash the recover Rebooting into TWRP recovery ... adb is not recognized
gusbemacbe said:
Hello,
A long time ago my brother has done something more stupid – had made root in Sony Xperia Z2 with TWRP, using the latest version of Sirius. As he has bought his new mobile phone, he has given me his old mobile phone, but he was not interested in formatting, de-rooting or fixing the bug of AudioFX, then I decided to work on my own. I made a lot of researches about how to fix the bug of AudioFX, so no luck.
As I wanted to de-root, I had to use my friend and sister's computers with Windows, using Kingo Root, because I am a Linux user, but no luck.
Then I downloaded the original and de-rooted image from TWRP, booted into TWRP mode, and flashed that image into Recovery. After, I could not boot any more. I tried to press power and Volume - and Volume +, but I could not boot either. I plugged the mobile phone into my laptop with Linux, but it was not recognised.
I read the following topics of XDA Developers, trying to train myself, but no luck:
1. Problem with TWRP 3.0.2 and encryption to solve boot loop
2.. [Q] Flashtool tool failed after amss_fsg.sin, can't flash phone
3. Downgrade to KitKat?
4. Unknown firmware, no boot, I can't flash
5. I can not flash!
6. Boot loop after flashing any ROM
7. To flash the recover Rebooting into TWRP recovery ... adb is not recognized
Click to expand...
Click to collapse
Sounds like you just soft bricked your device. ?
As far as i know it's easily fixable.
I might be able to help you out with few more info. ✌
Was it a 3G one or a LTE one ?
What rom were you on ?
A custom one or stock one ?
And what exactly do you want to achieve ? A stock rom with no root ? ?
In answer to Minato
Hello
~ Minato ~ said:
Sounds like you just soft bricked your device.
Was it a 3G one or a LTE one ?
Click to expand...
Click to collapse
It was a 3G.
~ Minato ~ said:
Sounds like you just soft bricked your device.
What rom were you on ?
Click to expand...
Click to collapse
It is custom. Android 8.1 TWRP Sirius with root.
~ Minato ~ said:
Sounds like you just soft bricked your device.
And what exactly do you want to achieve ? A stock rom with no root ? ?
Click to expand...
Click to collapse
An original ROM without root. I know a de-rooted and rooted Android 7 and 8 cause AudioFX bugs.
Can You still boot into twrp ?
If so did you try flashing a stock rom via a zip ?
Or you can use the fastboot but i won't be much of a help unless you have a windows pc ,i'm not familiar with Linux ?
In answer to Minato
~ Minato ~ said:
Can You still boot into twrp?
Click to expand...
Click to collapse
No
~ Minato ~ said:
Or you can use the fastboot but i won't be much of a help unless you have a windows pc, i'm not familiar with Linux.
Click to expand...
Click to collapse
As I can not boot into TWRP, it is impossible to use FastBoot, using Windows. I did it once.
gusbemacbe said:
No
As I can not boot into TWRP, it is impossible to use FastBoot, using Windows. I did it once.
Click to expand...
Click to collapse
Did you install the fastboot unsigned drivers as + ADB ?
Whole process should be something like this
Disable windows driver signature enforcement.
[URL="https://www.howtogeek.com/167723/how...igned-drivers/"][/URL]
Restart your pc or laptop.
Install ADB.
https://drive.google.com/open?id=0B0MKgCbUM0itSUhpUklCTFpzWkE&authuser=0
Install flashtool-0.9.18.6 with all the drivers.
(For some reason this is the most compatible one for Xperia Z2)
Then try flash twrp recovery using the flashtool. ✌