Database Users

Need perm root to ROM?

Im not a big developer or hacker of any sort and so i just have a quick simple question. Dont get mad at me for not knowing. But do we NEED a perm root to be able to use ROMS? What happens if we use a rom without perm root? A bricked phone? Erased data? Ive always been wondering this and never came across an answer or a similar thread
Sent from my T-Mobile G2 using XDA App

hawaiian.monzta said:
Im not a big developer or hacker of any sort and so i just have a quick simple question. Dont get mad at me for not knowing. But do we NEED a perm root to be able to use ROMS? What happens if we use a rom without perm root? A bricked phone? Erased data? Ive always been wondering this and never came across an answer or a similar thread
Sent from my T-Mobile G2 using XDA App
Click to expand...
Click to collapse
Tmobile included the chip so it will revert back to stock if it is rooted, therefore eliminating the possibility of a brick. If you call cust support and tell them you are having issues because you tried to root your g2, all they have to say is "reboot your phone." I think tmo did this because of the slew of customers calling cust support when they bricked their g1/mt3gs. Therefore, it is the inexperienced user's faults that tmobile had to install the root kit. If noobs didn't brick their devices so prevalently and ask tmobile for help with their mess up, there wouldn't be a need for the chip.
Sent from my HTC Dream using XDA App

ad505 said:
Tmobile included the chip so it will revert back to stock if it is rooted, therefore eliminating the possibility of a brick.
Click to expand...
Click to collapse
Ugh. This is not only false, but has been repeatedly debunked. There is no chip, mechanism, or anything else that "reverts" the phone back to stock.
The NAND itself is set to be read-only at boot, and no one has yet succeeded in disabling this protection. When people root the G2 and make changes to the system, these changes only appear to be present because the Linux kernel is caching them. They are never written to the device, and so at next reboot (or earlier, when the caches are flushed) they disappear.

itp said:
Ugh. This is not only false, but has been repeatedly debunked. There is no chip, mechanism, or anything else that "reverts" the phone back to stock.
The NAND itself is set to be read-only at boot, and no one has yet succeeded in disabling this protection. When people root the G2 and make changes to the system, these changes only appear to be present because the Linux kernel is caching them. They are never written to the device, and so at next reboot (or earlier, when the caches are flushed) they disappear.
Click to expand...
Click to collapse
Ok, chip or not, the "reboot unroot" was because folks bricked their devices and asked tmobile for help, flooding their customer support and overwhelming their resources. It makes perfect sense to me why this was included in a flagship device like the g1's successor.
Sent from my HTC Dream using XDA App

Its a bug. Don't give tmobile too much credit.
Sent from my HTC Vision G2

luis86dr said:
Its a bug. Don't give tmobile too much credit.
Sent from my HTC Vision G2
Click to expand...
Click to collapse
More like "Unfortunate side-effect of being read-only but appearing as read/write to the OS."
In normal circumstances, it's not an issue (being that nothing needs /system to be r/w for normal operation.) Technically you are operating it out of spec, since you re-mounted /system as r/w.
Not that I agree with it, it's ****ty (and the main reason I returned my G2.)
To answer the OP, yes - two things need to happen before ROMs can be released:
1) Permanent NAND unlock
2) Recovery (Clockwork Mod or similar) to write the ROM to un-locked storage.
Until both of these happen, ROM development is at a standstill.

luis86dr said:
Its a bug. Don't give tmobile too much credit.
Sent from my HTC Vision G2
Click to expand...
Click to collapse
What on earth makes you think it's a bug rather than a deliberate HTC feature?

keenerb said:
What on earth makes you think it's a bug rather than a deliberate HTC feature?
Click to expand...
Click to collapse
One could argue that the controller lying about syncs to "disk" is buggy behavior. But it's clear that it's very much deliberate.

How is it clear that it's deliberate? It only serves to let us mess around with our phones through a temporary root. It doesn't add to the underlying cause that we haven't rooted the phone.
At least, thats what I gathered from the wiki.

Uhhhh....sooooo.....what's the need for a perm root to use a rom again? Either no one answered or I completely missed it and I don't think I missed it haha
Sent from my T-Mobile G2 using XDA App

You're only making changes to the cache, so after using the phone for awhile, parts of the cache get emptied out, and they just go away. This is why when you have temp root, after enough time, your phone will just restart.
I've seen that theres work to get ROMs loading from SD cards, I haven't checked into this myself, so it might just be a pipe dream, but still, do you really want to run everything from your SD card?
At this point, it works better (and longer) to have temp root, and make small changes here and there.
And please someone correct me if I'm wrong on any point.

