Related
Hi, i did not find a solution anywhere so i trust on you guys I have HTC ONE, and it is rooted and i also have TWRP v2.6.3.0. Then i was trying to update to Android 4.3 and Sense 5.5...it did not work...so i tried to unroot it...then i messed up the phone no i can only go to recovery mode, or twrp...that´s it...how i can make it functional again ? I just wanted it back to original, no need to root anymore...
sandelin85 said:
Hi, i did not find a solution anywhere so i trust on you guys I have HTC ONE, and it is rooted and i also have TWRP v2.6.3.0. Then i was trying to update to Android 4.3 and Sense 5.5...it did not work...so i tried to unroot it...then i messed up the phone no i can only go to recovery mode, or twrp...that´s it...how i can make it functional again ?
Click to expand...
Click to collapse
Use USB-OTG and flash a ROM using that.
If u can get to the bootloader try flashing a new recovery. fastboot flash recovery recovery.img
Sent from my HTC One using Tapatalk
sandelin85 said:
Hi, i did not find a solution anywhere so i trust on you guys I have HTC ONE, and it is rooted and i also have TWRP v2.6.3.0. Then i was trying to update to Android 4.3 and Sense 5.5...it did not work...so i tried to unroot it...then i messed up the phone no i can only go to recovery mode, or twrp...that´s it...how i can make it functional again ? I just wanted it back to original, no need to root anymore...
Click to expand...
Click to collapse
Or else sideload a rom.zip
Sorry, i am kinf of a newbie with those kind of stuff But when i go to fastboot/bootloader, my computer does not work with it, i have tried many different drivers...so i can´t put any files in it anymore...
So you can get into recovery? Have you tried wiping it yet?
Sent from my HTC One using Tapatalk
sandelin85 said:
Sorry, i am kinf of a newbie with those kind of stuff But when i go to fastboot/bootloader, my computer does not work with it, i have tried many different drivers...so i can´t put any files in it anymore...
Click to expand...
Click to collapse
Use windows 7/8 with the latest HTC drivers, it doesn't work with 8.1.
instigator008 said:
So you can get into recovery? Have you tried wiping it yet?
Sent from my HTC One using Tapatalk
Click to expand...
Click to collapse
yes, i can go to twrp v2.6.3.0...then i try to install: OTA_M7_UL_JB43_SENSE55_MR_HTC_Europe_3.62.401...then it says: no md5 file found, no file_contexts --> failed...so i think that i have delete the whole OS...it says also: No OS installed...ups :/
Have you tried wiping through twrp?
Sent from my HTC One using Tapatalk
sandelin85 said:
yes, i can go to twrp v2.6.3.0...then i try to install: OTA_M7_UL_JB43_SENSE55_MR_HTC_Europe_3.62.401...then it says: no md5 file found, no file_contexts --> failed...so i think that i have delete the whole OS...it says also: No OS installed...ups :/
Click to expand...
Click to collapse
Looks like your system partition is empty, so you'll have to install a whole rom ,an OTA won't help an empty system
n1234d said:
Looks like your system partition is empty, so you'll have to install a whole rom ,an OTA won't help an empty system
Click to expand...
Click to collapse
Okey, could you please tell me (like for a child), how to do that ?
sandelin85 said:
Okey, could you please tell me (like for a child), how to do that ?
Click to expand...
Click to collapse
Okay, do you have any rom(eg. ARHD).zip on your phone? If you do, flash that via twrp, and you're done
If you don't, copy a rom to a USB flash drive and connect it to your phone with an OTG Cable, and flash it via twrp
If you don't have an OTG cable, try this to sideload a rom to your internal sd card http://teamw.in/ADBSideload
n1234d said:
Okay, do you have any rom(eg. ARHD).zip on your phone? If you do, flash that via twrp, and you're done
If you don't, copy a rom to a USB flash drive and connect it to your phone with an OTG Cable, and flash it via twrp
If you don't have an OTG cable, try this to sideload a rom to your internal sd card
No, i don´t have any rom in the phone...i´m now trying the last option...the sideload-thing...my other computer is very slow...so it will take while...but how i can get the phone like it was when i bought it ? So no root access and stock rom and so on ???
Click to expand...
Click to collapse
sandelin85 said:
n1234d said:
Okay, do you have any rom(eg. ARHD).zip on your phone? If you do, flash that via twrp, and you're done
If you don't, copy a rom to a USB flash drive and connect it to your phone with an OTG Cable, and flash it via twrp
If you don't have an OTG cable, try this to sideload a rom to your internal sd card
No, i don´t have any rom in the phone...i´m now trying the last option...the sideload-thing...my other computer is very slow...so it will take while...but how i can get the phone like it was when i bought it ? So no root access and stock rom and so on ???
Click to expand...
Click to collapse
Boot your phone into bootloader-fastboot
Connect it to your pc so it shows fastboot-usb
then open cmd in the folder containing adb.exe (press shift+right click>open command prompt window here) and type fastboot getvar all
Post results after removing IMEI and serial no.
Click to expand...
Click to collapse
n1234d said:
sandelin85 said:
Boot your phone into bootloader-fastboot
Connect it to your pc so it shows fastboot-usb
then open cmd in the folder containing adb.exe (press shift+right click>open command prompt window here) and type fastboot getvar all
Post results after removing IMEI and serial no.
Click to expand...
Click to collapse
Now my computer with newest drivers and windows 7 would not even recognice the phone...damn, i´m stuck...again ! Samsung S4 was much easier...i made it a brick, then i connect to safe mode, and samsung kies rescue everything
Click to expand...
Click to collapse
sandelin85 said:
n1234d said:
Now my computer with newest drivers and windows 7 would not even recognice the phone...damn, i´m stuck...again ! Samsung S4 was much easier...i made it a brick, then i connect to safe mode, and samsung kies rescue everything
Click to expand...
Click to collapse
When your phone is in fastboot, type
fastboot devices
Does it list your phone?
If it doesn't, try changing USB ports/cord, and also try uninstalling and then fresh installing new drivers after restarting your pc, then connecting your phone.
Sent from my iPod touch using Tapatalk
---------- Post added at 12:26 AM ---------- Previous post was at 12:22 AM ----------
And what happened to the sideload? Did the rom zip get copied?
Sent from my iPod touch using Tapatalk
Click to expand...
Click to collapse
How are you getting on? You most likely haven't bricked your ONE
Sent from my HTC One using XDA Premium 4 mobile app
When your phone is in fastboot, type
fastboot devices
Does it list your phone?
If it doesn't, try changing USB ports/cord, and also try uninstalling and then fresh installing new drivers after restarting your pc, then connecting your phone.
Now it finds it again
nd what happened to the sideload? Did the rom zip get copied?
Sideload would not connect, it fails all the time...
How are you getting on? You most likely haven't bricked your ONE
I have tried all things that you guys have suggested...i can´t get any of them to work, for now...So hard find all the right links and so on...i´m not great with android...is there any video or story, how to do that ? I suck My english also, i´m from Finland
It's definitely NOT bricked. I'll keep an eye on this thread, you're getting great help but if you don't end up getting it fixed send me a PM, I sometimes forget about a thread I need to check back in on. It's for sure fixable and there's great advice in here.
Edit I somehow missed your last post before posting this. Send me a PM, and I'll help you get it fixed up after work.
sandelin85 said:
When your phone is in fastboot, type
fastboot devices
Does it list your phone?
If it doesn't, try changing USB ports/cord, and also try uninstalling and then fresh installing new drivers after restarting your pc, then connecting your phone.
Now it finds it again
nd what happened to the sideload? Did the rom zip get copied?
Sideload would not connect, it fails all the time...
How are you getting on? You most likely haven't bricked your ONE
I have tried all things that you guys have suggested...i can´t get any of them to work, for now...So hard find all the right links and so on...i´m not great with android...is there any video or story, how to do that ? I suck My english also, i´m from Finland
Click to expand...
Click to collapse
ok so fastboot is working, as suggested before post a "fastboot getvar all" (remove IMEI and s/n).
If sideload isn't working you can use "adb push", but first thing is to reflash custom recovery just in case it's corrupted.
so download CWM or TWRP (from the threads in xda), then
fastboot erase cache
fastboot flash recovery <name of recovery>.img
fastboot erase cache
fastboot reboot-bootloader
-> enter RECOVERY
then
adb push <name of rom>.zip /sdcard/ (this will take anywhere between 5 to 15minutes and not show progress, eventually it should come back with "success")
then
install zip in recovery, and choose the <name of rom>.zip and install it.
Hello. I have the following problem. I friend of mine that I've sold him my old rooted Htc One tried to make 4.4. kitkat
He tried to install
Android_Revolution_HD-One-53.0zip
BUT I don't know how he managed to stuck his phone.The problem is when I am power on the phone it shows the white HTC screen with the red letters "this build is for development purpose only..." after a while reboots in TWRP v2.5.0.0
And that's it , I cannot do anything because my PC won't recognize it via USB cable.
Any suggestions?
(excuse me for my English, with love from Greece )
As long as it boots into Recovery its not bricked. Do you have the HTC Driver installed on your computer?
Android Revolution HD 53 requires min. TWRP 2.6.3.3. Your version is too old.
foxgre said:
Hello. I have the following problem. I friend of mine that I've sold him my old rooted Htc One tried to make 4.4. kitkat
He tried to install
Android_Revolution_HD-One-53.0zip
BUT I don't know how he managed to stuck his phone.The problem is when I am power on the phone it shows the white HTC screen with the red letters "this build is for development purpose only..." after a while reboots in TWRP v2.5.0.0
And that's it , I cannot do anything because my PC won't recognize it via USB cable.
Any suggestions?
(excuse me for my English, with love from Greece )
Click to expand...
Click to collapse
From recovery go to fastboot connect phone to pc.
It must be recognized.
Then flash boot.img which is in the Revolution.zip.
Then install the rom via recovery.
Remember for unlock and not s-off users the boot.img must be flashed befor flashing a rom.zip.
Sent by myself, without help )
i am doing as you say, but it's not recognized.
I only get a message android phone, not installed properly
SAME problem (or pretty similar) here
foxgre said:
i am doing as you say, but it's not recognized.
I only get a message android phone, not installed properly
Click to expand...
Click to collapse
SAME problem (or pretty similar) here, trying to instal ARHD61.1... I don't know how did I screw up this so much...
My bootloader is TAMPERED, UNLOCKED, S-On. Recovery TRWP (2.7) launches but... many things don't work.
First thing I have to mention is that I didn't forget to enable debugging before all this started (and now I can't launch android to do it).
My HTC drivers should be up-to-date, as I installed yesterday HTC sync 3.00.52...
In bootloader, if I type "fastboot devices" I get "FA34HW903605 fastboot", and "fastboot reboot.bootloader" does what it is expected to do...
In recovery, "adb push" tells me "error: device not found".
Can someone help me? If you need more details, just ask. Thanks
foxgre said:
i am doing as you say, but it's not recognized.
I only get a message android phone, not installed properly
Click to expand...
Click to collapse
Duwie_80 said:
SAME problem (or pretty similar) here, trying to instal ARHD61.1... I don't know how did I screw up this so much...
My bootloader is TAMPERED, UNLOCKED, S-On. Recovery TRWP (2.7) launches but... many things don't work.
First thing I have to mention is that I didn't forget to enable debugging before all this started (and now I can't launch android to do it).
My HTC drivers should be up-to-date, as I installed yesterday HTC sync 3.00.52...
In bootloader, if I type "fastboot devices" I get "FA34HW903605 fastboot", and "fastboot reboot.bootloader" does what it is expected to do...
In recovery, "adb push" tells me "error: device not found".
Can someone help me? If you need more details, just ask. Thanks
Click to expand...
Click to collapse
can you guys check out FAQ #2 in my guide: http://forum.xda-developers.com/showthread.php?t=2541082 if that's the problem you have
nkk71 said:
can you guys check out FAQ #2 in my guide: http://forum.xda-developers.com/showthread.php?t=2541082 if that's the problem you have
Click to expand...
Click to collapse
Let me try and I'll tell you later. I also think it's a matter of drivers, so I was downloading and re-installing it... Thank you for your help
-------------------------------------------------- UPDATE --------------------------------------------------------------------------------
Well, I followed your steps (LET ME THANK YOU FOR MAKING THAT GUIDE) and now the device is "My HTC" as you show.
Something has changed:
If I type "adb devices" (in PC) when phone is in fastboot, the listing is void (before I got "FA34HW903605 fastboot"), and if I do the same while phone is in recovery, I get the mentioned "FA34HW903605 recovery".
In Windows7 I don't see "My HTC" as a conventional USB storage or Memory of a Camera (should it be?)
I've managed to ADB PUSH a ROM (ARHD) in recovery, but now I get an error message: "Unable to mount '/data' " and "Unable to mount internal storage " then FAILED. Now I'll try flashing a new recovery...
WOW WOW WOW!! It was enough for me, sir
1st) Solve comunnication issues as shown in FAQ #2 here
2nd) Solve TWRP recovery mount issues by:
2.a) Installing any other (clockwork) in fastboot using One All In One Kit (eaaaasy)
2.b) Formatting cache, system, data partitions
2.c) Installing TWRP again using One All In One Kit (Android Revolution REQUIRES this recovery)
2.d) Sending the ROM ('adb push your_rom.zip /sdcard/wherever_you_want_it')
2.e) Installing it from TWRP recovery.
An that was all. THANKS A LOT nkk71; without your help I still would be here trying to figure out what's broken... Thanks.
Duwie_80 said:
WOW WOW WOW!! It was enough for me, sir
1st) Solve comunnication issues as shown in FAQ #2 here
2nd) Solve TWRP recovery mount issues by:
2.a) Installing any other (clockwork) in fastboot using One All In One Kit (eaaaasy)
2.b) Formatting cache, system, data partitions
2.c) Installing TWRP again using One All In One Kit (Android Revolution REQUIRES this recovery)
2.d) Sending the ROM ('adb push your_rom.zip /sdcard/wherever_you_want_it')
2.e) Installing it from TWRP recovery.
An that was all. THANKS A LOT nkk71; without your help I still would be here trying to figure out what's broken... Thanks.
Click to expand...
Click to collapse
no problem, glad to be of help
remember for most 4.4 ROMs, (for m7_u/ul) TWRP 2.6.3.3 (or higher) is recommended at the moment.
though you should be good by downloading it, then checking MD5 to make sure the download isnt corrupt (that site doesnt work with download managers), then:
fastboot flash recovery openrecovery-twrp-2.6.3.3-m7.img
fastboot erase cache
fastboot reboot-bootloader
-> enter recovery and push the rom
Thank you all for your support, but still the problem remains.
I have installed HTC Drivers and when i connect the HtcOne i can hear the USB beep from windows but i cannot open the phone like a drive.
In other words i cannot add files to the phone :crying::crying:
foxgre said:
Thank you all for your support, but still the problem remains.
I have installed HTC Drivers and when i connect the HtcOne i can hear the USB beep from windows but i cannot open the phone like a drive.
In other words i cannot add files to the phone :crying::crying:
Click to expand...
Click to collapse
you're really not giving any details... so you hear a sound... what does Windows Device Manager show??
foxgre said:
Thank you all for your support, but still the problem remains.
I have installed HTC Drivers and when i connect the HtcOne i can hear the USB beep from windows but i cannot open the phone like a drive.
In other words i cannot add files to the phone :crying::crying:
Click to expand...
Click to collapse
It wont be so easy, I'm afraid. Even if comunication issues are solved, you won't be able to copy your ROM using windows file manager, opening the phone like a conventional drive...
You have to install "ADB" in your PC (search in HTC ONE subforums, there's a lot of info about ADB pusing (=copying) ROMS) and use it to copy your ROM. One advice: while "pushing" the ROM, be patient: it takes a long time. When your ROM is "pushed", just install it in recovery and... that's it!!
I think here you have a good starting point.
Duwie_80 said:
It wont be so easy, I'm afraid. Even if comunication issues are solved, you won't be able to copy your ROM using windows file manager, opening the phone like a conventional drive...
You have to install "ADB" in your PC (search in HTC ONE subforums, there's a lot of info about ADB pusing (=copying) ROMS) and use it to copy your ROM. One advice: while "pushing" the ROM, be patient: it takes a long time. When your ROM is "pushed", just install it in recovery and... that's it!!
I think here you have a good starting point.
Click to expand...
Click to collapse
Thanks again i am already looking for it.
AT LAST!!!
I've managed to push the rom.
Thank you very much for your help
foxgre said:
AT LAST!!!
I've managed to push the rom.
Thank you very much for your help
Click to expand...
Click to collapse
Hey, congratulations!! :good::good::good:
My bootloader is unlocked already, I deleted HTC Sync, debugging on, usb is in disk mode, etc. but for the life of me I can't get any recoveries to flash. I get the "Remote: not allowed" and if I try again it just gets stuck on sending recovery. It shows up as a fastboot device in cmd. Any suggestions?
Try the tool kit in development.
redmanjoey said:
My bootloader is unlocked already, I deleted HTC Sync, debugging on, usb is in disk mode, etc. but for the life of me I can't get any recoveries to flash. I get the "Remote: not allowed" and if I try again it just gets stuck on sending recovery. It shows up as a fastboot device in cmd. Any suggestions?
Click to expand...
Click to collapse
redmanjoey said:
My bootloader is unlocked already, I deleted HTC Sync, debugging on, usb is in disk mode, etc. but for the life of me I can't get any recoveries to flash. I get the "Remote: not allowed" and if I try again it just gets stuck on sending recovery. It shows up as a fastboot device in cmd. Any suggestions?
Click to expand...
Click to collapse
Are you in bootloader/fastbootusb?
BD619 said:
Are you in bootloader/fastbootusb?
Click to expand...
Click to collapse
Yes, I am in fastbootusb. The same thing happens on the toolkit. I doubt it is any kind of hardware defect, but the device is recognized in fastboot which is why I am SUPER confused. This is the first time I have ever run into an issue with fastboot.
redmanjoey said:
Yes, I am in fastbootusb. The same thing happens on the toolkit. I doubt it is any kind of hardware defect, but the device is recognized in fastboot which is why I am SUPER confused. This is the first time I have ever run into an issue with fastboot.
Click to expand...
Click to collapse
I initially had a bad download and had issues with both ways to flash. Redownloaded and it worked.
Also, with the tool I've had issues with usb switching from storage to media which affected even using adb to push files. Make sure that's not an issue with the push method.
Sent from M8 on XDA Premium APP
joshuaw84 said:
I initially had a bad download and had issues with both ways to flash. Redownloaded and it worked.
Also, with the tool I've had issues with usb switching from storage to media which affected even using adb to push files. Make sure that's not an issue with the push method.
Sent from M8 on XDA Premium APP
Click to expand...
Click to collapse
Are you implying the fastboot download was bad or the recovery? I tried three different recoveries now and none worked. I also tried using hassoon2000s method and just get an error saying device not found.
Also, I am using the fastboot file that came directly from HTC so I am really scratching my head right now...
redmanjoey said:
Also, I am using the fastboot file that came directly from HTC so I am really scratching my head right now...
Click to expand...
Click to collapse
It could be outdated.
Do you have android sdk on your PC?
If so make sure it's up to date.
If not get it HERE
redmanjoey said:
Are you implying the fastboot download was bad or the recovery? I tried three different recoveries now and none worked. I also tried using hassoon2000s method and just get an error saying device not found.
Click to expand...
Click to collapse
Just giving you my experience where there were a couple issues that made it seem like I was stuck. Take it or leave it I guess.
Sent from M8 on XDA Premium APP
joshuaw84 said:
Just giving you my experience where there were a couple issues that made it seem like I was stuck. Take it or leave it I guess.
Sent from M8 on XDA Premium APP
Click to expand...
Click to collapse
Sorry if I sounded mean or anything I was literally just asking which one you meant lol. I now realize "are you implying" does sound kinda snarky. Anyway, it must have been something with my computer because I did it on another computer and got it to work.
So the thread doesn't go to waste, if anyone is having issues try on another computer.
Okay, now trying to flash the stock recovery to get the phone exchanged for radio issues, I am running into the same problem. I tried both computers now. Hopefully I figure it out soon, had to activate an old blackberry for the time being.
"sending 'recovery' (16472 KB)...
FAILED (remote: not allowed)
finished. total time: 0.007s"
I have had the same problem before on a different phone. All you need to do is put it on the sd card and use the boot loader method. The phone will automatically find it and flash it. Then just remove sd card and delete file so it doesn't keep prompting to flash it every time you reboot.
{ParanoiA} said:
I have had the same problem before on a different phone. All you need to do is put it on the sd card and use the boot loader method. The phone will automatically find it and flash it. Then just remove sd card and delete file so it doesn't keep prompting to flash it every time you reboot.
Click to expand...
Click to collapse
To flash a recovery? Just rename the recovery as a radio file?
Yes. Go to http://forum.xda-developers.com/showthread.php?t=2696652 and all the info you need is there along with directions.
Hi guys, I'll just start things off with saying that I am far from being anywhere near as technologically advanced as the majority of you so I would like your help if possible.
I had wanted to flash back to Stock and unroot my Moto X but for some reason I had gone into TWRP and decided to delete everything. Now every time I try to reboot from TWRP, it'll just say that the phone does not have an OS Installed and therefore if I reboot it, it will just stay on the 'Warning Bootloader Unlocked" screen.
I've read quite a few threads on various forums but I am unable to get my laptop to recognise the device in fastboot. That's my only problem so far as I've downloaded the Motorola Device Manager and all those other things but still cannot get my laptop to show the device for me to put the files into. When I plug it in, I am able to hear the sound and the device recognizes that it's been plugged in but I can't see it on my laptop.
Any and all help is GREATLY appreciated. Thanks guys and forgive my ignorance.
Sent from my SM-N9005 using XDA Free mobile app
boss. said:
Hi guys, I'll just start things off with saying that I am far from being anywhere near as technologically advanced as the majority of you so I would like your help if possible.
I had wanted to flash back to Stock and unroot my Moto X but for some reason I had gone into TWRP and decided to delete everything. Now every time I try to reboot from TWRP, it'll just say that the phone does not have an OS Installed and therefore if I reboot it, it will just stay on the 'Warning Bootloader Unlocked" screen.
I've read quite a few threads on various forums but I am unable to get my laptop to recognise the device in fastboot. That's my only problem so far as I've downloaded the Motorola Device Manager and all those other things but still cannot get my laptop to show the device for me to put the files into. When I plug it in, I am able to hear the sound and the device recognizes that it's been plugged in but I can't see it on my laptop.
Any and all help is GREATLY appreciated. Thanks guys and forgive my ignorance.
Sent from my SM-N9005 using XDA Free mobile app
Click to expand...
Click to collapse
You don't put files on the phone and you don't use twrp. Follow the instructions in the return to 100% stock thread.
samwathegreat said:
You don't put files on the phone and you don't use twrp. Follow the instructions in the return to 100% stock thread.
Click to expand...
Click to collapse
I've tried following the steps but I was unsure of step 3 where it says to download and install the proper firmware for the device but still unsure on how to install it. RSD Lite won't pick up the device nor will it show up when I type 'adb devices' in CMD. And finally, how do I go about turning on USB debugging when it won't boot up past the bootloader unlock screen?
Appreciate the help
Sent from my SM-N9005 using XDA Free mobile app
boss. said:
I've tried following the steps but I was unsure of step 3 where it says to download and install the proper firmware for the device but still unsure on how to install it. RSD Lite won't pick up the device nor will it show up when I type 'adb devices' in CMD. And finally, how do I go about turning on USB debugging when it won't boot up past the bootloader unlock screen?
Appreciate the help
Sent from my SM-N9005 using XDA Free mobile app
Click to expand...
Click to collapse
Turn the phone off. Unplug it. Hold down VOL DOWN, and press power. The phone will boot into the bootloader. This is how you flash with rsd lite.
Adb does not work in bootloader, and isn't used for this. Once in bootloader (ap fastboot mode), rsd lite should recognize the device.
Make absolutely sure you do not downgrade to a previous version (you will brick), and make sure you flash the correct firmware for YOUR device/carrier.
You can only flash the same version or higher than what you were on before you erased everything.
samwathegreat said:
Turn the phone off. Unplug it. Hold down VOL DOWN, and press power. The phone will boot into the bootloader. This is how you flash with rsd lite.
Adb does not work in bootloader, and isn't used for this. Once in bootloader (ap fastboot mode), rsd lite should recognize the device.
Make absolutely sure you do not downgrade to a previous version (you will brick), and make sure you flash the correct firmware for YOUR device/carrier.
You can only flash the same version or higher than what you were on before you erased everything.
Click to expand...
Click to collapse
Thanks for the help! Unfortunately RSD Lite doesn't recognise the device in bootloader. Am I supposed to put the files into a certain place for things to start working properly and is it also because I'm using windows 8.1? I've already installed the Motorola Device Manager as well.
Really sorry for all the questions - complete newbie right here
Sent from my SM-N9005 using XDA Free mobile app
boss. said:
Thanks for the help! Unfortunately RSD Lite doesn't recognise the device in bootloader. Am I supposed to put the files into a certain place for things to start working properly and is it also because I'm using windows 8.1? I've already installed the Motorola Device Manager as well.
Really sorry for all the questions - complete newbie right here
Sent from my SM-N9005 using XDA Free mobile app
Click to expand...
Click to collapse
You said you downloaded moto device manager... Did you install it? If so you are one of the unlucky ones and will have to use the manual method with fastboot and mfastboot. Take it slow and follow the instructions. Leave out the config carrier line.
To make sure fastboot is working, type fastboot devices while in bootloader mode.
samwathegreat said:
You said you downloaded moto device manager... Did you install it? If so you are one of the unlucky ones and will have to use the manual method with fastboot and mfastboot. Take it slow and follow the instructions. Leave out the config carrier line.
To make sure fastboot is working, type fastboot devices while in bootloader mode.
Click to expand...
Click to collapse
Oh okay that makes sense. Yeah I had installed but still nothing. Okay, I'll try the manual method, thanks heaps!
I've typed it fastboot devices in CMD and it came up with T017500PDP fastboot. I assume that's good? Haha
Sent from my SM-N9005 using XDA Free mobile app
boss. said:
Oh okay that makes sense. Yeah I had installed but still nothing. Okay, I'll try the manual method, thanks heaps!
I've typed it fastboot devices in CMD and it came up with T017500PDP fastboot. I assume that's good? Haha
Sent from my SM-N9005 using XDA Free mobile app
Click to expand...
Click to collapse
Yes perfect.
Run one command at a time - copy/paste them.
Remember to use mfastboot for system.img - regular fastboot will NOT work. Also remember to skip the config carrier command.
samwathegreat said:
Yes perfect.
Run one command at a time - copy/paste them.
Remember to use mfastboot for system.img - regular fastboot will NOT work. Also remember to skip the config carrier command.
Click to expand...
Click to collapse
You my friend are a legend. Last round (hopefully) of questions though: where the code says to type in fastboot flash .... .gpt.bin and all those other things, am I supposed to put the files somewhere in particular? Because just regularly typing them into CMD comes up with (bootloader) Variable not supported! Then error: cannot open 'gtp.bin' or cannot open 'recovery.img' and so on but on the phone it says getvar partition-type:recovery or boot and so on.
Also the when the instructions say to use mfastboot, CMD says that it is not recognized as an internal or external command. Thanks!
Sent from my SM-N9005 using XDA Free mobile app
boss. said:
You my friend are a legend. Last round (hopefully) of questions though: where the code says to type in fastboot flash .... .gpt.bin and all those other things, am I supposed to put the files somewhere in particular? Because just regularly typing them into CMD comes up with (bootloader) Variable not supported! Then error: cannot open 'gtp.bin' or cannot open 'recovery.img' and so on but on the phone it says getvar partition-type:recovery or boot and so on.
Also the when the instructions say to use mfastboot, CMD says that it is not recognized as an internal or external command. Thanks!
Sent from my SM-N9005 using XDA Free mobile app
Click to expand...
Click to collapse
First: yes, you have to put those files in the same folder as you are running the commands from. If your command prompt shows C:\users\jimmy\
Then that is where the files should be! You should have extracted the zip file you downloaded to the same folder you are running the commands from.
Second, you obviously have not download mfastboot.exe (it is linked in the return to stock thread) OR you didn't put it in the same folder as the rest of the files.
The "variable not supported" messages are normal. The error cannot open.... errors are NOT.
I'm attaching mfastboot.exe (it's zipped - extract it to the same folder as everything else) to this post so you don't have to go looking for it.
DON'T move on if the first command doesn't work. Make sure each one gives success before you move on.
Awesome!
samwathegreat said:
First: yes, you have to put those files in the same folder as you are running the commands from. If your command prompt shows C:\users\jimmy\
Then that is where the files should be! You should have extracted the zip file you downloaded to the same folder you are running the commands from.
Second, you obviously have not download mfastboot.exe (it is linked in the return to stock thread) OR you didn't put it in the same folder as the rest of the files.
The "variable not supported" messages are normal. The error cannot open.... errors are NOT.
I'm attaching mfastboot.exe (it's zipped - extract it to the same folder as everything else) to this post so you don't have to go looking for it.
DON'T move on if the first command doesn't work. Make sure each one gives success before you move on.
Click to expand...
Click to collapse
Thanks so much, it worked great! The colours are a bit out of wack though (the blues are now orange and so on) and the bot animation is messed but still better than nothing. Thanks so much for your help!
boss. said:
Thanks so much, it worked great! The colours are a bit out of wack though (the blues are now orange and so on) and the bot animation is messed but still better than nothing. Thanks so much for your help!
Click to expand...
Click to collapse
You're welcome....but that isn't normal. I suggest doing it again from the beginning. A full SBF to stock re-writes all the partitions and there shouldn't be anything "out of wack". Sounds like something went wrong....OR your device has physical damage?
Anyways, please consider hitting the "THANKS" button under any and all posts that help you. :good:
samwathegreat said:
You're welcome....but that isn't normal. I suggest doing it again from the beginning. A full SBF to stock re-writes all the partitions and there shouldn't be anything "out of wack". Sounds like something went wrong....OR your device has physical damage?
Anyways, please consider hitting the "THANKS" button under any and all posts that help you. :good:
Click to expand...
Click to collapse
Re-did the whole thing from scratch again and now all problems are solved. Really appreciate the help my friend!
Sent from my SM-N9005 using XDA Free mobile app
So let's say theoretically that someone in their first week of using an Android device (ever) were to boot up the TWRP recovery and wipe their Fire because YOLO. Would anyone have advice for any possible way to revive it? Here's a description of the device's state:
It boots the Amazon logo only, and adb lists the device as unauthorized. If I boot it in recovery it says it's in fastboot mode and adb doesn't recognize the device at all. (Edit: ) Fastboot does recognize it though, but I'm not sure of the best path to take since I can't use adb to push files to the device for reinstallation of the firmware.
So from my view it's a paperweight, and that's cool because what I did was all kinds of dumb (thinking I could still revive it after what I was doing). But before I use it as a door stop, I figured I might ask you guys what you'd do. I'm guessing maybe I boot from an image that allows me to push the firmware to the sdcard, then I can boot from TWRP recovery and install it, but the first image to use there is something I'm not yet sure of.
Have you tried the methods at http://forum.xda-developers.com/amazon-fire/general/unbrick-restore-stock-2015-amazon-fire-t3250639
stultus2 said:
Have you tried the methods at http://forum.xda-developers.com/amazon-fire/general/unbrick-restore-stock-2015-amazon-fire-t3250639
Click to expand...
Click to collapse
Thanks for the reply
I think that's along the lines of what I need to do, but I can't use adb sideload as adb no longer sees the devices in recovery. Fastboot does though.
stultus2 said:
Have you tried the methods at http://forum.xda-developers.com/amazon-fire/general/unbrick-restore-stock-2015-amazon-fire-t3250639
Click to expand...
Click to collapse
Ah you know what, you just encouraged me to read over again and try one different thing. The CM recovery enables adb sideload, and I'm pushing the stock firmware to it now.
Thanks for the help