After flashing TWRP version 3.7.0_9.0-poplar, and waiting for "Your device has been unlocked and can't be trusted." message to disappear it displays "Your device has been unlocked and the boot image is not working".
How have I flashed TWRP:
Code:
# NOTE: I am using Arch Linux as the host, not windows adb installed from official repositories.
adb reboot bootloader
fastboot oem unlock 0x################ (I have blackout unlock code)
# Restarted and seted up device again, OEM unlocked is enabled in settings + USB debugging
adb reboot bootloader
fastboot flash boot twrp-3.7.0_9-0-poplar.img
After flashing finished and phone being restarted I encountered the message above.
So far I have tried to:
Boot into recovery mode. Power button + Volume Down, the same result except now I have SONY logo for around 5 seconds.
Using ADB to boot into recovery. "adb wait-for-device" doesn't work and never sees the device.
Also when plugged into a computer green light appears in left top corner of phone and also it won't react to any buttons like Power and Volume Up/Down. But Power + Volume Up (completely turn off device) is an exception and it still works.
I think TWRP was corrupted when transferring probably because I have two cables and probably grabbed the one which likes to on random stop transferring data
Is there a way to flash original boot or repair this phone?
EDIT: Okay so I managed to enable fastboot mode. But I can't find stock Boot/ROM.
EDIT 2: Finally created ftf image using Flashtool using files downloaded using XperiFirm. Now the issue is when entering flashmode (Volume Down + Power [NOT fastboot]), green light indicator lights up for ~4.5 seconds then for 2 seconds it turns off and cycle repeats for ever until I unplug the cable. Also when just plugging cable without pressing Vol- the result is the same. If flashmode doesn't work is there a workaround to use fastboot to flash ftf file? Also when I enter fastboot mode and try to get unlock ability I get an error:
Code:
$ fastboot flashing get_unlock_ability
FAILED (remote: 'unknown command')
fastboot: error: Command failed
(Seems like Experia XZ is refusing to execute the command, but I can still flash anything I want onto it using "fastboot flash name file")
EDIT 3: Okay so using Sin extractor in flash tool I have extracted contents form kernel_S1-SW-LIVE-DE8D-PID1-0007-MMC.sin and flashed it as boot and... it works!, but also no. Because when I was messing with this phone I also have flashed something to recovery and oem partitions and I don't know what .sin files correspond to those partitions, below I provide list of files download by ExpriFirm for Experia XZ (F8331)
F8331_Orange MCV FR-ES-PL-SK-RO_41.3.A.2.192-R9E:
Code:
Folders:
boot
Sin Files:
adspso_S1-SW-LIVE-DE8D-PID1-0007-MMC.sin
amss_fs_1_S1-MODEMSW-LIVE-DE8D-PID1-0007-MMC.sin
amss_fs_2_S1-MODEMSW-LIVE-DE8D-PID1-0007-MMC.sin
amss_fsg_S1-MODEMSW-LIVE-DE8D-PID1-0007-MMC.sin
apps_log_S1-SW-LIVE-DE8D-PID1-0007-MMC.sin
cache_S1-SW-LIVE-DE8D-PID1-0007-MMC.sin
diag_S1-SW-LIVE-DE8D-PID1-0007-MMC.sin
elabel-F8331-row-row_201804120243693.1_41.3.A.2.149_S1-ELABEL-LIVE-DE8D-PID1-0004-MMC.sin
fotakernel_S1-SW-LIVE-DE8D-PID1-0007-MMC.sin
kernel_S1-SW-LIVE-DE8D-PID1-0007-MMC.sin
modem_S1-MODEMSW-LIVE-DE8D-PID1-0007-MMC.sin
oem_S1-CUST-LIVE-DE8D-PID1-0004-MMC.sin
partition-image_S1-SW-LIVE-DE8D-PID1-0007-MBR.sin
persist_S1-SW-LIVE-DE8D-PID1-0007-MMC.sin
Qnovo_S1-SW-LIVE-DE8D-PID1-0007-MMC.sin
ramdump_S1-SW-LIVE-DE8D-PID1-0007-MMC.sin
ssd_S1-SW-LIVE-DE8D-PID1-0007-MMC.sin
system_S1-SW-LIVE-DE8D-PID1-0007-MMC.sin
userdata_S1-CUST-LIVE-DE8D-PID1-0004-MMC.sin
XML Files:
fwinfo.xml
update.xml
TA Files:
auto-boot.ta
cust-reset.ta
fota-reset.ta
master-reset.ta
osv-restriction.ta
reset-kernel-cmd-debug.ta
reset-non-secure-adb.ta
reset-wipe-reason.ta
simlock.ta
F8331_Orange MCV FR-ES-PL-SK-RO_41.3.A.2.192-R9E/boot
Code:
SIN Files:
cmnlib_S1_Boot_MSM8996_LA2_0_O_204_AID_1_TONE-TEST-HWID009470E1-SWID0C-APPID01-OEM0-AID1-DEBUG00_S1-BOOT-TEST-B316-0001-MMC.sin
cmnlib_S1_Boot_MSM8996_LA2_0_O_204_AID_4_PLATFORM-TONE-COM-LIVE-HWID009470E1-SWID0C-APPID01-OEM1-AID4-DEBUG00_S1-BOOT-LIVE-DE8D-0004-MMC.sin
cmnlib_S1_Boot_MSM8996_LA2_0_O_204_AID_4_PLATFORM-TONE-LIVE-HWID009470E1-SWID0C-APPID01-OEM1-AID4-DEBUG00_S1-BOOT-LIVE-DE8D-0004-MMC.sin
devcfg_S1_Boot_MSM8996_LA2_0_O_204_AID_1_TONE-TEST-HWID009470E1-SWID05-OEM0-AID1-DEBUG00_S1-BOOT-TEST-B316-0001-MMC.sin
devcfg_S1_Boot_MSM8996_LA2_0_O_204_AID_4_PLATFORM-TONE-COM-LIVE-HWID009470E1-SWID05-OEM1-AID4-DEBUG00_S1-BOOT-LIVE-DE8D-0004-MMC.sin
devcfg_S1_Boot_MSM8996_LA2_0_O_204_AID_4_PLATFORM-TONE-LIVE-HWID009470E1-SWID05-OEM1-AID4-DEBUG00_S1-BOOT-LIVE-DE8D-0004-MMC.sin
emmc_appsboot_S1_Boot_MSM8996_LA2_0_O_204_AID_1_TONE-TEST-HWID009470E1-SWID09-OEM0-AID1-DEBUG00_S1-BOOT-TEST-B316-0001-MMC.sin
emmc_appsboot_S1_Boot_MSM8996_LA2_0_O_204_AID_4_PLATFORM-TONE-COM-LIVE-HWID009470E1-SWID09-OEM1-AID4-DEBUG00_S1-BOOT-LIVE-DE8D-0004-MMC.sin
emmc_appsboot_S1_Boot_MSM8996_LA2_0_O_204_AID_4_PLATFORM-TONE-LIVE-HWID009470E1-SWID09-OEM1-AID4-DEBUG00_S1-BOOT-LIVE-DE8D-0004-MMC.sin
hyp_S1_Boot_MSM8996_LA2_0_O_204_AID_1_TONE-TEST-HWID009470E1-SWID15-OEM0-AID1-DEBUG00_S1-BOOT-TEST-B316-0001-MMC.sin
hyp_S1_Boot_MSM8996_LA2_0_O_204_AID_4_PLATFORM-TONE-COM-LIVE-HWID009470E1-SWID15-OEM1-AID4-DEBUG00_S1-BOOT-LIVE-DE8D-0004-MMC.sin
hyp_S1_Boot_MSM8996_LA2_0_O_204_AID_4_PLATFORM-TONE-LIVE-HWID009470E1-SWID15-OEM1-AID4-DEBUG00_S1-BOOT-LIVE-DE8D-0004-MMC.sin
keymaster_S1_Boot_MSM8996_LA2_0_O_204_AID_1_TONE-TEST-HWID009470E1-SWID0C-APPID01-OEM0-AID1-DEBUG00_S1-BOOT-TEST-B316-0001-MMC.sin
keymaster_S1_Boot_MSM8996_LA2_0_O_204_AID_4_PLATFORM-TONE-COM-LIVE-HWID009470E1-SWID0C-APPID01-OEM1-AID4-DEBUG00_S1-BOOT-LIVE-DE8D-0004-MMC.sin
keymaster_S1_Boot_MSM8996_LA2_0_O_204_AID_4_PLATFORM-TONE-LIVE-HWID009470E1-SWID0C-APPID01-OEM1-AID4-DEBUG00_S1-BOOT-LIVE-DE8D-0004-MMC.sin
pmic_S1_Boot_MSM8996_LA2_0_O_204_AID_1_TONE-TEST-HWID009470E1-SWID16-OEM0-AID1-DEBUG00_S1-BOOT-TEST-B316-0001-MMC.sin
pmic_S1_Boot_MSM8996_LA2_0_O_204_AID_4_PLATFORM-TONE-COM-LIVE-HWID009470E1-SWID16-OEM1-AID4-DEBUG00_S1-BOOT-LIVE-DE8D-0004-MMC.sin
pmic_S1_Boot_MSM8996_LA2_0_O_204_AID_4_PLATFORM-TONE-LIVE-HWID009470E1-SWID16-OEM1-AID4-DEBUG00_S1-BOOT-LIVE-DE8D-0004-MMC.sin
rpm_S1_Boot_MSM8996_LA2_0_O_204_AID_1_TONE-TEST-HWID009470E1-SWID0A-OEM0-AID1-DEBUG00_S1-BOOT-TEST-B316-0001-MMC.sin
rpm_S1_Boot_MSM8996_LA2_0_O_204_AID_4_PLATFORM-TONE-COM-LIVE-HWID009470E1-SWID0A-OEM1-AID4-DEBUG00_S1-BOOT-LIVE-DE8D-0004-MMC.sin
rpm_S1_Boot_MSM8996_LA2_0_O_204_AID_4_PLATFORM-TONE-LIVE-HWID009470E1-SWID0A-OEM1-AID4-DEBUG00_S1-BOOT-LIVE-DE8D-0004-MMC.sin
s1sbl_S1_Boot_MSM8996_LA2_0_O_204_AID_1_TONE-S1-BOOT-TEST-B316-0001-MMC.sin
s1sbl_S1_Boot_MSM8996_LA2_0_O_204_AID_4_S1-BOOT-LIVE-DE8D-0004-ELF_S1-BOOT-LIVE-DE8D-0004-MMC.sin
tzs1attest_S1_Boot_MSM8996_LA2_0_O_204_AID_1_TONE-TEST-HWID009470E1-SWID0C-APPID01-OEM0-AID1-DEBUG00_S1-BOOT-TEST-B316-0001-MMC.sin
tzs1attest_S1_Boot_MSM8996_LA2_0_O_204_AID_4_PLATFORM-TONE-COM-LIVE-HWID009470E1-SWID0C-APPID01-OEM1-AID4-DEBUG00_S1-BOOT-LIVE-DE8D-0004-MMC.sin
tzs1attest_S1_Boot_MSM8996_LA2_0_O_204_AID_4_PLATFORM-TONE-LIVE-HWID009470E1-SWID0C-APPID01-OEM1-AID4-DEBUG00_S1-BOOT-LIVE-DE8D-0004-MMC.sin
tz_S1_Boot_MSM8996_LA2_0_O_204_AID_1_TONE-TEST-HWID009470E1-SWID07-OEM0-AID1-DEBUG00_S1-BOOT-TEST-B316-0001-MMC.sin
tz_S1_Boot_MSM8996_LA2_0_O_204_AID_4_PLATFORM-TONE-COM-LIVE-HWID009470E1-SWID07-OEM1-AID4-DEBUG00_S1-BOOT-LIVE-DE8D-0004-MMC.sin
tz_S1_Boot_MSM8996_LA2_0_O_204_AID_4_PLATFORM-TONE-LIVE-HWID009470E1-SWID07-OEM1-AID4-DEBUG00_S1-BOOT-LIVE-DE8D-0004-MMC.sin
tzs1sbl_S1_Boot_MSM8996_LA2_0_O_204_AID_1_TONE-TEST-HWID009470E1-SWID0C-APPID01-OEM0-AID1-DEBUG00_S1-BOOT-TEST-B316-0001-MMC.sin
tzs1sbl_S1_Boot_MSM8996_LA2_0_O_204_AID_4_PLATFORM-TONE-COM-LIVE-HWID009470E1-SWID0C-APPID01-OEM1-AID4-DEBUG00_S1-BOOT-LIVE-DE8D-0004-MMC.sin
tzs1sbl_S1_Boot_MSM8996_LA2_0_O_204_AID_4_PLATFORM-TONE-LIVE-HWID009470E1-SWID0C-APPID01-OEM1-AID4-DEBUG00_S1-BOOT-LIVE-DE8D-0004-MMC.sin
xbl_S1_Boot_MSM8996_LA2_0_O_204_AID_1_TONE-TEST-HWID009470E1-SWID00-OEM0-AID1-DEBUG00_S1-BOOT-TEST-B316-0001-MMC.sin
xbl_S1_Boot_MSM8996_LA2_0_O_204_AID_4_PLATFORM-TONE-COM-LIVE-HWID009470E1-SWID00-OEM1-AID4-DEBUG00_S1-BOOT-LIVE-DE8D-0004-MMC.sin
xbl_S1_Boot_MSM8996_LA2_0_O_204_AID_4_PLATFORM-TONE-LIVE-HWID009470E1-SWID00-OEM1-AID4-DEBUG00_S1-BOOT-LIVE-DE8D-0004-MMC.sin
TA Files:
Kagura_S1BootConfig_MiscTA.ta
XML Files:
boot_delivery.xml
EDIT 4: Also I have egzamined the green light further and it looks like it reboots phone, because when I hold Vol- after green light turn off it will enter fastboot mode. I now know that ROM is located in system.sin, but when I extract the data from it I get ext4 partition which I can mount but I have absolutly no idea how to flash it as Experia XZ complains that file is too big (~5.3GB). Oh and I would almost forgot, I still don't know which .sin file is the recovery one.
EDIT 5: BIG NEWS!!! After unbricking boot partition I was able to install TWRP on recovery. I will get microSD ASAP and I will see what if I can flash stock ROM at least for now.
Thanks in advice for any kind of help!
Related
a few days ago I tried to root my xperia S to get more functionality. So i read on the internet on several blogs and started to download a rom. First i unlocked my phone with fastboot.exe. Then i try to boot via Command prompt. It says everinthing was okay in about 120 secs, but when i disconnect and tried to start my phone, i only got the sony logo and that was freezed. Even if i reboot, it cames again. I've tried some other ftf files to flash, but nothing worked. Now my battery is empty, and i don't get the phone back in fastboot mode.
Anyone have tips for me? Im very new in it so please help me...
leenbrak said:
a few days ago I tried to root my xperia S to get more functionality. So i read on the internet on several blogs and started to download a rom. First i unlocked my phone with fastboot.exe. Then i try to boot via Command prompt. It says everinthing was okay in about 120 secs, but when i disconnect and tried to start my phone, i only got the sony logo and that was freezed. Even if i reboot, it cames again. I've tried some other ftf files to flash, but nothing worked. Now my battery is empty, and i don't get the phone back in fastboot mode.
Anyone have tips for me? Im very new in it so please help me...
Click to expand...
Click to collapse
For now, charge your battery first. U atleast need to have 80% charge before u can fastboot/flash your phone.
- (Only If Your Phone Doesnt Start) Press Power Button+Volume Up for some 10/15 seconds, u will get three vibrations which mean u just hard reset the phone. It normally takes about 2/3 minutes to boot up a phone after a new flash or kernel has been installed. If not then follow the the below instructions after the hard reset and see if it works.
- Assuming that you have already got the downloaded ftf (Firmware file) saved in the FIRMWARE folder of flashtool, if not then save it.
- Open up your flashtool.
- Press and hold the VOLUME DOWN key.
- Keep it pressed, connect the USB cable to your PC (assuming that u already have the usb connected to the phone)
- Release the Volume Down key when phone's GREEN LED lights
- Click the flash button (yes: the thunder icon up left)
- Select "Flahsmode" and click "OK"
- Select your desire firmware and click "OK", DON'T TOUCH ANYTHING ELSE
- Flashtool will prepare the files for flashing, just be patient
- Flashtool will start flashing automatically, let it finish to 100%
- At the end, Flashtool will prompt a line saying u need to check Unknown Sources And USB Debugging mode and thats when u know that u have successfully flashed a stock/custom ROM.
- Disconnect the phone, power up and give it some minute to boot up and work.
- Have fun :highfive:
HOW TO ROOT:
Depending on the Firmware/ROM the rooting method varies, i use Advanced Kernel Build14 on my new stock ICS firmware but always used DoomKernelv0.4+Recovery to Root Stock GB firmwares
You Can Download Any One Of them:
- AdvancedKernel14(Fastboot) For ICS
- DoomKernels(Fastboot+Recovery) Thread
How to Fastboot and just Root without Recovery and back to STOCK KERNEL:
First of all i will advice you to do this if ONLY you are planning to root your phone but want to come back on your stock kernel. Its a good thing to do if you have just flashed a new firmware like 6.0.A.2.45
Here's what you do:
[ requirements ]
# bootloader of the device is UNLOCKED
# Download and install FASTBOOT DRIVERS (DoomLord)
# Downlaod and Unzip FASTBOOT BINARIES
- Unplugged your USB from pc and Turn Off your phone
- Rename Advanced Kernel Build 14 to kernel.elf or unzip DoomlordKernelv0.4, unzip it and copy kernel.elf
- Open Fastboot Binaries folder
- Go To Fastboot folder, paste the kernel.elf file
- Press and hold VOLUME UP key.
- Keep it pressed and connect your phone and pc through USB.
- BLUE LED light will turn on means you are in fastboot mode, release the key.
- Fastboot folder opened, press SHIFT+RIGHT MOUSE button on the screen and choose Open Command Window here.
- Type
fastboot devices
Click to expand...
Click to collapse
to check if your phone is connected properly and if it is, something like PSDN : xxxxx will be shown.
- Type
fastboot flash boot kernel.elf
Click to expand...
Click to collapse
- Give it some seconds as it will load the kernel on the phone.
- Type
fastboot reboot
Click to expand...
Click to collapse
and your phone will restart. Give it some minute and it will boot up plus you will have root access :highfive:
ONLY IF YOU WANT TO GO BACK ON STOCK KERNEL WITH ROOT ACCESS:
- Assuming you have 7zip installed in your system, if not then google, download and install the programme.
- Right click on the ftf (firmware) file.
- Choose 7zip > Open Archive
- Click kernel.sin > Extract and save it anywhere in your PC
- Connect your phone through USB (You Can do it even if your phone is ON)
- Click the THUNDER ICON.
- Choose FASTBOOT. Choose OK.
- Click Reboot into fastboot mode (via ADB) if it gives error on flashtool then click REBOOT INTO FASTBOOT MODE ( via FASTBOOT)
- The Phone will turn off and will automatically go into fastboot mode ( BLUE LED )
- Click SELECT KERNEL TO FLASH
- Choose kernel.sin
- Give the kernel some seconds to flash and the phone will restart.
- You will see the SONY logo again if you have done it correctly ( YES YOU WILL because you just successfully flashed the stock kernel)
- Wait for some minute and the phone will reboot with stock kernel still with root access to it.
ALTERNATIVE WAY TO FLASH THE kernel.sin :
- Copy and paste the kernel.sin file over at the fastboot folder in fastboot binaries. Delete the kernel.elf
- Type fastboot devices
- Type fastboot flash boot kernel.sin
- Type fastboot reboot
:highfive: :highfive:
Follow the above steps and you will definitely have a success
I dont think i can charge my battery. When i put it on a charger, the led is burning red. I've done that for a hole night. But if i disconnect, and try to power up, it doesnt react at all. When i connect it on my pc, the pc doesnt recognize it as a device, only the red led is burning. After a few time the sony logo appears. But stil no recognizing by pc, and still not 3 vibrates after trying a hard reset...
okay, after 3 weeks of waiting im back. I had brought de Xperia S to a telecom store to fix it, but they said that it was impossible for them. Now, i tried for my self again. There are some things to explain.
1 flashing a kernel(eg. kernel.sin) is possible.
2 then, i want to flash a the system partition
3 if i do that via the command prompt by this command it says it fails
4 if i do that by the flashtool by clicking on the thunder icon, then choose the flashmode, and choose the version to load, it's unpackage some files, but then it asks to put the phone into flashmode. If i do that by pushing the volume downbutton and then connect phone with PC, the green LED is burning, but the flashtool still asks to put into flashmode. So it does not start to flash at all, because the phone is not really in flashmode.
Anyone suggestions??
You say you unlocked your phone, do you mean unlocked the bootloader? If it's stuck at boot loop this is sometimes due to locked bootloader. Try to unlock again making sure it has correctly unlocked.
If your pc cannot detect your phone in flash mode, it may be that you don't have all the drivers installed. I don't understand 2.
All in all if your phone is in flashmode but it still says put phone into flash mode im going to presume the drivers aren't installed (or installed correctly).
Here is what I have done in a similar situation.
1, Hold the vol up and vol down buttons pressed at the same with your thumb the while holding the full button pressed, press down on the power button, you are now holding power button and volume +/- at the same time, maintain this pressure for a while, you will feel 1 vibration but keep pressing until you feel 3 vibrations then take your fingers off the power and the volume.
2, Press the vol down and insert your usb that is connected to the PC. you should get a green light, if not try # 1 again 2-3 times
3,Recharge it should only take an hour or two to get decent charge.
4, Start flashtool or PC companion. flash or update.
U should avoid unlocking ur device if u r a noob..and wait for devs to develop a method that roots the device widout hving to unlock bootloader like recentlyBin4ry has developed
Sent from my LT26i using xda premium
Finally, I found the solution by installing flashtool update 9.6.0. With that installed, my phone went into flashmode and it was flashed well. A new question: i installed a rooted version of the ICS firmware. But now it is now longer possible to install updates. Is that a known issue, and is there a solution?
Hi, I tried to install a custom JB rom on my Sony Xperia U but now I'm in a reboot loop when i connect my device to the computer it connects and disconnects all the time cannot even flash please help thanks.
Are you connecting it off, then holding Vol - to trigger fastboot on USB? Don't do it when it's bootlooping.
Check the following things:
1 you have unlocked bootloader.
2 you have Xperia u fastboot and flashing drivers properly installed.
Reinstall drivers if you aren't sure whether they're properly installed or not
3 you said you're getting bootloop so your device isn't bricked..
4 take out the battery and insert again and press volume down button for flashmode and flash stock ics
5 flash boot.img from kernel zip file in FASTBOOT MODE.. If you're not sure how to do that there's a guide available in forum.. Search for it
6 then reboot to recovery, do wipes, then flash the Rom...
7 reboot twice
8 second reboot takes 10 mins don't freak out its normal
9 enjoy
AD9295 said:
Check the following things:
1 you have unlocked bootloader.
2 you have Xperia u fastboot and flashing drivers properly installed.
Reinstall drivers if you aren't sure whether they're properly installed or not
3 you said you're getting bootloop so your device isn't bricked..
4 take out the battery and insert again and press volume down button for flashmode and flash stock ics
5 flash boot.img from kernel zip file in FASTBOOT MODE.. If you're not sure how to do that there's a guide available in forum.. Search for it
6 then reboot to recovery, do wipes, then flash the Rom...
7 reboot twice
8 second reboot takes 10 mins don't freak out its normal
9 enjoy
Click to expand...
Click to collapse
Thanks!, It worked my device is working normally now .. but I can't really find a guide on how to install the boot.img can you please link me to it ? thanks.
GoldenMikez said:
Thanks!, It worked my device is working normally now .. but I can't really find a guide on how to install the boot.img can you please link me to it ? thanks.
Click to expand...
Click to collapse
the command for fastboot is
fastboot flash boot boot.img
the boot.img file must be in same folder as fastboot
there are two methods :
i recommend second method..
1. using command prompt
procedure - download adb and fastboot drivers.. extract them anywhere in pc.. copy the boot.img file to that extracted folder (i cant find the thread which contains the link for the drivers but u can definitely get it by google-ing it)
press and hold shift and right click..
select open command window here
switch off your phone
hold vol up key on ur phone and connect it to pc.. (blue led will come up)
then pass the command in command prompt as - fastboot flash boot boot.img
or
2 using flashtool
open flashtool
switch off your phone
hold vol up key on ur phone and connect it to pc.. u'll see in the flashtool that - device connected in fastboot mode
then clickon flash button and select fastboot
click on select kernel to flash and select boot.img which u extracted from kernel file..
Do these steps quickly.. fastboot mode automatically shuts down after 15-20 seconds and ur phone will start charging itself..
after flashing jb kernel reboot in recovery and then follow next steps
Enjoyy
reboot loop
im in a bootloop with a phantom kernel and i didnt place the rom in the phone storage, the telephone is rebooting again and again. i can acces to the CWM but i don't know how i can transplant the rom now :crying: thanks
First of all I would thank Crowds he is the best reference that I've to return in case of any problem I face. (He doesn't sleep - any time I ask he immediately supports)
I bought Lenovo K910 and I've managed successfully to install new ROM "VIBEUI_v2.0_1443" and Gapps with Crowds support.
I advised two of my friends to buy this good and cheap phone. For one of them I installed the latest rom successfully. But with the other I had a big problem The phone stuck on Lenovo Logo.
I was trying to install TWRP 2.7.0.0 batch before installing my new ROM, but during installation and after the phone rebooting the batch command screen shows <Waiting for Device> and the phone is stuck on logo screen.
I tried to connect the phone to PC many times, but PC doesn't recognize the phone. When I try to turn off the phone by pressing the power buttons, the phone restart on logo screen like the shown in this video.
I've read in many site that I have to do the following:
Download and install "minimal adb and fastboot"
Just type on the command line without pressing Enter:
Code:
[COLOR="Blue"][B][I]fastboot [COLOR="Plum"][STRIKE]boot[/STRIKE][/COLOR] recovery.img[/I][/B][/COLOR]
you should place your recovery image file in "minimal adb and fastboot" directory
The phone should be disconnected from computer and completely off (press the Power button for 10 seconds - in my case the phone is restarting)
Press and hold both volume buttons, then connect the cable to the PC.
Once the phone vibrate, press Enter to execute the recovery command line
Click to expand...
Click to collapse
In my case when I press and hold power button the phone is restarting on logo screen so I have to wait for battery consumption
I tried many times with TWRP images but it failed...
I tried with CWM image and it succeeded to load, but I don't have otg cable to load recovery or ROM from usb storage (The problem was in installing TWRP and my ROM should has no problem)
I want to flash TWRP on phone not only loading by "minimal adb and fastboot".
I decided to flash TWRP 2.7.1.2 batch through modifying the batch file. I just used fastboot commands
Code:
[COLOR="blue"][I]fastboot oem device-info
fastboot oem unlock
fastboot oem device-info
fastboot [COLOR="Red"][U][B]flash[/B][/U][/COLOR] recovery data/recovery.img
fastboot flash aboot data/lock/emmc_appsboot.mbn
fastboot flash rpm data/lock/rpm.mbn
fastboot flash sbl1 data/lock/sbl1.mbn
fastboot flash dbi data/lock/sdi.mbn
fastboot flash tz data/lock/tz.mbn
fastboot reboot[/I][/COLOR]
Finally I succeeded to install Recovery and phone works well in the new recovery mode and the system mode that I've not update it yet
I want to share you the problem solution in brief:
Download and extract this file "flashrec TWRP v2.7.1.2" from here
Just select without executing "flashrec_Modified.bat" file from the extracted files.
The phone should be disconnected from computer and completely off (press the Power button for 10 seconds or wait for the battery to be almost empty)
Press and hold both volume buttons, then connect the cable to the PC.
Once the phone vibrate, press Enter to execute the recovery batch file
and as me the phone start the recovery mode in TWRP and can be rebooted in system without any problem
i must extract "flashrec TWRP v2.7.1.2 this file on phone or where? can u explain a
agsao said:
First of all I would thank Crowds he is the best reference that I've to return in case of any problem I face. (He doesn't sleep - any time I ask he immediately supports)
I bought Lenovo K910 and I've managed successfully to install new ROM "VIBEUI_v2.0_1443" and Gapps with Crowds support.
I advised two of my friends to buy this good and cheap phone. For one of them I installed the latest rom successfully. But with the other I had a big problem The phone stuck on Lenovo Logo.
I was trying to install TWRP 2.7.0.0 batch before installing my new ROM, but during installation and after the phone rebooting the batch command screen shows <Waiting for Device> and the phone is stuck on logo screen.
I tried to connect the phone to PC many times, but PC doesn't recognize the phone. When I try to turn off the phone by pressing the power buttons, the phone restart on logo screen like the shown in this video.
I've read in many site that I have to do the following:
In my case when I press and hold power button the phone is restarting on logo screen so I have to wait for battery consumption
I tried many times with TWRP images but it failed...
I tried with CWM image and it succeeded to load, but I don't have otg cable to load recovery or ROM from usb storage (The problem was in installing TWRP and my ROM should has no problem)
I want to flash TWRP on phone not only loading by "minimal adb and fastboot".
I decided to flash TWRP 2.7.1.2 batch through modifying the batch file. I just used fastboot commands
Code:
[COLOR="blue"][I]fastboot oem device-info
fastboot oem unlock
fastboot oem device-info
fastboot [COLOR="Red"][U][B]flash[/B][/U][/COLOR] recovery data/recovery.img
fastboot flash aboot data/lock/emmc_appsboot.mbn
fastboot flash rpm data/lock/rpm.mbn
fastboot flash sbl1 data/lock/sbl1.mbn
fastboot flash dbi data/lock/sdi.mbn
fastboot flash tz data/lock/tz.mbn
fastboot reboot[/I][/COLOR]
Finally I succeeded to install Recovery and phone works well in the new recovery mode and the system mode that I've not update it yet
I want to share you the problem solution in brief:
Download and extract this file "flashrec TWRP v2.7.1.2" from here
Just select without executing "flashrec_Modified.bat" file from the extracted files.
The phone should be disconnected from computer and completely off (press the Power button for 10 seconds or wait for the battery to be almost empty)
Press and hold both volume buttons, then connect the cable to the PC.
Once the phone vibrate, press Enter to execute the recovery batch file
and as me the phone start the recovery mode in TWRP and can be rebooted in system without any problem
Click to expand...
Click to collapse
Please explain me. idont know how to do
prxzero said:
Please explain me. idont know how to do
Click to expand...
Click to collapse
What Is your problem?
Is your phone stuck on logo screen? what were you doing to get the problem??
agsao said:
First of all I would thank Crowds he is the best reference that I've to return in case of any problem I face. (He doesn't sleep - any time I ask he immediately supports)
I bought Lenovo K910 and I've managed successfully to install new ROM "VIBEUI_v2.0_1443" and Gapps with Crowds support.
I advised two of my friends to buy this good and cheap phone. For one of them I installed the latest rom successfully. But with the other I had a big problem The phone stuck on Lenovo Logo.
I was trying to install TWRP 2.7.0.0 batch before installing my new ROM, but during installation and after the phone rebooting the batch command screen shows <Waiting for Device> and the phone is stuck on logo screen.
I tried to connect the phone to PC many times, but PC doesn't recognize the phone. When I try to turn off the phone by pressing the power buttons, the phone restart on logo screen like the shown in this video.
I've read in many site that I have to do the following:
In my case when I press and hold power button the phone is restarting on logo screen so I have to wait for battery consumption
I tried many times with TWRP images but it failed...
I tried with CWM image and it succeeded to load, but I don't have otg cable to load recovery or ROM from usb storage (The problem was in installing TWRP and my ROM should has no problem)
I want to flash TWRP on phone not only loading by "minimal adb and fastboot".
I decided to flash TWRP 2.7.1.2 batch through modifying the batch file. I just used fastboot commands
Code:
[COLOR="blue"][I]fastboot oem device-info
fastboot oem unlock
fastboot oem device-info
fastboot [COLOR="Red"][U][B]flash[/B][/U][/COLOR] recovery data/recovery.img
fastboot flash aboot data/lock/emmc_appsboot.mbn
fastboot flash rpm data/lock/rpm.mbn
fastboot flash sbl1 data/lock/sbl1.mbn
fastboot flash dbi data/lock/sdi.mbn
fastboot flash tz data/lock/tz.mbn
fastboot reboot[/I][/COLOR]
Finally I succeeded to install Recovery and phone works well in the new recovery mode and the system mode that I've not update it yet
I want to share you the problem solution in brief:
Download and extract this file "flashrec TWRP v2.7.1.2" from here
Just select without executing "flashrec_Modified.bat" file from the extracted files.
The phone should be disconnected from computer and completely off (press the Power button for 10 seconds or wait for the battery to be almost empty)
Press and hold both volume buttons, then connect the cable to the PC.
Once the phone vibrate, press Enter to execute the recovery batch file
and as me the phone start the recovery mode in TWRP and can be rebooted in system without any problem
Click to expand...
Click to collapse
Hi..
i just try to install CM12 to this device, with twrp 2.8.6.1 from master lie.
First time its working well, but suddenly this device restarting and stuck on the "lenovo" logo screen.
Every time i presh power button always restarting (like ON-OFF-ON-OFF forever).
when i connectto charger also restarting....
i cant go to twrp using vol- & pwr, when i use minimal adb cannot detected..
Can you help me...
Help
hi.
i try to do something to enable notifications on my lenovo vibe z.
i install new rom from needrom, but it didn't help. So i try to install other one, but i wipe my phone and restart without installed system.
Now when i go to twrp have just flashing teamwin logo, and only when phone is in this mode i can communicate through adb
i have checked many forums and try allot stuff to fix it but nothing works
Please Help!
U are not alone I also in same stage
Is there any one plz help
As long as the hardware is not physically broken, your K910 is unbrickable
http://www.teamsuperluminal.org/unbrick-lenovo-k910/
I followed the guide to revive my K910. You can refer to this forum post in which I documented my experiences:
http://www.teamsuperluminal.org/forums/topic/flash-back-to-lenovo-stock-just-temporarily/
nowbo said:
Is there any one plz help
Click to expand...
Click to collapse
Thanks for your reply
I will apply today. Hope for the best.
Will inform you as soon as this applied..
Have you fixed that problem?
Still at same stage
EcoDan said:
Have you fixed that problem?
Click to expand...
Click to collapse
Hi,
I am still on same stage (Black screen with lenovo logo). Try several ways but can't get out of this. Please help me If any one successful to startup this device or can get on the boot screen where I can do factory reset.
---------- Post added at 07:25 AM ---------- Previous post was at 07:21 AM ----------
wxppro said:
http://www.teamsuperluminal.org/unbrick-lenovo-k910/
I followed the guide to revive my K910. You can refer to this forum post in which I documented my experiences:
http://www.teamsuperluminal.org/forums/topic/flash-back-to-lenovo-stock-just-temporarily/
Click to expand...
Click to collapse
I Try this method but can't get out from that black screen ( Lenovo logo and powered by android)
My device is Lenovo Vibe shot Z90a40. I also try with boot unlock-er but nothing sitll work. So its about 20 days can't use my Lenovo Vibe Shot.
Please help me If you know how to get out of this issue..
Thanks
[/COLOR]
I Try this method but can't get out from that black screen ( Lenovo logo and powered by android)
My device is Lenovo Vibe shot Z90a40. I also try with boot unlock-er but nothing sitll work. So its about 20 days can't use my Lenovo Vibe Shot.
Please help me If you know how to get out of this issue..
Thanks[/QUOTE]
You need to carefully follow each steps in the method - if you short that magic pin and then connect the USB cable (with battery disconnected), your computer will report seeing the device at either COM port 9008 or 9006. Then you can download the factory image to revive the phone. Of course you need to have the right device driver installed. Like I said, as long as the hardware is not broken, this procedure will succeed for sure.
I love you man!
I love you man! I wish you all the happiness and wealth!:victory::victory::victory::angel::angel::highfive::highfive:
Dear everyone,
I have an ASUS MeMoPad 10 (ME103K) here which I vowed to fix. The user wanted to revert to Factory Defaults, lost power or something like this, and ended up with a bricked device.
I can only start it with power button + volume up, into Fastboot. Secure Boot is enabled.
I have Android SDK and minimal FastBoot installed. Have the Google USB Drivers on my desktop.
I tried flashing SuperBoot (ADB), but ADB simply lists "Waiting for Device". No devices can be listed. It does show up in Windows Device Manager: ASUS Android Bootloader Interface.
I have the following files available:
- SuperBoot r5
- Kernel: l-8064-r1_V12.16.1.12-201508071139-foss.tar
- UL-K01E-WW-12.16.1.12-user
- recovery-original-me103k
There is apparently no recovery.img for this device. The boot.img is in the UL-K01E-WW-12.16.1.12-user file
Power = ASUS logo then goes black
Power + Volume up = Fastboot
Power + Volume down = /
Power + Volume up+down = /
Is this the place I should be looking? I'm honestly not sure if I can catch up with the details: android.stackexchange.com/questions/124344/trying-to-flash-a-system-img-i-took-with-dd-failing
Any help would be much appreciated!
- Al
EDIT:
fastboot devices now detects #serialnumber
Alright, fastboot now detects my device. I installed PDANet which didn't do anything, and then downloaded another adbfastboot package which hit it.
I'm able to start writing boot.img, but that's what it stays at. It's an 8MB file, so it shouldn't take half an hour, I suppose?
I'm not getting any error message either, though.
EDIT: It seems that regardless of what commands I send, they stall and don't get executed. ADB doesn't seem to find any devices, only Fastboot does.
EDIT 2: Tried the same on my laptop. Different ports. Nothing goes further than for example "Writing 'boot' - that's it.
Bump (won't bump until tomorrow late)
B0mp
kab0mp
boink
Bwamp
Recover Asus Me103k (k01e)
1) Stock recovery:
View attachment k01e_stock_recovery.zip
3) Run it without flash:
Code:
fastboot boot k01e_stock_recovery.img
3) In recovery select to install UL-K01E-WW-12.16.1.12-user.zip (early placed on microsd)
4) Also can check boot ability:
Extract boot.img from update firmware zip UL-K01E-WW-12.16.1.12-user
And run it from fastboot:
Code:
fastboot boot boot.img
If Android loaded normaly after it, but after reboot you see FASTBOOT MODE, than execute this commands:
Code:
fastboot oem reset-dev_info
fastboot reboot
Asus MeMo pad ME103K/K01E bootloader unlock
sheinbo said:
Hi,
after all these years I remembered my asus memo... Such a fine displsay but ... . I discovered an unofficial rom for another old device ( samsung gt 5830) and so I'd like to ask you whether you know any possibility to "upgrade" the MeMo or any other way to pitch / patch it. Your reply here let me think that you are very attached to asus memo, maybe you are still interested.
Click to expand...
Click to collapse
Same here, running the device on Lollipop is awfully slow, KitKat is somewhat better though but those are the only two official ROM's which can be found and installed.
Tried to unlock the bootloader to try different ROM's but bootloader is locked, despite all info here on XDA, nothing seems to work and the bootloader remains locked. Unlock APK's also give no result.
Running out of options here, any suggestions will be appreciated.
Hey, I have an Archos Helium 45 that I put a custom ROM on a while ago, but today decided to revert to the stock ROM because it was having some issues. I must have done something wrong though, and softbricked my phone. Now this would be no problem if only I could enter recovery mode, however when I boot up my phone holding down the +volume and power button, all I get is a green screen, which is the fastboot mode. On this screen there is nothing I can select (just seems to be some tiny tiny white, unreadable text on the top). I'm guessing this is because I installed TWRP over the regular recovery.
When I first installed the custom ROM, I did something wrong and softbricked my phone too, and had the same problem of not being able to select anything on the green screen, but then I was able to use the command 'adb reboot recovery' via the PC to boot into recovery mode. However, now this does not work anymore, and when using 'adb devices', it returns an empty list. I still do get a code when using 'fastboot devices' though.
Does anyone have any solution to boot into recovery mode from the fastboot mode?
I read somewhere that I could try flashing the img files from the original ROM via fastboot one by one, however the only img file in ROM's zip file is boot.img.
I also tried updating the ROM using 'fastboot update update.zip' but then it says
Code:
archive does not contain 'android-info.txt'
error: update package 'update.zip' has no android-info.txt
Edit: Never mind, right after creating this thread I found out I could enter recovery mode simply by continuing to hold the +volume button and releasing the power button after the green screen... (and I also plugged it into my computer right when TWRP started, don't know if this was a requirement or coincidence) **** I spent all day looking for a fix and ended up finding it just by trying something.
I'm having issues with the stock ROM though, but at least I can install an other custom ROM and have a working phone.