Related
OK, this is going to sound waaaay out there.
In the past week, I've had two G1's crap out on me. Well, one crapped out on me (the keyboard), and the RMA came damaged. #3 arrived yesterday, and it's rooted, Cupcaked and ready to go.
I restored the RMA unit back to RC33 without root. Everything OK, it's good to go back to the factory.
On the first one though - I went back to RC29 and re-installed the original SPL. What I didn't realize was that the custom splash image that I had installed wouldn't be overwritten in the process, so you guessed it - I've got my custom image coming up right after the G1 splash screen.
I'm still on RC29, so I'd just root it, except for one nasty little problem - not all of the keys work. Particularly - the enter key, which makes starting the telnet daemon impossible (at least to me).
So that's where I am. Does anyone know how I might either be able to root this sucker without having access to the enter key (is it possible to run a script, or is there another keystroke combo substitute for enter)? Is it possible to remap keys? Is there some other way to change that splash image back?
Or am I resolved to sending this thing back with a splash image that screams 'hey, this thing isn't stock!'
use adb to start telnet?
You could probably use ADB somehow, not sure the specifics though. Just out of curiosity, what is ur splash??
giantcrazy said:
On the first one though - I went back to RC29 and re-installed the original SPL. What I didn't realize was that the custom splash image that I had installed wouldn't be overwritten in the process, so you guessed it - I've got my custom image coming up right after the G1 splash screen.\
Click to expand...
Click to collapse
You used RC29 DREAIMG.NBH and it didn't reset your custom splash? Interesting.
giantcrazy said:
Or am I resolved to sending this thing back with a splash image that screams 'hey, this thing isn't stock!'
Click to expand...
Click to collapse
yeah send it like that... i had the same problem as you... and forgot to change the splash image... but i sent it like that to tmobile... been 2 months already and they havent said anything....
I cant seem to get adb working - isnt the HardSPL a requirement for adb? Would it be running on a stock RC29 phone with the regular SPL?
I thought of trying an app with a soft keyboard, but I don't know whether that'll work. I ran out of time to play with it yesterday so today's first try will be the soft keyboard.
My splash isn't anything offensive, just a picture of my kids. And it does come up after the initial splash screen (it seems the NBH file is resetting the first splash only, since I had put it in both spots). Failing the soft keyboard, its going to be time to send it back the way it is and hope TMo doesnt get bent out of shape (the phone does work and its in pristine condition, just a few of the keys are shorted somehow, and the water damage indicator is as white as can be).
Thanks for the suggestions though!
The original Eng. SPL supports fastboot..
I don't know if you can find it - I'm pretty sure the one in the sticky is signed with the test keys. And if you do find it, will the phone let you apply it??
Just throwing out an idea...
Good luck.
boogie1077 said:
The original Eng. SPL supports fastboot..
I don't know if you can find it - I'm pretty sure the one in the sticky is signed with the test keys. And if you do find it, will the phone let you apply it??
Just throwing out an idea...
Good luck.
Click to expand...
Click to collapse
Interesting - I'll seek out and report back. Thanks for the tip!
Nope - no dice To get the engineering SPL installed you still need to have the modified recovery image working.
What am I missing here - does adb need something else to work? I thought it'd work with a stock phone, although without root it'd be of lesser value.
no special form of adb is needed to use adb, what you are going to need to do is try this:
adb shell input text telnetd
adb shell input keyevent 66
those two commands are exactly like if you had typed them on the phone itself the first obviously types telnetd and the second hits enter for you. try it out and let me know if you need any more help, i may or may not be on most of the day i am going to see star trek tonight
also you wanna make sure that usb debugging is turned on in your options i think it's settings>applications>developement>usb debugging but i might be wrong, my phone isn't nearby
tubaking182 said:
no special form of adb is needed to use adb, what you are going to need to do is try this:
adb shell input text telnetd
adb shell input keyevent 66
those two commands are exactly like if you had typed them on the phone itself the first obviously types telnetd and the second hits enter for you. try it out and let me know if you need any more help, i may or may not be on most of the day i am going to see star trek tonight
also you wanna make sure that usb debugging is turned on in your options i think it's settings>applications>developement>usb debugging but i might be wrong, my phone isn't nearby
Click to expand...
Click to collapse
Thanks for the suggestion - I did get adb back, but when I entered the first shell command after connecting, I got the 'telnetd' up , but the carriage return/enter seems to not be working.
ok, well my next suggestion is a stretch and i'm gonna need to research a few things to even know exactly what to do, but what if you change the mapping of the keys so that whan you hit the enter key the phone responds by pressing the alt key and visa versa. i am not sure where the key mapping is stored i am looking for it now, but it seems like it would work ok(in theory)
tubaking182 said:
ok, well my next suggestion is a stretch and i'm gonna need to research a few things to even know exactly what to do, but what if you change the mapping of the keys so that whan you hit the enter key the phone responds by pressing the alt key and visa versa. i am not sure where the key mapping is stored i am looking for it now, but it seems like it would work ok(in theory)
Click to expand...
Click to collapse
That was one of the first things I thought about trying, but couldn't find any way to remap the keys. I'm going to go back to searching for it.
Well, I'm giving up.
I've tried everything I can think of, along with a few suggestions here. It seems that unless I start the telnet daemon from the home page with the keyboard it just ain't happening. Not an adb command, not a soft keyboard (and I tried a couple). Nada.
Thanks again for all your help - now I just have to hope this thing doesn't run up a red flag over at T-Mo...
So, I decided to try Ultimate X2 BetaII. Here's my problem:
I decided to flash to OEM ROM first, as I've read this is better with some ROMs, but I think I did something stupid. Instead of using the .exe file to install (_ATT Tilt_RUU_Kaiser_CINGULAR_WWE_3.57.502.2_radio_sign_25.88.40.05_1.65.21.18_Ship.exe), I decided I wanted to install with my SD card, so I extracted the .nb file (KaiserIMG_CINGULAR_WWE_3.57.502.2_radio_sign_25.88.40.05_1.65.21.19_Ship.nbh) and renamed it "KAISIMG.nbh" and copied it to my SD card. I installed with the standard SD card method, and now I'm stuck at a (seemingly) endless screen alignment that loops over and over. The only posts I've found so far on this topic seem to deal with hardware issues, but my screen has worked okay until now, so I'm guessing I screwed something up software-wise by impatiently trying my own idea, instead of following instructions.
Mind you all, this is only my second attempt at flashing a ROM, and the first one I flashed was months ago, so you can consider me somewhat of a newb.
By the way, I just tried going through the screen align twenty times to see if there was any change, and I'm still stuck there. I haven't tried making a welcome.not file yet, but I'll give it a shot now. It seems like even if that works, there should be a way to fix my problem properly. Any ideas?
welcome.not
Welcome.not does get me past the align screen and into the Ultimate X2 Beta II ROM. This does, of course leave me unable to align my screen with the WM app. Still looking for a "proper" fix.
Did you try a different ROM?
RE: Did you try a different ROM?
I first had the screen alignment problem after flashing the OEM ROM. Afterward, I flashed Ultimate X2 Beta II, and the problem persisted. I flashed back to OEM, and the problem was still there, so I flashed back to Ultimate X2, and after conferming the existance of the same issue, I used the welcome.not bypass. I suppose this will be okay, if I can find another way to align the screen, besides the WM screen alignment utility. I saw a post regarding a possible Reg key that changes the max screen alignment repeats. Perhaps altering that key would make it save my initial alignment and end the infinite loop?
P.S. Does anyone know of a screen alignment utility that works from the device and saves the settings, a way of working around the WM utility?
Registry Keys?
Are there registry keys I could alter to fix my screen alignment?
You do have a correct HARDspl right? When you enter bootloader you should see hard spl. Flash another spl and see what happens. Sorry im not of more help but im on my phone.
I have HardSPL 3.29. Ultimate X2 Beta II is running quit well. Radio's working fine, too. I just can't figure out my screen alignment issue. If someone could hook me up with a screen alignment file or registry settings, and perhaps clue me in a little on how to implement, that would, perhaps, be a temporary fix.
Well then think old school. If the cross is moving when you press it i would think the digitizer is ok. So clean the edges around the screen really good. Maybe some lint or dust around the edges. Also maybe loosen the screws on the back a little in case the screen is in a bind.
Yeah, I think the digitizer is fine. I already cleaned the edges with a business card. I don't have a torx kit with me, but I'll keep the screw loosening in mind. I figured the problem must be a result of extracting the .nbh file from the OEM install file, rather than running the .exe. However, flashing again (I used the .exe files for the OEM and Ultimate X2 the second cycle of flashing, rather than using my SD card) hasn't helped. I ran across the following thread, and am downloading the app now. I don't know if it will help, but maybe if someone else runs it and extracts their alignment settings, they can post them for me to try out?
http://forum.xda-developers.com/showthread.php?t=396466
Reg Key
Here's another instance of the same type of solution:
corollatercel said:
So i've been having problems with the screen alignment on mine since i had one spot on my MDA screen that was dead and my screen was cracked so the alignment wizard basically got stuck in limbo when I tried to calibrate it. SO basically what I had to do was download PHM Registry Editor and change the registry key touch referenced in here.
kernelguy said:
My touchscreen had a crack only at the bottom. After skipping the 'align screen' during initial ROM load, I lived with a non-functional touch screen for a day or two. I then remembered the post from equinoxe that had registry settings for his phone. I took those settings and updated my registry. I now have a decent touch screen - at least the top 3/4 works fine.
The key and settings are:
[HKEY_LOCAL_MACHINE\HARDWARE\DEVICEMAP\TOUCH]
"CalibrationData"="1922,1957 3330,639 3317,3276 600,3230 609,677 "
I could surmise that the screen is being treated as a square of 3900 x 3900 dots. 0,0 seems to be the top, right corner.
kernelguy
Click to expand...
Click to collapse
Afterwards I used the remote alignment tool (attached) to retrieve the correct settings from the correctly aligned mda(after changing the registry key then rebooting the device) then made sure the file was saved on my pc....normally it's saved by default in the C:\Program Files\Code Factory\Remote Screen Alignment directory. The file was called WIZA200.dat. I did a soft reset then when the alignment screen came up I did the skip function in the remote screen alignment application and it automatically read the proper calibration from the wiza200.dat file and then properly calibrated my mda now my screen is properly calibrated even though i never ran the alignment wizard.
So here are the Instructions folks:
1. Download the latest activesync and connect your mda to your computer and verify your device is connected(not as guest)
2. Perform a soft/hard reset on your MDA then tap your screen to start the screen alignment wizard
3. Download the remote screen alignment tool attached and install it on your machine.
4. Download the wiza200.txt file attached and rename it to WIZA200.dat then put it in the C:\Program Files\Code Factory\Remote Screen Alignment directory on your computer
5. Ensure your MDA is connected to your pc(A green activesync Icon usually indicates a connection )
6. Open the remote screen alignment tool on your pc meanwhile your phone be displaying the alignment screen wizard.
7. Click SKIP in the screen alignment tool.
Assuming everything went fine a message box displaying "The operation has been completed successfully. Your device will be restarted." should pop up on your computer and your device should restart. Afterwards your phone will run the files it always does when you do a soft/hard reset then you touch screen should be properly calibrated and work fine.
Click to expand...
Click to collapse
If someone could do a fresh, accurate screen alignment and report the registry key settings, I could try editing them for myself and see if that does it.
check your pm
check your pm
Thanks!
Thanks for the help, guys. I found the kaiser.dat file in the program's directory, opened with notepad, and copied the string into the appropriate reg key:
2002,1944 3292,635 3352,3272 681,3268 624,673
Thanks, lewnetoons, for providing your info, as well:
1862,1960 3131,673 3129,3260 628,3291 635,655
I suspect my digitizer may need replacement because it wasn't terribly accurate before I encountered this problem, but I'll have to find a proper solution for the "Align Screen" loop for a new digitizer to even matter. This is enough to appease me for now, as my screen is now responding semi-accurately, but if anyone can come up with a fix for my align screen loop, so I won't have to rely on the "welcome.not" fix, I would appreciate it a LOT.
A little off-topic, but it seems to me that five points isn't enough to align the whole digitizer in the first place.
Thanks a lot, guys, I'm good for now.
Bob_Beard said:
Thanks for the help, guys. I found the kaiser.dat file in the program's directory, opened with notepad, and copied the string into the appropriate reg key:
2002,1944 3292,635 3352,3272 681,3268 624,673
Thanks, lewnetoons, for providing your info, as well:
1862,1960 3131,673 3129,3260 628,3291 635,655
I suspect my digitizer may need replacement because it wasn't terribly accurate before I encountered this problem, but I'll have to find a proper solution for the "Align Screen" loop for a new digitizer to even matter. This is enough to appease me for now, as my screen is now responding semi-accurately, but if anyone can come up with a fix for my align screen loop, so I won't have to rely on the "welcome.not" fix, I would appreciate it a LOT.
A little off-topic, but it seems to me that five points isn't enough to align the whole digitizer in the first place.
Thanks a lot, guys, I'm good for now.
Click to expand...
Click to collapse
glad you got it fixed my brother
It occurs to me that I may not have been clear in my first post. I didn't use NBHExtract or anything. I opened the exe with 7-Zip, extracted the larger of two nbh files, renamed it, copied it to my SD card, and flashed it to my phone. I don't know why I did it that way, and it seems like it sort of worked, but something was lost in translation. I've done half a dozen or so flashes since then, but the problem still exists. Any insight into a possible permanent solution for this semi-permanent problem would be very much appreciated.
So, I've gone through a few flashes and my screen alignment still works for the most part, but it can be a pain in the ass using programs that have have small expandable menus or buttons at the bottom of the screen. I can fine tune this a little better using my slow, primitive hand-modify the registry method, but I would still appreciate any input on fixing the problem.
I guess I'm looking for one of two possible solutions:
1. A program that does exactly what the built-in screen alignment utility does.
2. A way to fix whatever I ****ed up, so I can use the screen alignment utility without it looping infinitely.
So, once again, does anyone have any helpful input?
Bob_Beard said:
So, I've gone through a few flashes and my screen alignment still works for the most part, but it can be a pain in the ass using programs that have have small expandable menus or buttons at the bottom of the screen. I can fine tune this a little better using my slow, primitive hand-modify the registry method, but I would still appreciate any input on fixing the problem.
I guess I'm looking for one of two possible solutions:
1. A program that does exactly what the built-in screen alignment utility does.
2. A way to fix whatever I ****ed up, so I can use the screen alignment utility without it looping infinitely.
So, once again, does anyone have any helpful input?
Click to expand...
Click to collapse
try flashing abu's new rom that doesn't require screen alignment. see what happens.
I flashed it within hours of its release, but I'm not sure how it's affected me, since I still keep "welcome.not" in the root directory of my SD card, and I input my alignment config into the registry after every flash. I may expirament with it, though, by removing "welcome.not" and/or reflashing.
Bob_Beard said:
I flashed it within hours of its release, but I'm not sure how it's affected me, since I still keep "welcome.not" in the root directory of my SD card, and I input my alignment config into the registry after every flash. I may expirament with it, though, by removing "welcome.not" and/or reflashing.
Click to expand...
Click to collapse
yeah give it a try and see what happens
I'm trying to put the android 2.0.1 on my touch pro and am having some troubles.
I am getting to where you run HaRET and it starts up and pulls up the loading bar that says it is going to run linux. It loads all the way up then the load box goes away and it leaves me frozen at the file explorer with the haret start bar on the bottom and also the file bar on the top.
I attached a picture showing my phone at this screen too.
Thanks guys
It just seems like linux will not start up for me? Is there something else I should do?
Read: forum.xda-developers. com/showthread.php?t=601751
and/or
forum.xda-developers. com/showthread.php?p=5420781#post5420781
Hello, I have a XDA Orbit 2 (screen res 240x320). I wanted to install Android on it. I did a quick search and found a few things....
My Tutorial:
http://forum.xda-developers.com/showthread.php?t=625200
I had a read though that. Got a rough idea on what I was doing.
(1º CHOOSE YOUR ANDROID BUILD) I decided to use:
Warm Donut (Donut): http://forum.xda-developers.com/showthread.php?t=619980
(2º INSTALL THE OS LOADER TO NAND) Now this was my problem, I visited the website "http://it029000.massey.ac.nz/vogue/files/?C=M;O=D" to choose my .NBH file. I choose the latest ones. And the selection was:
polaimg-panel1-320-08-04-10.nbh
polaimg-panel2-320-08-04-10.nbh
polaimg-panel3-320-08-04-10.nbh
I tested ALL 3 and non worked (unless I was doing something wrong) all i got was when it restarted it went to a fizzy kind of screen then came straight to a white one.
But I did try another .NBH file what was near the bottom called "polaimg-240x320-03-02-10.nbh " that didn't work but it was close.... when it restarted it vibrated once then went to a black screen then vibrated twice then came to another screen with a animal in the top left and under niethe they was loads of white numbers letters scrolling down the screen then it just got stuck on that and nothing happened from there.
EDIT:
I have got a bit closer now. I decided to try run it through haret, Well... I click Run. see black screen with letters scrolling, I get to the bit where it says "Hold down Volume Up or DPad center to launch installer. And before I have chance to do that this appears under:
Code:
sh:2: unknown operand
losetup: /dev/block/loop 1: No such file or directory
Failed
Failed to reach system.img on SD card.
Can anyone help me? or point me in the right direction to get android installed on my xda orbit 2?
Thanks, James
Just try a earlier nbh i use polaimg-panel3-320-29-03-10.nbh most of the later ones have either problems with sound or wifi.
If you get a white screen it's prob wrong panel depends on you phone pola100 or 200.
Thanks, But I have tried that.
I have a new problem now. Might be easier to solve.
can't anyone help? kinda in a rush for it.
Hi,
i had the same problem with another build.
You should try to get into the installation menu and install Android.
This helped for me.
I found the solution here on xda-developer.
Since I am too new or too stupid to post a link the post seems to be this one:
showpost.php?p=5602064
Have fun,
René
Hello,
I am posting in this forum for a few reasons.
First of all, I rooted my phone the day I bought it and took it home. I originally rooted it with a simple one-click method from a webpage I randomly found online.
Unfortunately, I do not remember the name of the hack, and I'm beginning to think that it has permanently affected the boot for my phone. After installing the hack, I found the CynoagenMod (or however it is spelled) custom ROM. I took some time into researching more about custom ROMs and installing with advanced settings, etc.
After I did my research, I found it best to flash with the new ROM and have had trouble with my boot since.
I did everything step by step from the website, and ran everything to the best of my abilities. The problem I am having now is that I can not access the HBoot menu.
In fact, every time I restart or shut off my phone, the screen goes black and will not respond to me holding down the recovery mode buttons. It stays pitch black and even battery resetting does nothing.
It will randomly turn on, vibrating for about a minute or two straight with the HTC splash screen, and then boot into my phone with the current ROM.
It seems strange that this is going on, and I have been searching all over the internet for weeks now trying to figure out what's wrong. I have reinstalled the stock RUU for my Inspire multiple times to no avail. It still sits at a black screen and will randomly boot into the splash whenever it deems to do so.
Is there anyone with any suggestions or advanced technical knowledge that could lead me to a solution? It is most unfortunate because I can't access for viewing s-on, s-off. I'm really debating whether to take the phone back to the rep and replace it. I'm just afraid they will discover the security off and tell me to suck a ****.
Thanks.
Run this nice little tool to factory reset, s-on your device
http://forum.xda-developers.com/showthread.php?t=1208507
Then reroot with the Hack Kit here. Read the "effen manual"
http://forum.xda-developers.com/showthread.php?t=952352
Thanks for the reply.
But here's my problem:
I can't access the HBoot menu in order to flash or install any type of file.
I've been using the terminal on my Mac to do most of my editing, and now I've ran in to a new problem: whenever I try to move files to my sd root, it says that the card is read only and therefore no files can be transferred to it.
I use the command ./adb push PD98IMG.zip /sdcard/
This is where I get the error.
Also, it takes my phone literally 5 or 6 minutes to boot into the splash screen after I use the command ./adb reboot bootloader/recovery (both of which I have tried).
I'm beginning to get quite frustrated, as I'm sure you can understand. I've also attempted to rewrite all of the necessary root programs onto the device in hope that the bootloader and recovery options will be accessible.
Do you have a solution for the write problem I am getting from my device?
Thanks.
Also, is there a way to go about doing this procedure straight from the Terminal since I can't run HBoot and recovery directly from my phone?
I have sucessfully restored s-on on my previous inspire so I can rma it for a signal issue I was having.
So I consider myself savy enough on this task. I rooted that inspire using a method available on here and not some random site. Doing that, u accept the possiblility that you may not get support on xda for using a root method that was not posted here. However, I do remember reading somewhere on here that certain inspires will go to a black screen at somewhere during the rooting process. My advice is to search the inspire threads for this topic, using keywords black screen, and see if this can provide a solution for you.
Sent from my HTC Inspire 4G using XDA App
Thanks soldier, but I've already searched through every black screen forum topic on this site for the inspire, all of which require reboot to HBoot, which I can not access from my phone without terminal access.
It seems like my phone is permanently soft bricked or something, or maybe the key commands don't do as they are supposed to. I can never get into the HBoot menu or recovery by holding down vol. - and the power button.
All it does is boots into the splash screen after about five minutes or son, and once the splash screen comes up, the phone vibrates for about 2 minutes straight.
During this time, my phone is not recognized by adp until after the phone stops vibrating.
I can't seem to find any forums ANYWHERE that propose a solution to this problem, let alone anyone that has the same issue as me.
Yeah that sux man. Well I would say, if you are within your warranty exchange, I would go that route first. Worst thing they can say is no. Although I still have yet to find a story about how someone was denied a warranty exchange for a phone that does not have physical damage. The next route is to suck it up and pay the deductible if you have insurance on it. (I always recommend insurance on any modern touchscreen smartphone) If that is not an option, then start saving up for a new phone, and lesson learned.
Ya, that seems like the only available option at the moment since my phone can't access HBoot even though I rewrote the root files to the device.
I just bought the phone this weekend, so I'm thinking of hard bricking the phone in case they decide to do an on-the-spot check. Hopefully they'll believe some bull**** story I can come up with and just give me a replacement.
Would any of you still recommend rooting again with a new phone? And what would be the best way to do so without the consequence of a soft or hard brick?
I'm just thinking of rooting and keeping the original stock OS on the device instead of running a custom ROM. That's what seems to have effed my phone.
All I really wanted to do was cut all the crappy useless programs and services out of the original Google Apps package with a fresh install to get the most out of my hardware.
FYI...if you haven't figured it by now, xda is the BEST site there is for android hacking/modding. This website IS the centralized location for all android developers/modders. Sure there are plenty of other android community sites out there, but this is the direct centralized source for all android hacking/modding.
My suggestion is to go ahead and root the next inspire you get using the hack kit in the development section. That is a long time proven and supported rooting method for the inspire. As far as roms go, from what you are saying, i would recommend you install a custom rom that is based on stock. (ex. Android Revolution) It was not the custom rom that effed up your phone, it was the questionable rooting method that did. Custom roms, by default, are superior to true stock roms, because they are modded, tweaked, and optimized far beyond the stock rom.
Awesome, I appreciate the information.
I'll keep that in mind. So which exact ROM would you suggest for my Inspire that's completely like Gingerbread?
I wasn't too fond of the CyanogenMod ROM because the GUI was a little sketchy. I like having a professional looking GUI, and I love the Gingerbread screens and menus.
Oh, one more thing. I had some success a little while ago getting into the HBoot menu from the terminal. Now I'm having a new issue:
I get into the menu at which the phone freezes and I can not use the arrow keys or power button to make a selection. Any tips?
I also believe that it is in fastboot, since it says fastboot at the top and has the Androids on the bottom skateboarding. Is this an issue? And am I screwed because I can't access the OS to turn the option off?
When you see the fastboot at the top of the screen and the androids skating at the bottom, that is perfectly normal. That is the pre screen before actually going into the bootloader. If your keys work, u press the volume down button to select which option you want, which will highlight in blue. The first option is the bootloader, so if you press the power button, it will load into the bootloader. The bootloader looks exactly the same as this screen, but with different options. This screen will show hboot at the top and have the options of fastboot, recovery, factory reset, simlock, and image crc. I have never heard of the keys not working at this point, so i couldn't help you there. Search around the forums if you haven't already.
If you want to compare this to something more familiar, think of these two screens as your motherboard bios to your PC. (What you see when your pc boots up, before it loads the OS, windows, mac, etc) On a pc, you can install any OS you want, like on the inspire, you can install any custom rom you want. But the motherboard bios is the highest level of permanent software that is directly written to the motherboard itself, like the bootloader/hboot is on the inspire. When rooting, you are essentially altering the motherboard bios on the inspire. When you install a custom rom, you are just installing an OS on the inspire.
There are plenty of custom ROMS that are based off of stock in the development section. I use and like Android Revolution. But when choosing custom roms, its always a matter of preference, and what works best for you.
digitalism said:
Thanks for the reply.
But here's my problem:
I can't access the HBoot menu in order to flash or install any type of file.
I've been using the terminal on my Mac to do most of my editing, and now I've ran in to a new problem: whenever I try to move files to my sd root, it says that the card is read only and therefore no files can be transferred to it.
I use the command ./adb push PD98IMG.zip /sdcard/
This is where I get the error.
Also, it takes my phone literally 5 or 6 minutes to boot into the splash screen after I use the command ./adb reboot bootloader/recovery (both of which I have tried).
I'm beginning to get quite frustrated, as I'm sure you can understand. I've also attempted to rewrite all of the necessary root programs onto the device in hope that the bootloader and recovery options will be accessible.
Do you have a solution for the write problem I am getting from my device?
Thanks.
Click to expand...
Click to collapse
It sounds like you may have the bad combination of a newer Inspire and the older ENG hboot. This is a problem dealt with commonly on the Aria/Inspire IRC channel. If you want to jump in, we can probably get you straightened out.
http://webchat.freenode.net/?channels=#liberatedAria
Awesome.
I am a little upset that I can't choose an action from the boot menu with the keys on the phone.
It also seems that the only way I can completely get into the boot menu is through the terminal after which I run ./fastboot-mac
After I put in this action, the menu will begin looking for the PD98IMG.zip file, and only goes on to say that there is no file, when there actually is one.
I just wish I could do all of this straight from the phone since I'm not well versed on terminal and commands for running programs to their full ability.
I wish I could figure out a way to the write permission on my sdcard so I could reinstall the .zip file for the bootloader to find.
digitalism said:
Awesome.
I am a little upset that I can't choose an action from the boot menu with the keys on the phone.
It also seems that the only way I can completely get into the boot menu is through the terminal after which I run ./fastboot-mac
After I put in this action, the menu will begin looking for the PD98IMG.zip file, and only goes on to say that there is no file, when there actually is one.
I just wish I could do all of this straight from the phone since I'm not well versed on terminal and commands for running programs to their full ability.
I wish I could figure out a way to the write permission on my sdcard so I could reinstall the .zip file for the bootloader to find.
Click to expand...
Click to collapse
You will not be able to use the volume rocker to select options if you have a PD98IMG.zip on your SD card.
Try booting into hboot with the SD card removed. That should let you move around the menu.
Sent from my Inspire 4G using the power of the dark side
Thanks for the heads up!
I can move the menus now.
Seems like all is going well now...
Just a matter of time.
digitalism said:
Thanks for the heads up!
I can move the menus now.
Seems like all is going well now...
Just a matter of time.
Click to expand...
Click to collapse
It's good to hear you're moving forward. Let us know how it comes out.
Sent from my Inspire 4G using the power of the dark side