Warning about using CWM.zip (temporary / Touch recovery) to root or flash any file
Note : This is referance only to CWM.zip , which is temporary/touch recovery commonly used to root device. Other cwm recoveries which are permanent and getting along with custom kernels are safe.
Entropy have quoted this
Entropy512 said:
After seeing multiple reports of Superbricks connected with a "cwm.zip" - I've finally found the source of that file - here.
I checked the recovery binary using "strings" to see if it was a "dangerous" or "safe" one.
Code:
[email protected]:~/Documents/galaxynote/tmp/sbin$ strings recovery |grep discard
warning: %s: Wipe via secure discard failed, used discard instead
discard_after_textures
discard_before_textures
Can't discard critical data on CRC error.
discard
discard
The key here is that warning - if that string is present in a binary, it is most likely a dangerous one. Since there have been multiple reports of bricks associated with this zip file, I've sent the moderators a report that this release should be removed.
Click to expand...
Click to collapse
DON'T USE CWM.zip (touch recovery) at all
Present option to root ICS ROM is
So present option for rooting is - You can select any of one.
1. Short, easy - requires to reset counter
-Download Odin (.tar) version of custom kernel like Notecore, Speedmod, CF root kernel Or other any with same function.
-Flash it using PC odin for PDA tab.
-You will get exclamation mark and raised counter, which can be reset with Triangle Away
2. Long, No raised couter OR Exclamation mark
-Downgrade to Rootable GB ROM and Root it. OR Download This pre rooted GB ROM and flash using PC Odin
-Wipe cache, data and delvic cache from recovery
-Install Mobile Odin Pro
-Copy ICS ROM file in .tar (you want to flash) to Internal SD card (recommended, but you can have it on EXT too)
-Copy one of custom Kernel in .tar file e.g.Notecore, Speedmod, CF root kernel Or other any with same function.
-Open Mobile Odin Pro
-select open file
-Point to ROM file you have copied
-All fiels will popup and feel automatically
-select kernel and point to custom kernel file you have copied
Flash.
Done!
Damn !!! just when you think we're making progress and things and things are getting 'safer' something like this happens
Good find :good: well done !!
Do we have any working methods for rooting the latest 4.0.4 Stock ROMS at the moment ?
Or do we need to wait till a fixed CWM is available ?
I think available option is
-Flashing custom kernel with PC odin, and then reseting counter with triangle away
-switching Rooted ROM to ICS with Mobile odin pro
dr.ketan said:
Warning about using CWM.zip to root or flash any file
Or it is same unsafe like using backup/restore/wipe function with CWM.zip
Click to expand...
Click to collapse
backup?! is backup also dangerous on an effected kernel? I understand it writes the backup image ,but that's usually to the external SD card which is unaffected by the bug due to different hardware
are you sure a backup is as dangerous as a restore? I backup all the time on an affected kernel
How about mobile odin. Is it safe.
Sent from my GT-N7000 using xda app-developers app
I'm on anidroid rom with anidroid kernel and recovery.
Will I brick when I wipe in cwm using this setup?
Sent from my GT-N7000 using xda premium
dr.ketan said:
-switching Rooted ROM to ICS with Mobile odin pro
Click to expand...
Click to collapse
Yin-Yang said:
How about mobile odin. Is it safe.
Sent from my GT-N7000 using xda app-developers app
Click to expand...
Click to collapse
Yes, Mobile Odin should be safe if you read what Dr.Ketan said.
---------- Post added at 09:39 AM ---------- Previous post was at 09:38 AM ----------
msedek said:
I'm on anidroid rom with anidroid kernel and recovery.
Will I brick when I wipe in cwm using this setup?
Sent from my GT-N7000 using xda premium
Click to expand...
Click to collapse
No, you are safe. From everything I am reading, this is different.
Damn it. I used to flash SpeedMod kernel from "CWM.zip" to root ICS.
But only kernels not ROMs or never used it to factory reset or backup / restore.
From now on I'll use only PC Odin.
edit...
I just checked that Note has 12 partitions and one of those is kernel partition. And last thing I want is corrupt kernel partition.
As Dr Ketan and Entropy told, stay away from "CWM.zip"
This is really weird. Ive been using this cwm to flash ics and gb and my phone does have the emmc bug. I made this like 6 or 7 times and had no problem at all... o.o maybe im just lucky
Enviado de meu GT-N7000 usando o Tapatalk 2
Are there any other ways to root the device, now that CWM.zip is known to be dangerous....
Sent from my GT-N7000 using Tapatalk 2
Cruzaders said:
This is really weird. Ive been using this cwm to flash ics and gb and my phone does have the emmc bug. I made this like 6 or 7 times and had no problem at all... o.o maybe im just lucky
Enviado de meu GT-N7000 usando o Tapatalk 2
Click to expand...
Click to collapse
I wouldn't be so sure of that. Have you tried that eMMc app that chainfire made in Themes/Apps to see if you have a corrupted firmware?
---------- Post added at 10:06 AM ---------- Previous post was at 10:06 AM ----------
ckmemphis said:
Are there any other ways to root the device, now that CWM.zip is known to be dangerous....
Sent from my GT-N7000 using Tapatalk 2
Click to expand...
Click to collapse
Use PC Odin.
Even I've rooted with the CWM.zip file available in Dr.Ketan's thread a couple of times. But I only use it for installing the SU-Busybox Installer.
I flash everything else with Mobile ODIN.
By the way, If I root using this method, do I lose root if I factory reset? (I'm on speedmod kernel, which is told to be safe)
Or do I have to specifically use the SU-Busybox Uninstaller to Unroot?
Is it safe unrooting after such a discovery has been made?
Does flashing the Busybox ZIP files using this CWM.zip perform any wipes?
satishp said:
Even I've rooted with the CWM.zip file available in Dr.Ketan's thread a couple of times. But I only use it for installing the SU-Busybox Installer.
I flash everything else with Mobile ODIN.
By the way, If I root using this method, do I lose root if I factory reset? (I'm on speedmod kernel, which is told to be safe)
Or do I have to specifically use the SU-Busybox Uninstaller to Unroot?
Is it safe unrooting after such a discovery has been made?
Does flashing the Busybox ZIP files using this CWM.zip perform any wipes?
Click to expand...
Click to collapse
Factory reset wont erase root
Y u needbto uninstall busybox i dont understand.
Flashing busybox dont cause any wipe n i am still in process to discuss with entropy, if it is safe just for rooting purpose.
Sent from my GT-N7000 using xda premium
dr.ketan said:
Factory reset wont erase root
Y u needbto uninstall busybox i dont understand.
Flashing busybox dont cause any wipe n i am still in process to discuss with entropy, if it is safe just for rooting purpose.
Sent from my GT-N7000 using xda premium
Click to expand...
Click to collapse
so if cwm.zip not save, can u give me link step-by-step to root my galnote in safest way?coz 2 weeks ago i superbrick my galnote once using cwm.zip..
Use custom kernel e.g. speedmod CF root kernel in tar format and flash using PC odin. You will get raised counter and exclamation mark. That can be reset using triangle away application by CF.
dr.ketan said:
Factory reset wont erase root
Y u needbto uninstall busybox i dont understand.
Flashing busybox dont cause any wipe n i am still in process to discuss with entropy, if it is safe just for rooting purpose.
Sent from my GT-N7000 using xda premium
Click to expand...
Click to collapse
I asked because incase I ever need to take the device to a service centre, do I still have to uninstall busybox using SU-busybox Uninstall ZIP file? Because there is no other evidence of the device being rooted other than the busybox application on the phone as the counter is still at 0.
I've never tried unrooting though. So I was wondering whether factory reset would remove busybox as it saves the hassle of unrooting or even flashing back stock via ODIN.
Sorry for being offtopic, I also wanted to ask you one more thing, as you have an Indian Galaxy Note, are you seeing any "clipping" when playing videos with dark scenes or viewing images with dark shadows? Because every Note I've seen here has this issue and there are a lot of threads in XDA describing this issue.
dr.ketan said:
Use custom kernel e.g. speedmod CF root kernel in tar format and flash using PC odin. You will get raised counter and exclamation mark. That can be reset using triangle away application by CF.
Click to expand...
Click to collapse
will it work?bcoz im in ICS ROM.. do i need to downgrade it to GB first?or just flash it?i would like to flash paranoidandroid hybrid ROM, any suggestion?
satishp said:
I asked because incase I ever need to take the device to a service centre, do I still have to uninstall busybox using SU-busybox Uninstall ZIP file? Because there is no other evidence of the device being rooted other than the busybox application on the phone as the counter is still at 0.
I've never tried unrooting though. So I was wondering whether factory reset would remove busybox as it saves the hassle of unrooting or even flashing back stock via ODIN.
Sorry for being offtopic, I also wanted to ask you one more thing, as you have an Indian Galaxy Note, are you seeing any "clipping" when playing videos with dark scenes or viewing images with dark shadows? Because every Note I've seen here has this issue and there are a lot of threads in XDA describing this issue.
Click to expand...
Click to collapse
No factory reset won't remove busybox, and unrooting will leave some footprint.
So best way before sending service centre is just to flash stock GB ROM using PC odin + Wipe
No i have never experience clipping issue.
Matchstick said:
Do we have any working methods for rooting the latest 4.0.4 Stock ROMS at the moment ?
Or do we need to wait till a fixed CWM is available ?
Click to expand...
Click to collapse
Flash a custom kernel.
Cruzaders said:
This is really weird. Ive been using this cwm to flash ics and gb and my phone does have the emmc bug. I made this like 6 or 7 times and had no problem at all... o.o maybe im just lucky
Enviado de meu GT-N7000 usando o Tapatalk 2
Click to expand...
Click to collapse
You got lucky. Secure erase does not always do damage - in fact it frequently doesn't. But every time you do it, there's a risk of damage.
ckmemphis said:
Are there any other ways to root the device, now that CWM.zip is known to be dangerous....
Sent from my GT-N7000 using Tapatalk 2
Click to expand...
Click to collapse
Flash a custom kernel using PC Odin. Then flash SuperSU or Superuser using it.
Reset the flash counter with TriangleAway
If you wish, reflash the stock kernel for your release with PC Odin.
Even if current custom kernels have some sort of incompatibility with the latest firmwares, to my knowledge all of them (even the obsolete and unmaintained DAFUQ) will allow you to install SuperSU or Superuser then run TriangleAway before flashing back to the stock kernel.
Related
Do you face problem moving app to SD card!
Do you have problem restoring from Titanium Backup!
Do you face problem installing some apps from Market!
It seems the problem happened after rooting "CF-Root-SGS2_XX_OXA_LPH-v5.2-CWM5.tar" ; Always thanks to (Chainfire)
NEW SOLUTION: Siyah Kernel ICS-(Retouched) 3.0alpha2-LPH
I've just installed Siyah Kernel ICS and everything working fine with me
Please check and update thread if you face any problem.
(Always, Don't forget to backup)
DOWNLOAD LINK: http://gokhanmoral.desean.net/siyahkernel/v3.0/ICS-Only-For-Samsung-ROMS-Not-CM9/siyah3-alpha2.tar
Full details of Siyah Kernel ICS link: http://www.gokhanmoral.com/gm/2012/03/08/siyahkernel-ics-retouched-3-0alpha2-lph
Also, you can use EXTweaks from market: https://play.google.com/store/apps/details?id=com.darekxan.extweaks.app
__________________________________
OLD SOLUTION:
Well, Here is two steps solution: Thanks to (donalgodon)
First:
Flash zImage of LPH Kernel original* (by CWM Manager - Flash Kernel**).
. -phone will reboot after flashing kernel
Second:
Flash zImage of LPH CF-Root LPH v5.2 kernel* (by CWM Manager - Flash Kernel**).
. -phone will reboot after flashing kernel
* zImage (LPH Original + LPH Root Kernels) download link = www.mediafire.com/?vw8xib282b2pg1i
** How to video = http://youtu.be/ug4c2oG9LBs
That's all........
- Super user is working.
- CWM Manager is working.
- Moving app to SD Card is working.
- Restoring from Titanium Backup is working.
- Installing apps from Market (such as Ant Smasher game) is working.
Hope I added helpful solution.
great its working now good work bro
NOMIOMI said:
great its working now good work bro
Click to expand...
Click to collapse
You are most welcome
thnks its working now good work
kiriakos1963 said:
thnks its working now good work
Click to expand...
Click to collapse
Glad it works with you
this is the only workaround possible but one drwaback would be if you want cwm recovery again, you have to flash the cf root tar file via odin again
Please remove
Is this not the same workaround Chainfire has been discussing weeks ago?
http://forum.xda-developers.com/showpost.php?p=22138788&postcount=4211
Chainfire said:
Ok, so now I've tested a lot of things, a lot of tries, I'm not sure if it sticks in my head correctly.
I can only get the SD problem when transationing from official kernel + 0 counter to unofficial counter.
Afterwards, it seems flashing back the official kernel (triangle disappears) with ODIN, then flashing back CF-Root with CWM app or Mobile ODIN (preferred) solves the issue for me, every time.
I've also seen it appear/disappear with change of signatures, and then I couldn't reproduce the problem anymore, but the above procedure seems to work.
Click to expand...
Click to collapse
crachel said:
Is this not the same workaround Chainfire has been discussing weeks ago?
http://forum.xda-developers.com/showpost.php?p=22138788&postcount=4211
Click to expand...
Click to collapse
Yes, it is, but people are still asking this question without bothering to search(or don't know the terms so are unable to find) and the answer is buried under a few pages of posts.
Maybe this thread is necessary for those people but this has been discussed before so your call.
I did and it works. Thanks.
bala_gamer said:
this is the only workaround possible but one drwaback would be if you want cwm recovery again, you have to flash the cf root tar file via odin again
Click to expand...
Click to collapse
I did not understand (maybe because my english is terrible eheh).
Now, with this method, I have my phone rooted but stock recovery. Is there a way to get cwn recovery and no sd problem?
whats with people rating this thread down. sigh...
Mate thank you so muchGave you 5 stars.Flashed the zImage and got all my apps finally over to the SD as the LP6 wouldnt flash on my version of ROM for some reason.If I need to Ill flash the CF-Root back for a CWM backup.Well done.
I dont quite follow this either. I have flashed the zImage of original XXLPH kernel, but now what??
Do I need to flash the kernal again via Odin to get CWM back fully operational??
I have a diff. Firmware, CheckRom6 & Redpill Kernel 1.3. And despite of Download Counter 0 I have the problem with Titanium some apps' not flashing back, too. (had the problem already with CheckRom4 / Syiah, too).
nickmax1 said:
I dont quite follow this either. I have flashed the zImage of original XXLPH kernel, but now what??
Do I need to flash the kernal again via Odin to get CWM back fully operational??
Click to expand...
Click to collapse
Just flash the CF-Root kernel's zImage file via the CWM app and you will get root & CWM working again.
akbarhash said:
Yes, it is, but people are still asking this question without bothering to search(or don't know the terms so are unable to find) and the answer is buried under a few pages of posts.
Maybe this thread is necessary for those people but this has been discussed before so your call.
Click to expand...
Click to collapse
Even though got to solution by try & error; Yes, it is there in the deep of long thread.
Just want to put it up in simple well detailed steps since many people facing such problems and asking for.....
I followed the advice in Chainfire's very long thread after finding it here, and it worked for me.
I used this procedure:
1. rooted via CF-Root using Odin.
2. flashed the old bootloader using Odin.
3. reset flash counter via Jig.
4. flashed the ICS bootloader using Odin.
5. flashed the stock kernel using CWM app.
6. flashed the CF-kernel using CWM app.
SD works fine and root is retained.
ahh thank you!
thanks, this works fine for me.
you mean after flashing the zimage kernel you need to flash the http://download.chainfire.eu/147/CF-Root/SGS2/CF-Root-SGS2_XX_OXA_LPH-v5.2-CWM5.zip
to get CWM working again?
This guide is for those that require to return COMPLETLEY to stock (out of the box) and your firmware version is not yet available for download.
You must be; rooted, CWM Recovery and have an original nandroid backup (made after first root, and before flashing any custom ROM or non-regional firmware other than recovery or modem)
Australian Optus Nandroid :
* [email protected] has been kind enough to upload here
* You will need to Triangle Away, so begin at step #1
* I have not personally tested this nandroid, only my own
Australian Vodafone Nandroid :
* [email protected] has been kind enough to upload here
* You may need to Triangle Away, so begin at step #1
* Again, I have not personally tested this nandroid, only my own
Modem & Stock Recovery
* Not backup by CWM, thus you may need to restore your original
Modem Collection :
* [REF] Galaxy S3 Modem / Radio Collection (I9300 & I9300T ONLY) CWM & Odin Flashable
Android System Recovery 3e :
* CWM_Stock_I9300_Recovery.zip attached
* Stock recovery is the SAME between I9300 or I9300T versions
[Guide] Return to Stock from Original CWM Backup - No firmware released for download
Requirements:
1. Have a nandroid backup of your original stock firmware
2. Root & CWM Recovery
3. Triangle Away app
4. SU-BusyBox-CWM_Manager-Uninstaller.zip (wipes SU binary, SuperUser, BusyBox and CWM Manager v3.50/3.55/3.60)
5. CWM_I9300_Stock_Recovery.zip
6. CheckFus Downloader app to check Product Code (SGS2 dialer code *2767*4387264636# does not work)
7. CWM flashable modem.zip (if not original baseband version)
METHOD:
1. Use Triangle Away app to reset binary download counter
2. Boot into CWM Recovery
3. Restore "original" nandroid backup (ensure the name has not been modified or you may experience md5 mismatch)
4. Reboot & check for and uninstall any remaining User apps that require SU
5. Boot in CWM Recovery
6. Flash modem.zip (only if baseband is not original)
If you did not Triangle Away before making the original backup, your binary flash counter may not be restored as zero, so reboot and reset before proceeding to step#7
Click to expand...
Click to collapse
7. Flash SU-BusyBox-CWM_Manager-Uninstaller.zip
8. Flash CWM_I9300_Stock_Recovery.zip
9. Factory reset
10. Reboot system
11. Check settings > about device > status > device status > scanning............... Normal (This may take a few minutes)
12. Sign into Google Play & install CheckFus app. Product code should be correct
If returning for warranty:
13. Delete all contents of internal sdcard "phone"
14. Factory reset again and power off
All tested on my own device
Hope this helps some Hit THANKS if it has
Added Disclaimer: All your own risk. I am not responsible for anything you may try here. I didn't make you do it, blah blah blah
Thanks for this, really appreciate it!
I found a typo in one of your sentences:
Baseband I9300DTULE6 can be found here:
Click to expand...
Click to collapse
I really think you meant I9300TDULE6
kelvinyap9 said:
Thanks for this, really appreciate it!
I found a type in one of you sentences:
I really think you meant I9300TDULE6
Click to expand...
Click to collapse
Correcting...
Cheers
Sent from my GT-I9300T using xda premium
Anyway, I'm at the process of getting ready to do a NANDROID backup (already put an SD card in the phone).
As I'm aware, the stock recovery doesn't do NANDROID backups. Would I need to flash CWM (Chainfire one) via ODIN before doing so?
UPDATE: Never mind, NANDROID is a CWM feature x)
kelvinyap9 said:
Anyway, I'm at the process of getting ready to do a NANDROID backup (already put an SD card in the phone).
As I'm aware, the stock recovery doesn't do NANDROID backups. Would I need to flash CWM (Chainfire one) via ODIN before doing so?
Click to expand...
Click to collapse
Recommend it. Just follow Chainfire guide exactly.
Copy the backup found in clockworkmod folder to PC for safe keeping.
Once rooted, search for EFS Backup Pro and copy the backup to PC too. CWM will not back this up either. If this every becomes corrupted (and no backup) = iPod (no cellular network)
Sent from my GT-I9300T using xda premium
Thanks man, that's what I was heading towards but you beat me to it.
Sent from my GT-I9300T using xda premium
Lonski said:
Thanks man, that's what I was heading towards but you beat me to it.
Sent from my GT-I9300T using xda premium
Click to expand...
Click to collapse
Yeah, took a "little" bit of flashing just to prove the method works. Anyone following the steps and links to the appropriate guides shouldn't have any trouble.
Had other ideas such as how to dump your firmware and re-package into Odin flashable .tar file . This took a while, so maybe I'll add the other method in future. Wife is on my case
Sent from my GT-I9300T using xda premium
Rooted my phone,made a nandroid backup,flashed cm9,restored using original nandoid backup then used triangleaway to reset counter which shows 0,flashed a custom kernel on stock rom.Baseband has reverted to normal but device status showing modified.How to change it to normal?
Sent from my G-I9300 using Tapatalk 2
rock2702 said:
........flashed a custom kernel on stock rom.Baseband has reverted to normal but device status showing modified.How to change it to normal?
Click to expand...
Click to collapse
You didn't follow the guide did you?
Your firmware is now "modified" from the original (out of the box) having flashed a custom kernel. Also, depending on the flash method (Odin?), your counter most likely increased again
If you want completely back to original (out of the box state) firmware, follow the guide in FULL >> Redo steps 1-9 (or 1-11)
Obviously, if your official firmware is available for download somewhere, this guide becomes redundant. Flashing a complete official firmware will remove the modified status, but yours isn't completely official/stock now is it?
But, if this is want you want
This guide is for those that require to return COMPLETLEY to stock (out of the box) and your firmware version is not yet available for download.
Click to expand...
Click to collapse
, follow the guide step-by-step and it will work!
To avoid any further confusion I've added to the OP......... COMPLETLEY to stock (out of the box).......
Actually i did all this before you posted this thread.I used triangle away and the official counter is showing 0.My firmware is not up for download still but i made the nandroid backup before flashing cm9.
I rooted my phone using cf root by chainfire and then flashed cm9 using cwm.But then i returned to stock using my backup,then flashed a custom kernel using mobile odin pro.If i flash my stock kernel will my device status be normal again?
Also wanted to ask if the efs backup pro is an android app?I dloaded the zip on my cell as i dont have pc now,should i flash the zip using cwm to get efs pro app?
Sent from my GT-I9300 using Tapatalk 2
rock2702 said:
Actually i did all this before you posted this thread.I used triangle away and the official counter is showing 0.My firmware is not up for download still but i made the nandroid backup before flashing cm9.
I rooted my phone using cf root by chainfire and then flashed cm9 using cwm.But then i returned to stock using my backup,then flashed a custom kernel using mobile odin pro.If i flash my stock kernel will my device status be normal again?
Also wanted to ask if the efs backup pro is an android app?I dloaded the zip on my cell as i dont have pc now,should i flash the zip using cwm to get efs pro app?
Sent from my GT-I9300 using Tapatalk 2
Click to expand...
Click to collapse
I haven't tested any other method, as I was more concerned with getting the stock recovery.zip and proofed.
No counter + unroot + complete official firmware package => status = "normal".
If you flash an official kernel that is a different version to that of your official package, this would most likely "corrupt" the product code, so its not recognized = "modified".
These mix and match official firmware are referred as "Frankenstein".
EFS Backup Pro
http://forum.xda-developers.com/showthread.php?t=1308546
There are other methods, have a search...
Sent from my GT-I9300T using xda premium
I have a question, i followed the steps my phone shows normal for the device status but i still have cwm in my app drawer.
gadget069 said:
I have a question, i followed the steps my phone shows normal for the device status but i still have cwm in my app drawer.
Click to expand...
Click to collapse
CWM Manager app was installed when you first installed Chainfire CWM Recovery, and was back upped with your original nandroid.
You have not followed all the steps.....
Check steps #10 and #11
Sent from my GT-I9300T using xda premium
Thanks heaps for this.. I was trying to unroot & remove cwm recovery from my Optus Galaxy SIII all day yesterday with no luck since I couldn't find the stock Optus Australia firmware.. I skipped step 3 & 4 since all I did was flashing the CF-Root kernel . Now I can send this back without worrying
I did all those yesterday except I couldn't get back the stock recovery. Flashing the stock kernel didn't work. All good now
kamalmawa said:
Thanks heaps for this.. I was trying to unroot & remove cwm recovery from my Optus Galaxy SIII all day yesterday with no luck since I couldn't find the stock Optus Australia firmware.. I skipped step 3 & 4 since all I did was flashing the CF-Root kernel . Now I can send this back without worrying
I did all those yesterday except I couldn't get back the stock recovery. Flashing the stock kernel didn't work. All good now
Click to expand...
Click to collapse
Nice to hear success and was useful for you. Hope you get it back soon.
Hit thanks if you have the time
Sent from my GT-I9300 using xda premium
I only have a backup made before rooting, made with stock recovery.
This method will work for me?
But, my FW version is available. If I flashed through Odin I'll increase the counter. I'm a little bit lost here.
Yusei said:
I only have a backup made before rooting, made with stock recovery.
This method will work for me?
But, my FW version is available. If I flashed through Odin I'll increase the counter. I'm a little bit lost here.
Click to expand...
Click to collapse
I don't see how nandroid can be made without CWM recovery or various tools using ADB commands.
A nandroid backup is typically made up of:
1. boot.img
2. cache.ext4.tar
3. data.ext4.tar
4. nandroid.MD5 checksum
5. recovery.img
6. system.ext4.tar
Flashing any official firmware with Odin does not increase any counter.
++ This guide is not for you ++
For your case;
1. Use Triangle Away app to reset any counter
2. Flash official firmware with Odin (this will also remove root)
3. Wipe any evidence of SU apps and delete contents of internal sdcard
4. Maybe Factory reset before sending the phone off
Sent from my GT-I9300 using xda premium
With stock recovery I've made a backup xD
In that day I don't even bother with warranty, my wish was enter again in flashmaniac mode xD
I'm on my phone so I can't see if you have PayPal account, but if you have I'll buy you a beer.
Thanks dude, really thanks.
Yusei said:
With stock recovery I've made a backup xD
In that day I don't even bother with warranty, my wish was enter again in flashmaniac mode xD
I'm on my phone so I can't see if you have PayPal account, but if you have I'll buy you a beer.
Thanks dude, really thanks.
Click to expand...
Click to collapse
No problem. Happy my guide was of use.
Have Paypal, but happy to help out fellow XDA members and you hitting the "thanks" is enough.
Cheers
Sent from my GT-I9300 using xda premium
If I have not done any modifications than rooted can I triangle away then boot to cwm then install su unistaller and after that stock recovery and I'm done?
E: I read a guide where first triangle away then cwm and full wipe then odin flash and after that factory reset and I don't want to lose all data. Is the su app that is the reason for modified status as it's easy to remove in cwm before odin flash to stock?
Sent from my GT-I9300 using xda app-developers app
Pretty much a redundant thread, seeing as everyone is doing it now. (But not before I ported the method from SGS II by Phil 3759 http://forum.xda-developers.com/member.php?u=4666971 )
Still makes interesting reading though.....
Thank you for your feedback and link here
But your post links are broken as you copy pasted and forum shortcuts them
So, original thread here:
http://forum.xda-developers.com/showthread.php?t=1746794
Also linked in my signature
Please, ask questions there, I will not monitor this thread for support, so cannot answer questions
Phil3759 said:
Thank you for your feedback and link here
But your post links are broken as you copy pasted and forum shortcuts them
So, original thread here:
http://forum.xda-developers.com/showthread.php?t=1746794
Also linked in my signature
Please, ask questions there, I will not monitor this thread for support, so cannot answer questions
Click to expand...
Click to collapse
Thank you - (fixed it)
shoey63 said:
Possibly the easiest method yet! (Unless you want to PC Odin custom kernel and use potentially dangerous Triangle away to reset counter and get rid of yellow triangle)
1) Download this file:- http://forum.xda-developers.com/attachment.php?attachmentid=1256643&d=1344771266 (comes from this thread - http://forum.xda-developers.com/showthread.php?t=1746794 Kudos to Phil 3759)
2) Copy to external SD card
3) Reboot into stock recovery and select "apply update from external storage"
4) Select "CWM_Root_SuperSU.0.94-Busybox.1.20.2-S2-signed.zip" and wait for Superuser and Busybox to install
5) Go back and reboot system.
Done! You now have fully rooted stock ICS (works on 4.04). Don't forget you are also on stock kernel so NO WIPING!!!
If u want custom kernel, use mobile Odin afterwards.
(BTW dont forget to open superSU after reboot to update binary)
Click to expand...
Click to collapse
That's not rooting - that's rooting AND installing busybox. Sometimes installing busybox can cause problems on a device.
To root, it's simple:
Go to Chainfire's SuperSU thread
Download the latest "CWM-flashable" version
Put on external SD
Flash from recovery
This WON'T also add busybox which can sometimes cause problems.
The reason this works: With ICS updates for I9100/N7000/I777/probably others, Samsung started permitting ZIPs signed with testkeys to be flashed from recovery.
This does not appear to work on newer devices - fails on N8000/N8013 for example.
Hello,
Does this mean if I do this to my note running N7000DDLR6 (don't if its required to mention this), I'll be able to under-clock it and remove system apps without anything more? and that It will be totally safe?
what precautions need to be taken while doing this and after that?
Regards
Sujai
sujaishukla said:
Hello,
Does this mean if I do this to my note running N7000DDLR6 (don't if its required to mention this), I'll be able to under-clock it and remove system apps without anything more? and that It will be totally safe?
what precautions need to be taken while doing this and after that?
Regards
Sujai
Click to expand...
Click to collapse
Ofcourse not, after rooting you are not safe anymore.
If you delete something vital your phone won't boot anymore.
So only root after reading and understanding what you are doing or intent to do...
Entropy512 said:
That's not rooting - that's rooting AND installing busybox. Sometimes installing busybox can cause problems on a device.
...
This WON'T also add busybox which can sometimes cause problems.
Click to expand...
Click to collapse
It can be true under some circumstances, but:
- Many good applications will not run without busybox installed in /system/xbin. Some can chose to go without them, others no. Until developers start including their busybox under their app folder (like Titanium Backup), there will be no other choice if you do need those applications
- Without busybox, you loose a lot of commands under the terminal console. End users do not care, until they need debugging...
- CWM recovery installs busybox in /sbin, it is even completely built into his recovery. So, every time you have cwm installed, you end up with busybox (Most if not all custom kernels/ROMs are concerned that way, include CF-Root kernels...)
- Installing busybox from a market installer is a real mess while installing it through a recovery script can be fully undone
Entropy512 said:
...
Click to expand...
Click to collapse
I'm sorry, but wasn't the CWM.zip the problem for fast few weeks? How come out of nowhere it's "OK" to install the flashable/temporary CMW and it is the Busybox causing the problem?
Please make it clear - is it the CMW.zip counting as "Unsafe" or it is something else?
Spo0f said:
I'm sorry, but wasn't the CWM.zip the problem for fast few weeks? How come out of nowhere it's "OK" to install the flashable/temporary CMW and it is the Busybox causing the problem?
Please make it clear - is it the CMW.zip counting as "Unsafe" or it is something else?
Click to expand...
Click to collapse
The root methods mentioned above can be done from stock recovery skipping the cwm temporary step
Busybox can cause issues with some applications that rely on a generic busybox copy under /system/xbin
This is caused by the fact that each busybox build can have different valid commands. The application cannot know if the commands it needs are supported unless it is bundled with its own busybox copy. It will rely on the compiler of busybox to implement the commands.
Until now, I never encountered such problems with last busybox, but, it doesn't mean one of your apps will never behave strangely...
This is a problem related to the application its self, not busybox specifically
So to summarize this in clear words for note users it should be:
-Note users can easily get root only by flashing supersu or superuser (CWM flashable zips) through stock rom recovery directly,no need for CWM.ZIP at all.
-Note users can also get root + busybox by flashing CWM.ZIP old safe non touch v 4.x through stock recovery first,then to flash supersu/superuser+busybox zip through the temp CWM 4.
Am i right guys? plz do confirm...
Also what about wiping now through temp CWM4 with ICS rooted stock kernel? is it safe now??
↖(^▽^)↗ Sent from Rego Galaxy Note ↖(^▽^)↗
Entropy512 said:
That's not rooting - that's rooting AND installing busybox....
Click to expand...
Click to collapse
OK thanks, forgot to mention that, I'll amend OP
Already answered
eng.rego said:
So to summarize this in clear words for note users it should be:
-Note users can easily get root only by flashing supersu or superuser (CWM flashable zips) through stock rom recovery directly,no need for CWM.ZIP at all.
-Note users can also get root + busybox by flashing CWM.ZIP old safe non touch v 4.x through stock recovery first,then to flash supersu/superuser+busybox zip through the temp CWM 4.
Am i right guys? plz do confirm...
Also what about wiping now through temp CWM4 with ICS rooted stock kernel? is it safe now??
↖(^▽^)↗ Sent from Rego Galaxy Note ↖(^▽^)↗
Click to expand...
Click to collapse
All is ok, except wipe
I cannot certify it is safe. Entropy512 which is involved in CM dev said it is safe for CWM4. I never tested, cannot confirm
Also, CWM6 is still unknown state on stock kernel, until some dev can confirm it
eng.rego said:
So to summarize this in clear words for note users it should be:
-Note users can easily get root only by flashing supersu or superuser (CWM flashable zips) through stock rom recovery directly,no need for CWM.ZIP at all.
Click to expand...
Click to collapse
Correct.
eng.rego said:
-Note users can also get root + busybox by flashing CWM.ZIP old safe non touch v 4.x through stock recovery first,then to flash supersu/superuser+busybox zip through the temp CWM 4.
Click to expand...
Click to collapse
Haven't tried it that way because it involves an extra unnecessary flash. Anyway best to steer clear of any CWM.zip. I bricked my note wiping on touch version. Why use it if u don't have too?
but ultimately we have to used odin to flash a safe kernel after this proceedure.
can we use this to 'cure' the 'partial root' phenomenon many face after flashing even recent ics custom roms ?
i admit installing busybox from market successfully can be a real pain .....
we need busybox for many things like supercharger script etc etc
some apps wont work if you dont have the upgraded version of bb
Some like to stay on stock Ics kernel because of stability. (only unsafe if wipes are performed on them) If u want custom kernel then obviously mobile odin pro/lite is the way to go. At least this way u dont raise flash counter and then have to use potentially dangerous triangle away app. As far as "partial root" goes - not sure. It will install SuperSU. Just open it to update binary and uninstall any other superuser apps that are already on phone
Sent from my GT-N7000 using xda app-developers app
Let me get this straight:
The "official" root thread for Note [02Feb12]How to Root/Unroot Samsung Galaxy Note + CWM says this:
Using CWM.zip (temporary/Touch recovery)method to root is said to be unsafe by entropy, and till safe release don't use it
Read This http://forum.xda-developers.com/show....php?t=1810954
Click to expand...
Click to collapse
Now there is new release which is CWM 6.
Is the old method safe with the new release?
No need for ANY CWM.zip (safe or not). Just flash file in OP on stock kernel recovery from external sd card. Job done .
Sent from my GT-N7000 using xda app-developers app
Yes... Can confirm this has worked for me... Followed instructions in OP, and copied the Uninstaller to my SD Card in the even that I need to return the phone... Flashed in Stock Recovery, rooted and done..
Thanks a million for this...:good:
New Procedure updating to My this thread in 1 hr ( I am working on it)
http://forum.xda-developers.com/showthread.php?t=1329360
new method based on What Entropy have guided us few post back
No need to use CWM at all
No need to flash SUperSU busybox installer (as Entropy said this can cause problem)
For detail guide about how to root N7100 -
Read
http://forum.xda-developers.com/showthread.php?t=1896696
Post # 2 and 3 of above said thread
---------------------------------------------------------------
This guide basically written when there was only available method to root device was flashing chenglu's recovery, which was causing to raise flash counter 1 even after triangle away. That was due to samsung's bootloader for Note 2 which have autosum check for recovery. So if you are using any custom recovery your flash counter will raise to 1. Also read this if you want to use CWM recovery and want to reset counter at every boot.
Later Chainfire have introduce 'Cf Auto root' and in that case no need to use this tutorial as CF auto root package includes stock recovery.
Still this guide is useful who have flashed CWM and want to move to stock recovery with reseting counter '0'
Here is guide How to reset counter to '0' and keep device rooted
All credits to Chainfire and chenglu, without their amazing tool we can't have this......
-If you have rooted with CWM recovery
- Your device will have CWM recoovery with root access.
- Download this stock recovery OR This latest stock recovery from LL7 which believe to be patched by samsung.
- Flash with PC Odin for PDA tab.
- Reset counter with Triangle away
- Now your counter will be '0' and you will have now stock recovery but root access will be intact
- You will have binnary count '0' but system status still will be 'custom'
- Reboot to recovery, wipe cache and data
(this step is just for keeping status' official '
You can skip if you have too much data, as this status can be achieved even in semibricked condition by wiping from recovery Or by flashing stock rom from download mode. And in hard bricked this status can't be read ) important thing is to just keep count' 0'.
- You will have binary count '0' and current binary 'official' as well system status 'official'
- with latest bootloader you can't achieve system status 'official' with wipe cache and data too, in that case you may need to reflash stock ROM, reboot normally, play for 10 min and it should be 'official'
New :
How to change system status 'Modified' to 'Normal' in device setting without factory reset.
you can enjoy full root access without worrying of warranty
dr.ketan said:
Here is guide How to reset counter to '0' and keep device rooted
All credits to Chainfire and chenglu, without their amazing tool we can't have this......
As we have many reported case after reseting counter with Triangle Away, recovery gets broken
So I have manage to keep recovery and Root intact
Right Now updating short instruction
Full video guide and detail instruction for newbie tomorrow.
- Flash chenglu's custom recovery (first line on my signature post #2)
- Your device will have CWM recoovery with root access
- Reset counter with Triangle away
- Here your counter will be zero but,this will break recovery and you won't be able to reboot to recovery.(Don't attempt to check it otherwise count will be raise)
- Download this recovery
- Flash with PC Odin for PDA tab. (Don't use Mobile Odin, otherwise binary count raise)
- Now your counter still will be '0' and you will have now stock recovery but root access will be intact
- You will have binnary count '0' but system status still will be 'custom'
- Reboot to recovery, wipe cache and data
- You will have binary count '0' and current binary 'official' as well system status 'official'
- still you will have root but with stock recovery
you can enjoy full root access without worrying of warranty
Click to expand...
Click to collapse
Hi Dr !
Your recovery is for this problem ?
Uploaded with ImageShack.us
No No
This is bootloader bug
while entering recovery just release power button once splash screen appear, above said error will go, and you can entre to recovery.
Plz remove quating of full post.
dr.ketan said:
No No
This is bootloader bug
while entering recovery just release power button once splash screen appear, above said error will go, and you can entre to recovery.
Plz remove quating of full post.
I have said is different thing, once you reset counter, you won't able to reboot to recovery at all.
Click to expand...
Click to collapse
Mobile Odin Pro flashcounter raise is fixed in version 3.40 afaik
gee2012 said:
Mobile Odin Pro flashcounter raise is fixed in version 3.40 afaik
Click to expand...
Click to collapse
Mobile odin 3.40 itself first version which have add Note 2 support.
And i have tried (as well many other user reported) that to flash stock recovery, but it does raise counter.
Pls help
Hi guys where is the flash counter these posts r making me paranoid. Right now I flashed like 3 or 4 things but where is the counter???
the duderino said:
Hi guys where is the flash counter these posts r making me paranoid. Right now I flashed like 3 or 4 things but where is the counter???
Click to expand...
Click to collapse
Vol down +home+power and enter ind download mode.on the upper left screen you see three or four lines.One of them saying something like current binary status
Sent from the Beast
Can't find a reason to wipe.
Why is that necessary?
the duderino said:
Hi guys where is the flash counter these posts r making me paranoid. Right now I flashed like 3 or 4 things but where is the counter???
Click to expand...
Click to collapse
In download mode
nikos523 said:
Can't find s reason to wipe.
Why is that necessary?
In download mode
Click to expand...
Click to collapse
You mean the step 9?
If so this will change the system status from custom to official
Sent from the Beast
afilopou said:
You mean the step 10?
If so this will change the system status from custom to normal
Sent from the Beast
Click to expand...
Click to collapse
Yes.
It wasn't necessary for the s3 before.
Maybe is necessary but doesn't make any sense (for me at least)
nikos523 said:
Yes.
It wasn't necessary for the s3 before.
Maybe is needed but doesn't make any sense (for me at least)
Click to expand...
Click to collapse
Niko this changed in note 2.Did it few times before dr. Ketan's great guide and system status changed from custom to official.
I just know few basics in android but my feeling is that samsung changed their security flags(if this is the correct phrase) for rooting making our "life" harder but more interesting
Sent from the Beast
Wiping data makes system status 'official'
Hope thus can be find helpful to understand that point
Sent from my GT-N7000 using xda premium
Ok guys, ty.
I dont llike that lol
I'll try to find a way without wipe
That wud be great if we can preserve data too.
Hope we may get solution soon.
Sent from my GT-N7000 using xda premium
dr.ketan said:
Wiping data makes system status 'official'
Hope thus can be find helpful to understand that point
Sent from my GT-N7000 using xda premium
Click to expand...
Click to collapse
Doc i see few posts for the bootloader bug (you know the screeny thing).Because you are speaking to various devs,the xlaie (french) did not have this bug(for sure) and remember the first time have it is after flashing the prerooted stock lj1, how easy is to take bootloader from that version and check
1.bootloader without bug+stock unrooted
2. Bootloader without bug+stock rooted
??
Sent from the Beast
I think pre rooted rom just updated with new boot loader
Edit :
Here is post
http://forum.xda-developers.com/showthread.php?p=32632717
I have still didn't get this bug, may be I have did it correctly. Anyway I will check again if it is not in Indian ROM (which i have right now) Then I will port it.
Sent from my GT-N7000 using xda premium
dr.ketan said:
I think pre rooted rom just updated with new boot loader
Sent from my GT-N7000 using xda premium
Click to expand...
Click to collapse
And solve nothing regarding to bootloader bug, this is what i take from bodivas post
http://forum.xda-developers.com/showpost.php?p=32621227&postcount=210
Are we sure that this is bootloader bug?Sorry for chasing up
Updated previous post
Sent from my GT-N7000 using xda premium
I have just checked on my device
Indian rom too don't have this issue. But yes keep pressing all three button just gives bootloop, but not that buggy screen, for recovery you have to release power button. But i think that should be basic procedure as default.
Before porting let's caculate cases who are having flash anything else or just stock rom + cwm
Sent from my GT-N7000 using xda premium
dr.ketan said:
I have just checked on my device
Indian rom too don't have this issue. But yes keep pressing all three button just gives bootloop, but not that buggy screen, for recovery you have to release power button. But i think that should be basic procedure as default.
Before porting let's caculate cases who are having flash anything else or just stock rom + cwm
Sent from my GT-N7000 using xda premium
Click to expand...
Click to collapse
My case
Flashed stock prerooted rom lj1 (with old bootloader) (as i9000+bodivas post) and have stock recovery
Sent from the Beast
Hi
I need a step by step tutorial for rooting my phone to install a custom rom.
I have never rooted before and dont know the basics.
I tried rooting by flashing cf auto root but it gave me bootloop didnt know why
Fe7a said:
Hi
I need a step by step tutorial for rooting my phone to install a custom rom.
I have never rooted before and dont know the basics.
I tried rooting by flashing cf auto root but it gave me bootloop didnt know why
Click to expand...
Click to collapse
Alomost every custom rom is prerooted so all you need to do is download twrp for your device and flash with odin that's it. Once you have twrp installed just download and flash the rom you want
Here is a link to twrp for the N910C
https://dl.twrp.me/treltexx/
sawdoctor said:
Alomost every custom rom is prerooted so all you need to do is download twrp for your device and flash with odin that's it. Once you have twrp installed just download and flash the rom you want
Here is a link to twrp for the N910C
https://dl.twrp.me/treltexx/
Click to expand...
Click to collapse
The phone is completely stock and i never edited it so will flashing twrp give me bootloop as what happened when i tried cf? And can u give me alink for a good prerooted note 5 port with theme engine please?
Fe7a said:
The phone is completely stock and i never edited it so will flashing twrp give me bootloop as what happened when i tried cf? And can u give me alink for a good prerooted note 5 port with theme engine please?
Click to expand...
Click to collapse
What base are you on ? As long as you are on 5.1.1 then I'd recommend DN5, both erobot and sixperience have the theme engine as well but don't seem to be supported anymore.
http://forum.xda-developers.com/note-4/development/5-0-1-dn-rom-e-team-t3031712
I'm not sure CF auto root actually works anymore because of selinux , been that long since I tried it.
I've never known anyone get bootloop flashing the correct twrp. Once you have twrp installed dont do anything except flash dn5 (if thats the one you choose), don't select root in twrp you should be ok just flashing the rom
sawdoctor said:
What base are you on ? As long as you are on 5.1.1 then I'd recommend DN5, both erobot and sixperience have the theme engine as well but don't seem to be supported anymore.
http://forum.xda-developers.com/note-4/development/5-0-1-dn-rom-e-team-t3031712
I'm not sure CF auto root actually works anymore because of selinux , been that long since I tried it.
I've never known anyone get bootloop flashing the correct twrp. Once you have twrp installed dont do anything except flash dn5 (if thats the one you choose), don't select root in twrp you should be ok just flashing the rom
Click to expand...
Click to collapse
every thing ok like this?
after that I should flash the the dn5 rom via odin ?
* in case I want to be back to stock will installing stock rom via smart switch would do it and I will be eligible to Samsung updates again?
sorry for keeping asking but iam totally noob and this is the first time for me to do this
Fe7a said:
every thing ok like this?
after that I should flash the the dn5 rom via odin ?
* in case I want to be back to stock will installing stock rom via smart switch would do it and I will be eligible to Samsung updates again?
sorry for keeping asking but iam totally noob and this is the first time for me to do this
Click to expand...
Click to collapse
Download dn5 zip to your sdcard reboot to recovery and flash the zip file through twrp that's it. If you want to go back to stock you just download the latest firmware for your region from sammobile and flash that through odin. That simple, but I think you will probably stay on custom especially if you want theme store
Edit
Yes every thing is ok in odin, just always check that repartition is never ticked by accident. Repartition should always be left unticked
sawdoctor said:
Download dn5 zip to your sdcard reboot to recovery and flash the zip file through twrp that's it. If you want to go back to stock you just download the latest firmware for your region from sammobile and flash that through odin. That simple, but I think you will probably stay on custom especially if you want theme store
Edit
Yes every thing is ok in odin, just always check that repartition is never ticked by accident. Repartition should always be left unticked
Click to expand...
Click to collapse
is there any way to backup my apps so that I don't lose them after the process and also to backup the whole firmware in case I get a bootloop?
You shouldn't lose them tbh but you can do one of 2 things. 1 make a full back-up in recovery before you flash dn5 (think you can backup un rooted never actually tried)
2 flash latest su zip in recovery to get root then use titanium backup or similar to back them up. There may actually be an app in the playstore that doesn't need root to backup apps just can't remember what it's called
Sent from my SM-N920C using Tapatalk
sawdoctor said:
You shouldn't lose them tbh but you can do one of 2 things. 1 make a full back-up in recovery before you flash dn5 (think you can backup un rooted never actually tried)
2 flash latest su zip in recovery to get root then use titanium backup or similar to back them up. There may actually be an app in the playstore that doesn't need root to backup apps just can't remember what it's called
Sent from my SM-N920C using Tapatalk
Click to expand...
Click to collapse
ok thanks very much for the help . I will let you know if any problem encounters me :good:
sawdoctor said:
You shouldn't lose them tbh but you can do one of 2 things. 1 make a full back-up in recovery before you flash dn5 (think you can backup un rooted never actually tried)
2 flash latest su zip in recovery to get root then use titanium backup or similar to back them up. There may actually be an app in the playstore that doesn't need root to backup apps just can't remember what it's called
Sent from my SM-N920C using Tapatalk
Click to expand...
Click to collapse
hey man i flashed twrp my device status change to custom but when i enter recovery it gives me android system recovery
Fe7a said:
hey man i flashed twrp my device status change to custom but when i enter recovery it gives me android system recovery
Click to expand...
Click to collapse
Untick reboot in odin flash twrp again and reboot straight into recovery manually with 3 finger combo before you boot up the phone. If that doesn't work flash twrp 2.8.6 first, there was a bug in 2..8.7 guess it's still there in latest version. Once you have 2.8.6 you can flash any after that
Sent from my SM-N920C using Tapatalk
sawdoctor said:
Untick reboot in odin flash twrp again and reboot straight into recovery manually with 3 finger combo before you boot up the phone. If that doesn't work flash twrp 2.8.6 first, there was a bug in 2..8.7 guess it's still there in latest version. Once you have 2.8.6 you can flash any after that
Sent from my SM-N920C using Tapatalk
Click to expand...
Click to collapse
i will try and download and flash twrp 2.8.6
sawdoctor said:
Untick reboot in odin flash twrp again and reboot straight into recovery manually with 3 finger combo before you boot up the phone. If that doesn't work flash twrp 2.8.6 first, there was a bug in 2..8.7 guess it's still there in latest version. Once you have 2.8.6 you can flash any after that
Sent from my SM-N920C using Tapatalk
Click to expand...
Click to collapse
i did what u said but now iam stuck at the downloading screen
Fe7a said:
i did what u said but now iam stuck at the downloading screen
Click to expand...
Click to collapse
You flashed 2.8.6 or rebooted straight into recovery?
Sent from my SM-N920C using Tapatalk
sawdoctor said:
You flashed 2.8.6 or rebooted straight into recovery?
Sent from my SM-N920C using Tapatalk
Click to expand...
Click to collapse
i flashed twrp 2.8.6 and unchecked auto reboot but after flashing is done the phone didnt exit the downloading mode and there is a small blue bar at the bottom
sawdoctor said:
You flashed 2.8.6 or rebooted straight into recovery?
Sent from my SM-N920C using Tapatalk
Click to expand...
Click to collapse
i removed the batery and opened the recovery and finally it worked
there are many options what should i choose to install the room?
Fe7a said:
i removed the batery and opened the recovery and finally it worked
there are many options what should i choose to install the room?
Click to expand...
Click to collapse
Just download dn5 then select install zip and that's it. If it asks you to root after the zip finishes don't. Also first boot (only the first one) after flashing will take 10 mins so don't panic
Sent from my SM-N920C using Tapatalk
sawdoctor said:
Just download dn5 then select install zip and that's it. If it asks you to root after the zip finishes don't. Also first boot (only the first one) after flashing will take 10 mins so don't panic
Sent from my SM-N920C using Tapatalk
Click to expand...
Click to collapse
its saying optimising app now
is there anyway to exit that stupid downloading mode when i disable auto reboot in odin rather than removing the battery?
Fe7a said:
its saying optimising app now
is there anyway to exit that stupid downloading mode when i disable auto reboot in odin rather than removing the battery?
Click to expand...
Click to collapse
You won't need to worry about it now. It's just a twrp bug first time you flash it. It won't happen again
Sent from my SM-N920C using Tapatalk
sawdoctor said:
You won't need to worry about it now. It's just a twrp bug first time you flash it. It won't happen again
Sent from my SM-N920C using Tapatalk
Click to expand...
Click to collapse
after its finished optimising apps its now telling me system ui has stopped