Develop Bugs

[Q] Unable to update to last Stock (2.3.4) after...

Originally, my Arc was on 2.3.4 Stock, it is allowed for BootLoader unlocking.
I followed this guide to unlock the BootLoader
http://forum.xda-developers.com/showthread.php?t=1042978
I did Step 1, everything fine.
Then i did Step 2, then bad things starts to happen. Even at the command prompt, it state Flash is successful, my Arc got stuck at the Sony Ericsson Logo.
The Remedy I did:
I download the O2 Stock ROM from here
http://forum.xda-developers.com/showthread.php?t=1093523
Reinstall it using the FlashTool.
After reinstalling, I activated the SU using FlashTool.
So Far, everything is fine.
Seeing the Android is at 2.3.3, I connect using Sony Ericsson Phone Companion to attempt to update to 2.3.4.
Phone Companion complained my Firmware disable them from doing it.
Is there anywhere i can get 2.3.4?
Which then still allows me to ROOT, unlock Bootloader and subsequently, remove some of the bloated apps?
Thank you very much!

hello
use THIS to flash via flashtool : http://www.multiupload.com/GQO5RNQ856
and THIS to root your device: http://forum.xda-developers.com/showthread.php?t=1320350
if you don't want to lose root then you can just uncheck Wipe data and wipe cache in flashtool
hope it helped !

realfelix said:
hello
use THIS to flash via flashtool : http://www.multiupload.com/GQO5RNQ856
and THIS to root your device: http://forum.xda-developers.com/showthread.php?t=1320350
if you don't want to lose root then you can just uncheck Wipe data and wipe cache in flashtool
hope it helped !
Click to expand...
Click to collapse
What is the ROM in the first link?
Thks!!

