yashsingh1/xdaforums huggingface dataset:
[General Questions and Answers] I Am Marino:
Because they figure messing with the OS is apparently evil. I'm more than willing to bet this is more of a carrier pushed issue than the OEM because one big reason of rooting is to bypass carrier limits.

Sent from my ADR6300 using......you get the idea.
[General Questions and Answers] Step666:
That's an excuse, not a reason.

There is no reasonable justification for manufacturers to take such a stance.

And even less of one for someone on here to apparently agree with such behaviour.
[General Questions and Answers] Captainkrtek:
As one of the few founding members of the Dev Team AndIRC I got a good laugh out of this article, this is not the end of an era. All devices have had some challenges to rooting. The HTC Droid Eris which was our claim to fame took months to root and then finally we got some working methods, the fact that we owned the thunderbolt in less than a few hours (the article is too dramatic) is amazing, we have some very skilled devs and with time we get work done.
[General Questions and Answers] 313dash:
I think this is a carrier issue. Now that their all worried about tethering. Hey if you pay for the phone and service what you do with it is your problem. Its about making more money. If it gets worse I may downgrade to a metro! Omg
[General Questions and Answers] SteveG12543:
Incredible took a while too... Kinda seems like they're stepping it up a bit, generation after generation.

Sent from my Droid Incredible running Myn's Warm TwoPointTwo RLS5.3.
[General Questions and Answers] warningshot:
maybe the carriers got something to do with it? they want to charge extra for tethering and so on after all. if it would be too easy to unlock extra features and wipe devices of their bloatware they might miss out on additional money?
[General Questions and Answers] Product F(RED):
Well f*ck the carriers. If they're going to cripple a device, they have no right to charge what they do. Yes, you already pay about half of what they pay for the phone, BUT you pay back the difference over the term of your contract.
[General Questions and Answers] I Am Marino:
Probably more than that.

Sent from my Incredible with the XDA Premium App.
[General Questions and Answers] Phateless:
The G2 and MT4G took a couple of months to root but it happened. The amazing devs here will always find a way.

I completely agree that we own it and should be able to do what we want. If you expect the carrier to support it they have a right to only support their approved configuration.

I think hardware warranty and troubleshooting warranty should be separated.
[General Questions and Answers] dragonithe:
Why can't they just do it more like the PC's do.

If you screw up you can insert a bootable CD and restore the OS.

Of course a CD is not a ideal option for a phone, but I can see a SD card formated and coded in a way that it is able to restore the OS completely, even if the phone is bricked.

If the manufactures give such a card away (could just be a 512mb card I gues) then the consumer could hack the phone to dead and still have a backup thus keeping the manufacturer out of sight.

I mean, how hard could something like this be? ;p
[General Questions and Answers] I Am Marino:
Impossible for the carriers since to them rooting is horrible.

Sent from my Incredible with the XDA Premium App.
[General Questions and Answers] swanga:
..................
[General Questions and Answers] Phateless:
I agree. Then all they have to do is tell us to return the phone to stock before we troubleshoot it.
[Droid Incredible Q&A, Help & Troubleshooting] watt9493:
Solved, well kinda. Please delete
[HD2 Android Q&A, Help & Troubleshooting and Genera] silverwind:
Dear Friends,

I usually flash ZIP Android using CWM, through menu no.8 in MAGLDR menu. CMW was flashed via USB Flasher menu no.5 in MGLDR menu.

But after several times of failures, I gave up. I hope somebody can inform me what went wrong.

Here is the issue:

After flashing CWM (partition layout) and try to go into recovery mode, the screen says:

"ANDROID LOAD RAW

ERROR: ERROR: Cannot read kernel image"

