Database Info

[Rom]Stock Rooted Deodex 2.3.6 IS NOW UP!

thanks shady for the toggles and letting me use your theme. After installing boot will take approx 3-5 mins. Update superuser from the market.
Deodexed, Rooted, Overclocked, Webtop via HDMI mod, Toggles, Zipaligned.
....Flash at your own risk....
WIPE DATA/FACTORY RESET
http://depositfiles.com/files/wk7i3b1n1 <----Stock Rooted 2.3.5
http://www.mediafire.com/?rt4v29ompo3am6s <----Alt Link 2.3.5
http://www.multiupload.com/IZVCVPRNGJ <----Alt Link 2.3.5
Good luck and let me know about any issues not already covered.
ps. voice search and maps would not deodex so get them from the market.
http://forum.xda-developers.com/showthread.php?t=1385283
^--This works for us. I cant tell you how many times this has saved me from using rsd just b/c of a bootloop.
There seems to be some confusion with overclocking, If you don't understand it please read through this thread.
http://forum.xda-developers.com/showthread.php?t=1341514
___________________________________________________________________
Stock Rooted Deodxed 2.3.6
http://depositfiles.com/files/dmi40o4qx <----2.3.6
^---This is a cwm backup. You will need to wipe data/factory reset then restore the backup. Extract zip to root of sd card
________________________________
***********MD5**************
StockRootedDeodex 2.3.5 36E1DE744C0144C70AFF4BFD624BA369 *StockRootedOcWebDeodex.zip
StockRootedDeodex 2.3.6 BA6AF46EF4A2E0904422E6F73E8893AE *236_Rooted_Deodex_Do_No_Flash.rar

[Theme's]
1.) adb push framework-res.apk /mnt/sdcard
2.) adb push SystemUI.apk /mnt/sdcard
3.) adb push Settings.apk /mnt/sdcard
4.) adb push BlurPhone.apk /mnt/sdcard
5.) adb push BlurDialer.apk /mnt/sdcard
6.) adb push GoogleQuickSearchBox.apk /mnt/sdcard
7.) su
8.) mount -o rw,remount /dev/null /system
9.) cp /sdcard/framework-res.apk /system/framework
10.) cp /sdcard/SystemUI.apk /system/app (case sensitive)
11.) cp /sdcard/Settings.apk /system/app (case sensitive)
12.)cp /sdcard/BlurPhone.apk /system/app (case sensitive)
13.)cp /sdcard/BlurDialer.apk /system/app (case sensitive)
14.)cp /sdcard/GoogleQuickSearchBox.apk /system/app (case sensitive)
15.) reboot
16.) click thanks!
http://db.tt/qd0dVE0p <--Ics/Artic
Flashable Zip http://www.multiupload.com/9ANWSIAPA9
http://db.tt/21dhrctR <--ICS
Flashable Zip http://www.multiupload.com/SN3DKIIVNI
(Ports from shadys various themes)
***Wanna be sure your not going to boot loop? Make a backup and install the cwm on boot linked above. Commands are the same in recovery omitting 5&6 instead go to mounts and mount /system***
**The first 2 pictures are from Ics/artic, The last 4 pics are from ICS***

You peronally use the unofficial atrix 2 bootstrap for flashing correct?

Awesome man. I'm gonna hide in a corner and see what happens for now, but definitely exciting news.

Jimmy273 said:
You peronally use the unofficial atrix 2 bootstrap for flashing correct?
Click to expand...
Click to collapse
Yes
Everything downloaded well and is up and running!!! BTW boot took no longer than a usual boot on mine
Could you give some clarification on some of the notification drop down toggles and what they are? What is the little sun like icon and the circle arrow icon?
Will leave feedback as more proper use comes

I would guess the sun icon is brightness control and the circle arrow is sync
Sent from my MB865 using xda premium

Flashing it right now!

Jimmy273 said:
You peronally use the unofficial atrix 2 bootstrap for flashing correct?
Click to expand...
Click to collapse
Yes sir I do.

We need some step by step on how to install this ROM.

already flashed, so far so good.
Here is what i dou need to root first)
1: go here and download Bootstrap Recovery
http://forum.xda-developers.com/showthread.php?t=1346977
2: Download the rom and put it on sd card
3: install the app and boot into recovery.
4: do a backup first
5: factory reset
6: flash the rom
7: reboot!
last thing !!!!! Flash at your own risk!!!!!!!!!!
OH almost forgot. HAPPY NEW YEAR!!!!!

Just flashed so far so good
Sent from my MB865 using xda premium

What is this overclocked to and what other changes does it have. Maybe someone thats done it can do a video demonstration on youtube.

Running great so far..awesome job..thought I was gonna have to wait months for something..on point..just came reluctantly over from a g2x due to T-Mobiles lack of sympathy for the broke...any way to get instructions on how to overclock via terminal emulator?
Sent from my MB865 using xda premium

Are we able to restore Nandroid backups successfully? I read in the other thread that .img files were not present in the Nandroid backup. Has that been resolved?

devsk said:
Are we able to restore Nandroid backups successfully? I read in the other thread that .img files were not present in the Nandroid backup. Has that been resolved?
Click to expand...
Click to collapse
Yup! You can use it like you would any other cwm.

pretty much all cwm features are working, nandroid backup, restore, flash rom, wipe......

Thanks for the ROM!
So, let's see if I understand how this works: the only thing we can't do yet without unlocking the bootloader is to install a different kernel. Everything else can be changed, right?

