Develop Bugs

Help With EVO

My EVO keeps on going into recovery mode with red triangle on it. I have tried to push the adb push PC36IMG.zip /sdcard but when the phone reads the zip it keeps on failing with these errors radio_vz fail bootloader fail-ic , image check fail and update fail!..
I have also tried to run RUU but it keeps on giving me usb connection errors. What do I need to do get my phone up and running

hello and welcome to the forums.
What method of rooting are you using?
At what stage are you getting to that you are at this point?
additionally it is helpful for posters to post in the section that best fits there post in this case Q&A. this si so it keeps things easy to read and find which you will quickly find can be a task all its own as you root and start playing around. it isn't a huge deal that you posted wrong though you may get a few nasty remarks for it just dont let them get to you and in the future try post questions there.
lastly if you hold the vol up button and power when at the red ! does it do anything for you?

I followed this article
http://forum.xda-developers.com/showthread.php?t=838448 basically the root didnot go through sucessfully and phone keeps on going into the recovery mode.
Now I am trying to get my phone up and running , apparently something went wrong with the script posted in the forum.
This has turned out to be a quite an adventure for me . The process failed at step 7 and it never worked from that step.

smartguy10 said:
I followed this article
http://forum.xda-developers.com/showthread.php?t=838448 basically the root didnot go through sucessfully and phone keeps on going into the recovery mode.
Now I am trying to get my phone up and running , apparently something went wrong with the script posted in the forum.
This has turned out to be a quite an adventure for me
Click to expand...
Click to collapse
Don't worry. We've all had our bad rooting experiences. You're in good hands here. I'd recommend posting in the Q&A section because there will be a lot of people that can help you there (especially when it gets buisy later tonight). Breathe, you haven't bricked or destroyed your phone. You're no where close to in trouble

Are you S-off? If so sounds like your recovery didnt flash correctly.
You can try flashing a new recovery. Then if thats good just get superuser and busybox installed once your up and running.
zikronix said:
==========================================
FIX BROKEN RECOVERY
This is really only needed if you rooted with one of the previos guides version 6 or lower or if you installed a different recovery like I told you not to. It installs amon_ra 2.2.1
1) Download File PC36IMG_Recovery.zip and Rename to PC36IMG.zip.
copy to the root of your SDCard and power off phone
2) Power your phone back on into the boot loader by holding power and vol-down until your presented with a white screen. It will read the pc36img.zip and as you if you want to flash. Say yes. Then it will ask if you want to reboot, VOL+UP for yes.
3) If your rom gets tossed in the process. Reboot your phone into bootloader select recovery, and reflash your rom....DONE
Click to expand...
Click to collapse

No , its SOFF. I already copied the file to the zip and it failed with these errors
radio_vz fail bootloader fail-ic , image check fail and update fail!

Thread moved to Q&A.

smartguy10 said:
No , its SOFF. I already copied the file to the zip and it failed with these errors
radio_vz fail bootloader fail-ic , image check fail and update fail!
Click to expand...
Click to collapse
It sounds like it never flashed the rom & recovery. Could you attach the autorootlog file to a post so I can see where it went wrong?
Since you are already showing s-off it will be an easy fix. It would be better to run the RUU, for a clean flash, then running autoroot again where it will see you are s-off and finish, but you could also use the flash recovery tool in the post below to simply install a recovery.
http://forum.xda-developers.com/showpost.php?p=10563497&postcount=1386
Sent from my PC36100 using XDA App

I got the phone back with using RUU, now its time to step back and may be root again.

smartguy10 said:
I got the phone back with using RUU, now its time to step back and may be root again.
Click to expand...
Click to collapse
smartguy10,
Could you please send me the autoroot log file that was made so I can find out what went wrong and possibly fix it?

I looked at the autoroot folder and didnot find autoroot file. Before I use your script again what precautions I should take again. If you look at the error messages it looked again the flash didn't finish completely.
Is there a way that I can back up my stock rom to sd card and restore it again if something goes wrong.

[Q] Problem with SGS and custom kernels

