yashsingh1/xdaforums huggingface dataset:
[Droid X General] CONfirmedRAD:
I am trying to root this phone for a friend. I have tried Motorola One Click and Pete's Motorola Root Tools and both didn't work. I also tried the GingerBreak app and it didnt work either. Any help would be appreciated. Here are the phone's specs (and I am putting it all because I dont know what is and what isn't pertinent info):

System Version: 45.621.10.MB810.Verizon.en.US

Model number: DROIDX

Android Version: 2.3.4

Baseband version: BP_C_01.09.15P

Kernel Version: 2.6.32.9-g3e80c7a hudsoncm@il93lnxdroid53 #1

Build number 4.5.1_57_DX9-10

ERI version: 5

PRL version: 53342

And I am sorry in advance if I am just stupid with any of this. I do have experience rooting because I have rooted the original Droid.
[Droid X General] sd_shadow:
ROOT] Framaroot, a one-click application to root

I have verified it works with these Motorola devices running android 2.3.4

Droid 2 (a955), Droid 2 Global (a956), R2D2 (a957), & Droid X (MB810)
[Droid X General] CONfirmedRAD:
awesome, this worked within a few seconds

now i am trying to update it to ice cream sandwich, i have searched Google and attempted a few different ones, and every time it goes to Verify update package, it fails and says failed to verify whole-file signature and signature verification failed, then installation aborted.

http://www.android.gs/update-motorola-droid-x2-cm9/

those are the steps and files i am taking, except the step to get it into bootloader is actually needing to be getting into recovery, bootloader is wanting me to connect by USB and the steps dont actually give an instruction on what to do through USB to flash anything

so i get into Android system recovery

i wipe data/factory reset

i then wipe cache partition

then apply update from sdcard, then choose the one downloaded from above site, and i get the above error message, this is actually farthest ive got than the other ones ive tried, for example, i tried the Bootstrap Recovery and it never did anything, it rebooted to the Motorola logo and nothing ever happened

please assist, i am desperate
[Droid X General] sd_shadow:
you have a DX not a DX2, so use DX rom

sd_shadow's [Collection] of Links for: Droid X (MB810)
[Droid X General] CONfirmedRAD:
that is my bad, i should have confirmed the model of it, i just went off what my friend was saying it was, i went to that link, when i find steps to follow, download links are broken

if i could get specific working links for:

how to get a custom recovery installed, working link to such custom recovery for download

working link to download a ICS rom, the best one with as much working stuff as possible, camera etc

and if the above link doesnt include gapps, then a working link to gapps that is working for the ICS rom provided

im sorry im not trying to be needy but i have been working on this for like a week and its getting annoying, i really do appreciate any and all help
[Droid X General] sd_shadow:
everything you need is in my list sd_shadow's [Collection] of Links for: Droid X (MB810)

install a bootstrap from [HOW TO] Install/ Use Droid 2/X/3 Bootstrap

install a rom from my list of roms...

Liquid ics 2.0 is very popular

---------- Post added at 10:30 PM ---------- Previous post was at 10:29 PM ----------

gaaps are included with most of the DX roms
[Droid X General] CONfirmedRAD:
ya i figured it out, thank you very much, it works and running great, much appreciated
[Droid X General] CCC0180:
Seeking a 2.3.4/621 non OTA upgrade Recommendation

[MENTION=4267571]sd_shadow[/MENTION]

I have a Droid X on 2.3.3/4.5.602 that I am rooting. I was going to upgrade first to 2.3.4/4.5.621 but I read your warning "*****Do not use the 4.5.621 SBF file unless you took the OTA update, you won't be able to use any other SBF after updating or flashing to .621*****"

1. Is this warning still current? ie. I will not be able to downgrade to 2.3.3. tomorrow.

2. Should I care? ie 2.3.4/4.5.621 is a good upgrade, easily rooted, so I have no need to look back or all newer stable ROMs are based on 621.