devsk said:
Are we able to restore Nandroid backups successfully? I read in the other thread that .img files were not present in the Nandroid backup. Has that been resolved?
Click to expand...
Click to collapse
Yup! Everything restored perfectly for me...
Sent from my MB865 using xda premium

Its telling me that its at 300-1000Mhz. I don't believe its OC'd? Otherwise, LOVING it. Thanks a ton.
Sent from my MB865 using XDA App
---------- Post added at 09:40 AM ---------- Previous post was at 09:36 AM ----------
Zoide_ said:
Thanks for the ROM!
So, let's see if I understand how this works: the only thing we can't do yet without unlocking the bootloader is to install a different kernel. Everything else can be changed, right?
Click to expand...
Click to collapse
Can't flash new radios either.

Calundle said:
Its telling me that its at 300-1000Mhz. I don't believe its OC'd? Otherwise, LOVING it. Thanks a ton.
Click to expand...
Click to collapse
I think right now its not, but the scripting is there so if you want the OC you have to do it manually via terminal emulator or ADB shell.
I've had no problems as well. Cant wait to see the OC and a theme on it BTW loving the notification toggles!!! If airplane mode was included it would be set!!!

[Q] CWM recovery filenames

This is a general CWM question but I could not find any place better to post on XDA, so excuse this if incorrect location.
I have flashed all the Skyrocket ICS roms in the past few days to see which I liked best. Before I flashed a new one, I would make a CWM backup of the current one. Wanting to easily be able to identify the files, I appended the rom name to the end of the CWM filenames after deleting all the characters after the date, which appeared to be a GMT time stamp. Now, when I try to restore any of those files, I get an MD5 checksum error. I am only assuming that this is due to changing the filename and not some other problem. Anyone have any ideas on how to fix this? TIA.

phoneturf said:
This is a general CWM question but I could not find any place better to post on XDA, so excuse this if incorrect location.
I have flashed all the Skyrocket ICS roms in the past few days to see which I liked best. Before I flashed a new one, I would make a CWM backup of the current one. Wanting to easily be able to identify the files, I appended the rom name to the end of the CWM filenames after deleting all the characters after the date, which appeared to be a GMT time stamp. Now, when I try to restore any of those files, I get an MD5 checksum error. I am only assuming that this is due to changing the filename and not some other problem. Anyone have any ideas on how to fix this? TIA.
Click to expand...
Click to collapse
Are you talking about the folder name? Because that shouldnt affect it. Inside the folder that is created for each backup, there are backup files which dont have any dates/times in the filename itself.

I vaguely remember reading about this, but I can't recall how it was resolved. Try updating your can to 5.5.0.4 Touch or 5.8.1.3 (?? something along those lines) and seeing if that resolves it. Outside if that I must ask the obvious, did u Google "md5 checksum error cwm"?

Are you using the same CWM version as you did when you backed up? If you didnt, then thats one reason. You have to stay on the same CWM version, many of these CWM versions floating around have different fixes in there.
One way around this is to go to Advanced Restore and restore all the IMG files from there.
Dixit

ihtfp69 said:
I figured I would post this fix here in case anyone else ran into this problem. This is assuming you did not change the folder names and let Clockworkmod create them. I haven't had it happen until today, but it's not a nice message to see when you are trying to do a restore.
Code:
Checking MD5 sums...
MD5 mismatch!
Do this to fix:
To fix this problem use the code below. Substitute the final folder name for the backup you need to fix.
Code:
adb shell
# cd /sdcard/clockworkmod/backup/2010-06-29.20.22.53
# rm nandroid.md5
# md5sum *img > nandroid.md5
When that finishes, re-run the restore and everything should be fine.
NOTE: As rpearl stated, there could be something really wrong with your nandroid, so use this tutorial as a learning experience and not a fix-all. In my case, everything was fine after restoring. However, that may not always be the case. Do this with caution.
Click to expand...
Click to collapse
Use this method to potentially fix.

dixit said:
Are you using the same CWM version as you did when you backed up?
Dixit
Click to expand...
Click to collapse
That is correct on most of them. I updated to CWM Touch for the last one, but it did not restore either. To check this out, I just did a backup and without changing the name did a restore and it worked fine. The thing that was odd in the backups that would not restore was that it immediately bombed out of the checksum each time as if it was checking the name itself first.

That is brilliant. I did not realize you could generate the MD5 from ADB and stick it right into the folder. Thanks!

The few times this md5 mis-match has happened to me was because (a) the backup was actually messed up (check folder size) probably due to corruption or (b) my SD card was out of space. I've always renamed my backup set similar to yours (I append the ROM name) and it never affects the restore.

bdbx18 said:
The few times this md5 mis-match has happened to me was because (a) the backup was actually messed up (check folder size) probably due to corruption or (b) my SD card was out of space. I've always renamed my backup set similar to yours (I append the ROM name) and it never affects the restore.
Click to expand...
Click to collapse
Are you using touch or standard CWM? I wonder if this only happens in touch version. I will try this in the next few days.

I changed the name of one of the backups I created with CWM touch and it restored fine using touch. I suppose my earlier problem may have been trying to restore a backup created with old CWM using touch version.

well since you are on the subject cwm touch im making a nanadroid backup of my current ics rom right now as i speak. i started about an hour ago and its still on the backing up data part. when i used the older version to make backups i dont remember it taking this long. have any of you had cwm touch take well its been a little over an hour now? i do have more apps on my phone now than i did the last time i made a backup would that matter? should i just jerk the battery out and go back to the older version of cwm i was using? thanks ahead of time for any advice / help you may give i would appreciate it. im trying to backup this rom cause i want to flash a different modem cause the ics modem form the leak is crap and need a backup in case it dont work..

