Database Info

Possible Brick

Hey all,
So tonight I attempted to install the Unofficial AOKP Jelly Bean posted here: http://forum.xda-developers.com/showthread.php?t=1862156
Before doing that, I followed the instructions to Unlock, Recovery, and Root my One S here: http://forum.xda-developers.com/showthread.php?t=1583427
After following those instructions, I then followed the instructions for AOKP Jelly Bean however my sdcard couldn't be mounted and the phone was in a boot loop if I didn't boot into fastboot by holding down the volume - and power buttons.
I attempted these instructions below however I couldn't get a stock recovery flashed.
1) Use the All-in-One-Kit and flash your recovery back to stock
2) Boot into the bootloader and choose to "clear storage" and afterwards to reset to factory defaults.
3) Go back to the all-in-one-kit and flash a CWM recovery version again.
4) Reboot into recovery (CWM). Your /sdcard should now be mounted and visible.
5) Now, try the UTB rom (it worked for me), rename the zip file to something short (i.e. utb.zip), and push it to the sdcard using adb as follows:
Click to expand...
Click to collapse
Still caught in the reboot loop, I relocked and tried to run an RUU file found here: http://www.htconeforum.com/forum/ht...e-your-htc-one-s-back-100-stock-relocked.html
I was able to successfully re-lock the phone however every time I try to run the RUU file it comes back with an error about 3-5 minutes into the process.
At this point, my phone boots into fastboot. At the top I have "Tampered, Relocked, Security Warning." My HBOOT is 1.14.0004 and my Radios is 1.08ts.50.02.16
I would appreciate any help if there is a solution. Thank you for your time!
Update: Not sure if this is helpful or not, but whenever I try to do something with The All in one toolkit the cmd window says device not found. Also, when I try to boot into recovery from fastboot, I get a green downward and circular arrows before getting the red triangle and exclamation point.
Update: Running the RUU mentioned above fails at the Signature stage and the cmd prompt when trying to write recovery returns "signature verify fail"

Are you s4 or s3? what kind of computer you got? The drivers need to be installed. then read up how to use android SDK. Then retry to flash the stock recovery using the same steps in your quote.
Sent from my HTC One S using xda app-developers app

whozilla said:
Are you s4 or s3? what kind of computer you got? The drivers need to be installed. then read up how to use android SDK. Then retry to flash the stock recovery using the same steps in your quote.
Sent from my HTC One S using xda app-developers app
Click to expand...
Click to collapse
I am pretty sure I am S4 (tmobile USA). I am on a windows 7 home build, and the drivers should be installed (at least, I could use HTC sync before all of this). I'll definitely try again tonight. If anyone has any other suggestions they would be much appreciated!

Make sure HTC sync is NOT active on your pc. Try searching for the original version of one s all in one toolkit. It has the stock recovery. I'm pretty sure this unbrick method works for all hboot versions but don't take my word for it. Focus on your goal. Get stock recovery flashed. You can also try unlocking your boot loader again and using the all in one to reflash cwm. In some cases like mine. The unofficial cwm touch is the only successful flash I got. Ps. Try having your phone in fastboot. Plug in USB and see if it says "fastboot USB" then type your android SDK directory for your fastboot folder. For example open cmd
cd\
cd androidsdk\tools
androidsdk\tools fastboot devices.
Fastboot devices command will tell you if your drivers are working.
You can also type in adb devices instead of fastboot devices.
Hope this helps. But you probably already know this
Sent from my HTC One S using xda app-developers app

