yashsingh1/xdaforums huggingface dataset:
[HTC Sensation] T-Macgnolia:
I keep seeing people post about being rooted and flashing the OTA update. Now someone please, please, please correct me if I am wrong, but when you flash as new ROM, unless you just flash a new system via ADB fastboot commands, you flash a new kernel and all every time you flash a new ROM. So therefor it does not matter if you are rooted cause the rooted kernel will be replaced with a new ROM. For those out there that do not know the kernel is contained in the boot.img of a ROM. Now in a s tock ROM it is. Of always named boot.img but it is still pretty much the same thing with maybe a little more than a custom TOM's would be. So please people stop wording about being rooted, it does not matter. If you are on the correct stock ROM and have the stock recovery you are good to go to flash and run the OTA. It does not matter if you are S-off or S-on either.
[HTC Sensation] EddyOS:
It does 100% matter as otherwise the SU app/binary will still be present and potentially cause issue to the 'stock' ROM. Go look at the Desire forums all over the net for examples as to why you shouldn't flash an OTA onto a rooted handset
[HTC Sensation] killingflowers:
So as long as you're stock recovery, and stock ROM, but s-off, it shouldn't have any bearing whether or not you upgrade ota... Right?
[HTC Sensation] T-Macgnolia:
Ok I well look into this further when I get home from work. I have not looked at the Desire forums yet, bit I will later today. My question is though are the Desire users having to use the stock recovery, or has someone made a flashable .zip file for them of the OTA? If so this could have something to do with the troubles. Like I said I will check into this further this evening. I still say it should not as the kernel is replaced when you flash the OTA update, bit I could very well be wrong.
[HTC Sensation] EddyOS:
It's not that you can't do it, you can, it's just not recommended. By all means try it but should it go wrong flashing an RUU is all that would work
[HTC Sensation] T-Macgnolia:
I totally understand what you are saying, but flashing stock is not the only way to fix it, it is just the easiest and most user friendly way to fix it. It is pretty much a one click fix, and that is because of the RUU it self. When you flash via a RUU the utility runs a Task 28 on the NAND memory first meaning the NAND is totally wipped, meaning all partitions, before the ROM is flashed. Now you can also use ADB to remove and reflash all partitions,Splash 1(mtdblock0), recovery(mtdblock1), boot(mtdblock2), system(mtdblock3). cache(mtdblock4), userdata(mtdblock5).

Now back to the question about being rooted, I still have not got home yet to get on my computer to look at the desire forums. Now from what I know root is acheived on the kernel level cause that is what root is. It allows for direct communication with the kernel, again correct me if I am wrong. Now I understand that Superuser app binaries would still be present if you flashed just the system. But if you flash a whole new ROM wich is what the OTA update does, then the kernel is replaced with the kerneel in the OTA update, which by is either a completely new kernel or a modified kernel that HTC has made to work with ICS. I have not had time to look into wich one it is, but from my experience of trying to help port the SDK of ICS to the Sensation it is probably a completely new kernel.

Anyway I will have to do some research on the differences between stock recoveries and custom recoveries. Specifically the processes the recoveries run when flashing a ROM from SD card, and just what all is in the OTA update files. Once I get to do this I will be more able to give a hard core answer to this question. Oh and thinks to the EddyOS for helping to get me back into digging around in ROM files and learning more about how Android works. ;)

Edit: I totally forgot to mention JTAG, this is another way that you could fix the problem, all be it sort of a major over kill for the problem, but still a fix.
[EVO 4G Q&A, Help & Troubleshooting] Naturesretard:
So I was having issues with MikG and my settings.... Reinstalled aosp system apps by accident over sense system apps and it kept popping up with error messages....

So I wiped everything and reflashed MikG 3.xx and it boots up... But all I see is the wallpaper and status bar. I see no clock/apps, and am never prompted with entering my google info and whatnot.

I also deleted the ROM and put it on again thinking it might be corrupt but I still get this problem. Wtf just happened? Did I just brick my phone?

Gonna try and flash my old Deck 1.3d rom and post back with results
[EVO 4G Q&A, Help & Troubleshooting] louforgiveno:
did you factory reset wipe?
[EVO 4G Q&A, Help & Troubleshooting] Naturesretard:
I factory reset from within amon ra and wiped each thing individually as well. Flashed the full wipe version of MikG 3.11 and it proceeded to wipe everything again. Everything installs fine, but when it boots, it just shows the MikG walpaper, and the notification bar. No apps, no clock, no new user "welcome to android" prompt either. All I can do is turn the screen on and off.... I have to pull the battery to turn the phone off.