garydv2002 said:
well since you are on the subject cwm touch im making a nanadroid backup of my current ics rom right now as i speak. i started about an hour ago and its still on the backing up data part. when i used the older version to make backups i dont remember it taking this long. have any of you had cwm touch take well its been a little over an hour now? i do have more apps on my phone now than i did the last time i made a backup would that matter? should i just jerk the battery out and go back to the older version of cwm i was using? thanks ahead of time for any advice / help you may give i would appreciate it. im trying to backup this rom cause i want to flash a different modem cause the ics modem form the leak is crap and need a backup in case it dont work..
Click to expand...
Click to collapse
If you are using sk8erwitskil version of the CWM touch (ClockworkMod TOUCH 5.5.0.4 v3.5) then most likely you didnt follow one of the directions on the front page. This is a known issue. Here it is again. You need to create that file on the location you backing upto.
For CWM to recognize the .hidenandroidprogress file you need to boot into CWM and go to mounts and storage>>mount /sdcard then go back to backup & restore and make a restore and it should work everytime (as long as you do the steps in that order and you have the .hidenandroidprogress file in /sdcard/clockworkmod & /sdcard/external_sd/clockworkmod folders)
There is a known bug in ClockworkMod 5.5.0.4 that long file names can POSSIBLY cause backups to hang. There is a solution/workaround:
•boot into recovery
•try to make a backup (no matter if it passes or fails proceed to next step)
•either through terminal emulator or through adb run the following command EXACTLY:
Code:
touch /sdcard/clockworkmod/.hidenandroidprogress
•if you are backing up to external sdcard then run the following:
Code:
touch /sdcard/external_sd/clockworkmod/.hidenandroidprogress

im using 5.8.1.3 hercules that i got from the dev section. is this a known issue with it to?

garydv2002 said:
im using 5.8.1.3 hercules that i got from the dev section. is this a known issue with it to?
Click to expand...
Click to collapse
Not sure, I used that for awhile but then went back to the other touch and Ive had those two files still in my directories.
I would go ahead and create those two files (one for internal SD and one for external SD if you got one you are using that is) and try it again. Make sure you call that file exactly the way it is, or copy/paste the code identically if you do it through ADB.
Dixit

garydv2002 said:
im using 5.8.1.3 hercules that i got from the dev section. is this a known issue with it to?
Click to expand...
Click to collapse
I use that one, takes less than 5 minutes on my class 10 sd.
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2

Well the crazy thing is after sitting there over an hour waiting I finally took out the battery and even though it never said complete all the files are there but I still don't trust that it made a good backup so I deleted those files tried putting in the code above and it still would not work so I flashed back to version 5.0.2.0 thats not touch and it made a perfect backup in under 2 minutes. Might be one of those it just ain't gonna work right on this specific phone thing or it could be the little green gremlins at it again lol... who knows.. I'll just wait for new version of touch to come along and try it. It won't be long till a newer greater version comes along as fast as technology is going today.. thanks for the help. I'm learning more and more each day from you guys on xda.....
Sent from my SAMSUNG-SGH-I727 using XDA

Not sure if this is the cause of the issue but for nandroid backups you can't make a folder name with spaces otherwise you will get an md5 sum error. Try renaming the folder with underscores instead of spaces

[HOW-TO] Fix soft brick & error mounting sdcard

EDIT: I solved my own problem. Scroll down to post #8 for the solution.
My problem was that my phone (T-Mobile USA HTC One S) would not boot into ICS anymore, but I was still able to get into recovery (CWM), yet I had no access to the sdcard ("unable to mount /sdcard").
Post #8 below tells you how you can restore access to the sdcard in CWM so that you can push a ROM zip file to the sdcard via adb.
-J

Have you made any nandroids? If you have maybe you can restore. Also check in the download file in cwm that is possible place where that file may be.
Sent from my myTouch 4G Slide using xda premium

archie53 said:
Have you made any nandroids? If you have maybe you can restore. Also check in the download file in cwm that is possible place where that file may be.
Sent from my myTouch 4G Slide using xda premium
Click to expand...
Click to collapse
Unfortunately I didn't have the foresight to make a nandroid backup. My previous phone was a Samsung Galaxy S 4G, which, like most Android phones, has a removable SD-Card that stuff can be copied onto (and then flashed). Not so here obviously.
Is it even possible to push files to the sdcard using the method I tried when in CWM?

When you push the file via ADB, have you tried placing it into a folder that you know is on the /sdcard?

joshnichols189 said:
When you push the file via ADB, have you tried placing it into a folder that you know is on the /sdcard?
Click to expand...
Click to collapse
It just got worse. I got the idea to format all partitions (data, system, cache, sdcard) through CWM, and now CWM can't even mount /sdcard/ anymore...

I had to do the same thing:
adb push "NameOfFile.zip /sdcard
then go to install from zip.
Look on sd card and it will be there.
I always rename the zip files to there can be less errors.
you can also do
adb shell pull "nameOfFile.zip /sdcard
make sure the zip file is where your adb and fastboot is

My problem is CWM can't mount the /sdcard directory, so I can't flash the new OS. Is there anybody that knows how to recover from that problem?

