Database Info

stable root? DEVS READ FIRST POST, EDITED HACKED SPL [THINK TANK]

Ok, I'm ashamed to admit it.. but I'm unrooted.
I saw the sticky yesterday saying stop flashing. And it scared the hell outta me!
I don't fancy a random brick! If u ask me.. the only real issue with an unrooted phone, is the internal storage. Everything else just works.
Yeah I'd love to be tryin, and compilin my own roms. And I really wanna try cyanogenmod. But it ain't worth the randomness of the bricks were gettin.
So who is working on a way to flash the recovery? We need rw access sharpish!
I will even have a go at porting froyo, if we can get this done.
Tagged the topic as a think tank, in case people wanna collaborate.
EDIT
Ok guys... I found this...
forum.xda-developers.com/showthread.php?t=589642
It's about hacking spls. Any dev help is appreciated
-------------------------------------
Sent via the XDA Tapatalk App

philicibine said:
Ok, I'm ashamed to admit it.. but I'm unrooted.
I saw the sticky yesterday saying stop flashing. And it scared the hell outta me!
I don't fancy a random brick! If u ask me.. the only real issue with an unrooted phone, is the internal storage. Everything else just works.
Yeah I'd love to be tryin, and compilin my own roms. And I really wanna try cyanogenmod. But it ain't worth the randomness of the bricks were gettin.
So who is working on a way to flash the recovery? We need rw access sharpish!
I will even have a go at porting froyo, if we can get this done.
Tagged the topic as a think tank, in case people wanna collaborate.
-------------------------------------
Sent via the XDA Tapatalk App
Click to expand...
Click to collapse
if you do everything in the tutorial, you will not brick your phone, many people have done it and just because some dont know how to use a console und dont have to be scared.

starchildx said:
if you do everything in the tutorial, you will not brick your phone, many people have done it and just because some dont know how to use a console und dont have to be scared.
Click to expand...
Click to collapse
dude, are you out of your mind????????????
what do you mean? we did not do as the tutorial???? i have flashed my phone over 20-30 times. i did the root perfectly and the brick happenned after 20-30 flashes.
there are even developers who bricked their phones. think before making such comments and better inform yourself first!!!!

starchildx said:
if you do everything in the tutorial, you will not brick your phone, many people have done it and just because some dont know how to use a console und dont have to be scared.
Click to expand...
Click to collapse
Please, stop this kind of message .... You will pay a new one to the guy who will brick it ? No ...
And you are talking of something you seems to don't know very well... Some devices have been bricked only by appliyng the 2 steps of the simple root process (without custom rom, a2SD ..) ...

if you do everything in the tutorial, you will not brick your phone, many people have done it and just because some dont know how to use a console und dont have to be scared.
Click to expand...
Click to collapse
Man, maybe you should first read and than not post such a s**t. I bricked mine, too, and i think i know what i'm doing. If you would know about what you talk you would see that the cause for the bricked desires is not yet adressed, and that it could happen to anyone who rooted the phone

philicibine said:
Ok, I'm ashamed to admit it.. but I'm unrooted.
I saw the sticky yesterday saying stop flashing. And it scared the hell outta me!
Click to expand...
Click to collapse
You are easily scared
I just dont understand why you unrooted. If you have root then you are out of harms way. The brick only occurs while flashing in recovery. If you already done that - there is absolutely no risk to brick your usb that way.

stingerpl said:
You are easily scared
I just dont understand why you unrooted. If you have root then you are out of harms way. The brick only occurs while flashing in recovery. If you already done that - there is absolutely no risk to brick your usb that way.
Click to expand...
Click to collapse
I dunno man? My usb has been playing up recently. Been rooted since r1 and now I'm having trouble getting in recovery. Get a new and wonderful message everytime!
I've just put it down to my pc being a lazy f*ck! Hahahaha!! I just keep trying 'til it decides to do what I'm telling it to. Always get there in the end, there's no way I'm "unrooting". If I brick my Desire somehow, well, then I'll just cross that bridge when I come to it.

MrBadgerMilk said:
If I brick my Desire somehow, well, then I'll just cross that bridge when I come to it.
Click to expand...
Click to collapse
Ditto!
10char

