Related
I have my trinity briked and want to bring it to service centre. But ROM version I tried to flash before briking was in different region which may breach the warranty.
Now it boots and stops with a start up logo in different language. I am worried that service centre may refuse my repair request. Can I erase the image file from ROM? or any suggestion to avoid showing this screen? It is possible to use mtty and erase the image file? where is the image files' address? or how to erase the main ROM so that it will not show the image?
I tried most of the recovery method from here http://forum.xda-developers.com/showthread.php?t=286755 but still failed. My case is "Hybrid Bricks: combinations of both type 1 and type 2 bricks"
Model: D810 (trinity)
ROM Before Flash: 1.??
Radio Before Flash: 1.07??
Bootloader Before Flash: 1.07.??
Flash failed at: It seems completed at 100% but cannot boot after finish all
Flashing ROM: 1.23
Flashing Radio: 1.13.00
Bootloader After Failure: 1.07.0000
tried unlock and using SSPL to flash
CID Before Failure Super CID: tried unlock but don't know if success
CID Corrupt: Yes, info 2 shows HTCSF ?? HTCE
Radio Corrupt: Yes
No GSM Error: Yes
Stuck In Bootloader: No
Stuck On Windows Mobile Splash: Yes
Can boot into OS: No
Tried mtty command set 14 0: Yes
Tried wiki problem number 5: Yes
mtty info 2 output: CID: HTCSF ?? HTCE
Current Device Status: hang at welcome screen when power on
Hi, I have several questions about flashing a ICS beta kernel on my arc s
I have android 2.3.4 ...42, rooted by superoneclickv2+busybox+cwm, Im trying to install this kernel http://forum.xda-developers.com/showthread.php?t=1514849
to use with this rom http://forum.xda-developers.com/showthread.php?t=1540072
But when I try to flash by fastboot I get this log
2/024/2012 01:24:13 - INFO - For 2011 devices line, be sure you are not in MTP mode
12/024/2012 01:24:19 - INFO - Device connected with USB debugging on
12/024/2012 01:24:19 - INFO - Connected device : LT18
12/024/2012 01:24:19 - INFO - Installed version of busybox : BusyBox v1.19.0 (2011-08-14 23:46:58 CDT) multi-call binary.
12/024/2012 01:24:19 - INFO - Android version : 2.3.4 / kernel version : 2.6.32.9-perf
12/024/2012 01:24:41 - INFO - Root Access Allowed
12/025/2012 01:25:24 - INFO - Launching Fastboot Toolbox 1.0 by DooMLoRD
12/025/2012 01:25:24 - INFO - Device Status: ADB mode
12/025/2012 01:25:27 - INFO - Please wait device is rebooting into fastboot mode (via ADB)
12/025/2012 01:25:28 - INFO - Device will soon enter fastboot mode
12/025/2012 01:25:29 - INFO - Device disconnected
12/025/2012 01:25:30 - INFO - Device connected in fastboot mode
12/025/2012 01:25:33 - INFO - Please wait device is rebooting into fastboot mode (via Fastboot)
12/025/2012 01:25:33 - INFO - Device will soon reboot back into fastboot mode
12/025/2012 01:25:34 - INFO - Device disconnected
12/025/2012 01:25:36 - INFO - Device connected in fastboot mode
12/025/2012 01:25:40 - INFO - Selected kernel (boot.img or kernel.sin): C:\Flashtool\firmwares\boot.img
12/025/2012 01:25:40 - INFO - Flashing selected kernel
12/025/2012 01:25:40 - INFO - FASTBOOT Output:
sending 'boot' (5850 KB)...
FAILED (remote: The Device must be rooted first)
finished. total time: 0.001s
Click to expand...
Click to collapse
What Im doing wrong?
I dont know if my bootloader is unlocked or not, if I press *#*#7378423#*#*
it says "Bootloader unlock allowed: Yes"
Im very confused about this because somewhere in this forum I read that if you root your phone then bootloader get unlock...
Please help me, flashing my brothers x10 was soo easy with .ftf files, but I really dont know how to flash .img kernels or if my bootloader still locked
Need a guide for noobs
or should I wait until sony releases ICS update?
Rooting doesnt unlock the bootloader.. Is ur bootloader unlocked? how did u do it? SE has given official instructions on how to unlock the bootloader..
http://unlockbootloader.sonymobile.com/
R u trying to flash this Kernel via the Flash tool software? I would suggest you to connect ur cell in the fastboot mode.
Switch it off and connect it to PC via USB by pressing the menu button (A blue LED will be seen)
U need to have working fastboot for that..
http://www.mediafire.com/?b2of5mpqi2bwczt
Extract this file and when u'll connect ur cell to PC as stated above, for the first time, it will ask for drivers... browse to the USB driver folder which is in the .rar file.
Once u r done with the unlocking bootloader, download the kernel img file and save it in the folder where fastboot.exe is.
Now open the command promt (if u r using windows 7, just press shift and do a right click, select open command prompt here from the menu) and go to the fastboot folder in the cmd. once u r on the path of fastboot. Enter following commands :
fastboot flash boot KernelFile.img (ur copied kernel file)
it will start flashing the kernel, once it is done, type following
fastboot reboot
Ur cell be restarted, when u'll c the kernel booting, keep pressing the volume button to go into the recovery mode..
I cant be held responsible if u damage ur device!!!
Hit thanks if I helped u..
same issue
so ive tried everything i can come across to figure out why it gives me the same error. my bootloader is unlocked and phone is rooted. but i still get the phone must be rooted message no matter what i do and its so irritating cuz i want to put miui on it but cant for the life of me flash anything except stock roms. fastboot not working for me at all. any help please
edit
even though store claimed it to be unlocked the bootloader was not phone just wasnt branded to any carrier so had to unlock the bootloader and everything is glorious now:}
iKevinShah said:
I have got the same stuff (but on my xperia neo)
same exact problem.
The is nothing with bootloader or root, i guess
what my experience is, when i open with cmd in windows and type fastboot devices, i get none but in flashtool it recognised the device in fastboot.
Do you also have the same status as this ?
Click to expand...
Click to collapse
Seriously bro.. you're doing something wrong.. once install all the drivers and execute this command..
Fastboot.exe -i 0x0fce getvar version
If u get 0.3 or something its all fine..
Don't forget to hit 'THANKS' if I helped..
Sent from my Xperia Pro using XDA
You need to unlock your bootloader....
unlockbootloader.sonymobile.com/instructions
I has the same problem, after unlock bootloader, its fine!
I solve it
Overdose1986 said:
Hi, I have several questions about flashing a ICS beta kernel on my arc s
I have android 2.3.4 ...42, rooted by superoneclickv2+busybox+cwm, Im trying to install this kernel http://forum.xda-developers.com/showthread.php?t=1514849
to use with this rom http://forum.xda-developers.com/showthread.php?t=1540072
But when I try to flash by fastboot I get this log
What Im doing wrong?
I dont know if my bootloader is unlocked or not, if I press *#*#7378423#*#*
it says "Bootloader unlock allowed: Yes"
Im very confused about this because somewhere in this forum I read that if you root your phone then bootloader get unlock...
Please help me, flashing my brothers x10 was soo easy with .ftf files, but I really dont know how to flash .img kernels or if my bootloader still locked
Need a guide for noobs
or should I wait until sony releases ICS update?
Click to expand...
Click to collapse
Hi,after "BootLoader" again,it's OK.I hope it's useful for U.
i have the same problem
it says that you device must be rooted
and i have my xperia ray rooted and unlocked bootloader
please help me to solve this problem:crying:
I cannot unlock the bootloader
I do have the same problem, my device is rooted as per doomlord method and I when I try to install a custum kernel I too get the error
failed remote the device must be rooted first.
Also I could not unlock the bootloader when I try the steps mentioned in sony website, I got the unlock code and it says " need a unlocked device" while I try to unlock the bootloader: fastboot -i 0x0fce oem unlock 0x<unlockcode>
mail_venu said:
I do have the same problem, my device is rooted as per doomlord method and I when I try to install a custum kernel I too get the error
failed remote the device must be rooted first.
Also I could not unlock the bootloader when I try the steps mentioned in sony website, I got the unlock code and it says " need a unlocked device" while I try to unlock the bootloader: fastboot -i 0x0fce oem unlock 0x<unlockcode>
Click to expand...
Click to collapse
Put the unlock code in the command, enter it, while having phone in fastboot mode, and bootloader should get unlocked. That is only if you do have SIM-unlocked phone, that is no SIM-lock.
--
same problem
Overdose1986 said:
Hi, I have several questions about flashing a ICS beta kernel on my arc s
I have android 2.3.4 ...42, rooted by superoneclickv2+busybox+cwm, Im trying to install this kernel http://forum.xda-developers.com/showthread.php?t=1514849
to use with this rom http://forum.xda-developers.com/showthread.php?t=1540072
But when I try to flash by fastboot I get this log
What Im doing wrong?
I dont know if my bootloader is unlocked or not, if I press *#*#7378423#*#*
it says "Bootloader unlock allowed: Yes"
Im very confused about this because somewhere in this forum I read that if you root your phone then bootloader get unlock...
Please help me, flashing my brothers x10 was soo easy with .ftf files, but I really dont know how to flash .img kernels or if my bootloader still locked
Need a guide for noobs
or should I wait until sony releases ICS update?
Click to expand...
Click to collapse
same problem, who to fix?
joaoandre23 said:
same problem, who to fix?
Click to expand...
Click to collapse
Download the lastest flashtool available, now allows you to flash .img kernels
joaoandre23 said:
same problem, who to fix?
Click to expand...
Click to collapse
Rooting does not unlock your bootloader. They are not even related to each other!
There is a big difference between "Bootloader unlock allowed: Yes" and "Bootloader unlocked: Yes". I think you understand the difference.
Unlock bootloader and then try to flash kernel again.
Someguyfromhell said:
Put the unlock code in the command, enter it, while having phone in fastboot mode, and bootloader should get unlocked. That is only if you do have SIM-unlocked phone, that is no SIM-lock.
Click to expand...
Click to collapse
That's right.
The whole process look like (with my phone:
Code:
E:\Download\Mobile\Xperia>fastboot devices
CB5121CFWR&ZLP fastboot
E:\Download\Mobile\Xperia>fastboot.exe -i 0x0fce getvar version
version: 0.5
finished. total time: 0.001s
E:\Download\Mobile\Xperia>fastboot flash boot boot.img
sending 'boot' (8617 KB)...
FAILED (remote: The Device must be rooted first)
finished. total time: 0.005s
E:\Download\Mobile\Xperia>fastboot.exe -i 0x0fce oem unlock 0xUNLOCK-KEY
...
(bootloader) Unlock phone requested
OKAY [ 0.500s]
finished. total time: 0.501s
E:\Download\Mobile\Xperia>fastboot flash boot boot.img
sending 'boot' (8617 KB)...
(bootloader) USB download speed was 20960kB/s
OKAY [ 0.438s]
writing 'boot'...
(bootloader) Flash of partition 'boot' requested
(bootloader) S1 partID 0x00000003, block 0x0000d000-0x00014fff
(bootloader) Erase operation complete, 0 bad blocks encountered
(bootloader) Flashing...
(bootloader) Flash operation complete
OKAY [ 0.482s]
finished. total time: 0.922s
E:\Download\Mobile\Xperia>
mandarjoshiin said:
Rooting doesnt unlock the bootloader.. Is ur bootloader unlocked? how did u do it? SE has given official instructions on how to unlock the bootloader..
http://unlockbootloader.sonymobile.com/
R u trying to flash this Kernel via the Flash tool software? I would suggest you to connect ur cell in the fastboot mode.
Switch it off and connect it to PC via USB by pressing the menu button (A blue LED will be seen)
U need to have working fastboot for that..
http://www.mediafire.com/?b2of5mpqi2bwczt
Extract this file and when u'll connect ur cell to PC as stated above, for the first time, it will ask for drivers... browse to the USB driver folder which is in the .rar file.
Once u r done with the unlocking bootloader, download the kernel img file and save it in the folder where fastboot.exe is.
Now open the command promt (if u r using windows 7, just press shift and do a right click, select open command prompt here from the menu) and go to the fastboot folder in the cmd. once u r on the path of fastboot. Enter following commands :
fastboot flash boot KernelFile.img (ur copied kernel file)
it will start flashing the kernel, once it is done, type following
fastboot reboot
Ur cell be restarted, when u'll c the kernel booting, keep pressing the volume button to go into the recovery mode..
I cant be held responsible if u damage ur device!!!
Hit thanks if I helped u..
Click to expand...
Click to collapse
can you re-upload the files you uploaded on mediafire please?
isko95 said:
can you re-upload the files you uploaded on mediafire please?
Click to expand...
Click to collapse
Can you use the search button please?
僕のINO2から送られてきた
Solved
I was having the same problem and it was due locked bootloader
then i unlocked the bootloader and every thing goes fine
so, dudes, I had the same problem... beyond others
the situation is: YOUR BOOTLOADER LOOKS LIKE UNLOCKED,
BUT IT ISN'T!!
When you rooted your phone, the rooting method modificated this notification. But the true story is that you need to go to Sony website and claim your BOOTLOADER UNLOCK CODE.
Unless you do this, you'll never flash any thing on your smartphone.
Hugs and kisses!!
Have a bit of a problem updating back to 4.0.2.A.0.62. Since I got my phone all updates was done via PC Companion until I finally decided to take the big step forward and unlocking the bootloader and removing the sim lock. This was done by jinx13 (Thanks again!) My next big step was to root it simply just to get rid of all the bloatware.
My phone was already on the latest version, 4.0.2.A.0.62 via PC Companion as as I understand from the forums, it cannot be rooted and you have to downgrade and then upgrade OTA to maintain root as updating using PC Companion will remove the root functionality.
I got Flastool version 0.6.8.0 and then obtained the LT15i 4.0.2.A.0.42 Generic Global World ftf image from jlmc87's post "ARC/ARC S (ROOT.FTF&.IMG)4.0.2.A.0.62 Generic Global World+Flashtool+Ringtones+Other"
I downgraded to 4.0.2.A.0.42 without a hitch, then removed all the crap using constin's post "The Complete Comprehensive List of System Apps for Xperia Arc" as guidance. I then checked the OTA update and 4.0.2.A.0.62 was listed as available. I then proceeded to download and instaal this upgrade. The phone went through the motions of rebooting a few times and appeared to be upgrading but in the end a dialogue box shows "Software update. Could not install new software version. Try again" I have tried about seven times with the same end result before giving up on this option.
Next I tried to upgrade with a .img and proceeded to download Pre-rooted_LT15i_4.0.2.A.0.62_Generic Global World.img also from jlmc87's post, but how do I install this?
I searched a bit on the forums but could not get instructions suitable for a n00b like me to follow, so it was mostly trial and error and a lot more searching.
Once again I used flashtool and this time round I selected to flash using "Fastboot mode". In the fastboot toolbox I then selected "Reboot into fastboot mode (via ADB) and once this was done and drivers installed I selected the option "Select kernel to Flash" I selected the image and the process started.
I thought I did it and my phone is now back to the latest version whilst maintaining root, but unfortunately I got excited way too soon as the upgrade was not successfull as the "Image wont fit because the partition is too small"
Could this too small partition also be the reason why OTA upgrade didnt work? What to do next? Any help and advice greatly appreciated.
Here is the output of the logfile:
24/039/2012 00:39:27 - INFO - Device Status: FASTBOOT mode
24/040/2012 00:40:09 - INFO - Selected kernel (boot.img or kernel.sin): C:\Flashtool\firmwares\Pre-rooted_LT15i_4.0.2.A.0.62_Generic Global World.img
24/040/2012 00:40:09 - INFO - Flashing selected kernel
24/040/2012 00:40:35 - INFO - FASTBOOT Output:
sending 'boot' (231660 KB)...
(bootloader) USB download speed was 9191kB/s
OKAY [ 25.993s]
writing 'boot'...
(bootloader) Flash of partition 'boot' requested
(bootloader) S1 partID 0x00000003, block 0x00000280-0x000002e3
FAILED (remote: Image won't fit, partition too small!)
finished. total time: 25.996s
24/040/2012 00:40:35 - INFO - Please check the log before rebooting into system
24/041/2012 00:41:20 - INFO - Log written to C:\Flashtool\flashtool_2012-03-23_12-21-56.log
24/021/2012 01:21:13 - INFO - Device will now exit fastboot mode and start booting into system
24/021/2012 01:21:13 - INFO - Device disconnected
24/021/2012 01:21:29 - INFO - Device connected with USB debugging off
24/021/2012 01:21:29 - INFO - For 2011 devices line, be sure you are not in MTP mode
24/021/2012 01:21:31 - INFO - Device disconnected
24/021/2012 01:21:33 - INFO - Device connected with USB debugging on
24/021/2012 01:21:33 - INFO - Connected device : LT15
24/021/2012 01:21:34 - INFO - Installed version of busybox : BusyBox v1.19.0 (2011-08-14 23:46:58 CDT) multi-call binary.
24/021/2012 01:21:34 - INFO - Android version : 2.3.4 / kernel version : 2.6.32.9-perf
24/021/2012 01:21:55 - INFO - Root Access Allowed
JJD809 said:
Have a bit of a problem updating back to 4.0.2.A.0.62. Since I got my phone all updates was done via PC Companion until I finally decided to take the big step forward and unlocking the bootloader and removing the sim lock. This was done by jinx13 (Thanks again!) My next big step was to root it simply just to get rid of all the bloatware.
My phone was already on the latest version, 4.0.2.A.0.62 via PC Companion as as I understand from the forums, it cannot be rooted and you have to downgrade and then upgrade OTA to maintain root as updating using PC Companion will remove the root functionality.
I got Flastool version 0.6.8.0 and then obtained the LT15i 4.0.2.A.0.42 Generic Global World ftf image from jlmc87's post "ARC/ARC S (ROOT.FTF&.IMG)4.0.2.A.0.62 Generic Global World+Flashtool+Ringtones+Other"
I downgraded to 4.0.2.A.0.42 without a hitch, then removed all the crap using constin's post "The Complete Comprehensive List of System Apps for Xperia Arc" as guidance. I then checked the OTA update and 4.0.2.A.0.62 was listed as available. I then proceeded to download and instaal this upgrade. The phone went through the motions of rebooting a few times and appeared to be upgrading but in the end a dialogue box shows "Software update. Could not install new software version. Try again" I have tried about seven times with the same end result before giving up on this option.
Next I tried to upgrade with a .img and proceeded to download Pre-rooted_LT15i_4.0.2.A.0.62_Generic Global World.img also from jlmc87's post, but how do I install this?
I searched a bit on the forums but could not get instructions suitable for a n00b like me to follow, so it was mostly trial and error and a lot more searching.
Once again I used flashtool and this time round I selected to flash using "Fastboot mode". In the fastboot toolbox I then selected "Reboot into fastboot mode (via ADB) and once this was done and drivers installed I selected the option "Select kernel to Flash" I selected the image and the process started.
I thought I did it and my phone is now back to the latest version whilst maintaining root, but unfortunately I got excited way too soon as the upgrade was not successfull as the "Image wont fit because the partition is too small"
Could this too small partition also be the reason why OTA upgrade didnt work? What to do next? Any help and advice greatly appreciated.
Here is the output of the logfile:
24/039/2012 00:39:27 - INFO - Device Status: FASTBOOT mode
24/040/2012 00:40:09 - INFO - Selected kernel (boot.img or kernel.sin): C:\Flashtool\firmwares\Pre-rooted_LT15i_4.0.2.A.0.62_Generic Global World.img
24/040/2012 00:40:09 - INFO - Flashing selected kernel
24/040/2012 00:40:35 - INFO - FASTBOOT Output:
sending 'boot' (231660 KB)...
(bootloader) USB download speed was 9191kB/s
OKAY [ 25.993s]
writing 'boot'...
(bootloader) Flash of partition 'boot' requested
(bootloader) S1 partID 0x00000003, block 0x00000280-0x000002e3
FAILED (remote: Image won't fit, partition too small!)
finished. total time: 25.996s
24/040/2012 00:40:35 - INFO - Please check the log before rebooting into system
24/041/2012 00:41:20 - INFO - Log written to C:\Flashtool\flashtool_2012-03-23_12-21-56.log
24/021/2012 01:21:13 - INFO - Device will now exit fastboot mode and start booting into system
24/021/2012 01:21:13 - INFO - Device disconnected
24/021/2012 01:21:29 - INFO - Device connected with USB debugging off
24/021/2012 01:21:29 - INFO - For 2011 devices line, be sure you are not in MTP mode
24/021/2012 01:21:31 - INFO - Device disconnected
24/021/2012 01:21:33 - INFO - Device connected with USB debugging on
24/021/2012 01:21:33 - INFO - Connected device : LT15
24/021/2012 01:21:34 - INFO - Installed version of busybox : BusyBox v1.19.0 (2011-08-14 23:46:58 CDT) multi-call binary.
24/021/2012 01:21:34 - INFO - Android version : 2.3.4 / kernel version : 2.6.32.9-perf
24/021/2012 01:21:55 - INFO - Root Access Allowed
Click to expand...
Click to collapse
Dude, once you unlock the bootloader, you must not update your phone using any of the Sony update utilities like pc companion or ota update service.This would brick your phone.
Go to general section of this forum and search for the thread named. "FOTA Bricked devices" or something like that...The thread will guide you on how to get your phone back to normal.And the download links in the first post are not working I guess,so navigate yourself to the 16 or 17th pages of that thread to find the working download links.
Sent from my LT15i using XDA
Hi KingWickedd, thanks for your comments. My phone is not bricked, it is fine, all I want is to upgrade it to firmware version 4.0.2.A.0.62 whilst still maintaining root. Currently it is still on 4.0.2.A.0.42
I will not upgrate using PC Companion or OTA but can not install a pre-rooted IMG image of .62 firmware.
JJD809 said:
Once again I used flashtool and this time round I selected to flash using "Fastboot mode". In the fastboot toolbox I then selected "Reboot into fastboot mode (via ADB) and once this was done and drivers installed I selected the option "Select kernel to Flash" I selected the image and the process started.
I thought I did it and my phone is now back to the latest version whilst maintaining root, but unfortunately I got excited way too soon as the upgrade was not successfull as the "Image wont fit because the partition is too small"
Could this too small partition also be the reason why OTA upgrade didnt work? What to do next? Any help and advice greatly appreciated.
Here is the output of the logfile:
24/039/2012 00:39:27 - INFO - Device Status: FASTBOOT mode
24/040/2012 00:40:09 - INFO - Selected kernel (boot.img or kernel.sin): C:\Flashtool\firmwares\Pre-rooted_LT15i_4.0.2.A.0.62_Generic Global World.img
24/040/2012 00:40:09 - INFO - Flashing selected kernel
24/040/2012 00:40:35 - INFO - FASTBOOT Output:
sending 'boot' (231660 KB)...
(bootloader) USB download speed was 9191kB/s
OKAY [ 25.993s]
writing 'boot'...
(bootloader) Flash of partition 'boot' requested
(bootloader) S1 partID 0x00000003, block 0x00000280-0x000002e3
FAILED (remote: Image won't fit, partition too small!)
finished. total time: 25.996s
24/040/2012 00:40:35 - INFO - Please check the log before rebooting into system
24/041/2012 00:41:20 - INFO - Log written to C:\Flashtool\flashtool_2012-03-23_12-21-56.log
Click to expand...
Click to collapse
OMG! You are trying to flash a system image in the boot partition!?
Instead of using Flash Tool, use fastboot and command prompt to flash the img file to the system partition.
Code:
fastboot flash system system.img
Remember to download the fastboot package and then copy the img file to fastboot folder, rename it to system.img and run the above code in the command prompt after navigating to the fastboot directory.
Or simply use this : http://forum.xda-developers.com/showthread.php?t=1551073
Remember to flash that img file to "system" partition and not the boot partition.
Thank you very much!! That did the trick!! Thanks for pointing out the huge mistake I (almost) made!!
I updated using QuickIMG
I previously tried replacing my ROM which started this whole problem, i already had a custom rom installed and tried replacing it with a newer version of the same ROM, didnt work as my phone was stuck on a boot loop, ive read through multiple posts and followed instructions and now my phone dont go past the Boot screen and says relocked, i have no recovery option and when trying to flash a recovery.img file it fails. ive read about RUU files but i dont have filefactory premium, so if anybody could explain how i can fix this issue and get my phone working again id highly appreciate it
This is currently the screen im looking at:
*** RELOCKED ***
Endeavoru PVT SHIP S-ON RL
HBOOT-0.96.0000
CPLD-None
MICROP-None
RADIO-1.1204.105.14
eMMC-bootmode: disabled
CPU-bootmode: disabled
HW Secure boot: enabled
MODEM PATH: OFF
VOL UP
VOL DOWN
POWER
FASTBOOT USB
HBOOT
REBOOT
REBOOT DOWNLOADER
POWER DOWN
Update: Ive finally found the RUU file thats matches my system so if this is what i need could someone explain what i do now.
You need to unlock your bootloader to flash a recovery.img
Michealtbh said:
You need to unlock your bootloader to flash a recovery.img
Click to expand...
Click to collapse
Ive just tried this and the message i get when trying to flash is
< waiting for device >
sending 'recovery' (5732 KB)
OKAY [ 0.747s]
writing 'recovery'...
FAILED (remote: battery low)
finished. total time: 0.951s
Am i able to charge my phone at boot without recovery?
Man, just follow this steps:
1- from bootloader screen go to fast boot then select powerdown
2- wait a minute or 2 till its totally shuts down
3- plug in your charger
4- leave it for an hour or so (just be sure the screen remains off and the red lid is on for charging, if not then repeat the previous steps)
5- unplug your phone
6- power on your device, from bootloader screen, select fastboot
7- plug in your USB between your PC and HOX
8- redo the faild step
hope this helps
Hossam.Abdelsalam said:
Man, just follow this steps:
1- from bootloader screen go to fast boot then select powerdown
2- wait a minute or 2 till its totally shuts down
3- plug in your charger
4- leave it for an hour or so (just be sure the screen remains off and the red lid is on for charging, if not then repeat the previous steps)
5- unplug your phone
6- power on your device, from bootloader screen, select fastboot
7- plug in your USB between your PC and HOX
8- redo the faild step
hope this helps
Click to expand...
Click to collapse
Thanks for the reply, i finally got recovery back, my phone loads up to the homescreen but a triangle with an ! inside shows up and reboots, ive tried flashing my RUU, i can flash 'boot_signed.img' successfully but when i try flash 'system.img' it says (number of bytes) cant be allocated.
It is possible to boot directly into recovery without flashing it
What You need is fastboot binaries and image file for recovery.
1. reboot device into fastboot mode.
2. open CMD or bash
3. run this command: "fastboot.exe boot recovery.img"
this saved my life once
after flash stock rom using miflash and click clean all and lock , the flashing was successful then the phone was stuck on bootloader and now i cant even turn off the phone, the screen stay in fastboot..what should i do? please help me and tell me what to do step by step cz now the bootloader is locked..
Can you post the Miflash log?
Miflash/log folder, Txt file + or -25kb.
Use spoiler.
If you have a Chinese version (K40s)and you have locked the bootloader on a rom other than Chinese, it comes from that.
bvyral said:
after flash stock rom using miflash and click clean all and lock , the flashing was successful then the phone was stuck on bootloader and now i cant even turn off the phone, the screen stay in fastboot..what should i do? please help me and tell me what to do step by step cz now the bootloader is locked..
Click to expand...
Click to collapse
you know the Steps to Flash StockROM, only look 4 another Firmware, iam Think its Not the Correct
System23 said:
you know the Steps to Flash StockROM, only look 4 another Firmware, iam Think its Not the Correct
Click to expand...
Click to collapse
What do you mean( only look 4 another Firmware)?
NOSS8 said:
What do you mean( only look 4 another Firmware)?
Click to expand...
Click to collapse
you must Flash the Correct Firmware 4 ya Device, when ya have this the Device Boot Corectly after Flash it!! thats why iam Think its not the Correct Firmware you used!!
look here to Find your Firmware Xiamoi Pocco F4 Firmware Archiv
System23 said:
you must Flash the Correct Firmware 4 ya Device, when ya have this the Device Boot Corectly after Flash it!! thats why iam Think its not the Correct Firmware you used!!
Click to expand...
Click to collapse
I'm not the OP.
With the bootloader unlock you can flash any version of stock rom, EEA, Global, etc, and lock the bootloader.
Except if you have a K40S or you have to let the bootloader unlock.
System23 said:
look here to Find your Firmware Xiamoi Pocco F4 Firmware Archiv
Click to expand...
Click to collapse
But i got the firmware from here..i choose poco f4 global fastboot type
NOSS8 said:
I'm not the OP.
With the bootloader unlock you can flash any version of stock rom, EEA, Global, etc, and lock the bootloader.
Except if you have a K40S or you have to let the bootloader unlock.
Click to expand...
Click to collapse
Yea..the bootloader is now locked..what should i do?..and can it be done?..
bvyral said:
Yea..the bootloader is now locked..what should i do?..and can it be done?..
Click to expand...
Click to collapse
Do you have a Poco F4 or a K40S?
Can you post the Miflash log?
Miflash/log folder, Txt file + or -25kb.
Use spoiler
bvyral said:
Yea..the bootloader is now locked..what should i do?..and can it be done?..
Click to expand...
Click to collapse
If you need to leave Fastboot mode, just press and keep a combination of the Power button + the Volume Down for about 10 seconds.
have you any Expierience with Fastboot and the Terminal? than i have Read that your Device has A/B Partitions!!! That means SLOT A has now your Flashed Firmware & SLOT B has the older StockROM!!! Normaly when a Partition is Broken it changes the SLOT Automaticly!!!! with Terminal and fastboot can you Interact with the Device via PC!!!! so that you can use this commands to become the Information witch SLOT is Active, and SET one of the Booth Partitions!!!!
Show Activ SLOT
fastboot getvar current-slot
SET a SLOT
fastboot set_active b
or
fastboot set_active a
Show Activ SLOT
fastboot getvar current-slot
Reboot the Device
fastboot reboot
I have write a simple script that Downloads the Firmware,Extract it,copy Files 4 Flash,and Start Flash!!!
you Found that in my Onlinestorage Here >> Xiaomi_POCCO_F4_Firmware_Flash
Only Download it and extract it!!!
Run "Download_Firmware.cmd" and Connect Device via USB to PC and start it in Fastboot-Mode!!!
The Firmware is
Device: POCO F4 Global
Codename: munch
Version: V14.0.2.0.TLMMIXM
Branch: Stable
Type: Fastboot
Size: 6.3 GB
Release Date: 2023-03-12
Package Name: munch_global_images_V14.0.2.0.TLMMIXM_20230312.0000.00_13.0_global_cad4c8f425.tg
After the Download its extract it and delete the Archives and still 1 Firmware Folder exists!!!
After that its start the "flash_all.bat" that comes with this Firmware!!!! So make sure you have Connected the device via USB
to PC and have started Fastboot-Mode!!
than let it Flash the MIUI ROM!!!! if this Method working the Device will be Start normaly!!!
If this not work use "MIFLASHTOOL" and click on select and choose the Firmware Folder!! and Flash it with this Method!!!!
hope one of the Options will Work!!
System23 said:
have you any Expierience with Fastboot and the Terminal? than i have Read that your Device has A/B Partitions!!! That means SLOT A has now your Flashed Firmware & SLOT B has the older StockROM!!! Normaly when a Partition is Broken it changes the SLOT Automaticly!!!! with Terminal and fastboot can you Interact with the Device via PC!!!! so that you can use this commands to become the Information witch SLOT is Active, and SET one of the Booth Partitions!!!!
Show Activ SLOT
fastboot getvar current-slot
SET a SLOT
fastboot set_active b
or
fastboot set_active a
Show Activ SLOT
fastboot getvar current-slot
Reboot the Device
hope one of the Options will Work!!
Click to expand...
Click to collapse
You cannot use Mi Flash with a locked bootloader.
System23 said:
have you any Expierience with Fastboot and the Terminal? than i have Read that your Device has A/B Partitions!!! That means SLOT A has now your Flashed Firmware & SLOT B has the older StockROM!!! Normaly when a Partition is Broken it changes the SLOT Automaticly!!!! with Terminal and fastboot can you Interact with the Device via PC!!!! so that you can use this commands to become the Information witch SLOT is Active, and SET one of the Booth Partitions!!!!
Show Activ SLOT
fastboot getvar current-slot
SET a SLOT
fastboot set_active b
or
fastboot set_active a
Show Activ SLOT
fastboot getvar current-slot
Reboot the Device
fastboot reboot
I have write a simple script that Downloads the Firmware,Extract it,copy Files 4 Flash,and Start Flash!!!
you Found that in my Onlinestorage Here >> Xiaomi_POCCO_F4_Firmware_Flash
Only Download it and extract it!!!
Run "Download_Firmware.cmd" and Connect Device via USB to PC and start it in Fastboot-Mode!!!
The Firmware is
Device: POCO F4 Global
Codename: munch
Version: V14.0.2.0.TLMMIXM
Branch: Stable
Type: Fastboot
Size: 6.3 GB
Release Date: 2023-03-12
Package Name: munch_global_images_V14.0.2.0.TLMMIXM_20230312.0000.00_13.0_global_cad4c8f425.tg
After the Download its extract it and delete the Archives and still 1 Firmware Folder exists!!!
After that its start the "flash_all.bat" that comes with this Firmware!!!! So make sure you have Connected the device via USB
to PC and have started Fastboot-Mode!!
than let it Flash the MIUI ROM!!!! if this Method working the Device will be Start normaly!!!
If this not work use "MIFLASHTOOL" and click on select and choose the Firmware Folder!! and Flash it with this Method!!!!
hope one of the Options will Work!!
Click to expand...
Click to collapse
not working...error:FAILED (remote: Erase is not allowed in Lock State)
OK, original Tools and Firmware cannot Flash in locked BL!! than you can Flash in Recovery or in EDL Mode!! you stuck at Fastboot Mode so you cant Flash via Recovery!!! or you use fastboot in Terminal and test the following commands!!!
Boot Recovery via fastboot
fastboot boot xxx/Images/recovery.img
or
Reboot Recovery
fastboot reboot recovery
or
Flash Boot/Recovery
fastboot flash boot xxx/Images/boot.img
fastboot flash recovery xxx/Images/recovery.img
fastboot reboot
when this not working you can use EDL-Mode!!!
Poco F4 test Point Reboot 9008 EDL - ROM-Provider
Poco F4 test point is typically a set of pins on the device's circuit board that can be shorted together in order to put the device into edl mod
romprovider.com
Than you can Flash it with QPST or QFiL Tool from Qualcomm!!! but i must look when i at home if the fastboot Firmware includes all needed Files!!! rawprogrammer0.xml patch0.xml firehosexxxx.mbn
System23 said:
OK, original Tools and Firmware cannot Flash in locked BL!! than you can Flash in Recovery or in EDL Mode!! you stuck at Fastboot Mode so you cant Flash via Recovery!!! or you use fastboot in Terminal and test the following commands!!!
Click to expand...
Click to collapse
Stop posting non-solutions.
Miflash unusable with the bootloader locked. (Yet noted on the OP).
Regarding your last post, the command syntax is wrong and it will not change anything.
For EDL mode, you don't know, it is not necessary to open the phone to enter EDL mode and anyway, it will not have permission to flash.
QPST or QFiL Tool from Qualcomm may work but not on this device (too recent) and Sahara is a very sensitive program and requires some experience to avoid errors such as:
ERROR: function: sahara_rx_data:277 Unable to read packet header. Only read 0 bytes.
ERROR: function: sahara_main:983 Sahara protocol error
ERROR: function: main:320 Uploading Image using Sahara protocol failed
Download Fail:Sahara Fail:QSaharaServer Fail process fail.
Poco F4 (Munch) Firmware Flash File (Stock ROM) - ROM-Provider
Download Poco F4 Firmware Flash File stock ROM, here we share latest firmware for Xiaomi Poco F4 with flash tool & usb driver
www.google.de
with MiFlash in EDL-Mode and the EDL-Firmware GLO, its like this Article a working Solution!! and i dont know if fastboot reboot edl with special edl fastboot work, and I dont know if it can Start with ButtonsCombo!!! adb reboot edl is not availible wile stuck at Fastboot-Mode!! iam only give ideas to test them out, in variants they i know!! Iam Testing my variants out to find a way that works!!!
NOSS8 said:
Stop posting non-solutions.
Miflash unusable with the bootloader locked. (Yet noted on the OP).
Regarding your last post, the command syntax is wrong and it will not change anything.
For EDL mode, you don't know, it is not necessary to open the phone to enter EDL mode and anyway, it will not have permission to flash.
QPST or QFiL Tool from Qualcomm may work but not on this device (too recent) and Sahara is a very sensitive program and requires some experience to avoid errors such as:
ERROR: function: sahara_rx_data:277 Unable to read packet header. Only read 0 bytes.
ERROR: function: sahara_main:983 Sahara protocol error
ERROR: function: main:320 Uploading Image using Sahara protocol failed
Download Fail:Sahara Fail:QSaharaServer Fail process fail.
Click to expand...
Click to collapse
give me more Input, iam intressted to read more!!!
System23 said:
give me more Input, iam intressted to read more!!!
Click to expand...
Click to collapse
This is not the subject of the thread. (do some research).
If it is impossible to enter recovery or fastboot mode and if it is not a HW problem, the phone is in EDL Mode.
It will not appear on the PC unless you install the Qualcomm drivers and will be detected by Miflash (in Fastboot mode, no need to log in) on a com port (login mandatory), but you will not have permission to flash (requires a special account).
This permission is not needed on very old devices.
Until the OP has answered my questions, I could not provide him with a possible solution.
System23 said:
have you any Expierience with Fastboot and the Terminal? than i have Read that your Device has A/B Partitions!!! That means SLOT A has now your Flashed Firmware & SLOT B has the older StockROM!!! Normaly when a Partition is Broken it changes the SLOT Automaticly!!!! with Terminal and fastboot can you Interact with the Device via PC!!!! so that you can use this commands to become the Information witch SLOT is Active, and SET one of the Booth Partitions!!!!
Show Activ SLOT
fastboot getvar current-slot
SET a SLOT
fastboot set_active b
or
fastboot set_active a
Show Activ SLOT
fastboot getvar current-slot
Reboot the Device
fastboot reboot
I have write a simple script that Downloads the Firmware,Extract it,copy Files 4 Flash,and Start Flash!!!
you Found that in my Onlinestorage Here >> Xiaomi_POCCO_F4_Firmware_Flash
Only Download it and extract it!!!
Run "Download_Firmware.cmd" and Connect Device via USB to PC and start it in Fastboot-Mode!!!
The Firmware is
Device: POCO F4 Global
Codename: munch
Version: V14.0.2.0.TLMMIXM
Branch: Stable
Type: Fastboot
Size: 6.3 GB
Release Date: 2023-03-12
Package Name: munch_global_images_V14.0.2.0.TLMMIXM_20230312.0000.00_13.0_global_cad4c8f425.tg
After the Download its extract it and delete the Archives and still 1 Firmware Folder exists!!!
After that its start the "flash_all.bat" that comes with this Firmware!!!! So make sure you have Connected the device via USB
to PC and have started Fastboot-Mode!!
than let it Flash the MIUI ROM!!!! if this Method working the Device will be Start normaly!!!
If this not work use "MIFLASHTOOL" and click on select and choose the Firmware Folder!! and Flash it with this Method!!!!
hope one of the Options will Work!!
Click to expand...
Click to collapse
thanks, after managing to unlock the phone just by moving it to local disk c, after some googling n youtubing, and i tried ur method again ,editing some flash_all bat.((
fastboot %* getvar product 2>&1 | findstr /r /c:"^product: *munch" || echo Missmatching image and device
fastboot %* getvar product 2>&1 | findstr /r /c:"^product: *munch" || exit /B 1))
and run it....it works.. i sincerely thanks you..