Database Info

[HELP] Stuck in boot loop after modding framework-res.apk

Looks like my worst fears came true. I applied a Metamorph that was supposed to be compatible with all froyo based HDPI Devices, but I guess that wasn't true. It worked at first then I applied another mod from the same thread, then **** hit the fan.
Now my g2x is stuck in a boot loop. I have a stock recovery, and I'm on a mac to make things worse. Please help.

You'll need to fix from hboot guy
Sent from my Supersonic running MikGinger Sense 2.1

evasilisin said:
You'll need to fix from hboot guy
Sent from my Supersonic running MikGinger Sense 2.1
Click to expand...
Click to collapse
How do I do that? Specifically on a mac...

I was there yesterday, try a full restore. Volume down and power when phone is off.
Brought mine back to life.

samson_420 said:
I was there yesterday, try a full restore. Volume down and power when phone is off.
Brought mine back to life.
Click to expand...
Click to collapse
Brings me to the recovery (Open box with a green android), then it just continues looping the startup screen.

Can someone please help, my g2x is a paper weight right now

Pull the system dump from the development section. Push the framework-res file via adb while the phone is boot looping or while in cwm if that works.
You should always have a nandroid backup before modifying system files. If you have one, just restore /system.
The first option is the easiest.
Sent from my LG-P999 using XDA App

DeezNotes said:
Pull the system dump from the development section. Push the framework-res file via adb while the phone is boot looping or while in cwm if that works.
You should always have a nandroid backup before modifying system files. If you have one, just restore /system.
The first option is the easiest.
Sent from my LG-P999 using XDA App
Click to expand...
Click to collapse
I can't figure out how to pull the framework-apk from the system dump. When I type in ./adb devices into terminal, none come up. This is while the boot screen is looping and while it's in stock recovery. I don't have cwm installed

Go to the development section and download the dump in the post labeled T-Mobile g2x dump. Unzip him. After it's unzipped, find /system/framework/framework-res.apk. That's the original file. You news to replace that one with your modified one. Adb is an easy way to do that.
If you're rooted, you should be able to adb push that file to overwrite the modified one. If its not working, you may need to enable read+write on system.
I haven't rooted yet since this is a trial device, so I can't give you a step by step. And I'm typing this on the phone. :-/
Sent from my LG-P999 using XDA App

