Related
okay i really need some help.
ive tried all the steps to recover my phone.
i get to the g1 screen when i power it up.
i can still get in to recovery menu.
ive tried to do a wipe.
please i need help.
ive also tried reinstalling rc29 with the original spl
but my radio is still 2_22_19_26I
PLEASE I NEED HELP!
or if there is a way that i can make it look like i never touched it then im still able to return it
so anything would help. links also
if you put the DREAIMG.nbh on your phone via bootloader it will reset the radio and spl to stock and everything else will be stock so that you can return the phone as though you never did anything to it
sweet. i guess i cant fix my phone. good thing i only got it 3 days ago.
whats a good thing to tell them when returning my phone?
G-Fetus6 said:
sweet. i guess i cant fix my phone. good thing i only got it 3 days ago.
whats a good thing to tell them when returning my phone?
Click to expand...
Click to collapse
if your phone is not messed up then there is no reason to return it. if you keep it at stock rc29 then it will update to 1.5 firmware within 72 hours supposedly or if you still want root follow these steps in this thread. this is the probably the most reliable way to root your phone, and since it is not as automated as some of the other threads, you might learn some things about your phone in the process http://forum.xda-developers.com/showthread.php?t=442480
david1171 said:
if your phone is not messed up then there is no reason to return it. if you keep it at stock rc29 then it will update to 1.5 firmware within 72 hours supposedly or if you still want root follow these steps in this thread. this is the probably the most reliable way to root your phone, and since it is not as automated as some of the other threads, you might learn some things about your phone in the process http://forum.xda-developers.com/showthread.php?t=442480
Click to expand...
Click to collapse
well the thing is im stuck at the G1 boot screen.
and cant get it to do anything after that.
so i might as well save me time and just return it tomorrow
G-Fetus6 said:
well the thing is im stuck at the G1 boot screen.
and cant get it to do anything after that.
so i might as well save me time and just return it tomorrow
Click to expand...
Click to collapse
do you have a modified recovery image on the phone or were you able to get that far. if not just take it by where you got it and tell them you got an ota update then wouldn't boot up past the g1 screen
david1171 said:
do you have a modified recovery image on the phone or were you able to get that far. if not just take it by where you got it and tell them you got an ota update then wouldn't boot up past the g1 screen
Click to expand...
Click to collapse
i got that it back to looking stock. so that is better if they try to do a hard reset for me.
yeah ill just tell them that an ota did it. cuz the phone is only 3 days old so im sure theyll say "oh yeah it must of been cupcake"
thanks
I am fairly new to rooting, but thanks to this great website and all your inputs I have learned so much over the past month.
I first rooted my G1 using the 1-click method which was great, but now my earpiece has blown I will be receiving a new handset next week. So I learned how to properly downgrade and install stock firmware for my old handset.
When I receive my new handset, I decided to take the plunge and root the traditional way for 2 reasons.. 1- to learn a different way and 2- its possible the security hole may be patched by then rendering the 1-click useless.
Anyway, after reading all the varying posts on how to downgrade/root/flash custom rom I am still left with a little confusion so hopefully someone can clear this up for me.
When actually rooting, I have seen methods to type various things in the telnet window, and another method to just rerun the .apk and select "protect root". What is the difference between these two methods? Do they both accomplish the same task of making a permanent root? One method actually said to download the JFreke rom to fix permissions to root, bo no other method mentioned that. Is that even necessary?
Also, I know that with Cyanogen Roms I do not really need to flash to "hard spl" if I decide to stay with cm roms, and cm recovery also allows the use of nandroid backup as well. The only other argument I have seen is that a hard spl would potentially allow someone to "unbrick" a bricked phone, but from everything I have read, most people have bricked trying to flash the hard spl.
If I am going to stay with cm roms, is there any real benefit to a hard spl other than increasing the brick chance? If I do upgrade the spl, am I correct that it would be done last, after a potential radio update (assuming my replacement handset does not come with the latest radio)?
Sorry for all the questions, and thanks in advance for your help.
This is the best guide I found.
I have done 4 phones using this method with only 2 minor differences.
1) I format the sd card using a microsd card reader instead of the phone.
2) when it says What To Do Now That You Have Root don't download any of the builds listed there, just download the latest cyan stable rom.
This is the guide hehe forgot to link
http://forum.xda-developers.com/showthread.php?t=442480
Oh and don't worry about swap or apps2sd partitions until after you root and verify that the rom is working with no problems, this will limit the number of variables in case you have troubles.
Thanks for the input.
So do you install hard spl according to that guide or do you skip that and just install the cm rom?
I love the auto apps2sd of cm roms. My phone is currently back on stock cupcake and I miss having all my apps on my 500mb ext 3 partition!
yea you need HardSPL. and use the recovery linked in the guide. Install cyan's recovery later.
This to me is the easiest step by step visual rooting process have done 3 G1 with full success. The newest G1 I had would not let me do the 1 click rooting method.
http://www.youtube.com/watch?v=xOo2V9qCauc&feature=related
maybeoneday said:
This to me is the easiest step by step visual rooting process have done 3 G1 with full success. The newest G1 I had would not let me do the 1 click rooting method.
http://www.youtube.com/watch?v=xOo2V9qCauc&feature=related
Click to expand...
Click to collapse
Yeah I figured the new handset would most likely be patched. What was the result when you tried the 1-click. Would the new phone just not let you install the 1-click apk?
One thing I might add is you can't brick your phone by flashing Hardspl. It's the "danger" spl that has the potential of bricking your phone. Just follow the traditional guide that fingerlickin provided and your good to go.
Thanks for the help!
Anytime.......
Nope sure wouldn't just kept telling me install aborted. I don't no why. It could be some kind of patch. But I went to old faithfull step by step you tube install. Its really a nice video. You can pause the video and root your phone right along with guy doing the video. he also gives you links on the side bar to all files needed in the rooting process.
oh I'm sorry, I actually have one more question.
After flashing the HardSPl, would there ever be a reason to revert back to the original g1 spl? For instance if I had to send a phone back to t-mo, would they know that I am using the hardspl if all I did was reload the dreaimg.rbh rc-29 downgrade, or does that also reflash the spl back to the original?
Yes you would want to unroot phone before sending it to Tmobile, they do not warrenty a rooted phone
Unrooting
http://forum.xda-developers.com/showthread.php?t=491350
dcorrea said:
oh I'm sorry, I actually have one more question.
After flashing the HardSPl, would there ever be a reason to revert back to the original g1 spl? For instance if I had to send a phone back to t-mo, would they know that I am using the hardspl if all I did was reload the dreaimg.rbh rc-29 downgrade, or does that also reflash the spl back to the original?
Click to expand...
Click to collapse
You shouldn't ever have to go back. T-mo would prolly never check it. Many people have sent there phones in with root access and different things installed. But if you do get paranoid and ever have to do it, just flash RC29 and it will put everything back to stock.
maybeoneday said:
Yes you would want to unroot phone before sending it to Tmobile, they do not warrenty a rooted phone
Unrooting
http://forum.xda-developers.com/showthread.php?t=491350
Click to expand...
Click to collapse
I turned my phone in with root access and custom splash screen and they didn't say anything. You don't want to make it known that you have done anything to it, but they won't check. When they are sent in they just hook it up with jtag and reflash everything.
supremeteam256 said:
You shouldn't ever have to go back. T-mo would prolly never check it. Many people have sent there phones in with root access and different things installed. But if you do get paranoid and ever have to do it, just flash RC29 and it will put everything back to stock.
Click to expand...
Click to collapse
Ok thanks that is what I figured. I actually just unrooted my phone yesterday from cyanogens rom, but I never flashed the SPL (did the 1-click thing originally), but now that I am going to do the original method I wanted to be sure.
I can't wait for my replacement phone to get here next week, because using the stock cupcake rom sux!
Anyway, thanks to everyone who gave their input and helped me learn even more about the process! You all rock!
supremeteam256 said:
I turned my phone in with root access and custom splash screen and they didn't say anything. You don't want to make it known that you have done anything to it, but they won't check. When they are sent in they just hook it up with jtag and reflash everything.
Click to expand...
Click to collapse
Really, thats music to my ears. I have often thought it would be a pain if something broke on the phone and I had to try to unroot it before I sent it in. uhhhh like a bricked phone
I work in an electronics repair company and I agree with supremeteam256 about sending your phone in rooted. Our techs don't check for tampering, they just plug it in and use the programs my department writes to test and reflash the devices. Of course our devices are much more complicated but the same NON-Communication between customer service and technicians still exist.
I think the biggest reason for this is because the techs just aren't interested in explaining the technical details to a customer service rep because all they ever get is "huh? wtf is a bootloader?"
Disclaimer:
I'm not claiming that HTC or TMobile will not check or notice that you have rooted your phone. Just illustrating that the repair techs don't want to talk to customer service anymore than you do and would rather just fix the phone and move on to the next one.
Fingerlickin said:
I work in an electronics repair company and I agree with supremeteam256 about sending your phone in rooted. Our techs don't check for tampering, they just plug it in and use the programs my department writes to test and reflash the devices. Of course our devices are much more complicated but the same NON-Communication between customer service and technicians still exist.
I think the biggest reason for this is because the techs just aren't interested in explaining the technical details to a customer service rep because all they ever get is "huh? wtf is a bootloader?"
Click to expand...
Click to collapse
Nice breakdown.
i had to reroot my phone because somehow i lost the recovery image and it wouldnt let me flash anything
so i went re did everything
and i put the danger spl on here and now its stuck at the Tmobile G1 screen
am i screwed or is there something that i can do
Did you flash the radio first?
no
i didnt i couldnt remember which one was first
Remember when you flash the new spl you HAVE TO flash the rom again after it. Did you do that?
it doesnt even let me get to the recovery image to do that i had just flashed to jf 1.51 btw
roguestatuskat said:
no
i didnt i couldnt remember which one was first
Click to expand...
Click to collapse
if you can't boot into recovery (home and power) or bootloader (camera and power) then your phone is bricked. you can either call your provider or htc and say something about an update, and see if you can get a replacement phone.
can i just go to the tmo store tomarrow? and then they can just give me a new one?
roguestatuskat said:
can i just go to the tmo store tomarrow? and then they can just give me a new one?
Click to expand...
Click to collapse
you could try it, sometimes it is better over the phone, but you can try in store.
make sure you sound as dumb as possible, like you don't know anything about xda, rooting, flashing, brick, or anything technical. just say something about an update, then afterward it started back up, that it wouldn't boot.
im mexican so i can be all like
i was like eschool nd then the thing was like update nd i turn off pero no turn back on
phone or Tmo store which one is faster?
roguestatuskat said:
im mexican so i can be all like
i was like eschool nd then the thing was like update nd i turn off pero no turn back on
Click to expand...
Click to collapse
haha, i imagine that one would work
hopefully very well
The same exact thing happened to me a few monthes back, I called them and after some bs story they sent out a replacement phone. Then once you get the replacement, you just put your original phone back in the box and ship it back to them.
I have been able to replace a g1 in the store. Just don't take no for an answer. And if you have to take a hostage.
supremeteam256 said:
I have been able to replace a g1 in the store. Just don't take no for an answer. And if you have to take a hostage.
Click to expand...
Click to collapse
hahahahaha
but seriously though, you should try a little harder before resorting to re-rooting. You know that it may not always be possible to fall back to RC29 if HTC decides to change the keys, right? You should learn how to troubleshoot so you wont have to resort to that
damnit google, just give us root and this wont happen
roguestatuskat said:
damnit google, just give us root and this wont happen
Click to expand...
Click to collapse
lmfao they have. it costs $424 + shipping
google android developer phone
sorry google i apologize despite your cockliness towards cyanogen
what i meant to say is damnit Tmobile give us all dev phones
Rooted phones would do more harm than good to the average user...
As for your situation, does holding the Camera or Home key not boot you into SPL or recovery, respectively?
It's likely than when you went back to RC29 to reroot, your radio is reverted back along with it, and then you flashed the dangerSPL to brick your phone.
cigar3tte said:
Rooted phones would do more harm than good to the average user...
As for your situation, does holding the Camera or Home key not boot you into SPL or recovery, respectively?
It's likely than when you went back to RC29 to reroot, your radio is reverted back along with it, and then you flashed the dangerSPL to brick your phone.
Click to expand...
Click to collapse
flashing the DangerSPL then the RC29 image should have any detrimental affect on the phone. People has successfully downgraded directly to RC29 with success.
I've read many posts to that extent, but I cannot be 100% as I haven't done it myself
So, the only thing holding me back was voiding the warranty and the fact I have a rogers phone (build EPE54B).... so I think I have to flash the build to the one that matches the update?
Sooooo if anyone wants to point me in the safest, easiest direction... I would appreciate it... and dos and don't would be appreciated as well. I am new to the phone an android, so feel free to dumb it down.
Does the build actually mean anything? What happens once I change it... and official updates come out? I am going to cut the grass... and then root, so help me out (preferably someone that is on rogers and has done this)
thx in advance! Froyo or Brick, here I come!
had a long day with chores and family day.... but I am back at it, first tutorial down and it seems solid...
Uploaded with ImageShack.us
onward!
Let me know how you make out. I'm on Rogers as well and am debating rooting.
Just looking at the stickies in General section would save you from opening yet another thread on the subject
Follow this until rooted:
http://forum.xda-developers.com/showthread.php?t=636795
Follow the guide for rooted N1s from here:
http://forum.xda-developers.com/showthread.php?t=686326
Let me know how it goes for you.
I am on Rogers and experienced EXTREME instability the moment I flashed the Froyo radio. My phone would crash randomly and frequently.
I suspect it was a problem with my hardware and have returned the phone and am waiting for a new one.
Jack_R1 said:
Just looking at the stickies in General section would save you from opening yet another thread on the subject
Follow this until rooted:
http://forum.xda-developers.com/showthread.php?t=636795
Follow the guide for rooted N1s from here:
http://forum.xda-developers.com/showthread.php?t=686326
Click to expand...
Click to collapse
thx jack, I appreciate it.... sorry for the thread... but in my experience... it is easier having your hand held by someone experienced.... then assuming I am following the right one, lol.... so I follow that entire thread to go from rogers to whatever build I need? heh
I will try this in approx 2 hours.... when the yard work is done!
early quick question, when I go to "CyanogenMod"
it takes me to a thread, but I do not see the download, what am I not seeing? heh
I am at this part
Type: fastboot flash recovery recovery-RA-nexus-v1.7.0.img
it says cannot load image recovery? thx
well everything was working great up until this point, tried it 100 times, heh... so now I sit and wait for guidance? thx
Mr.Kakarot, have you put the .img in the same folder as fastboot? Or, alternatively, if fastboot is in your PATH, you won't have this problem.
i renamed the image to recovery.img and that seemed to work? I will continue after supper!
Jack_R1 said:
Just looking at the stickies in General section would save you from opening yet another thread on the subject
Follow this until rooted:
http://forum.xda-developers.com/showthread.php?t=636795
Follow the guide for rooted N1s from here:
http://forum.xda-developers.com/showthread.php?t=686326
Click to expand...
Click to collapse
followed that first thread to a T and it worked out... had 2 minor stalls but I got through it... I am doing this stuff off and on, thx for that thread... this is going to be a STUPID question I am sure... but following that first thread, what have I done? unlocked, rooted and installed google add ons? phone looks awesome, I will do the rest after supper!
hmmm, got it, lol
done, running 2.2.... so tomorrow at work, i guess I will see if I have any issues....
now that this is done, can I re install that sense ui? What should I do or try now that I have done those 2 tutorials? thx
first off there are no 2.2 froyo/sense roms available as of yet.. so if you want to use a desire rom youre more than likely going to want to downgrade to the latest 2.1 radio that works well with your carrier/area, as froyo has its own radio and needs it to run properly.. once you downgrade.. nandroid>wipe>flash
yea, I did not know it would put me back to 2.1, lol.... went back and then back again to 2.2, lol... sense sure looked good!
Any ideas, suggestions, tips for 2.2? I installed flash! thx
How stable is your phone with the Froyo radio? Any unexplained reboots yet?
well it was quite late by the time I did it, I was playing with it, went to a few flash websites.... and no reboots or shutdowns, I also just woke up.... so I will know today after a full day work/playing, thx
one of the bugs is my camera does not work for video... so I have to update the radio, any suggestions! thx
Nope thats pretty much what you need to do is update the radio
thanks, but I am not gonna lie... still not sure which are radios, roms, senses, lol.... could you point me to the one I need.... or does it matter? thx, I just do not want to brick, obviously!
Also, I did not do this step.... is this what I need to do, or is it unrelated?
11) You should still have root, but if you want BusyBox (or lost root somehow), Cyanogen has done it again! Go back into Recovery and flash froyo-rooter-signed.zip. Then Titanium Backup will work once again.
does not sound like something I need or use, so I did not do it....
as far as stability... my 3g signal looked low all day... but I never had a dropped call, instability or any reboots/crashes.... all is well! thx
go here:
http://forum.xda-developers.com/showpost.php?p=6734240&postcount=9532
havent had problems with the older one, but am going to try the new one just to see.
anyone around?
I tried these 3 things
Step_One_Froyo_Radio_Update.zip
step-two-RoDrIgUeZsTyLe-FroYo-MCR-R16-MOD-V1.8-FIX.zip
and then i ran
2.6.34_AVS-925mV_CFS_1113Mhz_061210.zip
anytime I run setcpu, I get this error
the application process com.mhuang.overclocking has stopped unexpectedly, please try again?
"uninstalled and reinstalled, worked. thx"
I need some ideas on how to fix my phone. I used to flash new roms all the time but a few weeks ago I started having problems.
When trying to load a new rom my phone would get hung at the multi colored X. Then once I got a rom to stick I would get lots of force closes when I hit the settings button.
I'm tired of dealing with it but I'm not sure how to fix it. Here are two Logcats of the phone stuck at the mulit colored X.
I would appreciate the help at getting my phone back to normal.
Logcat 1
Logcat 2
im not a expert but try unlocking ur bootloader and uploading all the update files from 2.2 froyo or something that helped me unbrick my almost brick
I would try passimg before fastboot flashing anything. If you want to know how to passimg it's in the wiki under unroot restore.
hitmanre said:
im not a expert but try unlocking ur bootloader and uploading all the update files from 2.2 froyo or something that helped me unbrick my almost brick
Click to expand...
Click to collapse
Thanks a ton! Your suggestion lead me to this thread.
http://forum.xda-developers.com/showthread.php?t=717870
I've spent hours trying everything I could to fix it. My phones been half busted for about 2 months.
I didn't think it would but it did. It brought my phone back to stock 2.1. I grabbed z4root to root it, then reflashed hboot, radio and went back to CM7 nightly. All is well with the world again.
Dude Random21 said:
I would try passimg before fastboot flashing anything. If you want to know how to passimg it's in the wiki under unroot restore.
Click to expand...
Click to collapse
Thank you, I just got it fixed using the method you described.
no problem, it sucks to have that feeling in ur stomach that u broke a 500$ device, thats why i like helping around while i can