Ever since google rolled out the marshmallow update I have been plagued with battery issues to an extent where it was dropping to half from a full charge within a day even on standby . Having looked at many fixes on this forum which including rooting and replacing the kernel or simply turning core features like wifi off.For some users it may be tedious and it may risk bricking their device . So I decided to go back to stock 5.1.1 until google fixes the battery issues.
Before Proceeding Backup Your Data.
Follow the steps below to roll back to stock 5.1.1 along with stock recovery.
1) Download the Android One Toolkit http://forum.xda-developers.com/cro...oolbox-android-one-toolkit-one-click-t3030165.
2) Download 5.1 OTA update from here : http://forum.xda-developers.com/cro...l/ota-micromax-official-ota-captured-t3058879
3) Download 5.1.1 OTA update from here: http://forum.xda-developers.com/cro...al/ota-canvas-a1-5-1-1-captured-link-t3121543
4) Place both the OTA zips in root of SD CARD.Note the names of both versions.
5) Open Android One Toolkit.Enable USB Debugging . Unlock the Bootloader.
6) Install CWM Recovery from the Toolkit.
7) Reboot to Recovery.
8) Make a full backup of your existing ROM in case something goes wrong.
9) Erase Data , Cache & Dalvik Cache.
10) Select install zip from ext-sd card select the 5.1 OTA zip.
11) After completion reboot your phone. Update will also replace CWM with stock recovery ( No Worries)
12) Keep Wifi Off & Data connection off to prevent marshmallow being downloaded again during Setup . Setup your device Offline.
13) Reboot to stock recovery using key combo Power + Volume Up.If you get "No command" in stock recovery continue pressing Power+Volume Up until menu appears.
14) Select Update from SD Card . Select 5.1.1 OTA zip.
15) Reboot phone and you will now be on 5.1.1. Along with Stock Recovery.
16)Once Data or Wifi is enabled you may get update prompts of Marshmallow in notification. Disable update notification by long pressing on notification and goto settings from there you can disable it.
17) You may Relock Bootloader if You Wish from toolkit
Disclaimer:
I Am Not Responsible For Any Damage Caused To your Phone.
Credits to:
@anil293 for his toolkit
@varun.chitre15 For His Recoveries
@ghpranav & @GokulNC for OTA links.
Draining continues
Can't go to CWM even I unlocked bootloader I flash ed CWM but still on NO COMMAND
ranj9660 said:
Can't go to CWM even I unlocked bootloader I flash ed CWM but still on NO COMMAND
Click to expand...
Click to collapse
FIrst check in android toolkit in list devices if your device is mentioned.
After flashing CWM boot straight to recovery. Booting to OS may cause the recovery to be overwritten by STOCK recovery.
Yeah my device
My device mentioned too . I clicked list devices and I got device id then only I unlocked bootloader and installed custom recovery also but I can't enter to customer recovery ?
ranj9660 said:
My device mentioned too . I clicked list devices and I got device id then only I unlocked bootloader and installed custom recovery also but I can't enter to customer recovery
Click to expand...
Click to collapse
After installing CWM from toolkit don't restart to OS. Press Power+Volume Up until recovery select option appears.
But now
(First i have to thank you to giving me the instruction now its worked) Doesn't show zip files. What to do? I wiped dalvik cache, data and cache partition but doesn't show zip file ? got another problem
Can I use Twrp?
What's wrong using TWRP instead of CWM? I do not have windows. I have Linux(Ubuntu). From linux I can flash anything. But the problem is I don't have the latest recovery image of CWM for Android one devices. (The CWM project has been abandoned anyway).
My only concern is to get back the stock recovery after flashing 5.1.
The process you told to revert back to Lollipop after Marshmallow update, have u done that, are u succeeded.
Please tell me, because after Marshmallow update i got a severe battery drain and over heat in My Spice Dream Uno MI-498.
When my phone is in ideal it is okay but when i started using it then the issue started.
After revert back to Lollipop according to your process is there any IMEI problem.
Is it possible after flashing the ROM in Custom Recovery can it revert back to Stock Recovery.
androidone14 said:
The process you told to revert back to Lollipop after Marshmallow update, have u done that, are u succeeded.
Please tell me, because after Marshmallow update i got a severe battery drain and over heat in My Spice Dream Uno MI-498.
When my phone is in ideal it is okay but when i started using it then the issue started.
After revert back to Lollipop according to your process is there any IMEI problem.
Is it possible after flashing the ROM in Custom Recovery can it revert back to Stock Recovery.
Click to expand...
Click to collapse
Just flash away the STOCK ROM and you'll get everything STOCK
---------- Post added 5th November 2015 at 00:06 ---------- Previous post was 4th November 2015 at 23:57 ----------
ranj9660 said:
(First i have to thank you to giving me the instruction now its worked) Doesn't show zip files. What to do? I wiped dalvik cache, data and cache partition but doesn't show zip file �� got another problem
Click to expand...
Click to collapse
Please give more details or send a pic of what is going wrong for you. You have to put the zip file in your external card and flash from install from external SD card if that's what you are asking for.
wickedspice said:
Ever since google rolled out the marshmallow update I have been plagued with battery issues to an extent where it was dropping to half from a full charge within a day even on standby . Having looked at many fixes on this forum which including rooting and replacing the kernel or simply turning core features like wifi off.For some users it may be tedious and it may risk bricking their device . So I decided to go back to stock 5.1.1 until google fixes the battery issues.
Before Proceeding Backup Your Data.
Follow the steps below to roll back to stock 5.1.1 along with stock recovery.
1) Download the Android One Toolkit http://forum.xda-developers.com/cro...oolbox-android-one-toolkit-one-click-t3030165.
2) Download 5.1 OTA update from here : http://forum.xda-developers.com/cro...l/ota-micromax-official-ota-captured-t3058879
3) Download 5.1.1 OTA update from here: http://forum.xda-developers.com/cro...al/ota-canvas-a1-5-1-1-captured-link-t3121543
4) Place both the OTA zips in root of SD CARD.Note the names of both versions.
5) Open Android One Toolkit.Enable USB Debugging . Unlock the Bootloader.
6) Install CWM Recovery from the Toolkit.
7) Reboot to Recovery.
8) Make a full backup of your existing ROM in case something goes wrong.
9) Erase Data , Cache & Dalvik Cache.
10) Select install zip from ext-sd card select the 5.1 OTA zip.
11) After completion reboot your phone. Update will also replace CWM with stock recovery ( No Worries)
12) Keep Wifi Off & Data connection off to prevent marshmallow being downloaded again during Setup . Setup your device Offline.
13) Reboot to stock recovery using key combo Power + Volume Up.If you get "No command" in stock recovery continue pressing Power+Volume Up until menu appears.
14) Select Update from SD Card . Select 5.1.1 OTA zip.
15) Reboot phone and you will now be on 5.1.1. Along with Stock Recovery.
16)Once Data or Wifi is enabled you may get update prompts of Marshmallow in notification. Disable update notification by long pressing on notification and goto settings from there you can disable it.
17) You may Relock Bootloader if You Wish from toolkit
Disclaimer:
I Am Not Responsible For Any Damage Caused To your Phone.
Credits to:
@anil293 for his toolkit
@varun.chitre15 For His Recoveries
@ghpranav & @GokulNC for OTA links.
Click to expand...
Click to collapse
Thanks!!!
But is there any way to roll back without rooting the phone.
i don't want to my phone now.
anupamdubey said:
Thanks!!!
But is there any way to roll back without rooting the phone.
i don't want to my phone now.
Click to expand...
Click to collapse
Downgrade is possible only through unlocking bootloader and then flashing custom recovery which shall help you flash the LP firmware.
Rooting has nothing to do with this.
wickedspice said:
After installing CWM from toolkit don't restart to OS. Press Power+Volume Up until recovery select option appears.
Click to expand...
Click to collapse
it gets rebooted automatically after flashing cwm recovery but still no command.
stan1996 said:
it gets rebooted automatically after flashing cwm recovery but still no command.
Click to expand...
Click to collapse
Yes , thats the tricky part as os tries to restore stock recovery on boot. Here's what you need to do. On your computer when the toolkit prompt says " completed /finished" prevent rebooting by quickly pressing power+volume up. Once you get the selection prompt select recovery by volume up and confirm selection by volume down.
You have to do this only once , After you successfully boot to cwm it will prevent os from re writing recovery
wickedspice said:
Yes , thats the tricky part as os tries to restore stock recovery on boot. Here's what you need to do. On your computer when the toolkit prompt says " completed /finished" prevent rebooting by quickly pressing power+volume up. Once you get the selection prompt select recovery by volume up and confirm selection by volume down.
You have to do this only once , After you successfully boot to cwm it will prevent os from re writing recovery
Click to expand...
Click to collapse
thank you so much:angel::angel::angel:
I am getting stuck on unlock bootloader, it freezes and does nothing ? any ideas guys ? I really need to get away from marshmallow, hot phone, no 4g etc etc
Related
Hey guys, I'm having a weird little problem here.
So I followed this guide here, unlocked my bootloader, everything fine.
So far so good. I flashed the mentioned TWRP Recovery through fastboot, no error messages, still looks like everything's fine.
But whenever I try to get from the fastboot screen on my phone into recovery mode, the screen stays black.
I tried restoring to stock, hoping that would add the original recovery back in. Nope, still black screen.
After that, I successfully flashed the recovery from this thread. Again, no error messages and everything looked fine. But still no luck. My recovery screen stays black for whatever reason.
I'm on Windows 8.1 64Bit and using the current Android SDK. The SDK setup had a little problem with finding Java JDK (64Bit) before I could set it up properly. But I solved that one by adding a system variable. Again, nothing out of the ordinary here, at least as far as I understand.
So what am I doing wrong?
I'd really like to get a custom rom with root on this baby. Don't wanna be stuck on stock. :/
Does anybody have an idea, how I could manage to access any kind of recovery in this case?
If the screen stay black then something went wrong
Fastboot gave you the OKAY on flashing ? Did you reboot your phone after you flashed the recovery ?
You don't have to, if you reboot you will have the stock one again = black screen.
Try like i did (assuming you correctly unlocked the bootloader, and installed MotorolaDeviceManager).
1) Get the right recovery for XT1072 from the author's post HERE.
2) Download the latest CM rom from HERE and latest CM gapps package from HERE.
3)Move the CM rom and the gapps zips on the SD or EMMC then reboot to bootloader.
4)Flash the recovery whit "fastboot flash recovery twrp-thea.img" and check if you got the OKEY from fastboot (DO NOT REBOOT YET).
5)Now pick up your phone and use VOL-DOWN to highlight RECOVERY then VOL-UP to start the recovery.
6)You should have the TWRP menu open now, go WIPE -> ADVANCED WIPE and check Dalvik/Data/Cache/System then swipe to wipe those 4 partitions.
7)Go back to main menu and select install, flash the CM12.1 zip then gapps zip and now you can reboot, first boot take a while so don't panic.
P.S.
I uploaded for you the latest untouched platform-tools folder (rev22) for windows if you wish to try this one, LINK, VirusTotal scan.
dr.nic said:
If the screen stay black then something went wrong
Fastboot gave you the OKAY on flashing ? Did you reboot your phone after you flashed the recovery ?
You don't have to, if you reboot you will have the stock one again = black screen.
Try like i did (assuming you correctly unlocked the bootloader, and installed MotorolaDeviceManager).
1) Get the right recovery for XT1072 from the author's post HERE.
2) Download the latest CM rom from HERE and latest CM gapps package from HERE.
3)Move the CM rom and the gapps zips on the SD or EMMC then reboot to bootloader.
4)Flash the recovery whit "fastboot flash recovery twrp-thea.img" and check if you got the OKEY from fastboot (DO NOT REBOOT YET).
5)Now pick up your phone and use VOL-DOWN to highlight RECOVERY then VOL-UP to start the recovery.
6)You should have the TWRP menu open now, go WIPE -> ADVANCED WIPE and check Dalvik/Data/Cache/System then swipe to wipe those 4 partitions.
7)Go back to main menu and select install, flash the CM12.1 zip then gapps zip and now you can reboot, first boot take a while so don't panic.
P.S.
I uploaded for you the latest untouched platform-tools folder (rev22) for windows if you wish to try this one, LINK, VirusTotal scan.
Click to expand...
Click to collapse
YOU ARE AMAZING!!!!!!!
SPENT LIKE 3 HOURS FAILING. AND FAILING. AND FAILING! NEARLY BLOODY BRICKED.
I'll stop capsing.
But this worked!!!!!!!!!!! (I think, currently rebooting after flashing)
THANK YOU!
I tried it again and this time it worked!
Beautiful! :good:
Hi all,
I'm trying to install Cyanogenmod following techbeasts.com tutorial but I'm stuck at the first step : installingTWRP (or CWM).
I followed precisely all the instructions (I allow debugging mode, I installed samsung drivers, I start the phone in download mode, I connect it with OEM cable, I start Odin, it sees the phone, I select the tar.md5 file.), Odin confirms it went well (green box writing "PASS"), but when I try to boot the recovery mode by holding Volume up + Home + Power it seems to boot another recovery software that doesn't offer a backup or a flashing options: "Android system recovery <3e>"
Can't get it to run TWRP or CWM... Can't install the supersu package.
What I'm I doing wrong? Can someone help?
Try to untick Auto Reboot option from odin. I had similiar issues and reason was if you have updated your phone with OTA-updates then it installs some kind of backup script. When your phone boots again after you had installed twrp it installs stock recovery during boot. So untick autoreboot, flash twrp and force boot straight to recovery without letting phone boot to OS. You can also try to pull battery out, put it back and then boot into recovery mode.
Sorry my english and try to understand.
adbhitman said:
Try to untick Auto Reboot option from odin. I had similiar issues and reason was if you have updated your phone with OTA-updates then it installs some kind of backup script. When your phone boots again after you had installed twrp it installs stock recovery during boot. So untick autoreboot, flash twrp and force boot straight to recovery without letting phone boot to OS. You can also try to pull battery out, put it back and then boot into recovery mode.
Sorry my english and try to understand.
Click to expand...
Click to collapse
Great it worked, thanks a lot !
But now I'm stuck on the next step : flashing CM11
I rooted my phone, booted TWRP, chose "install>cm11" (the zip downloaded from nova fusion) but it says "failed" after a few sec...
I would post my TWRP log but the forum prevents me doing so...
Well I get few things that you could check first.
1. Do factory reset for example from twrp. Factory reset is needed/recommended before installing custom rom from offical OS.
2. Sometimes just installing fails almost immediately if you have ticked check zip signature.
After you have installed new rom clear cache and davilk cache just in case. I'll do that every time if I install or update custom roms. Also don't forget to install right gapps package after you have installed rom.
Sorry my english and try to understand.
ok just realized i downloaded the wrong cm image (the odin one, not the recovery)
everything running smooth now
Okay happy to hear that everything is fine now. Happy playing with custom roms
I have a rooted Verizon Moto X 2013 Developer Edition (XT1060) with Android 4.4.4, TWRP and SuperSU installed. I rooted the phone so I could install a wi-fi tethering app that I frequently use. Last night I noticed that the Lollipop OTA was available, and being a dumas, I proceeded to download it without coming to xda-developers first to educate myself on the correct process and potential issues with the upgrade (one such issue being whether I will be able to run my tethering app after the upgrade). Consequently, after I downloaded the upgrade, my phone restarted and booted to the TWRP screen, and I don't know where to go from there to complete the upgrade, if it's even possible to do so.
This is my only phone, so it's more important that I get my phone up and running in the next 1-2 hours than it is to complete the upgrade. With that in mind, what should I do next? Is there a way to quickly abort the upgrade process, perhaps by simply deleting the update file "Blur_Version.212.166.3.ghost_verizion.Verizon.en.US.zip" in my cache folder using TWRP's File Manager and rebooting my phone? Or is it possible to complete the upgrade process in the next 1-2 hours? If so, how should I proceed?
By the way, TWRP is displaying the following error messages:
Error executing updater binary in zip '/cache/Blur_Version.212.166.3.ghost_verizion.Verizon.en.US.zip'
Error installing zip file '/cache/Blur_Version.212.166.3.ghost_verizion.Verizon.en.US.zip'
Thanks in advance for helping me recover from my dumas behavior.
The OTA update file does not work with TWRP, IMHO. It only works with the stock recovery.
If you just boot back out of TWRP (boot back to regular system) your phone should still be functional.
kschang said:
The OTA update file does not work with TWRP, IMHO. It only works with the stock recovery.
If you just boot back out of TWRP (boot back to regular system) your phone should still be functional.
Click to expand...
Click to collapse
Thanks, kschang. Your suggestion worked, but not right away, so there appears to be a twist involved that other users should be aware of if they get stuck in the same situation I was in.
As I indicated in my original post, after downloading the update, my phone would power off and boot to TWRP. From TWRP's main menu I would click on "Reboot," then "System." I tried this a number of times, and each time my phone would reboot to what it appeared to be before I downloaded the upgrade, but only for about 10 seconds, then it would power off and reboot to TWRP again--except for just now, when the phone displayed a message that the upgrade had failed and no changes were made to my phone! Apparently the upgrade process has to fail a certain number of times before it finally aborts. I don't know what the number is, but I must have tried rebooting my phone at least 10-15 times before the upgrade process aborted.
So thanks again for your suggestion. It encouraged me to keep trying to reboot until it ultimately worked:good:
I had the same issue with my phone rebooting so I forced the system update app to freeze via Titanium Backup and that seemed to work.
My phone now is kinda messed up though. To get it to boot I have to hold the volume key while powering it up and choose "boot normally". Any time I just restart my phone or power it up while it's off I get a black screen because like the OP I tried to update to Lollipop without reading XDA first. Doh!!
Any first impressions on the update for this phone by the way? Battery life improve or get worse? Can I still use Xposed on Lollipop? Rooting still possible? Wifi tethering for us on unlimited data?
Same situation. Want to upgrade but not sure how now... waiting for an angel to answer my prayers!
daddylonglegs said:
I had the same issue with my phone rebooting so I forced the system update app to freeze via Titanium Backup and that seemed to work.
My phone now is kinda messed up though. To get it to boot I have to hold the volume key while powering it up and choose "boot normally". Any time I just restart my phone or power it up while it's off I get a black screen because like the OP I tried to update to Lollipop without reading XDA first. Doh!!
Any first impressions on the update for this phone by the way? Battery life improve or get worse? Can I still use Xposed on Lollipop? Rooting still possible? Wifi tethering for us on unlimited data?
Click to expand...
Click to collapse
Root is still possible. The only issue i had was after flashing Twrp, if i rebooted the phone and then tried to boot the recovery Twrp was gone. So i reflashed Twrp while i was still in fastboot i selected "recovery" it booted into Twrp and i flashed a SuperSU zip.
After that i could reboot into Teamwin without issue. I haven't tried Xposed yet. Battery life is great on my end.
---------- Post added at 01:18 AM ---------- Previous post was at 01:16 AM ----------
rice923 said:
Same situation. Want to upgrade but not sure how now... waiting for an angel to answer my prayers!
Click to expand...
Click to collapse
The way i did it was to fastboot flash the dev edition 4.4.4 files to unroot. Then i used Verizon upgrade assistant to take the small update that came out awhile ago. After that i factory reset the phone, checked for updates and the first of two updates installed then it updated to 5.1
I reinstalled Twrp and regained root access.
James L said:
The way i did it was to fastboot flash the dev edition 4.4.4 files to unroot. Then i used Verizon upgrade assistant to take the small update that came out awhile ago. After that i factory reset the phone, checked for updates and the first of two updates installed then it updated to 5.1
I reinstalled Twrp and regained root access.
Click to expand...
Click to collapse
Would flashing dev 4.4.4 unroot as well as remove twrp? Twrp seems to be the main obstacle to get past in order to get the update going. If so, I might just do this tomorrow
The immediate way to get out of the failed flash and reboot-cycle is to (quickly) use a file explorer such as ES File Explorer and migrate to your internal cache folder and delete the Verizon flash file. That stops the reboot cycle in its tracks. You'll get the "failed" message before too long, too.
I found I had more like a minute before a reboot occurred after a failed flash. In other words, I'd be stuck on TWRP, clicked to reboot system, it would reboot. Then, I had about a minute to do stuff before it would shutdown/reboot again. During that time, I would just go to ES File Explorer and delete the Verizon update file from the cache folder, and problem solved.
Of course, it will download again shortly thereafter, but won't do anything until you agree to go ahead and install it.
Guess I'm going to have to flash all the 4.4.4 files like stated above to get back to stock (lame!) and then do the OTA updates. I seem to recall someone had figured out how to flash OTA on a previous update without having to go back to stock, though.
rice923 said:
Would flashing dev 4.4.4 unroot as well as remove twrp? Twrp seems to be the main obstacle to get past in order to get the update going. If so, I might just do this tomorrow
Click to expand...
Click to collapse
Yes it would remove Twrp if you flash the stock files.
---------- Post added at 10:34 AM ---------- Previous post was at 10:25 AM ----------
You could take the little update prior to the 5.1 update by reflashing the stock recovery that will stop the bootloop from the smaller update.
I didn't lose root and just reflashed Twrp. Then after a bit the 5.1 update was released so i just took the jump and flashed stock files to unroot, and took the update. Is it possible to update to 5.1 with root and a stock recovery?..... Not sure i was going to try it but didn't
Root is still possible. The only issue i had was after flashing Twrp, if i rebooted the phone and then tried to boot the recovery Twrp was gone. So i reflashed Twrp while i was still in fastboot i selected "recovery" it booted into Twrp and i flashed a SuperSU zip.
Click to expand...
Click to collapse
Verizon MotoX Developer Edition (2013) - I am having the same issue installing TWRP after reverting to stock and receiving/installing the 5.1 OTA. If I try to flash TWRP via fastboot, it doesn't seem to take. The flash shows as a success, but when I reboot to recovery I'm still in stock. I've tried flashing TWRP then using the volume rocker to immediately boot into TWRP, with no success. I've also tried holding down the bootloader key combo immediately after "fastboot reboot", with no success. When I boot up, though, my apps will optimize every time. Am I missing something?
EDIT: Resolved the problem, turns out I was not using the volume up button to enter recovery immediately after flashing...smh
My lenovo a-7000 boot into cwm recovery mode
Last time when I restarted my phone it's goes direct into recovery mode after then whenever,i reboot my system it's get back into recovery mode.
I tried power off and manually power on by power button and factory reset but it's not fixed.
Help me to get back my a-7000
I tried key test so it's confirm that my volume buttons are working fine
Am using cwm recovery and AOSP stallion mod custom rom
installed miui 7.0 also
I installed miui 7.0 custom rom also but it's not working either
When I power on my phone it's shows miui 7 logo and the enter into cwm recovery direct
Can I reset my bootloader? Please help me someone ????
I've update on OTA with S149 firmware, but after reboot, my phone's always shows "Lenovo-Recovery" screen. I can't boot into Android OS.
Help, please.
problem solved
Download stock recovery.zip of lenovo a7000 from xda and install it via cwm and my phone remove cwm recovery from system and add stock recovery after that I downloaded original marshmallow stock rom of a7000 put it in SF card ,rename stockrom.zip to update.zip and put a card in phone
Open stock recovery click on install updates and hurray phone automatically detect update.zip and installed
After reboot my phone got a new life it's back with pure stock rom marshmallow
baby1982 said:
I've update on OTA with S149 firmware, but after reboot, my phone's always shows "Lenovo-Recovery" screen. I can't boot into Android OS.
Help, please.
Click to expand...
Click to collapse
Download original marshmallow stock rom of a7000 and put it in Sd card rename it to update.zip and install it via recovery 'install update'
Hope it'll help you
baby1982 said:
I've update on OTA with S149 firmware, but after reboot, my phone's always shows "Lenovo-Recovery" screen. I can't boot into Android OS.
Help, please.
Click to expand...
Click to collapse
http://forum.xda-developers.com/lenovo-a7000/development/stock-firmware-lenovo-a7000-t3205505link of OTA stock rom and other files
Hi guys,
Im using Note 5 N920C at lastest stock Nougat firmware (N920CXXS4CRA2)
i've got a very headache when try to flash twrp (to flash custom rom) but my N920C still get stuck at Samsung logo
Prepare: unlock OEM, Odin 3.12, TWRP 3.2.1.0, SuperSU-v2.82
1. Try flash TWRP by Odin. reboot get stuck. Try to reboot to Recovery, wipe cache -> phone get reboot all the time
2. Back to Stock FW, try to flash TWRP. This time reboot to Recovery, allow system modifications -> flash N920_Nougat_Root_SuperSU_No_kernel_included script -> reboot and stuck
3. Back to Stock FW, try to flash TWRP. This time reboot to Recovery, allow system modifications -> format data -> reboot to recovery -> flash supersu -> reboot and stuck again
4. Back to Stock FW, TWRP allow system modifications > wipe data> reboot recovery > allow system modification> wipe data, system,cache, dalvik/art > flashed 'dm-verity and force encryption disabler' > flashed 'super-su' > flashed Custom ROM -> Stuck again
5. If i flash Lineage OS (or CM rom) via TWRP, it works without any issue
...
As many time i tried to flash something, myphone still get stuck, i dont know why because my previos Note 5 seem to be very easy to root (at Nougat also)
Could you please help me to findout what problem happen here and how can i flash a custom rom properly (i can back to stock whenever it stucks but i want to flash custom roms). Thank you so much
venomnguyen said:
Hi guys,
Im using Note 5 N920C at lastest stock Nougat firmware (N920CXXS4CRA2)
i've got a very headache when try to flash twrp (to flash custom rom) but my N920C still get stuck at Samsung logo
Prepare: unlock OEM, Odin 3.12, TWRP 3.2.1.0, SuperSU-v2.82
1. Try flash TWRP by Odin. reboot get stuck. Try to reboot to Recovery, wipe cache -> phone get reboot all the time
2. Back to Stock FW, try to flash TWRP. This time reboot to Recovery, allow system modifications -> flash N920_Nougat_Root_SuperSU_No_kernel_included script -> reboot and stuck
3. Back to Stock FW, try to flash TWRP. This time reboot to Recovery, allow system modifications -> format data -> reboot to recovery -> flash supersu -> reboot and stuck again
4. Back to Stock FW, TWRP allow system modifications > wipe data> reboot recovery > allow system modification> wipe data, system,cache, dalvik/art > flashed 'dm-verity and force encryption disabler' > flashed 'super-su' > flashed Custom ROM -> Stuck again
5. If i flash Lineage OS (or CM rom) via TWRP, it works without any issue
...
As many time i tried to flash something, myphone still get stuck, i dont know why because my previos Note 5 seem to be very easy to root (at Nougat also)
Could you please help me to findout what problem happen here and how can i flash a custom rom properly (i can back to stock whenever it stucks but i want to flash custom roms). Thank you so much
Click to expand...
Click to collapse
1: Flash the rom after you wipe system, data & cache.
2: Let it boot for the first initial setup & setup your phone with language & country etc.
3: Restart your phone to twrp recovery then flash supersu & dm verity.
Let me know.
PRADEEPHONDA said:
1: Flash the rom after you wipe system, data & cache.
2: Let it boot for the first initial setup & setup your phone with language & country etc.
3: Restart your phone to twrp recovery then flash supersu & dm verity.
Let me know.
Click to expand...
Click to collapse
Did you mean flash stock or custom ROM ? as i mentioned above, when flash custom my phone will stuck at logo (i can boot only with LineageOS, dont know why
I will try these steps:
1. Back to Stock
2. Flash TWRP, immediately go to TWRP recovery
3. Format Data, reboot to TWRP recovery
4. Flash SR5-SuperSU-v2.82-SR5-20171001224502.zip and no-verity-opt-encrypt-6.0.zip
5. Wipe Davik Cache
6. Reboot.
Am i right ?
I will try and post result to you for more help. Btw, thank for your attention.
venomnguyen said:
Did you mean flash stock or custom ROM ? as i mentioned above, when flash custom my phone will stuck at logo (i can boot only with LineageOS, dont know why
I will try these steps:
1. Back to Stock
2. Flash TWRP, immediately go to TWRP recovery
3. Format Data, reboot to TWRP recovery
4. Flash SR5-SuperSU-v2.82-SR5-20171001224502.zip and no-verity-opt-encrypt-6.0.zip
5. Wipe Davik Cache
6. Reboot.
Am i right ?
I will try and post result to you for more help. Btw, thank for your attention.
Click to expand...
Click to collapse
No.... After flashing stock through Odin, let the device boot for initial setup dude. Don't flash twrp...!
After the phone setup is done you can go back to download mode & flash twrp.
There is no need to format data for rooting your device dude.
Just flash supersu & no verity... You will be fine.
Stock rom or custom ROM follow my words.
PRADEEPHONDA said:
No.... After flashing stock through Odin, let the device boot for initial setup dude. Don't flash twrp...!
After the phone setup is done you can go back to download mode & flash twrp.
There is no need to format data for rooting your device dude.
Just flash supersu & no verity... You will be fine.
Stock rom or custom ROM follow my words.
Click to expand...
Click to collapse
It does not work, both my way and or way, it's still stuck
venomnguyen said:
It does not work, both my way and or way, it's still stuck
Click to expand...
Click to collapse
In your first post you have stated that you are not able to flash custom rom but now you are telling me that your phone is stuck even when Flashed with stock rom....!
I'm confused about what's happening here because the methods you have stated will not work in any case scenario as base ROM is required to flash - root to system or any mods so without rom you can't root any phone by flashing supersu first before even flashing rom that's the logical here.
There is no my method or your method but there is a universal step by step method which you clearly need to understand.
But anyways I can't help you anymore as I have no video to assess your process.
As a last resolution I will suggest one more method, if you can boot your phone to stock recovery then you can reset your device by factory reset which will again wipe everything within the phone so proceed with caution(just mentioning) so once you wipe your phone through stock recovery. Let me know. It has to boot in my opinion.
Before you do this try to reflash official & latest firmware which will be the January security updates through Odin with default settings.
After you get Odin pass message, it will automatically reboot so wait for 30 minutes max. If nothing happens press & hold volume down & power key to reboot device & as soon as the screen goes off to reboot, you will have to enter to recovery mode by holding on to volume up, power & home key as you already will know (just mentioned) then wipe to factory reset. Reboot.
Let me know if this works.
If not I'm located in Bangalore so if you are from Bangalore then I might help you. Again no fees or charges (just mentioned)
Or
Try this rom:
https://forum.xda-developers.com/note5/development/rom-t3607729
Or take it Samsung official Store to find out if your device has any issues with power chips or so..!
PRADEEPHONDA said:
In your first post you have stated that you are not able to flash custom rom but now you are telling me that your phone is stuck even when Flashed with stock rom....!
I'm confused about what's happening here because the methods you have stated will not work in any case scenario as base ROM is required to flash - root to system or any mods so without rom you can't root any phone by flashing supersu first before even flashing rom that's the logical here.
There is no my method or your method but there is a universal step by step method which you clearly need to understand.
But anyways I can't help you anymore as I have no video to assess your process.
As a last resolution I will suggest one more method, if you can boot your phone to stock recovery then you can reset your device by factory reset which will again wipe everything within the phone so proceed with caution(just mentioning) so once you wipe your phone through stock recovery. Let me know. It has to boot in my opinion.
Before you do this try to reflash official & latest firmware which will be the January security updates through Odin with default settings.
After you get Odin pass message, it will automatically reboot so wait for 30 minutes max. If nothing happens press & hold volume down & power key to reboot device & as soon as the screen goes off to reboot, you will have to enter to recovery mode by holding on to volume up, power & home key as you already will know (just mentioned) then wipe to factory reset. Reboot.
Let me know if this works.
If not I'm located in Bangalore so if you are from Bangalore then I might help you. Again no fees or charges (just mentioned)
Or
Try this rom:
https://forum.xda-developers.com/note5/development/rom-t3607729
Or take it Samsung official Store to find out if your device has any issues with power chips or so..!
Click to expand...
Click to collapse
Hi Bro,
Maybe you misunderstand what i mean. Ofcouse i can back to stock firmware without any problem. I said it still suck is when i try to flash TWRP, even root or Custom ROMs.
Thank you.
venomnguyen said:
Hi Bro,
Maybe you misunderstand what i mean. Ofcouse i can back to stock firmware without any problem. I said it still suck is when i try to flash TWRP, even root or Custom ROMs.
Thank you.
Click to expand...
Click to collapse
OK you have to state what version twrp you are flashing?
Now if it's just recovery then I would say to try TWRP 3.1.1.0 which is most stable version in my view.
Note: Re-download all Twrp tar, Supersu & no verity zip.
First flash twrp & then let the device boot to home screen.
Second reboot to recovery by hard keys.
If you see stock recovery go back to download mode flash twrp & go back to recovery without booting as you are doing but this time just swipe to allow modifications & reboot to recovery again.
Without flashing anything just reboot from recovery to system.
Thirdly if you device reboots to home screen then again get back to twrp recovery & now flash supersu & no verity zip & restart device. You should be able to solve this.
PRADEEPHONDA said:
OK you have to state what version twrp you are flashing?
Now if it's just recovery then I would say to try TWRP 3.1.1.0 which is most stable version in my view.
Note: Re-download all Twrp tar, Supersu & no verity zip.
First flash twrp & then let the device boot to home screen.
Second reboot to recovery by hard keys.
If you see stock recovery go back to download mode flash twrp & go back to recovery without booting as you are doing but this time just swipe to allow modifications & reboot to recovery again.
Without flashing anything just reboot from recovery to system.
Thirdly if you device reboots to home screen then again get back to twrp recovery & now flash supersu & no verity zip & restart device. You should be able to solve this.
Click to expand...
Click to collapse
Thank, i'm using TWRP 3.2.1.0 currently, i will try TWRP 3.1.1.0 as your guide. So, i will try as following step:
1. Flash TWRP 3.1.1.0 and let it boot to Home Screen
2. If ok then go to Recovery -> flash upersu & no verity zip & restart device
2.1 If still in stock then flash twrp again -> go to recovery -> allow modification -> reboot to recovery -> reboot to system
2.2 If cannot boot to Home Screen after First Step then flash twrp again -> go to recovery -> allow modification -> reboot to recovery -> reboot to system
Are those correct ?
venomnguyen said:
Thank, i'm using TWRP 3.2.1.0 currently, i will try TWRP 3.1.1.0 as your guide. So, i will try as following step:
1. Flash TWRP 3.1.1.0 and let it boot to Home Screen
2. If ok then go to Recovery -> flash upersu & no verity zip & restart device
2.1 If still in stock then flash twrp again -> go to recovery -> allow modification -> reboot to recovery -> reboot to system
2.2 If cannot boot to Home Screen after First Step then flash twrp again -> go to recovery -> allow modification -> reboot to recovery -> reboot to system
Are those correct ?
Click to expand...
Click to collapse
Yes
PRADEEPHONDA said:
Yes
Click to expand...
Click to collapse
Hi bro,
after try few time, the result is:
1. After flash TWRP and boot to home Scree, it's stuck at Samsung Logo, so i took the 2.2 step
2.2. Re-flash TWRP -> recovery -> allow modification -> reboot recovery -> reboot system. Then my device loop in bootloop
After all i have to back to stock and consider to give up rooting my phone . But one thing that always in my mind, why my Note 5 can boot normally with lineageos after flash with TWRP. Does this os different from other custom ROM that can boot in my Note 5.
Anw, thank you so much for your assist.
venomnguyen said:
Hi bro,
after try few time, the result is:
1. After flash TWRP and boot to home Scree, it's stuck at Samsung Logo, so i took the 2.2 step
2.2. Re-flash TWRP -> recovery -> allow modification -> reboot recovery -> reboot system. Then my device loop in bootloop
After all i have to back to stock and consider to give up rooting my phone . But one thing that always in my mind, why my Note 5 can boot normally with lineageos after flash with TWRP. Does this os different from other custom ROM that can boot in my Note 5.
Anw, thank you so much for your assist.
Click to expand...
Click to collapse
No problem, you are welcome.
Try magisk root. Follow their rooting procedures in the xda forum.
magisk root for note5 nougat try this sir.
http://galaxynote5root.com/galaxy-n...galaxy-note-5-on-android-7-0-nougat-w-magisk/
venomnguyen said:
Hi bro,
after try few time, the result is:
1. After flash TWRP and boot to home Scree, it's stuck at Samsung Logo, so i took the 2.2 step
2.2. Re-flash TWRP -> recovery -> allow modification -> reboot recovery -> reboot system. Then my device loop in bootloop
After all i have to back to stock and consider to give up rooting my phone . But one thing that always in my mind, why my Note 5 can boot normally with lineageos after flash with TWRP. Does this os different from other custom ROM that can boot in my Note 5.
Anw, thank you so much for your assist.
Click to expand...
Click to collapse
Hi there it's not that difficult i've faced the same issue with my n920c
Solution: Install the TWRP recovery just like normal but when the device is rebooting and black screen shows up Press and Hold [Power+home+vol down] until you see TWRP screen
Please Note: this is really important to press and hold while rebooting ...
After this you can normally reboot to recovery there would be no problem
Good luck !
hey bro,,im facing same problem i am a poor fellow and note5 was a gift for me, but i upgraded it to 7.0 from 5.1.1 which i was running from 2017....now the same problem always on samsung galaxy note5 logo ..i dont know what to do tried various roms , kernels it boots to homescreen but if i restart it gets stuck...otherwise lineage boots everytime, whats the problem ,,,xda heroes kindly help me and others facing this.
---------- Post added at 03:17 PM ---------- Previous post was at 03:16 PM ----------
plz rply devs
---------- Post added at 03:17 PM ---------- Previous post was at 03:17 PM ----------
venomnguyen - any solution bro? did u succeed