Hi all,
I have a 6045i variant of the idol3. I have successfully unlocked the bootloader and have been trying now to flash TWRP. Then I will install a custom ROM and SU to hopefully end the lagfest.
However, no matter which TWRP I try (2.8.7.0 or 3.0.0-1) it isn't sticking. I've followed the appropriate threads here using adb fastboot to flash the recoveries but when I try to get to recovery it goes to the stock version.
I'm running the latest stock firmware: 5.0.2-7SRN-UEN0
Here's the output of the adb session.
Code:
C:\adb>fastboot -i 0x1bbb devices
cc22eea2 fastboot
C:\adb>fastboot -i 0x1bbb oem device-info
...
(bootloader) Device tampered: false
(bootloader) Device unlocked: true
(bootloader) Charger screen enabled: false
(bootloader) Display panel:
(bootloader) Boot cpus: androidboot.earlyboot_cpus=3,4,5,6,7
(bootloader) Big core max freq:
(bootloader) Small core max freq:
OKAY [ 0.028s]
finished. total time: 0.029s
C:\adb>fastboot -i 0x1bbb flash recovery twrp-3.0.0-1-idol3.img
target reported max download size of 268435456 bytes
sending 'recovery' (23880 KB)...
OKAY [ 0.803s]
writing 'recovery'...
OKAY [ 2.207s]
finished. total time: 3.014s
C:\adb>fastboot -i 0x1bbb reboot
rebooting...
finished. total time: 0.003s
When I invoke recovery (either thru adb or power on/volume up) it loads into stock 3e recovery.
Any tips to get past this? I've done a fair amount of searching for similar issues here but haven't ran into any help.
thanks,
try this:
if youflash the TWRP recovery then turn off the phone and right go to recovery (volume up+power).
If you can go t oTWRP recovery and after reboot yo uwill get the stock one again, then there is a stratup script which replaces the custom recovery with the stock one, on every startup.
You have then to flash the twrp recovry, right boot into it and using the file manager inside TWRP to find the script and delete it.
mikehd1959 said:
Hi all,
I have a 6045i variant of the idol3. I have successfully unlocked the bootloader and have been trying now to flash TWRP. Then I will install a custom ROM and SU to hopefully end the lagfest.
However, no matter which TWRP I try (2.8.7.0 or 3.0.0-1) it isn't sticking. I've followed the appropriate threads here using adb fastboot to flash the recoveries but when I try to get to recovery it goes to the stock version.
I'm running the latest stock firmware: 5.0.2-7SRN-UEN0
Here's the output of the adb session.
Code:
C:\adb>fastboot -i 0x1bbb devices
cc22eea2 fastboot
C:\adb>fastboot -i 0x1bbb oem device-info
...
(bootloader) Device tampered: false
(bootloader) Device unlocked: true
(bootloader) Charger screen enabled: false
(bootloader) Display panel:
(bootloader) Boot cpus: androidboot.earlyboot_cpus=3,4,5,6,7
(bootloader) Big core max freq:
(bootloader) Small core max freq:
OKAY [ 0.028s]
finished. total time: 0.029s
C:\adb>fastboot -i 0x1bbb flash recovery twrp-3.0.0-1-idol3.img
target reported max download size of 268435456 bytes
sending 'recovery' (23880 KB)...
OKAY [ 0.803s]
writing 'recovery'...
OKAY [ 2.207s]
finished. total time: 3.014s
C:\adb>fastboot -i 0x1bbb reboot
rebooting...
finished. total time: 0.003s
When I invoke recovery (either thru adb or power on/volume up) it loads into stock 3e recovery.
Any tips to get past this? I've done a fair amount of searching for similar issues here but haven't ran into any help.
thanks,
Click to expand...
Click to collapse
You can just try like this
Connect to Pc with usb
Open Adb And Fastboot
Enable Debugging on Device
type "adb reboot bootloader"
Then write"fastboot -i 0x1bbb flash recovery twrp-3.0.0-1-idol3.img"
and then"fastboot -i 0x1bbb boot twrp-3.0.0-1.img"-wait 2s and Automaticily Device will boot to TWRP recovery so you can flash what do you want
Alek Dev said:
You can just try like this
Connect to Pc with usb
Open Adb And Fastboot
Enable Debugging on Device
type "adb reboot bootloader"
Then write"fastboot -i 0x1bbb flash recovery twrp-3.0.0-1-idol3.img"
and then"fastboot -i 0x1bbb boot twrp-3.0.0-1.img"-wait 2s and Automaticily Device will boot to TWRP recovery so you can flash what do you want
Click to expand...
Click to collapse
Thanks. That's what I just stumbled into as well. I've gotten into TWRP and was able to reboot in TWRP back into TWRP recovery. So now I'm trying reboot to system from TWRP. I'll then reboot to recovery to see if TWRP has stuck.
While in TWRP I used the terminal to find the init scripts. Here's the list:
Code:
init
init.qcom.usb.sh
init.rc
init.recovery.qcom.rc
init.recovery.qcom.usb.rc
When I executed a ls -lh to see timestamps, they were all some default 1969 year. So I didn't muck with anything with init.
Just completed my first boot into the OS. I shut it down fully then restarted with power on + Vol Up and it went straight to TWRP.
So the trick was to do the flash recovery then boot the image as you suggested.
Is this typical for this device? I've never encountered this on other phones (S3 for example).
mikehd1959 said:
Thanks. That's what I just stumbled into as well. I've gotten into TWRP and was able to reboot in TWRP back into TWRP recovery. So now I'm trying reboot to system from TWRP. I'll then reboot to recovery to see if TWRP has stuck.
While in TWRP I used the terminal to find the init scripts. Here's the list:
Code:
init
init.qcom.usb.sh
init.rc
init.recovery.qcom.rc
init.recovery.qcom.usb.rc
When I executed a ls -lh to see timestamps, they were all some default 1969 year. So I didn't muck with anything with init.
Just completed my first boot into the OS. I shut it down fully then restarted with power on + Vol Up and it went straight to TWRP.
So the trick was to do the flash recovery then boot the image as you suggested.
Is this typical for this device? I've never encountered this on other phones (S3 for example).
Click to expand...
Click to collapse
so the trick was been to flash the TWRP recovery and then aumotacilly go to Recovery...and if you want to restart phone...just reboot it .you no need to flash boot
Alek Dev said:
so the trick was been to flash the TWRP recovery and then aumotacilly go to Recovery...and if you want to restart phone...just reboot it .you no need to flash boot
Click to expand...
Click to collapse
Except that didn't work for me. It would consistently go to stock recovery no matter how I tried to exit adb. If I rebooted to recovery in adb the stock recovery would launch. If I plain rebooted to OS and then shut down and restart (power on + Vol Up) it would go to stock recovery. It was only when I did the commands as listed above would it at last go to TWRP and persist across reboots.
mikehd1959 said:
Except that didn't work for me. It would consistently go to stock recovery no matter how I tried to exit adb. If I rebooted to recovery in adb the stock recovery would launch. If I plain rebooted to OS and then shut down and restart (power on + Vol Up) it would go to stock recovery. It was only when I did the commands as listed above would it at last go to TWRP and persist across reboots.
Click to expand...
Click to collapse
So use the commands to go to Twrp..you can try to lock the bootloader and try again to unlock and then flash Twrp..
Edit:So it can be the problem with the system
Alek Dev said:
So use the commands to go to Twrp..you can try to lock the bootloader and try again to unlock and then flash Twrp..
Edit:So it can be the problem with the system
Click to expand...
Click to collapse
No need to do as you describe. It is now working correctly. When I go to recovery, it launches TWRP as expected. Issue closed.
Okay, so all day, I've been trying to fix this damn phone because of a root fail. I unlocked the bootloader, installed SuperSU and now the phone just reboots with a white screen and red words saying this build is for development purposdes only. I can get to download and bootloader mode fine though. Its S-On Bootloader Unlocked. I would honestly settle for it to be set to factory settings as I just need the phone fixed. Rooting has been so stressful. I don't care about losing data.
I'm thinking it failed because I used an SDHC 32GB Micro SD Card? Ive been trying to use a recovery img, Im using HTC Android Phone ROM Update Utility and thats not working. It asks to update the ROm version from 3.35.401.12 to image version (shows nothing). Then it says image error 158 (cannot update my android phone).
When flashing a recovery image, I get:
C:\Users\shaif\Downloads\Root M9>fastboot flash recovery recovery.img
target reported max download size of 800000000 bytes
sending 'recovery' (32848 KB)...
OKAY [ 2.503s]
writing 'recovery'...
(bootloader) HOSD CL#671758
(bootloader) [email protected]
(bootloader) [email protected]%
(bootloader) Update partition OK
(bootloader) [email protected]
OKAY [ 2.792s]
finished. total time: 5.301s
Still not working.
Also tried fastboot oem rebootRUU but that took me to a screen that says Security Warning
Someone please help me, Im desperate
Hi !
I see that you have fixed your issue https://forum.xda-developers.com/showpost.php?p=71188370&postcount=1372 so I close this down
Cheers !
Hi I hope someone can help me with this problem, I have rooted my Moto g2 XT1068 and installed TWRP however there were issues with SD card access, so I planned to install Lineage OS but somewhere along the line I must have messed up because the phone will no longer boot up.
I can still force the phone into fastboot screen with power + down buttons and connect to my Windows PC with “Minimal ADB and Fastboot” but running the command fastboot flash recovery TWRP.img returns
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash recovery TWRP.img
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:recovery: not found
target reported max download size of 536870912 bytes
sending 'recovery' (4598 KB)...
OKAY [ 0.188s]
writing 'recovery'...
OKAY [ 0.311s]
finished. total time: 0.505s
But on trying to reboot it seems to get stuck in the screen which says "Warning, bootloader unlocked", which is normal since unlocking, but the problem is that it gets no further than this even if I leave it on overnight.
Any help would be much appreciated.
Progress!
Hold the front page, I have found the stock firmware here https://forum.xda-developers.com/moto-g-2014/general/official-stock-firmware-t3018682 and am restoring back to stock.
The question is... am I brave enough to attempt to install the Lineage OS???
Hello
I am trying to put TWRP on my U12+ since 3 day and i am realy desperate.
I try 6 times Magisk to root but it broke my boot and then i had a loop boot of just a black screen.
I used the original boot_signed.img, patched it, flash and broke the phone..
I try to put the back the original... it dont boot
I put again the RUU a 7th time, my phone boot now.
I tryed to flash the recovery from Download Mode but i have this error:
Code:
D:\adb>fastboot flash recovery twrp.img
target reported max download size of 1082400000 bytes
sending 'recovery' (31016 KB)...
OKAY [ 2.172s]
writing 'recovery'...
(bootloader) HOSD CL#1041457
(bootloader) [email protected]
(bootloader) ERR flash_partition_by_file, partition recovery is not foun
(bootloader) [email protected]
(bootloader) [email protected]
FAILED (remote: 23 RU_READ_PARTITION_FAIL read/open partition fail )
finished. total time: 4.344s
I try to boot on TWRP with fastboot but:
Code:
fastboot boot twrp.img
downloading 'boot.img'...
OKAY [ 2.028s]
booting...
And the phone dont do anything.
I realy dont know what to do if someone have any idea ?
Thanks a lot and sorry for my bad english. I try my best.
EDIT 1:
the phone have to be in BOOTLOADER MODE to use fastboot boot xxx.img
Then i flash the twrp install ZIP and it worked. BUT......
EDIT 2:
After 2 reboot it freeze with the white HTC logo... PLEASE HELP
You didn't read the thread that covers why you can't do the old fastboot flash command.
Go to the ROMS section and read the TWRP thread. It tells you how to insert TWRP into the ramdisk.
---------- Post added at 08:53 PM ---------- Previous post was at 08:04 PM ----------
https://forum.xda-developers.com/u12-plus/development/recovery-unofficial-twrp-3-2-2-0-htc-t3819343
Please help!!
I have messed up my oneplus one bacon
I was using lineageos 16 and all was fine. For some dumb reason like getting 'Screen mirroring' feature, I decided to go back to lineageos 15.1. Somewhere in the instructions I [mis]read, a clean wipe is recommended to go back to previous release.
I wiped all my partitions from twrp. That's why, my system partition is gone.
I tried a bunch of things after searching on these forums for similar symptoms, but no luck as of yet.
I tried to flash the stock recovery and stock ROM
Recovery flash was successful and so I am on CWM, but the ROM failed as the system partition could not be mounted/unmounted
Now, my phone's state -- I have Cyanogen recovery
ADB devices does not work.
> adb reboot bootloader
adb server is out of date. killing...
* daemon started successfully *
error: device not found
Fastboot works, but am unable to unlock my bootloader, not sure how it got locked.
>fastboot oem unlock
OKAY [ 0.009s]
Finished. Total time: 0.019s
It simple reboots to the recovery without unlocking
>fastboot oem device-info
(bootloader) Device tampered: true
(bootloader) Device unlocked: false
(bootloader) Charger screen enabled: false
(bootloader) Display panel:
(bootloader) console_enabled: 0
(bootloader) exec_console_unconsole: 0
OKAY [ 0.021s]
Finished. Total time: 0.028s
I tried sideload to upload files like stock ROM, I get verification errors.
I was hoping this thread would help me. But not sure how to apply this fix
I am unable to flash or boot as I get the following error
> fastboot flash recovery recovery.img
target reported max download size of 1073741824 bytes
sending 'recovery' (9968 KB)...
OKAY [ 0.317s]
writing 'recovery'...
FAILED (remote: Device not unlocked cannot flash or erase)
>fastboot boot recovery.img
downloading 'boot.img'...
OKAY [ 0.318s]
booting...
FAILED (remote: Device not unlocked cannot boot)
finished. total time: 0.339s
Please help!!!