Database Info

pre rooted 2.3.6 NS i9020a att rom? anywhere

I have to restore my phone due to some error where it cant stay on googles servers and its killing my battery FAST!
is there a pre rooted 2.3.6 rom out there with super user and BB already on it.
I tried search the dev page but nothing ccame up
thanks, kind of need ASAP

tevil said:
I have to restore my phone due to some error where it cant stay on googles servers and its killing my battery FAST!
is there a pre rooted 2.3.6 rom out there with super user and BB already on it.
I tried search the dev page but nothing ccame up
thanks, kind of need ASAP
Click to expand...
Click to collapse
all the custom roms are "pre rooted".

simms22 said:
all the custom roms are "pre rooted".
Click to expand...
Click to collapse
I think he is talking about a rooted stock rom for his 9020a.... There should be a couple of them on the development section..

yeah sorry i meant stock. Im not really a fan of any of the custom ones after trying so many.
Ive tried running the search on the dev forum for "2.3.6" and it comes up with nothing. but after last night i used a few OLD backups and realized it weasnt the ROM.
Maybe ill try a new kernel. something is up with my phone or service but im starting to think its the phone. nothing makes sense why its acting up like this.

tevil said:
yeah sorry i meant stock. Im not really a fan of any of the custom ones after trying so many.
Ive tried running the search on the dev forum for "2.3.6" and it comes up with nothing. but after last night i used a few OLD backups and realized it weasnt the ROM.
Maybe ill try a new kernel. something is up with my phone or service but im starting to think its the phone. nothing makes sense why its acting up like this.
Click to expand...
Click to collapse
Since you are running CWM already (or atleast i assume so) getting stock and rooted is a piece of cake.
Grab the full ROM image for your phone from here.
http://forum.xda-developers.com/showthread.php?t=1063664
grab the SU binary from here: http://bit.ly/su2361ef
copy both ZIP files to your SD card
apply the full ROM zip
apply the su binary zip
wipe system, wipe dalvik
reboot

Matridom said:
Since you are running CWM already (or atleast i assume so) getting stock and rooted is a piece of cake.
Grab the full ROM image for your phone from here.
http://forum.xda-developers.com/showthread.php?t=1063664
grab the SU binary from here: http://bit.ly/su2361ef
copy both ZIP files to your SD card
apply the full ROM zip
apply the su binary zip
wipe system, wipe dalvik
reboot
Click to expand...
Click to collapse
Good posy, thanks for info!
Sent from my Nexus S using XDA App

okay does this even make sense?!!?!?!?
Today i was troubleshooting the problem again. I decided to go to the google market and see if it could see my phone.
It did but it was an unnamed device (which it usually is).
I named it, and its been green all morning.... WTF?!?!?!

[CAUTION][ICS][UPDATE][DOWNGRADE]Read before flashing ICS

