Hey guys, since I already saw it a couple of times now, that USB was broken and ppl cant unroot their phones using Smartflash then, I wanna make a ROM, that can be flashed by using CWM. Cause often ppl are able to access it still, but cant push data via USB.
What do we have to consider? I am using tantrums repack as a base http://forum.xda-developers.com/showthread.php?t=1554274.
I used the v20o version.
I think we need to remove /bin/su, /xbin/busybox, /app/superuser.apk. Also we need to remove symlinks. But I dont know which ones to remove...
Also we need the stock recovery.img, to get the original one back to the phone. ro.secure is still 1, so I think he didnt mess with the boot.img.
Did I miss anything and could anyone please mod the updater-script, so that the unnecessary symlinks are gone?
UPDATER-SCRIPT
Thanks in advance guys
P.S. if anyone has got a working updater-script without su and busybox for any other version, you can also hand it over. Cause then I ll just make a nandroid of that version, add the updater-script and binary, maybe the whole META-INF folder, the recovery.img from the according .bin file and then we also would have the perfect unroot ROM. Just hope anyone can help me
You need fresh files. Odexed. The ROM cannot be deoxed one if you're after warranty with LG.
There should be a busybox file in xbin. The original one.
All apps should be there including bloatwares.
Should be ext3 (default), not ext4. Use original boot.img cause there might be insertion of G-recovery on that ROM.
Updater-script: you can remove: symlink("/system/bin/su", "/system/xbin/su");
PS. Ask the person who would use, what was his last firmware flashed. Consider the baseband should match. Though it only shows XMM61xx, they might have a way to know.
To be a super clean rom:
More the stock build.prop since normally its changed to appear different things in "About Phone", for the rest, Gab already said everthing nedded
Both gabwerks and duarte got it covered.
Hmmm .... I think I got the unrooted, odexed v20o files in my PC. I can upload here if needed.
A recap of what to do.
1. Copy the boot.img from the stock ROM. I modified the boot.img to include g-recovery.
2. Copy the build.prop from the original stock ROM.
3. all apks were deodexed in my zip. So delete the app and framework folder from my zip and replace from the original stock ROM.
4. Edit the updater script.
a. use ext3 instead of ext4
b. remove: symlink("/system/bin/su", "/system/xbin/su");
5. compile. and i think that's it.
Does this look good then? I ll make a dutch unroot ROM, since this guy is dutch
http://pastebin.com/65tfX78H
N00BY0815 said:
Does this look good then? I ll make a dutch unroot ROM, since this guy is dutch
http://pastebin.com/65tfX78H
Click to expand...
Click to collapse
I think thats good .
Here you have the stock V20S build.prop if you want:
Code:
# begin build properties
# autogenerated by buildinfo.sh
ro.build.id=GRJ22
ro.build.display.id=GRJ22
ro.build.version.incremental=LG-P970-V20s.47F1AEC6
ro.build.version.sdk=10
ro.build.version.codename=REL
ro.build.version.release=2.3.4
ro.build.date=Mon Jul 2 12:55:00 IST 2012
ro.build.date.utc=1341213900
ro.build.type=user
ro.build.user=chinmay.mohapatra
ro.build.host=si-rd10-bld65
ro.build.tags=release-keys
ro.product.model=LG-P970
ro.product.brand=lge
ro.product.name=lge_bproj
ro.product.device=bproj_EUR-XXX
ro.product.board=bproj
ro.product.cpu.abi=armeabi-v7a
ro.product.cpu.abi2=armeabi
ro.product.manufacturer=LGE
ro.product.locale.language=en
ro.product.locale.region=GB,en
ro.wifi.channels=
ro.board.platform=omap3
# ro.build.product is obsolete; use ro.product.device
ro.build.product=bproj_EUR-XXX
# Do not try to parse ro.build.description or .fingerprint
ro.build.description=lge_bproj-user 2.3.4 GRJ22 LG-P970-V20s.47F1AEC6 release-keys
ro.build.fingerprint=lge/lge_bproj/bproj_EUR-XXX:2.3.4/GRJ22/LG-P970-V20s.47F1AEC6:user/release-keys
# end build properties
rild.libargs=-d /dev/ttyspi0
alsa.mixer.playback.master=DAC2 Analog \
#
# ADDITIONAL_BUILD_PROPERTIES
#
user.feature.flex=true
user.feature.lgdrm=true
user.feature.lgresource=true
user.feature.lgsetupwizard=true
user.feature.lgpoweroff=true
user.feature.preload_so=true
user.feature.preload_del=true
user.feature.lock_sui=true
user.feature.sui=true
user.feature.cmf=true
user.feature.wapservice=true
user.feature.lgorientation=true
user.feature.toucharea=true
user.feature.velocitytracker=true
user.feature.lgscroller=true
user.feature.eventthrottle=true
ro.build.lge.version.release=LG-P970-V20s
ro.config.ringtone=22_Dazzling_Brightness.ogg
ro.config.notification_sound=01_Acoustic_Guitar.ogg
ro.config.alarm_alert=Alarm_Beep01.ogg
ro.lge.vibrator_amp=120
ro.opengles.version=131072
ro.setupwizard.mode=DISABLED
ro.com.google.gmsversion=2.3_r10
ro.com.android.dateformat=MM-dd-yyyy
ro.com.android.dataroaming=true
ro.url.legal=http://www.google.com/intl/%s/mobile/android/basic/phone-legal.html
ro.url.legal.android_privacy=http://www.google.com/intl/%s/mobile/android/basic/privacy.html
ro.com.google.clientidbase=android-lge
ro.com.google.clientidbase.ms=android-lge
ro.com.google.clientidbase.gmm=android-lge
ro.com.google.clientidbase.yt=android-lge
ro.com.google.clientidbase.am=android-lge
ro.com.google.clientidbase=android-lge
rild.libpath=/system/lib/lge-ril.so
ro.telephony.default_network=0
ro.sf.lcd_density=240
com.ti.omap_enhancement=true
opencore.asmd=1
ro.radio.use-ppp=yes
keyguard.no_require_sim=1
ro.config.nocheckin=yes
wifi.interface=wlan0
alsa.mixer.capture.master=Analog
ro.com.android.dateformat=MM-dd-yyyy
ro.com.android.dataroaming=true
dalvik.vm.heapsize=48m
dalvik.vm.dexopt-flags=m=y
jpeg.libskiahw.decoder.enable=1
jpeg.libskiahw.decoder.thresh=100000
net.dns1=208.67.222.222
net.dns2=208.67.220.220
ro.tether.denied=false
net.bt.name=Android
dalvik.vm.stack-trace-file=/data/anr/traces.txt
If you make a unrooted version of another version, just change the "V20s" to "V20(letter version)" and think thats all, can contains more differences but will not influence the warranty.
Duarte777 said:
I think thats good .
Here you have the stock V20S build.prop if you want:
If you make a unrooted version of another version, just change the "V20s" to "V20(letter version)" and think thats all, can contains more differences but will not influence the warranty.
Click to expand...
Click to collapse
Thanks bro, but I made a fresh install, took the nandroid and it's in there already, but now I get error (status 6) while flashing... Should I upload the whole ROM, so you guys can have a look at it?
-edit- found it I think, didnt close "" around redy's name...
Thanks a bunch guys, i'm looking forward for the unrooted ROM!
Ok, here is a prerelease and wessyh0 please dont yet flash it, until someone else has confirmed, that I didnt miss anything.
It's v20o from NL, as I guess you are dutch. I flashed it to my own phone, injected cwm, made a nandroid, took META-INF folder from Echelon ROM by gabz, updater-script (modified) from tantrums, extracted the bin file, took the recovery partition and added it to the repack and updater-script.
Here it is: http://d-h.st/1RM
Please anyone check, if I missed anything, or if it's fine for unrooting purpose.
Note you ll lose CWM & root, so you ll have to flash with smartflash again, if you want to regain root.
If anyone confirms, have fun with it
Dont forget to do a factory reset, cache wipe, dalvik wipe, format your sd card/take it out and remove all other kind of trace, that might tell them, that your phone has been rooted once
Plus I want a donation from you then
Consisting of:
Push the thanks button.
A big thanks.
And a kiss
N00BY0815 said:
Ok, here is a prerelease and wessyh0 please dont yet flash it, until someone else has confirmed, that I didnt miss anything.
It's v20o from NL, as I guess you are dutch. I flashed it to my own phone, injected cwm, made a nandroid, took META-INF folder from Echelon ROM by gabz, updater-script (modified) from tantrums, extracted the bin file, took the recovery partition and added it to the repack and updater-script.
Here it is: http://d-h.st/1RM
Please anyone check, if I missed anything, or if it's fine for unrooting purpose.
Note you ll lose CWM & root, so you ll have to flash with smartflash again, if you want to regain root.
If anyone confirms, have fun with it
Dont forget to do a factory reset, cache wipe, dalvik wipe, format your sd card/take it out and remove all other kind of trace, that might tell them, that your phone has been rooted once
Plus I want a donation from you then
Consisting of:
Push the thanks button.
A big thanks.
And a kiss
Click to expand...
Click to collapse
I think that is better to creat another thread here on general or in dev section, a sticky thread.
N00BY0815 said:
Ok, here is a prerelease and wessyh0 please dont yet flash it, until someone else has confirmed, that I didnt miss anything.
It's v20o from NL, as I guess you are dutch. I flashed it to my own phone, injected cwm, made a nandroid, took META-INF folder from Echelon ROM by gabz, updater-script (modified) from tantrums, extracted the bin file, took the recovery partition and added it to the repack and updater-script.
Here it is: http://d-h.st/1RM
Please anyone check, if I missed anything, or if it's fine for unrooting purpose.
Note you ll lose CWM & root, so you ll have to flash with smartflash again, if you want to regain root.
If anyone confirms, have fun with it
Dont forget to do a factory reset, cache wipe, dalvik wipe, format your sd card/take it out and remove all other kind of trace, that might tell them, that your phone has been rooted once
Plus I want a donation from you then
Consisting of:
Push the thanks button.
A big thanks.
And a kiss
Click to expand...
Click to collapse
Thanks alot man! I'll wait for it to be confirmed, but for now you are my hero! And yes, im dutch :good:
If it's confirmed will you please tell me instructions how to use it? Thanks in advance
wessyh0 said:
Thanks alot man! I'll wait for it to be confirmed, but for now you are my hero! And yes, im dutch :good:
If it's confirmed will you please tell me instructions how to use it? Thanks in advance
Click to expand...
Click to collapse
Boot to recovery, wipe data/factory reset, wipe cache, wipe dalvik. Remove sd card or format it, flash the ROM, reboot, maybe do a factory reset from within the ROM and bring it to LG service. That's all, or did I miss anything?
Duarte777 said:
I think that is better to creat another thread here on general or in dev section, a sticky thread.
Click to expand...
Click to collapse
Well we can, or I mention it in my noob how to. Dont think it's worth a sticky though, but as always CMIIW, you can also create one, if you want to and maybe add some more ROMs (like 1 for europe, asia, ...)
N00BY0815 said:
Well we can, or I mention it in my noob how to. Dont think it's worth a sticky though, but as always CMIIW, you can also create one, if you want to and maybe add some more ROMs (like 1 for europe, asia, ...)
Click to expand...
Click to collapse
Nop bro, i just giving one ideia, i think that if you add to your noob how to its enough.
N00BY0815 said:
Boot to recovery, wipe data/factory reset, wipe cache, wipe dalvik. Remove sd card or format it, flash the ROM, reboot, maybe do a factory reset from within the ROM and bring it to LG service. That's all, or did I miss anything?
Click to expand...
Click to collapse
In my view you missed the fact that you have CWM instead of the stock recovery. As last step, to those listed by you, you should flash the stock recovery from CWM.
danfizesan said:
In my view you missed the fact that you have CWM instead of the stock recovery. As last step, to those listed by you, you should flash the stock recovery from CWM.
Click to expand...
Click to collapse
Stock recovery is in the flashable zip... I am already an advanced noob
Sent from my LG-P970 using xda app-developers app
N00BY0815 said:
Stock recovery is in the flashable zip... I am already an advanced noob
Sent from my LG-P970 using xda app-developers app
Click to expand...
Click to collapse
Great, wanna share it ?
danfizesan said:
Great, wanna share it ?
Click to expand...
Click to collapse
How about reading the whole thread? Only 2 pages till now and then you'll also find the link and see, that I am still waiting for an approval by the Pro's here
Can anyone please approve it? I want to bring it to the service center.
wessyh0 said:
Can anyone please approve it? I want to bring it to the service center.
Click to expand...
Click to collapse
I ll make a new version later, cause redy told me, that I forgot 2 format commands in updater-script + mount as ext3. But dont worry, then you should be just fine
Related
deleted .
Finally ! That bug was very annoying to me.
I'll try the fix asap, thanks a lot!
e: works like a charm!
Yeah, it was a so annoying issue...
I wonder why so less people visited this thread .
I copied this ZIP onto my SD card,rebooted, went into clockwork mod, install zip, choose zip and flashed this,rebooted but am stuck on the HTC screen now for over 7 minutes am i doing something wrong?
It's as well i made a backup or id lose everthing
jonny68 said:
I copied this ZIP onto my SD card,rebooted, went into clockwork mod, install zip, choose zip and flashed this,rebooted but am stuck on the HTC screen now for over 7 minutes am i doing something wrong?
It's as well i made a backup or id lose everthing
Click to expand...
Click to collapse
Try adding the libaudio.so to your ROM.zip (with 7-zip or WinRAR) at the right directory and flash the ROM.zip again. That's what I am doing everytime I change something
j4n87 said:
Yeah, it was a so annoying issue...
I wonder why so less people visited this thread .
Click to expand...
Click to collapse
Because you posted it in the "Themes and Apps" section
thanks a lot for post here
great job
kackburt said:
Try adding the libaudio.so to your ROM.zip (with 7-zip or WinRAR) at the right directory and flash the ROM.zip again. That's what I am doing everytime I change something
Click to expand...
Click to collapse
you mean copy the actual zip file into the ROM zip and then flash?
jonny68 said:
you mean copy the actual zip file into the ROM zip and then flash?
Click to expand...
Click to collapse
Unzip the cwm with the fix and navigate to "system/lib" and copy the "libaudio.so".
then open the rom zip navigate to "system/lib" and paste the "libaudio.so" there.
Didn't understand your previous post..did you make a backup or not?
If not...just flash your current rom again, you won't lose your data if you do this.
Only the files that you edited in /system like gps.conf or other tweaks you have to edit again.
Tried on UD3.3.0 wont boot... :s
People dont understand that this work the best on CM7 nexus roms.
That by installing this fix on CM7 or AOSP you will probaly lose the robo and high volume on first call fix. That most roms have custom libs including this lib. Minimum requirements I would say CM7 2.34 and AOSP 2.34 since cm7 and AOSP are the most equal roms to each other.
To say it simple you cant just simply flash this on every rom also make sure your permission is right.
Is this fix able to work on an HTC Desire running 2.3.4 Oxygen ROM?
jonny68 said:
I copied this ZIP onto my SD card,rebooted, went into clockwork mod, install zip, choose zip and flashed this,rebooted but am stuck on the HTC screen now for over 7 minutes am i doing something wrong?
It's as well i made a backup or id lose everthing
Click to expand...
Click to collapse
If you have a nandroid backup, you should be on the safe side!
Try to wipe cache partition first, then the dalvik cache and then flash the zip-file.
All of these actions take place in the CWM.
Hope it works!
The libaudio.so fix was submitted to gerrit (Change I24a4a11b: Fix for a1026 suspend)by Jordon aka Jyxent. It was mergered with the latest nightlies, and should be merged with CM 7.0.4
jens1288 said:
The libaudio.so fix was submitted to gerrit (Change I24a4a11b: Fix for a1026 suspend)by Jordon aka Jyxent. It was mergered with the latest nightlies, and should be merged with CM 7.0.4
Click to expand...
Click to collapse
Yes, that fix works fine. I'm not sure it fixes the few seconds delay that affects all Gingerbread phones though but there was another potential workaround submitted for that too.
http://review.cyanogenmod.com/#change,5420
I have yet to include it in my build and try it though.
The story on the front page links to the wrong fix. The libaudio fix was for the wonk on the Nexus One. The libaudio library is hardware specific and may cause issues on other devices that don't share the same processor.
I've submitted a patch to gerrit that helps with the call delay here:
http://review.cyanogenmod.com/#change,5420
Thank you for clearing that up jyxent. To go into a bit more detail...
The fix that was posted, as jyxent mentioned, is for the Nexus One. That is for the infamous "wonk" that has been plaguing N1 users since the Gingerbread nightlies started (who woulda thunk it was just a single line that needed to be added).
The 2-3 second delay is something that affects most (if not all) Gingerbread installs. Currently there isn't a simple "fix" for this. It requires recompiling portions of Gingerbread. jyxent's fix is submitted to CM, but I don't see any reason why this can't be applied to AOSP as well. It has yet to be reviewed by the CM dev team (at least it doesn't have any comments on it yet). It might be something that can be made into some device-independent flashable zip, but it has yet to be created.
j4n87 said:
Unzip the cwm with the fix and navigate to "system/lib" and copy the "libaudio.so".
then open the rom zip navigate to "system/lib" and paste the "libaudio.so" there.
Didn't understand your previous post..did you make a backup or not?
If not...just flash your current rom again, you won't lose your data if you do this.
Only the files that you edited in /system like gps.conf or other tweaks you have to edit again.
Click to expand...
Click to collapse
done thanks
Can this be done manually with root explorer, by copying the libaudio.so to/system/lib and a reboot?
The link is
http://hotfile.com/dl/131660662/a50edbc/GT-P7510_SER_P7510XWKH5_P7510OXEKH2.rar.html
Pasword to unzip is sampro.pl
Have to congratulate the guys from sampro.pl for getting this one.
Before you proceed
Am not responsible if your tab is "bricked" or damage...here you will have to play with Odin so a certain experience with odin is recommended
Note too.you will be required to wipe everything a la Odin (i.e. it will erase everything that is in your SD card as well so YOU MUST BACKUP any important info on to your PC or cloud!)
This is its build.props
Code:
# begin build properties
# autogenerated by buildinfo.sh
ro.build.id=HMJ37
ro.build.display.id=HMJ37
ro.build.version.incremental=XWKH5
ro.build.version.sdk=12
ro.build.version.codename=REL
ro.build.version.release=3.1
ro.build.date=Thu Aug 18 18:29:39 KST 2011
ro.build.date.utc=1313659779
ro.build.type=user
ro.build.user=root
ro.build.host=DELL136
ro.build.tags=release-keys
ro.product.model=GT-P7510
ro.product.brand=samsung
ro.product.name=GT-P7510
ro.product.device=GT-P7510
ro.product.board=GT-P7510
ro.product.cpu.abi=armeabi-v7a
ro.product.cpu.abi2=armeabi
ro.product.manufacturer=samsung
ro.product.locale.language=en
ro.product.locale.region=GB
ro.wifi.channels=
ro.board.platform=tegra
# ro.build.product is obsolete; use ro.product.device
ro.build.product=GT-P7510
# Do not try to parse ro.build.description or .fingerprint
ro.build.description=GT-P7510-user 3.1 HMJ37 XWKH5 release-keys
ro.build.fingerprint=samsung/GT-P7510/GT-P7510:3.1/HMJ37/XWKH5:user/release-keys
ro.build.characteristics=tablet,nosdcard
# Samsung Specific Properties
ro.build.PDA=P7510XWKH5
ro.build.hidden_ver=P7510XWKH5
ro.build.changelist=493499
ro.build.buildtag=
# end build properties
#
# system.prop for P3
#
ro.opengles.version = 131072
wifi.interface=eth0
rild.libpath=/system/lib/libsec-ril-apalone.so
rild.libargs=-d /dev/ttys0
keyguard.no_require_sim=yes
# Samsung Tvout Service
ro.sectvout.enable=0
#
# ADDITIONAL_BUILD_PROPERTIES
#
ro.config.ringtone=S_Minimal_tone.ogg
ro.config.notification_sound=S_On_time.ogg
ro.config.alarm_alert=Good_Morning.ogg
dev.sfbootcomplete=0
dalvik.vm.heapstartsize=5m
dalvik.vm.heapgrowthlimit=64m
dalvik.vm.heapsize=288m
ro.secdevenc=true
ro.carrier=wifi-only
drm.service.enabled=true
ro.setupwizard.mode=OPTIONAL
ro.setupwizard.enterprise_mode=1
ro.com.google.gmsversion=3.1_r2
ro.error.receiver.system.apps=com.google.android.feedback
ro.url.legal=http://www.google.com/intl/%s/mobile/android/basic/phone-legal.html
ro.url.legal.android_privacy=http://www.google.com/intl/%s/mobile/android/basic/privacy.html
ro.com.google.clientidbase=android-samsung
dalvik.vm.dexopt-flags=m=y
net.bt.name=Android
dalvik.vm.stack-trace-file=/data/anr/traces.txt
So it is newer than KME
Impressions...
ITs very fluid and responsive specially when dealing with widgets . I personally find it more so than KME
Flashing via ODIN
Make sure you have odin 3 1.85 you can get it here
http://www.multiupload.com/5QR3X8PHWW
Make sure you have the correct pit file to flash you can get it here
http://hotfile.com/dl/132389181/e245faa/android_fastboot_emmc_full_p4_16G_32G.pit.html
Unzipp your GT-P7510_SER_P7510XWKH5_P7510OXEKH2.rar
You will get a file called P7510XWKH5_P7510OXEKH2_HOME.TAR.md5
Assuming that you have backup all your important information on your tab to a PC make sure your tab is disconnected from your PC
Put tab in download mode (if not sure how to then don't precede)
Start odin first before connecting your tab to the PC
Tick on Re-Partition
Place the pit you downloaded earlier under the pit section (press pit button)
Place the tar.md5 you extracted earlier under the PDA section(press PDA button)
Assuming your tab is in download mode connect tab to your PC
Wait for odin to detect your tab ( the ID:COM box will be highlighted yellow)
Hit START button (it will take approx 2 to 5 mins to flash)
If all successful then you will see a green Pass on Odin
Your tab will reboot into the stock recovery 3e menu. You will see some errors in red but ignore them (use vol up /down and power button to select similar to what you are use to in CWM)
Once in the recovery 3e menu choose "Wipe Data/Factory Reset" and hit enter by pressing the Power button (similar to what you will do in CWM recovery)
Once you are notified that wiping is complete select to reboot your tab (again use vol up/down similar to CWM)
Once your tab is rebooted you will be presented with a russian language text (you can select from the drop down menu english! if you can't understand russian)
Begin in setting up your google account and your tab enjoy
Rooting
As this tab uses the same recovery you will expect from KME it is unlocked. (3e) so it is possible to simply flash via the stock recovery the root zip and lo and behold you are in root
There are 2 main ways of doing this.. one is a long way and the other a short way
The long way is the one where you first need to flash CWM via odin and then use CWM to flash the root exploit
For more info see http://forum.xda-developers.com/showthread.php?t=1171089
Benefits: It is possible to do a backup of your stock rom without been rooted for warranty purposes?
The easy way to gain root is
In your tab create a directory call it Myroot (can be any directory name under /mnt/sdcard) the crucial thing is that the directory name must start with a capital
so Myroot is a good directory name where as myroot is a BAD directory name.
(Stock 3E has problems recognising lowercase dir names!)
Download the root exploit http://hotfile.com/dl/132392484/68158c2/Samsung_Galaxy_Tab_10.1_root.zip.html (its the same one found under this post http://forum.xda-developers.com/showthread.php?t=1171089 )
Connect your tab to the PC and save the file to the directory you created (the one that has an upper case word (e.g. Myroot)
Disconnect your tab from the PC and switch your tab off
Put your tab in recovery mod
Once in recovery select 'Apply update from sd card'
Locate the directory where you placed the root exploit zip file (e.g. in Myroot dir)
Choose power button to select
Reboot device
Once rebooted in to your device your device has now root
Gaining CWM into KH5
Simply download Rom manager from market and select Flash ClockworkMod recovery
and apply root access when requested...and thats it!
Enhancing your tab experience
I had downloaded SpareParts+ from the market and made the following mods
- Windows animations chose FAST
- Transition animations chose FAST
I had downloaded Blade Buddy from the market and made the following mods
- went to advance settings
- applied root into it
- ticked debug.sf.hw
- rebooted tab
enjoy!
System dump for the Devs
http://www.multiupload.com/16O8LCEIX7
Even without the last mod this rom is so smooth!
Supported languages
* English
* Indonesian
* Catalan
* Deutsh
* Cestina
* Spanish (español)
* Estonian
* Francais
* Icelandic
* Hrvatski
* Italiano
* Kazakh
* Latviesu
* Lietuviu
* Magyar
* Nederlands
* Polski
* Portuguese
* Romana
* Slovenian
* Swedish
* Vietnam
* Turkish
* Russian
* Chinese
* Korean
hmmmmm........... can you pull a system dump for me bro?
SD - Wiped.
systems apps - Not Wiped.
But this is soooo smooth!
You mean if I give you the system img?
Sent from my GT-P7510 using Tapatalk
nandihno said:
You mean if I give you the system img?
Sent from my GT-P7510 using Tapatalk
Click to expand...
Click to collapse
The system image is already in this, I'm talking about pulling a system dump with adb
Oh have to learn how to do that will read on it
Sent from my GT-P7510 using Tapatalk
This is not a European ROM but a Russian one.
Sent from my Nexus S using Tapatalk
Quick question.... Does it have TouchWiz?
yes has tw de like I said this is newer than kme
It's very fluid
Btw am uploading the system dump for devs to play with it
nandihno said:
yes has tw de like I said this is newer than kme
It's very fluid
Btw am uploading the system dump for devs to play with it
Click to expand...
Click to collapse
Thanks mate
task650 said:
hmmmmm........... can you pull a system dump for me bro?
Click to expand...
Click to collapse
ok finally able to do it..! read OP
yeah i definitely wont be building off this. just tested out and i dont see anything better about it. its probably just placebo you're having. lol. newer doesnt always equal better is definitely very well known around here. thanks for posting this though.
ok i definately fill it much faster than KME after like 2 days of usage...so..if its placebo then it must be magical lol
but cool dude...no problems
so far the only issue is that is not 3.2
otherwise is pretty fluid
nandihno said:
ok i definately fill it much faster than KME after like 2 days of usage...so..if its placebo then it must be magical lol
but cool dude...no problems
so far the only issue is that is not 3.2
otherwise is pretty fluid
Click to expand...
Click to collapse
yep. definitely not 3.2. we'll probably skip it anyways when ics gets here eventually.
I do not know, if it is related to this ROM version, but I noticed the following:
-I renamed system/app/vending.apk to "vending.apk.old"
-I removed vending stuff from data/app and dalivik-cache
-I installed market 3.20 by copying vending.apk to system/app and clicking on it in root explorer to install it
However, I dont like this market version and want to revert back to the original one. Thus, I deleted all vending stuff again at locations mentioned above and renamed "vending.apk.old" to "vending.apk".
-When I click on "vending.apk" in root explorer, I get "application not installed".
Afterwards, I downloaded all market 3.1.5/3.1.6 apks that I could find, but I cannot install anyone of them anymore.
Also a reboot did not help.
However, I can still install market 3.20 ?!?! (I did this again just to be sure, that I do the correct things )
So what is wrong?
Is something wrong with this ROM version?
Did market 3.20 mess with my system?
Any ideas?
Klaus
oclock said:
I do not know, if it is related to this ROM version, but I noticed the following:
-I renamed system/app/vending.apk to "vending.apk.old"
-I removed vending stuff from data/app and dalivik-cache
-I installed market 3.20 by copying vending.apk to system/app and clicking on it in root explorer to install it
However, I dont like this market version and want to revert back to the original one. Thus, I deleted all vending stuff again at locations mentioned above and renamed "vending.apk.old" to "vending.apk".
-When I click on "vending.apk" in root explorer, I get "application not installed".
Afterwards, I downloaded all market 3.1.5/3.1.6 apks that I could find, but I cannot install anyone of them anymore.
Also a reboot did not help.
However, I can still install market 3.20 ?!?! (I did this again just to be sure, that I do the correct things )
So what is wrong?
Is something wrong with this ROM version?
Did market 3.20 mess with my system?
Any ideas?
Klaus
Click to expand...
Click to collapse
3.20 messed with your system.
To fix this just put your old vending.apk back, delete 3.20, clear cache and dalvik, then go to market.android.com and do a cloud install of some application, should fix things and bring back ur old vending.
oclock said:
I do not know, if it is related to this ROM version, but I noticed the following:
-I renamed system/app/vending.apk to "vending.apk.old"
-I removed vending stuff from data/app and dalivik-cache
-I installed market 3.20 by copying vending.apk to system/app and clicking on it in root explorer to install it
However, I dont like this market version and want to revert back to the original one. Thus, I deleted all vending stuff again at locations mentioned above and renamed "vending.apk.old" to "vending.apk".
-When I click on "vending.apk" in root explorer, I get "application not installed".
Afterwards, I downloaded all market 3.1.5/3.1.6 apks that I could find, but I cannot install anyone of them anymore.
Also a reboot did not help.
However, I can still install market 3.20 ?!?! (I did this again just to be sure, that I do the correct things )
So what is wrong?
Is something wrong with this ROM version?
Did market 3.20 mess with my system?
Any ideas?
Klaus
Click to expand...
Click to collapse
This is not the correct procedure for replacing system apps. I would just delete/rename the original apk and then just copy the new one to /system/app/. When you click the apk in root explorer, you're actually making a new copy in /data/app/. Needless to say, you shouldn't do that.
reflux21 said:
3.20 messed with your system.
To fix this just put your old vending.apk back, delete 3.20, clear cache and dalvik, then go to market.android.com and do a cloud install of some application, should fix things and bring back ur old vending.
Click to expand...
Click to collapse
I deleted the old vending stuff in
/system/app
/data/app
/data/dalvik-cache
/data/data
I also rebooted into recovery to clear the cache.
I renamed "/system/app/vending.apk.old" in "/system/app/vending.apk" (File date: 18. Aug. 11, 11:41:00 rw-r--r--, 1.76MB) and rebooted again.
However, Market is not recognized by my tablet. Thus, now I do not have a market anymore.
I surfed to market.android.com from my PC and installed a random app. Nothing happened. Still no market on my tab
Any other ideas?
I think you will need to reflash your FW.
Backup and flash!
I usually dont try and fix something broken
But if you are looking for a solution, I think you will need to wait.
reflux21 said:
I think you will need to reflash your FW.
Backup and flash!
I usually dont try and fix something broken
But if you are looking for a solution, I think you will need to wait.
Click to expand...
Click to collapse
I did a factory reset of my tab and now the old market is back...
Thank you for your support during my darkest hours
Klaus
Hello my fellow Android crack flashers! So Volk and I have wrote(him) and tested(me) his g2x nullifier for our phones. Well it works flawlessly! Which his thread is here. So with our learning adventures he has helped me port it to the O2x. So here is the run down. This was originally created as the g2xscrubber was insufficient enough for our flashberry addiction, and on top of that if wouldn't wipe our /cache either.
So the domino effect has begun. This is a simple script that will wipe your internal partitions cleaner then a whistle and get it dam near like new status, perfectly ready for a ROM. Like as if you just purchased it and didnt have any data on it nor a ROM and needed to be flashed. And yes it came all tricked out like that with CWM and all.. haha
So here it is...
The O2x Nullifier
This uses a special command in combination with a special file to overwrite the internal partitions with 0's, hence "Null" for 0 and "-ifier" for the fact that it does something. It also formats the partitions afterward, including /cache too! Enjoy!
Some brief need to knows:
1. This is a little lengthy process so please bear with it. The longest wipe is on /data which will take about 7 minutes. Obviously, make sure you have plenty of battery life before running it. I've ran this Nullifier like 20 times in the last two days of first testing and on average its about 1204 seconds or about 19.8 minutes, on average. The Single pass zip is only half of the time of course. Or you can just watch the progress bar. After 20 times of nullifing and log pulling in 2 days, im pretty dang sure the bar is accurate. So enjoy!
2. ONCE THE NULLIFICATION PROCESS HAS BEEN COMPLETED DO NOT, I REPEAT, DO NOT TURN OFF OR LET YOUR PHONE DIE BEFORE FLASHING A ROM OR RESTORING... or you will brick your phone.
3. I will provide help, support, etc. for this, but as always flash at your own risk and I am not responsible if you turn your phone into your next non-aerodynamic frisby.
Enjoy!
Also I have now decided to copy the log to sdcard at completion (thanks to DARKSIDE for the idea). But from now on the log created in /tmp while in cwm is now copied to sdcard as O2x-Nullified-recovery.log. So it will still be deleted from RAM but never lost any more!!!!! muhahahahahahah... love it!
Thanks go to Волк aka Volk for letting me test and learn from his G2x Nullifier script. And also to owain94 for helping me make sure that this thing will run ok on the O2x, since I dont actually have the O2x..
Also if is doesn't work, please we need logs. You need to use a file explorer or put the external sdcard into your pc and grab and upload or pm me the log from your sdcard the file will be named 'O2x-Nullified-recovery.log'
mini change log:
1.2 -> fixed sleep command, 1.2
1.3 -> updated binary script and added /cache info per vadonka's advice
1.3.1 -> Bad zip... reupped
1.3.2 -> zipped with 7zip should work now.. dumb winzip... reupped
skipped to 1.5 -> updated script and binary. Also removed /cache format command; instead do a manual wipe for now
skipped to 2.0 -> updated script and binary again. Manual format still.
2.1 -> No more manual /cache wipe and working progress bar!
2.2 -> Single/Dual pass zip options. Thanks to Volk for error check and darkside for log creation idea. Added support for su660
nice work mate!
Ok so i'm hijacking this post to use while i'm at work (with crappy lowest bid PC) and using this FOR MY TEST UPLOADS ONLY. THIS WILL CONSIST OF G2X TESTS GETTING READY FOR THE O2X... DO NOT DOWNLOAD ANY ATTACHMENT ON THIS POST OR ATTEMPT TO FLASH IT BECAUSE IT WONT WORK FOR YOU UNLESS YOU HAVE A G2X!
Thanks a lot mate
da-pharoah said:
This was originally created as the g2xscrubber was not sufficent enough for our flashberry addiction.
Click to expand...
Click to collapse
Remember to read first, if your question hasn't already been asked or answered, ask and maybe you'll get it posted in the Q&A post.
Pharoh, what did you fix I see nothing wrong.
>.>
carburano said:
Thanks a lot mate
Click to expand...
Click to collapse
No worries
Волк said:
Remember to read first, if your question hasn't already been asked or answered, ask and maybe you'll get it posted in the Q&A post.
Pharoh, what did you fix I see nothing wrong.
>.>.
Click to expand...
Click to collapse
lol nice catch.. was in a hurry to leave from work. Fixed now.
Hi friend...
just tried but it's not working... E: Can't Open /sdcard/O2x Nullifier beta 1.zip (bad) Installation Aborted...
Interesting, there will be a log in cache/Recovery can you send it to one of us and we can have a look. It may have not been zipped correctly. Or heck, I'll dl it right quick and have a look.
Ah, it's not signed. One sec.
new link.
http://db.tt/YeuzWktM
Error status 6...
Did you made the updater script in Linux, mac or windows?
If Mac or windows what text editor did you use?
Did you ever edited the updater script if yes what text editor did you use?
Sent from my LG-P990 using xda premium
owain94 said:
Error status 6...
Did you made the updater script in Linux, mac or windows?
If Mac or windows what text editor did you use?
Did you ever edited the updater script if yes what text editor did you use?
Sent from my LG-P990 using xda premium
Click to expand...
Click to collapse
used win7 and notepad++
error with op link or updated link by Волк?
carburano said:
Hi friend...
just tried but it's not working... E: Can't Open /sdcard/O2x Nullifier beta 1.zip (bad) Installation Aborted...
Click to expand...
Click to collapse
Волк said:
Interesting, there will be a log in cache/Recovery can you send it to one of us and we can have a look. It may have not been zipped correctly. Or heck, I'll dl it right quick and have a look.
Ah, it's not signed. One sec.
new link.
http://db.tt/YeuzWktM
Click to expand...
Click to collapse
OP updated thanks again Волк!
Why not just use the nvflash based v10b flashing released by Paul on modaco. I use that when I really want to clean everything up. Since it is V10b, easy to install CWM recovery using psneuter (thought it is not required) and can be done with a simple dd command directly.
hackworks said:
Why not just use the nvflash based v10b flashing released by Paul on modaco. I use that when I really want to clean everything up. Since it is V10b, easy to install CWM recovery using psneuter (thought it is not required) and can be done with a simple dd command directly.
Click to expand...
Click to collapse
Well really thats kind of a longer process.. thats a rom, this is just a tool to wipe clean your internal storage. Basically take it back to like new status, but still having full root ability. CWM will flash the rom of your choice after your done with the nullification process and manual /cache wipe. This will not take you back to a predetermined state (in terms of a rom), it will leave your phone a nice paper weight however until you decide to flash a rom.
nice work!
i have a little advice for you. use this method for the cache wipe and no need to manual wipe cache anymore
unmount("/cache");
run_program("/sbin/mke2fs", "/dev/block/mmcblk0p2");
run_program("/sbin/tune2fs", "-O", "extents,uninit_bg,dir_index,has_journal", "/dev/block/mmcblk0p2");
run_program("/sbin/e2fsck", "-fy", "/dev/block/mmcblk0p2");
run_program("/sbin/tune2fs", "-o", "journal_data_writeback", "/dev/block/mmcblk0p2");
run_program("/sbin/e2fsck", "-fy", "/dev/block/mmcblk0p2");
this create an ext4 partition, if you want ext3 just skip the first tune2fs row, and use the -j option in the mke2fs.
mke2fs recreate a new empty partition no need to fill with zeroes before, so the nullifying parts is unneded, just use the mke2fs. its enough, except if you want to wipe the data for reason.
I still receiving get the error message:
E: Can't Open /sdcard/O2x_Nullifier_1.2.zip (bad) Installation Aborted (Status 6)
Click to expand...
Click to collapse
What I'm doing wrong?
ev!denz said:
I still receiving get the error message:
What I'm doing wrong?
Click to expand...
Click to collapse
its because the update-binary is a bit old
use a newer update binary.
vadonka said:
its because the update-binary is a bit old
use a newer update binary.
Click to expand...
Click to collapse
How can I use a newer one?
Darn it! Ok im on my way to work.. I'll see if I can get around the limitations there an update for y'all...
Sent from my LG-P999 using xda premium
ev!denz said:
How can I use a newer one?
Click to expand...
Click to collapse
just replace the update-binary file in the META-INF\com\google\android\ directory
pull it from the cm7 kang for example.
vadonka said:
just replace the update-binary file in the META-INF\com\google\android\ directory
pull it from the cm7 kang for example.
Click to expand...
Click to collapse
OP updated
hey guys, where to find multipackage firmware for ace, only found s5830i/c multipack thread. none for this device.
thanks for all ur help.
dzeig said:
hey guys, where to find multipackage firmware for ace, only found s5830i/c multipack thread. none for this device.
thanks for all ur help.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?p=39294309
KPH
thanks alot. btw, is it possible to go back to stock from custom rom (ie cm10.1) using single firmware.
coz, i need to flash multipack fw first (from cusrom) before flashing lastest stock, on mini.
dzeig said:
thanks alot. btw, is it possible to go back to stock from custom rom (ie cm10.1) using single firmware.
coz, i need to flash multipack fw first (from cusrom) before flashing lastest stock, on mini.
Click to expand...
Click to collapse
Be careful the rom I posted was for Galaxy Ace!!!
Yes, It's possible, I don't know in mini ... this is the GT-S5830 Q&A THREAD so...
but the fastest way to go back to stock is doing a backup before to use the custom, and then restoring it when you want to go back via custom RECOVERY, or FALSHING A FRESH STOCK ROM VIA ODIN
...and in Galaxy Ace it's possible to use directly the lastest firmware, "one package fw"
i know, im using ace right now.
the thing is i was failed revert back to stock using one pack firmware (on mini). am bit afraid it happens to ace either. but now it's all clear, thanks for all ur helps.
edit: whoaa, we can backup stock on ace, it s not recommended on mini. thanks again.
dzeig said:
i know, im using ace right now.
the thing is i was failed revert back to stock using one pack firmware (on mini). am bit afraid it happens to ace either. but now it's all clear, thanks for all ur helps.
edit: whoaa, we can backup stock on ace, it s not recommended on mini. thanks again.
Click to expand...
Click to collapse
well, the best way to avoid all kind of troubles is flashing a fresh stock via Odin
I'm using a bareboned stock rom, I deleted all useless apps etc and I chaged the kernel and stock partitions from .rfs to .ext4, so I have a clean backup ready to restore in my SDCARD, so I can flash whatever I want, and then when I get tired I can always return to my clean previous rom and I don't need to use Odin
am a noob so...
1. change the kernel? even for lastest fw?
2. how to change the.rfs partition?
dzeig said:
am a noob so...
1. change the kernel? even for lastest fw?
2. how to change the.rfs partition?
Click to expand...
Click to collapse
well... you can change the kernel, deodex your rom, change .rfs partition format to .ext4 format and add more tweaks, barebone your rom... (not for a noob way) or the easiest way!! you can flash a based stock rom with ALL this changes done e.g. http://forum.xda-developers.com/showthread.php?t=1534804
Viper The Ripper said:
well... you can change the kernel, deodex your rom, change .rfs partition format to .ext4 format and add more tweaks, barebone your rom... (not for a noob way) or the easiest way!! you can flash a based stock rom with ALL this changes done e.g. http://forum.xda-developers.com/showthread.php?t=1534804
Click to expand...
Click to collapse
hey viper, can you tell how to root lastest fw (bvkt6). cuz I tried using root.zip, upd_1.zip, universalgbroot_25 none of it works. thanks.
dzeig said:
hey viper, can you tell how to root lastest fw (bvkt6). cuz I tried using root.zip, upd_1.zip, universalgbroot_25 none of it works. thanks.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2346116
I need to know which apps are included in /system. The problem is that there isn't enough free space in /system in this rom so we could use a script to delete whatever app in this partition that allow us to push su.apk and the binaries
Viper The Ripper said:
http://forum.xda-developers.com/showthread.php?t=2346116
I need to know which apps are included in /system. The problem is that there isn't enough free space in /system in this rom so we could use a script to delete whatever app in this partition that allow us to push su.apk and the binaries
Click to expand...
Click to collapse
i read those threads.
so all i need to do is changing the updater-script, and delete unuseful system apps, right?
man, your so helpful. thanks a lot.
dzeig said:
i read those threads.
so all i need to do is changing the updater-script, and delete unuseful system apps, right?
man, your so helpful. thanks a lot.
Click to expand...
Click to collapse
Yeah, it's because I needed to know about your useless apps m but you can modify the script too
I've posted in the other thread how to add to the script how to mount /system auntomatically
You're welcome dude!
Viper The Ripper said:
Yeah, it's because I needed to know about your useless apps m but you can modify the script too
I've posted in the other thread how to add to the script how to mount /system auntomatically
You're welcome dude!
Click to expand...
Click to collapse
i got my phone rooted. ur magical zip works great. once again thank you.
now, i got 50+ mb free space in /system.
i just tried backingup via cwm, it said error mounting the system, bla, bla...
so, next question is how to backup this rom?
dzeig said:
i got my phone rooted. ur magical zip works great. once again thank you.
now, i got 50+ mb free space in /system.
i just tried backingup via cwm, it said error mounting the system, bla, bla...
so, next question is how to backup this rom?
Click to expand...
Click to collapse
you can try mounting manually /system and then doing the backup
go to mount and system >>> mount /system >>> back >>> backup and restore >>> backup
Viper The Ripper said:
you can try mounting manually /system and then doing the backup
go to mount and system >>> mount /system >>> back >>> backup and restore >>> backup
Click to expand...
Click to collapse
already tried to mount /system manually but no luck: "error mounting the system".
what i have to do?
dzeig said:
already tried to mount /system manually but no luck: "error mounting the system".
what i have to do?
Click to expand...
Click to collapse
mm I guess what is your problem
maybe .rfs format , so try to convert your partitions to .ext4 partition, It would solve your problem
use CF-Root-S5830_ext4-v1.3u3.apk to convert .rfs to .ext4 format
Viper The Ripper said:
mm I guess what is your problem
maybe .rfs format , so try to convert your partitions to .ext4 partition, It would solve your problem
use CF-Root-S5830_ext4-v1.3u3.apk to convert .rfs to .ext4 format
Click to expand...
Click to collapse
is this the correct kernel: CF-Root-S5830-v3.7-b84.zip?
edit: i think i did it right. now ive converted it to .ext4.
ive backed it up too, and it works.
my next question, where is a2sd script located, am bout to change it to int2ext4 (i didnt find it in init.d folder)?
dzeig said:
is this the correct kernel: CF-Root-S5830-v3.7-b84.zip?
edit: i think i did it right. now ive converted it to .ext4.
ive backed it up too, and it works.
my next question, where is a2sd script located, am bout to change it to int2ext4 (i didnt find it in init.d folder)?
Click to expand...
Click to collapse
Wooow I'm glad!! I'm a wiseman xDDD
---------- Post added at 05:07 AM ---------- Previous post was at 05:03 AM ----------
dzeig said:
is this the correct kernel: CF-Root-S5830-v3.7-b84.zip?
edit: i think i did it right. now ive converted it to .ext4.
ive backed it up too, and it works.
cf-root b84 work fine
my next question, where is a2sd script located, am bout to change it to int2ext4 (i didnt find it in init.d folder)?
Click to expand...
Click to collapse
Well you need a custom kernel to get an init.d folder or create it on yourself but the easy way, flash cf-root b84, BE 1.5.1. or whatever kernel you want, and you'll get an init.d folder support, so you'll be able to flash the int2ext script without any kind of problem
Viper The Ripper said:
Wooow I'm glad!! I'm a wiseman xDDD
Click to expand...
Click to collapse
i believe you are, how bout removing a2sd i've mentioned before...
edit: mmm... i found a2sd uninstaller zip, i ll give it a go..
dzeig said:
i believe you are, how bout removing a2sd i've mentioned before...
Click to expand...
Click to collapse
Install a Terminal Emulator app and type this code
Code:
su
a2sd remove
But it is not compulsory to install int2ext script, at least if you didn't flash darktremor script to activate app2sd
---------- Post added at 05:17 AM ---------- Previous post was at 05:14 AM ----------
dzeig said:
i believe you are, how bout removing a2sd i've mentioned before...
edit: mmm... i found a2sd uninstaller zip, i ll give it a go..
Click to expand...
Click to collapse
Well you can try it, of course
Hi!
I have rooted my phone, and deleted bloatware using uninstall.
After reboot, the apps returned, so I deleted /system/apps/*.apk (relevant) files (I'd also like to know what are the *.odex files if someone can kindly tell me )
Then, I rebooted again, and again they were... I have read in previous threads that flashing the kernel is needed. Is that so? And if so, how can it be done?
Thanks!
barashe said:
Hi!
I have rooted my phone, and deleted bloatware using uninstall.
After reboot, the apps returned, so I deleted /system/apps/*.apk (relevant) files (Id also like to know what are the *.odex files if someone can kindly tell me )
Then, I rebooted again, and again they were... I have read in previous threads that flashing the kernel is needed. Is that so? And if so, how can it be done?
Thanks!
Click to expand...
Click to collapse
You need a custom kernel with /system write permission (unsecured kernel) .
You will not be able to install ota updates if you mess with /system files.
Thanks!
alray said:
You need a custom kernel with /system write permission (unsecured kernel) .
You will not be able to install ota updates if you mess with /system files.
Click to expand...
Click to collapse
Downloaded and installed ElementalX-m7 kernel and now they are all gone!
barashe said:
Downloaded and installed ElementalX-m7 kernel and now they are all gone!
Click to expand...
Click to collapse
for future reference, you can also stay on stock kernel (dont really know why ) and do the changes in custom recovery (eg TWRP)
if you want a relatively easy file manager for custom recovery, check out Aroma File Manager... that would save you the hassle of using an adb shell
oh, and if all is good now, can you also edit main thread title to include [SOLVED], thanks
edit the first post -> at the bottom of the edit window, click Go Advanced, and then you can edit main title