yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] Garoun:
Thanks for the info steps I've performed since leaving the post and reading yours, in order of execution:

*** Last night before making post (adding more detail now that I can think) ***

Prior to the root I had the issue a lot of people had reported in that the phone was somewhat temperamental at which cords it would charge on but 'most' of my micro's worked fine. Other than that I could get to adb and the sdcard without any issues.

The full sequence of events leading up to this is as such:

- Made sure I was fully charged

- Performed the root as mentioned in the OP

- Booted into CWM first thing and made a backup

- Used TiBu to restore some of my market apps (user only, no system apps) from my old rooted Incredible

- Finished setting up the rest of my phone

- Installed ROM Manager to update CWM to the newest version

- Installed the rest of my normal apps, then booted up TiBu and backed up all apps and their settings (user only, no system apps)

- Played with my phone for the next few hours with a reboot here and there if I installed an app and it's widget didn't show up

- About an hour after that I installed "market.android.com/details?id=com.rageconsulting.android.lightflowlite"

- After it had installed I clicked open and phone immediately jumped to the booting graphic and froze with no button response at all

- Pulled battery and rebooted, it showed the google logo (with the lock at the bottom), made it past the boot screen, got to the lock screen and no buttons or swipe action would take me to home screen

- Pulled battery and attempted to get into fastboot/recovery to no avail

- Attempted to get it talking to my pc and outside of the battery out OMAP4440 device manager message gave up for the night

- Uninstalled PDAnet, Samsung drivers, then used USBDeview to ensure I got them all, rebooted, reinstalled the Samsung drivers (Samsung_USB_Driver_for_Moblie_Phones_v1_4_6_0.exe), rebooted, attempted to plug in phone and same OMAP4440 message

- Tried pulling the SIM and battery for a few minutes with same results

- Left it on the charger overnight so I could get some rest (same time when I left the OP)

*** Starting this morning at 10AM ***

- Let the phone sit on the charger overnight with the battery in

> No change

- Pulled battery for 10-15min then put battery back in and attempted to fastboot

> No change

- With battery in, tried plugging it back into my pc

> No change or response from Device Manager

- With battery out, tried plugging it back into my pc

> I attempts to installed drivers but always fails, I've attached a picture of the device manager during this situation

View attachment 835514

And an image from USBDeview:

(The instance ID that is chopped off: USB\VID_0451&PID_D010\6&1f916cd7&0&7)

View attachment 835553

At this point I'm still dead in the water
[Samsung Galaxy Nexus] Garoun:
Ok, as a freak of nature I got to fastboot! I was doing a combination of trying to get the the OMAP driver to installed using samsung/pdanet drivers. A lot of plugging and unplugging with the battery out. Put the battery in one last time with the usb plugged in and finally got the oh so lovely 'vibrate' and fastboot loaded.

In the process of recovering to the original backup I made before the crash. Will let you know what happens from there.

I can get into the phone and restored my CWM backup from just before root, going to try flashing it back to stock and starting over after I give it time to charge fully.

Edit 11:53: Flashing the stock image back onto the phone and relocking the bootloader to see if the LED is still broken.

Edit 1:26: Phone is now locked and stock, trying to debug the LED since it use to come on while charging or if I was in a call. All it does now is one short blink and then nothing.