After the ICS was leaked, it bought some good news and as well some bad news..
Some of our user have just bricked their mobile after performing a wipe data thru recovery..
The cause of error is yet unknown..
Out user vijai has published some of the known causes...
The credit goes to vijai for pointing it out
vijai2011 said:
CAUSES
Symptoms of super brick(caused by emmc bug):
1.Phone gets stuck at splash screen.
2.recovery gets stuck at whenever trying to access corrupted partition.
3.ODIN gets stuck at flashing factoryfs.
4.You can flash kernel but almost nothing else using both ODIN and cwm.
Sent from my GT-N7000 using xda app-developers
Click to expand...
Click to collapse
vijai2011 said:
FIX
No problem....temporary fix to avoid bricking is to avoid using cwm to flash anything,doing wipes in cwm,formatting partitions in cwm,doing factory reset through settings and by typing code in phone,removing large size files from sdcard.
The permanent fix is to disable MMC_CAP_ERASE in kernel while making it.Any kernel dev can do that easily I guess....
Sent from my GT-N7000 using xda app-developers app
Click to expand...
Click to collapse
This definitely doesn't mean that all galaxy R handset are brick bug or you may encounter such problem..
Only a few have encountered the problem and the cause is yet unknown. This definitely, doesn't stop you from flashing ics..if you want to flash keep these things in mind.
Also, please do not completely rely on brick bug app from play store because the app (imo) is not supported to our device (correct me if i am wrong)
(i am no developer, just heard from my fellow user )
*****NOTE******
This applies to the Stock ROM released by machram and as well to all those ROM which are based/built upon the Stock ROM.
Click to expand...
Click to collapse
SO WHAT DOES IT MEANS TO YOU ?
If you have already flashed ICS, you are requested not to wipe data through CWM/Stock recovery and also do not factory reset the phone till the issue is identified. i.e. Once ICS === No Wipe (till its rectified)
Click to expand...
Click to collapse
Currently there are only two users who have hard bricked their phone after flashing ICS.
As you might be aware by now that the emmc brick bug app is not compatible with our phone.
The most elite developer Entropy512 wants to make it compatible and hence wants some sample..
Entropy512 said:
Can someone who experienced damage and still has their device contact me via PM? One of my contacts wants to collect a few damaged devices.
Click to expand...
Click to collapse
Note: I dnt recommend you to brick your phone
(thanks m.kochan, callmeventus, cooleagle)
A big thanks to entropy for showing interest to our device

Caution:
Here's what to say from a user who bricked his phone
mj.vikram said:
Caution:
when you are running ICS on you mobile do not downgrade directly to GB using ODIN, if you flash any GB ROM ROM (Stock/Custom) using ODIN your mobile will be bricked.
Live example is myself i have bricked my mobile by do this.
TO avoid this first you restore previous backup using CWM and then flash what ever you want using ODIN.
even Unbrick your Galaxy R. 2. Downgrade bootloader to v2.0 guide wont help you, I have followed it but no use I have successively flashed stock rom by using this method but still no luck..
Click to expand...
Click to collapse
*******UPDATE********
Here is the new fix method
vijai2011 said:
And guys for the guide to safe flash:
Flash a GB kernel,boot into recovery,flash any rom.GB or ICS.Its safe to wipe in gb kernel.But once you flashed ICS you arent safe.If you need to wipe again,you need a GB kernel again.
This was the method we used in Note to wipe when had not got a safe kernel.
Click to expand...
Click to collapse
We have got one lucky user who is enough brave and tested this method
selva.simple said:
To make a conclusion to that, i have tested your method in Galax R buddy. I found that i had a GB kernel in my phone. So why wait till i reach home. Tested now itself. I tested two rounds. One is for getting ICS via CWM flash and the other is for getting ICS via CWM restore.
First Test:
1. Flashed GB kernel
2. Rebooted to Recovery
3. Wipe data
4. Flash ICS by CWM flash i.e., "Install from Zip" method
5. Reboot
Second Test:
First Three points are same. and finally Restored a nandroid backup of ICS i took earlier. Reboot
In both the method i was able to boot the phone and get the ICS ROM and ICS kernel. To add more,
After both boots, I tested the system apps and data apps - mainly Play store, Gmail, Music player, Gallery, Camera for any FC issues. Everything is working perfectly and no issues created apart from existing issues of ICS.
Click to expand...
Click to collapse

And I forgot to add that It is not necessary that brick occurs once you do the above said things....for example,brick may occur at 10th factory reset,100th flash etc....And it is safe to flash anything with Odin as it shouldn't invoke MMC_CAP_ERASE from kernel when flashing.
Sent from my GT-N7000 using xda app-developers app

vijai2011 said:
And I forgot to add that It is not necessary that brick occurs once you do the above said things....for example,brick may occur at 10th factory reset,100th flash etc....And it is safe to flash anything with Odin as it shouldn't invoke MMC_CAP_ERASE from kernel when flashing.
Sent from my GT-N7000 using xda app-developers app
Click to expand...
Click to collapse
Yes i do agree..d problem may arise on 1st or on 100th wipe...
Bt the cause is yet unknown...
So imho, all the noobs shldnt do..who knows they get it for the first time...
Sent from my GT-I9103 using Tapatalk 2