LuckyMethod said:
My problem is CWM can't mount the /sdcard directory, so I can't flash the new OS. Is there anybody that knows how to recover from that problem?
Click to expand...
Click to collapse
Yes, I just fixed my problem yesterday after some serious trial-and-error.
1) Use the All-in-One-Kit and flash your recovery back to stock
2) Boot into the bootloader and choose to "clear storage" and afterwards to reset to factory defaults.
3) Go back to the all-in-one-kit and flash a CWM recovery version again.
4) Reboot into recovery (CWM). Your /sdcard should now be mounted and visible.
5) Now, try the UTB rom (it worked for me), rename the zip file to something short (i.e. utb.zip), and push it to the sdcard using adb as follows:
Code:
adb push utb.zip /sdcard
6) While still in CWM, flash the zip.
The trick here is that only the stock recovery is capable of restoring access to the sdcard by it's proprietary "clear storage" option.
Good luck!
-J

If that doesn't work an easy fix is boot into bootloader, goto fastboot and use "fastboot flash boot boot.img" and so fouth. In the dev section I seen a stock tmobile naindroid. Download it and you'll have your data.img and boot.img. You should be able to flash them without needing to push to /sdcard. letme know how it works
I know you fixed this already just thought this still might help

cannondale0815 said:
Yes, I just fixed my problem yesterday after some serious trial-and-error.
1) Use the All-in-One-Kit and flash your recovery back to stock
...cut...
-J
Click to expand...
Click to collapse
It worked like a charm, thank you very much. You saved my life, I was in a time crunch.

LuckyMethod said:
It worked like a charm, thank you very much. You saved my life, I was in a time crunch.
Click to expand...
Click to collapse
Happy it worked for you. Took me several days to figure this out
Sent from my HTC One S using xda premium

I too formatted my sd card but a little trial and error and using your direction, I am back in business ! Thank you , this should really be a sticky
Sent from my HTC VLE_U using xda premium

j3.cole said:
I too formatted my sd card but a little trial and error and using your direction, I am back in business ! Thank you , this should really be a sticky
Sent from my HTC VLE_U using xda premium
Click to expand...
Click to collapse
Thank you. I changed the title and original post to make it easier for people to find this thread.

I am going to try this trick tomorrow after having spent endless hours trying to fdisk/parted via adb, and flashing endless roms and updates to no avail. I will post the outcome here. I really hope this works for me like it has for you guys...

mrmoretti said:
I am going to try this trick tomorrow after having spent endless hours trying to fdisk/parted via adb, and flashing endless roms and updates to no avail. I will post the outcome here. I really hope this works for me like it has for you guys...
Click to expand...
Click to collapse
IT WORKED! This thread should be made sticky! I'm sure a lot of users who have HTC One S with built-in SD will have the same issue when mucking about with their phone. Thank you!

Bump, as too many people are having this problem.
Sent from my HTC One S using Tapatalk 2

cannondale0815 said:
Yes, I just fixed my problem yesterday after some serious trial-and-error.
1) Use the All-in-One-Kit and flash your recovery back to stock
2) Boot into the bootloader and choose to "clear storage" and afterwards to reset to factory defaults.
3) Go back to the all-in-one-kit and flash a CWM recovery version again.
4) Reboot into recovery (CWM). Your /sdcard should now be mounted and visible.
5) Now, try the UTB rom (it worked for me), rename the zip file to something short (i.e. utb.zip), and push it to the sdcard using adb as follows:
Code:
adb push utb.zip /sdcard
6) While still in CWM, flash the zip.
The trick here is that only the stock recovery is capable of restoring access to the sdcard by it's proprietary "clear storage" option.
Good luck!
-J
Click to expand...
Click to collapse
THANK YOU SO MUCH! THIS WORKED PERFECTLY!
This should definitely be included in a stickied guide for people like me who have managed to corrupt their recoveries.

Got it after several tries

hey guys i have the same problem, the solution sort of work, but when i try to do a adb push its show it was sucessful but when i do to flash it i cant see it.

yasir_jan87 said:
hey guys i have the same problem, the solution sort of work, but when i try to do a adb push its show it was sucessful but when i do to flash it i cant see it.
Click to expand...
Click to collapse
Try to shorten the filename, i.e. "rom.zip".
And try this slightly modified command instead:
adb push rom.zip /sdcard/rom.zip
Sent from my aokp_tenderloin using Tapatalk 2

[DEV] CM7 for Karbonn A9

