[Q] Please please help this noob out! - Android Q&A, Help & Troubleshooting

As previously stated I am a complete noob when it comes to flashing android devices.
Here is the problem I am faced with: I recently rooted, and unlocked the bootloader on my atrix hd (ATT)
Since then I tried installing cm10.1 multiple times on the secondary "Rom slots" within the bootloader, without any success. So I finally decided to go for it and install cm10.1 in the "stock rom" slot, Prior to doing this I did a back-up using Rom manager. Aand now I seemingly can't even boot into recovery mode, every time I restart my device it simply goes to the cyanogenmod blue ring thingy and gets stuck! (I have left it for 15-20 mins thinking it might be some kind of installation process..) But apparently it's not and i've broken my smartphone lol. Anyway i'd really appreciate some help fixing this problem, a step-by step guide would probably work best..!!! I have both windows 8 and Ubuntu installed on my pc, just saying..Don't know if it's relevant information and may simplify fixing my problem...Thanks in advance guys and girls
i've even tried holding down all three physical buttons and it simply takes me back to the same screen!!!

you could try something like this:
http://forum.xda-developers.com/showthread.php?t=2434726
.. and you are sure, that you can not enter the recovery menu??
official motorola guide, how to enter recovery menu:
https://motorola-global-portal.custhelp.com/app/answers/detail/a_id/60620/action/auth
.. adb could be your last possibility, if everything else fails, google it, you'll find many answer

Related

[Q] cm-5.0.8-droid-fontfix-signed.zip flashed and now stuck on HTC screen

I'm a newb so please be gentle as I'm having a hard time following what folks have said elsewhere on similar issues.
I have G2 and clockwork with stock rom. The only thing I have done to the phone so far:
1. Perma-rooted it. All went well, no problems, used the phone for several days.
2. Flashed cm-5.0.8-droid-fontfix-signed.zip to try and fix terminal emulator gibberish that made perma-rooting very nerve wracking.
3. Phone will not boot up. Stuck in HTC screen. I can get to Clockwork and tried re-setting to factory default and still had same problem.
4. edit - can get to SD card through clockwork/fastboot but have no idea what to put on there to flash and fix things
I know other folks have had similar problems but the computer doesn't recognize anything on USB and I'm a beginner android-idiot. Any step-by-step help for morons would be appreciated.
**edit** Once I got into the sdcard, flashed stock rom linked elsewhere. Sorry to bother folks!
Thank you.

[Q] Recovery refuses to work