Seriously? Removing large size files from sdcard can brick my phone?

Fusrodah said:
Seriously? Removing large size files from sdcard can brick my phone?
Click to expand...
Click to collapse
Dont know...but i have tried deleting large files as 1gb game data...such as max payne and asphalt7
No brick...
Sent from my GT-I9103 using Tapatalk 2

Fusrodah said:
Seriously? Removing large size files from sdcard can brick my phone?
Click to expand...
Click to collapse
Yes....sometimes.....it was reported by like 2 users have galaxy Note.While deleting large files,the phone stuck and force reboot caused damaged sdcard.
Sent from my GT-N7000 using xda app-developers app

vijai2011 said:
Yes....sometimes.....it was reported by like 2 users have galaxy Note.While deleting large files,the phone stuck and force reboot caused damaged sdcard.
Sent from my GT-N7000 using xda app-developers app
Click to expand...
Click to collapse
Well, how much reports from Galaxy R users with bricks? I see one from mj.vikram. Anyone else?

So a little story now.
From where has this infamous brick bug appeared??
Analysis by kernel devs say that MMC_CAP_ERASE command in kernels are present from gb periods.But why hasn't it been causing problems in GB?That's because it was disabled as Google didn't see the need for it.
But in ICS they feel that just removing files causes security problems.so they thought of enabling MMC_CAP_ERASE command which will completely wipe instead of removing.
So why should it need to brick our devices?
That's because,one of the Google engineer said that our mmc uses buggy firmware that initiates wrong process when the kernel receives MMC_CAP_ERASE command.
Actually MMC_CAP_ERASE command and mmc buggy firmware are harmless on its own.But when both are combined the result is super brick.
Sent from my GT-N7000 using xda app-developers app

This is not the worst scenario. In worst case you're gonna get hardbrick with no possibility to turn your device on.
MMC_CAP_ERASE on - wasn't present in every ICS version, at least not for S2 (I know that NOte users had bigger problem with that). All previous 4.0.3 were totally safe. Latest 4.0.4 - unfortunately not. It's not really buggy firmware that causes any problem here. According to Entropy512 (I guess the best xda-expert in that matter) MMC_CAP_ERASE was activated in order to improve writing speed. Hard brick occur if the all three conditions are fulfilled here:
1) You have a faulty (brickable) emmc-chip
2) If MMC_CAP_ERASE command is activated in kernel
3) If you perform wipe/restore nand backup/install roms (wipe-type) where:
a) cwm recovery - very high risk
b) stock recovery - lower risk but still not equal 0.
So faulty emmc chip is a bomb, mmc_cap_erase is a fuse, wiping in cwm - is a trigger or fire!
Not all devices are endangered, only those with brickable emmc-chips. In regard to Note or S2 it's easier because those devices have great dev support and there were thoroughly examined. So there are known some ways to bypass this problem. In case of SGR is much harder. First of all ... we don't know which chips are really sane and which are not.

Fusrodah said:
Well, how much reports from Galaxy R users with bricks? I see one from mj.vikram. Anyone else?
Click to expand...
Click to collapse
Just two as of now so don't panic !
You can use ICS 4.0.4 but till the cause of the bricking is confirmed just don't preform any Wipe data / Wipe Cache / Factory reset operations while on ICS 4.0.4 ROM.
As per mkochan if you want to go back to the stock ROM for giving it to the service center / etc then directly flash GB / 2.3.x ROM without wiping the cache / data using CWM.
m.kochan10 said:
1) To avoid brick = don't wipe, don't do factory reset, do not restore nandbackups.
a) If you wanna to get rid of this fw.version
-> Flash a safe kernel / or best stock rom directly via Odin.
-> Wipe after installation process is done. NOT BEFORE!
2) To recover...one guy from Note section wrote a tutorial for those bricked devices that was able to turn on. He managed to recover it but he had to sacrifice 2-3 gb of internal storage. If device is not bootable then it's a motherboard replacement.
3) Turning off this function in kernel is not easy thing. I don't think this flag can be easily removed. I'm not a kernel guy....so I'm sorry but don't know much more about that. Our devs can take a look, maybe they can find a solution.
4) Bootloaders cannot be flashed via recovery, not via mobile odin either. And FW-odin version is still unavailable so I assume you still have GB ones.
5) About USB jig - Is your DM protocol the same like before? 2.0? (people with 2.1 have never been able to used jig as far as I remember)
Click to expand...
Click to collapse

