As the title says I got a magic value mismatch, so used the nvflash to stock image and it seemed to work fine. Went to download z4root.apk from the forum here and got a download unsuccesful message. I installed z4root and rooted from sdcard without a problem. Having done that I still can't download any file from any site. Be it http or ftp. Any idea what the problem might be?
Related
Hey guys, I am trying to flash Cognition 2.3b3 from Cognition 2.3b2, and the flash keeps failing in clockwork recovery. I have voodoo lag fix disabled, I flash clockwork recovery, and I have even tried installing the update with the wipe option checked. I keep getting an error during the installation saying "installation aborted. Cannot open /sdcard/Cognition2.3b3.zip.
Does anyone have any ideas?
Did you try redownloading the zip file? It may be a corrupt download?
If not, I wouldn't know since I haven't upgraded to b3 yet
I did try redownloading the zip. I can't figure what the problem is. The file came straight from designgears sight. I do not have winzip installed on my laptop. Could that make a difference?
Just sharing my experiance.
I had stockish eclair with voodoo (deleted one system file by mistake and it wouldn't boot) so i flashed Cognition 2.3b3 thro odin , it went thro without problems kernel detected ext4 present (from previous voodoo) and everything works fine
So you don't need to disable voodoo lag fix if your next rom supports it. And you could also try flashing with odin if clockwork fails.
bparkerson04 said:
I did try redownloading the zip. I can't figure what the problem is. The file came straight from designgears sight. I do not have winzip installed on my laptop. Could that make a difference?
Click to expand...
Click to collapse
Give us a Step by step of what you did so we can help further. When asking for help it helps us alot to give as much information as possable
I think I figured out what the problem was. I was deleting some stuff from my internal sd card, and I deleted the update.zip I used to root my phone when it was stock. I didn't think I needed it anymore. The thought occurred to me just now to put that file back, and I was just able to flash the rom. Go figure. Thanks for all of the input guys. I guess I will always need to keep that update.zip on my root sd.
I just now rooted my infuse 4g with superoneclick and I am trying to flash gtg's infused rom via ROM Manager. I am following all steps correctly and everything is working fine up until I go to flash clockwork mod recovery. It say's to select the galaxy s i9000 and I do, it appears to be downloading it then comes up with the error "There was an error while downloading your recovery." Am I doing something wrong? Is this a server error? I have flashed previously before and have not had this issue. I can assure you that I have followed every step in his guide to a T. The last thing I did was delete the /system/bin/recovery file. Just need to know whether it's a server error or is there something I am missing?
EDIT: I tried to do so over 3g rather than Wifi and it worked. I don't know why this would matter but it did. Flashing now
I have ROM Manager v4.8.0.6 if that is necessary to include...
Did you replace your stock recovery file prior to flashing clockwork in rom manager?
You have to replace it with modded recovery that doesnt require driver signature.
I believe its in system/bin/recovery (someone correct me if im wrong)
joho5 said:
Did you replace your stock recovery file prior to flashing clockwork in rom manager?
You have to replace it with modded recovery that doesnt require driver signature.
I believe its in system/bin/recovery (someone correct me if im wrong)
Click to expand...
Click to collapse
I did not. If you go to the infused rom thread and look at the steps for flashing via ROM Manager, that is what I did. I got to the part where it say's to open ROM Manager and select flash clockwork mod recovery>GalaxyS i9000. When I do so it say's there is an error while downloading my recovery.
Hi there,
I got a brand new Galaxy Note 10.1 this weekend and tried to get my hands dirty on rooting it just yesterday. So I got Odin3, CWM and SuperSU, installed Samsung Kies and thought I were good to go. Unfortunately, after doing what some guides tell me to do, I'm still on official device status.
Before I go into detail: I had to manually edit the Odin3 INI file to force the device NOT to auto reboot after flashing the CWM - the checkboxes in Odin3 were disabled and greyed out. Can someone explain why and if that might be the cause of my problems?
HoPi` said:
Hi there,
I got a brand new Galaxy Note 10.1 this weekend and tried to get my hands dirty on rooting it just yesterday. So I got Odin3, CWM and SuperSU, installed Samsung Kies and thought I were good to go. Unfortunately, after doing what some guides tell me to do, I'm still on official device status.
Before I go into detail: I had to manually edit the Odin3 INI file to force the device NOT to auto reboot after flashing the CWM - the checkboxes in Odin3 were disabled and greyed out. Can someone explain why and if that might be the cause of my problems?
Click to expand...
Click to collapse
Download a clean copy of Odin and install .
Auto Reboot is normal .
Root and Recovery TWRP
http://forum.xda-developers.com/showthread.php?t=1851548
Root and Recovery CWM
http://forum.xda-developers.com/showthread.php?t=1831173
jje
Thanks, but that didn't help either. Auto-Rebooting brings me back to stock, device state official. I tried to install CWM-SuperSU-v0.99.zip manually via CWM, but a reboot later it's still "official" and apps that need root access either run forever ("checking...") or freeze the tablet. But since this is getting off topic, I might be better off asking in other threads.
Thanks anyway!
HoPi` said:
Thanks, but that didn't help either. Auto-Rebooting brings me back to stock, device state official. I tried to install CWM-SuperSU-v0.99.zip manually via CWM, but a reboot later it's still "official" and apps that need root access either run forever ("checking...") or freeze the tablet.
Click to expand...
Click to collapse
Then you are not understanding instructions .
What is your intention .
Root or flash a stock rom .
Root via either method i posted .
Stock rom direct flash tar file via Odin.
ODIN flash is a tar not a zip.
Custom rom via a rooted phone with recovery zip file from ext sd card or sd card .
jje
Come on, the instructions are pretty clear boot in Odin Mode, click a button in Odin, let it restart, finished. The SuperSU zip file is from another guide, where the tar-file didn't include it. So I tried to manually install it via CWM (I think it was 6.0.2.7 or 8), but that didn't work either. Whenever the device reboots, Root Checker Basic runs for a few minutes and says "Sorry, the device does not have proper root access". If it helps, I used this guide:
http://www.android-hilfe.de/root-cu...ly-root-fuer-anfaenger-n8000-n8010-n8020.html
Even though it's in german, the screenshots are pretty obvious.
Sorry never ever seen any method with those sort of instructions.Personally not a clue what they mean .
I have used two methods as posted to root note 4 or 5 times. Rooted standard Samsung phones with cwm and root hundreds of times without any of those instructions.
Even run one standard cwm root via Odin to allow a specific rom install followed by a reroot using TWRP this afternoon .
jje
Sent from my GT-N8010 using xda premium
Thanks to Darkman, I finally got it. The problem was the current firmware update from Samsung. I reflashed with the version from January, followed his tutorial (like I did before - wow, after doing this 3-4 times, it certainly becomes second nature), and BAM, the device is rooted. Thanks anyway JJegan
Last week I struggle with root on my One-S (S4)
I have followed this thread and it went fine till "root" When downloading / installing TWRP .zip superSU it went wrong, because it is a update file http://download.chainfire.eu/446/SuperSU/UPDATE-SuperSU-v1.99r3.zip, so I downloaded a older version, and then installed update file in recovery
Now SuperSU says SU binary must be updates and I can't update with file under TWRP.
So, now some programs say that I'm rooted and some say I'm not
Another problem is that I can't connect through USB anymore, I tried under win-7 win-8.1 and several PC, yeas I tried also several HTC drivers (it worked in the past with fastboot) In Recovery I CAN mount
WTF went wrong, and more important how can I get proper root
ROM = Twitedkat 2.5
TWRP 2.7
OMG !!!
I can't believe it, while writing post I tried to update SuperSU with update file, just like 7080120 attempts before.
Tried again and now it works like a charm.
I really can't understand what went wrong.
But.. problem solved
hi, i've got CyanogenMod 7.2 (Alpha9) on my galaxy 3, i initially used odin, then found i had the 0kb free space issue, but then used CWM to flash from a zip file and it's now working fine.
i'd like to put the MTD version on it, and i'm trying to follow the instructions here http://forum.xda-developers.com/showthread.php?t=2309390, but i can't get odin to flash the 1Ghz overclock mtd kernel.
the version of odin that i initially flashed the rom with has no problem establishing a connection with my phone, but says the .tar file is an invalid image when i try to load it in the PDA section.
i've tried a couple of other versions of odin, and they all accept it as a valid image, but none of them get past the point where it says setup connection.
alternatively, a link to a version of the same kernel that i can use CWM recovery to flash would be ideal, i've got to grips with CWM and find it easy to work with, but i'm struggling somewhat with odin.
i've realised my problem all along was that my copy of the mtd update was corrupt. i have re-downloaded it and all is going smoothly so far.
Mr Creosote said:
i've realised my problem all along was that my copy of the mtd update was corrupt. i have re-downloaded it and all is going smoothly so far.
Click to expand...
Click to collapse
Finally ! Have fun with the ROM.
marcellusbe said:
Finally ! Have fun with the ROM.
Click to expand...
Click to collapse
thanks, i'm very happy with it now that the battery isn't draining really quickly like it was with the non-mtd version. i'd been going about it the right way all along, lol, it just never occurred to me that i had a corrupt file. was only when i double clicked on it to look at the contents of the zip that i realised it was corrupt. i was beginning to worry that the world of android modding was hopelessly impenetrable.