Database Users

[Q] [Help]Attempts to root & install CM9 have failed.

OK, I have really screwed the pooch on this.
In attempting to install the Unofficial CM9 rom, I have rendered my Xoom totally unusable.
What I did.
* Unlocked Xoom
* Rooted Xoom
* Attempted install of CM9 from here
* It failed, or I thought it did. It would start booting with the CM9 splashscreen, but that was all that would show. It would never complete booting.
* Tried to rollback another rom. Ended up mistakenly installing a rom that was not 4G/LTE, so no mobile data worked.
* Found a 4G rom and began attempts to install it.
What my problem is now.
* Device will not boot past the red M screen. (it stayed on that screen all last night until the battery finally died).
* Device will not allow me to use ADB because I can't unlock it.
* I can get to fastboot, but when attempting to unlock the xoom it does the following.
- Shows unlock warning
- will respond that it's unlocking the device
- will eventually complete and reboot
- On reboot, it will completely reboot, but it acts like a fresh install of the OS has been done (have to do the setup steps again)
- after doing the setup, ADB fails to be able to flash items over to the device as the device acts like its still locked.
What I need help with.
* How to unlock the device so I can flash using this thread, post 2
Thanks for everyone's/anyone's help on this.

Back running again
I was able to get the tablet running again.
Downloaded the HLK75D revision from the Motorola Developer's site and used Fastboot to flash the 4 components to the device.
Now to start over.
Yep, I am hardheaded.
Hope this helps others.

coolbeans8 said:
I was able to get the tablet running again.
Downloaded the HLK75D revision from the Motorola Developer's site and used Fastboot to flash the 4 components to the device.
Now to start over.
Yep, I am hardheaded.
Hope this helps others.
Click to expand...
Click to collapse
Well, what will you do differently this time? We all learn from our mistakes. Good luck.