Seriously guys, i just don't know how you manage to **** up your phone. Just don't be a maverick installing any old custom rom out there, do as I did : root the phone and stick with the stock rooted rom.
I've tried quite a bunch of custom roms and their different revisions, and I still find the stock rooted one (without any of the experimental A2SD crap) is by far the most stable.

phentex said:
Seriously guys, i just don't know how you manage to f**k up your phone. Just don't be a maverick installing any old custom rom out there, do as I did : root the phone and stick with the stock rooted rom.
I've tried quite a bunch of custom roms and their different revisions, and I still find the stock rooted one (without any of the experimental A2SD crap) is by far the most stable.
Click to expand...
Click to collapse
Good for you, you rooted and found a rom you liked. Other people have different reasons for rooting, and for you to simply say 'do as you did' isn't exactly helpful or useful.
The primary reason people rooted was for the A2SD. Now to be clear, it doesn't matter one bit what ROM you flash with, there is still a fair chance you can brick the device during the flash process. There is no pattern, no particular issue and no particular rom that causes the fault to occur.
No one has yet actually found the reason for the problems. If people want to go ahead and flash their devices, then fine, but at least with threads like this and the sticky, people are made well aware of the risks and potential problems.
By the way, stop swearing on the forum. Children post and read here.

since HTC released the kernel code, I thought it would be easier to revert back to enterily stock

