So for awhile I used a droid as my main phone and I flashed countless different roms on it. One day though it just went kaput on me, the led flash started flashing on and off whenever I tried to reboot it and I could not access anything including recovery or boot loader. Eventually the battery died and it would not charge again.
I recently was messing around with it and was able to revive it, would not boot up still but was able to get in the boot loader and eventually sbf it. The battery still wont charge(normally) which tells me at least one issue still exists with hardware. Other than that the phone works fine now on android 2.0. The problem is that I cannot upgrade it to anything higher than that.
The only .sbf I could get to both load and boot up successfully was esd20 anything else would just boot loop indefinitely, after rooting that and trying to go from there anything else also boot looped. I installed every recovery I know of from clockwork to spr to that rzr mod of it but none could flash without the same results(restoring a nandroid of that esd20 still worked though). I've tried different kernels as well to no avail. The first steps I did were an exact procedure that I had done before on the same phone successfully with a 2.2 sbf but now it just wont work.
I don't know if there could be some hardware issue causing these problems though I cannot fathom how when one firmware still works and would appreciate any insight that anyone has as to what may be the problem. Was planning on giving the phone to a young family member to play games on as soon as I managed to boot it back up but I don't want to deal with the compatibility issues with such an old version of android.
Related
Hey guys its been a while since I've even tried to fix my phone cause everyone was saying its dead. But I've been reading stories of people coming back from the G1 logo. So i could really use your help.
Heres the problem, A while back I dropped my old G1 and had to get a new one. Upon looking for the video I used last time to root my phone, I couldn't find it. I searched high and low but to no avail. I figured any video would work as long as it rooted me. So I started up the video. however once i was "done" with it i noticed nothing had changed. So i figured the video was garbage and found another one and started it up. I know, STUPID. Well when i booted my phone after wiping and flashing. It stayed on the G1 logo. I knew the worst had happened. So now i don't know what to do. There have been one or two occasions that I've gotten it to boot loader. So i know i can get there. but what do i do when I get it?
Also, no, I never got to flashing raido's or anything like that. I thought I wasn't rooted so i didn't move on.
I know it was long but I'm getting all the info out there. Please help, I think its possible, and if it is I want my phone back!!!
What were you installing by the way?
EDIT: Made a mistake, thought you were able to boot into recovery.
He does not get to recovery, but into bootloader mode (cam + power on). This is good, as there is a good chance to recover from that.
Try the first section of this guide:
http://wiki.cyanogenmod.com/index.php/Full_Update_Guide_-_G1/Dream_Firmware_to_CyanogenMod
You have to flash the correct dreamimg.nbh via bootloader. You might need a Goldcard to do so, in certain countries, but lets just hope that is not the case (would be more work...)
€: Some more Info on Bricking your device with Radio/SPL updates, so take care: http://forum.xda-developers.com/showthread.php?t=655097
The guide on cyanogens wiki is considered dangerous at the optional update to HardSPL
a few days ago my fiance was complaining her basically stock Nexus was rebooting into a bootloop - where it displays the loading X and vibrates and then reboots and repeats every few moments (a few days after her doing the system update)- if I remove the battery for a few minutes then put battery back and reboot it will boot into the OS where it will stay sometimes for a few minutes othertimes an hour or more before going into the bootloop- so I told her I would attempt to flash a new rom. after many hours of messing with the phone and attempting to access the recovery it just will not work- the phone just goes into the bootloop - exactly as mentioned above. I have used fastboot to flash new images (userdata, system, boot, recovery etc) numerous times and it still does the same thing- crashes and reboots into the bootloop from the OS randomly and bootloop when trying to access recovery. I am pretty sure it is a hardware issue (the phone is only 3 months old) but the company i bought the phone from is stating it is a software issue and not covered by tehir warranty.
Problem is I unlocked the bootloader while messing with the rom's yesterday and am now concerned they wont honour the warranty anyway- does anyone have any suggestions as to anything else I can try? As far as I can tell as I cannot access recovery I cannot install any other roms..
Please help- otherwise I will be posting a yourtube video of me destroying a basically brand new nexus one- I really am that frustrated....
a bit more info- it was rooted but still had locked bootloader when this started- rooted using onclickroot or something- which after the update it wasn't rooted anymore- I am wondering if this has caused some low level conflict somehow- I have rooted again using superoneclick - and as stated have unlocked the bootloader.
is there any way to flash a rom using fastboot or adb on this thing- I would hazard surely there is but amongst all the information floating around for this phone I cannot find out how- I am thinking maybe I try and load cyanogen 6 or something if I could work out how to flash a rom using adb (because njo matter how many times I try to flash different recovery images it wont boot into recovery- I can access fastboot etc but as soon as i select recovery I get the bootloop...
and before I get flamed I have spent three days searching and reading and attempting everything short of voodoo witch magic. I thought my X10 was a P.I.A. to root and flash etc but really it was simple compared to the trouble this phone has given me..
I am wondeirng if some of the rom's are incompatible with some hardware- and I don't quite understand the whole radio thing either... can someone explain that?
BTW Im not a total noob- I have been around for a while without an account - then have had this account for a while but mostly just read the forums as I have no real input and knowledge to give...
...help!
Can no one help?
I have managed to get into recovery (by putting the phone in the freezer for ten minutes at a time to reduce the temperature and stabilise it enough to run for 15-20 minutes at a time)...
Have flashed different kernels this way and nothing is stable- it still bootloops because of heat....
I contacted HTC Hong Kong (it was purchased from a Hong Kong company) and they have told me there is a $350 fee to repair it as its a UK phone. Now the phone is exactly 55 days old not three months and I am really really frustrated.
Does anyone know if its worth contacting HTC UK?
I have friends in the UK I can have them send it in and recieve it from repair....
Someone please help- even if its just a comment of "just smash the damn thing..."
Thanks guys sorry about the long self centred posts but I am ready to destroy this phone- it doesnt have a mark on it either- any ideas what its worth for spare parts?
Hello All,
I'm fairly certain there isn't another thread asking this question, if I overlooked it I apologize in advance. Now to the point, I have a dell streak 7 and I have been having some stability issues with it for about the last week. What was happening is I was running Android 2.2.2 and my system would crash randomly eventually it wouldn't start back up. I tried doing a factory restore several times this didn't work so I re-flashed to restore the original file system and I installed the T-mobile system by mistake. I played around with this for a little bit and every thing seemed fine. So I decided to upgrade to 3.2 honeycomb, I flashed the DS7 did all of the set up steps and started reading about rooting the device (I didn't start any of the steps). While it was sitting next to me in sleep mode I noticed it just randomly reset itself and started booting up. I looked around in it and nothing seemed to be changed, so I powered it off and powered it back on to see if it would freeze up and crash again. it didn't so I put it back in sleep mode and kept reading. then the side lights came on and it froze up. I was able to get it to boot by going into recovery mode and then selecting boot normally. So my question is, is this some sort of hardware issue or something that I am doing wrong? I don't think it's hardware but I could be mistaken. Also, has anyone else had an issue like this and if so is there a known fix? I am going to try re-flashing to the original file system again and replace the restore .img and see if this helps. Also, I'm not sure if my DS7 is the mobile version or wifi only version. I entered the service tag at DELL's website and it said I had the mobile version, however it didn't have the t-mobile start up animation before I flashed it the first time and in the sim card slot there is a black piece of plastic or card (IDK which) lodged in there and it wont come out. Any help or advice on this would be greatly appreciated .
Thanks in advance-Woulfenstien
OK I'm pretty sure i got it solved. what I did was I re-flashed everything. I re-flashed the boot.img, the system.img, and the recovery.img using fastboot and then i re-flashed whole system with nvflash. It's been a couple of hrs. and this has seemed to work so far. I upgraded back to 3.2 honeycomb and rooted the device with no problems so far. If any other issues arise I will post them here along with what i did to fix it. I would also like to thank everyone on this forum who has posted the tutorials, it was a huge help I wouldn't have been able to fix my DS7 with out all of your help.
Thanks again-Woulfenstien
So here's my problem. I think I've bricked my device. Don't know if it's softbrick or hardbrick, but either way my phone just does not boot up. The only instance it works is when I remove the battery and try to charge the phone, it shows a picture that it didn't find a battery. All of this occurred while trying to unlock the bootloader. Something similar already happened to me like a month or two ago, but I was able to flash stock KDZ using the online LG Support Tool. Anyway, the part where it all messed up is probably the aboot.bin file, although I'm quite certain I flashed the right file for my device. Also, installed CWM recovery, and after restarting the device it just won't boot at all, not even the software upgrade mode or anything. So my guess is that something is wrong because of either a wrong aboot.bin file for my D405N or the custom recovery. I tried flashing stock KDZ, but I couldn't get my phone into software upgrade mode. Also, tried doing a hard reset, but an LG logo didn't even come up. The battery is at least half full. So is there anything I can actually do in this case? Any help is appreciated.
P.S. Yeah, I did post in another thread (though I didn't create it), but I'm quite desperate with this. Either I fix it myself somehow, or I'll have to take it to the warranty.
EDIT: Took it to a repair. Should be done in around a week. Got an old Samsung Galaxy Mini as a replacement.
linasj said:
So here's my problem. I think I've bricked my device. Don't know if it's softbrick or hardbrick, but either way my phone just does not boot up. The only instance it works is when I remove the battery and try to charge the phone, it shows a picture that it didn't find a battery. All of this occurred while trying to unlock the bootloader. Something similar already happened to me like a month or two ago, but I was able to flash stock KDZ using the online LG Support Tool. Anyway, the part where it all messed up is probably the aboot.bin file, although I'm quite certain I flashed the right file for my device. Also, installed CWM recovery, and after restarting the device it just won't boot at all, not even the software upgrade mode or anything. So my guess is that something is wrong because of either a wrong aboot.bin file for my D405N or the custom recovery. I tried flashing stock KDZ, but I couldn't get my phone into software upgrade mode. Also, tried doing a hard reset, but an LG logo didn't even come up. The battery is at least half full. So is there anything I can actually do in this case? Any help is appreciated.
P.S. Yeah, I did post in another thread (though I didn't create it), but I'm quite desperate with this. Either I fix it myself somehow, or I'll have to take it to the warranty.
EDIT: Took it to a repair. Should be done in around a week. Got an old Samsung Galaxy Mini as a replacement.
Click to expand...
Click to collapse
Remember Next time Unlock Bootloader before Installing CWM.
Hi XDA community,
I'm scared out of my mind. Tried rooting for the first time ever, but don't actually know what I'm doing. Using various guides I found in these forums, I:
1. Used HTCdev to unlock the bootloader
2. Used ADB to install TWRP 3.0.2-0
3. Used TWRP to install UPDATE-SuperSU-v2.76.zip
Once that finished, my phone tried booting up (the white HTC logo) but now it has the red development build text at the bottom.... and then it gets into an infinite boot loop.
I don't know how to fix my phone. Please someone here with guidance, please help.
I've got the same identical issue.
I was able to get out of the boot loop by holding volume up and power, and I got back to download mode. From there, since the SU update I tried to install boot looped me (I was following this tutorial), I jumped ahead and just installed cm13 as I was planning to.
This install went fine, but then I ran into the issue of the rom not recognizing my sim card. I've been researching this problem and I guess I need to update my baseband? I tried for hours but I do not know how to accomplish this, and couldn't figure it out for the life of me. This thread on the cyanongenmod forum seemed to be the closest thing to help I could find, but still it didn't help very much.
So at this point now I'm trying to back out and unroot my phone and get everything back to factory settings; it doesn't feel worth it anymore to me since I've just had trouble every step of the way. I've been trying to follow this post to get back to at least a usable factory rom. But I can't even get this one to install because I cannot access my phone through adb while it's in download mode. Furthermore the instructions are just confusing me because I'm not so versed in the nomenclature of these procedures.
Is there anyone that can help me get back to complete stock t-mobile sense? Or if not, help me get my cm13 rom to recognize my sim card so I can at least have my phone working in some capacity? I'd be tremendously grateful of either. I'm really in over my head here and quite scared I won't be able to figure this out.