Develop Bugs

Followed ALL steps one by one, small problem now.

Well i used the OTA Simple Root and it worked, but now everytime i try to go into recovery (power plus volume down) it searches the files again and tries to run all the updates and reboot the system. Then when i skip that and try to go to recovery to update a rom i get a black screen with a red triangle and cant get to the recovery menu even. I did one time and i was in boot loop.
My questions are these, how can i set my phone back to completely stock with nothing on the sd card but what i need.
Is there anyway to fix this with out having to start all over again?

Easier fix is to install Rom manager. Once inside tell it to flash clockwork recovery. Boom. Have recovery again.
Sent from my EVO

Delete any files named PC36IMG.zip from the root of your SD card. Then either flash Amon_RA's or Koush's Clockwork recovery.

===============================================================
===============================================================
Simple Root 1.47.651.1 OTA Edition
===============================================================
===============================================================
* server not running *
===============================================================
Pushing files, PLEASE WAIT!.....
===============================================================
* daemon not running. starting it now *
* daemon started successfully *
912 KB/s (26172 bytes in 0.028s)
1209 KB/s (655360 bytes in 0.529s)
160 KB/s (1813 bytes in 0.011s)
17 KB/s (424 bytes in 0.024s)
107 KB/s (1754 bytes in 0.016s)
cannot stat 'PC36IMG.zip': No such file or directory
Pushing complete!
Press any key to continue . . .
I formated my sd card and tried to start simple root over again and after step one i get this message, what does it mean and how can i fix it? thanks for the fast replies.

twigums said:
===============================================================
===============================================================
Simple Root 1.47.651.1 OTA Edition
===============================================================
===============================================================
* server not running *
===============================================================
Pushing files, PLEASE WAIT!.....
===============================================================
* daemon not running. starting it now *
* daemon started successfully *
912 KB/s (26172 bytes in 0.028s)
1209 KB/s (655360 bytes in 0.529s)
160 KB/s (1813 bytes in 0.011s)
17 KB/s (424 bytes in 0.024s)
107 KB/s (1754 bytes in 0.016s)
cannot stat 'PC36IMG.zip': No such file or directory
Pushing complete!
Press any key to continue . . .
I formated my sd card and tried to start simple root over again and after step one i get this message, what does it mean and how can i fix it? thanks for the fast replies.
Click to expand...
Click to collapse
Download whichever PC36IMG.zip file is relevant to that method and place it on the root of your SD card.

me thinks the PC36IMG.zip is in included in the OTA simple root zip file, just copy it to the root of your SDCARD using the phone as a USB drive

whit's "Start over" method will work since he has partial root. and it'll update radios appropriately.

Try use toast method 2 nand unlocking and flash the recovery image. Should work just fine.
Sent from my PC36100 using XDA App

i think i found the problem, down load was messed up for simple root, redld it and having no problems so far (crosses fingers)

[Q] Trying to root. Cannot enter recovery (nor Philz nor TWRP): bootloop