Edit 1:40: Looks like things are behaving again so back to root.
[Samsung Galaxy Nexus] Garoun:
And back to the original spot I started at :(

When I tried to root, it got past unlocking, during the root I completed the steps to let it keep loading but then it went into a boot loop and kept jumping between the animation, vibrate, black google screen. After it did that a few times in went completely black and now back to no load at all (fastboot or recovery).

I've tried the battery pull and wait, but seems I'm back where I started :(. Ah the joys we put ourselves through out of the quest for knowledge :).
[Samsung Galaxy Nexus] mskip:
Did you use my ToolKit for the second root or another root method?

What model and build are you on?

I dont see how the root method could make your phone not load into fastboot or adb as it only boots (not flashes) an insecure boot image to then push the 2 files needed.

Are you back running again or still nothing? If you get the phone running again then flash back to stock and exchange the phone. Just tell them the phone goes dead now and again.

Mark.
[Samsung Galaxy Nexus] Garoun:
Method: Yep, I used the Toolkit for the second try after using it to return to stock and locked phone. All drivers were working correctly but the main difference between the 1st time and second I did the root before trying to flash the CWM onto the device.

Version: (this is a snapshot from system info before the first root but it was 4.0.2 LTE/CDMA)

View attachment 836027

I honestly don't think it was the root that did it, since the phone was running stable for hours after the original root(including multiple reboots and charging). It wasn't until my LED Notification light started acting up that things went pear shaped, which started with Trillian then once I ran the led app that put the nail in the coffin. It was also having issues with recognizing most of my USB cables, only really had success with my included cord.

As from prior posts I somehow made it come back to life but could not achieve the same success with the 2nd SOD. Both times had the same case of seeing Device manager pop up the OMAP4440 pop up momentarily if no battery was installed, but not USB response at all by the PC if battery was in. The one time it worked I was in the middle of reinstalling PDAnet and the Device manager repeatedly tryed to reinstall the OMAP driver even though it failed every time but inserting the battery (while still connected) made the phone wake up.

I ended up biting the bullet and taking it back for warranty replacement. At least it was pretty much wiped clean (no titanium backups) at that point since I had just unlocked it. Lady up front said, "you broke it already", I responded with, "Well it was having issues charging on any cable other than what it came with so I didn't bother bring it in since I could get a charge, but after getting the rest of my apps installed I tried to open one and it went to that rainbow colored screen when you turn it on and froze. Tried pulling the battery but still wouldn't work". I simply answered the questions asked. Unfortunately, I'm going to hold off on rooting for now until I know my phone is completely stable since first one was having occasional oddities before I even touched the boot loader.

Considering I was only rooting and not doing any other customizations, only wanted to be able to backup/restore my apps and their data, my research made me think the SOD wasn't normal.

Am I correct in thinking that none of the actions made in ":applyroot" from the runme.bat should cause fastboot and/or ODIN to be unreachable if it fails at any point? Hell I don't even think a corrupt recovery should prevent it from at least making it to ODIN? I hadn't even gotten to the ":deleterecoveryrestore" step.
[Samsung Galaxy Nexus] NPuter:
wow - I'm definitely curious as to what happend here. Could it have been defective hardware?
[Samsung Galaxy Nexus] Garoun:
I'm leaning heavily towards defective hardware. The way my led and usb port started acting seemed like I had a short or something. The fact that it tried to connect to my pc with the battery out has me beyond perplexed.

Had done a lot of reading and researching to try to understand all the possible pitfalls, but this one had me dumbfounded.

I'm curious to see the reply to the questions on my previous post. I'll gladly answer any questions I can if it'll help someone else in the future. :)
[Samsung Galaxy Nexus] mskip:
Nothing in the rooting procedure in my ToolKit would harm the system. First it boots (not flashes) an insecure boot image to gain temporary adb root access. 2 files are then pushed to the phone and permissions are set. After a reboot the only thing left on the phone is the 2 files (su and superuser.apk). These files have been used thousands of times to grant root for phones so there is nothing wrong with the way they work.

The Galaxy Nexus is pretty much unbrickable in that it should always be able to boot into fastboot mode as it it is totally outside the operating system and cannot be overwritten by flashing.

Dont be put off by your bad experience as im sure it was a very rare thing to happen :)

Mark.
[Samsung Galaxy Nexus] adesos:
my god ....i have the same problem as you ...but now i can't find any omap4400 driver....and i don't what the timing to put battery back to the phone ...
[Samsung Galaxy Nexus] Garoun:
I'm just letting the phone rest for a while to make sure it's fully stable. I'm sure it'll eventually get rooted again (incredible has been ripped for a while now), for three time being I'll just have to use adb to push/pull my important app data.

Ade, I don't believe there is an omap driver we have access to, since my research has turned up that it's essentially the chipset trying to initialize. I am probably wrong, but for now I believe only a provider/manufacturer has that access.
[Samsung Galaxy Nexus] Firerouge:
Literally the same thing happened to me to.

Phone was rooted 4.0.2 with CWM recovery installed.

Turned off my phone this morning after charging all night.

Came back an hour later and saw the white full battery icon on the screen. Tried to turn it on and would not turn on.

Tried going into fastboot to no avail.

When plugged into PC all I got was the OMAP thing under device manager.

Took the phone to Verizon, they got it to boot up to the boot logo after removing the battery and then putting the battery in while holding the power button. The phone crashed after booting past the boot logo, had it replaced.
[Samsung Galaxy Nexus] Garoun:
So based on 3 quick accounts of this issue I'm wondering if there is a critical flaw that only pops up after the bootloader is unlocked.