Okay, we must wait for kernel with disabled MMC_CAP_ERASE. I hope we'll get it. Thanks for the information.

Oh my god
I did factory reset in ics because my keyboard dissappeared. Will my device hard brick?
I cannot understand why Samsung realeses a firmware which should make our mobile dead! What is this function even for?
Sent from my GT-I9103 using xda premium

You can find sort of explanation on the previous page

Just wondering should I worry about this if the bug eMMC app reports that I have a sane chip?

Google86 said:
Just wondering should I worry about this if the bug eMMC app reports that I have a sane chip?
Click to expand...
Click to collapse
I think app is not working for SGR, both user have used this app and app shown sane chip yet those both guys devices are bricked.
We should contact dev of app to make comp with SGR.
Sent from my CM7.2 powered Galaxy R using Tapatalk 2.

Damn it , I knew this would happen.....
"Friends forever." - Ventus

Guys actually you could check if you have any bad blocks in any partition through gpartrd in adb.Just looking its info.will post when I find some.
Sent from my GT-N7000 using xda app-developers app

OP please add this also,
Caution:
when you are running ICS on you mobile do not downgrade directly to GB using ODIN, if you flash any GB ROM ROM (Stock/Custom) using ODIN your mobile will be bricked.
Live example is myself i have bricked my mobile by do this.
TO avoid this first you restore previous backup using CWM and then flash what ever you want using ODIN.
even Unbrick your Galaxy R. 2. Downgrade bootloader to v2.0 guide wont help you, I have followed it but no use I have successively flashed stock rom by using this method but still no luck ..
Sorry i have't seen this thread and created new one, so if you think i have created duplicate one please ask Justin to delete it....

mj.vikram said:
OP please add this also,
Caution:
when you are running ICS on you mobile do not downgrade directly to GB using ODIN, if you flash any GB ROM ROM (Stock/Custom) using ODIN your mobile will be bricked.
Live example is myself i have bricked my mobile by do this.
TO avoid this first you restore previous backup using CWM and then flash what ever you want using ODIN.
even Unbrick your Galaxy R. 2. Downgrade bootloader to v2.0 guide wont help you, I have followed it but no use I have successively flashed stock rom by using this method but still no luck ..
Click to expand...
Click to collapse
Dude i dont have a GB Backup (CWM BACKUP)
and dude, what you gonna do now, how will you get back your phone ???

Cyanogenmod 9. boot taking very long!

i have rooted and unlocked bootloader on my htc one x from at&t. i installed twrp. i downloaded and copied this rom to my phone and i am now trying to flash it. http://onexroot.com/one-xl-roms/cm10-jelly-bean-rom-for-att-one-xone-xl/
what was weird is that when its booting it says cyanogenmod 9 not ten.
it has been at least 10 minuets now and i need to know how to fix this. thankyou.