---------------------------------------------------------------
Easy rooting toolkit (v3.0)
created by DooMLoRD
using exploit zergRush (Revolutionary Team)
Credits go to all those involved in making this possible!
---------------------------------------------------------------
[*] This script will:
(1) root ur device using latest zergRush exploit (16 Nov)
(2) install Busybox (1.18.4)
(3) install SU files (binary: 3.0.3 and apk: 3.0.6)
[*] Before u begin:
(1) make sure u have installed adb drivers for ur device
(2) enable "USB DEBUGGING"
from (Menu\Settings\Applications\Development)
(3) enable "UNKNOWN SOURCES"
from (Menu\Settings\Applications)
(4) [OPTIONAL] increase screen timeout to 10 minutes
(5) connect USB cable to PHONE and then connect to PC
(6) skip "PC Companion Software" prompt on device
---------------------------------------------------------------
CONFIRM ALL THE ABOVE THEN
Press any key to continue . . .
--- STARTING ----
--- WAITING FOR DEVICE
adb server is out of date. killing...
ADB server didn't ACK
* failed to start daemon *
error:
--- cleaning
adb server is out of date. killing...
* daemon started successfully *
rm failed for *, No such file or directory
--- pushing zergRush"
adb server is out of date. killing...
* daemon started successfully *
22 KB/s (23056 bytes in 1.000s)
--- correcting permissions
adb server is out of date. killing...
* daemon started successfully *
--- executing zergRush
adb server is out of date. killing...
* daemon started successfully *
[**] Zerg rush - Android 2.2/2.3 local root
[**] (C) 2011 Revolutionary. All rights reserved.
[**] Parts of code from Gingerbreak, (C) 2010-2011 The Android Exploid Crew.
[+] Found a GingerBread ! 0x00015118
[*] Scooting ...
[*] Sending 149 zerglings ...
[+] Zerglings found a way to enter ! 0x10
[+] Overseer found a path ! 0x000151e0
[*] Sending 149 zerglings ...
[+] Zerglings caused crash (good news): 0x2abcccc4 0x0054
[*] Researching Metabolic Boost ...
[+] Speedlings on the go ! 0x6fd19483 0x6fd39847
[*] Popping 24 more zerglings
[*] Sending 173 zerglings ...
[+] Rush did it ! It's a GG, man !
[+] Killing ADB and restarting as root... enjoy!
--- WAITING FOR DEVICE TO RECONNECT
if it gets stuck over here for a long time then try:
disconnect usb cable and reconnect it
toggle "USB DEBUGGING" (first disable it then enable it)
--- DEVICE FOUND
adb server is out of date. killing...
ADB server didn't ACK
* failed to start daemon *
error:
--- pushing busybox
adb server is out of date. killing...
* daemon started successfully *
error: device not found
--- correcting permissions
adb server is out of date. killing...
* daemon started successfully *
error: device not found
--- remounting /system
adb server is out of date. killing...
* daemon started successfully *
error: device not found
--- copying busybox to /system/xbin/
adb server is out of date. killing...
* daemon started successfully *
error: device not found
--- correcting ownership
adb server is out of date. killing...
* daemon started successfully *
error: device not found
--- correcting permissions
adb server is out of date. killing...
* daemon started successfully *
error: device not found
--- installing busybox
adb server is out of date. killing...
* daemon started successfully *
error: device not found
adb server is out of date. killing...
* daemon started successfully *
error: device not found
--- pushing SU binary
adb server is out of date. killing...
* daemon started successfully *
error: device not found
--- correcting ownership
adb server is out of date. killing...
* daemon started successfully *
error: device not found
--- correcting permissions
adb server is out of date. killing...
* daemon started successfully *
error: device not found
--- correcting symlinks
adb server is out of date. killing...
* daemon started successfully *
rm failed for /system/xbin/su, Read-only file system
adb server is out of date. killing...
* daemon started successfully *
link failed Read-only file system
--- pushing Superuser app
adb server is out of date. killing...
* daemon started successfully *
failed to copy 'files\Superuser.apk' to '/system/app/./Superuser.apk': Read-only
file system
--- cleaning
adb server is out of date. killing...
* daemon started successfully *
--- rebooting
adb server is out of date. killing...
* daemon started successfully *
ALL DONE!!!
Press any key to continue . . .
Click to expand...
Click to collapse
I have this all over the execution
adb server is out of date. killing...
Another error is this
rm failed for /system/xbin/su, Read-only file system
adb server is out of date. killing...
* daemon started successfully *
link failed Read-only file system
--- pushing Superuser app
adb server is out of date. killing...
* daemon started successfully *
failed to copy 'files\Superuser.apk' to '/system/app/./Superuser.apk': Read-only
file system
My phone is able to boot up after the installation, how to i verify whether the objective of the bat file is achieved?
Thank you.

It is the 4.0.A.2.0.58 generic HK(World) firmware
Sent from my LT15i using XDA App

realfelix said:
It is the 4.0.A.2.0.58 generic HK(World) firmware
Sent from my LT15i using XDA App
Click to expand...
Click to collapse
Ok. Thank you!
my arc is currently on Android 2.3.4
and the bootloader is unlocked.
i can install titanium backup, so i think everything should be fine!
Thank you very much!!

Cannot remove revolutionary from phone (hboot?)