hawaiian.monzta said:
Uhhhh....sooooo.....what's the need for a perm root to use a rom again? Either no one answered or I completely missed it and I don't think I missed it haha
Click to expand...
Click to collapse
In fact, there is no such thing as permanent root. There is only root, the problem is that anything you do while being rooted is not preserved, as the memory card where the system is is write-protected. So you can't modify the system and make the root available permanently.
And to your question - no, you don't need permanent root to use ROMs. But permanent root needs write access to system and custom ROMs also need write access to the system. So they don't depend on each other, but both depend on another feature - the write access to the system (the integrated memory card, eMMC). Once you get write access, both problems ("permanent root" and custom ROMs) will be solved.

faugusztin said:
And to your question - no, you don't need permanent root to use ROMs. But permanent root needs write access to system and custom ROMs also need write access to the system. So they don't depend on each other, but both depend on another feature - the write access to the system (the integrated memory card, eMMC). Once you get write access, both problems ("permanent root" and custom ROMs) will be solved.
Click to expand...
Click to collapse
Technically, you only need recovery. But the fact of the matter is, they go hand-in-hand. Once one is compromised, the other is as well. This has been the pattern with HTC thus far anyway...

hawaiian.monzta said:
Uhhhh....sooooo.....what's the need for a perm root to use a rom again? Either no one answered or I completely missed it and I don't think I missed it haha
Click to expand...
Click to collapse
I answered here
No roms until those two things happen.

ad505 said:
Ok, chip or not, the "reboot unroot" was because folks bricked their devices and asked tmobile for help, flooding their customer support and overwhelming their resources. It makes perfect sense to me why this was included in a flagship device like the g1's successor.
Sent from my HTC Dream using XDA App
Click to expand...
Click to collapse
If you think this is about anything but control, you're sorely mistaken. They do this because they can, and because they have commitments to Amazon, Photobucket, and every other pre-installed crapware provider they have a contract with to guarantee the user cannot remove their app.
If it's about bricked handsets, why not take the Nexus One approach: Make rooting trivially easy to do - anyone wishing to do so will likely take the path of least resistance. Once rooted, HTC/T-Mo can visually identify a rooted handset and decline warranty service. Problem solved.
franky1029 said:
How is it clear that it's deliberate? It only serves to let us mess around with our phones through a temporary root. It doesn't add to the underlying cause that we haven't rooted the phone.
At least, thats what I gathered from the wiki.
Click to expand...
Click to collapse
It's deliberate because of the whole history behind it. S-ON, write protection, read-only partitions, gold cards, subsidy unlocking, etc. This arms race has gone on for years. All of this is done deliberately.
T-Mobile has an interest in making it as difficult as possible to use the handset on a different network, or use apps they don't like (which, btw, they have not started revoking yet, just wait, it's a matter of time...) Likewise, HTC has an interest in making their customer (T-Mobile) happy.
HTC doesn't give a **** that you, the end user, are unhappy. Their client is T-Mobile.
None of this will change until we (as customers) stop putting up with it, stop buying subsidized handsets from the Provider channel, and start buying un-subsidized handsets straight from the manufacturer. Unfortunately, this isn't going to happen in the U.S. for quite a while - people are too dumb to know what they are doing...
It was no accident that the device is designed to make writing to /system difficult. It was no accident on any other HTC handset either.
Why would you want temporary root over persistent root? It doesn't serve us at all - it only makes it harder on them (HTC - in the long run) once someone like Unrevoked roots it forever.

[Q] Damage By Flashing?

Hello, I'm new to the whole Android thing, but I managed to recently root my Shift, and I can attest to the addictive properties of trying out ROMS/Kernels and all that good stuff. But I was worried about the idea of all this flashing I'm doing, as in the month or so I've been rooted I've flashed about four ROMS, messed up a few times, done a good 5 or 6 Nandroid restores/backups. I was just curios to know if this is excessive, or if this could damage my phone in any way. Thanks for any help guys!
P.S., I apologize if this is either in the wrong thread, or has already been answered >_< I'm still a young'un

As far as I know by flashing a lot you can damage the relationship with your wife or g/f due to spending a lot of time doing it.. besides that I believe that the only way you can damage your phone is due to a bad flash or flashing something that wasn't exactly supported by the Shift.