So I decided to try out the new cyanogen mod 7.1. I followed These instructions and everything went fine until it was time for the phone to reboot after heimdall's flash.
It didnt reboot, but stayed on the splash screen. I could still both boot in recovery (recovery was CVM) and download. I thought everything was ok, and put the cyanogen-update zip onto the external memory card. However, as all of you (and now I) already know, it doesnt work that way, as the zip has to be on the internal SD.
"Sucks to be me" I thought, but I applyed the update.zip that was already on the card, hoping that it would reset everything (did a factory wipe as well). It didnt.
So, I started kies, set the phone to download and hoped. Kies detects the phone, but it couldnt connect (it just tries infinitly). So, here comes the retard part: I found a guide for installing the same kernel with odin, so I tried that. Odin found the device, but stopped right after (SetupConnection). So, I pulled the battery, waited 5 minutes, and the dreaded "download error" came up. So I restarted the phone, tried to put it in download mode, and it worked! So, now Im back at square retard, becuase heimdall can still flash it and kies still finds the phone (without succeding in connecting), but it doesnt do anything else.
So: what do I do? At the present, I am prepared to settle for stock everything, as long as I get my phone back (I will probably try to install cyanogen again, and come back with new questions, but that is a later problem).
Thanks in advance<3

Prob better posting this in General or on a CM 7 thread/post...
You shouldn't have a problem flashing a stock rom with odin. Just remember to pick repartition, with the correct pit file for the rom.
Sent from my GT-I9000 using XDA App

is this **** bricked??

its just sitting on the freaking LG screen... every time i vol dwn + pwr and double press power it goes normal but then cwm doesn't come up and it just restarts and hangs at LG again. i ****ing hate this phone can someone please help me out? why won't cwm load

can you describe exactly the process you took to port CWM into your phone? Let's see if something happened along the way to cause it to not work properly.
Also, is CWM the one not working, or did you flash a ROM on your phone and something went wrong, and you are trying to get to CWM to restore your phone but not getting anywhere with it?

aquariuz23 said:
can you describe exactly the process you took to port CWM into your phone? Let's see if something happened along the way to cause it to not work properly.
Also, is CWM the one not working, or did you flash a ROM on your phone and something went wrong, and you are trying to get to CWM to restore your phone but not getting anywhere with it?
Click to expand...
Click to collapse
followed the steps on the cwm thread. used terminal emulator. worked great. was working fine until now. i flashed kernels beta 2 and only wiped cache and dalvik and now nothing is working. no cwm to restore, can't even get to the at&t boot animation. this is a mystery.

mic.mayorga said:
followed the steps on the cwm thread. used terminal emulator. worked great. was working fine until now. i flashed kernels beta 2 and only wiped cache and dalvik and now nothing is working. no cwm to restore, can't even get to the at&t boot animation. this is a mystery.
Click to expand...
Click to collapse
Sorry to hear that. Unfortunately I can't help much at all since I haven't done either yet (CWM or Kernels/rom installations) so rather than making things worse for you, I'll leave it to the Pros here to help you. Im sure one of them will respond back soon enough.

Try this:
Disconnect the phone and pull out the battery.
Put battery back in and plug phone to a wall charger. Let it boot to the battery charging screen. Once there press and hold POWER + VOLDOWN
Depends on type of the problem, it helped me 9 out 10 times...

tried it at least 20 times now. just realized that i didn't format /system nor did i update cwm yesterday. probably the root of all these problems. I'm just gonna start fresh with the kdz. I'm on a mac though so its going to be a long night starting with boot camp.

I'm having the same problems...well kind of...
I followed all the instructions for CWM and everything went great. No real issues but had to reinstall the .img twice and then was perfect thereafter. Saw the beta 2 ROM and figured what the hey...downloaded and installed to SD Card. Used CWM/Nandroid to do a backup then installed the zip for the ROM from the sd card.
It took a matter of 10 seconds and said it was successful/done and restarted phone-got a boot loop on LG screen for about 15 minutes and finally did a battery pull-tried several times to get it into CWM with no luck and finally was able to get in-but had to plug it into the wall and wait for charging screen to show. Was able to restore and all was well until turning the phone off.
Turning off the phone now causes the phone to loop on the ATT screen-I can get into download mode and can get into CWM and restore and all is well until turning phone off.
I figured it just needs a fresh install so I've been trying to flash the kdz but the firmware updater keeps faulting and never makes it through the process...so I'm stuck...have all the files I need (I believe) and have everything in place...just can't get it back to normal.
Any ideas from here?
Thanks in advance!