I managed to successfully compile CWM Recovery from sources for A9, but with a few issues (key-mapping where touch buttons don't work, etc)
Decided to take the jump to compiling CM.
Modified the extract-files from sgs2 but I have no knowledge when it comes to libraries, proprietary files, 'blobs', what the options in the makefiles mean,etc.
I have absolutely no idea what I'm supposed to do next, as compiling for unsupported devices doesn't give me many search results. I have the CyanogenMod GB branch synced, and a device tree for A9 set up, with a few file modifications done.
Any and all help, references, links to explanations are welcome.
Managed to compile it, finally, check posts below.
Sources: https://github.com/Siarc/a9

Shark- said:
I managed to successfully compile CWM Recovery from sources for A9, but with a few issues (key-mapping where touch buttons don't work, etc)
Decided to take the jump to compiling CM.
Modified the extract-files from sgs2 but I have no knowledge when it comes to libraries, proprietary files, 'blobs', what the options in the makefiles mean,etc.
I have absolutely no idea what I'm supposed to do next, as compiling for unsupported devices doesn't give me many search results. I have the CyanogenMod GB branch synced, and a device tree for A9 set up, with a few file modifications done.
Any and all help, references, links to explanations are welcome.
Sources: https://github.com/Siarc/a9
Click to expand...
Click to collapse
Dude, the only help i could give is test the ROM , let me know when you want it and i will be more than happy to help :fingers-crossed:

I've spent a lot of time, and it's simply not worth it, cannot even manage to get it to compile in the right directory. I can't believe there are so many people who have the knowledge but not one single reply.

CM7!
Flash at your OWN RISK.
I will not be held responsible if you brick/mess up your device.
This is meant for the A9, not anything else.
This is an experimental build, I cannot even guarantee that it will boot.
==========================================================================
Download : http://www.mediafire.com/?f85rdpx0kvbtmvh
Code:
SHA1: dd40f0cef5b40d8a8b5b3966e29074889bad9b8e
MD5: c2a28a1d012f2b3a4a1f79ead24c8d66
I'll be damned if you even get to the standby screen. I don't have the time to test it right now and restore backups if it doesn't work.
If it doesn't work, the screen will probably go blank and you should reboot into recovery (or you may get a bootloop)
If you think it has got past boot, try and run logcat and dmesg and post back the logs so I can know what went wrong.
Using dmesg and logcat: http://www.flashmyandroid.com/forum...ogcat-and-dmesg-outputs-for-trouble-shooting-!
Before flashing:
Backup all sdcard contents.
Make nandroid backup via CWM, test restore it, copy to computer just in case.
-------------------------------------------------------------------------------------------------------------
Make sure you have a nandroid backup (and test it out! if you get MD5 mismatch like I did, you'll be spending a lot more time getting your phone restored) on your phone /sdcard as well as your computer.
A microSD card reader (in case the sdcard gets wiped and you have no means of transferring your nandroid backup)
-------------------------------------------------------------------------------------------------------------
Instructions:
Place zip file on /sdcard
Flash zip via CWM (If you don't already have it, this is the one: http://www.mediafire.com/?aen9w6uinz923hy)
Wipe /data, /cache and dalvik-cache from CWM.
Reboot
Used the stock kernel, device tree is over here: https://github.com/Siarc/a9
[I have also tried manually flashing a previous build's system image, it wouldn't work, restored nandroid, everything back to normal.]
Only testers who are comfortable flashing ROMs and have a computer with fastboot working should try it out, in case there is a need to flash the recovery partition.

Shark- said:
Flash at your OWN RISK.
I will not be held responsible if you brick/mess up your device.
This is meant for the A9, not anything else.
This is an experimental build, I cannot even guarantee that it will boot.
==========================================================================
Download : http://www.mediafire.com/?f85rdpx0kvbtmvh
Code:
SHA1: dd40f0cef5b40d8a8b5b3966e29074889bad9b8e
MD5: c2a28a1d012f2b3a4a1f79ead24c8d66
I'll be damned if you even get to the standby screen. I don't have the time to test it right now and restore backups if it doesn't work.
If it doesn't work, the screen will probably go blank and you should reboot into recovery (or you may get a bootloop)
If you think it has got past boot, try and run logcat and dmesg and post back the logs so I can know what went wrong.
Using dmesg and logcat: http://www.flashmyandroid.com/forum...ogcat-and-dmesg-outputs-for-trouble-shooting-!
Before flashing:
Backup all sdcard contents.
Make nandroid backup via CWM, test restore it, copy to computer just in case.
-------------------------------------------------------------------------------------------------------------
Make sure you have a nandroid backup (and test it out! if you get MD5 mismatch like I did, you'll be spending a lot more time getting your phone restored) on your phone /sdcard as well as your computer.
A microSD card reader (in case the sdcard gets wiped and you have no means of transferring your nandroid backup)
-------------------------------------------------------------------------------------------------------------
Instructions:
Place zip file on /sdcard
Flash zip via CWM (If you don't already have it, this is the one: http://www.mediafire.com/?aen9w6uinz923hy)
Wipe /data, /cache and dalvik-cache from CWM.
Reboot
Used the stock kernel, device tree is over here: https://github.com/Siarc/a9
[I have also tried manually flashing a previous build's system image, it wouldn't work, restored nandroid, everything back to normal.]
Only testers who are comfortable flashing ROMs and have a computer with fastboot working should try it out, in case there is a need to flash the recovery partition.
Click to expand...
Click to collapse
I will test it bro..
thnks for compiling.

Shark- said:
Flash at your OWN RISK.
I will not be held responsible if you brick/mess up your device.
This is meant for the A9, not anything else.
This is an experimental build, I cannot even guarantee that it will boot.
==========================================================================
Download : http://www.mediafire.com/?f85rdpx0kvbtmvh
Code:
SHA1: dd40f0cef5b40d8a8b5b3966e29074889bad9b8e
MD5: c2a28a1d012f2b3a4a1f79ead24c8d66
I'll be damned if you even get to the standby screen. I don't have the time to test it right now and restore backups if it doesn't work.
If it doesn't work, the screen will probably go blank and you should reboot into recovery (or you may get a bootloop)
If you think it has got past boot, try and run logcat and dmesg and post back the logs so I can know what went wrong.
Using dmesg and logcat: http://www.flashmyandroid.com/forum...ogcat-and-dmesg-outputs-for-trouble-shooting-!
Before flashing:
Backup all sdcard contents.
Make nandroid backup via CWM, test restore it, copy to computer just in case.
-------------------------------------------------------------------------------------------------------------
Make sure you have a nandroid backup (and test it out! if you get MD5 mismatch like I did, you'll be spending a lot more time getting your phone restored) on your phone /sdcard as well as your computer.
A microSD card reader (in case the sdcard gets wiped and you have no means of transferring your nandroid backup)
-------------------------------------------------------------------------------------------------------------
Instructions:
Place zip file on /sdcard
Flash zip via CWM (If you don't already have it, this is the one: http://www.mediafire.com/?aen9w6uinz923hy)
Wipe /data, /cache and dalvik-cache from CWM.
Reboot
Used the stock kernel, device tree is over here: https://github.com/Siarc/a9
[I have also tried manually flashing a previous build's system image, it wouldn't work, restored nandroid, everything back to normal.]
Only testers who are comfortable flashing ROMs and have a computer with fastboot working should try it out, in case there is a need to flash the recovery partition.
Click to expand...
Click to collapse
I did as u said..
i wiped data / chache/ delvik cache .. But not able to install..
i m writing the exact error...
" Installing update..
assert failed : getprop("ro.product.device")== "a9" || getprop("ro.build.product") =="a9" ||getprop("ro.product.board")== "a9"
E: Error in /sdcard/cm7-20120911-UNOFFICIAL-a9.zip
(status 7)
Installation aborted. "

vijetaverma said:
I did as u said..
i wiped data / chache/ delvik cache .. But not able to install..
i m writing the exact error...
" Installing update..
assert failed : getprop("ro.product.device")== "a9" || getprop("ro.build.product") =="a9" ||getprop("ro.product.board")== "a9"
E: Error in /sdcard/cm7-20120911-UNOFFICIAL-a9.zip
(status 7)
Installation aborted. "
Click to expand...
Click to collapse
In the /system directory, edit the build.prop file and add this line:
Code:
ro.build.product=a9
Make sure it persists after a reboot.

Great work Friend's
Shark- said:
In the /system directory, edit the build.prop file and add this line:
Code:
ro.build.product=a9
Make sure it persists after a reboot.
Click to expand...
Click to collapse
Bro please reply fast cant Waite now.I also want to install cm7

Shark- said:
In the /system directory, edit the build.prop file and add this line:
Code:
ro.build.product=a9
Make sure it persists after a reboot.
Click to expand...
Click to collapse
just woke up..
I m adding that line.. will Post result in a while
---------- Post added at 10:28 AM ---------- Previous post was at 10:00 AM ----------
Still not able to install..
Error
"
same as previous one..
(status 7)
Installation aborted
"

Any more info like the previous one? Ro.build anything?
Sent from my A9 using xda app-developers app

Shark- said:
Any more info like the previous one? Ro.build anything?
Sent from my A9 using xda app-developers app
Click to expand...
Click to collapse
all same as before..nothing changed..

Can you post the complete log
Sent from my A9 using xda app-developers app

There is no systemui.apk in the build, so it's never gonna boot up
I think without kernel sources developing cm7 is impossible.
Anyway I really appreciate the effort you took in trying to compile cm7 for our device
Sent from my A9 using xda app-developers app

SystemUI can be copied in the makefiles , and I wouldn't say its impossible to compile, just very difficult.
Sent from my A9 using xda app-developers app

No phone.apk, conversations.apk camera.apk, systemui.And many permissions xml file are missing.You can't use stock apk instead of these, they need to be build specially for our device.
The reason why I said it is impossible is I have seen very good devs finding it very difficult to build cm7 for devices having kernel source released.our device don't even have kernel source available.Normal gingerbread kernel without any modification won't boot up cm7.
Sent from my A9 using xda app-developers app

Well thanks for the encouragement
Sent from my A9 using xda app-developers app

mahfoozceecy said:
There is no systemui.apk in the build, so it's never gonna boot up
I think without kernel sources developing cm7 is impossible.
Anyway I really appreciate the effort you took in trying to compile cm7 for our device
Sent from my A9 using xda app-developers app
Click to expand...
Click to collapse
Shark- said:
SystemUI can be copied in the makefiles , and I wouldn't say its impossible to compile, just very difficult.
Sent from my A9 using xda app-developers app
Click to expand...
Click to collapse
mahfoozceecy said:
No phone.apk, conversations.apk camera.apk, systemui.And many permissions xml file are missing.You can't use stock apk instead of these, they need to be build specially for our device.
The reason why I said it is impossible is I have seen very good devs finding it very difficult to build cm7 for devices having kernel source released.our device don't even have kernel source available.Normal gingerbread kernel without any modification won't boot up cm7.
Sent from my A9 using xda app-developers app
Click to expand...
Click to collapse
Shark- said:
Well thanks for the encouragement
Sent from my A9 using xda app-developers app
Click to expand...
Click to collapse
So guys is anyone working on CM7 for A9 ?

MiUi Rom released..
http://forum.xda-developers.com/showthread.php?p=41289727

how to tell if bootloader is unlocked after rooting...

followed this thread http://forum.xda-developers.com/showthread.php?t=2046439 yesterday to root my samsung galaxy s3 and unlock the bootloader, but i am unsure if it worked 100%. i know it is rooted because i dl'ed titanium backup and it works, but how do i tell if my bootloader is unlocked or not? did a search, couldn't find an answer, so i am asking here.

There's not really a concrete way to tell however if you reboot and the Samsung logo flashes by in a second then you're unlocked. Typically it sits for three to five seconds on this screen but once unlocked, this screen just flashes by.
Sent from my SCH-I535 using xda app-developers app

considering we all use the same unlocked aboot.img, it's pretty easy to concretely verify that you're bootloader is unlocked.
but im too stupid to write a script, and no one wants to do it because it's a bit longer than timing the samsung boot logo (which when you compare time-invested to information given, is pretty reliable)
basically involves comparing the md5 of the aboot.img of your phone to the known unlocked aboot.img (will try to find the terminal/adb shell commandsi posted before)
found it:
The unlocked md5 is: 0ba9ad45fc15cf3d62af7dd363686b3f
So if you pull a copy of your current aboot partition and save it to your sd card.
Run the following in ADB shell or terminal. Make sure you run it as superuser:
dd if=/dev/block/mmcblk0p5 of=/storage/sdcard0/aboot.img
That command will save an aboot.img to your internal sd. Check it's md5 and see if it matches.
Can run in adb:
md5 /storage/sdcard0/aboot.img
or
use any of the many md5 checking apps out there

SlimSnoopOS said:
There's not really a concrete way to tell however if you reboot and the Samsung logo flashes by in a second then you're unlocked. Typically it sits for three to five seconds on this screen but once unlocked, this screen just flashes by.
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
ok, cool, thanks! so it looks like the root took, but the bootloader didn't unlock. the samsung logo took 3 seconds to pass by. so what do i need to do now to unlock it? should i repeat the steps from what i did yesterday?

corbn89 said:
considering we all use the same unlocked aboot.img, it's pretty easy to concretely verify that you're bootloader is unlocked.
but im too stupid to write a script, and no one wants to do it because it's a bit longer than timing the samsung boot logo (which when you compare time-invested to information given, is pretty reliable)
basically involves comparing the md5 of the aboot.img of your phone to the known unlocked aboot.img (will try to find the terminal/adb shell commandsi posted before)
found it:
The unlocked md5 is: 0ba9ad45fc15cf3d62af7dd363686b3f
So if you pull a copy of your current aboot partition and save it to your sd card.
Run the following in ADB shell or terminal. Make sure you run it as superuser:
dd if=/dev/block/mmcblk0p5 of=/storage/sdcard0/aboot.img
That command will save an aboot.img to your internal sd. Check it's md5 and see if it matches.
Can run in adb:
md5 /storage/sdcard0/aboot.img
or
use any of the many md5 checking apps out there
Click to expand...
Click to collapse
I'm gonna bookmark this cuz this is a really good explanation. I don't ever suggest dd methods (nor memorize them) cuz I know a single typo could brick the device.
a.demarco said:
ok, cool, thanks! so it looks like the root took, but the bootloader didn't unlock. the samsung logo took 3 seconds to pass by. so what do i need to do now to unlock it? should i repeat the steps from what i did yesterday?
Click to expand...
Click to collapse
Just sideload EZ Unlock v1.2 and press the unlock button. You'll hear an audio confirmation and boom, unlocked.

ok, so now i am confused. i have the correct supersu+bootloader on the sd card, and the supersu app on the phone, but the samsung logo still takes a while to disappear.
edit: nevermind, got it working, samsung logo now just flashes by. thanks again for all your help!

SlimSnoopOS said:
I'm gonna bookmark this cuz this is a really good explanation. I don't ever suggest dd methods (nor memorize them) cuz I know a single typo could brick the device.
Just sideload EZ Unlock v1.2 and press the unlock button. You'll hear an audio confirmation and boom, unlocked.
Click to expand...
Click to collapse
Yep, it's pretty straightforward. I tested my unlocked bootloader with this. Haven't had a chance to tested while locked though (will have to wait till my next odin to stock).
But yeah, as long as no one switches the "if" and the "of" it should be safe (aka accidentally pasting something into the normally inaccessible partition rather than copying out to the sd)
---------- Post added at 10:32 AM ---------- Previous post was at 10:29 AM ----------
a.demarco said:
ok, so now i am confused. i have the correct supersu+bootloader on the sd card, and the supersu app on the phone, but the samsung logo still takes a while to disappear.
Click to expand...
Click to collapse
sometime that image doesn't take for whatever reason. just use the app slimsnoop os linked to, should do the trick

a.demarco said:
ok, so now i am confused. i have the correct supersu+bootloader on the sd card, and the supersu app on the phone, but the samsung logo still takes a while to disappear.
edit: nevermind, got it working, samsung logo now just flashes by. thanks again for all your help!
Click to expand...
Click to collapse
Great! Just so you know, you can uninstall EZ Unlock (if you installed it that is) and never use it again. You will not need it again unless you do the following which which will re-lock your bootloader:
1) take a Verizon OTA
2) Odin flash a stock image
Make sure to do a nandroid and happy flashing!

SlimSnoopOS said:
Great! Just so you know, you can uninstall EZ Unlock (if you installed it that is) and never use it again. You will not need it again unless you do the following which which will re-lock your bootloader:
1) take a Verizon OTA
2) Odin flash a stock image
Make sure to do a nandroid and happy flashing!
Click to expand...
Click to collapse
still learning all about this, i will have to search what a nandroid is. i am doing a backup currently using titanium backup (free version right now), and it seems to be working well.
i want to flash either the cm 10.1 or jellybeans v.15 i think, just gotta read more about them.

a.demarco said:
still learning all about this, i will have to search what a nandroid is. i am doing a backup currently using titanium backup (free version right now), and it seems to be working well.
i want to flash either the cm 10.1 or jellybeans v.15 i think, just gotta read more about them.
Click to expand...
Click to collapse
Ahh, you'll see a lot of terms thrown around like that haha here's a glossary of common terms taken from DroidStyle's guide in the dev section.
Basically a nandroid is a complete system or rom backup akin to a computer backup. You perform a nandroid in custom recovery (CWM or TWRP) however its labeled as "Backup" in both recoveries. "Nandroid" is just the common name for it. The reason you perform a nandroid is to have a safe point to restore your phone to if you flash a rom, kernel, or mod and your phone begins to misbehave. Before flashing your first rom, it's highly recommended that you perform a nandroid in your custom recovery and even save a copy on a computer so you always have that in two places. It may take about 1.5-2 GB's of space per backup so I wouldn't keep too many on your phone at a time.

SlimSnoopOS said:
Ahh, you'll see a lot of terms thrown around like that haha here's a glossary of common terms taken from DroidStyle's guide in the dev section.
Basically a nandroid is a complete system or rom backup akin to a computer backup. You perform a nandroid in custom recovery (CWM or TWRP) however its labeled as "Backup" in both recoveries. "Nandroid" is just the common name for it. The reason you perform a nandroid is to have a safe point to restore your phone to if you flash a rom, kernel, or mod and your phone begins to misbehave. Before flashing your first rom, it's highly recommended that you perform a nandroid in your custom recovery and even save a copy on a computer so you always have that in two places. It may take about 1.5-2 GB's of space per backup so I wouldn't keep too many on your phone at a time.
Click to expand...
Click to collapse
good to know... should i bother with titanium backup at all? or just boot into cwm and do a nandroid from there?

a.demarco said:
good to know... should i bother with titanium backup at all? or just boot into cwm and do a nandroid from there?
Click to expand...
Click to collapse
Perform both actually. Backup apps with TB so when you flash a rom you can restore apps at once if you actually like the rom. I typically restore a few apps when trying new roms then if I like the rom, I'll restore more apps. Backup with CWM so that in case you dislike the rom you flash, you can completely restore to your previous rom. They serve two similar functions yet distinctly different as well.

SlimSnoopOS said:
Perform both actually. Backup apps with TB so when you flash a rom you can restore apps at once if you actually like the rom. I typically restore a few apps when trying new roms then if I like the rom, I'll restore more apps. Backup with CWM so that in case you dislike the rom you flash, you can completely restore to your previous rom. They serve two similar functions yet distinctly different as well.
Click to expand...
Click to collapse
awesome, thank you for the help. doing the nandroid backup right now through cwm, backing it up to the external sd card so i can then save it to the computer.
so i should only use the tb to back up the apps? oops, i backed everything up on it, was wondering why it took so damn long!

a.demarco said:
awesome, thank you for the help. doing the nandroid backup right now through cwm, backing it up to the external sd card so i can then save it to the computer.
so i should only use the tb to back up the apps? oops, i backed everything up on it, was wondering why it took so damn long!
Click to expand...
Click to collapse
No problem! Yea, TB is useful for a lot once you have a grasp of the basic functions. Only backup user apps and do not backup/restore system apps. Depending on the number of apps and their storage size, backup time varies. You can always delete the previous TB backup files cuz its stored in the Titanium Backup folder of your internal or external sdcard. Doesn't hurt to copy that to a computer every once in awhile too.

corbn89 said:
considering we all use the same unlocked aboot.img, it's pretty easy to concretely verify that you're bootloader is unlocked.
but im too stupid to write a script, and no one wants to do it because it's a bit longer than timing the samsung boot logo (which when you compare time-invested to information given, is pretty reliable)
basically involves comparing the md5 of the aboot.img of your phone to the known unlocked aboot.img (will try to find the terminal/adb shell commandsi posted before)
found it:
The unlocked md5 is: 0ba9ad45fc15cf3d62af7dd363686b3f
So if you pull a copy of your current aboot partition and save it to your sd card.
Run the following in ADB shell or terminal. Make sure you run it as superuser:
dd if=/dev/block/mmcblk0p5 of=/storage/sdcard0/aboot.img
That command will save an aboot.img to your internal sd. Check it's md5 and see if it matches.
Can run in adb:
md5 /storage/sdcard0/aboot.img
or
use any of the many md5 checking apps out there
Click to expand...
Click to collapse
So when I start up terminal emulator, next to where it says "[email protected]:/ $" I type in su right? Then hit enter? Then on the following line I type: "dd if=/dev/block/mmcblk0p5 of=/storage/sdcard0/aboot.img"
After I type this a copy of aboot.img will be saved to my external memory card and from there I can match it up with the unlocked md5 and if it matches this garuntees that my bootloader is unlocked. Is this correct?
I'm a noob, please forgive me.

jricks said:
So when I start up terminal emulator, next to where it says "[email protected]:/ $" I type in su right? Then hit enter? Then on the following line I type: "dd if=/dev/block/mmcblk0p5 of=/storage/sdcard0/aboot.img"
Click to expand...
Click to collapse
Correct.
After I type this a copy of aboot.img will be saved to my external memory card and from there I can match it up with the unlocked md5 and if it matches this garuntees that my bootloader is unlocked. Is this correct?
I'm a noob, please forgive me.
Click to expand...
Click to collapse
It will save to your internal sdcard. sdcard0 = internal storage, sdcard1 = external sdcard.
Sent from my SCH-I535 using xda app-developers app

Much appreciated my friend.
Sent from my SCH-I535 using xda app-developers app

Let us know what your results are and which method you used to unlock.
I confirmed it on my phone that used the ez unlock app but multiple trials by others would be beneficial. Thanks

SlimSnoopOS said:
Correct.
It will save to your internal sdcard. sdcard0 = internal storage, sdcard1 = external sdcard.
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
I did everything mentioned above and it saved to my internal card however im unable to view it. What program do i to install to view it.
Sent from my SCH-I535 using xda app-developers app

You don't need to view it. You just need to run the file through a md5 checksum app or check the md5 with terminal or adb using the command I posted earlier