I recall this discussion back when I had a TouchPro2, I don't know if it applies to the Shift as well but I assume it does. From my understanding it was determined by people far more informed than me that flashing would eventually wear out the NAND memory...but it would take more flashes than even the most fiendish flashaholic could complete in the phones lifetime to do. This is what I know from discussions of a past phone, I'm not claiming anything about the lifetime of the phone and take no responsibility if you flash 5000 ROMS tonight and your NAND burns out. lol

I think the only way you can actually brick your phone from flashing is if you flash a bad ratio from like a gsm carrier to a cdma phone. Might be wrong. Cause even if you flash a bad rom as long as you have a working recovery you can always just reflash a new rom or ruu

I think his underlying question may have to do with the fact that every NAND flash memory module has a limited number of writes in its lifetime before it can't write another bit and tell whether or not the module is in the 0 or 1 state.
This is also why data2ext/apps2ext etc anything that constantly writes information to your SD card will also degrade the lifetime of the SD card.
Basically yes, in principle the number of times you write new data to the phone's built-in memory, you shave off another write from its life. But I don't think this is significant at all. Just as a reference, I'm sure there are people with the original G1 who have flashed a countless number of times over several years and still have it working.

^^This.
If it gives you peace of mind, think about how many times a ROM chef's phone gets flashed in its lifetime and usually if the phone dies it's on account of flashing something experimental that bricks the phone (wrong radio, etc.) I've never heard of someones NAND actually burning out. I flashed my TouchPro and TouchPro2 quite literally hundreds of times if that makes you feel better.

kbrn said:
As far as I know by flashing a lot you can damage the relationship with your wife or g/f due to spending a lot of time doing it.. besides that I believe that the only way you can damage your phone is due to a bad flash or flashing something that wasn't exactly supported by the Shift.
Click to expand...
Click to collapse
THIS. Main danger.
^ Shift Faced

jesusice said:
THIS. Main danger.
^ Shift Faced
Click to expand...
Click to collapse
Agreed!
Sent from my PG06100 using XDA Premium App

Thanks for all the answers, you guys are great I really appreciate your help. You're replies have put my mind at ease seeing as my level of flashing honestly doesn't seem that excessive compared to that of a developer's.
Sent from my PG06100 using XDA App

On my HeroC I changed roms two to three times a week. When CM6 came out, it was everyday (with full wipe) thanks to the nightlies. Then aosp started releasing his stuff in IRC yada yada.
My heroc made it well over a year of that torture. My wife did as well, barely.

Mytouch 4g Bad EMMC Question

I am aware that the questions i am about to ask might have been asked 1000 times, but the search feature didnt help this time, so i am sorry if i am bugging out somebody. So here is what happened.
I got a mytouch 4g phone today, and i rooted it using gfree as it was the first sticky on the forum. i did a bit of research about bricks on mt4g (have been playing with androids since a long time) and didnt find anything about the emmc problem. then i tried gfree and it was easier than i thought. so i unlocked it (s-off), changed cid and unlocked sim (all using gfree -f). and i installed cwm and installed a rom. everything is working perfect.
but i discovered all the threads about bad emmc and bricks and stuffs like that. so i checked my emmc name and it came out to be the bad one. and i figured out that i did a big mistake. so i thought about restoring gfree backup and using the other root method (hboot s-off not radio). i was just about to restore the backup using gfree, then i noticed that my backup file (.bin file) was not present on my sd. i was shocked at first. then i found that i could s-on the phone using gfree without using backup bin file. but if i do that, will my phone not get emmc bricked like others? or do i need my backup file? can i use someone else's bin backup file? if yes, can you give me yours? any help would be really appreciated. i am worried that i might get a brick anytime. i was planning to make some tools for mytouch 4g (like i did for hd2) but i guss i will not be able to do that anymore cuz i might get a brick anytime. thanks for reading.
Edit: do all bad emmc phones using gfree get bricked? and what is the average period before it gets bricked (yea im too worried ) and is there anythign i could do now? (except for sending it for replacement since i bought it off craigslist)

This gfree and bad eMMC is just a correlation. Nothing has been proven to be a fact just yet. I've rooted my phone via gfree about 3 months ago now and I flash at least 2-3 times a week and nothing happened so far (I have the bad eMMC by the way). Everything seems fine for now.
I've also came across people that have the bad eMMC and have bee rooting and flashed hundreds of time for 6 months and going, so it's not a definite that your phone with the bad chip will die soon, so just keep that in mind.
But yes, it has happened to numerous people with the bad chip. Honestly, I would just ride it out and see what happens. If it dies just exchange it through T-Mobile.