I tried so many attempts but always like that. I did task 29, reflashing MAGLDR, radio, I even tried to go back to Winmo and back again to reflash HSPL 2.08 and so on. But no luck:(

I remember that this happen after I tried flashing CWM using SD Card method (via menu no.2 in MAGLDR). If I used this method, I can go into recovery mode. I dont like this method, because I never succeeded flashing ZIP ANdroid using this method. That is why I want to go back to recovery mode via menu no.8 in MAGLDR.

Is the problem related with what i did (flashing CWM via SD Card method)? Is the NAND is damaged?

Is there a way to solve that?

Many thanks in advance
[HD2 Android Q&A, Help & Troubleshooting and Genera] samsamuel:
what are the contents of flash.cfg? (you can open that file in notepad)
[HD2 Android Q&A, Help & Troubleshooting and Genera] silverwind:
Which one? is it the one with CWM partitioner lay out?

This one was flashed when I tried to flash: Ultimate Droid v.3.1.1.v2:

misc ya 1M

recovery rrecov|ro|nospr filesize recovery-raw.img

boot yboot|ro 5M

system ya 150M

cache ya 30M

userdata ya|asize|hr allsize

And this one is the standard one with 150MB lay out:

misc ya 1M

recovery rrecov|ro|nospr filesize recovery-raw.img

boot yboot|ro 5M

system ya 150M

cache ya 44M

userdata ya|asize|hr allsize

I used either one as per instruction in the relevant thread
[HD2 Android Q&A, Help & Troubleshooting and Genera] samsamuel:
hmm, and there is deffinitely a file called recovery-raw.img in the same folder? do you get any error messages on the phone screen when you flash the cwm layout?
[HD2 Android Q&A, Help & Troubleshooting and Genera] silverwind:
Yes. Never happened before until I flashed cwm using ad method as explained in the following:

http://xdaforums.com/showthread.php?t=987531
[HD2 Android Q&A, Help & Troubleshooting and Genera] Richy99:
once you install CWM you are installing a rom from zip arent you?

if you just install cwm then it wont boot any existing rom, thats what i have found from past experience
[HD2 Android Q&A, Help & Troubleshooting and Genera] silverwind:
After flashed Recovery via AD SD boot, I flashed the ROM. But it won't boot. So, I decided to reflashed Recovery via USB FLasher (of course I did task 29, flash MAGLDR again).

After that, I went into MAGLDR menu and selected no.8 (AD Recovery). And, it wont boot to Recovery. It says ERROR cannot read kernel image.

My point is that I want to flash ROM via CWM (this CWM was flashed via USB Flasher), but the CWM itself failed to boot (after successful flashing).

I dont have problem boot into CWM if it is flashed via AD BOOT (menu no.2 in MAGLDR) and I cant flash the ROM (though the ROM fails to boot).

Any idea?
[HD2 Android Q&A, Help & Troubleshooting and Genera] samsamuel:
ive not used that edited/tweaked cwm, but two things come to mind.

First off, latest magldr required, check? (im not scrolling back to read, so sorry if you already said that)

and secondly, from teh error you are getting, it can only be that somewhere, (possibly when you are restoring from a backup taken when there was no recovery partition?) you are either wiping the recovery partition, or you arent loading back the contents of the recovery partition.
[HD2 Android Q&A, Help & Troubleshooting and Genera] silverwind:
Yes Magldr 1.13. I didn't restore any nandroid backup. How can I restore if recovery failed to boot?

It seem this tweaked cwm did/wrote something In the NAND that cannot be erased by task 29 or by flashing stock rom. I stiil can bot recovery through AD boot (menu no.2 in magldr) the tweaked recovery show version 3.0.1.9. Maybe I

should try mtty?
[HD2 Android Q&A, Help & Troubleshooting and Genera] samsamuel:
think id concentrate on getting back to winmo stock with an sd card flash, wipe the lot and start over yet again.
[HD2 Android Q&A, Help & Troubleshooting and Genera] greg17477:
As far as I remember, after you flash magdlr 1.13 you need to flash CWM to get the menu point 8 (ad recovery) working. Magdlr 1.13 itself doesn't have the CWM built in, but it supports CWM.
[HD2 Android Q&A, Help & Troubleshooting and Genera] silverwind:
Like I said, I did start it all over again;)