Well...
First off. If you know about XDA (Which is clear, since you're posting your problem here in the forum), why did you download a ROM from another site? One that doesn't look as 'legitimate' as XDA?
Second. CM10 doesn't have a boot animation yet (They may now, but the ROM you downloaded may not have been updated.) There was a CM10 ROM here on XDA that was using the CM9 animation due to lack of CM10 bootanimation.
It sounds to me like something went wrong when flashing. You need to reboot into twrp and reflash the ROM. I highly recommend downloading a ROM from XDA and going that route.

HTC_Phone said:
First off. If you know about XDA (Which is clear, since you're posting your problem here in the forum), why did you download a ROM from another site? One that doesn't look as 'legitimate' as XDA?
Click to expand...
Click to collapse
Completely agree here. That website looks pretty dodgy. Loaded with ads, it doesn't give much information on what you are even downloading/installing, and it doesn't seem to be posted by the actual developer, or give any credit to them (aside from the brief "Credits - XDA" link at the bottom of the article. Plus the download location is not the same as the original Developer's link, which would worry me (to say the least). I'd avoid downloading from this site, unless you have a legit reason to believe its reputable. But it just looks like one of those unscrupulous sites that posts contents from other sources, and rakes in ad revenue from clueless vendors.
Also, the version of the ROM linked is 3 weeks older than what the dev has posted here on XDA, with the newer version having fixed lots of stuff.
Stick to the Development subforums here. Much safer.

If you are looking for a safe ROM to install, I highly suggest you look through this XDA. There is a nearly flawless CM10 ROM here. I user it for a little while and loved it, but missed Sense too much and switched to CleanROM
Sent from my HTC One X using xda app-developers app

ewokiscool said:
i have rooted and unlocked bootloader on my htc one x from at&t. i installed twrp. i downloaded and copied this rom to my phone and i am now trying to flash it. http://onexroot.com/one-xl-roms/cm10-jelly-bean-rom-for-att-one-xone-xl/
what was weird is that when its booting it says cyanogenmod 9 not ten.
it has been at least 10 minuets now and i need to know how to fix this. thankyou.
Click to expand...
Click to collapse
I would strongly recommend doing a full wipe and factory reset before anything else. Who knows what you actually installed?
There are a LOT of sites out there offering what purports to be legitimate android software but is actually malware. Android's openness is a big plus but is also a risk. You have to be careful where you get apps and roms from. Just googling for them is going to get you in trouble very quickly.
Here's just one good example:
http://blog.trendmicro.com/malware-masquerades-as-flash-player-for-android/

HTC_Phone said:
Well...
First off. If you know about XDA (Which is clear, since you're posting your problem here in the forum), why did you download a ROM from another site? One that doesn't look as 'legitimate' as XDA?
Click to expand...
Click to collapse
Lol I said the exact same thing to this guy in his other thread when he thought he bricked his phone. Some people never learn.

Steps to fix your problem
1) are u coming from a sense 4.0.4 ROM/stock? If so u have an incompatible hboot. This will cause boot loop like what u are seeing if this is the case you have to change to the older boot.img (if u updated to the newest at&t ota ur on 4.0.4 if ur coming from a ROM like clean ROM 4.5 ur on 4.0.4) this is most likely your problem to fix this you need to use fast boot to change the boot.IMG I don't know the exact procedure off the top of my head but ull find it with a quick search
2) if not and ur coming from sense 4.0.3 then you should reboot to twrp and wipe cache/dalvic cache this should fix it
3) if not wipe everything (except SD card) this means cache, dalvik cache, factory reset, and system then reflash.
Important definitely grab the newest build from here like what was mentioned earlier.
Sent from my One X using xda app-developers app

ewokiscool said:
i have rooted and unlocked bootloader on my htc one x from at&t. i installed twrp. i downloaded and copied this rom to my phone and i am now trying to flash it. http://onexroot.com/one-xl-roms/cm10-jelly-bean-rom-for-att-one-xone-xl/
what was weird is that when its booting it says cyanogenmod 9 not ten.
it has been at least 10 minuets now and i need to know how to fix this. thankyou.
Click to expand...
Click to collapse
CM10 currently uses the CM9 boot animation. If you have AT&T 2.20 software, then you need to flash the boot.img using fastboot or CM10 (and all ROMs) will just stay in the boot animation for ever. Why didn't you download CM10 from XDA?

[Hard Brick] JTag vs Manuf. Warranty Exchange

I just hard bricked my sgs3. FIRST TIME EVER!! I've been flashing roms,kernels, etc since the MyTouch3.
Little back story.....
I flashed the LSmooth - Linaro 4.2.1 Jelly Bean Rom with CWM6. I noticed that I could not find my nandroid backups. Searched XDA and saw a thread that stated that TWRP is compatible with 4.2.1 and it will move the internal /sdcard from /0 back to its original file location, etc, etc. I went to GooManager, downloaded the twrp.tar (d2vzw), then went to MobileOdin, loaded the .tar file and flashed.
BOOM!!! No power, DOA. dead ass!! :crying::crying:
(( FACE SLAP )) then I remembered via build.prop it was configured as "maguro" and not "d2vzw". So, I'm assuming that since I failed to edit the build.prop before flashing the d2vzw TWRP recovery, it bricked my phone.
-- No power via wall, usb
-- No download / recovery mode
-- NOTHING!
My question is, if I were to call in and ask for a warranty exchange, what is the likely hood of Verizon troubleshooting, reviving my phone and figuring it out that its been rooted?
Or, should I just send my phone to someone that can JTAG it for me?

Idk if you're permanently hard bricked. Reason being is because this person flashed the latest twrp using GooManager but it installed the Maguro version. Different method but they were able to get out of it. Have you tried pulling the battery then booting holding all three buttons for like 15-20 seconds? Might take a few tries.

Verizon could care less I think.
I have had three droid razrs replaced just because of a boot loop and if they would look into the memory, they could clearly see I rooted if.
Sent from my SCH-I535 using xda app-developers app

SlimSnoopOS said:
Idk if you're permanently hard bricked. Reason being is because this person flashed the latest twrp using GooManager but it installed the Maguro version. Different method but they were able to get out of it. Have you tried pulling the battery then booting holding all three buttons for like 15-20 seconds? Might take a few tries.
Click to expand...
Click to collapse
I saw that post, lol. I tried that, but I will try it again. thanks

barrackOBAMA said:
Verizon could care less I think.
I have had three droid razrs replaced just because of a boot loop and if they would look into the memory, they could clearly see I rooted if.
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
Cool! Thanks!

MOD Close Thread, pls
MOD,
Can you close this thread please. Got my replacement today, so I'm Good.!!

[Q] I think my phone is bricked

as title states hard bricked after install of orthus eight then rebooted and nothing. followed instructions and still bricked. i have flashed many roms i don't know what went wrong with this flash. Will a jig work to unbrick to download mode? I have tried several methods to get into download and cant seem to succeed.

Re: [Q] Orthus eight hard bricked phone
I don't think the rom had anything to do with it. I've flashed it and it's fine.
What was the best thing before sliced bread?

baddogie said:
as title states hard bricked after install of orthus eight then rebooted and nothing. followed instructions and still bricked. i have flashed many roms i don't know what went wrong with this flash. Will a jig work to unbrick to download mode? I have tried several methods to get into download and cant seem to succeed.
Click to expand...
Click to collapse
What exactly did you do? And don't just say, "I followed the instructions." I need to know exactly what you did every step of the way from downloading Orthus Eight to laying the cornerstone of your new brick house.
I'll ask this first obvious question because so often it reveals the true problem: what kind of phone do you have?

Lets not go straight in to flaming a user just because he has no posts. I know for a fact there is a brick problem in AOSP 4.2.2. Lets hear him out.

baddogie said:
Will a jig work to unbrick to download mode?
Click to expand...
Click to collapse
I'm not an expert but if you really hard brick the phone then jig would be your solution.
You may want to read the posts on "[ROM][10.1]SUPERLITE CM10.1 JB 4.2.2 > 79mb < | SLGAPPS 10MB | FEB28/13" page 2 and 3 and try to get in touch with the user who bricked the phone and was going to try "JTAG brick repair"
BTW I also installed the ROM and is working smooth.
P.S. I don't think anyone is blaming Ortus8 ROM while the question ... and request for support ... was regarding jig

Re: [Q] Orthus eight hard bricked phone
prbassplayer said:
Lets not go straight in to flaming a user just because he has no posts. I know for a fact there is a brick problem in AOSP 4.2.2. Lets hear him out.
Click to expand...
Click to collapse
A Randomly appearing brick that only affects some and not others this i want proof of sir mod or not i want validation.
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
---------- Post added at 05:28 AM ---------- Previous post was at 05:27 AM ----------
err1max1 said:
I'm not an expert but if you really hard brick the phone then jig would be your solution.
You may want to read the posts on "[ROM][10.1]SUPERLITE CM10.1 JB 4.2.2 > 79mb < | SLGAPPS 10MB | FEB28/13" page 2 and 3 and try to get in touch with the user who bricked the phone and was going to try "JTAG brick repair"
BTW I also installed the ROM and is working smooth.
P.S. I don't think anyone is blaming Ortus8 ROM while the question ... and request for support ... was regarding jig
Click to expand...
Click to collapse
A jig does nothing for a hard brick. You don't need a jig to get to DL mode if soft brick. In short a jig is worthless.
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2

mtdew said:
A Randomly appearing brick that only affects some and not others this i want proof of sir mod or not i want validation.
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
---------- Post added at 05:28 AM ---------- Previous post was at 05:27 AM ----------
A jig does nothing for a hard brick. You don't need a jig to get to DL mode if soft brick. In short a jig is worthless.
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
Click to expand...
Click to collapse
In my opinion it has to do with the kernel, course I could be wrong. However I had 2 testers brick with CM's kernel. I've seen similar reports with the 4.2.2 AOKP around here. In the 2 cases I'm sure the phone booted and ran fine, then randomly locked up and dead. No life afterwards. I understand we all make mistake by both my testers where doing something different when it happen, and the fact the device booted fine THEN bricked (again my particular case) means it flashed fine and whole booted something happen (I believe it blew partitions, possibly secondary or third, if this device has a third, bootloader). If I had any better proof I would have found a solution, or tried to already.

Re: [Q] Orthus eight hard bricked phone
prbassplayer said:
In my opinion it has to do with the kernel, course I could be wrong. However I had 2 testers brick with CM's kernel. I've seen similar reports with the 4.2.2 AOKP around here. In the 2 cases I'm sure the phone booted and ran fine, then randomly locked up and dead. No life afterwards. I understand we all make mistake by both my testers where doing something different when it happen, and the fact the device booted fine THEN bricked (again my particular case) means it flashed fine and whole booted something happen (I believe it blew partitions, possibly secondary or third, if this device has a third, bootloader). If I had any better proof I would have found a solution, or tried to already.
Click to expand...
Click to collapse
I find it hard to believe this was random or attributed to to cm's kernel if nothing else it would be based on something particular to their hardware or your build as you would see a ton of these on cm's thread. You are placing blame in an unlikely place as well.
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2

Re: [Q] Orthus eight hard bricked phone
mtdew said:
I find it hard to believe this was random or attributed to to cm's kernel if nothing else it would be based on something particular to their hardware or your build as you would see a ton of these on cm's thread. You are placing blame in an unlikely place as well.
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
Click to expand...
Click to collapse
Well I was using cms device folders and my qcom hardware folders are constabtly updated with cms commits. Only difference are overlays files and that we use slim.mk which is mostly a copied cm.mk only fixed source locations. Don't know what I did different to create a brick zip. Not my first rodeo, though I'm no expert that's for sure.
Sent from my Nexus 4 using Tapatalk 2

Re: [Q] Orthus eight hard bricked phone
prbassplayer said:
Well I was using cms device folders and my qcom hardware folders are constabtly updated with cms commits. Only difference are overlays files and that we use slim.mk which is mostly a copied cm.mk only fixed source locations. Don't know what I did different to create a brick zip. Not my first rodeo, though I'm no expert that's for sure.
Sent from my Nexus 4 using Tapatalk 2
Click to expand...
Click to collapse
Again if it was cm's doing this would be far more widespread. Something's not adding up, also several people have successfully flashed orthus this is user error nothing more.
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2

mtdew said:
Again if it was cm's doing this would be far more widespread. Something's not adding up, also several people have successfully flashed orthus this is user error nothing more.
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
Click to expand...
Click to collapse
Mate Tell me something I don't know. Same thing with Slim. My test builds where flashed by 50+ people only 2 bricked, so happen both I had most communication with as they where helping me debug the camera problem I had. Like I said if I had a better idea of where the problem laid I wouldn't have stopped working with it (I still fiddle with the code) I just don't have any concrete evidence to work with to merit the chance of bricking other members devices. I originally thought it was me but not the case. There has been posts about this happening on AOKP, I believe on CM (not sure if it was here or not). I'm not saying its a wide spread problem, however its there.

Re: [Q] Orthus eight hard bricked phone
Aokp for this device? Cm for this device? Were the members who bricked very experienced? I'm not saying you don't know what you're talking about but i never trust testers and i especially don't trust people saying such and such ROM bricked my device. I've seen this all too often and all it does is spread fear and give good devs bad names.
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2

Re: [Q] Orthus eight hard bricked phone
Just as an fyi, I loaded Orthus onto my skyrocket just now. Booted fine, restoring apps now
Sent from my SGH-I317 using Tapatalk 2

Re: [Q] Orthus eight hard bricked phone
Been running it since it dropped absolutely no issues smoothest 4.2.2 ROM out.
Sent from my SGH-I727 using xda premium

Re: [Q] Orthus eight hard bricked phone
I'd love to try and help this user.
What methods have you tried to get into download mode?
You said you can reboot, then get nothing. Is that a blank screen? Does the backlight come on?
What recovery were you on? What steps to flash?
Can you get to the device via adb?
Even if I can't help you, maybe we can narrow down the issue.. Whatever it may be.
Sent from my SGH-I727 using Tapatalk 2

damn another brick bug, i thought it was all done with
as for blaming the op, if he had the sr and flashed an sr rom whichever rom that would be, we cant blame the op since theres nothing he could do wrong to actually hardbrick the phone , yes he could softbrick but not hardbrick it.
definition of the bug imo is its totally random, 1 out of x phones it will happen to

T.J. Bender said:
What exactly did you do? And don't just say, "I followed the instructions." I need to know exactly what you did every step of the way from downloading Orthus Eight to laying the cornerstone of your new brick house.
I'll ask this first obvious question because so often it reveals the true problem: what kind of phone do you have?
Click to expand...
Click to collapse
I have a samsung galaxy s2 skyrocket sigh i727. I downloaded the rom from the forums here (i think the link was goo.im) and transfered to my internal sd. I wiped data factory reset, wiped cache patroon, wiped system, wiped delvil cache then flash downloaded zip and half way through the android in background fell over and triangle showed up. I tried restoring backups and eving wiping did not work so I went to advance and restart recovery and the device turned off and now will not respond to anything.

Re: [Q] Orthus eight hard bricked phone
Be careful with goo. I've never been sure what I've downloaded from it.
Most likely not a problem with the rom.
Sent from my SAMSUNG-SGH-I727 using xda app-developers app

mtdew said:
Aokp for this device? Cm for this device? Were the members who bricked very experienced? I'm not saying you don't know what you're talking about but i never trust testers and i especially don't trust people saying such and such ROM bricked my device. I've seen this all too often and all it does is spread fear and give good devs bad names.
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
Click to expand...
Click to collapse
I'm not trying to give any dev a bad name I was just trying to specify what rom I was flashing when this happend

baddogie said:
I have a samsung galaxy s2 skyrocket sigh i727. I downloaded the rom from the forums here (i think the link was goo.im) and transfered to my internal sd. I wiped data factory reset, wiped cache patroon, wiped system, wiped delvil cache then flash downloaded zip and half way through the android in background fell over and triangle showed up. I tried restoring backups and eving wiping did not work so I went to advance and restart recovery and the device turned off and now will not respond to anything.
Click to expand...
Click to collapse
OK. Moving the file from external to internal could cause a corruption. It could have been a bad DL from the start. Hence the reason checking MD5s is so imortant. Either way you should still be able to enter recovery. No ROM that is flashable touches the recovery partition. Pull out your external sdcard and access it with a comp. Copy that files full name here.