You can't root the phone with "bad" eMMC by root.sh method, so you shouldn't even bother trying.

Jack_R1 said:
You can't root the phone with "bad" eMMC by root.sh method, so you shouldn't even bother trying.
Click to expand...
Click to collapse
I used this method on mine with the "bad chip" and had no problems.

tooter1 said:
I used this method on mine with the "bad chip" and had no problems.
Click to expand...
Click to collapse
You used g-free previously.. or root.sh wouldn't work on bad eMMc.
Please refer to the guides.
root.sh is guaranteed not to work on bad eMMc's unless g-free had previously been used.

Also not all "can't open /cache/recovery/log" errors in recovery are due to a dead eMMC chip. It can happen if your cache partition gets corrupted. Earlier this week, I had a bad flash--forgot to verify the md5sum before flashing, and after things started messing up, wifi not working, force-closes, etc...
So I went back to restore a nandroid backup I had made prior to the bad flash and got the dreaded "can't open /cache/recovery/log" error. I plopped the PD15IMG.zip on my sdcard and flashed it through hboot without any fail-PU errors.
So no, a M4G2DE eMMC chip doesn't always mean you'll have a brick. And cache partition errors in recovery don't always mean the eMMC chip died. What it means is that the "bad" eMMC chip has a much higher failure rate than the "good" chip. So if you have a "bad" chip, judging by the numbers, you have a much higher chance of ending up with a brick at some point.

might sound silly but where would I get the PD15IMG.zip file??
I thought PD15IMG.zip was the RADIO file.. but i think am pretty clueless...any enlightenment ?

3p4145 said:
might sound silly but where would I get the PD15IMG.zip file??
I thought PD15IMG.zip was the RADIO file.. but i think am pretty clueless...any enlightenment ?
Click to expand...
Click to collapse
Any file that has to be flashed through the bootloader (such as the stock RUU, radio files, etc) has to be named PD15IMG.zip for the bootloader to recognize it. There are two threads in the dev section that have the stock RUU you're looking for. A little searching should locate them.

Hi,
I'm a newb, and was thinking about rooting my phone and installing a different rom, but I read about this bad eMMC problem. I was wondering, if I have the bad eMMC and I don't root and install roms, will I still have the same problem that my phone might just die? Or is it only if I flash roms onto my phone?
Thanks,
Andy

Yes, if the "bad" eMMC in your phone is really bad - it'll die no matter if you flash ROMs or not. Just slower if you don't.

For what it's worth, I've had my phone with the bad emmc since December ... rooted since January & flashing roms ever since... no dead emmc. (Yet, if ever).
Sent from my HTC Glacier using XDA App

So, if you do have the M4G2DE chip, is it possible that is good? Like, you have a good version of the M4G2DE chip?

DashBlacK said:
So, if you do have the M4G2DE chip, is it possible that is good? Like, you have a good version of the M4G2DE chip?
Click to expand...
Click to collapse
+1
Sent from my Tweaked out RCmix3D myTouch 4G via xda premium !

good question. i don't have an answer to that. i've warrantied my phone, got another bad emmc around april? & have rooted & been flashing roms. phone hasn't died.

M4G2DE is just a regular chip. It's used for at least 3 other phones (G2, DHD, DS). I have one in my wife's Desire S, and it's rooted and running VU.
All the hype of the "bad" chip has gone WAY out of proportions.

DashBlacK said:
So, if you do have the M4G2DE chip, is it possible that is good? Like, you have a good version of the M4G2DE chip?
Click to expand...
Click to collapse
Yes, there is a good and a bad batch like most things in the world. My mytouch had the bad emmc from march to now and it's been fine. I flash like a maniac and it's been fine.
But like someone mentioned before if you really do have the bad bad chip; eventually your phone will just crap out. There are several cases on it from people who has never rooted before.
What people usually don't talk about is that some "good" chips are also bad and will eventually go bad overtime. Someone made a poll and discovered that the bad emmc chip showed a higher susceptibility of the phone failing. But remember it is only a poll. The poll also said that blacks are more susceptible than other colors... Why? because more blacks were distributed. It is possible that more bad chips were distributed. who knows?
Hope that clears some things up for everyone.

