This has probably been said 1000 times before, but, I'm an idiot.
Now that we got that out of the way, perhaps you fine folks will help a dummy out?
About a year ago, I followed this guide and was successful in all that it deals with (unlocking bootloader, root, installing custom recovery and flashing custom rom).
My phone started acting a little buggy lately, (probably because I had less than 5 gb of space left? ) so I decided I wanted to just wipe everything and start "fresh".
I went into TWRP, wiped EVERYTHING, (wipe/advanced wipe/checked everything (dalvick,system,data,internal,cache) rebooted into recovery, sideloaded the newest Pure Nexus ROM and GApps zips, flashed both. After flashing new ROM, tried to reboot system, a message appeared saying it appears I do not have supersu installed, would I like to install it now? or something to that effect.
I wiped for"yes", phone turned off, then was stuck on the animation screen (swirling/color dot things) when tying to boot up.
Hold power button down till shut off, then restarted in recovery, wiped EVERYTHING (again), re-flashed the ROM, only this time said "no" to the supersu install screen.
Phone loaded up and is running perfectly.
However, I am no longer rooted???
I wasn't aware wiping everything in TWRP would remove root.
I'm confused because as I already said, I'm a dummy!, but when following the guide, I should root, then install a custom recovery.
My question is, do I only need to concern myself with the one step for rooting with CF-Root
since I already have a recovery installed, or am I going to need to re-install TWRP after rooting and then re-flashing the ROM and GApps?
I'm sure you folks are probably sick and tired of fools like me who just blindly follow along with XDA's [HOW TO] threads without knowing what or why we are doing what we are doing, but I appreciate you all just the same!
Any advice is appreciated!
Thanks in advance.
totallybeachin said:
This has probably been said 1000 times before, but, I'm an idiot.
Now that we got that out of the way, perhaps you fine folks will help a dummy out?
About a year ago, I followed this guide and was successful in all that it deals with (unlocking bootloader, root, installing custom recovery and flashing custom rom).
My phone started acting a little buggy lately, (probably because I had less than 5 gb of space left? ) so I decided I wanted to just wipe everything and start "fresh".
I went into TWRP, wiped EVERYTHING, (wipe/advanced wipe/checked everything (dalvick,system,data,internal,cache) rebooted into recovery, sideloaded the newest Pure Nexus ROM and GApps zips, flashed both. After flashing new ROM, tried to reboot system, a message appeared saying it appears I do not have supersu installed, would I like to install it now? or something to that effect.
I wiped for"yes", phone turned off, then was stuck on the animation screen (swirling/color dot things) when tying to boot up.
Hold power button down till shut off, then restarted in recovery, wiped EVERYTHING (again), re-flashed the ROM, only this time said "no" to the supersu install screen.
Phone loaded up and is running perfectly.
However, I am no longer rooted???
I wasn't aware wiping everything in TWRP would remove root.
I'm confused because as I already said, I'm a dummy!, but when following the guide, I should root, then install a custom recovery.
My question is, do I only need to concern myself with the one step for rooting with CF-Root
since I already have a recovery installed, or am I going to need to re-install TWRP after rooting and then re-flashing the ROM and GApps?
I'm sure you folks are probably sick and tired of fools like me who just blindly follow along with XDA's [HOW TO] threads without knowing what or why we are doing what we are doing, but I appreciate you all just the same!
Any advice is appreciated!
Thanks in advance.
Click to expand...
Click to collapse
Boot back into TWRP and reflash SU
totallybeachin said:
... re-flashed the ROM, only this time said "no" to the supersu install screen......
Click to expand...
Click to collapse
That's correct. No in twrp - is needed when there is already a SU in the flashed rom.
Probably you have not the most recent version of twrp.
In play store there are apps to check if you have root acces.
You can also go to the launcher and start the superSU app
kwdan said:
Boot back into TWRP and reflash SU
Click to expand...
Click to collapse
It always seems to be the most simple thing!
I'm not generally a stupid person, but this stuff can sure make a girl blush!
Thank you.
Worked like a charm.
Falling in love all over again with my Nexus 6.
.....makes note for NEXT TIME I have been eating dummie bears!
As NLBeev said, you are probably using an outdated version of TWRP. It doesn't ask about su any longer.
Related
So I just got back my nexus one from htc, got my mother board changed and preloaded with 2.2. I rooted it with universal root without unlocking my bootloader.
Problem: when I reboot after successfully loading CM6 and have it running, it reboots to the "X" and hangs.
Am I doing something wrong?
For how long is it hanging? I recall having to wait what seemed like forever the first time I booted with CM6... but eventually it 'took'.
rnick1976 said:
For how long is it hanging? I recall having to wait what seemed like forever the first time I booted with CM6... but eventually it 'took'.
Click to expand...
Click to collapse
You have a locked bootloader as well right? I waited a good 30 mins. Maybe i should leave i and give it more time to boot?
All works normally on inital boot of CM6 after install with locked bootloader, just that when i try to reboot the first time manually... it stays at the "X" for an awefully long time.
Did you wipe?
Try wiping data,cache,dalvik-cache.
ya, this is what i did.
1) Universal root with locked biootloader on stock 2.2
2) installed rom manger
3) flashed recovery + downloaded and flashed CM6 + google apps
Boots up fine, runs CM6 flawless. Upon manual reboot, it hangs on the X
Then i tried:
1) reboot into recovery
2) full wipe + davlick cache
3) reinstall CM6 + google apps
Still hangs. I haven't had time to play with it, but ill try to leave it along upon reboot a lil longer to see if it pulls thu~
Please let me know whether after installing the 6.0 cyn. rom and after the initial install you can then reboot and it pulls up and runs as usual. I am getting ready to flash the cyn 6.0 rom I am on stock 2.2 and have never flashed a rom before I have backed up the current rom through Rom Manager and flashed Clockworkmod recovery and I have the unloocked bootloader root as well. I have a question if and when I flash the new rom through Rom Manager does it not wipe and clear data etc. automatically? If not how would i go about doing that. Any and all help is greatly Appreciated!!!!!!!!!!!!!!
tenbeau said:
Please let me know whether after installing the 6.0 cyn. rom and after the initial install you can then reboot and it pulls up and runs as usual. I am getting ready to flash the cyn 6.0 rom I am on stock 2.2 and have never flashed a rom before I have backed up the current rom through Rom Manager and flashed Clockworkmod recovery and I have the unloocked bootloader root as well. I have a question if and when I flash the new rom through Rom Manager does it not wipe and clear data etc. automatically? If not how would i go about doing that. Any and all help is greatly Appreciated!!!!!!!!!!!!!!
Click to expand...
Click to collapse
MY bootloader is LOCKED, i rooted differently. Since you have a UNLOCKED bootloader, you will have no problems booting.
I still never got a chance to play with the N1 yet, ill keep u guys updated
tenbeau said:
I have a question if and when I flash the new rom through Rom Manager does it not wipe and clear data etc. automatically? If not how would i go about doing that. Any and all help is greatly Appreciated!!!!!!!!!!!!!!
Click to expand...
Click to collapse
When you go to flash a new ROM in Manager, it will offer you the option to wipe and/or backup before it applies the ROM.
Thank you so much for the kind replies!! I meant to say that I had a locked bootloader root using the one click root and unroot. I guess this means I would face the same situation as described earlier in this thread. I am very grateful to all the posters for sharing. THANK YOU!!!
Do you mean it hangs on the nexus one X boot animation? Because CM6 has it's own boot animation you shouldn't see that at all.
I would test it with a different Rom to see if you get the same result. If it's only CM6 doing that, maybe try the nightly version.
I know there are a million posts about this, but I have been through them all trying to follow the guidance because the problems seemed to be the same as others have faced, but I feel differently now....
I unlocked my HTC one, following the htc dev site.
I installed TWRP (I cannot for the life of me get CWM to load into reovery, it only reboots the phone...)
loaded the roms/Super SU onto the SD card.
I know my phone is rooted (or i should assume?) because SuperSU is requiring me to grant access to apps and such.
I flash the custom ROM to the phone, install the package following Revolutions steps. Complete installation, return to fastboot menu. Flash boot.img, clear cache and reboot phone....Phone goes to the HTC Quietly Brilliant screen, with the development message at the bottom and continues to reboot over and over and over from there.
What did I do wrong?
I know pretty much have a phone that wont work because even after restoring it, it is ina boot loop after it fully boots up and nothing is loading correctly. Is there any way to start this from scratch?
Notes:
I tried doing an ADB sideload of Revolution HD.
I do a factory wipe before i load any rom....
Edit:
I have tried multiple ROMS...all the same effect....
I also get the message after installing the ROM from TWRP that "your device is not rooted, swipe to install superSU" so sometimes i swipe it, sometimes i dont...either way same result.
Update #2:
I flashed a ROM called 42ONE....it ended up successfully booting past the HTC screen and is currently updating the android system...However, it will operate for about 2 minutes then the phone reboots like it was before when i tried to restore....what the heck?!?
There is no need to flash the boot.img in fastboot. Just flash the rom from twrp.
iElvis said:
There is no need to flash the boot.img in fastboot. Just flash the rom from twrp.
Click to expand...
Click to collapse
right, i only did it to ensure that wasnt the problem....however my new problem...I Have a ROM finally installed...but my phone is rebooting a minute after it starts. I am able to use the screen and everything but it just shuts down and starts back up on its own...
Switchback802 said:
right, i only did it to ensure that wasnt the problem....however my new problem...I Have a ROM finally installed...but my phone is rebooting a minute after it starts. I am able to use the screen and everything but it just shuts down and starts back up on its own...
Click to expand...
Click to collapse
Download the rom again (might be a bad download), transfer to your sdcard, do a full wipe, and flash again. Something you flashed has created a conflict.
Edit: That's a Sprint ROM. Do you have a Sprint phone? If you've been flashing GSM roms, that's your problem there.
iElvis said:
Download the rom again (might be a bad download), transfer to your sdcard, do a full wipe, and flash again. Something you flashed has created a conflict.
Edit: That's a Sprint ROM. Do you have a Sprint phone? If you've been flashing GSM roms, that's your problem there.
Click to expand...
Click to collapse
I do have a sprint phone. Trying to reflash the rom now.
Edit #2:
Installed Cyanogen Mod, looks great boots up but stil reboots my phone. Not only that but I have no service either.
Switchback802 said:
I do have a sprint phone. Trying to reflash the rom now.
Click to expand...
Click to collapse
Hi,
Maybe you'll have a better help here: Sprint HTC One ?
Switchback802 said:
I know there are a million posts about this, but I have been through them all trying to follow the guidance because the problems seemed to be the same as others have faced, but I feel differently now....
I unlocked my HTC one, following the htc dev site.
I installed TWRP (I cannot for the life of me get CWM to load into reovery, it only reboots the phone...)
loaded the roms/Super SU onto the SD card.
I know my phone is rooted (or i should assume?) because SuperSU is requiring me to grant access to apps and such.
I flash the custom ROM to the phone, install the package following Revolutions steps. Complete installation, return to fastboot menu. Flash boot.img, clear cache and reboot phone....Phone goes to the HTC Quietly Brilliant screen, with the development message at the bottom and continues to reboot over and over and over from there.
What did I do wrong?
I know pretty much have a phone that wont work because even after restoring it, it is ina boot loop after it fully boots up and nothing is loading correctly. Is there any way to start this from scratch?
Notes:
I tried doing an ADB sideload of Revolution HD.
I do a factory wipe before i load any rom....
Edit:
I have tried multiple ROMS...all the same effect....
I also get the message after installing the ROM from TWRP that "your device is not rooted, swipe to install superSU" so sometimes i swipe it, sometimes i dont...either way same result.
Update #2:
I flashed a ROM called 42ONE....it ended up successfully booting past the HTC screen and is currently updating the android system...However, it will operate for about 2 minutes then the phone reboots like it was before when i tried to restore....what the heck?!?
Click to expand...
Click to collapse
Revolution HD is not compatible with Sprint devices.
bigdaddy619 said:
Revolution HD is not compatible with Sprint devices.
Click to expand...
Click to collapse
problem resolved so far. REflashed stock rom, relocked device. its working for now.
TWRP Recovery
Rooted
Xposed framework installed
Been getting bugged for the 4.4.4 update, and I wanted to open and look at the ZIP out of curiosity, so I hit install now, thinking it still needed to download... but turns out it didn't, and rebooted right away.
So now I'm stuck in a boot loop of sorts.... it boots, and loads up Android, and I can use the phone, but after about 20-30 seconds it reboots into recovery.
Is there an easy way out of this without wiping everything? Preferably a modded OTA that I can install for the 4.4.4 update.
Check out the thread under general tab to use RSD Flasher or House of Moto to install the 4.4.4 FXZ
DB's Moto X
coreno said:
TWRP Recovery
Rooted
Xposed framework installed
Been getting bugged for the 4.4.4 update, and I wanted to open and look at the ZIP out of curiosity, so I hit install now, thinking it still needed to download... but turns out it didn't, and rebooted right away.
So now I'm stuck in a boot loop of sorts.... it boots, and loads up Android, and I can use the phone, but after about 20-30 seconds it reboots into recovery.
Is there an easy way out of this without wiping everything? Preferably a modded OTA that I can install for the 4.4.4 update.
Click to expand...
Click to collapse
The above post is good advice. If you use House of Moto with the full 4.4.4 FXZ, you can choose to "KEEP DATA".
You will need to flash TWRP back on and re-root afterwards AND re-install Xposed, but all of your apps and settings will remain intact.
The reason this happened is because you have TWRP installed - taking OTAs *always* requires you to have STOCK recovery - not custom.
Good Luck :good:
samwathegreat said:
The above post is good advice. If you use House of Moto with the full 4.4.4 FXZ, you can choose to "KEEP DATA".
You will need to flash TWRP back on and re-root afterwards AND re-install Xposed, but all of your apps and settings will remain intact.
The reason this happened is because you have TWRP installed - taking OTAs *always* requires you to have STOCK recovery - not custom.
Good Luck :good:
Click to expand...
Click to collapse
Thanks for the replies. Thanks for the reply... the phone eventually decided the update failed and gave up. Apparently clearing the cache would've also probably worked.
But, now I've reflashed stock recovery, removed xposed, and unrooted. I should be safe to just take the OTA now, right?
I would've done the FXZ earlier, but didn't realize there was a keep data option.
coreno said:
Thanks for the replies. Thanks for the reply... the phone eventually decided the update failed and gave up. Apparently clearing the cache would've also probably worked.
But, now I've reflashed stock recovery, removed xposed, and unrooted. I should be safe to just take the OTA now, right?
I would've done the FXZ earlier, but didn't realize there was a keep data option.
Click to expand...
Click to collapse
You can try, and it will probably work....but if it were me, I'd still use the FXZ and keep data option. It's cleaner and no chance of something going wrong. Afterwards, just do like I said -- re-flash TWRP, re-root, then reinstall Xposed.
samwathegreat said:
You can try, and it will probably work....but if it were me, I'd still use the FXZ and keep data option. It's cleaner and no chance of something going wrong. Afterwards, just do like I said -- re-flash TWRP, re-root, then reinstall Xposed.
Click to expand...
Click to collapse
Thanks for you help! I am all upgraded and got everything back going to the way it was!
coreno said:
Thanks for you help! I am all upgraded and got everything back going to the way it was!
Click to expand...
Click to collapse
Great!! Glad to hear everything worked out. I sent you a Private message - check your PMs
Just to add my experience: I too tried to apply the update (rooted, 4.4.2, xposed, stock recovery, locked boot loader).
Got the boot loop you mentioned.
Only remedy was for me to quickly go into root explorer and rename the 3c.ota.apk and 3c.ota.odex files. Now I no longer get the notifications (unless I reboot my phone).
jco23 said:
Just to add my experience: I too tried to apply the update (rooted, 4.4.2, xposed, stock recovery, locked boot loader).
Got the boot loop you mentioned.
Only remedy was for me to quickly go into root explorer and rename the 3c.ota.apk and 3c.ota.odex files. Now I no longer get the notifications (unless I reboot my phone).
Click to expand...
Click to collapse
And in your case, it was Xposed.
There are several threads (and posts) discussing conditions for taking an OTA. You need stock recovery, have to disable Xposed, and you need to be close enough to stock so the pre-flash verification will pass. Otherwise, the OTA will fail, and/or you'll get stuck in a boot loop.
There is a little more to it as well, but I'll ask you to see the other threads.
Thought I disabled xposed. But perhaps not. I've read other threads. From my understanding, I won't be able to root (or even the quasi-root) on 4.4.4 with a locked boot loader.
Thx for the reply.
Ok so i had 5.02 rooted kitkat. Obviously unlocked bootloader. It says 3. And twrp 2.8something...
For the previous months every time i rebooted the phone it took like 10 minutes to boot for some reason. But it worked. It was laggy these days so i thought i will wipe everything and install CM12.1.
So i downloaded the rom and gapps. Then i wiped delvik, cache, system, internal memory and data. I also did format data.
I dont really understand, obviously, how android works. So i had the zips on external card and pressed install on from twrp menu. Then wiped cache and delvik cache. Tried to reboot and says 'Warning no OS found'. I say okay and then it says that it wants to root. I say ok again.
Now the PROBLEM is that it does nothing. It justs stucks on motorola boot logo for too much time. I am not sure if this is because i already had a problem with booting taking too much time or because of what i have wiped. I also tried updating bootloader again. Not sure if this changed anything
Long story short, how do i continue now? Is there a way to really delete everything i have done on the phone, then install fresh twrp and then CM12.1? And how do i fix the booting taking too much time problem...
Any help will be valueable. I just dont get how things work because nowadays there are too many things, kernels, roms, bootloaders, recoveries etc... Can i just flash the CM rom from my computer via usb? I tried something like that by ?sideload? only to get a problem about requiring 1.0.32 version. I tried to download new SDK but again i have 1.0.31 version of adb...
Thanks!
P.S. Yes, i am totally lost. But i have desire to understand...
NUKE1989 said:
Ok so i had 5.02 rooted kitkat. Obviously unlocked bootloader. It says 3. And twrp 2.8something...
For the previous months every time i rebooted the phone it took like 10 minutes to boot for some reason. But it worked. It was laggy these days so i thought i will wipe everything and install CM12.1.
So i downloaded the rom and gapps. Then i wiped delvik, cache, system, internal memory and data. I also did format data.
I dont really understand, obviously, how android works. So i had the zips on external card and pressed install on from twrp menu. Then wiped cache and delvik cache. Tried to reboot and says 'Warning no OS found'. I say okay and then it says that it wants to root. I say ok again.
Now the PROBLEM is that it does nothing. It justs stucks on motorola boot logo for too much time. I am not sure if this is because i already had a problem with booting taking too much time or because of what i have wiped. I also tried updating bootloader again. Not sure if this changed anything
Long story short, how do i continue now? Is there a way to really delete everything i have done on the phone, then install fresh twrp and then CM12.1? And how do i fix the booting taking too much time problem...
Any help will be valueable. I just dont get how things work because nowadays there are too many things, kernels, roms, bootloaders, recoveries etc... Can i just flash the CM rom from my computer via usb? I tried something like that by ?sideload? only to get a problem about requiring 1.0.32 version. I tried to download new SDK but again i have 1.0.31 version of adb...
Thanks!
P.S. Yes, i am totally lost. But i have desire to understand...
Click to expand...
Click to collapse
http://forum.xda-developers.com/moto-g-2014/general/restore-to-stock-t2873657 try to restore to stock
I am trying to do this but i dont have some files like boot.img or logo.bin etc.... Where can i download those? There is a link about mfastboot is not working. I am using linux btw so i guess the fastboot i already have is okay
EDIT: Ok i am obviously stupid. The files are on the zip ROM. Okay i am doing this. Now the question i have is, cant i install CM12.1 using fastboot like this ROM?
Okay and it worked. It booted stock rom and this time it booted in a minute or two (considering it was the first time booting i think its awesome).
Now i have to try CM rom. At least i know how to return the phone back if anything happens. Thank you very very much!
NUKE1989 said:
Okay and it worked. It booted stock rom and this time it booted in a minute or two (considering it was the first time booting i think its awesome).
Now i have to try CM rom. At least i know how to return the phone back if anything happens. Thank you very very much!
Click to expand...
Click to collapse
Glad to help
now just copy the rom you want to install and the gapps, install the latest TWRP, wipe: Cache, Dalvik Cache, Data and System and just flash the zips
Many thanks I managed to install CM12.1. Thought i think i failed to flash most of gapps for some reason i dont really care.
I only have one severe bug. 3G is not working for some reason. So i dont have gsm internet except the slow one...
So the case was I reset my device, and later after i flashed a ROM into my device, it does not boot. Instead, it goes into TWRP recovery. And it goes to TWRP every time i boot my device.
I have done this for so many times and I cannot even know what is going wrong this time. I am quite frustrated and I did googled a lot but it did not solve my problem. So, I want to know if anyone else encounter similar problem and solution towards it.
I tried:
1. Wipe the dalvik cache.
2. Remove the battery for half an hour
3. Reflash the twrp
Any efforts and reply is much appreciated.
Thank you.
Mine's exactly the same, I factory reset so I could pass the phone on; and now it will not install custom roms, I've tried about 7 or 8, and it will only boot into twrp 3.0.2-5. Soft brick, but I'm unable to find any solution.
Here's hoping someone will come and help.
I think I'll have to reinstall twrp by connecting the phone to the computer, but I've no idea how to do this.
slifer225 said:
So the case was I reset my device, and later after i flashed a ROM into my device, it does not boot. Instead, it goes into TWRP recovery. And it goes to TWRP every time i boot my device.
I have done this for so many times and I cannot even know what is going wrong this time. I am quite frustrated and I did googled a lot but it did not solve my problem. So, I want to know if anyone else encounter similar problem and solution towards it.
I tried:
1. Wipe the dalvik cache.
2. Remove the battery for half an hour
3. Reflash the twrp
Any efforts and reply is much appreciated.
Thank you.
Click to expand...
Click to collapse
Exactly the same issue here too, installed lineage 14.1, was working great, I was selling to a friend, did a factory reset, now stuck at twrp, roms install etc, but after a reset, every time straight back to TWRP.
Looks like I might need to flash back to stock somehow.
But I did find this, but not yet tried.
https://www.reddit.com/r/LineageOS/comments/5riech/how_fix_twrp_recovery_boot_loop_after_lineageos/
andydgg said:
Mine's exactly the same, I factory reset so I could pass the phone on; and now it will not install custom roms, I've tried about 7 or 8, and it will only boot into twrp 3.0.2-5. Soft brick, but I'm unable to find any solution.
Here's hoping someone will come and help.
I think I'll have to reinstall twrp by connecting the phone to the computer, but I've no idea how to do this.
Click to expand...
Click to collapse
Well i have took the ultimate solution. Back to stock firmware fix everything. Well, i guess not much to mention on stock firmware=)
I think you should do the same thing too. Good luck.
slifer225 said:
Well i have took the ultimate solution. Back to stock firmware fix everything. Well, i guess not much to mention on stock firmware=)
I think you should do the same thing too. Good luck.
Click to expand...
Click to collapse
That is good to know, I shall attempt to do the same, did you later install a custom rom and everything was fine afterwards?
Yes, i flashed custom recovery and ROM afterward. Even several attempt on wipe and flash the new ROM. So i guess it should be fixed
Thank you.
andydgg said:
Mine's exactly the same, I factory reset so I could pass the phone on; and now it will not install custom roms, I've tried about 7 or 8, and it will only boot into twrp 3.0.2-5. Soft brick, but I'm unable to find any solution.
Here's hoping someone will come and help.
I think I'll have to reinstall twrp by connecting the phone to the computer, but I've no idea how to do this.
Click to expand...
Click to collapse
As slifer225 mentioned you can downgrade to stock firmware by installing the stock MM rom s433 version using spftools.
Download and Install stock MM rom using spftools.
Here is the link- https://cloud.mail.ru/public/Cco5/JYk3ytrW1
For further info follow this post- https://forum.xda-developers.com/k3-...3#post71749243
Follow this step by step guide to go back to unrooted stock rom. If you want to root after that then try installing custom recovery(twrp) again using spftools and flash supersu.zip using recovery. Do take a backup though before rooting your device.
---------- Post added at 10:11 AM ---------- Previous post was at 10:04 AM ----------
justwondering said:
That is good to know, I shall attempt to do the same, did you later install a custom rom and everything was fine afterwards?
Click to expand...
Click to collapse
Everything is working perfectly as I myself had gone through the same issue and did everything to fix the problem until I downgraded back to stock. Did root on my device again and installed lineage 7.1.1 and it works like a charm. One thing I love about this rom is the efficient ram management, lag free but battery management is not upto the mark but I guess we can work it out.
Whatever you do never forget taking a backup of functional rom.
Yes, I can confirm the solution worked for me, I left it with stock rom for my friend, I tried lineage 14.1 and did a factory reset, but ended once again with softbrick , lineage will install and work perfectly, but as soon as you do a factory reset, soft brick
Now I've hard bricked it. I loaded up a 'looprecovery' when it rebooted there's nothing, no charge light no vibrations PC doesn't see it, land fill?
Wondering...
justwondering said:
Exactly the same issue here too, installed lineage 14.1, was working great, I was selling to a friend, did a factory reset, now stuck at twrp, roms install etc, but after a reset, every time straight back to TWRP.
Looks like I might need to flash back to stock somehow.
But I did find this, but not yet tried.
https://www.reddit.com/r/LineageOS/comments/5riech/how_fix_twrp_recovery_boot_loop_after_lineageos/
Click to expand...
Click to collapse
I think that solution only works on Snapdragons. It didn't for me. Is there a solution for MTK devices?
the solution for this(FIX)
all we need to do is reinstall a stock recovery and the again reinstall the TWRP
https://forum.xda-developers.com/k3-note/general/ufficial-thread-lenovo-k3-note-t3102997
follow this link..my phone just got fixed
My phone TWRP-looped many times. The solution is actually easy.
1. Reflash using SPFlashtool ONLY the stock recovery
2. boot into stock recovery
3. choose english > press reboot phone
4. phone will reboot into rom without problemos
5. reflash TWRP
cheers
or
1. Copy stock recovery.img into sdcard
2. In twrp, select Install and navigate to where you put stock recovery.img
3. Press install image. Then, Select recovery.img. Slide to install
4. boot into stock recovery
5. choose english > press reboot phone
6. phone will reboot into rom without problemos
7. reflash TWRP
DONE
Infinity loop recovery
andydgg said:
Now I've hard bricked it. I loaded up a 'looprecovery' when it rebooted there's nothing, no charge light no vibrations PC doesn't see it, land fill?
Click to expand...
Click to collapse
hI MY FRIEND , you have been able to fix your K3 note, I have the same problem, I made twrp flash and went into infinite loop. Can you help? thank you
I smashed it and put it in the bin. I think once you can't get a charge light after tyring for a couple of week, it's dead.
Not working for Lenovo K3 Note.
My K3 note stuck in the twrp recovery after factory reset from the RR. I tried this solution but it didn't work.
Please help.