Related
I found this online (and I'm sure many know about this already): See attached image for links.
I was wondering if anyone knew if this would be possible with the Eris? There is a compatibility chart with the Eris listed, but it shows "In Progress." I'm not entirely sure how similar the Eris and the Hero are when it comes to the hardware, but if you click on HTC Hero on the attached compatibility chart, you will see this...
"HTC Heros come with 2.6.2x Kernel kernels thus use the USB driver "msm_hsusb" (confirm in /proc/config.gz) and is not currently supported."
Currently, I am running KaosFroyo v32 - Kernel version 2.6.29-bfs302. Would that mean the Eris using 2.6.2x kernels will not be supported by PSfreedom? If any devs (or others with knowledge) can give some input as to what they think in regards to the Eris being able to use PSfreedom... I greatly look forward to all responses. Thank you.
Ianio said:
I found this online (and I'm sure many know about this already): See attached image for links.
I was wondering if anyone knew if this would be possible with the Eris? There is a compatibility chart with the Eris listed, but it shows "In Progress." I'm not entirely sure how similar the Eris and the Hero are when it comes to the hardware, but if you click on HTC Hero on the attached compatibility chart, you will see this...
"HTC Heros come with 2.6.2x Kernel kernels thus use the USB driver "msm_hsusb" (confirm in /proc/config.gz) and is not currently supported."
Currently, I am running KaosFroyo v32 - Kernel version 2.6.29-bfs302. Would that mean the Eris using 2.6.2x kernels will not be supported by PSfreedom? If any devs (or others with knowledge) can give some input as to what they think in regards to the Eris being able to use PSfreedom... I greatly look forward to all responses. Thank you.
Click to expand...
Click to collapse
The Hero and Eris have identical hardware
so if it's the same hardware as the hero then the compatibility list for the psfreedom is incorrect? Do you know if any eris Devs are currently working on this at all? thanks!
Ianio said:
I found this online (and I'm sure many know about this already): See attached image for links.
I was wondering if anyone knew if this would be possible with the Eris? There is a compatibility chart with the Eris listed, but it shows "In Progress." I'm not entirely sure how similar the Eris and the Hero are when it comes to the hardware, but if you click on HTC Hero on the attached compatibility chart, you will see this...
"HTC Heros come with 2.6.2x Kernel kernels thus use the USB driver "msm_hsusb" (confirm in /proc/config.gz) and is not currently supported."
Currently, I am running KaosFroyo v32 - Kernel version 2.6.29-bfs302. Would that mean the Eris using 2.6.2x kernels will not be supported by PSfreedom? If any devs (or others with knowledge) can give some input as to what they think in regards to the Eris being able to use PSfreedom... I greatly look forward to all responses. Thank you.
Click to expand...
Click to collapse
I've been looking for a port for the eris as well, but I have been waiting patiently. You shouldn't come here and nag the Devs. When it comes out, it comes out. If you are impatient, then just buy the usb board.
The psfreedom site is down. I did try some of the other ports for other phones with no success. Thought I bricked my phone trying. Got lucky I guess so save your time and energy and don't try the other ports
Sent from my Eris using XDA App
I dont think we will be seeing this on the eris for sometime as the USB driver used is actually the msm_hsusb driver. This was verified last night when i was in #psfreedom where someone was trying to get psfreedom on an eris and kept running into a problem and it turned out to be because of the msm_husb driver was in use. so until that msm_husb driver is working with psfreedom we are probably SOL.
Well I would not give up hope yet. With our usb boards the Eris and the incredible are the only HTC boards without psgroove. Just a matter of time
Sent from my Eris using XDA App
well the hero is now done. so i wonder if it'll work on the eris im at work now so i'll have to check it out later.
This is now working on the Eris i tested it for the dev waiting for him to officially release it should be this afternoon.
http://psfreedom.com/wiki/Device_compatibility_list
should be working. any questions i'll do my best to answer but i am not the dev just a tester. rgov gets all the credit.
hay just wondering where to start id like to try this but have no idea bout the phone done other kinds of flashing but never my phone do i need to get Android-SDK installed then kaosfroyo should i figuer out how to back up my phone first i know im a noob but hay never really thought about my phone as a toy its just a phone
so there aren't 2 post open with this go here,
http://forum.xda-developers.com/showthread.php?p=8095395#post8095395
Literally just rooted 2 PS3s, thanks guys!
refthemc said:
Literally just rooted 2 PS3s, thanks guys!
Click to expand...
Click to collapse
with an Eris?
rgov should be linking the files again here shortly from the wiki. it's his baby and i'll let him release it how he pleases. sit tight guys should be soon.
Well, I am unable to get this to work properly. My Eris is set up EXACTLY the way it needs to be (kaosfroyov34 with the proper kernel). I can fastboot the boot.img and my phone reboots (like it is supposed to) then I enter the information into the terminal like stated on the directions. When it comes time to plugging it into the PS3, I am met with failure as the new folders do not show up. No way to install the backup manager or anything for that matter.
Here is the crazy part... last night (before the directions were posted on the droid eris psfreedom wiki) there were files listed. I downloaded them and was able to jailbreak my PS3 using those files. I was able to install backup manager and even manager to backup my copy of Oblivion to an external HDD. But every time I attempted to load it, it would return me to the XMB but not show Oblivion. Instead it showed me the game I had in the disc drive (Super Street Fighter IV). After trying several times, I called it quits and went to bed (waiting for the eris psfreedom wiki to be updated with instructions.)
This morning, I followed the new instructions to the "T" but cannot "root" the PS3. It just will not work. The PS3 keeps loading like it normally should. Yes, I am unplugging the console (I have a Slim), yes I plug in the phone before plugging the PS3 back in. Yes, I press "power" then "eject" immediately. Again, I got this working last night. And yes, my firmware is still 3.41.
One thing that I noticed with the updated wiki... the .zip that I download now contains 4 files rather than the two I had from last night.
._boot.img
._psfreedom.ko
boot.img
psfreedom.ko
So, does anyone have any idea as to what is going on? Did the files on the wiki get changed so dramatically that they do not work anymore? I've also noticed that on the ps3-hacks.com - PSFreedom for HTC Droid Eris Released section, there are comments from other users that are experiencing the exact same issue I am (folders not appearing on the XMB.)
Any help would be greatly appreciated... this is giving me quite the headache.
UPDATE: I decided to try the files I acquired last night (from filevo.com/z67xy48mjoe6.html) and I can jailbreak the PS3 once again... but backup manager isn't supported. I try and load a game from HDD, reboots back to XMB, but only shows the game I have in the disc drive. So, I'm guessing that the files on (psfreedom.com/wiki/HTC_Droid_Eris) do not work or I am just not doing something...
UPDATE #2: I decided to start mixing and matching files... as a means to see exactly what is going wrong. This attempt, I used the boot.img that I got from (filevo.com/z67xy48mjoe6.html) with the newer psfreedom.ko file from (psfreedom.com/wiki/HTC_Droid_Eris). The PS3 will not boot into "root" mode. This leads me to believe there is something wrong with the newer psfreedom.ko file.
Since I can "root" the PS3 using the original files I grabbed, but playing backup games is not supported... does anyone know if it's possible to edit the psfreedom.ko file to allow backup support? If so, then how?
Ianio said:
Well, I am unable to get this to work properly.
Click to expand...
Click to collapse
I a in the exact same position as you, after I asked for th files lastnight , I visited the change log at the wiki and saw the post they removed, and I grabbed those files I was able to jailbreak but running backups were not supported
With the new ko file, it doesent jail break at all for me either. and I downloaded a dozen different ( or same) backupmagaers, including the rdx and some give me black screens, but none work with the 1st posted .ko
anyone make any headway? how to we specify the other payload?
thanks
There is another "older" version of the files that work, I am new and cannot post a link, but if you google "eris psfreedom" and look through the comments you shall find what ye seek
Ianio said:
Well, I am unable to get this to work properly. My Eris is set up EXACTLY the way it needs to be (kaosfroyov34 with the proper kernel). I can fastboot the boot.img and my phone reboots (like it is supposed to) then I enter the information into the terminal like stated on the directions. When it comes time to plugging it into the PS3, I am met with failure as the new folders do not show up. No way to install the backup manager or anything for that matter.
Here is the crazy part... last night (before the directions were posted on the droid eris psfreedom wiki) there were files listed. I downloaded them and was able to jailbreak my PS3 using those files. I was able to install backup manager and even manager to backup my copy of Oblivion to an external HDD. But every time I attempted to load it, it would return me to the XMB but not show Oblivion. Instead it showed me the game I had in the disc drive (Super Street Fighter IV). After trying several times, I called it quits and went to bed (waiting for the eris psfreedom wiki to be updated with instructions.)
This morning, I followed the new instructions to the "T" but cannot "root" the PS3. It just will not work. The PS3 keeps loading like it normally should. Yes, I am unplugging the console (I have a Slim), yes I plug in the phone before plugging the PS3 back in. Yes, I press "power" then "eject" immediately. Again, I got this working last night. And yes, my firmware is still 3.41.
One thing that I noticed with the updated wiki... the .zip that I download now contains 4 files rather than the two I had from last night.
._boot.img
._psfreedom.ko
boot.img
psfreedom.ko
So, does anyone have any idea as to what is going on? Did the files on the wiki get changed so dramatically that they do not work anymore? I've also noticed that on the ps3-hacks.com - PSFreedom for HTC Droid Eris Released section, there are comments from other users that are experiencing the exact same issue I am (folders not appearing on the XMB.)
Any help would be greatly appreciated... this is giving me quite the headache.
UPDATE: I decided to try the files I acquired last night (from filevo.com/z67xy48mjoe6.html) and I can jailbreak the PS3 once again... but backup manager isn't supported. I try and load a game from HDD, reboots back to XMB, but only shows the game I have in the disc drive. So, I'm guessing that the files on (psfreedom.com/wiki/HTC_Droid_Eris) do not work or I am just not doing something...
UPDATE #2: I decided to start mixing and matching files... as a means to see exactly what is going wrong. This attempt, I used the boot.img that I got from (filevo.com/z67xy48mjoe6.html) with the newer psfreedom.ko file from (psfreedom.com/wiki/HTC_Droid_Eris). The PS3 will not boot into "root" mode. This leads me to believe there is something wrong with the newer psfreedom.ko file.
Since I can "root" the PS3 using the original files I grabbed, but playing backup games is not supported... does anyone know if it's possible to edit the psfreedom.ko file to allow backup support? If so, then how?
Click to expand...
Click to collapse
here's the fix for backupmanager just replace the psfreedom.ko with this one i edited and you will have backup support
you rock! I will be trying it soon as my wifes done with the tv..
Maybe this question belongs in the general android dev section, if so then sorry. What makes a phone "brick". I know what it means, but why can't we in brick them. If everything is wiped, what keeps us from accessing the wiped partition with a pc and doing what we want to with it. We do it with computers all the time. I know its not exactly the same, but its very similar isn't it? Is it like the BIOS going bad on a pc that causes them to brick?
Sent from my ADR6425LVW using xda app-developers app
From what I have heard, at least on the Rezound, bricks are generally caused by bad hboots. People do often compare hboots to BIOSs, but when they do, they always qualify their statements, adding that the two actually have little in common, but it's the best comparison between Android and PC. I'm sure someone else can explain that a lot better than I can. I believe a brick can also, theoretically, be caused by a bad kernel/boot partition, since it is what tells the phone where to get the information needed to boot (or something like that).
People also sometimes call it bricking when they just mess up the hardware in some way, like while replacing the digitizer.
Their are methods to unbrick from an hboot related brick, but they do not always work.
What Max said.
Just wanted to say you did indeed post this in the correct section. Even if it's a development related question, questions belong in the questions section
Sent from my ADR6425LVW using XDA Premium.
I always thought the same thing why can't you just wipe everything and reinstall if the brick is caused by a software issue then what's the stop you from removing that software and putting working stuff on.
The only thing I can think of to answer my own question would be, for example, you know how you can adjust the voltages to the CPU, well lets say you install some bad or damaged software which controls the Hardware say you send too much voltage to a component such as the CPU and you fry the component by sending too much voltage or maybe its even possible by sending not enough voltage.
Just a thought anyways . I could be way off I have no idea really.
Sent from my HTC One S using xda premium
Bad hboot brick is the most common common and it is irreversible because you need a functional hboot to flash anything. So a corrupted hboot leaves you with a catch 22. Your hboot is bad, you want to flash a working hboot but your bad hboot can't flash anything so your stuck.
A kernel or bootlooping brick is a soft brick because you can still boot to hboot or recovery and flash a working kernel
Sent from my ADR6425LVW using xda app-developers app
Can't a bad radio brick it too? I know on a pc you can start with nothing, no boot partition or mbr, and the kernel is flashed with the os (windows, linux), and you boot from a cd or floppy. The only thong you start with is BIOS. Is being incapable of booting from another source like USB or sd card the main reason we can't unbrick most phones? I guess I'm just looking for deeper detailed nerd answers for a better understanding. I'm a nerd as most of you would probably claim to be too lol and I just want to get a better understanding of how it all works.
Sent from my ADR6425LVW using xda app-developers app
There are three main parts to phone firmware. You have the boot loader, which handles very low level stuff and generally doesn't touch partitions, but provides a boot environment for other software such as recovery and system...which is why, in Broad com routers, it is called the CFE or Common Firmware Environment. Think of it as the BIOS of the phone. If the boot loader is corrupt or damaged, chances are there will be no way to recover the phone via normal methods; JTAG must be used to directly interface with the hardware and force reflash of the boot loader.
Recovery is in a way like DOS. It has the ability to create, mount, change, and delete partitions, but can't touch low level stuff like the radio or bootloader. It can modify and remove files on partitions and change specific things such as the kernel. A damaged recovery can usually be fixed without any special tools as the phone will boot but won't go into recovery mode. In the case of the Rezound, a PH98IMG flash would fix it.
The operating system of the phone is as Windows or Linux GUI is to a computer. It provides the user with an easy to use environment as well as tools and software to help the user do what he wants to do. A damaged OS may boot, and problems may be limited to a few specific apps, or the problem may be system wide to the point of unusability...or if there is something wrong with the kernel, the OS will not start at all, and will be stuck in a boot loop. Easily fixable via recovery.
socal87 said:
JTAG must be used to directly interface with the hardware and force reflash of the boot loader.
Click to expand...
Click to collapse
What's JTAG?
feralicious said:
What's JTAG?
Click to expand...
Click to collapse
A lot of devices have JTAG ports that allow us to use another piece of hardware to access the deeper levels of the hardware and software.
This makes it possible to unbrick by fixing those deep files that are required for the device to work.
Also, Wikipedia is your friend.
Here's the nerdiest answer you're going to get. Your phone is ultimately just a large hunk of copper and silicon. It contains all sorts of microchips and connections and are necessary for literally every function of the phone. Literally... From the LEDs to the audio components. Everything. If youve heard of a schematic that's what I, talking about. Each one of these microchips must be programmed form its specific function. Were literally talking hardware level here. No Android OS no hboot etc.
Point of explaining all of that being that there are all sorts of programmable parts of the phone that you will never modify, access, or even think about. If you manage to access and screw up the wrong thing.. You can quickly go from functioning phone to just a hunk of copper and silicon. Hboot is the lowest layer software that devs will modify. If you screw up the hboot.... You are left with a brick. Is it ultimately possible to unbrick in any situation? Yeah of course. How else would HTC have made the phone in the first place. But if you screw up the hboot... You're gonna need an engineering degree to fix that thing. And at the cost/effort that that would take.. You'd be better off buying a new phone. Thus your phone is totaled and its best use just because a paperweight.
Sent from my Nexus 7 using Tapatalk 2
I think it's important to note that most of the phones people post about being "bricked" aren't actually bricked. A lot of times people panic and if they can't fix their phone, they call it a brick. It's kind of a common, often used slang term. Now there's terms like hardware brick, hard brick, software brick, and soft brick and probably some more.
But if it's fixable in my opinion using a computer and commands, or if you can see it's getting power, it's usually not really bricked.
For example, when the s off process came out the forums were over run by people who "bricked" their phones while trying to attain s off. What actually happened in a big number of these cases was that the windows script replaced the boot.img that was on their phone with a custom boot.img for the service mode. When there was a windows error with the software which was newly developed and released, and the windows app hung up or the computer went weird mid process, they had a black screen with a funny image, like a disk and arrow maybe, and when they turned the phone on it only went to that screen. In fact it happened to me which is why I figured out how to fix it and what caused the problem.
Now all they would have had to do is run a fastboot command from their computer, "fastboot flash boot boot.img" to flash the boot.img that matched whatever rom was installed on their phone, and they would be back up and running. But for a large number of users, when they phone was unresponsive and turning it on took them straight to the black screen, they considered it "bricked."
When in fact the phone was doing exactly what it had been commanded to do, and it was the person who was expecting something unreasonable, when you think of it in 1's and 0's, or black and white. Of course this isn't always the case, there are some real bricks, just not as many as one would first believe if they scanned through forum topics for the word bricked in the title.
A common theme I seem to see around here is those who want to S-Off but have the wrong OS. I'm not sure why this is a problem as the unlimited.io team lays out the linux option pretty clearly, but yet still many complain of having the wrong OS..So, here you go. I'll try to lay it out as simply as I can for those who maybe just don't understand.
This is the set up for building a bootable USB drive.
First off, go here and download the latest Ubuntu Desktop ISO image :
http://www.ubuntu.com/download/desktop/thank-you?release=latest&bits=32&distro=desktop&status=zeroc
Now download Universal USB installer from here :
http://www.pendrivelinux.com/downloads/Universal-USB-Installer/Universal-USB-Installer-1.9.2.4.exe
Ensure that your USB drive is Fat16/Fat32/NTFS formatted. The USB installer is very easy to use. Just select your ISO and your flashdrive and click install. It does all the work.
Once the drive is completed safely eject your flash drive and shut down your PC. You need to set your PC to boot from USB. This method might be different for you than it was for me. My laptop I tap F9 while booting. You will have to check into this for your particular machine.
Once you have the the USB booting you will be presented with a few options. Just pick Run Live (I think it's the first and default option). This will boot you into a fully fuctional Linux 32bit desktop. Just what you need to S-OFF! From here just go to the Unlimited site and follow their directions to the letter. Do all this and you should be S-Off in about an hours time.
If this is laid out somewhere else, Mods feel free to delete. If you found it to be helpful, hit the thanks. Be well fellow tweakers.
P.S. This makes no changes to your PC. Once done shut down, remove the pen drive, and boot normally to Windows.
mulhiny said:
A common theme I seem to see around here is those who want to S-Off but have the wrong OS. I'm not sure why this is a problem as the unlimited.io team lays out the linux option pretty clearly, but yet still many complain of having the wrong OS..So, here you go. I'll try to lay it out as simply as I can for those who maybe just don't understand.
This is the set up for building a bootable USB drive.
First off, go here and download the latest Ubuntu Desktop ISO image :
http://www.ubuntu.com/download/desktop/thank-you?release=latest&bits=32&distro=desktop&status=zeroc
Now download Universal USB installer from here :
http://www.pendrivelinux.com/downloads/Universal-USB-Installer/Universal-USB-Installer-1.9.2.4.exe
Ensure that your USB drive is Fat16/Fat32/NTFS formatted. The USB installer is very easy to use. Just select your ISO and your flashdrive and click install. It does all the work.
Once the drive is completed safely eject your flash drive and shut down your PC. You need to set your PC to boot from USB. This method might be different for you than it was for me. My laptop I tap F9 while booting. You will have to check into this for your particular machine.
Once you have the the USB booting you will be presented with a few options. Just pick Run Live (I think it's the first and default option). This will boot you into a fully fuctional Linux 32bit desktop. Just what you need to S-OFF! From here just go to the Unlimited site and follow their directions to the letter. Do all this and you should be S-Off in about an hours time.
If this is laid out somewhere else, Mods feel free to delete. If you found it to be helpful, hit the thanks. Be well fellow tweakers.
P.S. This makes no changes to your PC. Once done shut down, remove the pen drive, and boot normally to Windows.
Click to expand...
Click to collapse
You may want to change the title of your thread. I was not expecting this at all when I opened it up. I was expecting a question. Maybe something like 'How to get Ubuntu to obtain S-Off' or something of that nature.
Just my opinion.
Thanks!
nice write up
i personally preferred to use win 7 32bit though
i guess im just comfy using windows
Re: Guide to running a live Ubuntu session to S-Off
flex360 said:
nice write up
i personally preferred to use win 7 32bit though
i guess im just comfy using windows
Click to expand...
Click to collapse
Well, me too..but my machine is Windows 7 64bit and after all the warnings I didn't want to chance any screw ups. After running the live Ubuntu session I was amazed at how easy it was. Figured I'd share the love for those who may not understand how easy it really is.
Sent from my EVO using Tapatalk 2
This should be common sense for those used to Linux but I forgot and it took me a while to figure out:
Make sure you are running the Racun tools from a drive that is Linux-formatted (using ext3 or ext4 for example). Otherwise, you will not be able set the proper permissions and you may encounter errors like I did. * facepalm *
I just ran it through Windows 7 64 bit with no Linux...it was easy as pie.
Sent from my EVO using xda premium
I ran mine using Windows 7 64-bit. No issues
The advice is free....the bandwidth, not so much
Yup, another Win7 64bit user here. I've obtained s-off on both of my Evo LTEs using that setup. Went perfectly smooth and I didn't have to run anything twice or do anything manually. Was like it was a made for Win7 64bit!!
That said, it is super easy to make a LiveCD. I have a LiveCD and have used it to boot in to Ubuntu multiple times. I just wanted to see how far along it would get. I was pleasantly surprised that it finished, and was using successful as well!! After one Evo LTE was a success, I ran it on the second one as well!
Sent from my White Evo LTE running MeanBean, using XDA Premium
It's good to hear so many success stories using 64bit..with all the options out there I really can't see any reason for anyone in these forums to not S-off. The information and help is here.
Sent from my EVO using Tapatalk 2
mulhiny said:
It's good to hear so many success stories using 64bit..with all the options out there I really can't see any reason for anyone in these forums to not S-off. The information and help is here.
Sent from my EVO using Tapatalk 2
Click to expand...
Click to collapse
Nevertheless thanks for this thread.
#Root-Hack_Mod*Always=LTE
I actually used Windows 8 Pro 64 Bit. Everything fine except for step 14. My device was not being recognized. I used Ubuntu (just for step 14) and bingo!
Live usb works but last I checked Unlimited did not support live usb so if you run into problems they will be very reluctant to help
om4 said:
Live usb works but last I checked Unlimited did not support live usb so if you run into problems they will be very reluctant to help
Click to expand...
Click to collapse
Correct! The last time I checked as well, Team Unlimited does not support this method. I believe that it's due to your system's response speeds. When it's reading from a USB Stick/Drive it will be slower than when reading from a disc. I could be totally off base here, as this is just my own thoughts and I haven't heard Team Unlimited say. I'm simply relating my response to the reason 64bit isn't supported. People were saying that the Team just didn't want to take the time to test 64bit systems, which is completely incorrect!! The drivers needed to achieve s-off simply don't function properly on 64bit systems (and take longer to react, if I'm remembering this correctly).
***********
Disclaimer: Just because myself and others have been successful using 64bit does NOT mean that everyone, or anyone else for that matter, will have success using a 64bit system. If you are not comfortable with your phone messing up during the process and no one being willing to help/assist you then do NOT use Team Unlimited's tools on a 64bit system! Team Unlimited will not assist you if you're using a 64bit system (and yes, they WILL be able to tell). As long as you comply to their simple requests, if you need their help at any point (before, after, or during) use of their tools, then Team Unlimited will happily assist you on their IRC channel!
***********
I say this because I don't want anyone getting in to a situation with their phone where they get stuck, confused, or anything, and are not able to go directly to the developer of the tools for help! I really just want everyone to have a good experience with their Evo LTE and wish everyone good luck in everything/anything they do with their Evo LTE!! I remember my first Android experience, so I know what it's like to be new to Android and not fully understanding all of the terminology, how the operating system works, or what system pieces rely on what to function properly. While I had been unlocking and flashing WinMo phones for a while, Android is a different animal and could be a little overwhelming in the beginning. Plus, think of it like this - the more that people enjoy this phone then the more they will tell a friend, or someone will simply overhear them talking about it and become intrigued themselves. Thus, increasing Androids user base(and hopefully hurting Apple ) and maybe even improving HTC's profits!!
Sent from my White Evo LTE running MeanBean, using XDA Premium
I didn't realize that USB was not supported. After checking the site again I noticed that it indeed mentions a live CD but doesn't talk about using USB. I'm going to ask a mod to remove or close this thread due to this coming to my attention. I don't want anyone having issues at my hands.
Sent from my EVO using Tapatalk 2
Hi all! I could use a little help if ya'll don't mind. I'm new to the Amaze but not at all to Android.
I found an Amaze 4g on eBay for $65 that was in pretty good shape with one glaring problem: it wasn't fully functional. The seller explained that it would bootloop after hitting the HTC screen and, knowing what I know about Android, it sounded to me like this should be pretty simple to fix. And if I'm absolutely wrong, then I should be able to sell it for parts (perfect screen on it) to get some of my money back!
Well, it came in and sure enough, it bootlooped at the HTC screen and it was still S-On (yay for hoping nobody trashed its internals too hard!). So I slapped a factory image on the SD Card, loaded it up, and after a slow first boot I heard the T-Mobile jingle! Yay, all is good! Or so I thought...
On stock software, all is good. Everything functions as it should. And if I wanted to leave it stock, I would have never noticed a problem. However, when I went to go unlock it, that's when I began to run into problems. For the life of me, no matter what I do, I absolutely cannot get fastboot to work! ADB works great! I've transferred quite a bit over USB so the port itself seems fine. I've loaded up drivers (started out with universals, then went to HTC, then went to the toolkit stickied at the top of the forums here) and no matter what I use, it simply will not work. I can ADB to it all day, but I just cannot use fastboot.
Just going with the assumption that maybe I had bad/dirty/whatever drivers/conflicts, I actually installed Windows 7 64-bit from scratch, loaded up Windows Updates, and then ran the all-in-one toolkit (which takes care of drivers for me) and alas, absolutely nothing different. ADB works great but I can't get any response from fastboot with the device.
Have I done something wrong/dumb here? Is there something special about this device that could allow something required for fastboot to not work (damaged USB port in a special way) that would allow all other USB operations to function?
Thanks in advance, friends!
Jaxidian said:
Hi all! I could use a little help if ya'll don't mind. I'm new to the Amaze but not at all to Android.
I found an Amaze 4g on eBay for $65 that was in pretty good shape with one glaring problem: it wasn't fully functional. The seller explained that it would bootloop after hitting the HTC screen and, knowing what I know about Android, it sounded to me like this should be pretty simple to fix. And if I'm absolutely wrong, then I should be able to sell it for parts (perfect screen on it) to get some of my money back!
Well, it came in and sure enough, it bootlooped at the HTC screen and it was still S-On (yay for hoping nobody trashed its internals too hard!). So I slapped a factory image on the SD Card, loaded it up, and after a slow first boot I heard the T-Mobile jingle! Yay, all is good! Or so I thought...
On stock software, all is good. Everything functions as it should. And if I wanted to leave it stock, I would have never noticed a problem. However, when I went to go unlock it, that's when I began to run into problems. For the life of me, no matter what I do, I absolutely cannot get fastboot to work! ADB works great! I've transferred quite a bit over USB so the port itself seems fine. I've loaded up drivers (started out with universals, then went to HTC, then went to the toolkit stickied at the top of the forums here) and no matter what I use, it simply will not work. I can ADB to it all day, but I just cannot use fastboot.
Just going with the assumption that maybe I had bad/dirty/whatever drivers/conflicts, I actually installed Windows 7 64-bit from scratch, loaded up Windows Updates, and then ran the all-in-one toolkit (which takes care of drivers for me) and alas, absolutely nothing different. ADB works great but I can't get any response from fastboot with the device.
Have I done something wrong/dumb here? Is there something special about this device that could allow something required for fastboot to not work (damaged USB port in a special way) that would allow all other USB operations to function?
Thanks in advance, friends!
Click to expand...
Click to collapse
Hi,
I think that a USB port may be broken, but that would require soldering another USB port on it, so it might not be worth it.
Did you already try a RUU? If it's a software issue you may be in luck since RUU's fix those 90% of the time!
SuperAfnan said:
Hi,
I think that a USB port may be broken, but that would require soldering another USB port on it, so it might not be worth it.
Did you already try a RUU? If it's a software issue you may be in luck since RUU's fix those 90% of the time!
Click to expand...
Click to collapse
As I said, I recovered the soft-brick with an RUU. So getting to stock is fine, but I don't want to stay stock.
Are you saying it's possible that the USB port is broken even though ADB works perfectly and I can transfer a couple GB of data over it successfully?
Jaxidian said:
As I said, I recovered the soft-brick with an RUU. So getting to stock is fine, but I don't want to stay stock.
Are you saying it's possible that the USB port is broken even though ADB works perfectly and I can transfer a couple GB of data over it successfully?
Click to expand...
Click to collapse
Well that's just a guess... lol
It's probably not a USB problem then.
Yeah, unless there's something different about the Amaze compared to most other Android phones, I don't think this is a USB problem although it acts like it is. I'm really baffled on this. :-/
Jaxidian said:
Yeah, unless there's something different about the Amaze compared to most other Android phones, I don't think this is a USB problem although it acts like it is. I'm really baffled on this. :-/
Click to expand...
Click to collapse
Well good luck, but you at least got it on a stock ROM working fine. You could sell it and make a profit this time!
It could possibly be a hardware issue, but IDK.
What are you trying to fastboot? Make sure your in the correct window I mean you have to be in bootloader.. I forget it almost every time also if adb works it has to work.. Try the correct jbear hboot and see cuz if I'm right jbear hboot are fastboot enable or something like that
Sent from my HTC_Amaze_4G using XDA Premium 4 mobile app
ravike14 said:
What are you trying to fastboot? Make sure your in the correct window I mean you have to be in bootloader.. I forget it almost every time also if adb works it has to work.. Try the correct jbear hboot and see cuz if I'm right jbear hboot are fastboot enable or something like that
Click to expand...
Click to collapse
Simply running "fastboot devices" is my litmus test - I'm unable to get it to actually see the device. And yes, I have it booted into the bootloader and I have put it into fastboot mode.
@ Jaxidian
i m not an expert ! just giving advice
May be m completely wrong, just trying to help
have u tried in ubuntu ?
Check your fastboot script?
Sent from my HTC_Amaze_4G using XDA Premium 4 mobile app
So if you hook the phone up to the computer and at a command prompt type, "adb devices" it returns your device serial number; but, if you then type, "adb reboot recovery" and are then in the bootloader fastboot and type, "fastboot devices" it doesn't return the device serial number?
Ok, so please forgive me for this. I'm used to Samsung devices, and rooting/custom recovery is as simple as "Download this, flash through Odin, Easy as pie".
So I have my brother's P769. He had rooted it, but was unsure how to install CWM on it. Me, being completely ignorant of unlocking the bootloader, was able to get CWM on it and flash CM10.2. Which, of course, gave me the LG Security Error. Been stuck for many a day trying to get back to V20F_00. It doesn't help that there is ABSOLUTELY NO WAY to install the omap4 drivers in Windows 8.1, and reserving USB devices to Virtualbox is a pain in the (insert desired graphical descriptor here:_______).
So, I am just trying to clarify the steps to get my brother the CyanogenMod he so desires.
From Stock:
Root device
Unlock Bootloader
Install CWM
Flash CM from CWM
Is this a correct assumption?
jparnell8839 said:
Ok, so please forgive me for this. I'm used to Samsung devices, and rooting/custom recovery is as simple as "Download this, flash through Odin, Easy as pie".
So I have my brother's P769. He had rooted it, but was unsure how to install CWM on it. Me, being completely ignorant of unlocking the bootloader, was able to get CWM on it and flash CM10.2. Which, of course, gave me the LG Security Error. Been stuck for many a day trying to get back to V20F_00. It doesn't help that there is ABSOLUTELY NO WAY to install the omap4 drivers in Windows 8.1, and reserving USB devices to Virtualbox is a pain in the (insert desired graphical descriptor here:_______).
So, I am just trying to clarify the steps to get my brother the CyanogenMod he so desires.
From Stock:
Root device
Unlock Bootloader
Install CWM
Flash CM from CWM
Is this a correct assumption?
Click to expand...
Click to collapse
Welcome JP,getting a break from the Blaze. I've had this beast for a week and I'm ready to crush the phone. So far I've been able to root and remove T-Mobile bloatware.
I've tried to unlock the boot loader many times and no luck. I've read thru the guides and the result is the same.
I sitting patiently to see if the devs can solve the mystery of the bootloader. I can't wait for the day so I can leave the stock Rom. Hope all is well
Sent from my LG-P769 using xda app-developers app
I've had this phone almost a year. As far as the unlocking bootloader goes, it seems like some p769s just aren't unlockable, no matter what method used. Mine is one of those. It may never be able to be unlocked. Just throwing that out there.
THIS link will show you the most common way to unlock the bootloader. It has simple directions and even a video. The only problem is that it doesn't work on some devices, such as mine, so just be wary. And many people in the thread have managed to get results by modifying the instructions, but others have not had any luck.
Good luck! Hope yours works
Welcome to the dark pits of xda hell....LMAO! :sly:
Sent from my LG-P769 using XDA Premium 4 mobile app
LaDY Vengeance said:
Welcome to the dark pits of xda hell....LMAO! :sly:
Sent from my LG-P769 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
This is as bad as when I had the Cliq XT , that was a beast as well. That was a replacement phone as well. Hopefully the devs can crack it
thehritzinator said:
I've had this phone almost a year. As far as the unlocking bootloader goes, it seems like some p769s just aren't unlockable, no matter what method used. Mine is one of those. It may never be able to be unlocked. Just throwing that out there.
THIS link will show you the most common way to unlock the bootloader. It has simple directions and even a video. The only problem is that it doesn't work on some devices, such as mine, so just be wary. And many people in the thread have managed to get results by modifying the instructions, but others have not had any luck.
Good luck! Hope yours works
Click to expand...
Click to collapse
That's the link I found, and thought "There's no way it's that complicated!"
HTC uses a dev key. I don't remember Moto's method, but it was simple. Samsung is ridiculously simple. Why is LG so complicated? This has only re-enforced my idea of "Never get an LG"
LaDY Vengeance said:
Welcome to the dark pits of xda hell....LMAO! :sly:
Sent from my LG-P769 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Lol thanks! I'm starting to believe it
flyers00 said:
This is as bad as when I had the Cliq XT , that was a beast as well. That was a replacement phone as well. Hopefully the devs can crack it
Click to expand...
Click to collapse
This is the worst phone, as far as modding goes, I've ever seen. I haven't experienced many devices, but geez. Heck, hacking a SGS2 i777 with a faulty USB board was easier than this, and I couldn't even access recovery without ADB commands (because it thought a USB cable was plugged in even when it wasn't, was going to download mode) and couldn't enable ADB (because it thought a cable was plugged). I had to use SQLite hacks to force ADB to enable.
However, I've never let anything stop me before. I'm a world-champion Googler, and so I will crack this will probably take me a while, but meh.
jparnell8839 said:
That's the link I found, and thought "There's no way it's that complicated!"
HTC uses a dev key. I don't remember Moto's method, but it was simple. Samsung is ridiculously simple. Why is LG so complicated? This has only re-enforced my idea of "Never get an LG"
Lol thanks! I'm starting to believe it
This is the worst phone, as far as modding goes, I've ever seen. I haven't experienced many devices, but geez. Heck, hacking a SGS2 i777 with a faulty USB board was easier than this, and I couldn't even access recovery without ADB commands (because it thought a USB cable was plugged in even when it wasn't, was going to download mode) and couldn't enable ADB (because it thought a cable was plugged). I had to use SQLite hacks to force ADB to enable.
However, I've never let anything stop me before. I'm a world-champion Googler, and so I will crack this will probably take me a while, but meh.
Click to expand...
Click to collapse
Congrats on coming into teh darkside. I know you are world class Googler and if you find something or come up with something, I am in to help the cause. I was a guinea pig with the Blaze so why not here. Good luck with your Google skills