• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Root Warning(For Devs): Flashing a kernel in CWM will brick your TU

bads3ctor

bads3ctor

Well-Known Member
Using this partition: /dev/block/mmcblk0p8 to flash a kernel in CWM will brick your Samsung Transform Ultra.

You have been warned. This edify command bricked my TU:

package_extract_file("boot.img", "/dev/block/mmcblk0p8");

And using flash_image in CWM with /dev/block/mmcblk0p8 is just as fatal as that edify command.
 
bads3ctor said:
Using this partition: /dev/block/mmcblk0p8 to flash a kernel in CWM will brick your Samsung Transform Ultra.

You have been warned. This edify command bricked my TU:

package_extract_file("boot.img", "/dev/block/mmcblk0p8");

And using flash_image in CWM with /dev/block/mmcblk0p8 is just as fatal as that edify command.
Click to expand...

Thanks for sharing the info bada3tor btw Bobzhome made it a nandroid backup when he did the overclocking for the Ultra. You would install his by doing an advance restore and then select boot.img
 
bads3ctor said:
Yes...thx...thats how I have been doing it. Any idea if this is a CWM flaw or a phone hardware limitation?
Click to expand...

I would say its probably either cwm or something with the phone as simple commands that cwm to install new stuff just wont/dont work. For example the shevron rom. If you flash UOT theme it kills the status bar but if you extract the UOT theme and manually install it, it worka fine. Since the systemui.apk has alot to do with the status bar and if you removw it from your system apps it automatically kills the statusbar i would say cwm isnt placing systrmui.apk correctly or probably not doing it at all. Its probably the same for the kernel as well, if you dont have a kernel your phone is pretty much done. In guessing thats what happened? You used that command in a script updater and im guessing that our lazy cwm probably didnt even install the new kernel making your phone useless. Just my thoughts i could be wrong.
 
bads3ctor said:
Any idea if this is a CWM flaw or a phone hardware limitation?
Click to expand...

in my opinion i would have to say somthing is wrong with CWM... in your battle for odin you found out that some partitions were not what someone origanaly had/said they were... so other things might be a miss as well.

:confused::confused::confused:A hardware limitation??? the Ultra not able to handle the processes of cwm??? is that even possable???:confused::confused::confused:

(I am extreamly thankfull for CWM! even if somthing might be wrong)


chevanlol360 said:
For example the shevron rom. If you flash UOT theme it kills the status bar but if you extract the UOT theme and manually install it, it worka fine.
Click to expand...
uot flashes just fine... had no issue with status bar exept when i flashed a Odexed uot to a Deodexed rom or vica-versa...

.

when things are not done correctly from the ground up, there will be problems!

.
 
chevanlol360 said:
You used that command in a script updater and im guessing that our lazy cwm probably didnt even install the new kernel making your phone useless.
Click to expand...

No...it wiped out the internal flash partitions including sbl2 and the download partition that Odin needs. We have verified this on 2 phones....that is enough evidence for me that either CWM is faulty or the phone hardware is bricking automatically upon kernel partition image update.
 
bads3ctor said:
No...it wiped out the internal flash partitions including sbl2 and the download partition that Odin needs. We have verified this on 2 phones....that is enough evidence for me that either CWM is faulty or the phone hardware is bricking automatically upon kernel partition image update.
Click to expand...

Sounds like to me it could be CWM, unless it's hidden in samsungs gang signs lol:rolleyes:
 
Had anybody tried this app from the market?

Kernel Manager Article on LifeHacker

Google Play Store Link

EDIT: Also, I'm pretty sure you devs already knew this, but for those that didn't, here is the manual method
Manual Method

Since CWM had to be ported, I'm sure it just wasn't designed to flash kernels on the phone, flashing via one of these other methods may yeild better results. that way an entirely new ROM won't have to be created and a kernel can be flashed to try to OC and/or fix touchscreen driver issues
 
www.*************s.net/forum/coby-tablets/32349-how-un-brick-your-coby-tablet.html

help me understand this issue

there are people with this cheap coby tablet that say the stock boot.img or recovery.img from the android sdk can unbrick a softbicked phone
which has been a "known solution" when u do it the manual way.

from what im reading flashing a MODDED img to boot will result in a brick? so what would happen if we flashed a stock img from the sdk

since android has been integrated with linux kernel, is it possible the touchacreen drivers would be integrated?
 
All we know is that when a kernel is flashed to the boot partition on this phone using any method in CWM, it results in the internal flash partitions being so corrupted that the phone is bricked and no button combinations work to enter any mode....recovery and download mode are gone and the phone will not boot into any usable mode.
 
bads3ctor said:
package_extract_file("boot.img", "/dev/block/mmcblk0p8");
.
Click to expand...


where did you get the update-binary

from my experience if you use a update-binary for another phone and try to flash kernels and such, it usually bricks the phone, by overwriting boot loaders or other important partitions


but it may also be a problem with you CWM


sorry I can not help, but I am pretty busy with other stuff


it is a shame that after all that flashing with Odin with no ill effect, CWM did this





.
 
You must log in or register to reply here.
Back
Top Bottom