Hi guys.. I tried installing jelly bean on this device (i8160p and it's not mine) using odin and a stock 4.1 rom I got from samsung updates(I have no root and I went from a never-touched stock)... All went fine, It's working and has all the features. Except that now its owner is asking me constantly to revert back to the original os, since he did find 4.1.2 very slow. So I went back the same path as in the first place in an attempt to get the original gingerbread : I downloaded a stock 2.3 from the site and then tried flashing it.. All again went smooth, with no problems, until I got stuck on the bootscreen and noticed that there was no way to access recovery(download mode working fine though)... So what I'm left with now is a non-booting gingerbreak or the possibility to stay in jellybean(flashing it still works), I'd prefer if I could go back to GB; I think the problem is that there was some conflict caused by jellybean which will require a reset that I can't of course do since I can't boot into recovery, and I don't see any way to install a custom recovery. So can this be done any other way, I'm afraid I'll break this phone before I'll even come up with anything since this is my first experience with roms and boot on an android;
info : as I mentioned There is no root (for now. I might however get into that from jellybean, but I'd rather not if it's possible) and the model is i8160P . an emphasis on the P here since it's the reason I can't find any custom roms, and all I'm left with is the stuff in here
Edit : got gingerbread back after following what angrybb has suggested
Flash the working JB, and after that root your phone like here: http://forum.xda-developers.com/showthread.php?t=2139263 Reboot to recovery and after that follow the howto: http://forum.xda-developers.com/showthread.php?t=2352064 just in step 8 use original gb firmware.
If you can't get adb root access from stock recovery then flash kernel with cwm, for jb for example this: http://forum.xda-developers.com/showthread.php?t=2304432 or this http://forum.xda-developers.com/showthread.php?t=2171054
After flashing one of those kernel, again follow: http://forum.xda-developers.com/showthread.php?t=2352064 , again in step 8 use gb fw
Ok I'll see
Thanks man I'll try what you suggested as soon a I can...
I have a question though: now I noticed that some people fixed this issue by dowloading some other parts (.pit and something else), but of course I'm unable to find these for the model with the P... Now If someone can please tell me if these files have anything to do with the re-partion option in odin(I heard that it does format everything and not just put things on top of things).... Is using it safe given that I don't mind losing data, or should I stay away from it ?
For angrybb : the phone still shows as i8160p in the about section and has access to network...
Here there is a lot talking about pit files, some tehniques with flashing one fw after another, but with no real explanation why this should be done this way. I dont like doing things like that, i want to understand what i am doing. I still haven found some in depth info about pit files.
Anyway, i upgraded from GB to JB with kies, after that i compared some parts of fw and pit file is not changed. Pit from GB and JB have same md5 in my phone, so it is the exactly same file.
I know that method i suggested is not short and plain easy but it is tested and working.
Thanks
Sorry for the delay... For anyone with same problem just follow what angrybb has suggested, but do not under any circumstances ignore backing-up CSPSA_FS and MODEM_FS if you care about your phone's ability to make calls !
hey, maybe you guys could also help me out? i came from a custom ROM that i was having problems with so I wanted to go to an official ROM instead. Originally i came from a GB stock ROM, then i went straight to CM 10.1 but i didnt have any signal on my phone so i tried flashing original stock 4.1.2, now im stuck on the boot screen and i cant access recovery mode. please help?
P.S. my phone is i8160
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.
Like I'm sure this topic hasn't come up before, but I've searched for hours and I'm probably just making things worse. I also just accidentally deleted this post halfway through. It's too late and I'm too tired and I have no working phone.
Bought an SGH-I747 on E-Bay. Got a Straight Talk SIM card kit, activated it, so far so good.
Rooted it with CF-Auto-Root. Worked pretty well, took a lot of reboots, upgraded the SU from the Play Store and it got rid of Knox. So far so good. Got everything all set up the way I like it. Happy.
It was running 4.4.2. I'm assuming it was the release prior to the November 12th OTA release, but I can't say for sure.
Phone downloaded and installed an upgrade automatically. Now, it won't boot. I get the SAMSUNG logo, then the Samsung Galaxy S III logo then nothing.
I retried the CF-Auto-Root, no change.
I booted into recovery (volume up, home and power on), did factory reset, no change.
Started looking around for a way to return it to stock. Found an upgrade43.zip file somewhere (I'm sorry I can't find where I got that now). Put it on the sdcard card and tried installing it with the recovery and it fails part way through.
At this point, I think I probably need to completely overwrite everything with something stock. I just don't know how to do that. I see posts on such subjects but they all have warnings that make me think I'm going to totally brick the phone, so I'm hoping someone can point me the right way. I'm not all that Android savvy, as you can tell.
Help.
Since your phone was running 4.4.2, do not attempt to flash any ROMs using that attempt to downgrade your bootloader to anything prior to 4.4.2.
Try this to get your phone up and running:
download the latest CM11 for the d2lte and save it to an external SD card: https://download.cyanogenmod.org/?device=d2lte
dowload the latest tar.md5 version of Philz Touch for the d2lte from here: https://goo.im/devs/philz_touch/CWM_Advanced_Edition/d2lte/
boot phone in download mode, open Odin 3.07, do not check anything except f.reset.time, flash Philz via PDA box, remove USB cable when you see the word Reset appear in the status window, remove battery, replace battery, boot into recovery, format system, Dalvik, data, and cache, flash cm11, and reboot.
Thank you for your reply. There are a few things in there I don't quite understand, but I think I can figure it out.
I was going to attempt this...
http://forum.xda-developers.com/showthread.php?t=2658486
In fact, I did attempt it with TWRP last night after I posted here and new I still wasn't going to sleep. I kept getting an error about a bad ZIP file.
Is that stock restore a bad idea?
Do not attempt to flash an older bootloader. The mjb bootloader is from 4.3 and attempting to flash it could hard brick your phone.
I suggest doing what I suggested so you can confirm the bootloader and modem installed on your phone.
OK. Thanks. Probably a good thing I couldn't get it to work then.
Thank you so much. I have a working phone again. Now I just have to get it all set back up the way I like it.
I have to say, and it's probably words straight from the devils mouth, that I kind of wish I could have restored the Samsung stock software. It's just what I'm used to. But I will take what I can get.
A few questions. I like having root. But root is what got me in trouble in the first place. Is this going to be rooted now, or will I have to do that or am I better off just leaving it alone.
Second, I'm probably going to have questions since this is so different than what I'm used to (like I already can't find the Play store). Where is the best place to ask?
If you want root, one of the easiest ways to get it is to flash supersu from your custom recovery. Most ROMs are pre-rooted.
Many custom ROMs do not include Gapps. Just download and install the Gapps version for your ROM.
If you like the TW look, flash a TW-based ROM. Check out the development threads for different ROMs.
here is a thread for Q's that has some pretty good/friendly helpers on it if you need.
http://forum.xda-developers.com/showthread.php?t=2257421
"all i can really do , is stay out of my own way and let the will of heaven be done"
How to save in to external SD card
How do you save the file into the external SD card? I am having the same brick issue with my GS3.
To save a file to an external SD card, just put the card into a card reader and save the ROM to the SD card.
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.