But, still it didnt help. That is why I am beginning to think that task 29 does not erase all NAND or else there is a damaged/defect in the physical NAND. Should I try use MTTY?
[HD2 Android Q&A, Help & Troubleshooting and Genera] silverwind:
Yes I know. There are 3 methods (as I know from XDA;) ) to boot Recovery Clockword Mode (CWM). Firstly, flashing via USB Flasher (menu no.5) and after flashing, we should select menu no.8 to go into CWM mode (this one is the issue I am talking about), secondly, flashing via AD Boot (menu no.2), it will directly bring you into the CWM menu, and thirdly, using cLK (which I never try it).

I just wanted to try the second method and it works. However, due to the partition lay out issue (as far as I am concerned, the second method doesnt provide flexibility in providing partition lay out. it uses 150MB lay out). So, for the ROM requires different partition layout, I need to flash CWM in accordance with the relevant ROM requirement. This can only be done if we flash CWM via First method. When I flash CWM (for different partition lay out), it seems flashing successful , but when I selected menu no.8 to go into CWM mode it then says: "Error, cannot read kernel image".

Up to now, I can only boot CWM using second method. I just hope the dev of this method can provide a way to flash different partition lay out or did I miss something?:confused:

thanks
[HD2 Android Q&A, Help & Troubleshooting and Genera] seadersn:
does this occur with the standard content of raiderx' recovery download, for example the 400m layout...? you can try to edit the "recovery" line inside flash.cfg: remove "filesize" and instead type "6M", so it shows

...

recovery rrecov|ro|nospr 6M recovery-raw.img

...

maybe there are bad blocks on NAND (which is normal, especially after excessive flashing, which is native to us hd2 users due to the mass of roms available for it :)) which are causing this.

alternatively you can try to first delete the original "recovery-raw.img" inside the original raiderx recovery folder and then copy the new one; or to use another windows machine (or harddrive in your computer, if exist). maybe there is sth wrong...?

if all you've tried already and other tipps isn't / aren't working, it would be interesting to know if this occurs if you're using cLK; pure testing purpose :)

i hope you'll get this running... the sd method is no solution in my opinion.
[HD2 Android Q&A, Help & Troubleshooting and Genera] silverwind:
Thank Bro, I will try your suggestion and let u know the result.

I also guess there is something wrong with the NAND, maybe the cluster, block, etc. Maybe need to be defragmented ;) (is there any app for doing that?)

I use standar 150MB partion layout from Raider x and also 135MB layout for flashing Typhoon Cyanogenmod.

I still can flash using DAF, but since there is only few ROM for this method, then I would prefer to go through via CWM :)

thanks again :)
[HD2 Android Q&A, Help & Troubleshooting and Genera] seadersn:
sure, no problem! one additional question: this really started out since you've used the sdcard files?

cwm is essential and really needed, especially as the most of chefs doesn't provide DAF ROMs anymore. you want to flash typhoon cm7, right? if nothing is working for you, i'll create a daf version for you, so that you at least can use this ROM. just let me know.
[HD2 Android Q&A, Help & Troubleshooting and Genera] silverwind:
Yes, since I tried the SD card CWM (no offense Bro;) )

You are right, CWM is app you cant live without it if you are an Android lover :D

I highly appreciate if you can provide DAF version. I only knows how to convert from ZIP to DAF but not the other way round:o

Many thanks
[HD2 Android Q&A, Help & Troubleshooting and Genera] seadersn:
k, i will create it todays evening ~ 20:00 gmt+1; but first, pls try to test the other tipps :) (6M for adding "some spare blocks" and if nothing helps cLK pls).

i'll pm you if i'm ready ok?
[HD2 Android Q&A, Help & Troubleshooting and Genera] seadersn:
i have to do it tomorrow; today i've painted the livingroom of a friend and didn't go home. that's ok? or is there sth new on your side? did you test cLK?