Yeah, sometimes it could be quicker just start over and restore backups...
While you there, would you mind do this: Needed SystemUI.apk from SU640
[EDIT]
@fishscale28:
did you do kdz unbrick before? If not, then perhaps you are not doing it right...btw, kdz file for LU6200 didn't work for me.

Nope-never done a kdz unbrick before-I have the kdz v10i_00 for the 640. I have all the drivers installed, the parser deal installed, windows enabler program running and use the kdz updater to update the firmware. Is there something Im missing here? Seems like several people have gotten the updater to crash when trying to update the firmware...any ideas why?
---------- Post added at 05:51 AM ---------- Previous post was at 05:38 AM ----------
I went through a few of the threads and saw there was a .dll file to be deleted in the updater folders so I did that and now I can do absolutely nothing with the program. Only start and exit...am unable to select anything, view anything, get anything to function...

fishscale28 said:
Nope-never done a kdz unbrick before-I have the kdz v10i_00 for the 640. I have all the drivers installed, the parser deal installed, windows enabler program running and use the kdz updater to update the firmware. Is there something Im missing here? Seems like several people have gotten the updater to crash when trying to update the firmware...any ideas why?
---------- Post added at 05:51 AM ---------- Previous post was at 05:38 AM ----------
I went through a few of the threads and saw there was a .dll file to be deleted in the updater folders so I did that and now I can do absolutely nothing with the program. Only start and exit...am unable to select anything, view anything, get anything to function...
Click to expand...
Click to collapse
I installed from the kdz yesterday and didn't have to delete any files. I'm on Win 7 x64. The first time it ran it told me to restart my phone cause it didn't see it, but the second time it ran until my phone reboot and I killed the program. Be sure you have the KDZ_FW_UPD_EN with UpTestEX_mod2_marwin.exe in it. Hope this helps.

Thanks for your help. I did all that...again...I even deleted, reinstalled all the updater stuff, tried running as admin, tried running in compatibility mode, ran it after deleting the recommended .dll file and the option to do anything was gone, put it back in and was able to run everything fine and a little after extracting the kdz it would crash. I unplugged the phone and re-ran the proggy and it went through the check, noticed the phone wasn't hooked up and finished the check. Plug phone in, start process over and proggy crashes.
I don't get it-I would say its the wrong kdz but its not. I installed all the drivers and it still doesn't work. I've tried every combo of everything and the proggies keep crashing.
Now I was finally able to get into CWM to flash another ROM and was able to get one going-was able to boot into the os but same as before-once the phone is turned off it starts the boot loop. Now its even harder to get back to CWM but a restore works from there. Any ideas on why the boot image keeps reverting back to whatever was screwed up? Has to be something that happens once the system starts up again as it's after a restore and when the phone is turned off. Stumped and would love to be able to use my phone...It seems like flashing the kdz would be the sure fire way to get it done-are there options aside from the updaters that keep crashing?
Thanks in advance!

Maybe http://www.microsoft.com/windows/virtual-pc/ can help?

alright so i got to the 4% thing and my phone rebooted but it kept looping to the screen LG Optimus LTE bootscreen with the pink candy cane. thats it. i did vol dwn + pwr and got the android arrow and box with loading bar no text, then it rebooted back to the optimus lte screen. never got to the setup screen. tried the kdz again and my phone died. now when i plug it in i only get download mode... does it charge in download mode and why did it not get to the setup screen?!