This problem probably has shown up a lot and usually I would take my time to look around before asking but I'm feeling lazy so here goes:
I recently put in a new-ish ROM (it's am US stock type ROM that I found on here) and all works well except for one thing - the CWM refuses to load. At first I was getting the dead android with the red triangle sticking out and so I decided to use ROM Manager to flash CWM again. Might have been a bad move since I'm still fairly noob-ish but anyhow it didn't work. Now whenever I try to go in it just freezes. If I try manually it shows the RCK box, android box, etc and just stays there. When I try to do it through ROM Manager it stays at the first ASUS logo. Can someone refer me to a guide I could follow or even give me a solution to fix this? I will be very grateful. Thank you in advance.

[Q] Help needed

Hello! I have tried to get help from here before but then i did not have much info about the programs i used for my phone.
Anyways, I have a LG Optumis 3D (P929). I rooted it as told, Got myself a rom ( i useClockworkmod recovery v6.0.1.9).
Restarted into recovery mod and i did wipe out data/factory resetfollowed by Cache...
Installed this famous-for-not-working-file "XBSA404.ZIP". Not only me who's getting "Installation aborted" whitout any details why.
I have also tried out "ISC 30a" wich is supposed to be the stock rom. This one works to install but nothing happends.
It says it is mounting but as the XBSA404.ZIP once it comes to install it just jumps to complete?
It seems but i dont know if iits supposed to do that? It takes around 2minutes for this to happend..
Since i tried to install a newer version of android into my phone, everything is stuck at the startup logo. "Bricked" i think is the word.
Im new within this but i try to learn. Now i just want it to start and what ever i must do to get it to work again i am happy for any help with it.
I have looked for downloads with any working ROM and on this site all the links seems not to work.
I have done this tutorial via xda forum a several times without any good resaults.
Also.. once i try to start up in recoverymod the phone jumps into my logo and freezes. I press vol- home and power, releasing once the logo appears. Dont know if its me or if its the phone thats not working. No dmg to it what so ever but i have to repeat this a several times before it comes into recovery mod.
Please help!
Did you backed up your phone's ROM?
else, I think you have to find someone that have the same phone as you are and back its ROM then use that back up ROM to your own phone
*fellow people out there correct me if i am wrong, thanks"

I'm Not Even Sure What This Is SONY XPERIA Z2 TABLET -VERIZON- POSSIBLE BRICK?

Hey guys, please forgive me for any bad etiquette or lack of information (any information I can provide is available upon request if I leave anything out). I am new to forums in general and especially to XDA, which seems like a good place to get help.
I recently purchased a Sony Xperia Z2 Tablet from Craigslist under the assumption it was a fully unlocked tablet not associated to a carrier. Turns out it was a Verizon Z2 tablet. I dislike Verizon with a firey passion and without getting into too many details, I'm fairly certain they won't help me because a) this tablet wasn't purchased through them as a customer and b) Verizon and I have bad history (unauthorized account modification, shady charges, etc.)
So I thought I'd do my best to make the tablet mine since the asshole who sold it to me has ceased all contact and I don't know how to get a hold of him anymore. No receipt and a data-less tablet.
Anyway, I successfully rooted the tablet and began installing apps that I installed for my G4 when I rooted it (SuperSU, Adaway, Greenify, etc.)
Things were going well but I realised I wanted anything that had to do with Verizon removed from the tablet so I was going to flash Cyanogenmod onto it with a guide I found online. Now rooting and installing custom recoveries was familiar territory and I did these flawlessly. It had TWRP and I made a backup of the system -no Nandroid, sadly-and I began the flashing process. The process said it completed without issue and I went to reboot my device. Enter my current situation:
The device, when I attempted to turn it on, all it did was vibrate constantly until I let go of the power button. Attempting to enter recovery mode (green LED, power + vol down) it showed me, instead of TWRP, a very basic recovery mode with basic options. "Continue booting up", "enter safe mode", "system recovery", and "power down". I tried entering safe mode and it just shut back down, I tried doing a system recovery and it shut down. The only time I ever see the "SONY" logo is if I'm entering this mode. I can enter what I assume is "fastboot mode" (power + vol up and plugging the device into a PC). Nothing on the screen but the LED is blue. I am trying to find guides to restore it if I can and it all looks promising but the only things I know how to really do are root and install custom recovery. I know there are PC tools I can use to send commands to it while it's in fastboot, or send commands in general I just don't know where to begin.
Does anyone know how to fix this? I know it was from Verizon, which sucks, and I know the problem most likely occurred with the attempted flashing of Cyanogenmod. I think I read somewhere I might have done something regarding mismatching kernal numbers. I couldn't find a way to unlock the bootloader so I assume that had something to do with it too.
If someone could give me a guide to restore it to at least its stock ROM where I can begin rooting and installing a custom recovery again, that would be great. Even better would be just flashing a ROM on there that doesn't need Verizon or being able to take it to a stage where it's unlocked and the only evidence it was ever with a carrier is the Verizon logo on the back. I'd really hate to think I wasted money on this and now I'm at a dead end because of a mistake I made. This was supposed to be a gift for my mom on her birthday which is coming up soon. So if anyone knows anything, or has a guide where we can at least get the thing bootable again and I'll just try and deal with a rooted locked device, that would be great.
Thanks for considerations,
Marmalade_Shaws
I have spent time on that screen too.
2 things
1. .. If you installed dual recovery, there is an up, down sequence to select the recovery.
2. Find a downgrade guide, use flashtool to flash. Ft back to stock.
Also you need to know what hardware you are running..511, 561.. And use the proper version.
There are some options with the flashtool and prf maker that can remove branding and vendor stuff. I have not tried those options.
Ez-go said:
I have spent time on that screen too.
2 things
1. .. If you installed dual recovery, there is an up, down sequence to select the recovery.
2. Find a downgrade guide, use flashtool to flash. Ft back to stock.
Also you need to know what hardware you are running..511, 561.. And use the proper version.
There are some options with the flashtool and prf maker that can remove branding and vendor stuff. I have not tried those options.
Click to expand...
Click to collapse
Sorry if this is late... But where can I find the stock? I've searched everywhere and I would need to do it from a flash tool on my PC? I could use all the help I can get.
I just had a very similar experience to the OP, seemingly identical in every way, and am curious if anyone has a solution.
ADB won't function at all, and the bootloader has blocked any sort of flashing via fastboot. Can't boot into TWRP, it goes into a very minimal "recovery," which I imagine is the stock tool, and the Factory Restore option there does absolutely nothing. Flashtool would work great if ADB / Flashmode was at all functional (device blinks and vibrates in a fashion typical of something bricked, and no connection is picked up).
Verizon Z2 Tablets are 561s.
This thing dead or is there some way to push back onto it?