greetings :)
[HD2 Android Q&A, Help & Troubleshooting and Genera] silverwind:
No need to push yourself mate ;) I am patient enough to learn ;)

For installing cLK, I will do it later because I have to learn it since I am not familiar with it (or else if you have or know tutorial for newbie, i would go for it)

I will start with flashing with Recovery with 150MB layout provided by Raider x. Currently I am using Winmo with HSPL 4.

Here is what I will do:

1. Turn of the phone.

2. Go into bootloader mode

3. Task 29

4. Flashing HSPL 2.08

5. Flashing MAGLDR 1.13

6. Flashing CWM 150MB via USB Flasher in MAGLDR menu no.5

7. Boot into Recovery Mode via MGLDR menu no.8

This is the point where i got the problem. If it works, then I can go into Recovery mode to install ZIP ROM , but if fails then it will say Error: cannot read kernel image and it will bring me back to MAGLDR screen.

EDIT

:

After flashing MAGLDR 1.13, the phone reboot and I unplugged the usb cable.

It booted and the screen says:

"Booting Android from SD

Android load at 11800000

from Micro SD

Load zimage

k: / zimage

ssSD kernel open failed"

then it brought me to MAGLDR screen menu.

I thought it is normal, isnt it?

then I flash CWM using USB flasher via menu no.5

After flashing CWM complete, the phone reboot and again it showed the above screen and finally went back into MAGLDR screen.

Here is the same old problem. In MAGLDR screen, I selected menu no.8 in order to boot the Recovery mode.

But it failed and the screen says:

"LOAD ANDROID RAW

ERROR: ERROR: cannot read kernel image"

So, it happens again.

Before I continue with the next trial, I wanna hear your opinion about that.

BTW, the winmo before I started this, is ENERGY ROM.

PC I used is WIN XP SP2.

Battery is full, SIM CArd was in but Micro SD was removed.

Do you think I miss something?

Thanks in advance
[Thunderbolt General] rckymtnrfc:
I think I know the answer....but I am hoping someone knows if there is a way to turn this off. It's so big. Hate it. As far as I can tell...its not optional.
[Thunderbolt General] CyD13:
Nope, can't turn it off.
[Thunderbolt General] icedmayhem:
not yet, give it time for the framework to be ripped apart. root and s-off have just arrived, patience
[Thunderbolt General] distortedloop:
Agreed that it's a bit large, but I actually like the feature.

My biggest complaint with the TB (other than TFT vs SAMOLED screen) is the placement/arrangement of the capacitive menu buttons at the bottom of the screen. I don't have tiny hands, but they're not particular big either, so the size of the phone and the placement of the Home button make it just about impossible for me to use the phone with just one hand like I do my 4" phones. My thumb just can't reach the Home button when holding it in my right hand without risking dropping it, so it's difficult to do the long press to get the recent apps screen up. I can comfortably drop the shade and select from there, though, so I like it. Obviously a YMMV thing, and accessing the Home screens still takes two hands for me.
[Thunderbolt General] PJnc284:
yeah, the recently used apps in the notification bar was poorly thought out. It's redundant as holding the home button does the same thing and isn't needed. If they were going to put anything up there, it should've been the quick toggles like the Galaxy S line of devices.
[Thunderbolt General] rckymtnrfc:
Yes...I also miss the quick toggle from Cyan....I still find myself pulling down the shade only to realize its not there.

And I miss being able to dismiss notification with a sideways swipe.....A LOT!
[Thunderbolt General] URPREY:
Check out Widgetsoid. It does what you want but takes a bit of setup
[Thunderbolt General] apDroid:
Couldn't you just use a different launcher like ADW? Or is it built into the framework? If so, what a turn off.
[Thunderbolt Q&A, Help & Troubleshooting] mcargil05:
The main keys do not light up with the screen. Nothing about it on the HTC web sight.
[Desire HD Q&A, Help & Troubleshooting] b1rken:
I tried to flash my Desire HD today.

