So, before you think "Oh this guy just doesnt know how to enter fastboot mode" let me explain. So I had a Nexus S for att, all of the sudden *poof* the motherboard stopped working. So I bought a broken Spring Nexus S 4G. So I swapped the motherboards and all was good. Well, I wanted to use it for att. So I also swapped the Sprint communication board with the att one. Well it didn't boot after the switch. So I thought about putting a crespo rom on the crespo4g. It didnt like that, it wouldnt let me restore it. So I thought about flashing the bootloader from crespo. Fastboot accepted it, but then it rebooted fastboot could no longer find a device. Sadly, I hadn't rooted it or installed a custom recovery. If anyone has an idea to restore the crespo4g bootloader that would be amazing. Or a way to root without fastboot, then I could flash the recovery from userland.
Thanks,
Littlejd97
Littlejd97 said:
So, before you think "Oh this guy just doesnt know how to enter fastboot mode" let me explain. So I had a Nexus S for att, all of the sudden *poof* the motherboard stopped working. So I bought a broken Spring Nexus S 4G. So I swapped the motherboards and all was good. Well, I wanted to use it for att. So I also swapped the Sprint communication board with the att one. Well it didn't boot after the switch. So I thought about putting a crespo rom on the crespo4g. It didnt like that, it wouldnt let me restore it. So I thought about flashing the bootloader from crespo. Fastboot accepted it, but then it rebooted fastboot could no longer find a device. Sadly, I hadn't rooted it or installed a custom recovery. If anyone has an idea to restore the crespo4g bootloader that would be amazing. Or a way to root without fastboot, then I could flash the recovery from userland.
Thanks,
Littlejd97
Click to expand...
Click to collapse
Hi, try to go trough the Nexus Root Tool kit.
Related
My sister recently got her LG vortex and her husband rooted it and tried to flash clockwork recovery (i know). Upon reboot, it goes into fastboot and that is it. I don't want to tell them to douche move Verizon and get a replacement bit I have found basically nothing as far as files to recover from fastboot or anything like that. They are a few states away and I want to get them operational again.
Who knows how to help me help them?
Sent from my ADR6400L using Tapatalk
ever get that vortex out of fastboot????
Try to reflash the the recovery.img that is clockworkmod via fastboot or find another that is without a day doubt for that phone. If this is the only thing he was messing with then he must have corrupted the recovery. make sure the file he is flashing through fastboot is a image file ("img") or has that as the file extention and not something else such as a zip file etc etc.
junebug85 said:
My sister recently got her LG vortex and her husband rooted it and tried to flash clockwork recovery (i know). Upon reboot, it goes into fastboot and that is it. I don't want to tell them to douche move Verizon and get a replacement bit I have found basically nothing as far as files to recover from fastboot or anything like that. They are a few states away and I want to get them operational again.
Who knows how to help me help them?
Sent from my ADR6400L using Tapatalk
Click to expand...
Click to collapse
heres a guide (use the files that suit your phone):
http://forum.xda-developers.com/showthread.php?t=1088046
I screwed up big time. I got my nexus s 4g and unlocked and rooted. all was going well and I went the custom rom route and used rom manager to do so. It was g found out after my radio didnt work. I tried to flash back to stock and it did. I found out it was gsm stock and I am a f#cking moron, so I'm stuck on stock, unrooted, no radio and no computer can it now, not the samsung prog, odin, or adb. the usb on pc will charge, but not push data, please can anyone help.
n00b1269 said:
I screwed up big time. I got my nexus s 4g and unlocked and rooted. all was going well and I went the custom rom route and used rom manager to do so. It was g found out after my radio didnt work. I tried to flash back to stock and it did. I found out it was gsm stock and I am a f#cking moron, so I'm stuck on stock, unrooted, no radio and no computer can it now, not the samsung prog, odin, or adb. the usb on pc will charge, but not push data, please can anyone help.
Click to expand...
Click to collapse
in the other forum you said fastboot is not working right? did u enable usb debugging?
PM sent. I can fix this.
My dad came home from work today and his stock Inspire 4G has stopped working. Nothing has been done to it. It simply hard locked and turned itself off. Since then I can't get it to boot past the boot loader. Once it's in the bootloader it checks for the PG98IMG.zip and then doesn't respond to anything else. I have tried numerous battery pulls, connecting to the phone with ADB and so forth but no response from the phone. Any ideas? AT&T has shipped him a refurb, but I figured I would take a crack at it until then since his phone would probably be better than some random refurb.
Sad, seems like it's boot looping: on stock rom, no less. My options will void the warranty, though, as it entails installing custom roms:
1. Push a cooked rom by rooting it. The cooked rom should be clean, but it will be rooted, thus, warranty void.
2. Try looking for stock rom for the HTC Inspire, push that using ADB and have the bootloader use it. Hopefully, it should restore stock settings to your inspire and still be replaced through warranty (i wouldn't know, I haven't sent a rooted phone in to warranty yet)
If that fails, might as well call AT&T and say it's a dud.
Truculent said:
My dad came home from work today and his stock Inspire 4G has stopped working. Nothing has been done to it. It simply hard locked and turned itself off. Since then I can't get it to boot past the boot loader. Once it's in the bootloader it checks for the PG98IMG.zip and then doesn't respond to anything else. I have tried numerous battery pulls, connecting to the phone with ADB and so forth but no response from the phone. Any ideas? AT&T has shipped him a refurb, but I figured I would take a crack at it until then since his phone would probably be better than some random refurb.
Click to expand...
Click to collapse
You could take the pd98img.zip from the ruu and it would do a clean install and more then likely boot the phone up, unless it is a hardware issue. I don't see the need to root it if all he wants is the stock rom.
Btw you can find the pd98img.zip in the guide stickied in the general section.
Sent from my Inspire 4G using XDA Premium App
Wait, how did you get into the bootloader if you dad's phone is stock?
same way you do on a rooted phone power plus volume down..I think you are confusing the bootloader with recovery.
mudknot2005 said:
same way you do on a rooted phone power plus volume down..I think you are confusing the bootloader with recovery.
Click to expand...
Click to collapse
No, I just didn't know you could do that on stock.
mudknot2005 said:
You could take the pd98img.zip from the ruu and it would do a clean install and more then likely boot the phone up, unless it is a hardware issue. I don't see the need to root it if all he wants is the stock rom.
Btw you can find the pd98img.zip in the guide stickied in the general section.
Sent from my Inspire 4G using XDA Premium App
Click to expand...
Click to collapse
I think I'll try this. I'm wondering if it's a hardware problem though. My dad just told me that yesterday it was losing signal and then he would reboot it and it would regain signal for a little while and drop it again. May be a radio problem.
LEAVE IT BE. There is no reason to monkey with it if you already got the refurb, just send it away. Just because you want to poke around like bill nye or something might end up costing your dad $450.
I Agree Leave it be
Sent from my Inspire 4G using XDA App
Truculent said:
I think I'll try this. I'm wondering if it's a hardware problem though. My dad just told me that yesterday it was losing signal and then he would reboot it and it would regain signal for a little while and drop it again. May be a radio problem.
Click to expand...
Click to collapse
hi, friends my problem is ike that too. I swithed on to Hboot and pushed to recovery. after that my phone can not read PD98IMG.zip, I wanna install stock rom by sd card but it can not read it. when I stand in it sd card with PD98Img, its "checking" then again staying on Hboot system. please help me how to do it?
Why not just take the stock ruu which installs from the pc?
Sent from my Inspire 4G using XDA Premium App
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
I'm currently on my 4th replacement from Verizon. Everytime the phone has either went into an endless bootloader loop where clicking start takes me back to the bootloader and when going to recovery it says "failed to boot to recovery" or turned off and wouldn't turn back on and essentially becomes a bricked phone. Is there anyone else with this problem?
Edit- I'm on stock Android 7.1.1 and not rooted.
Timtube said:
I'm currently on my 4th replacement from Verizon. Everytime the phone has either went into an endless bootloader loop where clicking start takes me back to the bootloader and when going to recovery it says "failed to boot to recovery" or turned off and wouldn't turn back on and essentially becomes a bricked phone. Is there anyone else with this problem?
Click to expand...
Click to collapse
Did it work in the Verizon store? I've perhaps seen this once or twice but a replacement device usually worked. But 4 devices? That just doesn't seem real. Not that you're making it up but you need to explain what you are doing before the device goes into a boot loop. Worst case scenario, go to a store and make sure the phone works before you leave.
Weird sounds like you are trying to use depixel8 on an unsupported firmware? And you are bootlooping the phone ?
happened to me on my first device, partly why i havent SU or TWRP yet....just unlocked for future fun...
Mine bricked inbetween twrp and SU....but im sure i messed up somewhere. TWRP worked but as soon as i did SU, it all went wrong for me.....Figured id wait to more stable stuff is out, before messing around again.
mine did the same thing as what your describing...
peace
byte
I did not unlock the bootloader. I am not rooted. I am using stock Verizon Pixel XL 7.1.1.
well that changes everything, sounds like just bad luck dude
bytethegroove said:
well that changes everything, sounds like just bad luck dude
Click to expand...
Click to collapse
I know it sucks. I really like the phone when it works.