Hi all,
I'm trying to install ClockworkMod with no luck. I'm getting the "Signature verification failed" error.
I have a Samsung Galaxy s2 9100M (bell/virgin version). Currently running everything stock except that I manually gained root access, compiled su binary and placed it in /system/bin (with appropriate permissions of course). I also installed busybox from source. So my phone is fully rooted, the superuser app works fine as well (used chainsdd su).
Now an obvious option is to use Odin and flash CWM recovery. However, I'm running Linux, so no Odin (I'd also like to avoid using a VM). What's the alternative? The stock recovery will not allow me to flash unsigned files.
Please feel free to provide complex solutions. I'm a professional software engineer with extensive unix/linux knowledge. I'm just not entirely familiar with the SGS2/android architecture but I can google the missing bits.
As an aside, if I end up having to flash the recovery partition with CWM, is this recovery overwritten when flashing the stock rom? I.e. does it rebuild it on first boot? Is it part of the rom?
To get CWM recovery, you need to flash a kernel which comes with it. Since you're rooted already, you can either do that using Heimdall, via an app such as Mobile Odin (several others exist) or manually via adb/terminal.
Why do I need an entire kernel? Can't I just install the recovery? I was planning on making a full backup of my stock phone, including the kernel, for recovery purposes.
I used Rom Manager and tried to flash CWM with it. It failed and left me with the update.zip which I can't flash in recovery because of the signature issue.
About the Apps, I've heard that Rom Manager isn't safe to use (i.e. may brick the phone). What about Mobile Odin (which isn't free)? Does using a pay app make it any safer?
Simple method .
Root + CWM .
http://forum.xda-developers.com/showthread.php?t=1103399
Why do I need an entire kernel? Can't I just install the recovery? I was planning on making a full backup of my stock phone, including the kernel, for recovery purposes.
As recovery is in the kernel the answer is no .
jje
ldiamond2 said:
Hi all,
I'm trying to install ClockworkMod with no luck. I'm getting the "Signature verification failed" error.
I have a Samsung Galaxy s2 9100M (bell/virgin version). Currently running everything stock except that I manually gained root access, compiled su binary and placed it in /system/bin (with appropriate permissions of course). I also installed busybox from source. So my phone is fully rooted, the superuser app works fine as well (used chainsdd su).
As an aside, if I end up having to flash the recovery partition with CWM, is this recovery overwritten when flashing the stock rom? I.e. does it rebuild it on first boot? Is it part of the rom?
Click to expand...
Click to collapse
I had this problem originally when i first rooted my phone, (S2 International). Signature Verification Failed.
I flashed a CWM based recovery, 4.0 or something and my problems went away. S2 Kernels and Recoveries are merged in one, thats why you can't have one with out the other.
If you flash a different rom, unless it comes with its own recovery, it won't overwrite yours.
ldiamond2 said:
I was planning on making a full backup of my stock phone, including the kernel, for recovery purposes.
Click to expand...
Click to collapse
Any backup you make will still be rooted, which is likely to invalidate warranty anyway.
Read this thread for how to achieve what you want: http://forum.xda-developers.com/showthread.php?t=1409484
Rooted is fine since I can manually remove the su binary and busybox.
I've seen this method before but I have seen no comments on if it really works or not. Maybe you have?
ldiamond2 said:
I'm a professional software engineer with extensive unix/linux knowledge. I'm just not entirely familiar with the SGS2/android architecture but I can google the missing bits.
Click to expand...
Click to collapse
ldiamond2 said:
I've seen this method before but I have seen no comments on if it really works or not. Maybe you have?
Click to expand...
Click to collapse
It's dd, not much else to explain to a Linux user .
If you follow the advice of dd'ing the kernel first, then flashing a kernel containing CWM and dd'ing all the partitions from within recovery (adb) and doing nandroid backup for good measure, there's really not a lot that can go wrong when it comes to restoring.
oinkylicious said:
there's really not a lot that can go wrong when it comes to restoring.
Click to expand...
Click to collapse
Well, one thing that comes to mind is missing partitions... Another is partitions residing in read-only memory (which you can't remount as read-write) for which dd wouldn't be helpful for restoring.
Also using dd to copy partitions mounted as read-write can cause a corrupted output. Who knows what happened while you were copying it.
Quoting the post: "Put back your Backups [untested]"
hi guys
i'm now using NEAK 2.0 SAMMY kernel on ICS that is working with CWM 5.5 (touch)
how can i change it to the simple CWM that just use button to work ?
is it possible?
I can't give you the verification you're looking for, I've never had an interest in getting my phone back to the condition it was in when I bought it (I rooted it the day I bought it, 11 months ago, and never looked back).
I don't believe any of the partitions are incapable of being mounted R/W. If they were, it would surely be irrelevant for you anyway since if you can't write to them, they're not going to change no matter what you do. Also, dd'ing from recovery over adb should ensure nothing is writing to the partitions.
oinkylicious said:
If they were, it would surely be irrelevant for you anyway since if you can't write to them, they're not going to change no matter what you do.
Click to expand...
Click to collapse
Well, depends what the flashing process involves. It can flash memory that otherwise can't be flashed from the OS.
Also, dd'ing from recovery over adb should ensure nothing is writing to the partitions.
Click to expand...
Click to collapse
That's definitely a way to avoid the corruption of the dd image.
god.fsl: Don't try to hijack the thread.
ldiamond2 said:
Well, one thing that comes to mind is missing partitions... Another is partitions residing in read-only memory (which you can't remount as read-write) for which dd wouldn't be helpful for restoring.
Click to expand...
Click to collapse
I am not really sure why you are trying to make easy things that difficult.
Have a look at the CF-Root Kernels.
These are kernels taken from stock ROM and only included necessary things like busybox, superuser, CWM and so on.
With CWM you can easily make a backup of your entire system.
Seriously it's a pretty easy things and you would have to worry alot less. Even if you are a professional linux software engineer.
PS: When working on the system like you are it might probably be a good idea to do a quick backup of your efs Folder
Related
I've spend much of the day trying to root and then flash my new Optimus V. For some reason I keep running into snafus, even after rooting two Eris phones and a Nook color without too much difficulty. Would REALLY appreciate the group's assistance.
After much trial and error, I finally got root using SuperOneClick.
After that, I first tried to use adb to install the asop ROM per http://forum.xda-developers.com/showthread.php?t=962862 , but would always get stuck on the blue bootloader screen. By trying to fix that, I got stuck in a clockworkmod recovery loop. I finally got out of that by doing a flash_image of the stock ROM via adb. But then, the google market, and hence my google apps (including clockworkmod) was gone.
So now I'm stuck without access to clockwork mod, and a broken stock rom/interface (with no market access.) There may be a way to launch CWM even with the vashished google apps, but I'm not sure what it is...
Here is what I do have readily available in my "toolkit":
-root still working (via superoneclick);
-Root Explorer (having manually installed the Amazon marketplace apk);
-abd access to my 4g SD card;
-a backup 4g SD card, should one prove helpful.
My goal is pretty simple: to get a good custom rom (probably ASOP) with a fully functional suite of apps, and to MAKE SURE that the other corruption I've unwittingly done to my phone's data is complete eradicated.
I apologize for the jumbled nature of this post. I'm sure I'm leaving some diagnostic stuff out that would be useful--please fire away and I'll be more than patient about trying to clarify.
THANK YOU in advance for any help you can offer!
polphi said:
I've spend much of the day trying to root and then flash my new Optimus V. For some reason I keep running into snafus, even after rooting two Eris phones and a Nook color without too much difficulty. Would REALLY appreciate the group's assistance.
After much trial and error, I finally got root using SuperOneClick.
After that, I first tried to use adb to install the asop ROM per http://forum.xda-developers.com/showthread.php?t=962862 , but would always get stuck on the blue bootloader screen. By trying to fix that, I got stuck in a clockworkmod recovery loop. I finally got out of that by doing a flash_image of the stock ROM via adb. But then, the google market, and hence my google apps (including clockworkmod) was gone.
So now I'm stuck without access to clockwork mod, and a broken stock rom/interface (with no market access.) There may be a way to launch CWM even with the vashished google apps, but I'm not sure what it is...
Here is what I do have readily available in my "toolkit":
-root still working (via superoneclick);
-Root Explorer (having manually installed the Amazon marketplace apk);
-abd access to my 4g SD card;
-a backup 4g SD card, should one prove helpful.
My goal is pretty simple: to get a good custom rom (probably ASOP) with a fully functional suite of apps, and to MAKE SURE that the other corruption I've unwittingly done to my phone's data is complete eradicated.
I apologize for the jumbled nature of this post. I'm sure I'm leaving some diagnostic stuff out that would be useful--please fire away and I'll be more than patient about trying to clarify.
THANK YOU in advance for any help you can offer!
Click to expand...
Click to collapse
Boy, First of all don't panic. Without bricking you can't learn.
Second for Root you can use Gingerbreak. This should work. http://forum.xda-developers.com/showthread.php?t=1044765
for Flashing on all use custom recovery tool. And its like one two three from your phone only using terminal apps. Here is the guidehttp://androidforums.com/getitnowmarketing/221388-custom-recovery-optimus-one-p500-thunderg.html
After entering in Custom recovery mode you can do what ever you want to do. Flash rom as per your desire.
have you flashed clockworkmod recovery before?? if yes access it using the three button combo....you can flash any rom you want from recovery....
hit the thanks button if i have helped you.
sajjan said:
have you flashed clockworkmod recovery before?? if yes access it using the three button combo...
Click to expand...
Click to collapse
Alas, after restoring the stock, the three button combo brings up not clockworkmod, but "Android system recovery <3e>", which *only* allows:
reboot
apply sdcard update.zip
wipe data/factory reset
wipe cache partition
Since I don't have an update.zip file that works, I can't seem to get beyond this. When I tried renaming a custom rom recovery file update.zip, I got a signature mismatch, which makes sense.
First, thanks to both sweetbinodray and sajjan for the replies.
sweetbinodray said:
Boy, First of all don't panic. Without bricking you can't learn.
Click to expand...
Click to collapse
Hehe, that's similar to what I keep trying to tell myself.
Second for Root you can use Gingerbreak. This should work.
Click to expand...
Click to collapse
I have root, even have root explorer working via Amazon mktplace. (I shouldn't need or want to re-root, should I?)
for Flashing on all use custom recovery tool. And its like one two three from your phone only using terminal apps. Here is the guidehttp://androidforums.com/getitnowmarketing/221388-custom-recovery-optimus-one-p500-thunderg.html
After entering in Custom recovery mode you can do what ever you want to do. Flash rom as per your desire.
Click to expand...
Click to collapse
When I follow that guide, I'm linked to an updated thread which asks me to enter shell (no problem) then use the following command as first in a series:
mount -o remount,rw -t yaffs2 /dev/block/mtdblock5 /system
that results in "mount: operation not permitted".
Basically, having (regrettably) tried to to start from scratch by reflashing stock, I keep running into these permission snags.
Seems like if I could get to the CWM recovery screen, or figure out a way to trick the stock recovery screen into accepting a different update.zip, I'd be OK.
Then again, perhaps that's making things too complicated?
TIA once again!
Also, this looks like it might work, but I can't seem to get the validation email necessary to validate a board membership, which appears necessary to download the Quick Boot file.
polphi said:
First, thanks to both sweetbinodray and sajjan for the replies.
Hehe, that's similar to what I keep trying to tell myself.
I have root, even have root explorer working via Amazon mktplace. (I shouldn't need or want to re-root, should I?)
When I follow that guide, I'm linked to an updated thread which asks me to enter shell (no problem) then use the following command as first in a series:
mount -o remount,rw -t yaffs2 /dev/block/mtdblock5 /system
that results in "mount: operation not permitted".
Basically, having (regrettably) tried to to start from scratch by reflashing stock, I keep running into these permission snags.
Seems like if I could get to the CWM recovery screen, or figure out a way to trick the stock recovery screen into accepting a different update.zip, I'd be OK.
Then again, perhaps that's making things too complicated?
TIA once again!
Click to expand...
Click to collapse
Ok what i can suggest you is do manual set up for custom recovery using terminal apps. Here is the guide http://forum.xda-developers.com/showthread.php?p=15185778#post15185778 and start form install terminal emulator. And write following commands.. its like one to three....
so i have the i777 and i rooted using a guide on the android central forum
basically i downloaded kies, odin, cwm, and superoneclick
i put the cwm.tar file through odin, and than ran superoneclick, and i was rooted pretty easily
i than downloaded rom manager and through there i flashed CWM. I tried to make a back up using rom manager but that failed, no biggie i hear other people have the same problem. I boot up into CWM using rom manager and it says stuff like "failed to verify whole file signature"
im not sure if this means i rooted incorrectly?
i made a back up just fine using CWM. However i found out this stuff about flash increments and how i flashed a custom CWM kernal or something (sorry my definitions in this subject are still noob)
i decided i want to get rid of the yellow triangle + i9100 message every boot, no biggie but i am here to learn and i figure might as well if i can. I read a couple threads here and im not sure if this is my answer but i think it is please advise
my plan is to go back completely as if i never rooted and than root by using a stock rom/kernal so i dont get the error triangle message as well as the incorrect international i9100 display
i think this is my solution
"2b.) How to root by flashing Entropy512's Return/Unbrick to Stock, Kernel + Rooted System Package from the command line using Heimdall (Linux and Mac OS)
* Tested on Linux, should work on Mac OS
* Download and install the latest version of Heimdall Command Line for your operating system from here. (Latest version 1.3.1 at this writing.)
* Download Entropy512's Return/Unbrick to Stock, Kernel + Rooted System Package from here. Extract the PDA.tar file from this package to a directory on your hard disk drive, then extract the two component files from the tar - zImage and factoryfs.img.
* Place zImage and factoryfs.img both in the directory where you have the Heimdall command line executable, and enter the following at the command prompt:
Code:
heimdall flash --kernel zImage --factoryfs factoryfs.img
* Reboot the phone. Success. You're Rooted.
"
i am under the impression that if i flash the .tar file that is 200+mb (why so big) that i will be RE ROOTED and COMPLETELY stock, therefore no error message and no international thing popping up
also, no more flash counter increments ? << this one is also important as this is one major reason i want to re root
im not really sure but i think that by flashing this new .tar it will over ride my custom.tar file that i do not want any more, i dont know how to get rid of it so this is the only thing i can think of
im worried because i dont know if i have to UNROOT before i install entropys thing or if it will just over ride
thanks so much to any one who can give me advice
Really the best instructions are in creepncrawly's write up on how to return to stock. It covers any question you could have:
http://forum.xda-developers.com/showthread.php?t=1313659
And for doing it right:
http://forum.xda-developers.com/showthread.php?t=1311081
Plus new tools:
http://forum.xda-developers.com/showthread.php?t=1367319
The write ups he does are top notch and should be mandatory reading for first time visitors.
The file is so big because it contains the entire android os.
The issues you're having in cwm sound like clockworkmod needs to be reflashed.
The triangle will be removed simply by the stock kernel being replaced. The flash counter as of now can only be reset by a usb jig ~ less than $10.
Though a few have reported returning the phone for warranty issues and they did not check the flash counter.
The only way the flash counter is tripped is by using pc Odin to flash a non stock kernel.
Sent from my páhhōniē
ok thanks for the help, tomorow im gona read the links you posted thoroughly but i was wondering
if i flash a stock kernal, than how am i rooted
i am not even really sure what "roots" my phone but i thought that it was installing CWM because its a recovery tool which allows more options "superuser"
thanks again! cant wait to waste all day tom reading more about rooting
DroidBehavior said:
ok thanks for the help, tomorow im gona read the links you posted thoroughly but i was wondering
if i flash a stock kernal, than how am i rooted
i am not even really sure what "roots" my phone but i thought that it was installing CWM because its a recovery tool which allows more options "superuser"
thanks again! cant wait to waste all day tom reading more about rooting
Click to expand...
Click to collapse
There's a stock plus root package. One of the best ways to root in my opinion.
Root means installing SuperUser.apk, su, and busybox. That's it. The stock + root package has those already included, but also gives you the bone stock kernel.
You install a custom kernel to, among other things, get ClockworkMod Recovery.
DroidBehavior said:
ok thanks for the help, tomorow im gona read the links you posted thoroughly but i was wondering
if i flash a stock kernal, than how am i rooted
i am not even really sure what "roots" my phone but i thought that it was installing CWM because its a recovery tool which allows more options "superuser"
thanks again! cant wait to waste all day tom reading more about rooting
Click to expand...
Click to collapse
in reality, 'rooting' your phone is nothing more than placing 2 files on the /system (only one is really needed, since you can download Superuser from the market)
what happens is this:
android version release (say 2.3.5)
extremely smart people find way to exploit a memory hole in the OS, and create a 'rooting' method. what this method does is exploit that hole, which allows for a 'temp root' while it injects the needed files for root
needed files for root:
/system/bin/su <- this is the binary that allows you to retain root access
/system/app/Superuser.apk
without root access, /system is a read-only partition. utilizing the exploit, it will create temp root, then remount the /system partition as read/write, allowing your rooting tool to inject the required files into /system
rooting actually has nothing to do with the device at a true hardware level. it is all within the OS itself. anything outside the OS (recovery, boot, bootloaders, etc) dont get 'rooted' because root is only access to the /system within the OS
samsungs have this awesome ability to be easily rooted via CWM. its extremely easy with ODIN or heimdall to flash recovery/new kernel with recovery built in, and use a cwm zip file to inject the needed files into /system rather than relying on an exploit to do it for you.
its a common misconception that i hate to see when people associate rooting with access to anything outside the OS itself.
'i am having problems flashing this rom/kernel/mod in cwm'
'are you sure you are rooted? try re-rooting'
asinine logic...to say the least
^^
That needs to be stickied in every android forum on xda.
Sent from my páhhōniē
ok im back, i read a lot of the guides n a lot of pages and i successfully rooted using entropys 2a method return to stock + root
now i have a 2-3 second delay in my home button, and an additional 1 second delay when i turn my phone ion with the power button to show my display
i also added CWM by using the android terminal and that worked
but im regretting all this because of the delay, my error message is gone so thats good but now i have a delay
what could be the problem? i dont remember any one mentioning this issue and if im the only one than i dont know what to do, also i noticed the flash counter is still at 1 so i know i did everything right
DroidBehavior said:
ok im back, i read a lot of the guides n a lot of pages and i successfully rooted using entropys 2a method return to stock + root
now i have a 2-3 second delay in my home button, and an additional 1 second delay when i turn my phone ion with the power button to show my display
i also added CWM by using the android terminal and that worked
but im regretting all this because of the delay, my error message is gone so thats good but now i have a delay
what could be the problem? i dont remember any one mentioning this issue and if im the only one than i dont know what to do, also i noticed the flash counter is still at 1 so i know i did everything right
Click to expand...
Click to collapse
Sounds like you still have reading to do. And kudos to you for taking what they said as constructive criticism.
The flash counter can only be reset by a usb jig. Mobile Tech videos make some very good quality ones.
The delay from the home button is due to the vlingo app shortcut being tied to the home button (double tap home button) so it's waiting to see if you hit it twice before it takes you to the home screen. Cusom roms remove the vlingo app from being there which helps cut down on the delay.
But you may notice it more since what you did. And you should. By adding cwm you likely flashed Entropy512's kernel. Which is an awesome kernel. One of the ways that kernel helps battery life is by setting the cpu govener to conservative. It slows the cpu from jumping too high too quick. That explains why you may have not noticed the delay before you did anything. As well as the delay from unlocking the phone.
For me the extra battery life is worth it. If you don't like the delay one of the easier ways to set it back to ondemand (stock) is to use the app SetCpu:
https://market.android.com/details?id=com.mhuang.overclocking&hl=en
Hope that explains everything.
Sent from my páhhōniē
yeah that makes perfect sense thanks for the explanation
right now i installed miui and i ****ing love it! the interface is so smooth and sexy its like iphone spliced with android
minimalistic ftw
the interface was so much smoother i ran quadrant but the score was the same heh, but still its impressively smooth
I've been all through the old threads and googled the hell out of this...
I've recently been released from iHell and have to start all over as a noob again.
I successfully rooted my I-777 with entropy512's OneClick Odin method. Then re ran the OTA t back to 2.3.6. I am still rooted. (YAY!!!!!)
Anyway it was strongly suggested that I run a nandroid backup before flashing a new ROM. I went to the market, searched nandroid and was presented with CWM ROM manager. After install, on first run, it wanted to install CWM Recovery (which I thought could only come from a kernel but anyway). It appeared to have done so, but when I attempt to run the ROM backup it errors:
Code:
E:failed to verify whole-file signature
E:signature verification failed
I'm also getting errors in 3e:
Code:
--Copying Media Files ...
Successfully coppied media files
# manual mode #
--Updating Application...
Successfully updated application
-- applying multi-CSC...
installing multi-CSC
Can't access to '/system/csc/ATT/system/'.
successfully applied multi-csc.
Another strange behavior (not necessarily an error): Last night, prior to rooting, I was able to do to download mode with my USB cable plugged into EITHER the computer OR a USB power adapter / charger. Today, after root and ROM manager, I can only get to Download mode when plugged in to the computer. (caused a bit of panic till I took a couple deep breaths and began to trouble shoot)
I'm not a huge fan of flashing anything without a (relatively) virgin backup. I fear I may be stuck at root for a bit.
So questions:
1. Did ROM manager ACTUALLY install CWM R? Or do I have to flash the kernel to get it?
2. Is there a better way to gain a full file system image? I've seen a few users say that ROM manager and other GUI's add a layer of complexity and possibly error to the backup process.
2a. Is there a CLI in Android? (even an app to do CLI?) If so , can I interact direclty with the OS that way?
3. Is there a place to get a clean OS install if I get all A.D.D. and go ahead and flash without the backup and then screw the pooch? (Or if I want to virginize for any reason?)
I am planning to follow creepyncrawly's post to flash if I can work this out:
http://forum.xda-developers.com/showthread.php?t=1311081
I am dieing without my WiFi hotspot.
There are warnings in several places in the I777 forums to not use ROM Manager. It's not compatible with the I777 phone.
Yes, you have to have a custom kernel to have working ClockworkMod Recovery.
There is no way to do a nandroid backup of the stock kernel. You can do a nandroid backup of the stock file system by installing a custom kernel with CWM Recovery.
You can restore the original UCKH7 binaries with or without root by using Entropy512's Return/Unbrick to Stock, and there is also a UCKK6 available in that thread, so no need for a stock nandroid backup. The main reason for a nandroid backup is to backup the modifications that you have made.
So use the guide to install a custom kernel. I would suggest Entropy512's latest daily driver, especially if you plan to run the stock ROM for any length of time. Then do a nandroid backup. Then you can move forward to installing a custom rom if you want, or whenever you want.
SeniorGato said:
it wanted to install CWM Recovery (which I thought could only come from a kernel but anyway)
Click to expand...
Click to collapse
Somehow ROM Manager can try to run its own version of CWM - I have never seen this work properly.
I'm also getting errors in 3e:
Code:
--Copying Media Files ...
Successfully coppied media files
# manual mode #
--Updating Application...
Successfully updated application
-- applying multi-CSC...
installing multi-CSC
Can't access to '/system/csc/ATT/system/'.
successfully applied multi-csc.
Click to expand...
Click to collapse
Odd, that looks like the initial power-on CSC flash, shouldn't happen after that.
Another strange behavior (not necessarily an error): Last night, prior to rooting, I was able to do to download mode with my USB cable plugged into EITHER the computer OR a USB power adapter / charger. Today, after root and ROM manager, I can only get to Download mode when plugged in to the computer. (caused a bit of panic till I took a couple deep breaths and began to trouble shoot)
Click to expand...
Click to collapse
This is working as intended, not sure why you were able to enter DL mode on a charger (shouldn't have happened), unless it was not an official charger. The resistors in iDevice chargers make the phone think a real PC is connected, not a charger.
So questions:
1. Did ROM manager ACTUALLY install CWM R? Or do I have to flash the kernel to get it?
Click to expand...
Click to collapse
ROM Manager sort-of-installed a nonfunctional version of CWM. Only one that works properly is in-kernel CWM. (Read through Development, also read through Creepy's guides on flashing kernels without tripping the flash counter)
2. Is there a better way to gain a full file system image? I've seen a few users say that ROM manager and other GUI's add a layer of complexity and possibly error to the backup process.
Click to expand...
Click to collapse
Nandroid from CWM itself - the instructions for entering CWM and using it properly are in codeworkx'x CWM thread in Development.
2a. Is there a CLI in Android? (even an app to do CLI?) If so , can I interact direclty with the OS that way?
Click to expand...
Click to collapse
This is why Android is so popular with tinkerers - while the GUI is heavily customized, shell access is almost identical to a vanilla Linux system. Google "ADB" for more info. ADB only works in recovery on custom kernels.
3. Is there a place to get a clean OS install if I get all A.D.D. and go ahead and flash without the backup and then screw the pooch? (Or if I want to virginize for any reason?)
I am planning to follow creepyncrawly's post to flash if I can work this out:
http://forum.xda-developers.com/showthread.php?t=1311081
Click to expand...
Click to collapse
You answered your own question right there - his guides link my stock kernel/system dumps.
I suggest spending a day or two reading through the various threads in Development, and reading the FAQ in general, there is a LOT of reading material and even if it goes over your head the first time, you'll start absorbing it and it'll make more sense the next time around. The fact that you are proceeding cautiously is a good start.
Oops... Apparently I wasn't "all through" the forums enough huh? I didn't see any warnings about ROM Manager... but thanks I'll dump it.
Everything else you say makes sense. Thanks!!! I'm still trying to translate what I know about the iOS FS and jailbreaking to what I need to learn about Android. Ugh...
@ entropy
Ya the CSC thing, I've been multi-tasking all day and for the life of me I can't remember why I was even in 3e. It wasn't for a restore, thats for sure.
I had assumed that the development threads were the real high level stuff (as it is on iOS forums the "DEV's" speak in code and their conversations can strip the hair of a noob's head. I figured I'd start slow, with (what I assumed would be) the lower level stuff. I'll head over to the dev threads now.
Thanks again!!!
SeniorGato said:
@ entropy
Ya the CSC thing, I've been multi-tasking all day and for the life of me I can't remember why I was even in 3e. It wasn't for a restore, thats for sure.
I had assumed that the development threads were the real high level stuff (as it is on iOS forums the "DEV's" speak in code and their conversations can strip the hair of a noob's head. I figured I'd start slow, with (what I assumed would be) the lower level stuff. I'll head over to the dev threads now.
Thanks again!!!
Click to expand...
Click to collapse
Usually the threads for ROMs/kernels have enough to be useful in the first posts. Even if it goes over your head the first few times, you'll get ideas for Google search terms to play with like Odin and Heimdall.
Also there's a FAQ in General.
Hi out there! First should say im new on Android, and want to learn at least to a medium level user (flashing diferents ROMS, testing them, setting my phone how i like to, etc). Im now learning the basic vocabulary, looking and reserching about my android model and software. And the question is the next one:
I want to root my phone(SGS2/GT-I9100) by this method because i read the whole 44 pages of the thread and sounds safe, easy and all the people talks great about it (except one user that brick his phone ).
http://forum.xda-developers.com/showthread.php?t=1501719
And i have read too that the first thing you should do after rooting is an nandroid backup, so you can get to this point in a future if something doesn´t work rigth.
Usually the nandroid backups are made with CWM or Titanium backup. I would like to use CWM, and my question is:
When I follow below rooting guide, the CWM isn´t permanent no? it just used to flash de SU-Busybox. So should i download and install it to make the "holy" nandroid backup?? I found this other thread where is explained how to make this nandroid backup, with RM and then using CWM.
http://forum.xda-developers.com/showthread.php?t=1592104
So after rooting, i should follow those steps no?( i mean, getting RM) Because my doubt is that the first CWM (the one i use for rooting) is the same i can use for de nandroid backup?? or this one its just to flash the SU intaller and i need to download and install it (CWM)? So i can follow both guides without any problem? im not doing the same thing 2 times no?
Thanks, and sorry for my english, it´s a little rusty... Im a noob and hate my self (xD), but want to learn.
CF Root
I'd recommend rooting with the cf root method. It installs SU, Busybox and CWM recovery. In recovery you can make a nandroid back up. It's quick and easy.
The links you posted came up with a 404 error.
Cf root is always the best way to root ur phone, since it also installs the CWM recovery for u, so that u can do the nandroid bkp for future use if any issue peeps while flashing any roms r mods
ps- please ensure u choose the right cf-root kernel to root ur phone
So i should follow this guide (i assumpt):
http://forum.xda-developers.com/showthread.php?t=1103399
But i have looked to my kernel version (wich is LPB) and boths files give an error when mounting secure storage (said by CF)...
rolfer said:
So i should follow this guide (i assumpt):
http://forum.xda-developers.com/showthread.php?t=1103399
But i have looked to my kernel version (wich is LPB) and boths files give an error when mounting secure storage (said by CF)...
Click to expand...
Click to collapse
If that is what you fear I suggest installing a different official ROM which doesn't have the same problems with CF Root. Here is a thread where you can find many of them...
http://forum.xda-developers.com/showthread.php?t=1075278
After flashing official firmware, THEN you can flash the appropriate CF Root
Sent from my GT-I9100 using Tapatalk
rolfer said:
So i should follow this guide (i assumpt):
http://forum.xda-developers.com/showthread.php?t=1103399
But i have looked to my kernel version (wich is LPB) and boths files give an error when mounting secure storage (said by CF)...
Click to expand...
Click to collapse
To make a nandroid backup, just use the same steps to launch CWM from stock recovery. You will be able to make a nandroid backup. To restore, it is same thing, you have to launch the CWM from stock recovery each time. That is the only difference with CF_Root, you have to launch CWM with an extra step as you keep your original stock CWM
As if you should use my superSU zip or original superuser one, I advise my zip for 2 reasons:
- SuperSU offers the possibility to easily unroot or migrate to superuser if you like (superuser does not natively offers this)
- it is the last version of busybox and fixes issues with some applications like adaway
Great! So i don´t need to install CWM then? I can do everything i need through it by this way? like nandroid backups, flashing ROMS, etc...? I want to make a nandroid backup just after rooting, to have a secure save if i need it in the future (I hope I don´t xD)
And then ill take your files cause are latest Today i don´t have enough battery to root the device securly, so i´ll do it tomorrow. I´ll tell here if it was succesfull for future readers with same doubt like me.
Thanks again!
Yes, you can do all that you like from the included cwm custom recovery. After reboot, you are still on your original stock CWM as it vanishes. That is really the only difference with a permanent cwm recovery (except maybe some custom mods/tweaks by kernel developers)
That way, no yellow triangle or custom flash counter increase
Hi guys n girls,
I am sort of new to the Ace section here. I am doing a re-vamp of my mum's phone and said I would spruce it up a little. Shame there is no decent CM 9 versions that I can get working because of lack of RAM....the only one listed (no disrespect to the dev - thanks for making it available on such a low spec device!) but it doesn't work with my Optus GT S5830V (5830I) for some reason?
Anyway to my point, I have downloaded several versions of the stock firmware from Sammobile. The odd thing is that I cannot extract that firmware at all. Every archive program I have sees it as either being not an archive; corrupt or fails to extract it? So I am unable to make my own 4 part Odin recovery package. Making my own will save time; at the moment I have to flash the 4 part Odin (return to stock) package, then reboot into download mode again and then flash the stock firmware?
3 things I noted.
1). The device is not detected by the so called Odin specific for Ace and variants that uses an Ops type PIT file? The device is plugged in and all drivers upto date....it' just plain doesn't see it? It is however detected and flashable (albeit without an .ops file) using the 4 part package on Odin 3.07 made for my Galaxy S3?
2). I am unable to get any detection with EFS pro and it returns no PIT file?
3). All attempts to extract the stock Optus firmware package fail. I have removed the .MD5 file extension (only needed for preserving file naming conventions anyway - i.e. If you rename any .tar.md5 firmware package, in order to be able to flash it you need only to remove the .md5 from the end and leaving it as .tar and the firmware will flash without error. I digress.....What does someone suggest for me to being able to make my own firmware package based on stock?
First off, wrong section.
Jarmezrocks said:
Shame there is no decent CM 9 versions that I can get working because of lack of RAM....the only one listed (no disrespect to the dev - thanks for making it available on such a low spec device!) but it doesn't work with my Optus GT S5830V (5830I) for some reason?
Click to expand...
Click to collapse
1) We don't have a stable CM9 because our devs don't have the source code for all the drivers, not lack of RAM.
2) Have you formatted your system's partitions to the EXT4 filesystem? CM requires an EXT4 filesystem to operate.
Jarmezrocks said:
Anyway to my point, I have downloaded several versions of the stock firmware from Sammobile. The odd thing is that I cannot extract that firmware at all. Every archive program I have sees it as either being not an archive; corrupt or fails to extract it? So I am unable to make my own 4 part Odin recovery package. Making my own will save time; at the moment I have to flash the 4 part Odin (return to stock) package, then reboot into download mode again and then flash the stock firmware?
Click to expand...
Click to collapse
Jarmezrocks said:
3). All attempts to extract the stock Optus firmware package fail. I have removed the .MD5 file extension (only needed for preserving file naming conventions anyway - i.e. If you rename any .tar.md5 firmware package, in order to be able to flash it you need only to remove the .md5 from the end and leaving it as .tar and the firmware will flash without error. I digress.....What does someone suggest for me to being able to make my own firmware package based on stock?
Click to expand...
Click to collapse
The tar.md5 file has to split into the PDA, CSC, Modem and PIT files using Odinatrix. Search for it.
Jarmezrocks said:
3 things I noted.
1). The device is not detected by the so called Odin specific for Ace and variants that uses an Ops type PIT file? The device is plugged in and all drivers upto date....it' just plain doesn't see it? It is however detected and flashable (albeit without an .ops file) using the 4 part package on Odin 3.07 made for my Galaxy S3?
Click to expand...
Click to collapse
The Odin specific for Ace you stated above might be for GT-S5830. For the variants running the Broadcom BCM21553 the Odin version to use is v1.84. Odin v3.07 is more like a universal Odin that works on most devices.
Jarmezrocks said:
2). I am unable to get any detection with EFS pro and it returns no PIT file?
Click to expand...
Click to collapse
I don't know about this.
NightRaven49 said:
First off, wrong section.
Click to expand...
Click to collapse
Why? I was not actually asking for support as such, just sharing what I learnt/noticed.
NightRaven49 said:
1) We don't have a stable CM9 because our devs don't have the source code for all the drivers, not lack of RAM.
2) Have you formatted your system's partitions to the EXT4 filesystem? CM requires an EXT4 filesystem to operate.
Click to expand...
Click to collapse
Yes I am aware of that. I actually did attempt to flash the CM9 developer package several times all without result.
I tried many methods, firstly the conventional method and then several other unconventional methods. I first flashed CWM recovery 6.0.0.x (something around there) and that was ok but it could not detect the partitions....naturally I was on the standard firmware!
So I then flashed Thunder kernel which allowed recovery to see and mount all the partitions as well as prepare for a CM firmware flash. As I knew that CM required EXT4 I was prepared and flashed Rio's Ext4-RFS conversion script via Aroma in recovery. This worked very well. Only issue was that in doing so it corrupts the system partition and then I am unable to mount it anymore to flash CM.
Returning to stock or even attempting a nandroid restore from this point forward was fruitless as you can imagine. I tried several other combinations before retiring the idea. These included full system wipe after flashing CWM recovery (I figured maybe having data on the partitions its self could be interferring with the EXT conversion scripts? Everything seemed fine and ran correctly as expected only no system mounting.
I tried another method of flashing a ROM that included a kernel with it based on CM7 in the hopes that migrating to CM9 would be easier; this was not the case.
I picked a CM7 ROM that had a conversion script built in for BML to MTD. After returning to stock base via Odin I proceeded to flash recovery 6.0.0.x again, then I immediately flashed CM7 in the hope that I would kill two birds with 1 stone and have CM do its conversion on the fly as well as install (alleviating the need for mounting system after migrating to Ext4). This ROM installed without fault. All was well until I rebooted expecting to boot into CM7....this wasn't the case, I received bootloops like crazy. Naturally I booted into recovery (the ROM had downgraded me to version 5.x CWM recovery - that is fine anyway); I proceeded by clearing the caches and performing a factory reset (note This usually a good thing to do anyway regardless if you came from a clean reset factory firmware or not).
After doing this and rebooting the device reboots continuously as it did prior. I again decided to re-install the same zip as I am aware with changing to CM on many other devices it can sometimes require flashing 2-3 (and sometimes even 4) times for a firmware update to stick. Again still no response and forever bootloops. I decided at this point that if I was to waste the time and effort in Odin'ing back to stock AND THEN flashing my standard firmware that I should try another CM ROM.
I had CM9 available and even though half hour prior I was unable to mount the the system partition, I thought maybe that CM7 had been flashed first so if CM9 can see and mount partitions (like it should have originally) then I could flash CM9 in a hope that it might wipe out what ever was causing all the issues with bootloops.
CM9 installed correctly, however again I could not boot the device at all! I had read a post from a forum member's guide saying that if I got some of these issues that I should flash back to base and try it again. I did this another 3-4,5 times at least, various combinations of wiping base firmware, not wiping base firmware, wiping CM7; not wiping CM7......Always the end result = bootloops.
As you can imagine it was rather annoying if I was returning to base firmware (if I wanted to be stock carrier branded again I needed to flash twice, once to return to stock and again to flash Optus firmware.
Overall I was unable to get any firmware booting besides that which was provided as an Odin package AKA stock firmware. If I flashed a custom recovery over stock firmware I was unable to boot again. Oddly enough I found a standalone version of CWM recovery version 5 that was not CM specific and I performed a backup as it was able to see the stock partitions without throwing errors.
I then opted to do a conversion to EXT4 again and hoped that I could just restore my nandroid backup of the stock partitions like recommended in may of the guides for Galaxy Ace.
Unfortunately again I was unable to boot and the partitions become unmountable leading to yet again flashing back to base unbranded, then flashing stock carrier branded firmware (this has the correct modem for the carrier and region).
At this point I retired the idea of custom firmware. I will later root the device and just leave it on 2.3.7 and do internal/external SDcard swap and flash a theme and maybe a few compatible APKs from newer stock firmwares (at least ICS) to achieve the functionality I was hoping to have by flashing and using ICS. I found the best and most simplest way of achieving this was through Moto-Chopper Root method and adb, most of the documented ways of achieving root on the Ace don't work for the S5830V for some reason. So I will stick with what works.
NightRaven49 said:
The tar.md5 file has to split into the PDA, CSC, Modem and PIT files using Odinatrix. Search for it.
Click to expand...
Click to collapse
Thanks for the tip. :good: I have downloaded this ready now, so I will investigate how this goes? It looks very similar to a application I already use TAR.MD5_PACKAGER however I see it has an option for extracting from .tar.md5 files that have malformed header information. So that sounds like it should do the trick!:fingers-crossed: Do you think that this is maybe intensional as a means of stopping people like us from building custom firmware packages?
I mean the .tar.md5 package flashes perfectly as it should do which is very surprising seeming .md5 signature is very easily broken when you rename the file and you have not even opened it. That was what lead me to flashing it in the first place, I mean I figured that if the .tar.md5 was so corrupt as I believed it was, then the worst that can happen will be Odin will spit an error message and not proceed i.e. it won't even attempt to flash the said firmware!
Myself if I download any firmware that doesn't flash and fails due to md5 error, I immediately open it up and inspect it and unless it was extremely difficult to obtain (I have waited close to 30 hours once for an old firmware package to download from the only source I could find - but regardless if it was damaged or not I only wanted the old bootloader so I could integrate it into a new firmware package so the passing md5 was relatively unimportant), I would just re-download it again.
The fact that ALL of these packages for S5830I are like this (regardless of what browser or means I downloaded the package) and the fact that they DO in fact flash like normal packages, and the phone returns to 100% factory condition; tells me that this does look like a means of discouraging custom firmware developers? hmmm
NightRaven49 said:
The Odin specific for Ace you stated above might be for GT-S5830. For the variants running the Broadcom BCM21553 the Odin version to use is v1.84. Odin v3.07 is more like a universal Odin that works on most devices.
Click to expand...
Click to collapse
The device is actually a S5830V...the V devices are relatively undocumented, but they are essentially just the same as the more common i/M variants. I did my homework first with this, and I can most certainly attest that it is NOT the S5830. I wouldn't attempt flashing S5830 firmware, also S5830i firmware boots and functions as normal and has signal albeit not so strong when the modem is not for our carrier and/or region, but function none the less.
NightRaven49 said:
I don't know about this.
Click to expand...
Click to collapse
Well give the fact that I had performed so many download of firmware that I initially believed to be corrupt I was unable to extract the PIT (or in the case of the generic Ace OPS file) from the firmwares.
Being the fact that there was little known about the S5830V I was unsure if to proceed of not? There are few reports on the device and most of them were of owners bricking their device, only 1 report I know of where a V owner claimed he flashed S5830i firmware without a hitch, again he was not from Australia where I am from, so I was flying blind and scared I was going to brick the device.
At the very least if I had a PIT file I could analyse it and could manually make image backup of the EFS/IMEI partition straight after rooting the phone. I have looked already at scripts that scan the whole emmc and I hit a snag when the kernel I am using is not insecure i.e. adb cannot run as root. I have root and confirmed with root checker app but terminal emulator and/or command line are unable to obtain root
Anyway to shed some light for you EFS Pro is a means of doing this that works on most Samsung devices....just not the Ace as far as I can tell.
Yes I am already aware that there is Galaxy Toolbox and I had actually gone ahead and done all that already,but an incident more recently where I had a device I was repairing with a wiped IMEI and it actually refused to boot. This becomes a hassle when restoring the IMEI cause in order to have Galaxy Toolbox you need to be booted and rooted. I wasted a whole day repairing the IMEI. So pretty much the message here is what good is Galaxy Toolbox to me restoring the IMEI if it can't boot? NONE!
I contacted the developer weeks ago and explained my situation and he is still yet to respond. I explained that I had a V variant of the Ace and wanted to ensure I had all bases covered. I requested information on how I could open the IMEI manually outside of the Galaxy Toolbox in the case that it would not boot (as this was how I restored the other device last week and it worked), unfortunately I am still yet to hear a response form him? Slack.
When I obtain this information I will share it here on XDA in the hopes that people in Australia with this variant will search and find some info on it. This is also why I am making this post here so detailed for folks like me who have been searching fruitlessly for answers.
My thoughts are that maybe there is something still not 100% the same between the i and the V because all custom firmwares I tried made for the S5830i never worked?
There is maybe an issue with how they are scripting their installs that is causing issues, but it is worrying enough that flashing so far has lead to partitions becoming corrupted very easily. I have had this before with my own phone more recently because a dev made a simple mistake in an updater script that called an explicit partition by mounting point ID and not by a more generic mounting point like "/system", "system" which lead to lost IMEI and bricked phone.
I am not blaming the dev though because it is easy to assume that a even though the mounting was non-specific for my device and the partition being called was not actually the EFS, it should not have corrupted my EFS....but that is not true, so a discovery was made and a lesson learned from all this. I managed to revive my device and it lived to fight another day, but simple mistakes made in ignorance or lack of information can still be costly mistakes. Need I say more.
I will report back when I have got a proper partition map for the S5830V and all will be happy days
I don't feel like quoting anymore, but I do spot some anomalies.
1) ...we don't have CWM 6.0.0.x. Are you sure you used the 5830i CWM, not the 5830?
2) I was referring to some other version of Odin when you said the Odin version specific to Ace. Which version were you using then?
3) I don't see how rio's multi-formatter can render the system partitions unmountable. In that case try lopicl.00's EXT4 formatter. Go search for it. After formatting flash Biel's Specific Basic kernel.
also you were asking a question, so naturally this should be in Q&A.