Develop Bugs

[Q] S-OFF, NO OS, WRP won't install anything, adb drivers can't install. HELP!!!!

Please help! I have all of the following problems.
What's not working
- Samsung Kies, official Samsung drivers, AND "adb mount" or "fastboot devices" aren't working!
- My OS got wiped, and TWRP 2.4.0.0 always fails EVERY ROM install! I'm in a boot loop
- TWRP's Fix Permissions fails every time.
- I'm assuming it isn't rooted even though it was rooted before all of this happened, because every time I reboot TWRP asks if I'd like to install SuperUser. It never successfully roots the phone.
What's working (thank God)
- Odin can install various versions of TWRP or CWM Recovery
- TWRP and my stock Download mode work.
Other details
SGH-i747
Micro SD 64GB external
Windows 8 64bit with driver signing disabled
GRR. I want to throw my Android against the wall!
PLEASE HELP!!

s-off???? LOL

You need to Odin flash a stock rooted Rom. After it boots up, install goo manager from the market and use that to install twrp. If you want to flash a custom Rom, dl it and install it from directions in the first post of the Rom thread.

deavonb said:
Please help! I have all of the following problems.
What's not working
- Samsung Kies, official Samsung drivers, AND "adb mount" or "fastboot devices" aren't working!
- My OS got wiped, and TWRP 2.4.0.0 always fails EVERY ROM install! I'm in a boot loop
- TWRP's Fix Permissions fails every time.
- I'm assuming it isn't rooted even though it was rooted before all of this happened, because every time I reboot TWRP asks if I'd like to install SuperUser. It never successfully roots the phone.
What's working (thank God)
- Odin can install various versions of TWRP or CWM Recovery
- TWRP and my stock Download mode work.
Other details
SGH-i747
Micro SD 64GB external
Windows 8 64bit with driver signing disabled
GRR. I want to throw my Android against the wall!
PLEASE HELP!!
Click to expand...
Click to collapse
If you mean that anything you put in your usb ports don't work then i had that problem yesterday. Just get your windows disc you used to install your operating system and click repair ystem then restore your computer to atleast a week ago and you should be good, if thats the case.

all I know is I can't get ADB and kies to work on Win 7. I had to use Win 7 for it.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app

Used Newest FreeGee - Stuck in TWRP

ATT LG Optimus G Pro Here
I used newest FreeGee , Installed TWRP & Now im stuck in recovery mode. I flashed gummy rom first time & It worked. Ran into problem after I installed the Google apps so I did a factory reset, wiped everything to try again to install gummy rom. Now I'm stuck in TWRP. I also used ADB sideload commands to push the rom to phone & It did push it, except now. When I try to install the rom, It keeps saying FAILED. Can someone tell me what im doing wrong?

newgeek- I don't know if the AT&T version of this is very different to my F240 version but I am familiar with that 3rd screen you posted with the "secure booting error" or something like that.
What about just pulling that battery out and doing factory reset and start over from the beginning ?
LL13-

newgeek35 said:
ATT LG Optimus G Pro Here
I used newest FreeGee , Installed TWRP & Now im stuck in recovery mode. I flashed gummy rom first time & It worked. Ran into problem after I installed the Google apps so I did a factory reset, wiped everything to try again to install gummy rom. Now I'm stuck in TWRP. I also used ADB sideload commands to push the rom to phone & It did push it, except now. When I try to install the rom, It keeps saying FAILED. Can someone tell me what im doing wrong?
Click to expand...
Click to collapse
Try to push another ROM via adb, I read in the general Section that there were some Gummy files that weren't the right size, just download CM11 and try to flash it, TWRP is saying that the flash failed, that's why you are stuck in recovery.
Erik

The phone currently has no OS , I also tried to mount my 64gb sd card to install off of that & It gives me a mounting error for SD CARD. I have tried several other roms & No luck , Keeps giving me FAILED. Is this because of the secure boot perhaps? I'm totally clueless why it's not taking it. I'm running my nexus 4 with the gummy rom without a hitch.

Why not try a different SD card ? If that SD card was in the phone when all this happened maybe something is on the card that's bad ?
LL13-

I borrowed a 2GB SD CARD & It mounts but same thing as before FAILED. Tried both gummy & CM 10.2

newgeek35 said:
I borrowed a 2GB SD CARD & It mounts but same thing as before FAILED. Tried both gummy & CM 10.2
Click to expand...
Click to collapse
It looks like an error with the updater script, maybe something twrp isnt reading or executing? try a different rom.
At worst try a different Recovery.
ADDED:2/4/2014: I would avoid twrp on freegee, i've heard others have issues and it may have something to do with your situation.
Also, I noticed your twrp says 2.6.1.0, am I mistaken or is the newest teamwin 2.6.3.1? That number don't look right.
If possible try to flash madmacks twrp or cwm 6.0.4.6.

