Related
Hi, Iam newone here. So i need your help. I have HTC One SV where it's bricked the only info where i have is :
*** TAMPERED ***
*** UNLOCKED ***
K2_UL PVT SHIP S-ON RL
HBOOT-2.21.0000
RADIO-1.18.40a.00.05
OpenDSP-v13.2.0268.0620
OS-311.401.1
eMMC-boot 1024MB
So i tried to restore,nothing happen. fastory reset nothing happen.
I tried to install latest TWRP but it stuck ot logo of TWRP and after 5min it reboots.
I tried to turn s-on to s-off but adb can not find my device.
i tried to the latest ruu nothing again.
i tries to install rom from fastboot but i says that it can not verify signature.
I tried too remove the trampered but again adb can not see my device
HELP PLEASE.....
p.s.: sorry for my english i'm not good.....
If you using win8 try 7 cuz 8 is kind of creepy in recognizing new devices. And make sure you got the right ruu.
I'm sure @Modding.MyMind can help more.
georgekap said:
Hi, Iam newone here. So i need your help. I have HTC One SV where it's bricked the only info where i have is :
*** TAMPERED ***
*** UNLOCKED ***
K2_UL PVT SHIP S-ON RL
HBOOT-2.21.0000
RADIO-1.18.40a.00.05
OpenDSP-v13.2.0268.0620
OS-311.401.1
eMMC-boot 1024MB
So i tried to restore,nothing happen. fastory reset nothing happen.
I tried to install latest TWRP but it stuck ot logo of TWRP and after 5min it reboots.
I tried to turn s-on to s-off but adb can not find my device.
i tried to the latest ruu nothing again.
i tries to install rom from fastboot but i says that it can not verify signature.
I tried too remove the trampered but again adb can not see my device
HELP PLEASE.....
p.s.: sorry for my english i'm not good.....
Click to expand...
Click to collapse
Ok, you had already 4.2.2 on it, thats good, no firmwareupgrade needed!
- Make sure bootloader is unlocked.
- Download and flash (with fastboot) TWRP 2.7.0.1 recovery from here (1. post)
Now you should be able to boot into recovery!
You have two ways you can go now:
- Either download this rom (k2ul version) and flash from TWRP. Don't forget, boot.img must be flashed with fastboot, because you are S-on!
- Or download this stock TWRP backup, place it on your external sd and restore it from recovery.
The location on ext_sdcard for the backup is: \TWRP\BACKUPS\"Put here the serial number of your device"
Sorry, just now reading this. Currently having battery issues with my device. May be finally taking a crap on me and since this is my only one I may be forced to get a new device thus possibly leaving this community.... Still playing with my phone to determine if it will be neceassary or not.
Sent from my C525c using Tapatalk
J.ali.li said:
If you using win8 try 7 cuz 8 is kind of creepy in recognizing new devices. And make sure you got the right ruu.
I'm sure @Modding.MyMind can help more.
Click to expand...
Click to collapse
I'm using win ultimate 7 x64
old.splatterhand said:
Ok, you had already 4.2.2 on it, thats good, no firmwareupgrade needed!
- Make sure bootloader is unlocked.
- Download and flash (with fastboot) TWRP 2.7.0.1 recovery from here (1. post)
Now you should be able to boot into recovery!
You have two ways you can go now:
- Either download this rom (k2ul version) and flash from TWRP. Don't forget, boot.img must be flashed with fastboot, because you are S-on!
- Or download this stock TWRP backup, place it on your external sd and restore it from recovery.
The location on ext_sdcard for the backup is: \TWRP\BACKUPS\"Put here the serial number of your device"
Click to expand...
Click to collapse
I tried to flash twrp but it stuck on htc and at the top it is writes entering recovery...
i tried an other one twrp 2.7.0.1 but it stucks on teamwin and after few min it reboot back to htc logo.
Have you also tried the older version Recovery_TWRP_2.6.3.2_K2_UL.img from same post?
How do you flash it?
old.splatterhand said:
Have you also tried the older version Recovery_TWRP_2.6.3.2_K2_UL.img from same post?
How do you flash it?
Click to expand...
Click to collapse
from fastboot with this command fastboot flash recovery reovery.img
i tried and the older version but it stuck on htc logo with on the top writes entering recovery
georgekap said:
from fastboot with this command fastboot flash recovery reovery.img
i tried and the older version but it stuck on htc logo with on the top writes entering recovery
Click to expand...
Click to collapse
from fastboot with this command fastboot flash recovery recovery.img *
i tried to flash the rom k2ul_4.2.2_3.11.401.1_stock_odexed_v3.zip from the phone.
i rename it pl80img.zip. and now is stuck on htc logo and reboots
Then i think your phone has another issue. Both recoveries are proved working for k2u & k2ul.
This rom is for flashing in recovery, not for the bootloader.
old.splatterhand said:
Then i think your phone has another issue. Both recoveries are proved working for k2u & k2ul.
This rom is for flashing in recovery, not for the bootloader.
Click to expand...
Click to collapse
when i flash recovery from fastboot. whene im try to get in recovery mode after how many min its boot to recovery?
No minutes, just a few seconds.
old.splatterhand said:
No minutes, just a few seconds.
Click to expand...
Click to collapse
How can i downgrade os???
Not possible without a working OS.
@ old.splatterhand
I have same problem k2_ul. phone just restart after 10 sec
i try hard reset, enter recovery with TWRP but nothing happened .
what should i do at now?
More detailed please.
The phone restarts after booting?
After you have entered the pin number?
Also without simcard/sdcard/plugged into charger (while charging)?
Which OS you are running?
Which TWRP?
Connect your phone with fastboot and type into the cmd:
Code:
fastboot getvar all
Put the output here (except your IMEI & Serial number)
This is fastboot info.
phone not getting to booting.just htc logo 10 sec then again restart phone continue.
C:\adb>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 2.21.0000
(bootloader) version-baseband: 1.18.40a.00.05
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.11.415.10
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: HT313Txxxx
(bootloader) imei: 3528xxxxxxxxx
(bootloader) meid:
(bootloader) product: k2_ul
(bootloader) platform: HBOOT-8930
(bootloader) modelid: PL8010000
(bootloader) cidnum: HTC__J15
(bootloader) battery-status: good
(bootloader) battery-voltage: 3655mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-2bb255c2
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.063s
Please remove also your serial number.
You are able to enter recovery or not?
Post the link, where you've got the recovery from?
no i cant recovery mode.
i try many recovery.img but when i enter recovery its just give me "entering recovery" logo!!
Use this recovery.
Hey there XDA, I have a strange problem. Maybe you can help me out.
I just got my Moto G today and after unlocking the bootloader, the first thing I did was flash TWRP (fastboot flash recovery TWRP-2.7.0.0-falcon.img).
I did this with the normal fastboot from the Android SDK, not the Motorola version.
Now everytime I start the device, it always boots right into recovery. Always. Doesn't matter if there's TWRP, CWM or Stock installed.
I also flashed the device to GPE afterwards (using the Motorola fastboot) which should've erased everything, but it still does it.
The only way I can get into the actual system is by flashing the normal boot.img as recovery (fastboot flash recovery boot.img).
Can someone please shed some light on this for me? I'd be eternally grateful.
Thanks in advance.
Kenny
twofive said:
Hey there XDA, I have a strange problem. Maybe you can help me out.
I just got my Moto G today and after unlocking the bootloader, the first thing I did was flash TWRP (fastboot flash recovery TWRP-2.7.0.0-falcon.img).
I did this with the normal fastboot from the Android SDK, not the Motorola version.
Now everytime I start the device, it always boots right into recovery. Always. Doesn't matter if there's TWRP, CWM or Stock installed.
I also flashed the device to GPE afterwards (using the Motorola fastboot) which should've erased everything, but it still does it.
The only way I can get into the actual system is by flashing the normal boot.img as recovery (fastboot flash recovery boot.img).
Can someone please shed some light on this for me? I'd be eternally grateful.
Thanks in advance.
Kenny
Click to expand...
Click to collapse
on the custom recovery menu screen, when you press REBOOT then REBOOT SYSTEM, does it? Or does it just reboot back into recovery?
3RAN7ON said:
on the custom recovery menu screen, when you press REBOOT then REBOOT SYSTEM, does it? Or does it just reboot back into recovery?
Click to expand...
Click to collapse
It boots right back into Recovery. It always does that, no matter if I do it from the OS, the bootloader, whatever.
Have you tried flashing through fastboot the update for your device ?
twofive said:
Hey there XDA, I have a strange problem. Maybe you can help me out.
I just got my Moto G today and after unlocking the bootloader, the first thing I did was flash TWRP (fastboot flash recovery TWRP-2.7.0.0-falcon.img).
I did this with the normal fastboot from the Android SDK, not the Motorola version.
Now everytime I start the device, it always boots right into recovery. Always. Doesn't matter if there's TWRP, CWM or Stock installed.
I also flashed the device to GPE afterwards (using the Motorola fastboot) which should've erased everything, but it still does it.
The only way I can get into the actual system is by flashing the normal boot.img as recovery (fastboot flash recovery boot.img).
Can someone please shed some light on this for me? I'd be eternally grateful.
Thanks in advance.
Kenny
Click to expand...
Click to collapse
You could try re flashing the stock firmware. http://forum.xda-developers.com/showthread.php?t=2542219 Good luck, it will delete everything on the phone.
Sent from my Moto G using XDA Free mobile app
twofive said:
It boots right back into Recovery. It always does that, no matter if I do it from the OS, the bootloader, whatever.
Click to expand...
Click to collapse
hmmm....something similar happened to me about 2 days ago when I DL the ota, then tried to install it, but it failed. the phone rebooted into the system and a minute later it roobooted itsself back into recovery and tried to install the update again. Of course, the ota's are DL to the /cache folder by default, but once install is attempted, it erases it from that folder, but phone kept rebooting and trying to install, it failed then rebooted again into recovery. It did this like 5x until I was able to stop this by restoring a prev backup. Not sure if this is your situation, but in posting this experience it might help someone
---------- Post added at 09:53 AM ---------- Previous post was at 09:44 AM ----------
Also, check in your recovery if there is something called 'DISABLE RECOVERY FLASH' and make sure it is checked before rebooting the first time after installing recovery. I maybe mistaking, but I thought it was a bug only found on some earlier CWM builds, not found on TWRP...but recovery flash would make the phone do what you are describing
twofive said:
Hey there XDA, I have a strange problem. Maybe you can help me out.
I just got my Moto G today and after unlocking the bootloader, the first thing I did was flash TWRP (fastboot flash recovery TWRP-2.7.0.0-falcon.img).
I did this with the normal fastboot from the Android SDK, not the Motorola version.
Now everytime I start the device, it always boots right into recovery. Always. Doesn't matter if there's TWRP, CWM or Stock installed.
I also flashed the device to GPE afterwards (using the Motorola fastboot) which should've erased everything, but it still does it.
The only way I can get into the actual system is by flashing the normal boot.img as recovery (fastboot flash recovery boot.img).
Can someone please shed some light on this for me? I'd be eternally grateful.
Thanks in advance.
Kenny
Click to expand...
Click to collapse
You shouldn't have that issue, but you might have to try the latest 2.6.x branch of TWRP. I've seen both but never know which one is really better.
Also, why use the GPE edition? The moto stuff in the moto g is better than the google equivalents, especially the camera app and moto assist, but to each his own.
sprockkets said:
Also, why use the GPE edition? The moto stuff in the moto g is better than the google equivalents, especially the camera app and moto assist, but to each his own.
Click to expand...
Click to collapse
I also own a Nexus 5, Xperia Z Ultra flashed to GPE, and a Nexus 7. I just like having the same Software on all of them.
Hey try this.
twofive said:
I also own a Nexus 5, Xperia Z Ultra flashed to GPE, and a Nexus 7. I just like having the same Software on all of them.
Click to expand...
Click to collapse
https://docs.google.com/file/d/0Bx3fLPcfAf3BcmRmdENLWHhPaDQ/edit?pli=1
http://forum.xda-developers.com/showthread.php?t=2746401
Booting to recovery (twrp&cmw) when rebooting to system
twofive said:
hey there xda, i have a strange problem. Maybe you can help me out.
I just got my moto g today and after unlocking the bootloader, the first thing i did was flash twrp (fastboot flash recovery twrp-2.7.0.0-falcon.img).
I did this with the normal fastboot from the android sdk, not the motorola version.
Now everytime i start the device, it always boots right into recovery. Always. Doesn't matter if there's twrp, cwm or stock installed.
I also flashed the device to gpe afterwards (using the motorola fastboot) which should've erased everything, but it still does it.
The only way i can get into the actual system is by flashing the normal boot.img as recovery (fastboot flash recovery boot.img).
Can someone please shed some light on this for me? I'd be eternally grateful.
Thanks in advance.
Kenny
Click to expand...
Click to collapse
dear all,
pls help me.. I'm facing the same problem when i'm rebooting system from my recovery screen and it's rebooting to recovery . I cannot find any relevant solution for this anywhere. So please help me. I'm using moto g falcon (xt1033)
princehpd said:
dear all,
pls help me.. I'm facing the same problem when i'm rebooting system from my recovery screen and it's rebooting to recovery . I cannot find any relevant solution for this anywhere. So please help me. I'm using moto g falcon (xt1033)
Click to expand...
Click to collapse
Which version you were before that i mean lollipop or marshmallow and stock or custom roms?
Cyanogenmod 13
abhi0502 said:
Which version you were before that i mean lollipop or marshmallow and stock or custom roms?
Click to expand...
Click to collapse
BEFORE ROOTING I WAS ON ANDROID LOLLIPOP AND AFTER THAT I FLASHED CYANOGENMOD 13. RECENT ONE WAS CrDROID BASED ON ANDROID MARSHMALLOW. PLS HELP..
Ok I now have this problem also
Even flashing stock rom does not fix it.
Does anyone have any suggestions ??
The phone will say boot loader unlocked as usu then black screen then flashes stock recovery no command screen , then the device turns off. I can access boot loader mode !
That's about all I have :/
Any help would be greatly appreciated
I have the same problem, or similar. I installed CM13 but it didn't like me so much and when I wanted to reboot the phone to restore my previous backup I went to "Advanced reboot menu" and then just reboot recovery. And the phone never could boot again to system, I tried flashing 5.1 and various recoveries but nothing happended.
As nobody responses my trhead I was obliged to send my Moto G to an unofficial customer service, I have to go today to take up my phone, it should be ready, I hope.
Good luck, if they told me how they fixed it I'll post here.
Ok I think I may have found the fix. Flash all of the stock files normally , then flash boot.img once more. Then the phone will boot normally but only for one time. Quickly run though setup , then in the setting app factory reset your device. Your device will reboot and reset once more. Then the device will always boot normal This actually seems to work. I spent all night yesterday trying to fix my device and I finally found the solution. ! ��
therealduff1 said:
Ok I think I may have found the fix. Flash all of the stock files normally , then flash boot.img once more. Then the phone will boot normally but only for one time. Quickly run though setup , then in the setting app factory reset your device. Your device will reboot and reset once more. Then the device will always boot normal This actually seems to work. I spent all night yesterday trying to fix my device and I finally found the solution. ! ��
Click to expand...
Click to collapse
Man, I did that but it didn't work for me. Now when I reboot from fastboot the device power up directly to fastboot mode and on the log it shows
Fastboot reason: UTAG "bootmode" configured as fastboot
Anyway if I powerup from fastboot mode the phone sucks on the bootloader screen.
I had the same problem and was searching from this noon. Just now, i downloaded and flashed with Cyanogen Recovery "cm-12.1-20151117-SNAPSHOT-YOG7DAO1K9-falcon-recovery" and my problem is over now. Tried a couple of power off and restarts and now my reboots and power on will not go to recovery any more.
File is available to download at cyanogenmod website
Please make sure about your model before download. I use a Moto G 2013 XT1033 Asia Retail edition with 8GB.
I tried installing that recovery but I'm getting the exact same issue...
Any other solution? No one has solved it yet?
I got the same problem here.. My Moto G default boot is to recovery. The way i could enter the rom is with Bootloader option "Normal powerup". I already try many ways, reflash custom recovery (TWRP, CWM, CM), reflash stock, and reflash custom rom, but they do nothing to this case. Is there any way to change it back to normal? I'm currently on CM 12.1 Unofficial and running TWRP 2.8.6.0. It is not panic attack, it just anoying. Thanks in advance..
same here.. booting always into recovery by default..
tried different twrp versions (incl. 2.8.7), CWM and cyanogen recovery.. and also tried wiping the complete system.. reinstalling stock rom incl. bootloader, recovery, etc..
everytime the same boot into recovery by default
using "fastboot reboot" in bootloader mode also boots into recovery
in bootloadermode i'm able to boot my fresh installed CM12.1 by selecting "Normal Powerup"
maybe something happened with the bootloader configuration? where to edit it?
this also did not help:
mfastboot oem fb_mode_clear
Click to expand...
Click to collapse
(as i understand.. this just clears the fb_mode_set value.. which directs to bootloader on boot
edit:
# fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 411A
(bootloader) product: falcon
(bootloader) secure: yes
(bootloader) hwrev: 0x83C0
(bootloader) radio: 0x1
(bootloader) emmc: 16GB Toshiba REV=06 PRV=01 TYPE=17
(bootloader) ram: 1024MB Samsung S4 SDRAM DIE=4Gb
(bootloader) cpu: MSM8226 CS
(bootloader) serialno: xxxxxxxxxxxx
(bootloader) cid: 0x0007
(bootloader) channelid: 0x00
(bootloader) uid: 66FFC4020F000000000000000000
(bootloader) unlocked: yes
(bootloader) iswarrantyvoid: yes
(bootloader) mot_sst: 3
(bootloader) max-download-size: 536870912
(bootloader) reason: Reboot mode set to fastboot
(bootloader) imei:
(bootloader) meid:
(bootloader) date:
(bootloader) sku:
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time: "Wed Aug 19 2:19:55 UTC 2015"
(bootloader) ro.build.fingerprint[0]: motorola/falcon_retde/falcon_umts:
(bootloader) ro.build.fingerprint[1]: 5.1/LPB23.13-56/56:user/release-ke
(bootloader) ro.build.fingerprint[2]: ys
(bootloader) ro.build.version.full[0]: Blur_Version.221.21.56.falcon_umt
(bootloader) ro.build.version.full[1]: s.Retail.en.DE
(bootloader) ro.build.version.qcom[0]: AU_LINUX_ANDROID_LNX.LA.3.5.1_RB1
(bootloader) ro.build.version.qcom[1]: .04.04.02.048.045
(bootloader) version-baseband:
(bootloader) kernel.version[0]: Linux version 3.4.42-g89906d6 ([email protected]
(bootloader) kernel.version[1]: ilclbld34) (gcc version 4.8 (GCC) ) #1 S
(bootloader) kernel.version[2]: MP PREEMPT Mon Aug 17 19:06:25 CDT 2015
(bootloader) sdi.git: git=MBM-NG-V41.1A-0-gdc5aeaf
(bootloader) sbl1.git: git=MBM-NG-V41.1A-0-g199f3c5
(bootloader) rpm.git: git=MBM-NG-V41.1A-0-g8b7736e
(bootloader) tz.git: git=MBM-NG-V41.1A-0-g99c1a7c
(bootloader) aboot.git: git=MBM-NG-V41.1A-0-g80481ae
(bootloader) qe: qe 2/1
(bootloader) ro.carrier: unknown
all: listed above
finished. total time: 0.057s
Click to expand...
Click to collapse
Hi guys I' ve a problem with my oneplus one. I've the 38r version of cyanogenmod on my opo and I want to flash another ROM on my device.
The problem is that 1 week ago I ve unlocked bootloader and rooted it, but unfortunately with an app I've deleted root and relocked boot loader on my device (I'm a disaster I Know). Now I can' t reboot it into recovery, to reset my 1+1, because It's disappeared and it's stuck on 1+1 logo
In fastboot when I type in oem device-info I got this message:
(bootloader) Device tampered: true
(bootloader) Device unlocked: false
(bootloader) Charger screen enabled: false.
I've tried to relock 1+1 from fastboot but the device is stucked on 1+1 logo and I can only reboot with fastboot reboot. I can use it normally but I'd like to restore it.
Someone can helps me?? Thanks in advance.
I dont understand why It wont boot into the twrp img.
I have tried a few times now after i have deleted the content of the phone twice, and it still wont work..
I do have an unlocked bootloader, and I have followed different guides tried to read up on it myself, but ive tried all day, i dont know what is wrong.
Everytime i try to do "fastboot boot twrp.img" it wont work, it says okay, booting..., okay, finished. then my phone starts going into fastbootmode, but is then just stuck on the black screen with the 1+ logo with the text under it saying fastboot mode.
Im running android 10
The files i use is :
twrp-3.3.1-2-enchilada.img
twrp-installer-3.3.0-0-enchilada.zip (never gotten to this stage)
Magisk-v20.3.zip
I hope some1 is able to help me out thanks for reading
use newest twrp file image
mcboums said:
use newest twrp file image
Click to expand...
Click to collapse
I also did that, same result
Same issue here, had to settle for a magisk patched boot image
0x0null said:
Same issue here, had to settle for a magisk patched boot image
Click to expand...
Click to collapse
Same issue here....twrp-3.3.1-2-enchilada.img is last image
use this twrp
hello i just stuck at that problem too my phone stuck at fastboot mode similar to boot loop i find the solution by following this post https://forum.xda-developers.com/oneplus-6/how-to/how-to-flash-twrp-magisk-android-10-t3988213
Trevasta said:
hello i just stuck at that problem too my phone stuck at fastboot mode similar to boot loop i find the solution by following this post https://forum.xda-developers.com/oneplus-6/how-to/how-to-flash-twrp-magisk-android-10-t3988213
Click to expand...
Click to collapse
Tried all that too, same issue
Ive used 'fastboot flash boot twrp.img' in the past to get into twrp then flash stock boot.img in twrp to restore boot, then flashing twrp.zip in twrp.
gffmac said:
Ive used 'fastboot flash boot twrp.img' in the past to get into twrp then flash stock boot.img in twrp to restore boot, then flashing twrp.zip in twrp.
Click to expand...
Click to collapse
I'm not the OP but that also does not work.
Stuck in fastboot upgrading to OOS 10
Awkwardguy9000 said:
I dont understand why It wont boot into the twrp img.
Same problem here, after trying to upgrade from OOS 9 to OOS10 (clean flash like described in https://forum.xda-developers.com/oneplus-6/how-to/official-oxygenos-5-1-5-ota-oneplus-6-t3794232). After Flashing OOS10.03, latest TWRP bluespark 9.109, and Magisk 20.4, the phone got stuck in the "bootloader unlocked" startup screen.
Maybe the problem was I came from 9.08 (seems one first has to go to 9.09 ?), maybe the problem was Magisk 20.4 not working well with TWRP ?
In any case I decided to restore my nandroid backup. However, after this I lost the recovery, and now cant flash it back with fastboot (same symptoms as described elsewhere in this post). None of the belopw work:
fastboot flash recovery TWRPxxx (tells me recovery_a not found)
fastboot flash boot TWRPxxx (works, but can't boot into recovery anyway)
fastboot boot TWRPxxx (works, but doen't boot into recovery )
I noticed that at startup I see for a moment the Android 10 logo (the little green man), but the OOS I restored with the nandroid backup is 9.08 ! Presumably the phone is now stuck in the Nirwana between Pie and Q.
My question is now the following:
How can I use fastboot to flash a new TWRP, OOS amd Magisk without loosing my internal disk data ? Which version of TWRP, OOS, and Magisk should I use ? Is it best to first go back to OOS 9 or should I go rightaway to OOS 10 ?
Thanks
PS: Could I try to swich the active partition ? fastboot getvar all tells me I am in slot a
bootloader) has-slot:modem:yes
(bootloader) has-slot:system:yes
(bootloader) current-slot:a
(bootloader) has-slot:boot:yes
(bootloader) slot-retry-count:b:6
(bootloader) slot-unbootable:b:no
(bootloader) slot-successful:b:yes
(bootloader) slot-retry-count:a:7
(bootloader) slot-unbootable:a:no
(bootloader) slot-successful:a:no
(bootloader) slot-count:2
(bootloader) secure:yes
Edit: Managed to go back to TWRP recovery by switching the active partition (fastboot --set-active=b). But what next? Dont want to loose that slot as well..
EDIT: I now actually managed to boot back to recovery (fastboot boot twrp-3.3.1-18-enchilada-Q-mauronofrio.img). I could save important files back to the PC (via simple drag and drop), including the Nandroid Backup (OOS9.08), music, photos etc..
In principle I could now try to flash a new ROM.zip, but which one ? Should I go back to the old OOS (9.08), or to 9.09 so I can upgrade to 10 later ? But the TWRP version is Android Q, so maybe I should try 10.0 or 10.3 ?
Would anybody know which (if any) of these possibilities has the best chance to succeed without wiping the internal data ?
If a total wipe is unavoidable, what is the best way to proceed ? Is via TWRP recovery possible (clean install, but leave internal data intakt),or do I need fastboot flash which wipes all user data es well (as described https://forum.xda-developers.com/oneplus-6/how-to/rom-stock-fastboot-roms-oneplus-6-t3796665) ?
Click to expand...
Click to collapse
Problem Solved
I followed this post https://forum.xda-developers.com/showpost.php?p=78915106&postcount=2
(reflash same ROM and Magisk versions as those originally installed, then restore nandroid backup).
3 things to note which were not obvious to me:
- Unzipp ALL files into one single folder (same ROMs have zips within zips)
- use the "flash-all-partitions-fastboot.bat" file,
- answer NO to the first question "Wipe all data (recommended)". If not, the internal data (data/media) will be wiped as well, including your nandroid backup and other info (music, photo..). If you have to wipe, make sure the backup is on the PC
¡ I need help please !
I have a HTC Desire 10 pro (From Aliexpress, yes warranty avoid), it was working fine (more than a year) until a few days ago. One morning I took it and it was off but the notification led was not on despite charging. I tried to turn it on and enter to recovery but it was not responding. I decided to open the phone to remove the battery and verify that it was not damaged. Mysteriously the battery was in good condition, and once I removed it and plugged it back in, the phone responded again when connecting the USB and the charger.
But there is a problem, when the system is going to boot, after showing the HTC logo, the phone turns off together with the notification led and returns to the state in which I found it at first.
I removed and placed the battery again so that it would respond again, but now I entered to recovery to make a reset, but the problem is that the recovery is very outdated, so it does not have the "wipe data" options.
It should be said that i can enter into a "recovery mode" that shows:
"
hTC download mode
*** LOCKED ***
htc_a56dj_pro_dtwl PVT S-ON
LK-1.01.0000(8804eff8)
RADIO-UNKNOWN
OpenDSP-UNKNOWN
OS-1.18.400.22
Aug 1 2017,13:15:24(929341)
system info
show barcode
reboot to bootloader
reboot to download mode
reboot
power down
Security Warranty
If you flash this phone with any ROM
that was not officially released by HTC
you take the risk of
releasing your personal and financial
information to unknown sources.
SD NOT MOUNTED
OTG NOT MOUNTED
FILE NOT FOUND
"
Where the blue txt is the actual menu.
In this "recovery mode" I can't use ADB commands, i only can execute some fastboot commands (PC recognizes my device because of fastboot drivers) as "reboot", but for example:
* I can't use the "erase" command because my current recovery is not supported:
"
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot erase userdata
erasing 'userdata'...
FAILED (remote: Partition userdata erase not supported)
finished. total time: 0.022s
"
* Nor I can directly install the TWRP recovery because it tells me:
"
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash recovery recovery.img
target reported max download size of 1596000000 bytes
sending 'recovery' (14320 KB)...
OKAY [ 1.507s]
writing 'recovery'...
(bootloader) HOSD CL#929341
FAILED (remote: 9 RU_SECURITY_FAIL recovery and bootloader isn't BL_UNLOCKE)
finished. total time: 2.550s
"
* And I can't use the "oem unlock" command either because it just says:
"
...
(bootloader) [ERR] Command error !!!
OKAY [ 0.062s]
finished. total time: 0.062s
"
Finally "getvar all" command shows this (i think could be useful):
"
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot getvar all
(bootloader) kernel: lk
(bootloader) product: htc_a56dj_pro_dtwl
(bootloader) version: 1.0
(bootloader) max-download-size: 1596000000
(bootloader) serialno: LC68B1000101
(bootloader) current-slot:
(bootloader) imei: ( here shows IMEI correctly )
(bootloader) version-main: 1.18.400.22
(bootloader) boot-mode: download
(bootloader) version-baseband: READ version-baseband ERROR
(bootloader) version-bootloader: 1.01.0000(8804eff8)
(bootloader) mid: 2PYA1****
(bootloader) cid: 11111111
all:
finished. total time: 0.061s
"
Well, this is the situation, and i think the solution is:
Install the TWRP recovery to do a factory reset and if necessary install a ROM (official or not).
Buuut, to install the recovery I need to activate USB debugging (MANUALLY in the android options) and activate the OEM unlock option to unlock the bootloader, which is impossible for me since the phone "turns off" before starting.
My question is:
How to activate OEM unlock option without having to access to android settings? I mean, with commands in fastboot or in some software.
I have searched a LOT on the internet and I can't find anything about it, all the tutorials have the device fully functional, not like me that my device does not start.
Hmmm ill help you with your answer if u can get help for me with mine
Zaq1xsw222 said:
Hmmm ill help you with your answer if u can get help for me with mine
Click to expand...
Click to collapse
So help me and give me your answer, let me see if i can help you
CheckS86 said:
So help me and give me your answer, let me see if i can help you
Click to expand...
Click to collapse
Ok so you was saying you need a command right to type into linux shell. But hold on did you put a custom rom onto the phone yourself
Also, if your phone randomly stopped working by its self, our issues may be related........
Zaq1xsw222 said:
Ok so you was saying you need a command right to type into linux shell. But hold on did you put a custom rom onto the phone yourself
Also, if your phone randomly stopped working by its self, our issues may be related........
Click to expand...
Click to collapse
No, i dont flash nothing in this phone, it just stopped working by itself.
I have a Windows 10 pc and i only can use some fastboot commands, so, i already tried various commands but my outdated recovery only letme run some of them!
CheckS86 said:
No, i dont flash nothing in this phone, it just stopped working by itself.
I have a Windows 10 pc and i only can use some fastboot commands, so, i already tried various commands but my outdated recovery only letme run some of them!
Click to expand...
Click to collapse
What was the last thing you done on your phone?
The last setting you changed?
Have you tried turning the phone on with the battery out?
Zaq1xsw222 said:
What was the last thing you done on your phone?
The last setting you changed?
Have you tried turning the phone on with the battery out?
Click to expand...
Click to collapse
I was playing or using whatsapp maybe, and yes, i tried that, but never start (because of the volt needed), only the LED is on
CheckS86 said:
I was playing or using whatsapp maybe, and yes, i tried that, but never start (because of the volt needed), only the LED is on
Click to expand...
Click to collapse
Here u go.
Hard Reset HTC Desire 10 Pro, how to - HardReset.info
www.hardreset.info
Ok now its your turn
Zaq1xsw222 said:
Here u go.
Hard Reset HTC Desire 10 Pro, how to - HardReset.info
www.hardreset.info
Click to expand...
Click to collapse
The phone make exatly the same, after set the HTC logo the screen and LED turn down (like an animation when lock your screen), i dont know why, but making this led mi to the begining :/
(tell me your question btw)
CheckS86 said:
The phone make exatly the same, after set the HTC logo the screen and LED turn down (like an animation when lock your screen), i dont know why, but making this led mi to the begining :/
(tell me your question btw)
Click to expand...
Click to collapse
Have you tried to restart your phone in safety mode?
Zaq1xsw222 said:
Have you tried to restart your phone in safety mode?
Click to expand...
Click to collapse
It doesn't work, this just led me to de begining too.
The phone can't start, so maybe re-install his firmware is the best option. I already search the firmware for this phone (to try flash it with SP Flashtool), even here in XDA there is an RUU Collection for this phone, but none of them is compatible with mine. This is the firmware compatible:
2PYAIMG_A56DJ_PRO_DTWL_M60_SENSE80GP_HTC_India_SEA_1.18.400.22_Radio_0.A56DJPV1P32.7900.0216.A56T_release_508642_combined_signed_2_4.zip
but is only available to buy... here for example:
2PYAIMG_A56DJ_PRO_DTWL_M60_SENSE80GP_HTC_India_SEA_1.18.400.22_Radio_0.A56DJPV1P32.7900.0216.A56T_release_508642_combined_signed_2_4.zip | Easy Firmware
easy-firmware.com
IDK why this firmware is not in other pages .
Reinstall stock firmware so you can boot into system. Then follow instructions to unlock with unlock code