Related
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?
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.
here is my issue.
2 weeks ago, i rooted my phone. all was well. flashed CWM Recovery 5.0.2.1 for my Thunderbolt. I made a backup just before i rooted so that in case ANYTHING went wrong, it would unroot me and fix any problems. So, here i am, backing up apps with Titanium Backup, and it backed up fine. The next thing i did was start to uninstall HTC Bloatware... I knew which ones were the ones i could remove, plus even if i removed the wrong one, i could just restore using my image backup. After removal, the phone instantly ran better. i had over 65% free memory space... This was all well and good, until i rebooted the phone. the instant i rebooted my phone, i was getting the flashing HTC Quietly Brilliant screen. i had done NOTHING to it to cause this. It would alternate from HTC splash to Thunderbolt animation.
So, knowing what was wrong, (UI not loading) i went to recover my image from CWM. that went fine. but things just got worse. After a successful recovery (according to CWM) i rebooted, but to my surprise, now its worse. its stuck at the HTC boot logo. ALL MANNER OF ROMS DO NOT WORK!!! recoveries, new OS, anything, all the same result. AT LEAST with the thunderstick full blown ROM, i can get back to the looping splash screen, but not any further. i DONT KNOW what is wrong but i am hoping one of you mad phone geniuses out there can get my phone working. i tried getting s-off with revolutionary, but it failed because the phone has to be booted up for it to work, and is something i obviously cant do at this point... relocking the phone made things worse too because i unlocked using the HTCdev method.
This is not a boot loop, as it doesnt loop. it just sits there. i have tried every available resource on this, and other sites. i must have read over 1,000 posts in the past week to try and gather what the devil happened to my phone... If its any help, i did accidently delete the settings storage APK file, but a restore should have fixed that. i want to lock up the phone to send it in for repair but i cant gain s-off to flash a new radio with the phone in its current state. i know how to do all if these things but the phone wont let me.
Reformat the sd card to fat32 and flash an RUU file to put you back to stock.
Sent from my ADR6400L using xda premium
Does your computer recognize your device?
Sent from my ADR6400L using xda app-developers app
i am nearly pulling my hair out...
smtom said:
Reformat the sd card to fat32 and flash an RUU file to put you back to stock.
Sent from my ADR6400L using xda premium
Click to expand...
Click to collapse
any RUU downloads that would have been available on multiupload.com are disabled and redirects to to "the internet vs., holywood". besides, as i said, any attempt to flash any rom no matter what it is fails. Well, technically it FLASHES ok, but doesnt actually work. as far as i know, the phone has 2 bootloaders in any given android phone. There is the primary HTC Bootloader (Hboot) and a secondary ROM UI Bootloader. (Android Boot) i think what has happened is that this part has become corrupted and i wanted to know how to access this and reformat that. supposedly you cant because its partitioned, and formatting the partitions would fix my issue. problem is that i have done all of this. to answer the second reply, yes, i can get the phone to be recognized in any mode as long as its fastboot, or recovery. Fastboot.exe works, and adb recognizes it in recovery as being IN recovery mode. unfortunately, with my device still locked, i cannot flash a new bootloader, which might solve my problem. this is not like any issue currently on XDA so far as i read, so this is why i created a new thread.
I am sure the Moderators will agree that my problem seems to be unique. After reading what seems to be hundreds of forums, i cannot solve the issue. While technically i am a newbie here, i am no stranger to modding phones. i have been at it for over 4 years now. THIS problem is absolutely a first for me. At least before i could restore using CWM, but even that failed. i checked my MD5 Sum for CWM backup and it checked out.
If someone can provide me a link to an ORIGINAL, unmodded, RUU that shipped with the phone, (PRE OTA 2012) that ISNT that stupid file-factory corrupted crap, i would be extremely indebted to that person. last time i used File-factory, it took THREE hours and the download was corrupted according to CWM. it refused to flash the phone even though Chrome said it completely downloaded (Error: Bad - Installation Aborted). There was no MD5 SUM to compare with so thats also another problem. i absolutely need that info to properly flash the phone. All the other ROMS i downloaded like TSGB and Lightning Rom technically flashed fine after a full wipe, but refused to go past their own "Open Mobile" splash screen.
So you see, i am at a loss with this phone, as all i did was reboot after rooting it, and nothing i did could have possibly caused this kind of failure...
cyberkeeper1 said:
any RUU downloads that would have been available on multiupload.com are disabled and redirects to to "the internet vs., holywood". besides, as i said, any attempt to flash any rom no matter what it is fails. Well, technically it FLASHES ok, but doesnt actually work. as far as i know, the phone has 2 bootloaders in any given android phone. There is the primary HTC Bootloader (Hboot) and a secondary ROM UI Bootloader. (Android Boot) i think what has happened is that this part has become corrupted and i wanted to know how to access this and reformat that. supposedly you cant because its partitioned, and formatting the partitions would fix my issue. problem is that i have done all of this. to answer the second reply, yes, i can get the phone to be recognized in any mode as long as its fastboot, or recovery. Fastboot.exe works, and adb recognizes it in recovery as being IN recovery mode. unfortunately, with my device still locked, i cannot flash a new bootloader, which might solve my problem. this is not like any issue currently on XDA so far as i read, so this is why i created a new thread.
I am sure the Moderators will agree that my problem seems to be unique. After reading what seems to be hundreds of forums, i cannot solve the issue. While technically i am a newbie here, i am no stranger to modding phones. i have been at it for over 4 years now. THIS problem is absolutely a first for me. At least before i could restore using CWM, but even that failed. i checked my MD5 Sum for CWM backup and it checked out.
If someone can provide me a link to an ORIGINAL, unmodded, RUU that shipped with the phone, (PRE OTA 2012) that ISNT that stupid file-factory corrupted crap, i would be extremely indebted to that person. last time i used File-factory, it took THREE hours and the download was corrupted according to CWM. it refused to flash the phone even though Chrome said it completely downloaded (Error: Bad - Installation Aborted). There was no MD5 SUM to compare with so thats also another problem. i absolutely need that info to properly flash the phone. All the other ROMS i downloaded like TSGB and Lightning Rom technically flashed fine after a full wipe, but refused to go past their own "Open Mobile" splash screen.
So you see, i am at a loss with this phone, as all i did was reboot after rooting it, and nothing i did could have possibly caused this kind of failure...
Click to expand...
Click to collapse
https://dl.dropbox.com/u/61129367/Stock-ROM.zip
013CBDD3A9B28BC894631008FA2148E2
will this really work??!? lol
trter10 said:
https://dl.dropbox.com/u/61129367/Stock-ROM.zip
013CBDD3A9B28BC894631008FA2148E2
Click to expand...
Click to collapse
If this works, i will be forever grateful. and something that mere Custom ROMS wont do, is repair any boot issues and lock up my phone again right? i hope at least it fixes the issue.
new problem... i think...
cyberkeeper1 said:
If this works, i will be forever grateful. and something that mere Custom ROMS wont do, is repair any boot issues and lock up my phone again right? i hope at least it fixes the issue.
Click to expand...
Click to collapse
ok. so the download finished fine so far as i know, but now CWM says ITS bad too. i will try again but i cant seem to flash any stock rom no matter if its OTA or pre-OTA from CWM. is there a way to flash a rom from the PC via adb or something?
Ohh! They're not flashed through CWM. They're flashed through hboot. Just rename it to PG05IMG.zip and put on SD card and boot to hboot it will ask you to flash
Sent from my ADR6400L using Tapatalk 2
i will try that. previous hboot flashes always fail. it reads the archive, but never goes to "checking zip". it loads, checks, and then parses. i was successful with my evo shift earlier today, but that thing is ancient compared to my thunderbolt. With the Shift, i was able to gain root AND s-off with an old bootloader and i dont even need a new one.
i wanted to do the same with my bootloader in case another disaster hits because then i can flash whatever RUU i want with s-off. i will make sure the MD5 SUM matches before flashing. i forgot to do that anyhow.
Hboot flash failed. went through the motions of scanning it and it scanned the whole thing and then did nothing. it returned me to Boot Choices. Like Fastboot, recovery, etc... i tried twice. are you absolutely certain that is the shipping firmware that formats the entire phone, and not just updates it? i cant send it to verizon even though they know it was illegal to lock up my phone... Anyhow, i realy need this thing working and i have racked my brain enough to damage it already... lol. if it fails again i will try to redownload it. So far it loads and does NOT ask me to start the update. could be a version issue because it does not complain about anything else.
Have you tried following the instructions in the return to stock thread in the android development section stickies? This may help you.
Sent from my ADR6400L using xda app-developers app
lemew said:
Have you tried following the instructions in the return to stock thread in the android development section stickies? This may help you.
Sent from my ADR6400L using xda app-developers app
Click to expand...
Click to collapse
yes i have. i cannot do what it asks because it requires my phone to be functional to flash it using hboot. i need a signed copy of an older RUU. hboot doesnt do anything with it. its a valid copy, and i can see all the images and contents in windows and linux, but all i can get hboot to do is read it, then it doesnt ask me to update. i dont know what to do now.
I believe there is a ruu image without hoot download there.
Sent from my ADR6400L using xda app-developers app
---------- Post added at 06:39 PM ---------- Previous post was at 06:34 PM ----------
Try http://shipped-roms.com/index.php?category=android&model=Mecha
Sent from my ADR6400L using xda app-developers app
ok well i will literally try ALL of the signed images. i will see if hboot will update it.
If your hboot is flashed with revolutionary I believe you have to unlock it before anything thing else can be flashed over that. Hboot or emmc could be corrupted as well.
Sent from my ADR6400L using xda app-developers app
How i fixed my tbolt stuck at the white HTC screen
I had this exact same problem literally yesterday (stuck at HTC screen) with some different cwm symptoms. I'm guessing my cwm was corrupted because the phone would reboot after about 30 seconds being in cwm, preventing me from flashing any roms. oh, and my backup image was corrupted as well. awesome. Flashing other CWMs did not fix the CWM problem.
Your problem sounds similar in the fact the CWM won't flash properly. You're trying to fix it by trying to flash a rom in HBOOT that isn't configured to be flashed that way. for example, i put the skyraider rom (named properly) in the root folder and tried to flash with HBOOT. it scanned and parsed but didn't give me the option to flash.
What I did was go here and grab a stock like image:
androidforums.com/thunderbolt-all-things-root/418539-thunderbolt-root-unroot-thread.html
(won't let me make a link, i'm too new)
Go to the "Putting current stock firmware and s-on back onto the phone" section.
Download file 1 and flash it using HBOOT. I had to pull my sd card to get the file on there since cwm was crashing. Only flash that rom and nothing else. It flashed for me; if it doesn't flash for you then maybe your HBOOT is corrupted, and if so i don't know if you can fix it.
Once that flashes, reboot the phone and it should return to some level of functionality. You'll have S-off but no recovery or root tools installed. I ran revolutionary at this point, which recognized i already had S-off...then it offered to load CWM. This i did. in the meantime i deleted the unrooted image and put the image of the rom i wanted on the sd card. i then booted into recovery(it won't flash in HBOOT) and loaded that rom (skyraider zeus). That worked fine and the cwm didn't crash out.
I hope this works for you. I was getting ready to fire back up my OG droid before i did this.
mpcapps said:
I had this exact same problem literally yesterday (stuck at HTC screen) with some different cwm symptoms. I'm guessing my cwm was corrupted because the phone would reboot after about 30 seconds being in cwm, preventing me from flashing any roms. oh, and my backup image was corrupted as well. awesome. Flashing other CWMs did not fix the CWM problem.
Your problem sounds similar in the fact the CWM won't flash properly. You're trying to fix it by trying to flash a rom in HBOOT that isn't configured to be flashed that way. for example, i put the skyraider rom (named properly) in the root folder and tried to flash with HBOOT. it scanned and parsed but didn't give me the option to flash.
What I did was go here and grab a stock like image:
androidforums.com/thunderbolt-all-things-root/418539-thunderbolt-root-unroot-thread.html
(won't let me make a link, i'm too new)
Go to the "Putting current stock firmware and s-on back onto the phone" section.
Download file 1 and flash it using HBOOT. I had to pull my sd card to get the file on there since cwm was crashing. Only flash that rom and nothing else. It flashed for me; if it doesn't flash for you then maybe your HBOOT is corrupted, and if so i don't know if you can fix it.
Once that flashes, reboot the phone and it should return to some level of functionality. You'll have S-off but no recovery or root tools installed. I ran revolutionary at this point, which recognized i already had S-off...then it offered to load CWM. This i did. in the meantime i deleted the unrooted image and put the image of the rom i wanted on the sd card. i then booted into recovery(it won't flash in HBOOT) and loaded that rom (skyraider zeus). That worked fine and the cwm didn't crash out.
I hope this works for you. I was getting ready to fire back up my OG droid before i did this.
Click to expand...
Click to collapse
I have read that post you provided probably 100 times its not working for me. flashing a custom rom actually got me past the HTC white screen and into a splash screen loop (Open Mobile). Also, I havent even been able to use the REV tool because my phone is not recognized by it without it being fully functional. you have to be fully booted up for the REV tool to use adb and start the process. thats why i need a signed copy of an older ROM with hboot flashing capability so i can fully restore my phone. i am 100% sure its a corruption issue, but i am out of clues as to how to actually get it to flash over while being s-on. with the evo shift it worked perfectly. it only took me 20 minutes to root, s-off and flash a custom rom. this phone has been a thorn in my side ever since i accepted that STUPID FOTA... i regret not knowing before hand what that OTA was and what it prevented. Now i know, too little / too late.
without s-off, i cant unlock hboot to flash it, and the fastboot mw whatever command failed also because its locked tight.
lemew said:
If your hboot is flashed with revolutionary I believe you have to unlock it before anything thing else can be flashed over that. Hboot or emmc could be corrupted as well.
Sent from my ADR6400L using xda app-developers app
Click to expand...
Click to collapse
thats what i thought. is there a way to change out that eMMC, or remove it to format it manually? i mean based on the description, its technically external which implies removable.
Yes you can format emmc I do not know if this will solve your problem. You wipe abd format through adb but need to see if it is being mounted first.
Sent from my ADR6400L using xda app-developers app
lemew said:
Yes you can format emmc I do not know if this will solve your problem. You wipe abd format through adb but need to see if it is being mounted first.
Sent from my ADR6400L using xda app-developers app
Click to expand...
Click to collapse
too bad i cannot repartition it to allow for more RAM instead of app space. i dont care about app space because i have a 32gb card... lol. i just want that phone to be faster than what it is currently once i finally get it running.
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
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.