fishscale28 said:
Thanks for your help. I did all that...again...I even deleted, reinstalled all the updater stuff, tried running as admin, tried running in compatibility mode, ran it after deleting the recommended .dll file and the option to do anything was gone, put it back in and was able to run everything fine and a little after extracting the kdz it would crash. I unplugged the phone and re-ran the proggy and it went through the check, noticed the phone wasn't hooked up and finished the check. Plug phone in, start process over and proggy crashes.
I don't get it-I would say its the wrong kdz but its not. I installed all the drivers and it still doesn't work. I've tried every combo of everything and the proggies keep crashing.
Now I was finally able to get into CWM to flash another ROM and was able to get one going-was able to boot into the os but same as before-once the phone is turned off it starts the boot loop. Now its even harder to get back to CWM but a restore works from there. Any ideas on why the boot image keeps reverting back to whatever was screwed up? Has to be something that happens once the system starts up again as it's after a restore and when the phone is turned off. Stumped and would love to be able to use my phone...It seems like flashing the kdz would be the sure fire way to get it done-are there options aside from the updaters that keep crashing?
Thanks in advance!
Click to expand...
Click to collapse
Even after running the kdz, my phone still does that after installing CWM. I don't know if it's something with my ROM or something with CWM, but if you can't get into CWM you probably don't need to run the kdz. I couldn't get into CWM anymore when I ran it.

So you're saying you go into the boot loop after turning off your phone even after unbricking?

I don't get it-now I can't get into recovery and it keeps up with the boot loop. I've tried running on the virtual PC/XP deal and it doesn't crash but now it doesn't even see the phone...reinstalled all the drivers, etc. and still no luck. Is there anyway to get the kdz installed without this updater?

fishscale28 said:
So you're saying you go into the boot loop after turning off your phone even after unbricking?
Click to expand...
Click to collapse
Yes. I don't think that was happening until I put CWM on. But I can live with it until the issue is solved. I don't think I'm the only one having it.

[Q] I made a huge mistake and I need help.

First of all, Sorry if I make any mistakes with the language as English is not my first language.
I rooted my HTC One M8 (Unlocked version) a month or two months ago, yesterday I received the Lollipop OTA update and I wanted to install it, I did as it said and it sent me to the The Win Project thing and as you all know, it failed. So I made a research on the internet and it said that it was impossible, either I needed to wait for the ROM or I needed to unroot my phone, So I as the noob that I am, went to the SuperSU program and clicked Unroot, then try it again, and from then on I started to make one mistake after another, I checked how to do a factory reset because I thought that even that I have my phone Rooted, I don't really exploit it as much, so it was okay to go back to basics and then afterwards install the official Lollipop update.
I went then to check some tips and I was unsuccessful, then I try to download the Candy5 version and try it and when I was "following instructions" I downloaded the Candy 5 and the gapps and everything and then I went to recovery mode, I wiped all the things that needed to be wiped and then I realized that I forgot to move the downloads from my PC to my HTC, so I clicked Reboot, it asked me to install the SuperSU and I clicked yes, then it rebooted, but it never went further away from the white screen with the green HTC logo in the middle and the "powered by Android" at the bottom. The HTC is frozen, I can't really do anything from there, I press the power button, the volume buttons, any combination between all these and nothing happens, when I connect it to my computer, the computer makes a sound as if detected an external device being connected but it doesn't really appear as a file.
What can I do? What should I do? I know I screwed up big time and you guys may hate people like me.
Thanks in advance.

You need to load a custom rom on the external SDCard, go to TWRP, select external SDCard, and install the rom.
But really you have made the situation worse from where you were.

Done...but...
SaHiLzZ said:
You need to load a custom rom on the external SDCard, go to TWRP, select external SDCard, and install the rom.
But really you have made the situation worse from where you were.
Click to expand...
Click to collapse
Thanks, I know I messed up. Now I have another problem. The SDCard is not working on the TWRP. What should I do?
I found this: http://forum.xda-developers.com/showthread.php?t=2318497
Should I do that?

gamorro said:
Thanks, I know I messed up. Now I have another problem. The SDCard is not working on the TWRP. What should I do?
I found this: http://forum.xda-developers.com/showthread.php?t=2318497
Should I do that?
Click to expand...
Click to collapse
If you are in twrp you can use the command "adb push filename.zip /sdcard/" and it will put the zip onto your Internal storage or wherever you tell it to put it. I believe /sdcard/ is internal storage and /sdcard2/ is ext sd card. just remember to have the zips for the rom in the same folder that the adb file is. after pushing you do not have to reboot your device and should be good to go as far as wiping/installing goes