I have followed this guide twice now, but when I reboot the phone with Vol Down + Power, I still get the revolutionary screen:
http://forums.androidcentral.com/in...uide-unroot-revolutionary-incredible-2-a.html
Is this the hboot image that revolutionary is using? Why is it still on the phone after running these commands?
C:\Users\Bro\Desktop\unroot>adb push busybox /data/local/
2353 KB/s (1062992 bytes in 0.441s)
C:\Users\Bro\Desktop\unroot>adb push hboot_0.97.0000_336906.nb0 /data/local/
2250 KB/s (1048576 bytes in 0.455s)
C:\Users\Bro\Desktop\unroot>adb shell chmod 777 /data/local/psneuter
C:\Users\Bro\Desktop\unroot>adb shell chmod 777 /data/local/busybox
C:\Users\Bro\Desktop\unroot>adb shell /data/local/psneuter
property service neutered.
killing adbd. (should restart in a second or two)
C:\Users\Bro\Desktop\unroot>adb shell /data/local/busybox md5sum /data/local
/hboot_0.97.0000_336906.nb0
adb server is out of date. killing...
* daemon started successfully *
affe3dc9abe9d3a8c8bb3ba0ee5176ac /data/local/hboot_0.97.0000_336906.nb0
C:\Users\Bro\Desktop\unroot>adb shell dd if=/data/local/hboot_0.97.0000_3369
06.nb0 of=/dev/block/mmcblk0p18
2048+0 records in
2048+0 records out
1048576 bytes transferred in 0.275 secs (3813003 bytes/sec)
C:\Users\Bro\Desktop\unroot>adb shell /data/local/busybox md5sum /dev/block/
mmcblk0p18
adb server is out of date. killing...
* daemon started successfully *
affe3dc9abe9d3a8c8bb3ba0ee5176ac /dev/block/mmcblk0p18

[Q] Totally bricked kindle after 1st attempt at adding TWRP. No power on at all.

I was following the steps on the lilputing dot com website (I cant provide links yet) to install TWRP so I could then install Cynogenmod.
These are the exact commands I entered, I got a "No space left on device" error at one point, something I noticed after I bricked the device. I'm sure this is the cause of the problem:
Code:
C:\u-boot-firefirefire-1.2>adb push u-boot.bin /sdcard/
[I][COLOR="DimGray"]2251 KB/s (216164 bytes in 0.093s)[/COLOR][/I]
C:\u-boot-firefirefire-1.2>adb push openrecovery-twrp-2.2.0-blaze.img /sdcard/
[I][COLOR="DimGray"]3962 KB/s (5578752 bytes in 1.375s)[/COLOR][/I]
C:\u-boot-firefirefire-1.2>adb shell
[email protected]:/ $ su
su
[email protected]:/ # dd if=/sdcard/openrecovery-twrp-2.2.0-blaze.img of=/dev/block/mmcblk0p5
[COLOR="DimGray"][I]p-2.2.0-blaze.img of=/dev/block/mmcblk0p5
[B]/dev/block/mmcblk0p5: write error: No space left on device[/B]
129+0 records in
128+0 records out
65536 bytes transferred in 0.011 secs (5957818 bytes/sec)[/I][/COLOR]
[email protected]:/ # dd if=/sdcard/u-boot.bin of=/dev/block/mmcblk0p2
[COLOR="DimGray"][I]dd if=/sdcard/u-boot.bin of=/dev/block/mmcblk0p2
422+1 records in
422+1 records out
216164 bytes transferred in 0.061 secs (3543672 bytes/sec)[/I][/COLOR]
[email protected]:/ # exit
C:\u-boot-firefirefire-1.2>adb reboot
After the reboot statement the device shut down but never came back.
I fear I have killed the Kindle (my sons Kindle ). It is not recognised at all via usb into the computer. There is no power light when I put on charge. Have tried holding down power button for over a minute but still nothing. Would I be right in thinking this is totally unrecoverable?

If there is to be a solution to your problem, it will get figured out here:
http://forum.xda-developers.com/showthread.php?t=2622218
Sent from my Nexus 7 using Tapatalk