I followed this guide http://xdaforums.com/showthread.php?t=964996&highlight=Installation+aborted.

Followed it down to every detail, but after i have runned the FULL-WIPE-1-2-3, and started installing the Android Revolution rom i get this error message:

E:Cant't open /sdcard/Android_Revolution_HD-4G-3.2.zip

(bad)

Installation aborted.

I tried to download from another mirror, and ran a MD5 checksum on the file after download, and checked it up against the MD5 checksum that i found in the Android Revolution thread, and it was exactly the same.

What the hell is wrong? :confused::confused:
[Desire HD Q&A, Help & Troubleshooting] Andy:
May be a problem with your SD card. Do you have access to another one?
[Desire HD Q&A, Help & Troubleshooting] b1rken:
Hmm, no i dont have another SD card :(

I said i followed the guide to every bit, but i forgot that i skipped the radio step.

I did not flash the radio because i didnt know which radio to flash.

But now i saw that in the Android Revolution thread the recommended a radio, so i downloaded that radio and flashed it.

Could this cause the problem i had? That i didnt flash the radio before i flashed the Android Revolution rom?

I restored the nanodroid backup in clockwork so that i now have a working phone again, but damn i want this to work. If i do a wipe again will it delete the backup i made in clockwork recovery or do i have to make a new backup after i wipe?
[Desire HD Q&A, Help & Troubleshooting] b1rken:
SOLVED!!

I got it right now. Dont know for sure which of the things i did that made it working, but ill write em down if someone else has this problem.

- Downloaded the radio suitable for the rom, and flashed it

- Downloaded the rom flash image for the 5th time, this time i downloaded it via torrent

- Renamed the Android_Revolution_HD-4G_3.2.zip to update.zip
[Desire HD Q&A, Help & Troubleshooting] Alisinja:
Thanks SO MUCH it helped!:) I redownloaded file (now 198 Mb to 128 Mb I had primordially) and renamed it to update.zip

P.S. I have HTC Desire, but I guess this problem is common
[Desire HD Q&A, Help & Troubleshooting] ahnyungsaigon:
Solved, too.

Seems that I've solved the same problem in a much more weird and simpler one. Reboot, redo it, done!

Got a similar problem when installing the revolutionhd rom stuff next, and reboot, redo it, done!

No idea coz I'm a noob and would love to be a noob. I hate the processes to get the result I desire, so I have to suffer from it like a soldier who has to plant lots of flowers to get to the girl.
[HTC Inspire 4G] bowtieguy:
Just at the topic states.

What is a good kernel for CM 6.1.3 on the Inspire?

Thank you in advance
[HTC Inspire 4G] laxwillsch:
+1 I don't know why but I like the way cm6 looks and wanted to give it a run on my inspire but I can't seem to find a kernel that will include sound. I mean it makes sense because cm7 is already out, but I still wanna try cm6 for ****s and giggles.
[HTC Inspire 4G] CharlieBravo117:
The CM6 (6.1.3) rom I've used on my Inspire 4G had perfect sound. Make sure you're downloading the rom for the HTC Ace (I know... 3 names for one phone?), it might have a different set of drivers than the rom written for the Desire HD - even though they're almost identical.
[Galaxy S I9000 Q&A, Help & Troubleshooting] viper3009:
Hi, This is probably more a question for the seeARMS 0.4v JL2 or Super Optimized Kernel 4_8_3 Stable threads under development but I can't post there yet...

Hopefully someone can help me out. I installed seeARMS 0.4v JL2 rom that comes with the Super Optimized Kernel 4_7_6. Apparently there was a bug in SOK 4_7_6 that cause the system to reboot whenever the TV Out was turned on. Developer claimed to fix it in version 4_8_0 and newer but I just downloaded and flashed the 4_8_3 version and am still having the same TV Out reboot issue.

