Related
USE AT YOUR OWN RISK
adb push C:\Users\*\Downloads\redbend_ua /data/local
adb shell
chmod 755 /data/local/redbend_ua
/data/local/redbend_ua restore /sdcard/zImage.bin /dev/block/bml7
or
/data/local/redbend_ua restore /sdcard/recovery2.bin /dev/block/bml8
http://www.sdx-downloads.com/devs/noobnl/redbend_ua.zip
stock kernel http://www.sdx-downloads.com/devs/noobnl/zImage.bin
clockworkmod recovery: http://www.sdx-downloads.com/devs/noobnl/recovery2.bin
put it in sdcard
build 2: fixes script (made a dumb mistake)
So.. I used at my own risk.
after copying redbend over and trying to flash clockworkmod recovery I got a wierd error telling me something like the "file count is wrong" (if somebody else tries this PM me with the correct message so i can fix this)
I rebooted the phone and tried again. It worked and I can confirm clockwork recovery installed. I have not tried to do anything like format SD or install a zip yet, but I will.
After booting into recovery I was only able to find three working buttons.
1. The "Smiley" button next to left shift will allow you to navigate the menues, it functions like an up arrow would.
2. The "H" button behaves like the "enter" key
3. The "Searching Glass" (On the front, the rightmost lit button that looks like a magnifying glass) = return to the main menu within recovery.
I will test right now.
This is what I got.
FOTA : Make Block Device Nodes
lcd_init(498): start!
lcd_init(507): fb0 open success
lcd_init(514): width = 480, heig
open device file: Permission den
bmldevice_get_size: bmldevice_op
dst: /dev/block/bml8 partition s
part_size: 0x0
reboot: Operation not permitted
Bump for update.
AH I just realized i still have the command prompt window up from both the attempt that work and the attempt that failed.
Code:
C:\android-sdk-windows\tools>adb push c:\redbend_ua\redbend_ua /data/local
1523 KB/s (313888 bytes in 0.201s)
C:\android-sdk-windows\tools>adb shell
$ su
su
# chmod 755 /data/local/redbend_ua
chmod 755 /data/local/redbend_ua
# /data/local/redbend_ua restore /sdcard/recovery.bin /dev/block/bml8
/data/local/redbend_ua restore /sdcard/recovery.bin /dev/block/bml8
RedBend Update Agent 6,1,14,1
FOTA : Make Block Device Nodes
lcd_init(498): start!
lcd_init(507): fb0 open success
lcd_init(514): width = 480, height = 800
page_msize: 4096, phy_unit_size: 262144
src: /sdcard/recovery.bin
dst: /dev/block/bml8 partition size: 0x780000
part_size: 0x780000
failed to read from /sdcard/recovery.bin (Bad file number)
>>>>NOTE INSERT>>>>> BETWEEN THE PREVIOUS LINE AND THE NEXT I DID A BATTERY PULL REBOOT.
C:\android-sdk-windows\tools>adb shell
$ su
# /data/local/redbend_ua restore /sdcard/recovery.bin /dev/block/bml8
/data/local/redbend_ua restore /sdcard/recovery.bin /dev/block/bml8
RedBend Update Agent 6,1,14,1
FOTA : Make Block Device Nodes
lcd_init(498): start!
lcd_init(507): fb0 open success
lcd_init(514): width = 480, height = 800
page_msize: 4096, phy_unit_size: 262144
src: /sdcard/recovery.bin
dst: /dev/block/bml8 partition size: 0x780000
part_size: 0x780000
read 262144 bytes
read 262144 bytes
read 262144 bytes
read 262144 bytes
read 262144 bytes
read 262144 bytes
read 262144 bytes
read 262144 bytes
read 262144 bytes
read 262144 bytes
read 262144 bytes
read 262144 bytes
read 262144 bytes
read 262144 bytes
read 262144 bytes
read 262144 bytes
read 262144 bytes
read 262144 bytes
read 262144 bytes
read 262144 bytes
read 20384 bytes
read finished
C:\android-sdk-windows\tools>
Thanks. I know what went wrong. SU was needed.
BTW. The first time I did it. The many read file appeared to me. But I did not have ClockWork recovery.
Badge2378 said:
AH I just realized i still have the command prompt window up from both the attempt that work and the attempt that failed.
Code:
C:\android-sdk-windows\tools>adb push c:\redbend_ua\redbend_ua /data/local
1523 KB/s (313888 bytes in 0.201s)
C:\android-sdk-windows\tools>adb shell
$ su
su
# chmod 755 /data/local/redbend_ua
chmod 755 /data/local/redbend_ua
# /data/local/redbend_ua restore /sdcard/recovery.bin /dev/block/bml8
/data/local/redbend_ua restore /sdcard/recovery.bin /dev/block/bml8
RedBend Update Agent 6,1,14,1
FOTA : Make Block Device Nodes
lcd_init(498): start!
lcd_init(507): fb0 open success
lcd_init(514): width = 480, height = 800
page_msize: 4096, phy_unit_size: 262144
src: /sdcard/recovery.bin
dst: /dev/block/bml8 partition size: 0x780000
part_size: 0x780000
failed to read from /sdcard/recovery.bin (Bad file number)
>>>>NOTE INSERT>>>>> BETWEEN THE PREVIOUS LINE AND THE NEXT I DID A BATTERY PULL REBOOT.
C:\android-sdk-windows\tools>adb shell
$ su
# /data/local/redbend_ua restore /sdcard/recovery.bin /dev/block/bml8
/data/local/redbend_ua restore /sdcard/recovery.bin /dev/block/bml8
RedBend Update Agent 6,1,14,1
FOTA : Make Block Device Nodes
lcd_init(498): start!
lcd_init(507): fb0 open success
lcd_init(514): width = 480, height = 800
page_msize: 4096, phy_unit_size: 262144
src: /sdcard/recovery.bin
dst: /dev/block/bml8 partition size: 0x780000
part_size: 0x780000
read 262144 bytes
read 262144 bytes
read 262144 bytes
read 262144 bytes
read 262144 bytes
read 262144 bytes
read 262144 bytes
read 262144 bytes
read 262144 bytes
read 262144 bytes
read 262144 bytes
read 262144 bytes
read 262144 bytes
read 262144 bytes
read 262144 bytes
read 262144 bytes
read 262144 bytes
read 262144 bytes
read 262144 bytes
read 262144 bytes
read 20384 bytes
read finished
C:\android-sdk-windows\tools>
Click to expand...
Click to collapse
nice! time to update the post!
noobnl said:
nice! time to update the post!
Click to expand...
Click to collapse
The thing is Noob, that I had the same result with one try. And I do not have Clockwork recovery.
Here is a wierd bit.
If I reboot using "Volume Down" + "Camera" + "Power" i get into clockwork.
If I "Reboot to Recovery" using a software tool (Root Manager specifically) i end up in the stock recovery (Blue Text)
??
Badge2378 said:
Here is a wierd bit.
If I reboot using "Volume Down" + "Camera" + "Power" i get into clockwork.
If I "Reboot to Recovery" using a software tool (Root Manager specifically) i end up in the stock recovery (Blue Text)
??
Click to expand...
Click to collapse
If I boot on Recovery it boots to recovery. Hm..
C:\SDK\tools>adb shell
$ su
su
# /data/local/redbend_ua restore /sdcard/recovery.bin /dev/block/bml8
/data/local/redbend_ua restore /sdcard/recovery.bin /dev/block/bml8
RedBend Update Agent 6,1,14,1
FOTA : Make Block Device Nodes
lcd_init(498): start!
lcd_init(507): fb0 open success
lcd_init(514): width = 480, height = 800
page_msize: 4096, phy_unit_size: 262144
src: /sdcard/recovery.bin
dst: /dev/block/bml8 partition size: 0x780000
part_size: 0x780000
read 262144 bytes
read 262144 bytes
read 262144 bytes
read 262144 bytes
read 262144 bytes
read 262144 bytes
read 262144 bytes
read 262144 bytes
read 262144 bytes
read 262144 bytes
read 262144 bytes
read 262144 bytes
read 262144 bytes
read 262144 bytes
read 262144 bytes
read 262144 bytes
read 262144 bytes
read 262144 bytes
read 262144 bytes
read 262144 bytes
read 20384 bytes
read finished
I do not have Clockwork.
Fixter said:
If I boot on Recovery it boots to recovery. Hm..
Click to expand...
Click to collapse
I should have said boot, as from power off.
If I start with the power off, then Press "Volume Down" + "Camera" + "Power" and keep holding them, i end up in Clockwork Rocovery v2.5.0.4
I'll shoot a pic as soon as my wife(and her camera) get home.
Badge2378 said:
I should have said boot, as from power off.
If I start with the power off, then Press "Volume Down" + "Camera" + "Power" and keep holding them, i end up in Clockwork Rocovery v2.5.0.4
I'll shoot a pic as soon as my wife(and her camera) get home.
Click to expand...
Click to collapse
I'm gonna go check ROM Manager
Edit: Rom Manager boots me to Stock Recovery.
Fixter said:
I'm gonna go check ROM Manager
Edit: Rom Manager boots me to Stock Recovery.
Click to expand...
Click to collapse
Yeah, that's what i said before. The only way I've been able to boot into ClockworkMod is using the three button combo method.
Badge2378 said:
Yeah, that's what i said before. The only way I've been able to boot into ClockworkMod is using the three button combo method.
Click to expand...
Click to collapse
I get the same thing using both methods.
check the first post again make sure your applying the recovery.bin to bml8
shabbypenguin said:
check the first post again make sure your applying the recovery.bin to bml8
Click to expand...
Click to collapse
If you check my last post with the code, you can see we both have the exact same results. Also. I copy, pasted.
I dont understand the parrt about
/redbend_ua restore'
where do I place that file in the tools folder of sdk? and clockwork file on root of sd card?
rjmjr69 said:
I dont understand the parrt about
/redbend_ua restore'
where do I place that file in the tools folder of sdk? and clockwork file on root of sd card?
Click to expand...
Click to collapse
In the root of the SD Card.
Fixter said:
In the root of the SD Card.
Click to expand...
Click to collapse
thank you so all three files on root?
Ok so I have been trying to flash the newest oneclick flasher to my Epic all day. NOTHING is working.
The driver downloads in the thread are down but I located them else where. I know nothing is suppose to be mounted and debugging should be on. I have all of that and it still does not go through.
I went through the process of manually rooting the phone through the very first root method....I got root. No superuser app but I had root. So I figured hell the .bat file should work now....WRONG...still i get nothing.
I attached a picture of what happens every time I attempt to run the .bat file.
Maybe I'm making this over complicated since all the phones I've previously rooted were all through adb and a lot more work.
Can I please get some guidance on what I am doing wrong.
Thank you!
Open the .bat file and copy each command manually into command prompt. If you don't have paths set up, you'll have to CD to the directory with ADB (probably the 1-click-whatever folder you downloaded, which you have to do anyway, so might as well do it now). If you get a phone offline or phone disconected error. Just keep running the sam command until it goes through then move on. Copy+paste for safety. Don't worry about the ping commands.
Sent from my SPH-D700 using XDA App
This happened to me too. Use a different micro usb cable than the one the phone came with and it will fix it.
I had same issues..here is what I did:
1) unplugged phone and reset phone..
2) uninstalled the drivers..then reinstalled them.
3) Plugged in the device..
4) this is the hard part that got me...gotta wait for the device to fully install the drivers on the bottom right...I messed up the first time cause I couldn't wait..(This can take up to 5 minutes or so..there are total of 4 drivers that are installed..you need 3/4 to finish..2/4 is not enough and will cause the issues)
5) ran:
adb.exe get-state
it should give you output of "device" and not "unknown"
6) ran run.bat
7) Profit
I had the same problem the first time, but it only happed because I didn't restart my phone
After turning on debugging. When I plugged it into the usb after that it worked fine don"t even recall having to unmount anything.
I had the same issues as well. Then I tried a different laptop and it worked like a charm
And is the best way to know this goes throught superuser application??
Ok so it looks like it is STILL not working.
I uninstalled the drivers, reinstalled them, reset both computer and the phone, plugged the phone in, waited for those to fully install, ran adb.exe get-state it said device this time but now i get this:
exploit and busybox made by joeykrim and one click installer and andromeda galax
y kernel made by noobnl
Press any key to continue . . .
copy and run the exploit (may take 2 minutes)
adb server is out of date. killing...
* daemon started successfully *
175 KB/s (5392 bytes in 0.030s)
1 KB/s (88 bytes in 0.063s)
[*] CVE-2010-EASY Android local root exploit (C) 2010 by 743C
[*] checking NPROC limit ...
[+] RLIMIT_NPROC={3712, 3712}
[*] Searching for adb ...
[+] Found adb as PID 2223
[*] Spawning children. Dont type anything and wait for reset!
[*]
[*] If you like what we are doing you can send us PayPal money to
[*] [email protected] so we can compensate time, effort and HW costs.
[*] If you are a company and feel like you profit from our work,
[*] we also accept donations > 1000 USD!
[*]
[*] adb connection will be reset. restart adb server on desktop and re-login.
remove joeykrim root method
148 KB/s (14428 bytes in 0.095s)
5 KB/s (279 bytes in 0.051s)
rm failed for /system/bin/remount, No such file or directory
rm failed for /system/bin/busybox, No such file or directory
copy kernel and flasher
346 KB/s (313888 bytes in 0.885s)
488 KB/s (6889960 bytes in 13.785s)
flashing kernel
RedBend Update Agent 6,1,14,1
FOTA : Make Block Device Nodes
lcd_init(498): start!
lcd_init(507): fb0 open success
lcd_init(514): width = 480, height = 800
page_msize: 4096, phy_unit_size: 262144
src: /sdcard/zImage
dst: /dev/block/bml7 partition size: 0x780000
part_size: 0x780000
read 262144 bytes
read 262144 bytes
read 262144 bytes
read 262144 bytes
read 262144 bytes
read 262144 bytes
read 262144 bytes
read 262144 bytes
read 262144 bytes
read 262144 bytes
read 262144 bytes
read 262144 bytes
read 262144 bytes
read 262144 bytes
read 262144 bytes
read 262144 bytes
read 262144 bytes
read 262144 bytes
read 262144 bytes
read 262144 bytes
read 262144 bytes
read 262144 bytes
read 262144 bytes
read 262144 bytes
read 262144 bytes
read 262144 bytes
read 74216 bytes
read finished
wait 60 second
cleanup
done
Press any key to continue . . .
Click to expand...
Click to collapse
So what am I doing wrong now??
What would the physical ADB commands look like?? That's always how I have had to root on my phones in the past and I've never had issues. I have had more problems trying this "easy" one click root than with typing out everything myself.
Spectral8x said:
Ok so it looks like it is STILL not working.
I uninstalled the drivers, reinstalled them, reset both computer and the phone, plugged the phone in, waited for those to fully install, ran adb.exe get-state it said device this time but now i get this:
So what am I doing wrong now??
Click to expand...
Click to collapse
From the looks of it your using the 1.3 root with the kernal..what it failed on is to remove the other root (since you didn't have it which is fine)...seems like everything is ok..restart your phone and you should have root.
Hello,
How do I build Android 4.2.2 from source code for the Samsung Galaxy Tab 2 7.0 (GT-P3110)?
I have downloaded the source code in Ubuntu. I need a .zip file that I can flash using Clockworkmod.
Thanks
DD
AndroidRover said:
Hello,
How do I build Android 4.2.2 from source code for the Samsung Galaxy Tab 2 7.0 (GT-P3110)?
I have downloaded the source code in Ubuntu. I need a .zip file that I can flash using Clockworkmod.
Thanks
DD
Click to expand...
Click to collapse
what repo did you download ??
Did you download android source from android website of google?
Or from cm??
Also,
See here http://mobisocial.stanford.edu/news/2011/02/yet-another-tutorial-on-building-android-from-sources/ ,
I guess u need the Step Number 6 , u just compile it (its gonna take hell lot of time) and then flash it from recovery..
Also,
See the official guide released by Android http://source.android.com/source/initializing.html
Buddy google it first then post Nywys i am also considering building one just to expirience the stuff so u got lucky with the links
mhrsolanki2020 said:
what repo did you download ??
Did you download android source from android website of google?
Or from cm??
Click to expand...
Click to collapse
Hello,
I downloaded the code using the instructions on the Android open source website. I don't know what repo version I downloaded yesterday (I probably downloaded the latest). I just followed the instructions on the website.
Thanks
DD
Hello,
I tried this:
Code:
[email protected]:~$ cd Android/device/samsung
[email protected]:~/Android/device/samsung$ git clone https://github.com/Galaxian-Soup/android_device_samsung_espressowifi.git
Cloning into 'android_device_samsung_espressowifi'...
remote: Counting objects: 505, done.
remote: Compressing objects: 100% (276/276), done.
remote: Total 505 (delta 222), reused 460 (delta 177)
Receiving objects: 100% (505/505), 47.51 MiB | 727 KiB/s, done.
Resolving deltas: 100% (222/222), done.
[email protected]:~/Android/device/samsung$ cd android_device_samsung_espressowifi
[email protected]:~/Android/device/samsung/android_device_samsung_espressowifi$ . extract-files.sh
remote object '/system/bin/bcm_dut' does not exist
remote object '/system/bin/fRom' does not exist
180 KB/s (38808 bytes in 0.209s)
remote object '/system/bin/gps.cer' does not exist
482 KB/s (2249856 bytes in 4.555s)
remote object '/system/bin/lpmkey' does not exist
147 KB/s (14656 bytes in 0.096s)
remote object '/system/bin/playlpm' does not exist
29 KB/s (1563 bytes in 0.051s)
387 KB/s (173760 bytes in 0.437s)
93 KB/s (9484 bytes in 0.098s)
212 KB/s (21872 bytes in 0.100s)
remote object '/system/cameradata/datapattern_420sp.yuv' does not exist
remote object '/system/cameradata/datapattern_front_420sp.yuv' does not exist
remote object '/system/lib/libAMSWiFiLibs.so' does not exist
319 KB/s (62784 bytes in 0.191s)
73 KB/s (5108 bytes in 0.068s)
remote object '/system/lib/libion.so' does not exist
141 KB/s (13508 bytes in 0.093s)
84 KB/s (5212 bytes in 0.060s)
175 KB/s (17604 bytes in 0.097s)
86 KB/s (5212 bytes in 0.058s)
177 KB/s (17500 bytes in 0.096s)
171 KB/s (17552 bytes in 0.100s)
176 KB/s (17552 bytes in 0.097s)
195 KB/s (21600 bytes in 0.108s)
452 KB/s (471986 bytes in 1.019s)
121 KB/s (13396 bytes in 0.107s)
58 KB/s (5292 bytes in 0.088s)
153 KB/s (13448 bytes in 0.085s)
459 KB/s (243156 bytes in 0.516s)
341 KB/s (64664 bytes in 0.185s)
remote object '/system/lib/hw/lights.omap4.so' does not exist
280 KB/s (34172 bytes in 0.119s)
remote object '/system/media/battery_batteryerror.qmg' does not exist
remote object '/system/media/battery_charging_0.qmg' does not exist
remote object '/system/media/battery_charging_5.qmg' does not exist
remote object '/system/media/battery_charging_20.qmg' does not exist
remote object '/system/media/battery_charging_40.qmg' does not exist
remote object '/system/media/battery_charging_60.qmg' does not exist
remote object '/system/media/battery_charging_80.qmg' does not exist
remote object '/system/media/battery_charging_100.qmg' does not exist
remote object '/system/media/battery_error.qmg' does not exist
remote object '/system/media/bootsamsung.qmg' does not exist
remote object '/system/media/bootsamsungloop.qmg' does not exist
remote object '/system/media/chargingwarning.qmg' does not exist
remote object '/system/media/Disconnected.qmg' does not exist
93 KB/s (9360 bytes in 0.097s)
remote object '/system/vendor/lib/libglslcompiler.so' does not exist
remote object '/system/vendor/lib/libIMGegl.so' does not exist
remote object '/system/vendor/lib/libpvr2d.so' does not exist
remote object '/system/vendor/lib/libpvrANDROID_WSEGL.so' does not exist
92 KB/s (9188 bytes in 0.096s)
remote object '/system/vendor/lib/libsrv_init.so' does not exist
remote object '/system/vendor/lib/libsrv_um.so' does not exist
remote object '/system/vendor/lib/libusc.so' does not exist
91 KB/s (9136 bytes in 0.097s)
465 KB/s (419004 bytes in 0.879s)
450 KB/s (361660 bytes in 0.783s)
253 KB/s (26652 bytes in 0.102s)
368 KB/s (116136 bytes in 0.307s)
[email protected]:~/Android/device/samsung/android_device_samsung_espressowifi$ cd ~/Android
[email protected]:~/Android$ . build/envsetup.sh
including device/asus/grouper/vendorsetup.sh
including device/asus/tilapia/vendorsetup.sh
including device/generic/armv7-a-neon/vendorsetup.sh
including device/generic/armv7-a/vendorsetup.sh
including device/generic/mips/vendorsetup.sh
including device/generic/x86/vendorsetup.sh
including device/lge/mako/vendorsetup.sh
including device/samsung/android_device_samsung_espressowifi/vendorsetup.sh
including device/ti/panda/vendorsetup.sh
including sdk/bash_completion/adb.bash
[email protected]:~/Android$ lunch full_espressowifi-userdebug
build/core/product_config.mk:228: *** _nic.PRODUCTS.[[device/samsung/android_device_samsung_espressowifi/full_espressowifi.mk]]: "device/samsung/espressowifi/device_espressowifi.mk" does not exist. Stop.
** Don't have a product spec for: 'full_espressowifi'
** Do you have the right repo manifest?
[email protected]:~/Android$
Is this the correct way to go about building android for the P3110? If so where am I going wrong? My P3110 is running CM10.1 RC2. (If that affects adb when I ran extract-files.sh)
Thanks,
DD
AndroidRover said:
Hello,
I tried this:
Code:
[email protected]:~$ cd Android/device/samsung
[email protected]:~/Android/device/samsung$ git clone https://github.com/Galaxian-Soup/android_device_samsung_espressowifi.git
Cloning into 'android_device_samsung_espressowifi'...
remote: Counting objects: 505, done.
remote: Compressing objects: 100% (276/276), done.
remote: Total 505 (delta 222), reused 460 (delta 177)
Receiving objects: 100% (505/505), 47.51 MiB | 727 KiB/s, done.
Resolving deltas: 100% (222/222), done.
[email protected]:~/Android/device/samsung$ cd android_device_samsung_espressowifi
[email protected]:~/Android/device/samsung/android_device_samsung_espressowifi$ . extract-files.sh
remote object '/system/bin/bcm_dut' does not exist
remote object '/system/bin/fRom' does not exist
180 KB/s (38808 bytes in 0.209s)
remote object '/system/bin/gps.cer' does not exist
482 KB/s (2249856 bytes in 4.555s)
remote object '/system/bin/lpmkey' does not exist
147 KB/s (14656 bytes in 0.096s)
remote object '/system/bin/playlpm' does not exist
29 KB/s (1563 bytes in 0.051s)
387 KB/s (173760 bytes in 0.437s)
93 KB/s (9484 bytes in 0.098s)
212 KB/s (21872 bytes in 0.100s)
remote object '/system/cameradata/datapattern_420sp.yuv' does not exist
remote object '/system/cameradata/datapattern_front_420sp.yuv' does not exist
remote object '/system/lib/libAMSWiFiLibs.so' does not exist
319 KB/s (62784 bytes in 0.191s)
73 KB/s (5108 bytes in 0.068s)
remote object '/system/lib/libion.so' does not exist
141 KB/s (13508 bytes in 0.093s)
84 KB/s (5212 bytes in 0.060s)
175 KB/s (17604 bytes in 0.097s)
86 KB/s (5212 bytes in 0.058s)
177 KB/s (17500 bytes in 0.096s)
171 KB/s (17552 bytes in 0.100s)
176 KB/s (17552 bytes in 0.097s)
195 KB/s (21600 bytes in 0.108s)
452 KB/s (471986 bytes in 1.019s)
121 KB/s (13396 bytes in 0.107s)
58 KB/s (5292 bytes in 0.088s)
153 KB/s (13448 bytes in 0.085s)
459 KB/s (243156 bytes in 0.516s)
341 KB/s (64664 bytes in 0.185s)
remote object '/system/lib/hw/lights.omap4.so' does not exist
280 KB/s (34172 bytes in 0.119s)
remote object '/system/media/battery_batteryerror.qmg' does not exist
remote object '/system/media/battery_charging_0.qmg' does not exist
remote object '/system/media/battery_charging_5.qmg' does not exist
remote object '/system/media/battery_charging_20.qmg' does not exist
remote object '/system/media/battery_charging_40.qmg' does not exist
remote object '/system/media/battery_charging_60.qmg' does not exist
remote object '/system/media/battery_charging_80.qmg' does not exist
remote object '/system/media/battery_charging_100.qmg' does not exist
remote object '/system/media/battery_error.qmg' does not exist
remote object '/system/media/bootsamsung.qmg' does not exist
remote object '/system/media/bootsamsungloop.qmg' does not exist
remote object '/system/media/chargingwarning.qmg' does not exist
remote object '/system/media/Disconnected.qmg' does not exist
93 KB/s (9360 bytes in 0.097s)
remote object '/system/vendor/lib/libglslcompiler.so' does not exist
remote object '/system/vendor/lib/libIMGegl.so' does not exist
remote object '/system/vendor/lib/libpvr2d.so' does not exist
remote object '/system/vendor/lib/libpvrANDROID_WSEGL.so' does not exist
92 KB/s (9188 bytes in 0.096s)
remote object '/system/vendor/lib/libsrv_init.so' does not exist
remote object '/system/vendor/lib/libsrv_um.so' does not exist
remote object '/system/vendor/lib/libusc.so' does not exist
91 KB/s (9136 bytes in 0.097s)
465 KB/s (419004 bytes in 0.879s)
450 KB/s (361660 bytes in 0.783s)
253 KB/s (26652 bytes in 0.102s)
368 KB/s (116136 bytes in 0.307s)
[email protected]:~/Android/device/samsung/android_device_samsung_espressowifi$ cd ~/Android
[email protected]:~/Android$ . build/envsetup.sh
including device/asus/grouper/vendorsetup.sh
including device/asus/tilapia/vendorsetup.sh
including device/generic/armv7-a-neon/vendorsetup.sh
including device/generic/armv7-a/vendorsetup.sh
including device/generic/mips/vendorsetup.sh
including device/generic/x86/vendorsetup.sh
including device/lge/mako/vendorsetup.sh
including device/samsung/android_device_samsung_espressowifi/vendorsetup.sh
including device/ti/panda/vendorsetup.sh
including sdk/bash_completion/adb.bash
[email protected]:~/Android$ lunch full_espressowifi-userdebug
build/core/product_config.mk:228: *** _nic.PRODUCTS.[[device/samsung/android_device_samsung_espressowifi/full_espressowifi.mk]]: "device/samsung/espressowifi/device_espressowifi.mk" does not exist. Stop.
** Don't have a product spec for: 'full_espressowifi'
** Do you have the right repo manifest?
[email protected]:~/Android$
Is this the correct way to go about building android for the P3110? If so where am I going wrong? My P3110 is running CM10.1 RC2. (If that affects adb when I ran extract-files.sh)
Thanks,
DD
Click to expand...
Click to collapse
you should be using stock android for that . still it gives problem sometimes..
so what you should do is .. go to www.github.com/TheMuppets/
and download the "vendor_proprietory_samsung" (link : https://github.com/TheMuppets/proprietary_vendor_samsung) and replace it with the equivalent folder in /WORKING_DIRECTORY/vender/OVER-HERE
i downloaded the source from CM so it was /workingdirectory/vendor/samsung so i renamed the old samsung folder to samsungOld and the new "proprietory_samsun_vendor" to samsung .. and then continued with the build by skipping the step of pulling the proprietory blobs (i.e. skip the step of "./extract-files/sh" )
mhrsolanki2020 said:
so what you should do is .. go to
and download the "vendor_proprietory_samsung" (link : ) and replace it with the equivalent folder in /WORKING_DIRECTORY/vender/OVER-HERE
i downloaded the source from CM so it was /workingdirectory/vendor/samsung so i renamed the old samsung folder to samsungOld and the new "proprietory_samsun_vendor" to samsung .. and then continued with the build by skipping the step of pulling the proprietory blobs (i.e. skip the step of "./extract-files/sh" )
Click to expand...
Click to collapse
Hello,
I downloaded the `vendor_proprietory_samsung' in to WORKING_DIRECTORY/vendor and renamed it samsung. I renamed the old folder to samsungOld. I still had the same problem with building android.
Thanks
DD
AndroidRover said:
Hello,
I downloaded the `vendor_proprietory_samsung' in to WORKING_DIRECTORY/vendor and renamed it samsung. I renamed the old folder to samsungOld. I still had the same problem with building android.
Thanks
DD
Click to expand...
Click to collapse
I really am confused... But someone had adviced me not to go to develop pure android from source.. so i chosed the CyanogenMod's source of android .. go here http://wiki.cyanogenmod.org/w/Build_for_p3110 .. it specifically gives instructions for the device ..
it also gives instruction for mine at http://wiki.cyanogenmod.org/w/Build_for_p3100
So its really helpful at cm .. (do not delete the pure android repo though , you might want it after you are comfortable with cm's build process) (also , copy the samsung (the new proprietory files from TheMuppets git) to the /vendor of the cm's repo)
Trying to get XZDR to work on my D6603 with version 23.4.A.0.56 of my firmware. Following [NUT]'s instructions on http://nut.xperia-files.com/
This is what happens on my screen in cmd:
==============================================
= =
= PhilZ Touch, CWM and TWRP Dual Recovery =
= Maintained by [NUT] =
= =
= For Many Sony Xperia Devices! =
= =
==============================================
1. Installation on ROM rooted with SuperSU
2. Installation on ROM rooted with SuperUser
3. Installation on unrooted ROM using the TowelRoot method
4. Install ADB drivers to windows
5. Exit
Please choose install action.
[1,2,3,4,5]?3
* server not running *
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
=============================================
Waiting for Device, connect USB cable now...
=============================================
Device found!
=============================================
Getting ro.build.product
=============================================
Device model is D6603
Firmware is 23.4.A.0.546
=============================================
Step2 : Sending the recovery files.
=============================================
5 KB/s (31 bytes in 0.006s)
1492 KB/s (18340 bytes in 0.012s)
97 KB/s (501 bytes in 0.005s)
1323 KB/s (12198 bytes in 0.009s)
3067 KB/s (65965 bytes in 0.021s)
501 KB/s (3082 bytes in 0.006s)
2193 KB/s (29204 bytes in 0.013s)
220 KB/s (1357 bytes in 0.006s)
1683 KB/s (34473 bytes in 0.020s)
234 KB/s (1202 bytes in 0.005s)
1029 KB/s (96956 bytes in 0.092s)
2482 KB/s (1410852 bytes in 0.555s)
2177 KB/s (3415978 bytes in 1.532s)
2441 KB/s (2420032 bytes in 0.968s)
2286 KB/s (1936117 bytes in 0.827s)
1276 KB/s (11760 bytes in 0.009s)
=============================================
Step3 : Setup of dual recovery.
=============================================
=============================================
Attempting to get root access for installation using TowelRoot now.
NOTE: this only works on certain ROM/Kernel versions!
If it fails, please check the development thread (Post #2) on XDA for more detai
ls.
REMEMBER THIS:
XZDualRecovery does NOT install any superuser app!!
You can use one of the recoveries to root your device.
=============================================
=============================================
Sending files
=============================================
33 KB/s (1776 bytes in 0.052s)
632 KB/s (13592 bytes in 0.021s)
2293 KB/s (197320 bytes in 0.084s)
618 KB/s (9496 bytes in 0.015s)
1112 KB/s (13672 bytes in 0.012s)
Copying kernel module...
1346 KB/s (34473 bytes in 0.025s)
32 KB/s (765 bytes in 0.023s)
1721 KB/s (96956 bytes in 0.055s)
Kernel version is 3.4.0-perf-gc42d8a9-01971-gef29327
Version does not match 3.4.0-perf-ge4322cd, needs patching...
dd: conv option disabled
Kernel module patched.
modulecrcpatch (by zxz0O0)
module_layout: patched to 0xCE969278
__aeabi_unwind_cpp_pr1: match
kallsyms_lookup_name: not found
printk: not found
mem_text_write_kernel_word: not found
__aeabi_unwind_cpp_pr0: match
=============================================
Installing using zxz0O0's towelzxperia
(using geohot's towelroot library)
=============================================
error: only position independent executables (PIE) are supported.
=============================================
Installation finished. Enjoy the recoveries!
=============================================
* server not running *
Press any key to continue . . .
What am I doing wrong? I thought that you didnt need to unlock any bootloader to get dual recovery to work. Pretty new with Sony's products so I might have something.
/Dave
daspunner said:
Trying to get XZDR to work on my D6603 with version 23.4.A.0.56 of my firmware.
What am I doing wrong? I thought that you didnt need to unlock any bootloader to get dual recovery to work. Pretty new with Sony's products so I might have something.
/Dave
Click to expand...
Click to collapse
The problem is 5.1.1 is not directly rootable useing towelroot method. (option 3).
You need to find a method to root the firmware with supersu and select option 1.
Flash a prerooted v.77 4.4.4 ftf first, then you can flash a prerooted v.56 5.11 zip using xzdr.
Googled around a bit and I couldnt figure out how to do. Where do I find the V.77 u are mentioning?
tweker said:
Flash a prerooted v.77 4.4.4 ftf first, then you can flash a prerooted v.56 5.11 zip using xzdr.
Click to expand...
Click to collapse
Never mind, found it!
The best thing about xzdr is it's full backup/restore capabilities. You can save or restore from anywhere, but saving to sd card takes twice as long. I only wish it worked with Sony's built-in full phone encryption. Once phone is encrypted you can kiss xzdr goodbye.
I'm gettin ready to use it as I want to see what existenz y looks and feels like. I like running 5.1.1 but moonwalkers 4.0 changed my LTE to 4G and apparently there is no option but to flash a different radio which I'd rather not mess with atm.
Check MultiRom Mgr off playstore. Requires unlocked bootloader which I haven't done yet.
While connecting usb-cable I am holding volume down. This is recognized by flashtool as entering in flashmode. So far so good! Selecting the correct firmware and flashtool is starting its business. About 30-45 seconds later my phone reboots in to system and the downgrade cant continue. WTF?!
Please help!
-edit-
Worked it out. Let flashtool create its magic and connected phone in flash mode when it asked me.
/Dave
Next problem... *sighs*
(Managed to get .77 firmware on my phone.)
Running the included installer in XZDR and it gets stuck at a certain point, which is when it says libdvm opened (loljavasucks). Not before entering CTRL+C and pressing N when asked if I want to "Terminate batch job (Y/N)?" it continues and says:
=============================================
Installation finished. Enjoy the recoveries!
=============================================
Press any key to continue . . .
Still no dual recovery...
Here is everything that is going on on my screen during installation:
==============================================
= =
= PhilZ Touch, CWM and TWRP Dual Recovery =
= Maintained by [NUT] =
= =
= For Many Sony Xperia Devices! =
= =
==============================================
1. Installation on ROM rooted with SuperSU
2. Installation on ROM rooted with SuperUser
3. Installation on unrooted ROM using the TowelRoot method
4. Install ADB drivers to windows
5. Exit
Please choose install action.
[1,2,3,4,5]?3
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
=============================================
Waiting for Device, connect USB cable now...
=============================================
Device found!
=============================================
Getting ro.build.product
=============================================
Device model is D6603
Firmware is 23.0.1.A.5.77
=============================================
Step2 : Sending the recovery files.
=============================================
7 KB/s (31 bytes in 0.004s)
1989 KB/s (18340 bytes in 0.009s)
122 KB/s (501 bytes in 0.004s)
1701 KB/s (12198 bytes in 0.007s)
2477 KB/s (65965 bytes in 0.026s)
752 KB/s (3082 bytes in 0.004s)
2193 KB/s (29204 bytes in 0.013s)
331 KB/s (1357 bytes in 0.004s)
2244 KB/s (34473 bytes in 0.015s)
293 KB/s (1202 bytes in 0.004s)
2705 KB/s (96956 bytes in 0.035s)
2367 KB/s (1410852 bytes in 0.582s)
2349 KB/s (3415978 bytes in 1.420s)
2168 KB/s (2420032 bytes in 1.090s)
2248 KB/s (1936117 bytes in 0.841s)
1640 KB/s (11760 bytes in 0.007s)
=============================================
Step3 : Setup of dual recovery.
=============================================
=============================================
Attempting to get root access for installation using TowelRoot now.
NOTE: this only works on certain ROM/Kernel versions!
If it fails, please check the development thread (Post #2) on XDA for more detai
ls.
REMEMBER THIS:
XZDualRecovery does NOT install any superuser app!!
You can use one of the recoveries to root your device.
=============================================
=============================================
Sending files
=============================================
867 KB/s (1776 bytes in 0.002s)
3318 KB/s (13592 bytes in 0.004s)
3853 KB/s (197320 bytes in 0.050s)
1854 KB/s (9496 bytes in 0.005s)
1668 KB/s (13672 bytes in 0.008s)
Copying kernel module...
2404 KB/s (34473 bytes in 0.014s)
186 KB/s (765 bytes in 0.004s)
2705 KB/s (96956 bytes in 0.035s)
Kernel version is 3.4.0-perf-g1b1963a-02930-g23f7791
Version does not match 3.4.0-perf-ge4322cd, needs patching...
1+0 records in
0+1 records out
34 bytes transferred in 0.001 secs (34000 bytes/sec)
Kernel module patched.
modulecrcpatch (by zxz0O0)
module_layout: patched to 0xFF791C4F
__aeabi_unwind_cpp_pr1: match
kallsyms_lookup_name: not found
printk: not found
mem_text_write_kernel_word: not found
__aeabi_unwind_cpp_pr0: match
=============================================
Installing using zxz0O0's towelzxperia
(using geohot's towelroot library)
=============================================
towelzxperia (by zxz0O0)
thanks to geohot for libexploit
doing the magic
creating vm (loljavasucks)
libdvm opened (loljavasucks)
^CTerminate batch job (Y/N)? N
=============================================
Installation finished. Enjoy the recoveries!
=============================================
Press any key to continue . . .
Feeling like total noob... Pls help!
/Dave
So I solved this one too... After downgrading even futher to 23.0.A.2.93 I used the giefroot root method and succeded to get the phone rooted. Option 3 in XZDR doesnt work on D6603 i read somewhere in my search for knowledge...
Thx a bunch everybody for the help and I hope my struggles will help others with same issues. I will try to apply this same method once more tomorrow on a D5803. Will get back with info wheter it worked.
/Dave
Yeah first steps first is root. Glad you perservered.
One quick question btw... Are my drm-keys intact? Only used prerooted stock firmware the whole way...
Any way to check that?
Found out how to check the Drm:s. Entered the servicemenu by dialling *#*#7378423#*#*
Hi,
After a botched attempt to install LineageOS 17 on my Samsung Galaxy S5, I decided to revert to LOS16. the problem is that I had completely wiped my device in order to install LOS 17, and my only available 16.x ROM was gone, so I found another ROM on a backup site (October 2020 version).
Once installed, this version did not recognize my SD card where I had stored all my user data. Therefore I dumped the partitions on my Linux PC using dd, and let Android reformat the card.
I dumped 2 individual partitions (not the whole device with the partition table), one of 16Mb, and the other about 29Gb (it's a 32Gb SD card).
Now I want to browse my old data on the backup, but I cannot mount or fsck the partition dumps. the superblock is not recognized as ext*, fat, or even f2fs.
This is all the info I have on the 2 partitions:
Bash:
$ sudo fdisk -l klte-sdc1.img
Disk klte-sdc1.img: 16 MiB, 16777216 bytes, 32768 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
$ sudo fdisk -l klte-sdc2.img
Disk klte-sdc2.img: 29.71 GiB, 31897140736 bytes, 62299103 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Also, for comparison, I dumped the partition table of the currently working SD card:
Bash:
$ sudo fdisk -l /dev/sdc
Disk /dev/sdc: 29.72 GiB, 31914983424 bytes, 62333952 sectors
Disk model: MicroSD/M2
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: gpt
Disk identifier: 35D0FC04-06BD-4578-87FB-D6ED991C03A5
Device Start End Sectors Size Type
/dev/sdc1 2048 34815 32768 16M unknown
/dev/sdc2 34816 62333918 62299103 29.7G unknown
As you see, the partition sizes are identical. I can chance it and dd the original partitions into the new ones, but I don't want to lose recent data on the current partition. I could also corrupt the partition headers if the ones in the backups are corrupt, and be back to square 1.
Can anybody help? Which kind of partition or specialized tools shall I look for?
Thanks,
gm