Putting my Deck 1.3d nandroid on my sd card as I type and am going to flash in just a minute to test and see if I can even boot anything...
[EVO 4G Q&A, Help & Troubleshooting] ItsLasher:
You sure you got the FULL WIPE version? If you flashed the UPDATE version you will get these exact same problem.
[EVO 4G Q&A, Help & Troubleshooting] Naturesretard:
I got both.... originally thinking it was an update TO the ROM itself. (idk why lol) Decided to keep it for if I ever have to reflash the main rom due to a user error....

But no, I made sure I was flashing the full wipe version. You think I should redownload again and try it out? I had the file saved on my friends laptop and hadn't touch it since I put it on my SD card so.... figured I could just delete the one on my SD card and retransfer
[EVO 4G Q&A, Help & Troubleshooting] Naturesretard:
Just restored my Deck 1.3d and its booting as I type. Will post back with details.
[EVO 4G Q&A, Help & Troubleshooting] ItsLasher:
I'd do a complete wipe on everything and start from scratch. I just got a new SDcard and formatted it and did a fresh install of MikG 3.11 and it runs like no other.

Back up your SDcard to a PC and format and start fresh. I noticed a HUGE difference in function and performance although it sucked loading almost 10gigs of music back on.....lol
[EVO 4G Q&A, Help & Troubleshooting] Naturesretard:
you think it might be an error on the sd card like a bad sector?

Just booted back into Decks.... Although the backup of my sd:ext didn't take apparently and it's stock Decks.... Kinda odd; No apps or anything. Or is that supposed to happen? Same wallpaper though....

Gonna try and reflash MikG and if it still doesnt work I'll follow your method. Would rather not as I did that a few months ago when I partitioned my SD card for a2sd lol...

Will post back with results
[EVO 4G Q&A, Help & Troubleshooting] Naturesretard:
Redownloaded and flashed MikG full wipe. Its good now. Thanks to you anyway. :D
[Motorola Droid RAZR] zeidof:
DO NOT APPLY, SOMETHINGS WENT WRONG

BE PATIENT TO SOLVE THE ISSUES

​

is it helpfull? feel free to push - ------------------------------------------------------------------------------------------------------------------------------------ THANKS button here \/

to be continued​
[Motorola Droid RAZR] nameite:
Reserved for future use!

Thanks
[Motorola Droid RAZR] J.Y.Daddy:
oh~ very useful solution.

i'll try it on my Razr.(Korea Razr)

Thanks~;)
[Motorola Droid RAZR] therazrguy:
what is the advantage of deodexing the razr?
[Motorola Droid RAZR] kreez:
so what should I do with this..? can u please give us a little more detailed instructions on how to use it.. like a step-by-step instructions..

will be very appreciate that.. thanks..
[Motorola Droid RAZR] kevinarjun:
Apk files have respective odexes that devs use to supposedly save space. Deodexing means you convert it back to a .dex file and put it back inside the apk. This allows you to easily replace files (not having to worry about odexes), but the main point was to deodex services.jar so that you can change all text to different colors (such as the clock color to white) and to deodex services.jar, you need to deodex everything.
[Motorola Droid RAZR] mopss:
Where to download ? lol

Instruction?

The meaning of this topics?
[Motorola Droid RAZR] zeidof:
I'm working on, can u read first line of op?

Sliced by my Razr on Tapatalk
[Motorola Droid RAZR] mopss:
Oops.)