Hi evreyone !
I spent hours trying and reading posts everywhere I could without any success.
I'm trying to follow this rooting guide: http://forum.xda-developers.com/showthread.php?t=2634196 (Root and Dual Recovery for Locked Bootloader) and I'm stuck in a bootloop at step 10.
I'm using the last Z1C-lockeddualrecovery2.7.117-BETA.installer.zip and I noticed an error during recovery installation (after DEVICE WILL NOW REBOOT!):
Code:
##########################################################
#
# Installing XZDR version 2.7.117 BETA
#
#####
Temporarily disabling the RIC service, remount rootfs and /system writable to allow installation.
Copy recovery files to system.
Copy mr wrapper script to system.
Copy chargemon script to system.
Copy dualrecovery.sh to system.
Copy rickiller.sh to system.
Installing NDRUtils to system.
Copy busybox to system.
Trying to find and update the gpio-keys event node.
Found and will be using /dev/input/event4!
Trying to find and update the power key event node.
Found and will be monitoring /dev/input/event3!
Speeding up backups.
Make sure firstboot goes to recovery.
=============================================
DEVICE WILL NOW REBOOT!
=============================================
Error type 2
android.util.AndroidException: Can't connect to activity manager; is the system running?
at com.android.commands.am.Am.run(Am.java:101)
at com.android.commands.am.Am.main(Am.java:82)
at com.android.internal.os.RuntimeInit.nativeFinishInit(Native Method)
at com.android.internal.os.RuntimeInit.main(RuntimeInit.java:235)
at dalvik.system.NativeStart.main(Native Method)
=============================================
REMEMBER THIS:
XZDualRecovery does NOT install any superuser app!!
You can use one of the recoveries to root your device.
=============================================
Waiting for your device to reconnect.
After entering CWM for the first time, reboot to system to complete this installer if you want it to clean up after itself.
=============================================
Installation finished. Enjoy the recoveries!
=============================================
(Note that I'm using Linux... I tried to run the bash script both as a user or as root)
If I continue the rooting process by flashing D5503_14.2.A.1.114_Generic UK.ftf (step 9), I'm stuck at step 10 as I can't boot any recovery. The phone is stuck in a bootloop, and after the green light pressing vol up (ou down) won't do anything...
I tried the whole process (from the begining: docomo) several time and end up everytime with the same result: an error at the end of the recovery installation and a bootloop at step 10 that prevent me from entering any recovery...
I'm out of ideas ! What can I do to manage the installation of the recovery ?

OldBeurt said:
What can I do to manage the installation of the recovery ?
Click to expand...
Click to collapse
Try a newer guide - http://forum.xda-developers.com/showthread.php?t=2688933

Thanks for your answer !
XperienceD said:
Try a newer guide - http://forum.xda-developers.com/showthread.php?t=2688933
Click to expand...
Click to collapse
Since I don't have access to any recovery, I don't understand how I can follow this guide (step 5: Go to recovery menu[...]).
What did you meant ?

OldBeurt said:
I don't understand how I can follow this guide (step 5: Go to recovery menu[...])
Click to expand...
Click to collapse
Read the requirements and it links to how to root, and if you can't or won't unlock your bootloader then you're going to have to jump through hoops.

XperienceD said:
Read the requirements and it links to how to root, and if you can't or won't unlock your bootloader then you're going to have to jump through hoops.
Click to expand...
Click to collapse
Of course I red the requirements. The root method described is the same (http://forum.xda-developers.com/showthread.php?t=2642081) than the one I followed (http://forum.xda-developers.com/showthread.php?t=2634196). And so the result is going to be the same: being stuck in a bootloop after flashing the recovery form the computer (flashing witch returns an error that I quoted above).
I need help to "recover" the recovery, I mean to be able to properly flash the dual recovery on my phone (whether I wish to unlock the bootloader or not is not the point for now, since I need to root with the locked bootloader in the first place).

It's obvious that there is an error while installing dualrecovery. However I don't know what could cause that error. I advise you to try install it on a fresh ubuntu / Windows client.
Edit: You are executing the install.sh script right? Because at first you select option 3, which is missing in your output. It looks like you are simply executing installrecovery.sh which is of course wrong.

Thanks for your input !
zxz0O0 said:
It's obvious that there is an error while installing dualrecovery. However I don't know what could cause that error. I advise you to try install it on a fresh ubuntu / Windows client.
Click to expand...
Click to collapse
I don't know where the error came from, but I tried several times (about 10) and it end up the same way ! I will try on another machine (Linux too).
zxz0O0 said:
Edit: You are executing the install.sh script right? Because at first you select option 3, which is missing in your output. It looks like you are simply executing installrecovery.sh which is of course wrong.
Click to expand...
Click to collapse
Yes I'm using install.sh, I just pasted the relevat part of the output, but here I paste all of it:
Code:
Will attempt to get root to install!
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
=============================================
Step1 : Waiting for Device.
=============================================
Succes
=============================================
Step2 : Sending the recovery files.
=============================================
mkdir failed for /data/local/tmp/recovery, File exists
0 KB/s (29 bytes in 0.056s)
362 KB/s (17768 bytes in 0.047s)
325 KB/s (15578 bytes in 0.046s)
11 KB/s (501 bytes in 0.043s)
272 KB/s (11791 bytes in 0.042s)
3186 KB/s (44383 bytes in 0.013s)
70 KB/s (3082 bytes in 0.042s)
9 KB/s (385 bytes in 0.041s)
3645 KB/s (657704 bytes in 0.176s)
3521 KB/s (2597754 bytes in 0.720s)
3936 KB/s (1842873 bytes in 0.457s)
5217 KB/s (2447499 bytes in 0.458s)
193 KB/s (8124 bytes in 0.041s)
=============================================
Step3 : Setup of dual recovery.
=============================================
=============================================
Attempting to get root access for installation using rootkitXperia now.
NOTE: this only works on certain ROM/Kernel versions!
If it fails, please check the development thread on XDA for more details.
=============================================
ro.build.product=C6903
ro.build.id=14.1.G.1.534
search kallsyms...
1 2 3 4
(kallsyms_addresses=c0899410)
(kallsyms_num_syms=00014df1)
kernel dump...
1 2 3 4 5 6 7 8 9
prepare_kernel_cred=c00b89f4
commit_creds=c00b8518
ptmx_fops=c0ea365c
Succeeded in getroot!
##########################################################
#
# Installing XZDR version 2.7.117 BETA
#
#####
Temporarily disabling the RIC service, remount rootfs and /system writable to allow installation.
Copy recovery files to system.
Copy mr wrapper script to system.
Copy chargemon script to system.
Copy dualrecovery.sh to system.
Copy rickiller.sh to system.
Installing NDRUtils to system.
Copy busybox to system.
Trying to find and update the gpio-keys event node.
Found and will be using /dev/input/event4!
Trying to find and update the power key event node.
Found and will be monitoring /dev/input/event3!
Speeding up backups.
Make sure firstboot goes to recovery.
=============================================
DEVICE WILL NOW REBOOT!
=============================================
Error type 2
android.util.AndroidException: Can't connect to activity manager; is the system running?
at com.android.commands.am.Am.run(Am.java:101)
at com.android.commands.am.Am.main(Am.java:82)
at com.android.internal.os.RuntimeInit.nativeFinishInit(Native Method)
at com.android.internal.os.RuntimeInit.main(RuntimeInit.java:235)
at dalvik.system.NativeStart.main(Native Method)
=============================================
REMEMBER THIS:
XZDualRecovery does NOT install any superuser app!!
You can use one of the recoveries to root your device.
=============================================
Waiting for your device to reconnect.
After entering CWM for the first time, reboot to system to complete this installer if you want it to clean up after itself.
=============================================
Installation finished. Enjoy the recoveries!
=============================================

[SOLVED] stuck on sony logo after trying to root :S

alohaa guys,first post and thread
sinds i cant post in the developers thread
ill post here
as the title says im stuck on the sony logo,after trying to root my z1c
flashtool still see my phone,but it says :device connected with USB debugging off
i tried a couple of times to get in the recovery menu,boot phone,and press either volume up or down S:
nothing ever happens it just shows the sony logo and dissapears,then it comes back again :S
i got the proper files on the mirco sd card,as written in the tutorial
http://forum.xda-developers.com/showthread.php?t=2642081
any help is appriciated,and i will look further also in the trheads if i can find a solution for this,but havent found anything yet,if there is any

I made the mistake to first connect the phone to the PC and then running flash tool. Try to start the flashtool first. When it asks You to connect the phone do so ( I think in fastboot mode).
Then the ftf files should be flashed properly and the phone boot up normally
Gesendet von meinem D5503 mit Tapatalk

konsi said:
I made the mistake to first connect the phone to the PC and then running flash tool. Try to start the flashtool first. When it asks You to connect the phone do so ( I think in fastboot mode).
Then the ftf files should be flashed properly and the phone boot up normally
Gesendet von meinem D5503 mit Tapatalk
Click to expand...
Click to collapse
yes flash tool was already running before,so it detects the phone,i tried flashing again and this time it worked,eg just the flashing
at .16 of the tutorial i posted a link of i flashed D5503_14.3.A.0.681_Generic_UK-nosystem.ftf ,but then afterward,still same logo from sony comes and goes,but it doesnt get in recovery mode S:
before i flash anything more,ill wait for anwers,i geuss overflashing doesnt exist but i very uncertian of what im doing now
btw thanks for the quick reply
edit this is what unroot gave me http ://i61.tinypic.com/jhufyg.png

Well, I'm a noob as well
I did the root process with instructions from another thread which was called noob proof it doesn't unlock the bootloader though. I don't have the link right now. But it is one on the top of the forum.
Btw the rooting process of this phone is IMHO very complicated.
Edit: sorry, I didn't see it was this thread you are talking about. I used the same ?
Gesendet von meinem D5503 mit Tapatalk

Please start again from step 1 of the guide. Post the output of dualrecovery installer once you run it.
Bootloop can be caused by multiple mistakes the user did.

konsi said:
Well, I'm a noob as well
I did the root process with instructions from another thread which was called noob proof it doesn't unlock the bootloader though. I don't have the link right now. But it is one on the top of the forum.
Btw the rooting process of this phone is IMHO very complicated.
Edit: sorry, I didn't see it was this thread you are talking about. I used the same ?
Gesendet von meinem D5503 mit Tapatalk
Click to expand...
Click to collapse
lol,i read a few pages further, this post it says start over again from step 1,if sony logo keeps coming up,and no green light flashes
http://forum.xda-developers.com/showpost.php?p=50227041&postcount=19
i will try again S:
edit: thanks @ zxz0O0 ill try D:

I would've done the same. Report if you succeed
Gesendet von meinem D5503 mit Tapatalk

guys thanks for the help,i managed to root my xperia z1c
and i think i know what went wrong,the first time i used Z1C-lockeddualrecovery2.7.123-BETA.installer
with option 3 [Installation on unrooted ROM]
at exact same time windows explorer crashed dont know why,but that resulted in a protocol failure??,and afterwards could not connect to device
error :device not found , it said a few times
this is why i could not get in the recoverymode
after starting at step 1 again
and i could start/boot with the flashed docomo firmware,i was very reliefed (btw whats up with that docomo sheep walking on the screen lol)
and useing Z1C-lockeddualrecovery2.7.123-BETA.installer, install.bat for the 2nd time i saw the difference
this time it gave me this
Code:
==============================================
= =
= 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 ]
[ 4. Exit ]
Please choose install action. [1,2,3,4]?3
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
=============================================
Waiting for Device, connect USB cable now...
=============================================
Device found
=============================================
Step2 : Sending the recovery files.
=============================================
0 KB/s (29 bytes in 0.457s)
19 KB/s (17768 bytes in 0.907s)
415 KB/s (15759 bytes in 0.037s)
163 KB/s (501 bytes in 0.003s)
720 KB/s (11798 bytes in 0.016s)
2405 KB/s (56662 bytes in 0.023s)
1003 KB/s (3082 bytes in 0.003s)
6 KB/s (385 bytes in 0.056s)
1316 KB/s (657704 bytes in 0.488s)
3564 KB/s (2602457 bytes in 0.713s)
3150 KB/s (2464762 bytes in 0.764s)
2776 KB/s (1845018 bytes in 0.649s)
234 KB/s (8658 bytes in 0.036s)
=============================================
Step3 : Setup of dual recovery.
=============================================
=============================================
Attempting to get root access for installation using rootkitXperia now.
NOTE: this only works on certain ROM/Kernel versions
If it fails, please check the development thread (Post #2) on XDA for more deta
ls.
REMEMBER THIS:
XZDualRecovery does NOT install any superuser app
You can use one of the recoveries to root your device.
=============================================
ro.build.product=C6903
ro.build.id=14.1.G.1.534
search kallsyms...
1 2 3 4
(kallsyms_addresses=c0899410)
(kallsyms_num_syms=00014df1)
kernel dump...
1 2 3 4 5 6 7 8 9
prepare_kernel_cred=c00b89f4
commit_creds=c00b8518
ptmx_fops=c0ea365c
Succeeded in getroot!
/data/local/tmp/recovery/install.sh: line 23: /system/xbin/busybox: not found
/data/local/tmp/recovery/install.sh: line 23: /system/bin/busybox: not found
##########################################################
#
# Installing XZDR version 2.7.123 BETA
#
#####
Temporarily disabling the RIC service, remount rootfs and /system writable to a
low installation.
Copy recovery files to system.
Rename stock mr
Copy mr wrapper script to system.
Rename stock chargemon
Copy chargemon script to system.
Copy dualrecovery.sh to system.
Copy rickiller.sh to system.
Installing NDRUtils to system.
Creating /system/.XZDualRecovery to store a backup copy of busybox.
Copy busybox to system.
Trying to find and update the gpio-keys event node.
Found and will be using /dev/input/event4!
Trying to find and update the power key event node.
Found and will be monitoring /dev/input/event3!
Speeding up backups.
Make sure firstboot goes to recovery.
=============================================
DEVICE WILL NOW TRY A DATA SAFE REBOOT!
=============================================
=============================================
Your installation has already cleaned up after itself if you see the install.ba
/install.sh exit.
=============================================
=============================================
Installation finished. Enjoy the recoveries
=============================================
the rest was a piece of cake
thanks for all the very quick responses
this thread can be deleted by the mods if they wish to
or leave it for people with the same bad luck as me

[Q] twrp v2.7.1.0 corrupting zips iorooted lg v50020b

Hey peeps,
had to register today as never not been able to find a solution by searching, first time for everything!
Not long had my lg g pad v500 came with 20b 4.4.2 installed.
i have rooted using the ioroot method mentioned within the g pad section on here and then installed twrp v 2.7.1.0.(apologies, got somany tabsup i cant find where i got the recovery iinstall from)
i am trying to install various roms - mainly the slimkat latest 4.4.4 build, But TWRP seems to be corrupting the roms on this version. I know its not the zip/roms and i have read that this version is no good for installs!
Just tried jumping back to 2.3.6.2 as mentioned in the post below but get errors! I'm normally a CWM guy but twrp seemed the better choice after reading some posts!
http://forum.xda-developers.com/showthread.php?t=2641409
Code:
Install Recovery...
3365 KB/s (358400 bytes in 0.104s)
3059 KB/s (72056 bytes in 0.023s)
3043 KB/s (11016192 bytes in 3.535s)
/dev/block/platform/msm_sdcc.1/by-name/aboot: cannot open for read: Permission d
enied
Unable to open /data/local/tmp/aboot.img: No such file or directory
[+] loki_patch v2.1
[-] Failed to open /data/local/tmp/aboot.img for reading.
[+] loki_flash v2.1
[-] Failed to open aboot for reading.
Reboot into recovery now [yes/no]?
any ideas/direction on how i can jump back to lower stable twrp versions?

Xperia Z Recovery Installation can't find needed files

Hello. Sorry for my (german) English.
After hours and hours testing I must ask the forum.
I have rootet some phones yet, but with the Sony Xperia Z 6603 I don't know what to do anymore.
I followed this help:
techbeasts.com/install-cwmtwrp-recovery-root-xperia-z-107a0228-firmware/
Sorry, I'm not allowed to format a extern link.
(Some things seems to has changed since the help was written. The links to EasyRootTool goes to One Click Root Tool, and in others helps the needed SDK is now Android Studio whith maybe other Filestructures, so I read)
I have (under windows 10)
1. Downgrade to .283 Firmware and rooted
The problem is at point
f: Download latest installer for Xperia Z (Z-lockeddualrecovery2.8.xx-RELEASE.installer.zip)
I have downloaded a Package XZDualRecovery-2.8-RELEASE. Hope that that is the right one.
A help tells me, that I should start a install.bat from that folder. This file is in the folder /src/ of the recovery-package.
I start the install.bat from there. At this point I don't know which option I should choose, because in the help bevor there was no word about SuperSU or other.
Code:
1. Installation on ROM rooted with SuperSU
2. Installation on ROM rooted with SuperUser
3. Installation on an unrooted (Lollipop 5.0) ROM using rootkitXperia
4. Install ADB drivers to windows
I press "1" for luck and get the answers at the bottom of this post.
Ergo: I have no recovery installed. "NDR Utils" says:
Code:
Unable to read XZDR.prop
[NUT]'s XZDualRecovery is required'
The problem seems, that I don't know where to put the files from the recovery.
I tested something with
- starting the Android Studio before starting install.bat
(because I think that the adb-driver where activated with the studio)
- copying the Recovery-Folders to the Folder
...\AppData\Local\Android\Sdk\platform-tools
- copying the files that the install.bat needs (dr.prop and others) from the Folder
...\platform-tools\includes\builder\ to the platform-tools-Folder
but always the install.bat says that it can't find needed Files.
So how can I solve the problem? Whats my mistake?
Which files do I have to copy to which folder?
Firewall and Virusscan are offline and I have Admin-Rights.
RootChecker on the phone says that I have rooted. SuperSU has access.
SDK-platform-tools is in the windows System-Path.
Thanks from webazubi
Code:
* server not running *
* daemon not running. starting it now at tcp:5037 *
* daemon started successfully *
=============================================
Waiting for Device, connect USB cable now...
=============================================
Device found!
=============================================
Getting ro.build.product
=============================================
Device model is C6603
Firmware is 10.5.1.A.0.283
=============================================
Step2 : Sending the recovery files.
=============================================
* 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 C6603
Firmware is 10.5.1.A.0.283
=============================================
Step2 : Sending the recovery files.
=============================================
cannot stat 'dr.prop': No such file or directory
cannot stat 'chargemon.sh': No such file or directory
cannot stat 'mr.sh': No such file or directory
cannot stat 'dualrecovery.sh': No such file or directory
1894 KB/s (65965 bytes in 0.034s)
cannot stat 'rickiller.sh': No such file or directory
2479 KB/s (29204 bytes in 0.011s)
91 KB/s (699 bytes in 0.007s)
2171 KB/s (34473 bytes in 0.015s)
260 KB/s (1202 bytes in 0.004s)
2058 KB/s (96956 bytes in 0.045s)
2133 KB/s (657704 bytes in 0.301s)
cannot stat 'recovery.twrp.cpio.lzma': No such file or directory
cannot stat 'recovery.philz.cpio.lzma': No such file or directory
cannot stat 'installrecovery.sh': No such file or directory
=============================================
Step3 : Setup of dual recovery.
=============================================
Unable to open /data/local/tmp/recovery/install.sh: No such file or directory
Look at your device and grant supersu access!
Press any key to continue AFTER granting root access.
-rwxr-xr-x 1 shell shell 657704 Nov 9 2014 /data/local/tmp/recovery/busybox
Drücken Sie eine beliebige Taste . . .
tmp-mksh: /data/local/tmp/recovery/install.sh: not found
=============================================
Installation finished. Enjoy the recoveries!
=============================================