Im new to andriod, coming from IOS and my friend thought he could root my device and told me it was similar to jailbreak on IOS. After using odin to install twrp and flash SuperSU.zip onto my device, it will not go past the boot screen and has at the top 'Set Warranty Bit : kernel'. I need to get back andriod here is the situation:
No backups
Team win installed on device (If that helps)
Able to access data via computer and Odin can connect.
I have all my important stuff on a sd card so I was able to recover that
System/bin folder is empty
Samsung Galaxy Tab 2 SM-T719Y
Have downloaded the Firmware
SuperSU root
I just need Android back, so data loss isn't a worry. How can i do this in simple terms - Im a noob.
Will using Odin to install the firmware fix this?
cryoscalpel said:
Im new to andriod, coming from IOS and my friend thought he could root my device and told me it was similar to jailbreak on IOS. After using odin to install twrp and flash SuperSU.zip onto my device, it will not go past the boot screen and has at the top 'Set Warranty Bit : kernel'. I need to get back andriod here is the situation:
No backups
Team win installed on device (If that helps)
Able to access data via computer and Odin can connect.
I have all my important stuff on a sd card so I was able to recover that
System/bin folder is empty
Samsung Galaxy Tab 2 SM-T719Y
Have downloaded the Firmware
SuperSU root
I just need Android back, so data loss isn't a worry. How can i do this in simple terms - Im a noob.
Will using Odin to install the firmware fix this?
Click to expand...
Click to collapse
Yes using odin to flash stock firmware should fix it. Did the kernel message appear after you flashed TWRP or after you rooted? I think maybe you flashed a newer version of SuperSU that tried to modify the kernel. On older SuperSU it just puts binary files in /system/xbin.
Also, you said something about /system/bin being empty... Typically that means your /system partition isn't mounted. Go to Mount and check system, then check your /system partition with the File Manager...you may be able to use it to delete the root binary files and get it to boot.
Related
Hi,
I checked through many threads to see if anyone had a similar problem but couldn't find anything unfortunately.
Background :
I was running a Lite'ning ROM on my Samsung Galaxy S2. You're probably familiar with this ROM, but for those who aren't it gets flashed with ODIN and comes rooted and pre-installed with CWM.
I forget which version of Lite'ning ROM it was, but I am fairly certain it was pre-1.5 as the bundled CWM was definitely version 3.x.x.x (later versions I found had 4.x.x.x and 5.x.x.x).
I wanted to try a version of GalnetMIUI for something a bit different and hadn't changed ROMs in quite some time, so I booted into CWM 3.x.x.x (maybe 3.0.0.2?) and did a backup to the internal SD. This came in at around 1.4 GB and comprised of 4 files :
cache.img
data.img
nandroid.md5
system.img
I copied these to my PC too, just in case they somehow got erased from my phone.
Once I'd done this, I then copied the new ROM .zip file (latest version of GalnetMIUI) to the root of the internal SD, booted the phone into CWM, wiped user data and Dalvik cache, then proceeded to install it.
The problem :
I can't get my apps or data back. I was under the false impression that my Google account was automatically backing this up for me, and would restore everything once logged in as it had in the past (factory resets etc.). So once this didn't happen, I tried using CWM to revert back to how things were before installing the new ROM but although the restore appears to work I end up with issues.
I've tried a number of different ROMs and they either get stuck in 'boot loops' or a black screen after running through the restore procedure. I've tried restoring just data via the 'Advanced' option but this doesn't help.
I was under the impression that I'd be able to fully restore the ROM backup if I needed to, and have the phone running exactly how it was prior to messing around. It would seem this is not the case.
In desperation I tried flashing every Lite'ning ROM from version 1.0 to 4.2, restoring my backup each time but as mentioned I always get boot issues.
Have I lost my data? I hope not, as I had 'To Do' lists and all sorts of things that would cause problems if they were not retrievable. I realise this is a lack of knowledge and foresight on my part. I'm thinking now that I should have run Titanium Backup prior to this, and not assumed that CWM was going to provide a complete solution.
Hope all this makes sense and if any of you have the time to read through and offer advice it would be greatly appreciated. I am currently running a very pretty and slick GalnetMIUI without any of my data!
Thanks in advance.
download cwm 2.5.x.x its better
[email protected] said:
download cwm 2.5.x.x its better
Click to expand...
Click to collapse
Thanks for that, I'll give it a go tonight after work. Am I right in thinking that if it doesn't work I can extract the individual files and insert them manually to get my app data back?
OK, so after hours of searching I'm still no wiser as to how to install CWM 2.5.1.2
I found a zip file that was apparently version 2.5.1.2 but when I tried to install it from inside CWM 5.0.2.6 (included with GalnetMIUI) it sometimes gives an error, sometimes it reboots CWM and sometimes it simply says it has successfully installed (it lies). No matter what it says or does, it doesn't seem to actually replace version 5.0.2.6 with the older one and every time I do the three-finger boot it loads up the latest version like nothing changed.
I'm just so lost. All I want to do is restore my old backup, get my data back and move on. Please someone help me before I go insane from all this research!
[EDIT] In case any more information is needed, my exact procedure for installing version 2.5.1.2 of CWM went like this :
Download 2.5.1.2 zip file
Copy zip file to root folder on internal SD
Boot into CWM 5.0.2.6
Select "install zip from sdcard"
Select "choose zip from sdcard"
Navigate to 2.5.1.2 zip file, select and confirm
Can anyone help me at all?
In particular I'd like to know how I can downgrade to CWM 2.5.1.2 or similar in order to give [email protected]'s suggestion a go.
Failing that, if anyone has any suggestions whatsoever about how I can get my backup data restored it would be greatly appreciated. After spending some time with MIUI - in particular the Galnet ICS build - I have nothing but praise, but I really have to get my data back!
You should be able to downgrade through ROM manager. Go to "All Clockwork Mod Recoveries" and just flash one that is not 5.x.x. Any backup not made with version 5 will not work with the new version So if you can flash one that is version 2, 3 or 4 you should be good to go. If that doesn't work you can fastboot flash it. There are guides on how to do that.
Wait.....did you mount /system before installing the CWM zip ?
Sent from my GT-S5830 using XDA App
Sorry for the delayed reply, for some reason I didn't get an email notification that my thread had been updated.
lowandbehold said:
You should be able to downgrade through ROM manager. Go to "All Clockwork Mod Recoveries" and just flash one that is not 5.x.x. Any backup not made with version 5 will not work with the new version So if you can flash one that is version 2, 3 or 4 you should be good to go. If that doesn't work you can fastboot flash it. There are guides on how to do that.
Click to expand...
Click to collapse
For some reason, when I select "All ClockworkMod Recoveries" the only two options are 4.0.1.4 and v4.0.1.4. I'll have to look into "fastboot" flashing as I've never heard of that.
By the way, if I boot into CWM via ROM Manager the version that loads is 4.0.1.5, but if I perform the three-button combo when switching my device on I get version 5.0.2.6.
EmoBoiix3 said:
Wait.....did you mount /system before installing the CWM zip ?
Sent from my GT-S5830 using XDA App
Click to expand...
Click to collapse
I didn't, is that something I should try?
Edit - Just tried this and at first it rebooted CWM and the version number hadn't changed. Doing this again yielded me the following error with no change in version number :
Code:
E:Error in /sdcard/CM V 2.5.1.2_update.zip
(Status 0)
Installation aborted.
I found out that I can extract the contents of my backed up .img files using unyaffs.exe.
Unless I'm doing something wrong, it would appear that my backup is corrupt somehow. When trying to extract data.img, it processes for a while and does bring back a lot of files but I also get the following :
Code:
read image file
: Bad file descriptor
read image file
: Bad file descriptor
data.img is around 1.2GB but the files I extract only amount to around 190MB.
It would appear that I don't have my contacts database in there which is annoying as for some reason there were quite a few that didn't get synced to Google's servers.
I rooted my S3, changed one file, and am now stuck in the startup screen. I've looked on the forums but I'd like to confirm what my recovery options are.
(1) Since I have no backup*, can I recover from a factory recovery for my model and still keep some of my data, apps and customizations?
It's a N American SIII (Rogers Wireless Samsung SGH-I747M). I can boot successfully into both Odin and CWM Recovery (Clockwork 5.5). BusyBox installed. I do not have a functioning MicroSD.
*I only did one thing:
renamed framework-res.apk to framework-res.apk2 to test permissions. Errors and crash ensued, then I restarted and here I am.
That apk file is part of a fix which is circulating that corrects a bug in the North American models' battery reporting, which requires replacing the apk with a slightly modified version. I thought trying a file rename was a safe small test, prior to backing up. The name "framework" should have tipped me off probably.
(2) Is factory recovery my best option? I would love to get in and just name the file back. But I can't get in.
(3) Was some automatic backup made that I overlooked? Rooting and the learning curve took so many steps I can't remember myself.
(4) Can I just restore the /system directory perhaps?
Yep, relative noob here. Hope my question is placed correctly and I haven't missed another post with the answers I need, if not pls advise.
Copied question to a better thread
It's now in the Android Q&A, see:
http://forum.xda-developers.com/showthread.php?p=28256764
Just getting used to the forum here.
NEVER FEAR find a ROM that you want to install and flash it using Odin or copy it to SD card and flash using clockwork mod And no there is no secret backup BTW once you get your phone working again make a backup then Go to where its stored And label it ALWAYS backup as soon as you root your phone
If you can manage, push a similar framework (taken from someone else) using adb...
Typed using a small touchscreen
How?
jezus101 said:
NEVER FEAR find a ROM that you want to install and flash it using Odin or copy it to SD card and flash using clockwork mod And no there is no secret backup BTW once you get your phone working again make a backup then Go to where its stored And label it ALWAYS backup as soon as you root your phone
Click to expand...
Click to collapse
You can flash a ROM using Clockwork instead of Odin? I totally missed that memo! Tips please
I found that Clockwork required the file to be in the internal SD folder -- I couldn't access the External SD card under any circumstance. There was no way to get a file to the internal file system without a functioning ROM. This is still confusing me. Maybe I had the wrong version of Clockwork or was doing it wrong. Not for lack of trying.
This is a Loki'd ClockWorkMod Recovery TOUCH file that I created on my AT&T Samsung Galaxy S4 SGH-I337 with the UCUAMDL baseband.
Flash using loki_flash in a Terminal window (how I did mine) or ADB using the command loki_patch recovery cwm.lok. If running in a Terminal window, make sure you have SU access first and that the cwm.lok file is in the same folder as the loki_patch file. I placed both of mine on the root of my external SD card.
After flashing this I rebooted into Recovery via ROM Manager and Touch was installed.
Hope this helps someone else!
Can you give clearer, more specific instructions on how to use this?
this is pre-lokid whe build by builder.clockworkmod.ckm
Sent from my SGH-I337 using Tapatalk
jd1639 said:
Can you give clearer, more specific instructions on how to use this?
Click to expand...
Click to collapse
UnRar the file and copy the CWM.LOK file onto your SD card.
Download and save the loki_flash file from here:https: // github dot com/djrbliss/loki/tree/master/bin
Copy the loki_flash file onto your SD card in the same location as the CWM.LOK file.
Open a Terminal session (download and install your favorite Terminal app from the Play store)
In the Terminal window type:
[email protected]:/ $ su
[email protected]:/ # cd /<path to location you saved the files to>
[email protected]:/ # ./loki_flash recovery cwm.lok
* Note - not responsible if this bricks your device. Your best bet is to read up on how to do this yourself at https:// github dot com/djrbliss/loki, save your own aboot.img file and built your own CWM.LOK file.
blackwing182 said:
this is pre-lokid whe build by builder.clockworkmod.ckm
Sent from my SGH-I337 using Tapatalk
Click to expand...
Click to collapse
If this recovery.img file was downloaded from http://www.clockworkmod.com/rommanager then it is not loki'd by default. I actually just tried to flash the .img file i downloaded from there and it gave me the unauthorized BS and i had to heimdall the stock recovery image back on.
ROM Manager has a script that it runs AFTER the recovery.img file is downloaded that loki's the recovery.img, then flashes it to the device.
Question....
jakew02 said:
If this recovery.img file was downloaded from http://www.clockworkmod.com/rommanager then it is not loki'd by default. I actually just tried to flash the .img file i downloaded from there and it gave me the unauthorized BS and i had to heimdall the stock recovery image back on.
ROM Manager has a script that it runs AFTER the recovery.img file is downloaded that loki's the recovery.img, then flashes it to the device.
Click to expand...
Click to collapse
I have full root access with SuperSU on sgh_i337 NC1 SELinux permissive. I froze all Knox related apps with TiBu. You flashed and soft bricked... now my question is.... Is it Knox that gave you the warning about the unauthorized flash attempt? I don't think I can flash traditionally anyway with the boot loader the way it is, but I havnt found anyone else that's fully rooted 4.4.2 either, so this is an original question lol. If I soft brick, I'm pretty well dead at this point, but in for a dime, in for a dollar I guess lol. After a 15 hour hack session fighting with Knox I don't wan to lose now :cyclops: I need a recovery though,
Lt1streconbn said:
I have full root access with SuperSU on sgh_i337 NC1 SELinux permissive. I froze all Knox related apps with TiBu. You flashed and soft bricked... now my question is.... Is it Knox that gave you the warning about the unauthorized flash attempt? I don't think I can flash traditionally anyway with the boot loader the way it is, but I havnt found anyone else that's fully rooted 4.4.2 either, so this is an original question lol. If I soft brick, I'm pretty well dead at this point, but in for a dime, in for a dollar I guess lol. After a 15 hour hack session fighting with Knox I don't wan to lose now :cyclops: I need a recovery though,
Click to expand...
Click to collapse
This thread is from 2013, and it's referring to the old MDL firmware. Your on NC1, which came out nearly a year after this was posted... the reason your phone is softbricked is because any loki-based recoveries,etc do not work on devices MF3+. Your want to check out this thread to get help in restoring your device. Remember, next time to look at the date of the posting and to read around the forums before trying to modify your device if you are unsure what you are suppose to be doing.
Your need to use Odin, to flash your phone back to stock NC1. It's in the thread I linked above....
I'm not soft bricked lol... I'm trying to figure out how far I can push it without that happening I have su in /system/xbin & /system/bin... Long story but I needed it there while I was restricted to root access only in terminal emulator for a few hours getting Knox to take a nap. I have learned new respect for that dang little app!!!! I actually got full root without PC/Linux support In 4.4.2 that's... Probably the reason's Knox never saw it happening lol I'm still messed on recovery besides safe strap unfortunately, but I'll take SuperSU over towelroot or safe root any day I grabbed a nap and I'm deodexing my system apps and framework now. I was kinda excited and didn't notice the date... Ty for the help, but Ialready have stock firmware I'd need. I'll head over to the newer thread... I actually have an idea on the boot loader from the decompiled Knox file I've gone thru. The boot loader IS locked, but we have a very limited exploit. Knox has been revamped five times that I caught I believe, and it ridiculously still had the ability to safely uninstall itself like it done early on lol. Crazy! Anyhow tks... I'll head over there. This was just funnier than when I found 'vold 2.0 the vengence' rofl
hello guys, apologies if this has been asked before, I just can't find the answer to this anywhere, not directly anyhow.
anyhow, i'm trying to install cyanogenmod 11 on my note 10.1. I have already done this on my galaxy s 3, so i am basically aware of the process. I have rooted the note,and that works fine. and had initially installed the latest version of CWM, the version recompiled for the note 10.1
i've installed the CM11 and gapps zip files to the root of my sd card (that's internal btw, I don't have a external SD) I can see the file on the device in any file manager when the device is booted up. i can move it, and root browser can see it too.
here's my problem. when i actually boot into CWM to actually install the zips, CWM can't see them. the /sdcard folder has nothing in it. this is the same even if i put the file in another location. but when i boot the device back up, there it is! it hasn't gone anywhere, it just can't be seen when the phone is in CWM mode.
thinking that it might be a issue with CWM, since the version is an unofficial recompiled version, I decided to try TWRP instead, as they have an official version for the 10.1. I installed it through odin, and it works fine, but.... IT HAS THE SAME PROBLEM! it can't actually see the files to install them.
I've even tried running a rom manager on the device. if i load up the rom manager while the device is booted up normally, it can see the files, and when i press to reboot the device into recovery mode to install the files, the device reboots, it enters TWRP, and then gives an error message that basically translates to file not found!!
I just don't understand why it can see the file in normal mode, but not when in recovery, and bear in mind this is BOTH the CM11 zip, AND the gapps zip, so really it's just ALL files it can't see!
can anyone help me with this? sorry to ask, but it's got me
Hi! I have been searching on the web for the Stock ROM to G930F, but the phone only installs the modem.bin file. Everything else throws a error on the phone, and in Odin. So i’ll tell you how this happened, And yes this might be a long story.
I wanted to use Samsung Health to check my puls.
I opened the app and it said that I couldn’t use this app because the phone was rooted. (I had rooted my phone in the past and downloaded a stock ROM to flash my phone with to start off clean)
And so I thought I’ll just fix it now, because I am on computer. So I flashed my device with TWRP and mounted the system and the data. I saved the build.prop file on my computer and changed the Knox Trigger Value to 0. When I flashed the file back after editing it, ADB said it couldn’t read the file. I thought “what the hell?”. I rebooted the device, plugged it off my computer and noticed something was odd. It began to bootloop, the start-up image when you power on the device. I got into Recovery and checked to see what was wrong. It said the Internal Storage was (0 MB) used. I was powering off the device, and it said “No OS installed!”. I tried flashing the stock ROM but it would only accept the modem.bin file. I was worried and didn’t know what I would do. Any help would be great!
Lipticon said:
Hi! I have been searching on the web for the Stock ROM to G930F, but the phone only installs the modem.bin file. Everything else throws a error on the phone, and in Odin. So i’ll tell you how this happened, And yes this might be a long story.
I wanted to use Samsung Health to check my puls.
I opened the app and it said that I couldn’t use this app because the phone was rooted. (I had rooted my phone in the past and downloaded a stock ROM to flash my phone with to start off clean)
And so I thought I’ll just fix it now, because I am on computer. So I flashed my device with TWRP and mounted the system and the data. I saved the build.prop file on my computer and changed the Knox Trigger Value to 0. When I flashed the file back after editing it, ADB said it couldn’t read the file. I thought “what the hell?”. I rebooted the device, plugged it off my computer and noticed something was odd. It began to bootloop, the start-up image when you power on the device. I got into Recovery and checked to see what was wrong. It said the Internal Storage was (0 MB) used. I was powering off the device, and it said “No OS installed!”. I tried flashing the stock ROM but it would only accept the modem.bin file. I was worried and didn’t know what I would do. Any help would be great!
Click to expand...
Click to collapse
Ok so you don't say what firmware you had and which one you want to flash., there are lots of firmware for the G930. You can download them from several places , sammobile, SamFirm Tool and updato.com.
Use the latest version of Odin if you want Oreo, preferably unbranded.
With regard to Samsung health, this app will not work on a rooted device, just like banking apps, network provider apps and any other app which hold personal info.
Lipticon said:
Hi! I have been searching on the web for the Stock ROM to G930F, but the phone only installs the modem.bin file. Everything else throws a error on the phone, and in Odin. So i’ll tell you how this happened, And yes this might be a long story.
I wanted to use Samsung Health to check my puls.
I opened the app and it said that I couldn’t use this app because the phone was rooted. (I had rooted my phone in the past and downloaded a stock ROM to flash my phone with to start off clean)
And so I thought I’ll just fix it now, because I am on computer. So I flashed my device with TWRP and mounted the system and the data. I saved the build.prop file on my computer and changed the Knox Trigger Value to 0. When I flashed the file back after editing it, ADB said it couldn’t read the file. I thought “what the hell?”. I rebooted the device, plugged it off my computer and noticed something was odd. It began to bootloop, the start-up image when you power on the device. I got into Recovery and checked to see what was wrong. It said the Internal Storage was (0 MB) used. I was powering off the device, and it said “No OS installed!”. I tried flashing the stock ROM but it would only accept the modem.bin file. I was worried and didn’t know what I would do. Any help would be great!
Click to expand...
Click to collapse
As @cooltt said use SamFirm tool (search it on google, it's here on xda) and download the latest firmware for your variant (ex. SM-G930F if you own the international S7 flat).
Flash with odin. Make sure you put all the files in the right tabs.
Let the phone boot completly (until the tutorial shows up, if you used the CSC file instead of the HOME_CSC one)
To be able to use SHealth you will need to edit the build.prop. To do so:
1) flash twrp
2) boot to twrp and wipe data (you will loose everything you have in the internal storage so make a backup)
3) Reboot to recovery (twrp menu > reboot > recovery)
4) Flash Magisk 18.1
5) Reboot to system and wait until the phone boots (it may take 5-10minutes)
6) Set up everything and go to play store. Download BuildProp Editor
7) Open BuildProp Editor and make sure you grant it superuser access in Magisk
8) Search for the property: ro.config.tima and set its value to: 0
9) reboot the phone and you should be good to go.
If you want OTAs you will need to 1) uninstall magisk and 2) wait until the next update is released and flash it with odin using the HOME_CSC file.That will revert the kernel to its original state (non-rooted), the recovery to the stock one and the system and binary status to Official (which will allow you to receive OTAs once again)
Sent from my SM-G930F using Tapatalk