Related
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
I read through a bunch of guides on rooting and flashing a rom and all this has gotten me extremely confused. All I want to do is root my phone. I want to keep the stock HTC rom except I want my phone to be rooted.
What is the safest way to do this with almost no chance of getting my phone bricked? I keep hearing this thing about a "radio off" and how easily it bricks your phone. I am looking for the absolute safest root method out there.
All I need is to remove the SIM Lock since I am going to Europe in 2 weeks. I might try underclocking as well. Also, I obviously have an HTC Inspire 4G
I recommend the ace hack kit. Its extremely easy now with version 11. Its simply as following the prompts and hitting 1,2,3. Once rooted flash attn1 rom. And you will be stock rooted with the latest Ota's radio
As to the radio s off, that in itself is not the problem but of flashing of radios. For example if you happens to flash a radio that was corrupted while downloading that has a potential to cause a brick. That's why you should always verify the downloads.
Sent from my TARDIS using XDA App
ComradeNF said:
I read through a bunch of guides on rooting and flashing a rom and all this has gotten me extremely confused. All I want to do is root my phone. I want to keep the stock HTC rom except I want my phone to be rooted.
What is the safest way to do this with almost no chance of getting my phone bricked? I keep hearing this thing about a "radio off" and how easily it bricks your phone. I am looking for the absolute safest root method out there.
All I need is to remove the SIM Lock since I am going to Europe in 2 weeks. I might try underclocking as well. Also, I obviously have an HTC Inspire 4G
Click to expand...
Click to collapse
If you just need the sim unlocked, just call AT&T for the code. If your Inspire qualifies...is not new and still under consignment...they should provide one. No need to root to unlock the sim. And just because there seems to be a lot of people rooting their Inspires doesn't mean it is popular. I haven't rooted mine and don't plan to because my Inspire works flawlessly as is with the OEM ROM. If you are feeling the urge or pressure to root your Inspire just because other people are doing it, don't. If the Inspire was running WinMo or some other low-quality OS, yes, then take the time to root. But it isn't. The Inspire is running Android. There's nothing wrong with Android as it currently is.
Hello and welcome. IMHO, att1's Hack Kit is the way to go. So long as you don't have a bunch of apps on your phone yet, start to finish rooting will take approximately 15 mins.
This will flash the stock rooted rom back onto your phone. It's incumbent upon you to backup any SMS, apps, contacts...that you don't want to lose.
Take you're time, read the EFFIN MANUAL and search prior to askin any q's relating to using the hack kit. Should you run into a situation that you're unable to find a concise answer for, drop into the chat room and see if your issue(s) can be resolved from there.
Good luck,
Tx
As he said above if all you want is sim unlock, get an unlock code.
If you insist on rooting, we will be happy to help you through the process, as long as you promise to continue reading, and researching before you attempt it.
mudknot2005 said:
As he said above if all you want is sim unlock, get an unlock code.
If you insist on rooting, we will be happy to help you through the process, as long as you promise to continue reading, and researching before you attempt it.
Click to expand...
Click to collapse
It's like $30 if I want to buy it. AT&T Told me I need to wait undil December before they give me the code =/
ComradeNF said:
It's like $30 if I want to buy it. AT&T Told me I need to wait undil December before they give me the code =/
Click to expand...
Click to collapse
Okay, if its rooting, the best remedy is to read the threads, I know there is a lot. There is a lot of information on this forum, and alot of the questions you have been asking have been covered a couple times.
As said above all the instructions including a stock rooted rom (with the ota update and bloat removed) are included in the hack kit. What the hack kit will do, is help you create a gold card (to bypass the CID check), downgrade the rom ( you won't have sound while downgraded), root then s-off (security off) the phone which also sim unlocks the phone, then flash a rooted stock rom.
Mud is correct and I have run into him a lot today posting lol. He also made the sticky at the top of the forum. He knows what he is talking about. This isn't the first phone I have rooted. But it is the first that wasn't a one click root. The ace hack kit was very simple to use just read read read and read again make sure you understand the process before starting. If you don't understand ask in this thread and we can all try to help out as best we can. Although i think mud will be taking the most of this lol. Also use the search feature and google your probably not the first person with a problem so more then likely the answer is already out there. Good luck with rooting.
I have been seeing MANY threads lately involving questions such as, "How do I get on ICS?", "Should I update to ICS?", "I think I am bricked, how can I fix this?", and "How do I FXZ back to GB?" So I am creating this thread as an information only thread to answer these questions and more with links to proper threads that have already been posted for your benefit. Unless otherwise noted by the OP's or myself the following threads apply to the AT&T MB865. So without further ado....
What you need to know about ICS and your Atrix 2
The first link you need to look at is the Noob thread. I am going to be using terms like "Bootloader", "Soft-Brick", "Hard-Brick", "FXZ", "Fastboot", "OTA", and the like and user/developer JRW28 has posted a FANTASTIC thread to help you familiarize yourself with certain Android terminologies and certain HOWTO's that will help you understand and accomplish much of what I am going to be referring to. So with the Atrix 2, if you are confused with something. START WITH THE NOOB THREAD. Find it here: JRW28's NOOB Thread
Done? Well read it AGAIN.
Oh, what's that? You read it twice and memorized it? Okay, moving on....
The first question that needs to be answered is:
SHOULD I UPDATE TO ICS?
Well, we have all been waiting for ICS to come out, and it has officially been running on the Atrix 2 for a while via a find through Cheesecake. The initial leak is NOT the final OTA that is still trickling out. You need to first understand that. Is ICS better than GB? Of course it is. No one will argue that here, but what we are tackling is, should you upgrade to it?
When it comes to XDA, we are always looking for ways to improve our phones. That's why we're all here right? This is a DEVELOPERS site. With developing comes trials, and with trials comes ERRORS. Now when it comes to the Atrix 2 (A2 from here on) we have a locked bootloader. This means that recovering from developing, and/or modding errors is not as easy as recovering from errors and mistakes with phones that have unlocked bootloaders. Normally, on phones with unlocked bootloaders, it is easy enough to jump into Clockwork Recovery and restore a previously saved nandroid backup, because with unlocked phones the modified recovery REPLACES the original. Poof. Back to normal.
On locked down phones such as the A2, we have to depend on either a bootstrap recovery or the like to make up for the lack of our locked phones. Do we have recoveries? Sure, but they DO NOT replace the original stock recovery and therefore we depend on things such as Bootmenu and Safestrap to makeup for this. While this works it is definitely not ideal. So what happens when the recovery get's borked, ROM goes belly up, or your phone is stuck at the splash screen and won't boot into recovery?
Well this is where the ICS upgrade question comes into play. This phones DEPENDS on FXZ's (see noob thread for more info). If the above scenario(s) happen then we depend on being able to jump into Fastboot (FB from here on) and reflash our phone back to stock. With Gingerbread this was easy enough as we had an FXZ for GB.
With ICS, ONLY THE FIRST LEAK IS ABLE TO REFLASH BACK TO GB! WE HAVE NO WAY TO REFLASH BACK TO GB WITH THE LATEST LEAKS AND THE SOON TO BE OTA UPDATE!!!!!!
Only when we find an ICS FXZ will this be possible!
Now I can hear it now. Some might say at this point, "Well once I'm on ICS, I won't want to go back to Gingerbread." The point, my friend, is not WANTING to go back to GB, it is needing a way to fix your phone. I myself have a paperweight for an A2 for EXACTLY this reason. I was running the latest of the leaks (NOT the first, which we can go back with). I had made a couple of mods, as bootmenu was working for it, and I made a backup. Well, I flashed a mod, rebooted and BOOM. Bootloop. No biggie, I thought, I will just restore my backup. But apparently I had deleted my backup. I tried, with the help of Devs (whom will be named later) to FXZ back and quickly found that this was impossible to do at this point. Now I have a phone that is able to boot in FB, with no way of restoring it. Fastboot does us no good without a proper working FXZ to flash.
So upgrading to ICS at this point, is fine, but be warned, if you make just the littlest boo boo, you might have a paperweight on your hands. Myself, many of the other Senior Members, and many of the A2 developers are recommending to run the first leak, because it is the most stable and dependable as far as getting yourself out of a jam. Also, many of the the more stable leaks have been baked into the current ICS ROMS we have. Now once you are on the first leak, you will have no problems flashing these ROMS with the more stable versions on them, but you MUST be on the first leak beforehand!!!!! As always read carefully the install instructions from the developer and if you're unsure, ask a question in the ROM's thread before flashing!!!!
UDPATE 9/20/12 It seems as though Moto and AT&T are now releasing OTA updates to our leak! Remember the reasons as to why we are advising against them! IF YOU GET A MESSAGE TO UPDATE WHILE ON THE FIRST LEAK, COMPARE THE FIRMWARE INFO WITH THOSE LISTED IN THE THREAD BELOW BEFORE UPDATING!!!!!
THREAD WITH INFO ON OTHER ICS LEAKS AND WHY WE ARE ADVISING AGAINST THEM AT THIS POINT. Originally posted by alteredlikeness
The rest of this will mainly be references to threads as most questions have already been answered in other threads as I just felt we needed a place to consolidate all the info out there on this. Here goes...
In the following theads, PLEASE thank the OP's!
HOW DO I UPDATE TO ICS?
Other than the OTA method that has been trickling out at this point, I am ONLY going to refer you to the thread to get you onto the initial leak. Because at this point many of us see this is as the safest leak. As you have a way out. Because we want to do what is best for you and YOUR phone.
NOTE: The rest of these threads (unless otherwise specified) refer ONLY to the first leak, and to NOTHING ELSE!!!!
How to get your phone on ICS, and how to root it: Originally posted by Jimbridgman
Ok so now that you are comfortably running ICS and rooted.....
HOW DO I INSTALL A RECOVERY?
We currently have two recoveries for the first ICS leak. Both are very stable and work well, but are slightly different. Read each of the following threads for how to install and the differences between them.
BOOTMENU RECOVERY Originally posted and developed by lukensteinz and Whirleyes
SAFESTRAP RECOVERY Originally developed and posted by Recognized Developer Hashcode
And FOR PETE'S SAKE, now that you have a slick recovery working MAKE A BACKUP!. And then copy it and put one on your desktop!!!!
I MADE A MISTAKE, HOW DO I FXZ BACK?
You are ONLY going to be doing this if you somehow messed up a MOD, didn't make a backup, and now you are in a bootloop. REMEMBER, THIS IS ONLY FOR THE FIRST LEAK. I AM NOT RESPONSIBLE IF YOU DID NOT READ THROUGH FAR ENOUGH AND BRICK YOUR PHONE. If you managed to try and FXZ back while NOT on the first leak, or your phone won't turn on or go into FB, then, well sorry mate, but you are HARD-BRICKED. But if you are on the first leak then the following should work.
HOW TO FXZ BACK TO GINGERBREAD FROM THE FIRST ICS LEAK Originally posted and developed by Jimbridgman
ROMS TO INSTALL BASED ON THE FIRST LEAK
NOTE: You must be on the first ICS leak in aforementioned post to properly install the following ROMS, unless otherwise noted by the devs! And as always read CAREFULLY the installation procedure as laid out by the developer!!!
ScV7 - ICSupercharged Originally developed and posted by rdavisct
De-odexed and De-bloated basic ROM Originally developed and posted by timmytim
ROMS THAT ARE STILL A WIP:
MIUI PORT FOR A2 V4 2.8.17 Originally developed and posted by rdavisct
CYANOGENMOD 10 - JELLYBEAN Originally posted and ported by wanggjghost with continued help and fixes by rdavisct and Jimbridgman
In closing, hopefully this will answer all your who's, what's, and how's of ICS on the A2. Please DO NOT post questions regarding the threads themselves here. Post those in the appropriate posted thread, as this is what this is for. TO KEEP THINGS ORGANIZED!!!!!
If I need to update the OP, or have left something out. Feel free to post it here.
Enjoy ICS! And remember! ALWAYS MAKE A BACKUP!!!!!!!
Special thanks to the following: Jimbridgman, rdavisct, alteredlikeness, Apex_Strider, DX2Trip, Mtnlion and any others I left out.
One quick question what does bootloader, hard-brick and fastboot mean. JK
Thanks for the write up. I hope this saves alot of question's from being posted.
Sent from my MB865 on ICS
Good post man. Answered alot of my questions
Thanks for this, plenty of good information.
rdhoggattjr said:
One quick question what does bootloader, hard-brick and fastboot mean. JK
Thanks for the write up. I hope this saves alot of question's from being posted.
Sent from my MB865 on ICS
Click to expand...
Click to collapse
Consider your bootloader a prison warden. Nothing happens unless the bootloader says so. Pretty much plain and simple really. It's the partition on your device, which initiates first. And it checks to make sure the OS is a legitimate one. Ultimate security. If it thinks everything is in order (after communicating with the kernel), it boots the OS. This is the security most devs have to work at, to allow installation of custom recovery and roms.
There are 2 types of "bricks". A hard and soft brick. Soft bricks you can usually recover from. A hard brick, well, it's not impossible, but difficult. Typically with a hard brick, your device is basically dead. No response, or stuck at the logo screen forever more. forever more. forever more...... Edgar Allen Poe. You always want to avoid a hard brick. In essence, your device becomes nothing more than a ....brick.
Fastboot, is a part of the Android SDK. It allows some types of files to be "flashed" to certain partitions of the device, without a need for a custom recovery. For example a boot.img (kernel for easier terms), a recovery image, and a few other image files. Of course depending on the Bootloader, depends on what fastboot capability you have.
Some devices, Devs have been able to re-write the Bootloader to enable fastboot when it wasn't there from the factory. See Iconia A500. By virtue of patching, and re-writing, the bootloader was stripped of all security and features added. But you can't do this with all bootloaders.
Hope this explained.
MD
Hey Bro I have an Ics ota now. Will that unroot the phone? If yes how do I root it back? And is there gonna b any problem if I update with root?
Sent from my stock rooted Atrix2!
If you are stock 2.3.6 rooted, then yes you will lose root.
As far as rooting ICS goes you should be able to root it with Jim's script from the thread I posted in the OP.
Sent from my SAMSUNG-SGH-I727 using xda premium
Just a question out of the discussion but not of the thread. Why does ATT gets last the ICS OTA?? I see Cambodia and India got it already while ATT phones are still on leaks!!! Isnt this weird considering that ATT is the biggest Moto fan?!
how is the battery life on ics? better or less than GB???
V1P3R92 said:
Just a question out of the discussion but not of the thread. Why does ATT gets last the ICS OTA?? I see Cambodia and India got it already while ATT phones are still on leaks!!! Isnt this weird considering that ATT is the biggest Moto fan?!
Click to expand...
Click to collapse
Ahem, Viper? Did you not read my post man? TRUST ME. You want to be on the leak.
hemanbond said:
how is the battery life on ics? better or less than GB???
Click to expand...
Click to collapse
When I was on the leak, I personally was getting better battery life.
However, remember that battery life is all subjective. What might be good for me might not be others!
Sent from my SAMSUNG-SGH-I727 using xda premium
and what about root checker?
Yes there is a "Root checker" however, it will not hinder your installation, but as far as long term issues? We have no idea as to what Motorola is going to do with this.
its obvious for voiding our warranty
hemanbond said:
its obvious for voiding our warranty
Click to expand...
Click to collapse
If you're rooting/modding/theming/tweaking/overclocking/underclocking/changing voltages/editing build.prop/etc./etc./etc. haven't you already thrown caution to the wind in regards to your warranty?
If you are concerned about it, they (Apple) just released a new iToy, so all you have to do is pull it out of the box and use it.. as is... unless you 'jailbreak it', in which case, warranty worries wander back into the equation, right?
once started how do i stop the ota download
You don't. You can download it, and then NOT install it if you like. Once downloaded it will be in your cache folder.
Sent from my SAMSUNG-SGH-I727 using xda premium
it said update failed and now its asking me to download again....wth
---------- Post added at 10:57 AM ---------- Previous post was at 10:38 AM ----------
downloading was so slow that it took me 4 hrs...damn...and now it failed and asking me to download again
hemanbond said:
it said update failed and now its asking me to download again....wth
Click to expand...
Click to collapse
If update failed because of checksum error, downloading again won't be of help. Most likely you have changed a file that the update is trying to patch. Better you go back to stock 2.3.6 and then apply OTA.
Same happened with me as to the person above. Downloaded the update. I but it says update failed? Do I have to unroot or something?
Sent from my stock rooted Atrix2!
hi,
m kinda new to android phones.have been using iphone since 2007......very much expert with jailbreaking.....never bricked any iphone....coz u can always restore if anything goes wrong.
now i got a At&t one x and its on 4.0.4 with software version 2.20...i want to upgrade to jelly bean so i was looking through this forum....but i went through many post in which people have bricked their phones permanently....
now i want to root and install custom rom but m scared if i can brick my one x.....
can anyone tell possible reasons for bricking...and bricked phones can be unbricked???
sorry if this is repost but help will be appreciated....
thanks
Piyush
You can brick by flashing clockworkmod recovery or flashing a ROM from the other one x
Stay in this forum, do tons of research, and then do more research to know the difference from these two phones so you don't brick it
Sent from my One X using Tapatalk 2
The most common reason is flashing something meant for the international (Tegra3) One X. The hardware is completely different, and the memory partitioning is different. If you flash something meant for the international One X it may overwrite the hboot partition, meaning you are pretty much done.
There have been some people that have unbricked from this condition by fixing the partitions using a Linux coputer. But its not simple or a sure thing. There is a thread about it in General, if you are curious.
Otherwise, just stick to things in the AT&T One X specific forum. Read up, and follow instructions carefully, and you will not brick.
Technically, if it doesn't overwrite the hboot, you are done
Sent from my HTC One X-
I believe that with 2.20, it overwrites the extended partition table, not hboot, but that's almost as bad since it means the CPU can't find the OS.
iElvis said:
I believe that with 2.20, it overwrites the extended partition table, not hboot, but that's almost as bad since it means the CPU can't find the OS.
Click to expand...
Click to collapse
Ok, good to know. The moral of the story is that flashing a ROM, recovery, or other mods meant for the international version may overwrite something cirtical in memory due to the different partitioning, that causes you to be fooked.
Don't flash anything meant for the international version, and you don't need to worry about it.
Reason you've never bricked an iPhone is because you can't really change the way it boots or operates.. There's 1 type of firmware that's compatable with only iphones and nothing else. On android your changing the entire operation system that is not monitored or regulated.. If you install an operating system for a totally different phone, it'll render it useless.. Apple ensures you this will never happen with them lol. Therefore they lock it down
Sent from my One X using Tapatalk 2
InflatedTitan said:
Reason you've never bricked an iPhone is because you can't really change the way it boots or operates.
Click to expand...
Click to collapse
Well, not exactly. The jailbreak process is a change in how the phone boots, and it de-sandboxes the apps, which is an operational change. But it's not on the same level of a custom rom.
It is true you can't make major firmware changes with iTunes, but there are other methods of screwing around with the firmware, if you know what you're doing. It's just that this is beyond the abilities of anyone but jailbreak devs, so you don't hear about average users bricking their iPhones with redsn0w or Cydia.
Hey guys.
I have a rooted, unlocked bootloader, custom "recoveryed" Nexus 5, on stock 4.4.4 and stock kernel.
My question is, when Android L comes around, what should I do to update. Doing an OTA update is probably not the best idea right? Since I am rooted and have a custom recovery. So, what would be the steps to take to update. I don´t mind loosing root or making a fresh install.
Anyway just a noob question about something that I never had to do, since I rooted it on 4.4.4.
Thanks for your attention.
Flash a factory image.
Where can I get those?
J.Diogo said:
Where can I get those?
Click to expand...
Click to collapse
On the Google site. Google "nexus factory images"
Sent from my Nexus 5 using Tapatalk
You can OTA update fine. It will just remove root is all.
Get the wugfresh toolbox and reinstall root after. This is what I do every time.
Don't use toolkits.
Sent from my Nexus 5 using Tapatalk
rootSU said:
Don't use toolkits.
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
why Ive been using the wugfresh forever now. On my nexus 5 and 7 with no issues.
tevil said:
You can OTA update fine. It will just remove root is all.
Get the wugfresh toolbox and reinstall root after. This is what I do every time.
Click to expand...
Click to collapse
I've been away from the Nexus 5 forum for a while, I come back and this is still happening. Please don't recommend rootkits for people who are clearly new to android modification. As said a million times on these forums, rootkits are fine if you know what you're doing but not for beginners. Beginners need to do things manually because they need to be able to fix their own mistakes if they're simple. Instead of going back here and asking very basic questions which they could have answered themselves if they didn't use a rootkit.
OP: Please do as @rootSU said and flash a factory image. His sig contains all the threads and information you need. It's a very handy tool which can fix your phone's software problems in almost any situation. Especially in the case of Android L (an update with HUGE internal changes), I highly recommend flashing factory image. This is what I will be doing. The factory image completely replaces your OS with stock.
PsychDrummer said:
I've been away from the Nexus 5 forum for a while, I come back and this is still happening. Please don't recommend rootkits for people who are clearly new to android modification. As said a million times on these forums, rootkits are fine if you know what you're doing but not for beginners. Beginners need to do things manually because they need to be able to fix their own mistakes if they're simple. Instead of going back here and asking very basic questions which they could have answered themselves if they didn't use a rootkit.
OP: Please do as @rootSU said and flash a factory image. His sig contains all the threads and information you need. It's a very handy tool which can fix your phone's software problems in almost any situation. Especially in the case of Android L (an update with HUGE internal changes), I highly recommend flashing factory image. This is what I will be doing. The factory image completely replaces your OS with stock.
Click to expand...
Click to collapse
Okay but thats a fine answer over "dont use rootkits"
That made me think they were bad or something.
Technically like myself he is all stock he said, so aside root hes already pretty much stock OS.
Not sure where the animosity is. Also he obviously knows how to root and install custom Bls if hes done it before.
I very rarely pop in here anymore myself unless there is a major issue but doing things the way Ive been has pretty much eliminated those (jinx). Im still more on the Nexus S forum since I tinker with that more as my mp3 player.
He could always just take a backup before updating and dive in. Ive done that in the past with fine results.
Also even IF you do everything manually first and down the line screw up something theres a pretty BIG chance youll be here asking wtf happened. It happens to the best of us at one point or another.
tevil said:
Okay but thats a fine answer over "dont use rootkits"
That made me think they were bad or something.
Technically like myself he is all stock he said, so aside root hes already pretty much stock OS.
Not sure where the animosity is.
Click to expand...
Click to collapse
they are bad if you dont know what you're doing
the animosity comes in to play when you read the forums daily and you see threads saying "HELP i tried to use such and such toolkit and now my phone doesnt work"
tevil said:
Okay but thats a fine answer over "dont use rootkits"
Also even IF you do everything manually first and down the line screw up something theres a pretty BIG chance youll be here asking wtf happened. It happens to the best of us at one point or another.
Click to expand...
Click to collapse
Yeah, but that's why we ask people to read all the threads before starting to mess with the device first. If you understand how the basic things work and what you're actually doing to achieve root, it's alot easier to troubleshoot very basic problems yourself. Of course for bigger issues people can feel free to post and get help. Also, if they did read everything and still messed up, when they post they're able to list the steps they've taken in the post so people can help them better. Otherwise, it becomes "help I messed up, I don't know what to do, I pressed the start button on the toolkit and my phone doesn't turn on."
Regarding the first part of your post, I still think it's just better to start fresh. Yeah, you can do a backup and try it but I honestly think it will be wasting time. It's always good to start fresh once in a while even if you don't use xposed/rooted apps. Eventually, your phone gets cluttered with apps and sometimes they conflict and you have battery issues, and other issues, etc. Since L is the biggest update to android since even I've been involved in it (I only started getting involved in XDA around 4.0), I would highly recommend everyone flashes the factory image and starts fresh. That way you will also know if there are bugs with L itself, or if's the fact that you installed on top of kitkat and all your prior data that's causing the issue. Anyway, no hard feelings. You said you don't spend a lot of time here so it's understandable.
Zepius said:
they are bad if you dont know what you're doing
the animosity comes in to play when you read the forums daily and you see threads saying "HELP i tried to use such and such toolkit and now my phone doesnt work"
Click to expand...
Click to collapse
Well my bad, Ive never seen that. But toolkits (mainly this one) have very detailed instructions. Let alone the same issues happen when using ADB and push.
Its a double edged sword. I get the , go the long route first, which even I did (but also pre root kits), but In my own defense reading the OP he already did root and BL his phone (to my assumptions) so I didnt think my input was that bad.
---------- Post added at 04:49 PM ---------- Previous post was at 04:47 PM ----------
PsychDrummer said:
Yeah, but that's why we ask people to read all the threads before starting to mess with the device first. If you understand how the basic things work and what you're actually doing to achieve root, it's alot easier to troubleshoot very basic problems yourself. Of course for bigger issues people can feel free to post and get help. Also, if they did read everything and still messed up, when they post they're able to list the steps they've taken in the post so people can help them better. Otherwise, it becomes "help I messed up, I don't know what to do, I pressed the start button on the toolkit and my phone doesn't turn on."
Regarding the first part of your post, I still think it's just better to start fresh. Yeah, you can do a backup and try it but I honestly think it will be wasting time. It's always good to start fresh once in a while even if you don't use xposed/rooted apps. Eventually, your phone gets cluttered with apps and sometimes they conflict and you have battery issues, and other issues, etc. Since L is the biggest update to android since even I've been involved in it (I only started getting involved in XDA around 4.0), I would highly recommend everyone flashes the factory image and starts fresh. That way you will also know if there are bugs with L itself, or if's the fact that you installed on top of kitkat and all your prior data that's causing the issue. Anyway, no hard feelings. You said you don't spend a lot of time here so it's understandable.
Click to expand...
Click to collapse
I hear ya.
I ran the L beta a while so honestly Im not that worried. JINX, Im sure you will be answering my HELP thread in 4 weeks! lol
There was no animosity from me. I simply said "don't use toolkits" and that was for good reasons which have been well written in the (General) sticky threads that all new users should read
The problem is we have to waste our time trying to explain what fastboot is to someone who broke their phone after only having used a toolkit. This is why we prefer people don't use them or recommend them.
On top of that,many toolkits are multi-device and this can cause bricks when faced with uneducated users.
Sent from my Nexus 5 using Tapatalk
Yhea. I also remember, when I was first serching for ways to root the Nexus 5 on stock 4.4.4, I saw many warnings saying to not use toolkits.
I ended up usung CF-Auto-Root, wich is not a toolkit right? :-/
J.Diogo said:
Yhea. I also remember, when I was first serching for ways to root the Nexus 5 on stock 4.4.4, I saw many warnings saying to not use toolkits.
I ended up usung CF-Auto-Root, wich is not a toolkit right? :-/
Click to expand...
Click to collapse
Its not but it still sort of removes some of the manual steps we hope you would learn doing it all manually.
Best place to start is the general sticky thread. My adb and fastboot thread is designed to be a good start for people looking for basic info. Then anyone looking to actually root can move on to the rooting guides which employ much of what was learned in the former thread.
Sent from my Nexus 5 using Tapatalk
Right. I was checking the guide from the thread in your signature and saw the way you did the root. I've done the fastboot and bootloader unlock and all those thing, but when I got to the root part I used the CF-Auto-Root. Is this going to give me problems?
J.Diogo said:
Right. I was checking the guide from the thread in your signature and saw the way you did the root. I've done the fastboot and bootloader unlock and all those thing, but when I got to the root part I used the CF-Auto-Root. Is this going to give me problems?
Click to expand...
Click to collapse
No no. As a root method it works fine. Just not as an educational piece
Sent from my Nexus 5 using Tapatalk
@rootSU your point being? I mean, isn't rooting with the CF Auto Root easier.
larwindcunha said:
@rootSU your point being? I mean, isn't rooting with the CF Auto Root easier.
Click to expand...
Click to collapse
you clearly didnt read.
good god look what I started lol.