Hi guys,
Followed the steps in forum.xda-developers.com/showthread.php?t=736271 to root my N1. All worked ok, and had root access. I proceeded to flash a custom recovery and received an error "mtd: not writing bad block at 0x000xxxxx". I redownloaded the recovery again, with the same issue. I rebooted and found that the recovery had loaded, however, after another reboot, was no longer the Amon recovery, but stock?
Second question is how can i unroot and go back to full stock? Tried a method found in another threat but was receiving a "verification failed" error - i assume because the version being flashed was too old for the FRF91 i had.
Any help is appreciated
Update
Hi ended up downloading EPE76 and renaming it to passimg, and letting recovery find/run it to unroot.
I then upgraded to FRF85B by downloading and renaming it to update.zip and running it from recovery.
And finally, i downloaded FRF91 and renamed to update.zip and ran it, again from recovery console, to get back to where i was before the hassles.
Not sure if this was the correct way to unroot, but my radio, rom version etc all matches before i started the rooting. The recovery flash never stuck (even though i did it in manual mode), and so it seems i am stock again.
Any advice on the issues in my first post?
best way to root
http://forum.xda-developers.com/showthread.php?t=710842
had same issue while rooting my latest nexus one, not exactly sure of how it happend but I just did same process and it worked fine. Command error or adb push into wrong place. I just cut and paste commands and it worked out fine.
First nexus one I unlocked bootloader and ended up selling it, thinking of switching to iphone 4, but decided to stay with n1.
Update
Hi there...
The method i used is a copy of that but without the battery mod.
Didn't really think having to trim the battery pack was a great idea...
Update
osugsxr said:
had same issue while rooting my latest nexus one, not exactly sure of how it happend but I just did same process and it worked fine. Command error or adb push into wrong place. I just cut and paste commands and it worked out fine.
First nexus one I unlocked bootloader and ended up selling it, thinking of switching to iphone 4, but decided to stay with n1.
Click to expand...
Click to collapse
Yeah starting to wonder if i should even bother trying again... just not sure if CM will be worth the effort. Was more doing it to check it out, rather than a need.
If i can find out how to unroot properly (i may have done it correctly above), i may give it another go. Just felt my unroot effort was trial and error and not really game to try it again and stuff it completely.
Related
Here's the story:
A while back, I rooted my Nexus One without unlocking using the bait and switch method, and had been using various custom ROMs.
Recently, the power button hasn't been working well, so I called HTC to get a swap. Obviously, before sending my phone back, I need to unroot it.
I tried to restore my phone using the method in the XDA guides, but it hung on each step, and it didn't actually do anything. So, I flashed the non-rooted stock ERE27 through ROM Manager (this, I suspect was a huge mistake.)
Now, I have an rooted phone, that fails on any update attempt and so is stuck on 2.1, and worse, Clockwork Recovery is still on there. I've tried to unroot my phone again using both the bait and switch method, and the freenexus method, but both have run into errors. I've also tried installing Universal Androot and clicking Unroot, but it just tells me my phone isn't rooted.
So, I can't root my phone to attempt to flash the recovery, and I can't find a way to remove Clockwork Recovery, but I need to send this phone back to HTC within the next 7 days, or else I'm gonna be out $530.
Any ideas?
First: hate to be a douche, but someone's gotta say it: this is the wrong subforum for a question thread. Take a quick glance over the rules stickied at the top of the forum. There's a Q&A forum for things like this.
Second: HTC has typically honored the warranty for known hardware problems (of which the power button is probably the biggest) even for unlocked/rooted devices. They find for me, no problems. So relax.
Last, try using ClockworkMod recovery to flash CM 6 stable, then from that ROM, try flashing back to stock recovery. After that you should be able to flash a stock OTA ROM. You can't change recovery without root access, which you can't get on a stock ROM. So you have to change recovery first. And on your new phone, you should really just fastboot OEM unlock. Trying to deceive HTC makes them not want to give us this option anymore.
Yup no worries I had to send mine in because the trackball got stuck and they got it under warranty ... I had my phone running a custom recovery and rom and they didn't even ask about it.
I recently received a Nexus One from a friend. The bootloader is unlocked and I believe it is rooted. When I got it it kept generating some sort of process error and the phone randomly rebooted. I tried reinstalling a ROM and then the phone just sat with the "X" boot screen. 3 days later and I managed to find a ROM that makes the phone usable (22607-ERD79-update-nexusone-stock-signed). The phone ran fine with that but it is now 2 generations old and I want to update to Gingerbread. Every attempt I have made has ended with the phone just sitting there with the "X" screen after 20 mins. Clearly the updates aren't working. I'm completely confused by all of this.
I'm coming from an iPhone that I was able to jailbreak and hack with no problems. I also have experience with WinMo phones. Never had these issues.
Most of the updates seemed to install correctly. The log screen completes all the steps and ends with "Install from sdcard complete."
Running RA-nexus-v1.5.3
Please help me with this. I want Gingerbread!
First, what versions of Radio and HBoot you use?
How would I tell? Where would I find this info?
Sounds like you are not wiping data.
Whenever you change to a different rom (other than upgrading the same rom) you need to wipe the data partition, otherwise you could get bootloops, stuck at X, unstable systems, etc.
Sometimes not wiping works out okay, but in this case it sounds like it didn't.
I have tried the wiping. As I understand it, I should wipe before flashing the new ROM?
THe baseband is 32.41.00.32U_5.08.00.04
Found them!
HBOOT = 0.35.0017
radio = 5.08.00.04
so I've now upgrade to recovery-RA-supersonic-v2.3.img
supersonic is the wrong phone.....
OK. What is the correct one?
So apparently I was provided the wrong recovery. I did a little research and believe I have the correct one now. recovery-RA-passion-v2.2.1.img
Now should it work...
Still not working. I have no idea what I'm doing wrong. This is really getting under my skin.
Can anyone offer any more info on this? Maybe walk me through it. I have to believe that I am doing something wrong as the phone seems to work otherwise.
Return to a completely stock image. Follow the unroot/restore method from the wiki, using passimg and the FRG33 image...
http://forum.xda-developers.com/wiki/index.php?title=Nexus_One/Guides_%26_Tutorials#Unroot_.2F_Restore_your_Nexus
Sent from my Nexus One using XDA App
OP I had a similar issue. Wiped, installed, wiped, installed. No ROM was stable. It constantly rebooted.
Luckily it was under warranty and HTC replaced it. The new device is rock solid but has burn-in (Pandora buttons always visible and I don't even have Pandora installed).
They are replacing this one as well.
Hope it's under warranty. If so, HTC is great, even with an unlocked bootloader.
I'm starting a new thread on my exploits with my Captivate as I've been trying to get it to work well since updating to the official Samsung Froyo release when it came out (actually since getting the phone last fall). Any tips to get me past the problems that I'm having would be appreciated. I've tried searching the forums and googling the problems I've had, but this has been tedious to say the least, and really hasn't gotten me any further.
When I originally got my Captivate, I tried connecting it to Samsung Kies and I was never able to get Kies to actually recognize the phone and let me use it to move media about and such, so I gave that up. When the Froyo update was released, I installed it per the instructions and kept hitting a dead end until I uninstalled IE9 (I think it was the RC at the time). Then I was able to update my phone, but the update failed and I had to use some sort of recovery console within the Kies update (I'm sorry I don't remember the exact details). This updated my phone to Froyo, at least according to the Settings:About Phone (Firmware version 2.2 Build number FROYO.UCKB1). However, since then the phone has actually seemed slower than before the update and I thought the new JIT was supposed to make it faster. It often freezes on me requiring me to remove the battery to restart it. Also, the data connection will fail at times (the "3G" icon disappears or only shows uploading data despite having 5 bars) and when I reboot the phone I will have voicemail waiting despite having no missed calls. Anyway, I decided I've had enough of this and I wanted to root the phone and install Cyanogenmod. (I'd been thinking of this anyway.)
I tried using the 1-click root as described http://forum.xda-developers.com/showthread.php?t=739304. This failed as when I clicked on "reinstall packages", it says "E:signature verification failed Installation aborted."
I searched around for this and found information on getting an unsigned update.zip which was supposed to prevent this error. (http://forum.xda-developers.com/showthread.php?t=909213) However, I was not able to follow the mount instructions through the terminal emulator as I got this error for that command: "mount: Operation not permitted". My prompt is $ and I'm told it is supposed to be #. I found instructions that this is supposed to change by typing su for superuser, however when I do that it says, "su: not found".
I then found this thread: http://forum.xda-developers.com/showthread.php?p=8985854 which I have been trying to follow the step-by-step to root Captivate posted by clawsthatscratch. (I have an AT&T Captivate and they seem to be referring to Rogers Captivate, but I thought it should work anyway.) These instructions say to open a command prompt from the tools directory, but it seems that you actually have to open from platform-tools instead as the ADB had changed locations. I went through this step-by-step to the command "./rageagainstthecage-arm5.bin" This did not "kick my out of adb" the first time that I did it, but I've done it again now while typing this post and it seems to be going further and I'm actually seeing a # prompt instead of just the $ prompt.
----
OK. I think I may have root access. Everything worked up until the "no startup sounds" and "remove bloat" steps. When I try to run these commands, I get a "Read-only file system" error. I'm going to try to install Cyanogen. I'll repost when I see how that goes. Please (oh please, oh please) give me whatever help you can as to why I'm having so many problems running the simpler methods and even the step-by-step method.
From not being able to figure or how to change tot 3e recovery to flashing cm7? Take a step back and think about this
Sent from my SGH-I897 using XDA Premium App
Did you try super one click? It worked fine for me, as well as enabling non market apps..which also worked, as I was able to download the amazon app market and install apps from there
You need to flash back to the stock 2.1 build using odin one click then root then flash your rom. Please use a guide your first time so you don't brick it.
The 3e security found on the 2.2 build gives the failed error so flashing back to stock fixes that by changing back to the old security.
Sent from my Samsung-SGH-I897 w/ Firefly 2.7
Use super one click or something to get root, then download rom manager from market, download and install clockwork recovery from within rom manager. This will give u the 2e recovery u need. if u cant get into 2e from within rom manager, turn off ur phone, and instead of using the 3 button combo (vol up and down, and power), use 4 button - vol up and down, home button (softkey) and power button. This should put u into 2e recovery, thus eliminating your signature validation problems. Then flash away at will!
Hope this helps.
Sent from my SAMSUNG-SGH-I897 phoenix ultimate - onix 2.0.1 oc 1.6
I have an HTC Hero CDMA for Alltel. I have been on a quest to make it faster by overclocking or installing a new rom. Upon receiving the phone it would not work with MMS messages so Alltel had me flash the rom using HTC sync. The software came from here: http://software.alltel.com/software.aspx?deviceID=103&platformID=22. This updates the kernel to 2.41.556.1.
Since then I tried rooting it and had many difficulties. I tried 3 different rooting strategies before (semi?-) sucessfully running this one click root apk: http://forum.xda-developers.com/showthread.php?t=743289. It installs Darchstars Recovery.
I have since tried flashing 4 different roms such as cyangenmod 6.1 and 7.06. ALL of them bootloop for hours but recovery always restores the phone successfully.
None of this was working so I re rooted it again (never unrooted it, possibly a problem) following this guide: http://forum.cyanogenmod.com/topic/20126-cyanogenmod-7-for-the-htc-hero-cdma-v703-5-may-2011/. I installed the Andoid SDK on my computer and successfully ran all the needed commands to root my phone. Now instead of Darchstars Recovery it has ClockWorkMod 2.5.07. I tried installing all of the roms I tried before but again to no success.
At this point I'm desperate to just overclock it at least. I read around that people were getting into the mid 700 mhz ranges and I wanted that. So instead of a new rom with a newer Android version I wanted- I flashed a new overclock kernel onto the standard Alltel rom I updated my phone with. I used Zen Kernel found here: http://forum.xda-developers.com/showthread.php?t=750170. Upon flashing the new kernel the phone went into bootloop and exhibited the same behavior as the other roms did. I recovered and set back to normal. I tried the Zenkernal flash one more time but used StockVoltage Overclocked Kernel found on the same post. This time it worked!
With the new overclock kernel 2.62.29 I installed setcpu and overclocked. However I can only hit 672mhz with it - Not what I wanted. Also with the new kernel SuperUser permissions have to be set every time. It will not remember that I previously gave permission. Additionally RomManager 4.3.3 seemingly doesn't think my phone is rooted. It fails if I try to install a rom or new recovery through it citing that it can't get superuser permission. Even though I give it permission.
The thing I noticed that is messed up and possibly causing things to become awry is that in ClockWorkRecovery when I try to clear the Dalvik Cache I get a E:Can't Mount /Dev/block/mmcblk0p2 (file Exists) message. I'm thinking this may be causing the problems and it may have been messed up by my prior attempts to root it. Can anyone shed some light on this?
Since I installed the new updated Alltel rom 2.41.556.1. I have been reading that with Sprint the newer rom breaks the ability to root the phone using many methods. I'm starting to believe this may be the case with the newer Alltel rom as well.
From my understanding to fix my problem I need to restore everything to stock, find a way to unroot, downgrade Alltel's rom, root on the downgraded rom, flash a recovery, flash a new rom? I am unclear on how to do this and it's where I need some help.
Basically my current plan (At work can't do it now) is to:
1. Install Darchstars recovery instead of ClockWorkMods because Darchstars recovery has my first original Nandroid backup to undue everything else I've done. Clockwork and Darchstar appear not to be able to restore from one others backup Nandroid, is that correct?
2. To downgrade I was going to follow these instructions: http://tech-n-life.com/index.php/2010/01/support-sunday-how-to-un-root-your-htc-hero/. The problem I see with it is finding an original Alltel RUU as opposed to Sprints.
3. Root and install new rom.
Does anyone have suggestions or a better way to approach this in finding a way to flash a new rom and actually have it work?
I'm not on Alltel, but you're definitely on the right track to resolve the issue.
I know there's a ruu for the Alltel around here. I remember reading it a while back. After PT I'm come back and help locate it with you.
And keep up the excellent investigation! I applaud your digging efforts. First round is on me if I see you at the bar.
I've made much progress in the way of getting it rooted. Just about everything on the internet WILL NOT WORK to root it. Most of it is out of date. I have finally rooted it and have made it stay rooted. I found out that the device would unroot itself after rebooting it - must be something with the newer Alltel version 2.41 idk.
I used this post and program to root it: forums.regawmod.com/showthread.php?tid=6
The above attempt has flaws however. It makes the recovery inoperable. To fix this I ran the commands below in ADB. These commands are the only way to get a recovery on the phone properly. I have found every guide on the net is outdated or incomplete; after lots or trial and error I developed this. Flash_image and a recovery image are needed.
Code:
cd /d E:\HTC Hero\rooting
adb push recovery-RA-heroc-v1.6.2.img /sdcard/recovery-RA-heroc-v1.6.2.img
adb push flash_image /sdcard/flash_image
adb shell
su
mount -o remount,exec /dev/block//vold/179:1 /sdcard
cd /sdcard/
./flash_image recovery /sdcard/recovery-RA-heroc-v1.6.2.img
reboot recovery
--------or-------
adb push recovery-clockwork-2.5.0.7-heroc.img /sdcard/recovery-clockwork-2.5.0.7-heroc.img
./flash_image recovery /sdcard/recovery-clockwork-2.5.0.7-heroc.img
At this point the WiFi is broken and unable to start because of the root.
I flashed zenkernal again and, like before, the one with perflock disabled will not boot and the one with perflock on works - this kernel corrected the wifi issue. forum.xda-developers.com/showthread.php?t=750170
I'm pretty much back to where I started. I have to grant super user access constantly again. However I found this can be fixed by flashing "su-2.3.6.1-ef-signed.zip" via recovery mode.
Because I can't get a new rom to work I have pretty much altered the stock rom in a way that suits me. I have it overclocked decently (wished for more) at 673, it's 100% stable, and I used Fresh Kitchen 3.0.0.1 to delete all the crap such as Amazon MP3 that was on my phone.
Support for the Alltel HTC Hero is very lacking around the net. Strategies that work on Sprint and other phones don't work on this one. Also most strategies are very outdated. It seems I missed the bus by buying this phone at this point in time - but I did get a really good deal on it.
EDIT: I have constantly read about s-on and s-off but no one ever actually said what it was or what it had to do with anything. I didn't think it was important. I just researched it and mines on still. I'm gonna give everything a try again once I get it off.
Edit2: S is off via flashing unrevoked-forever.zip in recovery. It made no difference for booting other roms. The only apparent thing that I noticed is that the E:Can't Mount /Dev/block/mmcblk0p2 (file Exists) message is gone - it may have been fixed a while ago and I just never noticed.
Currently the phones set to S-off
adb says the phone is rooted via the # symbol
It's running Clockwork2.5.0.7
It's running ZenKernel-HTC-08122010 perf lock 2.6.29
Alltel Software version 2.41.556.1
Super User package su-2.3.6.1-ef-signed.zip
Overclocked to 672mhz
However RomManager says, "An error occured while attempting to run privileged commands!" and SystemTuner claims my phone is not rooted.
I don't know what to do with this phone.....
Hmm, that doesn't sound good. I recently had trouble with changing VM and busy box, and managed to destroy my phones driver's. I couldn't connect to Wi-Fi(MAC address was <UNKNOWN>), Bluetooth(Address was <UNKNOWN>, or mobile(My phone number was missing). After factory reset, I took it to Alltel and they said they would put an update on it that would fix many problems. It now works, but lags more, it doesn't crash as much, seems to run warmer, and the battery doesn't last as long. I was wondering if it was just a minor overclocking mod and a few bug fixes, but if root doesn't work, that may be a problem for me.
Flash that zenkernel I mentioned. It seems to somehow be better with battery life.
I have no way to prove this but I work from 7am till 5:30pm. Before the zenkernel battery life would be around 70% after work. The other day it was at a low 80% after the kernel update. It may have been affected by outside temperatures as well I have no idea but it does appear to have better battery life.
DerekZ10 said:
Flash that zenkernel I mentioned. It seems to somehow be better with battery life.
I have no way to prove this but I work from 7am till 5:30pm. Before the zenkernel battery life would be around 70% after work. The other day it was at a low 80% after the kernel update. It may have been affected by outside temperatures as well I have no idea but it does appear to have better battery life.
Click to expand...
Click to collapse
this is the same thing you did from the alltel site but there is a flashable zip for the update you used.
http://forum.xda-developers.com/showthread.php?t=894925
or this one
http://pcdphones.com/our-devices/products/75-adr6250al/downloads/42
maybe a bad download
for root look here
http://forum.xda-developers.com/showthread.php?t=710483
i would try one of dac's kernels here
http://forum.xda-developers.com/showthread.php?t=756774
you can try flashing this alltel rom i was messing with.
http://dev-host.org/?op=my_files&fld_id=24
this is all ready rooted and the updated one you flashed.
DerekZ10 said:
I have an HTC Hero CDMA for Alltel. I have been on a quest to make it faster by overclocking or installing a new rom. Upon receiving the phone it would not work with MMS messages so Alltel had me flash the rom using HTC sync. The software came from here: http://software.alltel.com/software.aspx?deviceID=103&platformID=22. This updates the kernel to 2.41.556.1.
Since then I tried rooting it and had many difficulties. I tried 3 different rooting strategies before (semi?-) sucessfully running this one click root apk: http://forum.xda-developers.com/showthread.php?t=743289. It installs Darchstars Recovery.
I have since tried flashing 4 different roms such as cyangenmod 6.1 and 7.06. ALL of them bootloop for hours but recovery always restores the phone successfully.
None of this was working so I re rooted it again (never unrooted it, possibly a problem) following this guide: http://forum.cyanogenmod.com/topic/20126-cyanogenmod-7-for-the-htc-hero-cdma-v703-5-may-2011/. I installed the Andoid SDK on my computer and successfully ran all the needed commands to root my phone. Now instead of Darchstars Recovery it has ClockWorkMod 2.5.07. I tried installing all of the roms I tried before but again to no success.
At this point I'm desperate to just overclock it at least. I read around that people were getting into the mid 700 mhz ranges and I wanted that. So instead of a new rom with a newer Android version I wanted- I flashed a new overclock kernel onto the standard Alltel rom I updated my phone with. I used Zen Kernel found here: http://forum.xda-developers.com/showthread.php?t=750170. Upon flashing the new kernel the phone went into bootloop and exhibited the same behavior as the other roms did. I recovered and set back to normal. I tried the Zenkernal flash one more time but used StockVoltage Overclocked Kernel found on the same post. This time it worked!
With the new overclock kernel 2.62.29 I installed setcpu and overclocked. However I can only hit 672mhz with it - Not what I wanted. Also with the new kernel SuperUser permissions have to be set every time. It will not remember that I previously gave permission. Additionally RomManager 4.3.3 seemingly doesn't think my phone is rooted. It fails if I try to install a rom or new recovery through it citing that it can't get superuser permission. Even though I give it permission.
The thing I noticed that is messed up and possibly causing things to become awry is that in ClockWorkRecovery when I try to clear the Dalvik Cache I get a E:Can't Mount /Dev/block/mmcblk0p2 (file Exists) message. I'm thinking this may be causing the problems and it may have been messed up by my prior attempts to root it. Can anyone shed some light on this?
Since I installed the new updated Alltel rom 2.41.556.1. I have been reading that with Sprint the newer rom breaks the ability to root the phone using many methods. I'm starting to believe this may be the case with the newer Alltel rom as well.
From my understanding to fix my problem I need to restore everything to stock, find a way to unroot, downgrade Alltel's rom, root on the downgraded rom, flash a recovery, flash a new rom? I am unclear on how to do this and it's where I need some help.
Basically my current plan (At work can't do it now) is to:
1. Install Darchstars recovery instead of ClockWorkMods because Darchstars recovery has my first original Nandroid backup to undue everything else I've done. Clockwork and Darchstar appear not to be able to restore from one others backup Nandroid, is that correct?
2. To downgrade I was going to follow these instructions: http://tech-n-life.com/index.php/2010/01/support-sunday-how-to-un-root-your-htc-hero/. The problem I see with it is finding an original Alltel RUU as opposed to Sprints.
3. Root and install new rom.
Does anyone have suggestions or a better way to approach this in finding a way to flash a new rom and actually have it work?
Click to expand...
Click to collapse
Any of these should work :: http://www.pcdphones.com/our-devices/support/adr6250update but u should try the Bittersweet ROM (http://forum.xda-developers.com/showthread.php?t=658755) And i use the Kernel from here: (http://forum.xda-developers.com/showthread.php?t=1110418) AND if that dont work try dropping it and see if that helps (hasn't for me ... but does relieve some stress)
DerekZ10 said:
Flash that zenkernel I mentioned. It seems to somehow be better with battery life.
I have no way to prove this but I work from 7am till 5:30pm. Before the zenkernel battery life would be around 70% after work. The other day it was at a low 80% after the kernel update. It may have been affected by outside temperatures as well I have no idea but it does appear to have better battery life.
Click to expand...
Click to collapse
I'm really not wanting to mess my phone up again, I should be getting a new one shortly, then I will test out flashing ROMs and all that. I get the idea and how its done, I just don't feel like taking the chance. My stomach dropped literally when I turned my phone on and it had no service and the HTC video didn't display. I thought the phone company may deny fixing it, but I came up with an elaborate story that the lady there took. She did break into my phone though, and now it is still partially opened in between the volume keys, and the silver vertical bar that goes around the phone, I wasn't happy about that.
Just a quick background, I purchased my DS7 at staples and rooted it and installed CWM using the info found on the forums so I could connect to my ad-hoc tether. Last week I attempted to install the HC upgrade and got the mis-match message. I booted into CWM and started looping. In an effort to correct this I mistakenly wiped the memory (big mistake!). I found the instructions on flashing the stock ROM (turned out that it was TMO) and got the unit running again. I called Dell (I have posted in another thread on this) and they are to send a pickup. In the meantime I have found instructions on flashing the OEM stock wfi ROM and have done so. I, like many others, noticed that the service tag was wrong and edited PG23/line220 to reflect my correct tag ( note to posters of ROMs and those who would flash: before doing so write down all the information about your unit so you can make changes later if needed). I now have most everything back to pre-upgrade status, but Gingerbreak v1.2 will not root. When I attempt it the program runs but I get a message “Not sure what happened her. Either the exploit failed or the reboot failed. Please reboot manually and see if you have Superuser!” I reboot and nothing, no Superuser and no root access. Also, before I attempt the “unroot’ option is greyed out so I take it that the unit is not rooted nor can I see root files in file manager One thing I have not tried is the CWM un-install that was included in the stock ROM flash thread. Since I don’t see it and I boot into fastboot I am guessing that it is gone. Any suggestions or has anyone had this issue as well?
Another note, I too have the 338 version and no auto update yet. I am not real sure I want to update now. To those that have updated, can you connect to ad-hoc networks with out changing the WPA?
Big wall of text, if you're on 2.2.x reflash CWM 3.0 and flash Superuser.zip as a update.zip though it.
If you're on HC, flash CWM 4.0 and flash Superuser7.zip on it.
Superuser.zip will always work on 2.x roms.
Superuser7.zip will always work on 3.x roms.
If you try and run the wrong one it will just 'run' and give no error, it will simply not do anything, but it wont damage anything.
Thanks, you think cwm is still lurking and giving problems? So I need to reinstall cwm and use it to install the zip? Won't CWM interfere with the HC update?
alchrisr01 said:
Thanks, you think cwm is still lurking and giving problems? So I need to reinstall cwm and use it to install the zip? Won't CWM interfere with the HC update?
Click to expand...
Click to collapse
If you have CWM installed you won't get the update automatically no matter if you have a matching ROM or not... you must be FULLY stock... but I see no sense in waiting, TheManii has already posted the releases that are coming out... why not just flash the zip