How I did it this time.
After flashing the Moto original distro, I did the following to get the CM9 install running.
1 Using fastboot, flashed the CWM recovery onto the device.
- "recovery-clockwork-4.0.0.4-stingray.img"
2 Then rebooted to the interface and connected to laptop.
3 Copied over the "Update.zip" and used the "Cornea" tools to reboot into Recovery.
4 In recovery installed the "Update.zip" which gave me Root.
5 Rebooted to the OS.
6 Connected the tablet to windows
7 Copied over the CM9 zip "update-cm-9-20120403-SNAPSHOT-stingray-signed.zip" and the GAPPS zip "gapps-ics_tablets-rogue_v7.1-signed.zip" to SD card
8 Installed CWM (both the base app and the Premium upgrade
9 used CWM to reboot to recovery
10 In recovery cleared all the data
11 In recovery cleared all the cache
12 In recovery installed the CM9 zip
13 In recovery installed the GAPPS zip
14 Prayed. Seriously,
15 rebooted.
16 Did a happy dance.
That's it.
Hope it's helpful to others.

Congratulations! Enjoy!

[Q] !!!Assistance needed!!! Problems with almost every ROM!

I am trying to install the Sammy Deluxe Custom Rom, but when i did it got stuck on the boot animation and kept restarting again and again with 2 fast vibrations.
I tried installing a diferent S5-like ROM and ended up with the screen showing Samsung Galaxy S4 GT-I9505 and not going any further than that.Note that i installed a less consuming, 459 MB ROM 4.4.4 AOSP and worked fine. Now i unrooted and went back to stock for the moment, but i would really like to make Sammy Deluxe work.
That being said, here are the steps i followed:
1.Root the phone via the galaxys4root*[email protected] method via the motochopper application. It installed superuser but it didnt give me access to it, telling me it had to update and giving the options Cancel/Install/Recovery Install. Neither worked.
2.Root the phone via an apk found here on xda. Worked like a charm and Superuser updated.
3.Install Twrp. Put the .img file in the sdcard and typed command on Android Emulator. Flashed the .tar file via Odin.
4.Go to recovery, follow the guide steps(Full wipe, Advanced wipe, Install Rom), choose the settings i wanted in installer and reboot the system.
After i rebooted i got to what i typed on the first row, boot animation crash and double vibration restart.
Click to expand...
Click to collapse
So what did i do wrong?How can i install the ROM correctly?

[Q] Problems after installing boot loader V8

Hi!
Last night I installed bootloader on my A500. And noticed problems right away.
Problem #1: I can't boot into recovery using RECOVERY menu in bootloader. I flashed CWM as secondary kernel and can boot that way. But I think there is something wrong. Also HOME button didn't work.
Problem #2. Right after installing bootloader I was able to boot into my system (ICS). Then i installed rooted deodex stock ROM. This time my tablet kept crashing launcher.
Problem #3. I installed Omni unofficial light ROM, gapps and SU. Creared cache etc. Tried to boot - tablet gets stuck on boit animation - ANDROID sign with running lights.
Does somebody have an idea what is wrong?
Any help appreciated!

[Q] Cannot install TWRP (Bootstrap)

Hi,
I have Defy MB525 and I currently flashed JORDN_U3_97.21.51.sbf.
I read most of the guides here, but I'm still in the loop - cannot get working TWRP to install latest CM11.
I flashed Recovery BootStrap v4 (TWRP) but when the phone starts booting, it ends up with the following screen and I cannot go foward.
It doesn't matter, what I choose (Recovery or continue.). When I press the menu button (to choose Recovery), nothing happen, till the 3rd press - than the display goes black and thats all .
Maybe its related to the bootloader version, which is 09.10 or is there any prerequisite to successfully install TWRP?
Any idea where could be the problem or what I'm doing wrong?
Thank you in advance

Issue fixed
Even that nobody replied, I finally fixed this issue, so I will post here the solution, which may help to anybody else:
I finally found the sbf file, which is working with my Defy: http://motoroladefyall.nortol.info/motorola/joe30_236_DFP-231_Magyaritasa/DEFYPLUS_U3_4.5.1-134_DFP-231_GR_SIGN_UCADEFYEMARAB1B80AA004.0R_PDS03C_USAJRDNGIBRRTCEE_P022_A022_Service1FF.sbf.gz
After flashing this, the phone finally booted and saying its MB526, but never mind...
Then I rooted the phone with Framaroot app and installed the TWRP recovery (bootstrap). This time SuperUser was asking for root permission, so I granted it, flashing recovery was finished and the phone was rebooted.
Then the recovery was finally working, so I flashed the resize.zip, latest CM11 and minimal GAPPS.
And hurray, my Defy is finally running with the latest KK

CM 13 - Stuck in Recovery Mode after update

Yesterday I wanted to update my Nexus 4 to the latest nightly cm-13.0-20160221-NIGHTLY-mako.zip using the built-in update tool. The old build was cm-13.0-20160209-NIGHTLY-mako.zip.
But after hitting reboot, the screen went off and on repeatedly (just plain black). I let it like this for the night. In the morning it was still turning the screen on and off. I was able to reboot to the bootloader. Apparently, the update deleted TWRP and installed Cyanogenmod Recovery. I re-flashed twrp.img, and now I'm stuck there: booting ALWAYS goes to TWRP (or the bootloader), I can't boot the system anymore. I tried re-flashing the old nightly, retried the new one, tried sideloading an even newer one (cm-13.0-20160222-NIGHTLY-mako.zip), wiped cache, wiped data - nothing helped.
What can I do to unbrick my phone?

Do u have a back up to your stock Rom or any other Rom aside from CM?

Flash back to stock and start over with twrp, cm, and gapps.

I just flashed back to stock, the problem persists: bootloop, the lying android with a red warning sign is showing up very briefly, then it reboots.

My first attempt to go go back to stock was manually. Now I tried again using the Nexus Root Toolkit. (Note: both time I flashed build LMY48T
After it finished flashing, the error message (lying android with red warning sign) appeared again, but this time it stayed - no bootloop anymore.
Then I rebooted into revovery mode, and there was some output:
Code:
Finding update package...
Opening update package...
E:unknown volume for path [/storage/emulated/0/cmupdater/cm-13.0-20160221-NIGHTLY-mako.zip]
E:failed to map file
Installation aborted.
OTA failed! Please power off the device to keep it in this state and file a bug report!
So, despite all flashing, apparently it is STILL looking for the - now missing - cm13 update. Where is this coming from? There must be some flag somewhere, some config file or whatever.

So, after the next reboot, the ominous boot parameters seem to be gone - I'm on a fresh 5.1.1, build LMY48T.
I'm still curious what happened here. I guess the whole flashing wasn't necessary, I just needed to get rid of the malicious boot parameter. Maybe a file or a file system was readonly?
Any idea how this happened?