How can I flash to CWM externally? I've softbricked my phone!

Hey lovely ladies and gents,
So here is the situation: I have an LG Optimus l70 MS323, which until yesterday was with a stock ROM. I banged my head against the wall, trying desperately to follow a guide and root it, along with trying to unlock the bootloader until I watched a video (in Spanish. Thank you high school spanish!) which used flashify to flash a CWM and boot to the custom recovery. I loved it, since that meant that I would be able to finally flash an official Cyanogenmod OS. The first ROM that I flashed was cm-13.0-20160121-NIGHTLY-w5.zip, which worked and made me feel SO HAPPY (I almost yelled Eurika for the sake of historical comedy). I then went ahead and installed an Superuser-SU binary update through the CWM recovery because I wanted to keep on having root. Then I installed a nano gapps package for ARM, Android 6.0 with some minor complications (mostly the "Setup Wizard" crashing every 2 seconds). I rewiped and reinstalled Cyanogenmod through CWM, flashed gapps on the same go, and made a little backup through the recovery menu. I booted up successfully to be met with that buttery-smooth GUI of Marshmallow (ugh, so good.) I decided to go ahead and fetch some apps from the Play Store, such as Messenger and ROM manager. I saw that the Cyanogenmod Update Center had pushed out a notification that the newest nightly snapshot is already downloaded and decided "Meh. What new features have been added? Let's reboot and reinstall." At that point it was 4:40am (keep in mind that I've been trying to get the goddamn phone to cooperate since ~10pm) and I noticed that the boot sequence takes up a lot longer and told myself "It's probably taking a bit longer than usual, it's normal." I put the phone next to my head, hoping that it's going to be ready to use in the morning.
Fast forward to 8:07 am. Bootloader is still going, phone is so hot it can cook an egg.
GNAAAAAAAAAAAAAAAAAAAHHHH. WHY YOU GOTTA DO DIS TO ME PHONE?!??! WHY!?!
SO, the CURRENT situation:
1. Whenever I press the power button, it starts off normally. According to my definition of bootloop, it's stuck in a bootloop.
After hours of staring that goddamn cyanogenmod mascot do you realize that it's going to boot itself into the booting oblivion.
2. I don't have access to CWM. I have tried holding down the power buttons with godknowswhat combinations (I like to call them the Naruto Jutsu of pure despair). Maybe I should hold the buttons for 2 milliseconds longer and it might work. *Sigh*
3. I don't think that I can use fastbood or adb. My computer doesn't see the phone. (GNAAHHAHASDJFLSKDHFSLJHLKJ.)
4. I am totally clueless about what I should do or try. I've basically softbricked my phone and don't know how to unbrick it.
So, now that you see that saying that I'm frustrated is truly an understatement, what do you suggest I do?
In advance, I'd like to thank you SO MUCH for even giving a sh!t about my problem.
Other misc info: I have a 32GB SD card on which I have all the different tools I have used throughout this journey.
I am willing to have it back on stock ROM. My biggest goal is to somehow boot into CWM recovery. From there on, I will be able to deal with it. Until I come back to this forum, begging for mercy.
Have u tried using LG suite or LGUP u need to go to LG 's firmware page I'm not sure about this phone but it worked w my k7 about 100 times also helped unlock it. Check out the LG k7 forum lots of guys on there that use the lgup program and can help

Categories

Resources