Fly_Trap said:
I was following the steps on the lilputing dot com website (I cant provide links yet) to install TWRP so I could then install Cynogenmod.
These are the exact commands I entered, I got a "No space left on device" error at one point, something I noticed after I bricked the device. I'm sure this is the cause of the problem:
Code:
C:\u-boot-firefirefire-1.2>adb push u-boot.bin /sdcard/
[I][COLOR="DimGray"]2251 KB/s (216164 bytes in 0.093s)[/COLOR][/I]
C:\u-boot-firefirefire-1.2>adb push openrecovery-twrp-2.2.0-blaze.img /sdcard/
[I][COLOR="DimGray"]3962 KB/s (5578752 bytes in 1.375s)[/COLOR][/I]
C:\u-boot-firefirefire-1.2>adb shell
[email protected]:/ $ su
su
[email protected]:/ # dd if=/sdcard/openrecovery-twrp-2.2.0-blaze.img of=/dev/block/mmcblk0p5
[COLOR="DimGray"][I]p-2.2.0-blaze.img of=/dev/block/mmcblk0p5
[B]/dev/block/mmcblk0p5: write error: No space left on device[/B]
129+0 records in
128+0 records out
65536 bytes transferred in 0.011 secs (5957818 bytes/sec)[/I][/COLOR]
[email protected]:/ # dd if=/sdcard/u-boot.bin of=/dev/block/mmcblk0p2
[COLOR="DimGray"][I]dd if=/sdcard/u-boot.bin of=/dev/block/mmcblk0p2
422+1 records in
422+1 records out
216164 bytes transferred in 0.061 secs (3543672 bytes/sec)[/I][/COLOR]
[email protected]:/ # exit
C:\u-boot-firefirefire-1.2>adb reboot
After the reboot statement the device shut down but never came back.
I fear I have killed the Kindle (my sons Kindle ). It is not recognised at all via usb into the computer. There is no power light when I put on charge. Have tried holding down power button for over a minute but still nothing. Would I be right in thinking this is totally unrecoverable?
Click to expand...
Click to collapse
Cause of the problem is that the above method does not work for the latest software version 6.3.2

androvista said:
Cause of the problem is that the above method does not work for the latest software version 6.3.2
Click to expand...
Click to collapse
So, @androvista, is there a solution?
Sent from my Nexus 7 using Tapatalk

jma9454 said:
So, @androvista, is there a solution?
Sent from my Nexus 7 using Tapatalk
Click to expand...
Click to collapse
did you get it figured out? i have same prob

Fly_Trap said:
I was following the steps on the lilputing dot com website (I cant provide links yet) to install TWRP so I could then install Cynogenmod.
These are the exact commands I entered, I got a "No space left on device" error at one point, something I noticed after I bricked the device. I'm sure this is the cause of the problem:
Code:
C:\u-boot-firefirefire-1.2>adb push u-boot.bin /sdcard/
[I][COLOR="DimGray"]2251 KB/s (216164 bytes in 0.093s)[/COLOR][/I]
C:\u-boot-firefirefire-1.2>adb push openrecovery-twrp-2.2.0-blaze.img /sdcard/
[I][COLOR="DimGray"]3962 KB/s (5578752 bytes in 1.375s)[/COLOR][/I]
C:\u-boot-firefirefire-1.2>adb shell
[email protected]:/ $ su
su
[email protected]:/ # dd if=/sdcard/openrecovery-twrp-2.2.0-blaze.img of=/dev/block/mmcblk0p5
[COLOR="DimGray"][I]p-2.2.0-blaze.img of=/dev/block/mmcblk0p5
[B]/dev/block/mmcblk0p5: write error: No space left on device[/B]
129+0 records in
128+0 records out
65536 bytes transferred in 0.011 secs (5957818 bytes/sec)[/I][/COLOR]
[email protected]:/ # dd if=/sdcard/u-boot.bin of=/dev/block/mmcblk0p2
[COLOR="DimGray"][I]dd if=/sdcard/u-boot.bin of=/dev/block/mmcblk0p2
422+1 records in
422+1 records out
216164 bytes transferred in 0.061 secs (3543672 bytes/sec)[/I][/COLOR]
[email protected]:/ # exit
C:\u-boot-firefirefire-1.2>adb reboot
After the reboot statement the device shut down but never came back.
I fear I have killed the Kindle (my sons Kindle ). It is not recognised at all via usb into the computer. There is no power light when I put on charge. Have tried holding down power button for over a minute but still nothing. Would I be right in thinking this is totally unrecoverable?
Click to expand...
Click to collapse
Hello
You can try doing the following
Install Minimal Fastboot and ADB, you can find a thread here on xda.
Type in when connected to kindle from pc, abd devices.
If you see any long serial number type in adb reboot recovery
Then adb reboot bootloader, either way the kindle should go into recovery after step one, and there you could get factory reset. It worked for me. Just check out the link, thanks to SnegovikRZN http://forum.xda-developers.com/showthread.php?t=2530623

