So yeah i installed Marshmallow on my K3 Note via the OTA update (had to replace CWM with stock recovery for it to work, but in the end it did)
Now the question is, how do i root my phone?
Will the same Lollipop process work for Marshmallow?
I dont think that method will work.
Read here: http://www.needrom.com/download/row-s422/
please help me too..!!!
shinudgr8 said:
So yeah i installed Marshmallow on my K3 Note via the OTA update (had to replace CWM with stock recovery for it to work, but in the end it did)
Now the question is, how do i root my phone?
Will the same Lollipop process work for Marshmallow?
Click to expand...
Click to collapse
i had tried everything no use.. anyone please help to root the update version... lenovo k3 note...:crying::crying::crying::crying::crying::crying:
Alright, I first updated my phone to marshmallow, then flashed twrp recovery. Until then everything was alright, it was working just fine.
Then I installed the update.zip for lollipop to root it, and installed the zip via twrp.
It resulted in my phone going into something we all know as "soft brick". It did proceed the lenovo screen, but after that I was greeted with an static black screen. ADB wasn't working either, so I couldn't boot it into bootloader or recovery. I manually booted into the recovery mode using the button sequence (volUp+volDown+power) and wiped the data. Nothing, still didn't boot. Then I finally gave up, downloaded the stock lollipop rom from somewhere, and flashed it via spflash tool. Then updated everything back to marshmallow
In short, the old twrp and cwm recoveries (probably, mostly actually) work with marshmallow, so I guess that's a start
it work well...
shinudgr8 said:
Alright, I first updated my phone to marshmallow, then flashed twrp recovery. Until then everything was alright, it was working just fine.
Then I installed the update.zip for lollipop to root it, and installed the zip via twrp.
It resulted in my phone going into something we all know as "soft brick". It did proceed the lenovo screen, but after that I was greeted with an static black screen. ADB wasn't working either, so I couldn't boot it into bootloader or recovery. I manually booted into the recovery mode using the button sequence (volUp+volDown+power) and wiped the data. Nothing, still didn't boot. Then I finally gave up, downloaded the stock lollipop rom from somewhere, and flashed it via spflash tool. Then updated everything back to marshmallow
In short, the old twrp and cwm recoveries (probably, mostly actually) work with marshmallow, so I guess that's a start
Click to expand...
Click to collapse
no ya it works well.. but cant find a way root it....
ChainFire Beta SuperUser for Marshmallow K3 Note
Hi,
You may try the steps "androiding.how" on how to root the Lenovo K3 Note after the Marshmallow OTA update.
NOTE : THE ABOVE WOULD ONLY WORK THROUGH CWM/TWRP Recovery. Use the older Lollipop TWRP/CWM recovery. It should work.
Where is the link??
Fizix7 said:
Where is the link??
Click to expand...
Click to collapse
androiding.how is the website. Just go to the website and you will find the information on the webpage. It wont let me put the link in the post.
Hope it helps!!
massguy786 said:
androiding.how is the website. Just go to the website and you will find the information on the webpage. It wont let me put the link in the post.
Hope it helps!!
Click to expand...
Click to collapse
Interesting, never thought it could be this easy, I literally installed marshmallow the other day and now hopefully now I can root it again
So what's the final verdict boss? Did you try the process yourself? Was it successful? Or am I to be the first guinea pig?
I also got back to stock recovery from TWRP. but my update to marshmallow failed, can you help? I had rooted with Lenovo k3 note manager by prince3v. it also installed twrp. Using the same tool I went back to stock. Thanks.
shinudgr8 said:
Alright, I first updated my phone to marshmallow, then flashed twrp recovery. Until then everything was alright, it was working just fine.
Then I installed the update.zip for lollipop to root it, and installed the zip via twrp.
It resulted in my phone going into something we all know as "soft brick". It did proceed the lenovo screen, but after that I was greeted with an static black screen. ADB wasn't working either, so I couldn't boot it into bootloader or recovery. I manually booted into the recovery mode using the button sequence (volUp+volDown+power) and wiped the data. Nothing, still didn't boot. Then I finally gave up, downloaded the stock lollipop rom from somewhere, and flashed it via spflash tool. Then updated everything back to marshmallow
In short, the old twrp and cwm recoveries (probably, mostly actually) work with marshmallow, so I guess that's a start
Click to expand...
Click to collapse
That supersu file is the one causing problem. I started from scratch, and got marshmallow working. But as soon as I flash data.zip file, it gets stuck at empty black screen. It works without supersu fine, sadly no root.
shinudgr8 said:
Interesting, never thought it could be this easy, I literally installed marshmallow the other day and now hopefully now I can root it again
So what's the final verdict boss? Did you try the process yourself? Was it successful? Or am I to be the first guinea pig?
Click to expand...
Click to collapse
LOL... It will work.. You are not the Guinea pig...
Related
Verizon LG G2
Rooted
Installed TWRP
Without thinking (doink) tried to install the latest OTA.
OTA failed.
Now I cannot reboot into TWRP.
Installed ClockwordMOD and installed its own custom recovery. Still won't boot into any custom recovery.
Phone works fine other than that.
How can I get back into custom reccovery?
Note: When I turn phone off and try to reboot into custom recovery it takes me to the "reset" screen.. and then IT RESETS the phone.
When I try to boot into recovery from Clockwork or TWRP app it gives me the android robot with the open tummy and red triangle.
Danokan said:
Verizon LG G2
Rooted
Installed TWRP
Without thinking (doink) tried to install the latest OTA.
OTA failed.
Now I cannot reboot into TWRP.
Installed ClockwordMOD and installed its own custom recovery. Still won't boot into any custom recovery.
Phone works fine other than that.
How can I get back into custom reccovery?
Note: When I turn phone off and try to reboot into custom recovery it takes me to the "reset" screen.. and then IT RESETS the phone.
When I try to boot into recovery from Clockwork or TWRP app it gives me the android robot with the open tummy and red triangle.
Click to expand...
Click to collapse
The OTA update installed the KitKat bootloader, which hasn't been hacked for custom recovery yet.
Use this to downgrade the only the bootloader and install custom recovery: http://forum.xda-developers.com/showthread.php?t=2715496
You have to root frist. You can use IORoot25 to root the KitKat rom that you have now: http://forum.xda-developers.com/showpost.php?p=48709232
Amro90 said:
The OTA update installed the KitKat bootloader, which hasn't been hacked for custom recovery yet.
Use this to downgrade the only the bootloader and install custom recovery: http://forum.xda-developers.com/showthread.php?t=2715496
You have to root frist. You can use IORoot25 to root the KitKat rom that you have now: http://forum.xda-developers.com/showpost.php?p=48709232
Click to expand...
Click to collapse
Ok.
The KITKAT rom didn't install properly..
Phone says 4.2.2
Super user and apps that need root to work are working properly. Looks like the bootloader is the only thing that got hit.
Danokan said:
Ok.
The KITKAT rom didn't install properly..
Phone says 4.2.2
Super user and apps that need root to work are working properly. Looks like the bootloader is the only thing that got hit.
Click to expand...
Click to collapse
Oh. Not sure if AutoRec works if you are still on 4.2.2. Sorry bout that.
If it doesn't work, you can always just manually flash the complete firmware using this guide: http://forum.xda-developers.com/showthread.php?t=2432476. Surest way to get back from failed flashes. You can flash the full 4.2.2 or 4.4.2 KDZ and then start over again. That method wipes everything though.
Amro90 said:
Oh. Not sure if AutoRec works if you are still on 4.2.2. Sorry bout that.
If it doesn't work, you can always just manually flash the complete firmware using this guide: http://forum.xda-developers.com/showthread.php?t=2432476. Surest way to get back from failed flashes. You can flash the full 4.2.2 or 4.4.2 KDZ and then start over again. That method wipes everything though.
Click to expand...
Click to collapse
YIKES.
Well.. it got the TWRP recovery loaded alright.
But it won't boot into anything else...light is flashing but screen is black.
HELP
I am screwed here.
#1. Tried the "unbrick stock" solution. Can NOT get it to work. I tried it all 3 ways given and it gets to the LG driver start... and then it says I am up to date. I tried to change the country, the language, upgrade recovery, can NOT get it to work.
#2. I can get TWRP to load. But I can't get my computer to recognize my phone so I can move a rom over
#3. I can't get ADB to recognize my phone.
HEEEEEEEEEEEEEEEEEEEEEEELP
Danokan said:
HELP
I am screwed here.
#1. Tried the "unbrick stock" solution. Can NOT get it to work. I tried it all 3 ways given and it gets to the LG driver start... and then it says I am up to date. I tried to change the country, the language, upgrade recovery, can NOT get it to work.
#2. I can get TWRP to load. But I can't get my computer to recognize my phone so I can move a rom over
#3. I can't get ADB to recognize my phone.
HEEEEEEEEEEEEEEEEEEEEEEELP
Click to expand...
Click to collapse
save yourself the hassle flash stock 4.4.2 KK, use IORoot25 to root and then use Autorec to install Custom recovery.
Time needed 1 hour.
Hartendief said:
save yourself the hassle flash stock 4.4.2 KK, use IORoot25 to root and then use Autorec to install Custom recovery.
Time needed 1 hour.
Click to expand...
Click to collapse
How do you propose I flash it?
SOLVED
FIXED
http://forum.xda-developers.com/showthread.php?t=2448960
So here's my little guide on returning your v410 to stock unrooted from kitkat.
First of all download the stock rooted rom by @timmytim
http://forum.xda-developers.com/g-p...-v410-onlykot49i-v4101d-4-4-2-rooted-t3040208
Next download the stock recovery img.
jason2678 said:
here's a link to an image I made before flashing twrp on my v410. I've restored it with dd and flashify and it works fine. https://docs.google.com/file/d/0B1l3W9XHAqEgX0ZCUWc1QTlfWjg/edit?usp=docslist_api
Click to expand...
Click to collapse
Have flashify installed
Busy box app by stericson installed, I have pro.
Boot into twrp
Flash stock rom. Do not wipe anything!!
Reboot
Wait for apps to optimize.
Upon reboot flash the stock recovery via flashify. Once succeeded just press the home button to exit out!!
Open busy box wait for it to load and choose uninstall, normal uninstall not smart.
Reboot
Upon reboot open up su. Do not update binary!!
Scroll through settings and tick Full Unroot, select yes and wait.
Once uninstalled it will exit out on it's own
Reboot
Download root checker and check, you should be unrooted and able to factory reset or whatever you choose.
You removed busy box so there should be no traces of root.
Has anyone tried this? I'm desperate to get back on stock OTA/unrooted, this tablet has just been too laggy for my liking on any custom ROM. I'm currently on CM nightlies, on LL.....
So this works fine, I said "screw it" last night and flashed it. I decided to keep root though......so I just went from CM Nightlies on LL....back to KK. Oh man I missed KK. :silly: :good:
Only thing is, I went into bootloop after flashing the ROM, so I booted into TWRP and did a full wipe (minus external SD), did a factory reset.....and flashed it again. Booted up fine, and with an hour I was getting a prompt for an OTA being available.
ok, i followed your guide here and several others on the interweb. I am stumped. I am trying to install the update, but when I do i get that updates are not for rooted devices.
I did do a full unroot via supersu and flashed the stock recovery. When I put it in download mode, it says that it is still rooted. What did I do wrong?
little background, this all started when i was stock rooted and running xposed and twrp, and accidentally allowed my kid to install an update with out looking and got stuck in a twrp bootloop. flashed test build and then I am here. Any help would be appreciated.
any updates?
joeclark said:
ok, i followed your guide here and several others on the interweb. I am stumped. I am trying to install the update, but when I do i get that updates are not for rooted devices.
I did do a full unroot via supersu and flashed the stock recovery. When I put it in download mode, it says that it is still rooted. What did I do wrong?.
Click to expand...
Click to collapse
Hey did the same and i'm now in the same predicament. i know its been a while but did u manage to figure it out by any chance?
Nope still sitting on my desk as a mouse pad
sent from a device using an app
LXative said:
So this works fine, I said "screw it" last night and flashed it. I decided to keep root though......so I just went from CM Nightlies on LL....back to KK. Oh man I missed KK. :silly: :good:
Only thing is, I went into bootloop after flashing the ROM, so I booted into TWRP and did a full wipe (minus external SD), did a factory reset.....and flashed it again. Booted up fine, and with an hour I was getting a prompt for an OTA being available.
Click to expand...
Click to collapse
did you have a Sim card in it?
---------- Post added at 03:47 PM ---------- Previous post was at 03:44 PM ----------
joeclark said:
ok, i followed your guide here and several others on the interweb. I am stumped. I am trying to install the update, but when I do i get that updates are not for rooted devices.
I did do a full unroot via supersu and flashed the stock recovery. When I put it in download mode, it says that it is still rooted. What did I do wrong?
little background, this all started when i was stock rooted and running xposed and twrp, and accidentally allowed my kid to install an update with out looking and got stuck in a twrp bootloop. flashed test build and then I am here. Any help would be appreciated.
Click to expand...
Click to collapse
ok so there is a zip for stock non testbuild. But how did the device pop up with a update wouldn't it not update if you had a custom recovery
Hi I am using the windroid toolkit trying to root my new x pure. I got thru the first two steps ok, with a message thats its ok to move on to step 3, root access by flashing superuser.... everytime I try to flash super user I get a message that the phone is in the wrong state? I am still in the fastboot mode, start option. Is that correct? I tried rebooting the phone into the recovery mode by selecting the power and up volume keys, but that did not work? Im confused.......If I got by the 2nd step, should team win be in the recovery? thanks for any ideas here......
Why do you need a toolkit to root?
update,,,, the toolkit was on youtube and looked like an easy way to go thru the unlock, install recovery, root process. It worked fine and fast for the first two sections. I have an unlocked bootloader and teamwin recovery. I went to a different video that showed how to flash superuser into the recovery. I did that and now the phone is stuck on the Android M bootup screen. I am able to boot into the fastboot flash mode and teamwin recovery, so Im not completely bricked. Just stuck on the boot screen. Turns out the flashing superuser method does not work on Marshmellow... Anyone know how to fix this?
Did a bunch of searching and after a very long night I was able to return to stock, 5.1.1. Phone is back to normal and rooted. Lots of info here....just need to find it.....
Garyalp said:
Did a bunch of searching and after a very long night I was able to return to stock, 5.1.1. Phone is back to normal and rooted. Lots of info here....just need to find it.....
Click to expand...
Click to collapse
You can update to Android M 6.0 and then you should flash SuperSU 2.62-3 through TWRP to gain root, after rooting with this version or SuperSU, you should be able to update to a new version of SuperSU, I have update to SuperSu 2.65 with no issue. This was the easiest way that I have found to root our phone running Android M 6.0.
Thank you for that information. Wish I had it from the beginning, would have saved a bunch of trouble. Turns out I spoke to soon. I am having the wi fi issue that some have had. I have gone from a stock 5.1.1 to 6.0, unlocked bootloader, teamwin recovery, soft brick, back to 5.1.1, now rooted. Not sure exactly where the phone is. The bootloader remained unlocked thru the reflash to stock 5.1.1. I noticed that the mac address and Ip address are both, "unavailable", when I go to: settings/wifi/ advanced. Most likely the reason wifi is inop. Is there a way to find the mac and Ip address? Which modem should I be on, now that Im 5.1.1? Will a factory reset bring them back or does that just clear user data? As you can tell I know just enough to be dangerous....lol.
mcx6 said:
You can update to Android M 6.0 and then you should flash SuperSU 2.62-3 through TWRP to gain root, after rooting with this version or SuperSU, you should be able to update to a new version of SuperSU, I have update to SuperSu 2.65 with no issue. This was the easiest way that I have found to root our phone running Android M 6.0.
Click to expand...
Click to collapse
exactly what I did, works great.
Does anyone have a copy of the stock recovery? I'm trying to upgrade to b150 (both automated via the setting menu and manually by secret menu) but every time it tries to flash the firmware, the phone just reboots to TWRP and sits there.
Any help would be appreciated.
The directions you should be following have a copy of the stock recovery, don't they? If not, post a link to those directions.
Bill R said:
Does anyone have a copy of the stock recovery? I'm trying to upgrade to b150 (both automated via the setting menu and manually by secret menu) but every time it tries to flash the firmware, the phone just reboots to TWRP and sits there.
Any help would be appreciated.
Click to expand...
Click to collapse
divineBliss said:
The directions you should be following have a copy of the stock recovery, don't they? If not, post a link to those directions.
Click to expand...
Click to collapse
The first attempt was not following a guide. It was by going into the AT&T Software Update settings applet (my phone is on b140 and b150 was downloaded this way). That would start to load the update, reboot the phone into TWRP and then sit there. Subsequent booting into the OS would only re-attempt to install the update which would again reboot to TWRP.
After recovering my phone from a pre-update backup I tried, somewhat, following this method:
https://forum.xda-developers.com/android/development/guide-how-to-update-b130-to-b140-b150-t3555254
I was able to install the stock b140 image from my SD card but where it said TWRP would be gone, mine still had it. Attempting the secret menu would start the firmware update which would, again, boot to TWRP and sit there.
The stock ROMs in that guide thread should have stock recovery images. Just restore one of those stock recovery images using TWRP. Does your phone still have root?
Bill R said:
The first attempt was not following a guide. It was by going into the AT&T Software Update settings applet (my phone is on b140 and b150 was downloaded this way). That would start to load the update, reboot the phone into TWRP and then sit there. Subsequent booting into the OS would only re-attempt to install the update which would again reboot to TWRP.
After recovering my phone from a pre-update backup I tried, somewhat, following this method:
https://forum.xda-developers.com/android/development/guide-how-to-update-b130-to-b140-b150-t3555254
I was able to install the stock b140 image from my SD card but where it said TWRP would be gone, mine still had it. Attempting the secret menu would start the firmware update which would, again, boot to TWRP and sit there.
Click to expand...
Click to collapse
divineBliss said:
The stock ROMs in that guide thread should have stock recovery images. Just restore one of those stock recovery images using TWRP. Does your phone still have root?
Click to expand...
Click to collapse
I checked when you asked and surprisingly it does not. I'm surprised because I thought I re-installed it when I flashed the b140 ROM from that thread.
I'll try again this evening.
Also, if you followed the rooting guides, you should have your own copy of the stock recovery in your first TWRP backup.
Bill R said:
I checked when you asked and surprisingly it does not. I'm surprised because I thought I re-installed it when I flashed the b140 ROM from that thread.
I'll try again this evening.
Click to expand...
Click to collapse
Bill R said:
I checked when you asked and surprisingly it does not. I'm surprised because I thought I re-installed it when I flashed the b140 ROM from that thread.
I'll try again this evening.
Click to expand...
Click to collapse
The roms do NOT include Stock Recovery or any recovery for that matter ...Roms don't flash recovery (none that I have ever flashed anyway)
If you need B140 Stock recovery it's here B140.Stock.recovery.img
The Guide kind of assumes you just did the B130 to B140 update and you already have stock recovery installed
and yes if your phone was B140 when you rooted it you should already have your own stock backup of B140
I have to confess to a case of cranial flatulence. I had made a stock recovery backup. I'll proceed to banging my head on my desk now.
Back to business. So, after breaking my phone three times today, I finally got it back to the stock b140 (H1611C07B140) from the other thread and I'm ready to try the firmware upgrade again. I still have TWRP on it though so I'm wondering if I should reinstall the stock recovery first before trying the firmware upgrade. The other thread states that the b140-to-b150 firmware should overwrite the recovery but for me every time I do the firmware it boots to TWRP and sits there.
Bill R said:
I have to confess to a case of cranial flatulence. I had made a stock recovery backup. I'll proceed to banging my head on my desk now.
Back to business. So, after breaking my phone three times today, I finally got it back to the stock b140 (H1611C07B140) from the other thread and I'm ready to try the firmware upgrade again. I still have TWRP on it though so I'm wondering if I should reinstall the stock recovery first before trying the firmware upgrade. The other thread states that the b140-to-b150 firmware should overwrite the recovery but for me every time I do the firmware it boots to TWRP and sits there.
Click to expand...
Click to collapse
Yes I corrected the Guide
Flash stock recovery before doing the dload/ update.app flash
as soon as the firmware update is done boot to the bootloader
fastboot boot H1611.TWRP.New.img
then mount cust / system and data and flash the B150.Stock.rom
also flash Supersu and reboot
Thanks guys! I was finally able to get the b150 on with the additional instructions. Key was a couple of items:
Me confusing TWRP that I already had with H1611.TWRP.New.img.
Needing to go back to the stock recovery for the firmware upgrade
Discovering, by chance, that to get to fastboot mode with the power + volume down button it had to be connected to the PC via USB. It doesn't work if not connected.
Tomorrow I will get to where I've been wanting by installing the ROM to get rid of the AT&T bloat.
So thanks again!
Bill R said:
Thanks guys! I was finally able to get the b150 on with the additional instructions. Key was a couple of items:
Me confusing TWRP that I already had with H1611.TWRP.New.img.
Needing to go back to the stock recovery for the firmware upgrade
Discovering, by chance, that to get to fastboot mode with the power + volume down button it had to be connected to the PC via USB. It doesn't work if not connected.
Tomorrow I will get to where I've been wanting by installing the ROM to get rid of the AT&T bloat.
So thanks again!
Click to expand...
Click to collapse
It's pretty clear in the guide
When it's done it will reboot the phone so now boot to the bootloader with power + volume down while hooked to the PC via USB
Click to expand...
Click to collapse
Anyway congratulations
I hope you Enjoy the CleanRom
This morning I my phone pesented itself in TWRP.
Maybe this is because over the past days I repeatedly got notifications that a system upgrade wanted to install itself (I have a modified 26s X720 from Tora33).
I rejected those notifications.
Now I am stuck in TWRP and I cannot get around it. What I tried:
Reinstalling previous firmware (Tora33 26s) still on the phone
Restoring a TWRP backup from 6 months ago (TWRP didn't see it, maybe it's from a previous TWRP version, I now have v. 3.1)
Flash via fastbood factory image using Mauro's Tool All In One (error message "can't find file mke2fs.conf")
Wipe data, cache, dalvik cache, system; then install Mauro_V2.2 cleansed 23s firmware which I transferred to the phone
Every time it boots up in TWRP.
Your bricked you never flash ota with twrp you should read before doing anything.
The only thing that can help is ofil.
I suggest you study well before trying it.
Sent from my LEX720 using xda premium
mchlbenner said:
Your bricked you never flash ota with twrp you should read before doing anything.
The only thing that can help is ofil.
I suggest you study well before trying it.
Click to expand...
Click to collapse
Oh boy. Thanks anyway. OTA flashed itself, couldn't stop it. Maybe I made it worse by trying to fix.
The bootloader is not locked according to the AIO tool. I can flash succesfully any firmware, only after flashing the phone will still boot in TWRP. It is strange it still boots in TWRP. Is there no simpler trick like flashing the standard recovery and then flashing OFW?
You mention Ofil; do you think the guide described here work?
Wortelstok said:
Oh boy. Thanks anyway. OTA flashed itself, couldn't stop it. Maybe I made it worse by trying to fix.
The bootloader is not locked according to the AIO tool. I can flash succesfully any firmware, only after flashing the phone will still boot in TWRP. It is strange it still boots in TWRP. Is there no simpler trick like flashing the standard recovery and then flashing OFW?
You mention Ofil; do you think the guide described here work?
Click to expand...
Click to collapse
Yes, that QFIL guide is for the x720.
In my opinion, the best way to return stock is to push update.zip into phones main folder, then install stock recovery, then in this one install update zip then check that OS is working. If it is, then go into twrp and wipe. Can't do it?
I'll mention myself;
https://forum.xda-developers.com/le-pro3/how-to/guide-simple-to-return-to-stock-x720-t3618658
marik1 said:
In my opinion, the best way to return stock is to push update.zip into phones main folder, then install stock recovery, then in this one install update zip then check that OS is working. If it is, then go into twrp and wipe. Can't do it?
I'll mention myself;
https://forum.xda-developers.com/le-pro3/how-to/guide-simple-to-return-to-stock-x720-t3618658
Click to expand...
Click to collapse
If he was just going back stock that would work he flash 28s ota with twrp so this will not work.
Sent from my LEX720 using xda premium
No brick after OFW push 28s
The pushed (unvoluntary) update didn't brick my phone after all. This may be important for those that have modified stock ROMs with TWRP.
Not being able to restore OFW was a bug in Mauro's All-in-One tool which he fixed last night. After I could easily flash 20S or 26S stock from his repository. I would also recommend this as safest/easiest procedure. Afterwards you can just flash TWRP from the same tool and move from there.
By the way, immediately after flashing 20s the FW notified it wanted to update itself, again!
n my opinion, the best way to return stock is to push update.zip into phones main folder, then install stock recovery, then in this one install update zip then check that OS is working. If it is, then go into twrp and wipe. Can't do it?
Click to expand...
Click to collapse
Might have tried that