• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Root Terminal rebooting problem.

dogsey

Newbie
Right, as of yesterday my rebooting problem seems to have become terminal. :mad:

It won't boot beyond the red circle, and although it will load into the bootloader it won't go into recovery after that. Now obviously I'll be sending back for repair but what are the chances (given that it won't boot at all now) that they'll know the phone has been rooted and refuse to fix it?

Dogsey.
 
Was it a custom recovery? Was your handset branded originally? Is it now? If so, what branding?

Need specifics.
 
It was rooted using Unrevoked 3.21 (or what ever the current version is) originally using the Defrost 4.9 rom, most recently running Leedroid 2.2b. It was originally a branded UK T-Mobile phone that had been upgraded to Froyo.
 
Did you make a goldcard? Assume you did?

If so you could return to stock using a TMOB RUU

Not sure if running unrevoked again will reflash recovery in the current state of your phone?
 
Now let's assume for a moment that I didn't make a goldcard ... :o

I have to add that this rebooting problem is not the outcome of trying to do anything new to the phone, just the culmination of the standard "feature" of some Desires to reboot every now and again - Only this time no amount of leaving the battery out will make it boot.
 
Use an ruu from t mob. Boot to fast boot by hold back whilst turning on. Connect to pc and run ruu
 
Ok, slight improvement. Booting to Fastboot works, however the RUU I've downloaded (RUU Bravo TMO UK 1.21.110.4) gives me an Error [140]: Bootloader Version Error message. Do I need a newer (or older) RUU?
 
Ok, tried that one, new error message

Error [131]: Customer ID Error.

Next?

ETA: Is it because that RUU is TMO AT rather than TMO UK?
 
The only thing I can think of is if unrevoked flashes recovery without the phone being booted. Not sure if it does.

If somehow you can get into recovery, flash a Rom, make a gold card, use generic ruu, use teppic's downgrade tool, and flash t mob ruu...


Long shot though.


You may well be stuck
 
Ok, if I am stuck then we go back to my original question: Given that it won't boot at all will the repair team know that it's been rooted and therefore refuse to fix?
 
I couldn't say. Possibily they will only be able to load an ruu to fix. Nothing lost by sending it in.
 
Well it's gone back to the shop tonight - 14 to 28 days before I find out what happens.

In the mean time T-Mobile have given me as close a replacement as they could, a Nokia 2330! :eek:

I feel so dirty! :D
 
The one.that looks like a silver plimsol?

Awful. Poorest in call quality ice ever heard. Had one at work.
 
1 week after dropping it off with my local T-Mobile shop I got the text to say it was back ... new mainboard, no issue with having been rooted! Bonus.

Now waiting to see how long it is before it starts to go wrong again.
 
Back
Top Bottom