Related
Hi,
I'm awfully sorry to bother you, but I'm really stuck.
Been using my XZ for over a year now. Everything stock.
I then unlocked the bootloader, rooted it and flashed the latest stable release of CM (didn't use the flashtool for any of this)
CM was totally fine for me except for the camera app.
So I searched the board for a ROM that is better suited for my needs and found this:
http://forum.xda-developers.com/xperia-z/development/rom-existenz-ultimate-1-0-0-light-dark-t2779949
And this is where my problems began -->
Flash official Sony's 4.2.2 10.3.1.A.2.74 or 10.3.1.A.2.67 with flashtool (http://forum.xda-developers.com/show....php?t=2162907)
Even after hours and hours of tying, I cant get this working.
What I did so far:
Installed flash-tool; java development kit, android development kit, adb & fastboot drivers (via several different methods)
Windows (Win 7 64 Bit) recognizes my device as Sony Sa0107 when connected in normal mode.
And it recognizes it as S1 Device when connected in fastboot mode.
So, when I start the flashtool and get to the point where flashtool prompts me to connect my device in fastboot mode this happens:
it says that it didn't recognize my device and I have to search for the device in a list. I click on the XZ entry and flashtool then gets stuck. Just shows the screen where it says you to connect in fastboot.
I even tried to create cwm flashable zip to get around using the flashtool...but this didnt work out..
Has anyone any idea what I could have done wrong?
J26M377 said:
Hi,
I'm awfully sorry to bother you, but I'm really stuck.
Been using my XZ for over a year now. Everything stock.
I then unlocked the bootloader, rooted it and flashed the latest stable release of CM (didn't use the flashtool for any of this)
CM was totally fine for me except for the camera app.
So I searched the board for a ROM that is better suited for my needs and found this:
http://forum.xda-developers.com/xperia-z/development/rom-existenz-ultimate-1-0-0-light-dark-t2779949
And this is where my problems began -->
Flash official Sony's 4.2.2 10.3.1.A.2.74 or 10.3.1.A.2.67 with flashtool (http://forum.xda-developers.com/show....php?t=2162907)
Even after hours and hours of tying, I cant get this working.
What I did so far:
Installed flash-tool; java development kit, android development kit, adb & fastboot drivers (via several different methods)
Windows (Win 7 64 Bit) recognizes my device as Sony Sa0107 when connected in normal mode.
And it recognizes it as S1 Device when connected in fastboot mode.
So, when I start the flashtool and get to the point where flashtool prompts me to connect my device in fastboot mode this happens:
it says that it didn't recognize my device and I have to search for the device in a list. I click on the XZ entry and flashtool then gets stuck. Just shows the screen where it says you to connect in fastboot.
I even tried to create cwm flashable zip to get around using the flashtool...but this didnt work out..
Has anyone any idea what I could have done wrong?
Click to expand...
Click to collapse
Why are you trying to flash Flash official Sony's 4.2.2 10.3.1.A.2.74 or 10.3.1.A.2.67 with flashtool? If you are rooted and unlocked bootloader, you must have a custom recovery installed? I'm pretty sure that installing of an older official Sony firmware is mentioned at the installing instructions only to be able to root the XZ.
Try this:
1) Backup
2) Reboot to recovery
3) Wipe Data, Cache and Dalvik Cache
4) Flash the rom (existenz-ultimate)
Kariharri said:
Why are you trying to flash Flash official Sony's 4.2.2 10.3.1.A.2.74 or 10.3.1.A.2.67 with flashtool? If you are rooted and unlocked bootloader, you must have a custom recovery installed? I'm pretty sure that installing of an older official Sony firmware is mentioned at the installing instructions only to be able to root the XZ.
Try this:
1) Backup
2) Reboot to recovery
3) Wipe Data, Cache and Dalvik Cache
4) Flash the rom (existenz-ultimate)
Click to expand...
Click to collapse
Hi,
thank you for your reply.
Your version gets me stuck in a bootloop (cm logo).
I didn't need to install an older firmware, I was just using the Auto root files from doomlord “Z_DooMLoRD_CF-Auto-Root-ported_FW-350.img” & “Z_DooMLoRD_insecure_FW-350.img)
Did you wipe cache after flashing cm?
Thank you for your help.
I finally figured out what I did wrong.
I booted my phone in fastboot mode not flashmode (as it clearly stated by the flashtool ^^)
I guess I shouldn't have followed the guides so blindly.
Sorry for the double post, but I cant post in the existenz thread (not allowed to).
Is it possible to install a different theme for this rom (like this one: https://play.google.com/store/apps/...DIxMiwiY29tLm1hYy50aGVtZS5TaW1wbGV4LmJsdWUiXQ.. )
Didn't find an option in this rom
no as that's a cm11 theme and you are now on a stock based rom, have a look in the thread for themes, that's if anyone has made them
Hello i was using this guide :
http://forum.xda-developers.com/nexus-6/general/how-to-nexus-6-one-beginners-guide-t2948481
to root my phone i went and finished fastboot oem unlock step
the problem is after it and booted the phone i extracted the root files and clicked on it
then realized it said oem is not enabled in developer option
so now when i boot the phone a message says"Your Device is Corrupt. It can't be trusted and may not work properly."
and after it like 1-2 sec it turns off
i can still boot in bootloader
PLEASE SOME ONE HELP ME
Also it says device is unlocked in the bootloader statues code 3
extra information i was using android marshmallow 6 latest firmware
oudric said:
Hello i was using this guide :
http://forum.xda-developers.com/nexus-6/general/how-to-nexus-6-one-beginners-guide-t2948481
to root my phone i went and finished fastboot oem unlock step
the problem is after it and booted the phone i extracted the root files and clicked on it
then realized it said oem is not enabled in developer option
so now when i boot the phone a message says"Your Device is Corrupt. It can't be trusted and may not work properly."
and after it like 1-2 sec it turns off
i can still boot in bootloader
PLEASE SOME ONE HELP ME
Also it says device is unlocked in the bootloader statues code 3
extra information i was using android marshmallow 6 latest firmware
Click to expand...
Click to collapse
The same thing happened to me when I tried to use a rootkit method for rooting the phone when it apparently knew nothing about the most recent updates (MRA58N or MRA58R). I ended up having to manual flash each individual image file from the MRA58N factory image (the flash-all script in the factory image zip wouldn't work). Even so, when I rebooted it still displayed the Your Device is Corrupt message. Then I went through the manual root process again (flashed the modified boot.img through fastboot, then flashed the latest TWRP recovery via fastboot, and then used TWRP to flash the latest SuperSU. Only then did the Your Device is Corrupt message go away and I also had root with everything else working fine.
It definitely made for an un-Godly horrible first 24-hours with my new phone! I hope this helps you.
internetpilot said:
The same thing happened to me when I tried to use a rootkit method for rooting the phone when it apparently knew nothing about the most recent updates (MRA58N or MRA58R). I ended up having to manual flash each individual image file from the MRA58N factory image (the flash-all script in the factory image zip wouldn't work). Even so, when I rebooted it still displayed the Your Device is Corrupt message. Then I went through the manual root process again (flashed the modified boot.img through fastboot, then flashed the latest TWRP recovery via fastboot, and then used TWRP to flash the latest SuperSU. Only then did the Your Device is Corrupt message go away and I also had root with everything else working fine.
It definitely made for an un-Godly horrible first 24-hours with my new phone! I hope this helps you.
Click to expand...
Click to collapse
can you please tell me steps i am so afraid to do anything to my phone now and i think my problem is same as yours
i downloaded 6.0.0 (MRA58R) and i used option in toolkit flash stock it gave me an error
"failed (data transfer failure (unknown error))
Its not so easy to brick nexus, but make sure you don't lock bootloader before your phone is working right. You can find the guide how to flash it on XDA.
You will need to flash the missing files by hand.
I was able to fix the erro i got by flashing by :
setting up environmental variable
copy all the flash files, all.bat bootloaderXXX.img... etc to platform tools folder
made sure i connected into usb 2.0 port not usb 3.0
then i flashed the stock firmware XD now my phone to point zero again
oudric said:
I was able to fix the erro i got by flashing by :
setting up environmental variable
copy all the flash files, all.bat bootloaderXXX.img... etc to platform tools folder
made sure i connected into usb 2.0 port not usb 3.0
then i flashed the stock firmware XD now my phone to point zero again
Click to expand...
Click to collapse
You don't need to move the files to the platform-tools folder.
Go to Nexus 6 General > Sticky rol-up thread > Adb and fastboot. What is it?
This will tell you how to set up and use adb or fastboot properly.
Hi,
I'm having a problem installing TWRP on my doogee X5, in order to root the device. I have tried to flash the recovery with sp flash tool, and every time I try, I can boot to the boot mode menu, select "recovery" and see the doogee logo for a while, then a black screen, then the doogee logo again, following into a normal boot.
This is the X5, not the X5 pro.
firmware on phone: "DOOGEE-X5-B-Android5.1-2016.03.18"
Any help?
PS: I don't want to use kingroot to root the phone, as I also want xposed.
I'm looking for a solution to that very problem too. Let's see if someone comes to help!
Exactly the same goes here too. Probably there's not an updated TWRP for V18 which I am using. I have not the slightest idea who could help us.
Rooting Doogee X5 / TWRP install
Here's what worked for me, thought I'd share this.
Out of the box was on version 18 and wanted to root , so i blindly installed King Root which did work, i then installed Supeer SU me which changed the king root to super user. After that over a week i read that TWRP 3.0.2 worked for one person so using Flashify i flashed the recovery image , after changing it to recovery.img and it worked . Such luck right, i went on to read the forums as im in love with this device , Wakefield helpful was NEEDROM.com , you need to register but there are many roms and tools for mediatek 6580soc . Out of curiosity i downloaded some rar. File roms ACS different fish tools. The best to use if you've only got oneX5 is SP flash tool. Also look for mediatek vcom drivers which auto installs the correct drivers. There are easy to follow you tube videos fur flashing using SP Flash tool. The latest version had been updated for simplicity. the process basically is ( load .bin file in its respective area,( from Flash tool) and load scatter.txt in its box ( from rar. File) the whole interface will polemist populate plug go to format hit start plug in turned off phone without battery, it'll give red then yellow bar and a check, then unplug hi to firmware screen and choose to start dload only except bootloader, start , plug wait for coloured bars and check your done. i even had gotten errors due to a faulty dload and repeated the process till i got it. I understand that not all have the patience for this, therefore i suggest using flash tool of king root messes up though that's rare.
An alternative to supersu me is to root with king root then install twrp with flashify then you can uninstall / repack king root and flash Updateroot.Script available by someone on needrom. That includes super user and busy box. Then installxposed. Etc.
* Each process in the above proven tuturial has been obtained online from other sites not just xda. I've chosen 5.1 as an idealOS for me, I can't say the route to take fur Marshmallow.
This is for -b and non b only version 18, and 19. All others take your own chances but it's resilient chip so have fun.
(SOLVED just flash DOOGEE-X5-HOT2-6.0.zip and the twrp from the rom is installed and works after rebooting in recovery mode.) after flashing CWM recovery
Listed: 10/28/2016 11:16 pm
ROM Version: 6.0 / 5.1 to my doogeex5 (flashing succeed) i got an green android logo with an error sighn(see picture)and some chinese letters...
in normal boot no problem,also upgrading to android 6 (flashed) gave no problem...
how to get new recovery(flashing other recovery`s gave same output exept the chinese sighns disapeard)
kingroot V4.80 couldnt root my doogeex5 after 27%rooting it says cant root device
also doesnt the system update in `my device` recognice the memory card ...no sd card inserted...
any suggestions?
I have a similar problem. Unlocking the boot loader works fine, but i can't seem to find a working twrp file for my phone.
I have an X5 pro (x5pro-android5.1-r17-2015.07.01). I tried different twrp recoverys from needrom and i can flash them to the device, but if i try to boot into recovery i only get the robot with the red warning triangle. Rest of the phone works fine, but i'd like to get a working custom recovery.
Can anyone help me?
So i rooted my phone with kingroot and i wanted to install a custom recovery without breaking the device how should i move next ? My X5 is an old motherboard version android 5.1 V15-2015.11.02 and that was the last official fota update for me. Is there any ofgicial upgrade suitable for my model like android 6.0 ? Two more things. My battery goes down rapidly and i dont know if its battery or chargers problem what should i do ?
http://www.needrom.com/category/doogee/serial-x-doogee/x5-doogee/
even without rooted phone you can flash a lot of roms from above link and read how to
Yeah i noticed this site man but says you need to register first. And one more thing spft always detects scatter files as invalid or maybe not legal even from the official site of doogee. I use the spft from doogeemobile site.
I am using SP_Flash_Tool_exe_Linux_v5.1520.00.100 with ubuntu(linux) maybe try an other flashtool edition,registering needrom is simple just making username and make a password when you are registered take the inifix hot 2.6.0 for the x5 flash it and you have got also a TWRP from wich you can root or install also the .zip roms etc.
I mentioned the inifix hot2.6.0 because that was the one i had succes even with a bricked recovery caused by flashing a cwm recovery without rooting first.
Well i just want for sure make a backup of my current rom without wiping it. I guess the infinit will delete all. Plus i also want to install recovery having rooted it 1st which is easy i think on 5.1. I have the one with the old motherboard not the -b. To sum up i want to install the official updated rom V20 via sd (which i tried and didnt work) luckily it didnt brick or via spft which doesnt load scatter file says is not valid no matter if i use latest or older version of spft in order to flash it manually. Its risky to root and install a recovery by an apk without having my rom backed up 1st. And even with the spft i cant do that. I just want to fix my battery status. Thats all. I use xp pro os.
indeed it is hard to install android 5.1 roms on the doogee x5with a twrp,al the 5.1 roms i could flash,but then i bricked the recovery,wich made no differend for the installed 5.1 roms,they just work.i can only install a working twrp by flashing Infinix Hot 2 6.0,wich is a 6.0 rom,but as far as i know you cant install a 5.1 rom with a 6.0 twrp... error 7.
Thats why we will end this discussion for now and wait for future solutions. Thx for your concern man. I just dont want to brick it since it runs smoothly with 5.1. As i said before i wanted to install the latest (official stock) V20 rom recently released. But i cant do it even from the tutorial that exists on their forum. It's a use of spft but i cant manage to do it. Scatter file always invalid.V20 Rom fixes some bugs and displays your interface like on 6.0 android version. We talk mate.
Hello !
Any news on the matter ?
I have got an X5 with Android 6 (!) on it. Have tried to root it with several one-click tools but this does not work.
Any suggestions?
Hi! What room do you recommend The most stable, And best, Under flashtool To Doogee X5? Thanks in advance for help!
hello i need help on my doogee x5 all 6.0 custom rom flash give me error 11 on twrp how to fix please ,
Any help please?
I have error 7 on all rom
Help?
Having tried to install TWRP it is rejected
Having downloaded twrp_x5max.img from needrom and used the adp method of installing the TWRP.img (https://www.xda-developers.com/how-to-install-twrp/). I get the following error message. "writing 'recovery'...
FAILED (remote: download for partition 'recovery' is not allowed".
So How do I get the TWRP img loaded into the Doogee X5Max (not pro) android with marshmallow?
I have tried using SP FlashTool and it says installed successfully, but I still get the default recovery program, after the dead robot with triangle and a exclamation mark inside, when booting into recovery using keys or adb command.
Is there another way of getting this image file loaded into the recovery partition?
I have followed all the set up steps in developers mode, so why cannot I use adb?
Hi,
I experienced black rear camera bug on Official LOS16 (I have to admit that i had made backup and tested carbon and LOS17) Now i installed 17 to test if is it ROM problem but i think it is unfortunatelly hardware problem. I saw other threads and searched internet and decided to install stock branded marshmallow, lock bootloader (Yes, I had backup TA before UB) and send it to official Sony service because I should still have warranty.
But...
I don't know how to install stock ROM. I downloaded branded software from XperiFirm and stopped there. How to flash it and not brick device? Newflasher is for newer models. Flashtool needs .ftf file. I searched how to convert XperiFirm package to .ftf on other model but there is step where you have to decrypt some files (I couldn't find them in downloaded software package).
I thought about second option - format and wipe in twrp all internal partitions and use Xperia Companion Software Repair. Actually I don't know does it work properly with UB devices...
I decided to go to the unofficial Sony devices service if it'd be problem with sending it to official Sony service.
What do you suggest? Is it easy and cheap enough repair for unofficial service not to damage device? I have no tools in home neither any preferences or experiences to do that by myself. Should I skip installing stock and go straight to the unofficial service?
If you suggest relocking device please help me and write step by step, noob friendly instruction how to flash XperiFirm package by flashtool or post made that way tutorial.
If you can help me, thank you!
If you use Xperifirm within Flashtools, it should download and automatically repackage it to an FTF file.
Or https://forum.xda-developers.com/z3-compact/general/ref-roms-guides-tutorials-faqs-t3035066
temporary2010 said:
If you use Xperifirm within Flashtools, it should download and automatically repackage it to an FTF file.
Or https://forum.xda-developers.com/z3-compact/general/ref-roms-guides-tutorials-faqs-t3035066
Click to expand...
Click to collapse
Thank you so much! I think it'll help me solve the problem :good:
After long brake I decided to flash stock, after I got problems with lineage.
Flashtool downloaded and prepared necessary files and flashed successfully firmware. (as you said it should :good: )
Next when I reboot, got bootloop.
Tried Xperia companion, it said that my phone is unlocked and it won't proceed
So tired flash twrp from NeoArians lineageos17 thread using fastboot flash recovery
Nothing and reboot to stock with bootloop
Tried to boot in twrp using command fastboot boot
Black screen and force shutdown
Tried to flash another firmware branded for my country
Again bootloop
Maybe there is another ftf which I should flash, not that one from xperifirm?
Hmh I'm run out of ideas, please help me.
Summary What I have:
-Xperia Z3 Compact with not working camera and flashed stock firmware.
-Bootloop
-ta partition backup
-working flashtool, xperifirm and Xperia companion
-Adb and fastboot
If you know what I did wrong, please tell me. I'd be very grateful if someone help me
BigBrother84 said:
After long brake I decided to flash stock, after I got problems with lineage.
Flashtool downloaded and prepared necessary files and flashed successfully firmware. (as you said it should :good: )
Next when I reboot, got bootloop.
Tried Xperia companion, it said that my phone is unlocked and it won't proceed
So tired flash twrp from NeoArians lineageos17 thread using fastboot flash recovery
Nothing and reboot to stock with bootloop
Tried to boot in twrp using command fastboot boot
Black screen and force shutdown
Tried to flash another firmware branded for my country
Again bootloop
Maybe there is another ftf which I should flash, not that one from xperifirm?
Hmh I'm run out of ideas, please help me.
Summary What I have:
-Xperia Z3 Compact with not working camera and flashed stock firmware.
-Bootloop
-ta partition backup
-working flashtool, xperifirm and Xperia companion
-Adb and fastboot
If you know what I did wrong, please tell me. I'd be very grateful if someone help me
Click to expand...
Click to collapse
For every bootloop of sony device use Emma (flashtool from sony). It's cure for everything.
EDIT: it will of course delete everything from a device.
Yes! It helped for bootloop! Tank you, checked camera and now I know 100% it is hardware problem!
Thank you :highfive:
What should i do with this error : No flash script found. Flash script is mandatory. I tried many firmwares. I want to flash stock for bootloader lock. (It does lock it right?) I'm not getting safetynet check after i came back from lineageOS with emma flashtool which didnt lock bootloader. Thanks for any help
I know you posted this a while ago, but here is a flash script file that worked for me.
Google Drive
Put the file in C:\Users\[USERNAME]\.flashTool\devices\I31XX. This should allow a flash at least with FlashTool.
As far as I know, flashing with FlashTool, NewFlasher or even Emma doesn't lock the bootloader. You have to use a seperate command with ADB to lock it.
Let me know if it works.
i tried for dual version its working Thanks