Teo032 said:
Yes, there is a good and a bad batch like most things in the world. My mytouch had the bad emmc from march to now and it's been fine. I flash like a maniac and it's been fine.
But like someone mentioned before if you really do have the bad bad chip; eventually your phone will just crap out. There are several cases on it from people who has never rooted before.
What people usually don't talk about is that some "good" chips are also bad and will eventually go bad overtime. Someone made a poll and discovered that the bad emmc chip showed a higher susceptibility of the phone failing. But remember it is only a poll. The poll also said that blacks are more susceptible than other colors... Why? because more blacks were distributed. It is possible that more bad chips were distributed. who knows?
Hope that clears some things up for everyone.
Click to expand...
Click to collapse
Interesting info...
Sent from my HTC Glacier using xda premium

HTC Mytouch 4G EMMC
I sent in my lifeless HTC Mytouch 4G to have 'Jtag Service' done to it as thats what I thought it needed, but instead they performed this 'EMMC Repairs Service' which was what they diagnosed the problem to be. An it fixed it, before sending it in, all my phone did was to charge batteries. checkout their website they even send the bad EMMC chip with the phone :good: hope I helped someone be blessed :angel: here is the URL---> mobiletechvideos.mybigcommerce .com/htc-mytouch-4g-emmc-chip-repair-replacement/

Nice how much was that
Sent from my HTC Glacier using xda app-developers app

bramz said:
I sent in my lifeless HTC Mytouch 4G to have 'Jtag Service' done to it as thats what I thought it needed, but instead they performed this 'EMMC Repairs Service' which was what they diagnosed the problem to be. An it fixed it, before sending it in, all my phone did was to charge batteries. checkout their website they even send the bad EMMC chip with the phone :good: hope I helped someone be blessed :angel: here is the URL---> mobiletechvideos.mybigcommerce .com/htc-mytouch-4g-emmc-chip-repair-replacement/
Click to expand...
Click to collapse
I almost had the JTAG service done too. Before I did I did my research and come to find out that when I explained my situation to one of their techs I was emailing, he said that my situation was folly and there was nothing they could do. He stated it was the dreaded "bad eMMC chip problem" yet all i had was cache and recovery errors just like what was mentioned above. Formatted my sdcard, put the stock T-Mobile GB PD15IMG.zip on there, flashed, and booted right up. Lost root of course, but able to get it back to rooted state and been flashing custom roms ever since. Pretty sure just like what was stated above... Blown WAY out of proportion. Hope this helps some people with their anxiety about this issue.

Am I right to be afraid?

I'm actually kind of afraid to root my device. I just don't want to mess anything up. And we only have one Rom. Is it right to just wait? I loved having root on my sensation but I really really don't want to mess up my galaxy.
Sent from my SGH-T999 using xda app-developers app

Assuming the method of obtaining root is safe, you don't really have anything to worry about by just having root access.
It's only dangerous if:
A) The method of obtaining root initially is dangerous in some way
B) You start giving apps root permission that may be malicious
C) You use root access to start modifying system files carelessly
So as long are you are careful and follow the advice from helpful users who have confirmed which apps are safe to disable and such, you should not have any problems.
I don't have my device yet, as it's pre-ordered on Verizon, but I could never live without root on an Android device. As soon as we get custom ROMs though, I'll be flashing one of those.

I am too....but for fear of messing up my warranty due to the flash counter
Sent from my MB865 using XDA App

916x10 said:
I am too....but for fear of messing up my warranty due to the flash counter
Sent from my MB865 using XDA App
Click to expand...
Click to collapse
Exactly! I really don't want to screw my warranty up!
Sent from my SGH-T999 using xda app-developers app

If anything, give it a week or two to make sure your specific phone doesn't have any manufacturer defects that you'd have to return it for warranty on. If all looks good, go for root without worries. That's how I do it.

if you have sprint they dgaf about the flash count or even ir your rooted running a leaked jellybean rom they will still help you out and the flash process is simple just watch qbking77 videos on hius youtube channel root gives you access to more apps such at titanium backup and allows you to delete apps that you never use

