i just flashed my samsung vibrant back to stock from phiredroid(?) (wanting to then install another rom). i am rooted (according to root checker), but my ROM MANAGER app wont open to allow me to flash into recovery. any ideas as to a mistake i made in flashing back to stock or something i need to do (wipe something maybe?)?
vibrant!!! said:
i just flashed my samsung vibrant back to stock from phiredroid(?) (wanting to then install another rom). i am rooted (according to root checker), but my ROM MANAGER app wont open to allow me to flash into recovery. any ideas as to a mistake i made in flashing back to stock or something i need to do (wipe something maybe?)?
Click to expand...
Click to collapse
You accidentally chose something else and you bricked your phone .
Job well done .
Now get it to a service center .
Sent from my GT-S5830 using XDA App
my phone isnt bricked. i can download from market, make calls and texts, my other apps open, i just get a force close every time i try to open rom manager app. i can even get into my android system recovery (volume buttons + power button), but i cant "fix" anything from there that will allow me to get into cwr
EmoBoiix3 said:
You accidentally chose something else and you bricked your phone .
dont know how you got the idea i bricked my phone. i got an updated rom manager this morn and it opens just fine and i can flash cwr now. thanks for scaring me for nothing
Click to expand...
Click to collapse
I own a Galaxy S3 I bought from AT&T. It runs 4.4.2 and it is rooted. I rooted it two weeks ago via Odin and tried to put cyanogenmod on it. Luckily i backed up my phone before all of this happened. I did not know that i already had a cyanogenmod rom already installed on my phone(I am not very experienced with rooting and flashing custom roms). Since i already had cyanogenmod it would not flash and i kept getting an error and an aborted installation error. I did not know that I already had cm on my phone so I ignorantly kept trying over and over again. Then I tried flashing it to AOSP or something which was unsuccessful. I then flashed from clockworkmod recovery to teamwin recovery to see if flashing to Cyanogenmod would work using TWRP. Of course I failed so I wiped the dalvik cache and wiped my phone. When my phone booted up I had no service and it would not recognize my sim card. I have put my sim in other phones and it works completely fine. So iwent to the computer and tried flashing my phone back to its stock rom. Odin could not find the .zip file so I tried installing the zip in my recovery but I was unsuccessful in all of my attempts. In one of my attempts I actually soft bricked my phone but luckily I had a backup on my phone from before I started all of this. I have tried flashing the stock rom from my phone recovery and from the computer and I dont know what to do anymore. When i dial *#06# i get IMEI null/null. I have tried dialing in *#197328640#*and it does not show a menu. I have looked for similar threads and forums but I cant really find anything. My sim card is not recognized and on the google play store it says my phone has no carrier but I still have the MyAT&T app and my phone boots up like an AT&T phone. I looked in the efs file using Root Explorer and checked the carrier file. i found the hidden menu text and it said it is "OFF". Would this be the reason why i cant see the menu after dialing and if so do i need to change it from "OFF" to "ON"?
Sent from my SAMSUNG-SGH-I747
I have viewed a csc changer post and it was for international version only. I have an SGH-I747 I have downloaded the CSC changer app on my phone and it says "PreconfigUI does not support SingleCSC I do not know what this means. I also understand that it could be an efs problem which I do not know how to fix.
Sent from my SAMSUNG-SGH-I747
Use this. I did the same thing.
Unzip this file... read the read me. Use Odin. Dont unzip tge internal zips. Them are for odin.
https://www.dropbox.com/s/8d5jtszqr3i7919/SAVE MY ASS BOOST S3.zip?dl=0
Did that work for you?
No it was fixed before you posted. Thank you for replying though. I had updated Superuser and it updated its binary and installed it with CW recovery and somehow the imei and everything went back to normal. Unfortunately my phone will no longer download or load files (No social media, torrents, or downloading extra files from apps)
Sent from my SAMSUNG-SGH-I747
Hi guys, I just registered @ xda because it looks like it's the only serious and feedback active community available. In 10 minutes I found most of the info I was looking for, but I still want to make sure what Im planning to do is fine before I mess up again. Here's the issue:
I was fooling around with the tablet and had just rooted it so I could get rid of some bloatware, and decided to go further and install cyanogen, just for the looks. So I got this thing cm-10.1-20130411-EXPERIMENTAL-p3110-M3 from the official site, which was I put on a folder inside the tablets storage (not on the 16gb SDcard it had in it). I downloaded Rom Manager and skipped through the "search and download rom" and went for the option of looking for it inside the SD card. I had the Backup options and the wipe cache and data ON.
So I proceeded and it booted, started to do the backup and at some final point it had an error, something like "could not backup Data!". I had the options of rebooting, some other stuff and the option of installing a rom from the SD Card. I went for it and searched for the .zip inside the storage, and installed it. It did it withouth trouble, and when it finishd it prompted me to install an update, which I didn't (don't know why).
Then, I went for the reeboot option and when it started I get the normal samsung's black screen with the device's name on it, but then I get a fast glitching image that sweeps through the screen and the cyanogen startup logo which gets stuck for ever.
Click to expand...
Click to collapse
Now Im past it, I can get to download or recovery mode, so I moved onto getting the original firmware so I can clean-install again. I got it from sammobile, chose the one belonging to Chile (that's where I got the tablet), and it's 729mb of data. The tablet is a Samsung Galaxy Tab 2 7.0 P3110
If I flash it with Odin will everything be fine? All I have to do is that thing in downloadmode when I rooted it, but with that 729mb file? Should I put it in the external SD or is it more convenient to place it in the internal storage?
I appreciate your help in advance, I know this is as basic as it gets but messing up again would cost me dearly, since I have to do other stuff.
forum.xda-developers.com/showthread.php?t=1900055 read here, all the information you will need.
It's fine to flash through odin, you will back at stock provided you don't overlook small details and do exactly like the way it is shown. Don't worry, Don't panic. Just be careful to use the files meant for your device only. Second be extra careful when you are dealing with kernel file, pit file or reparation in odin in future.
Third, get root and custom recovery,twrp.
Fourth, after your device start running take backup from twrp recovery. That will save you from most of the trouble.
Most of the details and instructions are already here
billysam said:
forum.xda-developers.com/showthread.php?t=1900055 read here, all the information you will need.
It's fine to flash through odin, you will back at stock provided you don't overlook small details and do exactly like the way it is shown. Don't worry, Don't panic. Just be careful to use the files meant for your device only. Second be extra careful when you are dealing with kernel file, pit file or reparation in odin in future.
Third, get root and custom recovery,twrp.
Fourth, after your device start running take backup from twrp recovery. That will save you from most of the trouble.
Most of the details and instructions are already here
Click to expand...
Click to collapse
hey thanks a lot, im feeling better ow. There's just one issue left: I cant download the original firmware (it's 699mb, and the download keeps stopping midway through it). What happens if I go into clockwork recovery mode and do a factory reset? would that bring me to the original OS? Im kinda scared of downloading an erroneous file again.
EDIT: im doing a factory reset and then flashing this rom called AOSP Project Android 5.1.1 Lollipop on Samsung Galaxy Tab 2 7.0 P3110 which is a 161mb file. Will that work?
aguscanzani said:
hey thanks a lot, im feeling better ow. There's just one issue left: I cant download the original firmware (it's 699mb, and the download keeps stopping midway through it). What happens if I go into clockwork recovery mode and do a factory reset? would that bring me to the original OS? Im kinda scared of downloading an erroneous file again.
EDIT: im doing a factory reset and then flashing this rom called AOSP Project Android 5.1.1 Lollipop on Samsung Galaxy Tab 2 7.0 P3110 which is a 161mb file. Will that work?
Click to expand...
Click to collapse
Factory reset is just clearing data and cache, if you have made changes in kernel or system, factory reset won't reset them, in your case, system has been altered so you will have to format system, then flash the new rom. If you were on jelly bean stock, you are good to flash it.
billysam said:
Factory reset is just clearing data and cache, if you have made changes in kernel or system, factory reset won't reset them, in your case, system has been altered so you will have to format system, then flash the new rom. If you were on jelly bean stock, you are good to flash it.
Click to expand...
Click to collapse
You guys have helped me a lot. I've worked everything out and now i've got to reinstalling android on it, AOSP's 5.1.1 Lollipop. It's beautiful. There's just one problem: Since it came with no apps at all, I wanted to install everything on it again. Problem is, when I go to google play, it shows that i've already got my apps installed, so it wont let me download them, and it doesn't matter if I place the APK's inside the tablet as there's no manager to open them. Even if I download apk's through the tablet's own web browser, it says it can't open the file. Any ideas on this?
I am stumped! Long story short i have a customers device( i work as an AUTH DEALER for MetroPCS) that had a nasty popup device. One of those imfamous FBI virus asking for money. Completely locked the device. Anyway the customer didnt know gmail and PW so he couldnt master reset. ( i know now he could). I decided to flash the STOCK ROM obtained through Samsung firmware website. I flashed via ODIN. It was a success, no failing at all. The device booted as new phone, apps got optimized and all. BUT the FBI virus was still on the device popping up locking you out, forcing you to remove battery. THIS IS AFTER flashing stock OS directly from the samsung website. So i then decide to master reset thinking the stock ROM would allow me to setup as normal. NOPE. After reset its still requiring the GMAIL and PW to setup the device. I dont understand because the OEM rom was flashed successfully. Yet the FRP lock is still enabled and the device locked out. How do i flash this rom so that it becomes STOCK with no FRP lock??? ANY tips welcome as ive posted in other forums and got no response....:silly::silly::silly:
You should try master reset (wipe partition and wipe cache), then flash a stock ROM via Odin. (Nevermind, I didn't fully read the part you already did that) But to me, this is just another proof that even flashing full ROM via Odin doesn't delete/replace everything. I couldn't get it solved too.
karasahin said:
You should try master reset (wipe partition and wipe cache), then flash a stock ROM via Odin. (Nevermind, I didn't fully read the part you already did that) But to me, this is just another proof that even flashing full ROM via Odin doesn't delete/replace everything. I couldn't get it solved too.
Click to expand...
Click to collapse
i actually resolved this issue. and yes flashing via ODIN doesnt reset it to default. I used sidesync, got a settings apk, used sidesync to force the device to open samsung apps(like the play store) i then got a file manager and added the apk to the phone storage via a computer.(this was all done while on the google login screen) i then opened the filemanager , installed the settings apk, it took me to phone settings(without having to get past the initial sign in screen) i then did a master reset via phone menu and BOOM, device is stock. Never will i put this much effort into a 50 dollar device again haha but thanks for the response
CorporalCactus said:
i actually resolved this issue. and yes flashing via ODIN doesnt reset it to default. I used sidesync, got a settings apk, used sidesync to force the device to open samsung apps(like the play store) i then got a file manager and added the apk to the phone storage via a computer.(this was all done while on the google login screen) i then opened the filemanager , installed the settings apk, it took me to phone settings(without having to get past the initial sign in screen) i then did a master reset via phone menu and BOOM, device is stock. Never will i put this much effort into a 50 dollar device again haha but thanks for the response
Click to expand...
Click to collapse
Wow! Very nice to hear, well done!
I've got a rooted S7, apps backed up with Titanium Backup, etc.
Is there anything I need to know about getting this transferred over to a Pixel, which will presumably be running Oreo or Pie? I'd certainly like to take the opportunity to upgrade; I'm still on MM on the S7 mostly because it's just hassle to reflash the ROM (running Superman ROM, not stock).
I assume Nova Launcher will come across okay? What about things like Good Lock? It presumably won't work, but will it break anything or will I need to remove it from my backups before restoring?
Titanium allows me to create a zip of all my backups. Do I just flash that in TWRP? I don't think it's used from within the app itself, is it?
Any ROM recommendations? I use GravityBox so something AOSPish would be ideal, Pie would be awesome but I'd settle for Oreo. I'm not sure what Pie's release status is at the moment - I didn't think it was out yet but it seems to be. This is a very rushed thing (the S7 just stopped working and will be too expensive for repair to be worthwhile), so everything's very scrambled in my head at the moment and I'm just throwing thoughts out there, largely. EDIT: Actually, I assume Xposed and such aren't set up for Pie yet? If so Oreo would be the way to go.
Since I have GMail and such installed as user apps, not system apps, and backed up as such, I'm assuming I'll need to find a way to arrange the same with the Pixel? Superman ROM offers the option to install those apps or not through the Aroma installer.
Does anyone have any input on this?
I'm also curious as to the differences between rooting with/without tripping SafetyNet. I'm assuming there are some, or everyone would do the latter?
Do you have your Pixel, yet? Unlock the bootloader, install the latest factory image, use the latest TWRP & Magisk (do it properly, & a SafetyNet check will pass). When your phone is booting up fine and rooted, we can talk about transferring data.
I don't, but it should be arriving today. I like to be prepared, rather than getting into a situation where I have the phone and want to get everything sorted immediately, only to end up rushing and causing issues. I think I was reading and asking questions about two weeks ahead of my purchase of the S7. As I said, I'm replacing the S7 due to a fault, and I've been without it for a couple of weeks now, so the more I can get my head around before it arrives and I get all "OMG do everything immediately", the better.
If you really need Xposed, you can install a Magisk version of Xposed. Personally, I am no longer using Xposed; Magisk gives me root, and I can install all the modules I need.
Do you have the Pro version of Titanium Backup? You have to jump through some hoops to get it to recognize your Pro key. I would just transfer your entire backup directory to the backup directory on your new phone, then use the app to select which apps to restore. Do the app restores in waves, to help you narrow down a problematic restoration.
Even if you already have the latest version of Android installed on the Pixel, download the full factory image so that you can extract the boot.img file from it. Flashing the stock boot.img can get you out of most bootloops. Here's some reading material to help you understand what has changed.
Personally, I'm happy with the stock ROM, rooted. I suggest you look at Tulsadiver's mod. It has some sorely needed customization options.
:good:
post-mortem said:
If you really need Xposed, you can install a Magisk version of Xposed. Personally, I am no longer using Xposed; Magisk gives me root, and I can install all the modules I need.
Click to expand...
Click to collapse
So Xposed modules work in Magisk? Or....? I have GravityBox for notification control, as I find the default LED blink speed too low and like to change the sound/LED colour on a per-app basis far more than the apps themselves allow, along with Unbeloved Hosts, MinMinGuard, Airplane Mode Helper, Screenshot Delay Remover, Secure Settings, XToast and YouTube AdAway.
Do you have the Pro version of Titanium Backup? You have to jump through some hoops to get it to recognize your Pro key.
Click to expand...
Click to collapse
I do. There's an option to just create a flashable install of Titanium, and to back up its settings, which is what I've always done in the past. Is this different now?
EDIT: Which guide do I follow to install TWRP and Magisk? I thought this would be the go, but reading through it requires a custom ROM to begin with.
I followed this guide. I really don't know if it's actually necessary to uninstall com.android.phone, though I did it. The command you'll want to use to unlock the bootloader is fastboot flashing unlock, as stated at the top of this Google page.
If the enable OEM unlocking option under developer settings remains grayed out, you might have to get out of the settings and reenter them, restart your phone, or even reflash and start all over. For some reason, a number of people have reported that executing the command am start com.android.chrome in a terminal or adb shell allows the OEM unlocking options to become toggleable.
post-mortem said:
I followed this guide. I really don't know if it's actually necessary to uninstall com.android.phone, though I did it. The command you'll want to use to unlock the bootloader is fastboot flashing unlock, as stated at the top of this Google page
Click to expand...
Click to collapse
Why "flashing" and not "oem"? And then how do I install TWRP? The page you linked to has "install" zips and normal zips, not sure which I'm meant to download.
EDIT: Phone arrived, and is running 7.1.2.
Read the top of the Google page with the links to the Factory Images.
TWRP is temporarily booted using a PC with fastboot boot <TWRPfilename.zip> . Once you're in TWRP, you install the TWRP installer zip like any other zip. So the .img file stays on your computer (fastboot will load it onto your phone and boot into it), and the .zip goes on the phone so that you can install the TWRP installer.
post-mortem said:
TWRP is temporarily booted using a PC with fastboot boot <TWRPfilename.zip> .
Click to expand...
Click to collapse
Should that be the .img file, not the .zip file? Just guessing from context, otherwise you're using the zip file twice and the img file never.
So:
Unlock bootloader
Flash TWRP
Use TWRP to flash TWRP
Use TWRP to flash Magisk
Yes?
EDIT: Wait, that doesn't include flashing the system thing. When and how do I do that?
Unpopular opinion, but...
If I were you I would just use the phone as it is for at least a couple of days.
I don't want to sound like a Pixel fanboy but I'm liking the stock firmware much better than any custom ROM on this phone.
Of course I'm rooted and running a custom kernel, but I'm positive that Magisk will have the answers to most of your modding needs.
You got a new phone, why go out of your way and risk messing up stuff just to make it feel like your old one?
I mean, I'm cool with stock in theory, I just liked the debloated ROM I had last time because, well, debloating. And GMail and YouTube and such are now user apps on the S7, so my backups treat them as such.
Where do I find the drivers? I installed an "adb setup" thing that claimed to have them, but my PC isn't recognising the Pixel. Google's links to OEM drivers include a bunch of brands that aren't Google, so I'm not sure what to download.
EDIT: Okay, got it. Now running Android 9. When I'm installing TWRP, do I need to wipe anything? I miss the S7 forums and their one clear rooting guide that went step by step through everything.
koberulz said:
I mean, I'm cool with stock in theory, I just liked the debloated ROM I had last time because, well, debloating. And GMail and YouTube and such are now user apps on the S7, so my backups treat them as such.
Where do I find the drivers? I installed an "adb setup" thing that claimed to have them, but my PC isn't recognising the Pixel. Google's links to OEM drivers include a bunch of brands that aren't Google, so I'm not sure what to download.
EDIT: Okay, got it. Now running Android 9. When I'm installing TWRP, do I need to wipe anything? I miss the S7 forums and their one clear rooting guide that went step by step through everything.
Click to expand...
Click to collapse
No. just fastboot twrp img > flash zip via booted twrp. Reboot to system. That's all you gotta do
How do I boot into TWRP once installed? And come to that, what's the point of installing if I can boot to it regardless?
koberulz said:
There's an option to just create a flashable install of Titanium, and to back up its settings, which is what I've always done in the past. Is this different now?
Click to expand...
Click to collapse
Okay, this seems not to work. I've tried flashing it and there's no sign of the app at all.
koberulz said:
How do I boot into TWRP once installed? And come to that, what's the point of installing if I can boot to it regardless?
Click to expand...
Click to collapse
Doesn't the command fastboot boot twrp.img just boot it?
It does that for me, then I just have to flash twrp pixel installer.zip and it sticks.
I do this every time I update my factory image (which resets recovery to stock)
Anyways, I'm in. Had to manually install TB, then restore all my backups...and it screwed everything up big-time. Contacts are horribly broken; they initially kept crashing and now it says there's no contacts app installed. GMail crashes every time I open it. And the vibration has been replaced with a quiet beep.
I expected that... Just reflash latest factory image
Look, don't restore any apps, yet, especially any apps made by Google. You shouldn't need to restore any data, as all Google info is in the cloud, anyway. Just launch the app and log in to your Google account.
You don't need to "permanently" install TWRP if you don't want to.
I don't use Drive, so no it isn't.
I've managed to get everything over except my contacts. They killed it last time so I'm disinclined to try again. Not sure how else to get them over though.
My S7 had an "only display contacts with a phone number" option, does Pixel have an equivalent?
Since I don't have Xposed, I don't have any of my ad blockers. Are there options available?
I also had a lock screen with a tray of apps I could drag up to unlock straight into that app, the clock on the right instead of the left, and a percentage instead of just a battery icon on the lock screen and without swiping down. Any way I can set that up?
I tried Light Flow, but it doesn't seem to be working, I'm not getting any LED lights. It was working fine while I was setting up last night, but I unplugged the phone to go to bed and it's stopped.
I've looked at that Pie Aroma Mod Installer thing, but there's three files offered for download and I'm not sure what they are?
Is there a way to stop the screen turning on and the phone making a sound when I plug/unplug it?