I'm no longer providing support for this thread due to time constrains with school, thank you for your support and it been nice sharing this method with you all. I may be gone but this method has still been reported as working, but it is possible that the next updates pushed to your phone might break the rooting and this method might not work anymore. But there is no harm in trying, at most you get an error in recovery saying file is invalid.
This method works on the released ICS rom from Germany and I would expect it to work for the rest of the ICS roms due for release..
This method does not increase the binary counter or causes a yellow exclamation mark
Update :
Due to rising numbers of phone being bricked based on rumors and stuff, I strongly suggest NOT trying to use any nandroid backup or restore on this CWM and it is best we keep CWM out of our devices to do major I/O stuff. So far I have never seen anyone bricked their devices on this small rooting/unrooting process but JUST DO NOT MAKE BACKUPS OR RESTORES!
Rooting
Download the Files first and put in your EXTERNAL SD
Reboot to stock recovery. - Shutdown your device completely, press and hold Vol Up + Power button + Home, releasing the power buttons once you see the Samsung GALAXY Note N7000 screen but continue to hold the Vol Up and Power buttons still until you enter recovery
Choose apply update from external storage. - Touch the screen as if you are using the phone to choose the options.
Choose CWM.zip and wait until CWM recovery appear.
( From this point on, the volume rockers and power buttons do not work! It is now a Touch interface like how you use the phone normally )
Choose install zip from external SD
Choose and Install SU-Busybox-Installer.zip
Reboot
You are done and now your device is Rooted
Unroot
Download this File first and put in your EXTERNAL SD
Reboot to recovery.- Shutdown your device completely, press and hold Vol Up + Power button + Home, releasing the power buttons once you see the Samsung GALAXY Note N7000 screen but continue to hold the Vol Up and Power buttons still until you enter recovery
Choose apply update from external storage.- Touch the screen as if you are using the phone to choose the options
Choose CWM.zip and wait until CWM recovery appear.
( From this point on, the volume rockers and power buttons do not work! It is now a Touch interface like how you use the phone normally )
Choose install zip from External SD
Choose and Install SU-Uninstaller-Signed.zip
Reboot
You are done and now your device is Unrooted
Partial Root
Alright i managed to obtain partial root myself and a fix for the Partial root is quite simple. You can install SuperSU by Chainfire and update the root. would fix the Partial root. Once you install this.. DO NOT USE the Superuser app and DO NOT uninstall the SuperUser app. Use SuperSU from now.
SuperSU - https://play.google.com/store/apps/details?id=eu.chainfire.supersu&hl=en
MOD Edit: cwm.zip removed from the attachments, read Entropy512's post.
Thanks, but does this install CWM as well? id like to know so that I can go straight to flashing roms from it
are you sure this works ? can anyone confirm ?
nightfox11 said:
are you sure this works ? can anyone confirm ?
Click to expand...
Click to collapse
Works perfectly. Just rooted stock ICS.
Got a brand new Note in the box here.....
Trying to get things straight. Seems like I have two options now for rooted official ICS.
1. This method. Update official ICS Via PC odin (no binary counter, ect) and then follow above instructions.
2. Root stock gb via old method (not sure what that is yet) and then use the mobile odin proceedures w/ new ICS CF kernel?
Is the end result gonna be the same?
Bonus question for noob: what is binary counter and red triangle/exclamation point?
Sent from my SPH-D700 using xda premium
kvanlier said:
Works perfectly. Just rooted stock ICS.
Click to expand...
Click to collapse
thanks man!
Did you just copy this thread?
Oh well. No harm done I guess. Of course it works. It's a method for all android phones. Temporary cwm so you can copy busybox to /system.
Yeah it looks like it, but since it actually works i can't see why that would be a bad thing. But i would give the original author credits in the first post; that is if you copied it.
akenis said:
Got a brand new Note in the box here.....
Trying to get things straight. Seems like I have two options now for rooted official ICS.
1. This method. Update official ICS Via PC odin (no binary counter, ect) and then follow above instructions.
2. Root stock gb via old method (not sure what that is yet) and then use the mobile odin proceedures w/ new ICS CF kernel?
Is the end result gonna be the same?
Bonus question for noob: what is binary counter and red triangle/exclamation point?
Sent from my SPH-D700 using xda premium
Click to expand...
Click to collapse
Yes you will end up with the same result if you take either one of the 2 ways to root
Binary counter is a Samsung measurement of how many times you flashed custom firmwares using PC Odin, and the yellow (not red ) triangle is just a logo to further show that you indeed flashed custom firmware
However, the binary counter will not increase (and therefore no yellow triangle will appear) if you:
1. Flash stock firmware with PC Odin
2. Flash using Mobile Odin app by ChainfireXDA
3. Flash using CWM recovery
I got binary counted to 1 with yellow triangle after flashing ics stock from alba.can i use this method to erase counter and triangle?
Sent from my GT-N7000 using Tapatalk 2
So this gives cwm too looks easy
Sent from my GT-N7000 using Tapatalk 2
Drat?
I didn't have GB root because my previous version had root, but I $%*^ screwed
up and let KIES update it to 2.3.6 and I've got too much work to screw around with back flashing wiping etc.
I went ahead and let kies update to ics, now, my question, will this method work, or will I still have to go though all the other to get it to work.
I see it works on stock ICS, but is that after kies, or after you update via pc odin?
victorator said:
Did you just copy this thread?
Oh well. No harm done I guess. Of course it works. It's a method for all android phones. Temporary cwm so you can copy busybox to /system.
Click to expand...
Click to collapse
LordManhattan said:
Yeah it looks like it, but since it actually works i can't see why that would be a bad thing. But i would give the original author credits in the first post; that is if you copied it.
Click to expand...
Click to collapse
Not many ways to have a drastic difference from the method but hey it works well.
p51d007 said:
I didn't have GB root because my previous version had root, but I $%*^ screwed
up and let KIES update it to 2.3.6 and I've got too much work to screw around with back flashing wiping etc.
I went ahead and let kies update to ics, now, my question, will this method work, or will I still have to go though all the other to get it to work.
I see it works on stock ICS, but is that after kies, or after you update via pc odin?
Click to expand...
Click to collapse
This method works as long as you are on Stock ICS.. Can't really go wrong really.
so i did and have root and root works..
now my question is....
given that we get temp CWM..can i use the temp CWM to flash radios?
AND so if i want to flash LP6 radio via CWM will the steps be.
load Stock recovery
flash CWM.zip in stock recovery
load CWM
flash lp6 radio
will that work?
=============================
After no one answered i took the plunge...
Yes
so can confirm that the above procedure will work
PS: Am amazed how this is not in the sticky
Can anyone tell me any issues with using the CWM offered in this thread??? as in any issues with flashing other roms?? etc??
I fail to see?
The only issue is that CWM is not permanent but u can easily re-enable it by flashing it again...
again..dont understand why ppl are not paying attention to this thread as is great!
how come i only got partial root? i cannot paste into system
deathst said:
This method works as long as you are on Stock ICS.. Can't really go wrong really.
Click to expand...
Click to collapse
You are right, finally got my root back ICS, after the 2.3.6 update, been a while, now I have to remember how to use the freeze program, LBE security etc...all over again LOL. THANKS!
elijahtan said:
how come i only got partial root? i cannot paste into system
Click to expand...
Click to collapse
Try rooting again.. Are you sure your file manager app was given permission? Cause this thing is practically fool proof.
nandihno said:
so i did and have root and root works..
now my question is....
given that we get temp CWM..can i use the temp CWM to flash radios?
AND so if i want to flash LP6 radio via CWM will the steps be.
load Stock recovery
flash CWM.zip in stock recovery
load CWM
flash lp6 radio
will that work?
=============================
After no one answered i took the plunge...
Yes
so can confirm that the above procedure will work
PS: Am amazed how this is not in the sticky
Can anyone tell me any issues with using the CWM offered in this thread??? as in any issues with flashing other roms?? etc??
I fail to see?
The only issue is that CWM is not permanent but u can easily re-enable it by flashing it again...
again..dont understand why ppl are not paying attention to this thread as is great!
Click to expand...
Click to collapse
Glad it works for you Yes I wonder why is not many people taking notice.. :S
...and i thought I was screwed
THANKS MAN. works perfect. much faster than having to redownload the odex vrs
Worked perfectly thanks !
Sent from my HTC One X using xda premium
hmmm.... didn't work for me. CWM looks for update.zip so i renamed it as such. installed and rebooted to CWMR, no touch menu. same old blue colored menu. install su-binary, stuck at unmounting /system = not rooted.
Related
Ok, I have been thrown for a loop and need some help....
I had a Sprint Hero Rooted on 2.1 the .5 sprint update
Tried to run the new update but it kept getting corrupt.
Did a Nandroid backup
So I reverted back to the .5 RUU
Then it wanted me to update to the old .6 update, so I did
Hoping then I would upgrade to the new .6 but it was not able to find a new update?
Wanted to restore my nandroid update.
When I try to boot into the recovery mode I get a picture of a phone with a red Explanation mark in a triangle.
There is a bunch of people on the net that say they have seen or gotten it, but no one says how to get rid of it? So I can not get in to recovery mode at all.
Tried the home+power boot
Tried the volume down + power then home
always ends in the same screen with no recovery.
Tried multiple times to install the .5 RUU
Reset phone
never can get back there to the recovery?
Phone will boot fine into 2.1 and run fine..
Anyone have any ideas, I have tried everything I can think of.
Thanks
Did u try placing the recovery on ur SD card and flashing it threw terminal on ur phone
Root-Hack-Mod-Always™
You lost root, as far as I remember the .6 update was to block the corrent rooting efforts that you see around here, thats why the rooting instruction say to go back to the .5 ruu.
The corrupted update your getting is just sprints server being bogged down.
What you need todo is go back and re-root your phone. Dont worry about the update untill it gets released into one of the current roms or until you here that its safe todo without losing root.
ASimmons said:
You lost root, as far as I remember the .6 update was to block the corrent rooting efforts that you see around here, thats why the rooting instruction say to go back to the .5 ruu.
The corrupted update your getting is just sprints server being bogged down.
What you need todo is go back and re-root your phone. Dont worry about the update untill it gets released into one of the current roms or until you here that its safe todo without losing root.
Click to expand...
Click to collapse
Thanks, I can't believe I missed that! I had never tried a backup before root, so I did not think about that. Now I know and hopefully this will help someone that googles this issue, as there is never a clear answer until yours.
Thanks again...
So in closing of this thread:
if you are trying to get into recovery and see "Phone with Explanation mark" image.
it's because your phone is not rooted
So root your phone and it's all good
Also If you ever run an ruu on your phone you can kiss your root good bye no matter what version you do. but if you have nand backups you can reroot your phone and then restore one of your backups since there stored on your sdcard.
copc said:
So in closing of this thread:
if you are trying to get into recovery and see "Phone with Explanation mark" image.
it's because your phone is not rooted
So root your phone and it's all good
Click to expand...
Click to collapse
Correction: If you see this symbol, it means you don't have a custom recovery image in the phone. You can actually be rooted and still get that symbol if you haven't yet flashed a custom recovery after you rooted. You need to have a custom recovery (that requires root) to avoid getting that symbol when you try to boot into recovery.
Most rooting methods on here automatically include flashing a custom recovery as one of the steps, so this isn't really a big issue....but I just wanted to clarify the specifics of this for anyone else who reads.
copc said:
So in closing of this thread:
if you are trying to get into recovery and see "Phone with Explanation mark" image.
it's because your phone is not rooted
So root your phone and it's all good
Click to expand...
Click to collapse
I am running a rooted 2.1 and get this symbol , i installed rom manager and it asked me to install flash clockworkmod recovery and it booted into recovery straight away allowing me to partition my sd card, but if i want to access this mode i have to run flash clockworkmod recovery everytime or it will not work
Any idea why that is anyone?
brisuth said:
I am running a rooted 2.1 and get this symbol , i installed rom manager and it asked me to install flash clockworkmod recovery and it booted into recovery straight away allowing me to partition my sd card, but if i want to access this mode i have to run flash clockworkmod recovery everytime or it will not work
Any idea why that is anyone?
Click to expand...
Click to collapse
Nope once its on there you should be able to hold the home key while rebooting to get into recovery.
Sent from my HERO200 using XDA App
ASimmons said:
Nope once its on there you should be able to hold the home key while rebooting to get into recovery.
Sent from my HERO200 using XDA App
Click to expand...
Click to collapse
only way can get there is through flash clockworkmod recovery then select either reboot in recovery mode or turn of handset and restart with home and power button, what ever flash clockworkmod recovery does to make it work as soon as it has been used i am guessing it is deleted or modified,
i have tried running it then checking files on sd card but cant see anything different
brisuth said:
only way can get there is through flash clockworkmod recovery then select either reboot in recovery mode or turn of handset and restart with home and power button, what ever flash clockworkmod recovery does to make it work as soon as it has been used i am guessing it is deleted or modified,
i have tried running it then checking files on sd card but cant see anything different
Click to expand...
Click to collapse
The recovery console isn't on your SD card, it's flashed to a partition inside your phone's memory. So you won't see anything different on your card.
And if you can boot into recovery by "restart with home and power button" like you say, then it's working as it should -- that's how you get into recovery.
chromiumleaf said:
The recovery console isn't on your SD card, it's flashed to a partition inside your phone's memory. So you won't see anything different on your card.
And if you can boot into recovery by "restart with home and power button" like you say, then it's working as it should -- that's how you get into recovery.
Click to expand...
Click to collapse
just had a friendly member point out what i was starting to suspect the problem lies with the custom recovery being flashed back to stock on every restart, the shell command here
/system/etc/install-recovery.sh this stops any custom recovery on reboot. any advice on what tools to edit or remove
Delete that file when you get root I guess. Our as soon as you reboot into clockwork recovery, flash a rom. Use nfinitefx if you want a stock one
Sent from my HERO200 using XDA App
I always had root that was where the confusion was, what i did not know was the script was running with every boot of the handset and removing the recovery that was there as it was identified as unofficial and exclamation mark could be down to me using many methods to flash i may have renamed original recovery so when it goes to exclamation it is because cant find original recovery whether handset is rooted or not.
danaff37 said:
Delete that file when you get root I guess. Our as soon as you reboot into clockwork recovery, flash a rom. Use nfinitefx if you want a stock one
Sent from my HERO200 using XDA App
Click to expand...
Click to collapse
would that have worked? i thought about it many many times but as i had never flashed before was unsure how many times phone would reset and if it did before it was installed could i lose my recovery.
on the plus side the 2 months i have spent trying to solve this i have a much broader view of the workings of my handset and without the many members like yourself who take the time to reply and try to help others i would have given up a long time ago.
Brian
I'm sure if you deleted that script a custom recovery would have stuck
Sent from my HERO200 using XDA App
This is probably just me but I'm starting to think we are over complicating the ROM installation process by having different versions of recovery and flashing. We already have KIES and odin, do we need different recovery installations too?, tegrak, CMR, chainfires etc? We are now seeing ROMS that can only be flashed with one type which cant be good as its causing fragmentation of development. I may also have contributed to two people who have bricked their phones recently.
Why on earth are we doing this?, wouldnt it be much better to use one type of recovery, that way anyone can flash any ROM with it without having to change root / kernels etc.
I am sure each different version has its own advantages but are these really worth the fragmentation it is causing, be nice if devs all decided to get together and come up with a one fits all CWR which is then used on all ROMS and all Phones.
I can dream cant I, feel free to put me straight on this if I am missing something here.
couldn't agree more. i rooted my phone the other day with a kernel change, but now i want to isntall a rom but cant even start to work out the way to get cwm on to flash a rom!!! annoyinh to say the least.... the x10 and sgs1 i had were a breeze
da.trute said:
This is probably just me but I'm starting to think we are over complicating the ROM installation process by having different versions of recovery and flashing. We already have KIES and odin, do we need different recovery installations too?, tegrak, CMR, chainfires etc? We are now seeing ROMS that can only be flashed with one type which cant be good as its causing fragmentation of development. I may also have contributed to two people who have bricked their phones recently.
Why on earth are we doing this?, wouldnt it be much better to use one type of recovery, that way anyone can flash any ROM with it without having to change root / kernels etc.
I am sure each different version has its own advantages but are these really worth the fragmentation it is causing, be nice if devs all decided to get together and come up with a one fits all CWR which is then used on all ROMS and all Phones.
I can dream cant I, feel free to put me straight on this if I am missing something here.
Click to expand...
Click to collapse
But everyone is using CWM anyway...
And the .zip is a standard way to flash a ROM. So in theory, you can use any recovery to flash your zip
So there's no need to come up with some one-size-fits-all, as the zip files used meet a standard
Freedom to choose is a great thing. I like having options.
pulser_g2 said:
But everyone is using CWM anyway...
And the .zip is a standard way to flash a ROM. So in theory, you can use any recovery to flash your zip
So there's no need to come up with some one-size-fits-all, as the zip files used meet a standard
Click to expand...
Click to collapse
I am currently using cognition ROM, are you suggesting I can download any ROM, say Villain and copy to my SD and install without doing anything else?, I dont think that is the case, it mentions a different root, as does extreme. Cog and mui have no mention of changing root.
Intratech said:
Freedom to choose is a great thing. I like having options.
Click to expand...
Click to collapse
It is yes, however you seem to have misunderstood the thread, having different methods being forced up you by different cooks is not choice, choice would be that all methods were compatible and interchangeable, they are not apparently. Some require different roots / kernels.
EDIT. not suggesting anything is really being forced on us, I appreciate all dev work, just hoping for a bit more conformity of installation process.
da.trute said:
I am currently using cognition ROM, are you suggesting I can download any ROM, say Villain and copy to my SD and install without doing anything else?, I dont think that is the case, it mentions a different root, as does extreme. Cog and mui have no mention of changing root.
Click to expand...
Click to collapse
You copy it to internal SD, pull your head out of your ass, turn phone off, turn phone on holding menu and volume up and choose to flash zip from SD card.
Just.
Like.
Every.
Other.
Rom.
seshmaru said:
You copy it to internal SD, pull your head out of your ass, turn phone off, turn phone on holding menu and volume up and choose to flash zip from SD card.
Just.
Like.
Every.
Other.
Rom.
Click to expand...
Click to collapse
Cognition uses CMR root, Villain uses CF-root, I am pretty sure you cannot flash Villain straight of the top of a non CF rooted phone, or I am wrong?
da.trute said:
Cognition uses CMR root, Villain uses CF-root, I am pretty sure you cannot flash Villain straight of the top of a non CF rooted phone, or I am wrong?
Click to expand...
Click to collapse
See, if you actually had developed the ability to read, you would know that all root is is the su script in the ROM and SuperUser.apk, nothing more.
You would also know root has nothing to do with flashing ROMs, since you can have CWM as recovery without having root.
Now if you're flashing an entirely different ROM you might want to select "wipe data/factory reset" before flashing but you can still flash using CWM.
Turn phone off, turn phone on holding volume up and center button, select wipe data/factory reset, and then flash zip from SD card.
Wow. He's just asking a question. Why belittle people for asking?
duuurp said:
Wow. He's just asking a question. Why belittle people for asking?
Click to expand...
Click to collapse
Because I see exactly 3 threads on the same page that could either answer his question or link him to the answer. But people are too lazy to read.
Due to people like this we have a thread here which isn't needed at all since there is conformity to flashing across all ROMs. All because people make claims about things when they don't even know how it works.
The big difference in swapping from one custom rom to another is not the method of flashing but do you need a clean phone to install a custom rom on top of another one .
My personal choice is a fully wiped phone before installing a new custom rom .
Methods CWM or Odin mostly CWM as thats the major choice for devs .Kies is not a rom flash tool .
Choice also gives a better recovery option .
Villain on top of or below Cognition both use same flash method via rooted CWM flash .
The problem on this forum is not three or four choices but a complete refusal by many to even bother reading any instructions .
jje
duuurp said:
Wow. He's just asking a question. Why belittle people for asking?
Click to expand...
Click to collapse
Hi, you get used to these ***** after a while
seshmaru said:
See, if you actually had developed the ability to read, you would know that all root is is the su script in the ROM and SuperUser.apk, nothing more.
You would also know root has nothing to do with flashing ROMs, since you can have CWM as recovery without having root.
Now if you're flashing an entirely different ROM you might want to select "wipe data/factory reset" before flashing but you can still flash using CWM.
Turn phone off, turn phone on holding volume up and center button, select wipe data/factory reset, and then flash zip from SD card.
Click to expand...
Click to collapse
You have to change kernel at the end of flash on Villain which I suppose isnt the same but is still a difference in installation process
what about touch extreme, whats this about then?
Make sure you got CF Root CWM (not the clockworkmod root) go into CWM, flash zip file, done! its that simple!
PS. some roms out there installs through clockworkmod, not the one by Chainfire, in those cases you must flash Chainfires Root with his version of CWM first!
da.trute said:
You have to change kernel at the end of flash on Villain which I suppose isnt the same but is still a difference in installation process
what about touch extreme, whats this about then?
Make sure you got CF Root CWM (not the clockworkmod root) go into CWM, flash zip file, done! its that simple!
PS. some roms out there installs through clockworkmod, not the one by Chainfire, in those cases you must flash Chainfires Root with his version of CWM first!
Click to expand...
Click to collapse
So let me see, it says flash the .zip with CWM.
So... Lets turn phone off, turn phone on holding volume up, center button and power button, wipe data/factory reset, and then flash .zip from SD card.
All of a sudden it magically works.
PROTIP: They're talking about the CWM app, which you don't need, every ROM still has clockworkmod recovery installed so rebooting with volume up, center button and power button will always let you flash the .zip file.
Kernel files should always be flashed with Odin if you are flashing them seperately since it gives better security. Even if they have a flashable .zip.
It may seem like there are a hundred different versions of CWM recovery but they're all based on the same thing; CWM. They all work on the same premise of copying the zip to the phone and then flashing. Some have integrated apps, some don't but the basic premise remains. The other option is Odin/Heimdall but as one is .tar based and the other is .zip there shouldn't be too much confusion here
seshmaru said:
So let me see, it says flash the .zip with CWM.
So... Lets turn phone off, turn phone on holding volume up, center button and power button, wipe data/factory reset, and then flash .zip from SD card.
All of a sudden it magically works.
PROTIP: They're talking about the CWM app, which you don't need, every ROM still has clockworkmod recovery installed so rebooting with volume up, center button and power button will always let you flash the .zip file.
Kernel files should always be flashed with Odin if you are flashing them seperately since it gives better security. Even if they have a flashable .zip.
Click to expand...
Click to collapse
what does this actually mean then?
"Make sure you got CF Root CWM (not the clockworkmod root)"
I have flashed all three roms using the exact same method .
Changed kernels four times this week using CWM .
Revived one bricked phone using Odin .
jje
Hollow.Droid said:
It may seem like there are a hundred different versions of CWM recovery but they're all based on the same thing; CWM. They all work on the same premise of copying the zip to the phone and then flashing. Some have integrated apps, some don't but the basic premise remains. The other option is Odin/Heimdall but as one is .tar based and the other is .zip there shouldn't be too much confusion here
Click to expand...
Click to collapse
which kind of proves my point really, if they all do the same thing then there is no need for them and no need to stipulate their usage, it just makes flashing more confusing for noobs.
da.trute said:
which kind of proves my point really, if they all do the same thing then there is no need for them and no need to stipulate their usage, it just makes flashing more confusing for noobs.
Click to expand...
Click to collapse
No, there is only 1 method for ROM flashing, CWM. Every ROM has CWM, CWM is the end all be all for you, no matter what different apps do, they all use 1 method CWM. CWM CWM CWM. Stop being dense and read up before posting dumb factually wrong claims.
Every single ROM can be flashed by holding volume up, center button and power, how difficult is it to grasp this concept?
Here this video should help you.
http://www.youtube.com/watch?v=JmvCpR45LKA
I am not a computer guy--tried to install latest update and am now stuck in recovery--I tried to install a recovery off an sd card but seemed to fail and now cant get anywhere. Can anyone walk me through a fix??
Thanks
press ctrl+alt+del
not suer
Need more info. Were you on a stock or custom ROM? Are you stuck in stock or custom recovery? What method did you try to install another recovery?
Sent from my SGH-I777 using xda premium
stuck
I was custom but rooted--tried to update tonight and it failed--then tried to deroot but now stuck un clockwork recovery--I am downloading ics -us but dont even know how to access external card with this file on as recovery lets me only onto internal sd which i think i cannot access
Thanks for the help
this worked for me...my situation sounds very similar to yours....
http://forum.xda-developers.com/showpost.php?p=23587495&postcount=47
ostism attachable
seems to freeze on cold boot??? says cold booting linux but noting happens
I am stuck in something that says clockworkmod Recovery v5.5.0.4
voodoo_dr said:
seems to freeze on cold boot??? says cold booting linux but noting happens
I am stuck in something that says clockworkmod Recovery v5.5.0.4
Click to expand...
Click to collapse
5.5.0.4 from Koush has a known problem
Follow this:
http://forum.xda-developers.com/showthread.php?t=1530337
There are many ways to get out of this situation. Get all the tools (adb, ROM zip files, etc.). Read posts in the thread. Ask for help there.
Good luck.
Put your transformer in APX mode by hold the power button & volume up.. If it turns back on do it again, make sure you have you sync cable plugged in and drivers installed. Now that your in APX download this stock rom then root it with viper (option 1 in viper)
Stock rom
http://forum.xda-developers.com/showthread.php?t=1334673
Viper root works on transformer & prime for root and unroot!!!
http://forum.xda-developers.com/showthread.php?t=1427125
voodoo_dr said:
I was custom but rooted--tried to update tonight and it failed--then tried to deroot but now stuck un clockwork recovery--I am downloading ics -us but dont even know how to access external card with this file on as recovery lets me only onto internal sd which i think i cannot access
Thanks for the help
Click to expand...
Click to collapse
Why you trying a stock ota on a custom rom?
feisty_noodle said:
5.5.0.4 from Koush has a known problem
Follow this:
http://forum.xda-developers.com/showthread.php?t=1530337
There are many ways to get out of this situation. Get all the tools (adb, ROM zip files, etc.). Read posts in the thread. Ask for help there.
Good luck.
Click to expand...
Click to collapse
Yes there's a fix in there towards the bottom of the first post.
If you want to flash another recovery, turn your device on into recovery, connect it to your computer and use adb to push the file to your internal storage.
It should be something like "adb push filename.zip /data/media" then you can use the borked recovery you're on to flash the one you pushed.
tegezee said:
Put your transformer in APX mode by hold the power button & volume up.. If it turns back on do it again, make sure you have you sync cable plugged in and drivers installed. Now that your in APX download this stock rom then root it with viper (option 1 in viper)
Stock rom
http://forum.xda-developers.com/showthread.php?t=1334673
Viper root works on transformer & prime for root and unroot!!!
http://forum.xda-developers.com/showthread.php?t=1427125
Click to expand...
Click to collapse
No, this is overkill and won't fix his issue.
This will work period
fone_fanatic said:
Why you trying a stock ota on a custom rom?
Yes there's a fix in there towards the bottom of the first post.
If you want to flash another recovery, turn your device on into recovery, connect it to your computer and use adb to push the file to your internal storage.
It should be something like "adb push filename.zip /data/media" then you can use the borked recovery you're on to flash the one you pushed.
No, this is overkill and won't fix his issue.
Click to expand...
Click to collapse
Yes it will what are you talking about? If he wants his tablet to work again and if he's not worried about the data on it (since he can't access it anyway) then this will work... Overkill lol , call it what you want it will work and it's simple!
tegezee said:
Yes it will what are you talking about? If he wants his tablet to work again and if he's not worried about the data on it (since he can't access it anyway) then this will work... Overkill lol , call it what you want it will work and it's simple!
Click to expand...
Click to collapse
His problem is with it getting stuck in recovery, which is a known issue with Koush's 5.5.0.4, simple fix with adb. No need to reflash the whole rom.
voodoo_dr said:
I am not a computer guy
Thanks
Click to expand...
Click to collapse
Well if he's not good with a computer, my method is the easiest especially if he doesn't have it figured out by now...
Thanks for the help everyone--Ended up using NVflash to load a rom called prime 1.6. 3:30 a.m. and I am as good as new. No ICS but at least it is stable
Good to see you got it back working...
I'm running completely stock, no rom anything. Just flashed updates from users here to update me to the latest HC. I received the ICS update but pretty sure it won't work since I'm rooted and running CWM recovery. What do I need to do to install ICS? thanks
tu3218 said:
I'm running completely stock, no rom anything. Just flashed updates from users here to update me to the latest HC. I received the ICS update but pretty sure it won't work since I'm rooted and running CWM recovery. What do I need to do to install ICS? thanks
Click to expand...
Click to collapse
Same question here
Sent from my A500 using XDA
3d0rr said:
Same question here
Sent from my A500 using XDA
Click to expand...
Click to collapse
I am in the same camp.
I'm running a rooted 3.2 stock by Timmy Dean.
I'm happy I didn't jump the gun when I Saw the update last night, because it seems I would have truly been screwed.
What I would like to know is if a rooted 3.2 can simply be unrooted. Seems this would the simplest thing to do.
Thanks in advance for any and all help.
Apparently the root doesn't matter. It will just be removed when we install the ota ICS. What worries me is recovery. Because it has to boot into a recovery to install ICS. I had CWM installed then flashed to stock by acer recovery tool in the play store. But when I manually boot into recovery, I get a exclamation point inside a triangle. What recovery are you guys running?
tu3218 said:
Apparently the root doesn't matter. It will just be removed when we install the ota ICS. What worries me is recovery. Because it has to boot into a recovery to install ICS. I had CWM installed then flashed to stock by acer recovery tool in the play store. But when I manually boot into recovery, I get a exclamation point inside a triangle. What recovery are you guys running?
Click to expand...
Click to collapse
I have CWM recovery by thor2002. I think we can't update via ITS unless we flash original recovery
Sent from my A500 using XDA
3d0rr said:
I have CWM recovery by thor2002. I think we can't update via ITS unless we flash original recovery
Sent from my A500 using XDA
Click to expand...
Click to collapse
Yeah I think so as well. I flashed stock via the Acer recovery tool but I get nothing when I boot into recovery except what I stated above. I'm not sure if that's right or not.
Sent from my Galaxy Nexus using XDA
I was happily running timmydean's rooted 3.2.1 based on the leaked OTA. The ICS upgrade came through and installed just fine. No loss of data and the programs I tried all worked. I was on stock 4.0.4 unrooted.
However, I'm now borked. I rebooted into recovery (Power, Vol -) to see about rooting via the backdoor I'd installed. I had thor's 1.7 Touch CWM recovery installed. I got some weird message that recovery was broken. (Don't recall the exact msg.)
After that, it hung on the "android" screen. Soft-bricked.
So I did a factory reset (Power, vol+, rock screen switch) and ended up back on 3.2.1. Now, the Settings > About > Check update results in the "Network coverage is currently poor. Please move to a location with better coverage to continue." message.
My WiFi is fine, speedtest.net reports a 20 Mbps download. All other apps function well. I'm pulling a DCHP address from my router.
I'm fairly sure this is a badly-worded error message from Acer and actually refers to server overload or some other issue on their end.
Also, installing the latest Acer Iconia Update preps the system for ICS. At one point, installing it allowed the update to proceed, but not to ICS. Uninstalling/reinstalling that update seemed to jog the system at one time.
So I tried wiping data/cache/dalvik and went back to stock 3.2. Same error message when updating. Wiped again and went back to stock 3.0.1. Same error message.
So I'm stuck and am going to give it a few days to see if Acer can sort out their upgrade path. If not, I will probably load CM9 or Thor's ICS ROM. (I do have a Nandroid, so I can get back to where I was pre-ICS.)
All in all, I'm very disappointed in Acer for borking my tablet.
________
Update: So now a day later, the "poor coverage" message was replaced by an "update available". Installed A500_7.014.03_com_gen1, after reboot, another update A500_7.014.15_com_gen1 installed. I am now on stock 3.2.1.
System update shows "Your device is up to date".
Will see what tomorrow brings, but this is certainly frustrating.
thorne75 said:
I am in the same camp.
I'm running a rooted 3.2 stock by Timmy Dean.
I'm happy I didn't jump the gun when I Saw the update last night, because it seems I would have truly been screwed.
What I would like to know is if a rooted 3.2 can simply be unrooted. Seems this would the simplest thing to do.
Thanks in advance for any and all help.
Click to expand...
Click to collapse
********************************************
Could you guys running the backdoor and still rooted please try this:
1) Try and capture the build no. of the update
2) See if the update will download BUT do not install yet
3) Go to /cache/fota/ and find the zip -
4) copy it to yr external sd
5) post back the build no.
thanks!!!
Procedure for manual install:
1/ rename the file as : update.zip
2/ place the file on the micro sd card
3/ turn off the tablet
4/ press the down volume key and the power button at the same time untill the tablets turns on
5/ the iconia will start the upgrade process by itself.
OR just redownload the update and it install
*********************************************
I had trouble when i reverted to stock in the weekend
and it was a bit of a process to get the OTA's to 3.2.1.
I did manage to hold "full root" but had to revert a couple of times
by putting stock recovery back and using backdoor .
I accidentally factory reset and everything went a bit pear shaped from there...oops!!
Im still waiting for the OTA ICS - getting network coverage error -one good thing
is my partners tab is only 5 days old and still pure factory,
her tab shows same error so at least we know its not root/backdoor problem
So yeah if u gonna take the OTA best to get rid of the backdoor unless you wanna play guinea pig for us all>>>>
dunno why we aint found one of those yet
I dont think you can cause too much of a problem where a "hard reset" pwr/vol -/rotation lock/ combo wont fix...you can then root from there.
---------- Post added at 12:45 PM ---------- Previous post was at 12:36 PM ----------
3d0rr said:
I have CWM recovery by thor2002. I think we can't update via ITS unless we flash original recovery
Sent from my A500 using XDA
Click to expand...
Click to collapse
hi 3d0rr!!
i think those of us with the backdoor should be meticulous if/when taking the OTA.
we shouldnt need to unroot and use stock recovery as the ota should get rid of that in the flash. But to ensure a stress free OTA it may pay to do it anyway.
i know you previously told me u were stock gen 1 - but is that from factory, just finished reading a very interesting post regarding the different 'gens' so i for one am sticking with factory build gen :just for the official OTA anyway:
dibb_nz said:
********************************************
hi 3d0rr!!
i think those of us with the backdoor should be meticulous if/when taking the OTA.
we shouldnt need to unroot and use stock recovery as the ota should get rid of that in the flash. But to ensure a stress free OTA it may pay to do it anyway.
i know you previously told me u were stock gen 1 - but is that from factory, just finished reading a very interesting post regarding the different 'gens' so i for one am sticking with factory build gen :just for the official OTA anyway:
Click to expand...
Click to collapse
Dibb_nz, I was stock gen 2. I don't wanna take OTA until be sure it's safe. Unless now I know that a hard factory reset may save my tab if something happen.
Can you tell us where did you read that post about 'gens'? I still a little confuse about that
Sent from my A500 using XDA
BTW, the network coverage errors seems to be an Acer's error. First I received OTA and a day after that I see that error on my tab. And a couple of hours later I have OTA again. So, don't worry, you should get OTA asap
Sent from my A500 using XDA
3d0rr said:
BTW, the network coverage errors seems to be an Acer's error. First I received OTA and a day after that I see that error on my tab. And a couple of hours later I have OTA again. So, don't worry, you should get OTA asap
Sent from my A500 using XDA
Click to expand...
Click to collapse
oh sounds promising, although I just read another post from someone across the ditch in OZ he reckoned acer said they were working on a patch for the problems theyre havin with the first update...who knows
now m8, sorry to confuse you, that wasnt my intention, but i try to make sure that i;m not suggesting things which may end with you or others borkin or brickin yr tab. Ive spent the last few days reading thousands of posts (just like everyone else) thankfully we are fortunate in being able to learn from the mistakes of others I know a bit more about ics than i did 3 days ago let me tell you, lol.
i just finished helpin out a fellow "timmy-ite" stuck with no way of getting in to apx mode to get un-borked...well didnt really help just a sounding board more than anything
he got himself up and running, used the apx tool in my sig, unlocked the bootloader, rooted, flashed custom recovery did a nand and is now running flexreaper - with the tools and knowledge he gained he now has the choice to go back to HC to get the OTA or not....he's one happy camper!!!
Have a read have a read thru the threadhere. ask him a question or two if you want - but dont get too hung up "maybe doing something wrong" you won't be the only person ever to experience that uhh-ohh sinking feeling when you know you shouldnt have just done whatever it was that u just did
Theres always someone round here who will help - usually cos they done the same silly lthings themselves - why ya think i'm always posting
what is the backdoor program you guys talk about?
tu3218 said:
what is the backdoor program you guys talk about?
Click to expand...
Click to collapse
timmydean's root method also allows you to install a backdoor to re-root after accepting an OTA. You have to manually install it during the rooting process, so you would know if you had it.
jpinsl said:
timmydean's root method also allows you to install a backdoor to re-root after accepting an OTA. You have to manually install it during the rooting process, so you would know if you had it.
Click to expand...
Click to collapse
timmyDean How to root stock 3.2.1
Summary:
Version V4 is the same as V3 with the only difference being that there is a NEW backdoor script which has some additional features to protect root(#) from getting broken when you do an OTA. I also applied these to this flash image so you wouldn't have to add the additional protection yourself. V4 also has the drivers for XP included. However, when taking an OTA you should also install the backdoor for additional protection. However, you cannot leave the backdoor installed as it turns off sound. So having a little more protection just might save your root in case you take an OTA and forget to install the backdoor.
Click to expand...
Click to collapse
beat me to it
its a completely stock gen2 rooted and cwm - you can use to unbrick, or go back to stock. only for HC bootloaders though.....
This worked to me
tu3218 said:
I'm running completely stock, no rom anything. Just flashed updates from users here to update me to the latest HC. I received the ICS update but pretty sure it won't work since I'm rooted and running CWM recovery. What do I need to do to install ICS? thanks
Click to expand...
Click to collapse
Well my friend, this worked to me... I hope this can help somebody else:
Original ROM: Acer A500 3.2.1 COM_GEN2 Rooted and with CWM using Timmy's method.
1) Go to play market and install Acer Recovery Installer.
2) Open Acer Recovery and verify with recovery do you have. In my case it was CWM recovery by thor2002ro 1.5
3) Install stock recovery. Make a backup of your old recovery when ask.
4) Factory reset: in my case, I made a backup of all my data and used Titanium to backup some apps. Then I harded reset my tab by turning it off and the combo pwd + vol(+) then lock-unlock switch 3 times until I saw "eraing user data" in the top-left corner.
5) turn on the tab and go to google play. Search for acer and install Update enhancement.
6) Go to settings-> about-> system update and aply the OTA update.
You will lost root, but everything should work fine.
To gain root access again, you can follow this thread -> http://forum.xda-developers.com/showthread.php?t=1546593
Now I have rooted stock ICS and I'm so happy
Hey great write up, will try this as soon as I'm off work. Anyway to confirm stock recovery is installed? Because I have done what you said(just the flash stock recovery part) an when I boot into recovery I just get a triangle an exclamation point. Not sure if thats right or not. But I will definitely give this a go since you were running exactly what I'm running now.
Sent from my Galaxy Nexus using XDA
3d0rr said:
Well my friend, this worked to me... I hope this can help somebody else:
Original ROM: Acer A500 3.2.1 COM_GEN2 Rooted and with CWM using Timmy's method...
...To gain root access again, you can follow this thread - ...xda-developers.com/showthread...
Now I have rooted stock ICS and I'm so happy
Click to expand...
Click to collapse
yay for 3d0rr you finally took the plunge congrats!!!!!
@tu3218
That download link is no longer available
instead download blackthund3r's one-click-root,
google "ICS Root for Windows"
At step 3 - After you have backed up -
Copy the uid.txt file from the backup folder - this holds your cpu id -
you're probably gonna need it at sum stage
I followed your instructions and it went perfect!!! Rocking ics now. Thanks for the help. First thing I notice, soooo much faster an full of butter.
Sent from my Galaxy Nexus using XDA
I just bought a brand new xt890. It has just arrived and I realised that it is running on Android 4.0.2 ICS. I got no idea what to start with first, root, upgrade to jellybean, recommendable firmwares or any other must get upgrades/modifications? What about back-up and stuff?
Update before rooting then custom rom
Sent from my GT-I8160 using xda app-developers app
ken_alpha24 said:
Update before rooting then custom rom
Sent from my GT-I8160 using xda app-developers app
Click to expand...
Click to collapse
Sorry to be asking this; but how do you proceed to Update? Is there things I need to take note off like what country the current firmware is from etc?
OTA
Sent from my GT-I8160 using xda app-developers app
textus said:
Sorry to be asking this; but how do you proceed to Update? Is there things I need to take note off like what country the current firmware is from etc?
Click to expand...
Click to collapse
To update your device to jb, make sure that the battery is at least 80% and that you're connected to a wlan.
Then go to settings -> about phone -> system updates. It will pop up a message that there is a OTA-update available. Click on download and after the download is finished on install. The phone flash the OTA automatically.
gesendet von meinem Motorola RAZR i rooted+unlocked
Thanks for the replies! I have updated it is now on 4.1.2. Is there different rooting instructions for different flex versions? How should I go about rooting next?
Also, when I first powered-on my device I did not get the android start screen and activation. Does that mean the phone is not brand new? How do I check if the phone is brand new? I ordered it online and it got shipped over, as far as I can tell there seem to be no scratches or scruff marks.
There is thanks button
Sent from my GT-I8160 using xda app-developers app
I've hit the thanks!
Is there different rooting instructions for different flex versions? How should I go about rooting next?
Also, when I first powered-on my device I did not get the android start screen and activation. Does that mean the phone is not brand new? How do I check if the phone is brand new? I ordered it online and it got shipped over, as far as I can tell there seem to be no scratches or scruff marks.
Hey,
Congratz on your new phone, you will like it as many of us do
The first thing to do is unlocking your phone. There is a great guide in the development section and general section somewhere.
After that install custom recovery and root your device.
No specifik notes are needed
Your phone is genuine, but if u want to know for sure just do a full wipe/factory reset in recovery. Most of the time u can't see it on the outside.
Sent from my XT890 using xda app-developers app
1) I think my phone is already unlocked. How do I then install custom recovery? Is that in the Google Play Store?
2) About rooting... is there different rooting instructions for different flex versions? How should I go about rooting?
3) If I do a full wipe/factory reset then how will I know if it was used before? Wouldn't the wipe make it look new?
4) If I am to do a factory reset will that be after the backup in the same app? Thanks!
textus said:
1) I think my phone is already unlocked. How do I then install custom recovery? Is that in the Google Play Store?
2) About rooting... is there different rooting instructions for different flex versions? How should I go about rooting?
3) If I do a full wipe/factory reset then how will I know if it was used before? Wouldn't the wipe make it look new?
4) If I am to do a factory reset will that be after the backup in the same app? Thanks!
Click to expand...
Click to collapse
1. You need to unlock the bootloader. If it's already unlocked then you see a warning while turning on the phone ( before red m logo appears). Otherwise there is a nice guide by mattlgroff how to unlock the bootloader
http://forum.xda-developers.com/showthread.php?t=1928551
Just read the OP and follow the steps.
For custom recovery have a look here -> http://forum.xda-developers.com/showthread.php?p=41479852
2. No. There is only one root-method if you're on jb. Just flash the zip from this thread -> http://forum.xda-developers.com/showthread.php?t=2123369
Or you flash a custom ROM (which are prerooted).
3. After a factory reset you will maybe (it does not have) see the first start dialogue.
4. Sorry don't know what you mean
gesendet von meinem Motorola RAZR i rooted+unlocked
4) I meant that I wasn't sure if the phone is completely brand new. Is there any way to check the software to see if it has been used before? Because if I do a factory wipe, then it will look like it is new when it might not be. Also when I switched on for the first time I was not asked to activate android and sign in.
5) After unlocking the bootloader and backing up and flashing a custom load, I can no longer have OTA updates rights? Also should I do a factory wipe before unlocking the bootloader or after? Thank you.
textus said:
4) I meant that I wasn't sure if the phone is completely brand new. Is there any way to check the software to see if it has been used before? Because if I do a factory wipe, then it will look like it is new when it might not be. Also when I switched on for the first time I was not asked to activate android and sign in.
5) After unlocking the bootloader and backing up and flashing a custom load, I can no longer have OTA updates rights? Also should I do a factory wipe before unlocking the bootloader or after? Thank you.
Click to expand...
Click to collapse
you can check on which google account you are loged in. But that is the only way i think.
You can get ota updates after unlocking, but it isnt a good idea to install them, it can brick your device maybe. But what does it matter all updates and firmwares are on this site and u can flash them with a recovery or use the fastboot files
textus said:
4) I meant that I wasn't sure if the phone is completely brand new. Is there any way to check the software to see if it has been used before? Because if I do a factory wipe, then it will look like it is new when it might not be. Also when I switched on for the first time I was not asked to activate android and sign in.
5) After unlocking the bootloader and backing up and flashing a custom load, I can no longer have OTA updates rights? Also should I do a factory wipe before unlocking the bootloader or after? Thank you.
Click to expand...
Click to collapse
It will automatically do a factory reset while unlocking bootloader.
gesendet von meinem Motorola RAZR i rooted+unlocked
I am at the installing recovery phase. What is the difference between TWRP, stock and CWM? Which one do I install?
Recovery's
Stock:
- only install signed zip files like ota packages. No custom allowed.
- wipe to factory
CWM:
- from koush, the maker of the base custom recovery's
- install custom zips. For root etc or other roms
- backup/restore your full rom
- wipe to factory and more
- USB Mount
- fix permissions of your ROM
- more things i forgot
TWRP:
- cwm as base, but sort of rewritten
- everything that cwm does
- multi zip install
- compres backups
- build in file manager
- touch friendly ui
It is what u like. A very stable cwm that does everything u need or twrp that does more than that, but not from CM or kouch.
Sent from my GT-P5110 using XDA Premium HD app
When I run CWM Recovery from the cmd prompt menu, it says device found then stock recovery complete. But I chose CWM, and even tried it twice. When I try TWRP it writes correctly and say TWRP is completed but when I chose CWM again, it gives the same problem saying stock recovery complete. Am I suppose to think that it is now CWM? When I went back to my phone it did not seem like there was a wipe to factory. How do I know if the custom recovery phase is successful?
I can't seem to enter bootloader now. I tried pressing power button and volume down at the same time and then releasing the power button when I feel a vibration but continuing to press the volume down. It just boots normally. I can't seem to root.
Also is it possible to root without a microSD card and SIM card?
I just used the recovery flasher to reboot to recovery and it now shows a green android lying down with its front panel open and a triangular red warning exclamation mark sign on it.
Edit: Sorry for being so spammy after rebooting several times (like 15 times) and tinkering around, I managed to root it. But I am not quite sure how to check if I am successful.
Is there any way to get rid/change the warning unlocked bootloader message in the beginning?
textus said:
I can't seem to enter bootloader now. I tried pressing power button and volume down at the same time and then releasing the power button when I feel a vibration but continuing to press the volume down. It just boots normally. I can't seem to root.
Also is it possible to root without a microSD card and SIM card?
I just used the recovery flasher to reboot to recovery and it now shows a green android lying down with its front panel open and a triangular red warning exclamation mark sign on it.
Edit: Sorry for being so spammy after rebooting several times (like 15 times) and tinkering around, I managed to root it. But I am not quite sure how to check if I am successful.
Is there any way to get rid/change the warning unlocked bootloader message in the beginning?
Click to expand...
Click to collapse
oke, i am at the point that i dont understand your story fully anymore.
First off, a picture of a green android lying down means u are in stock recovery.
But now i see your edit, i assume u have managed to flash CWM or TWRP on your device and got it booting in recovery. After that u installed the zip file with the root files in it. Something with root2... (I dont know the name, never used it) If u have done those things u can install titanium backup to see if u are rooted. On startup of the app it wil give u a popup with the message if u want to give this app root rights. If u see this u are rooted.
U cant get rid of the warning messages. if u want to know why, do a little search in i think the development section.
for booting to bootloader: hold power + volume down. release power just after the first shutdown of the device, so u have only the volume down button pressed when the device boots for the second time in a row
The first thing to do is a backup of u rom!!!! when u got for sure a custom recovery on your device!
I have the feeling that u dont have many experience in android and rooting and stuff. It is wise to do some studying about it
textus said:
I can't seem to enter bootloader now. I tried pressing power button and volume down at the same time and then releasing the power button when I feel a vibration but continuing to press the volume down. It just boots normally. I can't seem to root.
Also is it possible to root without a microSD card and SIM card?
I just used the recovery flasher to reboot to recovery and it now shows a green android lying down with its front panel open and a triangular red warning exclamation mark sign on it.
Edit: Sorry for being so spammy after rebooting several times (like 15 times) and tinkering around, I managed to root it. But I am not quite sure how to check if I am successful.
Is there any way to get rid/change the warning unlocked bootloader message in the beginning?
Click to expand...
Click to collapse
When you see the superuser app in appdrawer you're rooted. Or install a root app from Google play ( for example titanium backup)
Don't know of there is a way to remove unlocked bootloader warning. But IMO the warning message isn't a problem.
gesendet von meinem Motorola RAZR i rooted+unlocked