Adesos and Fire, did you two use mskip's toolkit or another method?

In my case, the only common factors between my two roots was unlocking the boot loader and getting through the initial root. On the 2nd root it hardlocked before I had renamed the recovery reset file or installed CWM.

Trying to figure out some common ground.

So mship knows exactly what got completed before the hardlock, these are the parts that got completed from the batch before the bootloop.

fastboot-windows.exe oem unlock

fastboot-windows.exe boot root\boot_LTE_ICL53F_insecure.img

(had an issue with needing to restart the program at this point since I had to reboot into Android and enable usb debugging, did not have this problem the first time)

adb-windows.exe root

adb-windows.exe remount

adb-windows.exe push root\su /system/bin

adb-windows.exe push root\Superuser.apk /system/app

adb-windows.exe shell chmod 06755 /system/bin/su

adb-windows.exe shell chmod 06755 /system/app/Superuser.apk

echo Completed. Now booting back to FastBoot Mode:

echo.

pause

(The moment I hit Enter after this to kick off the reboot is when I got stuck in a boot loop, and it finally hard locked after about 6 reboots since I didn't want to battery pull unless it never stopped)

adb-windows.exe reboot bootloader

Again, the first root worked fine until I tried to test the LED notification light that had started acting up.

Hunh, now I wish I had a backup battery so I could see if something got screwed up with the battery since the phone acted like it was shorted or something when the battery was installed. (fact that device manager popped up the omap only when battery pulled)
[Samsung Galaxy Nexus] Firerouge:
I did indeed use the toolkit.

The first time I did it I unlocked bootloader. Phone rebooted tweaked it a bit.

About an hour later launched the tool before rebooting the phone into fastboot, tried to run the root exploit, all steps failed though since the phone hadn't been in fastboot first. So I rebooted into fastboot and then ran the tool again successfully.

Root was applied, then deleted the recovery restore file, then put CWM recovery on it.

I never once booted to CWM recovery. The next day the phone stopped working.
[Samsung Galaxy Nexus] adesos:
hi, did you get any idea to restore the dead phone???

13 days past away, and i'm only waiting to jtag flash a bootloader to my phone.....

1: i unlocked my bootlloader

2: i rooted my phone

3: fastboot flash recovery

and i'm very likely to know, how to get in the fastboot mode?

(1,with the battery in or out?

2, should i press any button when i plug the usb cable to phone?

3,or what esle i should do?)

thank you.....plz give me some answers....i hate to wait jtag info to flash my phone....it will be 1 month later or more....
[Samsung Galaxy Nexus] Garoun:
If the normal tests and attempts to get the phone at least booting, there had been mixed results of holding the power button only while putting the battery in, but the issue is honestly a toss up since I haven't heard of any other people with this problem.

I've been so busy at work I haven't bothered trying to root my phone again or track down more people with the same problem.

Your best bet may honestly be sending it in and take your chances.
[Samsung Galaxy Nexus] adesos:
yeah i'm busy in my work too, so my reply is late........

thanks for your reply

you mean that....

you just put battery in ...... and hold the power button......and plug usb cable to computer so you get in the fastboot mode???
[Samsung Galaxy Nexus] mskip:
You need to HOLD the volume up and down buttons then press the power button to get into fastboot mode.

MArk.
[Samsung Galaxy Nexus] xenspidey:
HELP!!

I have the exact same problem as stated before, however I don’t think it has anything to do with the rooting process. I unlocked and rooted the old fashion way weeks ago and have been running very stable since. However, yesterday I received my extended battery which has worked well and today I got a couple extra cables. I was charging both of my batteries with my new cable for 4-5 hours this morning at work. I was going to lunch and powered off my phone to switch out the batteries. Now my phone won’t turn on at all, with either battery. I have tried both batteries, with the OEM cable… nothing. If I have the battery out and attempt to plug into my PC I get the “looking for OMAP4400” pop up. I’ve tried every combination listed previously… has anyone got any new light to shed?
[Samsung Galaxy Nexus] gannon82:
boot problem

galaxy nexus 4.0.2 version boot loop cant even get to view files on comp constant loop when press vol up and down and power go to boot loader or recovery mode all i get is a android symbol with a explanation mark !!

please help
[Samsung Galaxy Nexus] mskip:
Have you unlocked your bootloader? Rooted? Flashed cwm? Have you flashed any Roms or Kernels on it?

More info please.

Mark.
[Samsung Galaxy Nexus] comicbookguy72:
very similar prob here!

Ok, so I've flashed several roms with CWM onto my Nexus since i rooted it in late Dec without problems, so when the MCR Dev kitchen went up i baked a Rom, loaded it up, did all my backups, and started to flash.

CWM booted to recovery and errored telling me to check my rom manager version number

so i uninstalled & reinstalled CWM & reflashed the recovery.....

which hung at about 95% complete for about 10 minutes,

until i rebooted the phone

or tried to reboot it, because now it's dead- no charging icon, no power button response, no fastboot or adb access

even after removing the battery for 1/2 an hour, tried booting with/without battery, plugged and unplugged from usb......

getting "omap4440" connect/disconnect in device manger, but it cant find the driver.

total noob with adb & fastboot, because i've never needed them before, through rooting my Vega, Desire and GNex repeatedly

HHHHHEEEEEEELLLLPPPPPPPPP! :(
[Samsung Galaxy Nexus] mskip:
Your phone definitely wont do anything without the battery plugged in, even if you have the usb cable attached.

Did the battery have a good charge in it when all this happened? Have you tried plugging the usb cable into a different port? Or trying a different cable to see if you get the charging symbol on the phone.

The only thing I can think of right now is to pull the battery from the phone and leave it overnight. Then plug it back in, hold vol down and vol up while pressing the power button to try and enter fastboot mode. If that works then connect the usb cable and use my ToolKit to flash a new recovery image or reflash a stock rom.

If you dont get any life out of your phone then get hold of another battery from ebay or somewhere similar and see if that helps.

Mark.
[Samsung Galaxy Nexus] comicbookguy72:
battery was at least 60%,

getting the rapid "attach/unattach" dings from windows as omap4440 appears & disappears in device manager.

tried different cables and ports, with & without powered hub all previously confirmed as working with the GNex, also tried official mains charger. no activity with any.......

battery has been out of phone for 36hrs due to other commitments, just about to try again.

tried the toolkit, but cant install drivers as phone is not recognized as adb or fastboot device...
[Samsung Galaxy Nexus] darrylhadfield:
And another one bites the dust...

No idea what happened.. put it into the desktop dock last night, when going to bed.. and when I woke up, it was dead.

I've had it boot into ODIN mode twice (but can't get it to boot back to that now); I've also had it reboot once - with volume up plus power - but when I unplugged the USB cable, the screen was flickering badly and it automatically started powering down.

Not a happy camper... esp. since I bought it form a store that apparently imported it from the UK - Samsung won't honor the warranty.

We'll see if the place I bought it from will honor the 4 year extended warranty I bought with it.

In the meantime.... anything further? this thread looks to be ~4mths old...

Help.. for the love of all things Googly, help!
[HTC Rezound] zonbal33:
I unlocked my bootloader following all the directions form HTC. I them followed these to get perm root:

The first time nothing happend and it just sat there and hanged. I exited and tried again now I get this:

Whats going on? Am I rooted now?

I then tried this again after, I doubled clicked the .bat file and got this, just sits here:

I made sure HTC Sync is not on, phone is in charge mode. oneclickroot is here: C:\Android\OneClickRoot_1.1
[HTC Rezound] con247:
Look at my rooting guide I just posted in Development section. It doesn't use OneClickRoot.
[HTC Rezound] zonbal33:
Ok I'm guessing this one? http://xdaforums.com/showthread.php?t=1418653

I tried that oneclickroot already, it didnt effect my phone in any way, right?

Why cant I use oneclick?
[Samsung Galaxy Nexus] Shamrock13:
Is it possible at all? I know there was a hacked APK out there in around July/August, but I'm wondering if I can root with the latest version of Videos and not lose access.

I like the ability to rent from my phone and toss it up on the big screen.

That's why I haven't rooted it yet! D:
[Samsung Galaxy Nexus] joeykrim:
I contemplated making an application to assist with this process of "hiding" root in order to run Google Videos. There were too many limitations which discouraged me from being able to make the application as high quality as I wanted.

This process ends up being a cat/mouse type of game and will probably continue to be. Everytime a work around is devised for bypassing the root check in the Google Videos apk, they update the apk and step up the complexity of their process.

The best work around is probably to unroot the device, then run Google Videos. And going forward, to always make sure the device is unrooted whenever Google Videos is ran.

Otherwise, I don't think there is a sure fire solution to this process. And any modified versions of Google Videos will only be temporary solutions.

If I'm completely wrong here, I'm sure somebody with better information will post up to correct but the above information is from my personal experience studying the issue over the last few months.

Hope that helps!
[Samsung Galaxy Nexus] ogdobber:
i am rooted and can rent and watch videos just fine on the gnex.
[Samsung Galaxy Nexus] Shamrock13:
Really?! D:

I might have to try rooting the phone then!
[Samsung Galaxy Nexus] ogdobber:
yes, 100%.

i have to say the quality through mhl cable to tv is quite impressive as well:D
[XPERIA X10 Q&A, Help & Troubleshooting] AX10i:
Are there any major differences concerning the picture / video quality between these two firmwares?

Sent from my X10i
[XPERIA X10 Q&A, Help & Troubleshooting] NuriJ:
2.1 vs 2.3.3 vs 2.3.4 vs 2.3.5 vs 2.3.7 (except 1.6) = No difference if camera work properly on all versions.
[XPERIA X10 Q&A, Help & Troubleshooting] AX10i:
Hum, I thought SE "improved" the camera with every new firmware release.

In that case, I think I'll go back to 2.1.

Sent from my X10I
[XPERIA X10 Q&A, Help & Troubleshooting] neoxx3m:
2.3.3 is way better then 2.1.

Sent from my xperia "z10i" :)
[XPERIA X10 Q&A, Help & Troubleshooting] laneyofdeath:
The camera itself doesn't improve it still 8.1 mp if thats what u mean :-)

