Related
Hi everyone,
Whilst trying to test a custom bootloader I made, I tried to flash a PJ40IMG.zip in RUU Mode. It started flashing, then froze completely. It displayed finished, but remained frozen on the phone screen. Then the screen disappeared. Upon insertion again, the phone went on to QHSUSB_DLOAD mode.
I have QPST, but no idea how to use it, and don't have the Qualcomm drivers installed, since they are only for x64 machines.
I have tried the unbrick thread in the development section. It flashed the HBOOT, then stood stuck on waiting for /dev/sdb12 I tried holding down POWER again, but didn't recognize the device like it did previously. Now, if I try again and spam
Code:
ls /dev/sd*
the partitions are no longer seen, no matter how fast I try and do it. I have attempted this multiple times, even tried the PblClear tool from unlimited.io, to no avail.
Any ideas? I think I will have a permanent paperweight at this stage.
usaff22 said:
Hi everyone,
Whilst trying to test a custom bootloader I made, I tried to flash a PJ40IMG.zip in RUU Mode. It started flashing, then froze completely. It displayed finished, but remained frozen on the phone screen. Then the screen disappeared. Upon insertion again, the phone went on to QHSUSB_DLOAD mode.
I have QPST, but no idea how to use it, and don't have the Qualcomm drivers installed, since they are only for x64 machines.
I have tried the unbrick thread in the development section. It flashed the HBOOT, then stood stuck on waiting for /dev/sdb12 I tried holding down POWER again, but didn't recognize the device like it did previously. Now, if I try again and spam
Code:
ls /dev/sd*
the partitions are no longer seen, no matter how fast I try and do it. I have attempted this multiple times, even tried the PblClear tool from unlimited.io, to no avail.
Any ideas? I think I will have a permanent paperweight at this stage.
Click to expand...
Click to collapse
I don't want to kick you while you're down but you tried to write a custom hboot then tried to install it with the PJ40IMG.zip method? That method has never been used on the One S. No one does it that way. The only reason it worked now was that you have S-OFF and look what happened. How come you didn't try to fastboot flash it?
Back to your question. I've never seen someone recover from the partitions not being enumerated. You're going to need to unbrick it with JTAG. I recommend you use these people http://mobiletechvideos.mybigcommerce.com/htc-one-s-jtag-brick-repair/
dc211 said:
I don't want to kick you while you're down but you tried to write a custom hboot then tried to install it with the PJ40IMG.zip method? That method has never been used on the One S. No one does it that way. The only reason it worked now was that you have S-OFF and look what happened. How come you didn't try to fastboot flash it?
Back to your question. I've never seen someone recover from the partitions not being enumerated. You're going to need to unbrick it with JTAG. I recommend you use these people http://mobiletechvideos.mybigcommerce.com/htc-one-s-jtag-brick-repair/
Click to expand...
Click to collapse
No, the plugin gave me a PJ40IMG.zip which I then flashed in RUU mode, the same way that a fastboot zip would, since I knew flashing it via the PJ40IMG method wouldn't work without a USB Y Cable, since it only works with a device that supports microSD.
fastboot oem rebootRUU
and then
fastboot flash zip PJ40IMG.zip
usaff22 said:
No, the plugin gave me a PJ40IMG.zip which I then flashed in RUU mode, the same way that a fastboot zip would, since I knew flashing it via the PJ40IMG method wouldn't work without a USB Y Cable, since it only works with a device that supports microSD.
fastboot oem rebootRUU
and then
fastboot flash zip PJ40IMG.zip
Click to expand...
Click to collapse
I'm glad you learned that! I had seen you recommend to others that you can just put it on your sdcard and it would work. My mistake that I assumed you did it yourself.
I know you've been waiting a long time for S-OFF, sorry to hear you bricked your phone so quickly after finally getting it. Good luck with the jtag. Or if you find another solution let us know.
dc211 said:
I'm glad you learned that! I had seen you recommend to others that you can just put it on your sdcard and it would work. My mistake that I assumed you did it yourself.
I know you've been waiting a long time for S-OFF, sorry to hear you bricked your phone so quickly after finally getting it. Good luck with the jtag. Or if you find another solution let us know.
Click to expand...
Click to collapse
Thanks, I knew it wouldn't work after I saw someone on the One XL forums who tried it on his with a USB Y Cable, and didn't look for the zip on the internal storage. I used to think it would work after doing it on my brother's Sensation, but it was a no go for me.
At this stage I think I will have to visit my carrier. Hopefully they can give me a replacement or get it fixed somehow.
This should be helpfull
http://forum.xda-developers.com/showthread.php?t=1990043&highlight=downgrade
Fofff said:
This should be helpfull
http://forum.xda-developers.com/showthread.php?t=1990043&highlight=downgrade
Click to expand...
Click to collapse
I tried that, my partitions won't show so it is of no help to me unfortunately.
I'm not sure where to post this, sorry for that.
I haven't found any help or so in any threads about my phone on this forum or on others...
I own a Vodafone Smart 2 (Alcatel V860) mobile phone that I rooted, had the original ROM (got rid of the Vodafone mess ) for a while and then flashed Roeddie's v 0.9.9 (OTA 4) ROM and it was all going well...
Until a couple of days ago when I saw a thread on HtcMania.com claiming a clockworkmod recovery for this phone, so I said why not... (not allowed to post the url...)
I've put the .zip on my SDcard and flashed it via the original recovery. The cwm loaded, but at reboot it was stuck in the original recovery. Sort of Boot Loop.
Happened this before (when flashing some idiot cm7), so I wiped data/factory reset, dalvik, cache partition and I restored a previous backup, supposed to solve that Boot Loop. But, this time, it didn't... The phone was still booting directly into the original recovery.
So I tried another thing. I've started the phone in fastboot mode and used the fastboot method to write that backup. That meant "fastboot erase bootloader, boot, system, userdata, custpack, recovery, cache" and then "fastboot flash the images from the backup", method that I used before and worked without any problem.
But, this time, after I erased everything, when I started to flash the images from the backup... the phone, somehow, POWERED OFF, I still don't have the slightest idea why... :crying:
When i powered it on, the bootloader was missing so it just froze with the Android logo on the screen and after a few seconds it shut down.
I tried starting it in fastboot mode, but no luck. It starts just like that every time, but if I plug the USB cable in it, it doesn't shut down anymore, freezing with the logo on screen.
Windows won't recognize it under any circumstances, no matter what drivers I have. no adb, fastboot. So it's pretty much useless.
If i restart it like 5 times, Windows eventually recognizes it as a Modem. Useless.
I think it's a Soft Brick, because it starts but it has no idea what to do without the bootloader. It would generally be recoverable, but, as you can see, I don't have any method to communicate with this phone...
I would consider the jtag, with a RIFF Box. Taking the motherboard out of it and "writing the dead body", but I don't think the Riff Manager supports this sh**ty phone and I wouldn't like to pay for it.
The phone is still covered by warranty, but I'm not sure if they are going to do it for free, because I messed with it.
I can try that story: "I was taking an OTA Update and the phone never powered on." maybe they are going to buy it.
So is it any other method to write at least the bootloader on it, any other that the ones mentioned before, methods that I have no access to ?
RO.maniac said:
I'm not sure where to post this, sorry for that.
I haven't found any help or so in any threads about my phone on this forum or on others...
I own a Vodafone Smart 2 (Alcatel V860) mobile phone that I rooted, had the original ROM (got rid of the Vodafone mess ) for a while and then flashed Roeddie's v 0.9.9 (OTA 4) ROM and it was all going well...
Until a couple of days ago when I saw a thread on HtcMania.com claiming a clockworkmod recovery for this phone, so I said why not... (not allowed to post the url...)
I've put the .zip on my SDcard and flashed it via the original recovery. The cwm loaded, but at reboot it was stuck in the original recovery. Sort of Boot Loop.
Happened this before (when flashing some idiot cm7), so I wiped data/factory reset, dalvik, cache partition and I restored a previous backup, supposed to solve that Boot Loop. But, this time, it didn't... The phone was still booting directly into the original recovery.
So I tried another thing. I've started the phone in fastboot mode and used the fastboot method to write that backup. That meant "fastboot erase bootloader, boot, system, userdata, custpack, recovery, cache" and then "fastboot flash the images from the backup", method that I used before and worked without any problem.
But, this time, after I erased everything, when I started to flash the images from the backup... the phone, somehow, POWERED OFF, I still don't have the slightest idea why... :crying:
Logically, when i powered it on, the bootloader was missing (I've erased it earlier and the phone Powered Off just before writing the bootloader from backup) it just freoze with the Android logo on the screen and after a few seconds it shut down. Because it has no bootloader and it doesn't know how and what to boot...
I tried starting it in fastboot mode, but no luck. It starts just like that every time, but if I plug the USB cable in it, it doesn't shut down anymore, freezing with the logo on screen.
Windows won't recognize it under any circumstances, no matter what drivers I have... no adb, fastboot, odin. So it's pretty much useless...
If i restart it like 5 times, Windows eventually recognizes it as a Modem. Useless...
I have no fastboot, adb, odin (that I'm not sure if works on this phone) access... :crying:
I think it's a Soft Brick, because it starts but it has no idea what to do without the bootloader. It would generally be recoverable, but, as you can see, I don't have any method to communicate with this phone...
I would consider the jtag, with a RIFF Box. Taking the motherboard out of it and "writing the dead body", but I don't think the Riff Manager supports this sh**ty phone and I wouldn't like to pay for it...
The phone is still covered by the warranty, but I'm not sure if they are going to do it for free, because I messed with it. Basically, I can try that story: "I was doing an On The Air Update and the phone never powered on..." maybe they are going to take it... anyways...
So, I'm asking you, is it any other method to write at least the bootloader on it, any other that the ones mentioned before, methods that I have no access to ???
Click to expand...
Click to collapse
Don't know anything about your phone but all I can sare is that using flashtool, flash the stock kernel(find for your device using search box) and reinstall stock firmware or if your bootloader is unlocked, flash a different kernel with working recovery. I have xperia x10 so not even close to your phone
Bigkiler5 said:
Don't know anything about your phone but all I can sare is that using flashtool, flash the stock kernel(find for your device using search box) and reinstall stock firmware or if your bootloader is unlocked, flash a different kernel with working recovery. I have xperia x10 so not even close to your phone
Click to expand...
Click to collapse
My bootloader isn't unlocked. No one actually did that until now for this "space craft"...
I don't think that "flashtool" will be able to connect to my phone as Windows doesn't recognize it at all... And, as far as I know, flashtool is only for SONY's Xperia...
Thanks, anyway...
RO.maniac said:
My bootloader isn't unlocked. No one actually did that until now for this "space craft"...
I don't think that "flashtool" will be able to connect to my phone as Windows doesn't recognize it at all... And, as far as I know, flashtool is only for SONY's Xperia...
Thanks, anyway...
Click to expand...
Click to collapse
Like i said i have xperia x10 so i have knowledge about my device. You should ask this question in your mobile's forum. That will really help..... I think the solution they will give may be similar but in a different way.
Greets
i cant power on phone vodafone smart 2
my Vodafone won't turned on after trying to make recovery from alberto. and even did not vibrate after pressing power button to turn it on.
also it does not work at all like there are no battery attached to it. almost dead phone. and my computer not detect it anymore. and can't access fastboot or recovery screen.
do anyone fix this problem??
same problem bricked Vodafone smart ii
Yes, mine too has the same problem, pc won't see it else than Broadcom usb to com device, using a COM port and I don't know what to do as it won't start at all...
Nobody has any ideea, like on Alcatel OT908 which can be unbricked?
Many thanks
mixeristu said:
Yes, mine too has the same problem, pc won't see it else than Broadcom usb to com device, using a COM port and I don't know what to do as it won't start at all...
Nobody has any ideea, like on Alcatel OT908 which can be unbricked?
Many thanks
Click to expand...
Click to collapse
Post on your phone's forum and try to reinstall official software using pc suite(or whatever you call it)
vodacrap II bricked
Bigkiler5 said:
Post on your phone's forum and try to reinstall official software using pc suite(or whatever you call it)
Click to expand...
Click to collapse
My phone IS Vodafone Smart II that' why I did write here. Have the same problem like the others, pressing power button does nothing, phone is recognized only as Broadcom USB to Serial so I can't do anything and have no ideea what to do
mixeristu said:
My phone IS Vodafone Smart II that' why I did write here. Have the same problem like the others, pressing power button does nothing, phone is recognized only as Broadcom USB to Serial so I can't do anything and have no ideea what to do
Click to expand...
Click to collapse
It could be a hard brick and your info seems to confirm this but don't take my word for it. Search on google for issues with your device I seem to remember reply to a thread similar to this a while back.
Sent from my HTC One using Tapatalk 4 beta
**Press the thanks button if I have helped you.
---------- Post added at 09:39 PM ---------- Previous post was at 09:33 PM ----------
The I think.this is because when some phones are bricked they show the manufactures name such as on a hard bricked htc device it sometimes shows qhsusb_dload (don't quote me on that if my spelling is wrong) and it connects under a Qualcomm USB device driver. That is because sometimes on devices the chipset is made by Qualcomm but on your device the chipset is made by Broadcom and that why it shows a Broadcom named device driver.
Sent from my HTC One using Tapatalk 4 beta
**Press the thanks button if I have helped you.
Hi!
Someone has news about this topic?
bad news
cfjrocha said:
Hi!
Someone has news about this topic?
Click to expand...
Click to collapse
Yes, the bad news is that even JTAG could not repair my hard-bricked vodacrap II. My advice is to be really carefull when installing the custom android version, especially when using another sim than vodafone, some of the mods won't let you insert the network cod (eight of 1), mine didn't work with any version of the mods, sometimes I wasn't able to receive calls, sometimes to make calls, depending. Take it and keep it using vodafone or in any other case don't buy is not worthy.
i accidentally erased boot and bootloader.nor download mode nor recovery work and my pc recognize it like Broadcom USB wireless modem.Any solution?
Hi there!
I'm really hoping you guys can help me today. I tried installing the android 4.2 bootloader, following guide 2 in this thread (http://forum.xda-developers.com/showthread.php?t=2187982&highlight=android+4+2+1)
However, after following the instructions given, the rom wouldn't boot. I left it for about 15 minutes, before returning to flash touch recovery. However, this didn't work as you needed to boot into android before running it. I managed to get CWM Recovery installed on the tablet, however it caan't do anything as it just says "E: Can't mount /sdcard/". It says that on everything I try do (Obviously, the error's a little different each time, but it always starts with E: )
As I can still access fastboot, I'm hoping one of you can help me flash a new rom and get things back to normal.
Extra info:
I'm not amazing with this stuff, so please explain what you mean!
It's a TF300T, not the TF300TG
I have an SD Card if needs be.
Thanks for any help you give!
Sorry this isn't a pretty thread!
Apologies if I broke any rules, I've not really used the TF300T Forums, only the HTC Wildfire S ones!
you can try flashing the twrp 2.5 recovery. Make sure you flash the one for the 4.2.1 bootloader otherwise you will brick your tablet.
bloodyshyt said:
you can try flashing the twrp 2.5 recovery. Make sure you flash the one for the 4.2.1 bootloader otherwise you will brick your tablet.
Click to expand...
Click to collapse
Tried doing that and it came up in splitscreen and was impossible to use :/ :crying:
Unfortunately putting cwm on it means it is now bricked. Sorry
midgetman7782 said:
Tried doing that and it came up in splitscreen and was impossible to use :/ :crying:
Click to expand...
Click to collapse
You got twrp 2.5 to flash?
I am running openrecovery-twrp-2.6.0.0-tf300t-4.2.blob on 4.2.1 and having no issues.
Try it you have nothing to loose! Most people never get rid of cwm but it seems you did.
midgetman7782 said:
Tried doing that and it came up in splitscreen and was impossible to use :/ :crying:
Click to expand...
Click to collapse
Go home, splitscreen TWRP. You're drunk.
Go back to the TWRP thread and reread it again. It specifically says you'll need a particular version of the TF300T's firmware flashed before using TWRP 2.5.x, otherwise you'll have the dual display problem. To be safe, I'd flash the firmware (you can do it through fastboot) and then reflash TWRP. Worked fine for me, although I'm not touching it until more ROMs are safe with 4.2.
It lives!!!
Sorry I've been quiet over the past few days guys, I've been really busy with Sony.
Anyway, I thought I'd try to explain how I got my tablet working again...
Giving up hope, I left it just to bootloop, in hope it might somehow actually boot. I couldn't do anything else as CWM wouldn't do anything, and my tablet wasn't seen by my PC or ADB. After 45 minutes, windows 8 (8.1 to be exact ) made a noise to say that something had been connected, I jumped up (Knocking over my glass of water -_-) and sure enough, The USB devices saw something called "???????"
Obviously, this is a little thing, but I was filled with hope. I got into adb, and asked to see connected devices. It once again saw "???????" and I almost fell off my chair. I flashed the correct version of TWRP and then flashed myself a rom!
For some reason, at somepoint during the driver installation, the bootloader f*cked itself up. It became the 4.1 bootloader with 4 icons, but still said it was the 4.2 bootloader. I know it was the 4.1, because only roms for the 4.1 bootloader flash. I don't dare try flash it again though, as that's where problems arose last time, even if I'm pretty good at this whole rooting business
So long story short, I was informed I was in a hardbrick, that needed to have the motherboard replaced....and I still fixed it!
I think that as the tablet booted, connected to my PC, it installed the drivers to my PC that had been lost. So, If you're in this state, try that!
Hope this helped someone somewhere, it certainly helped me!
PS: Ever since the accident, my tablet's been INCREDIBLY laggy. Unlocking takes 5 seconds, home takes 5 seconds, app menu takes a bit longer. It lags on all menu's and so on. Any idea's why? I'm running the latest version of Paranoid Android. Oh, and the holo animation just dies.
Next time (if you still want to upgrade to 4.2 or downgrade, etc) please read carefully!!
i attempted it once (just for the lolz) i succeeded upgrading to 4.2 and downgrading back to 4.1
Sent from my TF300T using xda app-developers app
midgetman7782 said:
Sorry I've been quiet over the past few days guys, I've been really busy with Sony.
Anyway, I thought I'd try to explain how I got my tablet working again...
Giving up hope, I left it just to bootloop, in hope it might somehow actually boot. I couldn't do anything else as CWM wouldn't do anything, and my tablet wasn't seen by my PC or ADB. After 45 minutes, windows 8 (8.1 to be exact ) made a noise to say that something had been connected, I jumped up (Knocking over my glass of water -_-) and sure enough, The USB devices saw something called "???????"
Obviously, this is a little thing, but I was filled with hope. I got into adb, and asked to see connected devices. It once again saw "???????" and I almost fell off my chair. I flashed the correct version of TWRP and then flashed myself a rom!
For some reason, at somepoint during the driver installation, the bootloader f*cked itself up. It became the 4.1 bootloader with 4 icons, but still said it was the 4.2 bootloader. I know it was the 4.1, because only roms for the 4.1 bootloader flash. I don't dare try flash it again though, as that's where problems arose last time, even if I'm pretty good at this whole rooting business
So long story short, I was informed I was in a hardbrick, that needed to have the motherboard replaced....and I still fixed it!
I think that as the tablet booted, connected to my PC, it installed the drivers to my PC that had been lost. So, If you're in this state, try that!
Hope this helped someone somewhere, it certainly helped me!
PS: Ever since the accident, my tablet's been INCREDIBLY laggy. Unlocking takes 5 seconds, home takes 5 seconds, app menu takes a bit longer. It lags on all menu's and so on. Any idea's why? I'm running the latest version of Paranoid Android. Oh, and the holo animation just dies.
Click to expand...
Click to collapse
What type of Bootloop it was???? was it stuck on ASUS logo or wait animation loop??
I am in same situation..may be this miracle can happen here as well,,,,,however congratulations.....i will try and wait for 45 minutes:angel:
---------- Post added at 02:57 PM ---------- Previous post was at 02:55 PM ----------
jaffer707 said:
What type of Bootloop it was???? was it stuck on ASUS logo or wait animation loop??
I am in same situation..may be this miracle can happen here as well,,,,,however congratulations.....i will try and wait for 45 minutes:angel:
Click to expand...
Click to collapse
Once my pc detect it on ADB mode i can slove it as well
jaffer707 said:
What type of Bootloop it was???? was it stuck on ASUS logo or wait animation loop??
I am in same situation..may be this miracle can happen here as well,,,,,however congratulations.....i will try and wait for 45 minutes:angel:
---------- Post added at 02:57 PM ---------- Previous post was at 02:55 PM ----------
Once my pc detect it on ADB mode i can slove it as well
Click to expand...
Click to collapse
It was the animated one. Good luck dude!
midgetman7782 said:
It was the animated one. Good luck dude!
Click to expand...
Click to collapse
There's the difference. I don't even get that far. My tablet doesn't flash anything in fastboot, and I have no access to adb. My tab only boots to the splash screen and NO further.
______________________________
HTC Evo 4G LTE
midgetman7782 said:
Hi there!
I'm really hoping you guys can help me today. I tried installing the android 4.2 bootloader, following guide 2 in this thread (http://forum.xda-developers.com/showthread.php?t=2187982&highlight=android+4+2+1)
However, after following the instructions given, the rom wouldn't boot. I left it for about 15 minutes, before returning to flash touch recovery. However, this didn't work as you needed to boot into android before running it. I managed to get CWM Recovery installed on the tablet, however it caan't do anything as it just says "E: Can't mount /sdcard/". It says that on everything I try do (Obviously, the error's a little different each time, but it always starts with E: )
As I can still access fastboot, I'm hoping one of you can help me flash a new rom and get things back to normal.
Extra info:
I'm not amazing with this stuff, so please explain what you mean!
It's a TF300T, not the TF300TG
I have an SD Card if needs be.
Thanks for any help you give!
Sorry this isn't a pretty thread!
Apologies if I broke any rules, I've not really used the TF300T Forums, only the HTC Wildfire S ones!
Click to expand...
Click to collapse
here how i restored my TF300T JB
download your appropriate lates firmware from Asus (WW, US etc.) and extract the zip twice so you have your blob file
install your device drivers if needed (i used Google SDK ones) (and as a Tip Win8 sucks for Fastboot stuff so try to get Win7 Vista XP for this)
Reset your device with a paperclip/needle (about 2 cm down of your sdcard slot) and hold vol-down to enter fastboot
(the folowing i did at least 10 times already but didn't erase misc)
fastboot erase system
fastboot erase recovery
fastboot erase userdata
fastboot erase boot
fastboot erase misc
fastboot erase cache
fastboot -i 0x0B05 flash system c:\adb\TF300t\blob (this is my path - your's may vary depending where you stored your blob) ((also this was the first time i saw the loading bar while flashing)*
fastboot -i 0x0B05 reboot
* it also took a lot longer as it should:
C:\>fastboot -i 0x0B05 flash system c:\adb\TF300t\blob
erasing 'system'...
OKAY [ 1.695s]
sending 'system' (800935 KB)...
OKAY [133.121s]
writing 'system'...
OKAY [153.973s]
finished. total time: 288.789s
Now flash recovery.....
midgetman7782 said:
It was the animated one. Good luck dude!
Click to expand...
Click to collapse
That's not a hardbrick, 99% of the time that can be fixed. A Hardbrick is when it doesn't get past the bootloader.
Ok, I've been reading around the forum for about a week, trying to solve a problem with an original moto g (falcon). Basically my cousin got the moto g a few years back, and I, in my ignorance, tried to root the device for him. What I can remember was oem unlocking the bootloader with Motorola's unlock code through their website and adb. then my cousin freaked about the warranty warning on the boot animation, and decided against it. So cut to now, I'm a little more experienced, the phone's years old now, and he'd like to refresh it with a new rom, which I suggested, trying to help him. So forgetting what I'd originally done those years ago, I started the process of rooting the phone, installing a custom recovery, to hopefully put a lighter rom on it for him.
OK so it's a UK Retail on tesco mobile, moto g xt1032 running Android 5.1.
in bootloader menu it says "Device Locked status 2", dunno what this is in relation to.
first I checked the bootloader was still unlocked, and adb said it was. so I tried to use CF-autoroot to finish the job, but there was issues. it restarted the phone into fastboot mode, but when the script started, pc end did nothing, on the phone it said, "flashing unlock" and just sat there for 10-15mins doing nothing (i left it the time, just incase it was doing it).
So i read a little more, and found because i'd already unlocked the bootloader, I could just flash a custom recovery and root from adb? so I downloaded the latest twrp and tried. I was unable to do so. it said the partition wasn't the right size? should have documented it, but really didn't expect to run into any problems.
So I restarted and tried to do my usual fallback, and flash the factory image and start again, But couldn't find a source for the specific img, and tried to keep fighting on.
So I noticed that the phone wouldn't respond to adb or fastboot once in fastboot mode, when in android with usb debugging, no problems, in fastboot, didn't show up as adb devices?
I tried booting into the recovery from the bootloader menu, and got a no command. So there isn't a recovery, and I can't flash a new one? if i could find the stock recovery, I would try that.
so apart from deleting all his apps and settings, I hadn't solved the problem at all, and had to leave the job there as I couldn't find a solution.
I know this isn't the most detailed, but I've done this with quiet a few phones now, and felt I was pretty competent. I see everyday as an excuse to learn more, and like to think I have humility. So, I'm assuming I did something those years ago to damage the recovery? I'm running out of ideas, and was hoping someone could point me in the right direction?
I've lurked on xda for years, and learned so much about this kind of thing through my past experiences, but I'm stumped this time, and feel obliged to resolve the problem, as it was me who caused it.
TL DR
Can't flash recovery, no command when I try to open recovery, trying to either factory image back, or root/custom recovery it.
any insight would be much appreciated.
Hi. I just rooted and installed CM13 on an old XT1034 about two days ago. I am also sort of a ROM noob, I have ROMed a few devices, but usually but following strict step by step guides I have found here on XDA. Over the years I have some minor understanding of the process now.
I also got the "No command screen" when trying to get into TWRP recovery. The issue seems to be that if you reboot via ADB and the ROM launches it will automatically rewrite the recovery to the stock one, and when you try to go to recovery from fastboot, it gives you the "no command" error. Apparently you can get to the stock recovery from there by a hardware key combo, something like holding up vol for 10 sec then a quick press of power (I can't remeber the exact key sequence or what forum I read it in). If it does this you have to reflash TWRP again. This issue is mentioned here (http://wiki.cyanogenmod.org/w/Install_CM_for_falcon) in step 8 about installing recovery. What I ended up doing was after the flash of TWRP via ADB, I manually powered down, then manually bood into fastboot by holding volume down and power, and selecting recovery. This was a bit fiddly and I had to attempt it a few times but eventually it worked and TWRP installed.
The issue with the phone not being recognized may be due to incorrect drivers. I had no issue with this because I installed the official driver package from Motorola. It is available in their website in the developer section. I don't have the URL right now.
Hopefully this helps, for me CM13 Official has been an a stable fresh start for this old device.
So I got my phone fully working minus getting into fast boot to flash TWRP (though I already have it).
This is the rundown of what happened (mind you I was drunk).
I went to change the fastboot image after drinking like 10ish or so beer not really sure anymore. Anyways I tried flashing it through TWRP. Later I realize how silly it was but it doesn't let me into fastboot anymore. (found this out later when I went to update TWRP.)
I am looking for a relatively way safe way to fix it as I'm sure I am not the first.
Some Advice on how to fix as I really don't wanna risk bricking it would be fantastic.
Thank you,
Shinobi_warrior said:
So I got my phone fully working minus getting into fast boot to flash TWRP (though I already have it).
This is the rundown of what happened (mind you I was drunk).
I went to change the fastboot image after drinking like 10ish or so beer not really sure anymore. Anyways I tried flashing it through TWRP. Later I realize how silly it was but it doesn't let me into fastboot anymore. (found this out later when I went to update TWRP.)
I am looking for a relatively way safe way to fix it as I'm sure I am not the first.
Some Advice on how to fix as I really don't wanna risk bricking it would be fantastic.
Thank you,
Click to expand...
Click to collapse
https://forum.xda-developers.com/oneplus-one/general/tool-oneplusrecovery-tool-v1-0-restore-t2991851
Maybe It's a driver issue I am having. Because what happens more specifically is fastboot menu vibrates a few times and goes to teh charging screen and doesn't allow me to flash anything (mind you this previously worked) I don't believe it is a driver issue though. Simply put I am unable to get into adb without loading the os and when the os is loaded It hangs on waiting for device. I tried manually flashing the stock logo.bin with no success..
Not sure if maybe im missing something here. Like my fastboot loads a little penguin on it instead of the stock image and then vibrates a **** load then loads the battery charger.
Shinobi_warrior said:
Maybe It's a driver issue I am having. Because what happens more specifically is fastboot menu vibrates a few times and goes to teh charging screen and doesn't allow me to flash anything (mind you this previously worked) I don't believe it is a driver issue though. Simply put I am unable to get into adb without loading the os and when the os is loaded It hangs on waiting for device. I tried manually flashing the stock logo.bin with no success..
Not sure if maybe im missing something here. Like my fastboot loads a little penguin on it instead of the stock image and then vibrates a **** load then loads the battery charger.
Click to expand...
Click to collapse
Are you able to boot into twrp? If yes,then flash this firmware.It should solve any firmware corrupt issues,i.e. you should be able to boot into fastboot again.
Thank you, YES this is exactly what I needed/looking for.
.
You have fixed/saved the Day confirmed now.