whozilla said:
Make sure HTC sync is NOT active on your pc. Try searching for the original version of one s all in one toolkit. It has the stock recovery. I'm pretty sure this unbrick method works for all hboot versions but don't take my word for it. Focus on your goal. Get stock recovery flashed. You can also try unlocking your boot loader again and using the all in one to reflash cwm. In some cases like mine. The unofficial cwm touch is the only successful flash I got. Ps. Try having your phone in fastboot. Plug in USB and see if it says "fastboot USB" then type your android SDK directory for your fastboot folder. For example open cmd
cd\
cd androidsdk\tools
androidsdk\tools fastboot devices.
Fastboot devices command will tell you if your drivers are working.
You can also type in adb devices instead of fastboot devices.
Hope this helps. But you probably already know this
Sent from my HTC One S using xda app-developers app
Click to expand...
Click to collapse
Thanks for the help!
Here are my results:
HTC Sync is not running. Fastboot devices returns a device ID so that seems good. When trying to flash a stock recovery (that I got on this forum somewhere, but can't remember where) it sends it ok but I still get "remote: signature verify fail"
I unlocked the device and flashed TWRP 2.2.2.0 with the all in one tool kit. This put me back into the boot loop mentioned above. Once I manually got back into the bootloader and selected recovery, I was able to get into the TWRP recovery. At this point, I am kind of worried about doing anything. I would like to be able to push AOKP Unofficial JB if at all possible. Any further guidance would be appreciated!

Please, please don't use the toolkit. It makes people find problems later on and not know a thing about what to do.
Sent from my locked, tampered ville
---------- Post added at 08:24 AM ---------- Previous post was at 08:23 AM ----------
Oh well, flash AOKP through TWRP and then reboot into bootloader and flash the boot.IMG.
Sent from my locked, tampered ville

usaff22 said:
Please, please don't use the toolkit. It makes people find problems later on and not know a thing about what to do.
Sent from my locked, tampered ville
---------- Post added at 08:24 AM ---------- Previous post was at 08:23 AM ----------
Oh well, flash AOKP through TWRP and then reboot into bootloader and flash the boot.IMG.
Sent from my locked, tampered ville
Click to expand...
Click to collapse
It is clear to me that I didn't do enough research before getting into this. I thought my experience with putting custom roms on my galaxy S (a phone I really disliked) would give me the appropriate background. Clearly I was wrong! I'm a little unsure how to flash AOKP through TWRP when AOKP is not on my SD card. In fact, when I look at the SD card in TWRP, the only file on it is "TWRP."
I think I need to flash TWRP 2.3.0 (rather than the 2.2.2.0 I have), because it supports ADB Sideload (talked about here on their site which I can't yet link to). Can I do that through the Android SDK like I have been doing? I don't need to do anything to the TWRP 2.2.2.0 before trying to flash 2.3.0 do I? It seems if I do that, I could send AOKP to my phone through adb when it is in recovery.
And just for my better understanding, what is different about flashing it in TWRP and then flashing the boot.img in fastboot?
Thanks again!

You have to fastboot push the AOKP zip through the bootloader I think.
Sent from my locked, tampered ville

Veritas327 said:
It is clear to fme that I didn't do enough research before getting into this. I thought my experience with putting custom roms on my galaxy S (a phone I really disliked) would give me the appropriate background. Clearly I was wrong! I'm a little unsure how to flash AOKP through TWRP when AOKP is not on my SD card. In fact, when I look at the SD card in TWRP, the only file on it is "TWRP."
I think I need to flash TWRP 2.3.0 (rather than the 2.2.2.0 I have), because it supports ADB Sideload (talked about here on their site which I can't yet link to). Can I do that through the Android SDK like I have been doing? I don't need to do anything to the TWRP 2.2.2.0 before trying to flash 2.3.0 do I? It seems if I do that, I could send AOKP to my phone through adb when it is in recovery.
And just for my better understanding, what is different about flashing it in TWRP and then flashing the boot.img in fastboot?
Thanks again!
Click to expand...
Click to collapse
Just like the post above mine says, you have to adb push the file onto the sd card. I'm not to familiar with TWRP (using it actually got me into a bit of a dilemma) so I only know the process for CWM. If TWRP is anything like CWM then you have to be in recovery to adb push and have sdcard and system set to "unmont". It's pretty easy and there's a couple threads explaining how to do it. The command basically is :: adb push romname.zip /sdcard/romname.zip:: Note the space before "/sdcard" I'dpn't know if this ill help you or if you've solved your problem already but this is just my 2 cents, good luck!

Sorry for my late reply; I was rushed to the ER last night in excruciating pain. Looks like I'll be dealing with a kidney stone over the next few days.
So far, I have tried to push AOKP through fastboot. ADB says "no devices found" and when I type adb devices, I get "List of devices attached" and nothing under it. However, when I type fastboot devices, I do get a device ID. As of now, I am downloading the TWRP 2.3 recovery and will try to sideload with adb with that.

Update:
I was able to successfully install TWRP 2.3 and adb sideload the AOKP zip file. The phone then went back into a reboot loop, and I was able to get into recovery to install the .zip. The phone then rebooted, showed the HTC with red text screen very briefly, went to black, showed the HTC with red text screen again, went black, and now the aokp boot animation is repeating over and over. It has been doing so for about 5-7 minutes. I haven't yet installed gapps as mentioned in the AOKP post (I'm honestly not even sure what that is). Where should I go from here?
As a side note, the phone is plugged into power though the LED is not lighting up. It was at 98% when I flashed the .zip, but I obviously don't want it to die on me. Should I turn the phone off or is it still charging?

Veritas327 said:
And just for my better understanding, what is different about flashing it in TWRP and then flashing the boot.img in fastboot?
Click to expand...
Click to collapse
The newer hboot versions (1.13 and up) don't let you flash boot images in recovery, even if it reports success.
So there is technically no difference, except fastboot always works and recovery depends on hboot version.
Did you fastboot flash the boot image that comes with your rom?
-Jobo
Edit to add: So it seems that following the recipe in your post #1 did in fact make your sdcard mountable again, or did you do something else as well for that?

Fixed!
I ended up flashing the boot.img with fastboot and then going into recovery, factory resetting and then re-installing the rom (and gapps which I now know stands for google apps). I'll be playing around with the ROM but at least I have a working phone again!
I think, in the end, it came down to my sd card not being mounted and my lack of knowledge about how to fix it.

Recovery is gone..?

hey guys,
i have a big problem. i bought a photon q 4g from ebay.
its with sim mod and had a unlocked bootloader (status code: 1)
so i readed some topics about using custom recovery and root for the phone and started
its not the first time i flashed a phone i already had droid2, droid3 and droid4
first i get stuck because fastboot was giving me a message of "variable not supported" & "download size to large"
but i found a mfastboot that flashed the recovery without a error message
so i restart the phone but the recovery not come up.
booting the system is no problem.
but when i wanne go in recovery (power+vol up, from bootloader, adb reboot recovery..) the phone restarts and boot up normal.
Moto boot logo->moto boot logo again->boot animation->system
i tryed to erase recovery and flashed again but the same happen.
tryed with cwm and twrp. maybe someone have the original 3e recovery.img?
and for what is the console option under APfastboot in the boot menu select?
someone know whats the difference between status code 1 & status code 3?
deleting userdata & cache with fastboot only reset the rom i have. :silly:

Status code 3 should be what you need. Maybe you should try unlocking it for yourself to make sure that it actually was unlocked. There are instructions for the full process from unlock to installing recovery to getting root in my signature if you need step-by-step.

Solust said:
Status code 3 should be what you need. Maybe you should try unlocking it for yourself to make sure that it actually was unlocked. There are instructions for the full process from unlock to installing recovery to getting root in my signature if you need step-by-step.
Click to expand...
Click to collapse
that was one of the first things i tryed but it not work. iam not sure what fastboot was saying (i`l look it up when iam at home) something like "no unlock data"
but when i start APfastboot it say "UNLOCKED status code:1" so its not locked.
but cant find information about the difference.
Edit: i see that i have no recovery-from-boot.p. someone know where i can get the correct one?
some more information: the phone run "AP Fastboot Flash Mode (NS) 10.97"
when i typed fastboot getvar all i saw
(bootloader) secure: no
(bootloader) mid: 0000
(bootloader) unlocked: notsupported
(bootloader) iswarrantyvoid: notsupported
the phone is running a not released test firmware with some apps that are not made for public i think.
there is a su in system/xbin and one app named TamperDetect(qualcomm app?)( only 2 button "get var" and "set var") say the phone is permanently rooted
but i installed superuser and it not work.
but other app called DockStatus(moto app?) let me make a adb over wifi with [email protected]_c: #
could that help me fixing my problem?

no one knows what wrong?

huhu1312 said:
no one knows what wrong?
Click to expand...
Click to collapse
I would try giving Motorola a call and see if they can help you. I would think they would at least be able to tell you the difference between the status codes, though who knows if they could get it unlocked for you or not.

no here is no good support in germany
and i read status code 1 = developer device
and why should it be locked if the phone say unlocked?

Why don't you go into the Bootloader menu and try it from this point into the recovery?
VOL_UP+VOL_DOWN+POWER

Loader009 said:
Why don't you go into the Bootloader menu and try it from this point into the recovery?
VOL_UP+VOL_DOWN+POWER
Click to expand...
Click to collapse
if u read my first post correct u will see i tryed and it not work..

Argh, sorry, I only read the first (key-combination) and overread the bootloader and adb.
My Bootloader version is 10.9B.
But my first Line shows "AP Fastboot Flash Mode (S)" instead of (NS).
You should try to contact the american Motorola support...
At least you should try to get some help from them.
I think because you got a developer device, it is slightly different with the partition sizes.
edit: What is with OTA updates on Stock ROM?

i found out S stand for secure NS for non secure

Please try "adb shell" and then "su", do you get a "Permission denied"?
If that works, you should be able to remount the /system partition to rw.
This way you should also be able to install superusers su, somehow... (sorry, never installed it that way)
But this won't help you in your situation.
Please backup your /system, before you make a custom firmware on it (if you'll ever have success).
Those test apps might be interesting.
As you already tried to flash a custom recovery, I assume that the "stock" (or test) recovery is already gone.
My thought is to bring your Bootloader up to date. But I'm not sure, if that would brick your device.
I'm also not sure, if Motorola America will be helpfull with a developer device in your hands.
But without a (valid) sbf flash file you won't be able to flash the appropriate firmware. I haven't seen any official sbf file for our Photon Q.
Theoretically I would say, that you could also try to flash a FXZ file, but it could also brick your device. (Please don't forget to backup /system)
http://forum.xda-developers.com/showthread.php?t=2095536

i know that flashing all can brick the phone thats why i not test it for now.
and yes the root via adb work.
i only found 1 guy in the internet with the same problem like me. he said it was fixed when he flashed a older recovery from GB but is there a old recovery img like this? (this guy had an other phone)

I saw somewhere a stock recovery (that's how I made my OTA Updates).
I still got it, but I prefer to find an uploaded one.
recovery.img 10MiB
CRC32 386A247D
MD5 46CB664521F98B1C1987C288A101A5EC
If you (or I) won't find it, I'll upload it.
Edit: Found it -> http://forum.xda-developers.com/showthread.php?t=2333094
Another one -> http://forum.xda-developers.com/showthread.php?t=1856456

thanks but this files i tryed already;/
i only made a copy of /system/ folder for now
i flashed all with rsd lite 6.1.4 now. and it worked

[Q] Unlocked, reflashed, app ran into problem phone restarted and bricked?

Hi there,
Im still kinda a noob with android...
but i managed to unlock my htc sensation trough the steps @HTC,
changed the recovery, tried to flash a rom.
it failed due to my phone not being S-off. so i flashed it back :/
no problem there i thought just a rooted htc.
downloaded an app to remove bloat. and all seemed fine...
I was playing Clash of Clans, and it gave a message that the Google play services stopped and the phone rebooted.
when booted the lock screen was frozen, i pulled out the battery to find out my phone is unresponsive..
When i connect to windows 8, it cant recognize my phone at all
When i connect it to a charger i dont see the charging light.
and the worse thing is.. i cant get into the recovery.
any idea's what i can try?
i checked out the [unbrick] tread but i cant seem to figure out which "Package" i need and the links on the bottom of the page dont work when i click them
Thanks in advance
-Aline

At first you have not to be S-OFF in order to flash a rom.
Your rom will get installed just fine.You just need to flash the kernel of your rom manually through fastboot using the command fastboot flash boot boot.img.
What exactly do you mean by telling "so i flashed it back"?
Did you relocked your bootloader with fastboot oem lock and you flashed an RUU?
You said you are just rooted.If my theory was right you probably unlocked your bootloader again by flashing the unlock.bin and a cwm recovery and then you had to use a (Superuser , SuperSU zip).
The first time you unlocked your device was you using the same computer with windows 8?
If yes this is a problem.Check your device manager for unrecognised devices.Can you see the device?
Check this out.You can also check this.
(You can try with win7 or a linux destribution instead.)
Are you still able to boot into bootloader (hboot) using (Power)+(Vol-) Buttons?
If you have enabled usb-debugging and a working adb shell despite you are in a bootloop you can try:
Code:
adb shell
su ------>(If you don't see # instead of $)
reboot oem-78 -------> To get in RUU mode
or
reboot bootloader -------->(To reboot into hboot)
* reboot recovery could bring you to recovery *
If you can get into hboot or RUU mode give the command fastboot getvar all and copy-paste what it prints.

I know it was possible to flash with S-on,
thats what i tried and it failed (manually flashed the boot.img resulted in a bootloop)
so i flashed back to the "stock" rom.
resulting in a "normal" rooted device
since i've replaced my recovery and got root access
it never has been oem locked again.(still isnt)
i cant get into my bootloader/ruu mode. nor start up.
when i plug it into my computer (windows 8) it makes the sound as it does when you connect a device.
but in device manager it shows nothing, not even a yellow ! as it normally would if it can recognize a device.

aline1996 said:
I know it was possible to flash with S-on,
thats what i tried and it failed (manually flashed the boot.img resulted in a bootloop)
so i flashed back to the "stock" rom.
resulting in a "normal" rooted device
since i've replaced my recovery and got root access
it never has been oem locked again.(still isnt)
i cant get into my bootloader/ruu mode. nor start up.
when i plug it into my computer (windows 8) it makes the sound as it does when you connect a device.
but in device manager it shows nothing, not even a yellow ! as it normally would if it can recognize a device.
Click to expand...
Click to collapse
As you have not access to bootloader but your device is still seems to get connected i think you can only try HTC Unbricking Project.If the brickdetect.sh is not working you can try a different linux destribution.

Gatosbil said:
As you have not access to bootloader but your device is still seems to get connected i think you can only try HTC Unbricking Project.If the brickdetect.sh is not working you can try a different linux destribution.
Click to expand...
Click to collapse
Well, i just wonder which package i need, tried the links at the bottom of the post but those are no longer valid :/

aline1996 said:
Well, i just wonder which package i need, tried the links at the bottom of the post but those are no longer valid :/
Click to expand...
Click to collapse
Oups!I downloaded those packages some days before and I didn't see the links are broken now.
You can download them from the attachments here.
For Sensation and Sensation 4G

Gatosbil said:
Oups!I downloaded those packages some days before and I didn't see the links are broken now.
You can download them from the attachments here.
For Sensation and Sensation 4G
Click to expand...
Click to collapse
Well im afraid my phone is offically dead
this is what i get when i use ./brickdetect
[email protected]:/media/sdc$ ./brickdetect.sh
Searching for bricked device...
Device can't be detected. Check connections
[email protected]:/media/sdc$
please tell me i did something wrong xD
edit:
after some digging in knoppix i did find this:
http://imgur.com/DR7T4QK

[Q] htc one sv soft bricked :/

Hi everybody !
I think i'm in the right section to expose you my problem, and no one on this forum had been confronted to such fails ! but i'm new in this forum to write threads (altough i already read many of them)
i'll try to be quick :
a year ago i bought a htc one sv , i unlocked the bootloader and then i stopped because i was with windows 8 and it was boring with usb 3.0 (i can use windows 7 right now..!). then i got some problems with "android.phone", or android.process.media" stopped et i believed my phone dead, but i learned things, installed the TWRP recovery 2.7.0.1 and flashed therom stock odexed jelly bean which allowed me to get back to stock my phone! (the twrp was with the root (or the rom odexed...) so i became rooted! but when i updates the superuser app few months ago, i got problems of binaries so i didn't install the last supersu app update (2/3 weeks ago). unfortunately,2 weeks ago, my phone did a reboot in the night (which awoke me) but in a bootloop...
First i tried factory reset then clean storage du bootloader, but it did nothing.
at the beginning i could not acceed to the recovery, but, lucky i am, a boot in fastboot usb and now from the phone, i can go to my recovery twrp 2.7.0.1 -or 2.8.4.0 by boot fastboot usb) however, TWRP shows "no os installed"it s been 2 weeks that i'm searching, but without results... that's why i'm asking here to the best in android world ^^
the things that i already tried without results:
flash the same zip odexed from recovery and from fastboot usb
flash hboot, but i'm s-on
update recovery ( i only can boot by fastboot usb)
flash rom custom venom with the installer in the rom
find files for sdcard "pl80diag.zip et nbh et pl80img.zip et nbh"
but i'm S-on and can't be S-off, the process with moonshine stopp when the devices has to boot...
i also tried adb sideload and simple adb with the phone in recovery recovery but:
recovery is unable to mount internal storage partitions (unable to mount int-sd, etc............)
my phone shows "tampered" "unlocked" and "s-on" hboot "2.00.000".. ask for more...
from now on, when i boot the phne i don't have any more bootloop, i'm directly in the hboot..!
i tried extract rom.zip from RUU.exe of ICS but i didn't used it...
so i'm wondering if there is a way to unbrick this soft bricked devices 'casue i already tried all of the unbrick things for soft brick but the partitions being unable to mount killed all my tries... i hope i gave you many informations ! all the suggestions and ideas are welcome!
(i can't find nbh files..)
thanks for reading this busy text, i'm a bit bored of using a very old phone in remplacement if i can repair my lover htc..!
i trust you people i'll check and answer suggestions asap!

Well, you are S-on, there is not much you can do.
Flash twrp recovery 2.7.x or 2.8.x and try to flash a rom for your device model.
Don't forget to do a full wipe in twrp and to flash the boot.img of the rom you are using with fastboot.

old.splatterhand said:
Well, you are S-on, there is not much you can do.
Flash twrp recovery 2.7.x or 2.8.x and try to flash a rom for your device model.
Don't forget to do a full wipe in twrp and to flash the boot.img of the rom you are using with fastboot.
Click to expand...
Click to collapse
it that i was thinking... i already try this (i have already twrp without booting in fastboot or flashing) but the fact is : twrp cannot mount any partitions so the step "writing" is impossible.. even the wipe fails..

If i remember right, in TWRP 2.8, under Wipe - Advanced there must be a button "Repair broken filesystem".
Not sure if this is working on SV, but it is worth a try i think.
What version of this phone do you own?

old.splatterhand said:
If i remember right, in TWRP 2.8, under Wipe - Advanced there must be a button "Repair broken filesystem".
Not sure if this is working on SV, but it is worth a try i think.
What version of this phone do you own?
Click to expand...
Click to collapse
yep you're right i'v already try it on every partitions but i'll do it again !
i've got the K2_UL (i'm french) and it was on 4.2.2 JB.
by the way, thanks for your answers

guess who's back
old.splatterhand said:
If i remember right, in TWRP 2.8, under Wipe - Advanced there must be a button "Repair broken filesystem".
Not sure if this is working on SV, but it is worth a try i think.
What version of this phone do you own?
Click to expand...
Click to collapse
hey guys, it's been a while but i was searching during all this time. I've experienced some things with adb shell and what i saw :
my partitions are messed up, not annihilated, but messed up. 2 reasons : partitions can't be mounted in the last recovery of TWRP, and when i use Fdisk -l /dev/block/mmcblk0 and the partition table of mmcblk0 and what I see is that my partitions table are not in disk order. My partitions are overlapping.. Perhaps it will help. I tried some ext2fd and mkfs.ext4 but it as not worked properly... maybe you have ideas... because it's been about months that my phone is useless and a paperweight.
by the way on my computer under windows 10, my phone used to be in qhsus_dload..! perhaps there are issues with that!
Thanks.

colton49 said:
hey guys, it's been a while but i was searching during all this time. I've experienced some things with adb shell and what i saw :
my partitions are messed up, not annihilated, but messed up. 2 reasons : partitions can't be mounted in the last recovery of TWRP, and when i use Fdisk -l /dev/block/mmcblk0 and the partition table of mmcblk0 and what I see is that my partitions table are not in disk order. My partitions are overlapping.. Perhaps it will help. I tried some ext2fd and mkfs.ext4 but it as not worked properly... maybe you have ideas... because it's been about months that my phone is useless and a paperweight.
by the way on my computer under windows 10, my phone used to be in qhsus_dload..! perhaps there are issues with that!
Thanks.
Click to expand...
Click to collapse
Which K2 variant do you have?
Sent from my C525c using Tapatalk

SHM said:
Which K2 variant do you have?
Sent from my C525c using Tapatalk
Click to expand...
Click to collapse
K2_UL, but I am at a point that each try worths it.. even with other K2!
moreover I've got a full stock backup of K2_UL but it didn't work with TWRP when I tried
. from now on i have no more ideas.. ^^

colton49 said:
K2_UL, but I am at a point that each try worths it.. even with other K2!
moreover I've got a full stock backup of K2_UL but it didn't work with TWRP when I tried
. from now on i have no more ideas.. ^^
Click to expand...
Click to collapse
You need an RUU to fix you up.
http://androidruu.com/getdownload.p...0.14_2_10.49.40.11L_release_301902_signed.exe
Sent from my C525c using Tapatalk

SHM said:
You need an RUU to fix you up.
http://androidruu.com/getdownload.p...0.14_2_10.49.40.11L_release_301902_signed.exe
Sent from my C525c using Tapatalk
Click to expand...
Click to collapse
ha
I've already tried but when it as to be detected, nothing occured, but i'll try again.. do you think that could be restore my phone ( ave you read my first explanation message,)

colton49 said:
ha
I've already tried but when it as to be detected, nothing occured, but i'll try again.. do you think that could be restore my phone ( ave you read my first explanation message,)
Click to expand...
Click to collapse
Well if you can extract the RUU from the .exe program then you can boot to your hboot then select fastboot from the screen. Plug device to your pc then enter:
Confirm pc reads phone and displays serial number before proceeding...
Code:
fastboot devices
Code:
fastboot oem rebootRUU
Code:
fastboot flash zip RUU.zip
If terminal shows it has completed successfully then reboot:
Code:
fastboot reboot
If terminal shows it didn't complete successfully then do not reboot but try again:
Code:
fastboot flash zip RUU.zip
I went through this last weekend for my K2CL because I was converting my device to f2fs and messed up in the process.
Sent from my C525c using Tapatalk

SHM said:
Well if you can extract the RUU from the .exe program then you can boot to your hboot then select fastboot from the screen. Plug device to your pc then enter:
Confirm pc reads phone and displays serial number before proceeding...
Code:
fastboot devices
Code:
fastboot oem rebootRUU
Code:
fastboot flash zip RUU.zip
If terminal shows it has completed successfully then reboot:
Code:
fastboot reboot
If terminal shows it didn't complete successfully then do not reboot but try again:
Code:
fastboot flash zip RUU.zip
I went through this last weekend for my K2CL because I was converting my device to f2fs and messed up in the process.
Sent from my C525c using Tapatalk
Click to expand...
Click to collapse
OK well i'll use my computer under windows 7, but i know that when i extract the ruu from the .exe (using the folder temp, you know) the file can't be flash with recovery but i'll give a try with fastboot (fastboot devices always work) if this can work you'll be my heroe haha because i've tried so many things with the adb shell the recoveries, the flash with fastboot (which taught me some things about android) but nothing worked!

colton49 said:
OK well i'll use my computer under windows 7, but i know that when i extract the ruu from the .exe (using the folder temp, you know) the file can't be flash with recovery but i'll give a try with fastboot (fastboot devices always work) if this can work you'll be my heroe haha because i've tried so many things with the adb shell the recoveries, the flash with fastboot (which taught me some things about android) but nothing worked!
Click to expand...
Click to collapse
Yea, the RUU extracted is not made to be flashed in the custom recovery or any recovery for that matter. Must be flashed with the device in RUU mode as instructed in my last comment. If you are S-On then make sure you relock the bootloader first before doing it. If you are S-Off then it does not matter. It will fix your device. Like I said, I borked my partitions last weekend and the RUU fixed it right up for me with no problems. However, I used a decrypted RUU but the process is still the same.
Sent from my C525c using Tapatalk

SHM said:
Yea, the RUU extracted is not made to be flashed in the custom recovery or any recovery for that matter. Must be flashed with the device in RUU mode as instructed in my last comment. If you are S-On then make sure you relock the bootloader first before doing it. If you are S-Off then it does not matter. It will fix your device. Like I said, I borked my partitions last weekend and the RUU fixed it right up for me with no problems. However, I used a decrypted RUU but the process is still the same.
Sent from my C525c using Tapatalk
Click to expand...
Click to collapse
okay thanks i'm gonna try this again and again if it does not work at the first shot! yes i'm S-ON and Unlocked.. ! okay you give me hope !!
i'll tell you if i succeed

SHM said:
Yea, the RUU extracted is not made to be flashed in the custom recovery or any recovery for that matter. Must be flashed with the device in RUU mode as instructed in my last comment. If you are S-On then make sure you relock the bootloader first before doing it. If you are S-Off then it does not matter. It will fix your device. Like I said, I borked my partitions last weekend and the RUU fixed it right up for me with no problems. However, I used a decrypted RUU but the process is still the same.
Sent from my C525c using Tapatalk
Click to expand...
Click to collapse
to decrypt the RUU You use smthing on Ubuntu right ? or you tried something else because i guess it's better when decrypted

colton49 said:
to decrypt the RUU You use smthing on Ubuntu right ? or you tried something else because i guess it's better when decrypted
Click to expand...
Click to collapse
On linux in general and decrypting the RUU is way more complicated and difficult than it sounds. An encrypted RUU will do you just fine.
Sent from my C525c using Tapatalk

SHM said:
On linux in general and decrypting the RUU is way more complicated and difficult than it sounds. An encrypted RUU will do you just fine.
Sent from my C525c using Tapatalk
Click to expand...
Click to collapse
ok i'll try with the encrypted and if it doesn't work after many tries i'll try to decrypt it! i'm gonna try all of this right now ! just have to remember where extract the ruu

SHM said:
On linux in general and decrypting the RUU is way more complicated and difficult than it sounds. An encrypted RUU will do you just fine.
Sent from my C525c using Tapatalk
Click to expand...
Click to collapse
I've got a huge pb, it seems that i can't relock my bootloader and well i'm s-on...
because fastboot oem lockfail
even htc bootloader unlock fails when i put the phone in a recovery to be recognized.. ****.. but if i can lock it it'll work..

colton49 said:
I've got a huge pb, it seems that i can't relock my bootloader and well i'm s-on...
because fastboot oem lockfail
even htc bootloader unlock fails when i put the phone in a recovery to be recognized.. ****.. but if i can lock it it'll work..
Click to expand...
Click to collapse
What do you mean by putting the phone in "recovery"? You shouldn't be in your recovery when using fastboot. You should be in your bootloader. Power off device, then press and hold the volume down key and the power key. Release when you see your hboot appear. Using your volume keys to move up and down you want to highlight the option, fastboot. Hit the power button to select fastboot. You are now in fastboot mode. You will see fastboot in red text. Plug your device into your pc and you should now see, fastboot usb, in red text. Using the terminal on your pc proceed to lock your bootloader using fastboot. Then proceed with my instructions in the other post.
Sent from my C525c using Tapatalk

SHM said:
What do you mean by putting the phone in "recovery"? You shouldn't be in your recovery when using fastboot. You should be in your bootloader. Power off device, then press and hold the volume down key and the power key. Release when you see your hboot appear. Using your volume keys to move up and down you want to highlight the option, fastboot. Hit the power button to select fastboot. You are now in fastboot mode. You will see fastboot in red text. Plug your device into your pc and you should now see, fastboot usb, in red text. Using the terminal on your pc proceed to lock your bootloader using fastboot. Then proceed with my instructions in the other post.
Sent from my C525c using Tapatalk
Click to expand...
Click to collapse
yeah of course i did it. Being in the recovery was just a try with a toolkit which is used to relock.
i know how fastboot works but i've got error messages with fastboot oem lock and by flashing the ruu the last thing after the signature checking fails because of my bootloader unlocked i guess.

Trying to flash TRWP Moto Z recovery - not working

Hey everyone, longtime lurker here finally going to try to get involved more since I just got a new Moto Z and I don't have much of a background with motorola hardware/software. I'm trying to flash recoveries through fastboot and I can't seem to get it working. I'm probably going to wait a while before I try again since there is not much support for the moto z yet. I am running MPL24.246-45 v6.0.1 XT1650-03, I have unlocked the bootloader through the instructions on the motorola website.
On the bootloader screen I can confirm it is now unlocked, but everytime I flash the TRWP recovery through fastboot I get the error message: "<bootloader> img not working or corrupt". I am trying to flash the most recent twrp recoveries for moto Z (twrp-3.0.2-0-griffin.img) but wasn't able to successfully flash it.
Coming from a samsung background, I might be skipping a step or doing something wrong. I am running the bell canadian firmware. Since I messed up my partitions on my last phone I want to be careful with this one, I mostly want to figure out why I am getting this error while trying to flash the recovery when
my bootloader is unlocked and when I check "adb devices" my moto is being read.
Thanks!!
szork

spacezork said:
Hey everyone, longtime lurker here finally going to try to get involved more since I just got a new Moto Z and I don't have much of a background with motorola hardware/software. I'm trying to flash recoveries through fastboot and I can't seem to get it working. I'm probably going to wait a while before I try again since there is not much support for the moto z yet. I am running MPL24.246-45 v6.0.1 XT1650-03, I have unlocked the bootloader through the instructions on the motorola website.
On the bootloader screen I can confirm it is now unlocked, but everytime I flash the TRWP recovery through fastboot I get the error message: "<bootloader> img not working or corrupt". I am trying to flash the most recent twrp recoveries for moto Z (twrp-3.0.2-0-griffin.img) but wasn't able to successfully flash it.
Coming from a samsung background, I might be skipping a step or doing something wrong. I am running the bell canadian firmware. Since I messed up my partitions on my last phone I want to be careful with this one, I mostly want to figure out why I am getting this error while trying to flash the recovery when
my bootloader is unlocked and when I check "adb devices" my moto is being read.
Thanks!!
szork
Click to expand...
Click to collapse
didn't try it yet, but did you try renaming it to recovery.img (if on windows be sure extenstions are shown so it is not actually recovery.img.img) and run (didn't see which command you are using:
Code:
fastboot flash recovery recovery.img
but search around forums about encryption thing and similar

the ljubich said:
didn't try it yet, but did you try renaming it to recovery.img (if on windows be sure extenstions are shown so it is not actually recovery.img.img) and run (didn't see which command you are using:
Code:
fastboot flash recovery recovery.img
but search around forums about encryption thing and similar
Click to expand...
Click to collapse
I've tried both with the original twrp name and extension as well as with renaming it to recovery.img, didn't seem to make a difference. If I am connection to the device itself does that mean that adb/sideload is installed properly? I mean I was able to unlocked the bootloader so I would assume so.
szork

spacezork said:
I've tried both with the original twrp name and extension as well as with renaming it to recovery.img, didn't seem to make a difference. If I am connection to the device itself does that mean that adb/sideload is installed properly? I mean I was able to unlocked the bootloader so I would assume so.
szork
Click to expand...
Click to collapse
i really don't know then.. if you successfully unlocked bootloader then fastboot should be ok. you can check in device manager. it should be bootloader iterface not adb interface there (you got me confused with mentioning adb so I am just writing to be sure).
also check if your device is shown when typing
Code:
fastboot devices
or try redownloading twrp.
otherwise I am out of ideas, sorry.

the ljubich said:
i really don't know then.. if you successfully unlocked bootloader then fastboot should be ok. you can check in device manager. it should be bootloader iterface not adb interface there (you got me confused with mentioning adb so I am just writing to be sure).
also check if your device is shown when typing
Code:
fastboot devices
or try redownloading twrp.
otherwise I am out of ideas, sorry.
Click to expand...
Click to collapse
Sorry for my confusion with adb/sideload - from what I understand I need both to be able to connect to my device (correct me if im wrong). In the bootloader menu I see "flashing_unlocked" which I believe confirms my bootloader being unlocked, but then at the top of the text right under the dead android guy I see "AP Fastboot Flash Mode (Secure)" could that be an issue?
I can retry downloading the recovery from the TWRP site, but I know I'm downloading the official one already, just can't put my finger on why I'm getting that error message if others are doing it successfully.
thanks for helping :good:

Do you have the Verizon model?

samwathegreat said:
Do you have the Verizon model?
Click to expand...
Click to collapse
I have the canadian BELL model XT1650-03

spacezork said:
I have the canadian BELL model XT1650-03
Click to expand...
Click to collapse
You're at the bootloader, it says Flashing Unlock so yes your bootloader is unlocked and you should be able to flash TWRP no problem.
Did you recently install this .45 firmware? Are you sure that TWRP wasnt actually flashed? I see lots of errors like this from the bootloader and its usually just rubbish.

The twrp does not show the actual memory value of my cell phone and does not let me paste ROM backup, from insufficient memory? how to support it?

I updated my phone to .45 when I bought the phone I believe 1-2 weeks ago, it's definitely NOT flashed as the flashing process runs for 0.2 seconds and fails. I can even boot in the stock recovery afterwards confirming that nothing flashed. I wish I knew what I was doing wrong? possibility of drivers not installed properly?
Before I try and flash recovery I check USB debugging, OEM is unlocked, don't verify ADB files and accept Unknown sources. Is there anything I'm missing?

What if fastboot boot twrpname.img
It's really weird anyway...

enetec said:
What if fastboot boot twrpname.img
It's really weird anyway...
Click to expand...
Click to collapse
I've been doing fastboot flash twrpname.img after opening cmd terminal with SHIFT-MOUSE2 in the designated folder. I have not tried that command specifically what's the difference between doing fastboot flash/boot as far as flashing a recovery.img
edit: I've read on different articles that people sometimes try and flash from the recovery menu? I understood it has to be while your are on the bootloader screen, could it be something to do with that? Or is it still a possibility the drivers may not be installed properly.

spacezork said:
I've been doing fastboot flash twrpname.img after opening cmd terminal with SHIFT-MOUSE2 in the designated folder. I have not tried that command specifically what's the difference between doing fastboot flash/boot as far as flashing a recovery.img
edit: I've read on different articles that people sometimes try and flash from the recovery menu? I understood it has to be while your are on the bootloader screen, could it be something to do with that? Or is it still a possibility the drivers may not be installed properly.
Click to expand...
Click to collapse
With fastboot boot you send recovery to your phone and ask it to boot on it without really flashing it...
It's useful e.g. to take a full stock backup including original recovery, to test a recovery prior to flash it or to use TWRP to root BUT remain on stock recovery...
Not on all phones it works, but on Moto Z should....
P.S.: you have to be on fastboot screen not on recovery when flashing...

enetec said:
With fastboot boot you send recovery to your phone and ask it to boot on it without really flashing it...
It's useful e.g. to take a full stock backup including original recovery, to test a recovery prior to flash it or to use TWRP to root BUT remain on stock recovery...
Not on all phones it works, but on Moto Z should....
P.S.: you have to be on fastboot screen not on recovery when flashing...
Click to expand...
Click to collapse
by fastboot screen you mean the bootloader menu right?
I've been accessing cmd from designated folder with .img file in it
- adb fastboot recovery
- fastboot flash recovery.img..
and I get the "img not working or corrupt" after it tries to flash it (lasts 0.2 seconds) and nothing is done.

spacezork said:
by fastboot screen you mean the bootloader menu right?
I've been accessing cmd from designated folder with .img file in it
- adb fastboot recovery
- fastboot flash recovery.img..
and I get the "img not working or corrupt" after it tries to flash it (lasts 0.2 seconds) and nothing is done.
Click to expand...
Click to collapse
Right, bootloader screen. Enter on it by key-comb... not by command...
Even the real flash take same time... Sending seems to work, is something on verify that doesn't "like" it...
Try to download again recovery and/or check its MD5...

if reading correctly (and what I told you yesterday) command is
fastboot flash recovery recovery.img
and not
fastboot flash recovery.img

hi can any one help me i need to get back to stock and lock boot loader to update i have eu any one please ???????????

Troll amiga said:
hi can any one help me i need to get back to stock and lock boot loader to update i have eu any one please ???????????
Click to expand...
Click to collapse
try following this instructions: http://forum.xda-developers.com/showpost.php?p=69065373&postcount=14
and download eu rom from here: https://mirrors.lolinet.com/firmware/moto/griffin/official/RETEU/
i don't know from which ROM you are coming, don't know if downgrading works, but this was onl RETEU ROM i could find.

I have the exact same phone and I've upgraded to Nougat but I got my TWRP working. You need an unlocked bootloader and after upgrading to nougat, the option "unlock OEM" need to be enabled again.
I've used this TWRP : https://dl.twrp.me/griffin/twrp-3.0.2-0-griffin.img.html
Also I tried to only boot on it at first with the command fastboot boot twrp.img then I saw it was working, I flashed it with fastboot flash recovery twrp.img but got the error : (bootloader) image not signed or corrupt . But I booted the recovery from the bootloader and TWRP was working even with this error.

cilk said:
...I flashed it with fastboot flash recovery twrp.img but got the error : (bootloader) image not signed or corrupt . But I booted the recovery from the bootloader and TWRP was working even with this error.
Click to expand...
Click to collapse
Yeessss... I don't know how could I forgot it!!! :silly:
The message (I forgot I received too...) is *only* to indicate that recovery is not signed! But before there is a clear "Done" confirming the flash!
Just boot on it!