Edit: yeah gb is better than eclair thats why it's an upgrade. It ain't gonna improve resolution though.
[XPERIA X10 Q&A, Help & Troubleshooting] 0000alex0000:
well all i know is that camera focus speed in 1.6 is the fastest so far
[XPERIA X10 Q&A, Help & Troubleshooting] neoxx3m:
Improved camera doesn't mean only more mpx.U have ****ty 5 mpx cams(HTC Hero) and much better 5 mpx like one on Samsung galaxy s.(this is only example).Somethimes in OS upgrades developers improves camera as well(better colors,less noise etc.).:)

Sent from my xperia "z10i" :)
[XPERIA X10 Q&A, Help & Troubleshooting] neoxx3m:
In video mode or?

Sent from my xperia "z10i" :)
[XPERIA X10 Q&A, Help & Troubleshooting] neoxx3m:
Nevermind.:)

Sent from my xperia "z10i" :)
[XPERIA X10 Q&A, Help & Troubleshooting] AX10i:
That's what I was talking about.

I just asked because I read somewhere that 2.1 is better in camera quality.

Is it true?

Sent from my X10i
[XPERIA X10 Q&A, Help & Troubleshooting] laneyofdeath:
All I can say is are u guys expecting our phone to have 16mp camera by time ics arrives or somethin? Os update isn't gonna make ur camera have higher resolution. It just improves ui and how it implemented, things like that. I suppose with advance in tech it could make image clearer but the resolution ain't gonna change. :-)
[XPERIA X10 Q&A, Help & Troubleshooting] AX10i:
Everyone knows that the resolution won't change with software improvement since it's hardware related. But colour management, contrast, detail, etc. can, and that's what my question is about.
[XPERIA X10 Q&A, Help & Troubleshooting] evo_zheng:
2.3 have faster focus speed~
[XPERIA X10 Q&A, Help & Troubleshooting] ashishshevale:
camera feature change from eclair to gingerbread

what I know is gingerbread removes the smile detection and some other feature :confused: in xperia x10 which eclair have and works correct :)
[XPERIA X10 Q&A, Help & Troubleshooting] neoxx3m:
Same image quality without some options(like smile detect)

Sent from my xperia "z10i" :)
[XPERIA X10 Q&A, Help & Troubleshooting] Olao99:
I can't find any difference between the stock camera app quality from 2.1 to 2.3....
[XPERIA X10 Q&A, Help & Troubleshooting] neoxx3m:
Because they have same quality,nothing changed.

Sent from my xperia "z10i" :)
[XPERIA X10 Q&A, Help & Troubleshooting] Bwyan Benton:
I just flashed back to 2.1 and this is one of the reasons. The video camera on 2.3 sucks, I can barely hear my recordings, on 2.1 its back to being nice and loud.