Related
Hi all, long term lurker first time poster so please go easy on me.
After having many successes on rooting and flashing various device over the years thanks to this forum, I have finally completely knackered my M8 I think.
Awhile ago I rooted and flashed Venom Rom which worked perfectly. I then decided I wanted Revolution HD rom but obviously didn't follow the guide correctly as afterwards I couldn't get wifi. I still used the phone for a few months until yesterday when I finally decided to do something about it. So using Minimal ADB Fastboot I flashed a Lollipop firmware and was going to flash another ROM.
However, the phone won't boot into recovery, just the bootloader. Can anyone please tell me (in simple terms ) where I can go from here or whether I now have a brick?
If it helps the phone is "Relocked" and S-ON.
pastyal said:
Hi all, long term lurker first time poster so please go easy on me.
After having many successes on rooting and flashing various device over the years thanks to this forum, I have finally completely knackered my M8 I think.
Awhile ago I rooted and flashed Venom Rom which worked perfectly. I then decided I wanted Revolution HD rom but obviously didn't follow the guide correctly as afterwards I couldn't get wifi. I still used the phone for a few months until yesterday when I finally decided to do something about it. So using Minimal ADB Fastboot I flashed a Lollipop firmware and was going to flash another ROM.
However, the phone won't boot into recovery, just the bootloader. Can anyone please tell me (in simple terms ) where I can go from here or whether I now have a brick?
If it helps the phone is "Relocked" and S-ON.
Click to expand...
Click to collapse
post your fastboot getvar all please without imei and serial number
did the firmware flash complete successfully ?
---------- Post added at 10:40 AM ---------- Previous post was at 10:34 AM ----------
also forgot to add, if the firmware flash went through fine then you will now have stock recovery on your phone, this will just look like a big red exclamation mark on your phone.
at this point you either need to find a stock RUU for your phone and run it now or unlocked your bootloader again at HTC dev, flash a custom recovery and then flash a custom rom.
if you have anything custom / non stock on your phone right now, it wont boot or load with a relocked bootloader.
Seanie280672 said:
post your fastboot getvar all please without imei and serial number
did the firmware flash complete successfully ?
---------- Post added at 10:40 AM ---------- Previous post was at 10:34 AM ----------
also forgot to add, if the firmware flash went through fine then you will now have stock recovery on your phone, this will just look like a big red exclamation mark on your phone.
at this point you either need to find a stock RUU for your phone and run it now or unlocked your bootloader again at HTC dev, flash a custom recovery and then flash a custom rom.
if you have anything custom / non stock on your phone right now, it wont boot or load with a relocked bootloader.
Click to expand...
Click to collapse
Many thanks for the reply. I don't think the Firmware flashed succesfully, I tried three times and each time got the same response:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash zip firmware.zip
target reported max download size of 1830711296 bytes
sending 'zip' (49565 KB)...
OKAY [ 2.770s]
writing 'zip'...
(bootloader) adopting the signature contained in this image...
(bootloader) signature checking...
(bootloader) zip header checking...
(bootloader) zip info parsing...
(bootloader) checking model ID...
(bootloader) checking custom ID...
FAILED (remote: 42 custom id check fail)
finished. total time: 6.410s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash zip firmware.zip
target reported max download size of 1830711296 bytes
sending 'zip' (49565 KB)...
OKAY [ 2.787s]
writing 'zip'...
(bootloader) adopting the signature contained in this image...
(bootloader) signature checking...
(bootloader) zip header checking...
(bootloader) zip info parsing...
(bootloader) checking model ID...
(bootloader) checking custom ID...
FAILED (remote: 42 custom id check fail)
finished. total time: 6.431s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash zip firmware.zip
target reported max download size of 1830711296 bytes
sending 'zip' (49565 KB)...
OKAY [ 2.790s]
writing 'zip'...
(bootloader) adopting the signature contained in this image...
(bootloader) signature checking...
(bootloader) zip header checking...
(bootloader) zip info parsing...
(bootloader) checking model ID...
(bootloader) checking custom ID...
FAILED (remote: 42 custom id check fail)
finished. total time: 6.415s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot reboot
rebooting...
finished. total time: 0.013s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash recovery twrp.img
target reported max download size of 1830711296 bytes
sending 'recovery' (17034 KB)...
OKAY [ 1.706s]
writing 'recovery'...
(bootloader) signature checking...
FAILED (remote: signature verify fail)
finished. total time: 2.455s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash recovery twrp.img
target reported max download size of 1830711296 bytes
sending 'recovery' (17034 KB)...
OKAY [ 1.713s]
writing 'recovery'...
(bootloader) signature checking...
FAILED (remote: signature verify fail)
finished. total time: 2.463s
Click to expand...
Click to collapse
And heres the getvar all
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.16.0.0000
(bootloader) version-baseband: 1.15.2133156.UA13G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno:
(bootloader) imei:
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B10000
(bootloader) cidnum: ORANG001
(bootloader) battery-status: good
(bootloader) battery-voltage: 0mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: ab0efa49
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
Click to expand...
Click to collapse
pastyal said:
Many thanks for the reply. I don't think the Firmware flashed succesfully, I tried three times and each time got the same response:
And heres the getvar all
Click to expand...
Click to collapse
which firmware did you download ? description or link if possible.
also you cant flash custom recovery as your bootloader is locked, and you need stock recovery and HTC dev unlock token to unlock it.
remove your imei and serial number from your getvar all, also, as you are s-on, you need to make sure that the firmware you flashed is ORANG001 firmware as per your cid, at a guess it will be something like 4.xx.61.x the 61 is the key, this will relate to region / carrier 61 is orange / EE, and the 4 is the latest android version firmware for the HTC one M8, as your version main is missing I cant fully confirm this, this is a fault from flashing earlier versions of TWRP recovery.
alternatively, you can flash a custom rom and get s-off via sunshine s-off @ $25 and convert your phone.
Seanie280672 said:
which firmware did you download ? description or link if possible.
also you cant flash custom recovery as your bootloader is locked, and you need stock recovery and HTC dev unlock token to unlock it.
remove your imei and serial number from your getvar all, also, as you are s-on, you need to make sure that the firmware you flashed is ORANG001 firmware as per your cid, at a guess it will be something like 4.xx.61.x the 61 is the key, this will relate to region / carrier 61 is orange / EE, and the 4 is the latest android version firmware for the HTC one M8, as your version main is missing I cant fully confirm this, this is a fault from flashing earlier versions of TWRP recovery.
alternatively, you can flash a custom rom and get s-off via sunshine s-off @ $25 and convert your phone.
Click to expand...
Click to collapse
Ooops thanks for the heads up on removing the info!
Aaah thats the mistake I made by using the wrong firmware. I will locate the correct firmware and try that later on today. I did look at the Sunshine option but was unsure if it would help me at this moment in time. Think i'll try the correct firmware first.
Will update here later with good news hopefully!
Seanie280672 said:
post your fastboot getvar all please without imei and serial number
did the firmware flash complete successfully ?
---------- Post added at 10:40 AM ---------- Previous post was at 10:34 AM ----------
also forgot to add, if the firmware flash went through fine then you will now have stock recovery on your phone, this will just look like a big red exclamation mark on your phone.
at this point you either need to find a stock RUU for your phone and run it now or unlocked your bootloader again at HTC dev, flash a custom recovery and then flash a custom rom.
if you have anything custom / non stock on your phone right now, it wont boot or load with a relocked bootloader.
Click to expand...
Click to collapse
Ok, I have now succesfully flashed the correct (I think ) firmware. I flashed twice to be sure. In cmd I rebooted to Fastboot but all I have now is the screen you mentioned with the red exclamation mark within a triangle. Where do I go from here as the phone won't do anything, not even turn off. It does occasionally turn off itself and I try to enter bootloader but it just loads to the red exclamation mark again.?
pastyal said:
Ok, I have now succesfully flashed the correct (I think ) firmware. I flashed twice to be sure. In cmd I rebooted to Fastboot but all I have now is the screen you mentioned with the red exclamation mark within a triangle. Where do I go from here as the phone won't do anything, not even turn off. It does occasionally turn off itself and I try to enter bootloader but it just loads to the red exclamation mark again.?
Click to expand...
Click to collapse
hold volume up, volume down and power button for about 15 to 20 seconds, phone will go off, before it comes back on quickly release all buttons and just hold volume down only, it should boot to the bootloader.
Thank you for that, that gets me into the bootloader but it won't load into fastboot now?
pastyal said:
Thank you for that, that gets me into the bootloader but it won't load into fastboot now?
Click to expand...
Click to collapse
what do you mean wont load into fastboot ? do you mean your computer just says waiting for device, which firmware did you flash ?
Seanie280672 said:
what do you mean wont load into fastboot ? do you mean your computer just says waiting for device, which firmware did you flash ?
Click to expand...
Click to collapse
Yes pc says waiting for device. I flashed a firmware from here, not sure which one it was now though http://forum.xda-developers.com/showthread.php?t=2701376
Do I need to flash a stock recovery now? If so do I need to be able to get the phone to load into fastboot?
pastyal said:
Yes pc says waiting for device. I flashed a firmware from here, not sure which one it was now though http://forum.xda-developers.com/showthread.php?t=2701376
Do I need to flash a stock recovery now? If so do I need to be able to get the phone to load into fastboot?
Click to expand...
Click to collapse
no you don't need to flash stock recovery, I don't see any firmware files for your phone in that link, and as your s-on, they shouldn't of been successful, nothing should of changed.
waiting for device is generally a driver problem, check device manager whilst your phone is plugged into your computer, should say android devices - MyHTC
Seanie280672 said:
no you don't need to flash stock recovery, I don't see any firmware files for your phone in that link, and as your s-on, they shouldn't of been successful, nothing should of changed.
waiting for device is generally a driver problem, check device manager whilst your phone is plugged into your computer, should say android devices - MyHTC
Click to expand...
Click to collapse
I can't see any android devices listed under device manager. I installed HTC Sync yesterday though which I thought loaded the drivers? What should i do now?
pastyal said:
I can't see any android devices listed under device manager. I installed HTC Sync yesterday though which I thought loaded the drivers? What should i do now?
Click to expand...
Click to collapse
Try to uninstall HTC Sync and any HTC drivers. Then see if the phone shows up in Device Manager. If so, select to manually pick drivers, and pick the generic MTP device.
Might not work for you, but this is what I had to do to get fastboot/adb working on my PC with the M8.
pastyal said:
I can't see any android devices listed under device manager. I installed HTC Sync yesterday though which I thought loaded the drivers? What should i do now?
Click to expand...
Click to collapse
Also make sure in bootloader it says FASTBOOT USB and not HBOOT
redpoint73 said:
Try to uninstall HTC Sync and any HTC drivers. Then see if the phone shows up in Device Manager. If so, select to manually pick drivers, and pick the generic MTP device.
Might not work for you, but this is what I had to do to get fastboot/adb working on my PC with the M8.
Click to expand...
Click to collapse
ssantos132 said:
Also make sure in bootloader it says FASTBOOT USB and not HBOOT
Click to expand...
Click to collapse
Sorted it, was a simple matter of swapping USB ports. I have a new laptop and forgot one of the ports was USB 3.0 which the phone was connected with. Evidently it prefers a USB 2.0 port.
So I assume now I need to find the correct firmware, of which I'm struggling with a little. Can anyone po8nt me in the right direction? I have been through a lot of threads here and can't seem to find anything.
pastyal said:
Sorted it, was a simple matter of swapping USB ports. I have a new laptop and forgot one of the ports was USB 3.0 which the phone was connected with. Evidently it prefers a USB 2.0 port.
Click to expand...
Click to collapse
That's right, USB 3.0 does not play well with this device.
pastyal said:
So I assume now I need to find the correct firmware, of which I'm struggling with a little. Can anyone po8nt me in the right direction? I have been through a lot of threads here and can't seem to find anything.
Click to expand...
Click to collapse
I can't find the firmware for your CID either. You may have better luck updating the firmware by OTA.
To do that, you will need to restore the stock ROM and stock recovery, using the files and instructions here: http://forum.xda-developers.com/showthread.php?t=2701376
After restoring stock ROM and stock recovery, you will need to update up to Lollipop, which will probably include a few (3) OTA updates.
Once you've updated to current firmware by OTA, you can install custom recovery again, and run the current custom ROMs.
redpoint73 said:
That's right, USB 3.0 does not play well with this device.
I can't find the firmware for your CID either. You may have better luck updating the firmware by OTA.
To do that, you will need to restore the stock ROM and stock recovery, using the files and instructions here: http://forum.xda-developers.com/showthread.php?t=2701376
After restoring stock ROM and stock recovery, you will need to update up to Lollipop, which will probably include a few (3) OTA updates.
Once you've updated to current firmware by OTA, you can install custom recovery again, and run the current custom ROMs.
Click to expand...
Click to collapse
I'm getting myself in a right mess I think. I've just tried installing the stock recoveries from https://www.androidfilehost.com/?w=files&flid=25064 as linked to from this thread http://forum.xda-developers.com/showthread.php?t=2694994 which I thought woud be perfect for me but I get an error of "FAILED (remote: signature verify fail)" in cmd. If I reboot the phone into recovery I get the red exclamation mark again.
Any ideas on what i'm doing wrong? Am i right in thinking I need to flash a stock recovery and THEN a stock ROM, or should it be the other way around?
pastyal said:
I'm getting myself in a right mess I think. I've just tried installing the stock recoveries from https://www.androidfilehost.com/?w=files&flid=25064 as linked to from this thread http://forum.xda-developers.com/showthread.php?t=2694994 which I thought woud be perfect for me but I get an error of "FAILED (remote: signature verify fail)" in cmd. If I reboot the phone into recovery I get the red exclamation mark again.
Any ideas on what i'm doing wrong? Am i right in thinking I need to flash a stock recovery and THEN a stock ROM, or should it be the other way around?
Click to expand...
Click to collapse
Multiple mistakes here:
1) You need the stock ROM and recovery that corresponds with your hboot (3.16) which would indicate a 1.x software and corresponding recovery. The files you linked are for software 3.x and 4.x.
2) I'm also not sure why you are stumbling around in threads that aren't even for your CID when I already gave you a link to the proper location for the stock nandroid for your CID version. You want to restore the stock nandroid for ORANG001, which is 1.54.61.5 and the stock recovery 1.54.xx
3) You need to flash the stock ROM (restore stock nandroid) before the stock recovery. Once you've restored stock recovery, you cannot flash a ROM or nandroid. You need custom recovery to do that.
3) Lollipop recoveries for other CID won't work. But a KitKat recovery for another CID will work (as mentioned in item 2 above, you want a 1.54.xx recovery to correspond to the stock ROM 1.54.61.5 since a recovery doesn't seem to be posted for your exact software 1.54.61.5
redpoint73 said:
Multiple mistakes here:
1) You need the stock ROM and recovery that corresponds with your hboot (3.16) which would indicate a 1.x software and corresponding recovery. The files you linked are for software 3.x and 4.x.
2) I'm also not sure why you are stumbling around in threads that aren't even for your CID when I already gave you a link to the proper location for the stock nandroid for your CID version. You want to restore the stock nandroid for ORANG001, which is 1.54.61.5 and the stock recovery 1.54.xx
3) You need to flash the stock ROM (restore stock nandroid) before the stock recovery. Once you've restored stock recovery, you cannot flash a ROM or nandroid. You need custom recovery to do that.
3) Lollipop recoveries for other CID won't work. But a KitKat recovery for another CID will work (as mentioned in item 2 above, you want a 1.54.xx recovery to correspond to the stock ROM 1.54.61.5 since a recovery doesn't seem to be posted for your exact software 1.54.61.5
Click to expand...
Click to collapse
Thanks very much for that, the reason why i was stumbling around is because i had already tried that Nandroid backup but i think i must have used incorrect instructions. I read I had to open the zip file and flash the boot.img, but I just get the same error as before if I do that.
Could you please tell me how to restore the stock Nandroid. i promise you I am going around in circles lol
pastyal said:
i had already tried that Nandroid backup but i think i must have used incorrect instructions. I read I had to open the zip file and flash the boot.img, but I just get the same error as before if I do that.
Click to expand...
Click to collapse
Instruction on restoring a nandroid are in post #3 of the stock nandroid collection thread I linked before. Click where it says Questions & Answers, and you will see the 2nd question is how to restore a stock nandroid: http://forum.xda-developers.com/showpost.php?p=58128936&postcount=3
I think you may have seen these instructions, but you only did one part, not the remaining parts of the process. The boot.img is essentially just the kernel; technically a few other things too, but either way its like 1% of what you need to have a working ROM. Namely, if you only flashed boot.img, you didn't do the steps I've highlighted in orange below:
- Place the nandroid backup unpacked on the sdcard of the phone in the right backup folder
* Philz touch uses - Clockworkmod\Backups\
* TWRP uses - TWRP\Backups\ or TWRP/Backups/serialnum/ (replace serialnum with your device's serial number. To have TWRP create the proper directory structure for you, just do a simple backup of just the boot partition and put the backup files in there) thanks to garyd9 for the additional info
- Flash the boot.img or boot.emmc.win file from the nandroid backup
- Make a full wipe in the recovery
- Restore the nandroid backup and reboot
You need to unzip the downloaded file, then place the entire folder contents to the proper location on the phone. Then boot recovery (probably TWRP) and use the restore function to install the nandroid. I actually do not think you need to extract and flash boot.img separately.
After that, install the stock recovery with the fastboot command: fastboot flash recovery filename.img
Where "filename.img" is the actual name of the desired stock recovery file.
---------- Post added at 11:03 AM ---------- Previous post was at 10:57 AM ----------
pastyal said:
If it helps the phone is "Relocked" and S-ON.
Click to expand...
Click to collapse
Are you currently unlocked again? The above is from your top post, but I don't know if you've changed this (unlocked again).
You can only do the above mentioned steps (restore nandroid, stock recovery, etc.) if you are bootloader unlocked.
Hi guys.
I rooted my 816 using CWM and SuperSU months ago. Now, there's an OTA update to Android 6.0 which will hopefully render the usefulness of root obsolete, as I mostly need it for link2sd (they also cite better RAM management as a new feature, which should get rid of the horrible lag on Lollipop).
I know I have to go back to full stock, and I read a simple guide somewhere, and I thought, why don't I give it a crack. So, it said I should just "fastboot oem lock" the phone and flash the correct .zip RUU. After much trouble with connectivity and driver issues between my computer (adb server is out of date. killing...; device offline; errors etc.) I FINALLY (after hours of troubleshooting) managed to go into fastboot via USB and lock the bootloader. Great. But, when I tried to flash the .zip, it just says waiting for device, indefinitely. Tried to go into recovery via the power buttons on the phone, but it shows an error and simply refuses to. As a sidenote, root still works, but the phone displays this in fastboot: Relocked, Security Warning.
Basically, I'm afraid to proceed because I think I'm on the wrong track, and could end up f'ing up my device altogether. I'm from Croatia so I downloaded the 5.0.1 EU version .zip from here: (can't post link, just search htcdev downloads, it's the first one).
I hate opening new threads because I'm sure someone has already had the problems I'm having, but I just can't keep searching the web for hours on end trying to find a solution. Forgive me for this guys, and please help a poor noob in need if you can.
Could you please post your device info? (Make sure to delete serialno. and imei!)
To get your device info, you'll need to make sure all drivers are up-to-date.(HTC Sync, Java and ADB)
After installing,
- Navigate to ADB folder and click on any free space while holding the shift Key
- Choose 'Open command window here'
- Once cmd is started use this command
Code:
fastboot devices
and check if your device is listed, then type
Code:
fastboot getvar all
and copy/paste code here.
nukaru said:
Could you please post your device info? (Make sure to delete serialno. and imei!)
To get your device info, you'll need to make sure all drivers are up-to-date.(HTC Sync, Java and ADB)
After installing,
- Navigate to ADB folder and click on any free space while holding the shift Key
- Choose 'Open command window here'
- Once cmd is started use this command
Code:
fastboot devices
and check if your device is listed, then type
Code:
fastboot getvar all
and copy/paste code here.
Click to expand...
Click to collapse
Oh great, you're from Germany, so you have an EU 816 too. It's an a5ul just like yours. I'll send the full info text as soon as i install SDK tools completely.
I noticed that in your guide you first flash the stock ROM, and only then lock the bootloader. In the guide I found it said to first lock the bootloader, and then flash the stock ROM. So right now, I have a locked bootloader and CWM recovery I can't get into. Is this going to be a problem?
No, you first flash the stock recovery, then relock bootloader. And if your flashed recovery works you flash the RUU.
running fastboot devices does literally nothing, just sends me to the next line.
running adb devices, on the other hand, lists my device.
great, so I messed up there. do you know how I can fix it?
Are you able to boot into fastboot USB? Have you tried the fastboot getvar all comand?
If yes, first you need to flash the stock recovery and check if the flash was a success. If you can get into recovery without any errors, relock bootloader and place the RUU file on sd-card. Boot to bootloader again and the flashing should start on its own.
nukaru said:
Are you able to boot into fastboot USB? Have you tried the fastboot getvar all comand?
If yes, first you need to flash the stock recovery and check if the flash was a success. If you can get into recovery without any errors, relock bootloader and place the RUU file on sd-card. Boot to bootloader again and the flashing should start on its own.
Click to expand...
Click to collapse
I managed to get the getvar command to work: here's the info
C:\Program Files (x86)\Android\android-sdk\platform-tools>adb reboot bootloader
C:\Program Files (x86)\Android\android-sdk\platform-tools>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.101.111011.20.0123
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: *
(bootloader) imei: *
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: a5_ul
(bootloader) platform: hTCBmsm8226
(bootloader) modelid: 0P9C20000
(bootloader) cidnum: HTC__032
(bootloader) battery-status: good
(bootloader) battery-voltage: 0mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: 09813c97
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.054s
The files from my guide should work with your device.
so it doesn't matter that my bootloader is now locked? I can just follow your guide and it should work?
Have you flashed stock recovery BEFORE locking bootloader? You have to install stock recovery or the RUU won't flash. It's all in the guide.
No, i didn't. I locked the bootloader and then tried to flash the stock RUU. That's the problem.
I wish I'd seen your guide before I did anything. I assume trying to flash anything now won't work, and that I'll have to unlock the bootloader again?
edofot said:
No, i didn't. I locked the bootloader and then tried to flash the stock RUU. That's the problem.
I wish I'd seen your guide before I did anything. I assume trying to flash anything now won't work, and that I'll have to unlock the bootloader again?
Click to expand...
Click to collapse
Did you type this before flashing the RUU?
Code:
fastboot oem rebootRUU
Nope. I tried to flash the RUU with fastboot flash ... .zip but it just said: waiting for device; and nothing happened. So I'll try the rebootRUU command when I get home from classes.
You need to flash the stock recovery, otherwise you won't be able to flash any official RUU.
Unlock bootloader, flash stock recovery, relock bootloader and flash RUU.
The command won't work, since you have a custom recovery. You need to get rid of that first.
nukaru said:
You need to flash the stock recovery, otherwise you won't be able to flash any official RUU.
Unlock bootloader, flash stock recovery, relock bootloader and flash RUU.
The command won't work, since you have a custom recovery. You need to get rid of that first.
Click to expand...
Click to collapse
I unlocked the bootloader, and did everything your guide said. Everything worked perfectly.
I just have a problem right now flashing the 0P9CIMG.zip. I can't flash it over the computer (it says the data length is too large or something similar), and I can't move it to sd-card on my phone. I tried moving other files and other .zip files, and that works. I tried redownloading from mega.nz, nothing. I'm thinking the .zip gets corrupted when downloading. Can you maybe re-upload it or send it to me through a different medium?
edofot said:
I unlocked the bootloader, and did everything your guide said. Everything worked perfectly.
I just have a problem right now flashing the 0P9CIMG.zip. I can't flash it over the computer (it says the data length is too large or something similar), and I can't move it to sd-card on my phone. I tried moving other files and other .zip files, and that works. I tried redownloading from mega.nz, nothing. I'm thinking the .zip gets corrupted when downloading. Can you maybe re-upload it or send it to me through a different medium?
Click to expand...
Click to collapse
Use this HTC mini-SDK
Gibz97 said:
Use this HTC mini-SDK
Click to expand...
Click to collapse
Tried it.
Stumped by this:
Code:
C:\Users\Korisnik\Desktop\HTC mini SDK>fastboot flash zip 0P9CIMG.zip
sending 'zip'... (51060 KB) OKAY
sending time = 2.709 secs
writing 'zip'... (bootloader) adopting the signature contained in this image...
(bootloader) signature checking...
FAILnot allowed
FAILED (remote: not allowed)
Execution time is 7(s)
edofot said:
Tried it.
Stumped by this:
Code:
C:\Users\Korisnik\Desktop\HTC mini SDK>fastboot flash zip 0P9CIMG.zip
sending 'zip'... (51060 KB) OKAY
sending time = 2.709 secs
writing 'zip'... (bootloader) adopting the signature contained in this image...
(bootloader) signature checking...
FAILnot allowed
FAILED (remote: not allowed)
Execution time is 7(s)
Click to expand...
Click to collapse
First type this. It will reboot phone into a black screen with a silver HTC logo:
Code:
fastboot oem rebootRUU
then type:
Code:
fastboot erase cache
then type:
Code:
fastboot flash zip 0P9CIMG.zip
Sorry, I was looking for an sd-card adapter, I wasn't here.
Update: Moved the 09PCIMG.zip to the sd-card successfully this time and am flashing the img now from sd-card! Seems to be going well so far.
Success
Finally! Did it, works like a charm.
I'm still amazed by how fast the phone really is when it's stock.
Viele Dank, @nukaru, du wärst eine sehr grosse hilfe. Wenn du nach Kroatien kommst, melde mich an, du hast ein Bier und/oder Kaffe von mich (at least I tried, even without google translate)
Thank you too @Gibz97, really appreciate the effort.
If anyone reading this has the same questions I had, just follow nukaru's guide, it has all you need to know. If you have an A5_UL, it's gonna work.
Hi, Yesterday I flashed TWRP recovery in my Moto G5, and as i'm a newbie with Moto's phones i didn't unlock OEM, and I bricked the phone. When I turn on my phone it goes to a bootloop. How can I unbrick my phone, because the phone doesn't boot. I tried to flash the stock rom for my moto g5 XT1670, it wasn't updated and it failed because i'm making a downgrade. My Question is what can I do to "revive" my phone???
LonchoNe said:
Hi, Yesterday I flashed TWRP recovery in my Moto G5, and as i'm a newbie with Moto's phones i didn't unlock OEM, and I bricked the phone. When I turn on my phone it goes to a bootloop. How can I unbrick my phone, because the phone doesn't boot. I tried to flash the stock rom for my moto g5 XT1670, it wasn't updated and it failed because i'm making a downgrade. My Question is what can I do to "revive" my phone???
Click to expand...
Click to collapse
Thats not a Problem, just Google how to unlock and youre fine afterwards.
Unlock the bootloader then flash twrp once more, then flash the rom you want. If it's an oreo rom then flash a 64bit recovery as it's mandatory.
Unlock phone here: https://motorola-global-portal.custhelp.com/app/standalone/bootloader/unlock-your-device-a
I Tried to unlock bootloader but i don't know if the bootloader is unlocked:
C:\Users\karln\OneDrive\Escritorio\platform-tools>.\fastboot oem unlock BVMF22NAUPPPFUXM3JBP
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
...
(bootloader) Check 'Allow OEM Unlock' in Android Settings > Developer
(bootloader) Options
OKAY [ 0.179s]
finished. total time: 0.180s
Is it unlocked or not? if not, what can I do, 'cos I can't boot
LonchoNe said:
I Tried to unlock bootloader but i don't know if the bootloader is unlocked:
C:\Users\karln\OneDrive\Escritorio\platform-tools>.\fastboot oem unlock BVMF22NAUPPPFUXM3JBP
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
...
(bootloader) Check 'Allow OEM Unlock' in Android Settings > Developer
(bootloader) Options
OKAY [ 0.179s]
finished. total time: 0.180s
Is it unlocked or not? if not, what can I do, 'cos I can't boot
Click to expand...
Click to collapse
Try to start in Factory mode (Fastboot > Factory Mode). If you can't, you can search about your warranty.
go in settings- about- then type 7 times on build, go back, click on developer options- go to allow oem unlock and turn on. After that retry to unlock via fastboot
LonchoNe said:
I Is it unlocked or not? if not, what can I do, 'cos I can't boot
Click to expand...
Click to collapse
I can't activate oem in settings because i'm in soft brick
Download a fastboot stock ROM and flash it. Since it's official, you shouldn't have any problem. Before flashing, make sure it's a newer ROM version that the one you currently had.
I unlocked boot loader and got to the screen where you select with your volume keys to select yes which i did after which my phone restarted and from then on just keeps restarting after staying on the HTC white screen for a minute or so. I cant do anything such as access the recovery mode through hold power and volume down keys. PLEASE Help.
Update
Somehow managed to get into recovery says it unlocked but cant move up or down with volume keys. Did manage to click select and have gone through the process of SD Checking-No Gift file- Loading...0P6BDIAG.zip-No image-loading...0P6BDIAG.nbh-no image or wrong image and another zip file and then back to menu with fastboot recovery etc. Now can move around but what should i select next?
MinionZee said:
Somehow managed to get into recovery says it unlocked but cant move up or down with volume keys. Did manage to click select and have gone through the process of SD Checking-No Gift file- Loading...0P6BDIAG.zip-No image-loading...0P6BDIAG.nbh-no image or wrong image and another zip file and then back to menu with fastboot recovery etc. Now can move around but what should i select next?
Click to expand...
Click to collapse
Was there any indication that your volume rocker was broken before you unlocked the bootloader?
redpoint73 said:
Was there any indication that your volume rocker was broken before you unlocked the bootloader?
Click to expand...
Click to collapse
Volume rocker works perfectly as well as power button but as i stated i got to the point where they do work but which option do i select from recovery mode?
MinionZee said:
Volume rocker works perfectly as well as power button but as i stated i got to the point where they do work but which option do i select from recovery mode?
Click to expand...
Click to collapse
The screen is called bootloader (not recovery) just to be clear.
Select FASTBOOT, then proceed with flashing TWRP via fastboot. Which I assume is what you are trying to do (install TWRP) as that is the next step after unlocking the bootloader, whether you are rooting or flashing a custom ROM.
redpoint73 said:
The screen is called bootloader (not recovery) just to be clear.
Select FASTBOOT, then proceed with flashing TWRP via fastboot. Which I assume is what you are trying to do (install TWRP) as that is the next step after unlocking the bootloader, whether you are rooting or flashing a custom ROM.
Click to expand...
Click to collapse
What exactly would be the process of doing that? can i just do it through hasoons toolkit or do i do it manually?
MinionZee said:
What exactly would be the process of doing that? can i just do it through hasoons toolkit or do i do it manually?
Click to expand...
Click to collapse
Do it manually. @hasoon2000's toolkit is deprecated and out of date.
Go to here to download TWRP There are download mirrors for either US or Europe there. There are instructions there as well. You'll want to read the fastboot install method
MinionZee said:
What exactly would be the process of doing that? can i just do it through hasoons toolkit or do i do it manually?
Click to expand...
Click to collapse
I find it a bit concerning that you are asking this question in the middle of the process. These are things you should be researching (or asking) and understanding before you start to unlock the bootloader, not during or after. I typically recommend (to folks unfamiliar with phone mods) reading for at least a couple hours, and fully understanding all the steps, files, etc. before you begin any part of the process.
The advice from xunholyx is sound. Download the latest version TWRP, from the link he provided. Flash TWRP with fastboot install method on the same link.
But again, make sure you understand what you are doing before proceeding. For instance, it's not even clear what you are trying to accomplish from unlocking the bootloader: root or flash a custom ROM? Do you know how to do that after you have installed TWRP?
redpoint73 said:
I find it a bit concerning that you are asking this question in the middle of the process. These are things you should be researching (or asking) and understanding before you start to unlock the bootloader, not during or after. I typically recommend (to folks unfamiliar with phone mods) reading for at least a couple hours, and fully understanding all the steps, files, etc. before you begin any part of the process.
The advice from xunholyx is sound. Download the latest version TWRP, from the link he provided. Flash TWRP with fastboot install method on the same link.
But again, make sure you understand what you are doing before proceeding. For instance, it's not even clear what you are trying to accomplish from unlocking the bootloader: root or flash a custom ROM? Do you know how to do that after you have installed TWRP?
Click to expand...
Click to collapse
xunholyx said:
Do it manually. @hasoon2000's toolkit is deprecated and out of date.
Go to here to download TWRP There are download mirrors for either US or Europe there. There are instructions there as well. You'll want to read the fastboot install method
Click to expand...
Click to collapse
Update sorry for the delay. I manually flashed the recovery all went successfully, Until i try to access it on my phone it shows the htc logo white screen with the red warning text stays for about 1 min and phone restarts.
C:\One_M8_All-In-One_Kit_v\Data>fastboot flash recovery C:\One_M8_All-In-One_Kit_v\Data\twrp-3.2.1-0-m8.img
target reported max download size of 1826373632 bytes
sending 'recovery' (20298 KB)...
OKAY [ 1.830s]
writing 'recovery'...
OKAY [ 0.743s]
finished. total time: 2.581s
C:\One_M8_All-In-One_Kit_v\Data>fastboot reboot
rebooting...
finished. total time: 0.011s
Any more advice? and i was planning to root this phone using the website guide on https://htc-one.gadgethacks.com/how-to/unlock-bootloader-root-your-htc-one-m8-0154444/
MinionZee said:
Update sorry for the delay. I manually flashed the recovery all went successfully, Until i try to access it on my phone it shows the htc logo white screen with the red warning text stays for about 1 min and phone restarts.
Click to expand...
Click to collapse
Something seems odd in the way the phone is behaving, both in the quoted text above, and also in your first couple posts.
Need more info about the device. Can you still get to bootloader, by holding the vol down button the next time it restarts? If you need to trigger a restart, hold power button until it restarts (may take a minute in a "stuck" condition).
If you can access bootloader, do fastboot getvar all, and post the results (delete IMEI and serial number before posting).
MinionZee said:
Any more advice? and i was planning to root this phone using the website guide on https://htc-one.gadgethacks.com/how-to/unlock-bootloader-root-your-htc-one-m8-0154444/
Click to expand...
Click to collapse
Never heard of that website. Did someone recommend it to you, or did you just randomly Google it? How do you know it is reputable, and that the information is correct?
These random "root" websites usually just steal content from XDA and the developer's here, without giving proper credit. Case in point, the webpage you linked when referening chainfire (dev for SuperSU) just links to yet another random website I've never heard of "wonderhowto", which also looks like it just steals XDA content.
Another reason I don't recommend these websites, is for similar reason as the toolkits. A single webpage is going to miss a lot of detail and nuance. And has no mechanism for you to ask questions and get help (I don't consider the "comments" section a viable forum). So like the toolkits, they spoon feed you just enough info to get you into trouble. And do nothing to help you once you are at that point.
If you want a proper XDA guide, Vomer's guide is a good one: https://forum.xda-developers.com/htc-one-m8/general/vomerguides-m8-bootldr-unlock-s-off-t2800727
With the following caveats:
- As with most guides, you need to make sure you use updated version TWRP, as well as SuperSU (or Magisk is also highly recommended root method). The links in the guide are not up to date.
- Only follow Sections 0 and 1. The rest is outdated and no longer correct (but not any more outdated than the guide you linked).
redpoint73 said:
Something seems odd in the way the phone is behaving, both in the quoted text above, and also in your first couple posts.
Need more info about the device. Can you still get to bootloader, by holding the vol down button the next time it restarts? If you need to trigger a restart, hold power button until it restarts (may take a minute in a "stuck" condition).
If you can access bootloader, do fastboot getvar all, and post the results (delete IMEI and serial number before posting).
Never heard of that website. Did someone recommend it to you, or did you just randomly Google it? How do you know it is reputable, and that the information is correct?
These random "root" websites usually just steal content from XDA and the developer's here, without giving proper credit. Case in point, the webpage you linked when referening chainfire (dev for SuperSU) just links to yet another random website I've never heard of "wonderhowto", which also looks like it just steals XDA content.
Another reason I don't recommend these websites, is for similar reason as the toolkits. A single webpage is going to miss a lot of detail and nuance. And has no mechanism for you to ask questions and get help (I don't consider the "comments" section a viable forum). So like the toolkits, they spoon feed you just enough info to get you into trouble. And do nothing to help you once you are at that point.
If you want a proper XDA guide, Vomer's guide is a good one: https://forum.xda-developers.com/htc-one-m8/general/vomerguides-m8-bootldr-unlock-s-off-t2800727
With the following caveats:
- As with most guides, you need to make sure you use updated version TWRP, as well as SuperSU (or Magisk is also highly recommended root method). The links in the guide are not up to date.
- Only follow Sections 0 and 1. The rest is outdated and no longer correct (but not any more outdated than the guide you linked).
Click to expand...
Click to collapse
Another update. As i turned the phone on a black screen with red text came up at the bottom with the htc logo from which i got to the white screen boot-loop from which i accessed the bootloader and done as you said
C:\One_M8_All-In-One_Kit_v\Data>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.29.214500021.12G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 6.24.710.1
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno:
(bootloader) imei:
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B11000
(bootloader) cidnum: VODAP021
(bootloader) battery-status: good
(bootloader) battery-voltage: 0mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: 205bdca3
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.046s
Hope this helps
Thanks for posting the getvar data. Unfortunately, nothing there looks conspicuous (old firmware, certain troublesome M8 variants, etc.).
So from bootloader, you are able to select "recovery" and it just restarts to HTC logo screen (or bootloader screen)?
redpoint73 said:
Thanks for posting the getvar data. Unfortunately, nothing there looks conspicuous (old firmware, certain troublesome M8 variants, etc.).
So from bootloader, you are able to select "recovery" and it just restarts to HTC logo screen (or bootloader screen)?
Click to expand...
Click to collapse
Yeah it restarts and goes to the htc logo screen not bootloader.
MinionZee said:
Yeah it restarts and goes to the htc logo screen not bootloader.
Click to expand...
Click to collapse
Go back to bootloader, try fastboot erase cache, then try to install TWRP again (fastboot method). You can also try another TWRP build, such as one build older than the current (3.1.1-0). Or honestly, any build that is 2.8.7 or newer should be okay.
redpoint73 said:
Go back to bootloader, try fastboot erase cache, then try to install TWRP again (fastboot method). You can also try another TWRP build, such as one build older than the current (3.1.1-0). Or honestly, any build that is 2.8.7 or newer should be okay.
Click to expand...
Click to collapse
Tried it same thing happens, phone just reboots back in to white screen.
C:\One_M8_All-In-One_Kit_v\Data>fastboot erase cache
******** Did you mean to fastboot format this partition?
erasing 'cache'...
OKAY [ 0.074s]
finished. total time: 0.075s
C:\One_M8_All-In-One_Kit_v\Data>fastboot flash recovery C:\One_M8_All-In-One_Kit_v\Data\twrp-3.1.1-0-m8.img
target reported max download size of 1826373632 bytes
sending 'recovery' (20100 KB)...
OKAY [ 1.830s]
writing 'recovery'...
OKAY [ 0.726s]
finished. total time: 2.561s
C:\One_M8_All-In-One_Kit_v\Data>fastboot reboot
rebooting...
finished. total time: 0.011s
C:\One_M8_All-In-One_Kit_v\Data>
MinionZee said:
Tried it same thing happens, phone just reboots back in to white screen.
Click to expand...
Click to collapse
Hmmm, that is unfortunate. You may have corrupt data partition or even hardware emmc failure.
You might be able to format data without custom recovery, not sure how to do that (think I saw a thread on here at one time?).
Besides trying that, or keeping trying different TWRP versions, I'm not sure what else can be done.
Basically I tried to install TWRP from https://forum.xda-developers.com/razer-phone/how-to/razer-phone-android-9-0-pie-cheryl-p-t3974325
Long story short (I can give details if it helps). I got into fastboot and tried to switch slots and reboot recovery. Instead it rebooted and the message that my bootloader is unlocked is gone, just bootlooping on the android logo. I can get to fast boot and it shows I'm not on either slot:
(bootloader) unlocked:yes
(bootloader) off-mode-charge:1
(bootloader) charger-screen-enabled:1
(bootloader) battery-soc-ok:yes
(bootloader) battery-voltage:4077
(bootloader) version-baseband:
(bootloader) version-bootloader:
(bootloader) variant:MSM UFS
(bootloader) has-slot:modem:yes
(bootloader) has-slot:system:yes
(bootloader) current-slot:
(bootloader) has-slot:boot:yes
(bootloader) slot-retry-count:b:7
(bootloader) slot-unbootable:b:no
(bootloader) slot-successful:b:no
(bootloader) slot-retry-count:a:1
(bootloader) slot-unbootable:a:no
(bootloader) slot-successful:a:no
(bootloader) slot-count:2
(bootloader) slot-suffixes:_a,_b,
(bootloader) secure:yes
(bootloader) serialno:181801V00403118
(bootloader) product:cheryl
(bootloader) max-download-size:0x20000000
(bootloader) kernel:uefi
(bootloader) version:0.0
all:
Finished. Total time: 0.060s
I have no idea how to even just load TWRP and reflash the stock boot.img. (I'd like to preserve my phone data)
Any help would be greatly appreciated. Thank you very much.
If you can get into fastboot try to flask stock factory images and start over.
guillermohs9 said:
If you can get into fastboot try to flask stock factory images and start over.
Click to expand...
Click to collapse
I tried this:
fastboot flash boot twrp-3.2.2-0-cheryl.img && fastboot reboot
fastboot: error: Failed to identify current slot
Leprechaun7 said:
I tried this:
fastboot flash boot twrp-3.2.2-0-cheryl.img && fastboot reboot
fastboot: error: Failed to identify current slot
Click to expand...
Click to collapse
Download the stock image over at razer website. Unzipped the firmware and flash it using platform tool.
sinkoo1979 said:
Download the stock image over at razer website. Unzipped the firmware and flash it using platform tool.
Click to expand...
Click to collapse
Thanks for the help!! I ran flash_all.bat, some files wrote, some failed writes (I can post a long log, if that helps). I'm at least out of my latest dug hole, I can get to the bootloader screen. I'm still stuck at selecting a slot to do anything, still no slot selected. I guess that's the next step for me. I can't find anything about a phone with no slot selected. Any help from anyone would be appreciated.
Leprechaun7 said:
Thanks for the help!! I ran flash_all.bat, some files wrote, some failed writes (I can post a long log, if that helps). I'm at least out of my latest dug hole, I can get to the bootloader screen. I'm still stuck at selecting a slot to do anything, still no slot selected. I guess that's the next step for me. I can't find anything about a phone with no slot selected. Any help from anyone would be appreciated.
Click to expand...
Click to collapse
You should definitely post the log. I suppose you can attach it rather than flood the thread.
guillermohs9 said:
You should definitely post the log. I suppose you can attach it rather than flood the thread.
Click to expand...
Click to collapse
Here is the log (attached). Thanks!
Leprechaun7 said:
Here is the log (attached). Thanks!
Click to expand...
Click to collapse
Those are a lot of FAILED commands. I'm surprised it booted at all.
Did you issue the command
Code:
fastboot flashing unlock_critical
after
Code:
fastboot flashing unlock
?
guillermohs9 said:
Those are a lot of FAILED commands. I'm surprised it booted at all.
Did you issue the command
Code:
fastboot flashing unlock_critical
after
Code:
fastboot flashing unlock
?
Click to expand...
Click to collapse
No, I just ran flash_all.bat. I assume I should run those commands first then flash_all.bat?
My bootloader is already unlocked. Thanks for helping.
Leprechaun7 said:
Those are a lot of FAILED commands. I'm surprised it booted at all.
Did you issue the command after
No, I just ran flash_all.bat. I assume I should run those commands first then flash_all.bat?
My bootloader is already unlocked. Thanks for helping.
Click to expand...
Click to collapse
From the logs I'd say it's not fully unlocked. The 2 commands I quoted are necessary for that.
guillermohs9 said:
From the logs I'd say it's not fully unlocked. The 2 commands I quoted are necessary for that.
Click to expand...
Click to collapse
Good news: Thanks so much!, reunlocking the bootloader and then running flash_all.bat (2x, the first time didn't work right for some reason). It's back up and booting.
Bad news: I'm stuck at a "to start android enter your password" screen. I assume it's the pin to unlock the phone when you reboot. It doesn't seem to work. It might be a problem with the OS (https://www.reddit.com/r/razerphone/comments/bf7qes/restarted_phone_and_get_wrong_pin_when_prompted/)
I've tried all possible passwords I would have used, no luck. Now I've got limited attempts before the device wipes. Of course I think everything is wiped since I re-unlocked the bootloader and flash_all.bat
Leprechaun7 said:
Good news: Thanks so much!, reunlocking the bootloader and then running flash_all.bat (2x, the first time didn't work right for some reason). It's back up and booting.
Bad news: I'm stuck at a "to start android enter your password" screen. I assume it's the pin to unlock the phone when you reboot. It doesn't seem to work. It might be a problem with the OS (https://www.reddit.com/r/razerphone...arted_phone_and_get_wrong_pin_when_prompted/)
I've tried all possible passwords I would have used, no luck. Now I've got limited attempts before the device wipes. Of course I think everything is wiped since I re-unlocked the bootloader and flash_all.bat
Click to expand...
Click to collapse
Mm that doesn't sound right. The data partition should be formatted. There is a fastboot command to format user data. I don't know it by heart but it's on this forum.
guillermohs9 said:
Mm that doesn't sound right. The data partition should be formatted. There is a fastboot command to format user data. I don't know it by heart but it's on this forum.
Click to expand...
Click to collapse
um...cough..cough... I may have deleted the "%fastboot_cmd% erase userdata" command in a feeble attempt to save my data...
I'm guessing I should just pull the trigger on deleting my user data.
Leprechaun7 said:
um...cough..cough... I may have deleted the "%fastboot_cmd% erase userdata" command in a feeble attempt to save my data...
I'm guessing I should just pull the trigger on deleting my user data.
Click to expand...
Click to collapse
That may be it. Always back up first. Anyway, it may be worth the shot to try enter a PIN. Did you use a pattern or pin? You can translate a pattern to a PIN, it worked for me on recoveries on other devices...
When it asks for decryption by PIN and you've been using a pattern, I was able to "translate" pattern to pin using the following matrix:
1 2 3
4 5 6
7 8 9
So a diagonal line from bottom left to top right would translate to a pin "753" unless 5 is already used by another line in which case you'd go directly from 7 to 3.
guillermohs9 said:
That may be it. Always back up first. Anyway, it may be worth the shot to try enter a PIN. Did you use a pattern or pin? You can translate a pattern to a PIN, it worked for me on recoveries on other devices...
When it asks for decryption by PIN and you've been using a pattern, I was able to "translate" pattern to pin using the following matrix:
1 2 3
4 5 6
7 8 9
So a diagonal line from bottom left to top right would translate to a pin "753" unless 5 is already used by another line in which case you'd go directly from 7 to 3.
Click to expand...
Click to collapse
Thanks so much. I have a pin and have tried it many times, no luck. I actually bricked my phone in the first place trying to get TWRP and root (for Titanium Backup). I'm backup crazy. I might try to get TWRP working again and backup before I mess with the password anymore.
Leprechaun7 said:
Thanks so much. I have a pin and have tried it many times, no luck. I actually bricked my phone in the first place trying to get TWRP and root (for Titanium Backup). I'm backup crazy. I might try to get TWRP working again and backup before I mess with the password anymore.
Click to expand...
Click to collapse
Well, good luck. Last resort, flash_all without modifications and start from there.