Related
Hi there!
The RAM hack for the G1 is very popular, and EVERYONE tells fastboot is the best way to flash this. BUT, in this version it is S-On and no fastboot options. Is there a way to get S-Off on this thing? So why is everyone liking fastboot and loving it? So now nobody can use fastboot, only with DangerSPL. Of course I know that it is the standard MT3G HBOOT and SPL, but asking again, is there a way to enable fastboot on this badboy? Thanks in advance!
(I still support Recovery as my PERMANENT flashing tool!)
From what I understand:
Fastboot can only flash if it is a S-Off Hboot.
Our options seem to be to flash a temp Hboot with S-Off, flash with Fastboot, then back to the S-On Hboot. Flash something twice to flash something once. Hmm.
Or, Flash thru recovery.
Personally, I see the "Use Fastboot" method, but I also think it's dang silly to change the engine in your car so you can repaint the body, but the body color doesn't match the engine, so you replace the engine with the original. I'd rather just repaint the car in one step.
Use recovery if you want to. Use Fastboot if you want to. It's YOUR PHONE. What are 'they' going to do? Turn Apple on you, and stop you from using your phone?
What's next? We're not allowed to install and use Linux instead of Windows or OSX?
I say, do whatever method you want. If it works, why not?
Saying "only use this method" is just plain silly. It's about choice. While it may be "preferred" it is NOT the only way.
If you CAN'T flash using Fastboot, flash using recovery. If you look at many of those threads, they also want you to use superwipe. That can only flash thru recovery. And Fastboot can't wipe as well as that.
So, use whatever method works for you.
cwwilson721 said:
From what I understand:
Fastboot can only flash if it is a S-Off Hboot.
Our options seem to be to flash a temp Hboot with S-Off, flash with Fastboot, then back to the S-On Hboot. Flash something twice to flash something once. Hmm.
Or, Flash thru recovery.
Personally, I see the "Use Fastboot" method, but I also think it's dang silly to change the engine in your car so you can repaint the body, but the body color doesn't match the engine, so you replace the engine with the original. I'd rather just repaint the car in one step.
Use recovery if you want to. Use Fastboot if you want to. It's YOUR PHONE. What are 'they' going to do? Turn Apple on you, and stop you from using your phone?
What's next? We're not allowed to install and use Linux instead of Windows or OSX?
I say, do whatever method you want. If it works, why not?
Saying "only use this method" is just plain silly. It's about choice. While it may be "preferred" it is NOT the only way.
If you CAN'T flash using Fastboot, flash using recovery. If you look at many of those threads, they also want you to use superwipe. That can only flash thru recovery. And Fastboot can't wipe as well as that.
So, use whatever method works for you.
Click to expand...
Click to collapse
That's what I am saying: I have made a guide for doing this with recovery and everyone is saying why do you do that and saying just do it with fastboot. I have told them a million times that it is the choice of the user and not me and they are pushing people to do it with fastboot like it is the only option. I think that's enough, lots of people did this with recovery and no one has had a single complaint so far. What was the point of recovery anyway? To flash ROMs if you dont want to set up your computer, plug in your phone and THEN flash stuff. It's actually totally not making sense at all! I am thinkng tp put a poll to decide what is the best to do.
To put it LOUD and CLEAR: FASTBOOT IS NOT YOUR ONLY OPTION!!!!!!!!!!!!!!!!!!!!!!!!!!!!
If you support this, post a reply and just type in 'fastboot' or 'recovery' for what you use the most. Thanks in advance (again)
I use them both.
Whatever works. If I happen to have my phone plugged in to a USB port, I'll try to use Fastboot. If I don't, I'll just flash thru recovery. Sometimes, I HAVE to use Recovery.
Whatever works.
I think the point isn't fully clear.
Fastboot is nice but not the only method
When flashing something to your phone that may cause you to brick it, radio or hboot namely you should use fastboot as it has the proper checks to lessen the chance of a brick.
If you are just flashing roms and so forth recovery and fastboot it won't matter as a brick is so unlikely.
After you flash the .13d hboot you loose out on most fastboot commands due to the base of the spl. Chances are you won't be flashing a new radio or hboot with the .13d hboot so not having things like fastboot flash doesn't matter so much and the extra 14mb of ram is a fair tradeoff for this.
Yes you can flash the 2708+ update with fastboot and and with recovery, and unless you aren't good at following directions chances are you won't brick your phone. But it is much harder to brick it with fastboot.
As for roms I only use recovery to flash because my hboot won't allow fastboot flash
Sent from my HTC Vision using xda premium
Yeah, you are right, AGAIN. My HBOOT is not compatible for fastboot and for others too.
I think fastboot is only good if you want to change Radio/SPL, for other stuff you just can use recovery. I just wanted to say that Fastboot is not so super awesome as other people think, and it's not the only way to go. You can't make any mistakes if you don't follow it. Plain and simple. It all comes to that, don't it?
Probably you should read a bit about the different kinds of SPLs around and their possibilities. Even the 0013d has fastboot capabilities, you can for example flash an .nbh with it, but that's not the main point.
The main reason why you shouldn't use recovery to flash radio/spl is *how* flashing is done by recovery: Flashing happens when re-booting your phone and a flag is set which says "reboot into recovery". This flag prevents the phone from accepting any other keys pressed, i.e. you are no longer able to press the home-button to go to recovery or the back-button to go to fastboot. If you are in this mode and for some reason (incompatible radio / spl / bad flash / ...) your recovery kernel cannot be startet you have a bricked phone. Using fastboot this cannot happen, because of that it's much more secure. That's the reason why everybody is telling not to flash radio/spl using recovery.
Now it's on you to choose.
AndDiSa said:
Probably you should read a bit about the different kinds of SPLs around and their possibilities. Even the 0013d has fastboot capabilities, you can for example flash an .nbh with it, but that's not the main point.
The main reason why you shouldn't use recovery to flash radio/spl is *how* flashing is done by recovery: Flashing happens when re-booting your phone and a flag is set which says "reboot into recovery". This flag prevents the phone from accepting any other keys pressed, i.e. you are no longer able to press the home-button to go to recovery or the back-button to go to fastboot. If you are in this mode and for some reason (incompatible radio / spl / bad flash / ...) your recovery kernel cannot be startet you have a bricked phone. Using fastboot this cannot happen, because of that it's much more secure. That's the reason why everybody is telling not to flash radio/spl using recovery.
Now it's on you to choose.
Click to expand...
Click to collapse
Yeah, but if you check everything and not be so dumb to flash it without knowing what it takes, you won't have any problems. Only for people who are new to this should flash with fastboot. But people who know what they are doing can flash with recovery and both options are still open.
TheShortybro said:
Yeah, but if you check everything and not be so dumb to flash it without knowing what it takes, you won't have any problems. Only for people who are new to this should flash with fastboot. But people who know what they are doing can flash with recovery and both options are still open.
Click to expand...
Click to collapse
If you want to flash those things through recovery do it! But you shouldn't recommend to people to do that, maybe you can be the cause of a brick
Enviado desde mi LG-E730 usando Tapatalk 2
I am not reccomending anything, just naming an option!
thats it i think its dead wont go in recovery cant get usb to see it keeps turning on and trying to go in recovery then turning of then on and so on
have you got adb running on your pc to sideload it?
ant78 said:
have you got adb running on your pc to sideload it?
Click to expand...
Click to collapse
i have but wont go to fastboot usb
what did you do with it? If you've got empty battery try to keep it on the charger for a while. Ignore it if there's no led light.
Or have you flashed a custom rom? If so, did you flash the boot img? did you also erase cache in that case? If not, go to fastboot, connect phone to computer and use the fastboot erase cache command.
EDIT: just saw your post about not getting to fastboot after I posted hmm weird indeed..
thom109 said:
what did you do with it? If you've got empty battery try to keep it on the charger for a while. Ignore it if there's no led light.
Or have you flashed a custom rom? If so, did you flash the boot img? did you also erase cache in that case? If not, go to fastboot, connect phone to computer and use the fastboot erase cache command.
EDIT: just saw your post about not getting to fastboot after I posted hmm weird indeed..
Click to expand...
Click to collapse
think i fixed it i done s-off instead of s-on or the other way round
Hello XDA I'm new to these forums but i'm hoping you can help me out.
So basically I was following a youtube video I was linked to by a guide on here on how to root my One. and everything was going smoothly and then i got to the stage where i was to boot into recovery mode so i could load into twrp. But what happens on my phone now is the loading screen for recovery mode where it says for developers only ect. will just hang there for a while then the phone will shut off and boot back into regular mode. could use some help. I wouldn't mind resetting and starting fresh if that's what's needed im just not sure how to. thank you guys!
Kdenery said:
Hello XDA I'm new to these forums but i'm hoping you can help me out.
So basically I was following a youtube video I was linked to by a guide on here on how to root my One. and everything was going smoothly and then i got to the stage where i was to boot into recovery mode so i could load into twrp. But what happens on my phone now is the loading screen for recovery mode where it says for developers only ect. will just hang there for a while then the phone will shut off and boot back into regular mode. could use some help. I wouldn't mind resetting and starting fresh if that's what's needed im just not sure how to. thank you guys!
Click to expand...
Click to collapse
read this: http://forum.xda-developers.com/showthread.php?t=1435228
you will need to reflash recovery using fastboot/adb
Aldo101t said:
read this: http://forum.xda-developers.com/showthread.php?t=1435228
you will need to reflash recovery using fastboot/adb
Click to expand...
Click to collapse
first problem, how do i select charge only? and second when i try the first command code posted it just wouldn't work and when i tried it while the phone was slected on fastboot usb (just incase that would work) it said no device.
Ok i figured it out i did everything in that thread. the same thing is happening. it just says entering recovery then restarts in normal mode.
Kdenery said:
Ok i figured it out i did everything in that thread. the same thing is happening. it just says entering recovery then restarts in normal mode.
Click to expand...
Click to collapse
do you have sdk tools installed on your computer.
make sure usb debugging is on, apperently you do.
did you put the recovery image in the folder where fastboot is then run cmd(as administrator) and cd to that folder(example/:cd c:/Program Files/Android/android-sdk/platform-tools or where ever you have it)then adb reboot bootloader>enter----Then fastboot flash recovery(name of recovery image).img>enter--- then type fastboot reboot recovery
If you are unlocked already, watch this https://www.youtube.com/watch?v=rRkAHw_GmIs&feature=youtube_gdata_player
Sent from my HTCONE using Tapatalk 4 Beta
Aldo101t said:
do you have sdk tools installed on your computer.
make sure usb debugging is on, apperently you do.
did you put the recovery image in the folder where fastboot is then run cmd(as administrator) and cd to that folder(example/:cd c:/Program Files/Android/android-sdk/platform-tools or where ever you have it)then adb reboot bootloader>enter----Then fastboot flash recovery(name of recovery image).img>enter--- then type fastboot reboot recovery
Click to expand...
Click to collapse
yes. the problem is that it just stalls out on the entering recovery screen. with the htc logo and motto in the middle.
Kdenery said:
yes. the problem is that it just stalls out on the entering recovery screen. with the htc logo and motto in the middle.
Click to expand...
Click to collapse
which recovery are you installing if its twrp v2.6.0.0 try 2.5.0.0 there was a bug in the 2.6 don't know if they fixed it yet.
Aldo101t said:
which recovery are you installing if its twrp v2.6.0.0 try 2.5.0.0 there was a bug in the 2.6 don't know if they fixed it yet.
Click to expand...
Click to collapse
I tried this yesterday after installing 2.6.0.1 when the problem first happened. then i tried 2.6.0.0 then 2.5.0.0 the problem never went away and today i tried clockwork recovery. same thing. do i need to delete the images i've flashed onto it? if no how?
Kdenery said:
I tried this yesterday after installing 2.6.0.1 when the problem first happened. then i tried 2.6.0.0 then 2.5.0.0 the problem never went away and today i tried clockwork recovery. same thing. do i need to delete the images i've flashed onto it? if no how?
Click to expand...
Click to collapse
no i wouldn't think you do, it just overwrites the other, you're sure your bootloader is unlocked, check in settings under development option to make sure debugging is on.man you got me stumped here.
Kdenery said:
I tried this yesterday after installing 2.6.0.1 when the problem first happened. then i tried 2.6.0.0 then 2.5.0.0 the problem never went away and today i tried clockwork recovery. same thing. do i need to delete the images i've flashed onto it? if no how?
Click to expand...
Click to collapse
Are you typing "fastboot erase cache" without the quotes after you flash the recovery?
Aldo101t said:
no i wouldn't think you do, it just overwrites the other, you're sure your bootloader is unlocked, check in settings under development option to make sure debugging is on.man you got me stumped here.
Click to expand...
Click to collapse
I retried the whole process once more and made sure usb debugging was on and its just frozen again.
bigdaddy619 said:
Are you typing "fastboot erase cache" without the quotes after you flash the recovery?
Click to expand...
Click to collapse
Just tried and made sure to do this. same problem.
Perhaps i'm just being extremely retarded. I am unlocked but not rooted, i thought this was how to get rooted. but maybe im just far off.
Kdenery said:
Perhaps i'm just being extremely retarded. I am unlocked but not rooted, i thought this was how to get rooted. but maybe im just far off.
Click to expand...
Click to collapse
NO, you are NOT retarded, you install recovery, then su to get root, for all intent and purposes you're doing it all right, just can't figure out why it's not working, one more redundant question, you have fastboot under power settings disabled?? Just tryin to cover all the bases
you are installing the recovery for the m7wls(m7spr)?
Aldo101t said:
NO, you are NOT retarded, you install recovery, then su to get root, for all intent and purposes you're doing it all right, just can't figure out why it's not working, one more redundant question, you have fastboot under power settings disabled?? Just tryin to cover all the bases
you are installing the recovery for the m7wls(m7spr)?
Click to expand...
Click to collapse
fast boot is not checked. and i think/hope so, how do i check that?
Kdenery said:
fast boot is not checked. and i think/hope so, how do i check that?
Click to expand...
Click to collapse
in settings under power scroll to the bottom fastboot is there.
Sorry i guess i phrased that wrong. i'm sure fastboot is unchecked, i was asking about the second part of your post, about "you are installing the recovery for the m7wls(m7spr)?"
Kdenery said:
Sorry i guess i phrased that wrong. i'm sure fastboot is unchecked, i was asking about the second part of your post, about "you are installing the recovery for the m7wls(m7spr)?"
Click to expand...
Click to collapse
what exactly is the zip you're using,should be something like(fastboot flash recovery openrecovery-twrp-2.5.0.0-m7wls.img
I've tried
cwm-recovery-vivow
openrecovery-twrp-2.5.0.0-m7
openrecovery-twrp-2.6.0.0-m7
openrecovery-twrp-2.6.0.0-m7wls
openrecovery-twrp-2.6.0.1-m7
recovery-clockwork-6.0.3.2-m7spr
recovery-clockwork-touch-6.0.3.3-m7spr
Hey guys, I need some major help!
I was trying to update my phone earlier today, when I flashed Android Revolution HD 40.3 something very bad happened!
For some reason the ROM did not install properly, and I can't get back into recovery. I was using TWRP and the loading screen comes up for it, but it never fully launches.
I can get into the bootloader, and I tried using the Toolkit under fastboot. It seems like my phone is detected, but when I try and flash anything it doesnt work. Ive flashed both TWRP and clockword. They seem to flash because it will show the loading screen of either one, but it never actually enters the recovery. What should I do?
My phone is S-ON, I am not sure if that is what caused the problem/is what is keeping this an issue.
Thanks for your help
SMGkrome said:
Hey guys, I need some major help!
I was trying to update my phone earlier today, when I flashed Android Revolution HD 40.3 something very bad happened!
For some reason the ROM did not install properly, and I can't get back into recovery. I was using TWRP and the loading screen comes up for it, but it never fully launches.
I can get into the bootloader, and I tried using the Toolkit under fastboot. It seems like my phone is detected, but when I try and flash anything it doesnt work. Ive flashed both TWRP and clockword. They seem to flash because it will show the loading screen of either one, but it never actually enters the recovery. What should I do?
My phone is S-ON, I am not sure if that is what caused the problem/is what is keeping this an issue.
Thanks for your help
Click to expand...
Click to collapse
Does the phone just reboot before it enters recovery? I would try manually flashing a custom recovery image. Here is a link to the exact image I used.
http://forum.xda-developers.com/showthread.php?t=2173863
It's very straightforward once you have fast boot setup. Don't worry I've been in your situation myself!
JasSingh93 said:
Does the phone just reboot before it enters recovery? I would try manually flashing a custom recovery image. Here is a link to the exact image I used.
http://forum.xda-developers.com/showthread.php?t=2173863
It's very straightforward once you have fast boot setup. Don't worry I've been in your situation myself!
Click to expand...
Click to collapse
Thanks for the response!
Was your phone S-ON?? It seems that there are fixes when it is S-OFF, but not S-ON
SMGkrome said:
Thanks for the response!
Was your phone S-ON?? It seems that there are fixes when it is S-OFF, but not S-ON
Click to expand...
Click to collapse
My phone was S-ON at the time, I recently gained S-OFF. You should still be able to flash a new recovery with S-ON. S-OFF is usually only needed for flashing new radios or firmwares.
JasSingh93 said:
My phone was S-ON at the time, I recently gained S-OFF. You should still be able to flash a new recovery with S-ON. S-OFF is usually only needed for flashing new radios or firmwares.
Click to expand...
Click to collapse
How did you flash the recovery? Like I've said, I tried flashing a new recovery via the Toolkit. They do seem to flash, but I cant access the recovery. I'm not sure if my bootloader was relocked or what, but it doesn't go past the intro screen for TWRP or Clockwork
SMGkrome said:
How did you flash the recovery? Like I've said, I tried flashing a new recovery via the Toolkit. They do seem to flash, but I cant access the recovery. I'm not sure if my bootloader was relocked or what, but it doesn't go past the intro screen for TWRP or Clockwork
Click to expand...
Click to collapse
It could be possible that the toolkit is installing an incorrect version maybe? Switch off your phone. Once off hold vol - and power the phone on. This should load up HBOOT and tell you the boot loader status.
This is how I flashed recovery. I entered fastboot and used the commands from that link to flash a new recovery image. Have you used fastboot commands before?
JasSingh93 said:
It could be possible that the toolkit is installing an incorrect version maybe? Switch off your phone. Once off hold vol - and power the phone on. This should load up HBOOT and tell you the boot loader status.
This is how I flashed recovery. I entered fastboot and used the commands from that link to flash a new recovery image. Have you used fastboot commands before?
Click to expand...
Click to collapse
To be honest, I'm pretty new to the fastboot commands. I usually follow guides to root, and flashing ROMs is pretty straightforward.
SMGkrome said:
To be honest, I'm pretty new to the fastboot commands. I usually follow guides to root, and flashing ROMs is pretty straightforward.
Click to expand...
Click to collapse
If you have fastboot setup and working, just boot the phone into fastboot mode and use the commands in that link I gave you.
From fastboot. Use command "fastboot erase cache"
From fastboot. Use command "fastboot flash recovery recovery.img"
Then simply highlight "recovery", tap the power button and the phone should load up clockwordmod recovery.
Easy
JasSingh93 said:
If you have fastboot setup and working, just boot the phone into fastboot mode and use the commands in that link I gave you.
From fastboot. Use command "fastboot erase cache"
From fastboot. Use command "fastboot flash recovery recovery.img"
Then simply highlight "recovery", tap the power button and the phone should load up clockwordmod recovery.
Easy
Click to expand...
Click to collapse
Is fastboot mode just when you hold power and volume down then select fastboot?
SMGkrome said:
Is fastboot mode just when you hold power and volume down then select fastboot?
Click to expand...
Click to collapse
It is
SMGkrome said:
Is fastboot mode just when you hold power and volume down then select fastboot?
Click to expand...
Click to collapse
This is going to make me sound incompetent, but to use fastboot commands I just need to install the ADT Bundle from google for developers?
SMGkrome said:
This is going to make me sound incompetent, but to use fastboot commands I just need to install the ADT Bundle from google for developers?
Click to expand...
Click to collapse
It doesn't make you sound incompetent at all! Yes its just the bundle, then the drivers should be installed with that too. If you're not 100% sure there are plenty of guides online on how to setup fastboot.
For example: http://techbeasts.com/2013/08/26/how-to-install-adb-fastboot-drivers-on-your-windows-pc-guide/
Or if you're lazy like me you can use this: http://forum.xda-developers.com/showthread.php?p=42407269
JasSingh93 said:
It doesn't make you sound incompetent at all! Yes its just the bundle, then the drivers should be installed with that too. If you're not 100% sure there are plenty of guides online on how to setup fastboot.
For example: http://techbeasts.com/2013/08/26/how-to-install-adb-fastboot-drivers-on-your-windows-pc-guide/
Or if you're lazy like me you can use this: http://forum.xda-developers.com/showthread.php?p=42407269
Click to expand...
Click to collapse
Ah, no dice. I followed all the steps, everything seemed to work (thanks for the guide). It flashed the recovery okay. When I restarted the phone, it goes into recovery, shows clockwork mod recovery, version XX and then proceeds to try and boot into my regular system
SMGkrome said:
Ah, no dice. I followed all the steps, everything seemed to work (thanks for the guide). It flashed the recovery okay. When I restarted the phone, it goes into recovery, shows clockwork mod recovery, version XX and then proceeds to try and boot into my regular system
Click to expand...
Click to collapse
Hm, that's really strange. So recovery tried to boot, but the phone restarts and tried to boot normally?
Did you try running the command "fastboot erase cache" in fastboot mode?
JasSingh93 said:
Hm, that's really strange. So recovery tried to boot, but the phone restarts and tried to boot normally?
Did you try running the command "fastboot erase cache" in fastboot mode?
Click to expand...
Click to collapse
Yeah, basically it goes back and forth between trying to get into recovery and try to boot normally but can't boot into either
SMGkrome said:
Yeah, basically it goes back and forth between trying to get into recovery and try to boot normally but can't boot into either
Click to expand...
Click to collapse
OK so new recovery flashed, I would try running "fastboot erase cache". This commonly fixed issues with recoveries failing to boot.
JasSingh93 said:
OK so new recovery flashed, I would try running "fastboot erase cache". This commonly fixed issues with recoveries failing to boot.
Click to expand...
Click to collapse
So I owe you a beer! I guess I must have forgotten that command. Worked perfectly, phone is all good now!
Thanks for all the help
SMGkrome said:
So I owe you a beer! I guess I must have forgotten that command. Worked perfectly, phone is all good now!
Thanks for all the help
Click to expand...
Click to collapse
No worries! Glad you got it working. Happy to help!
Urbane powers off when not in cradle whenever I flash anything other than a stock img, with the exception of twrp. I can stay in TWRP and Bootloader without it being charged, and it works properly when it's on stock firmware, but if I flash a different boot.img, or a custom ROM, it shuts off whenever its not in the cradle. I know this forum is pretty much dead, but i hope hope HOPE someone can help me out here.
I hate to add to a list without contributing, but I'm having the same problem. How are you getting back to stock? I've tried flashing stock boot.img, recovery.img and system.img, still no luck. Clearly you didn't get an answer on here, but did you ever find an answer?
This was happening to me too. It was working for so long. Not sure what made it stop working.
I had the 4 cores boot img installed and it was working great till it wouldn't stay on for some reason. It was working for well over 6 months with no issues.
If the battery is the problem for you, this fix won't work. To know if this fix "COULD" work for you, jump straight to the second step, and take your watch off the cradle. Does the watch stay powered on while in fastboot mode? If yes, this fix "SHOULD" work, if not, you probably need to replace the battery.
Anyway, the following steps is what I did to get the watch working again, without it turning off out of the cradle:
These steps are assuming you have adb installed on your computer and know how to use it. If not, Google is your friend.
Went to this post and downloaded the images that were provided
Booted into the bootloader
If you can't get to the bootloader via adb, you can get to it with this method
Code:
fastboot flash boot boot.img
Code:
fastboot flash recovery recovery.img
Code:
fastboot flash system system.img
reboot to bootloader (even though you're still in bootloader)
Code:
fastboot oem lock
reboot to system
If you have a charge on the battery you should be able to take the watch off the cradle and it should be working now without powering off.
Hope this helps, and if it has please click the thanks!
xX5UN5H1N3Xx said:
I hate to add to a list without contributing, but I'm having the same problem. How are you getting back to stock? I've tried flashing stock boot.img, recovery.img and system.img, still no luck. Clearly you didn't get an answer on here, but did you ever find an answer?
Click to expand...
Click to collapse
I had this issue tried everything, ordered one battery from ebay, same result, then ordered from another site an original (more expensive) urbane battery and it worked
Check this link:
https://forum.xda-developers.com/g-w...tdown-t3729960
This fixed my phone with a similar issue.