I tried to get help last year to set up my HTC Wildfire S and ended up hard bricking it.
I have a Evo 3D now and tried to unlock using the universal toolkit, but the toolkit did not work. At the final stage the phone just restarted with no changes. Tried the old fashioned method using stk pack and HTC sync manager, but just with the Wildfire S, the Manager could not recognize the EVO 3D. I really like this phone and don't want to hard brick it as well.
I don't see any reason to try, as I really enjoy the 3D camera and every ROM I've seen either does not support 3D or the camera works poorly.
Is there something to the contrary that I missed?
LyleVertigo said:
I tried to get help last year to set up my HTC Wildfire S and ended up hard bricking it.
I have a Evo 3D now and tried to unlock using the universal toolkit, but the toolkit did not work. At the final stage the phone just restarted with no changes. Tried the old fashioned method using stk pack and HTC sync manager, but just with the Wildfire S, the Manager could not recognize the EVO 3D. I really like this phone and don't want to hard brick it as well.
I don't see any reason to try, as I really enjoy the 3D camera and every ROM I've seen either does not support 3D or the camera works poorly.
Is there something to the contrary that I missed?
Click to expand...
Click to collapse
Only ICS Sense 3.6 ROMs have fully working 3d and some of them have great camera software. So, if you want a custom ROM, my advice is to go with ISC Sense 3.6. All newer have issues. As for unlocking the phone, did you try Htc dev? Easiest and most secure way to unlock your bootloader
Sent from my Xceeded black M7 ul
donkeykong1 said:
Only ICS Sense 3.6 ROMs have fully working 3d and some of them have great camera software. So, if you want a custom ROM, my advice is to go with ISC Sense 3.6. All newer have issues. As for unlocking the phone, did you try Htc dev? Easiest and most secure way to unlock your bootloader
Sent from my Xceeded black M7 ul
Click to expand...
Click to collapse
Thanks for the info on the rom. I tried the HTC Dev after the Universal tool failed. Unfortunately, the HTC Sync cannot locate the EVO 3D, it was the exact same problem I had with the Wildfire S. There is another way if I recall but I forgot what it was that lets you enter the token. I think it was a custom program someone made.
LyleVertigo said:
Thanks for the info on the rom. I tried the HTC Dev after the Universal tool failed. Unfortunately, the HTC Sync cannot locate the EVO 3D, it was the exact same problem I had with the Wildfire S. There is another way if I recall but I forgot what it was that lets you enter the token. I think it was a custom program someone made.
Click to expand...
Click to collapse
What OS do you use on your PC? Windows 8 had some problems with htc drivers
Sent from my Xceeded black M7 ul
donkeykong1 said:
What OS do you use on your PC? Windows 8 had some problems with htc drivers
Sent from my Xceeded black M7 ul
Click to expand...
Click to collapse
I use Windows 7 64x ultimate. Could the micro usb cable be able to transmit data to the SD card np but still have a flaw that is causing this problem? The downloads I use are not corrupted, I've redownloaded them several times to be sure.
LyleVertigo said:
I use Windows 7 64x ultimate. Could the micro usb cable be able to transmit data to the SD card np but still have a flaw that is causing this problem? The downloads I use are not corrupted, I've redownloaded them several times to be sure.
Click to expand...
Click to collapse
I don't think so, but try another cable if you have one. Also, don't use USB 3 port. Did you enable USB debuging on your phone?
Sent from my Xceeded black M7 ul
donkeykong1 said:
I don't think so, but try another cable if you have one. Also, don't use USB 3 port. Did you enable USB debuging on your phone?
Sent from my Xceeded black M7 ul
Click to expand...
Click to collapse
Not connected to usb 3, and yes, phone is set to usb debugging. I'm very careful and follow directions to the T. I have read several "how to" threads but no success. I am being very careful with this phone however, and I don't want to do anything to it unless it is safe to do so.
Ok, I tried this tutorial
http://youtu.be/M3jbZZWKwkY?t=15m6s
And was able to unlock the bootloader using this. However, when I tried su-2.3.6.3-efgh-signed to root it, I got can't open error. (bad).
using revolutionary cwm v4.0.1.4
Now I tried this tutorial: http://youtu.be/Q21rX13hnUY
This one uses uses EX4 and SU 3.1.3 Instead of Revolutionary and 2.3.6.3.
Again, everything is fine until I try to install the SU. Why can't any of these zips install???? Ugh.
and that one has the exact same specs as mine. Same ver. software, android ver. ect.
I'm at a complete loss on what's going on.
All of these tutorials go from unlocking to flashing recovery to flashing Superuser, but do you need to have S-Off before you can flash Superuser?
Curious as I'm currently unlocked with 4ext and S-Off.
LyleVertigo said:
All of these tutorials go from unlocking to flashing recovery to flashing Superuser, but do you need to have S-Off before you can flash Superuser?
Curious as I'm currently unlocked with 4ext and S-Off.
Click to expand...
Click to collapse
It is not necessary to be S-OFF in order to flash a ZIP. S-OFF is mainly for getting onto new bootloader version to run newer ROMs.
Are you able to mention the errors you get from flashing the SU ZIP?
h4z3d said:
It is not necessary to be S-OFF in order to flash a ZIP. S-OFF is mainly for getting onto new bootloader version to run newer ROMs.
Are you able to mention the errors you get from flashing the SU ZIP?
Click to expand...
Click to collapse
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I renamed the files as someone mentioned it could cause it too. Didn't help though.
LyleVertigo said:
I renamed the files as someone mentioned it could cause it too. Didn't help though.
Click to expand...
Click to collapse
Are you able to link me to the download for that ZIP and also get the MD5 of the one on your SD card? I believe you might have a corrupted download. You can even try extracting the contents of the ZIP on Windows to a folder and if it shows an error, it's a bad download.
h4z3d said:
Are you able to link me to the download for that ZIP and also get the MD5 of the one on your SD card? I believe you might have a corrupted download. You can even try extracting the contents of the ZIP on Windows to a folder and if it shows an error, it's a bad download.
Click to expand...
Click to collapse
It's not a bad download, I've downloaded both versions from multiple sources. If you want to test the ones I have currently anyway, here they are.
LyleVertigo said:
It's not a bad download, I've downloaded both versions from multiple sources. If you want to test the ones I have currently anyway, here they are.
Click to expand...
Click to collapse
I just tried what you said, and I cannot unzip them in Windows. How in the world could that every download I've found be corrupt?
I DL multiple times for both files, the 3.1.3 came from SuperUser's own website and 2.3.6.3 came from this site.
LyleVertigo said:
I just tried what you said, and I cannot unzip them in Windows. How in the world could that every download I've found be corrupt?
I DL multiple times for both files, the 3.1.3 came from SuperUser's own website and 2.3.6.3 came from this site.
Click to expand...
Click to collapse
Sometimes it happens. I used to have a hard time downloading small files for some reason, they'd always corrupt, but larger files did not, it was odd. What I would personally try is downloading them via your mobile data, may work.
Also, both of your attachments were seen as corrupt on my end. You could try downloading from here:
download.chainfire.eu
h4z3d said:
Sometimes it happens. I used to have a hard time downloading small files for some reason, they'd always corrupt, but larger files did not, it was odd. What I would personally try is downloading them via your mobile data, may work.
Also, both of your attachments were seen as corrupt on my end. You could try downloading from here:
download.chainfire.eu
Click to expand...
Click to collapse
Finally, a clue. It appears that the SU zips are not corrupted when I download them, however when the recovery tries to flash them, it is then they become corrupted.
At first, one would think that it may be a bad recovery, but keep in mind I've tried Revolutionary before EXT4 and the problem was still occuring.
What could be causing the zips to become corrupt upon flashing? It can't be flashing in general, because it has been able to flash both recoveries just fine.
LyleVertigo said:
Finally, a clue. It appears that the SU zips are not corrupted when I download them, however when the recovery tries to flash them, it is then they become corrupted.
At first, one would think that it may be a bad recovery, but keep in mind I've tried Revolutionary before EXT4 and the problem was still occuring.
What could be causing the zips to become corrupt upon flashing? It can't be flashing in general, because it has been able to flash both recoveries just fine.
Click to expand...
Click to collapse
Hey, a fellow Texan!
Anyways, is it becoming corrupt after you transfer and attempt the flash, or is it becoming corrupt after the transfer (try transferring it and opening it again from the mounted drive). If it's the first, you could attempt to download another recovery, you don't have to flash it, you can simply type:
fastboot boot recovery.img
Here's a link to the recovery I'm currently using: http://forum.xda-developers.com/htc...overy-unoffical-twrp-2-7-1-0-selinux-t2831444
There's a link to 2.8.1.0 in the second post that you can attempt to use. If it's the second circumstance, what I would try to do is push the ZIP via adb. You can do this while in recovery as adb is recognized in it. Run this command to do it:
adb push file.zip /sdcard/file.zip
h4z3d said:
Hey, a fellow Texan!
Anyways, is it becoming corrupt after you transfer and attempt the flash, or is it becoming corrupt after the transfer (try transferring it and opening it again from the mounted drive). If it's the first, you could attempt to download another recovery, you don't have to flash it, you can simply type:
fastboot boot recovery.img
Here's a link to the recovery I'm currently using: http://forum.xda-developers.com/htc...overy-unoffical-twrp-2-7-1-0-selinux-t2831444
There's a link to 2.8.1.0 in the second post that you can attempt to use. If it's the second circumstance, what I would try to do is push the ZIP via adb. You can do this while in recovery as adb is recognized in it. Run this command to do it:
adb push file.zip /sdcard/file.zip
Click to expand...
Click to collapse
How would I push it? Keeps telling me device not found. adb is in C:/PhoneTools/ I have the file (Superuser3.1.3.zip) in both that folder and on SD card. I tried C:\PhoneTools>adb push Superuser313.zip /sdcard/Superuser313.zip but got a Error: device not found. Same if I tried adb push Superuser313.zip C:\PhoneTools\Superuser313.zip
LyleVertigo said:
How would I push it? Keeps telling me device not found. adb is in C:/PhoneTools/ I have the file (Superuser3.1.3.zip) in both that folder and on SD card. I tried C:\PhoneTools>adb push Superuser313.zip /sdcard/Superuser313.zip but got a Error: device not found. Same if I tried adb push Superuser313.zip C:\PhoneTools\Superuser313.zip
Click to expand...
Click to collapse
Try booting back into your phone and then pushing it through adb. Chances are not everyones device gets detected in recovery. Mine did at one point I think.
Related
Help! I have accidentally erased everything from my HOX+ and now i have no OS and my device's internal memory will not be read by my pc. Is there any way i can get something back on there?
If you can get to bootloader, and I'm sure you can.. (holding volume down while turning the phone on)
You could start by flashing the appropriate recovery. (non att is here , and the att recovery is here )
Then reboot to recovery, and side mount the sd card, and dump a rom on there. (i had to format my sd card at this time using windows.. it's ok if you need to)
Be sure to extract the boot.img to flash in fastboot before you reboot or you'll bootloop (if you have no idea what i just typed, let me google that for you)
you'll need these three files: https://www.dropbox.com/sh/q5u67wv5jjbz2te/1dV9Voar26
This thread may help.
http://forum.xda-developers.com/showthread.php?t=2051032
Bear in mind that's for the att model just be cognizant to flash international files.
Sent from my HTC EVARE_UL using xda app-developers app
can"t load the rom please help
borg00 said:
can"t load the rom please help
Click to expand...
Click to collapse
you cannot be helped
no dice
i have already tried using adb sideload and i must be doing something wrong because it says "device not found"
pelucaz491 said:
i have already tried using adb sideload and i must be doing something wrong because it says "device not found"
Click to expand...
Click to collapse
I don't know where any instructions said that.
Did you get the recovery installed?
if so, you need to click here to MOUNT sd card.. at that time, CONNECT the phone to the computer with a usb cable and then put a rom on the SD card.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
EDIT: i don't recommend the toolkit; it breeds ignorance.
The sideloading is not necessary. Just mount the SD, dump the rom, unmount the SD, and flash the rom.. then, when that's done, choose the reboot option in TWRP, reboot to bootloader, choose fastboot, and fastboot flash boot boot.img the boot.img you pulled out of the .zip from the rom you chose.
please excuse my ignorance and now that i have clicked MOUNT is something supposed to happen?
pelucaz491 said:
please excuse my ignorance and now that i have clicked MOUNT is something supposed to happen?
Click to expand...
Click to collapse
well, not on the phone. but, if you plug your phone into your computer, the SD card will magically pop up as storage on the computer. Just mount the SD, dump the rom, unmount the SD, and flash the rom.. then, when that's done, choose the reboot option in TWRP, reboot to bootloader, choose fastboot, and fastboot flash boot boot.img the boot.img you pulled out of the .zip from the rom you chose.
wdkingery said:
well, not on the phone. but, if you plug your phone into your computer, the SD card will magically pop up as storage on the computer. Just mount the SD, dump the rom, unmount the SD, and flash the rom.. then, when that's done, choose the reboot option in TWRP, reboot to bootloader, choose fastboot, and fastboot flash boot boot.img the boot.img you pulled out of the .zip from the rom you chose.
Click to expand...
Click to collapse
It does nothing on the computer either. No removable storage options or auto-play. however, HTC sync does come up.
did you go to my computer and make sure there's no extra storage on there that wasn't there a minute ago?
if there isn't, you have reached the end of my knowledge.
wdkingery said:
did you go to my computer and make sure there's no extra storage on there that wasn't there a minute ago?
if there isn't, you have reached the end of my knowledge.
Click to expand...
Click to collapse
yes i have. it does give a message "USB device not recognized" i have the drivers installed.
pelucaz491 said:
yes i have. it does give a message "USB device not recognized" i have the drivers installed.
Click to expand...
Click to collapse
I had a big driver fight when i first rooted my one x+.
only thing i can tell you is to press start button and type in device manager and hit enter.
if you see your phone with a yellow ! triangle.. you need to fix that.
make sure to disable antivirus software, and reboot after any driver installs.
also, i have seen a few posts where the USB cable was the problem; try a different one, or the one that came with the phone is preferred.
---------- Post added at 10:31 PM ---------- Previous post was at 10:25 PM ----------
also, i found this (it's for a one x but might work for you as well.. it looks promising)
I found this worked to get Win7 x64 to recognize the SD Card and ADB:
1. Uninstall the driver completely from the system (HTC MTP Device). This has to be done under the device properties. This should force the system to see a new device called "One" without a driver, under "Other Devices" in the Device Manager.
2. Install HTC Sync from http://www.htc.com/www/software/htc-sync/. Once installed, it has to update to the latest version. This is needed to install all additional drivers for SD Card access.
3. Latest HTC Drivers will be listed under C:\Program Files (x86)\HTC\HTC Driver\Driver Files
4. For ADB access, go to http://onexroot.com/one-x-root/how-to-unlock-bootloader-and-root-att-htc-one-xhtc-one-xl/ and download appropriate drivers for your Windows flavor. These are the ADB drivers. I only tested out the 64-bit drivers though as all my machines are 64-bit.
5. Download the zip, and extract. Remember the location of the files. Go into Device Manger, find "One" under "Other Devices" and Update Driver Software. Point to the new directory you made and install. The One X will now be listed in Device Manager as "My HTC" under "Android USB Devices"
6. To verify ADB, open a CMD prompt, point to Android directory and type in "adb devices". Your beautiful HTC One X should be listed.
don't give up pelucaz491. you are close.
You can't mount this phone's sd card from recovery because it is ext4, you have to use side load.
Sent from my HTC EVARE_UL using xda app-developers app
Someone with more experience has spoken. Maybe he can carry you the rest of the way; I tried.
If what he says is true, then I can no longer help, as I don't have experience with this issue. I only knew all that from my one X issues. Evidently what I was telling you is wrong for an x+.
GL
never.
mfpreach said:
You can't mount this phone's sd card from recovery because it is ext4, you have to use side load.
Sent from my HTC EVARE_UL using xda app-developers app
Click to expand...
Click to collapse
well as i said before, i have tried using that but i must have been doing something wrong. what are your ideas? im willing to try again.
pelucaz491 said:
Help! I have accidentally erased everything from my HOX+ and now i have no OS and my device's internal memory will not be read by my pc. Is there any way i can get something back on there?
Click to expand...
Click to collapse
If you have an ATT/Telus or INTL HOX+ then you can go to my TUT and get a rom back on your phone. My tut can be found here. I know it has already been mentioned in this thread but since people are trying to help out with the wrong info that is not intended for this device you might want to look at my tut and see if it will help you out.
Also, your phone is not bricked...
Cheers
Clonz said:
Can you give us anymore info? What carrier are you on...is the phone an att/telus or intl...what hboot are you running...
If you can provide more info we can more than likely help you out.
Cheers
Click to expand...
Click to collapse
of course
ATT
EVITARE_UL S-ON
UNLOCKED
HBOOT-1.32.0000
RADIO-SSD:1.09.55.17
Mistakenly erased everything including os from phone.
pelucaz491 said:
of course
ATT
EVITARE_UL S-ON
UNLOCKED
HBOOT-1.32.0000
RADIO-SSD:1.09.55.17
Mistakenly erased everything including os from phone.
Click to expand...
Click to collapse
Perfect...so I did the exact same thing with I unlocked my bootloader and put a custom recovery on...not realizing how the storage was setup I deleted my nandroid backup and everything else that was stock on the phone. So, you can definitely use my tut to get a rom back on...or you now have the choice to flash an RUU that has been provided by Football that is also listed in my tut.
If you have some specific questions for me or get stuck just let me know
Cheers
Hi All,
After a failed attempt to root my L9 769, I have an issue where when the phone is turned on, it does not boot, it goes to a screen with the LG logo and the words "security error" beneath it. The phone then powers off. The only thing I have access to on the phone is this screen and the software update mode. I used the offline flash method in my root attempt. I am sure I screwed up in the process. I have scoured the internet in an attempt to resolve this, but I have yet been able to. This seems to be a fairly common problem when a root attempt fails, however I cannot correct this.
Things I have tried:
Fastboot: I try to run fastboot, but it stops at waiting for device.
Offline flash: I tried the offline flash method, but the tool freezes at 15% saying the device cannot be found.
Online flash: The tool recognizes the phone but sees it as being up to date. I try to use the recovery option but it locks up at analyzing the phone.
I am at a loss. Any help would be greatly appreciated.
Thanks,
J
jlj012 said:
Hi All,
After a failed attempt to root my L9 769, I have an issue where when the phone is turned on, it does not boot, it goes to a screen with the LG logo and the words "security error" beneath it. The phone then powers off. The only thing I have access to on the phone is this screen and the software update mode. I used the offline flash method in my root attempt. I am sure I screwed up in the process. I have scoured the internet in an attempt to resolve this, but I have yet been able to. This seems to be a fairly common problem when a root attempt fails, however I cannot correct this.
Things I have tried:
Fastboot: I try to run fastboot, but it stops at waiting for device.
Offline flash: I tried the offline flash method, but the tool freezes at 15% saying the device cannot be found.
Online flash: The tool recognizes the phone but sees it as being up to date. I try to use the recovery option but it locks up at analyzing the phone.
I am at a loss. Any help would be greatly appreciated.
Thanks,
J
Click to expand...
Click to collapse
About offline flash I had the same problem that it couldn't connect to my device but when I used another computer it could find it.
jlj012 said:
Hi All,
After a failed attempt to root my L9 769, I have an issue where when the phone is turned on, it does not boot, it goes to a screen with the LG logo and the words "security error" beneath it. The phone then powers off. The only thing I have access to on the phone is this screen and the software update mode. I used the offline flash method in my root attempt. I am sure I screwed up in the process. I have scoured the internet in an attempt to resolve this, but I have yet been able to. This seems to be a fairly common problem when a root attempt fails, however I cannot correct this.
Things I have tried:
Fastboot: I try to run fastboot, but it stops at waiting for device.
Offline flash: I tried the offline flash method, but the tool freezes at 15% saying the device cannot be found.
Online flash: The tool recognizes the phone but sees it as being up to date. I try to use the recovery option but it locks up at analyzing the phone.
I am at a loss. Any help would be greatly appreciated.
Thanks,
J
Click to expand...
Click to collapse
You need a recovery.img from p769 and flash it through fastboot
Download https://mega.co.nz/#!7RxjnDyS!gYY7Zs6naT4fa3Oj1FfIFu2O_sfEtL1awPD-HOSOu_E
Then type in fastboot "fastboot flash recovery p4_769.img"
Sent from my LG-P769 using Tapatalk 4
I have the same issue adb won't connect no fastboot
Sent from my Amazon Kindle Fire using xda app-developers app
You need to flash the ice cream x & u boot for your device (in fastboot) to get the offline flash running again.
Some help on how to install fastboot
Did you install the omap4430 driver twice?
Open an elevated command prompt and type
Code:
SET DEVMGR_SHOW_NONPRESENT_DEVICES=1
devmgmt.msc
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Then open the Device Manager and see if you have the omap4 driver installed twice (in two locations)
Note: In Device Manager click the View tab and select Show hidden devices
If you don't see the omap driver installed twice, do this
Select the "other devices" and start deleting/uninstalling all of the devices you find here (I think the device you are looking for is "lg u2" but not 100% sure)
Once you have uninstalled all of the unknown drivers you found, run the start.bat again and follow the directions to flash the x & u img's (for your device).
Now go back to device manager and find the new unknown/other device created (should be lg u2) and install the omap4430 like you did the first time.
After you have done all this, rerun the start.bat and hopefully it will work for you.
Another thing, If you do see the omap driver installed twice, then it has to be your timing when you enter the battery. Keep trying different times to enter the battery
example. wait 1 second and enter battery, if that doesn't work wait 2 seconds then enter battery and etc.
Good luck
No luck yet with connecting to fastboot, I will give this a shot and report back. Thank you.
You were absolutely right, the issue was with having multiple drivers. I followed your steps and restored my phone to life. Thank you so much.
jlj012 said:
No luck yet with connecting to fastboot, I will give this a shot and report back. Thank you.
Click to expand...
Click to collapse
Your are welcome, now hit the thanks button, it makes me feel good, Lol.
CM 10.1 P769
kuma82 said:
Your are welcome, now hit the thanks button, it makes me feel good, Lol.
CM 10.1 P769
Click to expand...
Click to collapse
Lol..
Sent from my LG-P769 using Tapatalk 4
Got fastboot working, but now what?
kuma82 said:
You need to flash the ice cream x & u boot for your device (in fastboot) to get the offline flash running again
Click to expand...
Click to collapse
@kuma82,
Before I start, I had NO IDEA how crazy the L9 was! I've rooted/unlocked/custom recoveried/custom ROMed 4 other phones without any major set backs prior to hitting this wall.
Also, this is my daughter's phone and I'm really took a lot of precautions before starting.
Here is what I did prior to attempting to wipe (factory reset) and install CM 10.1 (here):
Device model: P769
[was] rooted
CWM Recovery [was] installed
Stock JB (T-Mobile US) ROM backed up (full nandroid)
I was concerned about the many submodels of the L9 and verified both in the about phone within the ROM settings as well as what's printed/etched below the battery under the back cover. Both checked out to be P769.
I ran `adb reboot recovery` and then proceeded to wipe/factory rest from within CWM recovery. After this, I installed the ROM zip from the external sdcard. It failed the update script's assert of ro.product.id and would not install. OK, bummer, I'll just restore the nandroid backup. Nope. It was unable to restore /system and so now I really got concerned. I then found the weirdest thing of all. After seeing what is asserted in the update script for the ROM zip, I ran getprop for each of the properties it checks for and got back the Prada 3D "p940"!
Well now I felt like I was in a world of pain, so I decided to hack the update script so that "p940" would be accepted. Well now the install went fine without any errors reported. I proceeded to flash the latest gapps for 4.2.2 and it too installed fine. GREAT! Now for the system boot.........
From that point on, I've been stuck in LG Security Error land
I was able to get the special fastboot to connect (after many failed attempts) by selecting option 5 for ICS x & u flashing.
Could someone be please be kind enough to help me get my daughter's phone back to some ROM? I'm alright with even stock right now. At least then she'll have a functioning phone and I could even extract apps to restore from the CWM nandroid I made via Titanium.
peace.
erraggy said:
@kuma82,
Before I start, I had NO IDEA how crazy the L9 was! I've rooted/unlocked/custom recoveried/custom ROMed 4 other phones without any major set backs prior to hitting this wall.
Also, this is my daughter's phone and I'm really took a lot of precautions before starting.
Here is what I did prior to attempting to wipe (factory reset) and install CM 10.1 (here):
Device model: P769
[was] rooted
CWM Recovery [was] installed
Stock JB (T-Mobile US) ROM backed up (full nandroid)
I was concerned about the many submodels of the L9 and verified both in the about phone within the ROM settings as well as what's printed/etched below the battery under the back cover. Both checked out to be P769.
I ran `adb reboot recovery` and then proceeded to wipe/factory rest from within CWM recovery. After this, I installed the ROM zip from the external sdcard. It failed the update script's assert of ro.product.id and would not install. OK, bummer, I'll just restore the nandroid backup. Nope. It was unable to restore /system and so now I really got concerned. I then found the weirdest thing of all. After seeing what is asserted in the update script for the ROM zip, I ran getprop for each of the properties it checks for and got back the Prada 3D "p940"!
Well now I felt like I was in a world of pain, so I decided to hack the update script so that "p940" would be accepted. Well now the install went fine without any errors reported. I proceeded to flash the latest gapps for 4.2.2 and it too installed fine. GREAT! Now for the system boot.........
From that point on, I've been stuck in LG Security Error land
I was able to get the special fastboot to connect (after many failed attempts) by selecting option 5 for ICS x & u flashing.
Could someone be please be kind enough to help me get my daughter's phone back to some ROM? I'm alright with even stock right now. At least then she'll have a functioning phone and I could even extract apps to restore from the CWM nandroid I made via Titanium.
peace.
Click to expand...
Click to collapse
To install custom rom or CM10 you need to unlock bootloader first. You should follow kuma82 in his post above to flash back stock rom.
The security error is because you didn't unlock it (sorry to hear that). Just flash with fastboot ice x & u for p769. Then put your phone in s/w upgrade and run the offline flash.
If you need anymore help, holla! I don't want your daughter mad at you
kuma82 said:
The security error is because you didn't unlock it (sorry to hear that). Just flash with fastboot ice x & u for p769. Then put your phone in s/w upgrade and run the offline flash.
If you need anymore help, holla! I don't want your daughter mad at you
Click to expand...
Click to collapse
I swear I read every link you posted above and still could not figure out what: "flash with ice x & u" is. I downloaded the fastboot zip and ran start.bat and selected option 5 for ICS x & u for p769 and that got me an inverted LG fastboot screen. I was also able to then choose option 1 for fastboot which dropped me into an empty yours directory.
It was midnight and I had at least 8 browser tabs open to various xda posts, but I still couldn't figure out what I needed to do with the start.bat next.
Thanks in advance. My weekend is dedicated to solely fixing her phone
Sent from my HTC Sensation using Tapatalk 4
jlj012 said:
Hi All,
After a failed attempt to root my L9 769, I have an issue where when the phone is turned on, it does not boot, it goes to a screen with the LG logo and the words "security error" beneath it. The phone then powers off. The only thing I have access to on the phone is this screen and the software update mode. I used the offline flash method in my root attempt. I am sure I screwed up in the process. I have scoured the internet in an attempt to resolve this, but I have yet been able to. This seems to be a fairly common problem when a root attempt fails, however I cannot correct this.
Things I have tried:
Fastboot: I try to run fastboot, but it stops at waiting for device.
Offline flash: I tried the offline flash method, but the tool freezes at 15% saying the device cannot be found.
Online flash: The tool recognizes the phone but sees it as being up to date. I try to use the recovery option but it locks up at analyzing the phone.
I am at a loss. Any help would be greatly appreciated.
Thanks,
J
Click to expand...
Click to collapse
I've been wanting to try this: go to your computer and check your device manager and disable the LG drivers then try the offline flash again. Kuma way works but it's very long, found this while I was reading but never tried for our phones. Same problem though as updating stops at 15 %
Sent from my LG-P769(v20f) using the xda-developers app. Hit the thanks bottom, makes me feel good!
erraggy said:
I swear I read every link you posted above and still could not figure out what: "flash with ice x & u" is. I downloaded the fastboot zip and ran start.bat and selected option 5 for ICS x & u for p769 and that got me an inverted LG fastboot screen. I was also able to then choose option 1 for fastboot which dropped me into an empty yours directory.
It was midnight and I had at least 8 browser tabs open to various xda posts, but I still couldn't figure out what I needed to do with the start.bat next.
Thanks in advance. My weekend is dedicated to solely fixing her phone
Sent from my HTC Sensation using Tapa talk 4
Click to expand...
Click to collapse
More help with fastboot
http://forum.xda-developers.com/showpost.php?p=44578108&postcount=34
http://forum.xda-developers.com/showpost.php?p=44653501&postcount=55
Another thing, more than likely, after you flash with the r&d tool you will need to do a hard reset because you flashed cyanogen. Also, you will still need to root to fix the touch screen.
CM 10.1 P769
Sent from my LG-P769 using xda app-developers app
kuma82 said:
More help with fastboot
http://forum.xda-developers.com/showpost.php?p=44578108&postcount=34
http://forum.xda-developers.com/showpost.php?p=44653501&postcount=55
CM 10.1 P769
Sent from my LG-P769 using xda app-developers app
Click to expand...
Click to collapse
Yeah, I was able to repeatedly get the inverted LG fastboot screen and see everything you saw in device manager as well as successfully get `fastboot devices` to show (echo) the device. I even tried `fastboot flash recovery p4_769.img` with the file linked in post #3 and it flashed without error.
Here's my problem: What do I need to do now that I have a working way to run fastboot commands? Is there a recovery image I need to flash (stock)? Is there a boot image I need to flash? Or, is there some other fastboot command I need to run?
I'm assuming the advice you're giving me is to ultimately get a stock ROM back on her phone. Is that correct?
I'd really like to unlock the bootloader so that I can do what I know with CWM: backup, wipe, restore, flash, etc... If that is something I can do from where I'm at now, I'd prefer to put the effort in to that. If this darned 'Security Error' splash message must be resolved by getting back to a stock ROM first, then I'm game.
Final request for clarification: Am I still needing to "flash the ice cream x & u boot for your device (in fastboot) to get the offline flash running again"? If so, could you please provide instructions for that step? So far all of the steps linked here have been to get Windows drivers sorted out and fastboot working. I've got that now.
Thanks again!
erraggy said:
Yeah, I was able to repeatedly get the inverted LG fastboot screen and see everything you saw in device manager as well as successfully get `fastboot devices` to show (echo) the device. I even tried `fastboot flash recovery p4_769.img` with the file linked in post #3 and it flashed without error.
Here's my problem: What do I need to do now that I have a working way to run fastboot commands? Is there a recovery image I need to flash (stock)? Is there a boot image I need to flash? Or, is there some other fastboot command I need to run?
I'm assuming the advice you're giving me is to ultimately get a stock ROM back on her phone. Is that correct?
I'd really like to unlock the bootloader so that I can do what I know with CWM: backup, wipe, restore, flash, etc... If that is something I can do from where I'm at now, I'd prefer to put the effort in to that. If this darned 'Security Error' splash message must be resolved by getting back to a stock ROM first, then I'm game.
Final request for clarification: Am I still needing to "flash the ice cream x & u boot for your device (in fastboot) to get the offline flash running again"? If so, could you please provide instructions for that step? So far all of the steps linked here have been to get Windows drivers sorted out and fastboot working. I've got that now.
Thanks again!
Click to expand...
Click to collapse
Okay, did you get all your info about unlocking the bootloader from carloswii5 video? So you had flashed 20b kdz right?
You gave me a hand full Lola, but I'm help you out. It get is going to take me some time to give you a guide, but I'll give you everything you need today and yes, you need to get back to stock.
I'll send you another link on how to use fast boot manually. Plus it has the images for ice cream. But hold up
Sent from my LG-P769 using xda app-developers app
kuma82 said:
Okay, did you get all your info about unlocking the bootloader from carloswii5 video? So you had flashed 20b kdz right?
You gave me a hand full Lola, but I'm help you out. It get is going to take me some time to give you a guide, but I'll give you everything you need today and yes, you need to get back to stock.
I'll send you another link on how to use fast boot manually. Plus it has the images for ice cream. But hold up
Sent from my LG-P769 using xda app-developers app
Click to expand...
Click to collapse
THANKS!
Her phone had the stock TMOUS jelly bean ROM that we received OTA. I had only rooted her phone previous to my CM10.1 fiasco attempt.
So I've never flashed anything (successfully at least) on her phone. All of my previous android experience has been on 3 nexuses (One, S, 4) and my current HTC Sensation. That means I've only unlocked one bootloader that didn't support the fastboot oem method
I'm an experienced dev with the entire weekend to "play" with my daughter's p769
I also promise to provide lengthy posts in the Optimus L9 forums to help any future people from soft bricking any more devices.
Sent from my HTC Sensation using Tapatalk 4
This will tell you how to use fastboot manually http://forum.xda-developers.com/showpost.php?p=43642515&postcount=21
The system image is to big to flash with fastboot, sucks.
1. Use the above to get back on stock (you need 10g kdz).
To enter s/w upgrade remove battery. Hold volume up and enter USB cable, then put the battery back in.
Sent from my LG-P769 using xda app-developers app
kuma82 said:
This will tell you how to use fastboot manually http://forum.xda-developers.com/showpost.php?p=43642515&postcount=21
The system image is to big to flash with fastboot, sucks.
1. Use the above to get back on stock (you need 10g kdz).
To enter s/w upgrade remove battery. Hold volume up and enter USB cable, then put the battery back in.
Sent from my LG-P769 using xda app-developers app
Click to expand...
Click to collapse
UH OH... The "volume up" method isn't working on this device. I posted more details about it here. I'm beginning to think I may need to return the phone. I never thought flashing a ROM zip in CWM recovery could brick the phone. When I restoring the CWM backup also failed (when I at least was in CWM recovery which now is inaccessible), I freaked.
P.S. - I'm all out of thanks for the day. I think you got the lion's share though
I tried following the upgrade to ViperX+2.0.1 and after flashing recovery and boot.img I seem to be stuck in a loop. Now I'm stuck on HTC splash screen and can't do anything. I go to recovery TWRP and none of my backups are there!
I cannot reboot. Computer won't recognise phone on USB.
Please Help!!!
vectorer said:
I tried following the upgrade to ViperX+2.0.1 and after flashing recovery and boot.img I seem to be stuck in a loop. Now I'm stuck on HTC splash screen and can't do anything. I go to recovery TWRP and none of my backups are there!
I cannot reboot. Computer won't recognise phone on USB.
Please Help!!!
Click to expand...
Click to collapse
How do you locate your backup in TWRP? Is it from the restore menu or from file manager menu? I never see my backups in file manager but if you choose restore menu, they are normally there.
superbay said:
How do you locate your backup in TWRP? Is it from the restore menu or from file manager menu? I never see my backups in file manager but if you choose restore menu, they are normally there.
Click to expand...
Click to collapse
Restore menu, but there is nothing there! I cannot find anything in the file manager or install zip and I know there are zip files!
Am I bricked? Any hope?
vectorer said:
Restore menu, but there is nothing there! I cannot find anything in the file manager or install zip and I know there are zip files!
Am I bricked? Any hope?
Click to expand...
Click to collapse
afaik as long as you can go to bootloader, your device is not bricked. You can still push the zip file or ruu. What indicates that your computer doesnt recognize the device?
superbay said:
afaik as long as you can go to bootloader, your device is not bricked. You can still push the zip file or ruu. What indicates that your computer doesnt recognize the device?
Click to expand...
Click to collapse
when I connect it the MTP driver won't install, I had thought to at least salvage some pictures etc. but the phone doesn't show in windows.
I was running ViperX+ 2.0.0, I've now got the 2.0.1 zip file so I'm going to try to sideload that, following directions from here http://forum.xda-developers.com/showthread.php?t=2318497, since I'm really new at this and need spoon feeding. I admit that if it works I am worried about the boot.img file but such is life. fingers crossed
okay, I just tried to flash the boot.img file using VenomKernelFlasher.exe and it won't do it because the device isn't connected!!
this driver is killing me
vectorer said:
when I connect it the MTP driver won't install, I had thought to at least salvage some pictures etc. but the phone doesn't show in windows.
I was running ViperX+ 2.0.0, I've now got the 2.0.1 zip file so I'm going to try to sideload that, following directions from here http://forum.xda-developers.com/showthread.php?t=2318497, since I'm really new at this and need spoon feeding. I admit that if it works I am worried about the boot.img file but such is life. fingers crossed
okay, I just tried to flash the boot.img file using VenomKernelFlasher.exe and it won't do it because the device isn't connected!!
this driver is killing me
Click to expand...
Click to collapse
Never mind about the MTP driver, mate. It is not always an indication that the computer doesn't recognize the phone. I have installed the same driver in several computers with similar OS and about half of them shows that MTP driver failed to install. HTC sync even always says no device connected. However, the computer still recognize the phone to be used for rooting or doing anything using hassoon's tool.
Before continuing, do you own HTC One or One X+? The link you refered shows that it's HTC One thread.
For HTC One X+ you can read in the 4th post in this thread http://forum.xda-developers.com/showthread.php?t=2066390
superbay said:
Never mind about the MTP driver, mate. It is not always an indication that the computer doesn't recognize the phone. I have installed the same driver in several computers with similar OS and about half of them shows that MTP driver failed to install. HTC sync even always says no device connected. However, the computer still recognize the phone to be used for rooting or doing anything using hassoon's tool.
Before continuing, do you own HTC One or One X+? The link you refered shows that it's HTC One thread.
For HTC One X+ you can read in the 4th post in this thread http://forum.xda-developers.com/showthread.php?t=2066390
Click to expand...
Click to collapse
Thanks. It's HTC One X+, I got there from a Google search for sideload as I know zero about it. As it turns out it didn't work, got to 22% then failed every time. I'll check out that link now.
Thanks again.
Ran Hasssoon and got
adb server is out of date. killing...
* daemon started successfully *
* failed to write data 'protocol fault (no status)' *
C:\Hassoon\One_X+_All-In-One_Kit_v\data>
Next idea please
Where can I find an RUU for this phone........ HTC One X+ EvitaRE
vectorer said:
Ran Hasssoon and got
adb server is out of date. killing...
* daemon started successfully *
* failed to write data 'protocol fault (no status)' *
C:\Hassoon\One_X+_All-In-One_Kit_v\data>
Next idea please
Where can I find an RUU for this phone........ HTC One X+ EvitaRE
Click to expand...
Click to collapse
Did you get that after choosing sideload option? try putting the zip file in the data folder in hassoon toolkit.
For ruu you can try look at q18 in the firsy post of this thread forum.xda-developers.com/showthread.php?t=2179337
My last post in that thread might help too. However, check your device radio version first to see which one suits yours.
or maybe this thread might help as well since it's for Telus version forum.xda-developers.com/showthread.php?t=2051032
superbay said:
Did you get that after choosing sideload option? try putting the zip file in the data folder in hassoon toolkit.
For ruu you can try look at q18 in the firsy post of this thread forum.xda-developers.com/showthread.php?t=2179337
My last post in that thread might help too. However, check your device radio version first to see which one suits yours.
or maybe this thread might help as well since it's for Telus version forum.xda-developers.com/showthread.php?t=2051032
Click to expand...
Click to collapse
been absent for a few days.
yes it was sideload, i'll try the data thing now
also i've had viper for a while and like it, but if you think another rom would work better in this case please let me know
i appreciate all your help. i'm using my old sensation 4G right now..... i like it but have gotten used to the OneX+ so i really hope to be up and running again
superbay said:
Did you get that after choosing sideload option? try putting the zip file in the data folder in hassoon toolkit.
Click to expand...
Click to collapse
how would i do this operation??
now no matter what i try i get
error: closed
vectorer said:
been absent for a few days.
yes it was sideload, i'll try the data thing now
also i've had viper for a while and like it, but if you think another rom would work better in this case please let me know
i appreciate all your help. i'm using my old sensation 4G right now..... i like it but have gotten used to the OneX+ so i really hope to be up and running again
Click to expand...
Click to collapse
Helping anyone in need whenever possible is how people give back to this community
I occassionally had the same case with you and surely would want yo see yours running up again like mine. The difference is i had several rom zips in my hox+ at that time but everytime i flashed any of them and no matter how many times i wipe and flash boot.img, it ended up in bootloop.
vectorer said:
how would i do this operation??
Click to expand...
Click to collapse
In hassoon toolkit there is a folder named 'data' just put your zip file there and choose the file from there when sideloading. Sometimes problem occurs from such minor thing where any file you need (rom, recovery, kernel) needs to be put in the adb folder.
vectorer said:
now no matter what i try i get
error: closed
Click to expand...
Click to collapse
If i were you,i would start fresh from another computer just to make sure that it is not your computer causing that and to see if it makes any difference. However I still believe that the computer recognizes the device,otherwise the command prompt will say 'waiting for device' if adb doesn't recognize the device. If such problem still persists, then i think it is the time for you to ruu.
Well i expect any help from others since the beginning. This thread has been viewed more than 500 times but there are you and me only mate. Just dont stop trying anyway. That's where your learning is from and how you prevail
superbay said:
Helping anyone in need whenever possible is how people give back to this community
I occassionally had the same case with you and surely would want yo see yours running up again like mine. The difference is i had several rom zips in my hox+ at that time but everytime i flashed any of them and no matter how many times i wipe and flash boot.img, it ended up in bootloop.
In hassoon toolkit there is a folder named 'data' just put your zip file there and choose the file from there when sideloading. Sometimes problem occurs from such minor thing where any file you need (rom, recovery, kernel) needs to be put in the adb folder.
If i were you,i would start fresh from another computer just to make sure that it is not your computer causing that and to see if it makes any difference. However I still believe that the computer recognizes the device,otherwise the command prompt will say 'waiting for device' if adb doesn't recognize the device. If such problem still persists, then i think it is the time for you to ruu.
Well i expect any help from others since the beginning. This thread has been viewed more than 500 times but there are you and me only mate. Just dont stop trying anyway. That's where your learning is from and how you prevail
Click to expand...
Click to collapse
thanks I'll keep trying this weekend
vectorer said:
thanks I'll keep trying this weekend
Click to expand...
Click to collapse
Just keep posting here to see how far your effort is with it. Good luck
superbay said:
Did you get that after choosing sideload option? try putting the zip file in the data folder in hassoon toolkit.
For ruu you can try look at q18 in the firsy post of this thread forum.xda-developers.com/showthread.php?t=2179337
My last post in that thread might help too. However, check your device radio version first to see which one suits yours.
or maybe this thread might help as well since it's for Telus version forum.xda-developers.com/showthread.php?t=2051032
Click to expand...
Click to collapse
mine may not be a telus version
my radio version is "RADIO-SSD:2.14.55.11"
the closest i can find to this version is Cingular!
http://www.androidruu.com/getdownlo....55.01_18.21.95.55L_release_310178_signed.exe
version is 2.14.55.01
the Telus one version is 1.09.55.17
I'm guessing the Cingular would be best??
thanks
vectorer said:
mine may not be a telus version
my radio version is "RADIO-SSD:2.14.55.11"
the closest i can find to this version is Cingular!
http://www.androidruu.com/getdownlo....55.01_18.21.95.55L_release_310178_signed.exe
version is 2.14.55.01
the Telus one version is 1.09.55.17
I'm guessing the Cingular would be best??
thanks
Click to expand...
Click to collapse
Well it should say the exact same radio version if you dont want to meet any problem. Can you search for the one as same as yours?
Or if you need further detail about the version, you can type 'fastboot getvar version-main' in the adb
superbay said:
Well it should say the exact same radio version if you dont want to meet any problem. Can you search for the one as same as yours?
Or if you need further detail about the version, you can type 'fastboot getvar version-main' in the adb
Click to expand...
Click to collapse
Well nothing is working.
I guess my device is a paperweight even if I can get into recovery.
Can't flash anything, not even the RUU, can't sideload........nothing.
Tried Hassoon's instructions for the RUU but it won't reconise that a device is attached to go into Bootlaoder, sideloading ALWAYS fails at 22%. Others seem to overcome this but I cannot. It's frustrating reading how many problems are solved when nothing works for me.
Well guys, I think I messed this one up, Sprint HTC One Max that I unlocked the bootloader on and then proceeded to S-Off with Rumrunner and failed due to not already having su permissions.(note his instructions say "OR Bootloader unlocked" so I figured I was fine having done that) The device rebooted fine initially after exiting the tool and then after attempting to manually flash TWRP for this device so I could get root access and try again, the phone rebooted to recovery and now fastboot AC is as far as I can get. Downloading the Sprint Decrypted RUU from OMJ now because I'm retarded and cant figure out how to get around using commands in Free Arc to unzip the signed RUU...any help is appreciated. :silly: Tried manually updating the drivers for the "unknown device" on usb hub port 8 in my device manager with offical and generic HTC drivers and tried reinstalling HTC Sync to no avail. am I bricked?
Everyone MUST use the files for the HTC One "MAX" corresponding to their model (Sprint, Verizon or International). *OMJ has posted in our thread.
Use this:
http://forum.xda-developers.com/showthread.php?t=2525805
*Did you flash the twrp for the One MAX from this forum?
Jiggity Janx said:
Everyone MUST use the files for the HTC One "MAX" corresponding to their model (Sprint, Verizon or International). OMJ has not posted in any forum for the One MAX (as far as I know).
Use this:
http://forum.xda-developers.com/showthread.php?t=2525805
*Did you flash the twrp for the One MAX from this forum?
Click to expand...
Click to collapse
I have it, both the decrypted one OMJ posted on page 2 and the signed one. But free arc wont let me open it. What the hell am I doing wrong? How do I unzip the signed one and use it without the error. I know it has to be something simple I'm missing. Yes I used the twrpsprint.img from Squabbi's Toolkit, thats what failed the phone into recovery. (Red Traingle). Now the phone can get into the bootloader and it will boot into android but no usb debugging when I enable it.
Skyymiles said:
I have it, both the decrypted one OMJ posted on page 2 and the signed one. But free arc wont let me open it. What the hell am I doing wrong? How do I unzip the signed one and use it without the error. I know it has to be something simple I'm missing. Yes I used the twrpsprint.img from Squabbi's Toolkit, thats what failed the phone into recovery. (Red Traingle). Now the phone can get into the bootloader and it will boot into android but no usb debugging when I enable it.
Click to expand...
Click to collapse
Found OMJ post now. He posted the decrypted in the same thread as the encrypted. Got it.
Can you boot to bootloader with vol down and power? Does it show you as s-off?
Flashify in the play store will flash the twrp .img from flyhalf twrp thread in original dev or you can use his instructions and use fastboot.
---------- Post added at 09:58 PM ---------- Previous post was at 09:54 PM ----------
I don't think you need to ruu if you can boot to android and bootloader. It can be fixed using other methods.
Jiggity Janx said:
Found OMJ post now. He posted the decrypted in the same thread as the encrypted. Got it.
Can you boot to bootloader with vol down and power? Does it show you as s-off?
Flashify in the play store will flash the twrp .img from flyhalf twrp thread in original dev or you can use his instructions and use fastboot.
---------- Post added at 09:58 PM ---------- Previous post was at 09:54 PM ----------
I don't think you need to ruu if you can boot to android and bootloader. It can be fixed using other methods.
Click to expand...
Click to collapse
I can get to the bootloader no problems just that the phone wont talk to the computer. I can hear it connect/disconnect from usb but always device unrecognized so I cant send the phone any commands. I can boot into android no issues though. So youre suggesting flash twrp img using an app like flashify or goo manager like a openrecoveryscrript from android then install a custom ROM after to fix the fastboot usb recognition? I am S-On, unlocked currently.
I am hoping to help but was/am distracted. I think you can fix what is going on with flashing the twrp from flyhalf thread. I am not on sprint so haven't gone through it on that side.
Also as noted in the ruu thread you cannot flash the older ruu posted if you are on a newer update. Check the version.
do you have the htc drivers installed on your computer?
Maybe try to follow this to get back on track. It was written specifically with Sprint in mind.
http://forum.xda-developers.com/showthread.php?t=2550559
Jiggity Janx said:
Maybe try to follow this to get back on track. It was written specifically with Sprint in mind.
http://forum.xda-developers.com/showthread.php?t=2550559
Click to expand...
Click to collapse
I started here actually...lol Yes I just uninstalled them, disabled Antivirus, rebooted and freshly installed HTC Sync Manager with Drivers to make sure. If I can get an this app to flash TWRP and SU I may be in business...
UNINSTALL Sync manager, and just keep the drivers..
wase4711 said:
UNINSTALL Sync manager, and just keep the drivers..
Click to expand...
Click to collapse
Done. Trying to figure out how to get twrp without fastboot... or how to get the laptop to recognize the device now.
Skyymiles said:
Done. Trying to figure out how to get twrp without fastboot... or how to get the laptop to recognize the device now.
Click to expand...
Click to collapse
are you using adb commands to see if you are connected?
did you reboot your laptop and phone after installing the drivers?
antivirus and firewall off?
wase4711 said:
are you using adb commands to see if you are connected?
did you reboot your laptop and phone after installing the drivers?
Click to expand...
Click to collapse
yup.. going through troubleshooting this connection right now... nothing returned on adb devices, list of devices is blank. somethings up. no serial number, nothing... tried both in the OS and in fastboot.
troubleshooting connectivity issues:
-try a reboot of the PC
-try different usb cables and ports
-dont use a usb hub
-dont use usb 3.0
-make sure nothing capable of comunicating with the phone is enabled and running. htc sync,pdanet,easy tether,and even itunes have all been known to cause issues.
-windows 8 has been known to have issues. try a windows 7 or older machine
failing the above,
-i use these drivers for fastboot and adb(donwload and run as admin): http://downloads.unrevoked.com/HTCDriver3.0.0.007.exe (mirror)
failing that,try manually updating the drivers in the following manner:
-put the phone in fastboot mode(select fastboot from the hboot menu)
-open device manager on the PC
-plug in phone,watch for it to pop up in device manager.
-update drivers with device manager,pointing the wizard to the extracted
driver download folder from above
note that you can check the connectivity of the phone,and make sure drivers are working by in the following manner:
-open cmd window. change to directory containing adb/fastboot utilities
-adb with the phone in the booted OS,usb debug enabled,enter:
adb devices in a cmd window
-fastboot with phone in fastboot,enter:
fastboot devices in cmd window
in either case,a properly connected phone with working drivers installed should report back the phones serial number.
at any rate I know adb works because it can see my old m7wls just fine.
Skyymiles said:
Done. Trying to figure out how to get twrp without fastboot... or how to get the laptop to recognize the device now.
Click to expand...
Click to collapse
Did the app "Flashify" from the play store not flash the twrp .img from fluhalf thread?
---------- Post added at 11:29 PM ---------- Previous post was at 11:27 PM ----------
Update your version of adb. Older versions may not recognize devices on fastboot even though they do in adb.
Jiggity Janx said:
Did the app "Flashify" from the play store not flash the twrp .img from fluhalf thread?
---------- Post added at 11:29 PM ---------- Previous post was at 11:27 PM ----------
Update your version of adb. Older versions may not recognize devices on fastboot even though they do in adb.
Click to expand...
Click to collapse
Never achieved SU to begin with so I cant flash it. the app FCs without Su permission. I'll try updating adb.
Question: If I never managed to achieve anything beyond Unlocking the bootloader, wouldn't a Factory Reset from the boot loader menu fix any partition discrepancies anyway and allow the PC to recognize the device again? I guess thats what I cant understand. What would go so wrong if I never flashed anything, not intended for Sprint HTC One Max's that would suddenly cause the PC not to recognize the Fastboot USB?
UPDATE1/25:
Updated everything in adb for 4.3 and 4.4 and 4.2.2 and the toolkits. Still nothing. I think I have determined the root cause may be a bad copy of TWRP that results in a QHSUSB_DLOAD issue like from the Evo 3D days. Unfortunately however, since the One Max is a relatively new device, there has been no "ultimate recovery tools" established to fix this type of error. So now, lol... wait for it. Now I have an "Unlocked", unrooted, S-ON, Stock HTC One Max(sprint) and stock recovery whos partitions I can only imagine are ok yet the computer refuses to recognize on fastboot.
That said, does anybody know, since I can apparently boot Android, and the phone itself works just fine, if there are any market apps which would support flashing from inside the phone, like Flash Image GUI to try and root this thing internally or am I just hosed/hard bricked stuck on stock?
Skyymiles said:
Never achieved SU to begin with so I cant flash it. the app FCs without Su permission. I'll try updating adb.
Question: If I never managed to achieve anything beyond Unlocking the bootloader, wouldn't a Factory Reset from the boot loader menu fix any partition discrepancies anyway and allow the PC to recognize the device again? I guess thats what I cant understand. What would go so wrong if I never flashed anything, not intended for Sprint HTC One Max's that would suddenly cause the PC not to recognize the Fastboot USB?
UPDATE1/25:
Updated everything in adb for 4.3 and 4.4 and 4.2.2 and the toolkits. Still nothing. I think I have determined the root cause may be a bad copy of TWRP that results in a QHSUSB_DLOAD issue like from the Evo 3D days. Unfortunately however, since the One Max is a relatively new device, there has been no "ultimate recovery tools" established to fix this type of error. So now, lol... wait for it. Now I have an "Unlocked", unrooted, S-ON, Stock HTC One Max(sprint) and stock recovery whos partitions I can only imagine are ok yet the computer refuses to recognize on fastboot.
That said, does anybody know, since I can apparently boot Android, and the phone itself works just fine, if there are any market apps which would support flashing from inside the phone, like Flash Image GUI to try and root this thing internally or am I just hosed/hard bricked stuck on stock?
Click to expand...
Click to collapse
Ok, Update 2! Managed to get into the Stock recovery console and wipe the cache partitions, but it seems even that did not fix the issue.(The phone had never been rooted or had a custom recovery flashed and got stuck on S-On, Unlocked, no recognition from Fastboot USB on the PC) So since I can apparently get here, can I flash a CWM or TWRP image from here(stock recovery->apply update from SD card or internal storage)? or is that only for flashing a whole ROM?
Thanks!!
Skyymiles said:
Ok, Update 2! Managed to get into the Stock recovery console and wipe the cache partitions, but it seems even that did not fix the issue.(The phone had never been rooted or had a custom recovery flashed and got stuck on S-On, Unlocked, no recognition from Fastboot USB on the PC) So since I can apparently get here, can I flash a CWM or TWRP image from here(stock recovery->apply update from SD card or internal storage)? or is that only for flashing a whole ROM?
Thanks!!
Click to expand...
Click to collapse
Ok, UPDATE 3, back at work trying a different computer... Turns out it wasnt as bad as I thought at all. Its a driver issue on my personal computer.(work computer recognizes the Max on Fastboot Usb, still didnt list it on devices yet but I'm not worried about that right now.) Oh well... so since I know this is an isolated incident, any recommendations for driver cleaner, like Drive Cleaner CC? Or what would be the best method short of wiping my laptop to a fresh copy of Win 7, that I could use to make sure I am removing all failing instances of HTC Drivers from my machine. Like I said it picks up and installs my HTC One (m7) fine, but the One Max, nadda. So I need to correct the driver issue on my end ultimately to reduce further issues. :silly: Sorry to keep posting to myself but hopefully someone else will benefit from reading what happened to me.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
[/URL][/IMG]
Profit! Thanks to those who helped!!! Your comments were appreciated, mods can lock this thread as solved.
Sent from my HTC0P3P7 using xda app-developers app
Congrats! you seemed to have a long time fighting with the device.
Anyone have a pair of these glasses and working on root access? Anyone interested? There are a group of us that would be really interested in finding a solution.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
dvegaman said:
Anyone have a pair of these glasses and working on root access? Anyone interested? There are a group of us that would be really interested in finding a solution.
Click to expand...
Click to collapse
I have a pair of the FPV Drone Edition. Have side loaded a few apps. Haven't rooted since Galaxy S3 ( back on iPhone now) am interested to get this going
Hi !
It seems the rooting of intel devices follow the scheme:
-get bootimg
-patch it
-allow oem bootloader (voiding warranty and endangering future updates)
-flash the patched bootimg and pray
Is this correct or did i oversimplify or generalize too much or am i plain wrong, anyone ?
Greetings,
Ender
P.S. Greetings dvegaman
Bump.
Well, BUMP, goddamn
Just came across 2 pairs of these (BT-300s).
If the lack of interest in rooting is due to lack of hardware, reach out to me privately here on XDA; would happily donate one to kickstart some development efforts.
-jd
jdiegmueller said:
Just came across 2 pairs of these (BT-300s).
If the lack of interest in rooting is due to lack of hardware, reach out to me privately here on XDA; would happily donate one to kickstart some development efforts.
-jd
Click to expand...
Click to collapse
Bumping this one up. Have a new pair and looking to root to wake them up some.
Sent from my Moto Z (2) using Tapatalk
This may seem easy to others but I figured out how to do a factory data reset using ADB... something that would've helped when my BT-300 went into a boot loop last weekend...
***DO AT YOUR OWN RISK! NOT RESPONSIBLE FOR BRICKING, ETC..... (but it worked fine for me).
1. Install "minimal_adb_fastboot_v1.4.2_setup.exe" (google it and grab at your own risk) on your Windows PC.
2. Go to the BT-300 and:
a. Under Security allow unknown sources
b. Under Developer Options allow USB debugging and unlock bootloader.
3. Connect same powered up BT-300 to PC via USB cable.
4. Start up that minimal ADB program. It will open in command prompt.
5. Check connection by typing "adb devices"
Should see "EMBT3C device" on PC
6. Now type, "adb reboot recovery" and wait for android with triangle/exclamation point to appear after device reboots. You will notice the physical buttons flash purple too.
7. Press and hold power button. Also press Vol Up, then release Vol Up and finally release Power button.
You should now see the recovery menu including "wipe data/factory reset", cache clear, and so on...
NOW... if I could get recovery.zip image to restore if I "kill" it to reload with ADB... THEN I'd try root. There must be a way. I just want GApps 5.1.1 on the thing for starters.
Still struggling with rooting... No dice so far. I've never rooted any Android... Once rooted can we then save the original factory ROM someplace safe, or do I need that first from another source? Newbie questions . I know just enough to be dangerous! LOL.
I got the factory image
Played around with the "SoftwareUpdate" apk and found the strings it uses to download the 1.4
Ugh just signed up but because I don't have enough posts I had to put a bunch of spaces in the links for them to
show up. Just remove the spaces and they should work? Either his or copy the SoftwareUpdate.apk and pull the strings from that.
ht tps:// download.ebz.epson.net /dsc /du /04 /SecureUpdateInfo ?PRN=BT-300&CTI=80&OSC=ARD&SCD=H756EMBT3C&SID=012345
You download a file called "SecureUpdateInfo" open it in a text editor and it will give you a link to the direct download for the zip. Its about 300megs. I have been playing with the boot options, but keep crashing it on boot and having to restore. I found 4 test pins that may be a serial port, but its 1.8 volt so I need to build something
PS - It might com back without a link but "BUSY" on it. I have been testing it a bunch so thats what happened right now. The fille will look like below
Code:
; secure update information
[BT-300;]
Version=R1.4.0
Size=371659424
Location= ht tps:// download.ebz.epson.net/ dsc/check/ 01/ GetFile. php ?PATH=xxxxxxx/OTA-R1.4.0.zip&KEY=lt1fs0DK
DownloadNumber=11474485
LALocation1=h ttp:// download.ebz.epso n.net/ dsc /hmd_license /EULA.zip
Erodros said:
Played around with the "SoftwareUpdate" apk and found the strings it uses to download the 1.4
Ugh just signed up but because I don't have enough posts I had to put a bunch of spaces in the links for them to
show up. Just remove the spaces and they should work? Either his or copy the SoftwareUpdate.apk and pull the strings from that.
ht tps:// download.ebz.epson.net /dsc /du /04 /SecureUpdateInfo ?PRN=BT-300&CTI=80&OSC=ARD&SCD=H756EMBT3C&SID=012345
You download a file called "SecureUpdateInfo" open it in a text editor and it will give you a link to the direct download for the zip. Its about 300megs. I have been playing with the boot options, but keep crashing it on boot and having to restore. I found 4 test pins that may be a serial port, but its 1.8 volt so I need to build something
PS - It might com back without a link but "BUSY" on it. I have been testing it a bunch so thats what happened right now. The fille will look like below
Code:
; secure update information
[BT-300;]
Version=R1.4.0
Size=371659424
Location= ht tps:// download.ebz.epson.net/ dsc/check/ 01/ GetFile. php ?PATH=xxxxxxx/OTA-R1.4.0.zip&KEY=lt1fs0DK
DownloadNumber=11474485
LALocation1=h ttp:// download.ebz.epso n.net/ dsc /hmd_license /EULA.zip
Click to expand...
Click to collapse
I am both impressed with your progress and baffled why I after I download SecureUpdateInfo I can't get to the zip file. Grrrrrrr.
chuck1026 said:
I am both impressed with your progress and baffled why I after I download SecureUpdateInfo I can't get to the zip file. Grrrrrrr.
Click to expand...
Click to collapse
Is the link in the in the secureupdate? I don't know if the strings encode the serial number in some why or if epson is reading this thread
I can pm you a link for the file if you can't get it
Erodros said:
Is the link in the in the secureupdate? I don't know if the strings encode the serial number in some why or if epson is reading this thread
I can pm you a link for the file if you can't get it
Click to expand...
Click to collapse
Yes, pm me the link. Thanks
Sent from my Moto Z (2) using Tapatalk
chuck1026 said:
Yes, pm me the link. Thanks
Sent from my Moto Z (2) using Tapatalk
Click to expand...
Click to collapse
Ok sending now.
I also managed to root my epson! I discovered the twrp.img here:
https://forum.xda-developers.com/android/development/root-tutorial-intel-atom-cherry-trail-t3468330
If you get into bootloader mode and fastboot flash it into the recovery partition, you can adb root it and then install supersu from there. I just trashed my device though so be sure to do a full image backup first haha.
Erodros said:
Ok sending now.
I also managed to root my epson! I discovered the twrp.img here:
https://forum.xda-developers.com/android/development/root-tutorial-intel-atom-cherry-trail-t3468330
If you get into bootloader mode and fastboot flash it into the recovery partition, you can adb root it and then install supersu from there. I just trashed my device though so be sure to do a full image backup first haha.
Click to expand...
Click to collapse
You trashed it? What did ya load after root to crash it?
chuck1026 said:
You trashed it? What did ya load after root to crash it?
Click to expand...
Click to collapse
Tried to load up opengapps, then every time I rebooted it would be "optimizing apps" I tried to side-load the OTA again and poof, it killed the system partition.
The ota apparently doesn't have the full image. Right now I am trying to hack together something from another cherry rom and side load it, but I need a DD of someones system Glad twrp still works or I wouldn't have shell root access to fix.
Erodros said:
Tried to load up opengapps, then every time I rebooted it would be "optimizing apps" I tried to side-load the OTA again and poof, it killed the system partition.
The ota apparently doesn't have the full image. Right now I am trying to hack together something from another cherry rom and side load it, but I need a DD of someones system Glad twrp still works or I wouldn't have shell root access to fix.
Click to expand...
Click to collapse
You tell me how to share a pure factory image of mine (I'll gladly do an FDR for the cause)... and I'll share with ya!
chuck1026 said:
You tell me how to share a pure factory image of mine (I'll gladly do an FDR for the cause)... and I'll share with ya!
Click to expand...
Click to collapse
Ok I am retarded. I didn't configure twp correctly so all the folders it had were wrong. So when I went to use the install tool it screwed up majorly.
Just glad I didn't overwrite the bootloader
PS - Ok, I figured out how to restore the original recovery loader and it recovered fine. It must be something in this hacked version of twip that isn't applying the ota correctly. Going to try to build a version of twip just for this
Erodros said:
Ok I am retarded. I didn't configure twp correctly so all the folders it had were wrong. So when I went to use the install tool it screwed up majorly.
Just glad I didn't overwrite the bootloader
Click to expand...
Click to collapse
You are not. I am the noob trying to figure out the whole root process and I don't even know how to backup the existing bootloader and ROM so I can restore it with ADB if I screw it all up in root..... I feel clueless and know just enough to be dangerous... yet for some reason, I'm not afraid, just need to learn.
chuck1026 said:
I am both impressed with your progress and baffled why I after I download SecureUpdateInfo I can't get to the zip file. Grrrrrrr.
Click to expand...
Click to collapse
Whew! I did it. First I took the instructions from here as a start:
https://forum.xda-developers.com/android/development/root-tutorial-intel-atom-cherry-trail-t3468330
In fact, if you can "almost" follow the instructions verbatim. The problem is that the data drive is encrypted and the default android password didn't work so I had to modify the boot.img to not encrypt the data partition then do a wipe. supersu installed fine then.
As for gapps, that was tricky. You have to manually install google webview apk as the built in one is garbage.
Still working on the vr settings. Camera has issues with scaling as I think good believes it to be a widescreen when its a 4.3.
Once I get it down, I will make a boot.img and recovery.img that should just work.