I relocked my bootloader anticipating to flash my RUU, but the bootloader doesn't recognize SD. Do I run the exe? Is it possible for me to adb w/o os? I never fked things up so bad lol. Forgot I had a custom rom...
EvoGuy2010 said:
I relocked my bootloader anticipating to flash my RUU, but the bootloader doesn't recognize SD. Do I run the exe? Is it possible for me to adb w/o os? I never fked things up so bad lol. Forgot I had a custom rom...
Click to expand...
Click to collapse
Just RUU.exe. Works fine without even relocking bootloader. Cheers!
rdasante said:
Just RUU.exe. Works fine without even relocking bootloader. Cheers!
Click to expand...
Click to collapse
I tried that, but I couldn't recognize device? It says error couldn't find blah blah...
I have no os, can't get to recovery...
EvoGuy2010 said:
I tried that, but I couldn't recognize device? It says error couldn't find blah blah...
Click to expand...
Click to collapse
Did you enable usb debugging?
---------- Post added at 05:29 PM ---------- Previous post was at 05:25 PM ----------
EvoGuy2010 said:
I have no os, can't get to recovery...
Click to expand...
Click to collapse
Which screen is your phone currently booted to? Can you get into download mode? Try pressing both volume keys and power button at the same time. We'll take it from there
I can go to download mode.
Okay, good.
Connect phone and open command on PC and issue this command: fastboot devices
Check to see if your device shows up. If it does issue this command: fastboot rebootRUU
And then flash RUU.exe from computer.
Alternatively, select 'bootloader' in download mode. Once there select recovery and let me know what happens
rdasante said:
Okay, good.
Connect phone and open command on PC and issue this command: fastboot devices
Check to see if your device shows up. If it does issue this command: fastboot rebootRUU
And then flash RUU.exe from computer.
Alternatively, select 'bootloader' in download mode. Once there select recovery and let me know what happens
Click to expand...
Click to collapse
The thing is I had a custom rom before relocking so my recovery doesn't boot. It boot loops and then after a few minutes goes back to boot loader. Right now, I can boot to boot loader and download mode. I will try a different laptop just in case the drivers aren't working. I'm taking a lecture right now so I'll do that as soon as I get home.
EvoGuy2010 said:
The thing is I had a custom rom before relocking so my recovery doesn't boot. It boot loops and then after a few minutes goes back to boot loader. Right now, I can boot to boot loader and download mode. I will try a different laptop just in case the drivers aren't working. I'm taking a lecture right now so I'll do that as soon as I get home.
Click to expand...
Click to collapse
try reflashing recovery, if you can
Reach me on Hangouts: rdasante
Faster to communicate that way.
rdasante said:
Just RUU.exe. Works fine without even relocking bootloader. Cheers!
Click to expand...
Click to collapse
rdasante said:
Reach me on Hangouts: rdasante
Faster to communicate that way.
Click to expand...
Click to collapse
Thanks for your support! I was able to flash my RUU through fat32 SD... I realized I had to use download mode, volume up, the system started installing the ruu, I'm good to go... Thank you man!
EvoGuy2010 said:
Thanks for your support! I was able to flash my RUU through fat32 SD... I realized I had to use download mode, volume up, the system started installing the ruu, I'm good to go... Thank you man!
Click to expand...
Click to collapse
Enjoy man!!
Related
I'm S-on. I was GB, rooted on ViperRom. Flashed .10 following Nils instructions. Everything was fine. Unlocked and tried to flash Amon Ra. The PC would not detect the phone. I deleted the PH98IMG and booted into recovery hoping the phone would be detected for adb. Now the phone is stuck at HBoot. It cannot find a PH98 since I stupidly deleted it and now I cannot get back to a working phone. Any sugestions are greatly appreciated. Thanks.
was your PC detecting the phone earlier?
Did you let the ruu make its second pass of the install? Did it boot normally before you went back to bootloader to flash a recovery? Also you have to be in fastboot menu to connect to usb
Sent from my ADR6425LVW using xda app-developers app
kancherlapraneeth said:
was your PC detecting the phone earlier?
Click to expand...
Click to collapse
Yes. I am positive it did before flashing the .10 RUU and i'm fairly sure it did in order for me to unlock, I just do not remember completely.
Squirrel1620 said:
Did you let the ruu make its second pass of the install? Did it boot normally before you went back to bootloader to flash a recovery? Also you have to be in fastboot menu to connect to usb
Sent from my ADR6425LVW using xda app-developers app
Click to expand...
Click to collapse
OH man, I forgot about going back into the fastboot menu. That seems to have solved it. I know have my phone back. Now I have to try and figure out why the pc is not detecting my phone. In the command prompt when I change directories to where fastbot and ADB are. I type adb devices, it does not detect the phone.
Thanks for the help on theHBoot issue. Phone is back but after booting up it flashes that it needs a SIMcard. Then loads up fine. I was able to connect thru the pc. I forgot to enable usb debugging and uncheck fastboot, but even after detected it will not let me flash amon ra. it gives me an error. I am bone tired and will try any suggestions tomorrow.
If you flashed a good ROM and your stuck in hboot, use fastboot and use the following command 'fastboot oem boot' that will force your phone to boot.
Hello,
My amaze 4g is currently running GB with the bullet proof custom rom i found here a couple years ago.
The boot loader is unlocked, and it is S-ON.
I wanted to try and update my phone to an ICS rom such as NRGZ28's energy Rom found here: http://forum.xda-developers.com/showthread.php?t=1362759.
First attempt, I factory reset the phone, cleared cache and cleared dalvik cache and flashed the rom. I chose the option to install it using the stock HTC kernel. The installation went smooth without errors until the final reboot to finalize the installation. The phone gets stuck in the white screen with the green htc logo on it. I recover using Clock Work Mod and everything is back to the old GB setting.
I assume it is because i have an outdated kernel so I go to NRGZ28's thread and download the stock kernel he has posted there. I flashed the kernel using Flash Image GUI apk. This is where the problem happens. After flashing the kernel, the phone is stuck on infinite loop at the above mentioned htc screen.
I flash the energy rom with the newly flashed stock kernel and the phone finally gets past the htc logo screen, but freezes shortly after during the blue animated splash screen and proceeds to repeat this. I can get into boot loader just fine, but am unable to get my phone working again even after a Clock work mod recovery.
please help!!
There is a special process you have to follow when going from GB to ICS, you can't just flash the latest kernel and expect it to work with ICS.
I would do a full wipe/factory reset, then follow the instructions here to upgrade to ICS stock, then you can install whatever ICS ROM you want:
http://forum.xda-developers.com/showpost.php?p=26865752&postcount=27
---------- Post added at 11:33 AM ---------- Previous post was at 11:27 AM ----------
Here is another, possibly more helpful link. It gives step by step instructions, make sure to follow the ones for S=On users (assuming you are S=On).
http://forum.xda-developers.com/showpost.php?p=25215207&postcount=2
I see. Thank you. I will try that right now. I will post an update soon.
o_jake said:
There is a special process you have to follow when going from GB to ICS, you can't just flash the latest kernel and expect it to work with ICS.
I would do a full wipe/factory reset, then follow the instructions here to upgrade to ICS stock, then you can install whatever ICS ROM you want:
http://forum.xda-developers.com/showpost.php?p=26865752&postcount=27
---------- Post added at 11:33 AM ---------- Previous post was at 11:27 AM ----------
Here is another, possibly more helpful link. It gives step by step instructions, make sure to follow the ones for S=On users (assuming you are S=On).
http://forum.xda-developers.com/showpost.php?p=25215207&postcount=2
Click to expand...
Click to collapse
Alright now I'm having a completely unrelated trouble trying to re-lock my bootloader. Yes, I am S-on. I've tried to factory reset but the phone still ends up looping on the htc logo screen. I type in "fastboot oem lock" on sdk but it just hangs at "waiting for device".
DougieJK said:
Alright now I'm having a completely unrelated trouble trying to re-lock my bootloader. Yes, I am S-on. I've tried to factory reset but the phone still ends up looping on the htc logo screen. I type in "fastboot oem lock" on sdk but it just hangs at "waiting for device".
Click to expand...
Click to collapse
Are you able to get into the bootloader, fastboot, or recovery? I'm unsure of which HTC screen you are talking about, if it is the one before trying to boot into Android then I would just ignore it for now. If you're having trouble relocking the bootloader, you might try this toolkit, which includes a tool to relock the bootloader: http://forum.xda-developers.com/showthread.php?t=1493905
All this stuff can probably be found in the HTC Amaze Bible, which you should probably familiarize yourself with before messing around and potentially bricking your phone. http://forum.xda-developers.com/showthread.php?t=1679486
o_jake said:
Are you able to get into the bootloader, fastboot, or recovery? I'm unsure of which HTC screen you are talking about, if it is the one before trying to boot into Android then I would just ignore it for now. If you're having trouble relocking the bootloader, you might try this toolkit, which includes a tool to relock the bootloader: http://forum.xda-developers.com/showthread.php?t=1493905
All this stuff can probably be found in the HTC Amaze Bible, which you should probably familiarize yourself with before messing around and potentially bricking your phone. http://forum.xda-developers.com/showthread.php?t=1679486
Click to expand...
Click to collapse
Yes, it is the screen right before it boots onto your phone's lock screen or main screen. Yes, I can get into the bootloader, fastboot, and the recovery without any problems.
DougieJK said:
Yes, it is the screen right before it boots onto your phone's lock screen or main screen. Yes, I can get into the bootloader, fastboot, and the recovery without any problems.
Click to expand...
Click to collapse
If you can get into the bootloader, fastboot, and recovery, then you should be able to continue the steps and get it working again. Try the Toolkit method of relocking bootloader and continue upgrade to ICS.
o_jake said:
If you can get into the bootloader, fastboot, and recovery, then you should be able to continue the steps and get it working again. Try the Toolkit method of relocking bootloader and continue upgrade to ICS.
Click to expand...
Click to collapse
The all-in-one toolkit is not recognizing my device. Not sure if it's a problem with windows or the toolkit.
Also, it seems the toolkit only works if you are able to actually get to your phone's home screen, which I am unable to do.
So frustrating.....
DougieJK said:
The all-in-one toolkit is not recognizing my device. Not sure if it's a problem with windows or the toolkit.
Also, it seems the toolkit only works if you are able to actually get to your phone's home screen, which I am unable to do.
So frustrating.....
Click to expand...
Click to collapse
Here are some more instructions: http://forum.xda-developers.com/showthread.php?t=1575550&highlight=relock+bootloader
It seems as though the problem is with ADB communicating with your phone. Type in "ADB devices" to see if it is detecting your phone.
Also make sure the file "fastboot.exe" is in the same folder as your ADB file that your command prompt is using.
---------- Post added at 03:12 PM ---------- Previous post was at 03:03 PM ----------
Also are you in bootloader or fastboot when you are trying to do this? I believe you should be in fastboot.
To enter fastboot: Boot into bootloader (hold power and volume down button), scroll down to fastboot, hit the power button.
Now try executing the fastboot command using adb. (remember to make sure fastboot.exe is in same folder as adb)
Alright, so I got it relocked by hooking it up to an old tower. It seems it was an issue with windows not recognizing my phone for some reason.
NOW, there's a new problem. On the bootloader menu, on the top it says "RELOCKED". I choose the recovery option, and it immediately takes me back to the bootloader menu displaying a "Security Warning" message under "RELOCKED".
I am going to cry.:crying:
DougieJK said:
Alright, so I got it relocked by hooking it up to an old tower. It seems it was an issue with windows not recognizing my phone for some reason.
NOW, there's a new problem. On the bootloader menu, on the top it says "RELOCKED". I choose the recovery option, and it immediately takes me back to the bootloader menu displaying a "Security Warning" message under "RELOCKED".
I am going to cry.:crying:
Click to expand...
Click to collapse
This is good... I think. You can now move on to the next step in these instructions: http://forum.xda-developers.com/showthread.php?t=1575550&highlight=relock+bootloader
You have to rename the RUU to what is says in that link, place it on an external SD card, then reboot into bootloader. Then it should automatically install the update (there might be a prompt, just hit yes).
o_jake said:
This is good... I think. You can now move on to the next step in these instructions: http://forum.xda-developers.com/showthread.php?t=1575550&highlight=relock+bootloader
You have to rename the RUU to what is says in that link, place it on an external SD card, then reboot into bootloader. Then it should automatically install the update (there might be a prompt, just hit yes).
Click to expand...
Click to collapse
Yes!!! I finally got it to work! Oh my god thank you so much. Thanks for being so patient with me. I dont know what more i can do do express my gratitude. It just felt amazing to see everything working and falling into place after hours and hours of hopelessness.
So from here on, I assume I just get back onto the boot loader menu, Unlock the boot loader again, then flash the rom I want.
Thank you again.
DougieJK said:
Yes!!! I finally got it to work! Oh my god thank you so much. Thanks for being so patient with me. I dont know what more i can do do express my gratitude. It just felt amazing to see everything working and falling into place after hours and hours of hopelessness.
So from here on, I assume I just get back onto the boot loader menu, Unlock the boot loader again, then flash the rom I want.
Thank you again.
Click to expand...
Click to collapse
You can flash any *ICS* ROM you want. There's another process if you want to go back to GB (though I'm not sure why you would want to).
You should be able to use the Toolkit to unlock the bootloader again, and I would recommend flashing the 4ext recovery while you're at it. From there you should be good!
o_jake said:
You can flash any *ICS* ROM you want. There's another process if you want to go back to GB (though I'm not sure why you would want to).
You should be able to use the Toolkit to unlock the bootloader again, and I would recommend flashing the 4ext recovery while you're at it. From there you should be good!
Click to expand...
Click to collapse
is the 4ext recovery preferred over Clockwork?
DougieJK said:
Alright, so I got it relocked by hooking it up to an old tower. It seems it was an issue with windows not recognizing my phone for some reason.
NOW, there's a new problem. On the bootloader menu, on the top it says "RELOCKED". I choose the recovery option, and it immediately takes me back to the bootloader menu displaying a "Security Warning" message under "RELOCKED".
I am going to cry.:crying:
Click to expand...
Click to collapse
Thats fine now since you are locked you can download the ruu file pertaining to your phone/carrier and put it in the root of your external sd card and boot into the bootloader and it will automatically detect the ruu and start updating. however you must rename the ruu appropriately (depending on which carrier your phone is) for T-Mobile you rename the ruu file ph85img and it detects it automatically. Good luck
Sent from my HTC_Amaze_4G using xda app-developers app
DougieJK said:
is the 4ext recovery preferred over Clockwork?
Click to expand...
Click to collapse
Yeah. You might like it better too.
hatlesssandman said:
Thats fine now since you are locked you can download the ruu file pertaining to your phone/carrier and put it in the root of your external sd card and boot into the bootloader and it will automatically detect the ruu and start updating. however you must rename the ruu appropriately (depending on which carrier your phone is) for T-Mobile you rename the ruu file ph85img and it detects it automatically. Good luck
Sent from my HTC_Amaze_4G using xda app-developers app
Click to expand...
Click to collapse
Yep I was just overreacting. After I renamed the ruu file, everything fell into place and my phone is now functioning with ICS.
So apparently, my phone isn't rooted anymore? is this normal?
Flashed 4ext using the all-in-one tool kit. Nothing happened. Can't run any apps that require root. I'm confused.
Yeah, that's totally normal after flashing an RUU and relocking the bootloader. Just re-root, here's a really easy tool for it: http://theunlockr.com/2012/05/01/how-to-root-htc-amaze-4g/
o_jake said:
Yeah, that's totally normal after flashing an RUU and relocking the bootloader. Just re-root, here's a really easy tool for it: http://theunlockr.com/2012/05/01/how-to-root-htc-amaze-4g/
Click to expand...
Click to collapse
That tool doesn't work for some reason, even though its the tool I used when I first rooted my phone. I just went and did the fastboot flash unlock_code.bin to unlock my phone again.
But for some reason, I can't get 4ext to flash... I went through the steps in the link you provided but my phone doesn't show the app nor am i able to access it through the recovery option from the boot loader menu.
hi guys im a total noob bought a droid dna on craigslist that was rooted. i tried to set back to stock with ruu got message error 158. i then tried hboot method and when i put cmd fastboot oem writeflagsecure 3 my phone now says tampered ,relocked, security warning and when you reboot just keeps going to fast boot menu.again im new to this and dont know what im doing so maybe i shouldnt have dabbled with it...ill attach a pic of the screen its a red employee edition droid dna... thanks for any help you can offer
Leave it alone! Go to recovery and delete data and reboot the phone.
Sent from my HTC6435LVW using XDA Premium HD app
ifi try recovery or anything just brings me back to the same screen
worm1977 said:
hi guys im a total noob bought a droid dna on craigslist that was rooted. i tried to set back to stock with ruu got message error 158. i then tried hboot method and when i put cmd fastboot oem writeflagsecure 3 my phone now says tampered ,relocked, security warning and when you reboot just keeps going to fast boot menu.again im new to this and dont know what im doing so maybe i shouldnt have dabbled with it...ill attach a pic of the screen its a red employee edition droid dna... thanks for any help you can offer
Click to expand...
Click to collapse
Did you know if it had an Engineer's HBOOT before? Writeflagsecure 3 is to remove S-OFF. You didn't need to do that to go stock.
Try flashing a recovery?
If this for insurance purposes? Just wondering what you're trying to do with your phone since it was working when you got it.
karn101 said:
Did you know if it had an Engineer's HBOOT before? Writeflagsecure 3 is to remove S-OFF. You didn't need to do that to go stock.
Try flashing a recovery?
If this for insurance purposes? Just wondering what you're trying to do with your phone since it was working when you got it.
Click to expand...
Click to collapse
i think i tried to flash recovery. i just want to get it to work so i can use it or sell it. when it poered up normally it had the red writing on the bottom that said for htc developer purposes also instead of the dna boot up it said htc one
worm1977 said:
i think i tried to flash recovery.
Click to expand...
Click to collapse
That isn't a good sign. What steps did you take to flash a recovery?
karn101 said:
That isn't a good sign. What steps did you take to flash a recovery?
Click to expand...
Click to collapse
tried recovery then reboot on phone just takes me to the same screen. also believe i tried fastboot-flash recovery
worm1977 said:
tried recovery then reboot on phone just takes me to the same screen. also believe i tried fastboot-flash recovery
Click to expand...
Click to collapse
No offense, but you keep saying things like "i think" or I "believe"; if you want our help, we need to know if you did it or not.
What recovery were you flashing?
Basically, what I'm saying is you might have deleted your recovery since you're saying that you keep ending up on the bootloader. You need to flash a recovery into your phone. If this doesn't make sense, just let me know and I'll point you in the right direction.
EDIT:
Follow these directions and then select RECOVERY from your bootloader. Let us know what happens please.
http://forum.xda-developers.com/showthread.php?t=1994662
karn101 said:
No offense, but you keep saying things like "i think" or I "believe"; if you want our help, we need to know if you did it or not.
What recovery were you flashing?
Basically, what I'm saying is you might have deleted your recovery since you're saying that you keep ending up on the bootloader. You need to flash a recovery into your phone. If this doesn't make sense, just let me know and I'll point you in the right direction.
Click to expand...
Click to collapse
It had clock work mod on it.no offense taken im just new to this and its kind if confusing to me.since it wouldnt boot thru ruu thats when I tried the hboot method.i dont quite understand the cmd's and flashing I guess.
karn101 said:
No offense, but you keep saying things like "i think" or I "believe"; if you want our help, we need to know if you did it or not.
What recovery were you flashing?
Basically, what I'm saying is you might have deleted your recovery since you're saying that you keep ending up on the bootloader. You need to flash a recovery into your phone. If this doesn't make sense, just let me know and I'll point you in the right direction.
EDIT:
Follow these directions and then select RECOVERY from your bootloader. Let us know what happens please.
http://forum.xda-developers.com/showthread.php?t=1994662
Click to expand...
Click to collapse
ok after i download do i just try to flash thru the adb commands?
worm1977 said:
It had clock work mod on it.no offense taken im just new to this and its kind if confusing to me.since it wouldnt boot thru ruu thats when I tried the hboot method.i dont quite understand the cmd's and flashing I guess.
Click to expand...
Click to collapse
I hear you, it can be overwhelming at first. I've been flashing since the WM 6.5 days and still don't know as much as some of the people here!
When you select RECOVERY, it's bringing you back to the BOOTLOADER screen, right?
If that's the case, the RECOVERY may have been removed, which is why I'm saying to flash a new one in. Did you follow the instructions on that thread I linked to?
---------- Post added at 04:04 AM ---------- Previous post was at 03:53 AM ----------
worm1977 said:
ok after i download do i just try to flash thru the adb commands?
Click to expand...
Click to collapse
Just saw this. No, you should be using fastboot commands, not ADB
fastboot flash recovery recovery.img
To begin, do you have the Android SDK installed on your computer? (Platform Tools)
You save the TWRP .img file in that folder.
Shift+Right Click on the folder and click Open Command Prompt Here
The phone should be connected to the PC
From the BOOTLOADER, go to FASTBOOT
It should say FASTBOOT USB
You can double check by typing 'fastboot devices'
Then run 'fastboot flash recovery recovery.img'
recovery.img will be named whatever your TWRP file is named
Then for good measure do 'fastboot reboot'
Now, you should be back in BOOTLOADER
Go to RECOVERY, and what do you see?
karn101 said:
I hear you, it can be overwhelming at first. I've been flashing since the WM 6.5 days and still don't know as much as some of the people here!
When you select RECOVERY, it's bringing you back to the BOOTLOADER screen, right?
If that's the case, the RECOVERY may have been removed, which is why I'm saying to flash a new one in. Did you follow the instructions on that thread I linked to?
---------- Post added at 04:04 AM ---------- Previous post was at 03:53 AM ----------
Just saw this. No, you should be using fastboot commands, not ADB
fastboot flash recovery recovery.img
yeah fastboot sorry. im at work now ill try it when i get home in 2 hours i have the sdk downloaded
To begin, do you have the Android SDK installed on your computer? (Platform Tools)
You save the TWRP .img file in that folder.
Shift+Right Click on the folder and click Open Command Prompt Here
The phone should be connected to the PC
From the BOOTLOADER, go to FASTBOOT
It should say FASTBOOT USB
You can double check by typing 'fastboot devices'
Then run 'fastboot flash recovery recovery.img'
recovery.img will be named whatever your TWRP file is named
Then for good measure do 'fastboot reboot'
Now, you should be back in BOOTLOADER
Go to RECOVERY, and what do you see?
Click to expand...
Click to collapse
i get home in 2 hours ill try then. i have sdk installed and was using fastboot commands
worm1977 said:
i get home in 2 hours ill try then. i have sdk installed and was using fastboot commands
Click to expand...
Click to collapse
Cool. Same here. I work 2300-0700 hours.
karn101 said:
Cool. Same here. I work 2300-0700 hours.
Click to expand...
Click to collapse
down loaded that goo manager tried fastboot flash recovery GooManager_2.1.2.img said unknown error cant load GooManager
worm1977 said:
down loaded that goo manager tried fastboot flash recovery GooManager_2.1.2.img said unknown error cant load GooManager
Click to expand...
Click to collapse
You need to flash a recovery twrp is probably the best one. Goomanager is a app use to download and install ROMs.
Sent from my HTC6435LVW using Tapatalk 2
coachcrey said:
You need to flash a recovery twrp is probably the best one. Goomanager is a app use to download and install ROMs.
Sent from my HTC6435LVW using Tapatalk 2
Click to expand...
Click to collapse
What he said ^^
Here are the direct links.
http://techerrata.com/browse/twrp2/dlx
I'd suggest downloading 2.5 as 2.6 gave me issues.
karn101 said:
What he said ^^
Here are the direct links.
http://techerrata.com/browse/twrp2/dlx
I'd suggest downloading 2.5 as 2.6 gave me issues.
Click to expand...
Click to collapse
I've had no problems with 2.6 personally but either one will work. Once your in
Recovery you can download a ROM on your computer and on adb use.
adb push "C:\Documents and Settings\Josh\My Documents\Downloads\ViperDNA_1.3.5.zip" sdcard
Clearly that's how I would do it via my computer after you type adb push you can hit the space bar and drag the file to the command prompt and drop it there that will do the dirty work lol then you just hit space and tell it to install on the sdcard.
Dont let your phone or computer go to sleep or the push will corrupt the file it can take up to 10 mins to transfer the file and once you hit enter it won't acknowledge its actually transferring Dont worry it is. It will tell you when its done how long it took and how much it transfered. After that you can flash the ROM and you should be golden man!
Sent from my HTC6435LVW using Tapatalk 2
coachcrey said:
I've had no problems with 2.6 personally but either one will work. Once your in
Recovery you can download a ROM on your computer and on adb use.
adb push "C:\Documents and Settings\Josh\My Documents\Downloads\ViperDNA_1.3.5.zip" sdcard
Clearly that's how I would do it via my computer after you type adb push you can hit the space bar and drag the file to the command prompt and drop it there that will do the dirty work lol then you just hit space and tell it to install on the sdcard.
Dont let your phone or computer go to sleep or the push will corrupt the file it can take up to 10 mins to transfer the file and once you hit enter it won't acknowledge its actually transferring Dont worry it is. It will tell you when its done how long it took and how much it transfered. After that you can flash the ROM and you should be golden man!
Sent from my HTC6435LVW using Tapatalk 2
Click to expand...
Click to collapse
thanks guys im going to try it when i get home in the morning...lol i got alot to learn!!
worm1977 said:
thanks guys im going to try it when i get home in the morning...lol i got alot to learn!!
Click to expand...
Click to collapse
Not a problem man I hope this helped let me know if your still having issues I'm no dev but I have gathered a plethora of knowledge over the years playing with stuff.
Sent from my HTC6435LVW using Tapatalk 2
@worm1977 any luck man?
Sent from my HTC6435LVW using Tapatalk 2
I flashed a backup from twrp recovery then it was successful but when I rebooted my device it was stuck on an endless boot. I was able to get to twrp recovery then i bootedinto the bootloader I dont know why but i relocked the bootloader using oem lock. then it booted up and now is stock on the htc logo. i thought it would boot up then i was going to unlock the bootloader again thinking it would fix it. i was not thinking straight. now my phone is not being picked by my pc when using adb devices. please help
please
thank you
JOE180360 said:
i was going to unlock the bootloader again thinking it would fix it. i was not thinking straight.
Click to expand...
Click to collapse
I think you mean you relocked the bootloader again, since that is what it said in your PM to me; and it makes more sense (based on what you are saying).
Relocking as you now know, is not (in itself) going to return you to stock. Think about that, where would the necessary stock ROM and other files magically come from?
JOE180360 said:
now my phone is not being picked by my pc when using adb devices. please help
Click to expand...
Click to collapse
adb only works when the phone is booted, and possibly in recovery. It will never work in bootloader or fastboot mode.
Check to see if the command works in fastboot mode: fastboot devices
If so, since you are already RELOCKED, just run the 4.28.502.2 RUU (as I've seen you asked for in another thread, which I also answered).
Thanks man.
redpoint73 said:
I think you mean you relocked the bootloader again, since that is what it said in your PM to me; and it makes more sense (based on what you are saying).
Relocking as you now know, is not (in itself) going to return you to stock. Think about that, where would the necessary stock ROM and other files magically come from?
adb only works when the phone is booted, and possibly in recovery. It will never work in bootloader or fastboot mode.
Check to see if the command works in fastboot mode: fastboot devices
If so, since you are already RELOCKED, just run the 4.28.502.2 RUU (as I've seen you asked for in another thread, which I also answered
I am charging m phone right now. hopefully everything goes well. thanks for finding the ruu.
Click to expand...
Click to collapse
help
redpoint73 said:
I think you mean you relocked the bootloader again, since that is what it said in your PM to me; and it makes more sense (based on what you are saying).
Relocking as you now know, is not (in itself) going to return you to stock. Think about that, where would the necessary stock ROM and other files magically come from?
adb only works when the phone is booted, and possibly in recovery. It will never work in bootloader or fastboot mode.
Check to see if the command works in fastboot mode: fastboot devices
If so, since you are already RELOCKED, just run the 4.28.502.2 RUU (as I've seen you asked for in another thread, which I also answered).
Click to expand...
Click to collapse
the command works but the ruu is saying it cant pickup the device
will the ruu work if there's no image version on the phone.
JOE180360 said:
the command works but the ruu is saying it cant pickup the device
Click to expand...
Click to collapse
theres no image version on the phone. will it still work
the ruu started and is stuck at 14% sening.....
JOE180360 said:
theres no image version on the phone. will it still work
Click to expand...
Click to collapse
it stated uo great then now is stuck at 14%. what should i do?
TAHNK YOU!!!!!!!
JOE180360 said:
it stated uo great then now is stuck at 14%. what should i do?
Click to expand...
Click to collapse
Your a real life saver man. thanks to you i got my phone back. i probably would have never found the ruu with out you.
Thanks so much.
Trying to re-install TWRP after the marshmallow update, and now when i reboot the device, an error pops up over the LG boot screen saying my software cant be checked for corruption. Not sure what i did or how to fix this issue, any and all help is accepted please!!
Means the bootloaders unlocked
Sent from my LG-H901 using XDA-Developers mobile app
---------- Post added at 10:24 AM ---------- Previous post was at 10:24 AM ----------
Let it boot
Sent from my LG-H901 using XDA-Developers mobile app
if it is unlocked, i cant load twrp.
Bildo41383 said:
if it is unlocked, i cant load twrp.
Click to expand...
Click to collapse
There's no twrp for it that I know of yet
Sent from my LG-H901 using XDA-Developers mobile app
Bildo41383 said:
if it is unlocked, i cant load twrp.
Click to expand...
Click to collapse
You flashed old recovery for lollipop on mm, that's your problem. If the computer recognizes your phone you'll have to flash the stock recovery img for mm, when it is available. Try pressing and holding volume down while plugging in usb connected to pc. You should be able to enter fastboot mode that way.
Swizzle82 said:
You flashed old recovery for lollipop on mm, that's your problem. If the computer recognizes your phone you'll have to flash the stock recovery img for mm, when it is available. Try pressing and holding volume down while plugging in usb connected to pc. You should be able to enter fastboot mode that way.
Click to expand...
Click to collapse
hahaha, well now that makes sense. who brought the new guy, hahaha. thanks for the info.
I can get into the fastboot menu, but its stuck at the reboot screen so i cant continue with the process after than, and then my computer gets stuck "waiting for devices". oh well, phone still works right now, ill just have to wait for the super groovy dev on here to put out the marshmallow software that i require.
again thanks for the knowledge.
i did the update via LG Bridge and it seems to have relocked my bootloader.
YrrchSebor said:
i did the update via LG Bridge and it seems to have relocked my bootloader.
Click to expand...
Click to collapse
Of course. It should be able to be unlocked again from what I'm seeing.
Same as before, fastboot oem unlock or whatever it was, but when I did that under LP, I don't remember the phone resetting everything back to square one, which it does now.
Swizzle82 said:
Of course. It should be able to be unlocked again from what I'm seeing.
Click to expand...
Click to collapse
chernabog88008 said:
Same as before, fastboot oem unlock or whatever it was, but when I did that under LP, I don't remember the phone resetting everything back to square one, which it does now.
Click to expand...
Click to collapse
Unlocking the bootloader factory resets.
There is two for mm v10 already, and the bootloader is unlocked, the problem is that a lot of the fastboot commands are locked up... So we can't fastboot recovery, and without that we can't root.
Common sense isn't all that common