Related
hi guys,
i'm usually into stock ROMs and since i got my Iconia A501 i tried to find a 3.2 Stock ROM but rooted.
since i didn't find any i did one myself with the help of kekinash's thread.
[ROM] Rooted Stock HC 3.2 US Rom for CWM only (5-oct-11)
it's based on Acer_A501_1.309.02_4.031.24_COM_GEN1 and all i did was to add su and superuser.
Here's the link:
took it down to retest it myself from scratch
i'm not a very "linuxy" person and i'm not sure if i can help with any kind of problems.
Steps to install:
Update from 3.0.1
1. Root using Initial Root for A500
2. Install Acer Recovery Install from market
3. (optional) update recovery to 1.5 from Here which i got from thor2002ro thread Here.
4. Flash the ROM
5. Clear cache and davlik-cache
6. reboot and enjoy
if you're on Custom 3.2 go from step 3.
Thanks to:
- kekinash for your thread.
- thor2002ro for CWM recovery
I tried it but unfortunatly it doesn't work for me...
During the initial setup, the com.google.android.gsf.login process FC. It impossible to connect to the market for the same reason.
Superuser also FC... and many other apps!
I'll have to revert to stock rom.
do not work built-in 3g modem
3G was working on mine... but nearly nothing else. And as I did not have market access, it was difficult to even get a logcat.
i went from scratch to flash this.
reverted to 3.0.1, wipe, rooted, CWM, flashed the ROM and i got some FC in browser and clear.fi. not sure why. i wiped again and it was the same. i replaced the update script with the one i got in the superuser.zip and everything works now.
i really have no idea what happened but i'm sorry guys.
No problem!
Thank you for your work. Your next release will be easier to install anyway as CWM is installed on my a501 now.
I will give you some feedback when I have installed it. Not before tomorrow however...
you can try also this and see if it works.
after flashing the ROM
flash the superuser zip from CWM
I can flash this on my non-rooted stock ROM isn't it?
yeap. as long as you flash it from CWM.
Still does not work. Same problem!
I downgraded again, rooted, flashed, updates with superuser and still no luck.
I tried to make my own rooted rom but it doesn't flash. I don't know why...
this sucks then.
at least i tried. sorry man.
I finally managed to get the latest A501 rom with root. For this:
- I took the latest A501 ROM (Acer_A501_0.000.00_4.037.01_EMEA)
- I applied the steps to insert su into the update.zip (copy su, remove bootloader, edit update-script) directly in the zip using 7zip
- I downgraded, rooted, installes CWM, flashed my zip, wiped caches etc.
- I installed SuperUser from the market
That's it!
Now i reinstalled acer recovery to reinstall CWM (which was overwritten) and everything seems to be ok.
YES!
glad it worked for you.
vax said:
I finally managed to get the latest A501 rom with root. For this:
- I took the latest A501 ROM (Acer_A501_0.000.00_4.037.01_EMEA)
- I applied the steps to insert su into the update.zip (copy su, remove bootloader, edit update-script) directly in the zip using 7zip
- I downgraded, rooted, installes CWM, flashed my zip, wiped caches etc.
- I installed SuperUser from the market
That's it!
Now i reinstalled acer recovery to reinstall CWM (which was overwritten) and everything seems to be ok.
YES!
Click to expand...
Click to collapse
Can you post your rom vax?
I'll try to do it this evening... But I'm not used to this kind of post!
Can I upload it to megaupload and post the link or is there an "official" way of doing it?
i did the same thing for a different version.
the one i posted in the first post.
it's the official Acer_A501_1.309.02_4.031.24_COM_GEN1
and i added the update script from the superuser zip.
http://www.multiupload.com/HBNZ8UPMMD
My ROM is here : http://www.megaupload.com/?d=ZNZ1L5WB
Working for me... But don't forget to install SuperUser from the market!
mrjay said:
i did the same thing for a different version.
the one i posted in the first post.
it's the official Acer_A501_1.309.02_4.031.24_COM_GEN1
Click to expand...
Click to collapse
The difference with my rom are:
- the version of su - I used 3.0.3 because there seemed to be a problem with 3.0.7
- the updater-script - I started with the script from the ROM and added/deleted the relevant lines.
The updater script for A501 is more complex than the one for the A500 : there's a whole section about flashing the 3G firmware and the required libs.
The best would be to modify the script a little further to remove the flashing of the bootloader. It should not be very complicated but my first try did not work : CWM did not want to flaseh the resulting zip.
Any suggestion is welcome.
vax said:
The difference with my rom are:
- the version of su - I used 3.0.3 because there seemed to be a problem with 3.0.7
- the updater-script - I started with the script from the ROM and added/deleted the relevant lines.
The updater script for A501 is more complex than the one for the A500 : there's a whole section about flashing the 3G firmware and the required libs.
The best would be to modify the script a little further to remove the flashing of the bootloader. It should not be very complicated but my first try did not work : CWM did not want to flaseh the resulting zip.
Any suggestion is welcome.
Click to expand...
Click to collapse
Would you consider doing it for a GEN1 ROM? I tried another "stock" ROM on the forums and it isn't actually stock at all.
Why not... but it is quite simple. Did you try it yourself?
Any fully rooted GB rom before process the upgrade to Criskelo or Cassies ICS Rom please install SuperSU (Chainfire) first and those already done please click and update if available and somehow will update the binary , if successful, you can now flash the ICS and gain full root. otherwise partial root will most likley occur.
Once flashed the new ICS rom then update the the SuperSU again. Then you are done with fully rooted rom without issues.
I have tried twice and worked fine. it was very painful to have partial root and flashing CF root LQ3 with mobil odin did not resolve my partial root problem
I personally like Cassies rom and speedmod together. Working very well.
I Hope these help.
help!
husky168 said:
Any fully rooted GB rom before process the upgrade to Criskelo or Cassies ICS Rom please install SuperSU (Chainfire) first and those already done please click and update if available and somehow will update the binary , if successful, you can now flash the ICS and gain full root. otherwise partial root will most likley occur.
Once flashed the new ICS rom then update the the SuperSU again. Then you are done with fully rooted rom without issues.
I have tried twice and worked fine. it was very painful to have partial root and flashing CF root LQ3 with mobil odin did not resolve my partial root problem
I personally like Cassies rom and speedmod together. Working very well.
I Hope these help.
Click to expand...
Click to collapse
hi i have a similar problem: my original firmware was gingerbread 2.3.6 lc1 acording to dr. ketan guide fi only way to get root was a downgrade wich i did i flash trought odin the kj1 2.3.5 pre rooted rom everything went well got full root only problem was the null null keyboard besides that superuser updated binaries just fine...
The trouble started when i flashed abysskernel to wipe completely and flashes kingdroid v7 trought the aroma installer , make my choices and the kernel that i picked was speedmod k11-3, restarted... room boted just fine... but i realized superuser app was changed too super su , i open it, tried to update binaries but failed , tried to install new busybox trought ericcson app and failed also... so then i tried to flash trough mobile odin the cf kernel but that was a failure and it end with loosing root,,,
now im on kingdroid v7 supersu updated fine , but i still cant write or mount system files , still on speedmod k 11-3... will doing these step you wrote end in gaining full root again on the rom that i have?
thank u for ur answer!:fingers-crossed::fingers-crossed:
if you choose CF root in aroma while installation you boot up fully rooted,
once booted check your root situation, update binaries if need be , then you can change kernel to your preference
Solution
After update to ICS using mobile odin, if you find partially rooted, i think SuperSU busyboxinstaller,zip still work from recovery and will update inary and will get full root.
@Vailord
Wat you have need to use abyss once you are on safe GB ROM ?
There is no such thing as partial root...
it's like being married, you are married or you are not,
there is no such thing a being partially married
friedje said:
There is no such thing as partial root...
it's like being married, you are married or you are not,
there is no such thing a being partially married
Click to expand...
Click to collapse
agreed ,partial root is a myth ,the only thing causing the so called "partial root" is a corruption in the system partition causing it to refuse to mount\unmount
the solution is to flash a kernel that does not automatically mount system partition during recovery (like CM9 kernels) ,and then format system partition and then flash\ nandroid restore your ROM.
other than that partial root is a myth!
source: Entropy512
friedje said:
There is no such thing as partial root...
it's like being married, you are married or you are not,
there is no such thing a being partially married
Click to expand...
Click to collapse
It is like 'commited'
It allows you to use many appl like titanium but dont allow to mount system n that's why it is partially rooted.
Sent from my GT-N7000 using xda premium
true, being on a custom rom and saying we dont have root , its a self- contradictory statement
but the term is being used now for want of a better one......
Pretty much a redundant thread, seeing as everyone is doing it now. (But not before I ported the method from SGS II by Phil 3759 http://forum.xda-developers.com/member.php?u=4666971 )
Still makes interesting reading though.....
Thank you for your feedback and link here
But your post links are broken as you copy pasted and forum shortcuts them
So, original thread here:
http://forum.xda-developers.com/showthread.php?t=1746794
Also linked in my signature
Please, ask questions there, I will not monitor this thread for support, so cannot answer questions
Phil3759 said:
Thank you for your feedback and link here
But your post links are broken as you copy pasted and forum shortcuts them
So, original thread here:
http://forum.xda-developers.com/showthread.php?t=1746794
Also linked in my signature
Please, ask questions there, I will not monitor this thread for support, so cannot answer questions
Click to expand...
Click to collapse
Thank you - (fixed it)
shoey63 said:
Possibly the easiest method yet! (Unless you want to PC Odin custom kernel and use potentially dangerous Triangle away to reset counter and get rid of yellow triangle)
1) Download this file:- http://forum.xda-developers.com/attachment.php?attachmentid=1256643&d=1344771266 (comes from this thread - http://forum.xda-developers.com/showthread.php?t=1746794 Kudos to Phil 3759)
2) Copy to external SD card
3) Reboot into stock recovery and select "apply update from external storage"
4) Select "CWM_Root_SuperSU.0.94-Busybox.1.20.2-S2-signed.zip" and wait for Superuser and Busybox to install
5) Go back and reboot system.
Done! You now have fully rooted stock ICS (works on 4.04). Don't forget you are also on stock kernel so NO WIPING!!!
If u want custom kernel, use mobile Odin afterwards.
(BTW dont forget to open superSU after reboot to update binary)
Click to expand...
Click to collapse
That's not rooting - that's rooting AND installing busybox. Sometimes installing busybox can cause problems on a device.
To root, it's simple:
Go to Chainfire's SuperSU thread
Download the latest "CWM-flashable" version
Put on external SD
Flash from recovery
This WON'T also add busybox which can sometimes cause problems.
The reason this works: With ICS updates for I9100/N7000/I777/probably others, Samsung started permitting ZIPs signed with testkeys to be flashed from recovery.
This does not appear to work on newer devices - fails on N8000/N8013 for example.
Hello,
Does this mean if I do this to my note running N7000DDLR6 (don't if its required to mention this), I'll be able to under-clock it and remove system apps without anything more? and that It will be totally safe?
what precautions need to be taken while doing this and after that?
Regards
Sujai
sujaishukla said:
Hello,
Does this mean if I do this to my note running N7000DDLR6 (don't if its required to mention this), I'll be able to under-clock it and remove system apps without anything more? and that It will be totally safe?
what precautions need to be taken while doing this and after that?
Regards
Sujai
Click to expand...
Click to collapse
Ofcourse not, after rooting you are not safe anymore.
If you delete something vital your phone won't boot anymore.
So only root after reading and understanding what you are doing or intent to do...
Entropy512 said:
That's not rooting - that's rooting AND installing busybox. Sometimes installing busybox can cause problems on a device.
...
This WON'T also add busybox which can sometimes cause problems.
Click to expand...
Click to collapse
It can be true under some circumstances, but:
- Many good applications will not run without busybox installed in /system/xbin. Some can chose to go without them, others no. Until developers start including their busybox under their app folder (like Titanium Backup), there will be no other choice if you do need those applications
- Without busybox, you loose a lot of commands under the terminal console. End users do not care, until they need debugging...
- CWM recovery installs busybox in /sbin, it is even completely built into his recovery. So, every time you have cwm installed, you end up with busybox (Most if not all custom kernels/ROMs are concerned that way, include CF-Root kernels...)
- Installing busybox from a market installer is a real mess while installing it through a recovery script can be fully undone
Entropy512 said:
...
Click to expand...
Click to collapse
I'm sorry, but wasn't the CWM.zip the problem for fast few weeks? How come out of nowhere it's "OK" to install the flashable/temporary CMW and it is the Busybox causing the problem?
Please make it clear - is it the CMW.zip counting as "Unsafe" or it is something else?
Spo0f said:
I'm sorry, but wasn't the CWM.zip the problem for fast few weeks? How come out of nowhere it's "OK" to install the flashable/temporary CMW and it is the Busybox causing the problem?
Please make it clear - is it the CMW.zip counting as "Unsafe" or it is something else?
Click to expand...
Click to collapse
The root methods mentioned above can be done from stock recovery skipping the cwm temporary step
Busybox can cause issues with some applications that rely on a generic busybox copy under /system/xbin
This is caused by the fact that each busybox build can have different valid commands. The application cannot know if the commands it needs are supported unless it is bundled with its own busybox copy. It will rely on the compiler of busybox to implement the commands.
Until now, I never encountered such problems with last busybox, but, it doesn't mean one of your apps will never behave strangely...
This is a problem related to the application its self, not busybox specifically
So to summarize this in clear words for note users it should be:
-Note users can easily get root only by flashing supersu or superuser (CWM flashable zips) through stock rom recovery directly,no need for CWM.ZIP at all.
-Note users can also get root + busybox by flashing CWM.ZIP old safe non touch v 4.x through stock recovery first,then to flash supersu/superuser+busybox zip through the temp CWM 4.
Am i right guys? plz do confirm...
Also what about wiping now through temp CWM4 with ICS rooted stock kernel? is it safe now??
↖(^▽^)↗ Sent from Rego Galaxy Note ↖(^▽^)↗
Entropy512 said:
That's not rooting - that's rooting AND installing busybox....
Click to expand...
Click to collapse
OK thanks, forgot to mention that, I'll amend OP
Already answered
eng.rego said:
So to summarize this in clear words for note users it should be:
-Note users can easily get root only by flashing supersu or superuser (CWM flashable zips) through stock rom recovery directly,no need for CWM.ZIP at all.
-Note users can also get root + busybox by flashing CWM.ZIP old safe non touch v 4.x through stock recovery first,then to flash supersu/superuser+busybox zip through the temp CWM 4.
Am i right guys? plz do confirm...
Also what about wiping now through temp CWM4 with ICS rooted stock kernel? is it safe now??
↖(^▽^)↗ Sent from Rego Galaxy Note ↖(^▽^)↗
Click to expand...
Click to collapse
All is ok, except wipe
I cannot certify it is safe. Entropy512 which is involved in CM dev said it is safe for CWM4. I never tested, cannot confirm
Also, CWM6 is still unknown state on stock kernel, until some dev can confirm it
eng.rego said:
So to summarize this in clear words for note users it should be:
-Note users can easily get root only by flashing supersu or superuser (CWM flashable zips) through stock rom recovery directly,no need for CWM.ZIP at all.
Click to expand...
Click to collapse
Correct.
eng.rego said:
-Note users can also get root + busybox by flashing CWM.ZIP old safe non touch v 4.x through stock recovery first,then to flash supersu/superuser+busybox zip through the temp CWM 4.
Click to expand...
Click to collapse
Haven't tried it that way because it involves an extra unnecessary flash. Anyway best to steer clear of any CWM.zip. I bricked my note wiping on touch version. Why use it if u don't have too?
but ultimately we have to used odin to flash a safe kernel after this proceedure.
can we use this to 'cure' the 'partial root' phenomenon many face after flashing even recent ics custom roms ?
i admit installing busybox from market successfully can be a real pain .....
we need busybox for many things like supercharger script etc etc
some apps wont work if you dont have the upgraded version of bb
Some like to stay on stock Ics kernel because of stability. (only unsafe if wipes are performed on them) If u want custom kernel then obviously mobile odin pro/lite is the way to go. At least this way u dont raise flash counter and then have to use potentially dangerous triangle away app. As far as "partial root" goes - not sure. It will install SuperSU. Just open it to update binary and uninstall any other superuser apps that are already on phone
Sent from my GT-N7000 using xda app-developers app
Let me get this straight:
The "official" root thread for Note [02Feb12]How to Root/Unroot Samsung Galaxy Note + CWM says this:
Using CWM.zip (temporary/Touch recovery)method to root is said to be unsafe by entropy, and till safe release don't use it
Read This http://forum.xda-developers.com/show....php?t=1810954
Click to expand...
Click to collapse
Now there is new release which is CWM 6.
Is the old method safe with the new release?
No need for ANY CWM.zip (safe or not). Just flash file in OP on stock kernel recovery from external sd card. Job done .
Sent from my GT-N7000 using xda app-developers app
Yes... Can confirm this has worked for me... Followed instructions in OP, and copied the Uninstaller to my SD Card in the even that I need to return the phone... Flashed in Stock Recovery, rooted and done..
Thanks a million for this...:good:
New Procedure updating to My this thread in 1 hr ( I am working on it)
http://forum.xda-developers.com/showthread.php?t=1329360
new method based on What Entropy have guided us few post back
No need to use CWM at all
No need to flash SUperSU busybox installer (as Entropy said this can cause problem)
Hello everyone,
I'm kind of new here in the forum but I have been around as a guest for a while. I own a Tab 10.1 3G and followed the instructions in the forum to update my tab to 4.0.4 XXLQ8 successfully. I'm so thankful to you guys.
But when I tried to gain root access after the update. It's unrooted again. It took me long enough with a little help from my friend to be able to flash CWM into the tab to be able install .zip files in the /sdcard again. But something is still wrong. With all the files I found in the forum, none has successfully given a proper root access (even though I followed the instructions exactly and did all the things needed). The thread is here:
http://forum.xda-developers.com/showthread.php?t=1807219
I have attached with this post 3 screenshots just to try to tell you what is going on.
1st image is BusyBox: It says my device has Root. And I have SuperUser installed in the drawer.
2nd image is SuperUser Fixer Update blah blah blah saying gaining root access failed.
3rd image is SDMaid telling me my device doesn't have root access.
So I can safely concluded that it is NOT ROOTED. BUT WHY? I did correctly everything.
I would like to know your opinion about this matter
Thank you so much
This is what I would say the best thing to do is.
1. Uninstall all su & busybox apps & preferably factory reset.
2. If your CWM version 6.x you can ignore this. Otherwise download the newest recovery for your tab from droidbasement and install using Odin. This is to make sure you don't accidentally invoke the "super bug" and brick your tablet
3. Make sure to download the zip in the sticky by Sockmonkey. Extract it and put the small flashable zip on to your tab
4. Install the root zip through Cwm. Now test by checking an app that needs root, like Titanium Backup.
To be honest it's probably easiest that if you want a completely stock rom with root just install something like tasks or toldos instead.
Sent from my GT-P7510 using XDA Premium HD app
Problem solved.
scaryshark said:
This is what I would say the best thing to do is.
1. Uninstall all su & busybox apps & preferably factory reset.
2. If your CWM version 6.x you can ignore this. Otherwise download the newest recovery for your tab from droidbasement and install using Odin. This is to make sure you don't accidentally invoke the "super bug" and brick your tablet
3. Make sure to download the zip in the sticky by Sockmonkey. Extract it and put the small flashable zip on to your tab
4. Install the root zip through Cwm. Now test by checking an app that needs root, like Titanium Backup.
To be honest it's probably easiest that if you want a completely stock rom with root just install something like tasks or toldos instead.
Sent from my GT-P7510 using XDA Premium HD app
Click to expand...
Click to collapse
I found a way, finally.
This is a video instructions how to root galaxy tab 10.1 (4.0.4)
Youtube video name: Hi-Tik How TO : Root GALAXY Tab 10.1 (Android 4.0.4)
It has been there since August 23rd but I don't know how come I couldn't find it earlier. Maybe I search the wrong keywords.
Anyway, the correct Root .zip file in there really did solve the problem and now I'm running SuperSU with root access
for some reason as of now on verizon note 3 there seems to be no fix for the supersu not updating binary on the new kitkat 4.4.2 im rooted using Towelroot i let it update the binary once and i never opened it again to avoid it asking me to update again then failing ... so to avoid uninstall and reinstall i just let it do its magic once and never touch it again... it will update the first run but once you reboot .. youre f you also want to make sure you delete the file su in system/xbin/su then uninstall and install fresh to get this to update you binary .. but you can never open it again or it will ask to update and fail ... however all apps asking to grant permisson will be granted so apon screen pop up and your prompt to allow ....
Is there any update or possible way to obtain update of binary successfully without having to worry about being asked to update again once you reopen SuperSu ..
if you have safe strap installed, you can download the Su zip file and flash in recovery. you can find it in the Android thread, just use the search. I have done it this way and works like a charm.
phillymade said:
if you have safe strap installed, you can download the Su zip file and flash in recovery. you can find it in the Android thread, just use the search. I have done it this way and works like a charm.
Click to expand...
Click to collapse
im currently running
Safestrap 3.72 SuperSu 2.02 does this matter ? i ask because i had already took the apk su file out of the zip you mention prior and installed via sd card before even having safestrap installed and the su file did the same .. so flashing it will make it work plus do notice there is an update for SuperSu on his site [chainfire}
phillymade said:
if you have safe strap installed, you can download the Su zip file and flash in recovery. you can find it in the Android thread, just use the search. I have done it this way and works like a charm.
Click to expand...
Click to collapse
I just noticed that apon installikng safestrap after having these issues i can actually open SuperSU with out it asking me to update again so i didnt have to flash the zip just install safestrap the proper one for kit kat Hashcode/note3/hltevzw/safestrap/Safestrap-HLTE-3.72-kk-B01.apk search thanks
sure. but be advised, there is an updated version of SS. HLTE-3.72-kkB04. it's in the SS OP. Look for the Crack flasher link. this version has rom slot support.
phillymade said:
sure. but be advised, there is an updated version of SS. HLTE-3.72-kkB04. it's in the SS OP. Look for the Crack flasher link. this version has rom slot support.
Click to expand...
Click to collapse
yes i read about that earlier where you have to use the stock slot to use a rom besides the slot you use for the backup .. so this Su youre talking about fixes those issues .... can you tell me to find it because ive searched Google already and keep coming up empty for that file ... more over looking into roms im seeing ill have to flash a stock rom that will install bootlaoders that i will need before flashing any custom roms ..is this about right ? thanking you in advance @phillymade
for Flashing custom Rom follow this OP, http://forum.xda-developers.com/showthread.php?t=2787627 and you can flash a custom Rom in place of the stock rooted. as for the Su, are you looking for the super user zip or the updated safe strap. I'm a bit confused by the post as to what you are asking
phillymade said:
for Flashing custom Rom follow this OP, http://forum.xda-developers.com/showthread.php?t=2787627 and you can flash a custom Rom in place of the stock rooted. as for the Su, are you looking for the super user zip or the updated safe strap. I'm a bit confused by the post as to what you are asking
Click to expand...
Click to collapse
i noticed after yes the updated safestrap with the slots fixed
I RE read your OP. you are stock root. Did you install busy box? If not, download it from the play store look for busy box installer. this will help with any issues with su and such
i only see this on crackflasher but in thrown off as i dont know what the NC2 is about Safestrap-HLTEVZW-NC2-3.75-B04.apk | hltevzw | Hashcode0f
phillymade said:
I RE read your OP. you are stock root. Did you install busy box? If not, download it from the play store look for busy box installer. this will help with any issues with su and such
Click to expand...
Click to collapse
when you told me about flashing it ., i said let me check the Su since i had previously installed it before safestrap but some how installing safestrap fixed my issue of Su asking to update binary and failing apon reboot so now i just want to basically update safestrap and install a romm thats stable with almost no flaws