User-agent: Mediapartners-Google Disallow: User-agent: * Disallow: /search Allow: / Sitemap: http://nano7mobile.blogspot.com/sitemap.xml Nano Mobile: screwed
Affichage des articles dont le libellé est screwed. Afficher tous les articles
Affichage des articles dont le libellé est screwed. Afficher tous les articles

[Q] I think I screwed up! topic






I went with this guide to root my Oneplus: http://www.xda-developers.com/how-to...-developer-tv/

It worked, it is fully rooted (tried installing a root-acces app). It has TWRP recovery.

I wanted to install Mahdi-ROM, I went with this URL: http://forum.xda-developers.com/onep...ra-4k-t2813107

I copied the GAPPS + Mahdi-ROM, booted into TWRP, went for advanced wipe and selected: Cache, System and Dalvik, like the guide says.
It worked and went on with flashing the Mahdi ZIP and Gapps ZIP. It said installation was succesfull, then it restarted to the onplus (powered by android) screen.

After this screen comes the 4 coloured circles (green blue red yellow) that swirl into each other and out of each other. My phone has been stuck into this screen for around 30/40 minutes now. I cannot turn it off or perform any action at all...

WHAT HAPPENED? O.o






[Q] Screwed up and now I'm stuck in a boot loop topic






Ok so to preface this my volume buttons don't work. I'm not sure if it's hardware or software issues because I have had them start working again after they originally failed. I've recently upgraded my phone and was planning on giving my friend my old DNA. I thought it be nice to update it for him to a better version of cyanogenmod and screwed up the install somewhere along the way. I made a backup before I started so if I could get into recovery I could set things right but with it stuck in a boot loop and no working volume buttons I've ran out of ideas on how to do that. Any one here have a clue?






My borother screwed up his Moto G bad, won't boot topic






When my brother first got his Moto G, I helped him root it and set up Xposed Framework with a security module, per his request. When he got the notification to update to Android 5.0, he accepted it and thereby screwed everything up.

Now when he tries to boot the phone, it shows the Google logo with the unlocked bootloader icon underneath for a while before showing the boot error symbol (android guy lying on his back with a red triangle). I've noticed that during this boot animation, the screen flickers, which is something I've never seen before. When the error symbol shows up, I can hold volume up + power to get the recovery menu. I can also boot into the bootloader by holding volume down + power while the phone is off.

I've tried wiping the phone via recovery, flashing a factory image, anything I could think of, with no success. What should I do? Thanks in advance!






[Q] May have possibly screwed up Blu Studio 5.5. topic






So I bought a Blu Studio 5.5 unlocked from boost earlier today and decided to mess around with it. I rooted and installed a clockwork recovery made for the device. I then flashed a supposedly ported version of MIUI for it too (stupid idea). The next boot did nothing but get stuck at the BLU logo. I've tried flashing two different stock roms to no avail. Now it is just stuck in a bootloop. I also seem to have lost root and cannot reboot the phone unless I removed the battery. I get the " Root access is missing. Root device. THIS CANNOT BE UNDONE" And then no and another option that is cut off and I can't even select the 2nd option. I stupidly don't have a backup image to restore with.

Is there anything I can do or have missed to potentially fix my stupid mistakes?






[Q] TWRP Manager screwed the USB storage write permissions topic






I used "TWRP Manager " Apply SD CARD Patch, and now it locked my USB storage write permissions. My apps cannot store anything now. Also I cannot paste any files to my phone from PC.

I even "Reverted the patch" from TWRP manager settings, but its not fixed. I have already did a factory reset.

Kindly help me.

http://android.stackexchange.com/que...le-from-pc-usb

It even affected app like Maps: http://android.stackexchange.com/que...-maps-lollipop


Im using Nexus 5 (5.0.1)