There are cwm instructions for Mac + Linux (thats what it looks like you're on based on your post). Try installing that to get adb working.
Sent from my LG-P999 using XDA App

I can't figure out how to get CWM onto my phone on a mac, adb can't even see the phone.
It's not even turning on now... I'm really worried.

what a helpful community we have here

rashad1 said:
what a helpful community we have here
Click to expand...
Click to collapse
Good way to ask for help... Everyone has given you directions. Your phone isn't a brick. Get on a windows PC and push everything over. Next time, be a bit more careful and flash a recovery image and nandroid before editing things.
Sent from my LG-P999 using XDA App

don't you have to adb shell to see devices in recovery?

rashad1 said:
what a helpful community we have here
Click to expand...
Click to collapse
First of all, I understand that you're worried about your phone, but don't get mad at us when we didn't do anything and we are, in fact, trying to help. Second, in order to fix your phone using your own computer, you're probably going to have to install a Linux distribution such as Ubuntu. I don't think anyone has found a way to use nvflash on a Mac thus far. Installing Ubuntu is fairly easy and wouldn't take long.
Check out this: https://help.ubuntu.com/community/M...telInstallation#Dual-Boot: Mac OSX and Ubuntu

which stock image do I download? There are several threads.
Do I get it from TMobile G2X dump, or T-Mobile G2X P999 Facotry Firmware, or Stock NANDROID Restore Froyo 2.22 Rooted LG-P999-V10f 4-23-2011
How do I get my computer to recognize the phone? when enter ./adb devices, nothing comes up
Can someone post the framework-res.apk for me please?
How do I restore the firmware with nvflash? I'm borrowing my brothers HP windows 7 computer

rashad1 said:
which stock image do I download? There are several threads.
Do I get it from TMobile G2X dump, or T-Mobile G2X P999 Facotry Firmware, or Stock NANDROID Restore Froyo 2.22 Rooted LG-P999-V10f 4-23-2011
How do I get my computer to recognize the phone? when enter ./adb devices, nothing comes up
Can someone post the framework-res.apk for me please?
How do I restore the firmware with nvflash? I'm borrowing my brothers HP windows 7 computer
Click to expand...
Click to collapse
Here are the drivers so that your computer can recognize your phone
http://forum.xda-developers.com/showthread.php?t=1044881&highlight=drivers
Hope that helps

moshe22 said:
Here are the drivers so that your computer can recognize your phone
http://forum.xda-developers.com/showthread.php?t=1044881&highlight=drivers
Hope that helps
Click to expand...
Click to collapse
my mac doesn't recognize it in adb mode, and it doesn't need a driver

If you can borrow a friend's windows PC, install the LG desktop app. It has a recovery option (assuming it can still communicate with the phone). That's probably the fastest way to get back to stock.

How long did it take?
samson_420 said:
I was there yesterday, try a full restore. Volume down and power when phone is off.
Brought mine back to life.
Click to expand...
Click to collapse
How long did it take?

[Q] Help Desperately Needed - Need to reroot and USB doesn't work

I think I put myself in a bad situation here...
I spent all day trying to figure out how to root my 5 week old Nexus as it's tethering ability is my only access to the web.
So - step one, I did the one-click method, as the instructions I was finding for "the long way" were written by people who know what they're doing FOR people who know what they're doing.
Once that was accomplished, I downloaded Rom Manager. Unfortunately Rom Manager didn't seem to want to work with One-Click's style of rooting, locking me on the boot screen every time I tried using it.
So, I finally worked out how to root my phone the "normal" way and Rom Manager was working.
Here's where my mistake came in... I was one part frustrated from how long it took me to figure it all out, one part elated that I finally DID figure it out, so I immediately put Cyanogenmod on my phone... without backing it up. I played with it a bit, but realized my mistake, so downloaded the 2.3.3 Stock Rom.
That totally futzed things up for me... First, my USB connection isn't working anymore. The USB cable still powers my phone, and the USB ports on my PC still work, but I can't get a phone to pc connection through USB anymore.
Second, my cell radio isn't working anymore, I can only get anything over wifi. The OTA 2.3.4 update was pushed and installed to me that way (The current version my phone is on now...)
Third, apparently my phone was no longer rooted, so Rom Manager wouldn't work anymore for me. When I go to the bootloader menu and try to Recover, it brings me to an android with a triangle and exclamation point symbol.
Once there, some trial and error brought up a menu that I'd hoped would have let me reroot or reinstall a working Rom, but every one I try gives me a Signature Verification error and aborts the install...
So, I'm stuck... Without my USB connection working, I can reroot my phone, and without rerooting, I can't get a working ROM back in place. If ANYBODY can help me with this, it will be greatly appreciated. If any additional information is needed, I'll do my best to give it. Thank you...

Who is your carrier? Need to know which phone you have.
Also I assume that since you said you rooted the hard way eventually, that means you successfully used Fastboot to unlock your bootloader, yes?
The Android with exclamation point is just the stock Android recovery partition.
The key to fixing your problem will be to get USB connection between phone and PC.
Please plug in your phone to USB connected to your computer, then put your phone into Bootloader mode (Power on while holding Volume Up). On your computer, open a command prompt window and type "fastboot devices" and post what it says.

Can you see the phone in fast boot by usb also have you course factory reset and then try to flash
Sent from my Nexus S 4G using Tapatalk

The big problem is that I'm unable to make a USB connection anymore. My phone is not reading any kind of connection to allow for file transfers or debugging, but it still powers the phone.

TBoarder said:
The big problem is that I'm unable to make a USB connection anymore. My phone is not reading any kind of connection to allow for file transfers or debugging, but it still powers the phone.
Click to expand...
Click to collapse
Can you answer my question about fastboot? I want to help you.

matt2053 said:
Who is your carrier? Need to know which phone you have.
Also I assume that since you said you rooted the hard way eventually, that means you successfully used Fastboot to unlock your bootloader, yes?
The Android with exclamation point is just the stock Android recovery partition.
The key to fixing your problem will be to get USB connection between phone and PC.
Please plug in your phone to USB connected to your computer, then put your phone into Bootloader mode (Power on while holding Volume Up). On your computer, open a command prompt window and type "fastboot devices" and post what it says.
Click to expand...
Click to collapse
I did that and nothing came up.

TBoarder said:
I did that and nothing came up.
Click to expand...
Click to collapse
ok can you please install PDAnet on your computer?
http://junefabrics.com/android/download.php
This will ensure the proper must up to date drivers are installed for you. This is the best and most reliable way to get the correct drivers.
EDIT: Then try fastboot again and tell me the output for "fastboot devices"

matt2053 said:
ok can you please install PDAnet on your computer?
This will ensure the proper must up to date drivers are installed for you. This is the best and most reliable way to get the correct drivers.
EDIT: Then try fastboot again and tell me the output for "fastboot devices"
Click to expand...
Click to collapse
It was already installed, but I reinstalled it. I got to the end of the process where it asked me to go into USB Debugging mode and won't finish the install because it's not reading the USB connection.
(Sorry for any delays here... Being a newbie, I have a 5 minute delay between when I can post)

No worries, thanks for trying. If you have hardware failure you might be out of luck. USB connection is pretty crucial for this stuff.
Maybe you can try Odin. See here: http://forum.xda-developers.com/showthread.php?t=947950

matt2053 said:
No worries, thanks for trying. If you have hardware failure you might be out of luck. USB connection is pretty crucial for this stuff.
Maybe you can try Odin. See here:
Click to expand...
Click to collapse
I've been looking into Odin, to see if there's a way I can do it just by pushing the files I need to my phone's sdcard and going into recovery mode. Not looking likely, but I'll read through the thread you linked me and maybe something will pop up. Thank you...
On the plus side, I just contacted Sprint and I *might* be able to get my phone replaced... Much as I'd like to troubleshoot this myself, it's looking like my only option. Too bad getting a phone replaced this early in a contract, just out of the warranty period is a total pain in the neck...

TBoarder said:
I've been looking into Odin, to see if there's a way I can do it just by pushing the files I need to my phone's sdcard and going into recovery mode. Not looking likely, but I'll read through the thread you linked me and maybe something will pop up. Thank you...
On the plus side, I just contacted Sprint and I *might* be able to get my phone replaced... Much as I'd like to troubleshoot this myself, it's looking like my only option. Too bad getting a phone replaced this early in a contract, just out of the warranty period is a total pain in the neck...
Click to expand...
Click to collapse
Can you post a link to the stock image you installed?

Was there ever a 2.3.3 for the nexus s 4g? Seems like it shipped with 2.3.4
Sent from my SPH-P100 using XDA App

matt2053 said:
Can you post a link to the stock image you installed?
Click to expand...
Click to collapse
It was downloaded through ROM Manager.
And yes, if I could get back into ROM Manager, I'd warn people NOT to flash their ROM to that. Bad mojo there.

My suggestion is to try and use Odin to flash it back to stock, I don't think Odin needs any drivers to see the phone...
Sent from my Nexus S 4G using XDA Premium App

TBoarder said:
It was downloaded through ROM Manager.
And yes, if I could get back into ROM Manager, I'd warn people NOT to flash their ROM to that. Bad mojo there.
Click to expand...
Click to collapse
Yeah see the thing is there is no 2.3.3 for NS4G. If you flashed 2.3.3 that means you flashed a GSM Rom on your CDMA phone. Oops! not the first time it has happened I'm sure.
Sent from my Nexus S using XDA App

Which totally explains what went wrong... Wow. ROM Manager, I though, was supposed to only bring up ROMs that are compatible with your phone model. Any way somebody can either let the developer know about this, or at the very least put a comment in the 2.3.3 ROM that specifically says it won't work with Sprint's network? That way nobody else will go through the hell I put myself through...
I'm wondering, could the USB connection issue be connected, like the "program" that controls that is integrated with the radio? Just curious, is all. Thanks again for your help!

How did you find astock 233 rom in rom manager, I only see cyanogen nighties oxygen, peter alphonso, extras etc everything is for the nexus a 4g
Sent from my Nexus S 4G using Tapatalk

TBoarder said:
Which totally explains what went wrong... Wow. ROM Manager, I though, was supposed to only bring up ROMs that are compatible with your phone model. Any way somebody can either let the developer know about this, or at the very least put a comment in the 2.3.3 ROM that specifically says it won't work with Sprint's network? That way nobody else will go through the hell I put myself through...
I'm wondering, could the USB connection issue be connected, like the "program" that controls that is integrated with the radio? Just curious, is all. Thanks again for your help!
Click to expand...
Click to collapse
Yeah. I have the T-Mobile version. When I download through Rom Manager I get a popup that says "select your phone model" or something similar and then two choices: "Nexus S" or "Nexus S 4G". It would be really easy to mess that up.
The good news is that I believe your phone can still be recovered, you're definitely not the first person with this exact issue, and at worst, it sounds like you have a Sprint rep who is willing to work with you. I think Odin is your only chance for a software solution. I can't walk you through Odin though, because I've never used it myself.

Let me know what happens.
Sent from my Nexus S using XDA App

matt2053 said:
Let me know what happens.
Sent from my Nexus S using XDA App
Click to expand...
Click to collapse
I just got my warranty replacement phone due to an abnormally long backorder. Thank you very much for your help (And well, I would've more appreciated it if you hadn't shown me that the problem was all my fault... ). Being my only phone and being poor, I won't be trying to root again, no matter what I learned from this problem. Anyway, thanks again, the help was, in all seriousness, greatly appreciated.

[Q] Hard Bricked GS3

Hello, I just got my new GS3 yesterday. Eager to root and ROM and all the fun stuff. I rooted and unlocked, and used Odin to flash CWM Recovery. Flashed the latest version of Android Revolution HD 16. I wiped cache, dalvik, the whole 9 yards. I did not WIPE boot.img though. Flashed Android Revolution 16, it all went good. Clicked Reboot Phone in CWM Recovery and nothing. No LED light on when plugged into USB or via wall charger. No Download mode, or recovery. Nothing, like nothing at all. Anything you guys suggest?
EDIT: I am not sure if it is Hard Bricked. When I plug it into my PC, it makes a sound. Also tries to install a driver and fails every time.
EDIT2: Okay guys, my fault. Downloaded a ROM that was meant for a different model/type GS3 forum when I have a Verizon GS3 (SCH-1535). Anyone know how to fix this problem? Please disregard this incorrect forum post.

If you flashed anything related to the international S3, Google search J-tag! Or return the device and play dumb...

droidstyle said:
Google search J-tag! Or return the device and play dumb...
Click to expand...
Click to collapse
I am paying for full coverage every month too, and okay, couldn't I also get a Usb JIG to force download mode?

T Greezy said:
I am paying for full coverage every month too, and okay, couldn't I also get a Usb JIG to force download mode?
Click to expand...
Click to collapse
No read my edited post. You most likely hardbricked your device, meaning you no longer have download mode.

droidstyle said:
No read my edited post. You most likely hardbricked your device, meaning you no longer have download mode.
Click to expand...
Click to collapse
Well, I NOW have a red LED on my phone when it is plugged into the PC without battery, sd card, or sim card. Is that a good sign?

T Greezy said:
Well, I NOW have a red LED on my phone when it is plugged into the PC without battery, sd card, or sim card. Is that a good sign?
Click to expand...
Click to collapse
No that verifies what i previously posted.

droidstyle said:
No that verifies what i previously posted.
Click to expand...
Click to collapse
I have faith, thought. I can maybe push something using ADB you think?

You need J-tag.
If there was a way to fix it yourself, nobody on here would worry about bricked phones.
Gotta be super careful and read every single word of a ROM thread and if you aren't sure if it will work for your phone or not, just ask and someone will say either yes or no
Sent from my SCH-I535 using xda app-developers app

josh995 said:
You need J-tag.
If there was a way to fix it yourself, nobody on here would worry about bricked phones.
Gotta be super careful and read every single word of a ROM thread and if you aren't sure if it will work for your phone or not, just ask and someone will say either yes or no
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
I guess so. I read something about plugging the phone into the pc without the battery so the red light would come on. Then, you would hold a combination of buttons, and while you're still holding them, put the battery back in while you're still holding them. I guess J-Tag is the only way? Where can I get this? Someone link me. Thanks!

T Greezy said:
I guess so. I read something about plugging the phone into the pc without the battery so the red light would come on. Then, you would hold a combination of buttons, and while you're still holding them, put the battery back in while you're still holding them. I guess J-Tag is the only way? Where can I get this? Someone link me. Thanks!
Click to expand...
Click to collapse
Look like I'm going to drop 60 bucks for a JTAG service? Anyone please stop me if this is not the only way to fix this
email me at [email protected]!

No one is going to stop you. You flashed an international ROM on an s3. This is a known method of hard bricking your s3.
Sent from my SCH-I535 using xda app-developers app

T Greezy said:
Look like I'm going to drop 60 bucks for a JTAG service? Anyone please stop me if this is not the only way to fix this
email me at [email protected]!
Click to expand...
Click to collapse
That sounds about right. Luckily it's $60 and not $600 for a new phone
Sent from my SCH-I535 using xda app-developers app

Same thing happened to me. Needed a j-tag but risked calling Verizon told them my phone wouldn't come on all they asked me was if I damaged it with water or heat. (Either Verizon doesn't care or actually they just scrap the phone) I was rooted and unlocked but flashed the wrong carrier rom. Now I have a replacement phone that cost me $0.
They sent me the 16g and not the 32g by mistake I figured I've pushed my luck enough
Sent from my SCH-I535 using Tapatalk 2