[Q] Trouble updating Kodi on AFTV

I am running a rooted Amazon Fire TV with Kodi 14.0. I decided to update it to 14.2
I downloaded kodi-14.2-Helix-armeabi-v7a.apk from Kodi.tv.
First I tried adbfire to install it. It seemed to go OK except that the progress bar keeps going from left to right over and over. After about 20 min, I killed it and tried using the adb command line.
I ran cmd as admin and typed these commands
adb kill-server
adb start-server
adb connect 192.168.1.3
adb install -r kodi-14.2-Helix-armeabi-v7a.apk
and got this output
C:\Windows\system32>adb kill-server
C:\Windows\system32>adb start-server
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
C:\Windows\system32>adb connect 192.168.1.3
connected to 192.168.1.3:5555
C:\Windows\system32>e:
E:\>cd users
E:\Users>cd downloads
E:\Users\Downloads>adb install -r kodi-14.2-Helix-armeabi-v7a.apk
3084 KB/s (62638253 bytes in 19.833s)
pkg: /data/local/tmp/kodi-14.2-Helix-armeabi-v7a.apk
At this point it hangs indefinately.
Any ideas?

Bonnie_Raitt said:
I am running a rooted Amazon Fire TV with Kodi 14.0. I decided to update it to 14.2
I downloaded kodi-14.2-Helix-armeabi-v7a.apk from Kodi.tv.
First I tried adbfire to install it. It seemed to go OK except that the progress bar keeps going from left to right over and over. After about 20 min, I killed it and tried using the adb command line.
I ran cmd as admin and typed these commands
adb kill-server
adb start-server
adb connect 192.168.1.3
adb install -r kodi-14.2-Helix-armeabi-v7a.apk
and got this output
C:\Windows\system32>adb kill-server
C:\Windows\system32>adb start-server
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
C:\Windows\system32>adb connect 192.168.1.3
connected to 192.168.1.3:5555
C:\Windows\system32>e:
E:\>cd users
E:\Users>cd downloads
E:\Users\Downloads>adb install -r kodi-14.2-Helix-armeabi-v7a.apk
3084 KB/s (62638253 bytes in 19.833s)
pkg: /data/local/tmp/kodi-14.2-Helix-armeabi-v7a.apk
At this point it hangs indefinately.
Any ideas?
Click to expand...
Click to collapse
Apparently, I'm impatient. After an hour it said success

Stuck in recovery.

Hi.
dev: d820n Europe
Had rooted lp with twrp but wanted to go back to stock.
Dl this
http://forum.xda-developers.com/desire-820/general/recovery-stock-recovery-lollipop-5-0-1-t3236989
and now i only can boot to recovery, but twrp. can't boot normal, or bootloader.
Tried to reinstall boot from backed up KK but still nothing...
boots when connected to pc and vol up + power boots recovery (managed to install twrp2.8 XianShiDeNiWo)
boots vol up + power 8 sec+ to recovery.
C:\adb>adb reboot
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
C:\adb>adb reboot recovery
adb server is out of date. killing...
* daemon started successfully *
C:\adb>adb reboot bootloader
adb server is out of date. killing...
* daemon started successfully *
C:\adb>
C:\adb>adb shell reboot
adb server is out of date. killing...
* daemon started successfully *
/sbin/sh: reboot: not found
Click to expand...
Click to collapse
all those still reboots to recovery
Any ideas what can I do?