Re: Unrooted :( til we get a stable root. Who's working on this? [THINK TANK?]
Well,i made some roms for my desire, some didnt work and i was stuck in the bootloader,but i could fix it everytime. I Flaschen my device over 20 times.
-------------------------------------
Sent via the XDA Tapatalk App

starchildx said:
Well,i made some roms for my desire, some didnt work and i was stuck in the bootloader,but i could fix it everytime. I Flaschen my device over 20 times.
-------------------------------------
Sent via the XDA Tapatalk App
Click to expand...
Click to collapse
And ? Like a lot of those who have bricked their device the 21th flash ....

Seeing as you can't flash over the SPL and radio anyway, once you are successfully rooted, it's probably impossible to get to a state of full bricking. Anything will be recoverable with a gold card and/or a RUU.

Unlike many others, I only got root because I wanted access to paid apps. AFAIK root is needed for that. So I'm running the stock rooted ROM, and the radio update, provided by Paul. I won't flash anything until a rooted 2.2 ROM is out...and who knows...maybe after 2.2 the bricking problem will be gone?

socktug said:
Good for you, you rooted and found a rom you liked. Other people have different reasons for rooting, and for you to simply say 'do as you did' isn't exactly helpful or useful.
The primary reason people rooted was for the A2SD. Now to be clear, it doesn't matter one bit what ROM you flash with, there is still a fair chance you can brick the device during the flash process. There is no pattern, no particular issue and no particular rom that causes the fault to occur.
No one has yet actually found the reason for the problems. If people want to go ahead and flash their devices, then fine, but at least with threads like this and the sticky, people are made well aware of the risks and potential problems.
By the way, stop swearing on the forum. Children post and read here.
Click to expand...
Click to collapse
There is actually a reason found if you have been reading the threads over at Modaco, When the phone hits the bootloop in the flashing process, it seems after the third boot loop, the phone stays in a constant debug mode. I did have the boot loop after one flash, but i was VERY lucky as had the back of the phone off and pulled the battery befor the third bootloop, i truely belive that has saved my bacon.......
Have flashed a fair few times using all the methords posted on the modaco and XDA forums. all worked flawlessly..... but i too have kept on stock ROM.
Wont flash Customem ROMs untill im either a developer or the spl gets fully opened.
And socktugs right watch your launguage please all
EDIT: As per Stingerpl Suggests if you notice a bootloop occuring take the battery out ASAP!!

It is generally a good idea to take your battery out on first bootloop, go to recovery and nandroid restore. Might save your USB from bricking
I still can't understand why someone would want to unroot because of this. You're already past the risky procedure.

I guess a fully function root need some info about the current root. Anyone know what exploits was used and how its been applied?

maybe the problem is exotic hardware in the pc/laptop. i'm using a standart motherboard with a intel chipset, i never had any problems with rooting or unlocking or flashing any device.
for the people that have problems under linux, what do dmesg say ?

potter1984 said:
There is actually a reason found if you have been reading the threads over at Modaco, When the phone hits the bootloop in the flashing process, it seems after the third boot loop, the phone stays in a constant debug mode. I did have the boot loop after one flash, but i was VERY lucky as had the back of the phone off and pulled the battery befor the third bootloop, i truely belive that has saved my bacon.......
Click to expand...
Click to collapse
Maybe the boot loop has something to do with it... but there are simple ways to avoid a boot loop.
I flashed my desire several times... and had bootloops occur several times. None bricked my phone.. fortunatley!
The reason i found for my boot loops, was NOT WIPING EVERYTHING!
I have read on modaco forums, that Paul's recovery does not clear the dalvik cache, when it is on a partitioned sd card. Maybe it is something to do with the rooting process (no rw access).
The only answer I found, was to re-partition the sdcard everytime. thus wiping all partitions.
So as with any rom you download... READ THE F`ING MANUAL!! its always best to do a FULL wipe. Then your getting the rom, as the developer wanted you to have it.
So not a solution, but some words of advice for noobs! And hopefully we can avoid too many more bricks!!
I will keep monitoring this thread and will update the title if / when we have any developments.
Maybe we need to pray for an engineering SPL

[Q] Rooting Inspire Question, Just got the phone.

Greets All,
I am sorry that I have to ask a few questions, only cause I really dont want to mess anything up, I got the phone about a week ago, and I have been reading alot of the different sections about rooting, and I see the different types of ways, and there is good replies and bad replies so I am a bit on the fence. I even got a CWR of this: att-inspire-rooted-signed.zip but I cant for the life of me find where I got it from. But let me ask the questions:
1) I want to keep the phone completely as is, I dont want to install another rom or anything right now, all I want to be able to do, is, remove the att software, and root the phone so that I can install the apk's I have on my sdcard. Do I have to go thru the whole hack kit or one click root and all that? Or is there a simple root and stay with the stock rom?
2) The file I mentioned: att-inspire-rooted-signed.zip I renamed it to update.zip, and then went into the bootloader, then recovery, obviously I got the phone with the red triangle thing, but hitting the up volume and the power button give me a CWR menu, and one of them is to install update from sdcard, but when I choose that zip it says about e:\cant open command folder blah, and then when I click update it says invalid operation. is that cause the phone isnt rooted?
3) If I have to root the phone, then which one will root it, but leabe everything intact if any? I dont want to change my radio, or the rom.
I am sorry if I am asking too much, but the rom has no sim at the moment and just playing with it everything works beautifully, even the gps works instantly because its properly using agps.
Thanks for the answers.

AngelDeath said:
Greets All,
I am sorry that I have to ask a few questions, only cause I really dont want to mess anything up, I got the phone about a week ago, and I have been reading alot of the different sections about rooting, and I see the different types of ways, and there is good replies and bad replies so I am a bit on the fence. I even got a CWR of this: att-inspire-rooted-signed.zip but I cant for the life of me find where I got it from. But let me ask the questions:
1) I want to keep the phone completely as is, I dont want to install another rom or anything right now, all I want to be able to do, is, remove the att software, and root the phone so that I can install the apk's I have on my sdcard. Do I have to go thru the whole hack kit or one click root and all that? Or is there a simple root and stay with the stock rom?
2) The file I mentioned: att-inspire-rooted-signed.zip I renamed it to update.zip, and then went into the bootloader, then recovery, obviously I got the phone with the red triangle thing, but hitting the up volume and the power button give me a CWR menu, and one of them is to install update from sdcard, but when I choose that zip it says about e:\cant open command folder blah, and then when I click update it says invalid operation. is that cause the phone isnt rooted?
3) If I have to root the phone, then which one will root it, but leabe everything intact if any? I dont want to change my radio, or the rom.
I am sorry if I am asking too much, but the rom has no sim at the moment and just playing with it everything works beautifully, even the gps works instantly because its properly using agps.
Thanks for the answers.
Click to expand...
Click to collapse
If you want to remove the ATT bloatware you will have to root. You don't have to root to sideload. Just download the sideload wonder machine found in the dev section. As for rooting id suggest using the hack kit. Ive rooted 4 phones with it. First use the simple gold card maker. Then download the hack kit and follow the instructions in the read me file. Att1 has made it pretty simple. Then flash cleardroid stock rooted rom. All the bloatware is already removed. Its really stable. Good luck.
Sent from my Desire HD using XDA Premium App

What about the simple one click program instead of the hack kit?
Sent from my SAMSUNG-SGH-I897 using XDA App

trell959 said:
What about the simple one click program instead of the hack kit?
Sent from my SAMSUNG-SGH-I897 using XDA App
Click to expand...
Click to collapse
I have never used it myself so i cant give advice on it. That being said several thousand people have so im sure it will work fine.
Sent from my Desire HD using XDA Premium App

I'm glad you asked this question because I want to do the same thing I want to keep my phone stock and just root so I to can delete ATT crap and to edit my build.prop file because ATT pissed me off today telling me my speeds are slower than my friends 3gs because his has more storage space. Wtf. We ran speedtest app on both Phones to the same server and every single time his ran double or more on download speeds. ATT told me its the device doing it. IPhone fan boys is all I can say.
Anyway is there a easy way. I rooted my old aria with the unrevoked root. Super easy. Does the inspire have a easy way.
Sent from my Desire HD using XDA App

slocav said:
I'm glad you asked this question because I want to do the same thing I want to keep my phone stock and just root so I to can delete ATT crap and to edit my build.prop file because ATT pissed me off today telling me my speeds are slower than my friends 3gs because his has more storage space. Wtf. We ran speedtest app on both Phones to the same server and every single time his ran double or more on download speeds. ATT told me its the device doing it. IPhone fan boys is all I can say.
Anyway is there a easy way. I rooted my old aria with the unrevoked root. Super easy. Does the inspire have a easy way.
Sent from my Desire HD using XDA App
Click to expand...
Click to collapse
No true one click. I find the hack kit to be the best for me.
Sent from my Desire HD using XDA Premium App

I used bubby's one click method. Very simple, and there is a youtube video of it as well. Watch the entire video first so you have an idea of whats going on then go through the video while rooting. (not, downplaying the hack kit, i have never tried it) And for what its worth i too wanted a stock rom and chose Two pump chumps rom (Its a stock inspire rom -bloatware and improved a bit) and lee droids kernel, which gives a slight sound boost and smooths things a bit more imho. Good luck.

So if I do the root do you have to flash a Rom to delete bloatware? If I have to do a ROM the one posted above will it have sound issues etc? Thanks a ton.
Sent from my Desire HD using XDA App

should be receiving my Inspire tomorrow....coming from the captivate section, this is definitely a little different. I have a quick question though...
The hack kit is used to enable s-off, temp-root, flash a rom that allows use of an old exploit, then permaroot. Once permarooted and CWM recovery has been flashed, any rom from the dev section can be flashed which will keep the root.
My question is, this process only has to be done once, correct?? All future roms will be flashed via CWM recovery, and there won't be ANY need to return to the stock ATT Inspire, unrooted rom??
I ask because with the Galaxy S/Captivate/etc it is usually recommended to flash back to stock before flashing a different custom rom, which means you lose root. I usually didn't that, and never had a problem, but i'm just trying to get a grasp on how this process differs from the Captivate. I will be GLAD to have a phone that can simply be cleared and flashed via CWM for all rom purposes.

All i know is bubby's method, and with it, it gives you root but its just like when you bought it. Now i think you can use clockwork mod or something to manually delete the bloat from there, but for the trouble its easier to flash a new rom that has it already done for you, and get a few bonuses with it. The one i suggested has given me no problems and is a ton faster than it was stock, although your phone may be different.

My question is, this process only has to be done once, correct?? All future roms will be flashed via CWM recovery, and there won't be ANY need to return to the stock ATT Inspire, unrooted rom??
Click to expand...
Click to collapse
yes, the only need to go back is if you have to do a warranty return. Technically rooting voids the warranty, but if you undo it whos to know the difference

Bamatide2007 said:
yes, the only need to go back is if you have to do a warranty return. Technically rooting voids the warranty, but if you undo it whos to know the difference
Click to expand...
Click to collapse
i actually meant to say "won't need to return to stock unless for warranty"...but yes i gotcha! thanks.
Like i said, although the Captivate seems more "open" or easier to root and such...in the end, this is going to be a MUCH better flashing technique compared to samsung phones. Everyone is always so worried about flashing to stock, doing this, doing that....

i guess i do have one last question....
it seems to be disputable at whether or not you need to do a factory reset/clear data within the CWM recovery during a new flash. When is it necessary and when can this be skipped?

Anytime your flashing a rom you need to do a full wipe, a benefit of CWM is it gives you the option when you start to flash anything to do one of 2 things A: being backup current rom, and B:full wipe.
So assuming you have a good backup already (if not do a backup before this step), just check the box for a full wipe and let it do the magic.
After getting the rom you want and you just want to flash a kernel, batterymod, etc then you only want to make a backup, you will not need to wipe at that point.

sounds good...thanks for all the help, Bamatide. Roll Tide!
I think i was just confused with the update process from within a rom, in which most dev's say it is ok to not wipe data in between updates. Flashing to a different rom requires the full wipe though everytime.
Just curious, but what happens if a full wipe is NOT done in between flashes? Is it just buggy or are there other problems?

The reason for a full wipe is because there could be conflicts between the two rom's where you could end up with just a bootloop and then you would need to do a wipe.
If you want there is a very simple way to do a full wipe, go to this thread http://forum.xda-developers.com/showthread.php?t=996383 and download the zip, this makes it very simple to do. I keep it on my sd card because I like to change rom's and this makes it very easy.
As for rooting I have tried both programs and found that Bubby's was the easy way to go, with the hack kit you have to be able to use the command prompt on the computer and with Bubby's it does it for you. I am not a whiz with command prompt that is why I did not use the hack kit.
I hope this helps especially the one click wipe, it work's great.

So with buddy's do you have to make the gold card what ever that is lol. I didn't have to do anything like that on my old aria and was curious. Also can someone make a sticky that explains what s-off is and what radio s-off etc. I didn't have any of that on my aria and I would like to know what they mean.
And to the op I'm sorry to thread jack but it was the exact same question I had. Hope you don't mind I'm asking on top of yours.
Sent from my Desire HD using XDA App

slocav said:
So with buddy's do you have to make the gold card what ever that is lol. I didn't have to do anything like that on my old aria and was curious. Also can someone make a sticky that explains what s-off is and what radio s-off etc. I didn't have any of that on my aria and I would like to know what they mean.
And to the op I'm sorry to thread jack but it was the exact same question I had. Hope you don't mind I'm asking on top of yours.
Sent from my Desire HD using XDA App
Click to expand...
Click to collapse
Don't be sorry most of us would rather you search then start a new thread. As for which method to use, essentially they are the same except the "one click" does most of the dos commands for you. Both downgrade your rom and radio and use that as an exploit, to root and s-off the phone.
Now problems people run into, there still seems to be a problem with CWM and the one click. For this reason I will recommend the Hack Kit, its nothing against bubby but it is sad to see the same "cwm blank screen" thread resurrected everyday.
Essentially s-on is Security on meaning you cannot flash unsigned roms. Radio s-off essentially allows you to flash custom roms. To flash a stock rooted rom you will need s-off.
With both methods you will need a gold card.

S-off also does away with the Gold card, once you get S-off you can format the SD card be done with it.

mudknot2005 said:
Don't be sorry most of us would rather you search then start a new thread. As for which method to use, essentially they are the same except the "one click" does most of the dos commands for you. Both downgrade your rom and radio and use that as an exploit, to root and s-off the phone.
Now problems people run into, there still seems to be a problem with CWM and the one click. For this reason I will recommend the Hack Kit, its nothing against bubby but it is sad to see the same "cwm blank screen" thread resurrected everyday.
Essentially s-on is Security on meaning you cannot flash unsigned roms. Radio s-off essentially allows you to flash custom roms. To flash a stock rooted rom you will need s-off.
With both methods you will need a gold card.
Click to expand...
Click to collapse
Awesome thanks for the explanation.
Sent from my Desire HD using XDA App

Since rooting,ROMing, games freeze and reboot phone

Hello, recived phone yesterday, tried install ARHD, that went wrong so I reverted to installing the latest stock, now whenever I play games they freeze for 5 seconds, then reboot my phone , I've tried unrooting, different roms and still the same problem, any help?

Android Revolution? That ROM is not meant for our phone, its for the international version. Completely different hardware, and therefore different ROMs. That's probably the cause of your issue. You're lucky you don't have a brick.
Try relocking the bootloader and running the RUU.
This is getting ridiculous. You're at least the 5th person posting here in the last day or 2 to flash something not meant for our phone. How many times does it need to be said? Stick to flashing only things in the AT&T specific Development section, and in my index thread:
http://forum.xda-developers.com/forumdisplay.php?f=1541
http://forum.xda-developers.com/showthread.php?t=1671237

lol another user who did no research at all before flashing. You kinda deserve it. Just be glad it's not a perm brick.
Sent from my HTC One X using Tapatalk 2

There have been an influx of people who jump in the deep end without learning to swim. No sympathy from me. All of this information is readily available on the internet, xda specifically, and if you screw up your phone because you tried to do something you didn't understand it is entirely your fault. Next time do a little research before you try flashing something.

0.o no way, is it even possible to flash arhd without bricking or at the very least bootlooping? I think he just posted in the wrong device forum.

kevina90 said:
0.o no way, is it even possible to flash arhd without bricking or at the very least bootlooping? I think he just posted in the wrong device forum.
Click to expand...
Click to collapse
interesting note. another guy accidently posted in our forum earlier today. could be what happened.

[Q] Seeking advice on unrooting and un-TWRP-ing a GT-I9020 Nexus S, back to stock

I've a two-year old Nexus S, which needs to be returned to complete stock, unrooted and un-recovery'd. I didn't root or install the recovery mod myself, so am at a disadvantage when trying to remove it. Guides I've seen for full unrooting seem to rely on a version-specific external file, which seems to usually be 9020A or 9023 - quoting the model number entirely, this is a GT-I9020, nothing more, which seems to render invalid all unrooting/stock-restoring guides I've seen. The phone is still running the official Android, in fact it was factory restored a week ago, and is at version 4.1.3. It's updated a bit since then, possibly including the droid version too.
So my question is how do I go about this? Flashing the wrong version of anything is usually highly unwise, I can't find anything specific for this model, and I don't know enough about the details of the matter to judge what's best to do.
All advice much appreciated.

Booksworth said:
I've a two-year old Nexus S, which needs to be returned to complete stock, unrooted and un-recovery'd. I didn't root or install the recovery mod myself, so am at a disadvantage when trying to remove it. Guides I've seen for full unrooting seem to rely on a version-specific external file, which seems to usually be 9020A or 9023 - quoting the model number entirely, this is a GT-I9020, nothing more, which seems to render invalid all unrooting/stock-restoring guides I've seen. The phone is still running the official Android, in fact it was factory restored a week ago, and is at version 4.1.3. It's updated a bit since then, possibly including the droid version too.
So my question is how do I go about this? Flashing the wrong version of anything is usually highly unwise, I can't find anything specific for this model, and I don't know enough about the details of the matter to judge what's best to do.
All advice much appreciated.
Click to expand...
Click to collapse
Try this
http://forum.xda-developers.com/showthread.php?t=1766475

CataHd said:
Try this
http://forum.xda-developers.com/showthread.php?t=1766475
Click to expand...
Click to collapse
Shall do then, I need to wait about a week before I can in any case (need the phone as-is for app testing), but that does look promising. I saw it a while after posting, but wasn't sure if it was genuinely as good as claimed, or suitable for this version - I'm very wary of bricking the phone.
Many thanks.

Booksworth said:
Shall do then, I need to wait about a week before I can in any case (need the phone as-is for app testing), but that does look promising. I saw it a while after posting, but wasn't sure if it was genuinely as good as claimed, or suitable for this version - I'm very wary of bricking the phone.
Many thanks.
Click to expand...
Click to collapse
It is genuinely that good if you read the instructions carefully. I use that toolkit myself for more than a year now and I recommend it.

How to update to stagefright patch if I'm rooted?

Soooo I've been holding off on doing any updates from hearing about all the people bricking their devices. I was hoping there would be a guide by now but I really don't wanna go through threads with hundreds of pages looking for answers.
Anyone have a sure fire start to finish guide for this update process that won't brick my phone and leave me with phone running the stagefright patch with root again?
Sent from my 6045I using XDA Free mobile app

Yep would be ideal
Sent from my 6045Y using Tapatalk

so you are ready to search and read the pages to root your device and then you are lazy to search and read the threads to get info about how to upgrade?
tsss. . :-/
want-to-able-to-install-ota-updates

Don't know how you could brick but...
1. unroot
2. Flash new image in twrp
3. flash twrp again then root

techware7 said:
Don't know how you could brick but...
1. unroot
2. Flash new image in twrp
3. flash twrp again then root
Click to expand...
Click to collapse
You can easily brick the device because the update replaces TWRP with factory recovery (at least the last one did which was the stagefright one) leaving 6045 owners with no way to get to bootloader in the event the phone goes into boot loops which it WILL do if you don't do a full UNROOT...the hide root option is a surefire method to boot loops....so is editing your build.prop in an editor that doesn't keep linux formatting or installing the supersu root or xposed framework zip files and having something go wrong. It's actually fairly easy to bootloop if you don't follow the instructions to the letter.
Luckily @petrov.0 has offered a way to flash TWRP to the 6045's via Download Mode to help recover these type of bricked solutions....You can check out his post here: http://forum.xda-developers.com/showpost.php?p=62911970&postcount=46

famewolf said:
You can easily brick the device because the update replaces TWRP with factory recovery (at least the last one did which was the stagefright one) leaving 6045 owners with no way to get to bootloader in the event the phone goes into boot loops which it WILL do if you don't do a full UNROOT...the hide root option is a surefire method to boot loops....so is editing your build.prop in an editor that doesn't keep linux formatting or installing the supersu root or xposed framework zip files and having something go wrong. It's actually fairly easy to bootloop if you don't follow the instructions to the letter.
Luckily @petrov.0 has offered a way to flash TWRP to the 6045's via Download Mode to help recover these type of bricked solutions....You can check out his post here: http://forum.xda-developers.com/showpost.php?p=62911970&postcount=46
Click to expand...
Click to collapse
Known fact for all devices (stock updates) that if you root you have to unroot, if you mod stock files you better restore them and if you removed stock apps you better add them right back. In the old days you also had to restore back to stock recovery so Alcatels' updates replacing twrp with stock is no different than those days. Update will not fail unless you play the monkey card and assume things.

techware7 said:
Known fact for all devices (stock updates) that if you root you have to unroot, if you mod stock files you better restore them and if you removed stock apps you better add them right back. In the old days you also had to restore back to stock recovery so Alcatels' updates replacing twrp with stock is no different than those days. Update will not fail unless you play the monkey card and assume things.
Click to expand...
Click to collapse
That may be a "known fact" for alcatel but it's not true for Nexus Line, LG and HTC...at least not for the models I've personally owned. They don't go to the dramatic extremes Alcatel does. Adding a line to build.prop should NOT bring your update to a screaming halt but for Alcatel it does (actually it checks hundreds of files to verify they match a checksum and if they don't it halts the update with "unexpected content in xxx)...patch will work just fine on a file that has minor additions or deletions. Neither my nexus 4 or 5 care if the recovery is TWRP, CWM etc.
The behavior you describe MAY be common in the cheap chinese phones but not in flagship devices which alcatel claims it is trying to handle the Idol 3 as.

famewolf said:
That may be a "known fact" for alcatel but it's not true for Nexus Line, LG and HTC...at least not for the models I've personally owned. They don't go to the dramatic extremes Alcatel does. Adding a line to build.prop should NOT bring your update to a screaming halt but for Alcatel it does (actually it checks hundreds of files to verify they match a checksum and if they don't it halts the update with "unexpected content in xxx)...patch will work just fine on a file that has minor additions or deletions. Neither my nexus 4 or 5 care if the recovery is TWRP, CWM etc.
The behavior you describe MAY be common in the cheap chinese phones but not in flagship devices which alcatel claims it is trying to handle the Idol 3 as.
Click to expand...
Click to collapse
Nexus? Seriously? All BRANDED manufacture/provider "managed" updates. Nexus clearly doesn't fit the bill. I've owned LG and HTC and what I said is true.

techware7 said:
Nexus? Seriously? All BRANDED and managed updates. Nexus clearly doesn't fit the bill. I've owned LG and HTC and what I said is true.
Click to expand...
Click to collapse
Excluding the nexus line then (even though both the 4 and 5 were created by LG), On the HTC Desire HD , T-mobile MDA (aka HTC Wizard aka Cingular 8125) and the HTC HD2 (applicable to the original windows mobile updates before it was ported to android) your information does not apply.
Since you are now making "exclusions" then perhaps you should not be stating "known fact for all devices (stock update)". Personally I'd consider "Nexus" a brand..it also used native AOSP roms and updates for it's "Stock Rom's".

famewolf said:
Excluding the nexus line then (even though both the 4 and 5 were created by LG), On the HTC Desire HD , T-mobile MDA (aka HTC Wizard aka Cingular 8125) and the HTC HD2 (applicable to the original windows mobile updates before it was ported to android) your information does not apply.
Since you are now making "exclusions" then perhaps you should not be stating "known fact for all devices (stock update)". Personally I'd consider "Nexus" a brand..it also used native AOSP roms and updates for it's "Stock Rom's".
Click to expand...
Click to collapse
what difference does it make who creates a Nexus? A Nexus is a developer phone. Is an LG G4 a developer phone? What about an M9? A Z5? Is the Idol 3 a developer phone? No. Do manufactures and providers generally perform hash checks or whatever in their encapsulated upgrades? Yes. Can a brave soul come along and play around with these updates and let the world know what they do and what they check before we all get screwed when trying to apply an update? Yes. In the mean time, don't toss your stock apps and go crazy modding system files. Are there scenarios in which a manufacture can do whatever they please and not check for anything on a certain model of a phone? Yes of course! They can do whatever they please. What about custom roms? Yeah, what about them? go crazy and do whatever you want: you do not rely on a controlled update system.

techware7 said:
what difference does it make who creates a Nexus? A Nexus is a developer phone. Is an LG G4 a developer phone? What about an M9? A Z5? Is the Idol 3 a developer phone? No. Do manufactures and providers generally perform hash checks or whatever in their encapsulated upgrades? Yes. Can a brave soul come along and play around with these updates and let the world know what they do and what they check before we all get screwed when trying to apply an update? Yes. In the mean time, don't toss your stock apps and go crazy modding system files. Are there scenarios in which a manufacture can do whatever they please and not check for anything on a certain model of a phone? Yes of course! They can do whatever they please. What about custom roms? Yeah, what about them? go crazy and do whatever you want: you do not rely on a controlled update system.
Click to expand...
Click to collapse
Enjoy your rant and might I suggest a switch to decaf? *moving on*

famewolf said:
Enjoy your rant and might I suggest a switch to decaf? *moving on*
Click to expand...
Click to collapse
Decaf? Nah, but I'll take some orange juice. Btw, don't comment on the other post, I've already moved on.

This is what I was unsure about. So you have to return the system state to stock. Does that mean having xposed framework or twrp recovery will mess it up the update and could cause a boot loop?
Sent from my 6045I using XDA Free mobile app

colonelcack said:
This is what I was unsure about. So you have to return the system state to stock. Does that mean having xposed framework or twrp recovery will mess it up the update and could cause a boot loop?
Sent from my 6045I using XDA Free mobile app
Click to expand...
Click to collapse
When in doubt uninstall it but xposed won't work since it will lose root access when you do the full unroot. twrp should not have an effect on it.