Related
tried installing glorious overdose but I tried to wipe data, and it stayed there for about 10min so i pulled out the battery. i tried a second time but without wiping data (i didnt know WTH i was thinking) so it rebooted and was stuck at boot screen saying create new partition and system not avaliable (sumthing like that) so i decided to try odin so i can go back to stock firmware and it finished and now it stays at the bootscreen blinking i tried recovery im stuck.
before you odin, reinstall the phones drivers on your pc. connect the phone to the pc without the battery, hold the volume down button and the trackpad and reinsert the battery. when you odin, make sure only auto reboot is checked, and put the pit file in the pit slot and the tar file in the pda slot. if you use kies to update firmware, reinstall drivers again before updating.
You may need to check "Re-Partition" in Odin.
shouldnt need to repart, in fact it may be a bad idea. every time i odined and accidentally had repart checked, it screwed something up. most recently the stock messaging app didnt work after odin. i have since switched to go sms, but still made sure i had a clean firmware install. i would try odin without repartitioning first and see how that goes. if something is wrong, you can always odin again. the first time i tried to flash a rom i bricked because i flashed cwm through rom manager. the thread where i found the odin file said make sure only auto reboot is checked. besides, if the rom didnt flash correctly, then it didnt convert any partitions anyway.
ok i had the same problem for the first time i tried to install a custom rom, theres a way that you can fix it with out odin. follow this steps... i promise it will work.
1)boot into the red cwm voodoo lagfix recovery
2)wipe data/factory reset
3)wipe cache partion
4)after all the steps above are completed, go to apply sdcard:update.zip
the its going to take you to the regular cwm once there follow this steps...
1)install the custom you want to install, but make sure that it doesnt need special mounts and unmounts, so follow the instruction flash the rom and it should fix it
Heimdall worked perfectly when I bricked my phone.
Thank you!! ^ I was boutta cry when it was Rebooting .... Yea I guess I messed something up with odin
WolfV2 said:
Heimdall worked perfectly when I bricked my phone.
Click to expand...
Click to collapse
I tried the method above but ater reboot it stays on the T-Mobile Sidekick 4G boot screen and does nothing else. I'm hesitant and Flash Bootloader but what do you all think?
flashing bootloader in that package doesn't break it.
creid2352 said:
I tried the method above but ater reboot it stays on the T-Mobile Sidekick 4G boot screen and does nothing else. I'm hesitant and Flash Bootloader but what do you all think?
Click to expand...
Click to collapse
My advice is do whatever it takes, and besides, don't worry about breaking something that's already broken, if you know what I mean...
johnwazhere said:
Thank you!! ^ I was boutta cry when it was Rebooting .... Yea I guess I messed something up with odin
Click to expand...
Click to collapse
No problem, glad I could help
creid2352 said:
I tried the method above but ater reboot it stays on the T-Mobile Sidekick 4G boot screen and does nothing else. I'm hesitant and Flash Bootloader but what do you all think?
Click to expand...
Click to collapse
This is my current problem as well, except I have tried checking flash bootloader and have also tried Odin, but all to no avail. Can anyone help me? This is my situation:
I've had my sidekick for about a year now and have gone through the typical problems of a sidekick user. Then yesterday, my sidekick's alarm woke me as normal, but I was unable to turn it off because my touch screen wasn't working. So i battery pulled, restarted, and noticed that the screen stayed on the "T-Mobile Sidekick 4g SAMSUNG" start up screen and did not budge. I tried battery draining, more battery pulling, and nothing worked. So i did a lot of research on here and other websites and decided to use Odin. After initial problems of a newbie, I eventually figured it out and got it to RESET and PASS, but the subsequent reboot only caused my phone to be stuck in the same Sidekick start up screen it has been getting stuck in. Similarly, after many tries, Heimdall has done the same for me. Sorry if that was a long read (also, I hope its cool that i bumped this thread with my own problems), but is there anything else i can do? I'd really like to use my phone again..
I've been working for hours trying to figure out how to fix it, and I just don't know. The end result is always just the freezing at the t-mobile start up screen..Also, since i forgot to mention, I can only get into download mode with the volume down+trackball method because otherwise it would just go to the regular start up screen and freeze. I don't know if that means anything, but yeah.
Have you used heimdall yet? I bricked my SK4G the other day when flashing a rom and heimdall put it back to stock within 5 minutes of me bricking it.
Thank you for replying. Unfortunately yes, I did. With flash bootloader unchecked and checked. It says it disconnects after everything is done and it restarts, only to become frozen at the start screen again =/. I don't know if there is some silly detail that im missing that makes the flash rather than just restart, but all i can manage to make it do is restart.
Sigh. Guess im going phone shopping.
How did u get the phone in dl. Mode
Sent from my SGH-T839 using XDA
I had to plug the phone into my computer without the battery, hold volume and the track ball, then pop the battery in. Any other attempts would simply start it up/freeze it.
Ok did u have heimdall started first?
Sent from my SGH-T839 using XDA
And what rom did u last have?
Sent from my SGH-T839 using XDA
I'm not entirely sure if I had it started first, so I'll try it that way now. And the last ROM that I had? Honestly not really sure what that means =p, but i've never flashed one and I had the most recent sidekick update installed (though it is possible that I had done a factory reset at some point to fix an error).
---------- Post added at 01:04 PM ---------- Previous post was at 12:45 PM ----------
Just tried it. Without flashing bootloaders, it finishes and restarts to my frozen start up screen as normal. However, when i flash bootloaders, it gets to "uploading pit", but the upload fails and it reboots my phone. But this time, it reboots into download mode. A welcome change from my start up screen. Maybe there's hope.
Ok, so I did my first root last night with my G2x and flashed CM7 onto it using the instructions here for GB. The process didn't seem to go through at first because it kind of froze for awhile, but when I took out the battery and put it back in it loaded up. (I understand I may have made a mistake here.)
I thought all was good but then I tried to boot up Clockwork recovery to flash the GAPPs zip and everytime I tried it wouldn't go through the screens it is supposed to.
I'd hold the down volume and power buttons and the first LG (white) would show. Then it would bring up a cyan colored horizontal loading bar under the LG. I continue to hold the buttons hoping to see the cyan LG but then screen changes to a box with an orange arrow pointing to an android logo. There is a loading bar under this as well. If I let go here it loads up CM7 but if I continue holding on it takes me to the S/W screen.
I've tried this multiple times but I've kinda given up. I even tried individually installing the apks from the GAPPS zip but only a few of them successfully installed.
At a loss .Please let me know what I can do.
Let me guess. You flashed CWM via ROM manager?
Follow he guide here and let us know how it goes:
http://forum.xda-developers.com/showthread.php?t=1056847
Also, before you install the ROM use the wipe tool in my sig.
I appreciate the response but I did use that thread to flash it.
ae2012 said:
Ok, so I did my first root last night with my G2x and flashed CM7 onto it using the instructions here for GB. The process didn't seem to go through at first because it kind of froze for awhile, but when I took out the battery and put it back in it loaded up. (I understand I may have made a mistake here.)
I thought all was good but then I tried to boot up Clockwork recovery to flash the GAPPs zip and everytime I tried it wouldn't go through the screens it is supposed to.
I'd hold the down volume and power buttons and the first LG (white) would show. Then it would bring up a cyan colored horizontal loading bar under the LG. I continue to hold the buttons hoping to see the cyan LG but then screen changes to a box with an orange arrow pointing to an android logo. There is a loading bar under this as well. If I let go here it loads up CM7 but if I continue holding on it takes me to the S/W screen.
I've tried this multiple times but I've kinda given up. I even tried individually installing the apks from the GAPPS zip but only a few of them successfully installed.
At a loss .Please let me know what I can do.
Click to expand...
Click to collapse
When it get to the point where "the cyan colored horizontal loading bar" let go of the volume and power button and see if it boots into CWM.
Ok, I tried that and it went to that android logo screen again. Then it went to a black screen and then the cyan LG logo screen. From there it booted up CM7.
I just noticed when I try to boot into Clockwork it erases everything I added to it including contacts and apps I installed.
ae2012 said:
Ok, I tried that and it went to that android logo screen again. Then it went to a black screen and then the cyan LG logo screen. From there it booted up CM7.
I just noticed when I try to boot into Clockwork it erases everything I added to it including contacts and apps I installed.
Click to expand...
Click to collapse
Try rooting process all over again... just make sure battery have plenty of charge and make sure during any of the process there's no interruptions... let us know what happen after that...
Sent from my LG-P999 using xda premium
I will unroot and try again. A few questions though:
I'm reading and it looks like I need to be able to boot into CWR to be able to unroot...is using ROM Manager a safe alternative?
And also, while I followed the instructions for flashing through the thread you provided last time, I read that I may need to erase/wipe certain types of data before I do so to avoid the market problems. Can someone provide me information on that?
I just want to make sure I do this right a second time.
ae2012 said:
I will unroot and try again. A few questions though:
I'm reading and it looks like I need to be able to boot into CWR to be able to unroot...is using ROM Manager a safe alternative?
And also, while I followed the instructions for flashing through the thread you provided last time, I read that I may need to erase/wipe certain types of data before I do so to avoid the market problems. Can someone provide me information on that?
I just want to make sure I do this right a second time.
Click to expand...
Click to collapse
No need to unroot... as long as your computer still detect your phone... just flash everything again... I mean since you want to root... I would just do all the rooting process again... and reflash clock work... don't use rom manager to flash clockwork mod...
Or
And since you can't get into clockwork... you can just try flashing clockwork again... no rom manager
Sent from my LG-P999 using xda premium
Sweet, so I reflashed CWR and CM7 and I got my contacts back and several other minor issues were corrected.
I am experiencing a new problem now though. Whenever I try to download from the market it tells me "[App name] could not be downloaded due to an error."
What can be done to fix this?
ae2012 said:
Sweet, so I reflashed CWR and CM7 and I got my contacts back and several other minor issues were corrected.
I am experiencing a new problem now though. Whenever I try to download from the market it tells me "[App name] could not be downloaded due to an error."
What can be done to fix this?
Click to expand...
Click to collapse
Try flashing Google apps again. Cm7 doesn't include them in their builds.
Sent from my LG-P999
Worked like a charm. Thanks, yall are the best.
ae2012 said:
I will unroot and try again. A few questions though:
I'm reading and it looks like I need to be able to boot into CWR to be able to unroot...is using ROM Manager a safe alternative?
And also, while I followed the instructions for flashing through the thread you provided last time, I read that I may need to erase/wipe certain types of data before I do so to avoid the market problems. Can someone provide me information on that?
I just want to make sure I do this right a second time.
Click to expand...
Click to collapse
Rom Manager is not a safe alternative. Stay with Nvidia ClockworkMod.
Its should be a blue lg logo when you have to let go of the buttons.
Sent from my LG-P999 using xda premium
ae2012 said:
I will unroot and try again. A few questions though:
I'm reading and it looks like I need to be able to boot into CWR to be able to unroot...is using ROM Manager a safe alternative?
And also, while I followed the instructions for flashing through the thread you provided last time, I read that I may need to erase/wipe certain types of data before I do so to avoid the market problems. Can someone provide me information on that?
I just want to make sure I do this right a second time.
Click to expand...
Click to collapse
Every time before you re- flash a rom I would recommend doing a data/factory reset within clockwork recovery. then Wipe your cache. And then even a wipe of the dalvic cache under advanced settings. Then flash the rom then gapps. Then reboot. Its called doing a clean install. It just makes everything smoother when re- flashing. And if your apps ever not update like that again just fix the permissions in clockworkmod then reboot. It usually fixes it. And i don't recommend flashing directly from the rom manager. Do it from recovery instead. Hope this helps.:thumbup:
Sent from my LG-P999 using XDA
[edit]
Sent from my G2X.
Rocking stock CM 7.2.0-RC1
Similar issue, totally different outcome...
Ladies and Gentlemen (and low-lifes),
I have found myself in a similar situation, after recently flashing a ROM, to where I am now unable to boot into CW Recovery. The ROM flashed is working fine but when I attempt to boot into recovery I get a black screen and it never progresses beyond that. I have attempted to reflash of course via NVFlasher and from all indications it's been a successful flash. That said, the results remain the same... black screen.
FYI: I have not yet attempted to flash back to Stock Recovery.
•Current Rom - Owain's Domination v77 (a great ROM by the way)
•Current kernel - Harsh's 3.0.32
•Used Nullifier to prep device for ROM install (as I have been doing for sometime now)
If anyone has any experience w/this issue or any advice going forward I would greatly appreciate it.
UPDATE: (that was fast huh?) .................................................................................................................................................................................................
So I went ahead and flashed the Stock Recovery, tested and got access. I then flashed CWM 5.0.2.0 and to my delight was able to see the CWM console. I let go of the power and volume down buttons and the phone rebooted. Now the ROM will not boot, just sits in a forever cycle on the splash screen and the results continue to be the same as recently mentioned for attempting to get into the freshly flashed recovery.
dark ma++er said:
UPDATE: (that was fast huh?) .................................................................................................................................................................................................
So I went ahead and flashed the Stock Recovery, tested and got access. I then flashed CWM 5.0.2.0 and to my delight was able to see the CWM console. I let go of the power and volume down buttons and the phone rebooted. Now the ROM will not boot, just sits in a forever cycle on the splash screen and the results continue to be the same as recently mentioned for attempting to get into the freshly flashed recovery.
Click to expand...
Click to collapse
Ok, I will bring my concerns to an end now. I forced CWM to remain in play by not letting go of the power and vol. down buttons then using my thumb to see if I could stroll through options in CWM. Once I accessed a few it remain stable. I nullified and re-flashed my ROM and all seems ok in my personal corner of the universe. I am now able to boot into CWM without issue.
Not sure if it's a soft or hard brick, because the darn thing does not turn on at all.
When plugged into the computer, my computer makes the sound when a new device is plugged in and then continuously makes the sound when a device is removed.
Can't turn on phone, so can't get into bootloader or recovery.
Here is what I did:
Ran trickdroid TMOUS 4.0 for about a week no problems.
Just now installed MDJ's new kernel(plus the necessary script and modules), and updated radio(yes, the US radio).
Everything went well, I disabled smokin1337's scripts, and instead enabled setcpu with fairly conservative settings (only maxed at 1.5 Ghz, a screen off profile and a battery percentage profile).
Decided to reboot to ensure changes would stick and BAM! Brick.
I am going to call warranty and get a new one soon. In the meantime, I am going to leave the phone completely off charger and when the weekend is over, try to plug it in and boot into recovery and start from scratch. If anybody has any ideas to try, let's hear them.
Also, I've rooted many many many phones before. I'm not a noob to android modding, and I'm 100% positive I didn't eff something up. I've rooted and installed trickdroid on my sister and my dad's phone too, no problems. They do not have the kernel or the radio.
Must have installed wrong radio which could be perminant brick don't take my word for it though wait for a developer
Sent from my HTC One S using xda premium
k1llacanon said:
Must have installed wrong radio which could be perminant brick don't take my word for it though wait for a developer
Sent from my HTC One S using xda premium
Click to expand...
Click to collapse
I guess so. I just checked the radio files, and they are the same name. I don't have an md5 to check it against though. Bummer
Sent from my HTC VLE_U using Tapatalk 2
Try holding the power button for 10 seconds, you will see the capacative lights flash, let go and quickly hold vol down, while holding vol down press the power button. If that boots into the bootloader, we can bring you back.
Is adb working when pluged in?
Gesendet von meinem HTC One S mit Tapatalk 2
Can not boot
I have the same problem.
My phone stop booting when the HTC logo is on display.
I ´ve flashed the mui rom and because it doesn´t works well i made a factory reset. And now i can´t boot and i can´t flash another rom because I can´t mount sdcard.
edition-driver said:
I have the same problem.
My phone stop booting when the HTC logo is on display.
I ´ve flashed the mui rom and because it doesn´t works well i made a factory reset. And now i can´t boot and i can´t flash another rom because I can´t mount sdcard.
Click to expand...
Click to collapse
Dude don't steal his post make ur own and if ur logo comes up means u should be able to get into bootloader then force a zip to sd card I'm guessing u must have installed wrong image or something else
Sent from my HTC One S using xda premium
edition-driver said:
I have the same problem.
My phone stop booting when the HTC logo is on display.
I ´ve flashed the mui rom and because it doesn´t works well i made a factory reset. And now i can´t boot and i can´t flash another rom because I can´t mount sdcard.
Click to expand...
Click to collapse
There's a guide in the dev section on how to adb push a Rom to the sdcard
Sent from my HTC One S using Tapatalk 2
To format the sdcard flash the stock recovery via fastboot and format the sdcard in the bootloader menu then flash a custom recovery and mount the sdcard via usb or push a zip via adb.
Gesendet von meinem HTC One S mit Tapatalk 2
Thanks for the replies, folks, but let me reiterate again that I CANNOT get into boot loader. It does not power on, no splash screen, no boot up, nothing. I'm assuming the worst, that I either somehow screwed the radio flash or got a bad download of the radio or something. Seems highly unlikely to me, especially since I was able to boot and go through normal operations for a little bit before deciding to reboot. That's the way it is I suppose.
Also, to answer another user's question, the phone does not respond to adb. If anyone else has an idea, I'm willing to try anything. But to repeat, I cannot get to boot loader.
Sent from my HTC VLE_U using Tapatalk 2
How much charge Did the phone have?
Sent from my HTC One S using xda premium
But if the computer recognizes the phone it must be turned on. What happens if you press and hold the powerbutton?
Gesendet von meinem HTC One S mit Tapatalk 2
hansthegeek said:
But if the computer recognizes the phone it must be turned on. What happens if you press and hold the powerbutton?
Gesendet von meinem HTC One S mit Tapatalk 2
Click to expand...
Click to collapse
Yeah that's true
Sent from my HTC One S using xda premium
Does fastboot reboot or fastboot reboot bootloader do anything? Also if you need a real hard reset find the youtube videos that show how to replace the display and disconnect the battery.
Can u get out of a full brick ?
Sent from my HTC One S using xda premium
Okay, finally some good news. I took the phone to the t-mobile store with intention of getting it replaced. While there, the phone magically turned on, but couldn't get past the lock screen. I was a little worried he would say something because of the custom splash screen, but he didn't notice that or the bootloader screen saying "tampered". And didn't say anything when he got to the TWRP screen. I immediately grabbed it and said "I cant take it from here". Now, the phone is working, but the SD card can't be mounted. So I plugged it into my computer and reformatted the SD card. Going to try flashing now.
To answer a couple questions, the phone had about a 90% charge.
Fastboot is a no go, because the phone *did* not turn on and did not answer to adb.
long story short, I believe I had some kind of data corruption on the SD card. Not sure how/why or what fixed it. I've just gotten done adding another ROM to the SD card, and i'm going to reflash and report back. Thank you all for your help.
Any update?
I'm experiencing a similar problem. I didn't fully brick my phone. Just went into a soft brick. Flashed MIUI, but decided I wanted to go back to stock, so I tried to factory reset. Now my SD card cannot be mounted and none of the ROMs I try to flash via Fastboot are going through. I'm stuck on MIUI with no SD card mount.
hansthegeek said:
To format the sdcard flash the stock recovery via fastboot and format the sdcard in the bootloader menu then flash a custom recovery and mount the sdcard via usb or push a zip via adb.
Gesendet von meinem HTC One S mit Tapatalk 2
Click to expand...
Click to collapse
Gesendet von meinem HTC One S mit Tapatalk 2
dung8604 said:
Okay, finally some good news. I took the phone to the t-mobile store with intention of getting it replaced. While there, the phone magically turned on, but couldn't get past the lock screen. I was a little worried he would say something because of the custom splash screen, but he didn't notice that or the bootloader screen saying "tampered". And didn't say anything when he got to the TWRP screen. I immediately grabbed it and said "I cant take it from here". Now, the phone is working, but the SD card can't be mounted. So I plugged it into my computer and reformatted the SD card. Going to try flashing now.
To answer a couple questions, the phone had about a 90% charge.
Fastboot is a no go, because the phone *did* not turn on and did not answer to adb.
long story short, I believe I had some kind of data corruption on the SD card. Not sure how/why or what fixed it. I've just gotten done adding another ROM to the SD card, and i'm going to reflash and report back. Thank you all for your help.
Click to expand...
Click to collapse
A friend of mine had this happen to her S2. I turned on magically the next day by itself.
Gregree said:
Any update?
I'm experiencing a similar problem. I didn't fully brick my phone. Just went into a soft brick. Flashed MIUI, but decided I wanted to go back to stock, so I tried to factory reset. Now my SD card cannot be mounted and none of the ROMs I try to flash via Fastboot are going through. I'm stuck on MIUI with no SD card mount.
Click to expand...
Click to collapse
Don't steal his thread
Sent from my HTC One S using xda premium
I just downloaded the newest CM release (10.0.0 stable) and upgraded. For some reason every time I attempt to boot up my phone it sends me directly into recovery (clockwork). Its almost like a boot loop, but I go into recovery instead. I've tried reflashing to an older nightly version of CM10 that I know works, but it consistently just sends me back to recovery when I go to reboot. I tried a Nandroid restore, same thing. I'm not new to flashing Roms, and went through all the rituals (wiping data/cache, etc). Never have had any trouble flashing Roms in this particular phone.
I can't get into fast boot either, always goes into recovery. Has anyone seen anything like this before? I'm running out of ideas of my own. Any ideas are appreciated. There's a beer in it for the best information leading to the reconstitution of this jobby.
Sent from my Nexus 7 using xda app-developers app
CounterSolar said:
I just downloaded the newest CM release (10.0.0 stable) and upgraded. For some reason every time I attempt to boot up my phone it sends me directly into recovery (clockwork). Its almost like a boot loop, but I go into recovery instead. I've tried reflashing to an older nightly version of CM10 that I know works, but it consistently just sends me back to recovery when I go to reboot. I tried a Nandroid restore, same thing. I'm not new to flashing Roms, and went through all the rituals (wiping data/cache, etc). Never have had any trouble flashing Roms in this particular phone.
I can't get into fast boot either, always goes into recovery. Has anyone seen anything like this before? I'm running out of ideas of my own. Any ideas are appreciated. There's a beer in it for the best information leading to the reconstitution of this jobby.
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
Getting into fast boot is tricky...hold down arrow and push power, then release vol after boot.
Are you flashing boot.img properly in fastboot?
OK. I got it semi sorted out. It turns out there is a bug of some kind, I am not sure if it is special to the One S or what, but it is to mine. CWM gets thrown into a sort of boot loop if the device is charging while attempting to restart, and won't boot either into the rom nor into fastboot. It won't respond to adb either. It just keeps going into recovery. And it won't shut off. This happens when charging for some reason.
After I took the USB cable out I reset it with volume +, volume -, and power. I guess HTC put that little trick in there to simulate removing the battery since you can't take the battery out of the back. That effectively shut the phone off. Then I was able to get into fastboot and connect with adb. I put Team Win Recovery on there instead of CWM for now, and got into recovery. Wiped everything, and flashed the extra rom I had on there.
I am still unable to flash CM10 stable, it just goes into bootloop if I try, but at least I have my phone back. Hopefully I will be able to figure out if there is a way to kick start it on there, or whatever bug is solved. Look forward to trying it when its (or I'm) not broken.
Sent from my Nexus 7 using xda app-developers app
CounterSolar said:
OK. I got it semi sorted out. It turns out there is a bug of some kind, I am not sure if it is special to the One S or what, but it is to mine. CWM gets thrown into a sort of boot loop if the device is charging while attempting to restart, and won't boot either into the rom nor into fastboot. It won't respond to adb either. It just keeps going into recovery. And it won't shut off. This happens when charging for some reason.
After I took the USB cable out I reset it with volume +, volume -, and power. I guess HTC put that little trick in there to simulate removing the battery since you can't take the battery out of the back. That effectively shut the phone off. Then I was able to get into fastboot and connect with adb. I put Team Win Recovery on there instead of CWM for now, and got into recovery. Wiped everything, and flashed the extra rom I had on there.
I am still unable to flash CM10 stable, it just goes into bootloop if I try, but at least I have my phone back. Hopefully I will be able to figure out if there is a way to kick start it on there, or whatever bug is solved. Look forward to trying it when its (or I'm) not broken.
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
The One S isn't offically supported by CWM. It sounds like you need to try and flash the boot.img in fastboot.
Try TWRP...it will be better
Sent whit HTC ONE S
That's weird. CM10 comes up as an update...
Either way, I tried flashing the 11/11/2012 nightly through twrp and came up the same thing, would just bootloop and not go into the rom. Fortunately I could still access both recovery and fastboot, so I went back to a previous nightly from last week, and after a (painfully long/manual) titanium restore, I'm back to normal. I'll have to investigate what is going on later when I have some extra time to commit to it.
Sent from my Nexus 7 using xda app-developers app
Yeah dc211 was right. I'm using hboot 1.14, had to go and flash boot.img in fastboot. Install went smoothly after that. Thanks for the input y'all.
Sent from my Nexus 7 using xda app-developers app
boot loop
CounterSolar said:
That's weird. CM10 comes up as an update...
Either way, I tried flashing the 11/11/2012 nightly through twrp and came up the same thing, would just bootloop and not go into the rom. Fortunately I could still access both recovery and fastboot, so I went back to a previous nightly from last week, and after a (painfully long/manual) titanium restore, I'm back to normal. I'll have to investigate what is going on later when I have some extra time to commit to it.
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
Before you flash this you need to remove "qrngd" file from the rom . The file is located at system-bin-qrngd.
I was able to flash 10.0.0 without removing qrngd. So far it hasn't been a problem. I read somewhere that file is some sort of random number generator, but that it isn't clear whether its even used anymore. Also, they say its more of a problem with earlier nightlies, especially with people using HBOOT < 1.14. It might be just junk DNA in the system files, or they may have patched the problem. I will keep my eye on it though, and will report back if I get any spooky behavior.
Sent from my Nexus 7 using xda app-developers app
jazz452 said:
Before you flash this you need to remove "qrngd" file from the rom . The file is located at system-bin-qrngd.
Click to expand...
Click to collapse
That was fixed in the 11/09/12 nightly, so its not an issue anymore.
http://forum.xda-developers.com/showpost.php?p=33867937&postcount=2209
I realize there are multiple threads like this but throughout all of them I have not found any that relate to my issue or a combination of them. If I have missed one I apologize in advance and please direct me to that thread then. I was running steel droid what I thought was 5.5 ICS but it looks like it is 5.1 according to the forums. I was previously running steel droid 4.5 GB. I was switching back to 4.5 because I could not get wifi hotspotting to work. I forgot to wipe my cache and went to install 4.5 and I am stuck in bootloop. X+Power gives me the android error screen, M+Power allows me into the main menu but I cannot use AP fastboot, SBF motorola will not pick up my phone and the screen will show a connection to the USB cable. I've never had a problem before but also have never forgotten to wipe the cache so any thoughts would help.
m3schz8! said:
I realize there are multiple threads like this but throughout all of them I have not found any that relate to my issue or a combination of them. If I have missed one I apologize in advance and please direct me to that thread then. I was running steel droid what I thought was 5.5 ICS but it looks like it is 5.1 according to the forums. I was previously running steel droid 4.5 GB. I was switching back to 4.5 because I could not get wifi hotspotting to work. I forgot to wipe my cache and went to install 4.5 and I am stuck in bootloop. X+Power gives me the android error screen, M+Power allows me into the main menu but I cannot use AP fastboot, SBF motorola will not pick up my phone and the screen will show a connection to the USB cable. I've never had a problem before but also have never forgotten to wipe the cache so any thoughts would help.
Click to expand...
Click to collapse
Not wiping cache won't give you boot loop lol just go back into recovery wipe everything and flash a working ROM solved :thumbup:
Sent from my SCH-I500 using Tapatalk 2
bbrad said:
Not wiping cache won't give you boot loop lol just go back into recovery wipe everything and flash a working ROM solved :thumbup:
Sent from my SCH-I500 using Tapatalk 2
Click to expand...
Click to collapse
I would but I get android error screen with exclamation mark each time regardless of how I access recovery X+Power or vol +,- and Power then going to recovery, I wouldn't have thought that not wiping the cache would have been the cause but it was the one step I didn't do that I normally always do so I was just adding it in for information but thanks for the know how that it wasn't the cause. Any other thoughts since I cant even get into my backup ROM or recovery, I have another SD card not sure if my SD card has become fried for some reason, I will be trying that to see if maybe that is all it is.
m3schz8! said:
I would but I get android error screen with exclamation mark each time regardless of how I access recovery X+Power or vol +,- and Power then going to recovery, I wouldn't have thought that not wiping the cache would have been the cause but it was the one step I didn't do that I normally always do so I was just adding it in for information but thanks for the know how that it wasn't the cause. Any other thoughts since I cant even get into my backup ROM or recovery, I have another SD card not sure if my SD card has become fried for some reason, I will be trying that to see if maybe that is all it is.
Click to expand...
Click to collapse
Well I'm on a Samsung device but we have a program you load files in and you can flash your device back to stock do you have something like that?
Sent from my SCH-I500 using Tapatalk 2
Droid 3 stuck in bootloop'
bbrad said:
Well I'm on a Samsung device but we have a program you load files in and you can flash your device back to stock do you have something like that?
Sent from my SCH-I500 using Tapatalk 2
Click to expand...
Click to collapse
Yep but phone isn't picking up my data cable and how ever many issues that have come about here, I think I am SOL but gonna try an SD card hoping that it is just a bad SD card or something like that. May end up having to use part of that great tax return also, thanks for the help, I'm going samsung next, that whole fore sight wasn't there two years ago.
In it's current state, is it in any way possible to tell that it is rooted? Is the boy animation stock or a different one? Motorola might repair it for you if you can't tell that it's been rooted
Sent from my HTC6435LVW using xda app-developers app
Droid 3 stuck in bootloop
dj2muchxx said:
In it's current state, is it in any way possible to tell that it is rooted? Is the boy animation stock or a different one? Motorola might repair it for you if you can't tell that it's been rooted
Sent from my HTC6435LVW using xda app-developers app
Click to expand...
Click to collapse
Unfortunately you can easily tell that it is not stock ROM by bootloop
Well your computer should recognize your droid that's a common problem with Odin and Samsung one of these steps always work so try then and seen if we can't get your droid recognized NUMBER 4 WILL WORK 99% OF THE TIME BUT TRY THE OTHER METHODS FIRST 1. Use the stock cable or try a difrent port 2. If its possible on your program take out the battery and SD card as leaving them in course problems 3. Run the program as aminstrative 4. Plug the phone in and have it in download mode or whatever you call it WHILE THE COMPUTER IS BOOTING Up This will force the computer to recognize it not the best method but it always works
Sent from my SCH-I500 using Tapatalk 2
Droid 3 stuck in bootloop
bbrad said:
Well your computer should recognize your droid that's a common problem with Odin and Samsung one of these steps always work so try then and seen if we can't get your droid recognized NUMBER 4 WILL WORK 99% OF THE TIME BUT TRY THE OTHER METHODS FIRST 1. Use the stock cable or try a difrent port 2. If its possible on your program take out the battery and SD card as leaving them in course problems 3. Run the program as aminstrative 4. Plug the phone in and have it in download mode or whatever you call it WHILE THE COMPUTER IS BOOTING Up This will force the computer to recognize it not the best method but it always works
Sent from my SCH-I500 using Tapatalk 2
Click to expand...
Click to collapse
Thanks step 4 ended up being the working method, happened again when loading gingerbread back on, so I walked through it again, removed ICS from memory card wiped phone completely and then loaded gingerbread back on and finally had success. Thanks for all the help
m3schz8! said:
Thanks step 4 ended up being the working method, happened again when loading gingerbread back on, so I walked through it again, removed ICS from memory card wiped phone completely and then loaded gingerbread back on and finally had success. Thanks for all the help
Click to expand...
Click to collapse
NP if you ever need anything just ask
Sent from my SCH-I500 using Tapatalk 2