In my browser is not the first line ((

Excuse me, ie to see
[Bravo General] magicCrazyThing:
So, as the title says, I am having problems installing MS2Ginger on my BRAVO. I downloaded the GreenbreadBravo.zip and the other backup file (I don't remember which one) and followed the instructions listed by Walter79. The install worked fine.

However after following the instructions I tried to boot up the phone and ended up with a bootloop after the Green LED light.

I think I may have downloaded the from Nandroid backup file, but i'm not sure.

Any help would be appreciated, Thanks in advance.
[Bravo General] skeevydude:
It sounds like you downloaded MS2Ginger3.0. It currently doesn't boot on the Bravo, I've tried. Try 2.1, it works, except for the camera.

BTW, you were supposed to download the Nandroid, just not that one.
[Bravo General] magicCrazyThing:
yeah, I figured out that I had downloaded the 3.0., but after that I couldn't figure out with file to download because it was listed for the DEFY. Could you please list the two files I need?
[Bravo General] skeevydude:
MS2Ginger2.1

Yes, it's supposed to be listed as Defy. The Defy and Bravo are very similar phones, so we can run a lot of Defy roms, with slight modifications. Honestly, I'm not sure if there is a 2nd 2.1 file. There's more information in the thread on pages 2 and 3. I only installed 2.1 once, and after a few hours of camera lib bootlooping, went back to CM72.
[Bravo General] magicCrazyThing:
Thanks, I usually don't have problems with stuff like this. I have been switching back and forth between all the ROMs for the BRAVO since I got the phone, and I can't decide whether I want to stick with stock or do what I can to make the camera work in GingerBlur.

Yes, I am one of those strange people that actually like Motoblur.lol
[Bravo General] skeevydude:
Try fixing the Ginger camera, if you can.

Have you tried Blur 3d Launcher at the Defy forums. It's pretty nice, but I had this issue once where widgets decided that they wanted to disappear. They came back after I found an invisible widget and moved it around. I was using CM72 at the time. It made me start to wonder how hard it would be to merge Blur with CM7.....

Sorry I can't help anymore with this, but I haven't used 2.1 very much.
[Bravo General] magicCrazyThing:
Wow, I wish I would have know about this sooner, that would have saved me a lot of trouble. thanks lol :D

Maybe I will go back to CM7, I just figured out that I can get the keyboard too.

First though I'm gunna do what I can to get the camera working in this ROM.
[EVO 4G Q&A, Help & Troubleshooting] ItsLasher:
Ok either way I get flamed. If I bump an old thread (2 of them) asking this or if I create a new thread too so here is the new thread.

What ROM(s) supports AVRCP 1.3 or higher if any? Does not have to be Sense but does have to be stable.:)
[Samsung Epic 4G Touch] ioos:
Has anyone tried connecting ADB to their docked ET4G? Using the same usb port I can connect just fine without the dock, but docked it doesn't recognize it. Is there something that needs to be set up specifically for the dock? Or is it "blocked" intentionally?
[Samsung Epic 4G Touch] ioos:
Still looking for an answer. Anyone?
[Samsung Epic 4G Touch] latinmaxima:
Usb on the dock is not wired for data connection. It won't work.

Dicho por el Epic Touch de Latinmaxima
[Samsung Epic 4G Touch] sratwars:
So i saw this article...and i was wondering if it involve our phones..

http://www.sammobile.com/2012/03/19...ng-releases-kernel-source-for-ics-galaxy-sii/
[Samsung Epic 4G Touch] flight01:
Nooooo!!!!! anytime u see galaxy s2 its for the international/eur one and it has way different hardware then ours i believe so it probably will not be very much help
[HTC EVO 3D] taiguy:
Just got my Evo3D replaced under warranty at my local sprint repair center. My original Evo3D's touch screen went bonkers and they ended up just having to replace the entire thing.

The service rep I wad dealing with told me it was a new phone (not refurb'd) but I'm starting to doubt that. I found out that 2 of the capacitive buttons are bright and the other 2 are dim. The home button is dim. The menu button is bright. The back button is dim. The search button is bright. I don't remember my other phone having this symptom.

Also there is dust under the screen already. How is this possible with a brand new phone?

Wondering if I should go back and try to get this one replaced as well.
[HTC EVO 3D] JohnM:
Buddy, you're lucky. On my first new phones, the capacitive light for the search button was screwed up. There was dirt under the screen and a few dead pixels. The screen was also slightly tilted to the right. I ended up getting a replacement which suffered from other problems

Sent from my HTC Evo 3D
[HTC EVO 3D] taiguy:
what other problems?
[HTC EVO 3D] eyeisdasteve:
Look at my signature. -.-'
[HTC EVO 3D] freeza:
##786# this will let you know if it is refurbished or not
[HTC EVO 3D] taiguy:
Good call. Yea, it's a refurb. Which is normal from what I know about the sprint replacement policy. Except the service rep told me it was brand new. Damn.
[Nook Color Q&A, Help & Troubleshooting] bluevolume:
I updated to the 7.2 RC Kang via CWM, but now my Nook will only boot to CWM. I was already on a 7.2 beta and working fine. Flashed the newest release, cleared cache and dalvik, now all it will do is boot to CWM.

I have taken the SD card right out and its doing the same thing. I have the Cyanogen boot loader on there (shows Cy logo instead of "The Future...").

Appreciate any guidance.
[Nook Color Q&A, Help & Troubleshooting] leapinlar:
If it is booting to CWM recovery and not locking up, that means the 'boot to recovery' flag is set and is not clearing when you leave CWM like it should. Try doing some things in CWM before you exit, like wiping cache or something. And when you exit, exit by the menu, not just powering off.

You can also try using the boot menu to try to force you to emmc. Hold the n button while booting and when the boot menu comes up, pick emmc and normal and reboot.

Edit: You say you take the SD out and it does the same. Why would you expect it to be different? Are you running from SD? If so you should not be flashing things with CWM, that puts things on emmc. Or did you mean you take the bootable CWM SD out? You should always take that out after flashing to emmc. And if your already running CM7 from emmc, you should be flashing with the CWM on emmc, not a bootable CWM SD. I'm confused as to what you were doing and what your configuration was.

Sent from my Nook Color running ICS and Tapatalk
[Nook Color Q&A, Help & Troubleshooting] bluevolume:
I took the SD card out as someone had suggested that in the ROM thread. No, it doesn't make sense that if would just start booting from the SD card when it wasn't before, but it eliminated a variable.

I have gone into the boot menu and checked that it is booting from emmc. I've even changed it to SD and back just to make sure it took.
[Nook Color Q&A, Help & Troubleshooting] leapinlar:
Then it is the set flag issue I mentioned in the first part of my post. Not sure how to get it cleared. Just exercising CWM? Try flashing something else. Gapps again maybe. It won't hurt to flash them twice.

Edit: btw, what version of CWM are you running?

Sent from my Nook Color running ICS and Tapatalk
[Nook Color Q&A, Help & Troubleshooting] bluevolume:
CWM v3.2.0.1

I installed gapps again, same problem. Gremlins!
[Nook Color Q&A, Help & Troubleshooting] cmendonc2:
I had this problem, but the only way I found to fix it was to flash a stock recovery zip from CWM recovery SD card, then CM7 again
[Nook Color Q&A, Help & Troubleshooting] leapinlar:
But in his case it is not locking up. It is cleanly rebooting to CWM. A little different scenario than yours.
[Nook Color Q&A, Help & Troubleshooting] votinh:
How could it reboot into CwM if there is no flashable CwM uSD installed, where those "Rec" files reside?

Did you some how flash CwM into eMMC before, OP?
[Nook Color Q&A, Help & Troubleshooting] bluevolume:
Yes, I've had CWM flashed into the emmc for a while. So I could use the boot menu utility to boot to CWM if needed.

BTW - this is the ROM i'm using: http://xdaforums.com/showthread.php?t=1344873
[Nook Color Q&A, Help & Troubleshooting] leapinlar:
He is on emmc. He had a CM version on earlier and used ROM Manager to put CWM on the emmc boot partition. This problem only emerged when he flashed the newest CM to emmc from ROM Manager with the CWM on emmc. He now only boots to CWM and it is loaded from emmc boot. It is a flag set problem. The boot loader is telling it to go to recovery instead of normal ROM. That flag is set by ROM Manager when it wants CWM to perform a task for it. Like flash a ROM. That is how the boot loader knows to boot to recovery rather than the ROM. CWM is supposed to reset that flag when it has finished the task that ROM Manager asked it to do. Somehow it is not being reset.

Edit: @bluevolume - a possible solution is to make a bootable CWM SD and boot to that. That may reset the flag when it exits.

Edit 2: I found where the recovery flag is stored on the nook. There is a separate partition (2) called /rom that stores basic information like your model number, date of manufacture, serial number, etc. Also there is a file named BCB which is usually an empty file. But if the word 'recovery' is written there properly, it will always boot into recovery. Recovery is supposed to write the empty file back when finished so that on next boot it boots normally to emmc. I'm not sure how much good this information is going to do you, but if you are proficient with adb, you can modify the file even if in recovery.
[Nook Color Q&A, Help & Troubleshooting] bluevolume:
That is good info, thank you. I have not been able to get ADB working in the past (i'm on Win 7 64); I think its a driver issue. I'll revisit that later today.
[Nook Color Q&A, Help & Troubleshooting] leapinlar:
If you can get adb working in CWM, this is what you want to do in at the dos prompt, one line at a time:

adb shell mount -t vfat /dev/block/mmcblk0p2 /rom

adb shell dd if=/dev/zero of=/rom/bcb bs=512 count=1

adb shell reboot

Edit: if you want help getting adb working this post may help:

http://xdaforums.com/showthread.php?p=21665649

Edit2: I've been doing a lot of experimenting. It is not what's in the bcb file. It's what the file size is. If the file size is 512 bytes or larger it will boot to normal emmc. If it is smaller than 512 bytes or MISSING, it will boot to recovery. It could be yours is missing. But recovery is supposed to create a new big one if it is. Could be a permissions problem. If you get adb going you can fix that.

On a side note I was thinking it could be corrupted boot files causing this, but I purposely messed with them and it does not boot into recovery, it just hangs.
[Nook Color Q&A, Help & Troubleshooting] bluevolume:
Let me first thank you for your time and support on this; its people like you that make these forums such a great resource.

I'm not that comfortable with adb commands so I starting looking for other solutions. Since you mentioned that its the actual boot files that are missing/corrupted, I searched around and found this:

http://xdaforums.com/showthread.php?t=958748

I loaded the RecoveryFix.zip on my SD card and flashed it with CWM. Rebooted, and I was back to the 'Future of reading..." boot logo, but it still went straight to CWM. So I flashed the ROM again (the ROM I listed earlier in the thread), wiped cache, fixed permissions. Rebooted, and the "Cyanogenmod" boot logo was back. And instead of going right to CWM, the screen was blank for quite a while then I saw the little Android guy skate by... And I'm back in business.

I know other people have had this problem and this seems like a pretty simple solution. I'm good at this point, and hopefully some other people will find this thread helpful.
[Nook Color Q&A, Help & Troubleshooting] leapinlar:
The next step I was going suggest if you could not fix it was to flash a new CWM to your boot files. Good job finding that.

Glad you got it running. I learned a lot myself and maybe that info will help others.

Sent from my Nook Color running ICS and Tapatalk
[Nook Color Q&A, Help & Troubleshooting] votinh:
Got it, thanks m8

That clears up my mind.
[Nook Color Q&A, Help & Troubleshooting] Hoser88:
I had the same problem, followed the thread you found. Did the same thing, now I'm back in business too. Thanks!
[Nook Color Q&A, Help & Troubleshooting] sgayol:
Just wanted to say thanks for figuring this out! I was in a similar situation after downgrading from cm9 back to cm7. Installed CWM using recoveryfix_3.0.2.8.zip from the thread above, and was back up and running after a restore of a cwm backup. Headed on vacation tomorrow and the wife would have had my head for being such an FW... you're a lifesaver!
[myTouch 4G Q&A, Help & Troubleshooting] jjbat87:
hello everyone , i have a mytouch 4G that had the good chip and good display , so that has nothing to do with the problem . my actual problem is that i attempted to do a digitizer repair on my own , and it went successfully , i put the phone back together and i turn it on , the phone vibrated and made boot sound but the screen did not light up, it remained black , i opened the phone like litterily more than 6 times to try disconnecting and connecting the lcd connector and nothing.

to this day it still doesnt light up at all, and now after trying at it one more time the phone doesnt even boot anymore , i cannot turn it on by power button , and when i connect the charger the light is orange , phone vibrates once , then turns green . this is the most i can get out of my phone .

when i was repairing my phone i used a hair dryer to soften up te adhesive , which is the correct way to do it right ? i put the hair dryer directly to the lcd if that probally done anything . and there is a chance i probally scraped a ribbon thats above the lcd on the front when i tried to pry it out

should i just give up on my phone ? or should i try to get professional help and get ready to chuck up 100 bucks for a repair , i am asking if there is nothing i can do.

p.s. i would realllllly like to avoid buying a lcd , cus it would suck if i spend 20-something bucks on a lcd and just to have find out its something else (since the phone currently wont even boot)
[myTouch 4G Q&A, Help & Troubleshooting] Attackd0g:
the phone probably won't boot b/c you may have ripped out the flex cable for the power button. i made this mistake myself a couple month ago and it cost me like $20 to get a new one. as for the lcd, i'm not sure. you may have to get a new one