Hi everyone,
Has anyone been successful in getting any of the CWM recovery variants to work on the N7105T? Every version I can find listed for the N7105 (no dedicated N7105T version, from both XDA/Google/ROM manager) causes the phone phone to boot into the standard Samsung screen. However the screen then glitches by moving to the left and disappears all together.
Easily rectified by flashing TWRP recovery or stock recovery, but the issue is I'm attempting to install one of the Modem files for the N7105T after flashing an N7105 custom ROM. Without the modem file the custom ROMS also experience the same glitch mentioned above from CWM recovery. Unfortunately the modem.zip file I have on file cannot be found in the Download directory of the phone when using TWRP so I suspect I'll have to flash this using CWM.
Any thoughts? Or better yet, has anyone else successful loaded a custom N7105 ROM by flashing the ROM and then the modem.zip in CWM as above for the N7105T or by any other methods?
FYI;
Just flashed Phils modification of CWM which works successfully on the N7105T without the glitch. However the phone still cannot boot into a custom N7105 ROM successfully.
I tried to do the below to no avail;
Using Phils Recovery, flashed Paranoid Android & applicable GAPPS. After this I flashed the N7105T Telstra Modem using Phils Recovery. Rebooted phone and the phone turns on and screen 'glitches' as described earlier.
I also have the same problem
Note2-CWM-6.0.4.1-GT-N7105t
Jonnit said:
Hi everyone,
Has anyone been successful in getting any of the CWM recovery variants to work on the N7105T? Every version I can find listed for the N7105 (no dedicated N7105T version, from both XDA/Google/ROM manager) causes the phone phone to boot into the standard Samsung screen. However the screen then glitches by moving to the left and disappears all together.
Easily rectified by flashing TWRP recovery or stock recovery, but the issue is I'm attempting to install one of the Modem files for the N7105T after flashing an N7105 custom ROM. Without the modem file the custom ROMS also experience the same glitch mentioned above from CWM recovery. Unfortunately the modem.zip file I have on file cannot be found in the Download directory of the phone when using TWRP so I suspect I'll have to flash this using CWM.
Any thoughts? Or better yet, has anyone else successful loaded a custom N7105 ROM by flashing the ROM and then the modem.zip in CWM as above for the N7105T or by any other methods?
Click to expand...
Click to collapse
I'm using Note2-CWM-6.0.4.1-GT-N7105t and all is good. I have never updated to 4.3 officially, I rooted with odin, while on 4.1.1 and used this recovery and have been flashing for months. I now am trying to return to stock and update to 4.3. Just so I can use stock kernel in custom 4.3 roms ( Wifi won't work unles flash Agni or Devil kernels ). http://techbeasts.com/2013/08/22/how-to-root-install-cwm-recovery-on-samsung-galaxy-note-2/ - happy to help more.
---------- Post added at 08:58 PM ---------- Previous post was at 08:46 PM ----------
slysurfer said:
I'm using Note2-CWM-6.0.4.1-GT-N7105t and all is good. I have never updated to 4.3 officially, I rooted with odin, while on 4.1.1 and used this recovery and have been flashing for months. I now am trying to return to stock and update to 4.3. Just so I can use stock kernel in custom 4.3 roms ( Wifi won't work unles flash Agni or Devil kernels ). http://techbeasts.com/2013/08/22/how-to-root-install-cwm-recovery-on-samsung-galaxy-note-2/ - happy to help more.
Click to expand...
Click to collapse
Follow all steps. - http://androidxda.com/root-samsung-galaxy-note-2-n7100t.
Now I updated to stock telstra 4.3, using odin v3.09. Firmware from samsmobile. worked first go and many times since
Then I flashed philz recovery - ( philz_touch_6.15.4-t0lte.tar) with odin v1.85 - untick auto-reboot and once installed just hold vol up/home and power to get to philz recovery - Then to root, download and extract saferoot = http://forum.xda-developers.com/showthread.php?t=2565758 - it works on GT-N7105T ( just a N7105 really once you get a message on your phone about allowing USB ADB debugging / SU permision, all is good. I started the bat file again after i got the su message prior attempt and it completed. Then I updated supersu in play store then opened and updated binary in supersu and restarted phone. Just installed CWM and installed cm touch recovery app granted permissions, like on 4.1.2. phone is free now. will install roms tonight. any issues i will update this.
I tried to unroot my phone after getting stuck in a cyanogen bootloop a while back. I managed to get into recovery and install stock firmware via Odin. I did not however install the stock kernel or stock recovery. I am now in a stock t-mobile bootloop. I'm not sure what to do, I have been unable to get into recovery thus far, but I can keep trying. What can I do?
lasabrjotur said:
I tried to unroot my phone after getting stuck in a cyanogen bootloop a while back. I managed to get into recovery and install stock firmware via Odin. I did not however install the stock kernel or stock recovery. I am now in a stock t-mobile bootloop. I'm not sure what to do, I have been unable to get into recovery thus far, but I can keep trying. What can I do?
Click to expand...
Click to collapse
Can you get in Download mode? To work with Odin you must be in Download mode, not recovery.
If you can get in Download mode, then start Odin and flash a TWRP Odin flashable recovery:
http://teamw.in/project/twrp2/101
Then at least you should have a functional recovery. From there you could either try to flash your stock ROM again, or any another ROM.
Are you 100% sure what you flashed was a good stock ROM for the T989 ?
Dont you have a nandroid you could restore?
I tried to root my LG-855 last night, i managed to get superuser installed but i cannot install a customer recovery.
i used flashify to flash recovery but i am getting a secure boot error when rebooting and when i try to manually boot into recovery it just goes to stock recovery.
I am currently on lollipop
please help
I just rooted my LG G3-D855 and i flashed TWRP-2.8.6.1 with flasify and everything goes fine. Did you try re-flash it again or some thing just when wrong when you rooted your phone.
Maybe you can try this app: https://play.google.com/store/apps/details?id=b007.autorecd855.
I have tried again using flashify and the app you have the link to and still nothing. I think I may just unroot it and try again. Cheers for the help
stewart30 said:
I tried to root my LG-855 last night, i managed to get superuser installed but i cannot install a customer recovery.
i used flashify to flash recovery but i am getting a secure boot error when rebooting and when i try to manually boot into recovery it just goes to stock recovery.
I am currently on lollipop
please help
Click to expand...
Click to collapse
Flashing recovery like on kitkat is not working on lollipop I think. There is a thread here on XDA about this
via LG G3 @ Resurrection Remix
---------- Post added at 12:20 AM ---------- Previous post was at 12:18 AM ----------
http://forum.xda-developers.com/showthread.php?t=3072767
via LG G3 @ Resurrection Remix
Managed to get it sorted. Used autorec app to flash stock recovery(although not needed) and they flashed twrp and it worked.
i used twrp 2..8.7.0 to flash various mokee roms, htc sense rom, resurrection remix and many more but facing bootloops on each.
i wiped everything formatted external and internal storage still last time i flashed mokee rom i was able to get into initial setup of the phone then after a minute still bootloop happened.
glad i took the backup so i was able to restore and i was able to run resurrection remix rom for a month
lastly i tried fastboot method to install stable 4.3 older version and it worked
after i tried flashing twrp and tried various new roms still bootloop.
i am tired of this i cant find any solution online.
EDIT- case still unresolved
my friend said that you messed up phones paritions thats why custom roms fail to boot well so when flash custom rom
it flashes data to some other parition and formats real parition so phone cant boot will go to boot loop maybe some recovery or some rom you installed over writtern your phone parition id's so now when install rom phone mistakes system folder for boot.img folder so when trying to boot up kernerl tries to find system files and its not inside system parition
i dont get much of it can someone help?
Have you flashed latest firmware file? You can find it in cm13 thread, post #3.
cvele992 said:
Have you flashed latest firmware file? You can find it in cm13 thread, post #3.
Click to expand...
Click to collapse
yes i tried that too still bootloop i dont know why i have flashed various roms in past never faced a bootloop
geek.shivam said:
yes i tried that too still bootloop i dont know why i have flashed various roms in past never faced a bootloop
Click to expand...
Click to collapse
flash latest miui 7 fastboot rom.
If it does not help then maybe its a problem with recovery.
Did u remember anything doing to recovery before getting bootloops
[email protected] said:
flash latest miui 7 fastboot rom.
If it does not help then maybe its a problem with recovery.
Did u remember anything doing to recovery before getting bootloops
Click to expand...
Click to collapse
nothing odd i can remember, i flashed twrp many times still facing this issue.
i am sure if i will flash the latest fastboot rom it will work its downloading but i cant install any custom rom, again i installed mokee rom it showed some starting steps in startup like setup wifi and google account then again it started bootlooping
happens with every rom
geek.shivam said:
nothing odd i can remember, i flashed twrp many times still facing this issue.
i am sure if i will flash the latest fastboot rom it will work its downloading but i cant install any custom rom, again i installed mokee rom it showed some starting steps in startup like setup wifi and google account then again it started bootlooping
happens with every rom
Click to expand...
Click to collapse
what i trying to say was First install the latest fastboot rom it got latest firmware then install twrp and try to flash custom rom
---------- Post added at 01:04 PM ---------- Previous post was at 01:02 PM ----------
New TWRP v3 also available in original development section in xda...try that if it does the trick
[email protected] said:
what i trying to say was First install the latest fastboot rom it got latest firmware then install twrp and try to flash custom rom
---------- Post added at 01:04 PM ---------- Previous post was at 01:02 PM ----------
New TWRP v3 also available in original development section in xda...try that if it does the trick
Click to expand...
Click to collapse
wait let me actually try that
Still same problems persists, i flashed laterst twrp recovery flashed latest fastboot rom too still i cant able to flash any custom rom still bootloops happen . the rom booted after several bootloops but soon i got on setup of new rom selected language and again bootloop :/
i tried everything i can it seems like i can only use a fastboot rom here on my phone and that too outdated i cant update it either . am i the only one facing this problem,?
Before flashing the rom. Format the phone from recovery and after flashing the rom try to factory reset it. Hope it works...
chauhansonu104 said:
Before flashing the rom. Format the phone from recovery and after flashing the rom try to factory reset it. Hope it works...
Click to expand...
Click to collapse
i have tried this many times this wont help me and same problem persist
failed
chauhansonu104 said:
Before flashing the rom. Format the phone from recovery and after flashing the rom try to factory reset it. Hope it works...
Click to expand...
Click to collapse
bro i tried that too still same problem persists
i cant able to flash a single rom except fastboot rom
not even the stable miui
Use latest firmware file
first get everything stock, i.e ROM< RECOVERY<KERNEL
after that flash latest TWRP<then download the latest CM build< flash it< wipe cache and dalvik< install the firmware file which u can find on the CM 13 Thread #3 post< wipe cache and dalvik again... reboot and enjoy
hope i helped
I also have the same problem.....
Is ur problem solved now???
Please reply
So I was running stock 4.0.0 with twrp recovery just fine, and go to update via ota the 4.0.1. Now this failed, and so I decided I might as well clean install. After installation now, regardless of rom (even lineageos based) I cannot boot out of twrp. Every reboot leads back to twrp. I can access fastboot, but thats it. I've tried reflashing twrp also
Edit: This is ridiculous. Literally everything looks perfect but it refuses to boot. Tried every rom I can, even tried different recoveries and ****ing nothing. I can't find any rhyme or reason to this nonsense.
Shayded said:
So I was running stock 4.0.0 with twrp recovery just fine, and go to update via ota the 4.0.1. Now this failed, and so I decided I might as well clean install. After installation now, regardless of rom (even lineageos based) I cannot boot out of twrp. Every reboot leads back to twrp. I can access fastboot, but thats it. I've tried reflashing twrp also
Edit: This is ridiculous. Literally everything looks perfect but it refuses to boot. Tried every rom I can, even tried different recoveries and ****ing nothing. I can't find any rhyme or reason to this nonsense.
Click to expand...
Click to collapse
I'll tell you exactly the same as the last one...
First of all... YOU can NEVER try to install an official update having a custom recovery (like TWRP) installed in your device. Previously, you should have changed to stock recovery.
Having said that, you have to make the following....
1. If you have already the full room into internal memory, reboot into recovery. If not, copy the full rom to a pendrive an connect it by OTG.
2. Restart in recovery mode and click on wipe and then, advance wipe and select... davilk, cache, data and system partitions. then, slide the bar.
3. When it finish, go back to the main menu and click on install. Select the full rom from internal storage (or OTG) and install it.
4. When it finishs, you have two options from here...
4.1. First option. Try to install TWRP recovery before rebooting, because the rom will have installed stock recovery. After flashing twrp, theoretically you should get twrp installed but sometimes it fails. So, It is possible it is blocked when you try to reboot system and you can see a warming saying "there is not rom installed". Don't panic, turn off your phone from power bottom and restart the device. You will see the room installed but not the twrp. In this case, you will have to install TWRP from sideload and then, Supersu from recovery.
4.2. Second option. When the rom instalation has a finished, reboot system to check the rom is installed correctly. Then, restart again your device to fastboot mode and install recovery twrp from sideload. Finally, you can install Supersu from recovery.
This is all! Never settle!
Flash stock recovery? Does it boot?
I have the exact same problem and in stuck in a pickle
---------- Post added at 08:15 AM ---------- Previous post was at 08:12 AM ----------
Crazyhat said:
I'll tell you exactly the same as the last one...
First of all... YOU can NEVER try to install an official update having a custom recovery (like TWRP) installed in your device. Previously, you should have changed to stock recovery.
Having said that, you have to make the following....
1. If you have already the full room into internal memory, reboot into recovery. If not, copy the full rom to a pendrive an connect it by OTG.
2. Restart in recovery mode and click on wipe and then, advance wipe and select... davilk, cache, data and system partitions. then, slide the bar.
3. When it finish, go back to the main menu and click on install. Select the full rom from internal storage (or OTG) and install it.
4. When it finishs, you have two options from here...
4.1. First option. Try to install TWRP recovery before rebooting, because the rom will have installed stock recovery. After flashing twrp, theoretically you should get twrp installed but sometimes it fails. So, It is possible it is blocked when you try to reboot system and you can see a warming saying "there is not rom installed". Don't panic, turn off your phone from power bottom and restart the device. You will see the room installed but not the twrp. In this case, you will have to install TWRP from sideload and then, Supersu from recovery.
4.2. Second option. When the rom instalation has a finished, reboot system to check the rom is installed correctly. Then, restart again your device to fastboot mode and install recovery twrp from sideload. Finally, you can install Supersu from recovery.
This is all! Never settle!
Click to expand...
Click to collapse
Here is the problem tho, I can flash Roms but when I attempte to boot into said ROM it just goes straight back to recovery.
---------- Post added at 08:16 AM ---------- Previous post was at 08:15 AM ----------
Puddi_Puddin said:
Flash stock recovery? Does it boot?
Click to expand...
Click to collapse
Tried that too through adb but didn't work for some reason, I forget. Either I messed up or the phone didn't allow it
urvianoob said:
I have the exact same problem and in stuck in a pickle
---------- Post added at 08:15 AM ---------- Previous post was at 08:12 AM ----------
Here is the problem tho, I can flash Roms but when I attempte to boot into said ROM it just goes straight back to recovery.
---------- Post added at 08:16 AM ---------- Previous post was at 08:15 AM ----------
Tried that too through adb but didn't work for some reason, I forget. Either I messed up or the phone didn't allow it
Click to expand...
Click to collapse
You don't do that with adb but with Fastboot
Boot into fastboot > fastboot flash recovery-file name.img
Here's what I had to do: flash the new stock recovery in fastboot rather than twrp at all, then boot to it FROM fastboot. Sideload the full firmware (4.0.0, 4.0.1 either should work) and reboot/power off. My phone seemingly bricked at this stage but playing around with the buttons got me back into stock recovery where I got the option to decrypt and wipe. After this it booted up unto a fresh install of 4.0.1.
Hi
Puddi_Puddin said:
You don't do that with adb but with Fastboot
Boot into fastboot > fastboot flash recovery-file name.img
Click to expand...
Click to collapse
Yeah that is what I meant to say lol, I found something in another article on the same problem that worked for a guy, gonna try it soon
---------- Post added at 08:31 AM ---------- Previous post was at 08:22 AM ----------
Shayded said:
Here's what I had to do: flash the new stock recovery in fastboot rather than twrp at all, then boot to it FROM fastboot. Sideload the full firmware (4.0.0, 4.0.1 either should work) and reboot/power off. My phone seemingly bricked at this stage but playing around with the buttons got me back into stock recovery where I got the option to decrypt and wipe. After this it booted up unto a fresh install of 4.0.1.
Click to expand...
Click to collapse
OK I get all of it so basically I flash stock recovery from fast boot, boot into the new stock recovery via fast boot, then flash ROM and I'm done?
OTA works ONLY if you are on stock recovery, rom, kernel.
I suggest to format data in recovery (this will wipe ALL in youre phone),
flash modified recovery (.22, .23. 28 by eng.stk),
flash FULL rom,
flash SuperSU 2.79 stable, if you want root,
flash recovery,
reboot to recovery,
reboot to rom.
Shayded said:
Here's what I had to do: flash the new stock recovery in fastboot rather than twrp at all, then boot to it FROM fastboot. Sideload the full firmware (4.0.0, 4.0.1 either should work) and reboot/power off. My phone seemingly bricked at this stage but playing around with the buttons got me back into stock recovery where I got the option to decrypt and wipe. After this it booted up unto a fresh install of 4.0.1.
Click to expand...
Click to collapse
Where can I get the stock recovery download?
something like that happen to me when i try to go back from N to MM oxygen, i managed to fixed it by installing the stock recovery then install the 3.26 plus the 3.26 "modem" (if i didnt install this one, my touch screen wouldnt work) after that it just works, then i updated to 3.28
i havent install twrp and do the root for now because dont have time to tinker yet, but i can just do than whenever i have the time
I think ---- and my solution
I think some script is created as we click update...It's running on boot up and causing this problem...
I had this problem yesterday and it took me a lot of time to get my device to working...
SOLUTION: first backup the data(it backsup apps and such) from twrp and other files which are important for you...copy it to a PC.
follow the second step in this thread(it will wipe everything)
It's not allowing me to post link...It's the mega unbrick guide from Oneplus3 forums
It will take you to older version and then flash full zip(nougat build) from modded twrp..restore the backup..don't update until someone finds a solution...I did that and I'm waiting for a solution to continue...
hope it helps
This is how I solved mine.
1) Go back to stock recovery v2
2) adb sideload oos, flash magisk then flash systemless supersu.
Try this guys, found a way how to flash 36mb OTA file with latest modified TWRP by eng.stk here https://forum.xda-developers.com/devdb/project/dl/?id=22429
1. Download and dirty flash the full 4.0 zip https://drive.google.com/file/d/0BzS3nWITUqU_Sk5yQkRqWkhFY3c/view
2. Flash 4.0.1 OTA (36mb) https://drive.google.com/file/d/0B6FY-XKZtgn4R2d2Rk8xd3AzWVE/view?usp=drivesdk
3. Flash SuperSU
4. Reboot
Sent from my ONEPLUS A3000 using XDA-Developers Legacy app
eko_cahyono said:
Try this guys, found a way how to flash 36mb OTA file with latest modified TWRP by eng.stk here https://forum.xda-developers.com/devdb/project/dl/?id=22429
1. Download and dirty flash the full 4.0 zip https://drive.google.com/file/d/0BzS3nWITUqU_Sk5yQkRqWkhFY3c/view
2. Flash 4.0.1 OTA (36mb) https://drive.google.com/file/d/0B6FY-XKZtgn4R2d2Rk8xd3AzWVE/view?usp=drivesdk
3. Flash SuperSU
4. Reboot
Sent from my ONEPLUS A3000 using XDA-Developers Legacy app
Click to expand...
Click to collapse
Did it work for you? For me it keeps booting back to TWRP
---------- Post added at 03:45 AM ---------- Previous post was at 03:17 AM ----------
Shayded said:
Here's what I had to do: flash the new stock recovery in fastboot rather than twrp at all, then boot to it FROM fastboot. Sideload the full firmware (4.0.0, 4.0.1 either should work) and reboot/power off. My phone seemingly bricked at this stage but playing around with the buttons got me back into stock recovery where I got the option to decrypt and wipe. After this it booted up unto a fresh install of 4.0.1.
Click to expand...
Click to collapse
Where did you get new stock recovery? link please
paul369741 said:
Did it work for you? For me it keeps booting back to TWRP
---------- Post added at 03:45 AM ---------- Previous post was at 03:17 AM ----------
Where did you get new stock recovery? link please
Click to expand...
Click to collapse
Yes It works
You can grab the stock recovery in the OP3 toolkit here on xda
https://forum.xda-developers.com/oneplus-3/development/toolkit-oneplus-3-toolkit-unlock-t3398799
Flash through fastboot, then flash/sideload a full stock zip. After that your phone should be back in working order and you can flash TWRP back.
Goodluck!
qyrus said:
You can grab the stock recovery in the OP3 toolkit here on xda
https://forum.xda-developers.com/oneplus-3/development/toolkit-oneplus-3-toolkit-unlock-t3398799
Flash through fastboot, then flash/sideload a full stock zip. After that your phone should be back in working order and you can flash TWRP back.
Goodluck!
Click to expand...
Click to collapse
If my phone is rooted, flashing through fastboot the stock recovery will remove root?