Related
I finally got my "Alltel Bee" rooted last nite using super one click. Before I roll out any custom roms etc, I'd like to make sure I get a backup, and my phone is hanging on the alltel logo whenever I try to boot into recovery (whether I boot in from Rom manager or from Hboot.) I always end up pulling the battery and rebooting the phone.
I do have an idea as to how I got to this point, and I have only myself to blame, but in my frustration of trying to root this thing I did try this http://forum.xda-developers.com/showthread.php?t=743289 and recovery has hung like this ever since.
I've got root now, and have installed Rom manager, used that to flash clockwork recovery, yet I still have the issue. After a few google searches, I've seen some suggest that fixing file permissions can fix this, and I've done that as well with no change.
Where do I turn next?
So after some more searching and reading and such, I've discovered that even though I have root access, booting into HBOOT shows S-ON still. Could this be the issue in my inability to get a recovery written? Anyone know how to deal with it?
How do you know it is a hang in recovery? If you see the triangle and nothing happens, just click the power button once and usually you will land in the recovery mod menu.
I don't get the triangle at all. I get the initial Alltel logo and that's it. I've waited several minutes before pulling the battery before, but I don't get to the triangle or the menu.
Super one click will only do a temp root. There are no hard roots for the bee that i am aware of. DO NOT TRY UNREVOKED AS IT IS FOR THE BUZZ AND COULD YOUR BEE OR A FROYO BUZZ
Sent from my GT-P1000 using XDA App
Doh! Thanks, I guess I'll wait patiently. (My network switches from Alltel to AT&T inside of 2 months, at which time I'll be provided an Aria.)
Still, it would be nice to customize this thing a bit before it turns into an mp3 player
Send me a boot.img from the bee and I'll get you a recovery
Sent from my HTC Wildfire using XDA App
Even though i dont have the bee would yoi mind clarifiying jacob
Sent from my GT-P1000 using XDA App
If I get a boot image from a shipped rom, I can extract the kernel and build a recovery image
Sent from my HTC Wildfire using XDA App
I'm more than willing to help, How do I pull what you need?
I also have the SDK installed, I've been looking into writing some code for this new toy...
edit: I think I have what I need to get this pulled. Ill see if I can find some time for it this weekend.
willing to help
just starting out. complete noob
But if i can help in any way let me know. in the same boat as the original poster. our section of Alltel is being acquired by at&t and switching to the aria. but would love to help any way i can
Would love to get my "bee" rooted to play with it some more to get familiar with it all
Just got through doing a romdump. Which files do you want?
I am also having this issue... has anyone successully extracted a recovery image for the bee?
My DroidX always enters bootstrap recovery mode everytime i turn it on or reboot. Can anyone tell me why this is happening? I ever had the same issue and then flashing the SBF cleared the problem. But that's the time when I haven't injected the RUIM. Since I'm not on Verizon, i'm afraid that if I do that again my injected number will lost. Is there any solution for it?
superbay said:
My DroidX always enters bootstrap recovery mode everytime i turn it on or reboot. Can anyone tell me why this is happening? I ever had the same issue and then flashing the SBF cleared the problem. But that's the time when I haven't injected the RUIM. Since I'm not on Verizon, i'm afraid that if I do that again my injected number will lost. Is there any solution for it?
Click to expand...
Click to collapse
This is the benefit of.bootstrap, it hijacks the boot process. Consider it a blessing that may be a slight inconvenience until the one time.something happens and your.phone doesnt.boot, then it will.be your.saving grace.
Sent from my DROIDX using XDA App
SysAdmin-X said:
This is the benefit of.bootstrap, it hijacks the boot process. Consider it a blessing that may be a slight inconvenience until the one time.something happens and your.phone doesnt.boot, then it will.be your.saving grace.
Sent from my DROIDX using XDA App
Click to expand...
Click to collapse
Dude, are you kidding me? I don't want grace. I want the bootstrap recovery to appear only when i need it to appear.
So is this what happens when I flash the ROM that already has bootstrap recovery feature inside? Coz i'm using Liberty 1.5 right now. So you're telling all people using Liberty experience this?
superbay said:
Dude, are you kidding me? I don't want grace. I want the bootstrap recovery to appear only when i need it to appear.
So is this what happens when I flash the ROM that already has bootstrap recovery feature inside? Coz i'm using Liberty 1.5 right now. So you're telling all people using Liberty experience this?
Click to expand...
Click to collapse
I can't remember where but there's a checkbox that might be checked that starts your phone in bootstrap. Go through the liberty settings or it might even be in the toolbox...
Sent from my DROIDX using XDA App
bigshotrob22 said:
I can't remember where but there's a checkbox that might be checked that starts your phone in bootstrap. Go through the liberty settings or it might even be in the toolbox...
Sent from my DROIDX using XDA App
Click to expand...
Click to collapse
I think there's no any checkboxes in the toolbox. I'll try looking for it in the Liberty setting
From the home screen hit menu, settings, Liberty settings. Then unchecked the one that says to go into recovery everytime.
With the nature of the bootstrap it is better that it is booting to it. And you will think the same when something goes wrong and you can't load a recovery. Remember there is no way to boot into recovery by holding a key like other phones.
Got it, dude, and it still goes into recovery even though I have unchecked the option.
I wonder if the ROM got bugs because i got some FC in the Liberty setting even after I reflash the ROM and got the fresh Liberty toolbox from the Market. Damn this thing just start p#@*%g me off.
Easy fix. Someone helped me when mine was doing it. Get or go into an app called root explore. Open it up and go all the way to the bottom and click on system then bin then at the top of the screen click where it shows RW it then should show RO then scroll down and find "hijack" long press and delete then scroll down and find "bootloger" delete that then the next one is bootloger.bin long press it and rename it to just bootloger just get rid of .bin and your done. Just remember to use bootstrap to get back into recovery when you need to.
Sent from my DROIDX using XDA App
spacecasespiff said:
Easy fix. Someone helped me when mine was doing it. Get or go into an app called root explore. Open it up and go all the way to the bottom and click on system then bin then at the top of the screen click where it shows RW it then should show RO then scroll down and find "hijack" long press and delete then scroll down and find "bootloger" delete that then the next one is bootloger.bin long press it and rename it to just bootloger just get rid of .bin and your done. Just remember to use bootstrap to get back into recovery when you need to.
Sent from my DROIDX using XDA App
Click to expand...
Click to collapse
Dont follow this, this makes bootstrap not work ever..... Careful with ur recommendations spiff, he doesnt want to completely remove bootstrap
Sent from my DROIDX using XDA App
Why are you even rebooting your phone enough for this to bug you? I reboot my once probobly once every three days just for fun, i dont experience any slowdowns or anything its just me deciding why not.. You make it sound like you reboot your phone voluntarily every hour or something for no reason
Secondly yes, bootstrap on reboot is a blessing not a curse... What happens if you start liberty up and you get a CONSTANT force close that does not go away and keeps coming up no matter how many times you click close?? Your phone will be INOP and you wont be able to do ANYTHING or even get to the manual bootstrap menu.. therefore having to SBF.. WAY better to have an available bootstrap whenever you need it automatically
I've done this about three times and never had a problem I got this information from someone that I trust and knows more about this stuff then I will ever know. Its not hurting anything. I can still get back into recovery through bootstrapper every time with no problems. I wouldn't post this if it would mess up anyones phone. After you do this you need to use bootstrapper to get back into recovery but you can
Someone helped me with a problem and im just trying to pass on what I've learned. Just to make sure it doesn't hurt anything I just did it to my phone and used bootstraper to flash apex on my phone with no issue.
Sent from my DROIDX using XDA App
spacecasespiff said:
I've done this about three times and never had a problem I got this information from someone that I trust and knows more about this stuff then I will ever know. Its not hurting anything. I can still get back into recovery through bootstrapper every time with no problems. I wouldn't post this if it would mess up anyones phone. After you do this you need to use bootstrapper to get back into recovery but you can
Someone helped me with a problem and im just trying to pass on what I've learned. Just to make sure it doesn't hurt anything I just did it to my phone and used bootstraper to flash apex on my phone with no issue.
Sent from my DROIDX using XDA App
Click to expand...
Click to collapse
So what happens when you screw something up and get bootloops? Difficult to access bootstrapper when you can't get past the boot animation or even boot logo.
The point of it starting first is in the event of said bootloops you can get into clockwork and restore. From what I understand if you turn off your phone you wait about 30 or so seconds and when you turn on your phone it will skip clockwork, it only pops up when you do a battery pull or if you shut down and power back on right away.
Why are you turning your phone on so much for it to be a pain? I reboot my phone every 2 or 3 days and it doesn't bother me one bit. If you're complaining against measures that are there for your benefit then I don't know what to say... Deal with it.
It works for me. I've had boot loops and have always been able to get in recovery. So is he just supposed live with it. I do turn my phone off ever night I like to give my phone some time off and by doing that I've never had to replace a battery. We all do things differently. He can do what I've showed him or not its up to him.
Sent from my DROIDX using XDA App
SysAdmin-X said:
Dont follow this, this makes bootstrap not work ever..... Careful with ur recommendations spiff, he doesnt want to completely remove bootstrap
Sent from my DROIDX using XDA App
Click to expand...
Click to collapse
Really? You mean never ever? Even though i already have Bootstrapper app?
Joe92T said:
Why are you even rebooting your phone enough for this to bug you? I reboot my once probobly once every three days just for fun, i dont experience any slowdowns or anything its just me deciding why not.. You make it sound like you reboot your phone voluntarily every hour or something for no reason
Secondly yes, bootstrap on reboot is a blessing not a curse... What happens if you start liberty up and you get a CONSTANT force close that does not go away and keeps coming up no matter how many times you click close?? Your phone will be INOP and you wont be able to do ANYTHING or even get to the manual bootstrap menu.. therefore having to SBF.. WAY better to have an available bootstrap whenever you need it automatically
Click to expand...
Click to collapse
spacecasespiff said:
It works for me. I've had boot loops and have always been able to get in recovery. So is he just supposed live with it. I do turn my phone off ever night I like to give my phone some time off and by doing that I've never had to replace a battery. We all do things differently. He can do what I've showed him or not its up to him.
Sent from my DROIDX using XDA App
Click to expand...
Click to collapse
Easy, boys. I appreciate the replies. The reason is I just dont like having to meet bootstrap option everytime i turn on the phone or reboot it. I never have bootloop even until now with this DX, even if I do, it's me who have to deal with it. So you see? The why-question is all about me. No offense but lets just stick to the how-question.
@spacecasespiff
So how do you go to bootstrap if you have bootloop?
I've had two bootloops the first was when my phone was doing what yours is doing do I did a batt pull and the recovery screen came up so all was good. The second tine was with liberty and that one a batt pull did nothing so I went to the forums and found out about holding the power button and the home button down and it put you on a different screen sorry I can't remember what was on that screen. You then use the search button to navigate the screen. I can't remember what I had to choose but I think it brought me back to the recovery screen. Its been awhile since that happend so I could be wrong. Just search the forums for it. Obviouse if you have a bootloop you can't get into bootstrapper. But if you can use what I learned about the power and home button you can get things back.
Sent from my DROIDX using XDA App
I
spacecasespiff said:
I've had two bootloops the first was when my phone was doing what yours is doing do I did a batt pull and the recovery screen came up so all was good. The second tine was with liberty and that one a batt pull did nothing so I went to the forums and found out about holding the power button and the home button down and it put you on a different screen sorry I can't remember what was on that screen. You then use the search button to navigate the screen. I can't remember what I had to choose but I think it brought me back to the recovery screen. Its been awhile since that happend so I could be wrong. Just search the forums for it. Obviouse if you have a bootloop you can't get into bootstrapper. But if you can use what I learned about the power and home button you can get things back.
Sent from my DROIDX using XDA App
Click to expand...
Click to collapse
Booting up the phone while holding the home and power button boots you into moto's stock recovery. Did u wind up doing a wipe data/factory reset perhaps?
Sent from my DROIDX using XDA App
Oh i see. I bet you just got to the DroidX original recovery then wipe it.
Well that's not so bad if you have bootloop eh?
So i guess have two choices here, using some ROM that doesn't have built in bootstrap recovery inside or applying the tutorial above to avoid the problem i have.
Problem solved then. Thanks everybody
I rooted my nook, downloaded rom manager, flashed cwm and did a nandroid back up. Now I'm stuck on the cwm revovery and cant reboot, volume rockers wont do anything, home button wont do anything or power button. Its just stuck on the black and orange recovery and wont reboot or anything. On my evo 4g I would do a battery pull and go back in to revovery but I can't do that with the nook. Any suggestions? Please!!! My wife will hang me alive. Thanks in advance.
Dave
Well I got it to power down...... now I can't get it to power back up?????
OK now everytime I hit rebbot system it goes right back to recovery. Can I just download a rom and flash it? That makes most sense to me.... and I want to go cm7 but dont understand this whole dual boot feature on the nook
check this out, it may help.
http://forum.xda-developers.com/showthread.php?t=949699
Thanks dude. Im in a pickle. I can't get out of recovery with my sd in. Quite a bit different from my evo 4g. I have some reading up to do.
Sent from my PC36100 using XDA Premium App
yeah, the nice thing about the nook is that it's (knock on wood) pretty much unbrickable... just flash an image onto your sdcard and boot it from there (it tries to read the sdcard first from my understanding) to fix issues...
Ohhh. That's awesome news because I have a brick right now. I've gotten into some sticky situations with my evo but always pulled out smelling like roses. I just don't know the Nook at all right now. Ill have cm7 on it by tonight. Im pretty stubborn. Lol
Sent from my PC36100 using XDA Premium App
So here is what happened. I made a backup of a stock atrix firmware and copied the backup to my atrix on deodexed 2.3.4. I tried to install the backup but it stops somewhere along the line and says error formatting data.
now the phone wont connect to the computer. when i opened rsdlite however it shows that the device is connected.the phone bootloops and I cant copy anything to the phone cause i cant connect to the phone except through rsd sorry if i posted in the wrong section cause this is the only one i can post in. and i searched for solutions but no one has this same problem. PLEASE HELP
then if you CAN use rsd lite place phone in rds lite mode then use "stock sdk from motorola and flash it back i went all the way ro 1.26 then over rhe air updated to 1.83
but i also continued on to unlocked bootloader and flashed gigerbread build (alien ) after installing cwm
im also on usa at&t fyi
ltdanno360 said:
then if you CAN use rsd lite place phone in rds lite mode then use "stock sdk from motorola and flash it back i went all the way ro 1.26 then over rhe air updated to 1.83
but i also continued on to unlocked bootloader and flashed gigerbread build (alien ) after installing cwm
im also on usa at&t fyi
Click to expand...
Click to collapse
I tried to flash the official 2.3.4 found here http://forum.xda-developers.com/showthread.php?t=1181932 but now i just have a locked bl. and it still bootloops. Can you give me little more detailed instructions on what you did. I'm not too experienced.
Morpheaous said:
I tried to flash the official 2.3.4 found here http://forum.xda-developers.com/showthread.php?t=1181932 but now i just have a locked bl. and it still bootloops. Can you give me little more detailed instructions on what you did. I'm not too experienced.
Click to expand...
Click to collapse
Did u do factory reset after the flash
Sent from my MB860 using xda premium
My atrix wont even boot to the RSD etc selection screen
So i had my phone rooted and wanted to unlock the bootloader so i followed the steps from pudding but it did not work. everyone has a NS version of the phone in RSD Lite but mine was SE not sure why. So i tried a few times to flash the new image and clear everything out to no avail. now i don't even get to the menu that gives me 5 seconds to select what method i want to use to fix it.
all i get is a flash of this on the screen before it goes black again
SVF:105:1:2
Failed to boot 0x1000
(stays for a second)
Entering NWFlash Recovery Mode
(Flashes under the other text but really fast before the screen goes blank)
windows wont even recognize that its plugged in. but what else is odd is that while plugged in it seems to be charging as the green notification light stays on.
any help would be great. thank you
voidlogik said:
Failed to boot 0x1000
Click to expand...
Click to collapse
isnt that a hard brick? it's over.
sanriver12 said:
isnt that a hard brick? it's over.
Click to expand...
Click to collapse
really?? no way to unbrick it?
Morpheaous said:
I tried to flash the official 2.3.4 found here http://forum.xda-developers.com/showthread.php?t=1181932 but now i just have a locked bl. and it still bootloops. Can you give me little more detailed instructions on what you did. I'm not too experienced.
Click to expand...
Click to collapse
Bootloops means soft bricks which is not really a problem. When your phone Boots up, press the down key along worth the power button. Then keep pressing down button until you see Android Recovery. Do a factory reset or flash another room once in there.
Sent from my MB860 using XDA App
voidlogik said:
really?? no way to unbrick it?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1165154
voidlogik said:
really?? no way to unbrick it?
Click to expand...
Click to collapse
Sounds like a hard brick indeed. At this moment in time hard bricks are incurable but some people said that taking their battery out and putting it back into their phones solved their problem. You might want to give it a shot.
A guy also claimed thay its possible to unhardbrick your phone using the jtag technique. You might want to read up on it.
Sent from my MB860 using XDA App
aIf it says failed to boot x1 its real bad but i got a failed to boot x2 and got it fixed but x1 tragic
Sent from my MB860 using xda premium
ltdanno360 said:
aIf it says failed to boot x1 its real bad but i got a failed to boot x2 and got it fixed but x1 tragic
Sent from my MB860 using xda premium
Click to expand...
Click to collapse
English plz.
Sent from my MB860 using Tapatalk
me too
There's soo many forums and different avenues to go down! after about 9 hours trying various things to make my atrix (running normal 2.3.4 rooted with no other cm7 or rom or any other mod) i am left with my atrix at the boot screen OR if i leave it to boot it just makes the logging on noises then shows the white screen, then nothing.
I stupidly followed the list to freeze using bloatfreezer. Not the updated list where it reads next to HOME (make sure you have another launcher) so i have frozen 'home' and i am stuck.
i cannot do a recovery because it has that fail message x2 everytime i do the power volume - and + on the android recov.
I am completely lost. i do not understand what hard/soft/adw/ push email/ or other jargon means. If you have any solutions i'd be more than grateful.
I hope i haven't bricked my phone, cos a 2year contract and no new phone is gonna push me near that ledge lol
atrixuk said:
There's soo many forums and different avenues to go down! after about 9 hours trying various things to make my atrix (running normal 2.3.4 rooted with no other cm7 or rom or any other mod) i am left with my atrix at the boot screen OR if i leave it to boot it just makes the logging on noises then shows the white screen, then nothing.
I stupidly followed the list to freeze using bloatfreezer. Not the updated list where it reads next to HOME (make sure you have another launcher) so i have frozen 'home' and i am stuck.
i cannot do a recovery because it has that fail message x2 everytime i do the power volume - and + on the android recov.
I am completely lost. i do not understand what hard/soft/adw/ push email/ or other jargon means. If you have any solutions i'd be more than grateful.
I hope i haven't bricked my phone, cos a 2year contract and no new phone is gonna push me near that ledge lol
Click to expand...
Click to collapse
I'd recommend starting a new thread w/ your issue. It's more likely to be seen and answered by someone who could help.
atrixuk said:
There's soo many forums and different avenues to go down! after about 9 hours trying various things to make my atrix (running normal 2.3.4 rooted with no other cm7 or rom or any other mod) i am left with my atrix at the boot screen OR if i leave it to boot it just makes the logging on noises then shows the white screen, then nothing.
I stupidly followed the list to freeze using bloatfreezer. Not the updated list where it reads next to HOME (make sure you have another launcher) so i have frozen 'home' and i am stuck.
i cannot do a recovery because it has that fail message x2 everytime i do the power volume - and + on the android recov.
I am completely lost. i do not understand what hard/soft/adw/ push email/ or other jargon means. If you have any solutions i'd be more than grateful.
I hope i haven't bricked my phone, cos a 2year contract and no new phone is gonna push me near that ledge lol
Click to expand...
Click to collapse
If you're on AT&T - get RSD lite and find the proper sbf file and flash it. If you were using Gingerbread, make SURE you have a GINGERBREAD sbf file - or else you'll permanently brick your phone. If you're on Bell - you'll need the appropriate file for Bell to flash, same rules apply - If your on gingerbread, make SURE its a gingerbread file you're flashing.
atrixuk said:
There's soo many forums and different avenues to go down! after about 9 hours trying various things to make my atrix (running normal 2.3.4 rooted with no other cm7 or rom or any other mod) i am left with my atrix at the boot screen OR if i leave it to boot it just makes the logging on noises then shows the white screen, then nothing.
I stupidly followed the list to freeze using bloatfreezer. Not the updated list where it reads next to HOME (make sure you have another launcher) so i have frozen 'home' and i am stuck.
i cannot do a recovery because it has that fail message x2 everytime i do the power volume - and + on the android recov.
I am completely lost. i do not understand what hard/soft/adw/ push email/ or other jargon means. If you have any solutions i'd be more than grateful.
I hope i haven't bricked my phone, cos a 2year contract and no new phone is gonna push me near that ledge lol
Click to expand...
Click to collapse
you need to have an unlocked bootloader to flash Any custom rom PM me ill show ya how its not too hard
a pc a atrix and a few files and you will
be up n running in no time at all
Sent from my MB860 using Tapatalk
I wanna ask a question. Earlier, I used 4ext Recovery Control (the app,not actual recovery) , but i was changing the recovery theme. Anyway I chose 'reboot into recovery' to check out how the theme looked, and my phone went black and vibrated 3 times, and the orange light blinked continuously. I took out the battery and put it back in and pressed power, and same thing..black, vibrate x3, blinking light. So i took out battery again, waited bout 5 minutes, put it back and pressed vol dwn + power and it booted into hboot menu, where i entered recovery and selected reboot and it powered up normally, thank goodness! But my question is, is that a sign of something bad that i should be aware of in the future? I do have the bad chip, and i thought it was a goner! Has anybody else experienced this? Im kinda scared to be messin around now.. just wondering if y'all have seen this before.
Sent from my Black Ice'd Glacier using xda premium
Your phone will do that if the volume up is held during boot. Maybe the button took a dump.
estallings15 said:
Your phone will do that if the volume up is held during boot. Maybe the button took a dump.
Click to expand...
Click to collapse
Thanks...I was holding it and maybe i did press it by mistake. Its been fine since so no worries ...
Sent from my Black Ice'd Glacier using xda premium
jjbadd385 said:
Thanks...I was holding it and maybe i did press it by mistake. Its been fine since so no worries ...
Sent from my Black Ice'd Glacier using xda premium
Click to expand...
Click to collapse
Nothing like an easy fix!
Yea i had just reversed the Htcdev unlocked bootloader, a few days ago. I was happy I had my phone True rooted, s-off, eng. Hboot..and that happened! I damn near had a panic attack!
Sent from my Black Ice'd Glacier using xda premium
I also had the three fast vibrations and blinking orange led. I downgraded from Gingerbread to stock Froyo, rooted using Visionary and gfree. I then changed the engineering bootloader to 0.85.2007. I got into hboot, and verified I was S-off with that bootloader. I installed Clockwork mod recovery, and was able to create a recovery image. But, when I tried to make a backup of the rom, I got a black screen, When I tried to flash a rom I just got the orange symbol. I tried to reboot, and that’s when I first got the vibrations and orange light. I was able to restart with a battery pull, So I thought there was something wrong with my clockwork mod recovery. I reinstalled it again with the same results. I followed advice I saw in another post and pushed volume down and power and waited for the bootloader. I still had the original stock rom on there. It recognized it after a few tries, and updated. When it said reboot by pushing the power button, I got the vibrations and orange light again. It erased everything I had put on there. I wanted to see if I still had S-off, so I went to the bootloader, and I still have S-off, but the bootloader changed back to to 0.86.0000. When I tried to reboot via the power button this time, I was still getting the vibrations and orange light, and could not get it to restart. I let it charge for a while, and then pulled the sdcard in and out, along with the battery pull, and got it to restart.
I’m still new at this, so I’m not sure what I should do next. Should I try another sdcard with the stock rom? Should I try to reinstall Visionary first?
Any help will be greatly appreciated. I really don’t want to stay on Froyo .
I think u should be ok to flash another rom. I was told it can be a result of holding volume up + power. Do you know if you might have did that by accident? Also, have you had any problems with your volume buttons sticking or anything? Since i had the problem, i have flashed several times, so maybe for me it was an isolated incident. I dont want u to blame me for anything, but my opinion is you should be ok to flash a rom, just be careful not to press the vol button while rebooting.
Sent from my HTC Glacier using xda premium
Thanks for the response. Should I try to run gfree again? Will it hurt anything? Even though the bootloader said S-off, when I run terminal emulator, and type in su, it says permission denied. Also I can't find gfree in the data/local folder I pushed with adb yesterday. Could this be the reason my 0.85.2007 bootloader didn't stick? I'm wondering if I should try another sdcard.
Thanks,
Erin
EMcTx said:
Thanks for the response. Should I try to run gfree again? Will it hurt anything? Even though the bootloader said S-off, when I run terminal emulator, and type in su, it says permission denied. Also I can't find gfree in the data/local folder I pushed with adb yesterday. Could this be the reason my 0.85.2007 bootloader didn't stick? I'm wondering if I should try another sdcard.
Thanks,
Erin
Click to expand...
Click to collapse
Now when you ask me if it will hurt anything, I am still quite new myself, and I dont want to tell you anything that would cause you to brick your phone. Do you know what emmc chip you have? Its been stated that some chips are more likely to mess up than others. If I could tell you anything, it would be to read what others have done, read the guides til you understand more..because there is no way to be sure that you won't brick your device. I have 2 mt4g so i took more chances than i should have. but go to the Ultimate Rooting, s-off guide in the wiki section, if you are choosing to continue. Im sorry i cant be of more help but i am only slightly ahead of you on this journey of learning ...
Sent from my HTC Glacier using xda premium
Before I did anything to the phone, I verified the emmc chip, it is the "good one".
This is actually my second phone. I bricked my first one in November, and it had the "bad" chip. I didn't know about that problem until I had rooted it already. I was waiting for the ICS roms to get going before I did anything. That's why I've waited so long. I ran gfree verify through adb but got su: permission denied. It seems that the gfree didn't take, although I do have the backups gfree created.
I may try to see if I can undo them in a couple of days. I need a break from the stress it creates .
Thanks again for your input.
I know what ya mean about the stress it causes...I wanted to stop, then i would lay there and think..I can do this! Then i would stop..then start again! But what really helped me more than anything, was just reading posts by other users, about similar issues. It helped me get a better grasp of what I was doing. But whatever u decide, good luck.. I think you will get it, provided you remain patient. If ya have anymore questions just ask here and if I can help I will...
Sent from my HTC Glacier using xda premium
My phone still vibrates 3 times and flashes the orange light everytime I reboot. The only way to get it restarted is to do a battery pull and wait 5 minutes. I tried to flash the stock rom again through hboot. This time I used a different freshly reformatted sd card. I just don't know what to try next. Does anyone have any other ideas?
Thanks,
Erin
I finally got it to boot normally! I unrooted my phone to get s-on again. It may have had something to with gfree. I'm going to try to root it again.
EMcTx said:
I finally got it to boot normally! I unrooted my phone to get s-on again. It may have had something to with gfree. I'm going to try to root it again.
Click to expand...
Click to collapse
Very good, I have been following ur progress, so post back your results ..
Sent from my HTC Glacier using xda premium
It's definitely the gfree. I tried it two other times, with the same results. I was able to use the gfree method on my other phone, it just had the bad chip, so it died a few days later. I'm going to have to try another way to root the phone.
okay, I used the VISIONary method to root, and I now have S-off. No more vibrations and blinking lights.