3. If you don't recommend SBF to 621, is there a way to get the OTA is nolonger on Verizon?

4. Should I at least upgrade to 2.3.3/605

I have failed to root using Framaroot 1.9.1 on 2.3.3/602. Is Framaroot not for this version?
[Droid X General] sd_shadow:
Wasn't originally my warning, it was likely 1kds from his page https://sites.google.com/site/motosbf/droid-x-sbf-files

yes, once on 4.5.621, you can not downgrade

i wouldn't worry isn't really any problems with 621, it was just hard to root until framaroot

OTA update can be done manually, but they are incremental, you will have to install 605 ota then 621 ota, but once on 621 you still can not downgrade

There are links to OTA files in my list, but I recommend using SBFs.

How to Install OTA update in my update thread http://www.droidxforums.com/forum/droid-x-general-discussion/50864-2013-sept-update-zip-system-version-45-621-10-verizon-en-us.html

605 works fine, your choice

may not, pretty sure Framaroot works on 605
[Droid X General] m.ksy:
Sometimes new versions of Framaroot wont work properly for old Moto phones. Try this: Framaroot, works always for me.
[Droid X General] CCC0180:
Rooted in 605

Thank you sd_shadow and m.ksy for your speedy responses. I spf-ed to 605 and Framaroot worked like a champ.
[AT&T Samsung Galaxy S 4 Q&A, Help & Troubleshootin] seedeh:
I just installed safestrap and I flashed gummy rom (4.4) . I wiped everything before hand and everything seemed okay until I booted it up. It said safestrap enabled but then when it actually booted up I am stuck with this boot animation that is striped sky blue and and green and skyblue alternating. Pink squares are shimmering in the background. It stays like this and I can't stop it.

Phone: AT&T GS4 MK2

What do I do?,

Seedeh
[AT&T Samsung Galaxy S 4 Q&A, Help & Troubleshootin] toxicpaulution:
OMG seriously another one of these. Read before you do anything to your phone. this is getting old real fast. YOU CANNOT USE ANYTHING OTHER THAN TW ON SS OTHERWISE IT WILL CREATE A BOOTLOOP. SS CANNOT CHANGE KERNEL THEREFORE YOU CANNOT USE AOSP OR GE BASED ROMS. Read before doing stuff like this. Search. There are plenty of forums on here explaining all of this.
[AT&T Samsung Galaxy S 4 Q&A, Help & Troubleshootin] seedeh:
Sorry.

Sorry I thought that only applied to MK3.
[XPERIA X10 Q&A, Help & Troubleshooting] ronaksworld:
C] Tried SEUS, Answer : After the complete successful operation : Nada Nothing !

after the Successful Operation did you unplug the phone and tried to turn it on?

After the Successful SE Update Services was successful my phone didn't start, then i removed battery and reconnected, power on and works fine.

search in forums for Dr Goodvibes his suggestions did help me.
[XPERIA X10 Q&A, Help & Troubleshooting] asciisort:
well thanks. at least some one replied. can you direct me to a specific url u have in mind regarding my query. also i have updated the query, kindly see the update. as for SEUS update Yes why indeed, i did that. Sorry, nothing came up. thanks for the reply though. gives me hope.
[XPERIA X10 Q&A, Help & Troubleshooting] ronaksworld:
Message this guy Dr Goodvibes http://xdaforums.com/member.php?u=4375132
[XPERIA X10 Q&A, Help & Troubleshooting] asciisort:
katctv Lord

thanks. will do.
[XPERIA X10 Q&A, Help & Troubleshooting] Dr Goodvibes:
Your phone indicates an unlocked bootloader, just for your information.

What's the thoughts on the battery? Was it in a good service state?

Take the battery out of the phone for 48 hours and then put it back in the phone and power the phone on.

The green light for a few seconds indicates the phone is attempting, or in a recovery state.

Your phone may have just had a 'moment' and has a "locked instruction", that just needs to be cleared with no power applied to the chipset.

This has worked for others and is more voodoo than science, but worth a try.
[XPERIA X10 Q&A, Help & Troubleshooting] asciisort:
Oh thanks for the update about the boot loader state. i definitely be keeping it apart for 48 hours and will update you regarding the same. thanks for the reply, you know i love this set of mine and your precious replies gives me hope.

Regarding the battery state, i guess it was okay, gave me a 1 day backup on the phone. So i guess it was in a kinda okay service state. though am not sure whether its fully charged or not. i don't actually know the power state / current charge level of the battery though coz i found the device bricked. if there's anything you can suggest, will be really helpful. though thanks for the information.
[XPERIA X10 Q&A, Help & Troubleshooting] asciisort:
So I waited and waited for some more time, couldn't wait any longer for the 48 hours duration. Does t has to be 2 days ? I just wanted to bring my device back to life. Though, after giving up shortly after 12 + hours, I flashed it again, it did successfully, although, nothing even now, green light followed by a vibration and then boom. nothing ! :( f1 help needed ? btw, does it has to be 2 days?
[XPERIA X10 Q&A, Help & Troubleshooting] Dr Goodvibes:
I would have placed the battery back in the phone and pressed the power button and see if it booted, or allowed you to get to CWM Recovery with blue light or xRecovery(if installed).

One day, one week. How long does residual power remain in a circuit board to hold the current date/time before resetting?

Maybe buy a cheap BST-41 1500mAh battery for the XPERIA X10 and try that. Could be just a bad battery.

You could check the battery with a multimeter and see if it still has a charge.

My knowledge base stops at this point as I have no experience beyond this.

Good luck.
[XPERIA X10 Q&A, Help & Troubleshooting] asciisort:
Thanks Dr. Goodvibes, I definitely will keep you posted. Though, when I plugged the battery in, first I did check, nuthing ! green light + vibration. and then it goes blank. I installed my feralab jb rom via xRecovery so, yes it is there (installed) but afterwards I have flashed the stock via SEUS so i guess even xRecovery is gone now. I am not for sure. Though it was installed earlier. Right now I am thinking of keeping it apart till the time i found a new battery, it can be even 2 + days. Even 1 week. I will wait for a week now. Thanks for letting me know all about this. Keep me posted.
[XPERIA X10 Q&A, Help & Troubleshooting] asciisort:
Update Number 2 : Hey, after completely keeping aside the battery for more than 24 hours, I connected the device to external wall DC supply (while battery was removed and never inserted after the 24 hours interval that is). After connecting the device to DC wall supply, it gave me the same response, flicked and showed green light and then vibrated and then nothing ! F1 !!!
[XPERIA X10 Q&A, Help & Troubleshooting] asciisort:
Update 3: http://talk.sonymobile.com/t5/Xperi...on-Flash-mode-even-when-plugin-to/td-p/273134

Just Googled my problem and came to this link. I can very much relate to the link although, His device was water locked, (there was this small white rectangle, if it is water damaged then it will be red) Surprisingly, his device which was water damaged shows the same symptom as mine. So, i checked mine, but the sticker or white rectangle for moist / humidity checker is white totally. So I guess it can't be water damaged, although, it showed the same symptoms ! :eek:
[XPERIA X10 Q&A, Help & Troubleshooting] asciisort:
Update Number 4: Since green Light was always On, I thought what if its in flash mode and much to my surprise, the device is in Flash Mode when I switch it on, how I found out : While flashing via SEUS, I didnt press the back key and the device got connected in flash mode by default, So i narrowed down the problem to something that : My device boots to Flash mode and not as it normally should ? Is it a mother board problem ? Can it be cured ? (god no please not mother board problem) So ? Any thoughts anyone to make it come out f the flash mode. ?
[Captivate General] ajeesh vijayan:
http://xdaforums.com/showthread.php?t=2625585

just informing..
[Nexus 4 Q&A, Help & Troubleshooting] CodyMoores:
Hello guys. I've been searching for hours and it seems no one had the same question as me or maybe I'm searching the wrong key words or something. Okay so to the problem (it is bugging the life out of me) First things first.

I am new to the whole rooting scene. I just rooted my Nexus 4 and it had Android 4.4.2 on it stock. I unlocked it and rooted it successfully. I installed the Paranoid android ROM and Gapps. It worked fine. BUT It wasn't the ROM I was looking for. So I tried to uninstall it and it went downhill from there.

I tried putting a different ROM on my sd from my windows 7 computer and it wouldnt let me. I downloaded it on my phone and found a way to do it it but the gapps were 4.4.2 and PacMan ROM was 4.2.2. I've been searching for the PacMan 4.4.2 ROM for hours and cannot seem to find it anywhere.

Also now with the gapps 4.2.2 and PacMan 4.2.2 on my phone, the wireless isn't working? If anyone can help, please do so! And as fast as possible! Thank you very much! Or point me where I can find PacMan ROM 4.4.2?
[Nexus 4 Q&A, Help & Troubleshooting] gabriel1946:
Well first question what android build do u wanna be on? 4.4.2 or 4.2.2? And your wireless isn't working cause u most likely have a 4.4.2 baseband radio you need a 4.2.2 radio for u to get service
[Nexus 4 Q&A, Help & Troubleshooting] CodyMoores:
Well I'd like to be on PacMan ROM 4.4.2 All up to date
[Nexus 4 Q&A, Help & Troubleshooting] metpage:
Looks like latest is JB4.3: http://xdaforums.com/nexus-4/orig-development/jb-4-3-p-c-true-1-rom-t2146879http://xdaforums.com/nexus-4/orig-development/jb-4-3-p-c-true-1-rom-t2146879
[Verizon Samsung Galaxy S 4] loonie01:
There is leaked copy of 4.4.2 for ATT with new a new bootloader

http://xdaforums.com/showthread.php?t=2624782&page=10
[Verizon Samsung Galaxy S 4] Skrazz:
This is NOT to be flashed on the Verizon variant, because you know somebody out there is going to want to try.

Sent from my SCH-I545
[Verizon Samsung Galaxy S 4] hovax615@hotmail.com:
Running it right now.
[Verizon Samsung Galaxy S 4] tech_head:
because people are stupid!!!!!!!!!!!
[Verizon Samsung Galaxy S 4] joefrog1996:
A new bootloader means there's a good chance we may soon be able to flash custom recovers right?
[Verizon Samsung Galaxy S 4] nickeedoo:
It is very doubtful unless they find an exploit that wasn't in the MK2 bootloader.
[Verizon Samsung Galaxy S 4] hovax615@hotmail.com:
You can flash back to 4.3 after you flash this leak. It doesn't trip the qfuse. But once the official release is out that might change but yeah people on VZW should not flash this.
[Verizon Samsung Galaxy S 4] tshelby73:
This might be good news. If the kernel changed for 4.4 and you can flash back devs might find a work around.
[HTC Droid DNA] crpalmer:
[MENTION=5053434]jamiethemorris[/MENTION],

If you want to submit a pull request to my kernel for the changes (and they don't look dangerous, which I don't expect them to), I'll merge them in for you.
[HTC Droid DNA] mr4r4n:
What do you mean by don't share the kernel?
[HTC Droid DNA] jamiethemorris:
Multi ROM has an option to share the kernel of the primary ROM with any other roms. Does that make sense? So if you have my kernel installed on the primary ROM you can let another ROM installed use it instead of having to install it separately on that ROM.
[HTC Droid DNA] jamiethemorris:
OK cool, I'll do that. BTW do you think the patch will be drastically different when we move to msm8960 (other than the file structure being different)?
[HTC Droid DNA] mr4r4n:
Yes it does all the stuff given to me at the hospital may have slowed down my thought process temporarily... Lol, thanks bud
[HTC Droid DNA] crpalmer:
It will not likely be very different, but I wouldn't worry too much about the new kernel just yet as we have at least one hard problem to solve before then. After that, adapting this patch will be simple...
[HTC Droid DNA] t1gartist:
androids grub 2 hs come to dna now thats awesome
[HTC Droid DNA] jamiethemorris:
OK. I've been wanting to learn some coding to make this stuff easier... Where would you recommend starting? I don't really have time to take a c or c++ class right now, but some tutorials online would be helpful.

EDIT: Also, how do I do a pull request for only the kexec-hardboot commit? I don't see an option for it.
[HTC Droid DNA] jamiethemorris:
Yep, now we just need to figure out how to make the internal storage bigger lol
[HTC Droid DNA] rootMBX:
Sense

This is pretty sick. Thanks for finally bringing this to the DNA!

Couple of things.

TAP2WAKE?:

The recovery, based on TWRP's beta, has a bit of a lag sometimes when performing operations right before the operation is complete. Giving the screen a couple taps (away from where the tiles will appear) will bring up the "Back" or "Reboot System" tiles instead of it being stuck with the twirling bar. This is not really related to MultiROM.

What is a new issue/feature with the modified recovery is that when the display timeouts, a simple press of the power button does not turn it back on. A single tap on the display does, though. It brings up the Swipe to Unlock screen. Is this intended?

SENSE:

Also, I've tried 5 different Sense ROMs. No kernel sharing of course. They all flashed "successfully", except for the complete, newest stock (failed), but none of them booted. I got a black screen after the initial HTC bootloader screen.

AOSP ROMs work great though! Have tried a couple with/without sharing the kernel. When/If Sense gets worked out, this will be a great way to quickly switch for use with an MHL adaptor for HDMI output.

THEME BOOT SELECTION SCREEN:

I do like the retro boot selection screen, but what are the possibilities of being able to theme it? Maybe even as simple/clean as a couple of custom icons on a black background for ROM selection?
[HTC Droid DNA] jamiethemorris:
I don't know if the power button thing is intended or not. I've noticed it too. I've also noticed this recovery, as well as the twrp beta, taking a really really long time to do certain things, I think it's just a shared bug...

About sense Roms, I think we're going to need to need a patched kernel for those as well. If one of our sense kernel devs doesn't get around to it than I can do it. Supposedly we also need the newest hboot also, I'm going to play around and see if I can get anything to work. If you look through the htc one multirom thread you well see that only certain configurations of dual booting sense with aosp work. That was actually the original reason I was inspired to port this to the DNA.

I don't know how to do anything with the boot menu besides just change the colors because I don't really know how any of that works.

Anyway I'm excited about these new sense Roms too and I want to dual boot them with aosp as bad as anyone else so I'll be working on it.
[HTC Droid DNA] jamiethemorris:
I just tried flashing UnSense 1.0. It flashes fine, but doesn't boot. As soon as I switched to TWRP 2.6 beta, it booted without me needing to reflash or anything. So it's detecting something about the recovery on boot that it doesn't like.

I will try doing a cm10.2 based version of it and hopefully that will solve the problem.
[HTC Droid DNA] KyJelly69:
Can I use the twrp recovery without flashing multirom first and use it as my regular recovery? Then sometime later when I'm ready flash multirom?
[HTC Droid DNA] jamiethemorris:
Yes, it will work the same as regular twrp if you don't flash the multirom zip.
[HTC Droid DNA] rootMBX:
Go Schnell, GO!
[HTC Droid DNA] Darkstar1756:
Shared Apps?

Is there or is there planned to be a feature where different ROM's can share the same user apps like MoDaCo Switch does?
[HTC Droid DNA] jamiethemorris:
Not that I know of. However, there is a modaco switch for the HTC one I think which means in theory it would be possible to port it to our device...
[HTC Droid DNA] jamiethemorris:
I've made some progress with getting sense booting. I patched the 4.4 kernel and was able to get unsense to boot as a secondary ROM. What's weird is when it booted it was using all my data from my main ROM, and had messed everything up on both roms by combining the sense and aosp data. Makes absolutely no sense (pun not intended). But hey, it's progress... I'm going to contract dees_troy to ask how he built the 2.6.3.x twrp beta so that hopefully I can get this and twrp 2.7 booting sense normally
[AT&T Samsung Galaxy S 4 Q&A, Help & Troubleshootin] crazymax1:
Ok, so I flashed a custom rom and kernal and all went wel except my contacts didn't sync. I couldn't pull them from my Nandroid or my Tibu backup. So I tried to flash the backup I did last night and it failed. So I tried to flash another backup from earlier and it said successful in TWRP but it wouldn't boot after. I tried to go back into recovery only to realize that I no longer have my custom recovery. I do have a working stock recovery though.I'm kind of in a jam here and really need the help guys. I probably should have just cut my losses with the contacts.

More details. I flashed Danv's ASOP Kitkat 4.4 with the latest Ktoonez kernal successfully. I tried to recover my stock rooted 1337m 4.3 rooted with Saferoot. It won't boot into it. Maybe the difference in kernal has an issue with that or would that have been taken care of in my Nandroid flash?

Going forward, I'm thinking about another factory wipe and going into download mode with Odin and flashing my stock 1337m firmware to the phone and booting up. I'm just looking for a little direction here since I got in a bit over my head. I thought I did it all by the book by doing a Nandroid,and Tibu backup, and backing Tibu up to Google drive and my SD card, but clearly something didn't go right and now I'm on the ropes. I just want a working phone again. I can't sleep lol. I'm serious.
[AT&T Samsung Galaxy S 4 Q&A, Help & Troubleshootin] crazymax1:
Tough crowd eh? So I'm hanging at my boot screen after successfully restoring my Nandroid backup in TWRP. I've lost my custom recovery but I got root before I did through TWRP. If I did a factory reset in the stock recovery, could this potentially fix my boot hang? Or is flashing back to stock 4.3 in Odin the only option? Or is there another method I can force it to boot? I'l be honest: not having my custom recovery and going into the unknown is nerve racking here knowing I don't have my get out of **** card to save my ass. Can I push my Nandroid backup and relfash it through Odin?
[AT&T Samsung Galaxy S 4 Q&A, Help & Troubleshootin] hueygunner:
Can you get in to download mode and if so does it show KNOX security enabled?
[AT&T Samsung Galaxy S 4 Q&A, Help & Troubleshootin] azuziel:
By

Tbh I would flash back to stock via a verified stock fw via odin, Reroot, reinstall cwm/twrp, and then flash rom from that point.

Ive never had luck recovering backups cross rom. Whether Nandroid or tb.

Sent from my SGH-I337M
[Eee Pad Transformer Q&A, Help & Troubleshooting] JB910:
Today I booted up my tf101 and the screen stayed black then flickered blue lines across the top. I tried hard reset, no dice, tried to boot into twrp (I was running katkiss 4.4 fine for weeks), and the screen flickered blurry images, nothing. Tried to push stock software with easy flasher, looks like it works, but same issue when I turn the tablet back on. Weird thing is my pc still sees my tablet and ext sd files. Anyone have any ideas? My son is not a happy camper at the moment.
[Eee Pad Transformer Q&A, Help & Troubleshooting] *Detection*:
Is there a chance it has been knocked or dropped ?

The display cable has a habit of coming lose pretty easily if they receive a bump but are fairly simple to fix if you don't mind opening it

Have a look at the links in this thread to check that cable

http://xdaforums.com/showthread.php?t=2457848
[Eee Pad Transformer Q&A, Help & Troubleshooting] JB910:
Thanks man, I bet that's what it is. I don't have a n5 bit to pull it apart, I'll have to stop at the hardware store tomorrow.