Hello everyone, I am having a issue here after updating (dirty flash) from xtrasmooth_MRA58K to Nexus Pure.. I originally made it to the homescreen (almost), but kept getting errors etc. I tried to unbrick it in many different fashions including the use of the toolkit (wug) and eventually landed with the stuck on google boot screen. I followed: http://forum.xda-developers.com/nexus-6/general/guide-flash-factory-images-nexus-6shamu-t2954008
option 1 and 2 and still can't boot pass the google boot screen. Any help would be appreciated, as I have been trying for the past 4 hours much to no avail. I would be will to teamviewer etc as needed. Thanks!
You can't really ever dirty flash from one rom to another.
Clean flash the new rom you want to try.
4 hours with out just wiping everything in TRWP and re-installing? Your going to brick your device for real one of these times... Read through the stickies here, and do a lot more research.
there are no options 1 and 2 in that thread?
Method 1 and Method 2?
Using fastboot manually or with your little toolkit?
What was the error messages?
Thank you for the reply scryan, I have tried method 1 with it still getting stuck on the google boot screen (initial white google text) and then tried method 2 with the same results. Both times the stock rom flashed with no errors (sig errors on method 1, but not 2), and I did a "Wipe data/factory data reset" then reset which brings me to the google boot screen.
You did method 2 manually? With MRA58R downloaded straight from google?
Use fastboot to completely flash all partitions again, as method 2 shows rebooting the bootlader as needed then copy and paste directly from the command prompt all your commands and all the output.
Post it here using the [code][/code] tags.
scryan said:
You can't really ever dirty flash from one rom to another.
Clean flash the new rom you want to try.
4 hours with out just wiping everything in TRWP and re-installing? Your going to brick your device for real one of these times... Read through the stickies here, and do a lot more research.
there are no options 1 and 2 in that thread?
Method 1 and Method 2?
Using fastboot manually or with your little toolkit?
What was the error messages?
Click to expand...
Click to collapse
kalans said:
Thank you for the reply scryan, I have tried method 1 with it still getting stuck on the google boot screen (initial white google text) and then tried method 2 with the same results. Both times the stock rom flashed with no errors (sig errors on method 1, but not 2), and I did a "Wipe data/factory data reset" then reset which brings me to the google boot screen.
Click to expand...
Click to collapse
while im going to say that i always dirty flash, always, im going to agree with @scryan. first off, if you do plan on dirty flashing, ALWAYS make a backup in twrp recovery, for situations like this. i try dirty flashing from roms with similar bases, never bases that are different, or they will never boot. anyways, enought with the talk, what you need to do is download your rom, gapps, and supersu, then you want to wipe your system and data in twrp recovery, then flash your rom(gapps, and supersu as well).
simms22 said:
while im going to say that i always dirty flash, always, im going to agree with @scryan. first off, if you do plan on dirty flashing, ALWAYS make a backup in twrp recovery, for situations like this. i try dirty flashing from roms with similar bases, never bases that are different, or they will never boot. anyways, enought with the talk, what you need to do is download your rom, gapps, and supersu, then you want to wipe your system and data in twrp recovery, then flash your rom(gapps, and supersu as well).
Click to expand...
Click to collapse
This is what I would have done from the beginning. Just wipe everything from TWRP and install rom straight out.
Going back to stock, then wiping and installing rom is extra work... But good reps and since it was ****ing up in the first place always good to figure out where it was going wrong instead of just giving up and doing something else.
It looks like I wasn't allowing enough time for the transfer to happen with method 1, I tried again it and now I am rolling. Thank you both very much for trying to help And I normally keep a good nandroid for everything, but 32gb is on the smaller end for me.
kalans said:
It looks like I wasn't allowing enough time for the transfer to happen with method 1, I tried again it and now I am rolling. Thank you both very much for trying to help And I normally keep a good nandroid for everything, but 32gb is on the smaller end for me.
Click to expand...
Click to collapse
im used to 16gb, so 32gb leaves me lots of space :angel:
Yeah I am getting somewhat better living on the cloud
Related
ok due to the massive number of people clogging the offical thread im starting this thread just to help some of our newer members get working. anyone with a proper working install can help as well. let the issues begin.
i have no data connection at all i have installed 1.6 from htc and then 4.1.99. I even went back and wiped and reinstalled both rebooted and still no connection (3g or 2g).
any ideas
when you signed into google did it work or say cant connect?
Ok here's a question. I was running 4.1.11 which was running fine. I downloaded the recovery image & flashed it thru the recovery console (home + power) and then tried to flash 4.1.99 & now when i try going into the recovery console, I get the Exclamation point with the phone on its side. If i let it power thru it loads up, but like its stock.
I even tried terminal emulation & can't even get the SU command to work.
Any suggestions besides, re-rooting?
This is what I did
Okay, let me start off by saying I have had none of the lag a lot of the people are reporting. So I figured I would post how I installed step by step just incase it helps someone.
Step 1: Download the HTC rom and Cyanogen rom.
Step 2: Reboot into recovery.
Step 3: Flash the HTC update from recovery and let it finish ( it will do the radio as well) the phone will reboot back into recovery by itself.
Step 4: Wipe.
Step 5: Flash the Cyanogen update.
Step 6: Enjoy.
Don't think it would make any diff but just incase, I came from JACxHEROSkiv2.2 and cm 1.4 recovery.
Hope this helps in any way.
yes the same thing happened to me. its very simple too. just fastboot cyanogens recovery.img
http://forum.xda-developers.com/showthread.php?p=3915123
heres fastboot stuff
http://forum.xda-developers.com/showthread.php?t=502010
then flash newest cyanogens like normal and wipe afterwards.
Whenever I follow the steps, the rom is unusuable. This is both before and after a wipe. Everything slows down and crashes. It won't even boot fully, because the launcher has issues. I don't know what to do. Any suggestions? Im about to wipe my EXT3 partition
Every time I try updating to 4.1.99 It stays on the g1 screen.
persiansown said:
Whenever I follow the steps, the rom is unusuable. This is both before and after a wipe. Everything slows down and crashes. It won't even boot fully, because the launcher has issues. I don't know what to do. Any suggestions? Im about to wipe my EXT3 partition
Click to expand...
Click to collapse
try wiping your ext3 however please note alot is going on first boot. i didnt have any issues with slow but i wiped my ext3 and data(wipe in recovery) slow downs are caused mostly by missing or incompatible issues. thats why wiping is recommended. try wiping ext3 and start from scratch. its worth it.
10-05 05:16:25.477: INFO//system/xbin/busybox(49): +++ Apps-to-SD successfully enabled
10-05 05:16:25.517: INFO//system/xbin/busybox(49): /system/etc/init.d/05userinit: 14: Syntax error: "fi" unexpected (expecting "then")
10-05 05:16:25.517: INFO//system/xbin/busybox(49): run-parts: /system/etc/init.d/05userinit exited with code 2
jeremycool said:
Every time I try updating to 4.1.99 It stays on the g1 screen.
Click to expand...
Click to collapse
did you flash the adp image first?
mormo said:
10-05 05:16:25.477: INFO//system/xbin/busybox(49): +++ Apps-to-SD successfully enabled
10-05 05:16:25.517: INFO//system/xbin/busybox(49): /system/etc/init.d/05userinit: 14: Syntax error: "fi" unexpected (expecting "then")
10-05 05:16:25.517: INFO//system/xbin/busybox(49): run-parts: /system/etc/init.d/05userinit exited with code 2
Click to expand...
Click to collapse
check your md5s on both and start from scratch.
Here's what I did:
1. Wipe.
2. Delete all your EXT partition stuff.
3. Reboot into recovery.
4. Flashed the HTC update from recovery. I did NOT reboot after this finished.
5. Flashed the Cyanogen update.
6. Rebooted and waited for the post flashing process to finish.
I had one single FC at the beginning but now it's all good.
If you are not clearing out your dalvik cache and all your other EXT stuff AND wiping, then it's only not working because you didn't do those things.
yes both ways work. however if you have issues try letting the radio install. ONLY if you have issues.
here's a question:
Why are some how to's telling you to flash the 2 files and simply fix permissions while others are saying you need to wipe? it seem like some are running fine without the wipe.
Also, did this myself without wiping and getting google fc at reboot. I've been reading these threads for like 2 hours now and i was under the impression the market, etc. would still work but it's backing out of the white screen and not loading it up. Is that my only option is to do a wipe now? And if i wipe, do i need to reflash anything?
Big thanks to cyan and everyone else for so much help! thank guys!
the reason some people have to let the radio flash is due to either a bad flash. corrupted install or some other reason. every new version come with a new radio and it will sometimes delete your recovery. this is because certain older setup are different and not very consistant. however things happen and some stuff gets messed up. every dream is the same and this software is the same. but you are the different part.
damngood98 said:
here's a question:
Why are some how to's telling you to flash the 2 files and simply fix permissions while others are saying you need to wipe? it seem like some are running fine without the wipe.
Also, did this myself without wiping and getting google fc at reboot. Is that my only option is to do a wipe now? And if i wipe, do i need to reflash anything?
Big thanks to cyan and everyone else for so much help! thank guys!
Click to expand...
Click to collapse
wipe is to fix an issue with google apps. as well as if you had something before causing issues.
damngood98 said:
Also, did this myself without wiping and getting google fc at reboot. Is that my only option is to do a wipe now? And if i wipe, do i need to reflash anything?
Click to expand...
Click to collapse
Not sure if it is your only option, but it might help. And no you will not need to flash anything afterwards.
jokersax11 said:
wipe is to fix an issue with google apps. as well as if you had something before causing issues.
Click to expand...
Click to collapse
damn! gonna go bed and maybe pout for a bit tomorrow before i do another wipe. I hate wiping!
thanks for help joker!
damngood98 said:
here's a question:
Why are some how to's telling you to flash the 2 files and simply fix permissions while others are saying you need to wipe? it seem like some are running fine without the wipe.
Also, did this myself without wiping and getting google fc at reboot. I've been reading these threads for like 2 hours now and i was under the impression the market, etc. would still work but it's backing out of the white screen and not loading it up. Is that my only option is to do a wipe now? And if i wipe, do i need to reflash anything?
Big thanks to cyan and everyone else for so much help! thank guys!
Click to expand...
Click to collapse
Look at it this way...
You moved into a new place and the last tenant was evicted. He left all his crap lying around (mostly trash and dirty laundry.)
Do you sweep the rooms and take out the trash and call it a day? Or do you clean the whole house first? Technically, taking the trash should be enough (laundry included) but you never know what else is hiding in the house (maybe he had a pet tarrantula and it's walking around unbeknown to you. Eventually, you'll run into it and force close yourself in shock.
I have flashed my Hero with many ROMS, mostly the Cyanogen nightly's. I have seen recently a huge lag no matter which build I use. I think there may be a corrupt file left behind that is causing the problems.
How can I erase everything and start completely from scratch? I have already done a wipse and re-imaged from there and it doesn't seem to help.
Run the officail RUU, then re-root again. that is all you need to do.
Sent from my HERO200 using XDA App
fowen said:
I have already done a wipse and re-imaged from there and it doesn't seem to help.
Click to expand...
Click to collapse
What all did you wipe? Make sure to wipe everything. You shouldn't have to go back to an official Sprint ROM and reroot. Just wipe everything and reflash the ROM you want.
ranger61878 said:
What all did you wipe? Make sure to wipe everything. You shouldn't have to go back to an official Sprint ROM and reroot. Just wipe everything and reflash the ROM you want.
Click to expand...
Click to collapse
I tried to wipe everything but I got errors asking me to do it through ADP. Since I am a newb with all of this I was hoping there was an easy way to do it.
fowen said:
I tried to wipe everything but I got errors asking me to do it through ADP. Since I am a newb with all of this I was hoping there was an easy way to do it.
Click to expand...
Click to collapse
If you are using the Amon Recovery v1.5.2, it does actually wipe everything even thought it gives you that 'run via adb' nonsense. It's just a small error/bug in that version of recovery that doesn't output the correct string of text, but the wiping part does work correctly and it does actually wipe Dalvik, data, ext, etc. even though the output tells you something else.
As said above, you need to wipe ALL of those (except battery) every time you flash a new ROM, or else it can lead to some corruption like you are experiencing. If still unsatisfied or if you still can't get things to work, then rerun the official RUU as also suggested above to start fresh. But I will tell you that I've never had to rerun the RUU before in the entire 6 months I've been rooted, so I think your problem is maybe just incorrect procedure between wiping and flashing ROMs. All phones are different though. Good luck, and please keep posting so we can continue to help you out.
fowen said:
I tried to wipe everything but I got errors asking me to do it through ADP. Since I am a newb with all of this I was hoping there was an easy way to do it.
Click to expand...
Click to collapse
What recovery are you using? Anyways, the RUU wipes everything, no need to wipe beforehand, see this to RUU
I haven't flashed many types of ROM's, only a few. I have been sticking with Cyanogen Mod I would say 90% of the time. I cleared out everything and it didn't seem to help much.
Most of the time it lags when I am dealing with email, or a email comes in. Last week I got tired of it and OC'd it up to 768 and I saw a huge difference but my battery died after 6 hours. Even with the CPU clocked to 768 I can notice a huge difference when I have a email coming in.
I just flashed to Cyanogen's newest nightly to see if there are any differences. If not, I will try to un-root and flash directly to Cyanogen's rom. Will I need to clear everything before going to a new rom from stock?
I am trying to flash back to Stock and I received an error basically saying the bootloader was wrong. It appears this happens when you are trying to go backwards. I am trying to go from CyanogenMod 6.1 (Froyo) to the stock 1.5 build. Is this not what i am supposed to do?
fowen said:
I am trying to flash back to Stock and I received an error basically saying the bootloader was wrong. It appears this happens when you are trying to go backwards. I am trying to go from CyanogenMod 6.1 (Froyo) to the stock 1.5 build. Is this not what i am supposed to do?
Click to expand...
Click to collapse
Assuming you mean going back to pre-root, right out of the box state...you need to run the official RUU from your computer, not via recovery.
Yes, I am trying to go to a pre-rooted state.
I tried that, and it could never detect my android phone. I googled the error message and someone said to try it from the fast boot mode. I rebooted my phone into this and re-ran the update. It got further along but it came up with this error message along the way.
fowen said:
Yes, I am trying to go to a pre-rooted state.
I tried that, and it could never detect my android phone. I googled the error message and someone said to try it from the fast boot mode. I rebooted my phone into this and re-ran the update. It got further along but it came up with this error message along the way.
Click to expand...
Click to collapse
You are using HTC Sync and have the USB drivers installed?
----------
Sent from the XDA App on my FroYoed Sprint Hero...so forgive my inevitable typos
Sounds like a driver issue. Also make sure you have USB debugging on, otherwise adb will not recognize your device.
I've run across issues with loose fragments of data being left after a wipe via recovery. My favorite was the home key ceasing to work. A full wipe via fastboot always seems to do the trick. Just make sure you have a copy of your recovery image to reflash when done. You'll need the ENG SPL as well.
You'll do this all via adb.
In bootloader:
fastboot erase system -w
fastboot erase boot
fastboot boot your_recovery_image.img
adb shell mount /sdcard
adb push your_recovery_image.img /sdcard/your_recovery_image.img
adb shell flash_image recovery /sdcard/your_recovery_image.img
adb shell reboot
Just make sure your recovery image is on the root of your sdcard. Full wipe in minutes without that long ruu process! I've been doing this every time I flash a new ROM lately, never an issue.
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...
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.
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.