I did something stupid yesterday a bit like whats going on with you see here I deleted the os got stuck on the white screen ect.
I used this rom and followed this guide
You may want to check to make sure it's the correct rom and that i'm not making things worse.

n910v unlocked boot, twrp, twrp reboots on any rom install

so i followed the recent bootloader unlock, i have the retail in developer mode, i got twrp installed, this i where it gets messy, it went into a bootloop, so i did a wipe on the cache and davk cach, didn't work. even pulled the battery, so i tried the format. same problem, did work, so i did a wipe again which i think i really broke it when i wiped all but the sdcard, so now, NO OS. so i'm trying to get files to reflash stock roms, i found downloads to the stock files btw, currently downloading.
so, i have twrp
no backup (i'ma idiot lol)
no OS installed
bootloader is confirmed to be in developer mode
can't get phone to access fastboot. via adb
only recovery and download avaible
[edit, i can move files onto my sd card by using another phone to move files]
so do i continue with trying to use idon to flash stock rom onto the phone? will twrp still be installed? and will i keep my developer unlocked booloader?
twrp is v2.8.5.0
(been working on this for about 14 hours now)
FIXED!!
ok, so i found a stock recovery file, md5.tar, i'll post a link below.
i used odin, put phone into download mode, connected with odin running as administrator.
selected the file i used in the AP button, (had to wait awhile for it to check md5, doesn't respond during that time)
it failed. so i pulled phone in battery and tried to turn on recovery, it sent me to the download screen and said the verizon update failed. tried to reinstall rom again. pulled battery. said same thing.
i reflashed the TWRP i was using with odin, doing the AP button with it too.
[[It will say failed on deviced and in odin]]
phone now boots up.
[btw the temp root i did was kingroot]
http://forum.xda-developers.com/devdb/project/dl/?id=12450
here is the original post for what i was doing
http://forum.xda-developers.com/note-4-verizon/general/note-4-verizon-bootloader-unlock-t3358913
the two walk throughs i found
1. http://forum.xda-developers.com/note-4-verizon/general/howto-converting-retail-note-4-to-t3358957
2. http://www.techtimes.com/articles/152037/20160421/modder-unlocks-verizon-galaxy-note-4-bootloader-heres-how-to-do-it.htm
the stock recovery( reason for old version is because a few can update from this one)
http://click.xda-developers.com/api/click?format=go&jsonp=vglnk_146187538272120&key=f0a7f91912ae2b52e0700f73990eb321&libId=inkoi1eq01000n4o000DLb61t4tis&loc=http%3A%2F%2Fforum.xda-developers.com%2Fnote-4-verizon%2Fdevelopment%2Ffirmware-firmware-kernel-modem-recovery-t2942937&v=1&out=https%3A%2F%2Fwww.androidfilehost.com%2F%3Ffid%3D24052804347793292&ref=https%3A%2F%2Fwww.google.com%2F&title=%5BFirmware%5D%20%5BOfficial%5D%20Firmware%20%2F%20Kernel%20%2F%20Mo%E2%80%A6%20%7C%20Verizon%20Samsung%20Galaxy%20Note%204&txt=https%3A%2F%2Fwww.androidfilehost.com%2F%3Ffid%3D24052804347793292
this is the main page to find the stock roms
http://forum.xda-developers.com/note-4-verizon/development/firmware-firmware-kernel-modem-recovery-t2942937

i may have put the wrong title

dragont4 said:
i may have put the wrong title
Click to expand...
Click to collapse
Try adb push worked for me

axeldiks1 said:
Try adb push worked for me
Click to expand...
Click to collapse
for moving files right?

fixed!!

dragont4 said:
for moving files right?
Click to expand...
Click to collapse
Yes just download a rom and flash it after you push it to your storage

dragont4 said:
so i followed the recent bootloader unlock, i have the retail in developer mode, i got twrp installed, this i where it gets messy, it went into a bootloop, so i did a wipe on the cache and davk cach, didn't work. even pulled the battery, so i tried the format. same problem, did work, so i did a wipe again which i think i really broke it when i wiped all but the sdcard, so now, NO OS. so i'm trying to get files to reflash stock roms, i found downloads to the stock files btw, currently downloading.
so, i have twrp
no backup (i'ma idiot lol)
no OS installed
bootloader is confirmed to be in developer mode
can't get phone to access fastboot. via adb
only recovery and download avaible
[edit, i can move files onto my sd card by using another phone to move files]
so do i continue with trying to use idon to flash stock rom onto the phone? will twrp still be installed? and will i keep my developer unlocked booloader?
twrp is v2.8.5.0
(been working on this for about 14 hours now)
FIXED!!
ok, so i found a stock recovery file, md5.tar, i'll post a link below.
i used odin, put phone into download mode, connected with odin running as administrator.
selected the file i used in the AP button, (had to wait awhile for it to check md5, doesn't respond during that time)
it failed. so i pulled phone in battery and tried to turn on recovery, it sent me to the download screen and said the verizon update failed. tried to reinstall rom again. pulled battery. said same thing.
i reflashed the TWRP i was using with odin, doing the AP button with it too.
[[It will say failed on deviced and in odin]]
phone now boots up.
[btw the temp root i did was kingroot]
http://forum.xda-developers.com/devdb/project/dl/?id=12450
here is the original post for what i was doing
http://forum.xda-developers.com/note-4-verizon/general/note-4-verizon-bootloader-unlock-t3358913
the two walk throughs i found
1. http://forum.xda-developers.com/note-4-verizon/general/howto-converting-retail-note-4-to-t3358957
2. http://www.techtimes.com/articles/152037/20160421/modder-unlocks-verizon-galaxy-note-4-bootloader-heres-how-to-do-it.htm
the stock recovery( reason for old version is because a few can update from this one)
http://click.xda-developers.com/api/click?format=go&jsonp=vglnk_146187538272120&key=f0a7f91912ae2b52e0700f73990eb321&libId=inkoi1eq01000n4o000DLb61t4tis&loc=http%3A%2F%2Fforum.xda-developers.com%2Fnote-4-verizon%2Fdevelopment%2Ffirmware-firmware-kernel-modem-recovery-t2942937&v=1&out=https%3A%2F%2Fwww.androidfilehost.com%2F%3Ffid%3D24052804347793292&ref=https%3A%2F%2Fwww.google.com%2F&title=%5BFirmware%5D%20%5BOfficial%5D%20Firmware%20%2F%20Kernel%20%2F%20Mo%E2%80%A6%20%7C%20Verizon%20Samsung%20Galaxy%20Note%204&txt=https%3A%2F%2Fwww.androidfilehost.com%2F%3Ffid%3D24052804347793292
this is the main page to find the stock roms
http://forum.xda-developers.com/note-4-verizon/development/firmware-firmware-kernel-modem-recovery-t2942937
Click to expand...
Click to collapse
I'm glad that you fixed it, but I just wanted to say what I think your problem was so that other people can fix it with a little less pain.
The bootloader unlock writes files to your sd card during the process. That's why the instructions state to use an SD card that you can set aside later. If you leave that SD card in the phone when you boot, you will bootloop. Simply removing the SD card and putting in another one will work. You can also remove the SD card, format it, and put it back in.

ssj4gogeta2003 said:
I'm glad that you fixed it, but I just wanted to say what I think your problem was so that other people can fix it with a little less pain.
The bootloader unlock writes files to your sd card during the process. That's why the instructions state to use an SD card that you can set aside later. If you leave that SD card in the phone when you boot, you will bootloop. Simply removing the SD card and putting in another one will work. You can also remove the SD card, format it, and put it back in.
Click to expand...
Click to collapse
Yeah I was thinkong about that. I had pulled the sd card right after due to boot loop. Think it had to do with the sd card. I messed a step up I believe there at the end.
Sorry for the late reply guys