Related
Hi i have rooted and flashed the phone it got stuck on the htc screen so i tried factory reset bad idea now my phone will just go into the bootlader menu i can enable fastboot usb but it dont show up on computer but the computer makes a noise to say ive connected it i cant enable usb debugging because the phone wont come on i have tried to flash another boot img through fastboot with no luck im hoping its not bricked
please any help would be appreciated thanks
pl4yb0y78 said:
Hi i have rooted and flashed the phone it got stuck on the htc screen so i tried factory reset bad idea now my phone will just go into the bootlader menu i can enable fastboot usb but it dont show up on computer but the computer makes a noise to say ive connected it i cant enable usb debugging because the phone wont come on i have tried to flash another boot img through fastboot with no luck im hoping its not bricked
please any help would be appreciated thanks
Click to expand...
Click to collapse
Hmm. so you probably need to flash a recovery first.
then you will be able to use the recovery to mount usb and put a new rom on your "sd card"
Then you can flash the rom on your new recovery and don't forget to fastboot flash the boot.img.
edit: the all in one toolkit is great for things like this. It will put a new recovery on your phone with just a click of the button.
http://forum.xda-developers.com/showthread.php?t=1604677
tivofool said:
Hmm. so you probably need to flash a recovery first.
then you will be able to use the recovery to mount usb and put a new rom on your "sd card"
Then you can flash the rom on your new recovery and don't forget to fastboot flash the boot.img.
Click to expand...
Click to collapse
Thanks for the reply but i dont know how to do this ?
could you please explain it ?
pl4yb0y78 said:
Thanks for the reply but i dont know how to do this ?
could you please explain it ?
Click to expand...
Click to collapse
I just edited my original post. just in case you didn't know how. I guess I was a little slow.
Also I can't remember if a bootloader factory reset relocked your phone but you might want to check that too. up on top it would say locked or relocked. If it still says unlocked you don't have to do that step again. Like you did when you first rooted the phone.
(all in one tool kit is great for unlocking and relocking too) just put a copy of that bin file in all in one tool kit (data file i believe, but it says what to do in that thread)
tivofool said:
I just edited my original post. just in case you didn't know how. I guess I was a little slow.
Also I can't remember if a bootloader factory reset relocked your phone but you might want to check that too. up on top it would say locked or relocked. If it still says unlocked you don't have to do that step again. Like you did when you first rooted the phone.
(all in one tool kit is great for unlocking and relocking too) just put a copy of that bin file in all in one tool kit (data file i believe, but it says what to do in that thread)
Click to expand...
Click to collapse
hi i have got the tool kit run twrp s3 now i have a black htc logo screen on what next
pl4yb0y78 said:
hi i have got the tool kit run twrp s3 now i have a black htc logo screen on what next
Click to expand...
Click to collapse
Your phone is an s3?
My phone is an S4 as are I would guess the majority of users. I think the s3 is the international version. If you are on T mobile then it's a s4.
Ok,,,
so .... if your phone is an s3 version then you will have to check that the Rom you download is specific for your phone as most of the Roms on this site are for the s4 version.
you need to go to your recovery. press the volume down button and hold it. Then press the power button (don't hold it). That will get you to recovery.
when in twrp recovery you will see a mounts button. hit that then the next screen will have mount usb. then you will be able to move a rom you downloaded on your computer to your phone.
then you can install the rom zip in twrp.
then from your computer, I assume you know how to flash a boot.img
put a boot.img in your fastboot folder, open up a comand prompt.
fastboot flash boot boot.img
if you wanted a different recovery than you are using, find the download the recovery. *I would rename the recovery to recovery.img
fastboot flash recovery recovery.img
(I only mention a different recovery because in some of the Rom threads you might read that you can only install a particular rom with an older version of twrp.)
I'm not sure of your skill or experience with all of this. If you are very new to it (then you are probably really frustrated) have no fear there is a little bit to learn but not that much. Just keep reading the development thread and the guides in it.
tivofool said:
Your phone is an s3?
My phone is an S4 as are I would guess the majority of users. I think the s3 is the international version. If you are on T mobile then it's a s4.
Ok,,,
so .... if your phone is an s3 version then you will have to check that the Rom you download is specific for your phone as most of the Roms on this site are for the s4 version.
you need to go to your recovery. press the volume down button and hold it. Then press the power button (don't hold it). That will get you to recovery.
when in twrp recovery you will see a mounts button. hit that then the next screen will have mount usb. then you will be able to move a rom you downloaded on your computer to your phone.
then you can install the rom zip in twrp.
then from your computer, I assume you know how to flash a boot.img
put a boot.img in your fastboot folder, open up a comand prompt.
fastboot flash boot boot.img
if you wanted a different recovery than you are using, find the download the recovery. *I would rename the recovery to recovery.img
fastboot flash recovery recovery.img
(I only mention a different recovery because in some of the Rom threads you might read that you can only install a particular rom with an older version of twrp.)
I'm not sure of your skill or experience with all of this. If you are very new to it (then you are probably really frustrated) have no fear there is a little bit to learn but not that much. Just keep reading the development thread and the guides in it.
Click to expand...
Click to collapse
Thank you for the reply yes i am getting stressed at this and i am new had a break before i smashed the phone now ive just got to find out what my phone is s3 or s4 ? google will help
when i connect my phone to the computer in recovery or flashboot it does not let me see it so i can not put rom on the hdd
(tried restart phone no luck tried restart comy no luck, cant get it to show phone ) all drivers installed
can i use the tool kit to flash recovery ?
phone on orange uk ,is it a s4 ?
thanks for the help guys with your knowledge i will get it working i pray!
pl4yb0y78 said:
when i connect my phone to the computer in recovery or flashboot it does not let me see it so i can not put rom on the hdd
(tried restart phone no luck tried restart comy no luck, cant get it to show phone ) all drivers installed
can i use the tool kit to flash recovery ?
phone on orange uk ,is it a s4 ?
thanks for the help guys with your knowledge i will get it working i pray!
Click to expand...
Click to collapse
do you have your box the phone came in?
Z520e is S4
Z560e is S3
So were you able to put twrp on your phone? when you are in boot loader and click on the recovery does it take you to twrp? Yes the all in one toolkit will flash a recovery for you. but you have your boot loader unlocked first.
tivofool said:
do you have your box the phone came in?
Z520e is S4
Z560e is S3
So were you able to put twrp on your phone? when you are in boot loader and click on the recovery does it take you to twrp? Yes the all in one toolkit will flash a recovery for you. but you have your boot loader unlocked first.
Click to expand...
Click to collapse
yes i now have the twrp in recovery it says enter password and cancel i tried both it was the s4 one that worked so im guessing its an s4
what will the next step be? (if i need anything please could you leave a link)
thanks for all the help starting to feel i might win lol
in twrp when you press "mounts" then press "mount usb", does your computer finally see your phone?
I was looking at your first post, you say that you rooted and flashed your phone. What do you mean by that? Did you download a ROM and attempt to flash it? Or did you "fastboot flash boot boot.img"?
If you are able to access your phone via computer it is as simple as downloading a rom on your computer moving it to your phone then in twrp "install from zip". Then fastboot flash the boot.img.
http://forum.xda-developers.com/showthread.php?t=1583427
how to flash fastboot
http://forum.xda-developers.com/showthread.php?t=1752270
if you are just fed up and want your phone back to stock then you will need to run an RUU.
http://forum.xda-developers.com/showthread.php?t=2094414
To run a RUU you would need to relock your bootloader.
in console type "fastboot lock oem" or use your all in one toolkit to relock it.
if that fails you will need to put your stock recovery back. (you need to have boot loader unlocked to do this)
on the clockworkmod recovery page the stock recovery is the second download link.
http://www.modaco.com/topic/353006-...ch-recovery-for-the-htc-one-s-stock-download/
Ok i am now really confused nothing works downloaded recovery roms they wont install always says failed tried to adb sideload it after google it failed again tried 3 recovery roms all fail what is going wrong icant get it to work
so far ive put twrp on it pressed mount so i can put rom on phone worked
pressed install pressed zip failed
pressed adb sideload then start on comy sent rom 100% install failed
reeboot phone still no os
tried this 3 times different roms all failed
please help
pl4yb0y78 said:
Ok i am now really confused nothing works downloaded recovery roms they wont install always says failed tried to adb sideload it after google it failed again tried 3 recovery roms all fail what is going wrong icant get it to work
so far ive put twrp on it pressed mount so i can put rom on phone worked
pressed install pressed zip failed
pressed adb sideload then start on comy sent rom 100% install failed
reeboot phone still no os
tried this 3 times different roms all failed
please help
Click to expand...
Click to collapse
Do you know how to FASTBOOT FLASH boot.img which is present inside the ROM.ZIP?
Try wiping data, cache, dalvik. Then reinstall.
Sent from my Nexus 7 using Tapatalk HD
khan.orak said:
Do you know how to FASTBOOT FLASH boot.img which is present inside the ROM.ZIP?
Try wiping data, cache, dalvik. Then reinstall.
Sent from my Nexus 7 using Tapatalk HD
Click to expand...
Click to collapse
thanks and yes i can do that i will try and get back to you
C:\adt-bundle-windows-x86_64-20130522\sdk\platform-tools>fastboot boot boot.img
creating boot image...
creating boot image - 16779264 bytes
downloading 'boot.img'...
OKAY [ 1.890s]
booting...
FAILED (remote: reproduce boot image with on-flash ramdisk error)
finished. total time: 1.926s
this is what i get when i try tried 3 imgs
pl4yb0y78 said:
C:\adt-bundle-windows-x86_64-20130522\sdk\platform-tools>fastboot boot boot.img
creating boot image...
creating boot image - 16779264 bytes
downloading 'boot.img'...
OKAY [ 1.890s]
booting...
FAILED (remote: reproduce boot image with on-flash ramdisk error)
finished. total time: 1.926s
this is what i get when i try tried 3 imgs
Click to expand...
Click to collapse
The command is:
Code:
fastboot flash boot boot.img
khan.orak said:
The command is:
Code:
fastboot flash boot boot.img
Click to expand...
Click to collapse
ok i try this i am only learning but getting there lol
So I bought my shield tablet back in March, used it until about may I think. Was browsing the internet then it suddenly crashed and got stuck on the Nvidia boot screen. tried to reboot several times. Nothing. So I forgot about it and thought I would just google the reset option later when I had time. Now since June I have tried everything! From factory reset to fast boot and adb my pc won't even recognize my tablet. Also I never turned on usb dbugging cause I didn't even know what that was. I even gave it to the IT guys at work and they couldn't fix it. Now after reading everything there is to read on this problem and trying to fix it myself I'm stuck on the no command screen with the dead android robot. And now I hear there is a recall do to the battery, I can't even check what type I have. So if someone can please help me I would be much appreciative. Also this happened after updating to the latest OS.
okay so i was able to unlock the bootloader and start flashing but from fastboot flash recovery.img and beyond it says failed to write. any ideas of why?
Ace0169 said:
okay so i was able to unlock the bootloader and start flashing but from fastboot flash recovery.img and beyond it says failed to write. any ideas of why?
Click to expand...
Click to collapse
Can you flash twrp and boot to it?
Ace0169 said:
okay so i was able to unlock the bootloader and start flashing but from fastboot flash recovery.img and beyond it says failed to write. any ideas of why?
Click to expand...
Click to collapse
Hello,
Did you use "Fastboot flash recovery.img" as your command line??
I believe it is "Fastboot flash recovery recovery.img"
If you were able to unlock bootloader you're on the right track.
Sent from a Locked Bootloader
Yes I used "fastboot flash recovery recovery.img" but every command after that keeps telling me "failed to write file"
danjull said:
Can you flash twrp and boot to it?
Click to expand...
Click to collapse
I'm a complete noob when it comes to this stuff, what is twrp? Haha
Ace0169 said:
I'm a complete noob when it comes to this stuff, what is twrp? Haha
Click to expand...
Click to collapse
TWRP (Team Win Recovery Project) is a custom recovery that you can flash on your device. You can flash it like the stock recovery over fastboot. With TWRP you can make full system backups, installing roms or other stuff, wipe partitions and more. Keep trying to install the drivers on your pc. Try to use another usb slot or boot your pc into test mode to install the driver. If you can still access the bootloader, you have really good chances to rescue your device.
Okay will try that. Thanks man.
Ace0169 said:
Okay will try that. Thanks man.
Click to expand...
Click to collapse
I see what your doing wrong. You probably don't even have the recovery img to flash. That's why it's giving you a write error.
There is a tutorial in the general section, that should have all the files and links, etc etc that you'll need to flash TWRP/CWM recovery and root the device if you want
Here is the link:
http://forum.xda-developers.com/shi...k-recovery-images-ota-library-guides-t2988881
Sent from my Nexus 5
Mojar7070 said:
I see what your doing wrong. You probably don't even have the recovery img to flash. That's why it's giving you a write error.
There is a tutorial in the general section, that should have all the files and links, etc etc that you'll need to flash TWRP/CWM recovery and root the device if you want
Here is the link:
http://forum.xda-developers.com/shi...k-recovery-images-ota-library-guides-t2988881
Sent from my Nexus 5
Click to expand...
Click to collapse
If your referring to the recovery images from Nvidia website I have dowloaded that, also the correct drivers. Maybe there is something else I'm missing?
Ace0169 said:
If your referring to the recovery images from Nvidia website I have dowloaded that, also the correct drivers. Maybe there is something else I'm missing?
Click to expand...
Click to collapse
First off, let me ask, what is your end result for the tablet?? Are you trying to just go a Complete stock tablet or are you trying to do anything custom (ex. Custom rom, recovery etc etc)
I'm assuming that since you unlocked your Bootloader, your trying to do something custom.
Sent from a Locked Bootloader
Ace0169 said:
If your referring to the recovery images from Nvidia website I have dowloaded that, also the correct drivers. Maybe there is something else I'm missing?
Click to expand...
Click to collapse
Those official nVidia recovery images come with smaller .img files such as recovery.img, system.img, etc. You'll need to flash those one by one ("fastboot flash recovery recovery.img", then run "fastboot flash system system.img", etc. etc.) or you can just run the flashall script that I think is included in the nVidia images.
Otherwise, if you want to flash TWRP, you'll need to download the TWRP recovery (you can rename it to "twrp-recovery.zip"). Then you'll need to "fastboot flash twrp-recovery.zip" in order to flash the twrp recovery to your tablet.
Mojar7070 said:
First off, let me ask, what is your end result for the tablet?? Are you trying to just go a Complete stock tablet or are you trying to do anything custom (ex. Custom rom, recovery etc etc)
I'm assuming that since you unlocked your Bootloader, your trying to do something custom.
Sent from a Locked Bootloader
Click to expand...
Click to collapse
I want my tablet to boot again, it's completely unusable in its condition I've heard re flashing will fix it.
Ace0169 said:
I want my tablet to boot again, it's completely unusable in its condition I've heard re flashing will fix it.
Click to expand...
Click to collapse
OK. Then the link I gave earlier should help flash stock software onto your tablet.
However, that guide is only to go back to factory "state" Operating System wise. It may not help with hardware. Once your flash everything correctly but device still doesn't boot, its probably not software related.
Sent from my Nexus 5
Mojar7070 said:
OK. Then the link I gave earlier should help flash stock software onto your tablet.
However, that guide is only to go back to factory "state" Operating System wise. It may not help with hardware. Once your flash everything correctly but device still doesn't boot, its probably not software related.
Sent from my Nexus 5
Click to expand...
Click to collapse
so ive followed the steps in the link, and ive executed all the commands but when i get to fasboot flash system system.img it says write failed. also all the commands beyond that one. ive got to be missing something. i have the image from nvidia developer, all the drivers, and my fastboot recognizes my device. has anyone encountered this before?
Ace0169 said:
so ive followed the steps in the link, and ive executed all the commands but when i get to fasboot flash system system.img it says write failed. also all the commands beyond that one. ive got to be missing something. i have the image from nvidia developer, all the drivers, and my fastboot recognizes my device. has anyone encountered this before?
Click to expand...
Click to collapse
After you unlocked the device but before trying to flash anything else on the device, try putting the shield into Fastboot mode. At the bootloader, select fastboot using the volume buttons.
koop1955 said:
After you unlocked the device but before trying to flash anything else on the device, try putting the shield into Fastboot mode. At the bootloader, select fastboot using the volume buttons.
Click to expand...
Click to collapse
Select "fastboot protocol"? Is that correct?
Ace0169 said:
Select "fastboot protocol"? Is that correct?
Click to expand...
Click to collapse
So i selected "fastboot protocol" it blipped for a second then brought me back to the bootloader. tried flashing again and once i reached the fastboot flash system system.img it said write failed again. did it not engage the "fastboot protocol"?
Bringing you back to the bootloader was expected behavior. The "write fail" is a mystery to me. Sorry, that is all that I can offer.
koop1955 said:
Bringing you back to the bootloader was expected behavior. The "write fail" is a mystery to me. Sorry, that is all that I can offer.
Click to expand...
Click to collapse
@Ace0169 Same, not sure what else to tell you. Sorry sir.
Sent from a Locked Bootloader
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!
So i did a stupid thing and flashed the wrong image when i was installing a new rom, I managed to lock myself out of ADB, TWRP and download mode. I'm in a bit of a pickle right now I've been trying everything I can to fix it, but I managed to do nothing. Is there anyone that can walk me through the steeps to get unbricked.
I've tried recovery through hisuite, but it says my device is not supported. My phone showed up via CMD command (fastboot devices) but not (adb devices). I have no idea what to do?
PLEASE HELP ME!!!
Nixonkai417 said:
So i did a stupid thing and flashed the wrong image when i was installing a new rom, I managed to lock myself out of ADB, TWRP and download mode. I'm in a bit of a pickle right now I've been trying everything I can to fix it, but I managed to do nothing. Is there anyone that can walk me through the steeps to get unbricked.
I've tried recovery through hisuite, but it says my device is not supported. My phone showed up via CMD command (fastboot devices) but not (adb devices). I have no idea what to do?
PLEASE HELP ME!!!
Click to expand...
Click to collapse
Give the all required information like Brand, model number in your post first.
Huawei honor 5x kiwi L24, I can't really acces the phone so finding some information is impossible. My main issue is when I boot it's failing to verify the Boot.img , recovery.img and system.img . I don't exactly know what all information I can give you
Nixonkai417 said:
So i did a stupid thing and flashed the wrong image when i was installing a new rom, I managed to lock myself out of ADB, TWRP and download mode. I'm in a bit of a pickle right now I've been trying everything I can to fix it, but I managed to do nothing. Is there anyone that can walk me through the steeps to get unbricked.
I've tried recovery through hisuite, but it says my device is not supported. My phone showed up via CMD command (fastboot devices) but not (adb devices). I have no idea what to do?
PLEASE HELP ME!!!
Click to expand...
Click to collapse
First open the tool
Select the update.app file
Then press Ctrl and select the imgs you want
And then right click and click extract selected
Like in here
https://up.harajgulf.com/imagef-149893652739431-png.html
-Hope- said:
First open the tool
Select the update.app file
Then press Ctrl and select the imgs you want
And then right click and click extract selected
Like in here
https://up.harajgulf.com/imagef-149893652739431-png.html
Click to expand...
Click to collapse
I have already done that, I've tried flashing it via SP flash tool but nothing, it won't show up. I've downloaded correct drivers and done what I could but my phone shows up as Lemobile android adb interface. It sometimes shows as a disk drive as well.
When I run CMD command (fastboot flash oem info) it shows everything but the recovery.img system.img and boot.img need verification how can I verify them without the debugging bridge active on the phone.
Nixonkai417 said:
I have already done that, I've tried flashing it via SP flash tool but nothing, it won't show up. I've downloaded correct drivers and done what I could but my phone shows up as Lemobile android adb interface. It sometimes shows as a disk drive as well.
When I run CMD command (fastboot flash oem info) it shows everything but the recovery.img system.img and boot.img need verification how can I verify them without the debugging bridge active on the phone.
Click to expand...
Click to collapse
What do you mean sir
Imgs are already verified cause they are official
And you don't need USB debug in fastboot mode
Your device is not has mtk processor so it won't work
-Hope- said:
What do you mean sir
Imgs are already verified cause they are official
And you don't need USB debug in fastboot mode
Your device is not has mtk processor so it won't work
Click to expand...
Click to collapse
I rooted my phone and was running xenon HD on my Huawei honor 5x, in the midst of switching ROMs I accidently targeted a TWRP recovery.img with the ROM and Gapps.
So what my phone dose now is when it powers on it an all green screen with a red box and a blue box. After a second it come up with " recovery image verify failed, please update to verified images." I can enter fastboot&rescue mode and a Huawei erecovery, but when i do try to download the recovery via WIFI it says package failure.
Nixonkai417 said:
I rooted my phone and was running xenon HD on my Huawei honor 5x, in the midst of switching ROMs I accidently targeted a TWRP recovery.img with the ROM and Gapps.
So what my phone dose now is when it powers on it an all green screen with a red box and a blue box. After a second it come up with " recovery image verify failed, please update to verified images." I can enter fastboot&rescue mode and a Huawei erecovery, but when i do try to download the recovery via WIFI it says package failure.
Click to expand...
Click to collapse
What happens when you try flashing through fastboot
Assuming that your bootloader is unlocked have you tried reflashing twrp?
-Hope- said:
What happens when you try flashing through fastboot
Assuming that your bootloader is unlocked have you tried reflashing twrp?
Click to expand...
Click to collapse
I had unlocked my bootloader but some research I was doing says, when you accidently flash wrong images it can relock the bootloader. I lost the original bootloader code and i don't exactly have the box anymore, so getting a new code will be difficult.
Nixonkai417 said:
I had unlocked my bootloader but some research I was doing says, when you accidently flash wrong images it can relock the bootloader. I lost the original bootloader code and i don't exactly have the box anymore, so getting a new code will be difficult.
Click to expand...
Click to collapse
As long as the bootloader says 'phone is unlocked' then its ok
-Hope- said:
As long as the bootloader says 'phone is unlocked' then its ok
Click to expand...
Click to collapse
I'm my case the bootloader has relocked, so in green it say phone status: locked.
Nixonkai417 said:
I'm my case the bootloader has relocked, so in green it say phone status: locked.
Click to expand...
Click to collapse
I've reread your previous post and you didn't mentioned what happens in the cmd window when trying to flash the files?
-Hope- said:
I've reread your previous post and you didn't mentioned what happens in the cmd window when trying to flash the files?
Click to expand...
Click to collapse
(REMOTE: command not allowed)
I have already sent an email to Huawei support, just waiting on a response to see if they can give me another unlock code. If I'm unable to unlock the boot loader again with the codes, what's my options for unlocling the boot loader without Huawei's help.
Hi!
Unfortunately there is no topic for Asus Tf303CL, but since it is the member of the TF3xx family I hope this post can stay here.
The problem is, that I'm stuck at the Asus boot (static white) logo and can't go further in booting.
I've tried ADB, but there's no response on the "adb devices" command.
I've also tried fastboot, but only two commands are woriking:
"fastboot devices" comes back with an alphanumeric number and
"fastboot continue" turns off the tablet.
The other fastboot commands are returning with the message "fastboot failed <remote failure>"
So finally I've found some hints that maybe with xFSTK I would able to fix fastboot, then with the Asus Flast Tool I supposed to be able to flash the stock raw rom (which I've already done before).
But unfortunately xFSTK is ether not working (no communication) or I'm using it wrong. As far as I know TF303CL has Intel SoC with Baytrail platform, so I used the Baytrail B0 tab in xFSTK and I've loaded the *ifwi*.bin file which I found in the stock raw rom.
Is this the right way to fix fastboot or I have to do something else? Or the tablet may has hardware defect?
mucden1 said:
Hi!
Unfortunately there is no topic for Asus Tf303CL, but since it is the member of the TF3xx family I hope this post can stay here.
Click to expand...
Click to collapse
I think it was a good idea to open this thread. To my mind your device is really very close related to TF300T and TF700T. The OS is Android 4.4. So it might be worth to attempt to flash a CR like "KatKiss - Nougatella"
But before you may start is to clarify following:
1. Is the bootloader on your device unlocked?
2. Is there already any custom recovery like TWRP on your device?
3. Can you boot into fastboot protocol by holding Power on and Volume down together?
If you cannot get access neither through ADB or Fastboot, your device is bricked for good. Sorry!
1. Is the bootloader on your device unlocked?
I have no idea. It bought it brand new, but I already had to debrick it once with Asus Flash Tool about a year ago. So raw firmware was flashed. I don't know whether flashing a raw rom with AFT requires unlocked bootloader or not.
2. Is there already any custom recovery like TWRP on your device?
As far as I know it has stock recovery.
3. Can you boot into fastboot protocol by holding Power on and Volume down together?
I think Power on & Vol down is the key combination for recovery mode. Power on & Vol up is the combination for fastboot. I can't access to recovery, but fastboot may partially work.
If you cannot get access neither through ADB or Fastboot, your device is bricked for good. Sorry!
Whit adb
Code:
adb devices
command has no response. With fastboot I have a response on the
Code:
fastboot devices
command, it returns some kind of an id. Beside this
Code:
fastboot continue
makes the device to turn off. Other fastboot commands (as I wrote) are returning with the "fastboot failed <remote failure>" response.
These are what I have tried so far:
reboot, reboot bootloader, update, flash (several images), erase cache, erase data
mucden1 said:
1. Is the bootloader on your device unlocked?
I have no idea. It bought it brand new, but I already had to debrick it once with Asus Flash Tool about a year ago. So raw firmware was flashed. I don't know whether flashing a raw rom with AFT requires unlocked bootloader or not.
Click to expand...
Click to collapse
People usually unlock their bootloader to root their device or install Custom ROM on it. I think your bootloader is still locked. On the other side in the left above corner of the dark screen should appear the hint "the device is unlocked" during the boot process.
For the TF300xx family there is an Asus unlock tool V8 available. I don't know if it is useable for your device. Please call Asus support and ask them about that. On the other hand there is a tutorial here: https://qitapso.com/how-to-unlock-asus-transformer-pad-tf303cl-bootloader/
Should I try to unlock the bootloader?
mucden1 said:
Should I try to unlock the bootloader?
Click to expand...
Click to collapse
Of course!
But it's on your own risk. You have to make the decision yourself.
ebonit said:
Of course!
But it's on your own risk. You have to make the decision yourself.
Click to expand...
Click to collapse
The link above goes to "AutorootTools" which is not a real sw, only promising download after an unwanted and long survey. I consider it as a dangerous site.