Hi guys,
Noob here.
Unlocked the bootloader on my XS and used fastboot to upload "central europe" routed version 6.0.A.3.73.
Everything worked fine doing this.
Followed blagus' / doomlord's tutorial to relock bootloader - (writes unlock-bit false). Used doomlord's ftf with his .sin crafted for XS.
Flashtool installed okay with flash and XS drivers. Sometimes flashing fails but if I run the flashtool first and connect my XS with the vol down button pressed, its LED lights up green and flashool logs "device connected in flash mode."
Go straight to flash button and point tool at the firmswares dir where I put DL's relock FTF. Just click the "OK" button and don't select "ignore TA" or "skip verify". Progress bar runs to 100% and flashtool log shows it has written a string of bytes successfully (no red-ink reported errors) - says phone will reboot. Nothing much happens on phone but flashtool reports "device connected in flash mode" again afterwards as if it did go offline momentarily and come back.
Using online SEUS via sonymobile.com/global_en or /gb (UK) shows ICS available for my phone. Downloads to phone successfully and says installation will carry on on the phone. Phone reboots to cardboard box logo and progress bar with 4 dots. First dot lights up and progress bar runs to 100%. Second dot lights up but progress bar fails to move. Screen blanks and phone boots to old rooted central-european firmware, eventually reporing "could not install updated."
The behaviour of the phone on official SEUS update has changed significantly. Before DL's relock was applied, update would fail without screen showing the 4 dots or a progress bar on reboot - just a brief picture of the "cardboard box" and it would switch to booting the old firmware. Now i appears to be installing at least some percentage of the update before failing. Leads me to believe DL's relock has been applied successfully even if it hasn't solved everything.
Sony on-air service suffers roughly the same progblem. It tries to push 6.0.A.73 to the phone, i.e. a pre-ICS update. Odd it's the same version as the rooted firmware I installed but there you go. I download it and select install. Phone reboots and picture of box with four dots appears. First dot runs to 100% on progress bar. Second dot illuminates but the progress bar doesn't move. After a few seconds, phone boots to old rooted firmware. Have tried to download update again and again via update centre on phone but each time the installation fails. Behaviour is very different to before I installed DL's relock though - same as above - it wouldn't even show the four dots or a progress bar on the boot screen with the cardboard box - just switch straight back to booting old firmware.
Have tried flashing DL's relock a few times. It doesn't always succeed but I always leave it after I've seen flashtool report a successful write. No change to above though.
Questions?
Why does SEUS / on air update fail part way through installation if they both seem to start correctly?
Is it because I'm trying to update from rooted firmware?
Is it because I have a central european image loaded and I'm trying to update in the UK?
Possible solution? Anyone?
All help very greatly appreciated. :crying:
Just wondered - could it be something I'm running on the rooted firmware that is stopping the update, like SetCPU with elevated superuser status? I assume the whole OS is suspended during update...
Also - I have 1.7GB free phone memory and 12GB free "memory card" memory. I assume these two stats aren't limiting factors?
Related
i recently flashed a new firmware on my sony xperia z2.
everthing went good.
i started up my phone and as i wanted to type in my sim code there was the error Unfortunately,android.process.acore has stopped for a millisecond and then my phone rebooted again and again and again.
pls i wanted also flash another firmware but the same thing happened.
Please Help.
Did a forum search and tried every solution I could but this is where I am at......D6503
Same problem as OP
Had working MM (niaboc79's found @ http://forum.xda-developers.com/xperia-z2/development/rom-official-6-0-1-23-5-0-486-beta-t3336770) but for some reason without the included recovery.
Decided I would install [NUT]'s Z2-lockeddualrecovery2.8.26-RELEASE.combined in preperation for future flashes.
This lead to a Bootloop.
Then I flashed D6503_Customized ES_1281-4644_23.4.A.1.264_R8C.ftf via Flashtool.
This helped me passed the initial Bootloop, all looked good, got the usual "program optimizing" load up.
System booted, albeit in Spanish, to language screen.
After that I got a few errors such as "unfortunately media...gmail...stopped" which allow me to press "OK"
then the "unfortunately,android.process.acore has stopped" message which is where the system freezes and reboots.
If I leave it alone and don't touch it, it just boots for 5/10 seconds before freezing and rebooting.
I tried flashing a different ftf however since flashing D6503_Customized ES_1281-4644_23.4.A.1.264_R8C.ftf all my settings have been reset, so USB Debugging etc is no longer checked which means it will not allow flashing.
I have access via Fastboot and Flashmode but I am unsure what I can do with these to restore a working system.
While phone is booting Flashtool reads my device correctly (model, firmware) and informs me I do not have root access, Busybox any longer.
It does give me the option at this stage, via now accessible tabs in Flashtool, to "root," "ask root permissions," and "install apk" but nothing I do works.
One one occasion, not sure what I did as I seem unable to repeat it, but it said I did infact HAVE root access. At that point I should have clicked on Flashtools "install recovery" or "root" tab but unfortunately didn't.
What are my options here? Is there a solution I can perform myself at this stage?
Thanks in advance
UPDATE:
Tried again for the 600th time, this time took my memory card out and it seems to have flashed the "...264" rom.
Select all wipes when flashing a new firmware.
Hello a few days i restored my galaxy to factory settings from inside the own phone settings everything was working fine until a couple days ago the phone started to rebooting every now and then
Right now is stuck on the samsung logo after you turn it on and in the recovery menu i got this error
E: failed to mount /efs (invalid argument)
I try to wipe the cache date and even doing a wipe from the recovery menu but nothing when the phone turn on and gets to the samsung logo it stays there a while and reboots again
I try doing this instructions from this post from another forum
The key for me was selecting the second item in the Tools menu (Firmware Upgrade and Initialisation?) - it seemed to bypass that whole 'connecting' process and just went to work. Here's the writeup that I put together (I need to insert the Kies screenshots that I captured).
- if you don't already have the Kies software installed on your PC, download it (just search Google) and install it. The first time it runs it'll update itself to the latest version so make sure you run it once before proceeding.
- put your phone in Download mode: with the phone completely off, press and hold the Volume Down and Home and Power buttons simultaneously, and release them all when you see the Samsung splash screen
- connect the phone to your PC with the USB cable that came with the phone
-- if you've never had the phone connected to your Windows-based computer before, you'll see messages about installing drivers, etc - just wait until this is done (may take 5 or 10 minutes) [I don't know what happens if you have a Mac - it probably just works]
- in the Kies software, select the second item in the Tools menu and just follow the prompts to enter the model number (in CAPS) and IMEI/Serial Number (both found under the battery - it's ok to remove the battery at this point)
- the Kies software should start downloading the correct firmware for your phone from the Internet; once that's done (depending on your Internet connection speed) it'll begin downloading that to the phone (this probably takes 10 minutes or so)
Click to expand...
Click to collapse
I manage to do all the steps but nothing now the phone turns on and it gets stuck on the samsung logo but this time it doesn't reboot it just stays there and in the recovery menu still have the same error
Does anyone have any solucion or a guide that explaings well how can i fix this?
I have seen other guides that saids i need to either root the phone and install a custom recovery menu but since the phone doesn't boot i have no clue how to do this
Edit: A few moments ago i tried doing this as well (i cant post the complete youtube link)
watch?v=xJMJLdzHaAY
The phone now turn on but i have a black box with some yellow letters i'm guessing is the called safe mode is there anything i can do from here?
Been honest i'm completely lost here
Can someone please give a valid link to download?
Edit: Sorry, wrong post.
You can try flashing a recovery (cwm official is best) via odin but most likely you'll need to flash a stock rom, definitely if the cwm flash doesn't solve it.
Beamed in by telepathy.
shivadow said:
You can try flashing a recovery (cwm official is best) via odin but most likely you'll need to flash a stock rom, definitely if the cwm flash doesn't solve it.
Beamed in by telepathy.
Click to expand...
Click to collapse
is there any tutorial on how to that for the I9300? because i to be honest without a tutorial i dont have a clue on how to start doing this, i will actually prefer a stock rom is by stock rom is a official firmware from samsung
Hi,
Anyone could help me with a weird behavior of Xperia Z Ultra of my sister?
THE PROBLEM:
- Trying to power it on, it boots up and stuck on "Sony Xperia" logo with no notification led sinalization.
- Once stucked on "Sony Xperia" logo, there is no response from pushing any combination of buttons ("POWER"; or "VOLUME_UP" + "POWER"; or "VOLUME_DOWN" + "POWER"). It is only possible to power it off pushing (and waiting for 3 vibrations) the red button besides the microSD card slot.
- Once powered it off, recharge is possible pluging it to the wall charger, the red led keeps solid until around 90% and then the notification led turns solid green and keeps charging until 100%. (It is possible to see the battery charge icon briefly pushing the "POWER" button).
My sister says that she has never did a system update, so it may have the stock firmware and locked boot loader; and this problem occurred few weeks after the end of the warranty during normal operation at low battery charge... when suddenly self powered off by battery discharge; after that, she plugged it at wall charger and tried to power it on, but everytime it keeps stucked on "Sony Xperia" logo since then.
MODEL IDENTIFICATION
On a stick at its box says:
Model: C6843 / Xperia Z Ultra
SI 1276-0910.12 PB
FIX TRY 1:
My first try to fix the problem was using the last version of Xperia Companion software in Windows 7 Ultimate SP1. I selected the option "Software Repair" and, following the instructions, connected the device to the USB holding the "VOLUME DOWN" button; the notification led fast blinked once red, and faster blinked once green and then turned off; Windows installed "SOMC Flash Device" driver. Aparently, the device was detected and showed the software version available to repair: 14.6.A.1.236-R3D and the repair process had gone to the end with no errors. But, after disconnected the device from USB and tried to power it on, its behavior keeped unchanged... keeped stucked on "Sony Xperia" logo.
I tried one more time with software repair of Xperia Companion, but this time I connected the device to the USB without holding any button, and for my surprise, it had gone to the end of repair process without errors! It seens like the device stucked in flash mode but without notification led sinalization!
FIX TRY 2:
I downloaded the last version (0.9.22.3) of Flashtool software of Androxyde and the last version of XperiFirm (v5.0.0).
I executed XperiFirm and browsed looking for my model/customization firmware and it showed that it has 3 firmwares for the model C6843, but curiously, there is no firmware available for my local customization SI (CDA) 1276-0910... So, I downloaded both CDA available for my country (Brazil): 1277-0849 and 1277-7513.
Using the Flashtool, I created the bundle and flashed the first (1277-0849) firmware version 14.6.A.1.236_R3D with no errors, but the problem keeped unchanged. I repeated the process with the second (1277-7513) firmware version 14.6.A.1.236_R5D, but with the same results.
Looking at the Flashtool's log, we can see that the device is detected as:
"...
Current device : C6843 - BY900EB69A - 1277-0849_R3D - 1276-7278_14.6.A.1.216 - DTV-LTE_14.6.A.1.216
..."
This is a bit confusing: witch is the CDA of my sister's device? The one on the stick at its box (1276-0910) or one of the log above (1277-0849 or 1276-7278)? I know that it is a DTV device (DTV = Digital TV).... but, anyway... none of the firmwares is fixing the problem.
I've already tried a downgrade: I downloaded a FTF from xda (C6843_14.4.A.0.108_BlueEther.ftf) and sucessfully flashed it, but also did not solve the problem. In this case, the logo at boot loader changes a little (it shows only "Sony", while in the last versions shows "Sony Xperia") proving that the boot loader is being written.
I've repeated all tries using the previous version of Flashtool (0.9.18.6), but with no different results.
As I observed when I using Xperia Companion, the same occurred with Flashtool in all tries: the device seems to be stucked in flash mode without notification led sinalization.
I've already searched xda and google for a solution, I've read lots of pages, I've tried several tips, but with no success.
Anyone have any idea of what I can do to fix the problem? :fingers-crossed:
Thank you.
Hi
I have a similar problem,
I was on AICP with the debugging mode on.
I try to flash my ZU with the the Stock ROM, I have download the files from the last version of XperiFirm of my country (France)
Here are de spec of the files :
Model: Sony Xperia Z Ultra (C6833)
Firmware version: 14.6.A.1.236_R4D
Region: Central Europe 1 (Generic) [1276-2235]
Android version: 5.1.1
Then i created my FTF file and start to flash it with flashtool
The first error appear, it was a problem with the loader.sin
Second try. I choose to flash it again and then a problem appear, it was about the system.sin this time !
The error said that i need to turn on my debbuging mode (the thing, it already was... And my phone won't start, it stay stuck on the logo screen so i can't activate it anymore)
Every try it's the same error.
And that's were I'm stuck.
I have thought about flash the boot.img system.im and else by fastboot, but I'm not sur of it..
Edit : I did it and it worked for me
First you need to be sure that your device is well charged and only then you can flash your device, you should be able to flash it. Do not forget to wipe your data when you are about to flash by choosing the right option
I'm not a n00b, I've rooted every Android device I've ever had, and I have my OnePlus Two running the latest CM14.1 nightlies. But I can not figure out what to do for this poor tablet.
I had downloaded and installed an OTA from Lenovo, but it must have been corrupt because the tablet got stuck in a boot loop. I can boot into recovery, so I tried formatting it and clearing all the caches, then it goes to a screen with a loading bar, which fills completely and just sits there. I've left the thing on all night. Nothing.
Sending it to Lenovo is a no-go because I voided the warranty when I rooted it.
I've also tried reinstalling the stock firmware, but the Intel phone flash tool either get's blocked by Windows 10 (with no way to whitelist it) or fails to flash properly.
crandroid99 said:
I'm not a n00b, I've rooted every Android device I've ever had, and I have my OnePlus Two running the latest CM14.1 nightlies. But I can not figure out what to do for this poor tablet.
I had downloaded and installed an OTA from Lenovo, but it must have been corrupt because the tablet got stuck in a boot loop. I can boot into recovery, so I tried formatting it and clearing all the caches, then it goes to a screen with a loading bar, which fills completely and just sits there. I've left the thing on all night. Nothing.
Sending it to Lenovo is a no-go because I voided the warranty when I rooted it.
I've also tried reinstalling the stock firmware, but the Intel phone flash tool either get's blocked by Windows 10 (with no way to whitelist it) or fails to flash properly.
Click to expand...
Click to collapse
What I've tried:
Just plain booting it - screen turns on and doesn't do anything, just black
Rebooting through recovery (power + vol_up) - plays boot animation, goes to a screen with a loading bar like it does after an update, but once the bar fills, a white line appears at the top of the screen and nothing happens
Downloading the official KitKat firmware (http://forum.xda-developers.com/android/help/lenovo-tab-s8-50f-stock-firmware-rom-t2989791), unarchiving the rar file and rearchiving it into a .zip, putting it on a MicroSD card, putting the card in the tablet, flashing through recovery - can't find the .zip, says SD card is blank
Clearing caches and wiping data - same as when rebooting through recovery
Using the Intel phone flash tool through bootloader (power + vol_down) - tool can't find device
Using the same tool through fastboot (power + vol_up + vol_down) - gets to the sleep 4000 ms step, reboots the device, then the device goes to the same loading screen and the flash tool can't contact it. I think it's trying to boot into the OS to finish the flash, but that's the problem to begin with
I've tried loading the temporary CWM session but that fails
I can't for the life of me figure out what the @bailka011 Unlock Tool is supposed to do or how to use it, plus the download link isn't working.
Can someone please guide my through this? I'm so confused
crandroid99 said:
What I've tried:
Just plain booting it - screen turns on and doesn't do anything, just black
Rebooting through recovery (power + vol_up) - plays boot animation, goes to a screen with a loading bar like it does after an update, but once the bar fills, a white line appears at the top of the screen and nothing happens
Downloading the official KitKat firmware (http://forum.xda-developers.com/android/help/lenovo-tab-s8-50f-stock-firmware-rom-t2989791), unarchiving the rar file and rearchiving it into a .zip, putting it on a MicroSD card, putting the card in the tablet, flashing through recovery - can't find the .zip, says SD card is blank
Clearing caches and wiping data - same as when rebooting through recovery
Using the Intel phone flash tool through bootloader (power + vol_down) - tool can't find device
Using the same tool through fastboot (power + vol_up + vol_down) - gets to the sleep 4000 ms step, reboots the device, then the device goes to the same loading screen and the flash tool can't contact it. I think it's trying to boot into the OS to finish the flash, but that's the problem to begin with
I've tried loading the temporary CWM session but that fails
I can't for the life of me figure out what the @bailka011 Unlock Tool is supposed to do or how to use it, plus the download link isn't working.
Can someone please guide my through this? I'm so confused
Click to expand...
Click to collapse
what did it says the update would do? android 6.0? latest update for this tablet was released 7 months ago... the unlock tool u mentioned unlocks the bootloader, and try to find a win7 pc to do the flashing. some users on a different forum stated that windows 10 will cause problems during flashing
good luck
xaocot said:
what did it says the update would do? android 6.0? latest update for this tablet was released 7 months ago... the unlock tool u mentioned unlocks the bootloader, and try to find a win7 pc to do the flashing. some users on a different forum stated that windows 10 will cause problems during flashing
good luck
Click to expand...
Click to collapse
This update was seven months ago. It did not claim to bring 6.0, just minor fixes.
Thank you for clearing that up, now I just have to figure out how to download and use it xD.
Also I have figured out how to enable the hidden administrator account in Win10 and use that to get around the security warning, still tries to boot partway through flashing. Unless there's some other part of Win10 that's disagreeing with it.
Sent from my ONE A2005 using Tapatalk
the same problem with me!
crandroid99 said:
What I've tried:
Just plain booting it - screen turns on and doesn't do anything, just black
Rebooting through recovery (power + vol_up) - plays boot animation, goes to a screen with a loading bar like it does after an update, but once the bar fills, a white line appears at the top of the screen and nothing happens
Downloading the official KitKat firmware (http://forum.xda-developers.com/android/help/lenovo-tab-s8-50f-stock-firmware-rom-t2989791), unarchiving the rar file and rearchiving it into a .zip, putting it on a MicroSD card, putting the card in the tablet, flashing through recovery - can't find the .zip, says SD card is blank
Clearing caches and wiping data - same as when rebooting through recovery
Using the Intel phone flash tool through bootloader (power + vol_down) - tool can't find device
Using the same tool through fastboot (power + vol_up + vol_down) - gets to the sleep 4000 ms step, reboots the device, then the device goes to the same loading screen and the flash tool can't contact it. I think it's trying to boot into the OS to finish the flash, but that's the problem to begin with
I've tried loading the temporary CWM session but that fails
I can't for the life of me figure out what the @bailka011 Unlock Tool is supposed to do or how to use it, plus the download link isn't working.
plz someone too guide me ,the same problem is happening but there is no appearance of a loading screen,when i switch on the tab ,it showws the lenova logo and goes to a black screen thats keeps on flahsing!! i dont knwo what to do ,when i connect to pc and try to flash it doesnt work,i dont what to do plz help me!!
Click to expand...
Click to collapse
So i followed the thread on how to root xperia xa ultra duel in here https://forum.xda-developers.com/xa-ultra/how-to/how-to-root-xperia-xa-ultra-dual-t3439173
but after rooting and doing all steps after booting the device and checking it's functionality I noticed that the front camera is not working and it crashes everytime
so i wanted to flash a new firmware but my flashtool kept saying "no flash script found" and aborted the flashing >>so i waited for a new boot and the creator "rrvuhpg"
made a new boot for the test in here https://forum.xda-developers.com/xa...12-f3216-stock-kernels-built-sources-t3527762
flashed it using adb and rooted the device one more time and booted the phone again now there are 2 problems while the camera problem is fixed
the screen won't turn off completely and after clicking the power button to turn it off it turns into a very dark screen "not noticeable in high light but in low light u can clearly see it's on"
and when i try to click the power button to turn it on again it does this weird TV like static and shows the normal screen afterwards
and the brightness level meter is always at the maximum and can't be changed so my phone battery dies very quick now
I need help because I can't flash anew firmware and i have to stick with "Battery Killer" setup i have right now so i need help with both flashtool and a fix for the boot or just a way to recover my stock firmware
i checked one more time and i found out that the twrp can't wipe cache partition and if i factory reset the phone it doesn't work and all data remain