Related
Just bricked a friends TF. Is it possible to unbrick it to stock rom ?
He just updated to latest 3.2WW ROM prior to this.
How exactly did you brick it? What were you doing at the time?
I managed to wipe all partitions .. for various reasons I ran download.sh which apparently formatted the whole TF and reformated it.
At this point I'm downloading the latest tf_rootkit_31 to get the cwm recovery image from it.. but I have my douts that this will work.
I have downloaded the last release from ASUS website and tried to nvflash on the blob files.. but it stays in APX mode..
I have PRIME 1.6r2 but I have no clue how to get this on the device .. without CWM ..
As i thought... didnt work.. but the download.sh wants system.img which I don't have.. :|
think I managed to get it unbricked.
I dumped recovery and system from my working TF101 .. seems to be booting now at least..
This thread can be locked or deleted... as mod see fit
Basically I managed to run the wrong script as I were about to root the TF. Instead of root.sh (self made) that run the needed commands to download, patch and send in the patched boot image back to the TF.
Download.sh is from someone else, don't really who.. but it does wipe the device and flash in boot.img, system.img and recovery.img ..
After fetching the needed files from a working TF101 and flashed it back to the device it is now up and running, but all apps need to be re-installed and setup again.. thankfully he made a mybackup pro backup prior to updating the device.. so I hope he'll managed to restore most of the device back to its original again.
What I love about the TF is that it seems impossible to permabrick. Glad to hear you got it going again.
Glad to hear it. I bricked mine not more than 5 hours ago, and sorted that too.
It's not very nice but you learn as you go I suppose..
(mmh I hate the new mouse-pointer )
Sent from my Transformer TF101 using Tapatalk
Need to pick this up again.. for some reason he doesn't have the 8.4.4.11/8.6.5.7 boot screen.. the one before the boot animation comes into play.. the one he has is the same as 8.4.4.5 .. any1 know the reason and/or a possible fix for this ?
Sent from my Transformer TF101 using Tapatalk
paddy01 said:
Need to pick this up again.. for some reason he doesn't have the 8.4.4.11/8.6.5.7 boot screen.. the one before the boot animation comes into play.. the one he has is the same as 8.4.4.5 .. any1 know the reason and/or a possible fix for this ?
Sent from my Transformer TF101 using Tapatalk
Click to expand...
Click to collapse
You have to update the bootloader too. It's the EBT partition in the flash.cfg. add something like filename=blob.EBT
You can extract the EBT/bootloader partition from the blob in the 8656 update. Rayman has put out some blob tools for extraction.
sent from my cyanogen(mod) vision
gee one said:
You have to update the bootloader too. It's the EBT partition in the flash.cfg. add something like filename=blob.EBT
You can extract the EBT/bootloader partition from the blob in the 8656 update. Rayman has put out some blob tools for extraction.
sent from my cyanogen(mod) vision
Click to expand...
Click to collapse
Aha perfect, thanks!
Sent from my Transformer TF101 using Tapatalk
paddy01 said:
Aha perfect, thanks!
Sent from my Transformer TF101 using Tapatalk
Click to expand...
Click to collapse
You might want to update the bootloader flag in the command line too "-bl blob.EBT" I'm not positive but I think this prevents bootloops since the images are flashed with the same bootloader that it is writing.
sent from my cyanogen(mod) vision
gee one said:
You might want to update the bootloader flag in the command line too "-bl blob.EBT" I'm not positive but I think this prevents bootloops since the images are flashed with the same bootloader that it is writing.
sent from my cyanogen(mod) vision
Click to expand...
Click to collapse
Thanks a lot for the answers. I haven't got around to do this yet so I have some further questions.. is there a way to do this without wiping the device ?
Also it seems like his Transformer think it's a mobile phone.. eh yea it has like EMEI column and stuff in the information tab.. will the bootloader fix that too ?
the update to 8.6.5.9 didn't appear automatically so we are currently manually updating it to that release.. might fix things.. we'll see..
Edit1: NM! the update to 8.6.5.9 fixed all the issues that were previously
ok so i rooted my xoom the other day flashed hammer head 2.1. restored my tablet to stock rooted rom buwhen i did i have now found a way to lock my device. i can boot up and have my su icon available to me however i cannot gain root access even through adb it tells me the file system is read only. so i figured i some how unrooted the device and proceeded to begin the root process for honeycomb. however when trying to push su over to the tablet it tells me the file failed to transfer because the file system is read only what do i do now? Any help would be appreciated.
Ok i have now some how erased my device completely it stops at the moto dual core boot screen. I still have cwm but thats it. Im at a loss guys. Bout to warranty this by runnin over it!
Sent from my ADR6400L using XDA Premium App
josephparlangeli said:
Ok i have now some how erased my device completely it stops at the moto dual core boot screen. I still have cwm but thats it. Im at a loss guys. Bout to warranty this by runnin over it!
Sent from my ADR6400L using XDA Premium App
Click to expand...
Click to collapse
your a noob mate seriously... these board are full of people like you... 1.. download the stock images from
http://developer.motorola.com/products/software/MZ604_HWI69.zip/
if your device is a wifi only and then push the files with fastboot...
ie.. unzip the folder into where the adb fastboot exe are
1. fastboot flash system system.img
2. fastboot flash boot boot.img
3. fastboot flash user user.img
4. fastboot flash recovery recovery.img (as you obviously cant handle root..)
Dont have to be an ass about it. But yeah already tried that when i try to push the files it tells me there is no such directory found. So i made sure in cwmr the system was mounted then it tries to transfer but tells me the directory is read only. So i tried the unlock procedure to make sure the tablet was unlocked. everything goes smoothly till i try to transfer the files again.
Sent from my ADR6400L using XDA Premium App
josephparlangeli said:
Dont have to be an ass about it. But yeah already tried that when i try to push the files it tells me there is no such directory found. So i made sure in cwmr the system was mounted then it tries to transfer but tells me the directory is read only. So i tried the unlock procedure to make sure the tablet was unlocked. everything goes smoothly till i try to transfer the files again.
Sent from my ADR6400L using XDA Premium App
Click to expand...
Click to collapse
Not talking mounting in cwm here bud
Get to fastboot mode not android recovery same process power plus vol down
Then flash the files not push as mounting in cwm only put the files on sd card not flashing it outright from what your reply was
I was a noob once and soft bricked everything and yet i read and read and fixed stuff myself through searching.. Cuz ultimately if its bricked what do u have to lose then ey lol just find and try everything cant make a worse paperweight than one u may already have eh
But get to fastboot not cwm then flash the files like i said and it will almost certainly work
Sent from my HTC Sensation 4G using XDA Premium App
Thats my other problem my sd card slot isnt wrkn that was my initial instinct. If i try to flash to the sd card it says no directory found. Ive used 3 different sd cards and get the same message. Im really thinkin i got a bad sd slot even when it was rooted and running i had issues with the sd card not wrking. I had several back ups on it when it did wrk and those dissappeared as well. I bought the xoom soley because of the sd card slot was pretty much going to be my saving grace when doing back ups if i ever messed up. I tried wrking it in fastboot as well if i try to flash to the system its read only. If i flash to the sd card directory not found. I know these questions are irritating to more savy individuals and i looked around trust me the last thing i like to do is say der i dun broke it i need an adult. Im just makin sure i didnt over look something more savy ppl know about. I honestly think its bricked at this point. Ive tried what you said and any other way i can think of but i alway get some kind of error.
Sent from my ADR6400L using XDA Premium App
Sent from my ADR6400L using XDA Premium App
What version of clockwork mod recovery are you using?
I believe is 4.0.0.2 i just got to wrk i know its the latest release tho.
Sent from my ADR6400L using XDA Premium App
josephparlangeli said:
I believe is 4.0.0.2 i just got to wrk i know its the latest release tho.
Sent from my ADR6400L using XDA Premium App
Click to expand...
Click to collapse
I would use this recovery instead of 4.0.0.2.
Ok thats a very helpful link. Did not know they had a special recovry for the xoom or realize that it wiped out all media if i didnt have this recovery. Lesson learned however i think its bricked solid now cuz it wont charge or come on at all may very well be a bad unit but i c where i went wrong with su as well i flashed 3.0 with out the chmod 4577 during the su update from cwm. Well im going to grab another one from bb and c what happens the unit is non responsive at this point. Thanks to everyone that posted here for the help.
Sent from my ADR6400L using XDA Premium App
josephparlangeli said:
Ok thats a very helpful link. Did not know they had a special recovry for the xoom or realize that it wiped out all media if i didnt have this recovery. Lesson learned however i think its bricked solid now cuz it wont charge or come on at all may very well be a bad unit but i c where i went wrong with su as well i flashed 3.0 with out the chmod 4577 during the su update from cwm. Well im going to grab another one from bb and c what happens the unit is non responsive at this point. Thanks to everyone that posted here for the help.
Sent from my ADR6400L using XDA Premium App
Click to expand...
Click to collapse
you needed to flash the recovery with FASTBOOT.. not adb push chmod stuff; much easier and the process works
read the top post again.. get the recovery.img file (the v3 one the other fellow told you to grab)
1. hold the volume down button and the power button... some text will come on up the top about fasboot protocol and then
2. leave it plugged in to your computer and DONT TOUCH THE XOOM...
3. get your cmd.exe prompt window out and navigate to where your adb.exe AND fastboot.exe files are (should be tools or platform-tools...)
4. Place the recovery.img file into the explorer window where the adb.exe and fastboot.exe both are.... (this should be there as u keep trying to use adb commands but do it again to make sure)
5. type fastboot flash recovery recovery.img
thats the recovery.img flashed...
Got my xoom replaced the other day works fine have root flashed the above mention cwm and everything worked fine. Funny thing tho when they checked to see if the original device had been unlocked they said it was still locked and they gave me a replacement. Other wise id have had to use the warranty i bought. Just thought that was odd.
Sent from my ADR6400L using XDA Premium App
josephparlangeli said:
Got my xoom replaced the other day works fine have root flashed the above mention cwm and everything worked fine. Funny thing tho when they checked to see if the original device had been unlocked they said it was still locked and they gave me a replacement. Other wise id have had to use the warranty i bought. Just thought that was odd.
Sent from my ADR6400L using XDA Premium App
Click to expand...
Click to collapse
Well, there's your answer. You did not successfully unlock.
Glad that you learned some useful things.
flying honey comb on xoom mz601
Hi everybody. I install new image for my xoom MZ601 (tiamat last version).
Xoom from Hongkong (CHINA) with 3G.
i make all steps about unlock bootloader and root. After all that steps - i have ClockworkRecovery v 3.2.0.0 (solarnz-R4c-100611-1150). After reboot (motorola logo) i see all time honeycomb flying.
I need help.
opps: i unbrick my device on android 3.0.1. Now try again to install 3.2 by Tiamat
3.2 doesn't work. SAD
aKolp2010 said:
Hi everybody. I install new image for my xoom MZ601 (tiamat last version).
Xoom from Hongkong (CHINA) with 3G.
i make all steps about unlock bootloader and root. After all that steps - i have ClockworkRecovery v 3.2.0.0 (solarnz-R4c-100611-1150). After reboot (motorola logo) i see all time honeycomb flying.
I need help.
opps: i unbrick my device on android 3.0.1. Now try again to install 3.2 by Tiamat
3.2 doesn't work. SAD
Click to expand...
Click to collapse
You should open a new thread with your issue. Seems the OP in this one has fixed his issues by replacing his Xoom. You'll get better attention by creating a new thread in this forum.
Hey guys. Semi newb here. I unlocked my TF300t a while back on the first offical JB update from ASUS. I then followed all the steps to unlock it and use fastboot to install TWRP. This was months back. I have been steadily updating CleanROM Inheritance as the revisions are released.
This latest revision to 3.4.4 flash was easy....as always. I wiped all and installed. When the system came back up I noticed my wifi was broken. I couldnt get it to initialize. So I booted to recovey so I could wipe all and reflash again just in case. Well, TWRP asked me for a password. Ive never encrypted my tablet nor have I used passwrods in the past as I know they can cause issues with access or permissions. I can hit cancel and use twrp but it wont mount anything or allow me to do anything until I 'decrypt' it. Not sure where to go from here. I guess Id like to flash the new official 4.2 from asus but I need advice on how to do this using fastboot.
Any help or pointers are welcomed. I only used the fastboot once to install twrp so I dont completely remember how to use it or if I can use it to flash a full ROM to hopefully reset the tablet. Thanks for any help! Cause I am stumped...
EDIT:
So I tried to turn off the tablet and pressed VOL DN + PWR to get to recovery options and choose fastboot, it just boot loops back to the asus logo twice then goes back in to TWRP. I cant even get into the OS now like I could. I need to unlock TWRP. PLEASE HELP!
EDIT 2:
I just wanted to add that by no means am I putting any blame on the ROM. Its a badass ROM that I love. The issue I am having is most definitely due to the bootloader and TWRP I suspect. I just dont know what I can do in TWRP locked down the way it is to regain some control...or at least fastboot.
cubaniche1 said:
Hey guys. Semi newb here. I unlocked my TF300t a while back on the first offical JB update from ASUS. I then followed all the steps to unlock it and use fastboot to install TWRP. This was months back. I have been steadily updating CleanROM Inheritance as the revisions are released.
This latest revision to 3.4.4 flash was easy....as always. I wiped all and installed. When the system came back up I noticed my wifi was broken. I couldnt get it to initialize. So I booted to recovey so I could wipe all and reflash again just in case. Well, TWRP asked me for a password. Ive never encrypted my tablet nor have I used passwrods in the past as I know they can cause issues with access or permissions. I can hit cancel and use twrp but it wont mount anything or allow me to do anything until I 'decrypt' it. Not sure where to go from here. I guess Id like to flash the new official 4.2 from asus but I need advice on how to do this using fastboot.
Any help or pointers are welcomed. I only used the fastboot once to install twrp so I dont completely remember how to use it or if I can use it to flash a full ROM to hopefully reset the tablet. Thanks for any help! Cause I am stumped...
EDIT:
So I tried to turn off the tablet and pressed VOL DN + PWR to get to recovery options and choose fastboot, it just boot loops back to the asus logo twice then goes back in to TWRP. I cant even get into the OS now like I could. I need to unlock TWRP. PLEASE HELP!
EDIT 2:
I just wanted to add that by no means am I putting any blame on the ROM. Its a badass ROM that I love. The issue I am having is most definitely due to the bootloader and TWRP I suspect. I just dont know what I can do in TWRP locked down the way it is to regain some control...or at least fastboot.
Click to expand...
Click to collapse
It sounds like you flashed the 4.2 update, as that has a new bootloader which causes the behavior you describe. Did you update it to 4.2 before flashing? If so, then check the threads associated with rooting/recovery with 4.2. Basically, you need to install a patched TWRP 2.4.4.0.
jimpmc said:
It sounds like you flashed the 4.2 update, as that has a new bootloader which causes the behavior you describe. Did you update it to 4.2 before flashing? If so, then check the threads associated with rooting/recovery with 4.2. Basically, you need to install a patched TWRP 2.4.4.0.
Click to expand...
Click to collapse
Hey thanks for the reply! Actually, no I was not installing 4.2. I would like to install a newer version of twrp but I cant do anything in twrp because it says its encrypted. I did read that other thread but all the options given are not available to me. I cant get to fastboot.
BUT heres an update:
I got the PC to recognize my device as a Transformer. But I couldn't get the naked drivers nor the newer Asus drivers to work. So I modified the .ini file for both the MTP install and USB driver install to include the Hardware ID shown in windows under device manager properties for the device. Basically I modded the .ini so that it also looks for the device ID, then saved and had windows look at the folder I gain to install the driver and this time is installed. So now I am going to try to use a fastboot command....Ill update if this works. Otherwise I may need to try adb and Im a total newb at adb...
UPDATE:
Got the driver installed but 2 issues:
1: Device manager says Device Cannot Start
2: I cant get recovery menu to show. Tablet goes right into TWRP recovery after looping through the ASUS boot screen twice.
I am stumped. I don't want to give up but I think I may have to
UPDATE
Just an update for those who were following:
I can boot into APX but since I never loaded NVFLASH I was screwed. Nothing I did to try to force it into download mode worked. Bootloader must be screwed. In any case, I went on ebay and bought a TF300T mainboard that was pulled from a damaged screen unit. It was 80 bukcs and should be here soon. I figure 80 bucks is better that 180 from ASUS or drop another 300-400 on a new tablet. I wish there was a JIG for the tablet. I used it on a SG SII once.
cubaniche1 said:
Just an update for those who were following:
I can boot into APX but since I never loaded NVFLASH I was screwed. Nothing I did to try to force it into download mode worked. Bootloader must be screwed. In any case, I went on ebay and bought a TF300T mainboard that was pulled from a damaged screen unit. It was 80 bukcs and should be here soon. I figure 80 bucks is better that 180 from ASUS or drop another 300-400 on a new tablet. I wish there was a JIG for the tablet. I used it on a SG SII once.
Click to expand...
Click to collapse
300-400? buy nexus10 for strong cpu and gpu. and retina display. asus build quality very bad. And support only need money.
chanhny said:
300-400? buy nexus10 for strong cpu and gpu. and retina display. asus build quality very bad. And support only need money.
Click to expand...
Click to collapse
Nexus 10 has it's drawbacks too, I love my TF300T.
UPDATE:
Installed new mainboard and got her back up and running quickly. Already updated to 4.2.1. I like it. Well done ASUS!
chanhny said:
300-400? buy nexus10 for strong cpu and gpu. and retina display. asus build quality very bad. And support only need money.
Click to expand...
Click to collapse
Lol. I love my TF300T. Sure, i can buy a better tablet but I would also have to spend a lot more money. I've only got $299 invested in my 32gb tablet plus $49 in my dock. I'm a happy camper. My tablet , when connected to the dock, will last almost twice as long as the Nexus on one charge. I can also keep using the tablet while the dock is charging. I really never even need to put the tablet itself into the charger. You can't do that with the more expensive Nexus 10.
Sent from my ASUS Transformer Pad TF300T using Tapatalk HD
This feature is one of the reasons I love this tab. I'm having the same problem as op. I can still get into my 4.2 is though but cannot get recovery to read anything. Maybe ill have to wait for a twrp update.
For now as long as the tab works I can deal with it. I would like to get it working the right way again though.
Sent from my ASUS Transformer Pad TF300T using xda app-developers app
klownin5643 said:
This feature is one of the reasons I love this tab. I'm having the same problem as op. I can still get into my 4.2 is though but cannot get recovery to read anything. Maybe ill have to wait for a twrp update.
For now as long as the tab works I can deal with it. I would like to get it working the right way again though.
Sent from my ASUS Transformer Pad TF300T using xda app-developers app
Click to expand...
Click to collapse
Have you added the patch yet? This will allow TWRP to pick up your sd card.
I tried flashing the patched one via fastboot but it did not seem to take. Its still encrypted. I'm thinking its not flashing properly. I'm not the only one having this issue. Hopefully I can just wait it out till a fix is found. I'm afriad of screwing it up to where its completely unuseable.
Sent from my ASUS Transformer Pad TF300T using xda app-developers 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
Hey guys!
Was trying to solve the restart loop problem by installing a MIUI rom, but I am now stuck on this screen that says..
Stuck on AP Fastboot Flash Mode (S) (Boot Failure)
Battery OK
OK to Program
Transfer Mode:
USB Connected
Invalid CG OTV(CG: webtop): Invalid SP Data
Invalid CG Version (CG: webtop)
Invalid CG OTV (CG: webtop)
Any thoughts or help would be highly appreciated
Did you find the proper fxz for your base firmware and flash it?
Need more info about where you are coming from, what you did to get this problem, and what you have tried..
Sent from my MB865 using xda app-developers app
I am not sure what fxz is...but from what I know, it was on 2.3.6 and next update was failing and it was restarting..so I rooted the phone, installed the bootstrap...tried installing miui from there.. it restarted and now I am on that screen...
Have not tried anything else after that... I was looking around and it seems, I should flash something from fastboot mode? I am currenty downloading the ics fastboot files... planing to use RSD lite to install it...
Is that right approach?
Thanks for your help through...much appreciated.
EDIT: Its an AT&T Atrix 2 if that helps..
So, you were on 2.3.6? The 4.0.4 update failed?
If so, then you should probably be using the 2.3.6 fxz/sbf/fastboot/firmware files - flash those to go back to stock GB, then ota update to ICS the normal way (unless returning to GB is important to you - if so, find ICS leak #1 and install that instead of the ota update after restoring stock 2.3.6).
And yea, you need to be on ICS base to install miui (unless there's a GB version I didn't know about).
Sent from my MB865 using xda app-developers app
Edit: you seen this thread? http://forum.xda-developers.com/showthread.php?p=32113181
Links to the att-us 2.3.6 and 4.0.4 fastboot files are there.. Just read carefully and ask if you're not sure.
It's important to know if you were on 2.3.6 or 4.0.4.. and if you just tried to install a new ROM (system only) through custom recovery, or if you flashed something else through fastboot.
I was surely on 2.3.6, but it was not stable and was rebooting quite often ...it was also trying to download the next update, each time the phone was on...but it would just restart before the download could ever finish...
I rooted the phone after that, installed bootstrap.apk to get into clockwork recovery, then tried installing the MIUI which was based on 4.xx something .... but that failed and I got stuck in that screen....
So, basically, I should download AT&T 2.3.6
http://sbf.droid-developers.org/edison/InlineFlashing_edison_5.5.175.25_cfc_p3_APBP.xml.zip
use fastboot and follow these steps?
Fastboot erase system
Fastboot erase userdata
Fastboot update romfilename.zip
Fastboot reboot
OR
Try to use RSD lite instead?
One more problem though...I tried using the fastboot erase system command...and it tells me Battery low...
I have the phone on charger now, but the Fastboot screen comes up again and I am not sure if it will charge this way?
Any thoughts?
Thanks in advance.
You need to charge somehow (wall charger, macgyver method, another battery, friend's phone, at&t store, etc).. It doesn't charge in fastboot mode.
Then try RSD lite..
Otherwise, you would need to use moto-fastboot commands. See the files in the zip package here for examples (you can look at the .bat files for the proper commands): http://forum.xda-developers.com/showpost.php?p=36834775&postcount=108
Sent from my MB865 using xda app-developers app
alteredlikeness said:
You need to charge somehow (wall charger, macgyver method, another battery, friend's phone, at&t store, etc).. It doesn't charge in fastboot mode.
Then try RSD lite..
Otherwise, you would need to use moto-fastboot commands. See the files in the zip package here for examples (you can look at the .bat files for the proper commands): http://forum.xda-developers.com/showpost.php?p=36834775&postcount=108
Sent from my MB865 using xda app-developers app
Click to expand...
Click to collapse
Thanks for that, I was able to do all that and now the phone is on 2.3.6 ..but the original problem is still there...the phone keep on restarting.. any ideas what the issue might be?
jackdowsan said:
Thanks for that, I was able to do all that and now the phone is on 2.3.6 ..but the original problem is still there...the phone keep on restarting.. any ideas what the issue might be?
Click to expand...
Click to collapse
So it just reboots at random? Or it boots to Fastboot mode everytime?
If it's random reboots, you might have a hardware issue in your phone.. And you could ask AT&T for a replacement (they will most likely just give you a new Atrix HD since our A2 has been EOL'd).
If it boots straight to fastboot everytime, then there's something else.. not sure what, but I have seen others post of that issue.
alteredlikeness said:
So it just reboots at random? Or it boots to Fastboot mode everytime?
If it's random reboots, you might have a hardware issue in your phone.. And you could ask AT&T for a replacement (they will most likely just give you a new Atrix HD since our A2 has been EOL'd).
If it boots straight to fastboot everytime, then there's something else.. not sure what, but I have seen others post of that issue.
Click to expand...
Click to collapse
It reboots every 3-4 mins or so... Also noticed, it says under settings, that radio if Off and there is no IMEI number...also I cannot seem to turn off the Airplane mode..
Does that indicate something?
jackdowsan said:
It reboots every 3-4 mins or so... Also noticed, it says under settings, that radio if Off and there is no IMEI number...also I cannot seem to turn off the Airplane mode..
Does that indicate something?
Click to expand...
Click to collapse
Hmm.. Yea.. What the heck did you do to it? Did you erase your cid? Do you have a backup of it? If not, sorry to say, but you may be out of luck...
Sent from my MB865 using xda app-developers app
alteredlikeness said:
Hmm.. Yea.. What the heck did you do to it? Did you erase your cid? Do you have a backup of it? If not, sorry to say, but you may be out of luck...
Sent from my MB865 using xda app-developers app
Click to expand...
Click to collapse
I was only doing a OTA update and I ended up in this mess of reboots, then I tried installing the 4.something MIUI, then fastboot files of 2.3.6...and now in this mess
I dont have any backup files or anything...if there any way I can go to stock maybe? or maybe if I can somehow manage to go to ICS, this might be fixed? No ideas :crying:
jackdowsan said:
I was only doing a OTA update and I ended up in this mess of reboots, then I tried installing the 4.something MIUI, then fastboot files of 2.3.6...and now in this mess
I dont have any backup files or anything...if there any way I can go to stock maybe? or maybe if I can somehow manage to go to ICS, this might be fixed? No ideas :crying:
Click to expand...
Click to collapse
You did go back to stock 2.3.6 (the fxz should have flashed all stock images/files)... but if your cid is gone (not positive though that that is your problem), there's no getting it back (it is specific to each device).
You could try forcing the update to 4.0.4 by following this: http://forum.xda-developers.com/showthread.php?t=1779968 - but not sure it will install the update if it can't recognize your phone. You are sure it is an AT&T phone, right?
Unless some other members here have some ideas, not sure what else to try... except calling AT&T for a replacement if you bought it under contract. Just tell them that an over-the-air update failed and the phone keeps rebooting..
So, I wonder, did the OTA update start installing, then fail (a while after installation started)? Maybe that messed things up.. Usually, if it fails right away at the beginning of installation during the system checks, then it should be no issue.. But if it was interrupted later during the install, then that can cause major issues.
alteredlikeness said:
You did go back to stock 2.3.6 (the fxz should have flashed all stock images/files)... but if your cid is gone (not positive though that that is your problem), there's no getting it back (it is specific to each device).
You could try forcing the update to 4.0.4 by following this: http://forum.xda-developers.com/showthread.php?t=1779968 - but not sure it will install the update if it can't recognize your phone. You are sure it is an AT&T phone, right?
Unless some other members here have some ideas, not sure what else to try... except calling AT&T for a replacement if you bought it under contract. Just tell them that an over-the-air update failed and the phone keeps rebooting..
So, I wonder, did the OTA update start installing, then fail (a while after installation started)? Maybe that messed things up.. Usually, if it fails right away at the beginning of installation during the system checks, then it should be no issue.. But if it was interrupted later during the install, then that can cause major issues.
Click to expand...
Click to collapse
tried updating to 4.0.4 but it fails ...I have attached the screenshot.. what can this be?