I used the JFUpdater and downloaded the JF1.5 [cupcake] build.
It then told me to apply it, which I did.
It went through the process of rebooting and then applying the update. From there, it reboots and it just HANGS on the "Tmobile G1" screen. It can't go anywhere from there. I've left it sitting for a good 10 minutes.
any ideas?
all help appreciated.
wipe, and reflash
question.com said:
wipe, and reflash
Click to expand...
Click to collapse
Dangit!
Should I d/l an update from online or let it go through via JFUpdater?
Thanks
EDIT: Stupid question - I got it to work. Thanks
akapoor said:
Dangit!
Should I d/l an update from online or let it go through via JFUpdater?
Thanks
EDIT: Stupid question - I got it to work. Thanks
Click to expand...
Click to collapse
It should still be in your SD card. Go into recovery mode and perform a wipe, then update. (alt-w, then alt-s)
edit: wow, you busted a ninja edit on me haha. Good to hear that you got it working, enjoy the new firmware!
Haha - my bad bro.
Lol but thanks a lot for the help.
I tried doing it before (few days back), and didn't work. I guess it was your magical "touch" that did it ^_^
Lovin' the speed improvement on this, by the way.
Related
what do I have to do?
Read the sticky about the 1.5.2
?? link please....
http://forum.xda-developers.com/showthread.php?t=596879
You might read a little about this ROM before flashing, some People Are Experiencing issues, but not all, i happen to be one of them with the Dalvik Cache Clearing problem.
Agimax thanks alot, I'm reading it right now. I Think I'm going to stick with 1.2.3 for now until the prob gets fixed.
It's pretty much OK to go ahead and just upgrade to the newest recovery. I just did using Flipz's auto-rooter, and it works 100% for me.
I flashed the new v1.5.2 recovery image directly over v1.2.3 and didn't have any problems at all.
Agimax said:
i happen to be one of them with the Dalvik Cache Clearing problem.
Click to expand...
Click to collapse
Yes, after all, it's so hard to just plug in a cable and clear the cache via adb if the recovery won't do it for some reason.
I think I'd take the potential weirdism with something you (a) seldom do, and (b) has a more than acceptable workaround, vs (c) the known nandroid breakage in 1.5.1.
mkhopper said:
I flashed the new v1.5.2 recovery image directly over v1.2.3 and didn't have any problems at all.
Click to expand...
Click to collapse
You just flashed it off the sd like any other update? Is that the way to go people?
stu-k said:
You just flashed it off the sd like any other update? Is that the way to go people?
Click to expand...
Click to collapse
No, actually following the directions written by Amon_RA in the thread announcing the recovery image is probably the way to go.
mrinehart93 said:
It's pretty much OK to go ahead and just upgrade to the newest recovery. I just did using Flipz's auto-rooter, and it works 100% for me.
Click to expand...
Click to collapse
Used Flipz auto-rooter in the pre-kitchen as well to go to 1.5.2 as well with no issues.
Here you folks go. Off of my phone to you. http://www.multiupload.com/YOXKQ18YW0. You Must have 2.1 with the 3.6 Update. I would recommend making a backup before applying. Use at your own use. If you get a Status 7 error, see my thread in the General forum on how I resolved it. Have Fun!
how is it? faster than 2.1?
Oh yeah. More bloatware, but that's easy to remove. Internet speed is faster. Phone is more responsive. Nice to have the Hotspot feature now. Overall a worthy upgrade. Now to wait for 2.3
can i use this update for my finland rom 3.42? or this is just for TMo version?
runeblade said:
Here you folks go. Off of my phone to you. http://www.multiupload.com/YOXKQ18YW0. You Must have 2.1 with the 3.6 Update. I would recommend making a backup before applying. Use at your own use. If you get a Status 7 error, see my thread in the General forum on how I resolved it. Have Fun!
Click to expand...
Click to collapse
Would you happen to have original t-mobile 2.1 in sbf format?
Unfortunately no-one has one for the US. I'm guessing you updated to the leaked version? The good news is that if my suspicion is correct a nandroid backup of this should play fine with the updated firmware. If you look at the difference its minor. 34.4.9 vs 34.4.4. I have not yet had the time to make one yet. I'll try to do so tonight.
What did you have to do with the update.zip in order to upgrade your defy? I'm on 2.1 with the 3.6 update, I'm rooted with superoneclick, and I have it copied to the root of my sd. Did you use clockworkmod recovery?
nanek921 said:
What did you have to do with the update.zip in order to upgrade your defy? I'm on 2.1 with the 3.6 update, I'm rooted with superoneclick, and I have it copied to the root of my sd. Did you use clockworkmod recovery?
Click to expand...
Click to collapse
Its an update zip file signed by company so you should enter stock recovery by power+vol down and then select update from zip.
hmm... how about flash 3.4.2-107 TMobile US Blur with RSDlite and then
update.zp?
Just tried it. No go.
It checks for the right build fingerprint before it continues. You need to have 6.36.0 or it aborts.
The Nandroid backup theory mught be the one that works...
no clue said:
hmm... how about flash 3.4.2-107 TMobile US Blur with RSDlite and then
update.zp?
Click to expand...
Click to collapse
Beach_Head said:
Just tried it. No go.
It checks for the right build fingerprint before it continues. You need to have 6.36.0 or it aborts.
The Nandroid backup theory mught be the one that works...
Click to expand...
Click to collapse
Thanks for the update.
...... I just want something official now
( I am on official Chinese 2.21 build 1.11, it is fast, specially when you skip Blur registration. But, just in case I need my phone service by t-mobile .... )
The leaked T-Mobile SBF was fast too.
But yeah, an official one would be better.
If the Nandroid method doesn't work, I hope someone posts an SBF soon...
no clue said:
Thanks for the update.
...... I just want something official now
( I am on official Chinese 2.21 build 1.11, it is fast, specially when you skip Blur registration. But, just in case I need my phone service by t-mobile .... )
Click to expand...
Click to collapse
As for right build fingerprint, yes you are right. It is picky as hell. In the other thread I also mentioned that it is checking for apps. For example, I have Blockbuster disabled....it checked for it, didn't find it, and failed. I spent over 4 hours last night getting this to a point that it would work. Way Way too much hassle. Unfortunately I don't think I'm going to get to do a backup tonight. Was up way too late last night/this morning working on this and put in a 12 hour day. As soon as I get a breather I will. Sorry.
No worries!
Is there any way to edit the build.prop file so that I can get the update to work?
runeblade said:
As for right build fingerprint, yes you are right. It is picky as hell. In the other thread I also mentioned that it is checking for apps. For example, I have Blockbuster disabled....it checked for it, didn't find it, and failed. I spent over 4 hours last night getting this to a point that it would work. Way Way too much hassle. Unfortunately I don't think I'm going to get to do a backup tonight. Was up way too late last night/this morning working on this and put in a 12 hour day. As soon as I get a breather I will. Sorry.
Click to expand...
Click to collapse
Unfortunately I don't have an un-updated Defy in front of me to pull the strings. I'll look at one of the ones at work tomorrow. If you read the error though it should tell you exactly what it is looking for. Mine did. Aslo try deleting the logwrapper. The was one of the holdups on mine.
I have the string. I'm just wondering if it would work if I do edit it...
Where do I locate logwrapper?
runeblade said:
Unfortunately I don't have an un-updated Defy in front of me to pull the strings. I'll look at one of the ones at work tomorrow. If you read the error though it should tell you exactly what it is looking for. Mine did. Aslo try deleting the logwrapper. The was one of the holdups on mine.
Click to expand...
Click to collapse
I just loaded this update.zip on my fiance's Defy...didn't wipe data or cache, it's booting right now....stuck at the T-Mobile "Stick Together" screen, waiting for the initial long boot
EDIT: Booted, running 2.2.1 now! So far so good, it's a little slow but it would be while it catches up. I have an Atrix and it's almost the identical interface.
can you make a sbf file of entire build?
Nandriod back up please! im dying for it
zencoran said:
Nandriod back up please! im dying for it
Click to expand...
Click to collapse
just flash the update.zip...why bother with a nandroid?
Hello all!
I am not sure what went wrong with my phone, but it is S-OFF Rooted, CWM'd. No matter what lockscreen I choose, where you would choose which shortcuts to pull to ring and where it opens up that particular shortcut.....the phone no longer is avail for me to choose. Anyone know what went wrong or have suggestions? Thank you!!
Reboot into CWM and wipe cache partition and dalvik cache and see if it works.
It happened with the 2.3.4 update -- previously discussed here:
http://forum.xda-developers.com/showthread.php?t=1226052
A work-around to get the phone icon back was posted here:
http://forum.xda-developers.com/showthread.php?t=1205384
knagl said:
It happened with the 2.3.4 update -- previously discussed here:
http://forum.xda-developers.com/showthread.php?t=1226052
A work-around to get the phone icon back was posted here:
http://forum.xda-developers.com/showthread.php?t=1205384
Click to expand...
Click to collapse
Thank you very much!!! It was quite annoying!! I was about to redo my phone again! You totally saved that from happening!
Happy to be able to help!
I've tried everything except rooting my Droid Charge to get it to accept the latest system update yet it will not get past a quarter of the way without stopping and displaying that triangle and exclamation point! Is there any way without rooting it that this problem can be corrected?! Maybe if i throw it against a wall...., please im at my wits end with it. Can someone help me?
Miserablewithdroidcharge said:
I've tried everything except rooting my Droid Charge to get it to accept the latest system update yet it will not get past a quarter of the way without stopping and displaying that triangle and exclamation point! Is there any way without rooting it that this problem can be corrected?! Maybe if i throw it against a wall...., please im at my wits end with it. Can someone help me?
Click to expand...
Click to collapse
Well don't root it because it'll never update then. Have you wiped data? If that won't work go to How to fix your phone get the download package for EP4 and follow the instructions exactly. Then take the 2 updates.
stueycaster said:
Well don't root it because it'll never update then. Have you wiped data? If that won't work go to How to fix your phone get the download package for EP4 and follow the instructions exactly. Then take the 2 updates.
Click to expand...
Click to collapse
Thanks for your response! Okay, So download the EP4 and the PIT file for Charge? Im sorry, Im a newbie and I wanna be precise.
stueycaster said:
Well don't root it because it'll never update then. Have you wiped data? If that won't work go to How to fix your phone get the download package for EP4 and follow the instructions exactly. Then take the 2 updates.
Click to expand...
Click to collapse
I JUST WANNA SAY THANK YOU AGAIN!!! YOU JUST DEMOLISHED A WHOLE YEARS WORTH OF STRESS FROM MY MIND! LITERALLY!!!! Ive been dealing with this issue for a whole year! Thanks so much! It worked perfect!!!!!:good:
Miserablewithdroidcharge said:
I JUST WANNA SAY THANK YOU AGAIN!!! YOU JUST DEMOLISHED A WHOLE YEARS WORTH OF STRESS FROM MY MIND! LITERALLY!!!! Ive been dealing with this issue for a whole year! Thanks so much! It worked perfect!!!!!:good:
Click to expand...
Click to collapse
That's what we like to hear. Glad it worked out.
Sent from my SCH-I510 running Tweaked 3.0 using Tapatalk 2
When I try to wipe data to install another rom my phone stays on the little android guy just saying formatting data. It's been like this for an hour. How long should it usually take? Thanks
That step shouldn't take more than a few seconds. I would try pressing a couple buttons to see if you can get back to the previous screen.
If that doesn't work I'd pull the battery and do the key combo to boot into recovery. I hate doing it this way though, I just can't ever seem to the combination correct. Hope it works better for you.
CrustyMcLovin said:
That step shouldn't take more than a few seconds. I would try pressing a couple buttons to see if you can get back to the previous screen.
If that doesn't work I'd pull the battery and do the key combo to boot into recovery. I hate doing it this way though, I just can't ever seem to the combination correct. Hope it works better for you.
This is where it is happening, when I go through yhe phone it does the same thing.
Click to expand...
Click to collapse
Please reads forum rules before posting
Questions and help issues go in Q&A
Thread moved
Thank you for your cooperation
Friendly Neighborhood Moderator
Still haven't figured this out. Would like to try a different rom if any body has any suggestions of how to figure this out. Thanks
That is odd. The only thing that take more than a min is fixing permissions.
king750 said:
When I try to wipe data to install another rom my phone stays on the little android guy just saying formatting data. It's been like this for an hour. How long should it usually take? Thanks
Click to expand...
Click to collapse
What version of CWM are you using? I heard that 6.0.2.9 had issues. Better to stick with 6.0.2.8 or the newest 6.0.3.0. Both are verified working fine.
Stealth111 said:
What version of CWM are you using? I heard that 6.0.2.9 had issues. Better to stick with 6.0.2.8 or the newest 6.0.3.0. Both are verified working fine.
Click to expand...
Click to collapse
I'm running v6.0.2.3. Could that be the problem? It's also the touch version.
king750 said:
I'm running v6.0.2.3. Could that be the problem? It's also the touch version.
Click to expand...
Click to collapse
It wouldn't hurt to Odin/flash up to 6.0.2.8, and then try again what you were having the original issue with.
There have been changes made since 6.0.2.3, and a newer version might offer you correct results.
I use the touch version all the time, so I would say that touch/non touch wouldn't be any different.
Stealth111 said:
It wouldn't hurt to Odin/flash up to 6.0.2.8, and then try again what you were having the original issue with.
There have been changes made since 6.0.2.3, and a newer version might offer you correct results.
I use the touch version all the time, so I would say that touch/non touch wouldn't be any different.
Click to expand...
Click to collapse
I flashed up to 6.0.3.0 and everything is working like it should. Thanks