Related
I just read a news here in xda that mentioned CWM as the culprit of some hard bricked galaxy note devices. Is it possible that this case might happen to us 7.7 users? I'm bothered as I just installed CWM today.
Sent from my GT-P6800 using XDA Premium HD app
Sent from my GT-P6800 using XDA Premium HD app
kencad said:
I just read a news here in xda that mentioned CWM as the culprit of some hard bricked galaxy note devices. Is it possible that this case might happen to us 7.7 users? I'm bothered as I just installed CWM today.
Sent from my GT-P6800 using XDA Premium HD app
Click to expand...
Click to collapse
First of all: our eMMC chips have a major bug that can cause the device to be bricked. Same as the Note, the SGSII, and other Samsung models. This is a hardware bug, there is nothing we can do to correct it. (Actually, not ALL of those devices have the bug. Check yours with GotBrickbug?, but don't hold your hopes up.)
Now, this bug is only triggered under some situations. The trigger we're familiar with is when some eMMC operations (partition wipes, for example) are done with a kernel that has the option MMC_CAP_ERASE enabled.
The problem is that Samsung's 4.0.4 kernels have it enabled. This means that a stock kernel has a chance to brick your device. The stock recovery seems to trigger the bug less often than CWM, though. Stock kernels with CWM recoveries (the popular cf-root kernels for the SGS series, for example) are directly affected.
The good news is that our device uses one kernel for the system and one for the recovery. locerra's CWM includes a kernel with MMC_CAP_ERASE disabled. This means that locerra's CWM should be as safe as you can be.
Note that it's possible that there are other, not so widespread triggers for the hardware bug (I know of none, so, to the best of my knowledge, using locerra's CWM should make you safe). This means that until Samsung releases all the information and gets the bug completely isolated, it is possible that you will have problems. They most likely won't be CWM related, though.
EDIT: Please, let me make this as clear as possible. CWM does NOT brick devices. A hardware defect of the memory chip bricks devices. CWM (and the standard recovery, and possibly TWRP) can only trigger this defect.
Thanks for the informative reply.
Ps. : I flashed CWM recovery that I downloaded from the Internet. Can I replace it with locerra's? Is there any difference?
Sent from my GT-P6800 using XDA Premium HD app
The especially dangerous cwm was touch cwm.zip that was used for rooting ics. Do not use this temporary cwm. I bricked my note using it.
Sent from my GT-P6800 using xda premium
I actually used that cwm. Zip to root my tab. Phew! Good for me as my device wasn't bricked.
Ps. : when a device gets hard bricked, what does it mean? Is it dead? What is the best option when I'm hard bricked?
Anybody? Thanks
Sent from my GT-P6800 using XDA Premium HD app
means... your motherboard fried and need replacement...
Now, this bug is only triggered under some situations. The trigger we're familiar with is when some eMMC operations (partition wipes, for example) are done with a kernel that has the option MMC_CAP_ERASE enabled.
The problem is that Samsung's 4.0.4 kernels have it enabled. This means that a stock kernel has a chance to brick your device. The stock recovery seems to trigger the bug less often than CWM, though. Stock kernels with CWM recoveries (the popular cf-root kernels for the SGS series, for example) are directly affected.
The good news is that our device uses one kernel for the system and one for the recovery. locerra's CWM includes a kernel with MMC_CAP_ERASE disabled. This means that locerra's CWM should be as safe as you can be.
what then is the safest way to format my tab/restore to factory settings in ICS?
kencad said:
when a device gets hard bricked, what does it mean? Is it dead? What is the best option when I'm hard bricked?
Click to expand...
Click to collapse
It means that a portion of your internal memory went to an irremediably unusable state. Looks like it may be possible to get it back to life by using a specially tailored PIT (the thread is for the Note, but the OP added a PIT for the P6800 in the first post. He may build a PIT for other devices, if you ask him to). You lose a few GB of your /sdcard (data) storage, and all data on your device, but you get it back. The other option is to go to a Samsung's repair centre and say you left it charging overnight and couldn't turn it on in the morning, or something to that effect.
kencad said:
what then is the safest way to format my tab/restore to factory settings in ICS?
Click to expand...
Click to collapse
Install locerra's CWM and do the data reset from there. Alternatively, I've never seen someone get a brick by erasing through the Settings menu.
Thanks a lot. After reading this forum, I immediately searched for locerra's CWM and updated the one I installed. Now I have the v. 6.x.x.x and it's great.
Thanks steve_max for explaining and locerra for the CWM for 7.7
I just made a backup of my current rom(stock) and hopefully, I may try CM9 after some reading. (still a newbie)
Sent from my GT-P6800 using XDA Premium HD app
Guys i came up with an idea
to change the kernel
by rewriting the kernel
i know this idea is crazy
but i just came up with this idea because im soo sick of using this stock roms stuck too much unlike the unlocked ones
im having 12W01 w8 mobile no wonder i bricked my phone twice
every one knows that we can modify the codes using rom manager so we just have to copy and paste whats in nAa kernel methods and implementations to stock tweaks
hope this will work
DEVELOPERS please consider
eh? explai better? you wanna unlock the bootloader with kernel for install kernel? ._.
its like this after 11W29+ they have blocked the kernel right
but still with using tools we can modify the running methods and implement new
so as i was trying to say it has to work if we replace the whole nAa Kernel methods and implementations to stock the whole bunch with out removing the kernel files
I dont think you can mod it whitout flashing it again...
Sent from my X8 using xda app-developers app
eh, nice idea bro!
but still, i don't think it could be possible without unlocked bootloader and trying it may brick your phone again as u need to probably reflash it, as said by Lukenda too...
good luck if you wanna try it. :good:
fingers crossed :fingers-crossed:
Do you mean something like this? I don't know if it works on X8 but with this thing we could be able to "install" custom kernels on devices with locked bootloader.
fifo171 said:
Do you mean something like this? I don't know if it works on X8 but with this thing we could be able to "install" custom kernels on devices with locked bootloader.
Click to expand...
Click to collapse
That could work. But i think the op is talking about modifying the kernel the phone is on as opposed to running a kernel on top of what's already there. At least that's how i understood the guide...
Sent from my rooted tomato using xda app
@OP : As long as the bootloader is locked, you can modify all the kernels you want, but it still won't be flashable to our phones.
untill your bootloader locked you cant flash any kernel mod into your device :'(
rohin he means to say to make changes in the stock kernel present in the phone some how and not flash new kernel...
it might work if some developer works on it....like alfsamsung and nobodyatall coming together and do it?
aZuZus method might be some help.. may be cwm flashable kernel? but that would require unlocked bootloader too.
CnC-ROCK said:
rohin he means to say to make changes in the stock kernel present in the phone some how and not flash new kernel...
it might work if some developer works on it....like alfsamsung and nobodyatall coming together and do it?
aZuZus method might be some help.. may be cwm flashable kernel? but that would require unlocked bootloader too.
Click to expand...
Click to collapse
To tamper with even the stock kernel, the bootloader needs to be unlocked. It's like trying to edit a stock rom (2.1 like Matej2010) without root. It's impossible.
Are you sure it won't work on locked BL? Then how is it possible that with kexec method X10 users can run custom kernels with locked BL? AFAIK they use the kexec to unload stock kernel and load custom kernel (for example like doixanhs DT module - it unloads the stock screen driver and loads the modified one. I think that kexec does the same with the whole kernel).
Provided you can load/unload the whole kernel w/o f*cking the system up
RohinZaraki said:
Provided you can load/unload the whole kernel w/o f*cking the system up
Click to expand...
Click to collapse
i suppose that if x10minipro can do it then so can x8
Yeah, maybe it's possible. Isn't here anyone to so that willingly?
Sent from my MANGO using Tapatalk2
Infact idea is working on the Samsung Galaxy S3 whereby Kexec is loading and selecting the boot from the recovery partition
But then we does need figure out a way to enable the system to boot from different partition.
hell of a work to rewrite script
Somebody should ask nAa and dx,they should know the answer
Sent from my X8 using xda app-developers app
@all azuzu's SBoot tool will make use of the kexec module. A kernel with a kexec module does not necessarily need an unlocked bootloader. It will (AFAIK) load up the new kernel for debugging over the existing stock kernel. We won't see such a kernel soon but that soon doesn't necessarily mean never.
Can we run 2 kernel om 2 different roms,like multibooting them? That way would be possible..
Sent from my X8 using Tapatalk 2
Lukenda said:
Can we run 2 kernel om 2 different roms,like multibooting them? That way would be possible..
Sent from my X8 using Tapatalk 2
Click to expand...
Click to collapse
Huh? Really explain what you mean and give an example if you can.
a while ago back when the S2 was relatively new there was some custom recoveries released that had a dual boot option you could do. siyah was the only one i found that had this at the time. later on it stopped being supported and i miss it.
I am now wondering if it is possible to have a dual-boot option for the S4 and if someone is working on it. i know it requires a custom kernel as well as a custom recovery but that is as far as my knowledge goes.
Buddyjohn said:
a while ago back when the S2 was relatively new there was some custom recoveries released that had a dual boot option you could do. siyah was the only one i found that had this at the time. later on it stopped being supported and i miss it.
I am now wondering if it is possible to have a dual-boot option for the S4 and if someone is working on it. i know it requires a custom kernel as well as a custom recovery but that is as far as my knowledge goes.
Click to expand...
Click to collapse
Forever taunting me in my dreams.... Want this capability SOOOO BADLY!
couldn't aroma be used for a for a dual boot? just a thought.
TheAxman said:
couldn't aroma be used for a for a dual boot? just a thought.
Click to expand...
Click to collapse
i suppose it could, i have not looked into that at all.
I also have no idea how to do aroma so i guess that still adds to the question of if anyone is working on this or not
I had this on my nexus 7 and its the best thing ever
Sent from my SAMSUNG-SGH-I337 using Tapatalk 4 Beta
Buddyjohn said:
i suppose it could, i have not looked into that at all.
I also have no idea how to do aroma so i guess that still adds to the question of if anyone is working on this or not
Click to expand...
Click to collapse
I mean, you can add into what you want, and it executes what you specify. I am no dev by all means, but......
If you come up with something, I will try it.
TheAxman said:
I mean, you can add into what you want, and it executes what you specify. I am no dev by all means, but......
If you come up with something, I will try it.
Click to expand...
Click to collapse
I am no dev either. which sucks. but if a dev sees this thread by all means feel free to take on this project and let us know!
Buddyjohn said:
a while ago back when the S2 was relatively new there was some custom recoveries released that had a dual boot option you could do. siyah was the only one i found that had this at the time. later on it stopped being supported and i miss it.
I am now wondering if it is possible to have a dual-boot option for the S4 and if someone is working on it. i know it requires a custom kernel as well as a custom recovery but that is as far as my knowledge goes.
Click to expand...
Click to collapse
It can happen only thing is I'm not sure how it would work u need both custom recovery and custom kernel on the s2 both were linked on the s4 they r not ( which is nice love twrp over cwm ) so a kernel dev would have to make a kernel and a recovery to support both plus there's the Loki factor for all the users who use the cwm auto Loki recovery ( I just use the Loki doki zip for twrp I stead ) so it will have a lot of factors but there is only 3 separate kernel devs for this device ATM
KT ( doubt he has the time or the want to dev this ) no speaking for him
Faux ( his kernel is tw only and his plate is full ATM with many devices and apps )
And
Albinoman887 ( aosp only kernel and not sure on his kernel dev knowledge as far as something this complex goes )
sent from my SGH - leet ( i337) using Tapatalk 4 beta
oddspec said:
It can happen only thing is I'm not sure how it would work u need both custom recovery and custom kernel on the s2 both were linked on the s4 they r not ( which is nice love twrp over cwm ) so a kernel dev would have to make a kernel and a recovery to support both plus there's the Loki factor for all the users who use the cwm auto Loki recovery ( I just use the Loki doki zip for twrp I stead ) so it will have a lot of factors but there is only 3 separate kernel devs for this device ATM
KT ( doubt he has the time or the want to dev this ) no speaking for him
Faux ( his kernel is tw only and his plate is full ATM with many devices and apps )
And
Albinoman887 ( aosp only kernel and not sure on his kernel dev knowledge as far as something this complex goes )
sent from my SGH - leet ( i337) using Tapatalk 4 beta
Click to expand...
Click to collapse
they just got it working on internation s4. Im not sure if this works with the ATT version of the s4..it may or may not.
I believe the bootloader needs unlocked first
Sent from my GT-I9505 using xda premium
jball said:
I believe the bootloader needs unlocked first
Sent from my GT-I9505 using xda premium
Click to expand...
Click to collapse
This is right, it exists for international but requires unlocked bootloader. However, a dev named Hashcode is porting his safestrap recovery to Verizon S4, and it should come to us afterwards, which will allow you to boot stock rom along with 4 custom rom slots.
OK so I have no clue really want safestrap is really. I've only had phones that I could unlock my bootloader.
I guess my questions are is how much different is safestrap vs unlocked bootloader and did Verizon/Samsung lock this thing down to the point we can't unlock this thing.?
I just bought this phone on Verizon edge and had no knowledge about this thing being locked down.
Simple search will help.
Safe strap allows you to Flash stock ROMs and stock kernels. It is not a bootloader bypass. You cannot have recovery at this time. The chance of an actual bootloader unlock and/or recovery is slim.
We currently do have root.
If you want to do anything other than flash stock based ROMs and kernels (when SS is available, which is likely soon), then you should use a different device or get the Dev edition when it comes out.
You should do more research before putting that much money on a device down. I want the Note3 very much, but I much prefer a device with more flexibility, even if it isn't as badass.
I've had safe strap on my bionic and flashed asop ...but why would anyone on this device want asop??? ...that would not make a lot of..."touchwiz" lol.
Thanks for the reply. Yes your correct but no need to be an douche. Yes search answers questions but people who have used safestrap can sometimes provide better answers. This is the q&a section so that means you can ask questions. Anyways thanks for part of your reply.
Sent from my SM-N900V using xda app-developers app
jprovan1 said:
Thanks for the reply. Yes your correct but no need to be an douche. Yes search answers questions but people who have used safestrap can sometimes provide better answers. This is the q&a section so that means you can ask questions. Anyways thanks for part of your reply.
Sent from my SM-N900V using xda app-developers app
Click to expand...
Click to collapse
I hope that was for the jerk and not the joke.....
Was for the jerk. I liked the joke
Sent from my SM-N900V using xda app-developers app
xdadevnube said:
Simple search will help.
Safe strap allows you to Flash stock ROMs and stock kernels. It is not a bootloader bypass. You cannot have recovery at this time. The chance of an actual bootloader unlock and/or recovery is slim.
We currently do have root.
If you want to do anything other than flash stock based ROMs and kernels (when SS is available, which is likely soon), then you should use a different device or get the Dev edition when it comes out.
You should do more research before putting that much money on a device down. I want the Note3 very much, but I much prefer a device with more flexibility, even if it isn't as badass.
Click to expand...
Click to collapse
This is wrong. Safestrap is a bootstrap recovery. It IS a "bootloader bypass" of sorts. Once everything is squared away, safestrap WILL allow flashing of non-stock ROMs and the execution of Kexec kernels. We will have access to almost everything available with an unlocked bootloader, except it will require room on our internal storage for the ROM files.
Banggugyangu said:
This is wrong. Safestrap is a bootstrap recovery. It IS a "bootloader bypass" of sorts. Once everything is squared away, safestrap WILL allow flashing of non-stock ROMs and the execution of Kexec kernels. We will have access to almost everything available with an unlocked bootloader, except it will require room on our internal storage for the ROM files.
Click to expand...
Click to collapse
AFAIK, it will not allow kexec, as that is a different exploit. Also, it cannot modify aboot. So you will not be able to install AOSP ROMs or anything but a modified stock kernel. Believe me, I would love to be wrong.
xdadevnube said:
AFAIK, it will not allow kexec, as that is a different exploit. Also, it cannot modify aboot. So you will not be able to install AOSP ROMs or anything but a modified stock kernel. Believe me, I would love to be wrong.
Click to expand...
Click to collapse
Hashcode has implemented kexec into nearly every device's safestrap. Also, AOSP is still possible with the stock kernel. You simply have to incorporate certain parts of the stock ROM. I did all of this on the Droid Bionic. I had an AOSP ROM before safestrap was even created. It had a couple Blur elements that were very minor, but required.
Do we loose safestrap if we take OTA upgrade to Kitkat (when it's available)?
Banggugyangu said:
Hashcode has implemented kexec into nearly every device's safestrap. Also, AOSP is still possible with the stock kernel. You simply have to incorporate certain parts of the stock ROM. I did all of this on the Droid Bionic. I had an AOSP ROM before safestrap was even created. It had a couple Blur elements that were very minor, but required.
Click to expand...
Click to collapse
I was thinking of the S4 that doesn't have kexec and cannot flash AOSP. It is reasonable to assume that the N3 could get kexec even although the S4 doesn't have it.
SS is not bootloader bypass. Many benefits of an unlocked bootloader will not be realized with SS. However, it should be a decent option for at least getting some ROMs. With kexec, then most people will be happy.
xdadevnube said:
I was thinking of the S4 that doesn't have kexec and cannot flash AOSP. It is reasonable to assume that the N3 could get kexec even although the S4 doesn't have it.
SS is not bootloader bypass. Many benefits of an unlocked bootloader will not be realized with SS. However, it should be a decent option for at least getting some ROMs. With kexec, then most people will be happy.
Click to expand...
Click to collapse
There is a huge difference when Hashcode has the phone in question. It's my understanding that this is the first Samsung phone he has had.
So he's stated that he plans to add kexec? That would be [email protected]$$.
Sent from my SM-N900V using Tapatalk
Hi,
Some of you may recognise my name from around the forums, especially if you have had an Xperia device before. I started my first android developments on the Xperia Play and then continued onto the Xperia U. I then lost mass interest in development due to joining college and being overloaded with work due to a computing course. I was no longer able to contribute to any developments.
Now, I am in the second year of college and have dropped a subject I am finding myself with more free time so I have decided to start developing again, only this time I have an Xperia SP.
There's only one catch, the device I have is network locked to O2 and therefore I cannot unlock my boot loader, so most if not all of my work will be for those with a locked bootloader. I am mostly interested in creating custom ROMs based on stock and also creating my own applications and embedding them into the stock ROM.
And the flashy bar at the bottom, yeah I have ideas for that.
Developments for Xperia SP:
illumination app
~Keiran
Sent from my C5303 using Tapatalk
Thank you!
Sent from my C5303 using XDA Premium 4 mobile app
Thank you!
Thank you guy!
You have locked bootloader and you don't use fastboot
You should sell branded phone and buy no-branded
MrZender said:
Thank you guy!
You have locked bootloader and you don't use fastboot
You should sell branded phone and buy no-branded
Click to expand...
Click to collapse
I can't, it just means that I will only be able to developed for locked bootloader which is no problem really. All it means is that I cannot change the kernel image, using scripts I can mess about with the ramdisk though and may be able to boot CM on a locked boot loader if the stock kernel allows it.
Sent from my C5303 using Tapatalk
Glad to see you back in the game mate ! Too bad that you can't unlock your bootloader. Although I know that would not be a problem for you.
Sent from my C5303 using Tapatalk
Hi @KeiranFTW welcome to Xperia SP development!
I hope we can work together on a project I want to try when we get the Android 4.3 update, I'm not sure if it will be successful and I'm not sure if anyone else tried this on other devices, but I want to try.
Basically I want to build Android 4.3 that works with the stock Sony 4.3 bootloader. I already have my fork of CodeAurora up and running here, I call it recaf, it will 'simply' be a matter of satisfying the extra dependencies and other Sony changes.
Come chat on freenode IRC, I'm in #freexperia, or on my own at #recaf. (If I don't reply immediately it mean's I'm afk, but my irc bouncer keeps me logged in.)
adfad666 said:
Hi @KeiranFTW welcome to Xperia SP development!
I hope we can work together on a project I want to try when we get the Android 4.3 update, I'm not sure if it will be successful and I'm not sure if anyone else tried this on other devices, but I want to try.
Basically I want to build Android 4.3 that works with the stock Sony 4.3 bootloader. I already have my fork of CodeAurora up and running here, I call it recaf, it will 'simply' be a matter of satisfying the extra dependencies and other Sony changes.
Come chat on freenode IRC, I'm in #freexperia, or on my own at #recaf. (If I don't reply immediately it mean's I'm afk, but my irc bouncer keeps me logged in.)
Click to expand...
Click to collapse
I'm sure it is very possible, as there is a way that could work really, I could probably set it up as a dual boot. You would need the AOSP ramdisk in tar format somewhere on your phone and at boot time if you wish to boot AOSP then it would delete everything at / and extract that ramdisk to / and then continue boot process with that ramdisk.. as long as stock kernel is compatible.
Sent from my C5303 using Tapatalk
Welcome in SP section
Happy to see more real dev here
Well, maybe you could port kexec to our locked SP's? The main part of the module and binary is done, there is only one thing left - implementing proper hardboot and finally porting to our phones. I think some Xperia SP devs might help you. There's a thread in Z1 forums where delewer tries to get last parts of the job done. If you decide to start working on it, I want to be a alpha or beta tester
http://forum.xda-developers.com/showthread.php?t=2495152
Welcome mate, glad you are here can't wait to see your work I also had an xperia play and I'm pretty sure I had a few of your roms and mods installed at some point.
Sent from my C5303 using XDA Premium HD app
I have a few projects in mind at the moment:
1. Getting the 4.3 leak to boot on locked bootloader
2. When 4.3 is released get AOSP 4.3 to run also on locked boot loader - I will be working with @adfad666 on this - most priority
3. Maybe a stock based custom ROM - least priority.
Sent from my C5303 using Tapatalk
Maybe after booting AOSP 4.3 on locked BL you could try booting 4.4? Because it was possible in Xperia X8 "age of glory"(some devs booted 2.2 on 2.1 kernel if I'm not mistaken).
MrSteve555 said:
Maybe after booting AOSP 4.3 on locked BL you could try booting 4.4? Because it was possible in Xperia X8 "age of glory"(some devs booted 2.2 on 2.1 kernel if I'm not mistaken).
Click to expand...
Click to collapse
We could try.
The way I'm going to do it is hijack pre_hw_config.sh and then launch a script from there to determine whether to extract recovery ramdisk or AOSP ramdisk, then this will be extracted to /, and then everything will be unmounted and init will be started again to restart the boot process.
Sent from my C5303 using Tapatalk
I think I'll try to boot 4.3 today, with the method described in this thread: http://forum.xda-developers.com/showthread.php?t=2593806
I'll post my results later.
KeiranFTW said:
We could try.
The way I'm going to do it is hijack pre_hw_config.sh and then launch a script from there to determine whether to extract recovery ramdisk or AOSP ramdisk, then this will be extracted to /, and then everything will be unmounted and init will be started again to restart the boot process.
Sent from my C5303 using Tapatalk
Click to expand...
Click to collapse
Unfortunately pre_hw_config.sh doesn't exist in the 4.3 leak, so assuming that doesn't change when we receive the official update, we won't be able to use that.
adfad666 said:
Unfortunately pre_hw_config.sh doesn't exist in the 4.3 leak, so assuming that doesn't change when we receive the official update, we won't be able to use that.
Click to expand...
Click to collapse
then /system/bin/charger
Sent from my C5303 using Tapatalk
Well, pre_hw_config.sh doesn't exist even in stock 4.1.2. I think we should try with chargemon, not charger(because it's executed earlier). I tried booting DooMLord's DoomKernel ramdisk on stock kernel. Absolutely no luck. I don't even know what's wrong - after loading ramdisk, kernel panic occurs. Maybe someone more clever will figure it out.:silly:
I think I'm nearly there at hijacking the boot process to inject new ramdisk, I just have a little test that I will have to do later as I need to go out now.
What I'm going to do is use the same ramdisk as that's in the kernel but inject it again after removing anything, this way I don't need to change my ROM and I know that I can inject a new ramdisk. I'll upload my work to github later too so people can contribute
~Keiran
Sent from my C5303 using Tapatalk
Okay, so I've been successful in booting a custom RAMdisk, only problem I am experiencing is that the data partition is not being remounted when the new ramdisk is loaded, no idea why though.
Okay, done and fixed, sources are at https://github.com/keiranFTW/hijack-ramdisk-huashan
Get ready for exciting things coming now
KeiranFTW said:
Okay, so I've been successful in booting a custom RAMdisk, only problem I am experiencing is that the data partition is not being remounted when the new ramdisk is loaded, no idea why though.
Okay, done and fixed, sources are at https://github.com/keiranFTW/hijack-ramdisk-huashan
Get ready for exciting things coming now
Click to expand...
Click to collapse
I tried your method, but it has one bug - it doesn't symlink /data/media to /storage/sdcard0, so the data from internal memory isn't accesible through that path. Still amazing work, but I suggest you to change the format of ramdisk read by the script to .cpio, because it's easier to get from kernels. :good: