yashsingh1/xdaforums huggingface dataset:
[Motorola Droid RAZR] sd_shadow:
you cannot wipe stock system, safestrap is installed there, and requires a working rom.

but if you just use a custom rom, it should be safe to leave system as is.

or even install a custom rom over system (stock slot)

roms on stock or safe slots are a little faster than roms on rom slot 1-4

slot 1-4 are good for testing a rom is to see if you like it, but most prefer their main rom on stock slot or safe slot.

If installing a custom rom over stock just be sure to not to reboot stock if you see errors

if see errors post them here, so we can try to diagnose.
[Motorola Droid RAZR] navinng:
Thanks for your reply....so its completely safe to install cm 12.1 on stock slot using safestrap with unused partition....I thought it will brick the device bcoz of bootloader n kernal and should install on safe slot.

While flashing I guess I should wipe data cache dalvic flash the ROM, gapps and the ram zip then wipe cache and dalvic cache.
[Motorola Droid RAZR] sd_shadow:
cm12.1 can be installed over stock rom, but you may find cm11 more stable.

custom kernels are booted after stock kernel using kexec.

kexec, abbreviated from kernel execution and derived from the Unix/Linux kernel call exec, is a mechanism of the Linux kernel that allows "live" booting of a new kernel "over" the currently running one.
[Motorola Droid RAZR] navinng:
I have flashed in safe slot and booted up cm 12.1 fine. Thanks a lot for your help. I guess I can boot into the default system also fine. Is there anything I need to be aware of like formatting internal storage or anything that can brick the device
[Motorola Droid RAZR] sd_shadow:
nope, just don't wipe /system partition without installing a rom right after.

cache, dalvik, data, internal storage and SD card can be wiped
[XDA Assist] tuckgray907:
Hello. I have done it again. What i mean is ive gone and glitched the phone by messing with the mixer paths file trying to boost the volume output. needless to say it didn't work and up until now (about 3 months later) its been working fine. but now im having the same issues that i did with my lg tribute. What happened is when i modified my mixer paths it didn't work and then it started to work very slowly and poorly. This happened to my Vista. I was able to fix it by some sort of backup on the tribute so im wondering if anyone knows what kind of backup thatd be. maybe a new rom or something. i got it from someone else that made it from an uncorrupted phone. I might need help finding one too. thanks for any help
[XDA Assist] tuckgray907:
Something that I just tried is resetting the phone. It didn't fix the mixer paths file but the phone is usable for now. I would like if someone could send me their mixer paths so I could try it. Also no media works. YouTube soundcloud and mp3's
[P3300, MDA Compact III  upgrading etc.] seeker777:
Hi, first of all would like to say this website is a great resource. I am slightly confused over the number of ROMS available. I have a MDA compact 3, its runs WM5. I want to upgrade it to a better ROM. Now which rom in your opinion is the most reliable and looks good? I want WM6, but what is the difference between touch pro and WM6? Is touch built on WM6? And how about the O2 WM6 Premium & PremiumPlus 1.0 WWE??

Can someone just recommend a nice ROM that will allow me to use my TOM TOM and run proficiently.

Many thanks

:eek:
[P3300, MDA Compact III  upgrading etc.] petervbeck:
Hi Seeker,

There is a thread comparing the different ROMS. But iMO you just can't say which one is the best one...depends on you.

Sometimes the developers making full and light editions, it's your choice if you want to use a app-free or app-loaded ROM.

Maybe a look into the threads can help you, in all the first threads there are some screenshots and a short description

about the released ROM.

I tried a lot of the ROMs since now (Fracoon, Tom, Meschle) and i was happy with every ROM.

TomTom is working on all of the ROMS....there is no reason to choose a special ROM just because of TT...

Cheers, Peter
[P3300, MDA Compact III  upgrading etc.] seeker777:
thanks Peter, will have a look. One more question:D Are all the new roms based upon Windows Mobile 6?
[P3300, MDA Compact III  upgrading etc.] petervbeck:
When you're searching in the Artemis WM6 Threads....yes of course :)
[P3300, MDA Compact III  upgrading etc.] seeker777:
Cheers Pal :)
[P3300, MDA Compact III  upgrading etc.] petervbeck:
...and I think your own experience is better than the impressions of others.

There are always people reclaiming some things in a ROM you maybe

never had a problem with. And hey, a ROM is installed in 10 minutes... ;)

And to say which one is the best isn't objective and unfair against the developer...
[P3300, MDA Compact III  upgrading etc.] seeker777:
Well thanks to this forum and ppl, i have managed to install a new ROM, works like a charm :)

Im thinking of trying others out. will i have to run the Artemis_USPL again everytime i install a new rom? or is this just required once?

Thanks again
[P3300, MDA Compact III  upgrading etc.] petervbeck:
Yes, always run USPL before , otherwise you could brick your device, and that's no fun :D

Cheers
[P3300, MDA Compact III  upgrading etc.] seeker777:
Cheers, will do!
[Moto G 2015 Q&A, Help & Troubleshooting] purplepizza:
We know you can boot to TWRP vice flash to your device by using the command:

fastboot boot twrp.img

But how do you proceed from here? Are you required to use ADB commands at this point or can you unplug your USB cable and use TWRP as if it was installed, I.E. , back up current ROM, and install new zip.
[Moto G 2015 Q&A, Help & Troubleshooting] HTCDreamOn:
Sorry if I wasn't clear. Yes you can unplug usb and use as normal, it just means twrp isn't flashed to the device so it won't be there when you reboot.

I just recommend this step because I'm paranoid. Once you've confirmed the image works you should reboot to bootloader and fastboot flash the image, then you'll be able to boot into twrp whenever you want.
[Moto G 2015 Q&A, Help & Troubleshooting] acejavelin:
This is a good step to do, and if the device supports it it should be used... for example the Moto G (if unlocked) fully supports fastboot boot commands, devices like the HTC One M7 do NOT support this anymore...

To the OP, what is really happening here is that TWRP or the boot.img (kernel) is being loaded from USB into RAM and executed normally, instead of the standard /boot partition which is skipped when executing fastboot boot. TWRP (and recovery in general) is really just a specialized micro-sized android distribution and when started via fastboot boot is executed as if it was the boot image. Once the image is transferred into RAM, the boot continues normally per the instructions of TWRP or the boot image, and no further action via USB is required. USB is just the medium to load the image into RAM and nothing more.

fastboot boot - used to manually load a boot image (or recovery) and execute from RAM, it is not flashed to the device, on the next reboot it will return to it's previous state

fastboot flash boot/recovery - used to actually flash the boot image or recovery image to the it's appropriate partition on the device, it does not execute it. On a reboot or factory default this information will stay in the device.
[Moto G 2015 Q&A, Help & Troubleshooting] purplepizza:
Thanks. So it seems there is no reason to ever flash TWRP unless you don't want the PC dependence to use the TWRP tool.
[Moto G 2015 Q&A, Help & Troubleshooting] acejavelin:
Well, sort of... but the point is once you flash anything via twrp, you are no longer stock, so why not flash twrp to make it easier to flash other things?

The smartest thing would be to unlock, boot TWRP, make a nandroid backup before you do anything at all, then flash TWRP and do your thing...
[Moto G 2015 Q&A, Help & Troubleshooting] purplepizza:
I understand what you are saying. The only flash I planned on was SuperSU. I thought when a system upgrade is available, I could simply use SU to unroot and be ready for the update. Would this work?

If I followed your recommendation, could I feasibly, flash TWRP, then when an upgrade is ready, flash nandroid backup (which I assume removes TWRP) then accept system update, then re-flash TWRP. I could restore apps by using TB. Does this make sense? Or does TWRP remain in place after flashing nandroid backup?
[Moto G 2015 Q&A, Help & Troubleshooting] acejavelin:
TWRP remains in place after restoring a nandroid (I think, I haven't installed on my Moto G, but in most devices it doesn't backup/restore recovery), but you can easily restore the original recovery via fastboot.
[Moto G 2015 Q&A, Help & Troubleshooting] purplepizza:
Just curious, how did you go from 5.1.1 to 6.0?
[Moto G 2015 Q&A, Help & Troubleshooting] acejavelin:
OTA... part of soak test on December 22.
[Moto G 2015 Q&A, Help & Troubleshooting] HTCDreamOn:
Hey thanks for helping to answer this, your explanation was much better :o I thought it had something to do with loading into RAM but wasn't sure. I didn't know some devices don't allow fastboot boot commands though, I've always relied on them. Part of the reason I'm avoiding htc now. :eek:

[MENTION=4837752]purplepizza[/MENTION] I agree with everything acejavelin has said: essentially you really do want to make sure your have twrp flashed.

To answer your nandroid question: It basically just takes an image of the partitions you choose, usually /system, /data, and /boot (where kernel stuff is) which is the least you need to boot back with all your data. It doesn't backup recovery and when you restore it doesn't write anything to recovery, so yes twrp will still be in place. In general you should only ever flash stuff to the recovery partition whilst in fastboot mode (i.e. using fastboot flash recovery recovery.img), I know on some devices you can flash recoveries as zip files in the recovery itself but you shouldn't.

I've seen quite a few people querying about the 6.0 OTA: in short, I wouldn't worry about it because once they start rolling out, people always catch the OTA and post here on xda. You can flash that and it'll return you to stock 6.0 anyway, at which point you can reroot and everything if you want.
[Moto G 2015 Q&A, Help & Troubleshooting] purplepizza:
One more question, when making the first nandroid backup. do you just back up system and data or do you include boot as well?
[Moto G 2015 Q&A, Help & Troubleshooting] acejavelin:
My opinion is always backup everything, you can always choose what to restore
[Moto G 2015 Q&A, Help & Troubleshooting] purplepizza:
So what is boot? I know I am kind of going back to my previous question, but if I restore boot, is that the boot loader? I would assume this would not commonly need restored?

And I now assume the bootloader is completely independent from recovery.
[Moto G 2015 Q&A, Help & Troubleshooting] acejavelin:
It is not the bootloader... It is the /boot partition of the phone, basically the kernel and RAM disk. If you screw things up and need to restore, you typically want to restore /boot, /system, and /data, and occasionally /cache (if you want to restore to save time and get an exact duplicate of the previous image, otherwise many people skip /cache and let it rebuild on the first boot which takes 10-15 minutes extra).
[Moto G 2015 Q&A, Help & Troubleshooting] purplepizza:
So I am following your advice. I booted to TWRP, made Nandroid backup.

Rebooted and flashed TWRP, see below:

sudo fastboot flash recovery twrp.img
target reported max download size of 268435456 bytes
sending 'recovery' (7772 KB)...
OKAY [ 10.635s]
writing 'recovery'...
OKAY [ 0.141s]
finished. total time: 10.776s

All seems OK.

Scrolled to recovery, selected recovery. TWRP was there. I then powered down.

After that I held power and volume down, system boots to dead Android with message “No command” Held power then volume up, I see stock boot loader. Is TWRP flashed somewhere or is it gone? So what did I do wrong.
[Moto G 2015 Q&A, Help & Troubleshooting] acejavelin:
:confused: I have no idea, you did it right... selecting recovery from the bootloader should start TWRP, not stock recovery, that should be gone.
[Moto G 2015 Q&A, Help & Troubleshooting] purplepizza:
Any recommendations how to proceed?
[Moto G 2015 Q&A, Help & Troubleshooting] just_another_guy:
I also need help with my soft bricked moto g3 :)

Moto g3 (xt 1550, Indian dual sim 16 gb version)

I officially upgraded to 6.0.0 via ota and my objective was to root my phone and use xposed modules. I am not interested in any other custom rom (I'd rather keep stock rom just for moto display :cool: and ota upgrades) or custom recovery like twrp(I'm afraid it may cause ota upgrades to fail).

I used the method described here in the question- http://android.stackexchange.com/qu...rsu-using-play-store-versus-a-custom-recovery

So I first successfully unlocked my bootloader using the official motorola method.

I then proceeded to use google's backup settings to re-install all the apps that were uninstalled due to unlocking the bootloader. I also put supersu.zip version 2.46 on internal sd card.

I then proceeded to (without rebooting) enter fastboot where i used minimal adb to temporarily boot into twrp version2.8.7 r5 (link - http://xdaforums.com/2015-moto-g/orig-development/twrp-twrp-moto-g-2015-t3170537 ).

Once in twrp, I located and flashed the supersu.zip. It flashed successfully. I procceded to clear dalvik cache and then after clearing cache I tried to reboot my phone using twrp.

However, it did not go beyond the "Warning - Bootloader Unlocked" screen that you get on unlocking a motorola bootloader.:( I left it for over 10 minutes (usb was still plugged in, I had >80% battery) but it did not proceed.

Long -pressing the power button causes the phone to vibrate and again attempt to boot, stuck at the same initial screen. Adb quite understandably does not work here.

I can press vol down+power and enter fastboot , where adb works fine.

I can enter stock recovery from the fastboot sceen too.

Using adb in fastboot, I am able to boot twrp . In fact, I tried to re-install supersu.zip. I retried version 2.46 and then tried version 2.56. On all occcassions, it was able to successfully flash it, but gets hung on the initial boot screen.

USB Debugging is also enabled, and I have a backp of my sd card data.

I tried taking a backup of the system and apps in twrp (3 gb in total) and tried to reflash it, but it still hangs at the same screen.:(

Is there any way I can unbrick my device and- (in decreasing order of preference)

1. Keep my stock rom and recovery?

2. Keep stock rom with twrp? (It should not be a problem)

3. Custom rom with custom recovery - perhaps official cm. Least preferred as I want Moto Display and stock/vanilla android.

Also, is SELinux involved anywhere with my phone getting bricked? :confused:I also read that a custom kernel is required for rooting 6.0, which I don't have. Supersu Version 2.56 is said to prevent soft bricks if the kernel is incorrect (systemless root), yet even after flashing the newer one it is still bricked. Where am I going wrong? :eek:What should I do? Thanks in advance! :good: :D
[Moto G 2015 Q&A, Help & Troubleshooting] acejavelin:
Try the flash again? Sorry, but I don't really know help... if you are successfully rooted, perhaps try to flash TWRP image with Flashify? (select your file, don't let it auto-grab an image)
[Moto G 2015 Q&A, Help & Troubleshooting] purplepizza:
I have not rooted yet. I guess I can try by booting TWRP then flashing SuperSU.

Can you think of any reasons not to try fastboot again the re-flash TWRP?
[Moto G 2015 Q&A, Help & Troubleshooting] acejavelin:
None... As long as you have the correct version of TWRP and are unlocked
[ONE Q&A, Help & Troubleshooting] ImHavenHart:
Hi guys. I have a OnePlus One and I flashed CM13. For some reason my call quality is very bad and callers say that I sound muffled. Is there a radio that I can flash or something that I could do to improve call quality?
[ONE Q&A, Help & Troubleshooting] jon52491:
Hi, I've had the same issues using the new 00011 or 00013 baseband. I've flashed the 00241 baseband from lollipop which fixed it for me. Here's the link: https://www.androidfilehost.com/?w=files&flid=28032

All credit goes to Chineel for the upload.
[ONE Q&A, Help & Troubleshooting] Odysseus1962:
I was having all kinds of problems with phone call clarity as were my friends that had purchased based on my recommendation and invite. These problems started around late August/early September. We tried flashing different ROMs, modems, and firmware to no avail.

Then I discovered an obscure post in the Oneplus forums suggesting turning off "OK Google" detection from any screen, and viola! No problems since. Apparently, the always on "OK Google" detection interferes with the noise cancelling microphones on the handset creating all sorts of problems with phone call clarity.

The workaround is to go to the Google settings app. Then dig down to... Search & Now/Voice/"Ok Google" detection and disable "From any screen". It immediately takes affect and the results are like night and day.

Good luck. I hope this helps, and don't forget to hit the thanks button if this works for you like it did for me and my friends.
[General Questions and Answers] Galaxian2600:
Hello, when i try to install a custom galaxy s5 rom for my onetouch c9, from my sd card, it shows installation aborted. i tried adb, but i don't have the 'developer-tools'. Can anyone help me? Thanks!
[General Questions and Answers] DJilaniE-070:
Developer tools

Go to settings, about phone, than press 10 times on build-number. You should now have developer options hope helps, DJE-070
[T-Mobile Galaxy Note 4 Q&A, Help & Troubleshooting] nigafied45:
I recently did the latest update to my T-mobile Note 4 upon updating the phone, the phone was in a constant boot loop and finally installed the update to the device. Upon installing the new software update to the phone it began the reboot loop and eventually started up I received one text message and it began to loop again and now it will not turn on. None of the button combinations will turn the phone on it is not accepting a charge either. I put the battery in another note 4 and it works fine and shows 79 percent of the battery is charged. What can be done to get the phone to wake up out of it's current state most of the pictures were salvaged with drop box, but it did not update from a family funeral yesterday with several pictures and those are important. Has anyone had this issue before and what was done to fix it?
[T-Mobile Galaxy Note 4 Q&A, Help & Troubleshooting] Modzilla44:
A few questions I would ask to be able to help would be:

Which baseband/bootloader/version were you on and which upgrade was your Note IV attempting to install?

Are you rooted or stock?

When you say that it bootlooped a bunch and then "finally installed the update", was that with no user interaction at all? seems odd to me for a bootloop to repeat and then randomly work.

If I were you and after pulling battery for 30 seconds doesnt work and holding down home+power+volume up, then try plugging it into a USB port on your computer and see if it recognizes it. Make sure your PC has latest samsung usb drivers.
[T-Mobile Galaxy Note 4 Q&A, Help & Troubleshooting] nigafied45:
All stock the last update performed was for that security hole android had on the android 5.1.1. What I mean is that during the install the phone kept restarting and restarting and then it installed the updates and went to the home screen. When it reached the home screen it showed me one text and I went on charging the phone thinking it was normal woke up this morning the phone was off yet the battery still has 79 percent when placed in another note 4 phone. I tried plugging into the pc the phone isn't recognized because it does not turned on it says unrecognizable usb device and I installed the latest samsung drivers as well I've tried those button combinations as well as pulling the battery. I'm wondering if the update corrupted something prohibiting it from booting it doesn't take a charge either when connected to the wall it's almost like the phone is in a stale state.
[T-Mobile Galaxy Note 4 Q&A, Help & Troubleshooting] Modzilla44:
Have you tried installing Kies on your PC to see if it can detect it? I believe it has a couple special options for detecting and repairing corrupted stock updates. http://www.samsung.com/us/support/owners/app/kies
[T-Mobile Galaxy Note 4 Q&A, Help & Troubleshooting] nigafied45:
I haven't tried kies I tried smart switch though and the phone wasn't detected I'll try kies as well. I'll be back with an update appreciate the help.
[T-Mobile Galaxy Note 4 Q&A, Help & Troubleshooting] nigafied45:
Kies didn't work because the phone can't be recognize by the program the computer makes a noise knowing when the phone is connected but the screen on phone doesn't turn on I can't even get it to boot up or accept a charge and the battery is nearly full given that I put it in another phone to check. I've tried even starting the phone up with no battery using direct charger as primary source but it didn't work. I'm not sure how the update fried my phone, but I'm going to be losing some important pics drop box didn't sync yesterday during a family funeral.
[T-Mobile Galaxy Note 4 Q&A, Help & Troubleshooting] Modzilla44:
That is just really ****ty luck. They say there is always a small chance that flashing anything can cause epic partition disasters. If kies is detecting it but saying it's unable to connect then I'd say the phone is toast. You might be able to get Odin to recognize it and reflash the entire ROM, but that would obviously destroy any data you had on the device previously. Might look into doing an adb pull or backup but being realistic with expectations, I'd say the chances of them working considering what you've done is minimal.

Since you're on stock anyways I'd just go warranty exchange it if you can. Not worth dicking around with Odin if you are stock.

Sorry I couldn't be more help but I would take this opportunity to seriously get yourself a cloud based automatic backup so you don't have to worry about these things anymore. I had something similar happen to me and I lost all my data and now it all syncs to my ex_sdcard and Dropbox haha..can never be too sure
[T-Mobile Galaxy Note 4 Q&A, Help & Troubleshooting] nigafied45:
Yeah I never flashed anything it was an over the air update basically that went bad. The last time I flashed software using odin I didn't lose any of my information it stayed on the internal memory and was there still. It truly is sad they roll out an update over air and it bricks your phone makes no sense.
[T-Mobile Galaxy Note 4 Q&A, Help & Troubleshooting] nigafied45:
I have gotten the phone to turn on randomly it turned on and is now regularly turning on however it is still in a bootloop will not allow me to enter recovery I can enter custom OS have tried to root but it flashes and does not stick with phone for the custom recovery I'm not sure what I can do now that the phone turns on any suggestions?
[T-Mobile Galaxy Note 4 Q&A, Help & Troubleshooting] nigafied45:
When trying to root or enter recovery I get recovery is not Seandroid enforcing set warranty bit recovery and boot loop
[T-Mobile Galaxy Note 4 Q&A, Help & Troubleshooting] Modzilla44:
Have you tried connecting it to kies again to see if it will repair the corrupted flash? If not, Google your bootloader and Odin flash the full stock firmware
[T-Mobile Galaxy Note 4 Q&A, Help & Troubleshooting] nigafied45:
I have a t-mobile 910T note 4. I will try kies again not sure what my bootloader is or was I'm just trying to do what ever i can to preserve the data on phone will flashing stock again delete the internal I know with root with my other note 4 it didn't. This phone was never rooted the over the air update boot looped the phone
[T-Mobile Galaxy Note 4 Q&A, Help & Troubleshooting] Modzilla44:
I would definitely try using kies or even adb from command to see if you can pull the data from it. Flashing a full firmware will wipe all data Yeah so I'd use that as a last resort
[T-Mobile Galaxy Note 4 Q&A, Help & Troubleshooting] nigafied45:
Not to sound stupid what's an adb command