First go to Get.cm download a d2vzw rom. Put it on your sd card. Put the sd card into phone
If you have ADB on your computer do
Code:
adb reboot recovery
You should boot in Clockwork Recovery.
From there flash the D2VZW Rom, Wipe Data,
That should save you.

ericerk said:
First go to Get.cm download a d2vzw rom. Put it on your sd card. Put the sd card into phone
If you have ADB on your computer do
Code:
adb reboot recovery
You should boot in Clockwork Recovery.
From there flash the D2VZW Rom, Wipe Data,
That should save you.
Click to expand...
Click to collapse
How do you figure? How can you adb recovery when the device wont turn on? The device is hardbricked plain and simple...your advice is simply false hope.

I do have a question for the op and the other guy who flashed an international ROM. Were did you get them and how did you find then ( like was it a site you googled?) I've noticed a lot of these lately and am wondering if it's something that can be avoided (besides the obvious read what you're flashing)
To the adb guy there us no recovery on his phone it was overwritten by part of the international ROM. he needs to JTAG his phone, don't call Verizon. You did this to your own phone, pay the 60 and learn your lesson.
Sent from my SGS3 running Eclipse 2.1

droidstyle said:
How do you figure? How can you adb recovery when the device wont turn on? The device is hardbricked plain and simple...your advice is simply false hope.
Click to expand...
Click to collapse
One day someone is going to find a way to unbrick the hard brick, lol. Eventually. Anyways, if it was "dead" then why would it show my S3 as "QHSUSB_DLOAD"? and attempts to install a driver. I'm gonna try to find the right driver to manually install, and troubleshoot from there. I mean come on guys, be optimistic. How great if this problem was RESOLVED? Also, the download mode got wiped/overwritten from a different ROM for a different model of the GS3. What about the Recovery? CWM? If I can just magically, somehow, maybe even push some type of command. Even maybe ADB? Or something in the terminal. I'm really trying to find a solution. So in the future, we will have a SOLUTION.
Anyways, I'm going to be shipping my GS3 Monday or Tuesday for Samsung to repair (If they can) or replace for no charge!
Wish me luck guys, gonna be really thinking out of the box.

Hope you can figure it out. But someone had a way to fix a hard brick.... The JTAG
Sent from my SGS3 running Eclipse 2.1

Okay guys, I've actually have gotten some good progress, I hope! I came across a thread that a guy named (therockk) he also, hard bricked his S3. Sent him a PM, and he told me he got ODIN to recognize his hard bricked S3 "WITHOUT" download mode. He said he found a driver for QHSUSB_DLOAD and manually applied the driver update. His PC, then recognized his S3 as a ID CODE: COM10 - I do not know what that means, I asked around. Some people say that it is the code for when your phone is connected in Download Mode? Nevertheless, this is good in my eyes. The phone as now, recognized as COM10 in ODIN, in its hard-bricked stage. This could be that also, maybe, the phone will be recognized in ADB/Fastboot commands. Maybe we can get something going here guys! I'm trying to look on the bright side. I'll keep you posted.
EDIT: Okay guys, was looking at some screenshots of the CODE ID's. Like I said, my buddy "therockk" said he got ODIN to recognize his phone as a COM10, while being hard-bricked. I am guessing there are different CODE ID's for each model/version of the S3. I did make an observation that he, has a different model S3 ( i747 ) and he got his to see COM10. Which means it was Added!! - My Verizon S3 (SCH-1525) should come up as COM4 when the PC recognizes it. When I do get my PC to recognize my S3, I will confirm that my SCH-1535 phone comes up as COM4, if not, I will confirm the correct CODE ID. therockk's i747 came up as a COM10, that is confirmed.
EDIT 2: Okay guys! Updated the driver successfully! QSHUSB_DLOAD is now Qualcomm HS-USB QDLoader 9008 (COM8). I feel like we're getting closer. Now to see if Odin will pick it up!

I can probably help you through this problem after work tonight if you are still having trouble. Just pm me around 10pm est
Sent from my SCH-I535 using xda app-developers app

[Q] screwed something while installing cromi4.0 need some direction

ok so i installed the asus 4.2 no problem. bootloader is unlocked. i then flashed twrp 4.2, then realized i needed to do push 4.4 twrp instead. so i did that. i was able to boot to the asus rom no problem. i then rebooted into twrp, and it starts asking me for a password, all i could do was hit cancel. Nothing will mount, no sdcards no external, no internal memory. so i did a bit of reading and someone said a factory reset from the bootloader screen would fix twrp. that was a big nope.
so, now the tablet will only boot into twrp, but not read anything, and i cant even get to the fastboot menu so that i can push anything. when i reset it says install super user??/ but it also says no os installed. i have a rom on my sd card i could load if i can get twrp to read it, but i tried mounting, and unmounting, and pretty much every option in every menu.
anyone have any insite?
Thank you
Mike

Who would have thought. I registered because of this exact issue. Actually, bought the Pad today and wanted to install this ROM which ended with a device that's stuck in recovery.
In my case I first unlocked, updated to the newest stock OS then installed TWRP "openrecovery-twrp-2.4.4.0-tf300t-JB.blob". After that it's the same as the OP.
I'm a noob, but I could install ADB drivers and then push files into the device with it ( including stock ROM ). Unfortunately, trying to install it ended with failure. Every time you reboot all the pushed files disappear, too.
Other than in ADB, the tablet is invisible to Windows ( says no drivers ).
After some research it's become rather obvious that our devices are bricked. So far it seems like the only way to fix this is to send our Pads back to Asus. The bad news is that they are likely to offer motherboard replacement which is close to the value of a new Transformer.
Myself I'll be emailing them tomorrow.

bythewayr said:
Who would have thought. I registered because of this exact issue. Actually, bought the Pad today and wanted to install this ROM which ended with a device that's stuck in recovery.
In my case I first unlocked, updated to the newest stock OS then installed TWRP "openrecovery-twrp-2.4.4.0-tf300t-JB.blob". After that it's the same as the OP.
I'm a noob, but I could install ADB drivers and then push files into the device with it ( including stock ROM ). Unfortunately, trying to install it ended with failure. Every time you reboot all the pushed files disappear, too.
Other than in ADB, the tablet is invisible to Windows ( says no drivers ).
After some research it's become rather obvious that our devices are bricked. So far it seems like the only way to fix this is to send our Pads back to Asus. The bad news is that they are likely to offer motherboard replacement which is close to the value of a new Transformer.
Myself I'll be emailing them tomorrow.
Click to expand...
Click to collapse
Did you use twrp from their site.or the modded one here on the forums
Sent from magical jelly bean.

Yeah. I had the modded one from the thread on the tab. But when i hooked it up to the computer and had everything in fast boot. I hadnt copied it over so i grabbed one from their site. I knew i screwed up something
Sent from my Galaxy Nexus using xda app-developers app

klownin5643 said:
Yeah. I had the modded one from the thread on the tab. But when i hooked it up to the computer and had everything in fast boot. I hadnt copied it over so i grabbed one from their site. I knew i screwed up something
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
That's your issue.you need the modded one
Sent from magical jelly bean.

kaos420 said:
That's your issue.you need the modded one
Sent from magical jelly bean.
Click to expand...
Click to collapse
Yeah, the only problem being that we can no longer flash anything. There's still no solution, right?

bythewayr said:
Yeah, the only problem being that we can no longer flash anything. There's still no solution, right?
Click to expand...
Click to collapse
Not sure why I stayed on 4.1 boot loader with 4.2.2 cm10.1 just not worth it to me until a o.c kernel appears
Sent from magical jelly bean.

bythewayr said:
Yeah, the only problem being that we can no longer flash anything. There's still no solution, right?
Click to expand...
Click to collapse
You might want to dig through the forums. I believe I did read about a trick using the little reset hole (About an inch below the microSD).
From there it might be possible to flash the modded TWRP. From there you should be able to get back into your JB.
I'd be very careful with flashing ROMs, I still don't see anything that confirms we can use one safely on our newest model/version.

I would be totally fine. Just installing stock Asus jellybean for now. Just so I works. I found the thread on the reset hole. I'm going to try it this afternoon.
Sent from my Galaxy Nexus using xda app-developers app

As long as fastboot still works you're not bricked. If you can't boot to download mode try adb in recovery mode and send
Adb reboot download
Sent from my SGH-T999
"So I put my phone into airplane mode and threw it... worst transformer ever. -.-" -My friend

I don't know if fast boot still works. When I boot up it boots directly to twrp I don't have the option to enter recovery. It flops directly into recovery. I'm gonna try and play with this so called reset button and see if that gets me anywhere. If I can get to fast boot from there I might be OK.
Sent from my Galaxy Nexus using xda app-developers app

klownin5643 said:
I don't know if fast boot still works. When I boot up it boots directly to twrp I don't have the option to enter recovery. It flops directly into recovery. I'm gonna try and play with this so called reset button and see if that gets me anywhere. If I can get to fast boot from there I might be OK.
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
Check if ADB still works, it should since you have TRWP!
and try:
adb reboot bootloader

klownin5643 said:
I don't know if fast boot still works. When I boot up it boots directly to twrp I don't have the option to enter recovery. It flops directly into recovery. I'm gonna try and play with this so called reset button and see if that gets me anywhere. If I can get to fast boot from there I might be OK.
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
That's why I said to execute adb from recovery.
Code:
adb reboot download
Sent from my ASUS Transformer Pad TF300T using Tapatalk 2

ok so the adb reboot bootloader worked. and i was finally able to reboot into the os. turns out it was still on there even though twrp said it was not. so now, i suppose im going to reboot into fastboot, and push the new modded twrp from fastboot. and we should be good? Im going to try it. ill report back. now that i know my adb works correctly, im not so scared of getting stuck. back in a few. thank you guys for the help. and direction. i only hope this helps someone else not get as stuck as i was.
edit:
yeah so that is no good. downloaded the modded one from the thread. though it appears that its the same as the one from twrp site. except the link in the cromi 4.0 first post points to an androidfiledownload site. i pushed it via fastboot. except when executing the reboot command, it simply booted back to the twrp screen with it still asking for a password. so now i guess im looking at reflashing the asus stock rom and letting rewrite the recovery? and starting fresh? can i do that via adb? im still learning adb and fastboot stuff. Thanks.

Can't check this adb command solution till next Thursday but I sure hope it'll work for me, too.
As far as I understand this whole TWRP problem is that it doesn't have permission to do anything which thankfully should keep the original OS safe.
Keep us posted klownin5643. At this point I'm also mostly concerned with getting back the original recovery program.

Same issue here! Happened to me a few weeks back:
http://forum.xda-developers.com/showthread.php?t=2197895
Only when mine booted directly into TWRP connecting it to the PC didnt yeaild me any results, even after I was able to get the PC to install the naked drivers. The PC would error and say, unable to start device so ADB would not work for me either and trying 'adb devices' didnt return any results. The ONLY thing that worked for me was booting into ADX but that did me no good as I had not installed NVFLASH prior to the brick.
The resolution for me was to replace the mainboard. I got it off of eBay for 88 dollars shipped. I replaced it the same day it came in and Im up and running on the new stock 4.2.1 ASUS release. Paying the 88 dollars was better than shopping for a new tablet
Good luck with your troubleshooting OP! :good:

I'm wondering at this point, can I even flash a new recovery? Or even reflash a new ROM thru fast boot? Someone else said they tried thru adb but the files just disappeared. Or was that cause he was just pushing it to the memory card? I had the os running but I got a freeze and reboot. And it went right back to the direct loading of twrp. I don't wanna have to do that every time I restart. What would be the ASB command or fast boot to flash a new rom.?
Sent from my Galaxy Nexus using xda app-developers app

I know I'm not the only one with this problem. But has anyone flashed the stock blob over top and got everything back to normal?
Sent from my ASUS Transformer Pad TF300T using xda app-developers app

Refering to your question about pushing files with ADB. I pushed them to internal memory, but that was in recovery mode with locked twrp. If you can get out of recovery with "adb reboot bootloader" then it wouldn't be directly applicable.
If you really have functional fastboot commands ( i.e. commands working instead of "waiting for device" ) then flashing a new ROM or recovery should be, more or less, straightforward. One thing I'm not sure about myself is whether new recovery can be named whatever or should it be called "twrp.blob" again. Technically, yoou're giving a "flash recovery" command so it should replace the current one, whatever it is but I'd rather not brick my device for good with a bad flash. Either way, like I mentioned, I have to wait till thursday to try anything.
I have to read more about fastboot to help with the right commands but there's a lot of guides out there.

I can give the flash recovery command and it will be fine. When I give the reboot command it freezes.
Sent from my Galaxy Nexus using xda app-developers app

[Q] Bricked?

Hello,
(My friend helped me with all this)
we were trying to root my phone and put cyanogenmod on it,
that worked and we saw we forgot to put google play on it,
we tried and my was stuck in bootloop, and after trying different things,
I got a black screen with green, red and blue dotted lines.
I can't get into download or any of the other modes either
Could someone please help me with this
Thanks in advance!

GyroW said:
Hello,
(My friend helped me with all this)
we were trying to root my phone and put cyanogenmod on it,
that worked and we saw we forgot to put google play on it,
we tried and my was stuck in bootloop, and after trying different things,
I got a black screen with green, red and blue dotted lines.
I can't get into download or any of the other modes either
Could someone please help me with this
Thanks in advance!
Click to expand...
Click to collapse
Depending on what phone your using can you get into recovery mode? If I knew what device your using, I could tell you how. You have to flash a "gapps" .zip to use the google play app. If you can't get into recovery mode at all, you have to reflash a stock ROM through your computer, like you did with cyanogenmod.
What were the "different things" you did, that caused it to brick and give you the dotted lines?

sinndissension said:
Depending on what phone your using can you get into recovery mode? If I knew what device your using, I could tell you how. You have to flash a "gapps" .zip to use the google play app. If you can't get into recovery mode at all, you have to reflash a stock ROM through your computer, like you did with cyanogenmod.
What were the "different things" you did, that caused it to brick and give you the dotted lines?
Click to expand...
Click to collapse
Sorry to not tell you what phone i had,
Its a samsung Xcover 2.
My friend gave me the list of things we did:
1. Flashed a root file to get root access | All fine
2. Checked root access | All worked
3. Flashed CWM recovery | All fine
4. In CWM, we flashed Cyanogenmod | Not fine
5. After, we factory resetted | All worked (CM)
6. We flashed gapps | All fine
7. CWM was stuck in a bootloop, eventually the screen turned to green dots
8. Phone won't go into any mode, with a black screen.

Phone won't respond either to any button pressing combos,
won't show up in list of attached devices and neither on adb with the "adb devices" command.
Now phone boots every so often with the coloured dotted lines.

Someone?
I really just want to use my phone, it doens't matter for me anymore if it's rooted or not.

Please, i just want to use my phone...

I had something similar happen with my nexus 4, but it wouldn't boot up in any way, not even the colored lines. If your computer stops recognizong the device, its usually a hard brick, and it's not fixable. But some people have luck, so did you do the factory reset before, or after flashing cyanogenmod?
Sent from my Nexus 4 using XDA Premium 4 mobile app

sinndissension said:
I had something similar happen with my nexus 4, but it wouldn't boot up in any way, not even the colored lines. If your computer stops recognizong the device, its usually a hard brick, and it's not fixable. But some people have luck, so did you do the factory reset before, or after flashing cyanogenmod?
Sent from my Nexus 4 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
After CM

That could be your problem, your supposed to wipe BEFORE you flash any new ROMs, or gapps packages. Flashing the root package, CM, and gapps package, THEN wiping, may have caused a "hard brick". Someone with more experience with this would be able to to tell you for sure, but if it's a true hard brick, your only option is JTAG, or getting a new phone. Unless you can boot into recovery, or use adb with your computer, there isn't really a fix for it.
Sent from my Nexus 4 using XDA Premium 4 mobile app

sinndissension said:
That could be your problem, your supposed to wipe BEFORE you flash any new ROMs, or gapps packages. Flashing the root package, CM, and gapps package, THEN wiping, may have caused a "hard brick". Someone with more experience with this would be able to to tell you for sure, but if it's a true hard brick, your only option is JTAG, or getting a new phone. Unless you can boot into recovery, or use adb with your computer, there isn't really a fix for it.
Sent from my Nexus 4 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Can you help me find a more experienced person?

Look up the phone you have, and post this question in the help and troubleshooting section underneath the specific phone your using, and you'll probably get better answers. Sorry I couldnt be more help. /:
Sent from my Nexus 4 using XDA Premium 4 mobile app

sinndissension said:
Look up the phone you have, and post this question in the help and troubleshooting section underneath the specific phone your using, and you'll probably get better answers. Sorry I couldnt be more help. /:
Sent from my Nexus 4 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Thanks alot, cause your answer I got a little bit closer to a solution i think.
(Answers are getting more relevant)