1.Try to Flash a ROM via sideload
2. you can end the recovery boot loop by using adb commands, there are two methods try them
http://forum.xda-developers.com/showpost.php?p=49370751&postcount=70
and
http://forum.xda-developers.com/showpost.php?p=48136185&postcount=268

I had the same issue seems like the are some problems with TWRP on this particular phone I flashed the regular clockworkmod and it works perfect.I tried on another phone with same results.
Right now
Flash stock rom
root
use freegee to install regular cwm I tried rom manage but recovery did not installed
the flash another rom if thats what you really want but copy rom directly to sd card instead

Its not just twrp apparently the new update of freegee installs the wrong bootloader/image on our phone. It bootloops anyone that uses it.
Sent from my LG-E980 using XDA Premium 4 mobile app

Use Madmack's hacked TWRP located in his CM threads. Best recovery for our device from what I've seen/tested.
Sent from my AICP 4.4 LG-E980

Neroga said:
Use Madmack's hacked TWRP located in his CM threads. Best recovery for our device from what I've seen/tested.
Sent from my AICP 4.4 LG-E980
Click to expand...
Click to collapse
Madmack's TWRP is reliable when you want to have no bootloops into your recovery. But i have the problem, that i cannot flash any other roms and it shows, that my LG E986 isnt recognized as a suitable device for the rom and it aborts the procedure. Although on the other recoveries it worked fine...
Is there something what i have to do except switching recoveries to my phone's death?

I used ADB to push the stock rom back to device & It took it's sweet time but it worked. I sold the phone to a friend of mine LOL! They wont know the difference.

[Q] Device bricked after trying to change ROM

I just bricked my galaxy nexus by trying to install Shiny ROM. I've got a (europe) maguro galaxy nexus which ran PA before, but I wanted to update as it became extremely slow at times.
Using TWRP v2.5.0.0 I did a factory reset(data, cache and dalvik wipe). I then tried to install ShinyROM, but it gave the following error:
Updating partition details...
Formatting Cache using make_ext4fs...
Done.
Wiping data without wiping /data/media ...
Done.
Updating partition details...
Installing '/sdcard/modsnstuff/ShinyROM_maguro_a
Checking for MD5 file...
Skipping MD5 check: no MD5 file found.
Warning: No file_contexts
Installing Shiny ROM build 062114
for maguro
set_metadata_recursive: some changes failed
E: Error executing updater binary in zip '/sdcard
Error flashing zip '/sdcard/modsnstuff/ShinyROM_
Updating partition details...
Click to expand...
Click to collapse
I also put a new PA version on the phone, which gave a similar error.
I tried using the android toolkit to get into adb recovery and flash a new rom somehow. I did not succeed to install the drivers successfully, which is probably because I am not able to boot into android. I do not see how I can use the toolkit now, and since I barely know what it does and I would not know how to install the drivers.
What can I do to correctly install the new ROM, or at least get it to boot in any version of android?

inasm said:
I just bricked my galaxy nexus by trying to install Shiny ROM. I've got a (europe) maguro galaxy nexus which ran PA before, but I wanted to update as it became extremely slow at times.
Using TWRP v2.5.0.0 I did a factory reset(data, cache and dalvik wipe). I then tried to install ShinyROM, but it gave the following error:
I also put a new PA version on the phone, which gave a similar error.
I tried using the android toolkit to get into adb recovery and flash a new rom somehow. I did not succeed to install the drivers successfully, which is probably because I am not able to boot into android. I do not see how I can use the toolkit now, and since I barely know what it does and I would not know how to install the drivers.
What can I do to correctly install the new ROM, or at least get it to boot in any version of android?
Click to expand...
Click to collapse
Search for using fastboot to return to stock Google image(stock ROM). Then install custom recovery again and flash a ROM.
This phone is nearly impossible to brick

DR3W5K1 said:
Search for using fastboot to return to stock Google image(stock ROM). Then install custom recovery again and flash a ROM.
This phone is nearly impossible to brick
Click to expand...
Click to collapse
Thanks a lot for the reply, trying it now. Apologies if I misused the word brick btw.

inasm said:
Thanks a lot for the reply, trying it now. Apologies if I misused the word brick btw.
Click to expand...
Click to collapse
No need to apologize just didn't want you to think that you were stuck.
Also it will be very beneficial to study up on adb along with fastboot.
If you learn these two things you will be able to get out of just about any sticky situation you run into.
PS The most difficult part is getting the drivers installed.