So my question is....in order to get the TV Out working can I try a different Kernel, (ie 4_8_1) or would rolling back to an older kernel mess things up?

Thanks for you help in advance!
[Galaxy S I9000 Q&A, Help & Troubleshooting] gfacer:
OK I think

I think it should be fine. If in doubt, just flash a different kernel first but I am pretty sure the kernels are quite stand alone.

I'm interested to know if that works. I was on seeArms .3 before my sd card went but I am on Darky's now... Always wondering if the grass is greener though!
[Desire Themes and Apps] green hoodlum:
Hi, i hope this post isn't covered anywhere else cos i've tried searching and i can't seem to find it, if it does exist, apologies.

i've currently installed the devnull ROM and i would like to install the htc clock widget.

where can i find the .apk for this widget? if i can get my hands on another htc desire, can i grab the files from that install it on my rooted device? if this is possible, which files do i need to copy?

thanks for any response!
[Desire Themes and Apps] wildcardspv:
I don't think you can get it, but beautiful Widgets or fancy Widgets are just as good.

I prefer fancy Widgets.

Posted telepathically. Oh yes.
[Desire Themes and Apps] cr1960:
HTC clock widget is only available in Sense ROMs - not AOSP ROMs like Devnull.

Beautiful widgets has a similar closk - very nice.
[Desire Themes and Apps] tigerfire25:
I wanted same for villain rom on my desire but could not find it, but there is an app on market named "sense analog clock widget" i.e pretty much same (well I think it's better with more options).

Give it a try ;)
[Desire Themes and Apps] !@ndre@!:
Hi guys, I'm looking for the DARK htc clock/meteo widget. Where can I find it?

I have seen that it is included in some themes but I don't want to install a complete theme only for a widget....
[Desire Themes and Apps] dainese01:
This is as close as you will get without the actual Sense clock.

http://www.mediafire.com/?t22i22zzfz74zcc
[Nexus One Q&A, Help & Troubleshooting] yellofello99:
Ok, so I have a rooted Nexus One with cyanogen 6.0rc3 on it. I recently tried to put cyanogen 6.1 on it so I could upgrade to 7.0. Then, I see the common glitch where there is no market so I revert back to my old rom which I made a backup for(using ROM Manager). So here comes the hard part, when it restores my ROM, have no apps, no nothing which I downloaded, and I tried to restore again, because ROM Manager reinstalled, but I didn't get anything. Can some tell me how to get my data and all my stuff back, please?!?!?!?! If I don't get help by the end of the month, my service gets cut off, so I really need help!!!! Please help guys, thanks in advance, you guys are the bomb!!!!:(:confused::eek:
[Nexus One Q&A, Help & Troubleshooting] KAwAtA:
What's that supposed to mean? You lose service because you don't have the data on your phone restored?

Are you using apps2sd?

I feel like you have no chance of restoring anything at the moment though.
[Nexus One Q&A, Help & Troubleshooting] danger-rat:
If you have a custom recovery, just wipe and start again, or restore your backup... Make sure you have a gapps package that is compatible with your ROM...
[Nexus One Q&A, Help & Troubleshooting] sparkyryan:
All your apps will be in the market under 'my apps' and as long as you have synched with Google servers all your data should be retrieveable by re-synching.
[Nexus One Q&A, Help & Troubleshooting] baseballfanz:
You don't need to go to cm6.1 to get to cm7. Even on 6.1 you need to do a full wipe anyway to eliminate any potential problems.

Also did you happen to use CWM 3.0?
[Nexus One Q&A, Help & Troubleshooting] yellofello99:
I tried to restore my backup, it doesn't work for some reason
[Nexus One Q&A, Help & Troubleshooting] yellofello99:
I tried that, too, not all of my apps restored, and my data would be gone on them anyway
[Nexus One Q&A, Help & Troubleshooting] yellofello99:
I was using 3.0