EDIT on Jan 18,2015
Please see post #9 for a flashable zip of the stock ROM with root that is taken after updated to B148.
Below original post has version B126.
******** ORIGINAL *********
Fix soft-bricked Mate 2 (MT2-L03) phone using TWRP
If you messed up the phone and it came to a state that phone can not boot into android, if you have TWRP installed and have a backup, then you know how to fix that easily.
But if you don't have your own backup, I have upload my system partition so hopefully you can use this to restore your phone. The backup is taken very close to stock, and it is rooted with SuperSU installed.
BTW, there is a "safe mode" boot method, so try that before using twrp recovery:
http://forum.xda-developers.com/asc...ted-amazon-app-store-stuck-boot-loop-t2872628 (post 6 and 7)
Steps to Restore you phone if all other ways failed:1. Your MT2-L03 need have bootloader unlocked, and TWRP recovery installed properly. Even your phone is soft bricked, as long as you can boot into bootloader mode, you can still unlock bootloader and install twrp recovery.Unlock bootloader: http://forum.xda-developers.com/ascend-mate2/general/progress-rooting-ham2-t2867975
Install twrp: http://forum.xda-developers.com/asc.../2014-09-22-teamwin-recovery-project-t28851442. Boot into twrp recovery and select "System" partition only, and backup it to your external storage (yes, I know your system partition is bad, this step is to create proper twrp backup directory)
3. Download following file to your PC, unzip it.http://tinyurl.com/qzxkm4x
FileName: TWRP_BACKUPS_stock-system-with-root.zip4. Turn off phone and take out your SD card out and plug into PC, then navigate to following directory under the SDCARD: \TWRP\BACKUPS\xxxxx, the xxxxx is a string that different in each phone
5. Copy all the files unzipped from step 3 to above location. overwrite any files with same name.
6. Put back the SDcard to the phone, and boot into TWRP recovery.
7. Choose restore, select the only entry that you did the backup, and select "System" only, perform the restore.
8. Wipe your dalvik cache, cache.
9. Then reboot.
10. If you still have problem, boot into recovery again, and wipe /data parition as well (Factory Reset).Download the MT2-L03 backup here:
http://tinyurl.com/qzxkm4x
FileName: TWRP_BACKUPS_stock-system-with-root.zip
And thanks @dbmj unlock bootloader, @Modding.MyMind build twrp recovery, and @D33PTHAWTE confirmation that this fixed his phone.
Glad you got this posted. This will be very vital to many people down the road. And great work on giving instructions to create a backup for the simplicity of automating the needed directories for usage of the actual shared backup. Thumbs up bro.
@D33PTHAWTE, welcome back
For everyone not getting TWRP to work I have done it on 3 HAM2s and all work try this.
1.flash this stock recovery https://drive.google.com/folderview?id=0B-nJFDpWA4MdVjhEYzU3TXlMZ0U&usp=sharing
2.even if you have your own use that because I know that works and I dont know what yours is.
3.boot into the recovery and make sure that its the stock recovery and its working.
4. restart the phone 2 or 3 times to be safe
5. flash using twrp using 15 second ADB installer.
Has anyone followed thoes steps and that recovery above? (not your own) if not try that and let me know. take a screen shot of what ADB is showing you so I can see that TWRP was successfully installed. Starting at square one. Flash twrp and show me its flashed.
superbass311 said:
For everyone not getting TWRP to work I have done it on 3 HAM2s and all work try this.
1.flash this stock recovery https://drive.google.com/folderview?id=0B-nJFDpWA4MdVjhEYzU3TXlMZ0U&usp=sharing
2.even if you have your own use that because I know that works and I dont know what yours is.
3.boot into the recovery and make sure that its the stock recovery and its working.
4. restart the phone 2 or 3 times to be safe
5. flash using twrp using 15 second ADB installer.
Has anyone followed thoes steps and that recovery above? (not your own) if not try that and let me know. take a screen shot of what ADB is showing you so I can see that TWRP was successfully installed. Starting at square one. Flash twrp and show me its flashed.
Click to expand...
Click to collapse
i tried several time cant boot into twrp ....tried through adb it says flash done in 1.1 or something sec seems like all went well ...but when u try and boot into recovery it goes to android recovery screen with broken android mark .....
other than this phone works well and boots normally into android and i can make calls etc ...its just when i try to boot into recovery it always goto ...factory recovery with android and red mark ....whats goign on ...thanks
Hey I tried this on my phone, I think everything worked okay. Android ui crashes constantly when my sim card is inserted. When I try to do the OTA update it says theres an error with facebook in the cust folder. I tried to copy that from the zip but it failed to copy. Im out of ideas of what to do next.
notoriouspk said:
i tried several time cant boot into twrp ....tried through adb it says flash done in 1.1 or something sec seems like all went well ...but when u try and boot into recovery it goes to android recovery screen with broken android mark .....
other than this phone works well and boots normally into android and i can make calls etc ...its just when i try to boot into recovery it always goto ...factory recovery with android and red mark ....whats goign on ...thanks
Click to expand...
Click to collapse
What button combination are you using? And did you have unlocked bootloader?
notoriouspk said:
i tried several time cant boot into twrp ....tried through adb it says flash done in 1.1 or something sec seems like all went well ...but when u try and boot into recovery it goes to android recovery screen with broken android mark .....
other than this phone works well and boots normally into android and i can make calls etc ...its just when i try to boot into recovery it always goto ...factory recovery with android and red mark ....whats goign on ...thanks
Click to expand...
Click to collapse
aragon257 said:
Hey I tried this on my phone, I think everything worked okay. Android ui crashes constantly when my sim card is inserted. When I try to do the OTA update it says theres an error with facebook in the cust folder. I tried to copy that from the zip but it failed to copy. Im out of ideas of what to do next.
Click to expand...
Click to collapse
Hi, I have seen these issues pretty frequent recently that:
1) /cust partition is not covered in this TWRP backup, so after restore, you may still got facebook app mismatch failure when upgrade.
2) Even after a successful OTA upgrade, many people (include myself) met problem to reflash the TWRP image.
So, give me a few days, I think I can make a flashable zip that has latest (B148) stock ROM with root, probably this weekend.
xordos said:
Hi, I have seen these issues pretty frequent recently that:
1) /cust partition is not covered in this TWRP backup, so after restore, you may still got facebook app mismatch failure when upgrade.
2) Even after a successful OTA upgrade, many people (include myself) met problem to reflash the TWRP image.
So, give me a few days, I think I can make a flashable zip that has latest (B148) stock ROM with root, probably this weekend.
Click to expand...
Click to collapse
Thank you so much!
Please try install this zip from recovery:
http://tinyurl.com/q62m68x
MT2L03_B148_Stock_ROM.zip
File Size: 670,252,615 md5: 684bcb2674367814b96eadfa0debe846
Click to expand...
Click to collapse
This is a clean Stock ROM (flashable zip) with Root after upgrade to B148 for MT2L03.
It should only be used for plain carrier unlocked Huawei MT2-L03. Other varies (carrier locked) MT2L03 is un-tested and may brick your phone.
This ROM include /cust, /firmware, /system and /boot partition.
The official B148 update also contains update to SBL1/ABoot/TZ/RPM partition, they are not included due to risk concern.
I didn't fully test this ROM, I just pickup the image from my early backups. I installed it to my already updated phone and boot up fine. So please try it and let me know if you see any problems.
Working great for me! thank you, fixed all my problems.
aragon257 said:
Working great for me! thank you, fixed all my problems.
Click to expand...
Click to collapse
Imei is correct after flashing this?
Moody66 said:
Imei is correct after flashing this?
Click to expand...
Click to collapse
A little confused on what you mean... My sim card works fine in my phone now
aragon257 said:
A little confused on what you mean... My sim card works fine in my phone now
Click to expand...
Click to collapse
Someone tried using a similar process to swap a consumer cellular mate to a standard mate. They lost their imei in the process.
Moody66 said:
Someone tried using a similar process to swap a consumer cellular mate to a standard mate. They lost their imei in the process.
Click to expand...
Click to collapse
Oh I dont think I did, I havent noticed anything. I do have the standard mate and not a consumer cellular mate.
standard ham2 bought from gethuawei
just testing your stock rom zip and everything works fine.
thank you for your effort and time.
after flashing i have no toggles and i dont have LTE so far
thugmafia said:
after flashing i have no toggles and i dont have LTE so far
Click to expand...
Click to collapse
toggle is set in settings -- notif panel, lte pls check apn settings.
xordos said:
toggle is set in settings -- notif panel, lte pls check apn settings.
Click to expand...
Click to collapse
its all gray out meaning i cant turn it on and the APN is set i used to get LTE on tmobile but now it juz 3G H 4G
Is your phone mt2l03 and bought as unlocked?
Another thing you can try is do a factory reset (to be safe backup /data first) and wipe cache, dalvik cache.
xordos said:
Is your phone mt2l03 and bought as unlocked?
Another thing you can try is do a factory reset (to be safe backup /data first) and wipe cache, dalvik cache.
Click to expand...
Click to collapse
yes i did i returned to the back up but still no LTE but the speed is the some
and one more thing i notice was the not home screen style to be able to hide the nar bar
Related
I know that I must have missed a step in these instructions: http://forum.xda-developers.com/showpost.php?p=29417266&postcount=1397
I am using an rooted EVO lte, with S-On (why I followed this thread with specific instructions with work around instructions)
I downloaded the zip file and was able to open up FlashImage and flash the zip file (the software found the correct file after indexing the .zip file). I rebooted the phone and held down volume down to get to the bootloader screen.
The only options I have are:
Fastboot
Recovery
Factory Reset
Clear Storage
Simlock
Image crc
Show Barcode.
I have tried Fastboot, recovery, and factory rest but all just restart the phone. When I try to restart the phone, it cycles through the HTC loading screens and then reboots again.
Is there anyway to save my phone?
Thanks in advance; your threads have been really helpful in the past.
spikedupclay said:
I know that I must have missed a step in these instructions: http://forum.xda-developers.com/showpost.php?p=29417266&postcount=1397
I am using an rooted EVO lte, with S-On (why I followed this thread with specific instructions with work around instructions)
I downloaded the zip file and was able to open up FlashImage and flash the zip file (the software found the correct file after indexing the .zip file). I rebooted the phone and held down volume down to get to the bootloader screen.
The only options I have are:
Fastboot
Recovery
Factory Reset
Clear Storage
Simlock
Image crc
Show Barcode.
I have tried Fastboot, recovery, and factory rest but all just restart the phone. When I try to restart the phone, it cycles through the HTC loading screens and then reboots again.
Is there anyway to save my phone?
Thanks in advance; your threads have been really helpful in the past.
Click to expand...
Click to collapse
Relock and run an RUU from the fastboot menu
If you use flash image you don't need to hold anything it has the option to boot recovery, it is only for the kernel, from there you boot to recovery and flash the rom and that should be it
The phone wont boot, so flash image GUI is useless. Exactly why I suggest people dont use it
The op never stated whether they actually flashed the ROM, for some reason they booted to the boot loader manually?
The way I read it the phone will only boot to the bootloader
I have tried Fastboot, recovery, and factory rest but all just restart the phone. When I try to restart the phone, it cycles through the HTC loading screens and then reboots again.
Click to expand...
Click to collapse
spikedupclay said:
I downloaded the zip file and was able to open up FlashImage and flash the zip file (the software found the correct file after indexing the .zip file). I rebooted the phone and held down volume down to get to the bootloader screen.
Is there anyway to save my phone?
Thanks in advance; your threads have been really helpful in the past.
Click to expand...
Click to collapse
The thread linked is cm9 op states after flash image they rebooted the phone and held volume down, and get to the boot loader screen but stops there no where is it mentioned cm9 ROM was flashed which leads me to believe they never jumped into recovery to flash rom
om4 said:
The thread linked is cm9 op states after flash image they rebooted the phone and held volume down, and get to the boot loader screen but stops there no where is it mentioned cm9 ROM was flashed which leads me to believe they never jumped into recovery to flash rom
Click to expand...
Click to collapse
I believe you are right. I tried to follow this step but could not verify it was done correctly.
The ROM is flashed seperately from the kernel, as soon as flash img is done it gives the option to reboot directly into the recovery, this is because the ROM is flashed next. Since you are going from sense to aosp you need to clear dalvik, cache, factory reset, then system wipe and then install and select your rom. Anytime you install a different ROM sense or aosp, you need to wipe the phone. Take a look at my guide, I go over the various issues that could happen and do my beat to explain why. I also list a ton of info in android in general
om4 said:
The ROM is flashed seperately from the kernel, as soon as flash img is done it gives the option to reboot directly into the recovery, this is because the ROM is flashed next. Since you are going from sense to aosp you need to clear dalvik, cache, factory reset, then system wipe and then install and select your rom. Anytime you install a different ROM sense or aosp, you need to wipe the phone. Take a look at my guide, I go over the various issues that could happen and do my beat to explain why. I also list a ton of info in android in general
Click to expand...
Click to collapse
Thanks; do I do this all from the bootloader screen? I don't see all of these as options.
You need to select recovery
spikedupclay said:
Thanks; do I do this all from the bootloader screen? I don't see all of these as options.
Click to expand...
Click to collapse
I think I am missing where I have the option to install/select a ROM
After twrp shade rolls away its the first button
om4 said:
You need to select recovery
Click to expand...
Click to collapse
When I do that it quickly reboots, and goes directly back to the same screen with the options:
bootloader
reboot
reboot bootloader
and power down
OK you need to flash recovery, do you have the adb tools package?
om4 said:
OK you need to flash recovery, do you have the adb tools package?
Click to expand...
Click to collapse
I just did; is there anyway to direct message you? Because I am a newly registered user it is only allowing me to post once every 5 minutes. I've installed the ADB tools package and it is not showing my phone
Hello there !
I have a Nexus 4 with ClockWorkMod and I'm wondering if flashing Ubuntu Touch could possibly wipe my recovery. Also, does it wipes the data contained in /sdcard ?
Some reports have said no, some say yes. I'm checking now, but assume it does until we know otherwise.
BlackEco said:
Hello there !
I have a Nexus 4 with ClockWorkMod and I'm wondering if flashing Ubuntu Touch could possibly wipe my recovery. Also, does it wipes the data contained in /sdcard ?
Click to expand...
Click to collapse
bitpushr said:
Some reports have said no, some say yes. I'm checking now, but assume it does until we know otherwise.
Click to expand...
Click to collapse
let us know asap gonna test it as well as soon as download finished (will take ages)
it wipes the entire device if you use the instructions Ubuntu provides....as stated in the instructions
there is info right here on xda, on how to do it without wiping everything
Pirateghost said:
it wipes the entire device if you use the instructions Ubuntu provides....as stated in the instructions
there is info right here on xda, on how to do it without wiping everything
Click to expand...
Click to collapse
where please? we are all flashing through zip via recovery...
Considering the build script checks if the recovery is flashable:
subprocess.check_call('sudo fastboot flash recovery %s' % recovery_file,
shell=True)
I would assume it would flash the recovery partition.
joshumax said:
Considering the build script checks if the recovery is flashable:
subprocess.check_call('sudo fastboot flash recovery %s' % recovery_file,
shell=True)
I would assume it would flash the recovery partition.
Click to expand...
Click to collapse
that's without any doubt! I don't have the zip yet, so can you check if something is related to an sd card wipe??
people are reporting TWRP works ok, no recovery nor sd card wipes
The built-in installer DOES flash a new recovery (looks like a stock recovery, or maybe with their own modifications). I'm not sure if it wipes nandroid backups yet, going to check that next.
memnoc said:
where please? we are all flashing through zip via recovery...
Click to expand...
Click to collapse
If people would stop creating new threads every 3 seconds about ubuntu it would be easier to find....but alas, the xda public is too damn impatient
After installing through the "Ubuntu" method, which does flash a new recovery, I reflashed TWRP and checked and it does still keep the nandroid backups, so everything is still there. It's easy to go back to your old backup even after flashing the new recovery. Meaning, their process does not wipe the sdcard.
bitpushr said:
After installing through the "Ubuntu" method, which does flash a new recovery, I reflashed TWRP and checked and it does still keep the nandroid backups, so everything is still there. It's easy to go back to your old backup even after flashing the new recovery. Meaning, their process does not wipe the sdcard.
Click to expand...
Click to collapse
during my install, it wiped my sdcard. i followed the instructions as provided by canonical. my device was empty
I flashed using the zip files and could simply reboot, holding the volume button down, and get back into TWRP
Dizzi800 said:
I flashed using the zip files and could simply reboot, holding the volume button down, and get back into TWRP
Click to expand...
Click to collapse
correct. if you dont flash using canonicals instructions, and only flash the 2 zip files, nothing on your boot or recovery is touched....
thats what i am trying to say here. if you follow the canonical way, it wipes everything, loads its own boot.img and recovery.img, then flashes those zip files.
we dont need their boot or recovery to make this work. if you already have cwm or twrp all you have to do is flash the zip files
Pirateghost said:
correct. if you dont flash using canonicals instructions, and only flash the 2 zip files, nothing on your boot or recovery is touched....
thats what i am trying to say here. if you follow the canonical way, it wipes everything, loads its own boot.img and recovery.img, then flashes those zip files.
we dont need their boot or recovery to make this work. if you already have cwm or twrp all you have to do is flash the zip files
Click to expand...
Click to collapse
i think we can close this thread and rpovides the solution to the other one thread here http://forum.xda-developers.com/showthread.php?p=38299437#post38299437 as I'm currently doing
memnoc said:
let us know asap gonna test it as well as soon as download finished (will take ages)
Click to expand...
Click to collapse
I flashed with cwm, was able to make a backup before hand of my android. After flashing the Ubuntu os, I made a backup of it. Was able to restore android from my backup without no problems!! For what its worth, I have both as duelboot. Never lost anything while flashing!!
warp64 said:
I flashed with cwm, was able to make a backup before hand of my android. After flashing the Ubuntu os, I made a backup of it. Was able to restore android from my backup without no problems!! For what its worth, I have both as duelboot. Never lost anything while flashing!!
Click to expand...
Click to collapse
can u advise which zip files you flashed? tks in advance.
Sent from my Nexus 4 using xda app-developers app
Try this
PHONE SLOW CLICK ME?
_____________________________________
"If your doing the right thing then to hell with everyone else -Deadly"
---------- Post added at 07:54 AM ---------- Previous post was at 07:54 AM ----------
http://forum.xda-developers.com/showthread.php?t=2159291
PHONE SLOW CLICK ME?
_____________________________________
"If your doing the right thing then to hell with everyone else -Deadly"
If you do it through Ubuntu, yes. If you flash a ZIP, no.
Sent from my Galaxy Nexus using Tapatalk 2
warp64 said:
I flashed with cwm, was able to make a backup before hand of my android. After flashing the Ubuntu os, I made a backup of it. Was able to restore android from my backup without no problems!! For what its worth, I have both as duelboot. Never lost anything while flashing!!
Click to expand...
Click to collapse
dual boot you say? You wouldn't happen to have a nexus 4 would you. I've been looking for a dual boot solution with cm10.1 nightlies
Every time I try to root my tmobile-galaxy s5, which in now on 5.1.1 and on the newest update fol1, I install the newest version of twrp for this device but every time I install twrp the error message "set warranty bit kernel" pops up. Any idea to get passed this so I can root my phone?
This guy needs help said:
Every time I try to root my tmobile-galaxy s5, which in now on 5.1.1 and on the newest update fol1, I install the newest version of twrp for this device but every time I install twrp the error message "set warranty bit kernel" pops up. Any idea to get passed this so I can root my phone?
Click to expand...
Click to collapse
The set warranty bit isn't a problem, it's just the phone's way of showing you have a custom recovery installed. I get the same notification every time I boot up but I was able to root successfully. I assume you're using the correct version of TWRP and the superSU zip?
thisisapoorusernamechoice said:
The set warranty bit isn't a problem, it's just the phone's way of showing you have a custom recovery installed. I get the same notification every time I boot up but I was able to root successfully. I assume you're using the correct version of TWRP and the superSU zip?
Click to expand...
Click to collapse
I flashed twrp on Odin and went into twrp but when I flash supersu in twrp I hit boot in to system but it says set warranty bit kernel in the top left corner for a while. Please help me I need root acess
This guy needs help said:
I flashed twrp on Odin and went into twrp but when I flash supersu in twrp I hit boot in to system but it says set warranty bit kernel in the top left corner for a while. Please help me I need root acess
Click to expand...
Click to collapse
Which superSU version and which TWRP version? Also did you check the md5 on both? It sounds like you might have a bad download; this method has worked to root countless other people's devices with no issue
thisisapoorusernamechoice said:
Which superSU version and which TWRP version? Also did you check the md5 on both? It sounds like you might have a bad download; this method has worked to root countless other people's devices with no issue
Click to expand...
Click to collapse
I downloaded twrp and supersu on a thread you were on and you said they were good. I have a question though, how long did the first boot up take for you rooted phone?
This guy needs help said:
I downloaded twrp and supersu on a thread you were on and you said they were good. I have a question though, how long did the first boot up take for you rooted phone?
Click to expand...
Click to collapse
Same as normal boot up if I remember correctly. I also hadn't set anything up yet, even skipped the initial setup wizard that runs when you first start the phone, because I knew I planned to install cyanogenmod as soon as I was rooted. I only booted into system after I rooted once to run a couple of apps that require root in order to verify that I was, in fact, rooted. After that I wiped everything in order to install CM
thisisapoorusernamechoice said:
Same as normal boot up if I remember correctly. I also hadn't set anything up yet, even skipped the initial setup wizard that runs when you first start the phone, because I knew I planned to install cyanogenmod as soon as I was rooted. I only booted into system after I rooted once to run a couple of apps that require root in order to verify that I was, in fact, rooted. After that I wiped everything in order to install CM
Click to expand...
Click to collapse
When I installed twrp and the used it than flashed supersu, I hit boot into system and then it didn't boot into system, it just said "set warranty bit kernel". Please help.
This guy needs help said:
When I installed twrp and the used it than flashed supersu, I hit boot into system and then it didn't boot into system, it just said "set warranty bit kernel". Please help.
Click to expand...
Click to collapse
I need logs or something, because as I've said, "set warranty bit kernel," isn't a problem, that's normal and expected. I can't know what's wrong with your device with no information.
Did you try starting from the beginning? Flashing the stock OL1 Odin file, booting that up (not setting anything up except a Wi-Fi connection), and trying rooting with that? Did you try opening the TWRP tar file with 7zip or WinRAR and extracting the img file to verify the download wasn't corrupted? Did you try doing a similar check with the superSU zip? What version of supersu are you trying to use? Have you tried clearing cache and dalvik after installing supersu (not necessary but sometimes helps clear up issues)?
thisisapoorusernamechoice said:
I need logs or something, because as I've said, "set warranty bit kernel," isn't a problem, that's normal and expected. I can't know what's wrong with your device with no information.
Did you try starting from the beginning? Flashing the stock OL1 Odin file, booting that up (not setting anything up except a Wi-Fi connection), and trying rooting with that? Did you try opening the TWRP tar file with 7zip or WinRAR and extracting the img file to verify the download wasn't corrupted? Did you try doing a similar check with the superSU zip? What version of supersu are you trying to use? Have you tried clearing cache and dalvik after installing supersu (not necessary but sometimes helps clear up issues)?
Click to expand...
Click to collapse
All I did was flash the latest file of twrp. Then when it said pass I went straight into download mode and then flashed supersu (the latest version for my phone. After that I rebooted but it only says "set warranty bit kernel" in the top left corner in yellow. I tried this twice but same result (on the second time I flashed fol1 again before I tried).
This guy needs help said:
All I did was flash the latest file of twrp. Then when it said pass I went straight into download mode and then flashed supersu (the latest version for my phone. After that I rebooted but it only says "set warranty bit kernel" in the top left corner in yellow. I tried this twice but same result (on the second time I flashed fol1 again before I tried).
Click to expand...
Click to collapse
you don't flash SU in download mode... you reboot into recovery to flash it.
mgp53 said:
you don't flash SU in download mode... you reboot into recovery to flash it.
Click to expand...
Click to collapse
Sorry I mean I went in to recovery mode and flashed it
When you rooted did it say "set warranty bit kernel " when you booted back to Android after flashing supersu with twrp?
thisisapoorusernamechoice said:
I need logs or something, because as I've said, "set warranty bit kernel," isn't a problem, that's normal and expected. I can't know what's wrong with your device with no information.
Did you try starting from the beginning? Flashing the stock OL1 Odin file, booting that up (not setting anything up except a Wi-Fi connection), and trying rooting with that? Did you try opening the TWRP tar file with 7zip or WinRAR and extracting the img file to verify the download wasn't corrupted? Did you try doing a similar check with the superSU zip? What version of supersu are you trying to use? Have you tried clearing cache and dalvik after installing supersu (not necessary but sometimes helps clear up issues)?
Click to expand...
Click to collapse
Do I have to factory reset to root with this method?
This guy needs help said:
Do I have to factory reset to root with this method?
Click to expand...
Click to collapse
No
I found it out
For some reason I had to clear the cache and dalvik cache after the flash. That did it now I'm rooted!
This guy needs help said:
For some reason I had to clear the cache and dalvik cache after the flash. That did it now I'm rooted!
Click to expand...
Click to collapse
Hi!! Okay, I am having the same problem you had and need to know exactly what you did to fix it.
I followed the instructions exactly. I am stuck on the "set warranty bit kernel screen. I want to know what you did to fix this.
(When you were flashing the supersu for the second time, before you had to clear cache and dalvik, did you just go into recovery mode and flash it again, or did you have to delete something before you did that)
Please get back to me anyone, advice needed!
I cleared the caches before i rebooted into the system ( well i think this is what i did , it was a week ago) good luck bud?
ktberr said:
Hi!! Okay, I am having the same problem you had and need to know exactly what you did to fix it.
I followed the instructions exactly. I am stuck on the "set warranty bit kernel screen. I want to know what you did to fix this.
(When you were flashing the supersu for the second time, before you had to clear cache and dalvik, did you just go into recovery mode and flash it again, or did you have to delete something before you did that)
Please get back to me anyone, advice needed!
Click to expand...
Click to collapse
Oh yeah i forgot. You need to say no if twrp says to you " your phone appears to not be rooted , do you want root " because this just bricks your phone. P.s. my phone is rooted and is still says it but it is not true because it just bricks your phone
I tried to root my Samsung Galaxy S5 using Odin and an autoroot file. After that failed, I researched how to restore my phone to its original OS. I have not been able to do that either. I either can only boot to the Odin Mode screen or am locked on the T-Mobile logo screen.
BTW, I am new to phone rooting so more detailed explanations would be appreciated.
Are you able to boot to recovery? [ home+volume up+power]
If so you can reset from there.
If not you should be able download the stock firmware and flash it with Odin.
FOL1 is the latest - it takes a long time to download from Sam's.
http://www.sammobile.com/firmwares/database/SM-G900T/
Jim
otisdog is right, sammobile takes forever to download which is why you should download the exact same file they linked to, but from here:
https://www.androidfilehost.com/?fid=24407100847293882
Since cf-autoroot didn't work for you, you should just install TWRP with Odin and use TWRP to flash supersu zip, that's more or less what cf auto-root is doing anyway. Boot your phone into Odin mode (home, vol down, and power), connect your phone to PC with USB, and install twrp-3.0.0-0-klte-klte.img.tar with Odin (AP button, auto-reboot option disabled). When the status bar is filled, you need to immediately boot into TWRP without rebooting system (this is where you hold down home, vol up, and power). In TWRP, install supersu zip file. Now wipe cache and dalvik
If you reboot to normal android before booting into TWRP and flashing the supersu zip when TWRP is first installed, the operating system will overwrite TWRP with the stock recovery, and you have to try again.
Thanks OtisDog and thisisapoorusernamechoice.
While I am downloading TMB-G900TUVS1FOL1-20160111153316, I tried your directions for installing TWRP and had success. I was able to boot into TWRP. (First boot success since I started 10 days ago.) I downloaded supersu zip and have it on my Windows 10 computer. I assume that I do not unzip it in Windows, correct?
From TWRP I clicked on Install and got the phone's files. When I clicked on Select Storage, the USB storage choice has 0MB so the option is disabled. Should I have started TWRP with my USB cable still connected? My computer still recognizes that I am connecting something to it while TWRP is running.
If that is not the problem, how do I install supersu zip into my phone?
Dave4237 said:
Thanks OtisDog and thisisapoorusernamechoice.
While I am downloading TMB-G900TUVS1FOL1-20160111153316, I tried your directions for installing TWRP and had success. I was able to boot into TWRP. (First boot success since I started 10 days ago.) I downloaded supersu zip and have it on my Windows 10 computer. I assume that I do not unzip it in Windows, correct?
From TWRP I clicked on Install and got the phone's files. When I clicked on Select Storage, the USB storage choice has 0MB so the option is disabled. Should I have started TWRP with my USB cable still connected? My computer still recognizes that I am connecting something to it while TWRP is running.
If that is not the problem, how do I install supersu zip into my phone?
Click to expand...
Click to collapse
The supersu zip needs to be in your phone's internal storage or micro SD card. USB storage is not used for this
thisisapoorusernamechoice said:
The supersu zip needs to be in your phone's internal storage or micro SD card. USB storage is not used for this
Click to expand...
Click to collapse
Since my phone has no SD card slot, this sounds like a Catch 22. I can't get my phone to work without installing the supersu zip, but I can't install the supersu zip without getting my phone to work.
Fortunately, the file that OtisDog suggested DID work. THANK YOU. THANK YOU. THANK YOU.
My wife is also thrilled that I don't have a $160 brick. She sends hugs to both of you.
Dave4237 said:
Since my phone has no SD card slot, this sounds like a Catch 22. I can't get my phone to work without installing the supersu zip, but I can't install the supersu zip without getting my phone to work.
Fortunately, the file that OtisDog suggested DID work. THANK YOU. THANK YOU. THANK YOU.
My wife is also thrilled that I don't have a $160 brick. She sends hugs to both of you.
Click to expand...
Click to collapse
You don't need the SD card, you can put the supersu zip file in your phone's internal memory and flash it from there in TWRP. Also if you have a Galaxy S5, you have an SD card slot. It's on top of, yes literally on top of the SIM card slot, can be a little confusing and hard to see until you know what you're looking for (see attached pic for clarification, sorry for my halfassed paint job lol).
thisisapoorusernamechoice said:
You don't need the SD card, you can put the supersu zip file in your phone's internal memory and flash it from there in TWRP. Also if you have a Galaxy S5, you have an SD card slot. It's on top of, yes literally on top of the SIM card slot, can be a little confusing and hard to see until you know what you're looking for (see attached pic for clarification, sorry for my halfassed paint job lol).
Click to expand...
Click to collapse
Thanks for the photo. That helps.
My latest problem is that every time I restart my phone, some shortcuts (Hi, Google; Gallery; magazines; exercise; camera) are added to my home screens and the default home screen is changed. I suspect that by clearing one of the caches, I can fix this. What do I need to do?
You can go into settings and find "backup and reset".
In there uncheck the backup and then do the factory reset. This will wipe all data and reload the os like when the phone was new - you can then put on it what you want.
MAKE SURE you have anything that's on the phone now, that you want, backed up on your computer because it will get wiped off the phone.
Once you get the phone to where you want it we can work on rooting it.
Jim
The instructions from thisis... worked great for me, although I accidentally did a full wipe from TWRP - no biggie, I was backed up. Thanks!
I appreciate the clear and concise instructions I've seen so far, I got as far as flashing superSU zip and wiping cache and dalvik, what next?
NexMortifer said:
I appreciate the clear and concise instructions I've seen so far, I got as far as flashing superSU zip and wiping cache and dalvik, what next?
Click to expand...
Click to collapse
Reboot lol
Sent from my SM-N920G using XDA Labs
ShinySide said:
Reboot lol
Click to expand...
Click to collapse
wouldn't it be nice if that just worked?
sorry, enough sarcasm, I'll clarify, I got that far with everything going as intended, but after reboot, it's not rooted (according to rootchecker) and I don't know why. Additional device info:
SM-G900T
running 4.4.2 (it doesn't want to let me update for some reason, and I thought maybe old versions might be easier to root)
Baseband Version G900TUVU1CNK2
Build # is KOT49H.G900TUVU1CNK2
(if there's other info you need, let me know.)
NexMortifer said:
wouldn't it be nice if that just worked?
sorry, enough sarcasm, I'll clarify, I got that far with everything going as intended, but after reboot, it's not rooted (according to rootchecker) and I don't know why. Additional device info:
SM-G900T
running 4.4.2 (it doesn't want to let me update for some reason, and I thought maybe old versions might be easier to root)
Baseband Version G900TUVU1CNK2
Build # is KOT49H.G900TUVU1CNK2
(if there's other info you need, let me know.)
Click to expand...
Click to collapse
Yeah that's weird. Since you're running kit Kat should of installed system root. Or maybe I'm wrong on the zip being able to root kitkat/use system root instead of systemless.
Open the supersu app and see if it asks to update su binary
Otherwise I'd just try flashing it again in twrp or finding a much older supersu zip to flash. (Probably a 1.×× version)
You don't need to wipe caches tho.
Sent from my SM-N920G using XDA Labs
ShinySide said:
Open the supersu app and see if it asks to update su binary
Click to expand...
Click to collapse
App isn't showing up either, don't know if that's useful info or not.
NexMortifer said:
App isn't showing up either, don't know if that's useful info or not.
Click to expand...
Click to collapse
You are flashing it in twrp correct?
Because you should have SuperSU installed then
Sent from my SM-N920G using XDA Labs
ShinySide said:
You are flashing it in twrp correct?
Because you should have SuperSU installed then
Sent from my SM-N920G using XDA Labs
Click to expand...
Click to collapse
Yes, I did, and no, it didn't.
Well, I eventually gave up on that root technique, and ended up using This instead, so now I'm running 6.0.1, and it seems to be working alright, but SuperSU says "The SU bianary needs to be updated!" and when I click it, it offers me the options of "normal" and "TWRP/CWM" as ways to install the SU bianary.
I know just enough to know that I don't know what I'm doing, and thought I'd get some advice before I proceed to screw something up.
Which option should I go for, and if TWRP, do I need to re-flash it with Odin like I did to install the 6.0.1 ROM, or is the process different now?
NexMortifer said:
Well, I eventually gave up on that root technique, and ended up using This instead, so now I'm running 6.0.1, and it seems to be working alright, but SuperSU says "The SU bianary needs to be updated!" and when I click it, it offers me the options of "normal" and "TWRP/CWM" as ways to install the SU bianary.
I know just enough to know that I don't know what I'm doing, and thought I'd get some advice before I proceed to screw something up.
Which option should I go for, and if TWRP, do I need to re-flash it with Odin like I did to install the 6.0.1 ROM, or is the process different now?
Click to expand...
Click to collapse
I always just click normal. Then it'll ask to reboot and just allow it and you'll be good to go
Sent from my SM-N920G using XDA Labs
https://forum.xda-developers.com/tm...l/root-how-to-root-sm-g900t-firmware-t3358190
use that guide, follow it precisely and you will be fine
hi
i've used two smartphones before GR5 and i've rooted then easily without and thing happens to my internal or external data
but i've seen alot of "Attentions" to take a complete backup of phone cuz root will format all ur system
is it true !! ??
aliraqi2009cs said:
hi
i've used two smartphones before GR5 and i've rooted then easily without and thing happens to my internal or external data
but i've seen alot of "Attentions" to take a complete backup of phone cuz root will format all ur system
is it true !! ??
Click to expand...
Click to collapse
Hello mate, I understand your question. However, i want to assure you that the action of rooting itself (Flashing SuperSU zip) will not format ur system. Only does a little modification. Nothing you will notice really. Except the addition of the SuperSU app in your app drawer.
However, actions like Unlocking your boot-loader which you need to get to the rooting aspect (flashing custom recovery), can do some wipes. That is why you are advised to backup first.
On a final note, you are advised to boot into the custom recovery first 'fastboot boot recovery.img' before doing any rooting or whatever so that you can always have a 'safe point' to get your phone back to fully stock working state incase anything goes wrong.
If you have any further doubts, feel free to ask. Cheers!
stanley08 said:
Hello mate, I understand your question. However, i want to assure you that the action of rooting itself (Flashing SuperSU zip) will not format ur system. Only does a little modification. Nothing you will notice really. Except the addition of the SuperSU app in your app drawer.
However, actions like Unlocking your boot-loader which you need to get to the rooting aspect (flashing custom recovery), can do some wipes. That is why you are advised to backup first.
On a final note, you are advised to boot into the custom recovery first 'fastboot boot recovery.img' before doing any rooting or whatever so that you can always have a 'safe point' to get your phone back to fully stock working state incase anything goes wrong.
If you have any further doubts, feel free to ask. Cheers!
Click to expand...
Click to collapse
Thanks very much 4 ur answer >> i got ur answer
let me ask u once again >>> How i can take full backup of my phone ?? in case of any problems happen
aliraqi2009cs said:
Thanks very much 4 ur answer >> i got ur answer
let me ask u once again >>> How i can take full backup of my phone ?? in case of any problems happen
Click to expand...
Click to collapse
That's easy. I would advise that instead of flashing custom recovery first, you only boot into it temporarily. This way, when you take full backup, it includes stock recovery also. Also i recommend you do it before rooting (flashing SuperSU zip). This way, you can a CLEAN, stock recovery-no root system to return to. Out-of-the-box state
So instead of flashing custom recovery using
'fastboot flash recovery recovery.img'
You use
'fastboot boot recovery.img'
This way it will only boot you into that custom recovery. TWRP. And you can backup by selecting 'backup' then simply choose the memory with more available storage. Preferably the external sd card if you have a high capacity one. Depending on how much stuff u have installed on your phone. You need 3 to 5GB for the backup.
Leave everything checked (exclude data if you want a clean version, but if you want to include your installed apps, settings etc then leave data checked. But of course data takes the more backup space), this is similar to creating a restore point in windows.
After deciding if you want to keep ur current setup in the backup or not, simply slide the slider below to start the backup process. Depending on how fast your memory card is, the process should take 5 to 15 mins MAX.
After doing the backup, you can just flash the SuperSU zip using the Install Zip option in TWRP home screen. After flashing SuperSU zip you reboot and let it work. Your phone might reboot a few times. If you get a prompt just select no. After reboot you have root, now u should decide if you still want to flash TWRP permanently. Because unless you need to do something else like flash another ROM. You do not need it immediately
NOTE: Use 5-14 version of TWRP instead of the older 3-12 or so. This version backs up more partitions. Like the CUST for instance.
Please ask if you don't understand anything. Happy flashing! xD
stanley08 said:
That's easy. I would advise that instead of flashing custom recovery first, you only boot into it temporarily. This way, when you take full backup, it includes stock recovery also. Also i recommend you do it before rooting (flashing SuperSU zip). This way, you can a CLEAN, stock recovery-no root system to return to. Out-of-the-box state
So instead of flashing custom recovery using
'fastboot flash recovery recovery.img'
You use
'fastboot boot recovery.img'
This way it will only boot you into that custom recovery. TWRP. And you can backup by selecting 'backup' then simply choose the memory with more available storage. Preferably the external sd card if you have a high capacity one. Depending on how much stuff u have installed on your phone. You need 3 to 5GB for the backup.
Leave everything checked (exclude data if you want a clean version, but if you want to include your installed apps, settings etc then leave data checked. But of course data takes the more backup space), this is similar to creating a restore point in windows.
After deciding if you want to keep ur current setup in the backup or not, simply slide the slider below to start the backup process. Depending on how fast your memory card is, the process should take 5 to 15 mins MAX.
After doing the backup, you can just flash the SuperSU zip using the Install Zip option in TWRP home screen. After flashing SuperSU zip you reboot and let it work. Your phone might reboot a few times. If you get a prompt just select no. After reboot you have root, now u should decide if you still want to flash TWRP permanently. Because unless you need to do something else like flash another ROM. You do not need it immediately
NOTE: Use 5-14 version of TWRP instead of the older 3-12 or so. This version backs up more partitions. Like the CUST for instance.
Please ask if you don't understand anything. Happy flashing! xD
Click to expand...
Click to collapse
Thanks for the infos
PalakMi said:
Thanks for the infos
Click to expand...
Click to collapse
You are welcome mate. Enjoy ur GR5/5X!
stanley08 said:
You are welcome mate. Enjoy ur GR5/5X!
Click to expand...
Click to collapse
Actually it's my brother's 5x, thanks again
PalakMi said:
Actually it's my brother's 5x, thanks again
Click to expand...
Click to collapse
Pass the message on to him xD
stanley08 said:
Pass the message on to him xD
Click to expand...
Click to collapse
Roger that