DR3W5K1 said:
No need to apologize just didn't want you to think that you were stuck.
Also it will be very beneficial to study up on adb along with fastboot.
If you learn these two things you will be able to get out of just about any sticky situation you run into.
PS The most difficult part is getting the drivers installed.
Click to expand...
Click to collapse
Would you happen to have a link to a post of some sort? I tried downloading the drivers, then installing them using device manager which didn't work, since windows said they were up to date already. All other guides I found to install the right drivers were with a working android version. Even the soft brick guides assume you have installed the drivers already.

inasm said:
Would you happen to have a link to a post of some sort? I tried downloading the drivers, then installing them using device manager which didn't work, since windows said they were up to date already. All other guides I found to install the right drivers were with a working android version. Even the soft brick guides assume you have installed the drivers already.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1583801. Use this for driver issues.
http://forum.xda-developers.com/galaxy-nexus/general/how-to-return-to-stock-galaxy-nexus-t1626895 use this to return to stock.
With these guides you can fix it!

DR3W5K1 said:
http://forum.xda-developers.com/showthread.php?t=1583801. Use this for driver issues.
http://forum.xda-developers.com/galaxy-nexus/general/how-to-return-to-stock-galaxy-nexus-t1626895 use this to return to stock.
With these guides you can fix it!
Click to expand...
Click to collapse
The driver still seems to refuse to work. It keeps saying the latest driver is installed. I am using Windows 7 in stead of 8, which is why the guide might not apply 100% to me.
When I use the Android ToolKit and I try to flash the google ROM, it does detect a device in ADB MODE, and it gets the serial number, but it gets stuck on "Waiting for adb Mode". Does this mean the drivers are already correctly installed?
EDIT:
I remembered that I downloaded an old version of PA a long time ago using goo manager, which was still on my phone. ADB drivers are also installed now it seems, now I just have to install the 4.4 version correctly.
Thanks a lot for your help!

inasm said:
The driver still seems to refuse to work. It keeps saying the latest driver is installed. I am using Windows 7 in stead of 8, which is why the guide might not apply 100% to me.
When I use the Android ToolKit and I try to flash the google ROM, it does detect a device in ADB MODE, and it gets the serial number, but it gets stuck on "Waiting for adb Mode". Does this mean the drivers are already correctly installed?
EDIT:
I remembered that I downloaded an old version of PA a long time ago using goo manager, which was still on my phone. ADB drivers are also installed now it seems, now I just have to install the 4.4 version correctly.
Thanks a lot for your help!
Click to expand...
Click to collapse
Your welcome but you should have been using fastboot instead of adb. For future reference they are two different things

Status 7 Error when Flashing Cyanogenmod 10.2 with FNH2 Bootloader (i747M)

Hello folks,
My phone is currently rooted, running Android 4.4.2. The bootloader is 1747MVLUFNH2. It is the Telus, i747M variant of the S3.
I am using ClockworkMod Recovery, Version 6.0.4.7 and trying to flash Cyanogenmod 10.2.1 (the latest stable release for this phone).
When I flash the Zip in CWM, the installation aborts and I get a Status 7 error. I have tried earlier releases of CyanogenMod, but they have resulted in the same error. Presumably, this is because my bootloader is not listed among those in the asserts of the ROM.
I have found old threads where folks have noted that, when running bootloaders from the ICS era, you can't flash any Cyanogenmod roms past 10.1. I figured that maybe my bootloader is one of these old ones, but from my research "FNH2" appears to be the newest. In most of the lists featured online, mine doesn't even show up. I understand that reverting your bootloader back to an old one is a huge "no no", and would likely result in my phone being bricked.
I suppose all of this leaves me wondering whether I am caught in some sort of limbo, where my bootloader is in fact too "new" for a relatively old version of Cynanogenmod (10.2.). The phone was recently given to me by my brother, and I am not sure how he updated the bootloader/firmware, but it was likely through Kies.
My end goal is just to have some stable version of Cyanogenmod running, and I've run out of ideas as to how I can make it work. I have tried using Cyanogenmod's "One Click Installer", and that seemed to work well until the phone rebooted to the stock ROM that had been running before; leaving me with effectively no change at all. I have verified root access, and gapps zips seem to extract and install just fine.
Any ideas or pointers would be greatly appreciated.
Thanks.

Why not run the latest cm11 for the d2lte? CM10.2 is only JB.

audit13 said:
Why not run the latest cm11 for the d2lte? CM10.2 is only JB.
Click to expand...
Click to collapse
I've actually tried that, but I still get the Status 7 error, even with a CM-11 nightly.
I flashed back to the stock ROM, with the most current bootloader, etc. It still won't flash any CM zip from CWM, and the Installer doesn't seem to work either. It will install CWM, and say that everything went ok, but when the phone reboots, it's still the stock ROM.
p.s. the CAPTCHAs on this forum are damn near impossible.

