Related
I have installed the correct drivers from C:\Flashtool\drivers.
I then connect the USB cable into my PC, hold the volume up button and connect my phone to it, but it just starts charging.
I have used the search function, but it was of no help.
Did you unlock the bootloader ? You cant get fastboot access without unlocking the bootloader
Hope it helps !
Cheers
Since you had a doubt, I thought Id just clarify, Fastboot isnt the only way to flash Kernels. We can also do it via Flashtool and CWM Only thing is, if the kernel we flash isnt Sony-signed (ie, its not released by Sony themselves and unmodified) only an unlocked bootloader device can run that kernel
Fast boot does work without an unlocked boot loader. (At the least, the phone does connect in Fast boot.)
Was the phone off when you attempted to connect it (in fast boot )?
Haters gonna hate
potatoes gonna potate.
Hello,
I have a Xperia U, and I found a nice ROM for it, MIUI. The problem is, that it needs to be in recovery mode. I tried all the ways to get there, but it keeps failing. I did it with ROM Manager, Quickboot and just via the buttons, but it keeps just booting normally. I know that my bootloader is not unlocked. Is it nessecary that it is unlocked, for it to go in recovery mode?
Gr. Leon
Loo
Lenn2226 said:
Hello,
I have a Xperia U, and I found a nice ROM for it, MIUI. The problem is, that it needs to be in recovery mode. I tried all the ways to get there, but it keeps failing. I did it with ROM Manager, Quickboot and just via the buttons, but it keeps just booting normally. I know that my bootloader is not unlocked. Is it nessecary that it is unlocked, for it to go in recovery mode?
Gr. Leon
Click to expand...
Click to collapse
Usually these roms require unlocked bootloader. But sometimes developers manage making these roms for lock bootloader also
I just found the thread for miui based on locked and unlocked bootloader.
Check it here http://forum.xda-developers.com/showthread.php?t=2190205
DaRk-L0rD said:
Loo
Usually these roms require unlocked bootloader. But sometimes developers manage making these roms for lock bootloader also
I just found the thread for miui based on locked and unlocked bootloader.
Check it here http://forum.xda-developers.com/showthread.php?t=2190205
Click to expand...
Click to collapse
Okay, but now I have another problem... If I want to unlock its bootloader, it needs to be in fastboot mode or something. It will only turn the left led blue. Then I should install drivers. The problem is, that it won't stay in fastboot mode long enough for me to install the drivers. Am I doing something wrong??
Pls help me.
Greets Leon
Lenn2226 said:
Okay, but now I have another problem... If I want to unlock its bootloader, it needs to be in fastboot mode or something. It will only turn the left led blue. Then I should install drivers. The problem is, that it won't stay in fastboot mode long enough for me to install the drivers. Am I doing something wrong??
Pls help me.
Greets Leon
Click to expand...
Click to collapse
No mate. you are not doing something wrong. You have to be really fast. You can try another method too. Right click on computer and click properties. Open device manager. Now connect your phone on fastboot and when you see your device on device manager screen do the magic and install drivers.
This is the tutorial on how exactly unblock bootloader. http://forum.xda-developers.com/showthread.php?t=1527159.
Remember that unblocked bootloader means void warranty!
hi guys.i have have the customer servise flash tool for m86(pro5).just for m86,not work on any other phones.
and i want to share it yo you.
now just forget the customer servise.
it can falsh roms even if you lost your recovery and fastboot when your bl is locked.just like the Downloading Mode in samsung.
tools download here (Credits go to @Naphtha)
TestPCTool 1.0.0.9.rar
MultiUpgrade 4.8.5.rar
SAMSUNG USB DRIVER
How to Flash the Rom (M86).pdf (if you need some help with this just reply i will answer your question if i have time.) although my english is poor
you may need flyme roms here
[url]http://www.flymeos.com/firmwarelist?modelId=10&type=1[/URL]
enjoy it
nothing has changed
error token signature
i have this programms but they don`t worked... (Token signing fail)
P.S. please help me to flash my phone (i have fastboot mode & root, system running normally)
skype - evgen2910
My PC does not recognize my device when connected via USB , is said to have been a malfunction , I installed the RR rom and can not recognize it.
Please help:crying::crying:
Are there any tools that work for us with locked bootloaders and no recovery?
locked boot and rooted Pro 5
hexxor93 said:
Are there any tools that work for us with locked bootloaders and no recovery?
Click to expand...
Click to collapse
i have same situation
without success always i get error token sign failed WHEN USE MultiUpgrade 4.8.5.
WHO HAVE REAL SOLUTION THIS HAPPEN AFTER UNLOCK PASSWORD WITH MRT Dongle.
The same, i've a Token sign failed.
EDIT : After research, this tool is the bull**** beacause we need to are into Meizu factory. Indeed, to get the right token you need another tool, but only Meizu have it.
Sorry Guys.
EDIT 2 : https://forum.xda-developers.com/meizu-pro-5/how-to/to-unlock-hardbricked-meizu-pro-5-t3566173 Possible Way
Hi Guys, any other solution ? It reports me the same token sigh failed.
- First time when I stucked in Guest Mode (firmware 5.1.6G i thing ) I was able to fix it by this guide from KYOTOX
https://forum.xda-developers.com/meizu-mx/general/guide-meizu-mx5-stuck-guest-mode-fix-t3397191
(after boot to the desktop phone was 5-6 seconds in Admin User than phone switched to the "GUEST MODE", no more recovery mode, locked bootloader, rooted ) it was possible to solve it by that guide
- now I stucked after upgrade to 6.9.7.5 with Android 7 again (propably because I am just beginner without any experiences with flashing etc )
- Problem is before desktop appears, new flyme or Android 7 is showing me stupid commercials on 7 sheets, so during the process of reading sheet , phone switches to the GUEST, so in generally no chance.
Sorry for my english
multimedia box said:
i have same situation
without success always i get error token sign failed WHEN USE MultiUpgrade 4.8.5.
WHO HAVE REAL SOLUTION THIS HAPPEN AFTER UNLOCK PASSWORD WITH MRT Dongle.
Click to expand...
Click to collapse
bl locked rooted and no recovery.i use the flash tool but no luck.tokens failed. i follow this steps.i have the phone in bootloader mode{locked,rooted}
c/adb write
1.fastboot devices
2.fastboot oem unlock
3.close and boot again in bootloader mode.now you have unlocked bootloader
4.download recovery TWRP_3.0_m86 and put it at c/adb and write fastboot flash recovery TWRP_3.0_m86.img
5.close phone and press volume + and close button to reboot recovery.
and thats it. the phone boots twrp recovery!!
mikee72 said:
bl locked rooted and no recovery.i use the flash tool but no luck.tokens failed. i follow this steps.i have the phone in bootloader mode{locked,rooted}
c/adb write
1.fastboot devices
2.fastboot oem unlock
3.close and boot again in bootloader mode.now you have unlocked bootloader
4.download recovery TWRP_3.0_m86 and put it at c/adb and write fastboot flash recovery TWRP_3.0_m86.img
5.close phone and press volume + and close button to reboot recovery.
and thats it. the phone boots twrp recovery!!
Click to expand...
Click to collapse
With what rom previously flashed u've been able to do this ?
1-step
in order to root these qilive devices you will need...
magisk manager apk v5.6.4
stock boot.img file
working ADB to unlock oem and flash
2-step
lets get to it
place the magisk.apk and the stock boot.img
in the internal memory of your phone (downloads)
if you like to keep stuff organized :good:
3-step
follow the vídeo tutorial and use magisk manager
to patch your stock boot.img it will output a new
boot.img that includes magisk Root (patched_boot.img)
https://www.youtube.com/watch?v=BF4_hnKgjFA
ps: major ty to hovatek team for this great tutorial
step-4 use Google drive or usb OTG to get the patched_
boot.img to your PC and place it in the ADB folder
once you have oem(bootloader) unlocked just
rename the patched_boot.img to boot.img
step-5
unlock oem, these qilive devices wont unlock
the bootloader even if you enable it in DEV options
enable USB debug in dev options
you will need to use ADB commands
command- adb devices
serial appears
command- adb reboot bootloader
phone reboots to fastboot mode
command- fastboot devices
serial appears
command- fastboot oem unlock
(MAJOR WARNING the fastboot
oem unlock will wipe/reset/factoryreset/delete your data)
after you give the command small letters will appear
on the phone screen(yes or no) hard to read dont be hasty plz
use VOLUME+ to select and VOLUME - to confirm
note: when my phone ended the unlock it whent back to
that black screen where you choose fastboot-recovery-restart
and was stuck there, side keys did nothing if this happens
just long press the power key for 10 sec it will shutdown
then press power again to turn on
first boot after unlock will take longer then normal dont freakout
after you unlock small letters will appear during boot up saying the device
is not safe unlocked ,you can later use ( fastboot oem lock )
step-6
flash the patched boot.img with ADB
command- adb devices
serial appears
command- adb reboot bootloader
phone reboots to fastboot mode
command- fastboot devices
serial appears
command- fastboot flash boot boot.img
finished/ok
command- fastboot reboot
and voila you should now have magisk
installed in the app drawer, open it!!
step-7 run the install one final time from the
magisk manager and install magisk V16 using
recomended option it will verify/patch the boot image
Do NOT select the AVB 2.0 BOX it will bootloop the phone
and your done, enjoy your qilive rooted phone.
from this point on you can use the fastboot
command- fastboot oem lock
to remove the letters in boot up about the
device not safe unlocked
WARNING oem lock
will WIPE/FACTORY RESET again (god damn it!!)
ps: i had to install twice in a row,major pain in the ....
Repeat step 7 after Wipe/Reset
here is the stock boot for 2 qilive models
you can get the stock firmware for any qilive
at this site www.doc-doapi.com/EM/qilive/smartph...te_3m-fdd-cs_mul_20170818-110645_songlixin_PC
and get the recovery or boot from the unpacked firmware file
ps:my phone is the Q8SIN4GP AND ITS WORKING FINE
A VERY SPECIAL TY to topjohnwu (magisk creator), this man is nothing
short of a God damn genius!! , and if you can donate to him.
hope this helps other qilive users to root:highfive:
quick note on the qilive models, they have two model names
the cliente name in my case Q8SIN4GP
and the factory name in my model its 882912
in order to download the right firmware for your model
you need the factory model witch is what appears in the qilive
site above, it will be in the back of the phone or the original
box on a sticker just bellow the bar code, full model exempl
:Q8SIN4GP/882912 my firmware serves several models,
these Q8 models all start with 88xxxx WARNING
dont try this using the wrong firmware/boot file or you will DAMAGE your phone
Help with BOOTLOOP problems, if you find your self stuck in a bootloop
the phone wont go past the qilive logo and just stays there, dont freak out
you will loose your data but there is a way out
just keep pressing power + Volume up until a black screen with 3 options appears
when it does let go, use Volume + to select option and Volume - to confirm
select Fastboot or alternative select recovery and then select reboot to bootloader
both option will place your phone in Fastboot mode, once in fastboot mode
connect your phone to PC and use ADB commands to fix/bootloop
command- fastboot devices
serial appears
command- fastboot oem unlock (skip this if you use phone unlocked)
a confirm action option appears on the phones screen
use Volume up to say YES / or Volume Down to say NO
Warning oem unlock will WIPE/Factory reset your phone
once it finishes the phone will be stuck on the
Recovery/fastboot/restart screen just long press the power key
until the phone shuts down
start the phone again using Power + Volume up when the black
screen with the 3 options come up, let go and use Volume up to
select Fastboot mode and confirm using Volume Down
Once in fastboot connect your phone to PC and use ADB commands
command- fastboot devices
serial apears
Here you will flash the magisk patched_boot.img
the same image you used to root your phone
command- fastboot flash boot boot.img
it will say finished-ok (or similar)
command- fastboot reboot
the boot up time will be longer than normal
but the phone should now complete the boot
and present the inicial setup screen, select language
enter your mail, the usual bla bla...
any way at this point just repeat step 7
to get root running again
sp flash tools v5.1716.
phonedriller said:
1-step
in order to root these qilive devices you will need...
magisk manager apk v5.6.4
stock boot.img file
working ADB to unlock oem and flash
2-step....
Click to expand...
Click to collapse
Hi phonedriller,
phew, I did it! (Q8S55IN4G2), thanks.
Next step: Have you found a compatible custom recovery? (especially for nandroid backups and for xposed installation)
Would be very thankful for your help!
thanks
xdatheresianum
xdacktheresianum said:
Hi phonedriller,
phew, I did it! (Q8S55IN4G2), thanks.
Next step: Have you found a compatible custom recovery? (especially for nandroid backups and for xposed installation)
Would be very thankful for your help!
thanks
xdatheresianum
Click to expand...
Click to collapse
Awsome work congrats, as for the recovery so far no luck so try not to go 2 crazy until a working recovery is up and working , install stericsons busy box this is always the first root app i install
If possible buy sterics busybox pro and titaniumbackup pro if you want to install apps to sd card apps2sd pro all of these can be tested in free
Version,again nice work congrats enjoy you rooted phone :highfive:
xdacktheresianum said:
Hi phonedriller,
phew, I did it! (Q8S55IN4G2), thanks.
Next step: Have you found a compatible custom recovery? (especially for nandroid backups and for xposed installation)
Would be very thankful for your help!
thanks
xdatheresianum
Click to expand...
Click to collapse
give a hungry man fish and you solve his problem for a day or two
teach him how to fish and you solve his problem for life
phonedriller said:
give a hungry man fish and you solve his problem for a day or two
teach him how to fish and you solve his problem for life
Click to expand...
Click to collapse
hi phonedriller,
...well, i must have been an unlucky fisherman
an app i installed ended up giving me a soft brick (bootloop between qilive icon opening screen - btw still with the "warning" of "device is unsafe etc", i.e. oem still open - and black screen, qilive opening screen etcetcetc)
have cleaned cache; went for factory reset; etc
BUT: am presently stuck when trying to go via ADB (which used to work perfectly before) that somehow the usb drivers don't want to get installed properly. as a consequence, desktop cannot see devices.
and i cannot, for the sake of me, remember how i had succeeded before installing usb drivers.
could you please help?
thx
cktheresianum
xdacktheresianum said:
hi phonedriller,
...well, i must have been an unlucky fisherman
an app i installed ended up giving me a soft brick (bootloop between qilive icon opening screen - btw still with the "warning" of "device is unsafe etc", i.e. oem still open - and black screen, qilive opening screen etcetcetc)
have cleaned cache; went for factory reset; etc
BUT: am presently stuck when trying to go via ADB (which used to work perfectly before) that somehow the usb drivers don't want to get installed properly. as a consequence, desktop cannot see devices.
and i cannot, for the sake of me, remember how i had succeeded before installing usb drivers.
could you please help?
thx
cktheresianum
Click to expand...
Click to collapse
PS: adb will not work if the phone is not booting to the OS
it will work if you manualy place the phone in fastboot AKA bootloader
MODE ,you see if it does not boot to OS then usb service is not working
use power + Volume up to enter the black menu
use the Volume up to select fastboot(bootloader) volume - to confirm
connect the phone to your PC
flash the boot.img, the same boot.img used to root (patched by magisk)
to see is adb is ok just run - fastboot devices
if a serial is presented then all other stuff should work
step 1 - reflash the boot img
step 2 - after the flash finishes - fastboot oem lock
message on the phone screen, confirm yes to lock
OEM
step 3- press power until it turns off
it should now complete the start up (boot)
if not working this method let me now
you can still flash the full factory firmware
using SP Flash Tool v5.17xx
phonedriller said:
PS: adb will not work if the phone is not booting to the OS
it will work if you manualy place the phone in fastboot AKA bootloader
MODE ,you see if it does not boot to OS then usb service is not working
use power + Volume up to enter the black menu
use the Volume up to select fastboot(bootloader) volume - to confirm
connect the phone to your PC
flash the boot.img, the same boot.img used to root (patched by magisk)
to see is adb is ok just run - fastboot devices
if a serial is presented then all other stuff should work
step 1 - reflash the boot img
step 2 - after the flash finishes - fastboot oem lock
message on the phone screen, confirm yes to lock
OEM
step 3- press power until it turns off
it should now complete the start up (boot)
if not working this method let me now
you can still flash the full factory firmware
using SP Flash Tool v5.17xx
Click to expand...
Click to collapse
dearphonedriller,
thank you so much for your speedy help.
followed the steps given by you. all is well, as you predicted, until step 3.
however:
phone (now without the "orange state" message, i.e. oem locked) still bootloops and short of ADB "fastboot devices" the desktop doesn't see the phone (and driver installation continues to fail), as per your PS (thanks!) i guess flashing the full factory firmware ("RC-mt6737...zip" quoted by you in your very first post) is next.
would you please point me to a basic-for-noobs tutorial or instruct me on the step-by-step commands/procedures using this zip file?!
HUGE thanks
ckth
xdacktheresianum said:
dearphonedriller,
thank you so much for your speedy help.
followed the steps given by you. all is well, as you predicted, until step 3.
however:
phone (now without the "orange state" message, i.e. oem locked) still bootloops and short of ADB "fastboot devices" the desktop doesn't see the phone (and driver installation continues to fail), as per your PS (thanks!) i guess flashing the full factory firmware ("RC-mt6737...zip" quoted by you in your very first post) is next.
would you please point me to a basic-for-noobs tutorial or instruct me on the step-by-step commands/procedures using this zip file?!
HUGE thanks
ckth
Click to expand...
Click to collapse
https://www.youtube.com/watch?v=-zaEmj3-prU
turn the phone off, follow the video
flashing the full firmware is actualy easy
https://forum.hovatek.com/thread-13970.html
or searh sp flash tool here on xda
https://www.youtube.com/watch?v=LzyYXAflmOk&t=125s
phonedriller said:
https://www.youtube.com/watch?v=-zaEmj3-prU
turn the phone off, follow the video
flashing the full firmware is actualy easy
https://forum.hovatek.com/thread-13970.html
or searh sp flash tool here on xda
https://www.youtube.com/watch?v=LzyYXAflmOk&t=125s
Click to expand...
Click to collapse
thank you, phonedriller
everything worked perfectly via SPFlash Tool.
and, referring back to our above questions re the possibility of getting TWRP onto the phones, a developer friend of mine writes me this:
>try to flash TWRP:
>Download following files from this link:
>https://mega.nz/#F!qZIgnJRK!5apBfYo1je0ytg-wmA6JMQ
>- Odin3 v3.12.3 (Complete folder)
>- twrp-3.2.1-0-Q8S55IN4G2-20180318.tar
>1. Start your Phone into download mode
>2. Start Odin (Odin3 v3.12.3\Odin3.exe)
>3. Click on Options and unmark Auto Reboot
>4. Click AP and select twrp-3.2.1-0-Q8S55IN4G2-20180318.tar
>5. Press Start and wait until finished (Reset or OK!)
>6. Restart your phone immediatly to recovery mode
>7. In TWRP Recovery click on mount
>8. Set the checkbox checked at system (that system is mounted)
>9. go back and click on advanced
>10. Open file manager
>11. navigate to system/build.prop and click on build.prop
>12. Click on chmod
>13. type: 0644 and hit the accept button on screen or at the virtual
>keyboard on your phone
>14. restart your phone
i haven't tried this, but am wondering whether it might seem "reasonably possible" when reading through it.
thanks
ckth
Do you perhaps have link to Q8S5IN4GP stock rorm? Mine came with malware installed on it. I want to see if those were chinese who preinstalled or or was it decided by Auchan.
tommo1982 said:
Do you perhaps have link to Q8S5IN4GP stock rorm? Mine came with malware installed on it. I want to see if those were chinese who preinstalled or or was it decided by Auchan.
Click to expand...
Click to collapse
On my phone it came from factory and on the firmware file on 2 models , however only kasperky complains about malware on an system app called Helper bla bla bla i think its a false positive(i think) as no other antivirus or playstore ever found anything,but hey better investigate and be safe then sry right :good: maybe a ported cyanogen rom, ive look at a few rom port tutorials but my knowhow is limited + dont even have a working twrp yet, avg/avast/malwarebytes and a few others ,only kaspersky detects malware.
phonedriller said:
On my phone it came from factory and on the firmware file on 2 models , however only kasperky complains about malware on an system app called Helper bla bla bla i think its a false positive(i think) as no other antivirus or playstore ever found anything,but hey better investigate and be safe then sry right :good: maybe a ported cyanogen rom, ive look at a few rom port tutorials but my knowhow is limited + dont even have a working twrp yet, avg/avast/malwarebytes and a few others ,only kaspersky detects malware.
Click to expand...
Click to collapse
I had issues with adds being displayed at home screen and I was not able to close them. I had to use NetGuard to find that FOTA talks to 'adsup' and it is a known malware provider. I learned that some of the system apps try to talk with Alibaba servers and AdOppo (whatever it's called). Kaspersky might not be wrong, actually.
I'm trying to download stock firmware, but I don't know the file name. The website with it is locked, so unless I know exactly what I need, I cannot download it.
phonedriller said:
On my phone it came from factory and on the firmware file on 2 models , however only kasperky complains about malware on an system app called Helper bla bla bla i think its a false positive(i think) as no other antivirus or playstore ever found anything,but hey better investigate and be safe then sry right :good: maybe a ported cyanogen rom, ive look at a few rom port tutorials but my knowhow is limited + dont even have a working twrp yet, avg/avast/malwarebytes and a few others ,only kaspersky detects malware.
Click to expand...
Click to collapse
Yes i noticed the site now asks for a login that i dont have,but it was open to all until recently i have the firmware file in my pc,a few days ago i went to check for firware updates and the site was diferent and closed , in the site the download link was 882912/****** this firmware services at least 3 similar models
phonedriller said:
Yes i noticed the site now asks for a login that i dont have,but it was open to all until recently i have the firmware file in my pc,a few days ago i went to check for firware updates and the site was diferent and closed , in the site the download link was 882912/****** this firmware services at least 3 similar models
Click to expand...
Click to collapse
I guess the best thing would be a lineage or cyanogen ported rom(clean),ps i flashed the phone 2 times because of popups/adds and battery drain,however im aware that having root and installing tones of crasy stuff can fu.. Up any phone cheap or flagship,thus the firmware flashes,i discovered that having malwarebytes(premium)free for 30days keeps the phone clean and working fine,it seems that one is forced to buy from a main stream brand or risk this kind of thing,little to no support,no updates at all,bad security,the problem is certain apps if removed resoult in boot loop like this Helper app
phonedriller said:
I guess the best thing would be a lineage or cyanogen ported rom(clean),ps i flashed the phone 2 times because of popups/adds and battery drain,however im aware that having root and installing tones of crasy stuff can fu.. Up any phone cheap or flagship,thus the firmware flashes,i discovered that having malwarebytes(premium)free for 30days keeps the phone clean and working fine,it seems that one is forced to buy from a main stream brand or risk this kind of thing,little to no support,no updates at all,bad security,the problem is certain apps if removed resoult in boot loop like this Helper app
Click to expand...
Click to collapse
Ps use root + apps2sd or titaniumbackup to stop/disable the bad apps and replace them with playS app,not possible on all apps of course
phonedriller said:
I guess the best thing would be a lineage or cyanogen ported rom(clean),ps i flashed the phone 2 times because of popups/adds and battery drain,however im aware that having root and installing tones of crasy stuff can fu.. Up any phone cheap or flagship,thus the firmware flashes,i discovered that having malwarebytes(premium)free for 30days keeps the phone clean and working fine,it seems that one is forced to buy from a main stream brand or risk this kind of thing,little to no support,no updates at all,bad security,the problem is certain apps if removed resoult in boot loop like this Helper app
Click to expand...
Click to collapse
I'm thinking about Android 8.1 with it's Treble project. I might not be knowledgable enought to compile and flash it, though.
tommo1982 said:
I'm thinking about Android 8.1 with it's Treble project. I might not be knowledgable enought to compile and flash it, though.
Click to expand...
Click to collapse
Flashing is super easy use spflashtools or. Odin compiling a Rom is not , were you able to get the original firmware? You will need the original firware to get the boot and partition info from what i read so far
Unfortunately not. I will ask at the shop where I bought it how to contact tech. It should be freely available. I don't understand why Qilive restricted access to firmware.
I'll post when I learn anything.
Well, you can download the firmware if you know the file name. The bad news is, it seems the stock firmware has malware preinstalled. If there is anyone who could help confirm it. I have the ROM, and I can upload it to Google Drive if needed.
Hi all,
I'm coming back to a question lingering since the very first post here and mentioned again in post #9:
Is there a successful way to install TWRP on this Qilive model?
Re this topic:
- has anybody tried/has anybody been successful with the procedure described in post #9?
and
- has anybody seen the following TWRP builders' version (do an in-page search on Q8S55IN4G2)
https://twrpbuilder.github.io/fr/downloads/twrp/
with the download belonging to it
https://androidfilehost.com/?fid=890129502657591798
???
any successful installations to report???
Wouldn't THAT be great!!??
thanks
xdack
Xperia 1 goes on boot loop after flashing the ROM.
What happened.
>Flashed Xperia 1 using new flasher.
>Device started and while setup went on boot loop with a message"Your device is corrupt. It can't be trusted and will not boot. Your device will be powered off in 5 seconds."
I tried to repair using Xperia Companion but it won't stay to the Flashmode. It goes on loop with the message.
Used original cable and things.
But the device goes to fastboot mode if I press volume up during plugging.
Flashtool and new flasher cannot since the device won't go to flashmode while volume down and plugging.
What can I do further? Please help.
Does the phone turn on again after it automatically turns off?
What region did you flash btw?
It turns on and off automatically in two of the cases.
1. Connected to the PC.
2. Connected to the charger.
But stays in Fastboot mode connected to PC.
I was getting bootlops after flashing rom (locked bootloader, wanted to change region), using both newflasher and flashtool. In my case the problem was i had to wipe/format reset when flashing with flashtool, otherwise got a bootloop.
Once phone is booting, force a shutdown with volume + and power at the same time, then hold volume - and connect to pc, then use flashtool.
snake218 said:
I was getting bootlops after flashing rom (locked bootloader, wanted to change region), using both newflasher and flashtool. In my case the problem was i had to wipe/format reset when flashing with flashtool, otherwise got a bootloop.
Once phone is booting, force a shutdown with volume + and power at the same time, then hold volume - and connect to pc, then use flashtool.
Click to expand...
Click to collapse
Yes, I tried that way but the problem is it won't stay in Flashmode. It shows that warning and goes to bootloop.
I still can see the light turns green while doing so but cannot hold.
Same with me, recover using pc companion and use good cable..
The problem i have because using bad cable
blegs said:
Same with me, recover using pc companion and use good cable..
The problem i have because using bad cable
Click to expand...
Click to collapse
Thanks!
My phone doesn't stay in flashmode.
It only stay without loop and message in Fastboot mode.
Else would have flashed already!!
Yes my phone always said my phone not trusted..
I tried using newflashe always failed.
But after chae the cable and recovery from pc companion now its work
I agree, it might be PC problem (drivers) or cable definitelly. Try diferent cable and diferent pc, go to someone with PC and try with his cable
munjeni said:
I agree, it might be PC problem (drivers) or cable definitelly. Try diferent cable and diferent pc, go to someone with PC and try with his cable
Click to expand...
Click to collapse
Thank you but the thing doesn't work.
I tried on Windows 7 PC ;
Installed Xperia Companion and Xperia one driver and yet again it booted into fastbootmode but not flashmode.
I used USB C-C cable, and then another sony phone cable but it didn't work.
I even tried a short cable of a battery bank.
Thats strange. Can you write in details what you have flashed and what you have skipped? Did you done something with your trim area?
Hi @munjeni
I unluckily flashed new device J8110. It was a new firmware for device named Sphinx or something similar which isn't released yet.
It was to be j9110 actually. I then flashed the firmware through new flasher. I flashed everything. Then device booted and during setup steps it rebooted. Then I knew the device was different.
I tried flashing J 9110 but then the device started showing the mesaage.
Why don't you reflash trought fastboot? Boot an recovery image with fastboot:
fastboot boot recovery.img
you will need to unlock bootloader to be able to do that. Trought recovery and adb to recovery you can do many things e.g. flash an custom rom... etc, just for idea.
I have thought of it but loosing drm keys was reason.
jeoleo7 said:
I have thought of it but loosing drm keys was reason.
Click to expand...
Click to collapse
Doesn't matter anyway as you need access to the phone to toggle OEM unlock before unlocking bootloader
So..
What should I be doing?
jeoleo7 said:
I have thought of it but loosing drm keys was reason.
Click to expand...
Click to collapse
But do you have choice? Did you tried?
fastboot erase userdata
Usedata sometimes cause boot loop and message on screen about corruption. Another thing which I curently thinking about, is your battery charged? Maybe empty battery don't allow you to get into flash mode.
munjeni said:
But do you have choice? Did you tried?
fastboot erase userdata
Usedata sometimes cause boot loop and message on screen about corruption. Another thing which I curently thinking about, is your battery charged? Maybe empty battery don't allow you to get into flash mode.
Click to expand...
Click to collapse
I'm not sure. It was more than 50% when I did everything.
Not sure now.
Will it charge in fastboot mode?
I don't own device to be able to tell you. Seems you are not only one who have problem with flashmode, here https://forum.xda-developers.com/z3/xperia-z3v-general/bricked-sony-z3v-access-fastboot-t3510214 . Did you tried to erase userdata trought fastboot? I'm believing you will need to unlock bootloader first because you have no choice with locked bootloader because everything you try going to give you "command not allowed". Unlock bootloader, install an recovery, trought recovery you can reflash broken things, e.g. reguest from somebody with same device to give you raw partitions dump (excluding trim area, system, data, cache) and use DD command to reflash it on your phone, remember do not touch trim area, its on first partition! Good luck!
munjeni said:
I don't own device to be able to tell you. Seems you are not only one who have problem with flashmode, here https://forum.xda-developers.com/z3/xperia-z3v-general/bricked-sony-z3v-access-fastboot-t3510214 . Did you tried to erase userdata trought fastboot? I'm believing you will need to unlock bootloader first because you have no choice with locked bootloader because everything you try going to give you "command not allowed". Unlock bootloader, install an recovery, trought recovery you can reflash broken things, e.g. reguest from somebody with same device to give you raw partitions dump (excluding trim area, system, data, cache) and use DD command to reflash it on your phone, remember do not touch trim area, its on first partition! Good luck!
Click to expand...
Click to collapse
That link is 3 years old....
Without access to the phone there will be no access to the OEM unlock. Without that I don't think the bootloader can be unlocked.
It's hard to properly brick a sony phone with flashmode. With previous ones a different PC with different cables etc has worked