Like an idiot i thought it would be a good idea to format my system. Well, now no OS is detected and backups gone. I still have access to TWRP and files are still on my touchpad (weird?), but when i go to flash a rom, it starts to flash, then goes blank, then reboots into TWRP. I cannot get an OS to install. Also, i've tried to boot into WebOS and it just stays at the glowing HP logo.
I was going to try Acmeinstaller3, but every single link in the known universe seems to be down. I have no clue how to restore my system. Ive also never used ADB either. Please help.
Most links point to goo.im which is being rebuilt at this time. Try this one //d-h.st/eFr
Well regardless if goo is being rebuilt...how would I exactly go about getting an OS back?
Sent from my SAMSUNG-SGH-I317 using Tapatalk 4
That link was for Acmeinstaller3
does anyone have a valid link for the acme uninstaller
How about this one http://www.mediafire.com/?cmmw89di1q7bsps
I webOS doctored it...got webOS functioning and booting. However, I've tried countless times to get Android back on and it keeps erroring and says no OS found. Btw, I have a cm rom file loaded on the TP and im using the ADB method to push the stuff. Nothing works. Any other ideas? Ive since purchased a note 10.1, so its not critical...But I would like to get Android back on it.
Sent from my GT-N8013 using Tapatalk 4
Anyone?
Sent from my SAMSUNG-SGH-I317 using Tapatalk 4
Related
I was playing in TWRP, thinking that clearing the touchpad of everything would still leave TWRP. Turns out, TWRPcan delete itself, and I have a brick for a tablet. Is there any way to fix this? The tablet turns on to the CM9 splash screen and hangs for hours. Otherwise, there is literally no OS on here. What can I do?? Trying webos doctor as we speak with no luck- it won't recognize on the computer.
Have u tried rebooting to recovery mode and running the doctor?
Sent from my ss_tenderloin using Tapatalk HD
Yes i am not a noob so feel like a real dork. Here goes. 2 weeks ago I had the latest CyanogenMod and Web OS on my touchpad using moboot . While using TWRP I accidentally erased the whole SD card now all I have is team win and it instantly boots in this I need your mind because it's not there it just sits on the little CyanogenMod word. And goes nowhere.i can get into TWRP using button combos(forgot which lol) .my question is....where do i go from here.all i want is android so if someone can tell me how to install it using twrp (remember its still there,moboot isnt)and how to get to TWRP again IT would be Greatly appreciated. Thanx
Update....after long pressing power+home takes me into moboot 0.3.5.......what do i do from here to hook to puter to install androit....choices
Boot webos(which i think is gone lol)
Boot twrp
Boot cyanogenMod which is gone
Boot web OS recovery(have never tried)
Thanx
Sent from my Galaxy Nexus using xda premium
Crwolv said:
Yes i am not a noob so feel like a real dork. Here goes. 2 weeks ago I had the latest CyanogenMod and Web OS on my touchpad using moboot . While using TWRP I accidentally erased the whole SD card now all I have is team win and it instantly boots in this I need your mind because it's not there it just sits on the little CyanogenMod word. And goes nowhere.i can get into TWRP using button combos(forgot which lol) .my question is....where do i go from here.all i want is android so if someone can tell me how to install it using twrp (remember its still there,moboot isnt)and how to get to TWRP again IT would be Greatly appreciated. Thanx
Update....after long pressing power+home takes me into moboot 0.3.5.......what do i do from here to hook to puter to install androit....choices
Boot webos(which i think is gone lol)
Boot twrp
Boot cyanogenMod which is gone
Boot web OS recovery(have never tried)
Thanx
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
If I understand correctly, you not only wiped the sdcard but also the system and maybe even the data partitions (I'm guessing this because you said you can't boot into CM). In that case, use ACMEInstaller3. RolandDeschain has a very good guide for this here: http://forum.xda-developers.com/showthread.php?t=2147284.
Oh, and if moboot wasn't working I don't think you'd be booting into recovery. So moboot should still be there and working fine.
EDIT: alternatively, if by wiping the whole sdcard you meant just the tablet's memory and your sdcard data (with the ROM zip) is still there, then just flash that from TWRP.
bananagranola said:
If I understand correctly, you not only wiped the sdcard but also the system and maybe even the data partitions (I'm guessing this because you said you can't boot into CM). In that case, use ACMEInstaller3. RolandDeschain has a very good guide for this here: http://forum.xda-developers.com/showthread.php?t=2147284.
Oh, and if moboot wasn't working I don't think you'd be booting into recovery. So moboot should still be there and working fine.
EDIT: alternatively, if by wiping the whole sdcard you meant just the tablet's memory and your sdcard data (with the ROM zip) is still there, then just flash that from TWRP.
Click to expand...
Click to collapse
Ya my dumb arse erased everything. Yes moboot is still there and some stuff I don't understand.I also found a self installer.THANK you very much form your help especially after the misunderstanding. Very couth of you God bless ya
almost
Crwolv said:
Ya my dumb arse erased everything. Yes moboot is still there and some stuff I don't understand.I also found a self installer.THANK you very much form your help especially after the misunderstanding. Very couth of you God bless ya
Click to expand...
Click to collapse
Almost there. WebOS doctor just reinstalled and on HP boot screen for about 8 min now.will update and thanx for the help.and messages
Ok so I have an Atrix HD that I rooted then went to install paranoid android on here. I made the mistake to try and install using Factory Recovery. So it threw an error in Fastboot. I used Myth Tools to get it back to stock. Then used Myth to install CWM Root it and unlock bootloader. Then went to install paranoid android again... Everything seemed to be going well but it just stayed on the Glowing X for 10-15 minutes. Knew something was up with it not loading into OS by then. So I tried to reinstall it again. No luck. Tried to use Myth Tools to go back to factory. Would just stay at Dual Core logo and do nothing. I went back in and installed CWM and tried to install Pacman Rom and it just stays at Pac is loading.
Fastboot still shows Bootloader as unlocked as it should, but is this the reason why Myth could not get me back to factory? I just want to get it back to factory at this point and worry about Rooting and installing Rom later. I have been searching and trying anything I can find on here, and droid razr forum. As well as various other sites and artices i find from google. I am at a lose. Have I bricked it enough to not come back from this or am I just missing something simple? I am looking for insight or help to get me in the right direction. I am on day 3 now off trying to get it running again.
I have tried in CWM formating Cache and re mounting it in Advance, Also have tried formating system, cache, davik cache... I did receive the can not mount errors but having formatting cache and remounting i did not get the error again.
Just take it a step at a time. Get it booted into stock first.
Sent from my MB886 using xda premium
darknessrise1234 said:
Just take it a step at a time. Get it booted into stock first.
Sent from my MB886 using xda premium
Click to expand...
Click to collapse
but where to begin? Trying to get it back to stock is not working even though Myth Tools. It states it finished I do not get any errors through Fastboot yet it stays on Dual Core never moves as if it is bricked.
DeVoe41 said:
but where to begin? Trying to get it back to stock is not working even though Myth Tools. It states it finished I do not get any errors through Fastboot yet it stays on Dual Core never moves as if it is bricked.
Click to expand...
Click to collapse
read this
http://forum.xda-developers.com/showthread.php?t=2226527
Make sure you have the adb drivers installed on your computer and I've noticed this phone is weird about chargers find one that works for data too. U will know cause if you have adb installed through myth tools and you reboot into fastboot mode then your computer will recognize it. Make sure the only thing in the firmware folder in myth tools is your .zip whatever stock att firmware you want. Then in myth tools install stock and make sure you type in the response 2 when it asks if you are in fastboot mode or normal. Fastboot is choice 2. I'm a flashaholic I've tried every rom in our development forum lol. I have bricked my AHD more times then anyone should this always worked for me. Try these things see if they help
Sent from my MB886 using xda app-developers app
Clean Flash
DeVoe41 said:
Ok so I have an Atrix HD that I rooted then went to install paranoid android on here. I made the mistake to try and install using Factory Recovery. So it threw an error in Fastboot. I used Myth Tools to get it back to stock. Then used Myth to install CWM Root it and unlock bootloader. Then went to install paranoid android again... Everything seemed to be going well but it just stayed on the Glowing X for 10-15 minutes. Knew something was up with it not loading into OS by then. So I tried to reinstall it again. No luck. Tried to use Myth Tools to go back to factory. Would just stay at Dual Core logo and do nothing. I went back in and installed CWM and tried to install Pacman Rom and it just stays at Pac is loading.
Fastboot still shows Bootloader as unlocked as it should, but is this the reason why Myth could not get me back to factory? I just want to get it back to factory at this point and worry about Rooting and installing Rom later. I have been searching and trying anything I can find on here, and droid razr forum. As well as various other sites and artices i find from google. I am at a lose. Have I bricked it enough to not come back from this or am I just missing something simple? I am looking for insight or help to get me in the right direction. I am on day 3 now off trying to get it running again.
I have tried in CWM formating Cache and re mounting it in Advance, Also have tried formating system, cache, davik cache... I did receive the can not mount errors but having formatting cache and remounting i did not get the error again.
Click to expand...
Click to collapse
I have a suspicion that for some odd reason, as Mythtools probably should have taken care of this, that there are some lingering files and caches that would cause any rom to fail upon install. I just posted something about this earlier today.
Read my post on this thread:
http://forum.xda-developers.com/showthread.php?t=2394238
PM me with any questions or problems and click the Thanks button if I helped.
I'm sorry I forgot to update I was able to get the phone working just had to do it through command prompt forcing you to file . The issue I had was using safestrap to install a ROM which somehow killed root access and the bootloader was not unlocked so and pretty much bricked the phone.
Sent from my MB886 using xda app-developers app
For recent custom roms, you must use a CWM with an unlocked bootloader.
So i got a new lg g2 for verizon last week. ive had good experiences with cyanomod and other roms so i figured off the bat that i would install one of these. turns out they were alot more problems than it was worth. so i went back to stock rom and rooted. for some reason i took OTA. now phone is stuck in fastboot. so i went through this thread http://forum.xda-developers.com/showthread.php?t=2582142. so i got everything done and figured out (running live ubuntu so getting automount to stop was a challenge and then figuring out the new file paths). so now i reboot phone and try to get into twrp (from complete power off hold power button and volume down, release when logo shows and press again). so i get the "do you want factory reset" screen and i click yes, yes then it just goes into fast boot again. problem is now not even linux is reconizing the device. device doesnt go into twrp. cant get into download mode to reflash. all i got is "[16370]fastboot mode started [16420]udc_start() [16590]-reset- [1660]-portcharge- [16640] fastboot: processing commands.
do i have any hope? the phone is new from a third party so i dont think i have a chance to return to the seller, and im not sure if lg will take it either
added info
also, just read and possibly part of problem, twrp was 2.7.1.0, either way though im still stuck with it at this point
ok, so just a bit more info. now when the phone is plugged into windows 7 computer it automatically installed a driver "USB Movem Phone ADB port". so i figured id try to run adb devices and see if it showed, no luck. dont know if this puts me in a different situation or not...
Did you try via terminal $ reboot-bootloader you may be able to force into bootloader for adb sideload twrp 2.7.0.0
Sent from my VS980 4G using XDA Premium 4 mobile app
---------- Post added at 09:12 PM ---------- Previous post was at 09:03 PM ----------
Adb and fastboot are two different programs. If your in fastboot mode computer won't recognize adb devices. While in fastboot mode, reboot-bootloader then see if you can get adb through toggling vol + or -
Sent from my VS980 4G using XDA Premium 4 mobile app
actually i just got a step farther.... now i have twrp installed and working (turns out version 2.7.1.0 and 2.7.0.0 both didnt work with my phone even though i specifically got the versions for my phone. now im using 2.6.3.2 in case anyone else is having issues).
so twrp is on the phone. by random luck i apparently had all the rom zips left on the SD card. so i was able to flash a known working rom (at least it was working well enough to get by...). so i flashed the rom and rebooted the phone. unfortunatly it went straight back into twrp. i dont know if there is a flag i havent set or what. i thought i saw a walkthrough about what to do at this point, so im still working on it and i will update if i can fix it... but as i stated right now have twrp 2.6.3.2 working, still no download mode apparently(ill mess with this more because originally this is how i was flashing back to stock when things went wrong), and even though twrp installed a known working rom its still booting straight into twrp (without the whole power and volume down seqeunce...)
Some ROMs won't work on 2.6.3.2
Sent from my VS980 4G using XDA Premium 4 mobile app
would it automatically go to twrp if the rom didnt work? the reason im asking is because when i was messing around with the roms throughout the week some of them didnt work (either black screen at boot, or bootloop with logo). and i would have to manually shut the phone off, then go through factory reset, then it would turn on twrp. right now the phone just turns on and goes straight to twrp
If recovery doesn't detect a compatible ROM it bootloops. That or corrupt download itself, make sure to verify md5s whenever possible.
Sent from my VS980 4G using XDA Premium 4 mobile app
YAY, got it mostly back kinda sorta. so i followed this http://forum.xda-developers.com/showthread.php?t=2451696 after getting back into twrp. i dont know what this did or if it helped. then i flashed a new rom (which i also by chance had on the SD already) i believe it was malladus 1.2.9 and it worked (except i didnt put gapps or anything so it was having a fit about play... now its restarted and i have download mode back so ill just flash the whole thing with the regular rom (the rom on this website might even be older than the phone, but for me it worked well...). here is that website i case anyone needs it http://www.lg-phones.org/guide-to-flash-restore-unbirck-verizon-lg-g2.html i will reflash and post results, hopefully a bone stock phone to start over with...
glenn3451 said:
would it automatically go to twrp if the rom didnt work? the reason im asking is because when i was messing around with the roms throughout the week some of them didnt work (either black screen at boot, or bootloop with logo). and i would have to manually shut the phone off, then go through factory reset, then it would turn on twrp. right now the phone just turns on and goes straight to twrp
Click to expand...
Click to collapse
As far as a straight to recovery, I haven't had that problem on my g2. On my tablet,I run multi ROM recovery and it will go straight to recovery if a ROM is not installed. I would think it would do the same on vs980 twrp.
Sent from my VS980 4G using XDA Premium 4 mobile app
btw thankyou for suggesting a different rom, wouldve probably been stuck for awhile without that advice. so flashed verizon stock firmware(which also deletes everything) and its 100% running with the exception of the activation (switched back to old phone while working on getting this guy running again). i feel like ive learned alot more than i ever wanted so ill stay subscribed to this thread and if anyone has similar issues when you post hopefully ill be able to help alittle... no promises though
okay, i had a slim rom running on my fire (5.1.1) and tried to go to cm12 using flashfire. i made sure that wipe was at the top of the list. it got stuck on installing the new rom, so after 30 minutes i restarted tablet. i got stuck in the cm logo bootloop. i do still have access to the amazon stock recovery. tried to do a data wipe/factory reset. still stuck at logo bootloop. i tried to sideload the amazon stock bin file, but it stops after 5 seconds and says "failed to read command: invalid argument" and goes back to the recovery main menu. if you try to do another sideload, it instantly says "timed out waiting for package. installation aborted" before you even press anything. have to restart device to try sideloading again.
at one point i had it almost install cm12 from a zip file through sideload, but at the very end it gave me a signature verification fail. since i can't boot the phone, i can't turn on usb debugging. sometimes it'll show up in the device manager as mtp but never shows up as fire or android device or any of that. it will show up on adb devices command when its in fastboot, but can't do anything with it from there. i've tried all the different ways in the forums here and rootjunky, but nothing seems to work at all. any ideas if i'm doing something wrong or is this just bricked, regardless of stock recovery?
tried a few commands to see if i could fastboot one of the roms or stock images, but they all tell me its missing the android-info.txt
dorkydroid said:
okay, i had a slim rom running on my fire (5.1.1) and tried to go to cm12 using flashfire. i made sure that wipe was at the top of the list. it got stuck on installing the new rom, so after 30 minutes i restarted tablet. i got stuck in the cm logo bootloop. i do still have access to the amazon stock recovery. tried to do a data wipe/factory reset. still stuck at logo bootloop. i tried to sideload the amazon stock bin file, but it stops after 5 seconds and says "failed to read command: invalid argument" and goes back to the recovery main menu. if you try to do another sideload, it instantly says "timed out waiting for package. installation aborted" before you even press anything. have to restart device to try sideloading again.
at one point i had it almost install cm12 from a zip file through sideload, but at the very end it gave me a signature verification fail. since i can't boot the phone, i can't turn on usb debugging. sometimes it'll show up in the device manager as mtp but never shows up as fire or android device or any of that. it will show up on adb devices command when its in fastboot, but can't do anything with it from there. i've tried all the different ways in the forums here and rootjunky, but nothing seems to work at all. any ideas if i'm doing something wrong or is this just bricked, regardless of stock recovery?
tried a few commands to see if i could fastboot one of the roms or stock images, but they all tell me its missing the android-info.txt
Click to expand...
Click to collapse
try stock 5.1.2 firmware
otherwise there is no fix that I know of
Sent from my KFFOWI using XDA Labs
i started trying to get it going, but got the same results. eventually the battery died and it doesn't want to charge anymore, so hopefully i'm still under warranty. thanks for all the help though, been a reader here for a really long time. just sucks to get a hard brick for the first time. used a droid x for four years straight with a locked bootloader and never came across a problem like this
dorkydroid said:
i started trying to get it going, but got the same results. eventually the battery died and it doesn't want to charge anymore, so hopefully i'm still under warranty. thanks for all the help though, been a reader here for a really long time. just sucks to get a hard brick for the first time. used a droid x for four years straight with a locked bootloader and never came across a problem like this
Click to expand...
Click to collapse
I fear I'm in the same boat. Which version of flash fire were you using?
Any further progress?
Sent from my Nexus 7 using XDA-Developers mobile app