Related
Hello All,
I am a beginner to all this stuff. I wanted to root my phone after seeing OnePlus One running on CyanogenMod. So, first I tried to directly install the Mod using the softwares downloaded from Cyanogen's website. But the software gave the error "Unsupported Firmware". Then I researched a bit on manually installing the mod. I followed the instructions.
- First I rooted my phone with Odin 3.09v
- Installed ROM Manger on my phone (Meanwhile the SuperSU app kept on crashing)
- Somehow I managed to install ClockworkMod (What I did was downloaded SuperSU apk, installed it again. It started working and then, not losing the chance I installed ClockworkMod).
- Then I tried to install CyanogenMod through ROM Manager
- My phone re-booted and then gave a error "Can't install package on incompatible data".
- I'm having the latest snapshot version on CyanogenMod.
- Then I left the things as it is. No rooting, unrooting, etc.
- So, now I tried to take backup of my current ROM, in case something happens at least I'll be having something with me to recover
- I used ROM Manager to take backup. But it gave the error "Can't create the image"
So, now I'm stuck between middle of nowhere. Please help me out to reach to some point.
svikramajit said:
Hello All,
I am a beginner to all this stuff. I wanted to root my phone after seeing OnePlus One running on CyanogenMod. So, first I tried to directly install the Mod using the softwares downloaded from Cyanogen's website. But the software gave the error "Unsupported Firmware". Then I researched a bit on manually installing the mod. I followed the instructions.
- First I rooted my phone with Odin 3.09v
- Installed ROM Manger on my phone (Meanwhile the SuperSU app kept on crashing)
- Somehow I managed to install ClockworkMod (What I did was downloaded SuperSU apk, installed it again. It started working and then, not losing the chance I installed ClockworkMod).
- Then I tried to install CyanogenMod through ROM Manager
- My phone re-booted and then gave a error "Can't install package on incompatible data".
- I'm having the latest snapshot version on CyanogenMod.
- Then I left the things as it is. No rooting, unrooting, etc.
- So, now I tried to take backup of my current ROM, in case something happens at least I'll be having something with me to recover
- I used ROM Manager to take backup. But it gave the error "Can't create the image"
So, now I'm stuck between middle of nowhere. Please help me out to reach to some point.
Click to expand...
Click to collapse
Ok, first I think your SuperSu is not working properly. Open the Supersu app to see if it needs to update binaries. If it continues to crash, go into recovery manually (not using rom manager) and flash the latest SuperSu. Wipe Cache, go to advanced and Wipe Dalvik. Reboot. Your phone will say "android is upgrading" for a bit. Once it's booted up, go back into the supersu app and see if it needs to update binaries, if so- let it update, if not- move on. Here's a link to download SuperSu 2.02
Go back into recovery manually and select backup and restore-> backup to sdcard (or sdcard1, external sd, is my preference) This will start the backup process.
Once that is done, you need to find the CyanogenMod file specific to your phone, then you can enter recovery and flash it.
If you have trouble entering recovery, you can flash a new one via recovery or with odin.
Hello absinthesummer,
I followed every instruction you told. Now I'm done till creating backup. The problem now I'm facing is this 'Status 7' error. It says "Can't install package on incompatible data.....". Now what to do?
Status 7 is a very specific error. It means your recovery is out of date. Get the absolute newest you can find and try again. This is good news though, you've got progress!
---------- Post added at 11:48 AM ---------- Previous post was at 11:46 AM ----------
Edit: flash the latest recovery you can find via Odin. You probably won't be able to do it in recovery while you're getting the status 7 error.
absinthesummer said:
Status 7 is a very specific error. It means your recovery is out of date. Get the absolute newest you can find and try again. This is good news though, you've got progress!
---------- Post added at 11:48 AM ---------- Previous post was at 11:46 AM ----------
Edit: flash the latest recovery you can find via Odin. You probably won't be able to do it in recovery while you're getting the status 7 error.
Click to expand...
Click to collapse
No, I've got the latest recovery. But I figured out the problem. It was with the package I downloaded. The CM 11 M9 version was giving errors. I researched and tried few fixes, but still it didn't work.
The fixes I tried :-
1. Deleting some coding lines from the updater-script file. But this fix gave the status 6 error.
2. Changing the updater-script file format to UNIX format. Then again it gave the status 7 error.
So, what I did, when I had no more brain to fix it, I downloaded the CM 11 M6 version and tried installing it. And VOILA! It worked. Then I updated it to M9 version through phone. Now it's working. Though it has some bugs. And some features are missing too that I wanted badly.
svikramajit said:
No, I've got the latest recovery. But I figured out the problem. It was with the package I downloaded. The CM 11 M9 version was giving errors. I researched and tried few fixes, but still it didn't work.
The fixes I tried :-
1. Deleting some coding lines from the updater-script file. But this fix gave the status 6 error.
2. Changing the updater-script file format to UNIX format. Then again it gave the status 7 error.
So, what I did, when I had no more brain to fix it, I downloaded the CM 11 M6 version and tried installing it. And VOILA! It worked. Then I updated it to M9 version through phone. Now it's working. Though it has some bugs. And some features are missing too that I wanted badly.
Click to expand...
Click to collapse
Awesome! I'm glad you got it working. You can also try comparing the two files to see what's different, or maybe swap the updater script. Maybe you'll be able to get the one you wanted working with a little modification
absinthesummer said:
Awesome! I'm glad you got it working. You can also try comparing the two files to see what's different, or maybe swap the updater script. Maybe you'll be able to get the one you wanted working with a little modification
Click to expand...
Click to collapse
Thanks to you. You too helped me in working it out!
But, I have some more questions
Question 1 : If I flash stock ROM on my rooted phone, will I receive the new updates? If yes, will I be able to install them via Kies on my phone without getting into any trouble?
Question 2 : If I install stock ROM of any other phone, say Galaxy S5, will it work on my phone properly without any problems? If yes, will I receive the updates for that too and able to install them via Kies? If no, is there any way to install it? Cause I have seen people using S5 ROM on Note 2.
First question the answer is yes. As long as you have the stock recovery and stock kernel (along with the stock rom) you will receive ota updates. You can use ota root keeper (an app) to keep root during an ota update. There are many people who choose to stay fully stock but root to get rid of bloatware & stuff. However, if you want to get ota, I recommend freezing the bloatware instead of uninstalling, because an ota usually replaces old bloatware with new bloatware and can sometimes abort the ota if those apps are missing... but keep on mind this is not always the case, only certain devices.
Second question, no you cannot. Roms from other devices have to be ported to be compatible. But if you look in the development forums, you can find many roms that are basically stock but have specific features from other roms, along with the system ui (ie S5, note 3, & so forth). These rom devs have ported either parts/features or full on roms to be compatible on our device. They are excellent! I recommend reading up them and if you see some you like, try them out!
absinthesummer said:
First question the answer is yes. As long as you have the stock recovery and stock kernel (along with the stock rom) you will receive ota updates. You can use ota root keeper (an app) to keep root during an ota update. There are many people who choose to stay fully stock but root to get rid of bloatware & stuff. However, if you want to get ota, I recommend freezing the bloatware instead of uninstalling, because an ota usually replaces old bloatware with new bloatware and can sometimes abort the ota if those apps are missing... but keep on mind this is not always the case, only certain devices.
Second question, no you cannot. Roms from other devices have to be ported to be compatible. But if you look in the development forums, you can find many roms that are basically stock but have specific features from other roms, along with the system ui (ie S5, note 3, & so forth). These rom devs have ported either parts/features or full on roms to be compatible on our device. They are excellent! I recommend reading up them and if you see some you like, try them out!
Click to expand...
Click to collapse
- Stock Recovery
- Stock Kernel
- OTA Root Keeper
- Bloatware
Well, to be honest, just right now I learned these new terms but know nothing about them. Can you please give me a brief description for these four terms so that when I do advanced search on them, I'd have a idea in my mind about what these are. It will make it easy for me to understand the advance things.
And I'm looking for S5 ROM for my phone. Let's see what I get.
One more question. I made a backup of my rooted stock ROM via latest ClockwordMod, manually. Now, if I reset the binary counter using Triangle Away and then wipe Cache and Dalvik and then flash my stock ROM which is located on my memory card and then after flashing I use SuperSU to unroot and then a factory reset (I don't know the method of factory reseting cause I'm confused. Whether to do it manually, like going into recovery mode or just from the phone settings. So please tell me this also.), will my phone be unrooted totally?
And sorry for bugging you so much. I hate to do that, but I don't want to take risk with my phone. So I am just collecting information. I hope so many queries are not a problem for you.
Ok...
You already know what a rom is. A kernel is a lower-level base. It controls the hardware. So when you do something on the interface, in the rom, it tells the hardware how to react. (Ie if you're playing music it tells which speakers to play and how loudly). The kernel controls almost everything you can't see, it relates to performance. Most stock kernels can be limiting as they underclock the cpu by a certain percentage. Because of this, people seek out custom kernels to max out their device's potential. Louder speakers, faster cpu, better graphics, etc. This is all stuff the kernel can optimize... but because you can change so many factors there is a risk of instability if you push your device too hard (max performance) or limit it too much (max battery saving).
Recovery is exactly what it sounds like. When you boot your device the very first screen that pops up is the bootloader. It's giving you time to boot in 3 different modes. The first mode, by doing nothing, is a normal boot into the rom/OS. The second mode, which you get to by one button combination, takes you to recovery. The stock recovery is very limited. It gives you the option to factory restore, wipe cache, update, or boot normally. Stock recovery only exists for emergencies, if your phone fails to boot normally. We have custom recoveries so we can do more stuff, flash custom roms and tinker with things. The third mode is download mode/Odin mode. This is the bootloader interface itself. It's the last resort for recovery if your recovery has been damaged or corrupted. It allows you to connect to Odin or kies and perform an emergency recovery of the device. If you damage your bootloader, your device is completely bricked.
So the order of operation is this:
Lowest level- bootloader
Second level- recovery
Third level- kernel
Fourth level- rom
Bloatware is all the pre-installed apps that your carrier adds to your phone. Most people don't use it, don't like it, and don't want it. That why we root. Without root we basically are just guest users of the device. With root we become the administrators of the device. Until you root, your carrier has admin rights over your phone (to use windows terms).
When you receive an ota update, your carrier can make it to where the update won't proceed if their pre-installed apps have been removed (although this isn't always the case). Additionally, the update package itself checks the integrity of the device. It checks recovery, kernel, and rom. If any have been altered, it will not proceed because it could cause conflict and potentially brick your device. That's why those things have to be stock.
Ota root keeper is simply an app that backs up your superuser rights before an update and restores them after its done.
You should be able to find plenty of roms with S5 features. I'm using one that makes my device fully like an S5 (my device even thinks it is an S5 and every app identifies it as such) I can think of at least 2 others as well. There's plenty to choose from, and if you see a rom you like but it's mudding a particular feature, you can probably find that feature as a stand-alone installation in the forum's themes & apps section. Just about every feature of S5, S4, and note 3 has been ported to this device, so look around!
Also, for future reference, if someone helps you on the forum, hit the thanks button instead of saying it. I don't mind either way, but some people get annoyed and will stop helping them if they don't hit that button lol. It's silly, but it's part of "forum decorum"
---------- Post added at 12:54 AM ---------- Previous post was at 12:44 AM ----------
svikramajit said:
One more question. I made a backup of my rooted stock ROM via latest ClockwordMod, manually. Now, if I reset the binary counter using Triangle Away and then wipe Cache and Dalvik and then flash my stock ROM which is located on my memory card and then after flashing I use SuperSU to unroot and then a factory reset (I don't know the method of factory reseting cause I'm confused. Whether to do it manually, like going into recovery mode or just from the phone settings. So please tell me this also.), will my phone be unrooted totally?
And sorry for bugging you so much. I hate to do that, but I don't want to take risk with my phone. So I am just collecting information. I hope so many queries are not a problem for you.
Click to expand...
Click to collapse
You're fine, I don't mind answering your questions. Yes, you can unroot fully in the way you just mentioned but you don't even have to go through all the trouble of factory reset. Just unroot in the app. The app can be uninstalled afterwards via the play store.
You can factory reset either way, the same commands are given no matter which way you go about it. But it can be more efficient to do it from recovery because when you do it from the rom it has to create a wipe script for when it reboots, and it has to shut down the rom first. If you do it from recovery it doesn't have to anything, the rom isn't running and it can execute the wipe command immediately. (The wipe command is wipe /data /cache etc)
Thanks again for all that great info!
Questions : Is there no way to fix the Bootloader if it gets damaged by chance? And which S5 ROM are you using?
svikramajit said:
Thanks again for all that great info!
Questions : Is there no way to fix the Bootloader if it gets damaged by chance? And which S5 ROM are you using?
Click to expand...
Click to collapse
If you damage the bootloader it's a hard brick and you would have to send it in for jtag services (this is a low level emmc chip flash service) The bootloader won't get damaged unless you do something to corrupt it. If you ever feel the need to flash a new bootloader, do it via Odin, never recovery! If you remember that you should be fine.
svikramajit said:
Thanks again for all that great info!
Questions : Is there no way to fix the Bootloader if it gets damaged by chance? And which S5 ROM are you using?
Click to expand...
Click to collapse
I meant to tell you I'm using DN3 rom. It has an aroma installer that lets you choose whether you want an S5 ui, a note 3 ui or a mixed ui. Choosing S5 ui & S5 build prop allows your device to work with S5 apps & it looks just like an S5. It's not the only rom out there, but it's beautiful, fast, and stable & the team works hard on it.
absinthesummer said:
I meant to tell you I'm using DN3 rom. It has an aroma installer that lets you choose whether you want an S5 ui, a note 3 ui or a mixed ui. Choosing S5 ui & S5 build prop allows your device to work with S5 apps & it looks just like an S5. It's not the only rom out there, but it's beautiful, fast, and stable & the team works hard on it.
Click to expand...
Click to collapse
Hey absinthesummer!
I tried to unroot my phone with the method I told you. But in the restore option, I am stuck at 'Checking MD5 Sums..'. What to do now?
MD5 checking takes forever! You have to wait it out. Most recoveries offer a way to turn it off. You shouldn't have to factory reset though, just click unroot in the super su app and then uninstall the app from the play store.
absinthesummer said:
MD5 checking takes forever! You have to wait it out. Most recoveries offer a way to turn it off. You shouldn't have to factory reset though, just click unroot in the super su app and then uninstall the app from the play store.
Click to expand...
Click to collapse
I waited and the system was restored. But I got an error on 'Restoring Data'. I rebooted the phone and now it's showing glowing Samsung logo from like 3-4 minutes.
I've seen that before. Can you get back into recovery? You may have to flash stock in Odin, flash recovery and then do the Restore again. Data got messed up.
absinthesummer said:
I've seen that before. Can you get back into recovery? You may have to flash stock in Odin, flash recovery and then do the Restore again. Data got messed up.
Click to expand...
Click to collapse
I'll try removing the battery now. Let's see what happens.
Ok if you can get into recovery, do a fresh flash and then try to restore again. And see if it offers a way to turn off MD5 checking. That's why I use philz or twrp, they offer that and move much faster through MD5 check by default.
---------- Post added at 11:13 AM ---------- Previous post was at 11:12 AM ----------
If you still fail on data, flash stock in Odin, flash custom recovery, then you should be able to enter recovery and have a successful restore.
I bought this tablet about a week ago. It's WiFi 16gb. A few days ago I rooted it via CF-autoroot, installed TWRP and SlimKAT. Everything went great started setting the Tab up. I was messing around with it last night and Supersu is gone and it appears I have lost root. I can't install the binaries or anything. The tablet hasn't been powered off. The only thing I know that's been done is updates via Play Store. Honestly I'm at a loss and any input would be great.
Wasn't aware I needed to reflash SuperSU via TWRP afterwards. For anyone in the same boat all I did was grab the latest stable SuperSU and flash it. All good now.
Its a bit confusing, on Slim (and CM is the same way) the ROM is pre-rooted as you would expect, but disabled by default. To enable, go to Settings>Developer Options, and enable root there. If no Dev Options, go to Settings>About>Software information, and tap Build Number enough times (7 times?) until it tells you Dev Options is enabled.
redpoint73 said:
Its a bit confusing, on Slim (and CM is the same way) the ROM is pre-rooted as you would expect, but disabled by default. To enable, go to Settings>Developer Options, and enable root there. If no Dev Options, go to Settings>About>Software information, and tap Build Number enough times (7 times?) until it tells you Dev Options is enabled.
Click to expand...
Click to collapse
AHH....that is helpful. I will look at that tonight. Is this something specific to the SM-T320? I have worked with many roms and many devices and haven't seen this before.....I've been doing this process below each time I install a new CM.....kinda painful and was about to ask about "why"? [Samsung seems a lit more difficult then HTC/LG/Google devices] [Literally just enable root and everything else (including TWRP) will work?]
Every time you update Cyanogenmod.... [you lose root]
1. Reflash 'CF-Auto-Root-mondrianwifi-mondrianwifixx-smt320.tar.md5' in Odin.
2. Reboot (remove cable or it won't boot correctly)
3. Open up SuperSU and update binary (normal)
4. Reboot
5. Reflash '' in Odin.openrecovery-twrp-2.X.X.X-mondrianwifiue.img
6. Reboot (remove cable or it won't boot correctly)
Rezinator said:
I've been doing this process below each time I install a new CM
Click to expand...
Click to collapse
As I previously mentioned, the process I described (enable root in Settings) also applies to CM, in addition to Slim ROMs. No need to flash CF Autoroot with Odin to obtain root.
I did the same thing the first time I flashed Slim. Then I read somewhere on the SlimROMs website how to obtain root after flashing the ROM.
I believe its a feature of the ROMs, not the device. I agree it seems counter intuitive, that root would not be enabled by default on a custom ROM. But I'm sure the devs have their reasons (likely for security of the user).
This happens on my galaxy s3 now and again. It used to be when using a custom recovery that wasnt official. Twrp causes issues with preload. Since using an official custom recovery (cwm touch) from the proper website my phone is stable so far.
My guess is the custom non official recoveries cause it.
Sent from a stolen phone!
I currently have a T-Mobile HTC One M8.
I am running 4.4.4 with Sense 6.0
It is rooted, custom recovery (TWRP), S-OFF, with Xposed Framework installed.
I know this has been asked and discussed a million times in bits and pieces around XDA and the internet in general, but I am still having trouble finding one source with a definitive answer as to the steps I should follow.
I would like to update to Android Lollipop 5.0 (5.0.1)
- The OTA that has shown up on my phone as of now is Software Update: 4.20.531.4 (632.7 MB). I am not sure if there is already another one that would follow this one if I were able to successfully update to this version.
With that being said, I did not make a backup of my stock rom, nor recovery.
I am assuming that the process I need to take is this (to return my device to stock):
1) Uninstall XPOSED Modules and XPOSED Framework
2) Flash a STOCK ROM via custom recovery (TWRP)
3) Flash a STOCK RECOVERY via custom recovery (TWRP)
- Is this correct?
- If so, can someone provide me a link to the STOCK ROM and STOCK RECOVERY that I would need?
- If not, what are the steps I should follow?
Then what do I need to do to update my device to Lollipop?
Do I just refresh and check the software update in the ABOUT section of settings and update it as an OTA?
Can I skip all of these steps and just flash a factory LOLLIPOP IMAGE and RECOVERY via ADB with my device in it's current state?
Thank you in advance to anyone who will help me out
-----
UPDATE...
-----
*** I finally updated to Android Lollipop 5.0 (5.0.1)
This is what I did:
* I kept my device plugged into my computer this entire time
1) Download this STOCK ROM zip (TMOUS-M8-3.32.531.2-Stock-TWRP.zip)
2) Download this STOCK RECOVERY img (Tmo-M8-3.32.531.2-recovery.img)
3) Download this OTA zip (OTA-3.32.531.2 to 4.20.531.4)
4) Backup CURRENT ROM via TWRP (just in case)
5) Extract the files from STOCK ROM zip and place them in a folder named STOCK ROM
6) Move the STOCK ROM folder to your device under |sdcard / TWRP / BACKUPS / "random numbers & letters" / Place the folder here|, next to your CURRENT ROM backup
7) Move the OTA zip to your device under |sdcard / Download|
8) Move the STOCK RECOVERY img to whatever folder you have ADB (fastboot) setup in, on your computer
9) Reboot into TWRP, click restore, select STOCK ROM, then swipe to restore
10) After it finishes restoring, do not reboot. Just click back until you can select reboot, then select to reboot bootloader
11) Once it reboots to the bootloader and you are at the screen where it says FASTBOOT, open ADB (fastboot) command prompt and flash the STOCK RECOVERY img by typing: fastboot flash recovery "name of recovery".img
12) Once that has completed, reboot the device
13) Once the device has rebooted open ADB (fastboot) command prompt again and reboot into recovery by typing: adb reboot recovery
14) For me, it rebooted to a black screen, then turned into a black screen with a warning triangle, then I hit the volume buttons a few times as well as the power button and then it loaded up the recovery options (sounds weird, but this is how it happened for me)
15) Once the options appear, use the volume and power buttons to select apply from phone storage, then locate the OTA zip file that you moved into the Download folder, select it and hit the power button to apply it
16) Let it run and apply the update, then follow the instructions at the end to reboot the phone
17) Now you will have Android Lollipop 5.0 (5.0.1) on your device
*** When you apply the OTA zip, it will sit at "patching system files" for quite a while, so don't worry. Applying the OTA took around 15 minutes to complete for me
*** I never wiped data or cache or anything like that during this entire process. All my apps, settings, etc... remained how I had them before. I didn't have to set anything up after the final reboot. Everything was just like I had had it on my CURRENT ROM
*** I never uninstalled XPOSED Modules or XPOSED Framework, or unrooted the device. I simply did all the steps I just listed. Nothing else.
*** Of course after completion of this update process you will lose root, and would have to re-root and re-install XPOSED (which is possible now that XPOSED is compatible with Lollipop)
I would also like to know...
It's somewhat old, but the instructions using Method #1 more or less apply. Just make sure that when/if you reflash TWRP that you flash 2.8.5. Nothing older.
http://venomroms.com/viperonem8_3-0-0-requirements/
This is of course irrelevant to the OP, but for anyone who's still considering the move, my advice would be not to "update". I see absolutely no advantage of Lollipop in comparison to KitKat, at least as long as stock Sense 6 phones are concerned.
I have a completely stock, unrooted (although not SIM-locked) HTC One M8. A few weeks ago the OTA came and I "updated". Now, my phone worked perfectly before: fast, on battery for more than 2 days, etc. After the "update" there where problems after problems after problems. The keyboard lags, the battery life is way worse, etc. Yes, some of the problems can be overcome. But in my opinion if you just want a working phone, this "update" is simply not worth your time.
unifex_ said:
This is of course irrelevant to the OP, but for anyone who's still considering the move, my advice would be not to "update". I see absolutely no advantage of Lollipop in comparison to KitKat, at least as long as stock Sense 6 phones are concerned.
I have a completely stock, unrooted (although not SIM-locked) HTC One M8. A few weeks ago the OTA came and I "updated". Now, my phone worked perfectly before: fast, on battery for more than 2 days, etc. After the "update" there where problems after problems after problems. The keyboard lags, the battery life is way worse, etc. Yes, some of the problems can be overcome. But in my opinion if you just want a working phone, this "update" is simply not worth your time.
Click to expand...
Click to collapse
Have you factory reset your device after the update? I'm 100% stock, not rooted (although S-OFF) and it lasts well over a day but I always factory reset after every major update
EddyOS said:
Have you factory reset your device after the update? I'm 100% stock, not rooted (although S-OFF) and it lasts well over a day but I always factory reset after every major update
Click to expand...
Click to collapse
Yes, I did the factory reset. Strangely enough (although perhaps not so strangely) the reset kept the data of old apps. For example, I had some navigation app that downloaded lots of maps. The app is gone, but the maps are still there, even after the reset. They are just a dead weight now, with no way of accessing them - although I'm not sure whether I will be able to access them if I reinstall the app. Same with dictionaries.
The battery life got a bit better lately, perhaps after the Google Services update. But it's still not as good as it was on KitKat.
And finally, shouldn't the update bring improvements? So far we've been talking about issues and how to deal with them. I honestly have not seen any single improvement over KitKat. Perhaps something "under the hood", but then I would expect the phone to be more responsive, not lagging. So looking back, I just don't see what was the point of this update. Maybe with Sense 7 ...
So I wanted to root this tablet, and I used a video online to help me do so.
I installed the USB drivers, got Odin 3, and loaded in CF_AutoRoot_Port_T700_BeansTown106.tar
It rooted my tablet and I was pretty happy about that. I then had update supersu, by getting the SU binaries.
So I came to this site and downloaded the recommended Supersu, and flashed it. It fixed that.
Well, then I wanted to get a custom ROM, so I flashed the Cyanogenmod 12, along with the component with it.
I found I didn't like it compared to my 5.0.2 Lolipop, and so I tried finding the stock ROM.
The gator download site everyone was showing refused to let me download anything, and just about all the ROMS seemed like they were from countries other than the U.S.
I searched for awhile, found nothing, then found a ROM called the Ironman Lolipop ROM, it was close enough to stock, so I flashed it.
Suddenly everything was normal, but then supersu needed binaries again, and after I flashed it again, it just stopped asking if it should grant permission, making the root useless.
Frustrated, I looked online again for ROMS, found a Canada one, decided to download, it would take two hours.
Well I'm not from Canada so I doubted it would work, and didn't want to wait two hours.
I decided to Flash back the Cyanogen.
Well unfortunately I went in and found out that I had deleted it earlier, whoops. And so my data wipe brought me back to Ironman ROM.
So, thinking that flashing to Iron Man screwed up my root I tried to re-root with Odin, the same way as the first.
It then had trouble booting, and when it did, it hung at the Samsung logo.
Now I've been stuck on this logo for about an hour, I can't turn it off. I'm assuming the only way to is to wait for it to run out of power.
I have been using TWRP this whole time.
I twice have backed up, and wiped data.
When I hit restore I saw no backups though, I'm not sure if they were for the ROM?
I don't know, I only have a year of experience.
Edit: I have an 8.1" T700 from Amazon.
pennylessz said:
So I wanted to root this tablet, and I used a video online to help me do so.
I installed the USB drivers, got Odin 3, and loaded in CF_AutoRoot_Port_T700_BeansTown106.tar
It rooted my tablet and I was pretty happy about that. I then had update supersu, by getting the SU binaries.
So I came to this site and downloaded the recommended Supersu, and flashed it. It fixed that.
Bla bla ......
Click to expand...
Click to collapse
Hi! To force reboot while in a soft brick, press and hold power+home button+ both volume buttons all at the same time.
Then when the screen goes black, quickly press the odin\download mode button combo or recovery comba if you wish.
Luckily, I have mirrored the latest firmware for the T700 to a faster hosting site. This is an UK firmware and is the latest one. It should flash fine as I have flashed different firmwares from different countries many times.
Download Firmware (fast download): https://www.androidfilehost.com/?fid=24052804347761130
Now, ironrom has problems with root sometimes. When I make roms I don't preroot them as they cause problems of binaries if you preroot them. Anyway feel free to flash the firmware with odin or load an custom ROM to your sd card and flash it.
Hope this helps!
DUHAsianSKILLZ said:
Hi! To force reboot while in a soft brick, press and hold power+home button+ both volume buttons all at the same time.
Then when the screen goes black, quickly press the odin\download mode button combo or recovery comba if you wish.
Luckily, I have mirrored the latest firmware for the T700 to a faster hosting site. This is an UK firmware and is the latest one. It should flash fine as I have flashed different firmwares from different countries many times.
Download Firmware (fast download):
Now, ironrom has problems with root sometimes. When I make roms I don't preroot them as they cause problems of binaries if you preroot them. Anyway feel free to flash the firmware with odin or load an custom ROM to your sd card and flash it.
Hope this helps!
Click to expand...
Click to collapse
Thank you for getting me out of the brick and back to stock.
However going into Supersu it says.
"There is no SU binary installed, and SuperSu cannot install it. This is a problem!
If you just upgraded to Android 5.0, you need to manually re-root- consult the relevant forums for your device!"
My question is, can I properly re-root it the way I had been?
I'm assuming if it soft bricks again I can just reinstall a stock ROM again.
Also all these ROMS and backups take up a lot of space, how would I go about deleting those when I'm done?
pennylessz said:
Thank you for getting me out of the brick and back to stock.
However going into Supersu it says.
"There is no SU binary installed, and SuperSu cannot install it. This is a problem!
If you just upgraded to Android 5.0, you need to manually re-root- consult the relevant forums for your device!"
My question is, can I properly re-root it the way I had been?
I'm assuming if it soft bricks again I can just reinstall a stock ROM again.
Also all these ROMS and backups take up a lot of space, how would I go about deleting those when I'm done?
Click to expand...
Click to collapse
In my files app, look for an folder called TWRP. Your backups are in there. To root simply install twrp and follow the twrp method to root. http://forum.xda-developers.com/showthread.php?p=59638836
You can delete your backups from within twrp. Just select restore, then the backup, then delete.
Hey everyone,
I have been rooted for a LONG time, but have been gone for a year or 2. I have the OnePlus 3 that IS rooted with:
Experience OS R11.0 with
Kernel 3.18.31-perf+
[email protected] #1
7.1.1
OP3_o2_open_18
This one has served me well, but may be a bit obsolete.
What rom and kernel can I use now from 7.1.1 What must I do? I see 8.0 and such, and a host of others. Will I lose everything if I upgrade to a new version? I always do a nandroid, and I have Titanium Backup, which I THINK keeps apps, etc...
I remember having trouble installing Roms way back when. Not sure if it was a TWRP issue, as I also had Philz at one point. ( I Have TWRP now, but not sure which version) I had to use what i have (Which IS a GREAT ROM) because I was afraid to brick my phone, because I had so much trouble getting a rom to load. I constantly remember the little android falling over saying "Leave me the **** alone. If I boot to recovery, I just get the TWRP screen 3.1.0.0 that never opens. It just stays on that page and never opens, so I have to turn off the phone to reboot to turn on
I sincerely apologize for not remembering or keeping up.
Have a great day
wascapsfan said:
Hey everyone,
I have been rooted for a LONG time, but have been gone for a year or 2. I have the OnePlus 3 that IS rooted with:
Experience OS R11.0 with
Kernel 3.18.31-perf+
[email protected] #1
7.1.1
OP3_o2_open_18
This one has served me well, but may be a bit obsolete.
What rom and kernel can I use now from 7.1.1 What must I do? I see 8.0 and such, and a host of others. Will I lose everything if I upgrade to a new version? I always do a nandroid, and I have Titanium Backup, which I THINK keeps apps, etc...
I remember having trouble installing Roms way back when. Not sure if it was a TWRP issue, as I also had Philz at one point. ( I Have TWRP now, but not sure which version) I had to use what i have (Which IS a GREAT ROM) because I was afraid to brick my phone, because I had so much trouble getting a rom to load. I constantly remember the little android falling over saying "Leave me the **** alone. If I boot to recovery, I just get the TWRP screen 3.1.0.0 that never opens. It just stays on that page and never opens, so I have to turn off the phone to reboot to turn on
I sincerely apologize for not remembering or keeping up.
Have a great day
Click to expand...
Click to collapse
Wow.. Not one answer. What happened to the days where you ask a question, you get ridiculed, then many come out of the woodwork to get you on track...
Oh well........
wascapsfan said:
Hey everyone,
I have been rooted for a LONG time, but have been gone for a year or 2. I have the OnePlus 3 that IS rooted with:
Experience OS R11.0 with
Kernel 3.18.31-perf+
[email protected] #1
7.1.1
OP3_o2_open_18
This one has served me well, but may be a bit obsolete.
What rom and kernel can I use now from 7.1.1 What must I do? I see 8.0 and such, and a host of others. Will I lose everything if I upgrade to a new version? I always do a nandroid, and I have Titanium Backup, which I THINK keeps apps, etc...
I remember having trouble installing Roms way back when. Not sure if it was a TWRP issue, as I also had Philz at one point. ( I Have TWRP now, but not sure which version) I had to use what i have (Which IS a GREAT ROM) because I was afraid to brick my phone, because I had so much trouble getting a rom to load. I constantly remember the little android falling over saying "Leave me the **** alone. If I boot to recovery, I just get the TWRP screen 3.1.0.0 that never opens. It just stays on that page and never opens, so I have to turn off the phone to reboot to turn on
I sincerely apologize for not remembering or keeping up.
Have a great day
Click to expand...
Click to collapse
Make sure you have the latest TWRP by Bluspark, it just works flawless for me and alot of other people.
Take a full backup. Wipe system and both cache partitions. Then flash the latest Experience ROM. For the open beta releases I should stick with stock kernel. Otherwise Franco and Flash kernel would be interesting. For root I should go with Magisk. Everyone uses it nowadays and the modules are super handy.
Twrp issues
I have rooted the One Plus 3. I loaded TWRP about a year and a half ago. Now when I try to go into recovery, TWRP comes up, but never opens. I tried removing it, but it wont remove, and I try to reinstall it using several methods including apps, but to no avail. The bootloader is unlocked and the debugging is on. Any suggestions. I can't do a backup or anything.
Thanks
Dave
wascapsfan said:
I have rooted the One Plus 3. I loaded TWRP about a year and a half ago. Now when I try to go into recovery, TWRP comes up, but never opens. I tried removing it, but it wont remove, and I try to reinstall it using several methods including apps, but to no avail. The bootloader is unlocked and the debugging is on. Any suggestions. I can't do a backup or anything.
Thanks
Dave
Click to expand...
Click to collapse
Boot into fastboot, then connect it to your pc and use fastboot flash recovery. Get the latest TWRP.
I tried that, but it won't take. If I had a tar file, I could try it with Odin, but no matter what I do, when I go into bootloader, it says I'm unlocked, then I try to go into recovery, and TWRP shows up, but typically you get the different choices like backup, install, etc... I stay stuck on the TWRP page, that does not do anything, nor does it give me any choices. I have to shut the phone down each time just to get it back to working mode. I tried the adb method using the cmd prompt, and everything works up to trying to actually flashing TWRP...
wascapsfan said:
I tried that, but it won't take. If I had a tar file, I could try it with Odin, but no matter what I do, when I go into bootloader, it says I'm unlocked, then I try to go into recovery, and TWRP shows up, but typically you get the different choices like backup, install, etc... I stay stuck on the TWRP page, that does not do anything, nor does it give me any choices. I have to shut the phone down each time just to get it back to working mode. I tried the adb method using the cmd prompt, and everything works up to trying to actually flashing TWRP...
Click to expand...
Click to collapse
You may have to flash the original recovery by oneplus , you can find it on one plus downloads in google , make sure before you do anything that you backup anything important like photos , videos to a computer , then download the ROM of choice along with the correct gapps for that ROM and the correct firmware ( most ROMs will include the recommended firmware in their post ) , also download the latest twrp recovery from twrp.me and magisk ( if not included in the ROM ) then its just a matter of wiping system , data , cache and dalvick whilst in twrp , install the ROM with the gapps let the ROM boot and setup a few of your settings then go back into twrp and flash magisk manager and you should be good to go , good luck and make sure you fully read the instructions on the ROM page that you want ...