"It will install CWM, and say that everything went ok, but when the phone reboots, it's still the stock ROM."
If you're having trouble installing CWM, try this: re-flash CWM or Philz in Odin and do not check anything except r.reset.time, flash recovery, remove the USB cable when you see reset in the status window, remove the battery, replace battery, boot into recovery.
If the latest version of CWM is working properly and you get the status 7 error, try to pull a logcat.

Oppo find 7a cant get into fastboot or recovery

Hi everyone, I'm in major trouble right now.
I just flashed a modem package from this link
https://www.androidfilehost.com/?fid=23578570567721897
and now I cant get to recovery or fastboot and of course cant boot up. Caan anyone help?
I flash using nameless latest twrp and my rom is Omni 6.0 test build.

Hey I have one problem here..
Im using oppo find7a Android 5.0 color os 2.1.5..
Already root using kingroot..
I want to flash to other os like cyanogen, gummybaer, miui etc
I follow all the step on many video on YouTube using TWRP ..
After I flash twrp recover img and reboot, it stuck on fastboot menu
It cannot enter the recovery menu
How do I solve this problem so I can do wipe cache and flash other os
Some people say I must unlock the bootloader so that I can enter TWRP recovery menu

Shouheng said:
Hi everyone, I'm in major trouble right now.
I just flashed a modem package from this link
https://www.androidfilehost.com/?fid=23578570567721897
and now I cant get to recovery or fastboot and of course cant boot up. Caan anyone help?
I flash using nameless latest twrp and my rom is Omni 6.0 test build.
Click to expand...
Click to collapse
Hello, almost the same happend to me.....flashed modem package on nameless ROM.
After reboot, the phone si completely dead.
No vibration, no fastboot, no recovery.....
Did you manage somehow to solve this????
EDIT: found this guide and it works http://community.oppo.com/en/forum.php?mod=viewthread&tid=23067&extra=

tw9 said:
Hello, almost the same happend to me.....flashed modem package on nameless ROM.
After reboot, the phone si completely dead.
No vibration, no fastboot, no recovery.....
Did you manage somehow to solve this????
EDIT: found this guide and it works http://community.oppo.com/en/forum.php?mod=viewthread&tid=23067&extra=
Click to expand...
Click to collapse
What's your device model name? After unbrick mobile data working fine?

My device is X9006 and on latest Nameless nightly everything is ok.

tw9 said:
My device is X9006 and on latest Nameless nightly everything is ok.
Click to expand...
Click to collapse
Can you give me like of drivers? I used one in unbrick tool but it is not getting installed

I have no other drivers than those in the unbrick thread.
There is also a process of installing them described, which is tricky, because the drivers are not digitally signed.
If you are on windows 7, you must put them in test mode....don't know how it is with other versions of windows, because I used my older machine with W7 for unbricking.
It is all there, in the unbrick thread.....If I remember correctly....

tw9 said:
I have no other drivers than those in the unbrick thread.
There is also a process of installing them described, which is tricky, because the drivers are not digitally signed.
If you are on windows 7, you must put them in test mode....don't know how it is with other versions of windows, because I used my older machine with W7 for unbricking.
It is all there, in the unbrick thread.....If I remember correctly....
Click to expand...
Click to collapse
Finally unbrciked the device using that guide and after some workarounds got 3g working. But the biggest problem I am facing now is. I am stuck in stock 1.2..5i with twrp 2.7.0 can't old backup are not showing in recovery also can't flash anything. No system update. Flashing nameless Rom latest results in updater script error. Tried flashing latest twrp but it will reboot to system every time I try to boot into recovery. Sorry for my bulky English.

Yes, this exact problem I had also to face.
And I don't remember it exactly, but If I'm not mistaken, I flashed the original ColorOS recovery, did some updates and finally then I ended up with ColorOS 2.1.5i, I think.....
From that point TWRP recoveries worked alright, even the newest versions.
If you managed to unbrick your device, this is piece of cake, just remember - you need original ColorOS recovery firstly.

tw9 said:
Yes, this exact problem I had also to face.
And I don't remember it exactly, but If I'm not mistaken, I flashed the original ColorOS recovery, did some updates and finally then I ended up with ColorOS 2.1.5i, I think.....
From that point TWRP recoveries worked alright, even the newest versions.
If you managed to unbrick your device, this is piece of cake, just remember - you need original ColorOS recovery firstly.
Click to expand...
Click to collapse
Thank you for your reply mate. Now flashed cm13 nightly using 2.8.4 I will be selling this phone ASAP. This fourm is almost inactive.