MacTheRipperr said:
Exactly! I really don't want to screw my warranty up!
Click to expand...
Click to collapse
Me either, which is why I tend to wait for my 1 year to be up before rooting.
At the very least, I wait for a safer, more painless root... Looking briefly at the root instructions for the SGSIII, it seems there are several opportunities to brick your phone if you F something up. Granted, if you're careful and you're remotely competent, it shouldn't happen, but it still can. I can't guarantee that I will make it the whole 1st year... but I'm pretty sure I will at least wait for one of those "download-this-program-which-roots-the-phone-for-you" type tools (a la "Unrevoked" on my beloved Incredible).
As for the warranty... I may be persuaded to root my phone earlier than the 1 year if there is a reliable unroot that leaves virtually no traces behind. I'm not sure what the "flash counter" is exactly, but unless it's something that shows up on the bootloader screen or anything like that, I'm sure Verizon won't notice. Unless anyone out there has had a different experience?

Besides the small amount of bloat that can be hidden with the launcher, the phone works flawless for me. If there was a way to go back to 100% stock on a T-999, I'd maybe do it.

Well I'm currently on T-Mobile. And I have had my device a week and have had no issues what so ever besides the black blotches I didn't even notice until reading the defect screen and I only have 2 tiny spots that don't bother me at all. I have never had to replace any Samsung device I have ever purchased. But I cannot say the same for HTC. That Damn counter is the only thing stopping me
Sent from my SGH-T999 using xda app-developers app

RampageRR said:
If anything, give it a week or two to make sure your specific phone doesn't have any manufacturer defects that you'd have to return it for warranty on. If all looks good, go for root without worries. That's how I do it.
Click to expand...
Click to collapse
^This
and never delete apps, IMO it's always better to just "freeze" them with Titanium Backup, because they can always be restored.
If you delete a system app (aka uninstall it) many times it cannot be restored via Titanium, so it's always risky to do that.

I've decided to wait for a one click root option.

The actual process of rooting is simple, only problem is if u dont read or rush through it. No worries there.
Sent from my MB865 using XDA App

You guys should not be scare to mess things up... i mean the root its so easy .... but like the other guy said just wait for a week or two to see the results...

I'm holding off rooting as well to make sure there isn't any issues with the phone. And if everything is working properly I will root. I do love this device though. Came from the Samsung Vibrant who has served me well for the two years I had it.

Rooting itself is not dangerous. When someone has root and does something they don't know how to fix, that is when it becomes dangerous.
A gun isn't dangerous until it is loaded. You can give a gun to any idiot but you have to be careful with who you give bullets to.
Sent from my Axiom MAXX!!

I agree, but there is always that what if? I suppose that's the risks we take
Sent from my SGH-T999 using xda app-developers app

You all just need to read all instructions and follow them perfectly. If you rely solely on One Click Roots and things of that nature, you'll never really learn how to work with Android. It might look daunting at first, but ADB and related stuff really isn't bad at all. Take the time to read and learn, and if in the rare case you should mess up, you'll have the knowledge of how to fix it yourself.
Also, don't be afraid to ask questions on how to do things rather than jump in head first and brick your phone. People here will be glad to help, just ignore the few idiots who flame you to make themselves feel better. We all started without knowledge at one point or another.

I have M4G2DE, is it safe to root?

Hi,
I have read everything about the M4G2DE, i know it's the bad eMMC but...
What do you suggest? To root or not to root?
What are the odds my phone die? I mean is there any other sign that my phone will die apart from the fact that I have a "bad" eMMC?

No offense, but had you read "everything" you would know this is heavily under debate.
I have rooted 3 phones with the "bad" eMMC and flashed ROMs to all of them. While porting a ROM tonight I flashed at least 6 times. No problems yet.
There is no way to tell if a chip will go bad until, all of a sudden, it does. Also something that was covered in the threads on this topic.
If you want to root it, root it. There is always a chance of failure. You make the choice.

I was afraid as you are. I did it last week and it's still working . But I read that if you have the bad "bad emmc", even if you don't s-off and root it you can get your phone bricked. I did it mostly because the bad battery performance in stock 2.3.4. estallings15 encouraged me a lot. I hope my phone last forever.
Sent from my Dark Unicorn Resurrected v.2 using Tapatalk 2

extrem0 said:
I was afraid as you are. I did it last week and it's still working . But I read that if you have the bad "bad emmc", even if you don't s-off and root it you can get your phone bricked. I did it mostly because the bad battery performance in stock 2.3.4. estallings15 encouraged me a lot. I hope my phone last forever.
Sent from my Dark Unicorn Resurrected v.2 using Tapatalk 2
Click to expand...
Click to collapse
Welcome to the fold